[kwin] [Bug 490358] Jerky/stuttering graphics in Plasma 6 with Intel GPU
https://bugs.kde.org/show_bug.cgi?id=490358 --- Comment #24 from valdi...@gmail.com --- This is not fixed for me in 6.3.2, but now I have a somewhat reliable reproducer. 1. Open Telegram messenger 2. Open Firefox with the dark theme, maximize the window 3. Hide Telegram window behind the Firefox, DO NOT MINIMIZE THE WINDOW 4. Open this page (this bug), or for example https://docs.hackerone.com/en/articles/8399430-id-verification 5. Scroll the page slowly Result: 30 fps rendering, as shown by "Show FPS" desktop effect. This happens only when Telegram window is present on screen. It could be hidden behind Firefox, it could be visible, but it should not be minimized. Moving Telegram window to another desktop (not where Firefox is) does not trigger the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 501309] New: Need to scroll for the relevant search result: Better strategy for search result's view needed
https://bugs.kde.org/show_bug.cgi?id=501309 Bug ID: 501309 Summary: Need to scroll for the relevant search result: Better strategy for search result's view needed Classification: Plasma Product: plasmashell Version: 6.3.2 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Application Menu (Kicker) widget Assignee: plasma-b...@kde.org Reporter: pos...@posteo.eu Target Milestone: 1.0 Created attachment 179269 --> https://bugs.kde.org/attachment.cgi?id=179269&action=edit Screenshot of Kicker: by default the widget is smaller (red line) If you search for something in Kicker you are presented results for different subsections, e. g. "files" and "applications". If I search for "gtk4-demo", I get 10 results for random flatpak runtimes in the "files" subsection and at the very bottom the desired "application" gtk4-demo. There are several possible solutions to improve the situation: 1) Always use a bigger Kicker widget, so that all results fit into the view - not so convenient 2) The results per subsection become limited to e.g. 5 instead of 10, with the possibility to expand. (Don't know if it's already limited?) 3) Push search result items, which are more often opened/used to the top, give them more weight: both within subsections and for subsections themselves 4) Order the list by application first as those are likely less in number than files 5) ... more ideas? -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 501331] Syncing Google Contacts with kAddressbook / Kontact results in phone number and email address label changes
https://bugs.kde.org/show_bug.cgi?id=501331 --- Comment #1 from BushMechanic --- Created attachment 179283 --> https://bugs.kde.org/attachment.cgi?id=179283&action=edit Screenshots showing label changes for a Google Contact created contact. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 500745] The Hardware section of the Info Center shows wrong and confusing description for 'Processors' on its initial (summary) page
https://bugs.kde.org/show_bug.cgi?id=500745 --- Comment #11 from John --- Created attachment 179284 --> https://bugs.kde.org/attachment.cgi?id=179284&action=edit The system monitor and the "Total CPU Use" are lying about the cores and the Info Center is agreeing with them BTW, here's the proof that your System Monitor software is lying about the hardware and consistency with it makes no sense when it comes displaying information about the hardware. I followed the tutorial in that link at my previous (nr. 7) comment and add in GRUB-Customizer (that I already had installed) on its "General settings" tab under the "Kernel parameters" section this: ' maxcpus=2', so the whole line looks like this: quiet maxcpus=2 Then clicked on the "Save" button and rebooted the laptop. Since changing a config and rebooting can't possibly trigger a "Transformers" movie-like change in CPU's hardware, it's clear that the software is not lying about the hardware as the CPU still has the same hardware cores / threads. It's just Linux that is making them appear less, probably by reporting less of them. So I don't see much sense to keep the "Hardware" section of the Info Center tied / in sync or how you call it "consistent" with the system monitor that can tell lies depending on the situation. BTW, lscpu now shows: CPU(s): 8 On-line CPU(s) list:0,1 Off-line CPU(s) list: 2-7 Vendor ID:GenuineIntel Model name: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz CPU family: 6 Model:142 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s):1 And kinfo, like its graphical counterpart: Processors: 2 × Intel® Core™ i5-8250U CPU @ 1.60GHz As I said before, I want the hardware section in this software, like in any other, to show me information about the hardware, not how the software sees it, uses it, limits it. Leave that for the resource monitors. It would be great if you would separate the non-changeable parts (the hardware) form the changeable parts (the software, even when it's about the hardware) If I buy a Wi-Fi 7 network adapter and connect it to a Wi-Fi 5 AP, it doesn't mean that my hardware is Wi-Fi 5 capable only. Anyway, I'm starting to get tired of explaining that I want to see hardware specs and those should be as accurate as possible. And it's pretty disappointing to see that the kernel and lscpu developers, at least decide to use CPUs, cores, threads interchangeably and on top of that lscpu, kinfo(center), can show wrong information about the hardware just because I changed only little kernel configuration. So, it's cool that the Info Center has a dedicated CPU info page, but it's bad that the page shows wrong / incorrect information too by default: CPU(s), and even more when somebody plays with the kernel configuration. It seems that there's is absolutely 0 software than can show accurate hardware information about the CPU when someone plays with that kernel config as I tested HardInfo2 and even CPU-X and even those fail this test by showing 2 cores only (HardInfo though still show the correct 8 threads, like lscpu). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402857] Touchpad and touchscreen gestures should be configurable
https://bugs.kde.org/show_bug.cgi?id=402857 sowi...@dukun.de changed: What|Removed |Added CC||sowi...@dukun.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 501332] New: wish - temporary zoom during cropping
https://bugs.kde.org/show_bug.cgi?id=501332 Bug ID: 501332 Summary: wish - temporary zoom during cropping Classification: Applications Product: digikam Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-Bqm-Crop Assignee: digikam-bugs-n...@kde.org Reporter: mke...@pigfy.de Target Milestone: --- I would like to suggest the following idea/request: For over 20 years, I have been working professionally with the commercial image database IMS from Imagic. To better select the start and end points of measurement tasks in images, there is a digital zoom at the push of a button. As long as the Shift key is pressed, the area around the current mouse position is digitally magnified to 100%. In this magnified view, the cursor can be positioned precisely. Currently, I have to manually crop many images, and such a button could significantly improve the result in digikam: pressing a button magnifies the image to 100% as soon as the mouse is in the upper right or lower left corner, or... and I can precisely select the corner for cropping. I was able to implement similar functionality in ImageJ/Fiji using GenAI, but having it directly in Digikam would of course be a great improvement. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480683] Allow choice of specific date and time format.
https://bugs.kde.org/show_bug.cgi?id=480683 --- Comment #8 from Kevin Kofler --- > Then how did KDE4 manage it kdelibs 4 had a working customizable locale implementation inherited from kdelibs 3 (KLocale) that handled this just fine. That was unfortunately dropped in favor of the inferior QLocale implementation in Qt proper as part of the KDE Frameworks 5 migration, where the developers were more interested in reducing the amount of required dependencies in a split library world (where every feature that was previously part of libkdecore or libkdeui is now its own split "Framework") than in keeping perfectly working functionality working. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 501130] Clipboard history replaces non-Latin characters with an escape sequence
https://bugs.kde.org/show_bug.cgi?id=501130 John Kizer changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WAITINGFORINFO |--- CC||john.ki...@proton.me --- Comment #3 from John Kizer --- I think this might have been accidentally set to the status Resolved/Waitingforinfo - Nate please override if I'm wrong there. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 450541] [event summary] The value associated to the "Calendar :" field is prefixed arbitrarily.
https://bugs.kde.org/show_bug.cgi?id=450541 Allen Winter changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||win...@kde.org --- Comment #1 from Allen Winter --- this isn't true for a long time. closing -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484031] On X11, after waking from suspend with four-monitor setup, one or two monitors don't wake up
https://bugs.kde.org/show_bug.cgi?id=484031 --- Comment #5 from Bug Janitor Service --- 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read 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.
[systemsettings] [Bug 501315] New: Unable to click "Apply" on Touchpad settings
https://bugs.kde.org/show_bug.cgi?id=501315 Bug ID: 501315 Summary: Unable to click "Apply" on Touchpad settings Classification: Applications Product: systemsettings Version: 6.3.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: kroot.pa...@gmail.com CC: duha.b...@gmail.com, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 179272 --> https://bugs.kde.org/attachment.cgi?id=179272&action=edit Bug in touchpad kcm SUMMARY I am not able to press the "Apply" button on Touchpad KCM after modifying some options. STEPS TO REPRODUCE 1. Go to Touchpad settings 2. Modify any option 3. Press "Apply" OBSERVED RESULT Apply button is pressed but does not actually save my settings. The button remains active. EXPECTED RESULT Settings are saved and the "Apply" button becomes disabled until further modifications are made. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION Note that this seems to only happen on X11. I recently switched from Wayland to X11 (both on plasma 6.3.2) and initially saw that my touchpad settings had been reset. Trying to modify them leads to this errors. I can still manage to apply by switching the KCM to something else (by pressing the "Mouse" entry in the sidebar, for example) and hitting "Apply" on the popup that says "Discard Changes?". However, many of the options (like Natural Scrolling) don't actually get activated on doing this. A restart sometimes fixes the issues, but they randomly reappear (as if the settings had been reset.) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 501257] People are not recognized
https://bugs.kde.org/show_bug.cgi?id=501257 --- Comment #9 from Andy --- Hi! I removed all the faces in one of the pictures in question and added the frames again. Then clicked "Recognize faces". Some of the faces were recognized correctly. 2 or 3 others were unknown. I started "Recognize faces" several times without the remaining faces being recognized. Then I confirmed one of the recognized faces and pressed "Recognize faces" again. Now one of the unknown faces was also assigned a name. When I confirmed one again and pressed "Recognize faces", another face was correctly suggested. Is there a limit for face recognition per photo? Regards Andy -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 501257] People are not recognized
https://bugs.kde.org/show_bug.cgi?id=501257 --- Comment #10 from Michael Miller --- Hi Andy, Can you upload the original image? I need the original, and without the face rects detected by digiKam. The sample image faces are definitely being rejected by FIQA because the face thumbnails are too small. I'd like to try the test on the original image. Cheers, Mike -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461063] xdg_toplevel.set_fullscreen does not center surface and doesn't add black background/padding/bars
https://bugs.kde.org/show_bug.cgi?id=461063 Zamundaaa changed: What|Removed |Added CC||o...@np880.ru --- Comment #5 from Zamundaaa --- *** Bug 501243 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 501257] People are not recognized
https://bugs.kde.org/show_bug.cgi?id=501257 --- Comment #11 from Michael Miller --- (In reply to Andy from comment #9) > Hi! > I removed all the faces in one of the pictures in question and added the > frames again. Then clicked "Recognize faces". Some of the faces were > recognized correctly. 2 or 3 others were unknown. > I started "Recognize faces" several times without the remaining faces being > recognized. Then I confirmed one of the recognized faces and pressed > "Recognize faces" again. Now one of the unknown faces was also assigned a > name. When I confirmed one again and pressed "Recognize faces", another face > was correctly suggested. > Is there a limit for face recognition per photo? > > Regards > Andy Hi Andy, No, there isn't a limit to the number of faces recognized in each photo. In version 8.5.0, we use the face for recognition if the AI model can extract the face features. Sometimes the AI can't extract the features, and so the face isn't used for training or matching. Sometimes because of thumbnail image quality factors the extracted features are so pool that they don't match anything. Cheers, Mike -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500997] The percentage of brightness slider does not sync with OSD settings
https://bugs.kde.org/show_bug.cgi?id=500997 --- Comment #2 from BryanLiang --- I found a similar bug report: https://bugs.kde.org/show_bug.cgi?id=470106. But if so, the bug should have been fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500797] kwin_wayland crashes on login with ASSERT: "m_pending.crtc" in file ./src/backends/drm/drm_pipeline.cpp, line 53
https://bugs.kde.org/show_bug.cgi?id=500797 --- Comment #20 from Daniel Petrov --- Created attachment 179265 --> https://bugs.kde.org/attachment.cgi?id=179265&action=edit drm_info for HP Zbook 15u G5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 501324] New: Switching source or turning off monitor results in loss of video output.
https://bugs.kde.org/show_bug.cgi?id=501324 Bug ID: 501324 Summary: Switching source or turning off monitor results in loss of video output. Classification: Plasma Product: plasmashell Version: 6.3.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: ch...@stringerhome.net CC: natalie_clar...@yahoo.de Target Milestone: 1.0 SUMMARY When I change sources or turn off my monitor, I am unable to return to my KDE desktop. The monitor reports that there is no signal. This behavior has been present since Nobara/FC 39 and has followed me through version upgrades. STEPS TO REPRODUCE 1. Be running on an nvidia card attached to a Dell u4025qw via HDMI or DisplayPort. 2. Change the source to any other source OR turn off the monitor. 3. Return to work and turn on the monitor, you will see no video signal. OBSERVED RESULT No video output. EXPECTED RESULT Video output. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Nobara 41 (fedora 41) KDE Plasma Version: 6.3.2-1.fc41 KDE Frameworks Version: not sure what you want here. Qt Version: 1:4.8.7-77.fc41 ADDITIONAL INFORMATION >From journalctl: Mar 05 20:21:59 chimera polkit-kde-authentication-agent-1[4274]: qt.qpa.wayland: There are no outputs - creating placeholder screen Mar 05 20:21:59 chimera kded6[4197]: qt.qpa.wayland: There are no outputs - creating placeholder screen Mar 05 20:21:59 chimera kactivitymanagerd[4233]: qt.qpa.wayland: There are no outputs - creating placeholder screen Mar 05 20:21:59 chimera kwalletd6[3877]: qt.qpa.wayland: There are no outputs - creating placeholder screen Mar 05 20:21:59 chimera xdg-desktop-portal-kde[4276]: qt.qpa.wayland: There are no outputs - creating placeholder screen Mar 05 20:21:59 chimera maliit-keyboard[4145]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Mar 05 20:21:59 chimera kdeconnectd[4468]: 2025-03-05T20:21:59 qt.qpa.wayland: There are no outputs - creating placeholder screen Mar 05 20:21:59 chimera konsole[5882]: qt.qpa.wayland: There are no outputs - creating placeholder screen Mar 05 20:21:59 chimera DiscoverNotifier[5106]: qt.qpa.wayland: There are no outputs - creating placeholder screen Mar 05 20:21:59 chimera openrgb[4982]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Mar 05 20:21:59 chimera baloorunner[5876]: qt.qpa.wayland: There are no outputs - creating placeholder screen Mar 05 20:21:59 chimera plasmashell[4216]: kde.plasmashell: requesting unexisting screen available rect -1 Mar 05 20:21:59 chimera plasmashell[4216]: kde.plasmashell: requesting unexisting screen available rect -1 Mar 05 20:21:59 chimera plasmashell[4216]: kde.plasmashell: requesting unexisting screen available rect -1 Mar 05 20:21:59 chimera plasmashell[4216]: kde.plasmashell: requesting unexisting screen available rect -1 Mar 05 20:21:59 chimera org_kde_powerdevil[4275]: qt.qpa.wayland: There are no outputs - creating placeholder screen Mar 05 20:21:59 chimera plasmashell[4216]: qt.qpa.wayland: There are no outputs - creating placeholder screen Mar 05 20:21:59 chimera plasmashell[4216]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken. Mar 05 20:21:59 chimera plasmashell[4216]: org.kde.applets.brightness: D-Bus action "KeyboardBrightnessControl" is not available at service "org.kde.Solid.PowerManagement" Mar 05 20:22:00 chimera org_kde_powerdevil[4275]: Delaying 6 seconds to avoid a false disconnect/connect sequence... Mar 05 20:22:06 chimera plasmashell[4216]: org.kde.applets.brightness: D-Bus action "KeyboardBrightnessControl" is not available at service "org.kde.Solid.PowerManagement" Mar 05 20:22:08 chimera org_kde_powerdevil[4275]: stabilized_connector_names required 1 extra calls to get_sysfs_drm_connector_names() -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501326] New: Activating an app on a different virtual desktop always switches to that VD or does nothing
https://bugs.kde.org/show_bug.cgi?id=501326 Bug ID: 501326 Summary: Activating an app on a different virtual desktop always switches to that VD or does nothing Classification: Plasma Product: kwin Version: 6.3.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: sephiroth...@hotmail.it Target Milestone: --- SUMMARY In Plasma 6, the behaviour when activating an application on a different virtual desktop (VD for brevity) falls under three cases: - the app is activated and the VD switches to the one where the app is; - the app is brought to the current VD; - nothing happens. This is true regardless of whether an app activates another (as an example, clicking on a link in Matrix opens a new tab in Firefox) or whether you click on the app's icon in the task manager. However, this is not how it was until Plasma 5. The way it worked was that the setting for application activation was only relevant in the context of an app-based activation; even when set to "nothing happens", clicking on an app's icon in the task manager would activate it and switch the view to the corresponding VD. This was an intuitive implementation of "do nothing" and allowed for cases where you have, as an example, a messaging application on VD1 and a browser on VD2, and having multiple links to click in the messaging application does not force you to do back and forth between VDs, but you can still switch to the browser easily by clicking on its icon in the task manager. The new Plasma 6 behaviour, on the other hand, just looks broken. STEPS TO REPRODUCE 1. Set the virtual desktop behaviour to "do nothing" 2. Click on an application's icon in the task manager OBSERVED RESULT Nothing happens. EXPECTED RESULT The view switches to the application's virtual desktop and the window is brought to the fore. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 499336] Feature request: Include filtered events in search, at least as an option
https://bugs.kde.org/show_bug.cgi?id=499336 Allen Winter changed: What|Removed |Added Version Fixed In||6.4.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501300] Window Decorations take on scale of the farthest left monitor rather than the primary monitor
https://bugs.kde.org/show_bug.cgi?id=501300 --- Comment #3 from sillym...@proton.me --- Created attachment 179277 --> https://bugs.kde.org/attachment.cgi?id=179277&action=edit second png describing the problem -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463301] Lock screen is slow - it takes several seconds for the screen to lock
https://bugs.kde.org/show_bug.cgi?id=463301 Riccardo Robecchi changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #9 from Riccardo Robecchi --- I can still reproduce this, although with Plasma 6.3.2 it is noticeably faster. It still takes 2-3 seconds to lock, which is however much better. I don't know if and how much it would be possible to optimise this further, though, nor if this is what other people normally experience - if it is, feel free to close the bug again. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501300] Window Decorations take on scale of the farthest left monitor rather than the primary monitor
https://bugs.kde.org/show_bug.cgi?id=501300 --- Comment #2 from sillym...@proton.me --- (In reply to TraceyC from comment #1) > Thanks for the screenshot, and the detailed description. > > Since this involves the window decorations, I'm moving it to kwin > The window decorations in the screenshot aren't from Breeze (the current > default theme). Which theme and window decorations are you using? We'll need > that information to try to reproduce this and figure out what's going on. > > Screenshots showing a full application window on the affected display > showing the blurry and clear buttons would also help a lot. > > I tested using the Oxygen theme that has rounded window controls on > git-master but wasn't able to reproduce this with: > Laptop (1920x1080 @100%) > External monitor (3440x1440 @175%) > > I had a window on each monitor, and wasn't able to tell the difference in > the crispness of the window controls on the either monitor, regardless of > which one was to the left. > I also tested with the external monitor at 100 and 125% > > Thanks! Hi! The problem really persists with most third party themes, but in my case, I am using Scratchy (https://store.kde.org/p/1898344/) I would also like to note that, when switching the position of the screens in the system settings, only newly opened windows get affected by the change in scale, while the ones done before the switch remained unaffected As soon as I finish writing this reply, I will also add another attachment with another image showcasing the problem For some reason that's really beyond me, the official themes that come preinstalled with KDE, like breeze, seem to be completely unaffected by this problem. Either that, or they're just too blur-friendly to be noticeable, which I doubt: When hovering over the buttons you get the same circle-type that gets demolished by this bug, but it still looks fine -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 501317] Text copied from XWayland windows is retained in the XWayland clipboard even if this text is removed from Klipper or its history is cleared
https://bugs.kde.org/show_bug.cgi?id=501317 --- Comment #1 from sergeyprotsero...@gmail.com --- Note about the reproduction steps: as written, they assume that the Klipper history is empty at the start of the reproduction. If this doesn't hold, i.e. there is something in Klipper history, merely deleting the current text item from it switches clipboards to the previous item, which, as far as I can tell, works correctly. Clearing Klipper history, however, still reproduces the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Implement real session save/restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #213 from Eugene Savitsky --- Some coverage: https://www.youtube.com/watch?v=UAMAlqqVijY -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 501276] Support HTTP URIs as arguments to the `--local-filename` parameter.
https://bugs.kde.org/show_bug.cgi?id=501276 John Kizer changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||john.ki...@proton.me Resolution|--- |WAITINGFORINFO --- Comment #1 from John Kizer --- Stepping back for a second - could you help articulate your use case for using Discover (a GUI tool) from the command-line in this situation, rather than the CLI package managers that you listed? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501254] Pitch black mouse cursor in HDR mode since upgrade to Mesa 25.0.1
https://bugs.kde.org/show_bug.cgi?id=501254 Zamundaaa changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM CC||xaver.h...@gmail.com --- Comment #1 from Zamundaaa --- Doesn't happen here, on a rx 7900XTX. This is definitely a driver bug, not sure if it's in Mesa or the display driver, but you can report it to Mesa and it'll be moved if necessary: https://gitlab.freedesktop.org/mesa/mesa/-/issues Until it's fixed, you can work around it by setting https://invent.kde.org/plasma/kwin/-/wikis/Environment-Variables#kwin_force_sw_cursor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501272] KWin crashed after entering sleep mode
https://bugs.kde.org/show_bug.cgi?id=501272 TraceyC changed: What|Removed |Added CC||kde...@tlcnet.info --- Comment #2 from TraceyC --- Searchable backtrace Thread 1 (Thread 0x7f97e70ef2c0 (LWP 3460)): [KCrash Handler] #5 KWin::DrmGpu::presentationClock (this=0x689d5e21157e9946) at /usr/src/debug/kwin-6.3.2.1-3.fc41.x86_64/src/backends/drm/drm_gpu.cpp:139 #6 KWin::DrmGpu::pageFlipHandler (fd=19, sequence=0, sec=18334, usec=26, crtc_id=57, user_data=0x7f97bc01e230) at /usr/src/debug/kwin-6.3.2.1-3.fc41.x86_64/src/backends/drm/drm_gpu.cpp:555 #7 0x7f97ed2e1580 in drmHandleEvent (fd=19, evctx=0x7ffe61068810) at ../xf86drmMode.c:1070 #8 0x7f97f0aebc24 in KWin::DrmGpu::dispatchEvents (this=) at /usr/src/debug/kwin-6.3.2.1-3.fc41.x86_64/src/backends/drm/drm_gpu.cpp:570 #9 KWin::DrmCommitThread::handlePing (this=0x55ef5108c2d0) at /usr/src/debug/kwin-6.3.2.1-3.fc41.x86_64/src/backends/drm/drm_commit_thread.cpp:388 #10 0x7f97edb4b9a2 in QObject::event (this=0x55ef5108c2d0, e=0x7f97bc01d490) at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/kernel/qobject.cpp:1418 #11 0x7f97eee3d9b8 in QApplicationPrivate::notify_helper (this=, receiver=0x55ef5108c2d0, e=0x7f97bc01d490) at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/widgets/kernel/qapplication.cpp:3296 #12 0x7f97edaf3590 in QCoreApplication::notifyInternal2 (receiver=0x55ef5108c2d0, event=0x7f97bc01d490) at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/kernel/qcoreapplication.cpp:1172 #13 0x7f97edaf37ed in QCoreApplication::sendEvent (receiver=, event=) at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/kernel/qcoreapplication.cpp:1612 #14 0x7f97edaf6f51 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=data@entry=0x55ef50faa9f0) at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/kernel/qcoreapplication.cpp:1946 #15 0x7f97edcb8b8f in QEventDispatcherUNIX::processEvents (this=0x55ef50fc9600, flags=...) at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/kernel/qeventdispatcher_unix.cpp:418 #16 0x7f97ee8cabf2 in QUnixEventDispatcherQPA::processEvents (this=, flags=...) at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/gui/platform/unix/qunixeventdispatcher.cpp:27 #17 0x7f97edb00993 in QEventLoop::exec (this=this@entry=0x7ffe61068bb0, flags=..., flags@entry=...) at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/global/qflags.h:34 #18 0x7f97edafbf6e in QCoreApplication::exec () at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/global/qflags.h:74 #19 0x7f97ee2d7d3d in QGuiApplication::exec () at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/gui/kernel/qguiapplication.cpp:1975 #20 0x7f97eee3d929 in QApplication::exec () at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/widgets/kernel/qapplication.cpp:2564 #21 0x55ef249e8753 in main (argc=, argv=) at /usr/src/debug/kwin-6.3.2.1-3.fc41.x86_64/src/main_wayland.cpp:622 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484722] Drag and Drop App from icon task bar in desired Activity not working (move to activity or copy to activity)
https://bugs.kde.org/show_bug.cgi?id=484722 aapm_px...@yahoo.com changed: What|Removed |Added CC||aapm_px...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 495878] Customizing the default view settings doesn't work anymore
https://bugs.kde.org/show_bug.cgi?id=495878 --- Comment #82 from BananasGoMoo --- (In reply to Méven Car from comment #81) > > I'm fine with this, but just letting you know, in case this is not the > > desired behavior. > > That's expected, the defaults with data on disk are just a way to save space > and the format must not change or view properties will change for folders > with user view properties set, depending on the new defaults the user has > selected, that would feel unexpected. > > I have backported the fix to 24.12 branch so the next bug fix release will > ship with it 24.12.3. > https://invent.kde.org/system/dolphin/-/commit/ > 092916a3113ad55ca74a21b0bf6b1e20c98ed92c > > BananasGoMoo whenever you update to Dolphin 24.12.3, if you can't confirm > the bug is fixed for you, please open a NEW bug then with a reference to > this one. I can confirm today that as of 24.12.3, this bug has been fixed for me as well. I will not be needing to open another ticket. Thank you for your work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500433] Fullscreen applications flicker if the cursor moves between displays
https://bugs.kde.org/show_bug.cgi?id=500433 --- Comment #11 from Tom Dzmelyk --- Created attachment 179280 --> https://bugs.kde.org/attachment.cgi?id=179280&action=edit kscreendoctor output I am using a 7700XT. The only difference between the kscreendoctor ouput with or without the 1080p monitor is geometry/enabled/priority values. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501329] When width of surface multipled by fractional scaling value are certain values, fonts are blurry in kitty
https://bugs.kde.org/show_bug.cgi?id=501329 Kelvie Wong changed: What|Removed |Added Summary|When width of surface |When width of surface |multipled by fractional |multipled by fractional |scaling value is a certain |scaling value are certain |value, fonts are blurry in |values, fonts are blurry in |kitty |kitty -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501329] New: When width of surface multipled by fractional scaling value is a certain value, fonts are blurry in kitty
https://bugs.kde.org/show_bug.cgi?id=501329 Bug ID: 501329 Summary: When width of surface multipled by fractional scaling value is a certain value, fonts are blurry in kitty Classification: Plasma Product: kwin Version: 6.3.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: kel...@kelvie.ca Target Milestone: --- SUMMARY I reported this to kitty, and the developer there said this is likely a compositor issue. I can help fix this if someone can point me to the right direction (I've contributed a bugfix to kwin a long time ago in the past!) https://github.com/kovidgoyal/kitty/issues/8429 STEPS TO REPRODUCE 1. Set fractional scaling to 1.25x (e.g. using kscreen-doctor output.DP-1.scale."1.25" ) 2. Resize the window so that the surface width, when multipled by the scaling factor, ends up .00, .50, or 0.75 3. notice the blurry fonts This is all in the github bug above, with screenshots and logs. I also put some debug statements in kwin (I think I have the right spot), and as far as I can tell, kwin and kitty both agree on the pixel-perfect size of the buffer. As a workaround, I've been setting the screen scale to 1.26 (which actually gets set as 1.2583), presumably so it's a lot less likely to run into whatever rounding error is causing this. OBSERVED RESULT Blurry fonts EXPECTED RESULT Not blurry fonts SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4090 ADDITIONAL INFORMATION See the bug in: https://github.com/kovidgoyal/kitty/issues/8429 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481177] Tabbox leave residue on screen with fall apart effect when switching virtual desktps
https://bugs.kde.org/show_bug.cgi?id=481177 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from fanzhuyi...@gmail.com --- fixed as of master -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 500354] visual artifacts when scrolling to bottom of list of files when additional info tags visible
https://bugs.kde.org/show_bug.cgi?id=500354 --- Comment #3 from Bug Janitor Service --- 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read 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 489813] While Watching YouTube Videos, Audio System Resets or Crashes
https://bugs.kde.org/show_bug.cgi?id=489813 TraceyC changed: What|Removed |Added Version|unspecified |6.1.2 Product|kde |plasmashell Target Milestone|--- |1.0 Assignee|unassigned-b...@kde.org |plasma-b...@kde.org CC||isma...@gmail.com, ||kde...@tlcnet.info Component|general |Audio in general Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from TraceyC --- If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 501330] New: driver not loaded for mysql
https://bugs.kde.org/show_bug.cgi?id=501330 Bug ID: 501330 Summary: driver not loaded for mysql Classification: Applications Product: digikam Version: 8.5.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Database-Mysql Assignee: digikam-bugs-n...@kde.org Reporter: b...@expander.net.au Target Milestone: --- unable to get digikam working with a maria db instance running elsewhere in my network. The dreaded "Driver not loaded" error occurs. I am mystified. How do I install the driver ? I searched and tried a few things but no luck. Looked for a qt6 driver package... but no joy. I am running digikam on a manjaro (arch) rolling release... so is fairly new. What am I missing ? Is this behaviour by design ? Or is there a missing documentation peice for this? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 501041] Common Actions shortcuts doesn't have "Find Action"
https://bugs.kde.org/show_bug.cgi?id=501041 fanzhuyi...@gmail.com changed: What|Removed |Added Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444747] automatically remove newlines from filenames when renaming
https://bugs.kde.org/show_bug.cgi?id=444747 fanzhuyi...@gmail.com changed: What|Removed |Added CC||the.9a3e...@gmail.com --- Comment #7 from fanzhuyi...@gmail.com --- *** Bug 501303 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 490827] kioworker crashes in ThumbnailProtocol::get() when save dialog is open
https://bugs.kde.org/show_bug.cgi?id=490827 Ash changed: What|Removed |Added CC||ashleysom...@gmail.com --- Comment #27 from Ash --- I'm seeing this bug in Signal too, I'm using the Signal-desktop Flatpak. As Laura said, I think this started happening around the end of January. Downloading files worked fine before that. I am seeing this error in journalctl: --- xdg-desktop-portal-kde: ASSERT failure in PreviewJobPrivate::getOrCreateThumbnail: "Local path for url file:./.cache is not absolute: ./.cache", file ./src/gui/previewjob.cpp, line 716 --- I'm on KDE Neon, relevant installed packages: kf6-kio: 6.11.0+p24.04+vstable+git20250303.0733-0 xdg-desktop-portal-kde: 6.3.2+p24.04+vstable+git20250225.1925-0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501311] New: Enabling an effect in the bottom right corner disables top left corner
https://bugs.kde.org/show_bug.cgi?id=501311 Bug ID: 501311 Summary: Enabling an effect in the bottom right corner disables top left corner Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Hotcorners and edges Assignee: kwin-bugs-n...@kde.org Reporter: sephiroth...@hotmail.it Target Milestone: --- SUMMARY Enabling an effect in the bottom right corner makes the top left corner not work: the corner lights up, but the effect simply does not work. It keeps on not working until KWin is restarted. STEPS TO REPRODUCE 1. Set "Overview" in the top left corner. 2. Set another effect (e.g. "Grid") in the bottom right corner. 3. Try to trigger the Overview effect by moving your mouse to the top left corner. OBSERVED RESULT The effect does not work. EXPECTED RESULT The effect works. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION This is on X11. I haven't tested on Wayland (because I don't use it). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488692] Error: Could not find the system's available locales using the localectl tool.
https://bugs.kde.org/show_bug.cgi?id=488692 Justin Zobel changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- CC||jus...@kde.org Platform|NixOS |postmarketOS Version|6.0.5 |master Ever confirmed|0 |1 --- Comment #4 from Justin Zobel --- I found this when about to the same issue. postmarketOS latest git master build. which localectl /usr/bin/localectl localectl is definitely available. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 501130] Selecting Clipboard history items with non-Latin characters, then pasting, sometimes results in escaped numeric references replacing the characters
https://bugs.kde.org/show_bug.cgi?id=501130 John Kizer changed: What|Removed |Added Ever confirmed|0 |1 Summary|Clipboard history replaces |Selecting Clipboard history |non-Latin characters with |items with non-Latin |an escape sequence |characters, then pasting, ||sometimes results in ||escaped numeric references ||replacing the characters Status|REPORTED|CONFIRMED --- Comment #4 from John Kizer --- I can reproduce that the first time I select such an item in the clipboard history, it pastes the numeric references to the Unicode characters, instead of the characters themselves. If I go back and re-select the same entry, it then subsequently pastes normally. This is on Fedora KDE 41, Plasma 6.3.2. I tried both KWrite and Firefox as the destinations to paste into, both giving the same results. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500492] Widgets are blank (no content) after a reboot, or sleep/wake cycle
https://bugs.kde.org/show_bug.cgi?id=500492 --- Comment #9 from Bug Janitor Service --- 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read 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.
[okular] [Bug 499645] Okular hasn`t functions like in acrobat
https://bugs.kde.org/show_bug.cgi?id=499645 --- Comment #3 from Bug Janitor Service --- 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read 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.
[krusader] [Bug 500670] Krusader becomes unusable (freezing all the time), after using SMB once
https://bugs.kde.org/show_bug.cgi?id=500670 --- Comment #3 from Bug Janitor Service --- 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read 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 489898] Bug/Enhancement: Use PAM failed login timeout or allow its configuration
https://bugs.kde.org/show_bug.cgi?id=489898 --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/2878 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 501328] The results of esveral runners (e.g. commands, unitconverter) are not keyboard-accessible in Application Dashboard
https://bugs.kde.org/show_bug.cgi?id=501328 cwo changed: What|Removed |Added CC||cwo@posteo.net Status|REPORTED|CONFIRMED Summary|Searching for command in|The results of esveral |Application Dashboard |runners (e.g. commands, |doesn't get highlighted |unitconverter) are not |when appearing and arrow|keyboard-accessible in |keys are disabled (mouse|Application Dashboard |needed) | Ever confirmed|0 |1 --- Comment #3 from cwo --- Can confirm, also for several of the other runners. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 474472] MySQL doesn't support modern caching_sha2_password
https://bugs.kde.org/show_bug.cgi?id=474472 leo zhen changed: What|Removed |Added CC||lzhen@outlook.com --- Comment #7 from leo zhen --- showing again for digikam in macos (digiKam-8.5.0-Qt6-MacOS-arm64) when connecting to a MySQL 8.4.3 server ``` Database connection test was not successful. Error was: Plugin caching_sha2_password could not be loaded: dlopen(/opt/digikam.org.arm64/lib/mariadb-10.11/plugin/caching_sha2_password.so, 0x0002): tried: '/opt/digikam.org.arm64/lib/mariadb-10.11/plugin/caching_sha2_password.so' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/opt/digikam.org.arm64/lib/mariadb-10.11/plugin/caching_sha2_password.so' (no such file), '/opt/digikam.org.arm64/lib/mariadb-10.11/plugin/caching_sha2_password.so' (no such file) QMYSQL: Unable to connect ``` -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 499787] Support xdg-document-portal
https://bugs.kde.org/show_bug.cgi?id=499787 --- Comment #7 from Ilya Fedin --- Apparently the latter given that https://github.com/flatpak/xdg-desktop-portal/issues/472#issuecomment-614701580 links the PR changing the logic to the current state. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501311] Enabling an effect in the bottom right corner disables top left corner
https://bugs.kde.org/show_bug.cgi?id=501311 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- fwiw cannot reproduce on wayland, master build -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 501330] driver not loaded for mysql
https://bugs.kde.org/show_bug.cgi?id=501330 caulier.gil...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED CC||caulier.gil...@gmail.com Resolution|--- |NOT A BUG Version Fixed In||8.6.0 Platform|Other |Manjaro --- Comment #1 from caulier.gil...@gmail.com --- The mysql "driver" is a Qt plugin loading dynamically on demand at run time. plugin is .so file installed on your system. So your Manjaro must provide the famous plugin to work. Under Ubunto the package is named "libqt6sql6-mysql" https://doc.qt.io/qt-6/sql-driver.html So, it's a packaging problem, not digiKam... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393781] Add option for wallpaper to span multiple screens
https://bugs.kde.org/show_bug.cgi?id=393781 django...@nobodiesfool.com changed: What|Removed |Added CC||django...@nobodiesfool.com --- Comment #9 from django...@nobodiesfool.com --- I support the request too. I miss the single desktop that spans multiple monitors since the days, xinerama has gone. I use 3 monitors in portrait mode and I would not only be happy about a common background, but also about the ability to maximize a window across all monitors. I know that the opponents of the shared desktop argue with the different monitor sizes that may be supported. I would therefore be happy if the shared desktop would be optional, so that each user may decide for themselves whether they want it or not. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 499336] Feature request: Include filtered events in search, at least as an option
https://bugs.kde.org/show_bug.cgi?id=499336 Allen Winter changed: What|Removed |Added Latest Commit|https://invent.kde.org/pim/ |https://invent.kde.org/pim/ |korganizer/-/commit/f70c524 |korganizer/-/commit/2233d47 |086ea7697e3ba3fb0cecfb3a738 |a34937b5e98edac6a60bfc2d4f2 |858854 |990dd3 --- Comment #3 from Allen Winter --- Git commit 2233d47a34937b5e98edac6a60bfc2d4f2990dd3 by Allen Winter. Committed on 10/03/2025 at 19:18. Pushed by winterz into branch 'release/25.04'. Add a search option to consider the current view filter By default, the current view filter is ignored when searching. The user can override that. (cherry picked from commit f70c524086ea7697e3ba3fb0cecfb3a738858854) Co-authored-by: Allen Winter M +37 -7src/dialog/searchdialog.cpp M +38 -22 src/ui/searchdialog_base.ui https://invent.kde.org/pim/korganizer/-/commit/2233d47a34937b5e98edac6a60bfc2d4f2990dd3 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 501321] New: Improve Cut Clip Functionality to Respect Track Activation States User Story
https://bugs.kde.org/show_bug.cgi?id=501321 Bug ID: 501321 Summary: Improve Cut Clip Functionality to Respect Track Activation States User Story Classification: Applications Product: kdenlive Version: 24.12.2 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Timeline & Editing Assignee: j...@kdenlive.org Reporter: rockinj...@gmail.com Target Milestone: --- As a video editor, I want the "Cut Clip" or Razor Clip function to respect the active/inactive state of video and audio tracks, so that I can place edit points on individual tracks without unintentionally modifying inactive tracks. Acceptance Criteria 1. The "Cut Clip" function should only affect tracks that are marked as active. 2. Inactive tracks must remain unaffected when the "Cut Clip" function is applied. 3. The user interface should clearly indicate which tracks are active and will be affected by the "Cut Clip" function. 4. Behaviour should align intuitively with the purpose of the track active/inactive selectors to avoid confusion. Additional Notes Ensure that changes in functionality do not affect overall application performance. Provide appropriate warnings or tooltips if a user attempts to perform a cut on tracks with mixed activation states. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Implement real session save/restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #212 from Eugene Savitsky --- https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/18 I believe this is the protocol of the topic. Turned 5 years now. Hurray, happy anniversary! :-/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500316] Window header does not scale with X11
https://bugs.kde.org/show_bug.cgi?id=500316 --- Comment #12 from Bug Janitor Service --- 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read 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.
[kleopatra] [Bug 499697] Crfeated public and private pgp used them then logged in again and were gone
https://bugs.kde.org/show_bug.cgi?id=499697 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. Closing as RESOLVED WORKSFORME. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 499865] Kate will crash if accessing a text file on the network and the network goes down
https://bugs.kde.org/show_bug.cgi?id=499865 --- Comment #10 from Bug Janitor Service --- 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read 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.
[frameworks-kauth] [Bug 500644] Laptop does not suspend when lid closed and says authentication is required to suspend the system. lmao bravo
https://bugs.kde.org/show_bug.cgi?id=500644 --- Comment #2 from Bug Janitor Service --- 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read 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.
[dolphin] [Bug 444747] automatically remove newlines from filenames when renaming
https://bugs.kde.org/show_bug.cgi?id=444747 fanzhuyi...@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 501303] Strip out newlines and other control/special characters when pasting a filename from clipboard
https://bugs.kde.org/show_bug.cgi?id=501303 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from fanzhuyi...@gmail.com --- *** This bug has been marked as a duplicate of bug 444747 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493679] Plasmashell crash on gpu reset with AMD GPUs
https://bugs.kde.org/show_bug.cgi?id=493679 TraceyC changed: What|Removed |Added CC||ad...@mailbox.org --- Comment #18 from TraceyC --- *** Bug 501250 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 501299] New: KDevelop window size resets to a strange 966x768 after exiting debug mode
https://bugs.kde.org/show_bug.cgi?id=501299 Bug ID: 501299 Summary: KDevelop window size resets to a strange 966x768 after exiting debug mode Classification: Applications Product: kdevelop Version: 6.1.241203 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: noctaliavib...@gmail.com Target Milestone: --- SUMMARY Whenever I use debug mode, exiting debug mode causes the main KDevelop window to reset to the aforementioned resolution. Its annoying but not a deal breaker. STEPS TO REPRODUCE 1. open a project (I am using a meson one but it also occurs for me on cmake projects) 2. debug the project (this is sometimes a pain in the ass with meson) 3. stop debugging (either close the app or force stop debugging) OBSERVED RESULT Window resets to 966x768 on primary monitor, even when maximised or if there are KWin application/window rules set to force a different resolution. EXPECTED RESULT Window size does not reset. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.13.6-2-cachyos-deckify (64-bit) KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 501296] Security issue: no screen locking at all
https://bugs.kde.org/show_bug.cgi?id=501296 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||fanzhuyi...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #1 from fanzhuyi...@gmail.com --- > kscreenlocker_greet: [PAM worker kde] Authenticate: Starting authentication > kscreenlocker_greet: [PAM worker kde-fingerprint] Authenticate: Starting > authentication > kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Starting > authentication > kscreenlocker_greet: [PAM worker kde-smartcard] Message: Info message: > auth=authinfo_unavail > kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Authentication > done, result code: 9 (Authentifizierungsdienst kann > Authentifizierungsinformationen nicht abrufen) > kscreenlocker_greet: [PAM worker kde] Authenticate: Authentication done, > result code: 0 (Erfolg) It seems that authentication is started and succeeds. Could you check if you have any custom pam configuration that might be messing things up? Also testing if you could reproduce in a clean user account would be super helpful. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 501257] People are not recognized
https://bugs.kde.org/show_bug.cgi?id=501257 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #3 from Maik Qualmann --- It is possible that the confirmed images are of too poor quality (blurry, too small, etc.), these are now filtered out and not added to the training. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 501285] New: kscreenlocker (sometimes) crashes when screen turns off/on
https://bugs.kde.org/show_bug.cgi?id=501285 Bug ID: 501285 Summary: kscreenlocker (sometimes) crashes when screen turns off/on Classification: Plasma Product: plasmashell Version: git-stable-Plasma/6.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Screen locking Assignee: plasma-b...@kde.org Reporter: knights_of...@gmx.com Target Milestone: 1.0 SUMMARY So, I know that this is not quite a full bug report with a nice backtrace yet, but I need some help to get there because I'm running out of ideas. Here is what I got so far: - This bug is hardware-specific. I get it on one machine (desktop using an AMD Ryzen 5 5600G's integrated graphics, connected to a Philips 272B7QPTK screen) but not on another (MSI Alpha A4DEK laptop using an AMD Ryzen 7 4800H + RX 5600M hybrid setup + unknown screen model), with otherwise similar hardware configuration. - This bug is related to GPU or screen power management. In the default powerdevil configuration, where the screen automatically turns off, when I wake up the computer I face the message telling me that I need to log in to a VT and run "loginctl unlock-session 2" to unlock the screen. And in journalctl, it says that kscreenlocker_greet segfaulted. If I disable screen poweroff, then the bug never happens, however long I keep the login screen on. I sometimes manage to reproduce the bug by running "sleep 10 && kscreen-doctor --dpms off" on one terminal and "/usr/lib/kscreenlocker_greet --testing" on another terminal, but not always, and it's not clear to me what are the precise circumstances that cause it to trigger. This makes it harder for me to analyze the bug further. - This bug is not related to libddc. Although there were tons of promising libddc warnings/errors in the journalctl logs, turning off libddc as directed by the powerdevil readme silences the warnings but does not stop the crashes. Along the way, I also tried to increase the powerdevil log verbosity as directed in the powerdevil readme, but that did not turn up anything useful. - This bug comes from some sort of memory corruption. One time I managed to get /usr/lib/kscreenlocker_greet to reproduce the bug under GDB, which gave me a stack trace where the code was attempting to dereference a QWeakPointer with a target address of 0x6d1 or something blatantly invalid like that. I hoped to find out who overwrote the address of that pointer with rr, but the bug does not reproduce under either rr or valgrind. That being said, valgrind does report many out-of-bounds issues in KSVG, but judging by the very different memory addresses and the fact that these errors are reported even if the screen does not turn off, this seems to be an unrelated issue. STEPS TO REPRODUCE 1. Get the same hardware as I do? 2. Set "Shutdown screen after..." to anything other than "Never" in powerdevil. 3. Wait for screen to lock and turn off, maybe some extra time (it seems the crash is not always right at the point where the screen turns off). OBSERVED RESULT Wiggle mouse, face a kscreenlocker crash report, need to switch to VT to get back to my desktop. EXPECTED RESULT Screen locker shows up normally and lets me unlock my session without dirty VT tricks. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics Memory: 62.2 Gio of RAM Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION I reliably get a plasma shell crash report dialog on the same system when resuming from sleep. I do not know if this is related or not. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 496802] Kate opens with Breeze Light colors in LXQt despite having Breeze Dark chosen in KDE System Settings
https://bugs.kde.org/show_bug.cgi?id=496802 --- Comment #33 from Harshit Tomar --- Awesome! I hope your PR gets merged soon -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 501285] kscreenlocker (sometimes) crashes when screen turns off/on
https://bugs.kde.org/show_bug.cgi?id=501285 Hadrien G. changed: What|Removed |Added CC||knights_of...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 501159] Lock Key Status indicator in system tray no longer shows the "input-combo-on" icon when appropriate
https://bugs.kde.org/show_bug.cgi?id=501159 Vlad Zahorodnii changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/-/commit/f68d21cbc6 |ma/kwin/-/commit/78491e5a34 |0f693c689d7b7ac212ee793f537 |95a2319e47dae5a83c873c79acf |c6e |8f3 --- Comment #4 from Vlad Zahorodnii --- Git commit 78491e5a3495a2319e47dae5a83c873c79acf8f3 by Vlad Zahorodnii. Committed on 10/03/2025 at 07:12. Pushed by vladz into branch 'Plasma/6.3'. xkb: Fix reporting state for multiple modifiers We need to check all modifiers and combine the result, not abort after the first active one (cherry picked from commit f68d21cbc60f693c689d7b7ac212ee793f537c6e) Co-authored-by: Nicolas Fella M +36 -18 src/xkb.cpp https://invent.kde.org/plasma/kwin/-/commit/78491e5a3495a2319e47dae5a83c873c79acf8f3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491751] On Wayland Full system freeze with kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
https://bugs.kde.org/show_bug.cgi?id=491751 Igor Murzich changed: What|Removed |Added CC||imurz...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 501257] People are not recognized
https://bugs.kde.org/show_bug.cgi?id=501257 --- Comment #5 from Andy --- Hi! I can't download 8.5.0. Nothing happens. I've tried three browsers. https://www.digikam.org/download/ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 499787] Support xdg-document-portal
https://bugs.kde.org/show_bug.cgi?id=499787 --- Comment #3 from David Redondo --- I think having per app default apps might be a bit too much to show in the UI. I had a look at this and I think it might no even be needed. - if a mime type has a default app the portal will use that - the app forces to show the app choosing dialog => nothing to do the dialog will always be shown. - the case that some mime type doesnt have a default app - in the case the user selects "remember" => go to 1 - if the user doesn't select a default app, the portal will keep asking a defined number of times and then stop asking, this is where this would matter - the number of times the portal should ask is saved in the permission store, we could just increase that number to some incredibly high number or even reset the number of times it has asked in the past from the portal impl to sidestep this problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 501253] plasmashell crashes usually after screen unlock
https://bugs.kde.org/show_bug.cgi?id=501253 cwo changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||cwo@posteo.net --- Comment #2 from cwo --- This has a trace matching bug 483134, which itself was identified as a duplicate of 414805. We believe that this is fixed with Qt 6/Plasma 6. *** This bug has been marked as a duplicate of bug 414805 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466380] kwin_x11 crashes in KWin::X11Window::finishCompositing() when disabling compositing
https://bugs.kde.org/show_bug.cgi?id=466380 Vlad Zahorodnii changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/6e3b8e407e ||da65a12c43afb9651fc284c6f15 ||4d6 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #45 from Vlad Zahorodnii --- Git commit 6e3b8e407eda65a12c43afb9651fc284c6f154d6 by Vlad Zahorodnii. Committed on 10/03/2025 at 07:13. Pushed by vladz into branch 'Plasma/5.27'. effect: Prevent QJSEngine garbage collecting EffectWindow EffectWindow has no parent so QJSEngine can garbage collect an instance if it's returned by a function marked with Q_INVOKABLE. M +2-0src/effects.cpp https://invent.kde.org/plasma/kwin/-/commit/6e3b8e407eda65a12c43afb9651fc284c6f154d6 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 443168] Add a setting to not follow sorting as in Dolphin when Gwenview started by image click
https://bugs.kde.org/show_bug.cgi?id=443168 Quincy changed: What|Removed |Added CC||bbc.qui...@gmx.de --- Comment #33 from Quincy --- Using gwenview for many years now and never observed that it somehow follows dolphin's settings for sorting. The only thing I encountered recently (version 24.08.x and still with 24.12.2) was that the "sort by" setting does not match with the actual sorting of files (e.g. files are sorted by name, but date is selected). If I clicked on the already selected setting again sorting gets updated accordingly, so it looked like a bug which finally brought me here to learn that the whole thing is not a bug, but a feature... My thoughts on this: - The selected settings should somehow make clear what the *current* sorting is. It is very misleading seeing "sort by date" being selected, but not actually being executed - I can see the link to dolphin feature to be of use for some people, but there should be at least a way to opt out - If possible the feature should only be active if gwenview is really started from dolphin as having it started e.g. from command line with some arbitrary directory it is even more misleading to not have sorting matching the displayed setting. The suggestion of having some option during invocation given above would be a way to implement this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #61 from Chan --- (In reply to Faidon Liambotis from comment #56) > I, too, am suffering from an increased memory usage from kwin to the point > of OOM, with resident memory often being at the 1.5G mark. > > However, unlike most (all?) reporters here I do not have a multi-GPU setup, > but rather just a regular single-GPU Intel TigerLake laptop. I am usually > connected to an external monitor, but when I do, my settings are configured > to turn the laptop screen off, so I wouldn't even call it "multi-monitor" > per se. > > No idea if this is the same bug as others have reported here or an entirely > separate one. > > This is with Debian trixie, KWin 6.3.0, Wayland, HiDPI external monitor > (scaling factor 2). > > I can find my way around gdb and Valgrind, so if you have any tips on how to > best debug this, I'd love to hear them! Ok, so I am not the only one with just an iGPU facing this OOM situation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 501285] kscreenlocker (sometimes) crashes when screen turns off/on
https://bugs.kde.org/show_bug.cgi?id=501285 --- Comment #1 from Hadrien G. --- ...ah, sorry, when I wrote "otherwise similar hardware configuration above", I meant "otherwise similar **software** configuration". I switched both to Arch recently and configured them in a very similar fashion, basically taking my notes from setting up one machine to set up the other. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #62 from Chan --- Is anyone here facing this issue while running the 6.6 LTS kernel? I somehow don't face this problem when I am running the 6.6 LTS kernel. I have run the same setup (just the latest KDE 6.3.2 and Frameworks) for a week straight (no reboots) with an external monitor connected, just on the 6.6 LTS kernel, and didn't face an OOM. As such, I am now running the 6.6 LTS for the daily usage, and it's running normally with no issues. So maybe even though it's still kwin_wayland (or kwin_wayland_wrapper?) that eventually fills the memory to the point of OOM, but it's somehow an upstream kernel issue? Can someone else check this or is this a separate issue for me, and I am lucky it doesn't happen on 6.6 LTS? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499423] Non-Qt XWayland apps don't ask for confirmation/saving on logout
https://bugs.kde.org/show_bug.cgi?id=499423 David Redondo changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #7 from David Redondo --- Nothing we can do there then. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 501257] People are not recognized
https://bugs.kde.org/show_bug.cgi?id=501257 --- Comment #6 from Andy --- Forget it. The blue button at the top right just links to the page. Phew. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 501286] Constant crash of kaccess when turning on/off "Use number pad to move cursor"
https://bugs.kde.org/show_bug.cgi?id=501286 Yaroslav Sidlovsky changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=478620 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 501286] Constant crash of kaccess when turning on/off "Use number pad to move cursor"
https://bugs.kde.org/show_bug.cgi?id=501286 --- Comment #1 from Yaroslav Sidlovsky --- Output from the console: ```$ systemsettings kcm_access 47.3 Comparing requested interface name QX11Application with available QX11Application Match for interface QX11Application. Comparing revisions (requested 1 / available 1) Full match. Returning dynamic cast of QXcbNativeInterface(0x55a1c6c6bb30) KCrash: Application '[U' crashing... crashRecursionCounter = 2 ``` -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 496802] Kate opens with Breeze Light colors in LXQt despite having Breeze Dark chosen in KDE System Settings
https://bugs.kde.org/show_bug.cgi?id=496802 --- Comment #34 from Ilya Fedin --- I have a feel qt6ct author is going to ignore it again. He ignored it for half a year before github suspended his account. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 494071] Clicking on system tray icon does not open main window, "Restore" missing from context menu
https://bugs.kde.org/show_bug.cgi?id=494071 Jonathan Marten changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||akregator/-/commit/37472c0e ||2ffbf539b697888ed1131571a6a ||231e3 Status|ASSIGNED|RESOLVED --- Comment #6 from Jonathan Marten --- Git commit 37472c0e2ffbf539b697888ed1131571a6a231e3 by Jonathan Marten. Committed on 10/03/2025 at 08:10. Pushed by marten into branch 'master'. Re-register the MainWindow with the system tray icon if its window handle changes This is initially set as the KStatusNotifierItem's associated window, but further on during startup the window gets destroyed and recreated. This happens during the initialisation of the article viewer, somewhere deep within QWebEngine. Since the KStatusNotifierItem retains the associated window using its window handle, that association is lost. The symptom is that the tray icon menu does not have a "Restore" item and clicking on the icon does not open the main window. The event filter monitors the MainWindow's window handle and, if it changes (either during startup or while running) for any reason, re-registers it as the tray icon's associated window. M +27 -3src/main.cpp https://invent.kde.org/pim/akregator/-/commit/37472c0e2ffbf539b697888ed1131571a6a231e3 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 494071] Clicking on system tray icon does not open main window, "Restore" missing from context menu
https://bugs.kde.org/show_bug.cgi?id=494071 Jonathan Marten changed: What|Removed |Added Latest Commit|https://invent.kde.org/pim/ |https://invent.kde.org/pim/ |akregator/-/commit/37472c0e |akregator/-/commit/4d04eedb |2ffbf539b697888ed1131571a6a |66483725974f807b1d39aed9152 |231e3 |3b674 --- Comment #7 from Jonathan Marten --- Git commit 4d04eedb66483725974f807b1d39aed91523b674 by Jonathan Marten. Committed on 10/03/2025 at 08:11. Pushed by marten into branch 'release/25.04'. Re-register the MainWindow with the system tray icon if its window handle changes This is initially set as the KStatusNotifierItem's associated window, but further on during startup the window gets destroyed and recreated. This happens during the initialisation of the article viewer, somewhere deep within QWebEngine. Since the KStatusNotifierItem retains the associated window using its window handle, that association is lost. The symptom is that the tray icon menu does not have a "Restore" item and clicking on the icon does not open the main window. The event filter monitors the MainWindow's window handle and, if it changes (either during startup or while running) for any reason, re-registers it as the tray icon's associated window. (cherry picked from commit 37472c0e2ffbf539b697888ed1131571a6a231e3) M +27 -3src/main.cpp https://invent.kde.org/pim/akregator/-/commit/4d04eedb66483725974f807b1d39aed91523b674 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 501217] Confirm faces - same processes in the background
https://bugs.kde.org/show_bug.cgi?id=501217 Maik Qualmann changed: What|Removed |Added Version Fixed In||8.6.0 Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from Maik Qualmann --- I don't see any errors in the debug logs. We just need to load the image to create the face thumbnail. This may use a different image loading method than what is set in the view (fast preview, full preview or RAW image). We also need to loop through the file to create a new unique file UUID since adding metadata has changed the file etc. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501241] Issue with connection between two Android phones on version 1.33.1
https://bugs.kde.org/show_bug.cgi?id=501241 --- Comment #5 from Matej --- Thank you Albert, I created file based on Linux Ubuntu and Android USB cable connection. TXT file is 41 MB. You can find log here on mega.nz cloud https://mega.nz/file/Nnwm1Q4J#u6UjofwGdtyT8RljU-EjWERHbMYcCa9cFmdRnaC8sSE It is without terminal characters limitation. I fully closed KDE connect (closed on background too) and then open again. Turn off Wifi connection on short time. (Main time is Wifi turn on, of course) I used this command: adb shell logcat Is it OK? Of you have any better command for me terminal (for example with any filter), send me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 501294] New: Setting keyboard shortcuts to tray entries only works for the current boot
https://bugs.kde.org/show_bug.cgi?id=501294 Bug ID: 501294 Summary: Setting keyboard shortcuts to tray entries only works for the current boot Classification: Plasma Product: plasmashell Version: 6.3.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray widget Assignee: plasma-b...@kde.org Reporter: im.tech@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY Setting a keyboard shortcut to the notifications entry in the system tray (in my case Meta+A, overriding walk through activities) works and activates the widget, until I reboot, it no longer works despite being registered as "Activate notification widget of plasmashell", however, it doesn't appear again in the entries page, but rather in the keyboard shortcuts page to "activate this widget as though it has been clicked" STEPS TO REPRODUCE 1. Right click system tray, "configure system tray" 2. Entries > pick an entry (in my case notifications) and assign it a keyboard shortcut (in my case Meta + A) 3. Apply, try, it works 4. Reboot 5. No longer works OBSERVED RESULT Should persist EXPECTED RESULT Doesn't persist properly SOFTWARE/OS VERSIONS Linux: 6.13.5-arch1-1 (64-bit) KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 501294] Setting keyboard shortcuts to tray entries only works for the current boot
https://bugs.kde.org/show_bug.cgi?id=501294 Tech-Tac changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=483688 -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 501297] New: Datetime - not all valid Datetime accepted -Version 2.11.80
https://bugs.kde.org/show_bug.cgi?id=501297 Bug ID: 501297 Summary: Datetime - not all valid Datetime accepted -Version 2.11.80 Classification: Applications Product: LabPlot2 Version: latest Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: juergen_liebm...@web.de Target Milestone: --- Hi, i have detected a strange behavior of labplot in the area of datetime: In a spreadsheet with a column with format datetime the input of 2024-03-31 01:55:00 is accepted The input of 2024-03-31 02:00:00 is r converted to 2024-03-31 03:00:00 2024-03-31 02:00:15 in 2024-03-31 03:00:15 and so on. This happen on all values between 2024-03-31 02:00:00 and 2024-03-31 02:59:59, Haven't any guess why this happens. The datetime value is a bigint value of milliseconds since 1970 or so. Good luck for bug hunting! Operating System: openSUSE Tumbleweed-Slowroll 20250205 KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.4-1.0.2.sr20250205-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 14,9 GiB of RAM Graphics Processor 1: Intel® UHD Graphics 620 Graphics Processor 2: NVIDIA GeForce 930MX Manufacturer: HP Product Name: HP ProBook 450 G5 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 499336] Feature request: Include filtered events in search, at least as an option
https://bugs.kde.org/show_bug.cgi?id=499336 Allen Winter changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||korganizer/-/commit/f70c524 ||086ea7697e3ba3fb0cecfb3a738 ||858854 Status|ASSIGNED|RESOLVED --- Comment #2 from Allen Winter --- Git commit f70c524086ea7697e3ba3fb0cecfb3a738858854 by Allen Winter. Committed on 10/03/2025 at 15:47. Pushed by winterz into branch 'master'. Add a search option to consider the current view filter By default, the current view filter is ignored when searching. The user can override that. M +37 -7src/dialog/searchdialog.cpp M +38 -22 src/ui/searchdialog_base.ui https://invent.kde.org/pim/korganizer/-/commit/f70c524086ea7697e3ba3fb0cecfb3a738858854 -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 501325] kinfocenter has a compile-time dependency on QTVulkanInstance, but Qt6 may be built without Vulkan support, handle this gracefully
https://bugs.kde.org/show_bug.cgi?id=501325 --- Comment #2 from Alexander Wessel --- (In reply to Harald Sitter from comment #1) > It's a required feature. Vulkan is now a required feature to compile and run KDE Plasma!? :O That's quite unfortunate news to me. Can you point me to some announcement or something to that effect? Also... Why? It's a just a few lines of conditional code, really... Thanks anyway, Alexander -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500455] Display freezes upon opening fullscreen views if both HDR and "Prefer color accuracy" are enabled
https://bugs.kde.org/show_bug.cgi?id=500455 --- Comment #13 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/7301 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500433] Fullscreen applications flicker if the cursor moves between displays
https://bugs.kde.org/show_bug.cgi?id=500433 Zamundaaa changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REOPENED|NEEDSINFO Component|wayland-generic |platform-drm --- Comment #10 from Zamundaaa --- I don't see this issue on my AMD laptop or desktop PC, with a second display connected or without - switching between direct scanout and compositing doesn't have any visual difference or glitches. Can I get some more details on what hardware you're on? The GPU model and the output of kscreen-doctor -o specifically (In reply to nyikoszoltan0 from comment #9) > Interestingly, I have "shake cursor" enabled, and if I shake the cursor to > magnify it and then move it to the other screen the flicker doesn't happen > until the cursor returns to its normal size. That's because the effect inhibits direct scanout while it's active. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482230] Useless button without label/icon in some dialogs
https://bugs.kde.org/show_bug.cgi?id=482230 --- Comment #9 from Roke Julian Lockhart Beedell <4wy78...@rokejulianlockhart.addy.io> --- (In reply to TraceyC from comment #8) I've not noticed it since I posted my corroborations. I'm using 6.3.2. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 501300] Window Decorations take on scale of the farthest left monitor rather than the primary monitor
https://bugs.kde.org/show_bug.cgi?id=501300 --- Comment #4 from sillym...@proton.me --- (In reply to sillymabs from comment #3) > Created attachment 179277 [details] > second png describing the problem PS: I don't think this problem relates to this bug, but the kde screenshot tool, Spectacle, makes screenshots look blurry, which also makes the navigation bars on screenshots of the problem look better than they are when you're witnessing them first hand. They look a lot worse and the problem is a lot more noticeable than they do in this screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 494522] Powerdevil causes Samsung Odyssey G5 to go on/off repeatedly forever with DDC support enabled
https://bugs.kde.org/show_bug.cgi?id=494522 --- Comment #29 from blumoopjap...@gmail.com --- False alarm from my above comment, fix is still working for me when I did a fresh install of Bazzite KDE this time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451090] When each screen has a Notifications widget, notifications appear on non-primary monitor on Wayland
https://bugs.kde.org/show_bug.cgi?id=451090 Riccardo Robecchi changed: What|Removed |Added CC||sephiroth...@hotmail.it --- Comment #5 from Riccardo Robecchi --- The same happens on X11 as well on Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 501309] Need to scroll for the relevant search result: Better strategy for search result's view needed
https://bugs.kde.org/show_bug.cgi?id=501309 postix changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from postix --- I see, you can add categories to a favorite list and change their order there. -- You are receiving this mail because: You are watching all bug changes.
