kmplot_20.12.0-1_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 24 Dec 2020 08:22:49 +0100 Source: kmplot Architecture: source Version: 4:20.12.0-1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Aurélien COUDERC Changes: kmplot (4:20.12.0-1) unstable; urgency=medium . * Team upload. * New upstream release (20.12.0). * Refresh copyright information. * Bump Standards-Version to 4.5.1, no change required. * Bump debhelper compatibility level to 13. * Build with hardening=+all build hardening flag. * Borrow minimal upstream signing key from k3b. * Refresh upstream metadata. * Add Rules-Requires-Root: no. * Drop kde-l10n migration rules, not needed anymore after 2 stable releases. Checksums-Sha1: 19f8bca0ba8f87a841fe7b870256b0ba59d47c33 2607 kmplot_20.12.0-1.dsc 81697c9bd1b95f9b51bb6baa5981300d4d8266a8 3055868 kmplot_20.12.0.orig.tar.xz e90dab15fe75f933dfdc526d9b3e7e7c3cef1826 488 kmplot_20.12.0.orig.tar.xz.asc 925712579eb9b5058236d0e91c99ca473df5820c 7608 kmplot_20.12.0-1.debian.tar.xz 13d559974c6101de27b95cb400b36e0fda9e0a17 21165 kmplot_20.12.0-1_amd64.buildinfo Checksums-Sha256: fd7dea8aadbfcc923f00871d6e488146a37ffa844c7bc517a4cba125fae66a63 2607 kmplot_20.12.0-1.dsc d5ac4d6cc79fdbf4d073588a3b9e20bfb69a115b38e6516c6e1823a29e507cbd 3055868 kmplot_20.12.0.orig.tar.xz c3e5bb9eff060cde55315f189295b4dd40c449fb2fa59ec7a8ae4cb4f8985e22 488 kmplot_20.12.0.orig.tar.xz.asc b4ee6defd5505a8f2cb468223083da7c6042bdf677c31b3b868630da9d8554ed 7608 kmplot_20.12.0-1.debian.tar.xz 66894065f4574bae7758ea6b13a99e74c4339e644dbb3cc8df74a1441894aa9d 21165 kmplot_20.12.0-1_amd64.buildinfo Files: 1725521efaf497978e3da9f4b89ff0e0 2607 kde optional kmplot_20.12.0-1.dsc 991ee45be28e61cb597ff20dfa598913 3055868 kde optional kmplot_20.12.0.orig.tar.xz 8d48868998411bc7785dc9d946451d74 488 kde optional kmplot_20.12.0.orig.tar.xz.asc 1c4636980a3919aac159c57c19ea7486 7608 kde optional kmplot_20.12.0-1.debian.tar.xz 91e4ec62a8cf98bfbb988f436625c1c1 21165 kde optional kmplot_20.12.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAl/kQfgTHGNvdWNvdWZA ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJHtAD/0XSt1pf1JWc3XyozgGJs287Ak8jFc6 4Si8l5bwwR6zoQLFbdAIX0lh7a0I0NHESBsUXQwaB9k7w8MYl3aU13ndfxHDbqsN XbkSi0eKO0mNwpdk/0FMVPSqxOVU6XNRZi6tJg78b89gKa69ZYP4GoCnEVqGUVW5 3Vam/AtnvQvdbUqu5Xdc2BNcDPETadL0BNinhCKWUx07eE7V6CD5qfKzquH36SpY qgoY1W9MTQM4GOROybm6u6ik7MXEJmAnvpQNm9aW2fe5PkkQxyn8b79c1rHwK5IG KGlOuTUBxbBsTD6+k+0R8CYYE3X82H3AZo8ehJJgP787OZ/Rsb+djwmqZMO5uwuG fHBn/0/HekKMkDa/nkJW1asrfoqoIuFe2NfWzqMdToi1d2nwVvic29umu4T4WdHd ZaxRoyc2sVMuGNDiYCEO01n7g+dvADEojJaq9Jfvp6tC14ndxgp+fZnXb396qe9h qMeyOtORYtMPfM3eR1cPIycigDtK51Bv/rLZYazROuPR++Mq3H8PmshX73mUPf3I yvcC55JHtRc+ynq85vLwqdG44pWsHAKaRsGSE7+hLLJBVOPk+nx55buGHu8wpA+d a4Ic0YZti+eGol4JuoT1mVQb3AWnbOG7gFMQ2iXUXYhNG2PHrGfq7PJb/3C0sWPx tFXdFtqA7Me7fQ== =wZJy -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#978008: libkwaylandserver5: undefined symbol: _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE"
Package: libkwaylandserver5 Version: 5.20.4-2 Severity: grave Justification: renders package unusable Dear Maintainer, After today Sid upgrades my KDE desktop failed to fully load after login. I see background and KDE spinner, but desktop does not appear. I've found this in `~/.xsession-errors`: ``` /usr/bin/kwin: symbol lookup error: /lib/x86_64-linux-gnu/libkwin.so.5: undefined symbol: _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShe llSurfaceInterfaceE ``` I've downgraded libkwaylandserver5 (to 5.19.5-2), kwayland-integration (to 5.19.5-3) and kwayland-data (to 4:5.74.0-2), rebooted and it started working again. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8), LANGUAGE=lt Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#974827: forwarded bug upstream
forwarded -1 https://bugs.kde.org/show_bug.cgi?id=430719
Bug#978008: libkwaylandserver5: undefined symbol: _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE"
I've reproduced same issue on VM. It seems that I have go perform `full-upgrade` that removes `user-manager`. After that KDE desktop works. If I try to install `user-manager` again, I get suggestion to remove whole kde-plasma-dekstop & friends...
Bug#974821: forwarded bug upstream
forwarded -1 https://bugs.kde.org/show_bug.cgi?id=430721
Bug#974860: Forwarded to upstream
forwarded -1 https://bugs.kde.org/show_bug.cgi?id=430787
Bug#978006: extra-cmake-modules: please change the section of the package
Package: extra-cmake-modules Version: 5.77.0-2 Severity: normal Dear Maintainer, when I run "deborphan" on my system, the extra-cmake-modules package is always listed as an "orphaned" library. This comes from the fact that this package is in the "libs" section and no other package depends on it: $ dpkg -s extra-cmake-modules [...] Section: libs How about changing the section from "libs" to "devel"? (the cmake package belongs to the devel section) -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-trunk-rt-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled extra-cmake-modules depends on no packages. extra-cmake-modules recommends no packages. Versions of packages extra-cmake-modules suggests: ii qt5-qmake5.15.2+dfsg-2 ii qtbase5-dev 5.15.2+dfsg-2 -- no debconf information -- Laurent.
Bug#974860: Forwarded to upstream
Silvério Santos - 24.12.20, 14:18:18 CET: > forwarded -1 https://bugs.kde.org/show_bug.cgi?id=430787 Please retest once you upgraded to Plasma 5.20 and KF 5.77. They should appear in testing soon. Have a Merry Christmas if you celebrate it, have a quiet and peaceful time, -- Martin
Processed: bug 974860 is forwarded to https://bugs.kde.org/show_bug.cgi?id=430787
Processing commands for cont...@bugs.debian.org: > forwarded 974860 https://bugs.kde.org/show_bug.cgi?id=430787 Bug #974860 [kmail] kmail: When moving an email into a subfolder on KDE Plasma Wayland the context menu does not appear at the target subfolder Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=430787'. > thanks Stopping processing here. Please contact me if you need assistance. -- 974860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974860 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955730: krita does not start under wayland
severity 955730 wishlist retitle 955730 krita does not support wayland forwarded 955730 https://bugs.kde.org/show_bug.cgi?id=429079 thanks Hi, In data sabato 4 aprile 2020 11:22:08 CET, Nicolas Évrard ha scritto: > I have started to use sway as my primary window manager unfortunately > krita does not work with wayland it seems. Other Qt applications seems > to work just find (provided I set the right environment variable ie > QT_QPA_PLATFORM=wayland) krita has never supported Wayland so far. It uses various X technologies (e.g. tablet support, color management) that are not available under Wayland, or nobody worked on them in krita. There is an upstream bug mentioning this: https://bugs.kde.org/show_bug.cgi?id=429079 starting from the upcoming version 4.4.2, you will even get an error message with krita closing itself afterwards in case you are running under Wayland. Please run krita within XWayland until proper Wayland support is implemented in krita. Thanks, -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#955730: krita does not start under wayland
Processing commands for cont...@bugs.debian.org: > severity 955730 wishlist Bug #955730 [krita] krita does not start under wayland Severity set to 'wishlist' from 'important' > retitle 955730 krita does not support wayland Bug #955730 [krita] krita does not start under wayland Changed Bug title to 'krita does not support wayland' from 'krita does not start under wayland'. > forwarded 955730 https://bugs.kde.org/show_bug.cgi?id=429079 Bug #955730 [krita] krita does not support wayland Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=429079'. > thanks Stopping processing here. Please contact me if you need assistance. -- 955730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955730 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#977329: krita segfaults when try to open with libQt5Gui.so.5.15.1
Processing commands for cont...@bugs.debian.org: > tag 977329 + moreinfo Bug #977329 [krita] krita segfaults when try to open with libQt5Gui.so.5.15.1 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 977329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977329: krita segfaults when try to open with libQt5Gui.so.5.15.1
tag 977329 + moreinfo thanks Hi, In data lunedì 14 dicembre 2020 02:12:14 CET, proctor ha scritto: > Package: krita > Version: 1:4.4.1+dfsg-1+b1 > Severity: important > X-Debbugs-Cc: damonswir...@gmail.com > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? >* What outcome did you expect instead? > > *** End of the template - remove these template lines *** > > > krita will not open. when i try i get this in dmesg and syslog > > [327378.536890] krita[1273329]: segfault at 0 ip 7efdeea7c190 sp > 7fff99cbf6f8 error 4 in libQt5Gui.so.5.15.1[7efdee9fe000+4c3000] > [327378.536895] Code: e0 10 48 09 f0 48 c1 e0 10 4c 09 e8 49 89 40 04 31 c0 > 66 41 89 40 0c 48 83 c4 18 4c 89 c0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 90 <48> > 8b 06 8b 56 08 48 89 07 89 57 08 f0 83 00 01 c3 90 66 66 2e 0f > > krita does work on a similar system but with AMD video card (this machine > has nvidia card) so maybe this is a video driver problem instead? is so let > me know and i will try to file this bug there instead! Unfortunately this dmesg line is not exactly useful, it merely says it crashed "somewhere" within QtGui. Do you still get a crash in an up-to-date testing installation? What where you doing when krita crashed? Which desktop environment or WM are you running? Are you running a Wayland session or an Xorg session? In case you still get a crash: please follow these two pages to install the debug packages for krita, and get a stack trace of the crash: https://wiki.debian.org/HowToGetABacktrace https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thanks, -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Processed: bug 964463 is forwarded to https://bugs.kde.org/show_bug.cgi?id=423303
Processing commands for cont...@bugs.debian.org: > forwarded 964463 https://bugs.kde.org/show_bug.cgi?id=423303 Bug #964463 [krita] krita doesn't start with multiple monitors Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=423303'. > thanks Stopping processing here. Please contact me if you need assistance. -- 964463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964463: marked as done (krita doesn't start with multiple monitors)
Your message dated Thu, 24 Dec 2020 19:05:46 +0100 with message-id <11677523.nUPlyArG6x@thyrus> and subject line Re: Bug#964463: krita doesn't start with multiple monitors has caused the Debian Bug report #964463, regarding krita doesn't start with multiple monitors to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 964463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: krita Version: 1:4.3.0+dfsg-1 Severity: normal Dear Maintainer, I installed krita for the first time on this machine. When I start krita with just one monitor (eDP-1, regular notebook monitor) it works just fine, but not with my normal workplace setup with multiple monitors. These are my monitors (eDP-1 is disabled in this setup): > % xrandr -q | grep "\bconnected\b" > eDP-1 connected (normal left inverted right x axis y axis) > DP-2-2 connected primary 3840x2160+0+648 (normal left inverted right x axis y > axis) 596mm x 335mm > DP-2-3 connected 1800x2880+3840+0 left (normal left inverted right x axis y > axis) 518mm x 324mm I get this lines when starting krita: > % krita > Invalid profile : "/usr/share/color/icc/colord/Crayons.icc" "Crayon Colors" > Invalid profile : "/usr/share/color/icc/colord/x11-colors.icc" "X11 Colors" > qt.gui.icc: Unsupported ICC input color space 47524159 > qt.gui.icc: fromIccProfile: failed general sanity check > QPngHandler: Failed to parse ICC profile > qt.gui.icc: Unsupported ICC input color space 47524159 > qt.gui.icc: fromIccProfile: failed general sanity check > QPngHandler: Failed to parse ICC profile > qt.gui.icc: Unsupported ICC input color space 47524159 > qt.gui.icc: fromIccProfile: failed general sanity check > QPngHandler: Failed to parse ICC profile > qt.gui.icc: Unsupported ICC input color space 47524159 > qt.gui.icc: fromIccProfile: failed general sanity check > QPngHandler: Failed to parse ICC profile > qt.gui.icc: Unsupported ICC input color space 47524159 > qt.gui.icc: fromIccProfile: failed general sanity check > QPngHandler: Failed to parse ICC profile > QObject::startTimer: Timers cannot have negative intervals > /usr/lib/x86_64-linux-gnu/krita-python-libs/krita added to PYTHONPATH > ASSERT (krita): "screen < QGuiApplication::screens().size() && screen >= 0" > in file /build/krita-VZXkgT/krita-4.3.0+dfsg/libs/widgets/KoToolBox.cpp, line > 51 > [1]51107 abort krita I think only the assert is relevant to this bug. If you need any further information, give me a heads up :) -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (800, 'testing'), (600, 'oldoldstable'), (600, 'stable'), (600, 'oldstable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages krita depends on: ii krita-data1:4.3.0+dfsg-1 ii libc6 2.30-8 ii libexiv2-27 0.27.2-8 ii libfftw3-double3 3.3.8-2 ii libgcc-s1 10.1.0-4 ii libgif7 5.1.9-1 ii libgsl25 2.6+dfsg-2 ii libheif1 1.6.1-1 ii libilmbase24 2.3.0-6 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libkf5completion5 5.70.0-1 ii libkf5configcore5 5.70.0-1 ii libkf5configgui5 5.70.0-1 ii libkf5coreaddons5 5.70.0-1 ii libkf5crash5 5.70.0-1 ii libkf5guiaddons5 5.70.0-2 ii libkf5i18n5 5.70.0-1 ii libkf5itemviews5 5.70.0-1 ii libkf5widgetsaddons5 5.70.0-1 ii libkf5windowsystem5 5.70.0-1 ii liblcms2-22.9-4+b1 ii libopencolorio1v5 1.1.1~dfsg0-6+b1 ii libopenexr24 2.3.0-6 ii libopenjp2-7 2.3.1-1 ii libpng16-16 1.6.37-2 ii libpoppler-qt5-1 0.71.0-6 ii libpython3.8 3.8.4~rc1-1 ii libqt5concurrent5 5.14.2+dfsg-4 ii libqt5core5a 5.14.2+dfsg-4 ii libqt5dbus5 5.14.2+dfsg-4 ii libqt5gui55.14.2+dfsg-4 ii libqt5multimedia5 5.14.2-2 ii libqt5network55.14.2+dfsg-4 ii libqt5printsupport5 5.14.2+dfsg-4 ii libqt5qml55.14.2+dfsg-2 ii libqt5quick5 5.14.2+dfsg-2 ii libqt5quickwidgets5 5.14.2+dfsg-2 ii libqt5svg55.14.2-2 ii libqt5widgets55.14.2+dfsg-4 ii libqt5x11ext
Bug#947361: krita: Keyboard doesn't respond after some popups (f.e show color selector) are opened.
tag 947361 + moreinfo thanks Hi, In data mercoledì 25 dicembre 2019 18:45:19 CET, Fenix ha scritto: > Package: krita > Version: 1:4.2.8.2+dfsg-1 > Severity: normal > > Dear Maintainer, > > Krita seems to have problems with some popups docks, for example > color selector, minimal shade selector... After this controls are showed > if they are hidden just moving the pointer outside its domain, keyboard > doesn't respond anymore, unless you change to another program or window. > > Brush preset, for example, works fine. This type of popup are close > clicking outside and not just moving pointer outside. > > > * What led up to the situation? > > 1.- Create new image. > 2.- Open, for example, a color selector (Shift + I) > 3.- Select a color and move the cursor outside the selector. It > will be vanished. > 4.- Try to open again the color selector with Shift + I or made > something with keyboard: change to full screen, undo action (ctrl-z)... > 5.- The keyboard will not repond. > 6.- Change to another program and back to Krita (Krita must lost the > focus). > 7.- Try again show color selector (Shift + I). It will work again. > > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > If enter key is pressed just before choosing color in color > selector and with the pointer inside the control (for not hide it), the > keyboard works fine: accept other shourtuts. But if the popup is hide > only moving the pointer outside its domain, the keyboard will be stucked > into Krita. And only come back after loosing the focus into another > program or window. Can you still reproduce the issue with a more recent version of krita, like krita 4.4.1 currently available in testing? If so, can you please report the bug to the upstream development team, as they have more expertise than me? See the following page: https://docs.krita.org/en/untranslatable_pages/reporting_bugs.html Thanks, -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#947361: krita: Keyboard doesn't respond after some popups (f.e show color selector) are opened.
Processing commands for cont...@bugs.debian.org: > tag 947361 + moreinfo Bug #947361 [krita] krita: Keyboard doesn't respond after some popups (f.e show color selector) are opened. Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 947361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#813570: marked as done (krita-1.2.8.5+dfsg-1: Krita crashes by creating a new workspace)
Your message dated Thu, 24 Dec 2020 19:18:32 +0100 with message-id <7434464.MhkbZ0Pkbq@thyrus> and subject line Re: Bug#813570: krita-1.2.8.5+dfsg-1: Krita crashes by creating a new workspace has caused the Debian Bug report #813570, regarding krita-1.2.8.5+dfsg-1: Krita crashes by creating a new workspace to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 813570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: krita-1.2.8.5+dfsg-1 Version: krita-1.2.8.5+dfsg Severity: normal Dear Maintainer, * What led up to the situation? First Start of Krita after installation * What exactly did you do (or not do) that was effective (or ineffective)? Started program and tried to create a new workspace * What was the outcome of this action? The Program crashed and the KDE-Crash-Handler opened * What outcome did you expect instead? start working with Krita KDE-crash-handler output: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". [Current thread is 1 (Thread 0x733a8000 (LWP 2312))] Thread 6 (Thread 0x6e8cc410 (LWP 2327)): #0 0x742797a4 in __pthread_cond_wait (cond=0x17573c0, mutex=0x17573a8) at pthread_cond_wait.c:187 #1 0x76dc6688 in __pthread_cond_wait (cond=, mutex=) at forward.c:149 #2 0x75ac9318 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4 #3 0x75ac4f54 in QSemaphore::acquire(int) () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4 #4 0x7556419c in ?? () from /usr/lib/libkritaimage.so.13 #5 0x755645ac in ?? () from /usr/lib/libkritaimage.so.13 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 5 (Thread 0x6e0cc410 (LWP 2328)): #0 0x742797a4 in __pthread_cond_wait (cond=0x1757608, mutex=0x17575f0) at pthread_cond_wait.c:187 #1 0x76dc6688 in __pthread_cond_wait (cond=, mutex=) at forward.c:149 #2 0x75ac9318 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4 #3 0x75ac53dc in QSemaphore::tryAcquire(int, int) () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4 #4 0x75581a54 in KisTileDataSwapper::run() () from /usr/lib/libkritaimage.so.13 #5 0x75ac8d74 in ?? () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 4 (Thread 0x6ccff410 (LWP 2340)): #0 0x74279b30 in __pthread_cond_timedwait (cond=0x1bc0398, mutex=0x1bc0380, abstime=0x6ccfed6c) at pthread_cond_timedwait.c:199 #1 0x76dc66e4 in __pthread_cond_timedwait (cond=, mutex=, abstime=) at forward.c:162 #2 0x75ac92f0 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4 #3 0x75abc0a0 in ?? () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 3 (Thread 0x6c2ff410 (LWP 2341)): #0 0x742797a4 in __pthread_cond_wait (cond=0x1ee0ef8, mutex=0x1ee0ee0) at pthread_cond_wait.c:187 #1 0x76dc6688 in __pthread_cond_wait (cond=, mutex=) at forward.c:149 #2 0x75ac9318 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4 -- System Information: Distributor ID: Raspbian on Raspberry Pi Version 2 B Description:Raspbian GNU/Linux 8.0 (jessie) Release:8.0 Codename: jessie Architecture: armv7l Kernel: Linux 4.1.13-v7+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Hi, sorry for the late answer. In data mercoledì 3 febbraio 2016 09:14:35 CET, hai scritto: > Dear Maintainer, > >* What led up to the situation? > First Start of Krita after installation >* What exactly did you do (or not do) that was effective (or > ineffective)? > Started program and tried to create a new workspace >* What was the outcome of this action? > The Program crashed and the KDE-Crash-Handler opened >* What outcome did you expect instead? > start working with Krita > > KDE-crash-handler output: > Application: Krita (krita), signal: Segmentation fault > Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". > [Current thread is 1 (Thread 0x733a8000 (LWP 2312))] > > [...] > -- System Information: > Distributor ID: Raspbian on Raspberry Pi Version 2 B > Description: Raspbian GNU/Linux 8
Processed: bug 977413 is forwarded to https://bugs.kde.org/show_bug.cgi?id=425177
Processing commands for cont...@bugs.debian.org: > forwarded 977413 https://bugs.kde.org/show_bug.cgi?id=425177 Bug #977413 [kio] kio: Python, Ruby, etc. scripts are not opened in Dolphin 20.12.0 Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=425177'. > thanks Stopping processing here. Please contact me if you need assistance. -- 977413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962534: marked as done (kio: Filesystem browser doesn't display expand arrow for some folders)
Your message dated Thu, 24 Dec 2020 19:37:41 +0100 with message-id <3677278.taCxCBeP46@thyrus> and subject line Re: Bug#962534: kio: Filesystem browser doesn't display expand arrow for some folders has caused the Debian Bug report #962534, regarding kio: Filesystem browser doesn't display expand arrow for some folders to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 962534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kio Version: 5.70.1-1 Severity: important Tags: upstream Dear Maintainer, It is no longer possible to expand some folders in Kate's filesystem browser tree view. I believe this issue was caused by a change in kio, the upstream bug is here: https://bugs.kde.org/show_bug.cgi?id=419434 The bug report says it was fixed in kio 5.71, but Debian still has 5.70. Please upgrade the package as soon as possible. Thanks, Gregor -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (600, 'testing-debug'), (600, 'testing'), (100, 'unstable-debug'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kio depends on: ii libacl1 2.2.53-8 ii libc6 2.30-8 ii libgcc-s1 10.1.0-3 ii libgssapi-krb5-2 1.17-7 ii libkf5archive55.70.0-1 ii libkf5authcore5 5.70.0-1 ii libkf5codecs5 5.70.0-1 ii libkf5completion5 5.70.0-1 ii libkf5configcore5 5.70.0-1 ii libkf5configwidgets5 5.70.0-1 ii libkf5coreaddons5 5.70.0-1 ii libkf5dbusaddons5 5.70.0-1 ii libkf5doctools5 5.70.0-1 ii libkf5i18n5 5.70.0-1 ii libkf5itemviews5 5.70.0-1 ii libkf5kiocore55.70.1-1 ii libkf5kiontlm55.70.1-1 ii libkf5kiowidgets5 5.70.1-1 ii libkf5notifications5 5.70.0-1 ii libkf5service-bin 5.70.0-1 ii libkf5service55.70.0-1 ii libkf5solid5 5.70.0-1 ii libkf5textwidgets55.70.0-1 ii libkf5wallet-bin 5.70.0-1 ii libkf5wallet5 5.70.0-1 ii libkf5widgetsaddons5 5.70.0-1 ii libkf5windowsystem5 5.70.0-1 ii libqt5core5a 5.12.5+dfsg-10+b1 ii libqt5dbus5 5.12.5+dfsg-10+b1 ii libqt5gui55.12.5+dfsg-10+b1 ii libqt5network55.12.5+dfsg-10+b1 ii libqt5qml55.12.5-5 ii libqt5widgets55.12.5+dfsg-10+b1 ii libqt5x11extras5 5.12.5-1 ii libqt5xml55.12.5+dfsg-10+b1 ii libstdc++610.1.0-3 ii libxml2 2.9.10+dfsg-5+b1 ii libxslt1.11.1.34-4 kio recommends no packages. kio suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: kio Source-Version: 5.74.0-1 Done: Sandro Knauß In data martedì 9 giugno 2020 17:17:03 CET, Gregor Riepl ha scritto: > Package: kio > Version: 5.70.1-1 > Severity: important > Tags: upstream > > Dear Maintainer, > > It is no longer possible to expand some folders in Kate's filesystem browser > tree view. > > I believe this issue was caused by a change in kio, the upstream bug is here: > https://bugs.kde.org/show_bug.cgi?id=419434 > The bug report says it was fixed in kio 5.71, but Debian still has 5.70. > > Please upgrade the package as soon as possible. This was fixed by the upload of the version 5.74.0 that was done few months ago. Hence, closing. Thanks for your report, -- Pino Toscano signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#977413: marked as done (kio: Python, Ruby, etc. scripts are not opened in Dolphin 20.12.0)
Your message dated Thu, 24 Dec 2020 19:34:40 +0100 with message-id <3919650.Mh6RI2rZIc@thyrus> and subject line Re: Bug#977413: kio: Python, Ruby, etc. scripts are not opened in Dolphin 20.12.0 has caused the Debian Bug report #977413, regarding kio: Python, Ruby, etc. scripts are not opened in Dolphin 20.12.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 977413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kio Version: 5.74.0-2 Severity: normal Tags: patch X-Debbugs-Cc: sh200...@mail.ru After upgrading to Dolphin 20.12.0, I encountered the same bug as described in https://bugs.kde.org/show_bug.cgi?id=425177. If I'm trying to open a Python script in Dolphin, nothing happens. The bug is fixed in Frameworks 5.75. The relevant commit is https://invent.kde.org/frameworks/kio/-/commit/fdd7c47c85d5d6dbf21e05e7a0d6afcf383f1d24. If the patch from this commit is applied, the bug doesn't reproduce. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-4-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kio depends on: ii kded5 5.74.0-2 ii libacl1 2.2.53-8 ii libc6 2.31-5 ii libgcc-s1 10.2.0-19 ii libgssapi-krb5-2 1.18.3-4 ii libkf5archive55.74.0-2 ii libkf5authcore5 5.74.0-2 ii libkf5codecs5 5.74.0-2 ii libkf5completion5 5.74.0-2 ii libkf5configcore5 5.74.0-2 ii libkf5configwidgets5 5.74.0-2 ii libkf5coreaddons5 5.74.0-2 ii libkf5dbusaddons5 5.74.0-2 ii libkf5doctools5 5.74.0-2 ii libkf5i18n5 5.74.0-3 ii libkf5itemviews5 5.74.0-2 ii libkf5kiocore55.74.0-2.0.1 ii libkf5kiontlm55.74.0-2.0.1 ii libkf5kiowidgets5 5.74.0-2.0.1 ii libkf5notifications5 5.74.0-2 ii libkf5service-bin 5.74.0-2 ii libkf5service55.74.0-2 ii libkf5solid5 5.74.0-2 ii libkf5textwidgets55.74.0-2 ii libkf5wallet-bin 5.74.0-2 ii libkf5wallet5 5.74.0-2 ii libkf5widgetsaddons5 5.74.0-3 ii libkf5windowsystem5 5.74.0-2 ii libqt5core5a 5.15.1+dfsg-4 ii libqt5dbus5 5.15.1+dfsg-4 ii libqt5gui55.15.1+dfsg-4 ii libqt5network55.15.1+dfsg-4 ii libqt5qml55.15.1+dfsg-3 ii libqt5widgets55.15.1+dfsg-4 ii libqt5x11extras5 5.15.1-2 ii libqt5xml55.15.1+dfsg-4 ii libstdc++610.2.0-19 ii libxml2 2.9.10+dfsg-6.3+b1 ii libxslt1.11.1.34-4 kio recommends no packages. kio suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: kio Source-Version: 5.77.0-1 Done: Norbert Preining In data lunedì 14 dicembre 2020 22:43:26 CET, Alexander Kernozhitsky ha scritto: > Package: kio > Version: 5.74.0-2 > Severity: normal > Tags: patch > X-Debbugs-Cc: sh200...@mail.ru > > After upgrading to Dolphin 20.12.0, I encountered the same bug as described in > https://bugs.kde.org/show_bug.cgi?id=425177. If I'm trying to open a Python > script in Dolphin, nothing happens. > > The bug is fixed in Frameworks 5.75. The relevant commit is > https://invent.kde.org/frameworks/kio/-/commit/fdd7c47c85d5d6dbf21e05e7a0d6afcf383f1d24. > If the patch from this commit is applied, the bug doesn't reproduce. Recently kio 5.77.0 (along with the rest of Frameworks) was uploaded to experimental and then unstable, bring the fix for this bug as well. Hence, closing with the first version of kio available in Debian after 5.75.0. Thanks for your report, -- Pino Toscano signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#895962: marked as done (kio: http.so resource leak causing background CPU usage)
Your message dated Thu, 24 Dec 2020 19:41:21 +0100
with message-id <109123250.nniJfEyVGO@thyrus>
and subject line Re: Bug#895962: kio: http.so resource leak causing background
CPU usage
has caused the Debian Bug report #895962,
regarding kio: http.so resource leak causing background CPU usage
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
895962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kio
Version: 5.44.0-2
Severity: normal
http.so seems to have some form of resource leak, leading to constant
background CPU use. This occurs for processes launched for both akregator
& choqok, stracing affect http.so processes shows constant:
ppoll([{fd=4, events=POLLIN}], 1, {tv_sec=0, tv_nsec=100}, NULL, 8) = 0
(Timeout)
write(3, "\1\0\0\0\0\0\0\0", 8)
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages kio depends on:
ii libacl1 2.2.52-3+b1
ii libc6 2.27-3
ii libgcc1 1:8-20180402-1
ii libgssapi-krb5-2 1.16-2
ii libkf5archive55.44.0-1
ii libkf5auth5 5.44.0-1
ii libkf5codecs5 5.44.0-1
ii libkf5completion5 5.44.0-1
ii libkf5configcore5 5.44.0-1
ii libkf5configwidgets5 5.44.0-1
ii libkf5coreaddons5 5.44.0-1
ii libkf5dbusaddons5 5.44.0-1
ii libkf5doctools5 5.44.0-1
ii libkf5i18n5 5.44.0-1
ii libkf5itemviews5 5.44.0-1
ii libkf5kiocore55.44.0-2
ii libkf5kiontlm55.44.0-2
ii libkf5kiowidgets5 5.44.0-2
ii libkf5notifications5 5.44.0-1
ii libkf5service-bin 5.44.0-1
ii libkf5service55.44.0-1
ii libkf5solid5 5.44.0-1
ii libkf5textwidgets55.44.0-1
ii libkf5wallet-bin 5.44.0-1
ii libkf5wallet5 5.44.0-1
ii libkf5widgetsaddons5 5.44.0-1
ii libkf5windowsystem5 5.44.0-1
ii libqt5core5a 5.10.1+dfsg-5
ii libqt5dbus5 5.10.1+dfsg-5
ii libqt5gui55.10.1+dfsg-5
ii libqt5network55.10.1+dfsg-5
ii libqt5script5 5.10.1+dfsg-2
ii libqt5widgets55.10.1+dfsg-5
ii libqt5x11extras5 5.10.1-2
ii libqt5xml55.10.1+dfsg-5
ii libstdc++68-20180402-1
ii libxml2 2.9.4+dfsg1-6.1
ii libxslt1.11.1.29-5
kio recommends no packages.
kio suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: kio
Source-Version: 5.69.0-1
Done: Sandro Knauß
In data mercoledì 18 aprile 2018 01:41:49 CET, Julien Goodwin ha scritto:
> Package: kio
> Version: 5.44.0-2
> Severity: normal
>
> http.so seems to have some form of resource leak, leading to constant
> background CPU use. This occurs for processes launched for both akregator
> & choqok, stracing affect http.so processes shows constant:
>
> ppoll([{fd=4, events=POLLIN}], 1, {tv_sec=0, tv_nsec=100}, NULL, 8) = 0
> (Timeout)
> write(3, "\1\0\0\0\0\0\0\0", 8)
According to its upstream bug report
https://bugs.kde.org/show_bug.cgi?id=392768
this was fixed in kio 5.67.0. Hence, closing accordingly.
Thanks for your report,
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
Bug#946044: marked as done (dolphin/kio: notification of file copy/move operations still depends on old kde4 packages)
Your message dated Thu, 24 Dec 2020 19:49:59 +0100 with message-id <3718929.yKVeVyVuyW@thyrus> and subject line Re: Bug#946044: dolphin/kio: notification of file copy/move operations still depends on old kde4 packages has caused the Debian Bug report #946044, regarding dolphin/kio: notification of file copy/move operations still depends on old kde4 packages to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 946044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kio Version: 5.62.1-2 Severity: normal Dear maintainer, why do the notification operations related to copying / moving a file depend on old packages of kde 4:14? If I remove these packages (previous release 4:4.14.38): "kate-data katepart kdelibs-bin kdelibs5-data kdelibs5-plugins kdoctools libgpgme++2v5 libkatepartinterfaces4 libkcmutils4 libkde3support4 libkdeclarative5 libkdecore5 libkdesu5 libkdeui5 libkdewebkit5 libkdnssd4 libkemoticons4 libkfile4 libkhtml5 libkio5 libkjsapi4 libkjsembed4 libkmediaplayer4 libknewstuff3-4 libknotifyconfig4 libkntlm4 libkparts4 libkpty4 libkrosscore4 libktexteditor4 libplasma3 libsolid4 libthreadweaver4" I get these results: - on notebook: no problem, view the animation of the circle in the system tray - on desktop: I no longer see the animation in the system tray but a separate window appears. Where is the problem? Thanks, Antonio -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (700, 'unstable'), (500, 'stable-updates'), (500, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.1-custom (SMP w/8 CPU cores; PREEMPT) Locale: LANG=it_IT, LC_CTYPE=it_IT (charmap=ISO-8859-1) (ignored: LC_ALL set to it_IT), LANGUAGE=it (charmap=ISO-8859-1) (ignored: LC_ALL set to it_IT) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kio depends on: ii libacl1 2.2.53-5 ii libc6 2.29-3 ii libgcc1 1:9.2.1-21 ii libgssapi-krb5-2 1.17-6 ii libkf5archive55.62.0-1 ii libkf5authcore5 5.62.0-1 ii libkf5codecs5 5.62.0-1 ii libkf5completion5 5.62.0-1 ii libkf5configcore5 5.62.0-1 ii libkf5configwidgets5 5.62.0-1 ii libkf5coreaddons5 5.62.0-1 ii libkf5dbusaddons5 5.62.0-1 ii libkf5doctools5 5.62.0-1 ii libkf5i18n5 5.62.0-1 ii libkf5itemviews5 5.62.0-1 ii libkf5kiocore55.62.1-2 ii libkf5kiontlm55.62.1-2 ii libkf5kiowidgets5 5.62.1-2 ii libkf5notifications5 5.62.0-1 ii libkf5service-bin 5.62.0-1 ii libkf5service55.62.0-1 ii libkf5solid5 5.62.0-2 ii libkf5textwidgets55.62.0-1 ii libkf5wallet-bin 5.62.0-1 ii libkf5wallet5 5.62.0-1 ii libkf5widgetsaddons5 5.62.0-1 ii libkf5windowsystem5 5.62.0-2 ii libqt5core5a 5.12.5+dfsg-2 ii libqt5dbus5 5.12.5+dfsg-2 ii libqt5gui55.12.5+dfsg-2 ii libqt5network55.12.5+dfsg-2 ii libqt5script5 5.12.5+dfsg-2 ii libqt5widgets55.12.5+dfsg-2 ii libqt5x11extras5 5.12.5-1 ii libqt5xml55.12.5+dfsg-2 ii libstdc++69.2.1-21 ii libxml2 2.9.4+dfsg1-8 ii libxslt1.11.1.32-2.2 --- End Message --- --- Begin Message --- Hi Antonio, In data martedì 3 dicembre 2019 11:49:49 CET, Antonio ha scritto: > Package: kio > Version: 5.62.1-2 > Severity: normal > > Dear maintainer, > why do the notification operations related to copying / moving a file > depend on old packages of kde 4:14? They do not, otherwise they would be broken for many users. > If I remove these packages (previous release 4:4.14.38): "kate-data > katepart kdelibs-bin kdelibs5-data kdelibs5-plugins kdoctools > libgpgme++2v5 libkatepartinterfaces4 libkcmutils4 libkde3support4 > libkdeclarative5 libkdecore5 libkdesu5 libkdeui5 libkdewebkit5 > libkdnssd4 libkemoticons4 libkfile4 libkhtml5 libkio5 libkjsapi4 > libkjsembed4 libkmediaplayer4 libknewstuff3-4 libknotifyconfig4 > libkntlm4 libkparts4 libkpty4 libkrosscore4 libktexteditor4 libplasma3 > libsolid4 libthreadweaver4" > > I get these results: > - on notebook: no problem, view the animation of the circle in the system tray > - on desktop: I no longer see the animation in the system tray but a separate > window appears. > > Where is the problem? I do not think any of these kde4-related packages has anything to do with your problem, but most likely something else is. D
Processed: Re: Bug#942129: kio: no multiarch support.
Processing commands for cont...@bugs.debian.org: > severity 942129 wishlist Bug #942129 [kio] kio: no multiarch support. Severity set to 'wishlist' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 942129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942129: kio: no multiarch support.
severity 942129 wishlist thanks Hi, In data giovedì 10 ottobre 2019 19:57:05 CET, peter green ha scritto: > While trying to install a kde app for a foreign architecture. I noticed that > while libkf5declarative5 is multi-arch: same it can only be installed for one > architecture at a time, because it depends on kio and kio has no multi-arch > field. > > Unfortunately it seems kio contains a bunch of stuff in architecture-specific > paths which look like they may be used from other packages, but also contains > native binaries in /usr/bin , so it seems adding multi-arch support would > require splitting the package. > > Thoughts? Multi-arch is in general not something upstream supports; we have some changes mostly related to cross-building, but otherwise anything beyond that is mostly "nice to have". Some of the KDE Frameworks (such as kio) also have runtime components/daemons that can spawn D-Bus services and/or load plugins. This makes the scenario you described above as hard to do, and (personally speaking) not something to invest into unless there is a strong demand for it. Hence, I'm lowering the severity of this to wishlist. -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#848180: konsole: Includes application name in window title when configured not to do so
Processing commands for cont...@bugs.debian.org: > reassign 848180 src:qtbase-opensource-src > qtbase-opensource-src/5.7.1~20161021+dfsg-6 Bug #848180 [src:kxmlgui] konsole: Includes application name in window title when configured not to do so Bug reassigned from package 'src:kxmlgui' to 'src:qtbase-opensource-src'. No longer marked as found in versions kxmlgui/5.8.0-1. Ignoring request to alter fixed versions of bug #848180 to the same values previously set Bug #848180 [src:qtbase-opensource-src] konsole: Includes application name in window title when configured not to do so Marked as found in versions qtbase-opensource-src/5.7.1~20161021+dfsg-6. > retitle 848180 setWindowTitle() includes application name in window title > when configured not to do so Bug #848180 [src:qtbase-opensource-src] konsole: Includes application name in window title when configured not to do so Changed Bug title to 'setWindowTitle() includes application name in window title when configured not to do so' from 'konsole: Includes application name in window title when configured not to do so'. > thanks Stopping processing here. Please contact me if you need assistance. -- 848180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848180 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#848180: konsole: Includes application name in window title when configured not to do so
reassign 848180 src:qtbase-opensource-src qtbase-opensource-src/5.7.1~20161021+dfsg-6 retitle 848180 setWindowTitle() includes application name in window title when configured not to do so thanks In data venerdì 23 dicembre 2016 16:36:15 CET, Maximiliano Curia ha scritto: > ¡Hola Aaron! > > El 2016-12-13 a las 19:49 -0500, Aaron Schrab escribió: > > Package: konsole > > Version: 4:16.08.3-1 > > Severity: minor > > > After unchecking the "Show application name on the titlebar" option in the > > Configure Konsole dialog it still inludes " - Konsole" at the end of window > > titles. This occurs even after closing all Konsole windows and restarting > > the > > application. > > > I first observed this with version 4:16.08.2-2 of both the konsole and > > konsole-kpart packages. I upgraded both of those to 4:16.08.3-1 from > > unstable > > to check if the issue was still present (and I again made sure to close all > > windows after the upgrade). Before I installed the version from testing > > yesterday I hadn't used this package in long time, so I can't say how long > > this > > bug has existed. > > I can reproduce the issue, this seems to be a issue in kxmlgui rather than > konsole. konsole calls setCaption or setPlainCaption depending on the value > of > the user setting, the first on documents that it would add the application > name, and the second one that it wouldn't, but sadly this is no longer true ( > since this was ported to qt5), as setCaption is implemented as a single call > to setPlainCaption (and the responsible for adding the application name in > the > title is the qt qpa plugin). > > The setCaption and setPlainCaption documentation can be seen here: > https://cgit.kde.org/kxmlgui.git/tree/src/kmainwindow.h > > While the implementation can be seen here: > https://api.kde.org/frameworks/kxmlgui/html/kmainwindow_8cpp_source.html > > The qt documentation for setWindowTitle can be found here: > http://doc.qt.io/qt-5/qwidget.html#windowTitle-prop > > kxmlgui is missing a way to workaround the setWindowTitle use of the qpa > plugin, this may need to be scale to qtbase. Indeed, this is a Qt limitation: https://bugreports.qt.io/browse/QTBUG-75535 Hence, reassigning to Qt 5. Thanks, -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug#816671: marked as done (krfb does not save all settings in config file)
Your message dated Thu, 24 Dec 2020 20:26:00 +0100 with message-id <14947548.RDIVbhacDa@thyrus> and subject line Re: Bug#816671: krfb does not save all settings in config file has caused the Debian Bug report #816671, regarding krfb does not save all settings in config file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 816671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: krfb Version: 4:4.14.2-1 Severity: important Dear Maintainer, I configured krfb to be enabled and specified a password for access. However, next time krfb starts up, it is disabled again. This i very anoying as I run krfb as autostart. I can only use it, if manually enable it on every log-in. The version from wheezy did not have this problem. The bug is also reported at: https://bugs.kde.org/show_bug.cgi?id=340411 -- System Information: Debian Release: 8.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages krfb depends on: ii kde-runtime4:4.14.2-2 ii libc6 2.19-18+deb8u3 ii libkdecore54:4.14.2-5 ii libkdeui5 4:4.14.2-5 ii libkdnssd4 4:4.14.2-5 ii libktpcommoninternalsprivate7 0.8.1-4 ii libktpmodelsprivate7 0.8.1-4 ii libktpwidgetsprivate7 0.8.1-4 ii libqt4-dbus4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libstdc++6 4.9.2-10 ii libtelepathy-qt4-2 0.9.4+dfsg-3 ii libvncserver0 0.9.9+dfsg2-6.1+deb8u1 ii libx11-6 2:1.6.2-3 ii libxdamage11:1.1.4-2+b1 ii libxext6 2:1.3.3-1 ii libxtst6 2:1.2.2-1+b1 krfb recommends no packages. Versions of packages krfb suggests: ii khelpcenter4 4:4.14.2-2 ii krdc 4:4.14.1-1 -- no debconf information --- End Message --- --- Begin Message --- Source: krfb Source-Version: 4:20.08.2-1 Done: Aurélien COUDERC In data giovedì 3 marzo 2016 21:10:00 CET, Jürgen Bausa ha scritto: > Package: krfb > Version: 4:4.14.2-1 > Severity: important > > Dear Maintainer, > > I configured krfb to be enabled and specified a password for access. However, > next time krfb > starts up, it is disabled again. This i very anoying as I run krfb as > autostart. I can only > use it, if manually enable it on every log-in. > > The version from wheezy did not have this problem. > > The bug is also reported at: > > https://bugs.kde.org/show_bug.cgi?id=340411 This was finally fixed in krfb 20.08.2, which has been available in testing for the last couple of months. Hence, closing appropriately. Thank you for your report, -- Pino Toscano signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#969055: marked as done (purpose: wrong homepage)
Your message dated Thu, 24 Dec 2020 20:44:11 +0100 with message-id <4354178.k3LOHGUjKi@thyrus> and subject line Re: Bug#969055: purpose: wrong homepage has caused the Debian Bug report #969055, regarding purpose: wrong homepage to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 969055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: purpose Severity: minor Tags: newcomer Hi maintainer, Current homepage field gives 404, but the current git(lab) of Purpose seems to be https://invent.kde.org/frameworks/purpose Perhaps somebody can update the field in control ;-) best regards, -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: purpose Source-Version: 5.74.0-1 Done: Sandro Knauß In data mercoledì 26 agosto 2020 21:33:21 CET, Ricardo Mones ha scritto: > Source: purpose > Severity: minor > Tags: newcomer > > Hi maintainer, > > Current homepage field gives 404, but the current git(lab) of Purpose > seems to be https://invent.kde.org/frameworks/purpose > > Perhaps somebody can update the field in control ;-) This was fixed with purpose 5.74.0-1. Thanks for your report, -- Pino Toscano signature.asc Description: This is a digitally signed message part. --- End Message ---
Processed: tagging 969055
Processing commands for cont...@bugs.debian.org: > tags 969055 - newcomer Bug #969055 [src:purpose] purpose: wrong homepage Removed tag(s) newcomer. > thanks Stopping processing here. Please contact me if you need assistance. -- 969055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977329: krita segfaults when try to open with libQt5Gui.so.5.15.1
hi! thanks very much for your help. the krita segfault still happens with all latest updates, including the most recent kernel 5.9.0-5-amd64 krita crashes at open. when i select the krita program from the menu nothing happens at all. when i run like this: $ krita Segmentation fault that's what happens i'm using lxqt i'm using xorg as far as i know. haven't installed wayland deliberately === here's output from dpkg regarding wayland and xorg: # dpkg -l *wayland* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===-===-- ii kwayland-data 4:5.74.0-2 all Qt library wrapper for Wayland libraries - data files ii kwayland-integration:amd64 5.19.5-3amd64kwayland runtime integration plugins ii libkf5waylandclient5:amd64 4:5.74.0-2 amd64Qt library wrapper for Wayland libraries ii libqt5waylandclient5:amd64 5.15.2-2amd64QtWayland client library ii libqt5waylandcompositor5:amd64 5.15.2-2amd64QtWayland compositor library ii libva-wayland2:amd642.10.0-1amd64Video Acceleration (VA) API for Linux -- Wayland runtime ii libwayland-client0:amd641.18.0-2~exp1.1 amd64wayland compositor infrastructure - client library ii libwayland-cursor0:amd641.18.0-2~exp1.1 amd64wayland compositor infrastructure - cursor library ii libwayland-egl1:amd64 1.18.0-2~exp1.1 amd64wayland compositor infrastructure - EGL library un libwayland-egl1-mesa (no description available) ii libwayland-server0:amd641.18.0-2~exp1.1 amd64wayland compositor infrastructure - server library un libwayland0 (no description available) un qtwayland-client-abi-5-15-2 (no description available) un qtwayland-compositor-abi-5-15-2 (no description available) ii qtwayland5:amd645.15.2-2amd64QtWayland platform plugin # dpkg -l *xorg* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--= ii xorg 1:7.7+21amd64 X.Org X Window System un xorg-docs (no description available) ii xorg-docs-core 1:1.7.1-1.1 all Core documentation for the X.org X Window System un xorg-driver-input (no description available) un xorg-driver-video (no description available) un xorg-input-abi-24 (no description available) un xorg-video-abi-24 (no description available) ii xserver-xorg 1:7.7+21amd64 X.Org X server ii xserver-xorg-core 2:1.20.10-1 amd64 Xorg X server - core server un xserver-xorg-driver-all (no description available) ii xserver-xorg-input-all 1:7.7+21amd64 X.Org X server -- input driver metapackage un xserver-xorg-input-evtouch (no description available) ii xserver-xorg-input-libinput0.30.0-1amd64 X.Org X server -- libinput input driver un xserver-xorg-input-vmmouse (no description available) ii xserver-xorg-input-wacom 0.34.99.1-1+b1 amd64 X.Org X server -- Wacom input driver ii xserver-xorg-legacy2:1.20.10-1 amd64 setuid root Xorg server wrapper ii xserver-xorg-video-all 1:7.7+21amd64 X.Org X server -- output driver metapackage ii xserver-xorg-video-amdgpu 19.1.0-1amd64 X.Org X server -- AMDGPU display driver ii xserver-xorg-video-ati 1:19.1.0-1 amd64 X.Org X server -- AMD/ATI display driver wrapper ii xserver-xorg-video-fbdev 1:0.5.0-1 amd64 X.Org X server -- fbdev display driver ii xserver-xorg-video-intel 2:2.99.917+git20200714-1+b1 amd64 X.Org X server -- Intel i8xx, i9xx display driver un xserver-xorg-video-mach64 (no description available) un xserver-xorg-video-modesetting
Bug#535466: marked as done ([ksnapshot] Area capture unusable when desktop effects are enabled)
Your message dated Thu, 24 Dec 2020 21:24:29 +0100 with message-id <38432143.10thIPus4b@thyrus> and subject line Closing old ksnapshot bug has caused the Debian Bug report #535466, regarding [ksnapshot] Area capture unusable when desktop effects are enabled to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 535466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535466 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ksnapshot Version: 4:4.2.2-2 Severity: normal --- Please enter the report below this line. --- When KDE4 desktop effects are enabled, KSnapshot behaves as follows: Window Area capture is unusable: area selection is possible but pressing enter to perform the capture does not work. There is no way to quit the app neither. --- System information. --- Architecture: amd64 Kernel: Linux 2.6.26-2-amd64 Debian Release: squeeze/sid 500 testing www.debian-multimedia.org 500 testing security.debian.org 500 testing http.us.debian.org 500 testing ftp.rediris.es 500 squeeze www.lamaresh.net 500 lenny-cran cran.es.r-project.org --- Package information. --- Depends(Version) | Installed -+-= kdebase-runtime (>= 4:4.2.2) | 4:4.2.2-1 kdelibs5(>= 4:4.2.2) | 4:4.2.2-2 libc6 (>= 2.2.5) | 2.9-12 libqt4-dbus (>= 4.5.1) | 4.5.1-2 libqtcore4(>= 4.5.1) | 4.5.1-2 libqtgui4 (>= 4.5.1) | 4.5.1-2 libstdc++6(>= 4.1.1) | 4.4.0-5 libx11-6 | 2:1.2.1-1 Package's Recommends field is empty. Package's Suggests field is empty. --- End Message --- --- Begin Message --- Dear ksnapshot user, ksnapshot has not been developed upstream for many years already, and Spectacle (available in the kde-spectacle package) replaced it upstream and also in Debian, starting from Debian 9 (Stretch). Since ksnapshot was removed from Debian more than 4 years ago, it is time to close all the open bugs for it. Spectacle, even if it does something similar to what ksnapshot did, is a totally different application started from scratch (and thus not sharing anything code-wise with ksnapshot); because of this, there is no point in moving all the ksnapshot bugs to Spectacle. Most probably you have been using Spectacle already for a few years; we recommend to report bugs and feature requests for it directly to the upstream bug tracker system: https://bugs.kde.org/, product "Spectacle". Thank you again for you report, -- Pino Toscano signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#548229: marked as done (ksnapshot has no man page)
Your message dated Thu, 24 Dec 2020 21:24:29 +0100 with message-id <38432143.10thIPus4b@thyrus> and subject line Closing old ksnapshot bug has caused the Debian Bug report #548229, regarding ksnapshot has no man page to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 548229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ksnapshot Version: 4:4.3.1-1 Severity: normal This is a binary without a manpage. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-dbb-deb (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ksnapshot depends on: ii kdebase-runtime 4:4.3.1-1 runtime components from the offici ii kdelibs5 4:4.3.1-1 core libraries for all KDE 4 appli ii libc6 2.9-25 GNU C Library: Shared libraries ii libqt4-dbus 4:4.5.2-2 Qt 4 D-Bus module ii libqtcore44:4.5.2-2 Qt 4 core module ii libqtgui4 4:4.5.2-2 Qt 4 GUI module ii libstdc++64.4.1-1The GNU Standard C++ Library v3 ii libx11-6 2:1.2.2-1 X11 client-side library ksnapshot recommends no packages. ksnapshot suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Dear ksnapshot user, ksnapshot has not been developed upstream for many years already, and Spectacle (available in the kde-spectacle package) replaced it upstream and also in Debian, starting from Debian 9 (Stretch). Since ksnapshot was removed from Debian more than 4 years ago, it is time to close all the open bugs for it. Spectacle, even if it does something similar to what ksnapshot did, is a totally different application started from scratch (and thus not sharing anything code-wise with ksnapshot); because of this, there is no point in moving all the ksnapshot bugs to Spectacle. Most probably you have been using Spectacle already for a few years; we recommend to report bugs and feature requests for it directly to the upstream bug tracker system: https://bugs.kde.org/, product "Spectacle". Thank you again for you report, -- Pino Toscano signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#589957: marked as done (ksnapshot: crashes when using alt-tab and drag-n-drop)
Your message dated Thu, 24 Dec 2020 21:24:29 +0100 with message-id <38432143.10thIPus4b@thyrus> and subject line Closing old ksnapshot bug has caused the Debian Bug report #589957, regarding ksnapshot: crashes when using alt-tab and drag-n-drop to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 589957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ksnapshot Version: 4:4.4.4-1+b1 Severity: normal If alt-tab is pressed after dragging the image from KSnapshot (with left mouse button still pressed), KSnapshot crashes. This behaviour can be reproduced, I attached a backtrace with libqt4-dbg installed. This bug renders the drag-n-drop functionality of KSnapshot partly unusable since one can only drag the image to windows that are on the screen at the time (so no alt-tab-ing is needed). -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.34.1 (SMP w/2 CPU cores) Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ksnapshot depends on: ii kdebase-runtime 4:4.4.4-1+b1 runtime components from the offici ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libkdecore5 4:4.4.4-2the KDE Platform Core Library ii libkdeui5 4:4.4.4-2the KDE Platform User Interface Li ii libkio5 4:4.4.4-2the Network-enabled File Managemen ii libqt4-dbus 4:4.6.3-1Qt 4 D-Bus module ii libqtcore4 4:4.6.3-1Qt 4 core module ii libqtgui4 4:4.6.3-1Qt 4 GUI module ii libstdc++6 4.4.4-6 The GNU Standard C++ Library v3 ii libx11-62:1.3.3-3X11 client-side library ii libxext62:1.1.2-1X11 miscellaneous extension librar ksnapshot recommends no packages. ksnapshot suggests no packages. -- debconf-show failed Application: KSnapshot (ksnapshot), signal: Segmentation fault [KCrash Handler] #6 QDragManager::move (this=0x86b5bd8, globalPos=...) at kernel/qdnd_x11.cpp:1596 #7 0xb61ce7ff in QDragManager::eventFilter (this=0x86b5bd8, o=0x877d050, e=0xbfda6b14) at kernel/qdnd_x11.cpp:1287 #8 0xb6be288c in QCoreApplicationPrivate::sendThroughApplicationEventFilters (this=0x826c980, receiver=0x877d050, event=0xbfda6b14) at kernel/qcoreapplication.cpp:822 #9 0xb612c553 in QApplicationPrivate::notify_helper (this=0x826c980, receiver=0x877d050, e=0xbfda6b14) at kernel/qapplication.cpp:4277 #10 0xb6133af7 in QApplication::notify (this=0xbfda83ec, receiver=0x877d050, e=0xbfda6b14) at kernel/qapplication.cpp:3867 #11 0xb71acb4a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #12 0xb6be352b in QCoreApplication::notifyInternal (this=0xbfda83ec, receiver=0x877d050, event=0xbfda6b14) at kernel/qcoreapplication.cpp:726 #13 0xb6132a52 in QCoreApplication::sendEvent (receiver=0x877d050, event=0xbfda6b14, alienWidget=0x0, nativeWidget=0x877d050, buttonDown=0xb6a74998, lastMouseReceiver=..., spontaneous=true) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #14 QApplicationPrivate::sendMouseEvent (receiver=0x877d050, event=0xbfda6b14, alienWidget=0x0, nativeWidget=0x877d050, buttonDown=0xb6a74998, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:2967 #15 0xb61bdd7c in QETWidget::translateMouseEvent (this=0x877d050, event=0xbfda6f60) at kernel/qapplication_x11.cpp:4380 #16 0xb61bd28b in QApplication::x11ProcessEvent (this=0xbfda83ec, event=0xbfda6f60) at kernel/qapplication_x11.cpp:3391 #17 0xb61eb3e2 in x11EventSourceDispatch (s=0x826fbe8, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #18 0xb592e2f5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #19 0xb5931fd8 in ?? () from /lib/libglib-2.0.so.0 #20 0xb59321b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #21 0xb6c0f095 in QEventDispatcherGlib::processEvents (this=0x8257c08, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #22 0xb61eaf45 in QGuiEventDispatcherGlib::processEvents (this=0x8257c08, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #23 0xb6be1b49 in QEventLoop::processEvents (this=0x87fff18, flags=) at kernel/qeventloop.cpp:149 #24 0xb6be1f9a in QEventLoop::exec (this=0x87fff18, flags=...) at kernel/qeventloop.cpp:201 #25 0xb61d17dc in QDragManager::drag (this=0x86b5bd8,
Bug#597673: marked as done (ksnapshot: area capture doesn't work properly when klipper's menu is opened)
Your message dated Thu, 24 Dec 2020 21:24:29 +0100 with message-id <38432143.10thIPus4b@thyrus> and subject line Closing old ksnapshot bug has caused the Debian Bug report #597673, regarding ksnapshot: area capture doesn't work properly when klipper's menu is opened to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 597673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ksnapshot Version: 4:4.4.5-1 Severity: normal Choose the following ksnaphot parameters: Capture mode: Region Snapshot delay: 3 seconds Open klipper's global menu with its hotkey, wait for selection area Bugs: 1) Usually in this mode ksnapshot changes cursor to cross, it doesn't do this now. I need to click once, then cursor is changed to cross 2) Usually I can use Enter to close selection area, it doesn't work now If the klipper's global menu is not opened, ksnapshot's selection area works as expected. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (20, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ksnapshot depends on: ii kdebase-runtime 4:4.4.5-1runtime components from the offici ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libkdecore5 4:4.4.5-1the KDE Platform Core Library ii libkdeui5 4:4.4.5-1the KDE Platform User Interface Li ii libkio5 4:4.4.5-1the Network-enabled File Managemen ii libqt4-dbus 4:4.6.3-1+b1 Qt 4 D-Bus module ii libqtcore4 4:4.6.3-1+b1 Qt 4 core module ii libqtgui4 4:4.6.3-1+b1 Qt 4 GUI module ii libstdc++6 4.4.4-8 The GNU Standard C++ Library v3 ii libx11-62:1.3.3-3X11 client-side library ii libxext62:1.1.2-1X11 miscellaneous extension librar ksnapshot recommends no packages. ksnapshot suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Dear ksnapshot user, ksnapshot has not been developed upstream for many years already, and Spectacle (available in the kde-spectacle package) replaced it upstream and also in Debian, starting from Debian 9 (Stretch). Since ksnapshot was removed from Debian more than 4 years ago, it is time to close all the open bugs for it. Spectacle, even if it does something similar to what ksnapshot did, is a totally different application started from scratch (and thus not sharing anything code-wise with ksnapshot); because of this, there is no point in moving all the ksnapshot bugs to Spectacle. Most probably you have been using Spectacle already for a few years; we recommend to report bugs and feature requests for it directly to the upstream bug tracker system: https://bugs.kde.org/, product "Spectacle". Thank you again for you report, -- Pino Toscano signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#828121: marked as done (ksnapshot: no translation available)
Your message dated Thu, 24 Dec 2020 21:24:29 +0100
with message-id <38432143.10thIPus4b@thyrus>
and subject line Closing old ksnapshot bug
has caused the Debian Bug report #828121,
regarding ksnapshot: no translation available
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
828121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ksnapshot
Version: 4:15.08.0-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Recent upgrades only allow to run ksnapshot in "american english".
* What exactly did you do (or not do) that was effective (or
ineffective)?
I've installed a kde translation package (e.g. kde-l10n-fr)
My KDE favorite language (in systemsettings) is French.
ksnapshot is in english.
I cannot change the application language in ksnapshot (Help > switch
application language): only american english is available in the list.
Adding a fallback language leads to the same list.
Note the other installed KDE apps are correctly translated (konqueror, dolphin,
korganizer, kmail, kopete, amarok, kmix, etc.), ksnapshot seems to be the only
application impacted by this bug.
* What was the outcome of this action?
The application still run in english.
* What outcome did you expect instead?
The application should be translated in the appropriate language.
dpkg -l | egrep "(ksnapshot|kde-l10n)" | awk '/ii/{print $1,$2,$3}'
ii kde-l10n-fr 4:16.04.2-1
ii ksnapshot 4:15.08.0-1
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (90, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages ksnapshot depends on:
ii kde-runtime 4:16.04.2-1
ii libc62.22-11
ii libkdecore5 4:4.14.21-1
ii libkdeui54:4.14.21-1
ii libkio5 4:4.14.21-1
ii libkipi114:15.08.3-2
ii libqt4-dbus 4:4.8.7+dfsg-8
ii libqtcore4 4:4.8.7+dfsg-8
ii libqtgui44:4.8.7+dfsg-8
ii libstdc++6 6.1.1-4
ii libx11-6 2:1.6.3-1
ii libxext6 2:1.3.3-1
ii libxfixes3 1:5.0.1-2+b2
ksnapshot recommends no packages.
ksnapshot suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Dear ksnapshot user,
ksnapshot has not been developed upstream for many years already, and
Spectacle (available in the kde-spectacle package) replaced it upstream
and also in Debian, starting from Debian 9 (Stretch).
Since ksnapshot was removed from Debian more than 4 years ago, it is
time to close all the open bugs for it. Spectacle, even if it does
something similar to what ksnapshot did, is a totally different
application started from scratch (and thus not sharing anything
code-wise with ksnapshot); because of this, there is no point in moving
all the ksnapshot bugs to Spectacle.
Most probably you have been using Spectacle already for a few years;
we recommend to report bugs and feature requests for it directly to
the upstream bug tracker system: https://bugs.kde.org/, product
"Spectacle".
Thank you again for you report,
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
Bug#632615: marked as done (ksnapshot: area capture problems introduced after 4.4.5)
Your message dated Thu, 24 Dec 2020 21:24:29 +0100 with message-id <38432143.10thIPus4b@thyrus> and subject line Closing old ksnapshot bug has caused the Debian Bug report #632615, regarding ksnapshot: area capture problems introduced after 4.4.5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 632615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ksnapshot Version: 4:4.6.3-1 Severity: normal Hi, I'm not a KDE user, but use ksnapshot for screen capture, as it has been the nicest screenshot application around. However, for releases after 4.4.5, the area capture isn't working very well. What happens is a screen grab is done, and then never relinquished. I have to kill the X server (with Ctrl-Alt-backspace) to get unstuck. For now, I am using an old version 4.4.5. For the record, I use the Compiz window manager. cheers, Simon -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_NZ.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ksnapshot depends on: ii kdebase-runtime 4:4.6.3-1 runtime components from the offici ii libc6 2.13-4 Embedded GNU C Library: Shared lib ii libkdecore5 4:4.6.3-2 KDE Platform Core Library ii libkdeui5 4:4.6.3-2 KDE Platform User Interface Librar ii libkio5 4:4.6.3-2 Network-enabled File Management Li ii libkipi8 4:4.6.3-1 library for apps that want to use ii libqt4-dbus 4:4.7.3-1 Qt 4 D-Bus module ii libqtcore44:4.7.3-1 Qt 4 core module ii libqtgui4 4:4.7.3-1 Qt 4 GUI module ii libstdc++64.6.0-10 The GNU Standard C++ Library v3 ii libx11-6 2:1.4.3-1 X11 client-side library ii libxext6 2:1.3.0-1 X11 miscellaneous extension librar ii libxfixes31:5.0-2X11 miscellaneous 'fixes' extensio ksnapshot recommends no packages. ksnapshot suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Dear ksnapshot user, ksnapshot has not been developed upstream for many years already, and Spectacle (available in the kde-spectacle package) replaced it upstream and also in Debian, starting from Debian 9 (Stretch). Since ksnapshot was removed from Debian more than 4 years ago, it is time to close all the open bugs for it. Spectacle, even if it does something similar to what ksnapshot did, is a totally different application started from scratch (and thus not sharing anything code-wise with ksnapshot); because of this, there is no point in moving all the ksnapshot bugs to Spectacle. Most probably you have been using Spectacle already for a few years; we recommend to report bugs and feature requests for it directly to the upstream bug tracker system: https://bugs.kde.org/, product "Spectacle". Thank you again for you report, -- Pino Toscano signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#651959: marked as done (ksnapshot: cannot open screenshot in an external program)
Your message dated Thu, 24 Dec 2020 21:24:29 +0100 with message-id <38432143.10thIPus4b@thyrus> and subject line Closing old ksnapshot bug has caused the Debian Bug report #651959, regarding ksnapshot: cannot open screenshot in an external program to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 651959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651959 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ksnapshot Version: 4:4.6.5-3 Severity: normal Take a screenshot. Save it as snapshot11.png. Try to open in external program like GIMP from ksnapshot's menu. GIMP will complain on non-existent file snapshot12.png. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (20, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/6 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ksnapshot depends on: ii kdebase-runtime 4:4.6.5-1+b1 ii libc62.13-21 ii libkdecore5 4:4.6.5-2+b1 ii libkdeui54:4.6.5-2+b1 ii libkio5 4:4.6.5-2+b1 ii libkipi8 4:4.6.5-3 ii libqt4-dbus 4:4.7.3-5 ii libqtcore4 4:4.7.3-5 ii libqtgui44:4.7.3-5 ii libstdc++6 4.6.2-5 ii libx11-6 2:1.4.4-4 ii libxext6 2:1.3.0-3 ii libxfixes3 1:5.0-4 ksnapshot recommends no packages. ksnapshot suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Dear ksnapshot user, ksnapshot has not been developed upstream for many years already, and Spectacle (available in the kde-spectacle package) replaced it upstream and also in Debian, starting from Debian 9 (Stretch). Since ksnapshot was removed from Debian more than 4 years ago, it is time to close all the open bugs for it. Spectacle, even if it does something similar to what ksnapshot did, is a totally different application started from scratch (and thus not sharing anything code-wise with ksnapshot); because of this, there is no point in moving all the ksnapshot bugs to Spectacle. Most probably you have been using Spectacle already for a few years; we recommend to report bugs and feature requests for it directly to the upstream bug tracker system: https://bugs.kde.org/, product "Spectacle". Thank you again for you report, -- Pino Toscano signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#667920: marked as done (ksnapshot: Output image is buggy when captured window is wider than the screen)
Your message dated Thu, 24 Dec 2020 21:24:29 +0100 with message-id <38432143.10thIPus4b@thyrus> and subject line Closing old ksnapshot bug has caused the Debian Bug report #667920, regarding ksnapshot: Output image is buggy when captured window is wider than the screen to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 667920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ksnapshot Version: 4:4.7.4-2 Severity: normal Tags: upstream Dear Maintainer, How to reproduce it: * Open a new window, of whatever software you want (tested with a software written with PyQt4) * Enlarge it to be larger than the screen * Open KSnapshot * Select "Window under cursor" as capture mode * Click "Take a New Snapshot" * Click on the large window * Save the screenshot Here is an example: http://ompldr.org/vZGFndQ/Capture3.png Regards, Valentin Lorentz -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ksnapshot depends on: ii kde-runtime 4:4.7.4-2 ii libc62.13-27 ii libkdecore5 4:4.7.4-4 ii libkdeui54:4.7.4-4 ii libkio5 4:4.7.4-4 ii libkipi8 4:4.7.4-2 ii libqt4-dbus 4:4.7.4-3 ii libqtcore4 4:4.7.4-3 ii libqtgui44:4.7.4-3 ii libstdc++6 4.7.0-1 ii libx11-6 2:1.4.4-4 ii libxext6 2:1.3.0-3 ii libxfixes3 1:5.0-4 ksnapshot recommends no packages. ksnapshot suggests no packages. -- no debconf information signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Dear ksnapshot user, ksnapshot has not been developed upstream for many years already, and Spectacle (available in the kde-spectacle package) replaced it upstream and also in Debian, starting from Debian 9 (Stretch). Since ksnapshot was removed from Debian more than 4 years ago, it is time to close all the open bugs for it. Spectacle, even if it does something similar to what ksnapshot did, is a totally different application started from scratch (and thus not sharing anything code-wise with ksnapshot); because of this, there is no point in moving all the ksnapshot bugs to Spectacle. Most probably you have been using Spectacle already for a few years; we recommend to report bugs and feature requests for it directly to the upstream bug tracker system: https://bugs.kde.org/, product "Spectacle". Thank you again for you report, -- Pino Toscano signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#836431: marked as done (ksnapshot: Update dependency from libkipi11 to libkf5kipi31.0.0)
Your message dated Thu, 24 Dec 2020 21:24:29 +0100 with message-id <38432143.10thIPus4b@thyrus> and subject line Closing old ksnapshot bug has caused the Debian Bug report #836431, regarding ksnapshot: Update dependency from libkipi11 to libkf5kipi31.0.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 836431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ksnapshot Version: 4:15.08.0-1 Severity: normal Hello, I've noticed a problem now while updating the KDE packages on my system to the next set of available testing packages. All packages seemed to update normally but ksnapshot is holding back gwenview due to a conflict between libkipi11 and libkf5kipi31.0.0. My understanding is that the latter is simply the new name for the package so if you could update the dependency to point to the latter it would probably solve the issue. This has just been a superficial analisys so sorry if I'm wrong - but gwenview for example is depending on the 31.0.0 package instead, which replaces libkipi11 so I hope this is a safe assumption. Thanks for the great work maintaining this package. It has been my one and only screenshot tool since moving to Linux and KDE over a decade ago. I hope this issue can be solved easily by just reassigning the dependency to the new package name, thank again for you time! -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ksnapshot depends on: ii kde-runtime 4:16.08.0-1 ii libc62.23-5 ii libkdecore5 4:4.14.23-1 ii libkdeui54:4.14.23-1 ii libkio5 4:4.14.23-1 ii libkipi114:15.08.3-2 ii libqt4-dbus 4:4.8.7+dfsg-8 ii libqtcore4 4:4.8.7+dfsg-8 ii libqtgui44:4.8.7+dfsg-8 ii libstdc++6 6.1.1-11 ii libx11-6 2:1.6.3-1 ii libxext6 2:1.3.3-1 ii libxfixes3 1:5.0.2-1 ksnapshot recommends no packages. ksnapshot suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Dear ksnapshot user, ksnapshot has not been developed upstream for many years already, and Spectacle (available in the kde-spectacle package) replaced it upstream and also in Debian, starting from Debian 9 (Stretch). Since ksnapshot was removed from Debian more than 4 years ago, it is time to close all the open bugs for it. Spectacle, even if it does something similar to what ksnapshot did, is a totally different application started from scratch (and thus not sharing anything code-wise with ksnapshot); because of this, there is no point in moving all the ksnapshot bugs to Spectacle. Most probably you have been using Spectacle already for a few years; we recommend to report bugs and feature requests for it directly to the upstream bug tracker system: https://bugs.kde.org/, product "Spectacle". Thank you again for you report, -- Pino Toscano signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#836728: marked as done (kde-spectacle: Please provide .desktop file for ksnapshot)
Your message dated Thu, 24 Dec 2020 21:24:29 +0100 with message-id <38432143.10thIPus4b@thyrus> and subject line Closing old ksnapshot bug has caused the Debian Bug report #836728, regarding kde-spectacle: Please provide .desktop file for ksnapshot to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 836728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kde-spectacle Version: 16.04.3-1 Severity: important Dear Maintainer, as kde-spectacle is replacing ksnapshot, what happened is that completely silently, on an update, ksnapshot got deleted. So when I type "ksnap" in my launcher, nothing happens anymore. I think that for the transition, a soft link and a .desktop file should be provided for a while, because it's not very immediate to know that now one has to type a different thing. Transitions shouldn't silently delete commands. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kde-spectacle depends on: ii libc6 2.24-1 ii libkf5configcore5 5.25.0-1 ii libkf5configgui5 5.25.0-1 ii libkf5configwidgets5 5.25.0-1 ii libkf5coreaddons5 5.25.0-1 ii libkf5dbusaddons5 5.25.0-1 ii libkf5declarative55.25.0-1 ii libkf5i18n5 5.25.0-1 ii libkf5kiocore55.25.0-1 ii libkf5kiowidgets5 5.25.0-1 ii libkf5kipi31.0.0 4:16.08.0-1 ii libkf5notifications5 5.25.0-1 ii libkf5screen-bin 4:5.7.4-1 ii libkf5screen7 4:5.7.4-1 ii libkf5service-bin 5.25.0-1 ii libkf5service55.25.0-1 ii libkf5widgetsaddons5 5.25.0-1 ii libkf5windowsystem5 5.25.0-1 ii libkf5xmlgui5 5.25.0-1 ii libqt5core5a 5.6.1+dfsg-3+b1 ii libqt5dbus5 5.6.1+dfsg-3+b1 ii libqt5gui55.6.1+dfsg-3+b1 ii libqt5printsupport5 5.6.1+dfsg-3+b1 ii libqt5qml55.6.1-7 ii libqt5quick5 5.6.1-7 ii libqt5widgets55.6.1+dfsg-3+b1 ii libqt5x11extras5 5.6.1-2 ii libstdc++66.2.0-2 ii libxcb-cursor00.1.1-3 ii libxcb-image0 0.4.0-1 ii libxcb-util0 0.3.8-3 ii libxcb-xfixes01.11.1-1.1 ii libxcb1 1.11.1-1.1 kde-spectacle recommends no packages. kde-spectacle suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Dear ksnapshot user, ksnapshot has not been developed upstream for many years already, and Spectacle (available in the kde-spectacle package) replaced it upstream and also in Debian, starting from Debian 9 (Stretch). Since ksnapshot was removed from Debian more than 4 years ago, it is time to close all the open bugs for it. Spectacle, even if it does something similar to what ksnapshot did, is a totally different application started from scratch (and thus not sharing anything code-wise with ksnapshot); because of this, there is no point in moving all the ksnapshot bugs to Spectacle. Most probably you have been using Spectacle already for a few years; we recommend to report bugs and feature requests for it directly to the upstream bug tracker system: https://bugs.kde.org/, product "Spectacle". Thank you again for you report, -- Pino Toscano signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#947361: krita: Keyboard doesn't respond after some popups (f.e show color selector) are opened.
Package: krita Followup-For: Bug #947361 X-Debbugs-Cc: fenix...@gmail.com Dear Maintainer, I've just checked this issue in current Debian Testing Krita version and it was fixed. I'm closing this issue. Thanks! -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/12 CPU threads) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages krita depends on: ii krita-data1:4.4.1+dfsg-1 ii libc6 2.31-5 ii libexiv2-27 0.27.3-3 ii libfftw3-double3 3.3.8-2 ii libgcc-s1 10.2.1-1 ii libgif7 5.1.9-1 ii libgsl25 2.6+dfsg-2 ii libheif1 1.9.1-1 ii libilmbase25 2.5.3-2 ii libjpeg62-turbo 1:2.0.5-1.1 ii libkf5completion5 5.74.0-2 ii libkf5configcore5 5.74.0-2 ii libkf5configgui5 5.74.0-2 ii libkf5coreaddons5 5.74.0-2 ii libkf5crash5 5.74.0-2 ii libkf5guiaddons5 5.74.0-3 ii libkf5i18n5 5.74.0-3 ii libkf5itemviews5 5.74.0-2 ii libkf5widgetsaddons5 5.74.0-3 ii libkf5windowsystem5 5.74.0-2 ii liblcms2-22.9-4+b1 ii libopencolorio1v5 1.1.1~dfsg0-7 ii libopenexr25 2.5.3-2 ii libopenjp2-7 2.3.1-1 ii libpng16-16 1.6.37-3 ii libpoppler-qt5-1 20.09.0-3 ii libpython3.9 3.9.1-1 ii libqt5concurrent5 5.15.2+dfsg-2 ii libqt5core5a 5.15.2+dfsg-2 ii libqt5dbus5 5.15.2+dfsg-2 ii libqt5gui55.15.2+dfsg-2 ii libqt5multimedia5 5.15.2-2 ii libqt5network55.15.2+dfsg-2 ii libqt5printsupport5 5.15.2+dfsg-2 ii libqt5qml55.15.2+dfsg-2 ii libqt5quick5 5.15.2+dfsg-2 ii libqt5quickwidgets5 5.15.2+dfsg-2 ii libqt5svg55.15.2-2 ii libqt5widgets55.15.2+dfsg-2 ii libqt5x11extras5 5.15.2-2 ii libqt5xml55.15.2+dfsg-2 ii libquazip5-1 0.9.1-1 ii libraw20 0.20.2-1 ii libstdc++610.2.1-1 ii libtiff5 4.1.0+git201212-1 ii libx11-6 2:1.6.12-1 ii zlib1g1:1.2.11.dfsg-2 Versions of packages krita recommends: ii krita-gmic 2.4.5-1.1+b1 ii python3-pyqt55.15.2+dfsg-1+b1 ii python3-sip 4.19.24+dfsg-1+b2 ii qml-module-qtmultimedia 5.15.2-2 Versions of packages krita suggests: ii colord 1.4.4-2 ii ffmpeg 7:4.3.1-5 pn krita-l10n -- no debconf information
Bug#947361: marked as done (krita: Keyboard doesn't respond after some popups (f.e show color selector) are opened.)
Your message dated Thu, 24 Dec 2020 22:01:17 +0100 with message-id <17640542.geO5KgaWL5@thyrus> and subject line Re: Bug#947361: krita: Keyboard doesn't respond after some popups (f.e show color selector) are opened. has caused the Debian Bug report #947361, regarding krita: Keyboard doesn't respond after some popups (f.e show color selector) are opened. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 947361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: krita Version: 1:4.2.8.2+dfsg-1 Severity: normal Dear Maintainer, Krita seems to have problems with some popups docks, for example color selector, minimal shade selector... After this controls are showed if they are hidden just moving the pointer outside its domain, keyboard doesn't respond anymore, unless you change to another program or window. Brush preset, for example, works fine. This type of popup are close clicking outside and not just moving pointer outside. * What led up to the situation? 1.- Create new image. 2.- Open, for example, a color selector (Shift + I) 3.- Select a color and move the cursor outside the selector. It will be vanished. 4.- Try to open again the color selector with Shift + I or made something with keyboard: change to full screen, undo action (ctrl-z)... 5.- The keyboard will not repond. 6.- Change to another program and back to Krita (Krita must lost the focus). 7.- Try again show color selector (Shift + I). It will work again. * What exactly did you do (or not do) that was effective (or ineffective)? If enter key is pressed just before choosing color in color selector and with the pointer inside the control (for not hide it), the keyboard works fine: accept other shourtuts. But if the popup is hide only moving the pointer outside its domain, the keyboard will be stucked into Krita. And only come back after loosing the focus into another program or window. Thanks. -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 5.3.0-3-686-pae (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8), LANGUAGE=es_ES.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages krita depends on: ii krita-data 1:4.2.8.2+dfsg-1 ii libboost-system1.67.0 1.67.0-13+b1 ii libc6 2.29-3 ii libexiv2-140.25-4 ii libfftw3-double3 3.3.8-2 ii libgcc11:9.2.1-21 ii libgif75.1.9-1 ii libgsl23 2.5+dfsg-6+b1 ii libheif1 1.6.0-1 ii libilmbase24 2.3.0-6 ii libjpeg62-turbo1:1.5.2-2+b1 ii libkf5archive5 5.62.0-1 ii libkf5completion5 5.62.0-1+b1 ii libkf5configcore5 5.62.0-1+b1 ii libkf5configgui5 5.62.0-1+b1 ii libkf5coreaddons5 5.62.0-1 ii libkf5crash5 5.62.0-1+b1 ii libkf5guiaddons5 5.62.0-2 ii libkf5i18n55.62.0-1 ii libkf5itemviews5 5.62.0-1+b1 ii libkf5widgetsaddons5 5.62.0-1+b1 ii libkf5windowsystem55.62.0-2+b1 ii liblcms2-2 2.9-3+b1 ii libopencolorio1v5 1.1.1~dfsg0-5 ii libopenexr24 2.3.0-6 ii libpng16-161.6.37-1 ii libpoppler-qt5-1 0.71.0-6 ii libpython3.7 3.7.5-2 ii libqt5concurrent5 5.12.5+dfsg-2 ii libqt5core5a 5.12.5+dfsg-2 ii libqt5dbus55.12.5+dfsg-2 ii libqt5gui5 5.12.5+dfsg-2 ii libqt5multimedia5 5.12.5-1 ii libqt5network5 5.12.5+dfsg-2 ii libqt5printsupport55.12.5+dfsg-2 ii libqt5qml5 5.12.5-3 ii libqt5quick5 5.12.5-3 ii libqt5quickwidgets55.12.5-3 ii libqt5svg5 5.12.5-2 ii libqt5widgets5 5.12.5+dfsg-2 ii libqt5x11extras5 5.12.5-1 ii libqt5xml5 5.12.5+dfsg-2 ii libquazip5-1 0.7.6-6 ii libraw19 0.19.5-1 ii libstdc++6 9.2.1-21 ii libtiff5 4.1.0+git191117-1 ii libx11-6 2:1.6.8-1 ii zlib1g 1:1.2.11.dfsg-1+b1 Versions of packages krita recommends: ii krita-gmic 2.4.5-1+b1 ii python3-pyqt55.13.2+dfsg-1 ii python3-sip 4.19.19+dfsg-2+b1 ii qm
Processed: tagging 947361
Processing commands for cont...@bugs.debian.org:
> tags 947361 - moreinfo
Bug #947361 {Done: Pino Toscano } [krita] krita: Keyboard
doesn't respond after some popups (f.e show color selector) are opened.
Removed tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
947361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#977329: krita segfaults when try to open with libQt5Gui.so.5.15.1
reassign 977329 lxqt-qtplugin retitle 977329 lxqt-plugin: platform theme needs fixes for Qt 5.15 tag 977329 = fixed-upstream severity 977329 serious thanks Hi, In data giovedì 24 dicembre 2020 20:48:32 CET, proctor ha scritto: > hi! thanks very much for your help. > > the krita segfault still happens with all latest updates, including the > most recent kernel 5.9.0-5-amd64 > > krita crashes at open. when i select the krita program from the menu > nothing happens at all. > when i run like this: > $ krita > Segmentation fault > > that's what happens > > i'm using lxqt Thanks for the detail about this, and most probably you have lxqt-qtplugin installed, right? I see that the there were various fixes upstream related to the compatibility with Qt 5.15 and color palettes, and I would not be surprised that any of these issues would cause a crash: https://github.com/lxqt/lxqt-qtplugin/issues/54 https://github.com/lxqt/lxqt-qtplugin/pull/55 https://github.com/lxqt/lxqt-qtplugin/commit/8cc32d94b4c9de74b5bcf27fae2d10e6b2b11caf It looks like everything is included in the new upstream release 0.16.0, which then needs to be packaged in Debian. Another check you can do is try to run krita in a different desktop environment / window manager than LxQt. Hence, I'm reassigning this to lxqt-qtplugin with proper metadata. Thanks for your report, -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#977329: krita segfaults when try to open with libQt5Gui.so.5.15.1
Processing commands for cont...@bugs.debian.org: > reassign 977329 lxqt-qtplugin Bug #977329 [krita] krita segfaults when try to open with libQt5Gui.so.5.15.1 Bug reassigned from package 'krita' to 'lxqt-qtplugin'. No longer marked as found in versions krita/1:4.4.1+dfsg-1. Ignoring request to alter fixed versions of bug #977329 to the same values previously set > retitle 977329 lxqt-plugin: platform theme needs fixes for Qt 5.15 Bug #977329 [lxqt-qtplugin] krita segfaults when try to open with libQt5Gui.so.5.15.1 Changed Bug title to 'lxqt-plugin: platform theme needs fixes for Qt 5.15' from 'krita segfaults when try to open with libQt5Gui.so.5.15.1'. > tag 977329 = fixed-upstream Bug #977329 [lxqt-qtplugin] lxqt-plugin: platform theme needs fixes for Qt 5.15 Added tag(s) fixed-upstream; removed tag(s) moreinfo. > severity 977329 serious Bug #977329 [lxqt-qtplugin] lxqt-plugin: platform theme needs fixes for Qt 5.15 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 977329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processing of kolourpaint_20.12.0-1_amd64.changes
kolourpaint_20.12.0-1_amd64.changes uploaded successfully to localhost along with the files: kolourpaint_20.12.0-1.dsc kolourpaint_20.12.0.orig.tar.xz kolourpaint_20.12.0.orig.tar.xz.asc kolourpaint_20.12.0-1.debian.tar.xz kolourpaint_20.12.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
kolourpaint_20.12.0-1_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Dec 2020 00:19:14 +0100 Source: kolourpaint Architecture: source Version: 4:20.12.0-1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Aurélien COUDERC Changes: kolourpaint (4:20.12.0-1) unstable; urgency=medium . * New upstream release (20.12.0). * Refresh copyright information. * Bump Standards-Version to 4.5.1, no change required. * Bump debhelper compatibility level to 13. * Refresh upstream metadata. * Update project homepage. * Removed Eshat Cakar, Maximiliano Curia from the uploaders, thanks for your work on the package! * Added myself to the uploaders. * Drop kde-l10n migration rules, not needed anymore after 2 stable releases. * Build with hardening=+all build hardening flag. * Borrow minimal upstream signing key from k3b. Checksums-Sha1: 68a1d93ba6b72346ec42d178faa3b72cd9a928d6 2771 kolourpaint_20.12.0-1.dsc 6f182f8b06022d54371dcee9336e11d7068e13ef 5686588 kolourpaint_20.12.0.orig.tar.xz 92919da76776b774c2c3ffa5638e627383c113eb 488 kolourpaint_20.12.0.orig.tar.xz.asc 9d2b7388bbeae894aa058ba22e5095627211b6d0 9072 kolourpaint_20.12.0-1.debian.tar.xz a80d1329728cc3e177cb8f53a316d2d0e88be793 21976 kolourpaint_20.12.0-1_amd64.buildinfo Checksums-Sha256: a6c4d3c316e9b7ef41777bef9340053b3ebd1f3a88fe228c0781cc8fdfe69461 2771 kolourpaint_20.12.0-1.dsc d80940e27155304aa0842fa3c08d72f8e383eb45beff49dc1a66b12b030be4ca 5686588 kolourpaint_20.12.0.orig.tar.xz 7743f2450e4896f258fe0abb98f5c1f31a12b4278444c1f451af512f484ce992 488 kolourpaint_20.12.0.orig.tar.xz.asc ecf0352980858d425a4b9e80ebd9cfec363722e4f107e62ecef04b67f251b03d 9072 kolourpaint_20.12.0-1.debian.tar.xz 624845a7d4ef388fe9f220f09de2b94eb37c9db777c7717718ea591d8ee36ea1 21976 kolourpaint_20.12.0-1_amd64.buildinfo Files: a5d2b330ae0582b2ae957bcbd8bda370 2771 kde optional kolourpaint_20.12.0-1.dsc ee3ab9780d52bfb4f73930166cfc03ae 5686588 kde optional kolourpaint_20.12.0.orig.tar.xz a65b7b874029d7faa7c8c8e46c5ac2e9 488 kde optional kolourpaint_20.12.0.orig.tar.xz.asc b87f7e1cc0830e38cdd94a63a0a46a98 9072 kde optional kolourpaint_20.12.0-1.debian.tar.xz e69d6d231ac8db452e562fd1c10debe5 21976 kde optional kolourpaint_20.12.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAl/lIlMTHGNvdWNvdWZA ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJOUID/4zfvUpNZJhzQpDx2vZEuDxp0ev/KHx OLlSRnDTRy1/NAAXsSmrSHgGxpuJfyT8/wDZBvJYV1D0ct/CM7Pgi9AzPOR6qmaK 52X7rrcauj2IK2Av7+f4/CDL1uUyRXcbN1M6Z2caF44WC3Rqrl0271ZRMiyT4b7u IZexW0tdZshmCdfTHAG1x5MSRg6Tg4Lqq3wI/S5RWEGfSjHd/i7q01YkQS6j6f/Q lRqttNN/d0lX0pQFTX/2uO8rucJF7njsBmcdHePcgLTcMPiuf4y8BUF0pNuw5IxV oHT4yo0tW1OlIZoBVhIkm7qppoDdmwSpyQwl9XzVVvkA9bsohFICy/8d6CiV0Ahq wyhLUiPicxiprn+3jedktL4uoiLw+l0zeuLTcabjOnHrX6cbklCsr72roBiDSxCX 3oRUv1hkNbkRU9bDglphe84FzwQLfAcoirFedJ7/P/VQVKlaZmWl1YZgTc7ZHCF/ lX5h+WZsws+jIWQvESWK98FrXfKY64BUHfJiMAdxjhvnX2RJX/PspQkFLFKDl4Oo b4RecHfY2bZliiIIxYuVLVi5k1lPB08EtFeAucGynlPAVwa4TEf/Sm/NC7GMxJlx FZ3coRCmvbh8pcmT00ZrHl3/QL/HBCMzJqoQ7IIdiDU1PG8+NS07h+MU6f3sGHej lpTEVcMj9RRAZA== =mCi0 -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of libkomparediff2_20.12.0-1_amd64.changes
libkomparediff2_20.12.0-1_amd64.changes uploaded successfully to localhost along with the files: libkomparediff2_20.12.0-1.dsc libkomparediff2_20.12.0.orig.tar.xz libkomparediff2_20.12.0.orig.tar.xz.asc libkomparediff2_20.12.0-1.debian.tar.xz libkomparediff2-5-dbgsym_20.12.0-1_amd64.deb libkomparediff2-5_20.12.0-1_amd64.deb libkomparediff2-dev_20.12.0-1_amd64.deb libkomparediff2_20.12.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processing of kompare_20.12.0-1_amd64.changes
kompare_20.12.0-1_amd64.changes uploaded successfully to localhost along with the files: kompare_20.12.0-1.dsc kompare_20.12.0.orig.tar.xz kompare_20.12.0.orig.tar.xz.asc kompare_20.12.0-1.debian.tar.xz kompare-dbgsym_20.12.0-1_amd64.deb kompare_20.12.0-1_amd64.buildinfo kompare_20.12.0-1_amd64.deb kpart5-kompare-dbgsym_20.12.0-1_amd64.deb kpart5-kompare_20.12.0-1_amd64.deb libkompareinterface-dev_20.12.0-1_amd64.deb libkompareinterface5-dbgsym_20.12.0-1_amd64.deb libkompareinterface5_20.12.0-1_amd64.deb Greetings, Your Debian queue daemon (running on host usper.debian.org)
kompare_20.12.0-1_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Dec 2020 01:22:43 +0100 Source: kompare Binary: kompare kompare-dbgsym kpart5-kompare kpart5-kompare-dbgsym libkompareinterface-dev libkompareinterface5 libkompareinterface5-dbgsym Architecture: source amd64 Version: 4:20.12.0-1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Aurélien COUDERC Description: kompare- file difference viewer kpart5-kompare - file difference viewer - kpart libkompareinterface-dev - file difference viewer - kpart interface library development file libkompareinterface5 - file difference viewer - kpart interface library Changes: kompare (4:20.12.0-1) unstable; urgency=medium . * New upstream release (20.12.0). * Update build dependencies according to the upstream build system: - Qt >= 5.12 - KF5 >= 5.68 * Refresh copyright information. * Bump Standards-Version to 4.5.1, no change required. * Bump debhelper compatibility level to 13. * Refresh upstream metadata. * Update project homepage. * Removed George Kiagiadakis, Maximiliano Curia, Modestas Vainius from the uploaders, thanks for your work on the package! * Added myself to the uploaders. * Build with hardening=+all build hardening flag. * Borrow minimal upstream signing key from k3b. * Install generated usr/share/qlogging-categories5/kompare.categories. * Drop kde-l10n migration rules, not needed anymore after 2 stable releases. Checksums-Sha1: f0d35901e59277183a3671d6e73ac0fd6209ff74 2898 kompare_20.12.0-1.dsc cc80a5c9b8845f1e9ee6eb1891d7b5019008fa14 921984 kompare_20.12.0.orig.tar.xz 1e6c6a641c31301d05de80e4fe8d04717860754b 488 kompare_20.12.0.orig.tar.xz.asc e9683d5caaa128d48199b32e4c0636fdd9630e3c 8672 kompare_20.12.0-1.debian.tar.xz ffd9c2758914887d26a16ad7d4f4fd6d1407c01c 655756 kompare-dbgsym_20.12.0-1_amd64.deb b8385b368cf7e0fad77d2c70c51b145ea71dcd36 23183 kompare_20.12.0-1_amd64.buildinfo 9a8b47081fe95d0fcec4e9eb1647b7bb4f692d31 738452 kompare_20.12.0-1_amd64.deb 8b598974b2729b37bde9bdada60b8cc118f443ab 1873748 kpart5-kompare-dbgsym_20.12.0-1_amd64.deb 2025f9a1e6b31962fdb4d73dd918b6eda988 133028 kpart5-kompare_20.12.0-1_amd64.deb 24ead02ca0087563f11057962bb50060872f9026 14320 libkompareinterface-dev_20.12.0-1_amd64.deb a77f8e6694dcd1f5f5fedc913ccf31cef8a14918 174976 libkompareinterface5-dbgsym_20.12.0-1_amd64.deb 345777f244e0e66e194c90d641d770e5c741b198 15340 libkompareinterface5_20.12.0-1_amd64.deb Checksums-Sha256: 47627566d63bf45fd0211a074f931e0aa86a543b784527c024e2dfeb944fcc6a 2898 kompare_20.12.0-1.dsc 6d838d59031dc91cbd0f690b881ec3b35e70e63a921c5454f709520f8646576a 921984 kompare_20.12.0.orig.tar.xz 5dfeaf88390abf7644ab5be98f4b246744a105caca243fb88d288de28d80ea66 488 kompare_20.12.0.orig.tar.xz.asc 0deb7c96f8af998c9d8783c75df8ec0cfc84fcf52777a1b4c516391fea6b655a 8672 kompare_20.12.0-1.debian.tar.xz d9fac3bce24a5c64b098e7431383eb9fe87dd218ef1529bea94716621e8a7043 655756 kompare-dbgsym_20.12.0-1_amd64.deb 87beb5bf4088a64106a186ee56b8d06b120bfb4cf84e739457e6c10dbe48b3a3 23183 kompare_20.12.0-1_amd64.buildinfo ee715b4bfce8e7958cdae1fc2bf9c23734a51ae96da091bc177cbac3376738e4 738452 kompare_20.12.0-1_amd64.deb fb0e46a018afbe9be589ef56991458dccc3ce1905f009c3ece6d1e9884abd7c2 1873748 kpart5-kompare-dbgsym_20.12.0-1_amd64.deb 984f8b83909065fa0e59792d987c6a84b66d0aeb26e3a54b4f89ad1321c48be1 133028 kpart5-kompare_20.12.0-1_amd64.deb 99372b7a1767917752439393f6c0aa8048188f272d5d3603b0afe503fcfce3a1 14320 libkompareinterface-dev_20.12.0-1_amd64.deb 56a778c4d5c28b0ea604735296755b748aaecd20ea8bcf116fb66be95958a70d 174976 libkompareinterface5-dbgsym_20.12.0-1_amd64.deb 4f19e288dae6e0ceb889a8672556f47dd62de95e18490cc6dc8e4b5d66a4c30e 15340 libkompareinterface5_20.12.0-1_amd64.deb Files: 7685bf2df5dab5ba42e8dfed2c4f515a 2898 kde optional kompare_20.12.0-1.dsc 2bd605f7386799febe214ad85288531e 921984 kde optional kompare_20.12.0.orig.tar.xz f3e3cdb7de1894843621601b813819e9 488 kde optional kompare_20.12.0.orig.tar.xz.asc 0f82a0e9cb596c8c6ab89a6086d7aa7c 8672 kde optional kompare_20.12.0-1.debian.tar.xz 0843c9e3ec4bd8112f8969be6e869495 655756 debug optional kompare-dbgsym_20.12.0-1_amd64.deb 17530a1fce28ed4afd7a7f2ae1c9a1e1 23183 kde optional kompare_20.12.0-1_amd64.buildinfo 1124e38b52cf728226e4bc5f6ad0fded 738452 devel optional kompare_20.12.0-1_amd64.deb e4ad831b1aebb5e57a795ff9f26d7564 1873748 debug optional kpart5-kompare-dbgsym_20.12.0-1_amd64.deb 3e0fe64b61b876380ffcdf230a44e04e 133028 devel optional kpart5-kompare_20.12.0-1_amd64.deb 47ae93e2af3932ab853035e553b74ec3 14320 libdevel optional libkompareinterface-dev_20.12.0-1_amd64.deb eb57ff1b2da323a867d55166d3066fe8 174976 debug optional libkompareinterface5-dbgsym_20.12.0-1_amd64.deb 56717e8a63996a32bff50f4980808769 15340 libs optional libkompareinterface5_20.12.0-1_amd64.deb -BEGIN PGP SIGNATURE-
libkomparediff2_20.12.0-1_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Dec 2020 01:21:49 +0100 Source: libkomparediff2 Binary: libkomparediff2-5 libkomparediff2-5-dbgsym libkomparediff2-dev Architecture: source amd64 Version: 4:20.12.0-1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Aurélien COUDERC Description: libkomparediff2-5 - library to compare files and strings libkomparediff2-dev - library to compare files and strings - development files Changes: libkomparediff2 (4:20.12.0-1) unstable; urgency=medium . * New upstream release (20.12.0). * Update build dependencies according to the upstream build system: - Qt >= 5.12 - KF5 >= 5.68 * Refresh copyright information. * Bump Standards-Version to 4.5.1, no change required. * Bump debhelper compatibility level to 13. * Refresh upstream metadata. * Update project homepage. * Build with hardening=+all build hardening flag. * Borrow minimal upstream signing key from k3b. * Drop kde-l10n migration rules, not needed anymore after 2 stable releases. * Install generated usr/share/qlogging-categories5/libkomparediff2.categories. * Removed Maximiliano Curia from the uploaders, thanks for your work on the package! * Added myself to the uploaders. Checksums-Sha1: ba4da37d97764f276a214a52f511ba28821420e6 2767 libkomparediff2_20.12.0-1.dsc 5a37c505e8ccfa83e4ee70162687444199590b32 159368 libkomparediff2_20.12.0.orig.tar.xz fdf93a294bee5117d207f1907efeaf69301636b6 488 libkomparediff2_20.12.0.orig.tar.xz.asc af5496e8edfcdeeb8e8b69a4fbe29ea7ce44e9cb 8816 libkomparediff2_20.12.0-1.debian.tar.xz 8d63e5260c954ee32ce72914073c5b3aad469c2b 1335560 libkomparediff2-5-dbgsym_20.12.0-1_amd64.deb ad63c42d3c200d898a5eb6118a188ac2552b6be8 90268 libkomparediff2-5_20.12.0-1_amd64.deb c3e66fa171643997825d52a490d9c0a08cef492d 14644 libkomparediff2-dev_20.12.0-1_amd64.deb 335c5e61c8e0c3b28921c8668fe2af0c4c7ce49a 15502 libkomparediff2_20.12.0-1_amd64.buildinfo Checksums-Sha256: babf8728c687f90b76514fb68d6ef806494ac7aff62508acf8744a963102abea 2767 libkomparediff2_20.12.0-1.dsc 8b92b729d2d1c7998b22ffd6a7ae95f46954785d4855ce6cfa7a1fb401cf66ec 159368 libkomparediff2_20.12.0.orig.tar.xz 660cac1dd334af5a315f341bfa683327fe17f2e67a4cc00a2943ebd60c44038a 488 libkomparediff2_20.12.0.orig.tar.xz.asc 95cb30af1627b97ee06694cbb56baed698d2f0ed8c7891544c2565300e1c8b46 8816 libkomparediff2_20.12.0-1.debian.tar.xz e571fab56c07f2f6fc1f288e329181e8b788869ab5ee4cff426533fd7501c583 1335560 libkomparediff2-5-dbgsym_20.12.0-1_amd64.deb 3244155c77b99e9acc101855ddfc5887628cb794bbfae6dce7b1017fa2ad943e 90268 libkomparediff2-5_20.12.0-1_amd64.deb 74622ff65c05c4ca4053fc0bc902534b8bb8d5501a19d4ed5a848eeff7e80a84 14644 libkomparediff2-dev_20.12.0-1_amd64.deb c89e90d4abb6b4130d184b8050cf7125c159d19b4e1dd54582fe081e8ec61f37 15502 libkomparediff2_20.12.0-1_amd64.buildinfo Files: 9293342c8bf747cf3645187d05666f6c 2767 kde optional libkomparediff2_20.12.0-1.dsc 49294bf98f2af71bdefe9389f66bed5c 159368 kde optional libkomparediff2_20.12.0.orig.tar.xz 53ad3476dec9fae2fdda0c89d0486c57 488 kde optional libkomparediff2_20.12.0.orig.tar.xz.asc 490917542f071d03f09e2fefb7b784d2 8816 kde optional libkomparediff2_20.12.0-1.debian.tar.xz d4ed8553f592c453b286bd5c1ea3c93e 1335560 debug optional libkomparediff2-5-dbgsym_20.12.0-1_amd64.deb 85240dc17b3b86b0c5bb707d38d36669 90268 libs optional libkomparediff2-5_20.12.0-1_amd64.deb 873e041276514918d46da2db0a7af9d2 14644 libdevel optional libkomparediff2-dev_20.12.0-1_amd64.deb ef8c546fa410ba6260bf6cca3eb23488 15502 kde optional libkomparediff2_20.12.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAl/lMfMTHGNvdWNvdWZA ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJCicD/4w2bUqZfVCsFuRHmA4IA+xPXpnyKrt zhY7ta0KjglRg1F90YuU1QUzGVRLTujMJiAM/HWM7pp2uv1BAhXHC2Wfm4uftLPr 2B4eaADYBzMde0pval3boKQAPixFLKI9sFoUzsk68dZOVNQ1WNzqsrt/A/OSy0Tc QiLOxMS3DSoBIUCnrZMVYA2jwrm90j4iccBifNBBRfoipGdcjr5M24NTahdeTzkc TV2wcuK6ybYm24YaWFKKKH5PkPLBrBSJGpQb9R0uDyo5mav8emxs7/4YatRw+90d mFRgBKU/vKapVIQdXvFsD/kvWZqi4KCt+jkrd188Hf/Sd3mIVlfB7cIBGTifUacs Fy3FR6RSEqMUraagMQpy6TF7YJqjMh5O31t8zcsWW4ZtF+P1ZswGfzSKHlTSoHg0 eaGB755fSIjVsgp2VwCvlCOdvdxyCGDvYqTEUT/pj/04v2MJVWFblGbqnvwnp6ps Xtp9040AYJsN7gre2CIj61x+HJoJnEq8xopASrX/wY/bODGdHGuv1vCPXPpd3Ldh P5+kWtG29t8oNj65IfVOmrDRhc9zA3XMFk0Oc9KsaVARlS2WZaqX3o1LaMar7cy8 6IAG7Xz6NnUU9ugXIfzG6EdGg/ir2mJDOngamJTZzpc4BfI+uIzOxxWLlLg/1GhK BGBJQzz30OXGrg== =LFIB -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#978008: libkwaylandserver5: undefined symbol: _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShellSurfaceInterfaceE"
Hi Vincas, > Package: libkwaylandserver5 > Version: 5.20.4-2 > /usr/bin/kwin: symbol lookup error: /lib/x86_64-linux-gnu/libkwin.so.5: > undefined symbol: > _ZN14KWaylandServer17XdgShellInterface14surfaceCreatedEPNS_24XdgShe > llSurfaceInterfaceE Which version of kwin do you have installed? Seems like a missing breaks against old versions of kwin or so. > It seems that I have go perform `full-upgrade` that removes `user-manager`. > After that KDE desktop works. Yes, user-manager is going away. It is now a kcm and not a separate program. Best Norbert -- PREINING Norbert https://www.preining.info Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#974860: Forwarded to upstream
Hey Silvério, thanks for forwanrding the bugs to upstream. I see you tried to update the Debian Bug Tracker(BTS) two times. Pino already properly updated your bugs. Okay I was not exactly clear about the correct syntax. There are two way to interact with BTS. You can use sending mails to cont...@debian.org, than you have to send: Forwarded 974860 https://bugs.kde.org/show_bug.cgi?id=430719 Or you send the mail to the bug itself ( 974...@bugs.debian.org) than you have to prefix the command with Control: Control: Forwarded 974860 https://bugs.kde.org/show_bug.cgi?id=430719 Additionally you are able to replace the current bugnumber with -1 so you can shorten this to: Control: Forwarded -1 https://bugs.kde.org/show_bug.cgi?id=430719 and please use only text-only mails. In the beginning it is hard to remember the differences and make a lot a failures. Sorry for not being that precise. You can find the documentation at https://bugs.debian.org. There is also a CLI from devscripts package the command is called bts. hefee signature.asc Description: This is a digitally signed message part.
Processed: Bug#978006 marked as pending in extra-cmake-modules
Processing control commands: > tag -1 pending Bug #978006 [extra-cmake-modules] extra-cmake-modules: please change the section of the package Added tag(s) pending. -- 978006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978006 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
