[dolphin] [Bug 483784] Super-user file manager can't paste
https://bugs.kde.org/show_bug.cgi?id=483784 Tim Carr changed: What|Removed |Added CC||t...@timcarr.me Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Tim Carr --- Option was available and seemed to work in Plasma 5.27/Dolphin 23.08, so this appears to be a regression. Could possibly be caused by the same issue as bug 482899 but I'll let someone with more experience make that judgement. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483809] Certain special keys on the virtual keyboard don't map to the correct key in Chrome
https://bugs.kde.org/show_bug.cgi?id=483809 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 483786] Incorrect parameter indexing in FreeBSD clock_nanosleep syscall wrapper
https://bugs.kde.org/show_bug.cgi?id=483786 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 483757] KFileWidget creation quits QApplication
https://bugs.kde.org/show_bug.cgi?id=483757 wolf.seif...@web.de changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #3 from wolf.seif...@web.de --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 473957] iPhone can pair with laptop, but upon refreshing it will never be able to connect again.
https://bugs.kde.org/show_bug.cgi?id=473957 bryan.williams7...@gmail.com changed: What|Removed |Added CC||bryan.williams7...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483810] Dynamically start/stop Xwayland
https://bugs.kde.org/show_bug.cgi?id=483810 --- Comment #1 from deresi...@protonmail.ch --- My other option would be to restart the plasma wayland session entirely every time I close or open my VM, but this means that I lose anything that I have opened. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483810] New: Dynamically start/stop Xwayland
https://bugs.kde.org/show_bug.cgi?id=483810 Bug ID: 483810 Summary: Dynamically start/stop Xwayland Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: platform-x11-nested Assignee: kwin-bugs-n...@kde.org Reporter: deresi...@protonmail.ch Target Milestone: --- SUMMARY I want to be able to dynamically start and stop Xwayland. It's helpful for multi GPU VM passthrough since xwayland seems to holds onto my secondary GPU. If Xwayland could be dynamically started and stopped, I would be able to: 1. Run wayland with Xwayland for X11 only apps 2. Stop Xwayland when I start up my GPU passthrough VM 3. Start Xwayland again so that it only uses the GPU which hasn't been passed though to my VM 4. When I stop my VM, I can restart Xwayland again and Xwayland can use both GPUs now 5. All of the above without having to restart kde plasma/kwin_wayland It might also help with optimus on laptops here: https://discuss.kde.org/t/is-there-any-way-to-restart-xwayland-without-closing-session-and-restarting-kwin-wayland/1741 Currently, I have removed the --xwayland option for kwin_wayland_wrapper but this means I don't have support for any X applications at all. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483809] New: Certain special keys on the virtual keyboard don't map to the correct key in Chrome
https://bugs.kde.org/show_bug.cgi?id=483809 Bug ID: 483809 Summary: Certain special keys on the virtual keyboard don't map to the correct key in Chrome Classification: Plasma Product: kwin Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: virtual-keyboard Assignee: kwin-bugs-n...@kde.org Reporter: espi...@gmail.com Target Milestone: --- SUMMARY Please let me know if this is an issue we actually should be reporting with maliit-keyboard or chromium. However, this doesn't seem to occur on Phosh which makes me believe it could be maliit or KWin specific. Original issue: https://invent.kde.org/teams/plasma-mobile/issues/-/issues/283 " If I open Bitwarden on my PinePhonePro using Manjaro and Phosh I can type my email in the login screen, including the period in ".com". If I reboot into pmOS Edge with Plasma 6.0.2 and open BitWarden, when I type in the email address, instead of a period, the keyboard types the > symbol instead. Some other characters type incorrectly as well, eg / becomes ?, \ becomes |, ; becomes :. Notably all the problematic characters seem to be on the bottom row of the keyboard when using the symbol layout. " I did further triaging and all Electron based apps and Chrome itself exhibit this behaviour. It persists when starting Chrome in Wayland as well. STEPS TO REPRODUCE 1. Open Chrome or an Electron app 2. Focus on a text field (bringing up the vkbd) 3. Type "/" OBSERVED RESULT It inputs "?" EXPECTED RESULT It inputs "/" SOFTWARE/OS VERSIONS Linux/KDE Plasma: postmarketOS (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6 Qt Version: 6.6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483808] Widgets on non-floating panels do not function in edges/corners of the screen
https://bugs.kde.org/show_bug.cgi?id=483808 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483808] New: Widgets on non-floating panels do not function in edges/corners of the screen
https://bugs.kde.org/show_bug.cgi?id=483808 Bug ID: 483808 Summary: Widgets on non-floating panels do not function in edges/corners of the screen Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: pallasw...@proton.me CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY *** TL;DR: a single row or column of pixels, at the edge of a panel, are unresponsive to mouse inputs to widgets. I'll do my best to explain, but it might be easier to create a panel, put a widget on the end (right or bottom) of it, move it to each screen edge, and try and click it on its very end. You'll see it fail and get a feel for the problem pretty quick that way. Type example: I have window control via a widget in my panel. Typically for window control, it is in the corner, so that a quick flick of the mouse always hits except with plasma 6, it seems like the widget never reaches the corner, it goes short by one pixel. I tested this with a new empty panel, added an expanding spacer, and an application launcher to put in the corners for testing. I found that for floating panels, the end of the panel always works as expected (even when the panel is floating and the mouse is nowhere near the widget, which is cool and clever...). But, for non-floating panels: * The entire top-left corner and surrounding pixel, work as expected * The bottom-left corner pixel - only that ONE pixel - works. - When the panel is vertical (left side), the subsequent pixels on the X axis (moving left-to-right along the bottom of the display) do not respond. Widgets act as if not hovered, and clicking does nothing. Right-clicking opens a menu as if blank space on the panel was clicked - it opens the panel's context menu. - When the panel is horizontal (bottom) those pixels do work. * The top-right corner pixel - only that ONE pixel - works. - When the panel is horizontal (top side), the subsequent pixels on the Y axis (moving top-to-bottom along the right edge of the display) do not respond. Widgets act as if not hovered, and clicking does nothing. Right-clicking opens a menu as if blank space on the panel was clicked - it opens the panel's context menu. - When the panel is vertical (right side) those pixels do work. * The bottom-right corner pixel never works. - When the panel is vertical (right side), the subsequent pixels on the X axis (moving left-to-right along the bottom of the display) do not respond. Widgets act as if not hovered, and clicking does nothing. Right-clicking opens a menu as if blank space on the panel was clicked - it opens the panel's context menu. - When the panel is horizontal (bottom), the subsequent pixels on the Y axis (moving bottom-to-top along the right edge of the display) do not respond. Widgets act as if not hovered, and clicking does nothing. Right-clicking opens a menu as if blank space on the panel was clicked - it opens the panel's context menu. Alignment does not have any effect (eg aligning a horizontal panel at the bottom edge, to the right, does not make the rightmost column of pixels work) *** STEPS TO REPRODUCE 1. Create a traditional Windows-style bottom panel, with Application launcher in the bottom left corner, not floating. 2. Move mouse to bottom-left corner of the screen and click. Note that app launcher is activated. 3. Edit the panel to move the App Launcher to the far right hand side (bottom-right corner of the screen) 4. Move mouse to bottom-right corner of the screen and click... Note no activation of the launcher. extra: 5. Edit panel and move it to the right side of the screen. 6. Click in the bottom-right corner. Note no activation of the launcher. Try one pixel above. Note that it works. Now try one pixel to the left. Note it does not respond. 7. Edit panel and move it to the left side of the screen. 8. Click in the bottom-left corner. Note that app launcher is activated. Now move the cursor one pixel to the right (it will still be on the bottom row of pixels, now one pixel in from the left). Click. Note no activation of the launcher. OBSERVED RESULT Cannot click on a widget in corners of the panel EXPECTED RESULT Corners :D SOFTWARE/OS VERSIONS Tumbleweed on kernel 6.7.9 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Aside from a few little things (I'll file bugs over time), a pretty smooth upgrade to 6, well done you all. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 483359] UI Glitches on Mouse/Tablet movements under Plasma 6 Wayland
https://bugs.kde.org/show_bug.cgi?id=483359 --- Comment #3 from HPetrus --- Is there a specific way to apply XWAYLAND_NO_GLAMOR=1 before running krita as an appimage, other than export XWAYLAND_NO_GLAMOR=1? I ask because when I do it this way, it makes no difference whatsoever. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 479107] Dolphin does not Copy-on-Write ???? on Btrfs filesystems
https://bugs.kde.org/show_bug.cgi?id=479107 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.
[kstars] [Bug 481270] Seg. Fault Kstars.
https://bugs.kde.org/show_bug.cgi?id=481270 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481431] Desktop gets a buggy side when clicking on it after the screen is detected again after it turned off
https://bugs.kde.org/show_bug.cgi?id=481431 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|FIXED |WORKSFORME --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476794] Kicad icons are not displayed correctly
https://bugs.kde.org/show_bug.cgi?id=476794 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.
[kwin] [Bug 483783] KWin effects show up black on the PinePhone Pro on some distros
https://bugs.kde.org/show_bug.cgi?id=483783 --- Comment #2 from Devin Lin --- The log basically loops: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glVertexAttribPointer(no array object bound) kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glVertexAttribPointer(no array object bound) kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glVertexAttribPointer(no array object bound) kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawElements kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glVertexAttribPointer(no array object bound) kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glVertexAttribPointer(no array object bound) kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawArrays -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478896] mouse events offset by some amount in Chrome and derivatives
https://bugs.kde.org/show_bug.cgi?id=478896 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478874] Application Launcher listing outdated search results of moved/deleted/renamed files
https://bugs.kde.org/show_bug.cgi?id=478874 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476778] Fullscreen windows' bottom hides behind the bottom panel.
https://bugs.kde.org/show_bug.cgi?id=476778 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.
[dolphin] [Bug 460967] Dolphin no longer runs executables and is no longer showing menu bar
https://bugs.kde.org/show_bug.cgi?id=460967 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.
[systemsettings] [Bug 483807] Switching global theme by using lookandfeeltool will freeze plasmashell
https://bugs.kde.org/show_bug.cgi?id=483807 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483807] Switching global theme by using lookandfeeltool will freeze plasmashell
https://bugs.kde.org/show_bug.cgi?id=483807 g311571...@gmail.com changed: What|Removed |Added CC||g311571...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483807] New: Switching global theme by using lookandfeeltool will freeze plasmashell
https://bugs.kde.org/show_bug.cgi?id=483807 Bug ID: 483807 Summary: Switching global theme by using lookandfeeltool will freeze plasmashell Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_lookandfeel Assignee: plasma-b...@kde.org Reporter: g311571...@gmail.com Target Milestone: --- SUMMARY When I switch global theme through lookandfeeltool, plasmashell freeze STEPS TO REPRODUCE 1. In konsole, run lookandfeeltool -a "org.kde.breeze.desktop" OBSERVED RESULT Plasmashell freeze. Somewhere the theme is updated, but all panel is freeze and can't interact with. EXPECTED RESULT Smoothly switch theme like on plasma5 SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: HP Product Name: OMEN by HP Laptop 16-b1xxx ADDITIONAL INFORMATION During freeze, journalctl says: kwin_wayland[1114]: This plugin does not support raise() -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 483806] No review reporting system on Discover.
https://bugs.kde.org/show_bug.cgi?id=483806 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! However Plasma 5.18.7 is no longer eligible for support or maintenance from KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need support for Plasma 5.18.7, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE. If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483805] Battery icon does not show charge rate when changing power profiles
https://bugs.kde.org/show_bug.cgi?id=483805 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 483439] File browser crashing Strawberry and similar programs
https://bugs.kde.org/show_bug.cgi?id=483439 --- Comment #13 from pmarget...@gmail.com --- Thank you for looking into this @Nicolas Fella. I've opened an issue with Strawberry (https://github.com/strawberrymusicplayer/strawberry/issues/1401) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 483806] New: No review reporting system on Discover.
https://bugs.kde.org/show_bug.cgi?id=483806 Bug ID: 483806 Summary: No review reporting system on Discover. Classification: Applications Product: Discover Version: 5.18.7 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: tnt.productions.questi...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 167358 --> https://bugs.kde.org/attachment.cgi?id=167358=edit Jamie Dignam is being offensive, with no way to disable. discover has a public reviews board, but there's no function to hide, block, report, or otherwise get rid of offensive, discriminatory, or other bothersome reviews. STEPS TO REPRODUCE 1. View any program with bad reviews. OBSERVED RESULT People being nasty. EXPECTED RESULT I don't want to see transphobia and racism in reviews. It's just not helpful. There's no function to report these creatures, and no function to disable reviews by default. See attachment: is the top review on several applications - and I don't want to see that 4chan nonsense. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483762] Plasma crashed after changing panel position
https://bugs.kde.org/show_bug.cgi?id=483762 --- Comment #4 from Fushan Wen --- screen->handle() is a dangling pointer -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482780] Incorrect color gamut with HDR enabled
https://bugs.kde.org/show_bug.cgi?id=482780 --- Comment #17 from c...@talnikar.in --- Can reproduce this bug on Nvidia Geforce 2080 Ti, Driver version 550.54.14 on an LG Monitor as well as an LG TV. The problem is not with either of the monitors as I tested that both work in HDR with a AMD Radeon 6700XT GPU on KDE Plasma 6.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482780] Incorrect color gamut with HDR enabled
https://bugs.kde.org/show_bug.cgi?id=482780 c...@talnikar.in changed: What|Removed |Added CC||c...@talnikar.in -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483805] New: Battery icon does not show charge rate when changing power profiles
https://bugs.kde.org/show_bug.cgi?id=483805 Bug ID: 483805 Summary: Battery icon does not show charge rate when changing power profiles Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Battery Monitor Assignee: plasma-b...@kde.org Reporter: loganturner...@gmail.com CC: k...@privat.broulik.de, m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: 1.0 Created attachment 167357 --> https://bugs.kde.org/attachment.cgi?id=167357=edit Battery monitor showing a useless, unhelpful lightning bolt symbol SUMMARY The new battery plasmoid is really terrible. When changing power profiles whilst connected to power, it becomes entirely useless and doesn't report the current percentage, just a leaf or lightning bolt symbol. This is a terrible UI design and defeats the purpose of even having the battery icon in the first place. STEPS TO REPRODUCE 1. Click on battery icon 2. Set performance profile to "Power Save" or "Performance" 3. Observe system tray icon. It no longer reports the current charge level. OBSERVED RESULT Battery icon is replaced by a static, non-changing Lightning bolt or Leaf symbol EXPECTED RESULT Battery icon should always show the current charge level. Otherwise it defeats the purpose of having a battery icon at all. Make this feature a toggle option in the plasmoid's settings or perhaps have this feature as a separate system tray icon that only appears when needed.. SOFTWARE/OS VERSIONS Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482768] Plasmashell crashes in KScreen::WaylandConfig::setupRegistry() when I turn my monitor off and back on
https://bugs.kde.org/show_bug.cgi?id=482768 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #8 from Nate Graham --- If the backtrace is different, it's a different bug, yeah. Please open a new bug report for it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482768] Plasmashell crashes in KScreen::WaylandConfig::setupRegistry() when I turn my monitor off and back on
https://bugs.kde.org/show_bug.cgi?id=482768 Sishun Liu changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO --- Comment #7 from Sishun Liu --- Unfortunately, I still encountered this issue this morning on plasma 6.0.2. But the backtrace looks completely different. It does not include KScreen::WaylandConfig::setupRegistry() anymore. So maybe I have trigger another bug. I will provide more info after I catch more crashes. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 483439] File browser crashing Strawberry and similar programs
https://bugs.kde.org/show_bug.cgi?id=483439 --- Comment #12 from Nicolas Fella --- Actually I can reproduce if - Strawberry is using Qt6 - The system tray icon is *not* enabled The cause is described in https://bugs.kde.org/show_bug.cgi?id=471941. It's not really a bug in KDE code but a behavior change in Qt6 that applications need to adapt to -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483804] kwin_wayland crashes on Lenovo laptop with hybrid cards UHD Graphics 620 + AMD GPU Radeon 540/540X/550/550X
https://bugs.kde.org/show_bug.cgi?id=483804 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 483803] Screen does not turn back on after Powerdevil turns it off.
https://bugs.kde.org/show_bug.cgi?id=483803 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 483802] Filelight partition hover tooltips overlap.
https://bugs.kde.org/show_bug.cgi?id=483802 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483804] kwin_wayland crashes on Lenovo laptop with hybrid cards UHD Graphics 620 + AMD GPU Radeon 540/540X/550/550X
https://bugs.kde.org/show_bug.cgi?id=483804 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483632] Spectacle shortcut "Capture win under cursor" shows crosshair
https://bugs.kde.org/show_bug.cgi?id=483632 --- Comment #3 from Rajinder Yadav --- One additional thing I like to add. Imagine the window is changing quickly and you want to quickly capture the changes. With just the hotkey, I can press it quickly multiple times. The "new way" I would have to press the hotkey and mouse click multiple times to try to keep up with changes. This is really cumbersom and you would not be able to capture rapidly. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 482642] On X11, cannot change multi-screen settings via OSD
https://bugs.kde.org/show_bug.cgi?id=482642 --- Comment #14 from Fushan Wen --- I myself cannot reproduce, but you can try to debug yourself by adding some qDebug in OsdAction::applyAction to see what is wrong -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483632] Spectacle shortcut "Capture win under cursor" shows crosshair
https://bugs.kde.org/show_bug.cgi?id=483632 --- Comment #2 from Rajinder Yadav --- (In reply to Titouan Camus from comment #1) > I can reproduce. I am not sure it is a bug though, as it seems much more > convenient to me this way. This is not how it use to work before, also now I have to do an additional mouse click and is not efficent. Before I just move the mouse cursor over a window and use my hotkey. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483762] Plasma crashed after changing panel position
https://bugs.kde.org/show_bug.cgi?id=483762 Fushan Wen changed: What|Removed |Added CC||qydwhotm...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Fushan Wen --- Can also reproduce this on X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483804] New: kwin_wayland crashes on Lenovo laptop with hybrid cards UHD Graphics 620 + AMD GPU Radeon 540/540X/550/550X
https://bugs.kde.org/show_bug.cgi?id=483804 Bug ID: 483804 Summary: kwin_wayland crashes on Lenovo laptop with hybrid cards UHD Graphics 620 + AMD GPU Radeon 540/540X/550/550X Classification: Plasma Product: kwin Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: musik...@hotmail.com Target Milestone: --- Created attachment 167356 --> https://bugs.kde.org/attachment.cgi?id=167356=edit kwin_wayland command on X11 + coredump + lspci + lsmod outputs SUMMARY When logging in to SDDM with Wayland, it crashes. If I enabled SDDM to use kwin_wayland, it crashes too. When I logging in to Plasma 6 in X11 and launch a wayland window, it crashes too. STEPS TO REPRODUCE 1. Start SDDM in X11 2. Log in to Plasma 6 3. From a shell run the commands: export $(dbus-launch); kwin_wayland --xwayland OBSERVED RESULT A Segmentation fault error occurs. EXPECTED RESULT It should display something in Wayland. SOFTWARE/OS VERSIONS Linux/KDE Plasma: yes KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Attached files with as much information as possible. If anything thing is needed, I'll be happy to help. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 483488] & Symbols in titles
https://bugs.kde.org/show_bug.cgi?id=483488 pmarget...@gmail.com changed: What|Removed |Added CC||pmarget...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 483803] New: Screen does not turn back on after Powerdevil turns it off.
https://bugs.kde.org/show_bug.cgi?id=483803 Bug ID: 483803 Summary: Screen does not turn back on after Powerdevil turns it off. Classification: Plasma Product: Powerdevil Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: stevenmcfeel...@gmail.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 167355 --> https://bugs.kde.org/attachment.cgi?id=167355=edit journalctl output covering the screen turning off and not turning back on SUMMARY When using Powerdevil's default settings, the screen turns off after 10 minutes. However, no amount of user input will wake the screen. The only way I have found to wake it (short of a hard shutdown) is to unplug the monitor's power cord and then plug it back in. Unlike other similar reported bugs such as, https://bugs.kde.org/show_bug.cgi?id=477738, the monitor's backlight clearly does not turn on at all. So, it is not a black screen that may or may not have a cursor. STEPS TO REPRODUCE 1. Have Powerdevil set to turn off the screen after a certain amount of time (default is after 10 min) 2. Do not interact with the machine and let Powerdevil turn off the screen 3. Provide user input that normally would wake the screen (type on the keyboard, move/click the mouse, etc.) OBSERVED RESULT The screen does not turn back on - the backlight remains off. EXPECTED RESULT The screen turns back on. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: Wayland HARDWARE: CPU: Ryzen 9 7950X3d GPU: Radeon RX 7900XTX RAM: 64 GB Product Name: MS-7D69 (MSI MEG X670E ACE) ADDITIONAL INFORMATION The only way to wake the screen up is to unplug it's power cord and then plug it back in. If I put the machine to sleep, then the monitor wakes up as expected. This issue has occurred on both 6.0.2 and 6.0.1, but never happened on 5.27.10 (the last plasma 5 version released on Arch). The display is plugged directly into the dGPU, the iGPU is not used for anything. The attached file show the output of journalctl from the moment I stopped interacting with the system until the screen turned off and I attempted to turn the screen back on by interacting with the system (typing my login password, moving the mouse, etc.). It also includes the screen's power cord being unplugged and then re-plugged in. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 483439] File browser crashing Strawberry and similar programs
https://bugs.kde.org/show_bug.cgi?id=483439 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #11 from Nicolas Fella --- Cannot reproduce with Strawberry. What's the exit code? Are there any relevant log entries? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 483757] KFileWidget creation quits QApplication
https://bugs.kde.org/show_bug.cgi?id=483757 Nicolas Fella changed: What|Removed |Added Status|RESOLVED|REPORTED CC||nicolas.fe...@gmx.de Resolution|DUPLICATE |--- --- Comment #2 from Nicolas Fella --- Your program terminates because it has no windows of its own, so when the last QEventLoopLocker goes away the event loop exits. KFileWidget internally uses QEventLoopLocker, so creating it triggers this behavior. Use QApplication::setQuitLockEnabled(false) to prevent this. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 483802] New: Filelight partition hover tooltips overlap.
https://bugs.kde.org/show_bug.cgi?id=483802 Bug ID: 483802 Summary: Filelight partition hover tooltips overlap. Classification: Applications Product: filelight Version: 24.02.0 Platform: openSUSE URL: https://download.opensuse.org/repositories/openSUSE:/F actory/standard/x86_64/filelight-24.02.0-1.1.x86_64.rp m OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: 4wy78...@rokejulianlockhart.addy.io CC: martin.sandsm...@kde.org Target Milestone: --- Flags: performance+ Created attachment 167354 --> https://bugs.kde.org/attachment.cgi?id=167354=edit Depiction of the problem. STEPS TO REPRODUCE 1. Invoke Filelight via its `.desktop` entry. 2. Hover over a partition in the graph. OBSERVED RESULT The partition hover tooltips overlap. EXPECTED RESULT I don't believe that they should. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240314 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: ASRock Product Name: X670E Taichi ADDITIONAL INFORMATION I am using https://download.opensuse.org/repositories/openSUSE:/Factory/standard/x86_64/filelight-24.02.0-1.1.x86_64.rpm. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 480459] Konsole doesn't remember its maximized state
https://bugs.kde.org/show_bug.cgi?id=480459 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 481898] No saved size & position
https://bugs.kde.org/show_bug.cgi?id=481898 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 415591] In a multi-display setup, KDE apps only remember window size across program launches when closed on the left-most display
https://bugs.kde.org/show_bug.cgi?id=415591 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 483801] Night Color wrong temperature when HDR is enabled
https://bugs.kde.org/show_bug.cgi?id=483801 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 483799] Toolbar background changes after calling QMainWindow::restoreState
https://bugs.kde.org/show_bug.cgi?id=483799 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461450] Get rid of italic text for links
https://bugs.kde.org/show_bug.cgi?id=461450 --- Comment #14 from Felix Ernst --- (In reply to Holmes from comment #12) > If youre not going to get rid of italic link fonts by default, then at least > give the user a plasma setting to do it themselves. > > I hate nano-ing or vim-ing plasma config files just to get rid of italic > fonts on both the desktop and dolphin! (In reply to mdcclxv from comment #13) > +1 here If I understand correctly, you two dislike italic text in general and want a general option to get rid of it. I am not sure how many users want this and if such an option is likely to be implemented. However, this is also not for me to decide. You might want to create another bug report for getting rid of italic text in general. Not sure if it would be filed against Plasma or against the font config. Either is probably fine. Comments on this resolved Dolphin bug report are somewhat unlikely to reach many Plasma contributors. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 483791] Weather Report Widget occasionally crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=483791
Nicolas Fella changed:
What|Removed |Added
CC||nicolas.fe...@gmx.de
--- Comment #1 from Nicolas Fella ---
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {94315592904976}}
ret =
#1 0x7faad9e94a73 in __pthread_kill_internal (signo=11,
threadid=) at pthread_kill.c:78
#2 0x7faad9e41176 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
ret =
#3 0x7faadd13fb93 in KCrash::defaultCrashHandler(int) (sig=11) at
/usr/src/debug/kcrash-6.0.0/src/kcrash.cpp:586
data = { = {_vptr.MetadataWriter =
0x7faadd1447d8 }, argv = {_M_elems = {0x0,
0x7faadd1423f9 "--glrenderer", 0x55c78fa033e0 "NVIDIA GeForce GTX 1660
SUPER/PCIe/SSE2", 0x7faadd142406 "--platform", 0x55c796c803e0 "wayland",
0x7faadd142437 "--appname", 0x55c78f68f1e0 "plasmashell", 0x7faadd142441
"--apppath", 0x55c78f697f80 "/usr/bin", 0x7faadd14244e "--signal",
0x7ffd29009926 "11", 0x7faadd14245c "--pid", 0x7ffd29009930 "2696",
0x7faadd142462 "--appversion", 0x55c78fa03450 "6.0.2", 0x7faadd14246f
"--programname", 0x55c78db42a58 "", 0x7faadd14247d
"--bugaddress", 0x55c78f697110 "sub...@bugs.kde.org", 0x0 }},
argc = 19, m_writer = 0x7ffd290098d0}
platformName = {d = {d = 0x55c796c803d0, ptr = 0x55c796c803e0
"wayland", size = 7}, static _empty = 0 '\000'}
about = 0x55c78fa05550
argv = 0x7ffd29009958
ini = { = {_vptr.MetadataWriter =
0x7faadd144808 }, writable = false, fd
= 84}
sigtxt = "11\000\000\000\000\000\000\000"
pidtxt = "2696\000\000\000\000\000\373\000U\r|\2262\000FO\235"
argc =
crashRecursionCounter = 2
#4 0x7faad9e41240 in () at /lib64/libc.so.6
#5 0x005d006e0065 in ()
#6 0x7faada78fe39 in QMetaObject::cast(QObject const*) const
(this=this@entry=0x7faacccab9a0 ,
obj=0x55c7977b9ab0) at
/usr/src/debug/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qmetaobject.cpp:395
#7 0x7faaccc8ae93 in QMetaObject::cast(QObject*) const (obj=, this=0x7faacccab9a0 ) at
/usr/include/qt6/QtCore/qobjectdefs.h:233
fillExtent =
isSet =
#8 qobject_cast(QObject*) (object=) at
/usr/include/qt6/QtCore/qobject.h:393
fillExtent =
isSet =
#9 QQuickLayout::effectiveSizePolicy_helper(QQuickItem*, Qt::Orientation,
QQuickLayoutAttached*) (item=, orientation=,
info=) at
/usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/quicklayouts/qquicklayout.cpp:1269
fillExtent =
isSet =
#10 0x7faadb2a2e87 in QGridLayoutItem::stretchFactor(Qt::Orientation) const
(orientation=, this=) at
/usr/src/debug/qtbase-everywhere-src-6.6.2/src/gui/util/qgridlayoutengine.cpp:533
policy = {i = }
stretch =
#11 QGridLayoutItem::stretchFactor(Qt::Orientation) const (this=, orientation=) at
/usr/src/debug/qtbase-everywhere-src-6.6.2/src/gui/util/qgridlayoutengine.cpp:527
stretch =
#12 0x7faadb2ad49d in QGridLayoutEngine::fillRowData(QGridLayoutRowData*,
double const*, double const*, Qt::Orientation, QAbstractLayoutStyleInfo const*)
const (this=this@entry=0x55c79930dd18, rowData=rowData@entry=0x55c79930deb8,
colPositions=colPositions@entry=0x0, colSizes=colSizes@entry=0x0,
orientation=orientation@entry=Qt::Horizontal,
styleInfo=styleInfo@entry=0x55c793ce4ac0) at
/usr/src/debug/qtbase-everywhere-src-6.6.2/src/gui/util/qgridlayoutengine.cpp:1395
itemStretch =
itemRowSpan =
effectiveRowSpan =
box =
itemRow = 0
itemColumn =
item = 0x55c795015150
column = 0
rowBox = @0x55c7941edc00: {q_minimumSize = 0, q_preferredSize = 0,
q_maximumSize = 3.4028234663852886e+38, q_minimumDescent = -1, q_minimumAscent
= -1}
rowStretch = @0x55c793c53eb0: -1
hasIgnoreFlag = true
row = 0
rowInfo = @0x55c79930dd68: {count = 2, stretches =
{> =
{> = {}, }, d = {d = 0x0, ptr = 0x0, size = 0}}, spacings =
{ >> =
{ >> = {}, }, d = {d = 0x0, ptr = 0x0, size = 0}}, alignments =
{ >> =
{ >> = {},
}, d = {d = 0x0, ptr = 0x0, size = 0}}, boxes =
{> =
{> = {}, }, d = {d = 0x0, ptr = 0x0, size = 0}}}
columnInfo = @0x55c79930ddd0: {count = 4, stretches =
{> =
{> = {}, }, d = {d = 0x0, ptr = 0x0, size = 0}}, spacings =
{ >> =
{ >> = {}, }, d = {d = 0x0, ptr = 0x0, size = 0}}, alignments =
{ >> =
{ >> = {},
}, d = {d = 0x0, ptr = 0x0, size = 0}}, boxes =
{> =
{> = {}, }, d = {d = 0x0, ptr = 0x0, size = 0}}}
bottom = Right
defaultSpacing = @0x55c79930dd48: {q_value = 5, q_state =
QLayoutParameter::Cached}
innerSpacing =
lastRowAdHocData = {q_row = -1, q_hasButtons = 0, q_hasNonButtons =
}
nextToLastRowAdHocData = {q_row = , q_hasButtons = 0,
[plasmashell] [Bug 479742] Sometimes the notification service is not available due to a Plasma crash that occurs after restarting plasmashell process by running `plasmashell --replace`
https://bugs.kde.org/show_bug.cgi?id=479742 Patrick Silva changed: What|Removed |Added Component|Desktop Containment |generic-crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479742] Sometimes the notification service is not available due to a Plasma crash that occurs after restarting plasmashell process by running `plasmashell --replace`
https://bugs.kde.org/show_bug.cgi?id=479742 Patrick Silva changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 483801] New: Night Color wrong temperature when HDR is enabled
https://bugs.kde.org/show_bug.cgi?id=483801 Bug ID: 483801 Summary: Night Color wrong temperature when HDR is enabled Classification: Plasma Product: kdeplasma-addons Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Night Color Control Assignee: plasma-b...@kde.org Reporter: evanc...@gmail.com CC: kwin-bugs-n...@kde.org, vlad.zahorod...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Night color is too warm when HDR is enabled on the display. STEPS TO REPRODUCE 1. Enable HDR on a display 2. Enable night color OBSERVED RESULT Night color filter is too warm EXPECTED RESULT Night color filter is the correct temperature SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479742] Sometimes the notification service is not available due to a Plasma crash that occurs after restarting plasmashell process by running `plasmashell --replace`
https://bugs.kde.org/show_bug.cgi?id=479742 Patrick Silva changed: What|Removed |Added Version|5.92.0 |6.0.2 Summary|When removing a widget from |Sometimes the notification |the desktop for a second|service is not available |time and restarting |due to a Plasma crash that |plasmashell using |occurs after restarting |`plasmashell --replace` |plasmashell process by |between the two removals, |running `plasmashell |no "Undo" notification |--replace` |appears | --- Comment #9 from Patrick Silva --- Thread 9 (Thread 0x722b12a006c0 (LWP 1090)): #0 0x722b25ca5ebe in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x6525e7c56490) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x6525e7c56490, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x722b25ca5f3f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x6525e7c56490, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x722b25ca8750 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x6525e7c56438, cond=0x6525e7c56468) at pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x6525e7c56468, mutex=0x6525e7c56438) at pthread_cond_wait.c:618 #5 0x722b1848685c in cnd_wait () at ../mesa-24.0.3/src/c11/impl/threads_posix.c:135 #6 util_queue_thread_func () at ../mesa-24.0.3/src/util/u_queue.c:290 #7 0x722b1849e80c in impl_thrd_routine () at ../mesa-24.0.3/src/c11/impl/threads_posix.c:67 #8 0x722b25ca955a in start_thread (arg=) at pthread_create.c:447 #9 0x722b25d26a3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 8 (Thread 0x722b13e006c0 (LWP 1086)): #0 0x722b25ca5ebe in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x6525e7b18558) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x6525e7b18558, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x722b25ca5f3f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x6525e7b18558, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x722b25ca8750 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x6525e7b18500, cond=0x6525e7b18530) at pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x6525e7b18530, mutex=0x6525e7b18500) at pthread_cond_wait.c:618 #5 0x722b1848685c in cnd_wait () at ../mesa-24.0.3/src/c11/impl/threads_posix.c:135 #6 util_queue_thread_func () at ../mesa-24.0.3/src/util/u_queue.c:290 #7 0x722b1849e80c in impl_thrd_routine () at ../mesa-24.0.3/src/c11/impl/threads_posix.c:67 #8 0x722b25ca955a in start_thread (arg=) at pthread_create.c:447 #9 0x722b25d26a3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 7 (Thread 0x722b116006c0 (LWP 1349)): #0 0x722b25d190bf in __GI___poll (fds=0x722ae4007000, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x722b24ea72f6 in g_main_context_poll_unlocked (priority=2147483647, n_fds=1, fds=0x722ae4007000, timeout=, context=0x722ae4000c60) at ../glib/glib/gmain.c:4653 #2 g_main_context_iterate_unlocked.isra.0 (context=context@entry=0x722ae4000c60, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4344 #3 0x722b24e47162 in g_main_context_iteration (context=0x722ae4000c60, may_block=1) at ../glib/glib/gmain.c:4414 #4 0x722b265739c4 in QEventDispatcherGlib::processEvents (this=0x722ae4000b70, flags=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventdispatcher_glib.cpp:393 #5 0x722b26343d6e in QEventLoop::processEvents (flags=..., this=0x722b115ffb30) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:100 #6 QEventLoop::exec (this=0x722b115ffb30, flags=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:182 #7 0x722b2642106f in QThread::exec (this=this@entry=0x6525e95bf400) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qflags.h:74 #8 0x722b27b0d0d3 in QQuickPixmapReader::run (this=0x6525e95bf400) at
[Falkon] [Bug 483192] Text and images are not properly scaled at 150% display scale
https://bugs.kde.org/show_bug.cgi?id=483192 Tim Carr changed: What|Removed |Added CC||vincenzo.rom...@notorand.it --- Comment #3 from Tim Carr --- *** Bug 482825 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 482825] Falkon displays chunky fonts
https://bugs.kde.org/show_bug.cgi?id=482825 Tim Carr changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||t...@timcarr.me --- Comment #6 from Tim Carr --- Duplicate of bug 483192. Seems likely related to upstream: https://bugreports.qt.io/browse/QTBUG-113574 Setting `QT_SCALE_FACTOR_ROUNDING_POLICY=RoundPreferFloor` seems to be a temporary workaround. *** This bug has been marked as a duplicate of bug 483192 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479742] When removing a widget from the desktop for a second time and restarting plasmashell using `plasmashell --replace` between the two removals, no "Undo" notification appears
https://bugs.kde.org/show_bug.cgi?id=479742 --- Comment #8 from Patrick Silva --- Created attachment 167353 --> https://bugs.kde.org/attachment.cgi?id=167353=edit screenshot The "Undo" notification (any notification, in fact) does not appear because the notification service is not available due to a Plasma crash that occurs after restarting Plasma with "plasmashell --replace". See the attached screenshot and the backtrace of the crash occurred after restarting Plasma. Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483800] New: Request for combining of panels
https://bugs.kde.org/show_bug.cgi?id=483800 Bug ID: 483800 Summary: Request for combining of panels Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: q64...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Just would like an option to lock two panels together (like a panel on top and a panel on the right side) with no border separating the panels themselves. I would love to have a seamless transition. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480648] Display Stuck in HDR After Disabling HDR
https://bugs.kde.org/show_bug.cgi?id=480648 Evan changed: What|Removed |Added CC||evanc...@gmail.com --- Comment #12 from Evan --- I'm also seeing this with my Innocn 27m2v, but it doesn't switch between HDR and SDR in either direction. It works fine in Windows. I also have 2 Gigabyte m28u monitors that switch correctly on Linux. HDR set in Plasma: Colorspace: BT2020_RGB, HDR_OUTPUT_METADATA: 144 HDR disabled in Plasma: Colorspace: Default, HDR_OUTPUT_METADATA: 0 Monitor mode makes no difference in drm_info Colorspace/HDR_OUTPUT_METADATA Plasma 6.0.2 Arch Linux Kernel 6.8.1-zen1-1-zen -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483776] Use Shift+Enter to open in the second application associated with its type
https://bugs.kde.org/show_bug.cgi?id=483776 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- IMO we should -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483789] While holding down shortcut to open or close an effect such as Overview, Grid, etc. the effect constantly open and closes manically
https://bugs.kde.org/show_bug.cgi?id=483789 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com --- Comment #2 from fanzhuyi...@gmail.com --- Currently shortcuts trigger on press, and will re-trigger upon key autorepeat. If we don't plan on changing that, this should be closed as resolved-intentional. Note that for other shortcuts (like ctrl-V), users would probably expect this behavior. So IMO this is intentional. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 483799] Toolbar background changes after calling QMainWindow::restoreState
https://bugs.kde.org/show_bug.cgi?id=483799 --- Comment #2 from equ...@gmail.com --- Created attachment 167352 --> https://bugs.kde.org/attachment.cgi?id=167352=edit Second run -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 480814] is no VR360 and 3D effects
https://bugs.kde.org/show_bug.cgi?id=480814 SMERKIN 5000 changed: What|Removed |Added CC||t...@smerkin.club Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from SMERKIN 5000 --- SUMMARY In the effects menu there is a submenu "VR360 and 3D". In a fresh install of kdenlive the only effect here is "Stereoscopic 3D" and the 6 x VR360 effects are missing. In a fresh install of 21.12.3 these effects exist. If you upgrade from 21.12.3 to 24.02.0_A these effects still exist and work. STEPS TO REPRODUCE 1. Perform a clean install of 24.02.0_A 2. Open kdenlive and identify the missing VR360 effects 3. Uninstall 24.02.0_A 4. Perform a clean install of 21.12.3 5. Open kdenlive and verify the VR360 effects exist 6. Upgrade to 24.02.0_A 7. Open kdenlive and verify the VR360 effects still exist OBSERVED RESULT * I found that on a clean install of 24.02.0_A there is the following folder: "C:\Program Files\kdenlive\frei0r-1" and it contains the effects. * A clean install of 21.12.3 does not have that folder and instead the effects are located in "C:\Program Files\kdenlive\lib\frei0r-1". * To fix the issue on 24.02.0_A copy the effects from the top level folder to the lib folder (also an addition effect "VR360 Equirectangular to Stereo" now exists) EXPECTED RESULT * frei0r-1/VR360 effects should be installed in the correct location with a fresh install. SOFTWARE/OS VERSIONS Windows: Windows 10 19045.4170 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 (built against 6.6.2) ADDITIONAL INFORMATION * I suspect the frei0r-1 folder location is incorrect in the installer after 21.12.3 * Only tested on Windows 10 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 483799] Toolbar background changes after calling QMainWindow::restoreState
https://bugs.kde.org/show_bug.cgi?id=483799 --- Comment #1 from equ...@gmail.com --- Created attachment 167351 --> https://bugs.kde.org/attachment.cgi?id=167351=edit First run -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 483799] New: Toolbar background changes after calling QMainWindow::restoreState
https://bugs.kde.org/show_bug.cgi?id=483799 Bug ID: 483799 Summary: Toolbar background changes after calling QMainWindow::restoreState Classification: Plasma Product: Breeze Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: QStyle Assignee: plasma-b...@kde.org Reporter: equ...@gmail.com CC: noaha...@gmail.com, uhh...@gmail.com Target Milestone: --- Created attachment 167350 --> https://bugs.kde.org/attachment.cgi?id=167350=edit Sample code SUMMARY After calling QMainWindow::restoreState() (i.e. after first run for typical application), toolbar's background does not match window decoration color anymore. Sample code: STEPS TO REPRODUCE 1. Save main window state using QMainWindow::saveState 2. Restore main window state using QMainWindow::restoreState OBSERVED RESULT Toolbar's background does not match window decoration. EXPECTED RESULT Toolbar's background matches window decoration. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481793] ddcutil constantly locked by powerdevil
https://bugs.kde.org/show_bug.cgi?id=481793 Jakob Petsovits changed: What|Removed |Added Version Fixed In||6.1.0 --- Comment #6 from Jakob Petsovits --- Marking fixed in 6.1.0 for now. I'll have a look how difficult/risky the backport to 6.0.3 would be. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481793] ddcutil constantly locked by powerdevil
https://bugs.kde.org/show_bug.cgi?id=481793 Jakob Petsovits changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/powerdevil/-/commit/db4a ||6c79bc5f58dccc43805502c5814 ||5ef341ea1 --- Comment #5 from Jakob Petsovits --- Git commit db4a6c79bc5f58dccc43805502c58145ef341ea1 by Jakob Petsovits. Committed on 16/03/2024 at 23:26. Pushed by jpetso into branch 'master'. daemon: Avoid constantly locking ddcutil display handles Since libddcutil implemented functionality for per-monitor device lock files, other programs that are also using libddcutil (such as the ddcutil CLI itself) were blocked from performing monitor commands because PowerDevil kept all its handles open. The better way of interacting with libddcutil as a long-running program is to store a DDCA_Display_Ref for each monitor in question, use it to get a temporary display handle, and close it again. Now we can peacefully coexist with other libddcutil programs, and users can e.g. query their monitor properties again. As a slight downside, this means it's possible for another program to set display brightness independently without PowerDevil noticing. That seems like a smaller evil though, and can't be fixed by simply using libddcutil itself as it cannot signal any VCP changes. Common infrastructure such as digitaltrails/ddcutil-service or a future kernel DRM interface for DDC/CI could help to mitigate this. M +16 -22 daemon/controllers/ddcutilbrightness.cpp M +79 -14 daemon/controllers/ddcutildisplay.cpp M +4-2daemon/controllers/ddcutildisplay.h https://invent.kde.org/plasma/powerdevil/-/commit/db4a6c79bc5f58dccc43805502c58145ef341ea1 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461450] Get rid of italic text for links
https://bugs.kde.org/show_bug.cgi?id=461450 mdcclxv changed: What|Removed |Added CC||mdcc...@gmx.net --- Comment #13 from mdcclxv --- (In reply to Holmes from comment #12) > If youre not going to get rid of italic link fonts by default, then at least > give the user a plasma setting to do it themselves. > > I hate nano-ing or vim-ing plasma config files just to get rid of italic > fonts on both the desktop and dolphin! +1 here -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483797] Selected folders are black
https://bugs.kde.org/show_bug.cgi?id=483797 Nicolas Fella changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483651] Edge barrier/corner barrier makes it almost impossible to move the mouse between diagonally placed screens
https://bugs.kde.org/show_bug.cgi?id=483651 --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/5448 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483797] Selected folders are black
https://bugs.kde.org/show_bug.cgi?id=483797 Nicolas Fella changed: What|Removed |Added Version|unspecified |24.02.0 CC||nicolas.fe...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451333] Windows open in awkward sizes when the display resolutions are not equal
https://bugs.kde.org/show_bug.cgi?id=451333 --- Comment #14 from Antti Savolainen --- Odd. Okteta still spawns over the screen borders and it doesn't remember the size it was last closed in? https://www.youtube.com/watch?v=Xr5OMsy-b7M Should I reopen this issue? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 483798] kdeconnect-sms doesn't detect URLs in messages
https://bugs.kde.org/show_bug.cgi?id=483798 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 483796] Some characters appear garbled in the UI
https://bugs.kde.org/show_bug.cgi?id=483796 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483797] Selected folders are black
https://bugs.kde.org/show_bug.cgi?id=483797 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 482169] System Monitor in Plasma 6 crashes on clicking "Show Details Sidebar"
https://bugs.kde.org/show_bug.cgi?id=482169 --- Comment #11 from SR_team --- Same issue. OS: ArchLinux, core 6.7.9-zen GPU: NVIDIA, 550.54.14 Plasma version: 6.0.2 Frameworks: 6.0.0 Qt: 6.6.2 Coredump: https://nc.sr.team/s/KCqcozY9pGbFDEC Backtrace: ``` QQuickItem::parentItem (this=0x0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp:2629 Downloading source file /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp 2629return d->parentItem; (gdb) (gdb) bt #0 QQuickItem::parentItem (this=0x0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp:2629 #1 0x7fffeaf81e13 in QQuickSelectionRectanglePrivate::updateSelectionMode (this=0x597aa0a0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quicktemplates/qquickselectionrectangle.cpp:496 #2 0x7fffeaf8373b in operator() (__closure=0x597ab4f0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quicktemplates/qquickselectionrectangle.cpp:542 #3 QtPrivate::FunctorCall, QtPrivate::List<>, void, QQuickSelectionRectangle::QQuickSelectionRectangle(QQuickItem*):: >::call (arg=, f=...) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:137 #4 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:339 #5 QtPrivate::QCallableObject, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x597ab4e0, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:522 #6 0x76190ca9 in QtPrivate::QSlotObjectBase::call (a=0x7fff7358, r=0x597a9fc0, this=0x597ab4e0, this=, r=, a=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobjectdefs_impl.h:433 #7 doActivate (sender=0x597a9fc0, signal_index=17, argv=0x7fff7358) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:4039 #8 0x7fffeb788d4b in QQuickItemPrivate::setEffectiveEnableRecur (this=0x59653340, scope=0x0, newEffectiveEnable=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp:6571 #9 0x7fffeb788d4b in QQuickItemPrivate::setEffectiveEnableRecur (this=0x59652e30, scope=0x0, newEffectiveEnable=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp:6571 #10 0x7fffeb788d4b in QQuickItemPrivate::setEffectiveEnableRecur (this=0x584f6dd0, scope=0x0, newEffectiveEnable=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp:6571 #11 0x7fffeb788d4b in QQuickItemPrivate::setEffectiveEnableRecur (this=0x588f6ab0, scope=0x0, newEffectiveEnable=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp:6571 #12 0x7fffeb788d4b in QQuickItemPrivate::setEffectiveEnableRecur (this=0x58008000, scope=0x0, newEffectiveEnable=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp:6571 #13 0x7fffeb77f6f4 in QQuickItem::setParentItem (this=0x7fffbc0021e0, parentItem=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp:2721 #14 0x7fffeb7ae1f9 in QQuickLoaderPrivate::setInitialState (obj=0x7fffbc0021e0, this=0x57eddda0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickloader.cpp:639 #15 QQuickLoaderIncubator::setInitialState (this=this@entry=0x584483d0, o=0x7fffbc0021e0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickloader.cpp:622 #16 0x772aedfa in QQmlIncubatorPrivate::incubate (this=this@entry=0x7fffbc002400, i=...) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/qml/qqmlincubator.cpp:321 #17 0x772af4a6 in QQmlEnginePrivate::incubate (this=0x557c48f0, i=, forContext=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/qml/qqmlincubator.cpp:53 #18 0x7725fb86 in QQmlComponent::create (this=, incubator=..., context=, forContext=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/qml/qqmlcomponent.cpp:1437 #19 0x7fffeb7a8b46 in QQuickLoaderPrivate::_q_sourceLoaded (this=0x57eddda0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickloader.cpp:741 #20 0x7fffeb7add6d in QQuickLoader::setActive (this=0x57ef41b0, newVal=) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickloader.cpp:315 #21 0x77231298 in QQmlPropertyData::writeProperty (this=, target=, value=, flags=...) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/qml/qml/qqmlpropertydata_p.h:298 #22 0x77246591 in GenericBinding<1>::doStore
[okular] [Bug 483678] Signing with Luxtrust's non-repudiation certificate just hangs
https://bugs.kde.org/show_bug.cgi?id=483678 --- Comment #4 from Alain Knaff --- I now wanted to try whether it works better with gpg, but I couldn't find how to switch to gpg. In Settings->ConfigureBackends->PDF, it seems to assume NSS, and there is no switch to use GPG Or is this in an entirely different place in settings? If so, where? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 482169] System Monitor in Plasma 6 crashes on clicking "Show Details Sidebar"
https://bugs.kde.org/show_bug.cgi?id=482169 SR_team changed: What|Removed |Added CC||m...@sr.team -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 483798] New: kdeconnect-sms doesn't detect URLs in messages
https://bugs.kde.org/show_bug.cgi?id=483798 Bug ID: 483798 Summary: kdeconnect-sms doesn't detect URLs in messages Classification: Applications Product: kdeconnect Version: 24.02.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: messaging-application Assignee: si...@ergotech.com Reporter: john@pelago.org.uk Target Milestone: --- SUMMARY SMS messages I receive often contain URLs. SMS apps on Android generally recognise these and allow them to be clickable, but KDE Connect SMS does not. It would aid usability if it could. STEPS TO REPRODUCE 1. Receive an SMS message on your mobile that contains a URL 2. Run KDE Connect SMS (kdeconnect-sms) 3. Read the message and hover the mouse over the URL OBSERVED RESULT The URL is just normal text, not clickable. EXPECTED RESULT The URL is clickable. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240314 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 Manufacturer: HP Product Name: HP ProBook 450 G4 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 483795] Updates with Version=6 were ignored if kconf_update5 ran before
https://bugs.kde.org/show_bug.cgi?id=483795 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483797] Selected folders are black
https://bugs.kde.org/show_bug.cgi?id=483797 --- Comment #1 from Oleg --- Created attachment 167349 --> https://bugs.kde.org/attachment.cgi?id=167349=edit Selected folder with previews I want to clarify that folders which have mini-thumbnails don't suffer from this issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483797] New: Selected folders are black
https://bugs.kde.org/show_bug.cgi?id=483797 Bug ID: 483797 Summary: Selected folders are black Classification: Applications Product: dolphin Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: icons mode Assignee: dolphin-bugs-n...@kde.org Reporter: o...@np880.ru CC: kfm-de...@kde.org Target Milestone: --- Created attachment 167348 --> https://bugs.kde.org/attachment.cgi?id=167348=edit Black icons SUMMARY When selecting folders in Dolphin in icons mode they're becoming black SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION No other icons are behaving in such way -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 483796] New: Some characters appear garbled in the UI
https://bugs.kde.org/show_bug.cgi?id=483796 Bug ID: 483796 Summary: Some characters appear garbled in the UI Classification: Applications Product: kdenlive Version: 24.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: mashkal2...@gmail.com Target Milestone: --- Created attachment 167347 --> https://bugs.kde.org/attachment.cgi?id=167347=edit garbled text SUMMARY Some text is rendered incorrectly, resulting in garbled unreadable text. STEPS TO REPRODUCE 1. Open a file created with kdenlive 23.08 SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-25-generic (64-bit) Graphics Platform: X11 Processors: 20 × 13th Gen Intel® Core™ i5-13600K Memory: 31.1 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 Manufacturer: ASRock Product Name: Z690M-ITX/ax -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478165] The hovered clipboard item is blurry with fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=478165 --- Comment #12 from zvova7...@gmail.com --- https://bugreports.qt.io/browse/QTBUG-122830 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 422880] Some icons in Inkscape are inappropriately using the colorful style at large size
https://bugs.kde.org/show_bug.cgi?id=422880 medin changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #7 from medin --- (In reply to Nate Graham from comment #6) > I can't reproduce this issue with Inkscape today; can you? I suspect it was > a bug in either GTK or KIconLoader. You are right, I tested with Inkscape 1.3.2 on Plasma 6.0.2/Wayland, and apart from some minor duplicated icons, it seems all Breeze icons appear correctly inside Inkscape when system icon theme is selected in Inkscape preferences. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 483795] Updates with Version=6 were ignored if kconf_update5 ran before
https://bugs.kde.org/show_bug.cgi?id=483795 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kconfig/-/merge_requests/283 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482992] Clicks falling through a Firefox window after it was moved
https://bugs.kde.org/show_bug.cgi?id=482992 jas...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from jas...@gmail.com --- Tested in 6.0.2, and indeed it's fixed now. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 483795] New: Updates with Version=6 were ignored if kconf_update5 ran before
https://bugs.kde.org/show_bug.cgi?id=483795 Bug ID: 483795 Summary: Updates with Version=6 were ignored if kconf_update5 ran before Classification: Frameworks and Libraries Product: frameworks-kconfig Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: matt...@mjdsystems.ca Reporter: fab...@ritter-vogt.de CC: kdelibs-b...@kde.org Target Milestone: --- kconf_update5 is missing 1a4c737941316c1e6ad61479b0c16b7de595339e, which means it updates ctime and mtime entries for .upd files even on version mismatch. This means that kconf_update6 ignores those files when it runs after kconf_update5. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 483794] Scrollbar arrows scroll to the extreme top and bottom rather than just a small amount in QQC2 apps
https://bugs.kde.org/show_bug.cgi?id=483794 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483641] KDE6 Task manager pinned icon and layout
https://bugs.kde.org/show_bug.cgi?id=483641 --- Comment #8 from jonzn4SUSE --- Looks like task manager has issues with layout when more than 2 rows are used. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 483713] KDENLIVE application is Suspended by MS Windows when opening a project with lots of sequences
https://bugs.kde.org/show_bug.cgi?id=483713 --- Comment #3 from SMERKIN 5000 --- No worries, I hope it reproduces on your end. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 483713] KDENLIVE application is Suspended by MS Windows when opening a project with lots of sequences
https://bugs.kde.org/show_bug.cgi?id=483713 --- Comment #2 from SMERKIN 5000 --- Created attachment 167346 --> https://bugs.kde.org/attachment.cgi?id=167346=edit Project with 112 open sequences -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 434884] Scroll bar arrow buttons does not highlight on hover in QQC2 apps
https://bugs.kde.org/show_bug.cgi?id=434884 Paul McAuley changed: What|Removed |Added CC||k...@paulmcauley.com Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #4 from Paul McAuley --- This fix isn't quite the same. On normal Qt widget apps the scrollbar highlights when that scrollarea is active, not just on hover. In QCC2 the scollbar only highlights on hover. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 483794] New: Scrollbar arrows scroll to the extreme top and bottom rather than just a small amount in QQC2 apps
https://bugs.kde.org/show_bug.cgi?id=483794 Bug ID: 483794 Summary: Scrollbar arrows scroll to the extreme top and bottom rather than just a small amount in QQC2 apps Classification: Frameworks and Libraries Product: frameworks-qqc2-desktop-style Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: k...@paulmcauley.com CC: ahiems...@heimr.nl, k...@davidedmundson.co.uk, noaha...@gmail.com, notm...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Enable scrollbar arrows in Breeze application style 2. Open Discover or System Settings 3. Click on the scrollbar arrow OBSERVED RESULT The page scrolls to the extreme bottom or top EXPECTED RESULT The page should only scroll a small increment SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.0-63.fc40.1.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Google Product Name: Pantheon System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438315] Kwin crashed in KWin::FocusChain::isUsableFocusCandidate()
https://bugs.kde.org/show_bug.cgi?id=438315 Mark changed: What|Removed |Added CC|m...@leyva.me | -- You are receiving this mail because: You are watching all bug changes.
