[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.
[plasmashell] [Bug 470573] New: cannot select items with selection rectangle on desktop in folder view
https://bugs.kde.org/show_bug.cgi?id=470573 Bug ID: 470573 Summary: cannot select items with selection rectangle on desktop in folder view Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: justin.zo...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. Use folder view for desktop 2. Try and select any files on the desktop with a selection box with the mouse OBSERVED RESULT Blue rectangle is drawn but no files inside the box are selected EXPECTED RESULT Files are selected Git master Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.5.1 Kernel Version: 6.4.0-0.rc4.20230529gite338142b39cf.35.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 31.0 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 470572] New: double clicking on the empty area next to tabs no longer opens a new tab
https://bugs.kde.org/show_bug.cgi?id=470572 Bug ID: 470572 Summary: double clicking on the empty area next to tabs no longer opens a new tab Classification: Applications Product: konsole Version: master Platform: Other OS: Linux Status: REPORTED Keywords: qt6, regression Severity: normal Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: justin.zo...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Have tab bar shown 2. Double click to open a new tab on an empty area on the tab bar OBSERVED RESULT Nothing EXPECTED RESULT New tab Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.5.1 Kernel Version: 6.4.0-0.rc4.20230529gite338142b39cf.35.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 31.0 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470280] Color scheme doesn't change after applying accent color from bw wallpaper
https://bugs.kde.org/show_bug.cgi?id=470280 --- Comment #7 from Fushan Wen --- Git commit 7695386070f6c3c61ac3b95c2234566ef0f5301b by Fushan Wen. Committed on 03/06/2023 at 05:11. Pushed by fusionfuture into branch 'master'. Desktop: set accentColor binding enabled condition Without this, accentColor may still be updated after usedInAccentColor becomes false. (cherry picked from commit cd05ae276c5fb95b129ffd1b2bf651549afe5a48) M +1-0desktoppackage/contents/views/Desktop.qml https://invent.kde.org/plasma/plasma-desktop/-/commit/7695386070f6c3c61ac3b95c2234566ef0f5301b -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470280] Color scheme doesn't change after applying accent color from bw wallpaper
https://bugs.kde.org/show_bug.cgi?id=470280 --- Comment #6 from Fushan Wen --- Git commit cd05ae276c5fb95b129ffd1b2bf651549afe5a48 by Fushan Wen. Committed on 03/06/2023 at 05:08. Pushed by fusionfuture into branch 'Plasma/5.27'. Desktop: set accentColor binding enabled condition Without this, accentColor may still be updated after usedInAccentColor becomes false. M +1-0desktoppackage/contents/views/Desktop.qml https://invent.kde.org/plasma/plasma-desktop/-/commit/cd05ae276c5fb95b129ffd1b2bf651549afe5a48 -- 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 470280] Color scheme doesn't change after applying accent color from bw wallpaper
https://bugs.kde.org/show_bug.cgi?id=470280 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2970 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470571] New: I can't save any artwork I have done on Krita. Whenever I try to save it, a message shows up saying: ''Cannot open file for writing. Reason: The file could not be opened''
https://bugs.kde.org/show_bug.cgi?id=470571 Bug ID: 470571 Summary: I can't save any artwork I have done on Krita. Whenever I try to save it, a message shows up saying: ''Cannot open file for writing. Reason: The file could not be opened'' Classification: Applications Product: krita Version: 5.1.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: grave Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: viniciusabadco...@gmail.com Target Milestone: --- Created attachment 159423 --> https://bugs.kde.org/attachment.cgi?id=159423=edit message that shows up whenever I try to save SUMMARY Doesn't matter what I do, I can't save any artwork I have done on Krita. Whenever I try to save it, a message shows up saying: ''Cannot open file for writing. Reason: The file could not be opened''. I tried to change some things on the properties, but nothing seems to work. SOFTWARE/OS VERSIONS Windows: 10 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470570] New: After dragging an item from dolphin to the desktop the plus symbol remains on the cursor in dolphin
https://bugs.kde.org/show_bug.cgi?id=470570 Bug ID: 470570 Summary: After dragging an item from dolphin to the desktop the plus symbol remains on the cursor in dolphin Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: justin.zo...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Drag and drop (copy or other action) an item from dolphin onto the desktop 2. Move cursor back to Dolphin 3. Notice green circle with plus (drag and drop cursor) in dolhpin contents window Can't attach screenshot as the cursor goes back to normal once spectacle is taking the screenshot. Git master build Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.5.1 Kernel Version: 6.4.0-0.rc4.20230529gite338142b39cf.35.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 31.0 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 470345] Configuring toolbars in KF6-ported apps fails
https://bugs.kde.org/show_bug.cgi?id=470345 Justin Zobel changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||justin.zo...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Justin Zobel --- Can confirm both issues, lack of configure in right-click and no change to the toolbar apart from flicker when configuring via the hamburger menu. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470216] latte does not build on KDE neon unstable (Qt 6 Preview)
https://bugs.kde.org/show_bug.cgi?id=470216 Justin Zobel changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||justin.zo...@gmail.com --- Comment #1 from Justin Zobel --- Install plasma-workspace-devel or whatever that package is called on Neon. If this works please let me know and I will send a Merge Request to the INSTALLATION.md file to include it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470528] "Choose Style…" button in configuration dialog does nothing when clicked in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=470528 Justin Zobel changed: What|Removed |Added CC||justin.zo...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Justin Zobel --- Can confirm I can reproduce this issue as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470357] "Appearance" section in the settings of System Monitor widgets is empty
https://bugs.kde.org/show_bug.cgi?id=470357 Justin Zobel changed: What|Removed |Added CC||justin.zo...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Justin Zobel --- Can confirm. Possibly relevant log entries: qrc:/usr/share/ksysguard/sensorfaces/org.kde.ksysguard.piechart/contents/ui/Config.qml: No such file or directory kf.kirigami: Failed to find a Kirigami platform plugin "qrc:/ConfigAppearance.qml:15:1: module \"org.kde.kconfig\" is not installed" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470358] Widget Explorer without icons
https://bugs.kde.org/show_bug.cgi?id=470358 Justin Zobel changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||justin.zo...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Justin Zobel --- Can also confirm. Had to launch from panel as launching from the desktop wouldn't work for me, separate issue though. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470355] "Pause indexer" button is present and active even when baloo is disabled
https://bugs.kde.org/show_bug.cgi?id=470355 Justin Zobel changed: What|Removed |Added CC||justin.zo...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Justin Zobel --- Confirmed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442321] Task manager sometimes opens new instance of an already-running app on left click when using wayland
https://bugs.kde.org/show_bug.cgi?id=442321 Anubhab Ghosh changed: What|Removed |Added CC||anubhabghosh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 469356] KMail crashed while configuring email account
https://bugs.kde.org/show_bug.cgi?id=469356 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |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.
[kolourpaint] [Bug 469369] Can't open images from SSD
https://bugs.kde.org/show_bug.cgi?id=469369 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.
[NeoChat] [Bug 462348] Crash when click Open Externally if image is not loaded
https://bugs.kde.org/show_bug.cgi?id=462348 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[kdevelop] [Bug 469938] crash every time I try to change Config -> Format source -> Artistic style
https://bugs.kde.org/show_bug.cgi?id=469938 --- Comment #5 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.
[plasmashell] [Bug 469946] When I move my cursor over a text or any other place where I have to write to text, this bug is triggered. It changes default look of the cursor to the way it looks over a t
https://bugs.kde.org/show_bug.cgi?id=469946 --- 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.
[frameworks-plasma] [Bug 470379] Adding icon applet to containment has wrong name/icon
https://bugs.kde.org/show_bug.cgi?id=470379 Justin Zobel changed: What|Removed |Added CC||justin.zo...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Justin Zobel --- I can't reproduce this on the latest builds. I dropped an image and a text file on the desktop, used Add Icon and both were created using the correct name and icon. Can you confirm it's fixed? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469989] Screen recording doesn't work
https://bugs.kde.org/show_bug.cgi?id=469989 Justin Zobel changed: What|Removed |Added CC||justin.zo...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Justin Zobel --- Can also confirm. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470364] Cannot open images (.jpg, .png) located on desktop with double-click
https://bugs.kde.org/show_bug.cgi?id=470364 Justin Zobel changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||justin.zo...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #1 from Justin Zobel --- I am unable to reproduce this on my builds done from today/yesterday. A .jpg file opens with the image viewer of choice. Can you please test? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470569] New: Dolphin crashes when closing a split
https://bugs.kde.org/show_bug.cgi?id=470569 Bug ID: 470569 Summary: Dolphin crashes when closing a split Classification: Applications Product: dolphin Version: 23.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: tholpsem...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (23.04.1) Qt Version: 5.15.9 Frameworks Version: 5.106.0 Operating System: Linux 6.3.4-201.fc38.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 38 (KDE Plasma) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: Has started to happen frequently since this morning (June 2, 2023) The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7fd68abb3bcc in UpdateItemStatesThread::run() () from /lib64/libdolphinprivate.so.5 #6 0x7fd6886f556d in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7fd6880ae907 in start_thread () from /lib64/libc.so.6 #8 0x7fd688134870 in clone3 () from /lib64/libc.so.6 Thread 10 (Thread 0x7fd64f7fe6c0 (LWP 119696) "QThread"): #1 0x7ffc2c4599b0 in clock_gettime () #2 0x7fd6880f82fd in clock_gettime@GLIBC_2.2.5 () from /lib64/libc.so.6 #3 0x7fd686912f7b in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #4 0x7fd686971211 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #5 0x7fd686910a23 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #6 0x7fd688906936 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7fd6888b270b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #8 0x7fd6886f4160 in QThread::exec() () from /lib64/libQt5Core.so.5 #9 0x7fd6886f556d in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #10 0x7fd6880ae907 in start_thread () from /lib64/libc.so.6 #11 0x7fd688134870 in clone3 () from /lib64/libc.so.6 Thread 9 (Thread 0x7fd646c0 (LWP 119695) "dolphin"): #1 0x7fd685d060cc in usbmuxd_listen_inotify () from /lib64/libusbmuxd-2.0.so.6 #2 0x7fd685d06dc2 in device_monitor () from /lib64/libusbmuxd-2.0.so.6 #3 0x7fd6880ae907 in start_thread () from /lib64/libc.so.6 #4 0x7fd688134870 in clone3 () from /lib64/libc.so.6 Thread 8 (Thread 0x7fd65d1fc6c0 (LWP 119690) "dolphin:shlo0"): #1 0x7fd6880adb79 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7fd66611443d in cnd_wait () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fd6660c3c7b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #4 0x7fd66611436c in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #5 0x7fd6880ae907 in start_thread () from /lib64/libc.so.6 #6 0x7fd688134870 in clone3 () from /lib64/libc.so.6 Thread 7 (Thread 0x7fd65d9fd6c0 (LWP 119689) "dolphin:sh0"): #1 0x7fd6880adb79 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7fd66611443d in cnd_wait () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fd6660c3c7b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #4 0x7fd66611436c in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #5 0x7fd6880ae907 in start_thread () from /lib64/libc.so.6 #6 0x7fd688134870 in clone3 () from /lib64/libc.so.6 Thread 6 (Thread 0x7fd65e1fe6c0 (LWP 119688) "dolphin:disk$0"): #1 0x7fd6880adb79 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7fd66611443d in cnd_wait () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fd6660c3c7b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #4 0x7fd66611436c in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #5 0x7fd6880ae907 in start_thread () from /lib64/libc.so.6 #6 0x7fd688134870 in clone3 () from /lib64/libc.so.6 Thread 5 (Thread 0x7fd65e9ff6c0 (LWP 119687) "dolphin:cs0"): #1 0x7fd6880adb79 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7fd66611443d in cnd_wait () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fd6660c3c7b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #4 0x7fd66611436c in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #5 0x7fd6880ae907 in start_thread () from /lib64/libc.so.6 #6 0x7fd688134870 in clone3 () from /lib64/libc.so.6 Thread 4 (Thread 0x7fd674c4b6c0 (LWP 119686) "WaylandEventThr"): #1 0x7fd685f26c6c in QtWaylandClient::EventThread::run() () from /lib64/libQt5WaylandClient.so.5 #2 0x7fd6886f556d in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #3 0x7fd6880ae907 in start_thread () from /lib64/libc.so.6 #4 0x7fd688134870 in clone3 ()
[kde] [Bug 470568] New: plasma-remotecontrollers causes "duplicate" inputs in games
https://bugs.kde.org/show_bug.cgi?id=470568 Bug ID: 470568 Summary: plasma-remotecontrollers causes "duplicate" inputs in games Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: evanpbis...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Start Plasma Bigscreen 2. Connect game controller 3. Open an application with controller support (eg. Steam Big Picture) OBSERVED RESULT plasma-remotecontrollers takes effect on non-plasma applications EXPECTED RESULT plasma-remotecontrollers only affects the "desktop" and settings apps. SOFTWARE/OS VERSIONS Linux: 6.1.31-1-lts KDE Plasma: 5.27.5-1 KDE Frameworks Version: Qt Version: 5.15.9+kde+r155-1 -- 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 465712] After upgrade to 5.27, periodic visual glitches when monitors' refresh rates don't match
https://bugs.kde.org/show_bug.cgi?id=465712 Nate Graham changed: What|Removed |Added Priority|VHI |HI -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 460523] Categories in Widget Explorer are not translated after updating to the latest Framework
https://bugs.kde.org/show_bug.cgi?id=460523 Nate Graham changed: What|Removed |Added Version Fixed In||5.27.6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406101] Window "Keep above" overrides "Show Desktop"
https://bugs.kde.org/show_bug.cgi?id=406101 Nate Graham changed: What|Removed |Added Version Fixed In|5.16.0 |6.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470531] [Android] SDLAudioManager crash
https://bugs.kde.org/show_bug.cgi?id=470531 sh_zam changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit|2ceec081587284d7d5eae5d5039 |https://invent.kde.org/grap |4084a111a21ff |hics/krita/-/commit/42b82a8 ||fc87d3f049f04a832f880d82008 ||86ef39 --- Comment #2 from sh_zam --- Git commit 42b82a8fc87d3f049f04a832f880d8200886ef39 by Sharaf Zaman. Committed on 03/06/2023 at 02:59. Pushed by szaman into branch 'master'. Android: Fix crash in SDL This happened because proguard removed our symbols. M +1-0packaging/android/apk/proguard-rules.pro https://invent.kde.org/graphics/krita/-/commit/42b82a8fc87d3f049f04a832f880d8200886ef39 -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 469865] Crash when exporting scans to PDF
https://bugs.kde.org/show_bug.cgi?id=469865 Nate Graham changed: What|Removed |Added Version Fixed In||23.04.2 -- 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 470280] Color scheme doesn't change after applying accent color from bw wallpaper
https://bugs.kde.org/show_bug.cgi?id=470280 --- Comment #4 from Fushan Wen --- Can reproduce -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] Metadata not updated
https://bugs.kde.org/show_bug.cgi?id=470566 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Platform|Other |Microsoft Windows --- Comment #1 from caulier.gil...@gmail.com --- What do you seen in debugview while you process the operations ? https://www.digikam.org/contribute/ Gilles Caulier -- 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 458446] Menus Start Showing behind Windows
https://bugs.kde.org/show_bug.cgi?id=458446 --- Comment #8 from Pedro Rosado --- Thank you, I will do so. Regards, Sent from Yahoo Mail on Android On Fri, Jun 2, 2023 at 13:52, Nate Graham wrote: https://bugs.kde.org/show_bug.cgi?id=458446 Nate Graham changed: What |Removed |Added Status|REOPENED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #7 from Nate Graham --- See Comment 3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 260266] Allow assigning keyboard shortcuts to service menu actions
https://bugs.kde.org/show_bug.cgi?id=260266 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=470542 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470542] Custom User Commands
https://bugs.kde.org/show_bug.cgi?id=470542 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=260266 --- Comment #2 from Christoph Feck --- See also bug 260266. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 342392] custom toolbar actions
https://bugs.kde.org/show_bug.cgi?id=342392 Christoph Feck changed: What|Removed |Added CC||advice2...@protonmail.com --- Comment #2 from Christoph Feck --- *** Bug 470542 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470542] Custom User Commands
https://bugs.kde.org/show_bug.cgi?id=470542 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED CC||cf...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 342392 *** -- 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 470567] New: ICC profiles are not applied for WebP images.
https://bugs.kde.org/show_bug.cgi?id=470567 Bug ID: 470567 Summary: ICC profiles are not applied for WebP images. Classification: Applications Product: krita Version: 5.1.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: replicable+...@protonmail.com Target Milestone: --- Created attachment 159421 --> https://bugs.kde.org/attachment.cgi?id=159421=edit A photo of a red bench, with an ICC profile ICC profiles are not applied when importing WebP images. STEPS TO REPRODUCE 1. Download the attached file 2. Open it in Firefox/Chrome/GIMP. It will appear red. 3. Open it in Krita. It will appear green. OBSERVED RESULT The bench appears green, since the ICC profile isn't applied. EXPECTED RESULT The bench should appear red. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION ICC profiles are correctly applied for AVIF, HEIC, JPEG, JXL, PNG and TIFF images. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466699] Dolphin crashes at start after failed offline-update
https://bugs.kde.org/show_bug.cgi?id=466699 --- Comment #3 from yl...@free.fr --- Created attachment 159420 --> https://bugs.kde.org/attachment.cgi?id=159420=edit New crash information added by DrKonqi plasma-discover (5.27.5) using Qt 5.15.9 I understood that this problem came from a ssl certificate and I had this problem on several applications. -- Backtrace (Reduced): #5 0x7ff20052bc50 in PackageKitBackend::resolvePackages(QStringList const&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so [...] #8 0x7ff22aae9bee in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7ff22c56c793 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7ff22aabc18a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7ff22aabf277 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448271] Integrate night mode controls into separate Brightness applet
https://bugs.kde.org/show_bug.cgi?id=448271 Natalie Clarius changed: What|Removed |Added CC||natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424283] Split applet into two: "Power Management" and "Brightness"
https://bugs.kde.org/show_bug.cgi?id=424283 Natalie Clarius changed: What|Removed |Added CC||natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 470382] Baloo unable to index any files
https://bugs.kde.org/show_bug.cgi?id=470382 --- Comment #5 from tagwer...@innerjoin.org --- (In reply to tagwerk19 from comment #4) > ... There's a wonderful, eye watering > example in Bug 394759 (scroll down to the 13th comment) ... Sorry that should be: https://bugs.kde.org/show_bug.cgi?id=394750#c13 The change that introduced the limit is here: https://invent.kde.org/frameworks/baloo/-/merge_requests/124 -- 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 466686] [NVIDIA] On Wayland, screen goes black after changing resolution and doesn't come back
https://bugs.kde.org/show_bug.cgi?id=466686 --- Comment #4 from kevin --- I've installed nvidia beta driver 535.43. Current updates are Plasma 5.27.5 Frameworks 5.106.0 Qt 5.15.9 and kernel 6.3.4-1. I can now change the resolution and settings will save it after a few of seconds of a dark screen. Looks like this bug has been solved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452022] The digital clock widget freezes randomly and recovers only on KDE restart
https://bugs.kde.org/show_bug.cgi?id=452022 ker...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452022] The digital clock widget freezes randomly and recovers only on KDE restart
https://bugs.kde.org/show_bug.cgi?id=452022 ker...@gmail.com changed: What|Removed |Added Platform|Fedora RPMs |Archlinux Version|5.24.3 |5.27.5 CC||ker...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 470484] Powerdevil crashes multiple times during screen sleep
https://bugs.kde.org/show_bug.cgi?id=470484
ratijas changed:
What|Removed |Added
CC||aleix...@kde.org,
||vlad.zahorod...@kde.org,
||xaver.h...@gmail.com
Status|REPORTED|CONFIRMED
Ever confirmed|0 |1
--- Comment #3 from ratijas ---
here,
> #5 QtWayland::org_kde_kwin_dpms::set(unsigned int) (mode=,
this=0x10) at /usr/src/debug/libkscreen/build/src/libdpms/qwayland-dpms.cpp:126
`this` is a null pointer, although incremented by 0x10 probably to account for
nested object layout within inheritance hierarchy of C++:
> class Dpms : public QObject, public QtWayland::org_kde_kwin_dpms
Perhaps, this call should be guarded?
> void WaylandDpmsHelper::trigger(KScreen::Dpms::Mode mode, const QList *> )
> {
> // ...
> for (auto screen : screens) {
> auto dpms = m_dpmsManager->fetch(screen);
> dpms->set(level);
> }
Because having an output per se does not seem to guarantee the existence of a
Dpms object available for fetch:
> Dpms *fetch(QScreen *screen)
> {
> return m_dpmsPerScreen.value(screen);
> }
>
> private:
> void addScreen(QScreen *screen)
> {
> // We can't rely on checking the wl_output being null yet
> // https://codereview.qt-project.org/c/qt/qtwayland/+/464669
> const bool fake = screen->geometry().isEmpty() ||
> screen->name().isEmpty();
> if (fake) {
> return;
> }
>
> QPlatformNativeInterface *native = qGuiApp->platformNativeInterface();
> wl_output *output = reinterpret_cast *>(native->nativeResourceForScreen(QByteArrayLiteral("output"), screen));
> if (output) {
> m_dpmsPerScreen[screen] = new Dpms(get(output), m_dpms, screen);
> }
> }
As you can see there are several conditions under which `m_dpmsPerScreen` hash
map would be left without a value for some given screen.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kwayland] [Bug 466767] kwayland 5.103.0 fails to compile with LTO enabled due to ODR violations and lto type mismatch
https://bugs.kde.org/show_bug.cgi?id=466767 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 469396] alt+number not working in yakuake
https://bugs.kde.org/show_bug.cgi?id=469396 surla...@proton.me changed: What|Removed |Added CC||surla...@proton.me --- Comment #2 from surla...@proton.me --- All alt+number are default shortcuts to switch to the numbered tab. What happens if you rebind them? -- 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.
[Powerdevil] [Bug 470484] Powerdevil crashes multiple times during screen sleep
https://bugs.kde.org/show_bug.cgi?id=470484 --- Comment #2 from MScattolin --- (In reply to Nicolas Fella from comment #1) > Can you please follow > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > to get a proper backtrace? The one you pasted is missing demangling and > debug symbols to be fully useful Hello, sure, got the following from the latest coredump: #0 __GI___pthread_sigmask (how=1, newmask=, oldmask=0x0) at pthread_sigmask.c:43 #1 0x7fd6e264fcad in __GI___sigprocmask (how=, set=, oset=) at ../sysdeps/unix/sysv/linux/sigprocmask.c:25 #2 0x7fd6e3c5520b in KCrash::setCrashHandler(void (*)(int)) (handler=handler@entry=0x0) at /usr/src/debug/kcrash/kcrash-5.106.0/src/kcrash.cpp:414 #3 0x7fd6e3c57816 in KCrash::defaultCrashHandler(int) (sig=11) at /usr/src/debug/kcrash/kcrash-5.106.0/src/kcrash.cpp:625 #4 0x7fd6e264fab0 in () at /usr/lib/libc.so.6 #5 QtWayland::org_kde_kwin_dpms::set(unsigned int) (mode=, this=0x10) at /usr/src/debug/libkscreen/build/src/libdpms/qwayland-dpms.cpp:126 #6 WaylandDpmsHelper::trigger(KScreen::Dpms::Mode, QList const&) (this=0x559b6a7b7380, mode=, screens=) at /usr/src/debug/libkscreen/libkscreen-5.27.5/src/libdpms/waylanddpmshelper.cpp:191 #7 0x7fd6dc2ffcc4 in KScreen::Dpms::switchMode(KScreen::Dpms::Mode, QList const&) (this=, mode=mode@entry=KScreen::Dpms::Off, screens=...) at /usr/src/debug/libkscreen/libkscreen-5.27.5/src/libdpms/dpms.cpp:40 #8 0x7fd6dc30a6ca in PowerDevil::BundledActions::DPMS::onIdleTimeout(int) (this=, msec=) at /usr/src/debug/powerdevil/powerdevil-5.27.5/daemon/actions/bundled/dpms.cpp:135 #9 0x7fd6e3c22a51 in PowerDevil::Core::onKIdleTimeoutReached(int, int) (this=0x559b6a7606b0, identifier=1, msec=150) at /usr/src/debug/powerdevil/powerdevil-5.27.5/daemon/powerdevilcore.cpp:840 #10 0x7fd6e2ed01a3 in doActivate(QObject*, int, void**) (sender=0x559b6a759570, signal_index=5, argv=0x7ffc3e8201a0) at kernel/qobject.cpp:3935 #11 0x7fd6e31c433d in KIdleTime::timeoutReached(int, int) (this=this@entry=0x559b6a759570, _t1=, _t1@entry=1, _t2=, _t2@entry=150) at /usr/src/debug/kidletime/build/src/KF5IdleTime_autogen/include/moc_kidletime.cpp:195 #12 0x7fd6e31c4ee1 in KIdleTimePrivate::timeoutReached(int) (msec=150, this=) at /usr/src/debug/kidletime/kidletime-5.106.0/src/kidletime.cpp:297 #13 operator() (msec=150, __closure=) at /usr/src/debug/kidletime/kidletime-5.106.0/src/kidletime.cpp:88 #14 QtPrivate::FunctorCall, QtPrivate::List, void, KIdleTime::KIdleTime():: >::call (arg=, f=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:146 #15 QtPrivate::Functor, 1>::call, void> (arg=, f=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:256 #16 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:443 #17 0x7fd6e2ecffe7 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc3e8202f0, r=, this=0x559b6a7b2c30, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #18 doActivate(QObject*, int, void**) (sender=0x559b6a81b3f0, signal_index=4, argv=0x7ffc3e8202f0) at kernel/qobject.cpp:3923 #19 0x7fd6e31c4226 in AbstractSystemPoller::timeoutReached(int) (this=, _t1=) at /usr/src/debug/kidletime/build/src/KF5IdleTime_autogen/EWIEGA46WW/moc_abstractsystempoller.cpp:189 #20 0x7fd6e2ecffe7 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc3e8203a0, r=, this=0x559b6a76c5b0, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #21 doActivate(QObject*, int, void**) (sender=0x7fd6d8026640, signal_index=3, argv=0x7ffc3e8203a0) at kernel/qobject.cpp:3923 #22 0x7fd6e3c6b4f6 in () at /usr/lib/libffi.so.8 #23 0x7fd6e3c67f5e in () at /usr/lib/libffi.so.8 #24 0x7fd6e3c6ab73 in ffi_call () at /usr/lib/libffi.so.8 #25 0x7fd6e3c76645 in wl_closure_invoke (closure=closure@entry=0x7fd6d0001980, target=, target@entry=0x559b6a848860, opcode=opcode@entry=0, data=, flags=1) at ../wayland-1.22.0/src/connection.c:1025 #26 0x7fd6e3c76e73 in dispatch_event (display=display@entry=0x559b6a753100, queue=0x559b6a7531f0) at ../wayland-1.22.0/src/wayland-client.c:1631 #27 0x7fd6e3c7713c in dispatch_queue (queue=0x559b6a7531f0, display=0x559b6a753100) at ../wayland-1.22.0/src/wayland-client.c:1777 #28 wl_display_dispatch_queue_pending (display=0x559b6a753100, queue=0x559b6a7531f0) at ../wayland-1.22.0/src/wayland-client.c:2019 #29 0x7fd6dd6efc06 in QtWaylandClient::QWaylandDisplay::flushRequests() (this=) at /usr/src/debug/qt5-wayland/qtwayland/src/client/qwaylanddisplay.cpp:255 #30 0x7fd6e2ec2834 in QObject::event(QEvent*) (this=0x559b6a752fa0, e=0x7fd6d0001b90) at kernel/qobject.cpp:1347 #31
[Discover] [Bug 470232] Show package description on updates page
https://bugs.kde.org/show_bug.cgi?id=470232 --- Comment #5 from vaughan.m.johns...@protonmail.com --- (In reply to Nate Graham from comment #4) > Seems sane, thanks. I'll see what I can do. Thanks :-) -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 442582] When merging files from`git mergetool`, output is scrolled to top instead of first conflict
https://bugs.kde.org/show_bug.cgi?id=442582 --- Comment #7 from nyanpasu64 --- Created attachment 159419 --> https://bugs.kde.org/attachment.cgi?id=159419=edit Picture of "git mergetool" opening kdiff3 1.10.4, with output scrolled to top -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 442582] When merging files from`git mergetool`, output is scrolled to top instead of first conflict
https://bugs.kde.org/show_bug.cgi?id=442582 nyanpasu64 changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #6 from nyanpasu64 --- Actually the bug still occurs on 1.10.4 I think? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470566] New: Metadata not updated
https://bugs.kde.org/show_bug.cgi?id=470566 Bug ID: 470566 Summary: Metadata not updated Classification: Applications Product: digikam Version: 8.0.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Engine Assignee: digikam-bugs-n...@kde.org Reporter: bugzi...@kgb.ovh Target Milestone: --- Created attachment 159418 --> https://bugs.kde.org/attachment.cgi?id=159418=edit screen capture SUMMARY Difficult to update an image. STEPS TO REPRODUCE 1. Outside digiKam 8.0.0, modify some information about some images. For example, use exiftool directly to add geo‐location to a photograph. Or change the timestamp of a file (I’m not speaking about the Exif time, although the result should be the same). 2. Rescan your image (after a digiKam restart or manually refresh a folder). OBSERVED RESULT Metadata is usually not updated in digiKam. After the metadata update, I tried many things to force digiKam to update the metadata: - restart digKam to force it to update the files, - delete the files then restore them, - rescan the folder, - rename the files, - have a new identical copy in the system file manager. They all fail. In the screen capture, you can see that digiKam actually updates something, but not all. − The geo‐location appears in the Metadata pane, but the globe icon is not presented for any of these photographs. - I can’t upload these files to iNaturalist because they are “not located”. - However the Geolocation Editor can pin the photograph where it belongs. EXPECTED RESULT The metadata should be updated. SOFTWARE/OS VERSIONS Windows: 7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 470365] Timer counts down too fast
https://bugs.kde.org/show_bug.cgi?id=470365 jim+...@nekojimi.moe changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from jim+...@nekojimi.moe --- (In reply to Nate Graham from comment #5) > Ok, thanks. > > Is it only the Timer widget, or do other times things in Plasma exhibit the > same issue? For example do notifications time out 2.5x as fast? Now that you mention it, I've just checked the settings and it seems that notifications do time out much too quickly as well - I tested by setting the notification timeout to 20 seconds, made a notification appear, and it timed out in about 8 seconds. I also tried changing the Plasma animation speed to the slowest setting to rule it out but it had no effect. I've also noticed that the issue is a slightly inconsistent - I've seen the timer work correctly once or twice, I think (?) shortly after starting my computer. It inevitably starts misbehaving at some point during the day, and then never works again until a restart, and usually not even then. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470329] Monitor power on / off results in stolen input and broken xwayland clients
https://bugs.kde.org/show_bug.cgi?id=470329 --- Comment #6 from Andrei Amuraritei --- Forgot to mention that Plasma was updated to 5.27.5 in the mean time. Nate, could you detail why you think this is a duplicate of 466149? I am not following that. Or, in my case, for the Wayland session, the primary screen remains primary (DELL) and is always XWAYLAND0 and it is currently set at pos 0x0. Then the other screen is SAMSUNG, at pos +2560 and remains there. The primary thing does not change as far as I can see, xrandr always says primary is XWAYLAND0 (maybe because it should be fixed with 5.27.5). However as noted, the SAMSUNG screen gets a new XWAYLAND ID every time I power it on. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463641] Dolphin crashes while navigating filesystem (Other programs running in background)
https://bugs.kde.org/show_bug.cgi?id=463641 wouter.sch...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from wouter.sch...@gmail.com --- Update on 02 june 2023: Reinstalled my system and switched to Fedora 38 KDE Spin. Most likely something got patched. Or the plasma desktop is installed completely and correctly this time. If it could help anyone, i will leave the version numbers of baloo file extractor related packages in this comment. - baloo-widgets version 23.04.1 release 1.fc38 - kf5-baloo version 5.106.0 release 1.fc38 - kf5-baloo-file version 5.106.0 release 1.fc38 - kf5-baloo-libs version 5.106.0 release 1.fc38 - -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 470565] New: Crash after try to scan sftp path
https://bugs.kde.org/show_bug.cgi?id=470565 Bug ID: 470565 Summary: Crash after try to scan sftp path Classification: Applications Product: filelight Version: 22.12.3 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@kokanovic.org CC: martin.sandsm...@kde.org Target Milestone: --- Application: filelight (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-7-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: In Konqueror, I am browsing sftp://192.168.0.x/some/link url and I open Filelight with right-click. Clicking "Scan" crashed Filelight. The crash can be reproduced every time. -- Backtrace: Application: Filelight (filelight), signal: Segmentation fault [KCrash Handler] #4 0x7fcca48afe30 in QEventLoop::exit(int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcca59a2c24 in KJob::finishJob(bool) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #6 0x7fcca48dd6f0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fcca6162fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7fcca48b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fcca48b4681 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fcca490a153 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fcca311e7a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fcca311ea38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7fcca311eacc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fcca4909836 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fcca48b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fcca48b82d6 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x5578fff079c3 in ?? () #18 0x7fcca444618a in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #19 0x7fcca4446245 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #20 0x5578fff07bf1 in ?? () [Inferior 1 (process 1940062) detached] Reported using DrKonqi -- 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 154804] Add option for alternative Drag behaviour
https://bugs.kde.org/show_bug.cgi?id=154804 --- Comment #61 from Nate Graham --- I've been planning to work on finishing up the earlier patches, but as with so many things, it's just so hard to carve out time with the 500,000 other things I have to do. I imagine most other people are in a similar situation, especially since this is really a nice-to-have, not even a bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 154804] Add option for alternative Drag behaviour
https://bugs.kde.org/show_bug.cgi?id=154804 advice2...@protonmail.com changed: What|Removed |Added CC||advice2...@protonmail.com --- Comment #60 from advice2...@protonmail.com --- I agree with this as well, this one is so important to me. KDE Plasma is amazing, this is literally one of the only things I can find that I do not care for, makes it very difficult to use. I am aware that you can use modifier keys to avoid them but for such a standard action should not really have to use a keyboard modifier to perform a simple drag & drop action like moving a file. Nothing wrong with having these context menus be the default for those who like them, but seems odd that KDE, a group known for endless customization / settings, does not have an option to be able to turn these off / allow users to choose how drag & drops perform. I have never seen any other file managers use this approach with LMB D so with something that is far away from a standard, again seems odd not to be able to have a setting for something like this. I have however seen in Windows as well as some FM in Linux the use of the RMB D for these context menus which I would prefer. RMB makes more sense because a single click brings up context menu so D with RMB to bring up these CM would fit in better here. I made a more in depth post about how this could possibly be handled here as well to hopefully get some more users to vote for this. https://discuss.kde.org/t/plasma-dolphin-drag-drop-context-menus/1809 Do votes really mean anything? How many does an issue have to have in order to be worked on? To me personally this is a pretty big deal, hopefully this could finally be addressed. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 392626] Tab changes when an unselected tab is closed
https://bugs.kde.org/show_bug.cgi?id=392626 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/yakuake/-/merge_requests/103 -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 441925] Okteta search behavior keeps selecting "selected bytes" when it's not wanted--doesn't remember settings
https://bugs.kde.org/show_bug.cgi?id=441925 Friedrich W. H. Kossebau changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||0.26.11 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/util ||ities/okteta/-/commit/48e3f ||9820009abd7198653590a3787e2 ||1c45907c --- Comment #1 from Friedrich W. H. Kossebau --- Git commit 48e3f9820009abd7198653590a3787e21c45907c by Friedrich W. H. Kossebau. Committed on 02/06/2023 at 19:29. Pushed by kossebau into branch '0.26'. Search/replace tools: disable automagic for "In selection" checkbox Conditions used not the silver bullet behaviour after all. FIXED-IN: 0.26.11 M +3-1kasten/controllers/view/replace/replacedialog.cpp M +3-1kasten/controllers/view/search/searchdialog.cpp https://invent.kde.org/utilities/okteta/-/commit/48e3f9820009abd7198653590a3787e21c45907c -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466699] Dolphin crashes at start after failed offline-update
https://bugs.kde.org/show_bug.cgi?id=466699 --- Comment #2 from yl...@free.fr --- Created attachment 159417 --> https://bugs.kde.org/attachment.cgi?id=159417=edit New crash information added by DrKonqi plasma-discover (5.27.5) using Qt 5.15.9 I understood that this problem came from a ssl certificate and I had this problem on several applications. -- Backtrace (Reduced): #5 0x7f0e7847bc50 in PackageKitBackend::resolvePackages(QStringList const&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so [...] #8 0x7f0eb96e9bee in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f0ebb36c793 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f0eb96bc18a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f0eb96bf277 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466699] Dolphin crashes at start after failed offline-update
https://bugs.kde.org/show_bug.cgi?id=466699 yl...@free.fr changed: What|Removed |Added CC||yl...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 470564] New: Link is formatted mathematically
https://bugs.kde.org/show_bug.cgi?id=470564 Bug ID: 470564 Summary: Link is formatted mathematically Classification: Applications Product: akregator Version: 5.22.3 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: schwar...@kde.org Target Milestone: --- Created attachment 159416 --> https://bugs.kde.org/attachment.cgi?id=159416=edit link in mathematical format SUMMARY A link in one article is formatted as if it were a mathematical formula. See attached image. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469277] Black screen after loging in my machine when external screen is attached
https://bugs.kde.org/show_bug.cgi?id=469277 Nate Graham changed: What|Removed |Added Status|REOPENED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #13 from Nate Graham --- Can you move aside your ~/.local/share/kscreen folder, disable any randr scripts you're using, and then try again? If the issue happens again, hit Alt+F2 to launch KRunner, which you can use to launch Konsole, and then you can run kscreen-doctor in there. But from the looks of it, the problem here may be in Plasma, rather than KScreen. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 468687] Feature request: mark episodes as complete with an adjustable time remaining in Kasts
https://bugs.kde.org/show_bug.cgi?id=468687 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/multimedia/kasts/-/merge_requests/115 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470280] Color scheme doesn't change after applying accent color from bw wallpaper
https://bugs.kde.org/show_bug.cgi?id=470280 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 --- Comment #3 from Nate Graham --- Oops, was not testing correctly, sorry. I can in fact reproduce this issue. I wonder if the lack of any colors is throwing off the detector. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457370] Task manager causes Plasma to hang with heavy usage
https://bugs.kde.org/show_bug.cgi?id=457370 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #17 from Nate Graham --- (In reply to David Chmelik from comment #16) > (In reply to Nate Graham from comment #13) > > Ok, so the issue in the Task Manager code somewhere. > > > > Can you clarify what "doing millions updates again" means? Are any of these > > apps rapidly changing their window title or rapidly changing whether audio > > is played or not? > > Not those but other things that may have been causing the task manager to > update/flash mostly/all text/file updates... many on status bars or > elsewhere, but not title bar. What does that mean? What apps are you talking about? Can you describe *exactly* what those apps are doing that causes the Task Manager to update or flash? I ask because this does not seem like normal behavior. A screen recording might help avoid a lot of bash-and-forth questions and answering. If you could attach one, it would be very helpful. -- 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 470185] Maximized windows not covering entire screen in some circumstances
https://bugs.kde.org/show_bug.cgi?id=470185 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #6 from Nate Graham --- Does the issue still happen... ...on Wayland? ...if you make your panel always visible? ...if you add `export PLASMA_USE_QT_SCALING=1` to the `~/.config/plasma-workspace/env/envs.sh` file (creating it if it doesn't exist) and then reboot? -- 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 Nate Graham changed: What|Removed |Added Status|REOPENED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 470376] kscreenlocker uses discrete GPU when integrated GPU is available
https://bugs.kde.org/show_bug.cgi?id=470376 --- Comment #3 from Nate Graham --- Thanks. Out of curiosity, does the discrete GPU also render the logout screen? The thing that appears when you click "Shut Down." If so, then I'm guessing the shader-based blur effects they both use are triggering the behavior. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470232] Show package description on updates page
https://bugs.kde.org/show_bug.cgi?id=470232 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #4 from Nate Graham --- Seems sane, thanks. I'll see what I can do. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469349] Custom Shortcuts gobble "keyboard input" letter
https://bugs.kde.org/show_bug.cgi?id=469349 Nate Graham changed: What|Removed |Added Component|general |kcm_khotkeys Assignee|unassigned-b...@kde.org |k...@michael-jansen.biz CC||plasma-b...@kde.org Product|kde |systemsettings Version|unspecified |5.27.5 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 439364] Dialog "Conflicts Left" is displayed when kdiff3 just started.
https://bugs.kde.org/show_bug.cgi?id=439364 michael changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #4 from michael --- Looks like this should now be resolved in 1.10.4 by changes for an unrelated issue handling auto-merge. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 452565] Akonadi is creating "Unknown Organization" in $HOME/.config
https://bugs.kde.org/show_bug.cgi?id=452565 --- Comment #1 from Shmerl --- Any news on this? -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 470476] File portal uses an incorrect too-small font size
https://bugs.kde.org/show_bug.cgi?id=470476 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Nate Graham --- > The logical DPI on this system is already set to 144. Note that this isn't a supported way to do scaling in a KDE environment. If you want everything on the screen to be bigger, the expected UX is to use the global scaling slider in System Settings > Display and Monitor. If yo just want the text to be a bit bigger for readability's take, the expected UX is to increase the font sizes in System Settings > Appearance > Fonts. In no case should it be necessary to change the Font DPI, and we're actually removing the ability to do so in Plasma 6. Does the global scale slider help? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469653] Primary monitor changes after resume from sleep when screens' DP cables are plugged into the NVIDIA GPU in a specific way
https://bugs.kde.org/show_bug.cgi?id=469653 Nate Graham changed: What|Removed |Added Keywords||wayland Summary|[Wayland] Primary monitor |Primary monitor changes |changes after resume from |after resume from sleep |sleep |when screens' DP cables are ||plugged into the NVIDIA GPU ||in a specific way --- Comment #15 from Nate Graham --- Amazing. I'm not sure how to proceed from here, so I'll keep the bug report open. Glad you found a setup that works now, though! -- 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.
[kio-extras] [Bug 470544] Many SSH config options are not respected
https://bugs.kde.org/show_bug.cgi?id=470544 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Nate Graham --- In a project with a deep technology stack, it's common that issues manifesting to users are caused by problems at a lower level in the stack. Other common examples that I can think of include: - Graphical glitches or multi-screen problems caused by graphics drivers - Audio issues caused by PulseAudio/PipeWire - Power management and battery life issues caused by the Linux kernel and its hardware platform drivers - Network connection isues caused by NetworkManager - Bluetooth connection issues caused Bluez etc. It would not feasible for KDE to take ownership of those parts of the stack by either forking them or assigning people to contribute to them; frankly we have trouble even maintaining our own code, due to its vast breadth and our limited resources. I wish this were different, but it's not. Ultimately, resolving issues like these is the job of the system integrators. Their role is to take diverse pieces of software, jam them together, see what breaks, assign people to work permanently on problem-child upstream projects, fix bugs in a targeted manner, QA the result and polish it up, and then distribute it as a cohesive supported product--likely for money, because doing all of this is un-fun work that people generally only do when paid. In the Linux world, historically our system integrators have been the software distributions--especially the ones that have commercial backing and deep pockets. Today the model seems like it's sort of dying, with the big players taking less interest in our world and neglecting critical issues for years, and a massive proliferation of micro-distros developed by 1-2 person teams that aren't sustainable and pass the buck for every issue below them. All of this makes sense when resources are highly constrained, as they are. It's my opinion that those selling Linux-powered hardware need to step up to take the role of system integrator more seriously, by putting dedicated engineering effort into fixing problems at all levels of the stack. When you get all the software you ship for free, that's a business cost savings, which should free up funds for developing it. This work takes money, and they have it. Certainly more than KDE and most distros do. Speaking personally, it's been my dream to see KDE itself become a hardware company and reinvest the revenue from selling devices into development not only on KDE software, but on the software we rely on. But at this point, it's just a dream. --- If you'd like to take the initiative to better-categorize the upstream bug reports that affect users so that there's at least a record of what's damaging the UX, that seems like something actionable that could be done--by anyone! Since you expressed interest in it, I think it makes sense for you to give it a shot. The way this would work is as follows: - Create a new metabug titled something like "Upstream libssh issues" - Find all the bug reports we have that are ultimately caused by upstream libssh issues - For each one, identify the upstream libssh bug report and put it in the URL field of the bug report, then close it as RESOLVED UPSTREAM and then mark it as a blocker for the metabug That way, even though they're closed in our bu tracker, the bug reports will still be findable. What do you think? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 470563] New: konsole bell sound blows up memory usage of pipewire-pulse
https://bugs.kde.org/show_bug.cgi?id=470563 Bug ID: 470563 Summary: konsole bell sound blows up memory usage of pipewire-pulse Classification: Applications Product: konsole Version: 22.12.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: dmat...@gmx.de Target Milestone: --- SUMMARY If konsole plays bell sounds in quick succession, the memory usage of the pipewire-pulse background process grows without limits. The memory usage does not go down over time. The pipewire-pulse process has to be restarted to reclaim the memory. STEPS TO REPRODUCE 1. Open konsole. 2. Open the Settings -> Configure Notifications ... dialog. Select "Bell in focused session" from the list of events. Check "Play a sound" and select an existing sound file. Apply. 3. Press Ctrl+Esc to open the "System Activity" monitor - or any other too that is able to show the memory consumption of background processes. 4. In the console window, press and hold backspace key for a few seconds to generate a quick succession of bell sounds. 5. Watch how the memory consumption of pipewire-pulse behaves. OBSERVED RESULT The memory consumption grows to several hundred megabytes and stays high afterwards. When releasing the key, the memory consumption goes down a little bit but stays high. This behavior may also be caused by other applications that play sound. When I play audio using audacious or watching a video in firefox, the memory consumption of pipewire-pulse stays very low (a few megabytes). When I discovered the problem, pipewire-pulse permanently occupied over 600 MiB. After a reboot, the memory consumption was on the normal level of a few megabytes. EXPECTED RESULT I would expect that the memory consumption grows a bit while playing the possibly overlapping bell sounds and then goes down to a few megabytes after the internal buffers have been freed. SOFTWARE/OS VERSIONS Linux kernel: 6.2.0-20-generic (64-bit) KDE Plasma Version: 5.27.5 (backports on Kubuntu 23.04) KDE Frameworks Version: 5.106.0 Qt Version: 5.15.8 pipewire/pipewire-pulse Version: 0.3.65-3 libpulse0 Version: 1:16.1+dfsg1-2ubuntu3 ADDITIONAL INFORMATION The bug may be anywhere between konsole and pipewire-pulse. I filed this bug under konsole because it can be reproduced in the konsole window and I couldn't identify other applications that let the memory consumption grow that much. -- You are receiving this mail because: You are watching all bug changes.
