[dolphin] [Bug 476627] Loading of large directories abnormally slow after update
https://bugs.kde.org/show_bug.cgi?id=476627 --- Comment #1 from Mircea Kitsune --- Created attachment 162901 --> https://bugs.kde.org/attachment.cgi?id=162901=edit hdparm Output of "hdparm -Tt /dev/sda" which is the main affected drive: It shows that my usual drive read / write speeds are normal and this isn't an issue with my HDD, which is confirmed by the fact that other applications who work with lots of files or large files work just as fast and only Dolphin appears to be abnormally slowed down. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 476627] Loading of large directories abnormally slow after update
https://bugs.kde.org/show_bug.cgi?id=476627 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 476627] New: Loading of large directories abnormally slow after update
https://bugs.kde.org/show_bug.cgi?id=476627 Bug ID: 476627 Summary: Loading of large directories abnormally slow after update Classification: Applications Product: dolphin Version: 23.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sonichedgehog_hyperblas...@yahoo.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 162900 --> https://bugs.kde.org/attachment.cgi?id=162900=edit fstab SUMMARY Large directories are now taking a ridiculous amount of time to load in Dolphin. A folder with over 65.000 images would previously take roughly 15 seconds to finish loading, now it’s over 5 minutes. During this time I see 100% of one CPU core being used, however I can’t find a root or user process doing it and it’s not the Dolphin application itself… my hard drive keeps being read at a rate of roughly 3 MB/s. This only happens once per directory after boot, after a directory finishes showing up it will load at normal speed until you reboot... this indicates the problem may be related to caching. It’s definitely not a problem with my drive and was introduced by a recent update, other operations such as using the 'ls' command are just as fast only Dolphin appears to be affected. STEPS TO REPRODUCE You need a directory with a lot of files to see it clearly, at least 50.000 if possible: Open it and the issue should be quickly noticeable. A good test folder that's typically large for most users is ~/.cache/thumbnails/large where preview thumbnails are cached by the system, opening that should trigger it if you have a lot of previews. OBSERVED RESULT The directory takes minutes to load as Dolphin is barely responsive during the process. EXPECTED RESULT Over a month ago it would only take a few seconds, something clearly changed affecting directory loading speeds on Dolphin or some KDE component exclusively. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.6.0-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series ADDITIONAL INFORMATION Attached /etc/fstab as it's been previously pointed out Dolphin had issues with certain parameters there. The affected partition is a SATA3 HDD, I'm also able to reproduce it on my SSD where loading a large directory with lots of images is abnormally slow as well... both are ext4. No drive errors, booted with "fsck.mode=force fsck.repair=yes" to make extra sure and the issue persists even afterward. Baloo is enabled but the affected directories are not indexed. Enabling or disabling previews in Dolphin doesn't make any difference. Extra discussion of the issue on the Manjaro Linux forum: https://forum.manjaro.org/t/dolphin-loading-of-large-directories-very-slow-after-update/149727 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449352] Widgets positioned to the right of the panel return left after Plasma restarts
https://bugs.kde.org/show_bug.cgi?id=449352 --- Comment #4 from Mircea Kitsune --- Haven't see it in a while: Unless someone else can confirm otherwise I consider it solved. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470881] Dolphin won't remove moved files from the source view in symlinked directory
https://bugs.kde.org/show_bug.cgi?id=470881 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470881] New: Dolphin won't remove moved files from the source view in symlinked directory
https://bugs.kde.org/show_bug.cgi?id=470881 Bug ID: 470881 Summary: Dolphin won't remove moved files from the source view in symlinked directory Classification: Applications Product: dolphin Version: 23.04.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sonichedgehog_hyperblas...@yahoo.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When dragging files between different tabs, Dolphin will not update the view from which a file was moved: Files will appear as if still there until you press F5 to refresh manually. Upon further investigation I discovered this only happens when dragging one or more files (not folders) between symlinked directories. STEPS TO REPRODUCE 1. Create two directories, eg: ~/A and ~/B. Create a symlink pointing to each one, eg: ~/sym_A and ~/sym_B. 2. Open up Dolphin then press F3 to enable split view. 3. Navigate each view to one directory but through its symlink not the original path. 4. Place any file in either directory or just create an empty text file in one. 5. Shift-drag the file in between the different views to move it. OBSERVED RESULT While the moved file appears in its new location, it will not be removed from the old view and still appear as if a copy is present there. This goes away upon pressing F5 to refresh. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.3.5-2-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series ADDITIONAL INFORMATION I'm using Plasma Wayland session on Manjaro Linux, Dolphin 23.04.1, all partitions are ext4. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446204] Widgets without background have fully black text with dark color schemes making them unreadable
https://bugs.kde.org/show_bug.cgi?id=446204 Mircea Kitsune changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Mircea Kitsune --- This no longer seems to be occurring when using new color schemes based on the Breeze Light / Dark theme, I'd say whatever it was should be fixed and will mark this as resolved. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445449] Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM
https://bugs.kde.org/show_bug.cgi?id=445449 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 --- Comment #22 from Mircea Kitsune --- Only reason the issue was finally resolved for me is last year I got a new monitor from Samsung due to the old one showing signs of failing. The Samsung Odyssey monitor will correctly go and stay in standby, both in X11 and Wayland on both HDMI and DisplayPort cable, also enabling or disabling automatic source detection in the monitor OSD doesn't effect it (works fine on both). By comparison the ViewSonic will not stay powered down on either cable: It will only on X11 if I disable the KScreen2 service, on Wayland never. On the machine it's now on (also Manjaro / KDE) I just disabled monitor power saving especially since WL can still experience minor issues when there's no screen, I put the whole machine into standby / suspend which saves more power anyway. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463277] Wayland: Dolphin no longer detects Control and Shift keys when dragging items
https://bugs.kde.org/show_bug.cgi?id=463277 --- Comment #2 from Mircea Kitsune --- Found an important clue I surprisingly missed till now, which might offer indication as to what is happening. The problem doesn't happen if you hold the respective key before you start dragging the file, only if you do it during the drag. So if you hold down shift then click and drag on a file / folder, it will be moved correctly without a prompt. But if you click-drag the file, press and hold shift after that, then release the mouse button to drop it... now you will get the prompt and Dolphin acts like the key wasn't being held. Since I got used to pressing the key midway I might be in a minority who notices this problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463288] Wayland: Firefox picture-in-picture mode adds extra icon to the taskbar
https://bugs.kde.org/show_bug.cgi?id=463288 Mircea Kitsune changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463288] Wayland: Firefox picture-in-picture mode adds extra icon to the taskbar
https://bugs.kde.org/show_bug.cgi?id=463288 --- Comment #2 from Mircea Kitsune --- (In reply to Enrico from comment #1) Thank you for checking. I see you have the little green + icon so I take it you use grouping, I disabled that in my configuration: If you right-click the task manager and go to "configure icon-only task manager" then in behavior set group to "do not group" can you see it then? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463288] Wayland: Firefox picture-in-picture mode adds extra icon to the taskbar
https://bugs.kde.org/show_bug.cgi?id=463288 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463288] New: Wayland: Firefox picture-in-picture mode adds extra icon to the taskbar
https://bugs.kde.org/show_bug.cgi?id=463288 Bug ID: 463288 Summary: Wayland: Firefox picture-in-picture mode adds extra icon to the taskbar Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: sonichedgehog_hyperblas...@yahoo.com Target Milestone: 1.0 Created attachment 154720 --> https://bugs.kde.org/attachment.cgi?id=154720=edit Screenshot SUMMARY A small but annoying inconvenience: When watching Youtube videos in Firefox and using Picture in Picture mode, a new icon will be created in the task manager for the popup video. Things like floating panels or detached videos shouldn't have icons like actual dialogs and applications, which creates confusion and clutter in the taskbar. This is a Wayland issue and doesn't occur on X11: I'm running into it since I decided to give Plasma Wayland another try with many of the core issues finally being fixed over the past months. STEPS TO REPRODUCE 1. Open and play any Youtube video in Firefox, any video will likely trigger it. 2. Click on the icon to enable PiP mode, which should put the video into a small window. OBSERVED RESULT A new icon with the Firefox logo is added to the task manager for the video window. EXPECTED RESULT This is the sort of window that doesn't need a task manager icon. This already doesn't happen on the X11 session. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.0-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463277] Wayland: Dolphin no longer detects Control and Shift keys when dragging items
https://bugs.kde.org/show_bug.cgi?id=463277 Mircea Kitsune changed: What|Removed |Added Summary|Dolphin no longer detects |Wayland: Dolphin no longer |Control and Shift keys when |detects Control and Shift |dragging items |keys when dragging items -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463277] Dolphin no longer detects Control and Shift keys when dragging items
https://bugs.kde.org/show_bug.cgi?id=463277 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463277] New: Dolphin no longer detects Control and Shift keys when dragging items
https://bugs.kde.org/show_bug.cgi?id=463277 Bug ID: 463277 Summary: Dolphin no longer detects Control and Shift keys when dragging items Classification: Applications Product: dolphin Version: 22.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sonichedgehog_hyperblas...@yahoo.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Seeing the vast majority of issues with Plasma Session on Wayland have finally been fixed, I decided to try switching from X11 again after years of waiting. Apart from some annoying but bearable intermittent bugs, there's one persistent issue I'm now encountering with Dolphin: Holding Control or Shift to copy or move files no longer seems to be working. Upon click-dragging an item, I'm always asked if I want to either copy or move that item. The menu even shows the Control and Shift shortcuts, but it's as if the buttons are no longer detected. STEPS TO REPRODUCE Either open two Dolphin sessions or use one with split view. Go to different directories and click-drag files between them while holding the Control or Shift key down. OBSERVED RESULT Dolphin acts as if no key is being held. It will ask you whether to copy or move the file instead of automatically doing so based on the key held. EXPECTED RESULT On X11 holding Control while dragging the item copies it whereas holding Shift moves it without a prompt. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.0-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 452553] Monitor instantly wakes up from energy saving in Wayland
https://bugs.kde.org/show_bug.cgi?id=452553 --- Comment #5 from Mircea Kitsune --- Only addition I can make is confirming the issue is heavily dependent on the monitor model. I just bought a new Samsung Odyssey to replace my Viewsonic monitor over multiple issues: Where the Viewsonic wouldn't normally stay in sleep under either X11 or Wayland, the Samsung does so in both with KScreen2 enabled and on either HDMI or DP cables. The old monitor was moved to another computer... on it standby actually works now, despite not working on the same cable on my box. And both machines use AMD cards, I forgot if I still enable amdgpu on my mother's PC which may explain why there it's working at least in X11. Hopefully affected monitor models will also be fixed, there seem to be quite a few especially around lower end products. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 --- Comment #19 from Mircea Kitsune --- Only addition I can make is confirming the issue is heavily dependent on the monitor model. I just bought a new Samsung Odyssey to replace my Viewsonic monitor over multiple issues: Where the Viewsonic wouldn't normally stay in sleep under either X11 or Wayland, the Samsung does so in both with KScreen2 enabled and on either HDMI or DP cables. The old monitor was moved to another computer... on it standby actually works now, despite not working on the same cable on my box. And both machines use AMD cards, I forgot if I still enable amdgpu on my mother's PC which may explain why there it's working at least in X11. Hopefully affected monitor models will also be fixed, there seem to be quite a few especially around lower end products. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 457483] Screeching noise comes out of HDMI monitor when clicking the volume icon in system tray
https://bugs.kde.org/show_bug.cgi?id=457483 Mircea Kitsune changed: What|Removed |Added Assignee|plasma-b...@kde.org |sonichedgehog_hyperblast00@ ||yahoo.com Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Mircea Kitsune --- Created attachment 151258 --> https://bugs.kde.org/attachment.cgi?id=151258=edit Output of: aplay -l Today I opened an RPG Maker game in WINE: That caused the exact screeching effect from the monitor as the volume icon. So I can confirm a few other things may trigger this as well. As I forgot this rather important step, here's also my devices as listed by "aplay -l". In case any of them is recognized to have a recent issue or anything else out of the ordinary is spotted there. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 457483] Screeching noise comes out of HDMI monitor when clicking the volume icon in system tray
https://bugs.kde.org/show_bug.cgi?id=457483 --- Comment #3 from Mircea Kitsune --- Created attachment 151122 --> https://bugs.kde.org/attachment.cgi?id=151122=edit Capture I'll try with tools like Pavucontrol and similar later to give it time. I find it odd if were something else as this happened just as I updated Plasma, IIRC few other packages were updated in that run but at the same time I can't rule out the possibility. For now here's a short capture just so others can see and hear what's happening. Keep in mind the noise is always different and usually sounds more high pitch. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 457483] New: Screeching noise comes out of HDMI monitor when clicking the volume icon in system tray
https://bugs.kde.org/show_bug.cgi?id=457483 Bug ID: 457483 Summary: Screeching noise comes out of HDMI monitor when clicking the volume icon in system tray Product: plasma-pa Version: 5.25.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: sonichedgehog_hyperblas...@yahoo.com CC: m...@ratijas.tk, now...@gmail.com Target Milestone: --- SUMMARY Whenever I click on the volume icon in the system tray, a screeching that literally sounds like a FNAF jumpscare sound comes out of my monitor for roughly 3 seconds then stops. This happens the first time after booting then every few hours, I can keep opening the audio volume applet and it won't occur any more except rarely after some time. Audio appears to work fine on all devices otherwise including the affected monitor. This started happening once I upgraded to Plasma 5.25.3: In 5.24.6 or earlier I don't believe I ever got the issue. STEPS TO REPRODUCE Make sure you have a monitor connected via HDMI and with audio enabled. Just click on the volume icon in the system tray every now and then. If the system contains affected configurations it should eventually happen. OBSERVED RESULT At some point you'll hear loud audio glitching that sounds like fast-forwarding a cassette tape. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.19.0-2-MANJARO (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 457483] Screeching noise comes out of HDMI monitor when clicking the volume icon in system tray
https://bugs.kde.org/show_bug.cgi?id=457483 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 --- Comment #17 from Mircea Kitsune --- Kernel 5.18 and I definitely still have the problem. Sadly also on HDMI alongside DP. It occurs both in X11 and Wayland: In X11 it can be stopped by disabling the KScreen2 service, in Wayland it will do it regardless of whether that service is running so there's virtually no way to use monitor power saving (at least it no longer crashes as well). This is frustrating and very unfortunate, after so many years I wonder if this can ever be addressed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455809] Option "Make window titlebars accent-colored" is slightly inaccurate when applied to header-color-using color schemes
https://bugs.kde.org/show_bug.cgi?id=455809 --- Comment #3 from Mircea Kitsune --- Playing with color schemes in 5.25.3 to figure this out, I noticed there are two problems which are unclear to the end user: 1. What exactly is the header color? In the color scheme editor there is a Header category like all others (eg: Tooltip) with multiple colors. Which one does what in terms of colorization and acts as the trigger? 2. What does it mean for the header color to be defined or undefined by the color scheme? Every color has an implicit value, you can't erase a definition from the menu. Does not defined mean setting the color to black? This doesn't seem to be the case as color schemes with opposite behaviors all have a color other than fully black or white so something else must be determining it. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 414097] Preview folder icons not repainted automatically after color scheme change
https://bugs.kde.org/show_bug.cgi?id=414097 --- Comment #6 from Mircea Kitsune --- Created attachment 150721 --> https://bugs.kde.org/attachment.cgi?id=150721=edit Screenshot Confirming. You need to press F5 to refresh, sometimes you must also navigate away then come back to the directory first. I didn't notice it until accent colors came along: Plasma 5.25 added wallpaper based coloring and lets the color automatically change with a wallpaper slideshow, even in this case directory icons with previews don't have their color updated. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 414097] Preview folder icons not repainted automatically after color scheme change
https://bugs.kde.org/show_bug.cgi?id=414097 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456874] Changes to accent color do not take effect immediately in GTK apps using Breeze GTK theme; they need to be restarted
https://bugs.kde.org/show_bug.cgi?id=456874 --- Comment #5 from Mircea Kitsune --- Thanks for clarifying. Please take a look at my last comment too, I seem to have ended up reporting two bugs in one due to them appearing the same: Dolphin also forgets to update the icon colors for directories sometimes, apparently when preview is enabled and the folder contains overlays from what I'm noticing in my own screenshot. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456887] Colorizing the toolbar with the accent color depends on a hidden setting in the color scheme
https://bugs.kde.org/show_bug.cgi?id=456887 --- Comment #1 from Mircea Kitsune --- Created attachment 150719 --> https://bugs.kde.org/attachment.cgi?id=150719=edit Screenshot This is the difference I'm referring to just so there's no confusion. Both styles are great but the color scheme editor doesn't let you pick which it is, it's seemingly based on which color scheme you start from. You also can't get this effect without using accent colors from what I've seen, IMHO accents should only change the color being used but without being a dependency for applying different color categories to different elements. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456887] Colorizing the toolbar with the accent color depends on a hidden setting in the color scheme
https://bugs.kde.org/show_bug.cgi?id=456887 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456887] New: Colorizing the toolbar with the accent color depends on a hidden setting in the color scheme
https://bugs.kde.org/show_bug.cgi?id=456887 Bug ID: 456887 Summary: Colorizing the toolbar with the accent color depends on a hidden setting in the color scheme Product: systemsettings Version: 5.25.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: sonichedgehog_hyperblas...@yahoo.com CC: noaha...@gmail.com, tantalising...@gmail.com, uhh...@gmail.com Target Milestone: --- SUMMARY I love the new ability in Plasma 5.25.3 to colorize either just the titlebar or the titlebar and toolbar together using accent color. However there's a limitation I noticed while setting up the color schemes to use it: The choice between the two depends on a hidden option in the color scheme which isn't visible in the scheme editor. STEPS TO REPRODUCE Easiest way I found: Copy both the Breeze Light and Breeze Classic color schemes that come by default, then in both enable the "apply accent color to (in)active window titlebars" option. OBSERVED RESULT You should notice that both themes tint the titlebar, but only the one copied from Breeze Light will also tint the toolbar. If you dig through the settings, you won't find any option that makes it be one or the other. I even looked at the scheme in a text editor and couldn't find exactly what determines it. EXPECTED RESULT There should be something that can be changed in the color scheme editor which lets you decide. IDEA AND SUGGESTION Considering another issue is you can't make a color scheme that tints the titlebar without enabling accent colors, maybe it would be a good idea to make tinting the titlebar an explicit option as well. A new scheme option "use titlebar color in toolbar" should suffice: This way you can also use it without accent colors and apply the color scheme's titlebar color to the toolbar even when the accent color is disabled. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.12-3-MANJARO (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438110] Editing color scheme without changing color scheme doesn't update GTK3 app colors
https://bugs.kde.org/show_bug.cgi?id=438110 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456876] Inactive accent color applied to titlebar when the application menu is open
https://bugs.kde.org/show_bug.cgi?id=456876 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456876] New: Inactive accent color applied to titlebar when the application menu is open
https://bugs.kde.org/show_bug.cgi?id=456876 Bug ID: 456876 Summary: Inactive accent color applied to titlebar when the application menu is open Product: systemsettings Version: 5.25.3 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: sonichedgehog_hyperblas...@yahoo.com CC: noaha...@gmail.com, tantalising...@gmail.com, uhh...@gmail.com Target Milestone: --- Created attachment 150716 --> https://bugs.kde.org/attachment.cgi?id=150716=edit Screenshot SUMMARY A minor issue with accent coloring in 5.25.3: When opening the application menu, the toolbar will change to the inactive color even if you're still on the active window. This looks ugly and inconsistent. STEPS TO REPRODUCE 1. Make sure in the Window Decoration settings you added the "application menu" icon to KWin, otherwise you'll get the classic menu bar which doesn't seem to have this issue. Also that you're using a color scheme which colorizes the toolbar with the accent color. 2. Open an application like Dolphin or Kate. 3. Click on the application icon in the window title. OBSERVED RESULT The toolbar switches to the inactive coloring while the menu is open, even if the window is still active and the titlebar still accurately represents the active color. EXPECTED RESULT The toolbar should maintain the active colorization as you haven't deselected the window. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.12-3-MANJARO (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456874] Changes to accent color or color scheme are sometimes not updated in applications
https://bugs.kde.org/show_bug.cgi?id=456874 Mircea Kitsune changed: What|Removed |Added Summary|Changes to accent color are |Changes to accent color or |sometimes not updated in|color scheme are sometimes |Firefox and Thunderbird |not updated in applications -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456874] Changes to accent color are sometimes not updated in Firefox and Thunderbird
https://bugs.kde.org/show_bug.cgi?id=456874 --- Comment #3 from Mircea Kitsune --- Created attachment 150715 --> https://bugs.kde.org/attachment.cgi?id=150715=edit Screenshot of Dolphin Actually when it comes to the Breeze colorized icons for directories, the issue exist in Dolphin too though it may be for different causes. Some directories don't have their icon updated immediately and require you hit F5 to refresh, including the preview in the sidebar if you have a directory selected. Sometimes even if you refresh the old color still appears on directories, in those cases it seems to go away if I navigate to another path then return and refresh after that. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456874] Changes to accent color are sometimes not updated in Firefox and Thunderbird
https://bugs.kde.org/show_bug.cgi?id=456874 --- Comment #2 from Mircea Kitsune --- Created attachment 150713 --> https://bugs.kde.org/attachment.cgi?id=150713=edit Screenshot of Thunderbird -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456874] Changes to accent color are sometimes not updated in Firefox and Thunderbird
https://bugs.kde.org/show_bug.cgi?id=456874 --- Comment #1 from Mircea Kitsune --- Created attachment 150712 --> https://bugs.kde.org/attachment.cgi?id=150712=edit Screenshot of Firefox -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456874] Changes to accent color are sometimes not updated in Firefox and Thunderbird
https://bugs.kde.org/show_bug.cgi?id=456874 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456874] New: Changes to accent color are sometimes not updated in Firefox and Thunderbird
https://bugs.kde.org/show_bug.cgi?id=456874 Bug ID: 456874 Summary: Changes to accent color are sometimes not updated in Firefox and Thunderbird Product: systemsettings Version: 5.25.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: sonichedgehog_hyperblas...@yahoo.com CC: noaha...@gmail.com, tantalising...@gmail.com, uhh...@gmail.com Target Milestone: --- SUMMARY After upgrading to Plasma 5.25.3 to enjoy the new accent color features, I noticed a few issues remain with some applications. When using wallpaper based accent coloring or changing the accent from system settings, parts of the toolbar will sometimes not update in Firefox and Thunderbird. I couldn't reproduce it in any KDE applications where everything seems to work fine, most likely QT apps don't have that problem and this is a GTK bug. STEPS TO REPRODUCE 1. Make sure you're using the Breeze GTK theme, open Firefox and Thunderbird. 2. In the System Settings go to Colors: Keep changing the color scheme and accent color, also try the wallpaper color with an image slideshow configured in the desktop settings. OBSERVED RESULT When certain changes are made, parts of the toolbar in Firefox or Thunderbird may fail to change and remain stuck on the old color. This includes the selection color on websites and in emails, which can be noticed if you click-drag over text in FF and TB to select it: If you open the Bookmarks menu in Firefox and select entries, you may find that has yet another selection color forgotten in between changes. You need to restart the application for those colors to be updated. EXPECTED RESULT All colors should notice changes to the accent color or the color scheme and update accordingly. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.12-3-MANJARO (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382828] Plasma panel auto-hide effect doesn't work during the first show / hide after re-enabling desktop compositing
https://bugs.kde.org/show_bug.cgi?id=382828 Mircea Kitsune changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #4 from Mircea Kitsune --- Not seeing it any more either when toggling with Alt + Shift + F12, seems to have been indeed fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453314] When changing display resolutions, desktop icons should try to keep the same position as much as possible
https://bugs.kde.org/show_bug.cgi?id=453314 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453141] When changing display resolutions, icons and widets should try to keep the same position as much as possible
https://bugs.kde.org/show_bug.cgi?id=453141 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389808] Task manager: Manual sorting occasionally stops working
https://bugs.kde.org/show_bug.cgi?id=389808 --- Comment #3 from Mircea Kitsune --- Been a while, trying to remember exactly what this was about myself. I did use to have issues with entries in the task manager freezing into place, something happened and you couldn't drag icons before or after other icons even if manual sorting was enabled, it would typically unfreeze after opening or closing some applications. I think I last saw it an year ago or more, it's possible that it was solved since. If others are sure and no one else is seeing it, it may be resolved by now, if I ever see it again I can reopen or post a new one. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 452553] Monitor instantly wakes up from energy saving in Wayland
https://bugs.kde.org/show_bug.cgi?id=452553 --- Comment #2 from Mircea Kitsune --- (In reply to Nate Graham from comment #1) > Are you sure you're on Wayland? :) I guess you reported the bug while you > were on X11? Yes: I use X11 due to this issue. I only logged into Wayland temporarily to test how the problem behaves in Plasma 5.24. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop icons and widgets do not remember their sizes and positions on a per-resolution basis
https://bugs.kde.org/show_bug.cgi?id=360478 --- Comment #262 from Mircea Kitsune --- (In reply to Nate Graham from comment #261) > In comment 122 of this bug report, you can see the commit by Marco Martin to > make widgets remember their positions per-resolution. Sorry about that, was a little confused and must have missed it. Then this should be fully solved. Thanks for all the work on finding a solution! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 452553] Monitor instantly wakes up from energy saving in Wayland
https://bugs.kde.org/show_bug.cgi?id=452553 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets and Folder View icons do not remember their sizes and positions on a per-resolution basis
https://bugs.kde.org/show_bug.cgi?id=360478 Mircea Kitsune changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #253 from Mircea Kitsune --- (In reply to Bharadwaj Raju from comment #252) > It does not, actually. That would require a separate fix. Thanks for clarifying. The problem I was experiencing had to do with the system monitor widgets I place on the right side of the screen, they'd get shrunken and repositioned whenever a fullscreen game lowered the resolution, once exiting the game and returning to normal resolution they'd remain positioned in the upper-left corner in a box representing the resolution the game temporarily switched to. I'm glad at least Folder View works now, but it would be appreciated if a fix for plasmoids was possible as well. I'll set this to reopened with that in mind, as the issue was also about widgets on the desktop. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 452553] New: Monitor instantly wakes up from energy saving in Wayland
https://bugs.kde.org/show_bug.cgi?id=452553 Bug ID: 452553 Summary: Monitor instantly wakes up from energy saving in Wayland Product: frameworks-kwayland Version: 5.73.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: sonichedgehog_hyperblas...@yahoo.com CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY For many years the Plasma Wayland session suffered from issues with monitor standby breaking things, which has been the one explicit reason why I still need to use the X11 session. In the past the problem was the session crashing whenever the screen went into power saving, typically Plasmashell or Kwin or the screen locker. Allegedly this was because Wayland didn't know how to handle being left without any displays: I understand a fake display is now being used which keeps the desktop from freaking out. I tried this again under Plasma 5.24.3, and for the first time the screen powering off did not appear to crash or break anything. Unfortunately monitor standby still doesn't work: The screen immediately wakes up as it goes to sleep, instead of staying asleep until I move the mouse or press a button on the keyboard. Since all previous discussion about monitor standby not working in Wayland was related to processes crashing, I wanted to open a new report focusing on the screen not staying powered down. Let us know what's documented on this issue so far, and what extra information you'd like me to provide to better understand it. It's worth noting that problems with monitors not staying asleep exist with X11 as well: I need to disable the KScreen 2 service from System Settings - Workspace - Startup and Shutdown - Background Services, only then the monitor won't wake up immediately... in Wayland the monitor always wakes up instantly after going to sleep, regardless whether KScreen 2 is stopped or running. I remember that at least with the previous monitor, this wasn't always an issue when using a DVI cable, but both HDMI and DisplayPort would introduce such problems, and yes I tried different cables the last of which are high quality and explicitly the latest version of the interface. All of my video cards are AMD and use the amdgpu module. I believe it was suggested that I look for a setting in the monitor's OSD having to do with automatic source detection, I looked everywhere but couldn't find such an option. STEPS TO REPRODUCE 1. Select Plasma (Wayland) as the session in SDDM and log in. 2. Go to System Settings - Hardware - Power Management - Energy Saving. Enable the checkbox for Screen Energy Saving. Set the Switch off After counter to 1 minute for quick testing. 3. Wait for a minute without using the mouse or keyboard. OBSERVED RESULT At first the screen powers off and goes black accordingly, but after a second wakes right back up. EXPECTED RESULT The screen must stay powered off until moving the mouse or pressing a button on the keyboard. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.16.14-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets and Folder View icons do not remember their sizes and positions on a per-resolution basis
https://bugs.kde.org/show_bug.cgi?id=360478 --- Comment #251 from Mircea Kitsune --- Wonderful to see this resolved! The message seems to refer to folder view though: Does the solution also address widgets placed on the desktop? If yes this should be good. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets and Folder View icons do not remember their sizes and positions on a per-resolution basis
https://bugs.kde.org/show_bug.cgi?id=360478 --- Comment #219 from Mircea Kitsune --- I'd rather contribute positively than being negative if possible. There is one thing I can't avoid adding myself: For a bug like this to be open for 6 years now with no attempted solution in sight... I get the feeling the KDE team must be seriously understaffed and in need of help. This shouldn't be some complex revolutionary feature, unlike many that were in fact added to recent versions of Plasma which are amazing! If KDE had the amazing amount of effort I see going into Blender it could be more complete than we imagine today. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443757] Please bring back cover switch effect
https://bugs.kde.org/show_bug.cgi?id=443757 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API
https://bugs.kde.org/show_bug.cgi?id=438883 --- Comment #23 from Mircea Kitsune --- Can anyone confirm if this was successfully reimplemented in Plasma 5.24 as I understand the planning was? I'm still on 5.23 while waiting for the new release to reach Manjaro stable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash when turning off or unplugging monitor
https://bugs.kde.org/show_bug.cgi?id=449957 --- Comment #4 from Mircea Kitsune --- I only know I'm waiting for at least 3 years on the Wayland session to fix issues with monitor standby. The one and only reason I'm still stuck on X11 is everything crashes when my monitor goes into power saving, which I must enable to conserve power and preserve the screen. Even when it doesn't crash by some miracle, the monitor immediately wakes back up after powering down so power saving still won't work. HDMI and DisplayPort both do this. Whatever it is, please try to fix it in the upcoming Plasma 5.24! Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash when turning off or unplugging monitor
https://bugs.kde.org/show_bug.cgi?id=449957 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449352] Widgets positioned to the right of the panel return left after Plasma restarts
https://bugs.kde.org/show_bug.cgi?id=449352 --- Comment #1 from Mircea Kitsune --- I just realized you can use spacers on the panel to work around this issue, probably the right way of doing it anyway. This is still a bug since the editor lets you drag widgets to the right just doesn't persist them between restarts... if the feature didn't exist you wouldn't be able to do the dragging, since you can it should also remember your changes then. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 449402] Latte doesn't fill the panel width, causes system tray / clock / etc to move left
https://bugs.kde.org/show_bug.cgi?id=449402 --- Comment #2 from Mircea Kitsune --- Thanks for clarifying: If this is intentional and not a bug it makes sense. I can confirm spacers work, I'll be using that approach in that case. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 449402] Latte doesn't fill the panel width, causes system tray / clock / etc to move left
https://bugs.kde.org/show_bug.cgi?id=449402 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 449402] New: Latte doesn't fill the panel width, causes system tray / clock / etc to move left
https://bugs.kde.org/show_bug.cgi?id=449402 Bug ID: 449402 Summary: Latte doesn't fill the panel width, causes system tray / clock / etc to move left Product: lattedock Version: 0.10.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: sonichedgehog_hyperblas...@yahoo.com Target Milestone: --- Created attachment 146092 --> https://bugs.kde.org/attachment.cgi?id=146092=edit Screenshot SUMMARY When placed on a panel, the Latte task manager will not fill the panel and take up its entire width, causing widgets to its right (system tray, clock, etc) to be positioned at its left rather than at the right side of the screen. The default Task Manager and Icon Only Task manager take this approach which seems to be the safe and correct technique. STEPS TO REPRODUCE In a standard Plasma setup you can just right-click the existing task manager and select Show Alternatives then replace it with Latte, or just place it on the bottom panel manually if that fails. OBSERVED RESULT The first thing you'll notice is how your system tray and clock move to the center of the panel then move around based on how many tasks you have open. EXPECTED RESULT It feels like Latte should behave like the builtin task managers in this regard, not changing the size of the entire plasmoid. ADDITIONAL INFORMATION It might be a good idea to have an option for this? One that allows you to pick where and how you want the icons to be positioned: Either dynamically scale the widget (current functionality), fixed width aligned to the left (default task manager behavior), to the right if anyone wants that, or center them in the middle of the screen (a cool feature to have)... it should however be consistent both when the plasmoid is on the desktop or the panel. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449352] Widgets positioned to the right of the panel return left after Plasma restarts
https://bugs.kde.org/show_bug.cgi?id=449352 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449352] New: Widgets positioned to the right of the panel return left after Plasma restarts
https://bugs.kde.org/show_bug.cgi?id=449352 Bug ID: 449352 Summary: Widgets positioned to the right of the panel return left after Plasma restarts Product: plasmashell Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: sonichedgehog_hyperblas...@yahoo.com Target Milestone: 1.0 Created attachment 146064 --> https://bugs.kde.org/attachment.cgi?id=146064=edit Screenshot: Top before restart, bottom after restart SUMMARY Widgets don't seem to persist their position at the right of the bottom panel between restarts of the plasma shell, breaking the user's desktop configuration after reboot if they rely on this positioning. This can be seen when using a task manager that doesn't fill the width of the panel and automatically push widgets to its right there, such as Latte dock. Entering edit mode lets you drag widgets to the side so this feature clearly exists, just that it's not remembered. STEPS TO REPRODUCE 1. Remove the Task Manager or Icon Only Task Manager, or use Latte Dock which adjusts its width dynamically. 2. Drag the digital clock, system tray, other widgets to the right side of the panel. 3. Once you're done editing, restart plasma with the command "pkill plasmashell;kstart5 plasmashell" OBSERVED RESULT The system tray and digital clock move back to the left and now reside right of the dock. EXPECTED RESULT They should retain their position and stay at the right of the screen where they've been placed. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420039] [XWayland]: Windows are often invisible and unusable
https://bugs.kde.org/show_bug.cgi?id=420039 Mircea Kitsune changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #37 from Mircea Kitsune --- Going to assume this was fixed as I haven't seen it last time I tested Wayland, which was a while ago but WL changes a lot with each release: Most things discussed here are likely irrelevant after so many code rewrites and architecture changes. I'm on X11 due to WL still being unable to handle monitor power saving without something crashing every time; If and when that problem is someday finally resolved I'll switch for good and open new issues for any graphical glitches I may find. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 440536] Allow playing a stream on multiple outputs
https://bugs.kde.org/show_bug.cgi?id=440536 --- Comment #8 from Mircea Kitsune --- (In reply to kortrax11 from comment #7) Thanks for this information. That sounds like a big limitation in Pipewire itself. Until there's a solution for it, the interface could probably be adjusted to support this for PulseAudio without making it too weird for Pipewire users: PA remains the default over PW on most distributions as far as I'm aware, whereas I'm assuming the later will also get this limitation lifted before it's considered fully stable to use. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 --- Comment #13 from Mircea Kitsune --- (In reply to pqwoerituytrueiwoq from comment #12) > disable your monitors auto-detect source feature, that is the best workaround > there is I looked everywhere for that: My monitor OSD doesn't have an option for that, at least not any I can find. For the record my screen is a ViewSonic VX2458-C-MHD: https://www.viewsonic.com/us/products/shop/monitors/vx2458-c-mhd.html -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 426609] kscreen2 kicks monitor out of power save mode
https://bugs.kde.org/show_bug.cgi?id=426609 --- Comment #10 from Mircea Kitsune --- (In reply to pqwoerituytrueiwoq from comment #9) My monitor doesn't even have such a setting as far as I'm aware: I played with the options in its OSD countless times, never found any additional settings that could be helpful. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 426609] kscreen2 kicks monitor out of power save mode
https://bugs.kde.org/show_bug.cgi?id=426609 --- Comment #7 from Mircea Kitsune --- Is this issue truly resolved? I'm on Plasma 5.23.4 and the problem persists on multiple monitors and connectors: My mother's screen is plugged in via HDMI and affected, I connect mine on both HDMI and DisplayPort and now I get it on both. I'm having to disable kscreen2 once more, which this has the downside of waking up from standby being slower and I need to manually set the monitor from 60 Hz to 120 Hz each time I log in (the refresh rate setting won't be persisted without this service). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438839] Wayland - turning monitor off and back on causes plasmashell to make invalid xdgshell request and crash
https://bugs.kde.org/show_bug.cgi?id=438839 Mircea Kitsune changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #52 from Mircea Kitsune --- Done, hopefully this works. This issue has been around for so long and is literally the one reason why some of us can't use Wayland and need to stick to X11, hope this offers more hope in solving the issue soon. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438839] Wayland - turning monitor off and back on causes plasmashell to make invalid xdgshell request and crash
https://bugs.kde.org/show_bug.cgi?id=438839 --- Comment #50 from Mircea Kitsune --- Is it okay to reopen this please? Clearly the core issue hasn't been resolved, at best it might have been moved elsewhere. Seems this option is provided below the comment box, figured I'd ask first before messing with the bug status if it will let me as a non-reporting user. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446204] Widgets without background have fully black text with dark color schemes making them unreadable
https://bugs.kde.org/show_bug.cgi?id=446204 --- Comment #1 from Mircea Kitsune --- I wonder if this may be a Breeze specific issue to some extent: Noticed that with other themes like Materia the widget text also turns white when using a dark theme, this solves the readability problem albeit I prefer using Breeze. Maybe Breeze shouldn't flip text color when you disable the background of a widget, and instead always use the color specified in the window section of the color scheme? Black text requiring a white shadow remains an issue in either case. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446204] New: Widgets without background have fully black text with dark color schemes making them unreadable
https://bugs.kde.org/show_bug.cgi?id=446204 Bug ID: 446204 Summary: Widgets without background have fully black text with dark color schemes making them unreadable Product: plasmashell Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sonichedgehog_hyperblas...@yahoo.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 144037 --> https://bugs.kde.org/attachment.cgi?id=144037=edit Screenshot SUMMARY When using a dark color scheme and widgets without a background, both the text color and text shadow are black. This makes it next to impossible to read the font on such widgets, especially if you're using a dark wallpaper as well. STEPS TO REPRODUCE 1. Set a dark color scheme in the system settings, Breeze Dark for instance. I'm using my own in this case, if for any reason this doesn't reproduce let me know and I'll upload mine for comparison. 2. Make sure you have widgets on the desktop that contain text but have the background turned off. 3. Possibly set a dark wallpaper which makes the text even harder to read. OBSERVED RESULT Widget text is fully black thus difficult to read when the background is dark too. EXPECTED RESULT The text should be readable. I'm thinking that for a dark font the text shadow should reverse and become white or the complementary color, it might not look beautiful but should solve the readability issue. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-2-MANJARO (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon R9 390 Series ADDITIONAL INFORMATION Same result can be seen with the digital clock in the lock screen, text is black and you can barely tell the hour. In this case a desktop screenshot speaks louder than words: In the attached image you can see how my system monitor and weather widgets can barely be read. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446204] Widgets without background have fully black text with dark color schemes making them unreadable
https://bugs.kde.org/show_bug.cgi?id=446204 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 400704] Baloo indexing I/O introduces serious noticable delays
https://bugs.kde.org/show_bug.cgi?id=400704 --- Comment #42 from Mircea Kitsune --- (In reply to tagwerk19 from comment #41) Yeah 100MB sounds like a good default limit for all files. I'd make it an option in the search settings of course, users should be able to customize this based on the amount of files they have and the power of their computer. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 400704] Baloo indexing I/O introduces serious noticable delays
https://bugs.kde.org/show_bug.cgi?id=400704 --- Comment #39 from Mircea Kitsune --- (In reply to tagwerk19 from comment #38) +1 on that idea. Dolphin actually has a file size limit for generating thumbnails, in Manjaro you need to manually remove it or most images won't generate thumbnails at all. It would be more than logical to have something like this for Baloo, indicating a size limit past which a file's contents will not be indexed (only its name and location). Thanks for this suggestion. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 440536] Allow playing a stream on multiple outputs
https://bugs.kde.org/show_bug.cgi?id=440536 --- Comment #2 from Mircea Kitsune --- Has the team given any thought to this? I'm seeing it's still a limitation in 5.23.3. Any hope of seeing a solution for 5.24 perhaps? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445863] Add ability for users to customize accent color presets
https://bugs.kde.org/show_bug.cgi?id=445863 --- Comment #2 from Mircea Kitsune --- Wonderful! Thank you very much for being thoughtful and amazing as always KDE team. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445863] Add ability for users to customize accent color presets
https://bugs.kde.org/show_bug.cgi?id=445863 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445863] New: Add ability for users to customize accent color presets
https://bugs.kde.org/show_bug.cgi?id=445863 Bug ID: 445863 Summary: Add ability for users to customize accent color presets Product: systemsettings Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: sonichedgehog_hyperblas...@yahoo.com CC: jpwhit...@kde.org, mwoehlke.fl...@gmail.com Target Milestone: --- Created attachment 143802 --> https://bugs.kde.org/attachment.cgi?id=143802=edit Screenshot One of my favorite new features in Plasma 5.23.3 is the new accent colors. Seriously, thank you for implementing this! It finally saves me from having to create and maintain a dozen copies of each color scheme just to customize the highlight of every item in each. I had only one request for a minor change regarding it: May we be be allowed to customize the presets to our own colors of choice? You only have a few options on that bar at the top of the window, which are good enough in my book to be fair, still I’d like the ability to set them to my own custom colors and tweak the brightness and saturation. It would be nice if we could even as little as a config file (eg: ~/.config/plasma/accentcolors.cfg) where we can set the hex codes of the colors available there (currently 10 presets). For clarification since this was brought up elsewhere: I know the selection color can be customized in the color schemes as before. This is solely about the new accent colors independent of color scheme: You now have those colored circles in the top bar where you can click on to pick one, I wanted to know if the colors you have available there can be customized by the user or will be hard coded into KDE forever. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API
https://bugs.kde.org/show_bug.cgi?id=438883 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com --- Comment #17 from Mircea Kitsune --- Although I've no longer been using the desktop cube animation for a while, I second this request: Please don't actually remove it! The last thing an user wants to deal with, alongside running into any major bugs, is features they enjoy going away because someone wise thought it's too obscure to matter. Code cleanness and optimization is a great target to go by in everything, but I strongly believe it must be done without removing entire features with no alternative in place. A bonus thought: This might be a good chance to implement a new and even better desktop cube. I always thought it would be nice if we could have proper 3D effects for windows, such as being able to drag them in full 3D space like sheets of paper. It would be a different feature and unrelated to this discussion, but goes well with the thought of putting something better in place if an older alternative felt less than optimal. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com --- Comment #34 from Mircea Kitsune --- Although I've no longer been using the desktop cube animation for a while, I second this request: Please don't actually remove it! The last thing an user wants to deal with, alongside running into any major bugs, is features they enjoy going away because someone wise thought it's too obscure to matter. Code cleanness and optimization is a great target to go by in everything, but I strongly believe it must be done without removing entire features with no alternative in place. A bonus thought: This might be a good chance to implement a new and even better desktop cube. I always thought it would be nice if we could have proper 3D effects for windows, such as being able to drag them in full 3D space like sheets of paper. It would be a different feature and unrelated to this discussion, but goes well with the thought of putting something better in place if an older alternative felt less than optimal. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 --- Comment #8 from Mircea Kitsune --- Got on Plasma 5.23.3 in Manjaro. Even in this release the issue hasn't been fully addressed: Tested Wayland session again on my mother's computer, it uses a common HDMI connection for the monitor. Once the monitor shut itself off, it came right back up as usual... this time however I only saw the desktop wallpaper and none of the keys worked, it's like the entire system froze as not even Alt + Shift + F# to change runlevel worked any more, though I could still move the mouse pointer around which was peculiar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438839] Wayland - turning monitor off and back on causes plasmashell to make invalid xdgshell request and crash
https://bugs.kde.org/show_bug.cgi?id=438839 --- Comment #47 from Mircea Kitsune --- Got on Plasma 5.23.3 in Manjaro. Even in this release the issue hasn't been fully addressed: Tested Wayland session again on my mother's computer, it uses a common HDMI connection for the monitor. Once the monitor shut itself off, it came right back up as usual... this time however I only saw the desktop wallpaper and none of the keys worked, it's like the entire system froze as not even Alt + Shift + F# to change runlevel worked any more, though I could still move the mouse pointer around which was peculiar. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 442786] Search doesn't work in symlinked directories when Baloo is enabled
https://bugs.kde.org/show_bug.cgi?id=442786 --- Comment #4 from Mircea Kitsune --- The problem as I'm noticing it is even greater, as there isn't even fallback to the simple search: Search doesn't work at all and returns no results. I'm assuming the system is trying to use Baloo in this case too, but it doesn't understand symlinks accordingly so it ends up returning empty results. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444161] Wayland - Turning monitor off then on again causes the shell to crash
https://bugs.kde.org/show_bug.cgi?id=444161 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 Mircea Kitsune changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=413618 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413618] When I assign a key combination to turn off the screen and apply it the display output stays off only for one second and then power on again automatically ...
https://bugs.kde.org/show_bug.cgi?id=413618 Mircea Kitsune changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=422455 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 426609] kscreen2 kicks monitor out of power save mode
https://bugs.kde.org/show_bug.cgi?id=426609 Mircea Kitsune changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=422455 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 Mircea Kitsune changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=426609 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413618] When I assign a key combination to turn off the screen and apply it the display output stays off only for one second and then power on again automatically ...
https://bugs.kde.org/show_bug.cgi?id=413618 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 426609] kscreen2 kicks monitor out of power save mode
https://bugs.kde.org/show_bug.cgi?id=426609 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 442786] Search doesn't work in symlinked directories when Baloo is enabled
https://bugs.kde.org/show_bug.cgi?id=442786 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com --- Comment #2 from Mircea Kitsune --- Created attachment 141779 --> https://bugs.kde.org/attachment.cgi?id=141779=edit Example screenshot, search Now we preform a search in each window. In the original directory the results show up. In the symlink window, "no items matching the search" is printed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 442786] Search doesn't work in symlinked directories when Baloo is enabled
https://bugs.kde.org/show_bug.cgi?id=442786 --- Comment #1 from Mircea Kitsune --- Created attachment 141778 --> https://bugs.kde.org/attachment.cgi?id=141778=edit Example screenshot, directories A screenshot showing an example directory on my machine. /home/username/Pictures is a symlink pointing to /archive/username/Pictures. As can be seen the content of the directories is identical, they are the same just that one is accessed from the original path and the other from the symlink. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 442786] New: Search doesn't work in symlinked directories when Baloo is enabled
https://bugs.kde.org/show_bug.cgi?id=442786 Bug ID: 442786 Summary: Search doesn't work in symlinked directories when Baloo is enabled Product: frameworks-baloo Version: 5.85.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: baloo-bugs-n...@kde.org Reporter: sonichedgehog_hyperblas...@yahoo.com Target Milestone: --- SUMMARY When Baloo is active, searching symlinked directories in Dolphin always returns no results. You can only search inside the original directory at its real path, never through a symlink as well. STEPS TO REPRODUCE Create a directory ~/foo. Control + Shift + Left-Click drag it to create a symlink as ~/bar. Place any file inside ~/foo. OBSERVED RESULT Go inside ~/foo and use Control + F to open the search bar and do a search, this should work normally and give you results. Now go in ~/bar (its symlink) and do the same, you will be told no results could be found. EXPECTED RESULT The search system should be aware of symlinks and show search results as if you're looking at the directory through its original path. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.2-1-MANJARO (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 400704] Baloo indexing I/O introduces serious noticable delays
https://bugs.kde.org/show_bug.cgi?id=400704 --- Comment #32 from Mircea Kitsune --- The issue seems to have gotten somewhat better at this day, especially with the latest Plasma version 5.22. Though I've since moved to using an SSD / NVME drive, might be why disk sleep isn't as bad as it used to be during indexing. Another issue now seems to be the baloo processes are using more memory than I wish they did, based on the amount of files it indexed. If anyone has a large HDD but not enough RAM, they'll need to blacklist every large directory. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #46 from Mircea Kitsune --- (In reply to Zamundaaa from comment #43) A virtual fallback output sounds like a promising start: From what I understood so far these crashes occur because Wayland doesn't know how to handle being left without any display device. At this point I can agree even with a way to trick the pipeline into not freaking out in that scenario, even if it's not ideal long term from a programming standpoint. Unfortunately, as comment 44 describes above, even this doesn't resolve our issue just yet. Thank you Seqularise for testing so rapidly to confirm this. Is it known what else is happening to still cause those crashes? -- You are receiving this mail because: You are watching all bug changes.
[pulseaudio-qt] [Bug 440536] Audio settings don't allow selecting multiple outputs
https://bugs.kde.org/show_bug.cgi?id=440536 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[pulseaudio-qt] [Bug 440536] New: Audio settings don't allow selecting multiple outputs
https://bugs.kde.org/show_bug.cgi?id=440536 Bug ID: 440536 Summary: Audio settings don't allow selecting multiple outputs Product: pulseaudio-qt Version: 1.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: nicolas.fe...@gmx.de Reporter: sonichedgehog_hyperblas...@yahoo.com Target Milestone: --- Created attachment 140476 --> https://bugs.kde.org/attachment.cgi?id=140476=edit Audio settings screenshot SUMMARY This issue was brought up to me by someone close who is a streamer, to whom I suggested trying the KDE version of our Linux distribution of choice. They like the DE with the exception of a very frustrating issue: As a streamer they need to do advanced audio mixing, which involves having an application output to multiple audio devices. This is something Pulseaudio allows but the KDE interface for it doesn't. Currently they use Pulseaudio Volume Control to work around this limitation. The problem as can be seen in the attached screenshot is that every audio device is a radio button and not a checkbox: You must pick one active device but cannot select multiple. Pulseaudio itself lets you do this, it's just this interface that does not. Could the developers please consider a method to resolve this and allow picking multiple audio inputs / outputs? Thank you. STEPS TO REPRODUCE Simply go to System Settings - Hardware - Audio to see this. OBSERVED RESULT You can select just one active audio device applied to all applications. EXPECTED RESULT It would be very helpful if we were able to enable multiple output devices for sound to be piped through, ideally per-application if possible. At the moment Plasma users need tools like PAVUControl to do this. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro OS KDE Plasma Version: Plasma 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION We're aware of the setting to create a unified audio output from all devices. They clarified that isn't a good solution: They don't want the audio to go to all local outputs automatically, only certain devices of choice. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 400704] Baloo indexing I/O introduces serious noticable delays
https://bugs.kde.org/show_bug.cgi?id=400704 Mircea Kitsune changed: What|Removed |Added CC||sonichedgehog_hyperblast00@ ||yahoo.com --- Comment #30 from Mircea Kitsune --- A very real and annoying issue. I've kept Baloo disabled for years now, due to it putting my hard drive in "disk sleep" and causing processes on the system to freeze while waiting for drive access. Nowadays I have a different HDD setup so I managed to enable it with some directories blacklisted. Still eats more RAM than it should... if it's not drive I/O it's gonna be the memory or CPU. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #42 from Mircea Kitsune --- (In reply to miku84 from comment #41) > Hi All, > > I am having this issue since a while which forced me: > -do not forget to turn on monitor before computer > -disable monitor autosuspend, even do not turn it off > otherwise plasma wayland gives only black screen back :( > > A single listening to music needs monitor turned on, pls. fix it ASAP. > thanks This is the one reason why I'm having to stick to X11 right now: Everything else works almost perfectly on Wayland except for the monitor! I have one screen which I don't need to unplug at runtime... however I want it to go into standby after 5 minutes of inactivity, to reduce wear and most importantly my electricity consumption. If I were to use Wayland I'd have to keep my monitor on all the time, for a computer I leave powered on overnight: I can't throw money away on pointless electricity usage. So I second: PLEASE fix this in the next Plasma release! Plasma Wayland has been around for years, yet in such a long time something as basic as monitor standby couldn't be safely implemented? Part of the fix in the display stack was done in 5.22, the crash was reduced but is still there and the monitor still wakes up right after going to sleep. Test via DisplayPort cable if possible, the issue may still be related this connection more. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #38 from Mircea Kitsune --- I could confirm today the issue is far from resolved in Plasma 5.22 (Manjaro Linux) albeit it has gotten a step closer to being fixed. I tried the Wayland session and let my monitor go into standby with the following results: This time I'm taken to a black screen with a message written in large font, saying the screen locker stopped working and I need to use a systemctl command to unlock my session. Out of curiosity I jumped to another runlevel (Control + Alt + F#) logged in as root and unlocked: This time I could at least return to my session without noticing any major glitches! But icons on my taskbar were reordered, indicating plasmashell might have crashed and restarted. The monitor obviously didn't remain in standby: It attempts going to sleep then wakes up and I'm faced with the message about the screen locker crash. -- You are receiving this mail because: You are watching all bug changes.
