[kwin] [Bug 467212] New: Unexpectedly when "move to desktop" functionality is used
https://bugs.kde.org/show_bug.cgi?id=467212 Bug ID: 467212 Summary: Unexpectedly when "move to desktop" functionality is used Classification: Plasma Product: kwin Version: 5.27.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: hartog@gmail.com Target Milestone: --- Created attachment 157195 --> https://bugs.kde.org/attachment.cgi?id=157195&action=edit Video demonstration of the bug SUMMARY 1. When an applications is moved to another desktop, the icon is still active on the current Task Manager (and not shown on the desired desktop) Only 1 applications showed this behavior, after the application was closed. It behaved as expected (See the first part of the video for a demonstration) 2. When an applications is moved to a specific desktop, the selected radio button is not highlighted (also note that no radio button option is selected at all) (See the second part of the video for a demonstration) STEPS TO REPRODUCE Unfortunately I haven't been able to reproduce these issues The first issue was "resolved" when I closed the application I'm not able to close the application for the second issue (because that would clear out this form) OBSERVED RESULT 1. Application is moved to different desktop, but this is not reflected in the Task Manager 2. No radio button in the "Move to desktop" is selected EXPECTED RESULT 1. Application is moved to different desktop, and application is shown in the Task Manager when the other desktop is selected 2. The radio button reflects the selected option SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I was not able to add 2 videos, so both scenarios are combined into a single video -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467212] Unexpectedly when "move to desktop" functionality is used
https://bugs.kde.org/show_bug.cgi?id=467212 --- Comment #1 from Jasper --- I was able to reproduce the second issue, by opening multiple instances of the same application STEPS TO REPRODUCE Open multiple instances of an application OBSERVED RESULT No radio button in "Move to desktop" is highlighted EXPECTED RESULT The selected radio button is highlighted -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365372] HSY' square color selector does not display the correct square content for a given hue
https://bugs.kde.org/show_bug.cgi?id=365372 Jasper changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |hartog@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365372] HSY' square color selector does not display the correct square content for a given hue
https://bugs.kde.org/show_bug.cgi?id=365372 Jasper changed: What|Removed |Added CC||hartog@gmail.com --- Comment #5 from Jasper --- I'm unable to reproduce this bug in the latest release (4.3.0). Can anybody confirm that this bug is still present in the latest release? When I draw a shape with a color selected on the color circle and pick it up with the eye-dropper the color of the color circle doesn't change. (This may be another bug, but seems related) When a color is selected on the color wheel, and the color model type is changed the square inside the color wheel is moved. Although this is the case for all the color model types. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404771] Panning of canvas cant be set to Shift+Alt+LMB.
https://bugs.kde.org/show_bug.cgi?id=404771 Jasper changed: What|Removed |Added Resolution|--- |NOT A BUG CC||firebea...@gmail.com Status|CONFIRMED |RESOLVED --- Comment #1 from Jasper --- The shortcut Shift + Alt + Left is already in use in the Default Krita Profile. The shortcut is used in the Alternate Invocation section to set the action mode of the current tool to Secondary Mode. If you want to use the Shift + Alt + Left combination for another action you need to make sure that the key/mouse combination is only used once. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407278] New: safe assert
https://bugs.kde.org/show_bug.cgi?id=407278 Bug ID: 407278 Summary: safe assert Product: krita Version: git master Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: G'Mic for Krita Assignee: krita-bugs-n...@kde.org Reporter: firebea...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407278] safe assert
https://bugs.kde.org/show_bug.cgi?id=407278 Jasper changed: What|Removed |Added Component|G'Mic for Krita |Tools/Colorize Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Jasper --- SUMMARY When using the Colorize Mask tool the latest version of Krita(#2e600f3) crashes. This bug was probably introduced by #56a13166. STEPS TO REPRODUCE 1. Open Krita 2. Create new file 3. Select Colorize Mask Editing Tool 4. Click somewhere on the image OBSERVED RESULT The program crashes. EXPECTED RESULT The colorized mask is used as normal. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel: 5.0.7-rt5-MANJARO KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION Git hash of krita source: #2e600f3 Error code: SAFE ASSERT (krita): "m_d->selection" in file /home/jasper/Projects/krita/src/libs/image/kis_mask.cc, line 228 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407278] safe assert
https://bugs.kde.org/show_bug.cgi?id=407278 Jasper changed: What|Removed |Added CC||firebea...@gmail.com --- Comment #3 from Jasper --- Created attachment 119877 --> https://bugs.kde.org/attachment.cgi?id=119877&action=edit backtrace of crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379463] Advanced Color Picker stops updating after picking a color with the Zoom Selector UI
https://bugs.kde.org/show_bug.cgi?id=379463 Jasper changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |hartog@gmail.com CC||hartog@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409818] For float bit depths, some fraction inputs convert too early, making it impossible to type in some fractions
https://bugs.kde.org/show_bug.cgi?id=409818 Jasper changed: What|Removed |Added Status|CONFIRMED |ASSIGNED Assignee|krita-bugs-n...@kde.org |firebea...@gmail.com CC||firebea...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379463] Advanced Color Picker stops updating after picking a color with the Zoom Selector UI
https://bugs.kde.org/show_bug.cgi?id=379463 Jasper changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||krita/commit/170cc3ea48b575 ||9ca93b3343f6ac74f9d5733b4c Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Jasper --- Git commit 170cc3ea48b5759ca93b3343f6ac74f9d5733b4c by Jasper Hartog. Committed on 30/10/2019 at 12:33. Pushed by rempt into branch 'master'. Re-activate Advanced Color Selector after popup Only block the Color Selector when it actualy updates the resource. M +2-5 plugins/dockers/advancedcolorselector/kis_color_selector_base.cpp M +2-0plugins/dockers/advancedcolorselector/kis_color_selector_base.h https://invent.kde.org/kde/krita/commit/170cc3ea48b5759ca93b3343f6ac74f9d5733b4c -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387946] New: find new items stalls at 90%
https://bugs.kde.org/show_bug.cgi?id=387946 Bug ID: 387946 Summary: find new items stalls at 90% Product: digikam Version: 5.6.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Database-Scan Assignee: digikam-bugs-n...@kde.org Reporter: jasper.macken...@gmail.com Target Milestone: --- On start up "find new items" progresses to 90% then halts. This has affected my versions of Digikam from Ubuntu for over a year now, and is worse on 5.8 as an appimage- which halts at 30%. The 90% halt occurs when scanning a collection mounted via NFS (gigabit), and is not influenced by the number of files. I have not been able to determine whether it is the fault of a single file. Database is local MYSQL and MariaDB - tried both, same issue. I have removed all configuration, created new databases etc. same result. I have tried with many versions from stock ubuntu going back to at least 17.04, and a compile from git around that time, from the 'official' ppa, and the 5.8 appimage. Digikam process does not end with program close via window close or album->quit when scanning fails to complete, rather it locks a thread up with 100% CPU, and requires a ctrl-c or harder kill to stop. The locked up thread is always called `Digikam::ScanCo` -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387946] find new items stalls at 90%
https://bugs.kde.org/show_bug.cgi?id=387946 --- Comment #2 from Jasper --- Nothing on the console seems that useful, and neither the Ubuntu package or the appimage have debugging symbols. THe best I can get you is running in GDB up to the point I kill it (after freezing at 90%). Please note that there is _nothing_ emitted in the console at the point at which digikam scan reaches 90%. So the last output are some time before then. THe scan is very fast up to this point 8) Starting program: /usr/bin/digikam [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffbd9f6700 (LWP 20935)] [New Thread 0x7fffb36a2700 (LWP 20936)] [New Thread 0x7fffb2ea1700 (LWP 20937)] [New Thread 0x7fffb26a0700 (LWP 20938)] [New Thread 0x7fffb0fdf700 (LWP 20939)] [New Thread 0x7fffa1fa2700 (LWP 20941)] [New Thread 0x7fffa17a1700 (LWP 20942)] [Thread 0x7fffa17a1700 (LWP 20942) exited] [New Thread 0x7fffa17a1700 (LWP 20956)] [New Thread 0x7fff965cb700 (LWP 20957)] [New Thread 0x7fff95b82700 (LWP 20958)] [New Thread 0x7fff94ce3700 (LWP 20959)] [New Thread 0x7fff4fffd700 (LWP 20960)] [New Thread 0x7fff4f7fc700 (LWP 20961)] [New Thread 0x7fff4effb700 (LWP 20962)] QFSFileEngine::open: No file name specified [New Thread 0x7fff4d887700 (LWP 20965)] QFSFileEngine::open: No file name specified [New Thread 0x7fff4cb84700 (LWP 20968)] [New Thread 0x7fff2700 (LWP 20969)] [New Thread 0x7fff2f7fe700 (LWP 20970)] [New Thread 0x7fff4cb84700 (LWP 20971)] [Thread 0x7fff4cb84700 (LWP 20968) exited] [Thread 0x7fff2f7fe700 (LWP 20970) exited] [New Thread 0x7fff2f7fe700 (LWP 20972)] QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified [Thread 0x7fff2700 (LWP 20969) exited] [Thread 0x7fff2f7fe700 (LWP 20972) exited] [Thread 0x7fff4d887700 (LWP 20965) exited] [Thread 0x7fff4cb84700 (LWP 20971) exited] ^C Thread 1 "digikam" received signal SIGINT, Interrupt. 0x73472901 in __GI___poll (fds=0x55df1dc0, nfds=11, timeout=5636) at ../sysdeps/unix/sysv/linux/poll.c:29 29 ../sysdeps/unix/sysv/linux/poll.c: No such file or directory. (gdb) bt #0 0x73472901 in __GI___poll (fds=0x55df1dc0, nfds=11, timeout=5636) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fffe97db169 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fffe97db27c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7439d47f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x74342e3a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x774a8056 in Digikam::ScanController::completeCollectionScanCore(bool, bool) () at /usr/lib/digikam/libdigikamgui.so.5.6.0 #6 0x7766f6e8 in Digikam::NewItemsFinder::slotStart() () at /usr/lib/digikam/libdigikamgui.so.5.6.0 #7 0x74374452 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x750bf46c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x750c6d34 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x74344de8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7434755d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7439de53 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fffe97dafb7 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fffe97db1f0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fffe97db27c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7439d47f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x74342e3a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7434bda4 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x9fd0 in () #20 0x7338b1c1 in __libc_start_main (main= 0x9360, argc=1, argv=0x7fffde68, init=, fini=, rtld_fini=, stack_end=0x7fffde58) at ../csu/libc-start.c:308 #21 0xb06a in _start () -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387946] find new items stalls at 90%
https://bugs.kde.org/show_bug.cgi?id=387946 --- Comment #3 from Jasper --- Please note the bug was persistent on a Digikam database that had been stable for a very long time, and only had this years images added to it. I tried moving all the directories on the NFS server side away, adding them one at a time, starting digikam, letting it scan to completion, quitting digikam, moving one more directory (one directory per year) etc. In this way I found that the digikam scanning was failing on some very old images, very large 20x30x300dpi TIFF's which would have been scanned a long time ago. I have not found the exact file yet. I am not sure whether this makes the current bug _solved_/_resolved_/whatever. It would have been very useful to have some more verbose logging to know which file it is failing on. Amazingly there is a lot of bitrot, with more corrupt images than I would expect, yet digikam handled these fine. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387946] find new items stalls at 90%
https://bugs.kde.org/show_bug.cgi?id=387946 --- Comment #5 from Jasper --- Great that there are debugging symbols in the appimage. I was basing this assumption off GDB outputting Reading symbols from digikam-5.8.0-20171212T132305-x86-64.appimage...(no debugging symbols found)...done. But I had started the appimage from gdb i.e wrongly. Running the appimage 'find new files' halts at 21%. Note that this is without the problematic directory such that digikam 5.6 installed from ubuntu was able to complete the 'find new images' without a problem. I can still not see any reference to the image that may be causing the lockup/halt if this is indeed the fault. ./digikam-5.8.0-20171217T160920-x86-64.appimage debug --config ~/digikam.config -- digiKam AppImage Bundle -- Use 'help' as CLI argument to know all available options Starting digiKam into GDB... Use 'bt' command on debugger prompt to get a crash backtrace. Use 'q' command to quit debugger session. GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from digikam...done. Starting program: /tmp/.mount_jCx752/usr/bin/digikam --config /home/jasper/digikam.config [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe63ea700 (LWP 25731)] [New Thread 0x7fffe598b700 (LWP 25732)] [New Thread 0x7fffd700 (LWP 25734)] [New Thread 0x7fffde44b700 (LWP 25735)] [Thread 0x7fffde44b700 (LWP 25735) exited] [New Thread 0x7fffde44b700 (LWP 25736)] [Thread 0x7fffde44b700 (LWP 25736) exited] [New Thread 0x7fffde44b700 (LWP 25737)] [New Thread 0x7fffd2f3f700 (LWP 25738)] [New Thread 0x7fffd273e700 (LWP 25739)] [New Thread 0x7fffd1f3d700 (LWP 25740)] [New Thread 0x7fffd173c700 (LWP 25741)] [New Thread 0x7fffd0f3b700 (LWP 25742)] [New Thread 0x7fffb7fff700 (LWP 25743)] [New Thread 0x7fffb77fe700 (LWP 25744)] [New Thread 0x7fffb6ffd700 (LWP 25745)] [New Thread 0x7fffb67fc700 (LWP 25746)] [New Thread 0x7fffb5ffb700 (LWP 25747)] [New Thread 0x7fffb57fa700 (LWP 25748)] [New Thread 0x7fffb4ff9700 (LWP 25749)] [New Thread 0x7fff97fff700 (LWP 25750)] [New Thread 0x7fff577fc700 (LWP 25753)] [New Thread 0x7fff56ffb700 (LWP 25754)] [New Thread 0x7fff567fa700 (LWP 25755)] QtAV 1.12.0(Jul 20 2017, 17:39:32) Multimedia framework base on Qt and FFmpeg. Distributed under the terms of LGPLv2.1 or later. Shanghai University->S3 Graphics->Deepin->PPTV, Shanghai, China Copyright (C) 2012-2016 Wang Bin (aka. Lucas Wang) wbse...@gmail.com Donate: http://qtav.org/donate.html Source: https://github.com/wang-bin/QtAV Home page: http://qtav.org capi::version: 0.6.0 [New Thread 0x7fffd0301700 (LWP 25756)] Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock [Thread 0x7fffd0301700 (LWP 25756) exited] [New Thread 0x7fff55ff9700 (LWP 25757)] [Thread 0x7fff55ff9700 (LWP 25757) exited] [New Thread 0x7fff55ff9700 (LWP 25758)] [Thread 0x7fff55ff9700 (LWP 25758) exited] [New Thread 0x7fff55ff9700 (LWP 25759)] [New Thread 0x7fffd0280700 (LWP 25760)] [New Thread 0x7fff54fe0700 (LWP 25761)] [New Thread 0x7fff3bffe700 (LWP 25762)] [New Thread 0x7fff3b7fd700 (LWP 25763)] [New Thread 0x7fff3affc700 (LWP 25764)] [New Thread 0x7fff3a7fb700 (LWP 25765)] [New Thread 0x7fff39ffa700 (LWP 25766)] [New Thread 0x7fff397f9700 (LWP 25767)] QFSFileEngine::open: No file name specified [New Thread 0x7fff1bfff700 (LWP 25769)] [New Thread 0x7fff1b7fe700 (LWP 25770)] [New Thread 0x7fff1affd700 (LWP 25771)] [New Thread 0x7fff1a7fc700 (LWP 25772)] [New Thread 0x7fff19ffb700 (LWP 25773)] [New Thread 0x7fff197fa700 (LWP 25774)] [New Thread 0x7fff18ff9700 (LWP 25775)] [New Thread 0x7fff0bfff700 (LWP 25776)] [New Thread 0x7fff0b7fe700 (LWP 25777)] [New Thread 0x7fff0affd700 (LWP 25778)] [New Thread 0x7fff0a7fc700 (LWP 25779)] [New Thread 0x7fff09ffb700 (LWP 25780)] [New Thread 0x7fff097fa700 (LWP 25781)] [New Thread 0x7fff08ff9700 (LWP 25
[krita] [Bug 403535] New: Canvas isn't cleared when adding a new blank frame.
https://bugs.kde.org/show_bug.cgi?id=403535 Bug ID: 403535 Summary: Canvas isn't cleared when adding a new blank frame. Product: krita Version: 4.1.7 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: firebea...@gmail.com Target Milestone: --- Created attachment 117624 --> https://bugs.kde.org/attachment.cgi?id=117624&action=edit Quick demonstration of the bug SUMMARY Canvas isn't cleared when creating a blank frame. STEPS TO REPRODUCE 1. Set Krita's workspace to Animation. 2. Create a new document. 3. Create two new blank frames. 4. Draw on each frame a line. 5. Click on "Create Blank Frame" while having one of the two frames selected. 6. Draw a line across the other line. 7. Switch to the other frame and back. OBSERVED RESULT The old frame is still visible after creating a blank frame. EXPECTED RESULT The current canvas is cleared. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I reprodused this bug on: Windows 10 (OpenGL & DirectX), Krita 4.1.7 Manjaro Krita 4.1.7 & newest Krita (compiled from source) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403535] Canvas isn't cleared when adding a new blank frame.
https://bugs.kde.org/show_bug.cgi?id=403535 Jasper changed: What|Removed |Added CC||firebea...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403854] New: Timeline doesn't highlight current frame when loading document
https://bugs.kde.org/show_bug.cgi?id=403854 Bug ID: 403854 Summary: Timeline doesn't highlight current frame when loading document Product: krita Version: 4.1.7 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: firebea...@gmail.com Target Milestone: --- SUMMARY When a animation is loaded the last active frame is selected but not highlighted in the timeline. STEPS TO REPRODUCE 1. Set Krita's workspace to Animation. 2. Create a new document. 3. Create a animation with 5 frames. 4. Select the 3th frame. 5. Draw something on the 3th frame. 6. Save your animation. 7. Close Krita, not only your document. 8. Open Krita. 9. Open your animation. OBSERVED RESULT When you open your animation the first frame in the timeline is highlighted but the 3th frame is active. EXPECTED RESULT The 3th frame in the timeline is highlighted and active. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Tested on 4.1.7 and from source (#2400a82) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404376] THE FILTER OPTION DOESNT WORK
https://bugs.kde.org/show_bug.cgi?id=404376 Jasper changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||firebea...@gmail.com --- Comment #1 from Jasper --- Please create only one bug report per bug. If you want to add any information to clarify your bug, please update your other bug report. *** This bug has been marked as a duplicate of bug 404377 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404377] THE FILTER OPTION DOESNT WORK
https://bugs.kde.org/show_bug.cgi?id=404377 --- Comment #1 from Jasper --- *** Bug 404376 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444801] Turning monitor off and back on causes plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=444801 Jasper Albering changed: What|Removed |Added CC||jasper.alber...@gmail.com --- Comment #1 from Jasper Albering --- I'm having this issue with Plasma Wayland 5.23.2 on Arch Linux. Turning the screen off, and back on again with the button on the back makes plasmashell, konsole, dolphin and other kde apps crash. This is the log file I captured with journalctl -f | grep --line-buffered kde Nothing really different from the others it seems. Nov 02 14:52:35 doosje kded5[1154]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Nov 02 14:52:35 doosje polkit-kde-authentication-agent-1[1182]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Nov 02 14:52:35 doosje org_kde_powerdevil[1177]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Nov 02 14:52:35 doosje kdeconnectd[1221]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Nov 02 14:52:35 doosje xdg-desktop-portal-kde[3142]: xdp-kde-wayland-integration: Removing output: Nov 02 14:52:35 doosje xdg-desktop-portal-kde[3142]: xdp-kde-wayland-integration: manufacturer: "Acer Technologies" Nov 02 14:52:35 doosje xdg-desktop-portal-kde[3142]: xdp-kde-wayland-integration: model: "Acer R270U/85456647" Nov 02 14:52:35 doosje xdg-desktop-portal-kde[3142]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Nov 02 14:52:35 doosje plasmashell[9920]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop detected for property "height" Nov 02 14:52:35 doosje plasmashell[9920]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop detected for property "height" Nov 02 14:52:35 doosje plasmashell[9920]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop detected for property "height" Nov 02 14:52:35 doosje plasmashell[9920]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop detected for property "height" Nov 02 14:52:35 doosje kded5[1154]: Service "org.kde.StatusNotifierHost-9920" unregistered Nov 02 14:52:35 doosje kded5[1154]: kscreen.kded: Config does not have at least one screen enabled, WILL NOT save this config, this is not what user wants. -- Then this repeated 12 times: Nov 02 14:52:36 doosje xdg-desktop-portal-kde[3142]: xdp-kde-wayland-integration: Adding output: Nov 02 14:52:36 doosje xdg-desktop-portal-kde[3142]: xdp-kde-wayland-integration: manufacturer: "Acer Technologies" Nov 02 14:52:36 doosje xdg-desktop-portal-kde[3142]: xdp-kde-wayland-integration: model: "Acer R270U/85456647" Nov 02 14:52:36 doosje xdg-desktop-portal-kde[3142]: xdp-kde-wayland-integration: resolution: QSize(2560, 1440) -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 364365] Login not possible any more after changing password (with home partition encrypted)
https://bugs.kde.org/show_bug.cgi?id=364365 Jasper Jongmans changed: What|Removed |Added CC||jasper.jongmans+kde@gmail.c ||om Version|5.6.5 |5.12.3 Platform|Neon Packages |Kubuntu Packages --- Comment #5 from Jasper Jongmans --- I can confirm the same issue on KDE 5.12.3. Normally pam_ecryptfs will rewrap the mount passphrase on a login password change, so long as it is done by a tool that uses PAM. By design it cannot do so if the old password is not known as it needs to unwrap (decrypt) the mount passphrase first. Although User Manager does ask for the current password, this seems to be the generic prompt to elevate privileges. I suspect User Manager executes the password change as root passing only the new password, leaving PAM_OLDAUTHTOK empty and breaking pam_ecryptfs. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 504853] Endless loop asking for a certificate password when signing a document
https://bugs.kde.org/show_bug.cgi?id=504853 Jasper-Ben changed: What|Removed |Added CC||k...@fancydomain.mozmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #7 from Jasper-Ben --- Quick drive-by comment: The last working version is 24.12.3. 25.04.0 shows the same erroneous behaviour. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359820] New: Nvidia X server X Server Display Configuration Crashes KDE
https://bugs.kde.org/show_bug.cgi?id=359820 Bug ID: 359820 Summary: Nvidia X server X Server Display Configuration Crashes KDE Product: plasmashell Version: 5.5.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: morbid@hotmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Simply switching the one monitor off causes KDE to crash. There are many other issues with KDE and Nvidia X server, some are way too inconsistent to report. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7feb600a0800 (LWP 1776))] Thread 23 (Thread 0x7feb480ce700 (LWP 1777)): #0 0x7feb595c4bbd in poll () at /lib64/libc.so.6 #1 0x7feb5e4f1422 in () at /usr/lib64/libxcb.so.1 #2 0x7feb5e4f300f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7feb4a8513c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7feb59cbd32f in () at /usr/lib64/libQt5Core.so.5 #5 0x7feb58dce0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7feb595ccfed in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7feb45502700 (LWP 1791)): #0 0x7feb595c0c8d in read () at /lib64/libc.so.6 #1 0x7feb51762f45 in () at /usr/lib64/tls/libnvidia-tls.so.340.96 #2 0x7feb55ce7b60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7feb55ca6999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7feb55ca6df8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7feb55ca6f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7feb59eefd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7feb59e96d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7feb59cb861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7feb5cfa3df8 in () at /usr/lib64/libQt5Qml.so.5 #10 0x7feb59cbd32f in () at /usr/lib64/libQt5Core.so.5 #11 0x7feb58dce0a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7feb595ccfed in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7feb35368700 (LWP 1811)): #0 0x7feb595c4bbd in poll () at /lib64/libc.so.6 #1 0x7feb55ca6e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7feb55ca6f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7feb59eefd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7feb59e96d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7feb59cb861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7feb5cfa3df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7feb59cbd32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7feb58dce0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7feb595ccfed in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7feb2fa78700 (LWP 1812)): #0 0x7feb55ce8cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7feb55ca6e4a in () at /usr/lib64/libglib-2.0.so.0 #2 0x7feb55ca6f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7feb59eefd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7feb59e96d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7feb59cb861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7feb5cfa3df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7feb59cbd32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7feb58dce0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7feb595ccfed in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7feb2e1a8700 (LWP 1816)): #0 0x7feb58dd203f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7feb5f77586b in () at /usr/lib64/libQt5Script.so.5 #2 0x7feb5f775899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7feb58dce0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7feb595ccfed in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7feaa730d700 (LWP 1818)): #0 0x7feb595c4bbd in poll () at /lib64/libc.so.6 #1 0x7feb55ca6e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7feb55ca6f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7feb59eefd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7feb59e96d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7feb59cb861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6
