[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 471966] New: Using KRunner sometimes stops meta key from opening launcher
https://bugs.kde.org/show_bug.cgi?id=471966 Bug ID: 471966 Summary: Using KRunner sometimes stops meta key from opening launcher Classification: Plasma Product: krunner Version: 5.27.6 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lionsshark...@gmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY *** After KRunner is used, pressing the meta key to open your launcher (kickoff/"start menu", to be clear) sometimes does not work anymore. Alt+F1 command always works to open launcher when it is the assigned keyboard shortcut. Putting the computer to sleep and bringing it back up fixes the bug. *** STEPS TO REPRODUCE 1. Run KRunner 2. Close KRunner 3. Try to open launcher with Meta key 4. Launcher does not open, nothing happens OBSERVED RESULT Pressing the meta key to open your launcher does not work after KRunner is opened. EXPECTED RESULT KRunner having been opened in the past should not affect the user's ability to open their launcher with the meta key. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kernel 6.4.1-arch2-1 (64-bit) (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 471965] Starting a file transfer and cancelling it doesn't delete the cached/temporary/partially copied file and doesn't even shows up in the files. This fills up unnecessary storage
https://bugs.kde.org/show_bug.cgi?id=471965 Harsh NJ changed: What|Removed |Added Summary|Starting a file transfer|Starting a file transfer |and cancelling it doesn't |and cancelling it doesn't |delete the |delete the |cached/temporary/partially |cached/temporary/partially |copied file and doesn't |copied file and doesn't |even shows up in the files. |even shows up in the files. |This fills up unnecessary |This fills up unnecessary |storage.|storage. That can't be ||cleared up. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 471965] New: Starting a file transfer and cancelling it doesn't delete the cached/temporary/partially copied file and doesn't even shows up in the files. This fills up unnecessary st
https://bugs.kde.org/show_bug.cgi?id=471965 Bug ID: 471965 Summary: Starting a file transfer and cancelling it doesn't delete the cached/temporary/partially copied file and doesn't even shows up in the files. This fills up unnecessary storage. Classification: Applications Product: kdeconnect Version: unspecified Platform: Apple App Store OS: iPadOS Status: REPORTED Severity: major Priority: NOR Component: ios-application Assignee: lucas.w...@tuta.io Reporter: gunjanpawan1...@gmail.com Target Milestone: --- SUMMARY *** When you start to transfer a large file from KDE Connect on any of the platforms (I tested only from Android and Linux, both versions up to date) to KDE Connect on iPad, and cancel the transfer either manually, or when the iPadOS KDE connect app goes background or when iPad auto locks, that partially copied file stays on the disk, taking up space, and it doesn't even shows up in the Files up (even as a temp file that I can delete using a-shell App). Though it takes space as it shows in the iPadOS Settings App's storage menu. STEPS TO REPRODUCE 1. Start to copy a large (~2gb) file from some other device (on which app can go background, such as Android) to iPadOS 2. After it's done around 50% (you can see a progress bar on android device), cancel the transfer manually, or by backgrounding the app on iPad or locking the iPad. 3. Android will say "Transfer Failed" OBSERVED RESULT Open Settings>General>iPad Storage>KDE Connect on the iPad. The "Documents and Data" attribute will have an +1GB in it's size. Open the KDE Connect folder in Files App, the partial file is nowhere to be found. Use some method to "see hidden files", still no good! EXPECTED RESULT If any in progress transfer was cancelled, the partial file must be deleted. Otherwise small file cancels will add up to a large quantity, and large files will really fill up the storage. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Ubuntu 22.04 LTS Android Version: Android 10 Android KDE Connect version: 1.26.2 (Latest) iPadOS Version: 16.5.1 (20F75) iPad KDE Connect version: 0.3.0 (9) (Latest) KDE Plasma Version: N/A (GNOME) KDE Frameworks Version: N/A Qt Version: N/A ADDITIONAL INFORMATION To fix this temporarily I did the following: 1. Current "Documents and Data" size for KDE Connect: 2.26GB ( actual file contents size in the files app: 533.8 MB ) 2. Compress the KDE Connect folder in iPad , using the Files App. ( for backup purposes) 3. Delete the KDE Connect App Folder, and then also from the Recently Deleted bin 4. Current "Documents and Data" size for KDE Connect: 1.68GB ( with no files at all, this is the failed partial file storage ) 5. Delete the KDE Connect App from iPad, and reinstall it. 6. There shall be no entry for the App right now. Pair a new device and share something, say a photo. 7. check files storage and settings storage 8. Current "Documents and Data" size for KDE Connect: 300kb ( size of the copied photo, in my case ) 9. Uncompress the archive back into the KDE Connect folder 10. Current "Documents and Data" size for KDE Connect: 534.1 MB ( actual size of the real contents of the folder ) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470511] [NVIDIA] External Display not detected on wayland
https://bugs.kde.org/show_bug.cgi?id=470511 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470552] "Hide after: 3 seconds" never hides notifications
https://bugs.kde.org/show_bug.cgi?id=470552 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 470486] Can't update system
https://bugs.kde.org/show_bug.cgi?id=470486 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 471964] vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xFA 0x48 0x89 0x11 0x73 0x28 0x48
https://bugs.kde.org/show_bug.cgi?id=471964 Kyle Sanderson changed: What|Removed |Added Version|3.19.0 |3.21.0 --- Comment #1 from Kyle Sanderson --- fetch https://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/APKINDEX.tar.gz fetch https://dl-cdn.alpinelinux.org/alpine/v3.16/main/x86_64/APKINDEX.tar.gz fetch https://dl-cdn.alpinelinux.org/alpine/v3.16/community/x86_64/APKINDEX.tar.gz (1/1) Installing valgrind (3.21.0-r5) Executing busybox-1.35.0-r17.trigger OK: 92 MiB in 20 packages ==10== Massif, a heap profiler ==10== Copyright (C) 2003-2017, and GNU GPL'd, by Nicholas Nethercote ==10== Using Valgrind-3.21.0 and LibVEX; rerun with -h for copyright info ==10== Command: qbittorrent-nox ==10== Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8. Qt depends on a UTF-8 locale, but has failed to switch to one. If this causes problems, reconfigure your locale. See the locale(1) manual for more information. vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xFA 0x48 0x89 0x11 0x73 0x28 0x48 vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==10== valgrind: Unrecognised instruction at address 0xd7e210. ==10==at 0xD7E210: qRandomCpu(void*, long long) (in /bin/qbittorrent-nox) ==10==by 0xBD622F: QRandomGenerator::SystemGenerator::generate(unsigned int*, unsigned int*) (in /bin/qbittorrent-nox) ==10==by 0xBD633E: std::enable_if::type>::type, std::mersenne_twister_engine > >, std::is_unsigned, std::__not_ > >::value, void>::type std::mersenne_twister_engine::seed(QRandomGenerator::SystemGenerator&) (in /bin/qbittorrent-nox) ==10==by 0xBD6441: QRandomGenerator64::global() (in /bin/qbittorrent-nox) ==10==by 0xC03F2A: QTemporaryFileName::generateNext() (in /bin/qbittorrent-nox) ==10==by 0xC037F3: QTemporaryDirPrivate::create(QString const&) (in /bin/qbittorrent-nox) ==10==by 0x9C2A8F: QLocalServerPrivate::listen(QString const&) (in /bin/qbittorrent-nox) ==10==by 0x9C00C0: QLocalServer::listen(QString const&) (in /bin/qbittorrent-nox) ==10==by 0x47F569: QtLocalPeer::isClient() (in /bin/qbittorrent-nox) ==10==by 0x47533D: ApplicationInstanceManager::ApplicationInstanceManager(QString const&, QObject*) (in /bin/qbittorrent-nox) ==10==by 0x474366: Application::Application(int&, char**) (in /bin/qbittorrent-nox) ==10==by 0x47E26F: std::_MakeUniq::__single_object std::make_unique(int&, char**&) [clone .isra.0] (in /bin/qbittorrent-nox) ==10==by 0x463CD4: main (in /bin/qbittorrent-nox) ==10== Your program just tried to execute an instruction that Valgrind ==10== did not recognise. There are two possible reasons for this. ==10== 1. Your program has a bug and erroneously jumped to a non-code ==10==location. If you are running Memcheck and you just saw a ==10==warning about a bad jump, it's probably your program's fault. ==10== 2. The instruction is legitimate but Valgrind doesn't handle it, ==10==i.e. it's Valgrind's fault. If you think this is the case or ==10==you are not sure, please let us know and we'll try to fix it. ==10== Either way, Valgrind will now raise a SIGILL signal which will ==10== probably kill your program. ==10== ==10== Process terminating with default action of signal 4 (SIGILL): dumping core ==10== Illegal opcode at address 0xD7E210 ==10==at 0xD7E210: qRandomCpu(void*, long long) (in /bin/qbittorrent-nox) ==10==by 0xBD622F: QRandomGenerator::SystemGenerator::generate(unsigned int*, unsigned int*) (in /bin/qbittorrent-nox) ==10==by 0xBD633E: std::enable_if::type>::type, std::mersenne_twister_engine > >, std::is_unsigned, std::__not_ > >::value, void>::type std::mersenne_twister_engine::seed(QRandomGenerator::SystemGenerator&) (in /bin/qbittorrent-nox) ==10==by 0xBD6441: QRandomGenerator64::global() (in /bin/qbittorrent-nox) ==10==by 0xC03F2A: QTemporaryFileName::generateNext() (in /bin/qbittorrent-nox) ==10==by 0xC037F3: QTemporaryDirPrivate::create(QString const&) (in /bin/qbittorrent-nox) ==10==by 0x9C2A8F: QLocalServerPrivate::listen(QString const&) (in /bin/qbittorrent-nox) ==10==by 0x9C00C0: QLocalServer::listen(QString const&) (in /bin/qbittorrent-nox) ==10==by 0x47F569: QtLocalPeer::isClient() (in /bin/qbittorrent-nox) ==10==by 0x47533D: ApplicationInstanceManager::ApplicationInstanceManager(QString const&, QObject*) (in /bin/qbittorrent-nox) ==10==by 0x474366: Application::Application(int&, char**) (in /bin/qbittorrent-nox) ==10==by 0x47E26F: std::_MakeUniq::__single_object std::make_unique(int&, char**&) [clone .isra.0] (in /bin/qbittorrent-nox) ==10==by 0x463CD4: main (in /bin/qbittorrent-nox) ==10== Illegal instruction (core dumped) -- You are receiving this mail because: You are watching
[kwin] [Bug 470998] Tile Editor Launcher HotKey Meta+T Not Working
https://bugs.kde.org/show_bug.cgi?id=470998 vindicator changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from vindicator --- LOL @ bot -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 470576] While `built-in Screen` is disabled, If I manipulate the brightness mouse starts jiggling.
https://bugs.kde.org/show_bug.cgi?id=470576 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470623] After reboot/log-out, widgets that have been resized to minimum size, change size back
https://bugs.kde.org/show_bug.cgi?id=470623 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 470589] 'Searching' doesn't seem to work
https://bugs.kde.org/show_bug.cgi?id=470589 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 469600] Discover loads home fine, but installed tab, and apps that are not from flatpak, will just show "*Loading...*"
https://bugs.kde.org/show_bug.cgi?id=469600 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 420529] "Background activity" notification appears every time, even after you make a decision
https://bugs.kde.org/show_bug.cgi?id=420529 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #26 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471246] estimated output size
https://bugs.kde.org/show_bug.cgi?id=471246 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470437] Installing flatpak file opens Discover but "Loading" animation continuously loops; flackpak does not install.
https://bugs.kde.org/show_bug.cgi?id=470437 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471054] running into a hard coded limit in workspace_wrapper.h - - - causing kwin crashes
https://bugs.kde.org/show_bug.cgi?id=471054 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471089] Undocumented gestures/mouse swipe
https://bugs.kde.org/show_bug.cgi?id=471089 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470998] Tile Editor Launcher HotKey Meta+T Not Working
https://bugs.kde.org/show_bug.cgi?id=470998 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420157] Desktop is unresponsive after ALT+Tabbing
https://bugs.kde.org/show_bug.cgi?id=420157 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 471964] New: vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xFA 0x48 0x89 0x11 0x73 0x28 0x48
https://bugs.kde.org/show_bug.cgi?id=471964 Bug ID: 471964 Summary: vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xFA 0x48 0x89 0x11 0x73 0x28 0x48 Classification: Developer tools Product: valgrind Version: 3.19.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: massif Assignee: n...@valgrind.org Reporter: kyle.l...@gmail.com Target Milestone: --- fetch https://dl-cdn.alpinelinux.org/alpine/v3.16/main/x86_64/APKINDEX.tar.gz fetch https://dl-cdn.alpinelinux.org/alpine/v3.16/community/x86_64/APKINDEX.tar.gz (1/1) Installing valgrind (3.19.0-r0) Executing busybox-1.35.0-r17.trigger OK: 91 MiB in 20 packages ==10== Massif, a heap profiler ==10== Copyright (C) 2003-2017, and GNU GPL'd, by Nicholas Nethercote ==10== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info ==10== Command: qbittorrent-nox ==10== Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8. Qt depends on a UTF-8 locale, but has failed to switch to one. If this causes problems, reconfigure your locale. See the locale(1) manual for more information. vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xFA 0x48 0x89 0x11 0x73 0x28 0x48 vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==10== valgrind: Unrecognised instruction at address 0xd7e210. ==10==at 0xD7E210: qRandomCpu(void*, long long) (in /bin/qbittorrent-nox) ==10==by 0xBD622F: QRandomGenerator::SystemGenerator::generate(unsigned int*, unsigned int*) (in /bin/qbittorrent-nox) ==10==by 0xBD633E: std::enable_if::type>::type, std::mersenne_twister_engine > >, std::is_unsigned, std::__not_ > >::value, void>::type std::mersenne_twister_engine::seed(QRandomGenerator::SystemGenerator&) (in /bin/qbittorrent-nox) ==10==by 0xBD6441: QRandomGenerator64::global() (in /bin/qbittorrent-nox) ==10==by 0xC03F2A: QTemporaryFileName::generateNext() (in /bin/qbittorrent-nox) ==10==by 0xC037F3: QTemporaryDirPrivate::create(QString const&) (in /bin/qbittorrent-nox) ==10==by 0x9C2A8F: QLocalServerPrivate::listen(QString const&) (in /bin/qbittorrent-nox) ==10==by 0x9C00C0: QLocalServer::listen(QString const&) (in /bin/qbittorrent-nox) ==10==by 0x47F569: QtLocalPeer::isClient() (in /bin/qbittorrent-nox) ==10==by 0x47533D: ApplicationInstanceManager::ApplicationInstanceManager(QString const&, QObject*) (in /bin/qbittorrent-nox) ==10==by 0x474366: Application::Application(int&, char**) (in /bin/qbittorrent-nox) ==10==by 0x47E26F: std::_MakeUniq::__single_object std::make_unique(int&, char**&) [clone .isra.0] (in /bin/qbittorrent-nox) ==10==by 0x463CD4: main (in /bin/qbittorrent-nox) ==10== Your program just tried to execute an instruction that Valgrind ==10== did not recognise. There are two possible reasons for this. ==10== 1. Your program has a bug and erroneously jumped to a non-code ==10==location. If you are running Memcheck and you just saw a ==10==warning about a bad jump, it's probably your program's fault. ==10== 2. The instruction is legitimate but Valgrind doesn't handle it, ==10==i.e. it's Valgrind's fault. If you think this is the case or ==10==you are not sure, please let us know and we'll try to fix it. ==10== Either way, Valgrind will now raise a SIGILL signal which will ==10== probably kill your program. ==10== ==10== Process terminating with default action of signal 4 (SIGILL): dumping core ==10== Illegal opcode at address 0xD7E210 ==10==at 0xD7E210: qRandomCpu(void*, long long) (in /bin/qbittorrent-nox) ==10==by 0xBD622F: QRandomGenerator::SystemGenerator::generate(unsigned int*, unsigned int*) (in /bin/qbittorrent-nox) ==10==by 0xBD633E: std::enable_if::type>::type, std::mersenne_twister_engine > >, std::is_unsigned, std::__not_ > >::value, void>::type std::mersenne_twister_engine::seed(QRandomGenerator::SystemGenerator&) (in /bin/qbittorrent-nox) ==10==by 0xBD6441: QRandomGenerator64::global() (in /bin/qbittorrent-nox) ==10==by 0xC03F2A: QTemporaryFileName::generateNext() (in /bin/qbittorrent-nox) ==10==by 0xC037F3: QTemporaryDirPrivate::create(QString const&) (in /bin/qbittorrent-nox) ==10==by 0x9C2A8F: QLocalServerPrivate::listen(QString const&) (in /bin/qbittorrent-nox) ==10==by 0x9C00C0: QLocalServer::listen(QString const&) (in /bin/qbittorrent-nox) ==10==by 0x47F569: QtLocalPeer::isClient() (in /bin/qbittorrent-nox) ==10==by 0x47533D: ApplicationInstanceManager::ApplicationInstanceManager(QString const&, QObject*) (in /bin/qbittorrent-nox) ==10==by 0x474366: Application::Application(int&, char**) (in /bin/qbittorrent-nox) ==10==by 0x47E26F: std::_MakeUniq::__single_object std::make_unique(int&, char**&) [clone
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471961] Two database dump was made on the same day, but one of them is not read by digiKam
https://bugs.kde.org/show_bug.cgi?id=471961 caulier.gil...@gmail.com changed: What|Removed |Added Platform|Other |Microsoft Windows CC||caulier.gil...@gmail.com Component|Database-Albums |Database-Engine -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431431] Merging to hidden layer discards hidden layer
https://bugs.kde.org/show_bug.cgi?id=431431 marty changed: What|Removed |Added CC||kynlo@gmail.com --- Comment #6 from marty --- This particular issues loves to get me. It feels inconsistent to allow a user to merge a visible layer and an invisible layer. Considering the following behavior - try to apply a filter (Blur) to an invisible layer, I get error: "Cannot apply filter to locked layer" - try to draw on the invisible layer, I get error: "Layer is invisible" - try to merge 2 invisible layers, nothing changes I'd like to also add another perspective. When we merge an invisible layer, it isn't empty, it's hidden. Shouldn't a merge maintain that information that's within the layer (ignoring the layer property)? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #15 from pallaswept --- > I think the priority here is to make it not add subfolders/subfiles to the > config. Absolutely. Like I said in my post, items which never appear on the desktop do not ever need an entry in this file, and those are the ones that are causing the greatest part of the problem, after all, there are only so many items one can actually fit on the desktop, so hitting an amount sufficient to crash plasma would be very difficult if not for the fact that it's getting subfolders. > remember, people's computers are crashing Again I agree strongly with this. I've just made a comment on a case (384782, about being able to re-order taskbar items) where discussing *how* to do it has been going on for 6 years and nobody has done anything to make it *actually happen*. Time is of the essence here, let's not over-plan and under-do. > so just fixing the unnecessary > entries would be a good solution for now. After all the "positions" entry > already handles adding/removing the correct files correctly so it seems > fairly simple to me to fix the sceeenMapping.. It would be a good start to a solution, and decrease the amount of crashes experienced by more than any other part of it, for sure. But as I also mentioned in my post, the positions entry is not handling removing entries correctly. The entries that caused my crash were for files that no longer even existed. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471963] New: System settings crach while setting file type associations
https://bugs.kde.org/show_bug.cgi?id=471963 Bug ID: 471963 Summary: System settings crach while setting file type associations Classification: Applications Product: systemsettings Version: 5.27.6 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: formic...@gmail.com Target Milestone: --- Application: systemsettings (5.27.6) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.3.8-200.fc38.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 38 (KDE Plasma) DrKonqi: 5.27.6 [KCrashBackend] -- Information about the crash: After setting the default app for a dozen or two of file type in the Applications section, the System Settings crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7fbab877953c in operator==(QString const&, QString const&) () from /lib64/libQt5Core.so.5 #5 0x7fbaa45488a3 in KServiceListWidget::addService() () from /usr/lib64/qt5/plugins/plasma/kcms/systemsettings_qwidgets/kcm_filetypes.so #6 0x7fbab88e8461 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #7 0x7fbab96a9c64 in QAbstractButton::clicked(bool) () from /lib64/libQt5Widgets.so.5 #8 0x7fbab96a9eef in QAbstractButtonPrivate::emitClicked() () from /lib64/libQt5Widgets.so.5 #9 0x7fbab96ab850 in QAbstractButtonPrivate::click() () from /lib64/libQt5Widgets.so.5 #10 0x7fbab96aba58 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #11 0x7fbab95f3688 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #12 0x7fbab95aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #13 0x7fbab95b7456 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #14 0x7fbab88b4188 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #15 0x7fbab95b56a4 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib64/libQt5Widgets.so.5 #16 0x7fbab960d1a9 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7fbab961072f in QWidgetWindow::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #18 0x7fbab95aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #19 0x7fbab88b4188 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #20 0x7fbab8d6cc6b in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib64/libQt5Gui.so.5 #21 0x7fbab8d4acfc in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #22 0x7fbab34db4d6 in xcbSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5XcbQpa.so.5 #23 0x7fbab731339c in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #24 0x7fbab7371438 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #25 0x7fbab7310a23 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #26 0x7fbab8906729 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7fbab88b2b4b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #28 0x7fbab88baddb in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #29 0x563391c075a8 in main () [Inferior 1 (process 3034) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471962] Many windows are rendered black after opening
https://bugs.kde.org/show_bug.cgi?id=471962 --- Comment #2 from e.insafutdi...@gmail.com --- Created attachment 160085 --> https://bugs.kde.org/attachment.cgi?id=160085=edit screenshot1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471962] Many windows are rendered black after opening
https://bugs.kde.org/show_bug.cgi?id=471962 --- Comment #1 from e.insafutdi...@gmail.com --- Created attachment 160084 --> https://bugs.kde.org/attachment.cgi?id=160084=edit screenshot0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471962] New: Many windows are rendered black after opening
https://bugs.kde.org/show_bug.cgi?id=471962 Bug ID: 471962 Summary: Many windows are rendered black after opening Classification: Plasma Product: kwin Version: 5.27.6 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: e.insafutdi...@gmail.com Target Milestone: --- SUMMARY Occasionally, various windows on my desktop appear completely black after opening for the first time. This happens to context menus (see attached screenshot), a Thumbnail grid task switcher, File Save dialogs or even newly opened applications such as Gwenview. Unfortunately, I cannot reliably reproduce this behavior, it happens roughly once a week and is fixed by a reboot. Most likely, this is connected to NVIDIA platform. I'm using the latest driver (535.54.03), though this bug was present with the previous driver version (525) too. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 466241] kdiff3 crashes on invalid symbolic link
https://bugs.kde.org/show_bug.cgi?id=466241 michael changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #7 from michael --- The !m_modificationTime.isNull() assertion no longer exists in kdiff3 source. It proved to be invalid due to the design of QDateTime::isNull(). Current 1.10 yields a conflicting type error in the permissions case but will no longer crash. That removal may not have been part of the same commit. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471443] Low-res Images in Qt Apps when using fractional scaling
https://bugs.kde.org/show_bug.cgi?id=471443 Ilya Fedin changed: What|Removed |Added Component|general |Startup process CC||k...@davidedmundson.co.uk Target Milestone|--- |1.0 Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Product|kde |plasmashell Version|unspecified |5.27.6 --- Comment #2 from Ilya Fedin --- Hope plasmashell is the correct component, the bug is in startkde which is a part of plasma-workspace. The underlying problem is Plasma uses debug environment variables Qt provides instead of the proper API[1] such as Xft.dpi in xrdb and Xft/DPI in xsettings. The second one could be changed without re-login. Since the way Plasma sets up the scaling[3][4] is a debug one[2], it completely disregards the hints set by applications, such as no fractional scaling support[5] so Qt applies fractional scaling forcefully what leads to UI corruption. I'd say this is even worse than the effect of setting GTK debug environment variables which Plasma was doing in the past. Moreover, during the evolution of the codebase it has happened that a part of this logic has ended up being in startplasma-x11.cpp[3] and a part resides now in startplasma.cpp[4]. This leads to Xwayland Qt 5 applications being forbidden to scale. QT_AUTO_SCREEN_SCALE_FACTOR[4] is also a deprecated variable that was replaced by QT_ENABLE_HIGHDPI_SCALING during Qt 5 lifetime (seem to be undocumented) and is not being read by Qt 6 so Qt 6 applications end up being double-scaled. What Plasma should is to stop using Qt's debug environment variables, at all. This never makes any good, just like with gtk and likely any other library. If it needs its apps to be fractionally scaled then it should do that properly: by opting in every application, as that's the way upstream in the face of Qt has provided. Every other way screws up third-party applications which may not have support for fractional scaling. [1] https://doc.qt.io/qt-6/highdpi.html#configuring-x11 (undocumented in Qt 5 but mostly the same) [2] https://doc.qt.io/qt-6/highdpi.html#environment-variable-reference (poorly documented in Qt 5) [3] https://invent.kde.org/plasma/plasma-workspace/-/blob/master/startkde/startplasma-x11.cpp#L46-54 [4] https://invent.kde.org/plasma/plasma-workspace/-/blob/master/startkde/startplasma.cpp#L328-330 [5] https://doc.qt.io/qt-5/qguiapplication.html#highDpiScaleFactorRoundingPolicy -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441384] Dolphin's UI responsiveness becomes slow while counting items inside subfolders in an NTFS partition
https://bugs.kde.org/show_bug.cgi?id=441384 --- Comment #9 from René Fritz --- (In reply to René Fritz from comment #8) > KDE neon 5.27 22.04 (x86_64) > > I have the same Problem but with ext4. > > It seems dolphin in kde neon has git functionality included - even when the > dolphin-plugins package for git support is NOT installed. > > Dolphin shows icons with git status. Directories with many git repositories > take ages to count. The gui is laggy. > > A folder without git repositories is faster, but not lightning fast. I realised Kommit (Git gui client for KDE) was installed and caused the slow down. Which means my problem was not related to the bug report. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 471855] Application neochat doesn't start in Neon Unstable
https://bugs.kde.org/show_bug.cgi?id=471855 Piotr Mierzwinski changed: What|Removed |Added Keywords|qt6 | -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 471855] Application neochat doesn't start in Neon Unstable
https://bugs.kde.org/show_bug.cgi?id=471855 Piotr Mierzwinski changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 471855] Application neochat doesn't start in Neon Unstable
https://bugs.kde.org/show_bug.cgi?id=471855 Piotr Mierzwinski changed: What|Removed |Added Summary|Application doesn't start |Application neochat doesn't |in Neon Unstable|start in Neon Unstable -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441384] Dolphin's UI responsiveness becomes slow while counting items inside subfolders in an NTFS partition
https://bugs.kde.org/show_bug.cgi?id=441384 René Fritz changed: What|Removed |Added CC||rf-...@colorcube.de --- Comment #8 from René Fritz --- KDE neon 5.27 22.04 (x86_64) I have the same Problem but with ext4. It seems dolphin in kde neon has git functionality included - even when the dolphin-plugins package for git support is NOT installed. Dolphin shows icons with git status. Directories with many git repositories take ages to count. The gui is laggy. A folder without git repositories is faster, but not lightning fast. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471947] Wrong keyboard layout in sandboxed applications after login
https://bugs.kde.org/show_bug.cgi?id=471947 Aleix Pol changed: What|Removed |Added Version|5.27.6 |5.27.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471947] Wrong keyboard layout in sandboxed applications after login
https://bugs.kde.org/show_bug.cgi?id=471947 Aleix Pol changed: What|Removed |Added Target Milestone|--- |1.0 Product|plasma-wayland-protocols|plasmashell Component|general |general Version|1.10.0 |5.27.6 CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 471927] Plasma crashes in moment of click menu application outside of KDE
https://bugs.kde.org/show_bug.cgi?id=471927 --- Comment #1 from Piotr Mierzwinski --- SUMMARY When I click into menu in VLC, synaptic, signal, libreofice application then Plasma session crashes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.5.1 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471961] New: Two database dump was made on the same day, but one of them is not read by digiKam
https://bugs.kde.org/show_bug.cgi?id=471961 Bug ID: 471961 Summary: Two database dump was made on the same day, but one of them is not read by digiKam Classification: Applications Product: digikam Version: 8.1.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Database-Albums Assignee: digikam-bugs-n...@kde.org Reporter: benedekppe...@gmail.com Target Milestone: --- digiKam version: (Weekly Snapshots) 8.1 on Windows 10 and LinuxMint 21 (appimage) Database: mysql-server 5.7.42-0ubuntu0.18.04.1 (The database runs on an ubuntu server) Dump: dump files were created automatically warning before loading the database (20230704_09:00:01-digikam_FAULT.sql): Old character set: UTF8, new character set: UTF8MB4 Comment: 20230704_23:22:29-digikam_GOOD.sql -- I restored a previous database backup, then I created a new dump. This works well. The uploaded two database dump and two screenshot: https://mega.nz/folder/IMwn0aKa#kJW3tpwUM5FGfFkrNSL8tQ Environment: Language: HU The database runs on an ubuntu server, and windows 10 clients connect to it in a network. In LinuxMint am currently only checking the database backups, no changes are made! I opened the 20230704_09:00:01-digikam_FAULT.sql database in Windows 10 and LinuxMint client, and I see that the data is not displayed (Fault_database_dump.jpg). After opening the database, digiKam starts rebuilding the data, even though the data is already in the database (I checked in a text editor). I restored a save from a few days ago and the data appeared (Good_database_dump.jpg) Between the two dates, only a few labels and captions were made for the pictures. I reloaded again the 20230704_09:00:01-digikam_FAULT.sql database, but it seems the albums/photos data is lost. Can two nearby digiKam weekly snapshots cause this problem? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 446700] Kate does not save changes to user config on MacOS
https://bugs.kde.org/show_bug.cgi?id=446700 --- Comment #9 from ejkirch...@gmail.com --- I just tried with the last successful build (#1994 in my case, built today), and now Kate will crash upon launch. Unlike Kate's Linux version, Mac OS doesn't output Kate's stdout messages on the terminal, so finding log output is a bit difficult. But I was able to save the crash logs from console.app. Since this is now another issue, I'm considering writing a new bug report since now Kate won't launch at all. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 446700] Kate does not save changes to user config on MacOS
https://bugs.kde.org/show_bug.cgi?id=446700 --- Comment #8 from ejkirch...@gmail.com --- Created attachment 160083 --> https://bugs.kde.org/attachment.cgi?id=160083=edit Kate Crash Logs 040723 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471960] New: Frequent random crashes
https://bugs.kde.org/show_bug.cgi?id=471960 Bug ID: 471960 Summary: Frequent random crashes Classification: Applications Product: krita Version: git master (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: lynx.mw+...@gmail.com Target Milestone: --- Created attachment 160082 --> https://bugs.kde.org/attachment.cgi?id=160082=edit gdb backtrace Krita crashes every few minutes for me, no identifiable reason (even happened while idle in background once). See attached backtrace. Looks a lot like this commit is the cause: https://invent.kde.org/graphics/krita/-/commit/183997233a2bff56815573565ed27914eeed4cea 5.2.0 pre-alpha, git b1c826224092874a4c5926c97f2cea40147821d3 Ubuntu 22.04, compiled from source -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 448637] kalendar causes OOM when loading an event with location information
https://bugs.kde.org/show_bug.cgi?id=448637 el...@seznam.cz changed: What|Removed |Added CC||el...@seznam.cz --- Comment #10 from el...@seznam.cz --- Not sure if this is the same error, but when I try to edit an event with location by double clicking it, first click opens popup to show incidence information with trying to load a map, then second click opens edit modal and then whole Kalendar crashes. ``` PID: 387026 (kalendar) UID: 1000 (elman) GID: 1000 (elman) Signal: 11 (SEGV) Timestamp: Wed 2023-07-05 09:37:32 NZST (2min 27s ago) Command Line: /usr/bin/kalendar Executable: /usr/bin/kalendar Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.kalendar-2f4a80e07ca84bf9a24cda656eb65549.scope Unit: user@1000.service User Unit: app-org.kde.kalendar-2f4a80e07ca84bf9a24cda656eb65549.scope Slice: user-1000.slice Owner UID: 1000 (elman) Boot ID: b0805135d5284d688762490bd56de0ab Machine ID: 6938998c984d450f87775256a2c4554d Hostname: localhost Storage: /var/lib/systemd/coredump/core.kalendar.1000.b0805135d5284d688762490bd56de0ab.387026.168850665200.zst (present) Size on Disk: 38.9M Message: Process 387026 (kalendar) of user 1000 dumped core. Stack trace of thread 387026: #0 0x7f1d2a09900b pthread_kill (libc.so.6 + 0x9900b) #1 0x7f1d2a03e5e8 raise (libc.so.6 + 0x3e5e8) #2 0x7f1d28fd8ccf _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7ccf) #3 0x7f1d2a03e690 n/a (libc.so.6 + 0x3e690) Stack trace of thread 387030: #0 0x7f1d2a121e3d syscall (libc.so.6 + 0x121e3d) #1 0x7f1d2a8f2edc _ZN10QSemaphore7acquireEi (libQt5Core.so.5 + 0xf2edc) #2 0x7f1d2aadb78e n/a (libQt5Core.so.5 + 0x2db78e) #3 0x7f1d2aadbcc4 _ZN7QObject9destroyedEPS_ (libQt5Core.so.5 + 0x2dbcc4) #4 0x7f1d2aad18cc _ZN7QObjectD2Ev (libQt5Core.so.5 + 0x2d18cc) #5 0x7f1d2278b238 n/a (libKF5Kirigami2.so.5 + 0x1f238) #6 0x7f1d2aad113d _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 + 0x2d113d) #7 0x7f1d2aad18b9 _ZN7QObjectD2Ev (libQt5Core.so.5 + 0x2d18b9) #8 0x7f1d22787b5e n/a (libKF5Kirigami2.so.5 + 0x1bb5e) #9 0x7f1d2a040f05 n/a (libc.so.6 + 0x40f05) #10 0x7f1d2a041050 exit (libc.so.6 + 0x41050) #11 0x7f1d0d08e2b3 n/a (radeonsi_dri.so + 0xc8e2b3) #12 0x7f1d0c4cb930 n/a (radeonsi_dri.so + 0xcb930) #13 0x7f1d0c64ff1c n/a (radeonsi_dri.so + 0x24ff1c) #14 0x7f1d2a09708f n/a (libc.so.6 + 0x9708f) #15 0x7f1d2a1294b0 n/a (libc.so.6 + 0x1294b0) Stack trace of thread 387027: #0 0x7f1d2a117c3c read (libc.so.6 + 0x117c3c) #1 0x7f1d28700629 g_main_context_check (libglib-2.0.so.0 + 0x61629) #2 0x7f1d2876d788 n/a (libglib-2.0.so.0 + 0xce788) #3 0x7f1d286fe852 g_main_context_iteration (libglib-2.0.so.0 + 0x5f852) #4 0x7f1d2aaf72cc _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2f72cc) #5 0x7f1d2aaa4704 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2a4704) #6 0x7f1d2a8fa9e6 _ZN7QThread4execEv (libQt5Core.so.5 + 0xfa9e6) #7 0x7f1d2be6a02a n/a (libQt5DBus.so.5 + 0x1802a) #8 0x7f1d2a8f6b7a n/a (libQt5Core.so.5 + 0xf6b7a) #9 0x7f1d2a09708f n/a (libc.so.6 + 0x9708f) #10 0x7f1d2a1294b0 n/a (libc.so.6 + 0x1294b0) Stack trace of thread 387042: #0 0x7f1d2876efd7 n/a (libglib-2.0.so.0 + 0xcffd7) #1 0x7f1d28765659 n/a (libglib-2.0.so.0 + 0xc6659) #2 0x7f1d286ffaf2 g_main_context_prepare (libglib-2.0.so.0 + 0x60af2) #3 0x7f1d2876d6f6 n/a (libglib-2.0.so.0 + 0xce6f6) #4 0x7f1d286fe852 g_main_context_iteration (libglib-2.0.so.0 + 0x5f852) #5 0x7f1d2aaf72ef _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2f72ef) #6 0x7f1d2aaa4704 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2a4704) #7 0x7f1d2a8fa9e6 _ZN7QThread4execEv (libQt5Core.so.5 + 0xfa9e6) #8 0x7f1d2a8f6b7a n/a (libQt5Core.so.5 + 0xf6b7a) #9
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 471959] New: Remote input doesn't work
https://bugs.kde.org/show_bug.cgi?id=471959 Bug ID: 471959 Summary: Remote input doesn't work Classification: Applications Product: kdeconnect Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: r...@rwb.me.uk CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Install Ubuntu 22.04 2. Install Android app 3. Pair devices 4. Open app and go to remote input OBSERVED RESULT It doesn't work. EXPECTED RESULT It does work. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION ``` Jul 4 21:22:23 imac51 org.kde.kdeconnect.daemon.desktop[1630]: requestActivate() called for QQuickView(0x56132ef9a3b0) which has Qt::WindowDoesNotAcceptFocus set. Jul 4 21:24:30 imac51 pulseaudio[822]: Battery Level: 95% Jul 4 21:25:16 imac51 org.kde.kdeconnect.daemon.desktop[1630]: QObject::connect(KWayland::Client::Registry, Unknown): invalid nullptr parameter Jul 4 21:25:16 imac51 org.kde.kdeconnect.daemon.desktop[1630]: kdeconnect.plugin.battery: No Primary Battery detected on this system. This may be a bug. Jul 4 21:25:16 imac51 org.kde.kdeconnect.daemon.desktop[1630]: kdeconnect.plugin.battery: Total quantity of batteries found: 0 Jul 4 21:25:16 imac51 org.kde.kdeconnect.daemon.desktop[1630]: discarding unsupported packet "kdeconnect.notification.request" for "pad" ``` -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 470322] When in Rectangular Region mode, ESC key should exit that mode and show the viewer window or "take new screenshot" window rather than quitting Spectacle
https://bugs.kde.org/show_bug.cgi?id=470322 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 470322] When in Rectangular Region mode, ESC key should exit that mode and show the viewer window or "take new screenshot" window rather than quitting Spectacle
https://bugs.kde.org/show_bug.cgi?id=470322 Nate Graham changed: What|Removed |Added Severity|normal |wishlist CC||n...@kde.org Resolution|NOT A BUG |--- Summary|Spectacle closes when |When in Rectangular Region |hitting the ESC key |mode, ESC key should exit ||that mode and show the ||viewer window or "take new ||screenshot" window rather ||than quitting Spectacle Status|RESOLVED|REPORTED --- Comment #7 from Nate Graham --- Re-titling and re-opening to reflect the request, which seems reasonable given that it's a behavioral change from the older version of Spectacle. Marking it as a wishlist though, as it's not technically a bug but rather a request to change the current design. But the request seems reasonable to me. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471955] Konsole crashed after replacing the file for the selected font
https://bugs.kde.org/show_bug.cgi?id=471955 --- Comment #1 from tcanabr...@kde.org --- The crash seems to happen inside of Qt, so it’s an upstream issue :/ On Tue, 4 Jul 2023 at 20:27 Ben Blank wrote: > https://bugs.kde.org/show_bug.cgi?id=471955 > > Bug ID: 471955 >Summary: Konsole crashed after replacing the file for the > selected font > Classification: Applications >Product: konsole >Version: 22.12.3 > Platform: Kubuntu > OS: Linux > Status: REPORTED > Keywords: drkonqi > Severity: crash > Priority: NOR > Component: general > Assignee: konsole-de...@kde.org > Reporter: ben.bl...@gmail.com > Target Milestone: --- > > Application: konsole (22.12.3) > > Qt Version: 5.15.8 > Frameworks Version: 5.104.0 > Operating System: Linux 6.2.0-24-generic x86_64 > Windowing System: X11 > Distribution: Ubuntu 23.04 > DrKonqi: 5.27.4 [KCrashBackend] > > -- Information about the crash: > I had two tabs open; the first was running Python through Bash, but I > hadn't > interacted with it in a bit. In the active tab, I had recently used Bash to > copy v0.050 of the JuliaMono TTF files into ~/.fonts/j/, replacing the > v0.045 > files already there. This was almost certainly a foolish thing to do, as > JuliaMono was the font selected in Konsole's settings for displaying the > terminal. > > The crash didn't happen right away; I moved some other files around via > Bash, > then switched to another application. Upon switching back to Konsole, I > attempted to run the command "man curl", at which point Konsole decided it > didn't like me any more. After relaunching Konsole, "man curl" runs just > fine > (unsurprisingly). > > While I have no evidence to support the conjecture, replacing in-use TTF > files > seems highly likely to cause problems. > > The crash does not seem to be reproducible. > > -- Backtrace: > Application: Konsole (konsole), signal: Segmentation fault > > [KCrash Handler] > #4 0x7fe16b3a95a0 in ?? () from /lib/x86_64-linux-gnu/libfreetype.so.6 > #5 0x7fe16b3a9688 in ?? () from /lib/x86_64-linux-gnu/libfreetype.so.6 > #6 0x7fe16b367c80 in FT_Get_Char_Index () from > /lib/x86_64-linux-gnu/libfreetype.so.6 > #7 0x7fe16955a2c6 in ?? () from > /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 > #8 0x7fe16fc17d77 in QFontEngineMulti::stringToCMap(QChar const*, int, > QGlyphLayout*, int*, QFlags) const () from > /lib/x86_64-linux-gnu/libQt5Gui.so.5 > #9 0x7fe16fc3a8a5 in QTextEngine::shapeText(int) const () from > /lib/x86_64-linux-gnu/libQt5Gui.so.5 > #10 0x7fe16fc4041b in QTextEngine::shapeLine(QScriptLine const&) () > from > /lib/x86_64-linux-gnu/libQt5Gui.so.5 > #11 0x7fe16fe227c8 in QPainter::drawText(QPointF const&, QString > const&, > int, int) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 > #12 0x7fe170db58a0 in ?? () from > /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 > #13 0x7fe170d5a91e in ?? () from > /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 > #14 0x7fe170d473d3 in > Konsole::TerminalDisplay::paintEvent(QPaintEvent*) () > from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 > #15 0x7fe1703aec28 in QWidget::event(QEvent*) () from > /lib/x86_64-linux-gnu/libQt5Widgets.so.5 > #16 0x7fe17036bf92 in QApplicationPrivate::notify_helper(QObject*, > QEvent*) > () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 > #17 0x7fe16f6bae38 in QCoreApplication::notifyInternal2(QObject*, > QEvent*) > () from /lib/x86_64-linux-gnu/libQt5Core.so.5 > #18 0x7fe1703a6e59 in QWidgetPrivate::sendPaintEvent(QRegion const&) () > from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 > #19 0x7fe1703a7751 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion > const&, QPoint const&, QFlags, QPainter*, > QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 > #20 0x7fe17037d421 in ?? () from > /lib/x86_64-linux-gnu/libQt5Widgets.so.5 > #21 0x7fe1703aeee8 in QWidget::event(QEvent*) () from > /lib/x86_64-linux-gnu/libQt5Widgets.so.5 > #22 0x7fe170c25e4d in KXmlGuiWindow::event(QEvent*) () from > /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 > #23 0x7fe17036bf92 in QApplicationPrivate::notify_helper(QObject*, > QEvent*) > () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 > #24 0x7fe16f6bae38 in QCoreApplication::notifyInternal2(QObject*, > QEvent*) > () from /lib/x86_64-linux-gnu/libQt5Core.so.5 > #25 0x7fe16f6bdea1 in > QCoreApplicationPrivate::sendPostedEvents(QObject*, > int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 > #26 0x7fe16f7157b7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 > #27 0x7fe16d9d249d in g_main_context_dispatch () from > /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #28 0x7fe16da2d178 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 > #29 0x7fe16d9d11b0 in g_main_context_iteration () from >
[gwenview] [Bug 471958] New: Gwenview crash at startup/didn't start and crahs with "free(): invalid pointer"
https://bugs.kde.org/show_bug.cgi?id=471958 Bug ID: 471958 Summary: Gwenview crash at startup/didn't start and crahs with "free(): invalid pointer" Classification: Applications Product: gwenview Version: 23.04.2 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: kde-...@schiermeier-it.de Target Milestone: --- Application: gwenview (23.04.2) Qt Version: 5.15.8 Frameworks Version: 5.107.0 Operating System: Linux 6.3.0-2-amd64 x86_64 Windowing System: X11 Distribution: Devuan GNU/Linux 6 (excalibur/ceres) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: So I tried to start it via Konsole and got this: user@Machine ~/Downloads % gwenview free(): invalid pointer KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = gwenview path = /usr/bin pid = 12884 KCrash: Arguments: /usr/bin/gwenview KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi zsh: suspended (signal) gwenview user@Machine ~/Downloads % The crash can be reproduced every time. -- Backtrace: Application: Gwenview (gwenview), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #5 0x7fbcb02a815f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #6 0x7fbcb025a472 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #7 0x7fbcb02444b2 in __GI_abort () at ./stdlib/abort.c:79 #8 0x7fbcb02451ed in __libc_message (fmt=fmt@entry=0x7fbcb03b778c "%s\n") at ../sysdeps/posix/libc_fatal.c:150 #9 0x7fbcb02b1a75 in malloc_printerr (str=str@entry=0x7fbcb03b522c "free(): invalid pointer") at ./malloc/malloc.c:5651 #10 0x7fbcb02b37f4 in _int_free (av=, p=, have_lock=have_lock@entry=0) at ./malloc/malloc.c:4425 #11 0x7fbcb02b616f in __GI___libc_free (mem=) at ./malloc/malloc.c:3367 #12 0x7fbcae2d9792 in LibRaw::~LibRaw() () from /lib/x86_64-linux-gnu/libraw.so.23 #13 0x7fbcae2d97e9 in LibRaw::~LibRaw() () from /lib/x86_64-linux-gnu/libraw.so.23 #14 0x7fbca07b96ea in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/kimg_raw.so #15 0x7fbca07b990c in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/kimg_raw.so #16 0x7fbcb0fa9f94 in ?? () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #17 0x7fbcb0faaf86 in ?? () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #18 0x7fbcb0faba6c in QImageReader::canRead() const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #19 0x7fbcb2511cd2 in ?? () from /lib/x86_64-linux-gnu/libKF5IconThemes.so.5 #20 0x7fbcb2512bc7 in KIconLoader::loadScaledIcon(QString const&, KIconLoader::Group, double, QSize const&, int, QStringList const&, QString*, bool, std::optional const&) const () from /lib/x86_64-linux-gnu/libKF5IconThemes.so.5 #21 0x7fbcb2508253 in KIconEngine::createPixmap(QSize const&, double, QIcon::Mode, QIcon::State) () from /lib/x86_64-linux-gnu/libKF5IconThemes.so.5 #22 0x7fbcb2508675 in KIconEngine::pixmap(QSize const&, QIcon::Mode, QIcon::State) () from /lib/x86_64-linux-gnu/libKF5IconThemes.so.5 #23 0x7fbcb0fccbc4 in QIcon::pixmap(QWindow*, QSize const&, QIcon::Mode, QIcon::State) const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #24 0x7fbcb0fe in QIcon::pixmap(QSize const&, QIcon::Mode, QIcon::State) const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #25 0x560cab208b8d in ?? () #26 0x560cab20770d in ?? () #27 0x560cab1ff43b in ?? () #28 0x560cab1fda56 in ?? () #29 0x560cab1f450e in ?? () #30 0x560cab1c757d in ?? () #31 0x7fbcb02456ca in __libc_start_call_main (main=main@entry=0x560cab1c7070, argc=argc@entry=1, argv=argv@entry=0x7fffa472eea8) at ../sysdeps/nptl/libc_start_call_main.h:58 #32 0x7fbcb0245785 in __libc_start_main_impl (main=0x560cab1c7070, argc=1, argv=0x7fffa472eea8, init=, fini=, rtld_fini=, stack_end=0x7fffa472ee98) at ../csu/libc-start.c:360 #33 0x560cab1c76c1 in ?? () [Inferior 1 (process 12392) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470789] Firefox flickers in Plasma Wayland session
https://bugs.kde.org/show_bug.cgi?id=470789 wescode changed: What|Removed |Added CC||whic...@gmail.com --- Comment #9 from wescode --- (In reply to Lassi Väätämöinen from comment #3) > (In reply to Lassi Väätämöinen from comment #2) > > https://bugs.kde.org/show_bug.cgi?id=424586 > > > > Seems to be particular issue to Firefox. I had to go to Chrome for now. > > Also, eventually Firefox window contents stop updating, but when clicking > around the tabs, the window title changes, so the actual UI events are > passed, but the window contents is not updating. > > When attempting closing Firefox, it ends up to "Not responding" grey window > view. This is what I am experiencing, but I do not get any type of flicker. I haven't been able to reproduce the error yet, it seems random. Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.11-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon Graphics 7900XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C84 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 471908] sudo pkcon update fatal error: unmet dependencies - libkf5purpose-bin
https://bugs.kde.org/show_bug.cgi?id=471908 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 471908] sudo pkcon update fatal error: unmet dependencies - libkf5purpose-bin
https://bugs.kde.org/show_bug.cgi?id=471908 --- Comment #4 from Moltke --- By the way, forgot to mention I use KDE Neon Testing: Operating System: KDE neon Testing Edition KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.1.34-060134-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 471908] sudo pkcon update fatal error: unmet dependencies - libkf5purpose-bin
https://bugs.kde.org/show_bug.cgi?id=471908 Moltke changed: What|Removed |Added CC||amel_anc...@hotmail.com --- Comment #3 from Moltke --- I've been having this like for a week now. Updating via "pkcon" doesn't work, but "apt full-upgrade" does, however, these pkgs are held thus not updated: libkf5purpose-bin libkf5purpose5 qml-module-org-kde-purpose. I tried installing them, but apt complains about "libaccounts-qt not going to be installed" like Jonathan Riddell's comment suggests. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 387920] [RFE] Implement network priority using the main network list, via drag-and-drop
https://bugs.kde.org/show_bug.cgi?id=387920 m.w...@web.de changed: What|Removed |Added Version|5.17.4 |5.27.6 Platform|Ubuntu |Neon --- Comment #10 from m.w...@web.de --- I wonder if it would be possible to fix/ implement this for KDE/Plasma 6? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384782] Allow manually re-ordering tray icons
https://bugs.kde.org/show_bug.cgi?id=384782 pallaswept changed: What|Removed |Added CC||pallasw...@proton.me --- Comment #36 from pallaswept --- During the 6 years of this case being open there has been lots of positive discussion regarding design, I would like to shift the focus of discussion to project management. While the invitation for a volunteer to provide a solution has kindly been made, that approach is obviously ineffective. At some point, somebody with appropriate authority, needs to delegate this task to an appropriate developer, to begin implementation. Let's talk about how to make that happen? I unfortunately feel that I'd be the perhaps the least appropriate developer, given that I have little and aged experience with the toolchains in use, and I've long ago moved from development to management of development teams, but I'm not one to shirk responsibility, so if you must delegate it to me, do that, but please, let's put it in *somebody*'s to-do list. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470604] Desktop icon positions and pinned Task Manager apps reset when plasmashell is stopped/started or restarted using systemctl
https://bugs.kde.org/show_bug.cgi?id=470604 Nicolas Fella changed: What|Removed |Added CC||publiclyvisibleemail@gmail. ||com --- Comment #5 from Nicolas Fella --- *** Bug 471949 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 471949] (Classic) Task Manager - Unpinned applications keep re-showing after reboot
https://bugs.kde.org/show_bug.cgi?id=471949 Nicolas Fella changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 470604 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471950] Distorted windows contents on recovering from sleep / hibernate
https://bugs.kde.org/show_bug.cgi?id=471950 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Summary|Plasma 6 X11 - Distorted|Distorted windows contents |windows contents on |on recovering from sleep / |recovering from sleep / |hibernate |hibernate | -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471951] Can't clear Clipboard
https://bugs.kde.org/show_bug.cgi?id=471951 Nicolas Fella changed: What|Removed |Added Summary|Plasma 6 X11 - Can't clear |Can't clear Clipboard |Clipboard | CC||nicolas.fe...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 471949] (Classic) Task Manager - Unpinned applications keep re-showing after reboot
https://bugs.kde.org/show_bug.cgi?id=471949 Nicolas Fella changed: What|Removed |Added Summary|Plasma 6 X11 - (Classic)|(Classic) Task Manager - |Task Manager - Unpinned |Unpinned applications keep |applications keep |re-showing after reboot |re-showing after reboot | CC||nicolas.fe...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471957] New: Apply button is not in the tab order
https://bugs.kde.org/show_bug.cgi?id=471957 Bug ID: 471957 Summary: Apply button is not in the tab order Classification: Applications Product: systemsettings Version: 5.27.6 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: jonzn4s...@hotmail.com CC: natalie_clar...@yahoo.de Target Milestone: --- SUMMARY When tabbing through the Touchpad page in System Settings, the Apply button in not part of the tab order. After tabbing to Device enabled and hitting the space bar, I wanted to tab down to the Apply button to enable the Touchpad, but tab focus just goes back to the top option Device enabled. STEPS TO REPRODUCE 1. Go to System Settings >>> Input Devices >>> Touchpad 2. Then check the box for Device enabled 3. Using the Tab key, try to tab down the Apply button, but the button is not part of the tab order. It just back to the top option Device enabled. OBSERVED RESULT The Apply button is not in the tab order EXPECTED RESULT Should've been able the Apply button using the tab key Operating System: openSUSE Tumbleweed 20230629 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.9-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5825U with Radeon Graphics Memory: 62.1 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP ProBook 455 15.6 inch G9 Notebook PC ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 471949] Plasma 6 X11 - (Classic) Task Manager - Unpinned applications keep re-showing after reboot
https://bugs.kde.org/show_bug.cgi?id=471949 --- Comment #1 from publiclyvisibleem...@gmail.com --- And now the unpinned applications are finally gone, with a fourth or fifth reboot. *shrug* -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471917] kdenlive does not start after flatpak update
https://bugs.kde.org/show_bug.cgi?id=471917 --- Comment #1 from Didier Peyret --- ... from 24.04.01, not from 24.03.01.Sorry -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471956] New: File paths containing whitespace not working with proxy generation
https://bugs.kde.org/show_bug.cgi?id=471956 Bug ID: 471956 Summary: File paths containing whitespace not working with proxy generation Classification: Applications Product: kdenlive Version: 23.04.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: ad...@arkades.org Target Milestone: --- 1. Make a project directory with whitespace in it 2. Save a project file to it 3. Add a clip from within this project directory 4. Enable proxy clip Kdenlive throws an error about non-existing directory -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443723] "Display geometry when moving or resizing" feature is missing
https://bugs.kde.org/show_bug.cgi?id=443723 Kevin Chadwick changed: What|Removed |Added CC||kc-...@chadwicks.me.uk --- Comment #23 from Kevin Chadwick --- I found this vefy usegul for developing guis whether desktop, websites or flutter. Reactive guis change behaviour upon width chsngesanf it is nice to hsve that information reactively. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kemoticons] [Bug 363215] reduce amount of default emoticons
https://bugs.kde.org/show_bug.cgi?id=363215 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #1 from Christoph Cullmann --- KEmoticons is removed for kf6. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471955] New: Konsole crashed after replacing the file for the selected font
https://bugs.kde.org/show_bug.cgi?id=471955 Bug ID: 471955 Summary: Konsole crashed after replacing the file for the selected font Classification: Applications Product: konsole Version: 22.12.3 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: ben.bl...@gmail.com Target Milestone: --- Application: konsole (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.0-24-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.04 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: I had two tabs open; the first was running Python through Bash, but I hadn't interacted with it in a bit. In the active tab, I had recently used Bash to copy v0.050 of the JuliaMono TTF files into ~/.fonts/j/, replacing the v0.045 files already there. This was almost certainly a foolish thing to do, as JuliaMono was the font selected in Konsole's settings for displaying the terminal. The crash didn't happen right away; I moved some other files around via Bash, then switched to another application. Upon switching back to Konsole, I attempted to run the command "man curl", at which point Konsole decided it didn't like me any more. After relaunching Konsole, "man curl" runs just fine (unsurprisingly). While I have no evidence to support the conjecture, replacing in-use TTF files seems highly likely to cause problems. The crash does not seem to be reproducible. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault [KCrash Handler] #4 0x7fe16b3a95a0 in ?? () from /lib/x86_64-linux-gnu/libfreetype.so.6 #5 0x7fe16b3a9688 in ?? () from /lib/x86_64-linux-gnu/libfreetype.so.6 #6 0x7fe16b367c80 in FT_Get_Char_Index () from /lib/x86_64-linux-gnu/libfreetype.so.6 #7 0x7fe16955a2c6 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #8 0x7fe16fc17d77 in QFontEngineMulti::stringToCMap(QChar const*, int, QGlyphLayout*, int*, QFlags) const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #9 0x7fe16fc3a8a5 in QTextEngine::shapeText(int) const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #10 0x7fe16fc4041b in QTextEngine::shapeLine(QScriptLine const&) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x7fe16fe227c8 in QPainter::drawText(QPointF const&, QString const&, int, int) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7fe170db58a0 in ?? () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #13 0x7fe170d5a91e in ?? () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #14 0x7fe170d473d3 in Konsole::TerminalDisplay::paintEvent(QPaintEvent*) () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #15 0x7fe1703aec28 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7fe17036bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7fe16f6bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fe1703a6e59 in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fe1703a7751 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7fe17037d421 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7fe1703aeee8 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7fe170c25e4d in KXmlGuiWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #23 0x7fe17036bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7fe16f6bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7fe16f6bdea1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7fe16f7157b7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fe16d9d249d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7fe16da2d178 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7fe16d9d11b0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7fe16f714e7a in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7fe16f6b97cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fe16f6c1c1a in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x55771231c7c1 in ?? () #34 0x7fe16ec23a90 in __libc_start_call_main
[Discover] [Bug 471894] Offline Updates Does Not Check Polkit Correctly On Remote Systems
https://bugs.kde.org/show_bug.cgi?id=471894 --- Comment #1 from Noorez --- This issue appears to extend to reboot and shutdown as well. Instead of the expected authentication prompt, the screen simply goes blank and does not provide any other feedback. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471954] "Verschieben und Größe ändern" effect flutters, without keyframe at the end
https://bugs.kde.org/show_bug.cgi?id=471954 --- Comment #1 from fehler-im-progr...@posteo.de --- Created attachment 160080 --> https://bugs.kde.org/attachment.cgi?id=160080=edit test1.png -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471954] New: "Verschieben und Größe ändern" effect flutters, without keyframe at the end
https://bugs.kde.org/show_bug.cgi?id=471954 Bug ID: 471954 Summary: "Verschieben und Größe ändern" effect flutters, without keyframe at the end Classification: Applications Product: kdenlive Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: fehler-im-progr...@posteo.de Target Milestone: --- Created attachment 160079 --> https://bugs.kde.org/attachment.cgi?id=160079=edit Bug 'Verschieben & Größe ändern'.kdenlive STEPS TO REPRODUCE See attachment "Bug 'Verschieben & Größe ändern'.kdenlive" OBSERVED RESULT effect flutters, without keyframe at the end EXPECTED RESULT no flutter. Effect must stay at 100.00% at frame 30. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471934] "Remove face region" from Ignored sends it to Unknown
https://bugs.kde.org/show_bug.cgi?id=471934 Maik Qualmann changed: What|Removed |Added Version Fixed In||8.2.0 Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/digikam/-/commit/329f8 ||28a36b5c528d472550ab8a89f8a ||1feafdff Resolution|--- |FIXED --- Comment #1 from Maik Qualmann --- Git commit 329f828a36b5c528d472550ab8a89f8a1feafdff by Maik Qualmann. Committed on 04/07/2023 at 17:56. Pushed by mqualmann into branch 'master'. remove face when rejecting an ignored face FIXED-IN: 8.2.0 M +2-1NEWS M +7-1core/app/items/views/digikamitemview.cpp https://invent.kde.org/graphics/digikam/-/commit/329f828a36b5c528d472550ab8a89f8a1feafdff -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471517] Whole-screen diagonal-stripes glitch on external display with hybrid graphics
https://bugs.kde.org/show_bug.cgi?id=471517 Zamundaaa changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/e698cafa27 ||37904255d47d1e1710ee857cde9 ||afd --- Comment #12 from Zamundaaa --- Git commit e698cafa2737904255d47d1e1710ee857cde9afd by Xaver Hugl. Committed on 04/07/2023 at 15:33. Pushed by zamundaaa into branch 'master'. backends/drm: handle mismatching stride with CPU copying M +12 -12 src/backends/drm/drm_egl_layer_surface.cpp https://invent.kde.org/plasma/kwin/-/commit/e698cafa2737904255d47d1e1710ee857cde9afd -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471951] Plasma 6 X11 - Can't clear Clipboard
https://bugs.kde.org/show_bug.cgi?id=471951 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 471952] kscreenlocker_greet crashes when qmlcache is corrupted
https://bugs.kde.org/show_bug.cgi?id=471952 Bug Janitor Service changed: What|Removed |Added Severity|minor |crash -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 471953] New: Gwenview crashed while scrolling through images
https://bugs.kde.org/show_bug.cgi?id=471953 Bug ID: 471953 Summary: Gwenview crashed while scrolling through images Classification: Applications Product: gwenview Version: 22.12.3 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: rodene...@gmail.com Target Milestone: --- Application: gwenview (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.0-24-generic x86_64 Windowing System: Wayland Distribution: Ubuntu 23.04 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: I have a folder with many (hundreds) of images that I was scrolling but Gwenview crashed unexpectedly while doing so. I had Gwenview opened for a long time before this happened (3 days and 9 hrs) while working on a project. The files are mostly png plots. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Gwenview (gwenview), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7fcdb603c406 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7fcdb602287c in __GI_abort () at ./stdlib/abort.c:79 #9 0x7fcdb60235a4 in __libc_message (fmt=fmt@entry=0x7fcdb61b86c6 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:150 #10 0x7fcdb612ec1b in __GI___fortify_fail (msg=msg@entry=0x7fcdb61b86ae "stack smashing detected") at ./debug/fortify_fail.c:24 #11 0x7fcdb612ebf6 in __stack_chk_fail () at ./debug/stack_chk_fail.c:24 #12 0x7fcdb74f5060 in cmsBuildParametricToneCurve () from /lib/x86_64-linux-gnu/liblcms2.so.2 #13 0x7fcdb7512935 in cmsCreate_sRGBProfileTHR () from /lib/x86_64-linux-gnu/liblcms2.so.2 #14 0x7fcdb8e4b31f in Gwenview::Cms::Profile::getSRgbProfile() () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5 #15 0x7fcdb8e7cb19 in ?? () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5 #16 0x7fcdb7ab6921 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7fcdb7ab717a in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fcdb7ab6673 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fcdb7ab717a in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7fcdb7ab6673 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7fcdb7a7a5d4 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7fcdb7b223f8 in QGraphicsEffectSource::draw(QPainter*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7fcdb7ab7573 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7fcdb7ab7ba2 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7fcdb7adc277 in QGraphicsView::paintEvent(QPaintEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7fcdb77aec28 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7fcdb785b792 in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7fcdb6ababa3 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fcdb776bf82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fcdb6abae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7fcdb77a6e59 in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x7fcdb77a7751 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x7fcdb777d421 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #34 0x7fcdb77aeee8 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #35 0x7fcdb85e7e4d in KXmlGuiWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #36 0x7fcdb776bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #37 0x7fcdb6abae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #38 0x7fcdb6abdea1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #39 0x7fcdb7aa9193 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #40 0x7fcdb6ae7de0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #41 0x7fcdb776bf92 in QApplicationPrivate::notify_helper(QObject*,
[kscreenlocker] [Bug 471952] New: kscreenlocker_greet crashes when qmlcache is corrupted
https://bugs.kde.org/show_bug.cgi?id=471952 Bug ID: 471952 Summary: kscreenlocker_greet crashes when qmlcache is corrupted Classification: Plasma Product: kscreenlocker Version: 5.27.6 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: l.fuerde...@gmail.com Target Milestone: --- Created attachment 160078 --> https://bugs.kde.org/attachment.cgi?id=160078=edit The lockscreen as I see it when kscreenlocker_greet crashes SUMMARY When I lock my screen, I see an error message telling me how to unlock my screen again using a console. It looks like I corrupted my qmlcache that kscreenlocker_greet uses. The file ~/.cache/kscreenlocker_greet/qmlcache/5c5649af53bb78a2255cc07dba00b5d037690788.qmlc is truncated to 12288 bytes on my system (which is exactly 12 KiB). When I remove the file, it will be regenerated with a size of 16068 bytes and the screen lock works as expected. I can only speculate, how this file corruption happened. In my opinion, the most likely explanation is a "full disk" that caused the file not to be written to the end. After this "incident" the file stayed corrupted until I manually deleted it. STEPS TO REPRODUCE 1. Make sure, the screen was locked at least once before, so that the following file exists. 2. truncate -s 12288 ~/.cache/kscreenlocker_greet/qmlcache/5c5649af53bb78a2255cc07dba00b5d037690788.qmlc 3. Lock the screen. OBSERVED RESULT A black screen with white text that cannot be unlocked graphically. It gives me instructions, how to unlock using the console. (See attached screenshot) EXPECTED RESULT When a cache file was not completely written to disk before, I would expect that it is not used the next time but regenerated instead. The screen should be able to lock as normal. SOFTWARE/OS VERSIONS Linux-Kernel: 6.4.1 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION The following messages appear in the journal log: Jul 04 18:09:50 lukas kcminit[20142]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_mouse.so" Jul 04 18:09:50 lukas kcminit[20142]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_touchpad.so" Jul 04 18:09:50 lukas kcminit[20142]: kcm_touchpad: Using X11 backend Jul 04 18:09:51 lukas kscreenlocker_greet[20147]: Qt: Session management error: networkIdsList argument is NULL Jul 04 18:09:51 lukas kernel: QQmlThread[20165]: segfault at 7f87b2296b24 ip 7f875fc1f781 sp 7f873cff7580 error 4 in libQt5Qml.so.5.15.10[7f875faa7000+281000] likely on CPU 5 (core 1, socket 0) Jul 04 18:09:51 lukas kernel: Code: c0 0f 84 62 02 00 00 4c 8d 3c 40 31 db 49 c1 e7 02 0f 1f 84 00 00 00 00 00 41 8b 45 44 48 89 ef 48 01 d8 48 83 c3 0c 4c 01 e8 <8b> 70 04 48 8d 50 08 e8 d3 c5 ff ff 4c 39 fb 75 de 66 41 83 7d 48 Jul 04 18:09:51 lukas kscreenlocker_greet[20166]: Qt: Session management error: networkIdsList argument is NULL Jul 04 18:09:51 lukas kernel: QQmlThread[20180]: segfault at 7fe77dff8007 ip 7fe71841f781 sp 7fe6f4ff7580 error 4 in libQt5Qml.so.5.15.10[7fe7182a7000+281000] likely on CPU 4 (core 0, socket 0) Jul 04 18:09:51 lukas kernel: Code: c0 0f 84 62 02 00 00 4c 8d 3c 40 31 db 49 c1 e7 02 0f 1f 84 00 00 00 00 00 41 8b 45 44 48 89 ef 48 01 d8 48 83 c3 0c 4c 01 e8 <8b> 70 04 48 8d 50 08 e8 d3 c5 ff ff 4c 39 fb 75 de 66 41 83 7d 48 Jul 04 18:09:51 lukas kscreenlocker_greet[20181]: Qt: Session management error: networkIdsList argument is NULL Jul 04 18:09:51 lukas kernel: QQmlThread[20195]: segfault at 7f8faf415007 ip 7f8f4e81f781 sp 7f8f2cd6d580 error 4 in libQt5Qml.so.5.15.10[7f8f4e6a7000+281000] likely on CPU 3 (core 3, socket 0) Jul 04 18:09:51 lukas kernel: Code: c0 0f 84 62 02 00 00 4c 8d 3c 40 31 db 49 c1 e7 02 0f 1f 84 00 00 00 00 00 41 8b 45 44 48 89 ef 48 01 d8 48 83 c3 0c 4c 01 e8 <8b> 70 04 48 8d 50 08 e8 d3 c5 ff ff 4c 39 fb 75 de 66 41 83 7d 48 Jul 04 18:09:51 lukas kscreenlocker_greet[20196]: Qt: Session management error: networkIdsList argument is NULL Jul 04 18:09:51 lukas kernel: QQmlThread[20210]: segfault at 7f46db59cb24 ip 7f467821f781 sp 7f4655ff9580 error 4 in libQt5Qml.so.5.15.10[7f46780a7000+281000] likely on CPU 2 (core 2, socket 0) Jul 04 18:09:51 lukas kernel: Code: c0 0f 84 62 02 00 00 4c 8d 3c 40 31 db 49 c1 e7 02 0f 1f 84 00 00 00 00 00 41 8b 45 44 48 89 ef 48 01 d8 48 83 c3 0c 4c 01 e8 <8b> 70 04 48 8d 50 08 e8 d3 c5 ff ff 4c 39 fb 75 de 66 41 83 7d 48 -- You are receiving this mail because: You are watching all bug changes.
