[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)
https://bugs.kde.org/show_bug.cgi?id=483691 --- Comment #12 from S. Christian Collins --- (In reply to Nate Graham from comment #11) > Glad to hear it. S. Christian Collins, is that your experience too? Yes, this does appear to be fixed now! Hooray! -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 485407] polkit-kde-agent crashes with nullptr
https://bugs.kde.org/show_bug.cgi?id=485407 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407459] new notifications: Abnormal space appears below "Open" and hamburger buttons when a download is completed
https://bugs.kde.org/show_bug.cgi?id=407459 --- Comment #20 from S. Christian Collins --- Reading again through the comments, I realize I've had the "morphing popups" desktop effect disabled for a while now, which might be why I no longer see the bug (or any of the other bugs that effect creates). So, the bug might still be out there, folks. Be sure to lock your doors at night and count your kids. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464086] keyboard selection gets stuck when trying to delete a file permanently
https://bugs.kde.org/show_bug.cgi?id=464086 S. Christian Collins changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from S. Christian Collins --- This bug was fixed at some point. Closing. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425007] dolphin loses "all desktops" setting when a folder is opened via another application
https://bugs.kde.org/show_bug.cgi?id=425007 S. Christian Collins changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #6 from S. Christian Collins --- I haven't been able to reproduce this bug for a long time, so I consider it fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468371] Kate window rules: "All Desktops" + "No titlebar and frame" = pager & taskbar only see Kate on Desktop #1
https://bugs.kde.org/show_bug.cgi?id=468371 S. Christian Collins changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #5 from S. Christian Collins --- I have not encountered this bug in a while, so I am closing it. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 453452] creating 7zip archive of ~/.mozilla or ~/.thunderbird folder fails
https://bugs.kde.org/show_bug.cgi?id=453452 --- Comment #1 from S. Christian Collins --- This bug is still present in Ark 24.02.2 (Plasma 6.0.4). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407459] new notifications: Abnormal space appears below "Open" and hamburger buttons when a download is completed
https://bugs.kde.org/show_bug.cgi?id=407459 --- Comment #18 from S. Christian Collins --- I haven't experienced this bug in a long, long time. I'd say we can probably close it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 S. Christian Collins changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #20 from S. Christian Collins --- I can no longer reproduce this in Plasma 6. Closing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483689] Invisible text in some widget settings with mixed light/dark theme e.g. Breeze Twilight
https://bugs.kde.org/show_bug.cgi?id=483689 --- Comment #7 from S. Christian Collins --- Created attachment 168619 --> https://bugs.kde.org/attachment.cgi?id=168619=edit new look of the bug (sensors details) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483689] Invisible text in some widget settings with mixed light/dark theme e.g. Breeze Twilight
https://bugs.kde.org/show_bug.cgi?id=483689 --- Comment #6 from S. Christian Collins --- Created attachment 168618 --> https://bugs.kde.org/attachment.cgi?id=168618=edit new look of the bug (pie chart details) With the upgrade to Plasma 6.0.4 and Frameworks 6.1.0, this bug has changed its colors, literally. Previously, the text color for certain widgets was being pulled from the dark plasma theme, conflicting with the light application theme making the white text impossible to read against the white background (when using Twilight). Now, the widget background is also being pulled from the plasma theme, leading to cases of hard to read black text on a dark background and white check marks instead of black. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482899] Dolphin can't write to folder with group write access
https://bugs.kde.org/show_bug.cgi?id=482899 --- Comment #10 from S. Christian Collins --- I can confirm this bug is indeed fixed in Frameworks 6.1. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484473] Symbolic icons have wrong color when using Twilight theme
https://bugs.kde.org/show_bug.cgi?id=484473 --- Comment #5 from S. Christian Collins --- Perhaps the assigned component of this bug should be changed from "widget explorer" to "icon" or whatever is most appropriate, as this issue clearly affects more than just the widget explorer. Being assigned to the wrong component might hamper this bug's visibility to the pertinent developers. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)
https://bugs.kde.org/show_bug.cgi?id=483691 --- Comment #9 from S. Christian Collins --- I took a video reproducing steps 4 and 5 above on my laptop (after the reboot): https://youtu.be/Ew2JgrpOG7I -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)
https://bugs.kde.org/show_bug.cgi?id=483691 --- Comment #8 from S. Christian Collins --- (In reply to Nate Graham from comment #7) > Either way, we need to know if it reproduces at all in a new clean user > account. Thanks all! When I try these steps in a new user account with no changes to the UI from default, the following happens: 1. Plug in the monitor and configure to the left of primary screen: the panel works fine. 2. Unplug the monitor: the right side of the panel becomes unresponsive. 3. Reboot & log in again. Panel will again be responsive. 4. Plug in the monitor (which will remember its configuration to the left of primary): panel is unresponsive. 5. Unplug the monitor: all but the leftmost bit of the panel remains unresponsive. I haven't tried this yet with VirtualBox, but here is the system info from the laptop on which I reproduced the above: OS: KDE Neon 6.0 User Edition (Plasma Desktop 6.0.3, KDE Frameworks 6.0.0, Qt 6.7.0) Linux Kernel: 6.5.0-27-lowlatency (64-bit) PC: HP Pavilion m6-1035dx laptop CPU/GPU: AMD A10-4600M 2.3 GHz quad-core APU with Trinity [Radeon HD 7660G] Graphics (using radeon driver) RAM: 8GB DDR3 (2x 4GB PC3-12800 1600 MHz), 7.2GB usable Screen #1 (LVDS-1, screen 0): - Resolution: 1366 x 768 @ 60 Hz Screen #2 (HDMI-A-1, screen 1): - Monitor: Dell P170Sb 17" LCD Monitor - Resolution: 1280 x 1024 @ 75 Hz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)
https://bugs.kde.org/show_bug.cgi?id=483691 --- Comment #5 from S. Christian Collins --- Just now after testing your last steps, I unplugged the secondary monitor, and only some parts of the panel became responsive again to clicks. The panel itself isn't dead, though... I can still hit the Meta key to bring up the menu. It's just dead to mouse clicks throughout some areas of the panel. Again, this bug only happens when the secondary monitor is configured *to the left* of primary. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)
https://bugs.kde.org/show_bug.cgi?id=483691 --- Comment #4 from S. Christian Collins --- (In reply to Nate Graham from comment #3) > Sounds a bit like Bug 483188. Does it start working if you restart > plasmashell or maximize and de-maximize a window? Neither of these steps work. The command to restart plasmashell (systemctl --user restart plasma-plasmashell) does nothing. The panel just sits there, frozen until I unplug the secondary monitor. Also, while I mentioned that my affected laptop has an AMD GPU, I can reproduce this bug in VirtualBox on a different system with an NVIDIA graphics card (though obviously the NVIDIA driver is not running inside the virtual machine). See the video linked in my original report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483689] invisible text in widget settings
https://bugs.kde.org/show_bug.cgi?id=483689 --- Comment #4 from S. Christian Collins --- (In reply to Nate Graham from comment #3) > I can't reproduce the issue. I suspect it may be related to the color sin > your active color scheme or Plasma theme. Can you reproduce it in a new > clean user account? Aah! The issue only appears when using "Breeze Twilight" (light application theme with dark plasma theme). Perhaps the affected text boxes are getting their text color from the plasma theme rather than the application theme? I tested this in a KDE neon VirtualBox install (X11), rebooting between each theme change as the plasma theme didn't fully change over until I did. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)
https://bugs.kde.org/show_bug.cgi?id=483691 --- Comment #2 from S. Christian Collins --- (In reply to Nate Graham from comment #1) > What GPU hardware are you using? It is an old AMD APU: AMD A10-4600M 2.3 GHz quad-core APU with Trinity [Radeon HD 7660G] Graphics (using radeon driver) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483684] memory monitor circle sometimes stuck at 100%
https://bugs.kde.org/show_bug.cgi?id=483684 S. Christian Collins changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- --- Comment #4 from S. Christian Collins --- (In reply to Nate Graham from comment #3) > > *** This bug has been marked as a duplicate of bug 477983 *** Nate, I don't think these are the same bugs. In bug #477983, it is the sensor data that is incorrect. In my bug, the reported value is correct, but the graphical representation (circle) is occasionally stuck at 100%. Also, in my original report, I had said this only happens on my laptop. I finally had it happen for the first time on my desktop just the other day. I wonder if system speed is a factor? My laptop is quite old and slow compared to my much faster desktop and has the bug happen much more frequently. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 407672] printer changes not saved when clicking "Apply"
https://bugs.kde.org/show_bug.cgi?id=407672 S. Christian Collins changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #10 from S. Christian Collins --- Yes, this bug is now fixed. The "Apply" button never becomes active when changing printer settings, so the user can only hit "OK", which works. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484473] Symbolic icons have wrong color when using Twilight theme
https://bugs.kde.org/show_bug.cgi?id=484473 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com --- Comment #2 from S. Christian Collins --- Created attachment 167916 --> https://bugs.kde.org/attachment.cgi?id=167916=edit wrong color discover and telegram tray icons I can also confirm this behavior on two systems (one X11, one Wayland) after the update to Plasma 6.0.3. Affects the discover update notifier and telegram, among others. I am also using the Twilight theme. OS: KDE neon 6.0 User Edition KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475468] On X11 with NVIDIA GPU, window and panel resizing is very laggy when any panels are set to Floating or Adapting transparency
https://bugs.kde.org/show_bug.cgi?id=475468 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 483701] New: unable to launch Software Sources - root password never accepted
https://bugs.kde.org/show_bug.cgi?id=483701 Bug ID: 483701 Summary: unable to launch Software Sources - root password never accepted Classification: Applications Product: Discover Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Clicking the "Software Sources" button in Discover's "Settings" page prompts for the root password, but the root password (sudo) is never accepted. STEPS TO REPRODUCE These steps are for KDE neon and might vary for other distributions. 1. Make sure "software-properties-qt" is installed. 2. Start Discover. 3. Wait for update check to finish. 4. Navigate to the "Settings" page. 5. Click the "Software Sources" button on the right side of the page. OBSERVED RESULT A window pops up prompting for the root password. It has the window title "Run as root — KDE su" and says "The action you requested needs root privileges. Please enter root's password below or click Ignore to continue with your current privileges. Command: /usr/bin/software-properties-qt". After entering the user's password (since Ubuntu uses sudo), another box pops up with: "Permission denied. Possibly incorrect password, please try again. On some systems, you need to be in a special group (often: wheel) to use this program." The password continues to be prompted, but is never accepted. EXPECTED RESULT Sudo password should be accepted and software properties launched. SOFTWARE/OS VERSIONS Linux: KDE neon 6.0 User Edition 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.
[kwin] [Bug 483698] choppy framerate in X11 after upgrade to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=483698 --- Comment #2 from S. Christian Collins --- I also tested the following environment variables found in other framerate-related bug reports, but neither of them had any affect in my case: --- KWIN_DRM_DISABLE_BUFFER_READABILITY_CHECKS=1 KWIN_DRM_NO_AMS=1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483698] choppy framerate in X11 after upgrade to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=483698 --- Comment #1 from S. Christian Collins --- Testing with the KWIN_X11_NO_SYNC_TO_VBLANK=1 environment variable set, I am now getting well over 60 FPS constantly, so my issue would seem to be possibly vsync related. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483698] New: choppy framerate in X11 after upgrade to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=483698 Bug ID: 483698 Summary: choppy framerate in X11 after upgrade to Plasma 6 Classification: Plasma Product: kwin Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: s_chriscoll...@hotmail.com Target Milestone: --- Created attachment 167280 --> https://bugs.kde.org/attachment.cgi?id=167280=edit additional information from Info Center SUMMARY Since upgrading my laptop to Plasma 6, the compositor performance in X11 has become very choppy. I previously had smooth 60 fps for desktop effects, but now I get around 32-35 fps when moving a window around and 45-50 fps when doing nothing. Switching to Wayland, everything stays at a smooth 60 fps. Here is a video comparing X11 vs. Wayland performance on my laptop: https://youtu.be/O5LSSBpYJW0 SOFTWARE/OS VERSIONS Linux: KDE neon 6.0 User Edition KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 LAPTOP INFO PC: HP Pavilion m6-1035dx CPU/GPU: AMD A10-4600M 2.3 GHz quad-core APU with Trinity [Radeon HD 7660G] Graphics (using radeon driver) RAM: 8GB DDR3 (2x 4GB PC3-12800 1600 MHz), 7.2GB usable ADDITIONAL INFORMATION I have attached additional system information from Info Center. I also use the following X11 settings for my GPU, though deleting this file appears to make no difference to performance: --- Section "Device" Identifier "Card0" Driver "radeon" Option "AccelMethod" "glamor" Option "TearFree" "off" Option "DRI3" "1" EndSection --- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483689] invisible text in widget settings
https://bugs.kde.org/show_bug.cgi?id=483689 --- Comment #2 from S. Christian Collins --- Created attachment 167279 --> https://bugs.kde.org/attachment.cgi?id=167279=edit video showing the bug Whoops! It's attached now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483684] memory monitor circle sometimes stuck at 100%
https://bugs.kde.org/show_bug.cgi?id=483684 --- Comment #2 from S. Christian Collins --- (In reply to Arjen Hiemstra from comment #1) > This sounds like it might not have the proper maximum value and thus it ends > up just filling the entire area since it doesn't have a range. The next time > this happens, can you share the output of "kstatsviewer --details > memory/physical/used" and also the same output from when it doesn't happen? I get the same output in both cases: Name:Used Physical Memory Short Name: Used Description: Unit:B Minimum: 0 Maximum: 7.75892e+09 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483692] New: folder view widget in panel cannot be resized
https://bugs.kde.org/show_bug.cgi?id=483692 Bug ID: 483692 Summary: folder view widget in panel cannot be resized Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com CC: h...@kde.org Target Milestone: 1.0 SUMMARY When using the folder view widget in a panel, the popup cannot be resized, even though a resize cursor is offered when hovering the cursor over the edges of the popup. STEPS TO REPRODUCE 1. Add "Folder View" widget to the panel. 2. Click the icon to open the widget and attempt to resize any of its boundaries. OBSERVED RESULT The widget cannot be resized. EXPECTED RESULT Either A: The widget should be resizable. Or B: The resize cursor should not be shown. SOFTWARE/OS VERSIONS Linux: KDE neon 6.0 User Edition 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 483691] New: plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)
https://bugs.kde.org/show_bug.cgi?id=483691 Bug ID: 483691 Summary: plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland) Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 167269 --> https://bugs.kde.org/attachment.cgi?id=167269=edit journal entries from plasma panel crash in X11 SUMMARY If I connect a secondary monitor and have it arranged to the left of the primary screen, icons on the left side of the plasma panel become unresponsive to mouse clicks. Icons on the right side of the panel seem to work fine, and pressing the Meta key brings up the application launcher just fine. I have been able to reproduce this both in VirtualBox and on real hardware. This bug only happens if I am already logged into a Wayland session before connecting the second screen. If the second screen is connected prior to logging in, then the plasma panel functions just fine. Here is a video demonstrating the issue in VirtualBox: https://youtu.be/jGWVN3tkZr4 If I connect the secondary screen while logged into an X11 session, plasma appears to crash (black screen, panel and desktop widgets eventually reload), but once everything is back up, the panel responds as normal to mouse clicks. I have attached the system journal entries pertaining to this event, though I don't know how useful they are. No crash reporter was offered. STEPS TO REPRODUCE 1. In a Wayland session, connect a secondary screen and configure it to appear to the left of the primary screen. 2. Disconnect the screen and restart the computer. 3. Log into a Plasma Wayland session. 4. Connect the secondary screen. OBSERVED RESULT Icons on the left side of the panel are unresponsive to mouse clicks or hover actions until the secondary monitor is disconnected. EXPECTED RESULT The icons should respond as normal. SOFTWARE/OS VERSIONS Linux: KDE neon 6.0 User Edition 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.
[yakuake] [Bug 470144] Yakuake: Wayland keep above other windows not functional
https://bugs.kde.org/show_bug.cgi?id=470144 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483689] New: invisible text in widget settings
https://bugs.kde.org/show_bug.cgi?id=483689 Bug ID: 483689 Summary: invisible text in widget settings Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 SUMMARY The contents of some text fields in the settings for the system monitor widgets is sometimes invisible. The only way to see the text is by selecting it with the mouse cursor. See attached video. STEPS TO REPRODUCE 1. Add a system monitor widget to the desktop (e.g., "Memory Usage") 2. Go into the settings for the widget and look through the various pages. OBSERVED RESULT Several of the text input fields appear blank, but actually contain invisible text. In the example of the "Memory Usage" widget with default settings, this affects the "Start from Angle" and "Total Pie Angle" fields on the "Pie Chart Details" page, and if you click the edit icon on any of the sensors on the "Sensors Details" page, the resulting text box will also contain invisible text. EXPECTED RESULT All of the text should be visible. SOFTWARE/OS VERSIONS Linux: KDE neon 6.0 User Edition 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 483684] New: memory monitor circle sometimes stuck at 100%
https://bugs.kde.org/show_bug.cgi?id=483684 Bug ID: 483684 Summary: memory monitor circle sometimes stuck at 100% Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Created attachment 167265 --> https://bugs.kde.org/attachment.cgi?id=167265=edit screenshot showing the bug SUMMARY This bug only happens on my laptop, for whatever reason. Every so often (perhaps 1 out of 7 times I log in), the memory monitor widget's blue circle will be stuck at 100% for the entire session. It does show the correct usage percentage number, however. Logging out and back in usually resolves the issue. See attached screenshot. This bug has been happening for a while, even on Plasma 5, and it happens in both X11 and Wayland sessions. STEPS TO REPRODUCE 1. Add the system monitor memory usage widget to the desktop, as seen in the screenshot. I am using the following settings: * Appearance - Display Style: Pie Chart - Minimum Time Between Updates: No Limit * Pie Chart Details - Show Sensors Legend: Yes - Start from Angle: -180° - Total Pie Angle: 180° - Rounded Lines: Yes - Automatic Data Range: Yes * Sensors Details - Total Sensors: [Used Physical Memory Percentage] - Sensors: [Used Physical Memory] - Text-Only Sensors: [Total Physical Memory] 2. Have just the right hardware configuration, apparently. 3. Boot your computer normally over the course of several days. OBSERVED RESULT Occasionally the blue circle is stuck at 100%. EXPECTED RESULT The blue circle should always represent the actual memory usage. SOFTWARE/OS VERSIONS Linux: KDE neon 6.0 User Edition KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Laptop: HP Pavilion m6-1035dx CPU/GPU: AMD A10-4600M 2.3 GHz quad-core APU with Trinity [Radeon HD 7660G] Graphics (using radeon driver) RAM: 8GB DDR3 (2x 4GB PC3-12800 1600 MHz), 7.2GB usable -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483581] New: folder view in panel: cannot open item unless cursor is moved upward first
https://bugs.kde.org/show_bug.cgi?id=483581 Bug ID: 483581 Summary: folder view in panel: cannot open item unless cursor is moved upward first Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com CC: h...@kde.org Target Milestone: 1.0 Created attachment 167192 --> https://bugs.kde.org/attachment.cgi?id=167192=edit video showing the bug SUMMARY I have the folder view widget on my plasma panel for quick access to commonly-used documents. Since the upgrade to Plasma 6, items in the list will only be highlighted and launchable if I first move the mouse cursor in an upward direction. If the mouse moves downward instead, no items on the list will be highlighted or launchable. I have attached a video showing the bug. STEPS TO REPRODUCE 1. Add "Folder View" widget to the panel and make sure it is pointing to a folder that contains more than one file. 2. Click to open the widget and move your mouse cursor up and down across the folder's contents. OBSERVED RESULT Files are only highlighted when moving the cursor up. EXPECTED RESULT Files should be highlighted regardless of cursor trajectory. SOFTWARE/OS VERSIONS Linux: KDE neon 6.0 User Edition KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Repro'd in X11 and Wayland on three separate KDE neon installs, including one Virtualbox install. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482034] Some animations are not playing at the monitor's refresh rate
https://bugs.kde.org/show_bug.cgi?id=482034 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482686] The shade option works incorrectly on X11
https://bugs.kde.org/show_bug.cgi?id=482686 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com --- Comment #1 from S. Christian Collins --- What window decoration are you using? The Breeze decoration doesn't seem to have this problem. -- You are receiving this mail because: You are watching all bug changes.
[XWaylandVideoBridge] [Bug 476385] Substantially reduced stream performance with XWayland video bridge
https://bugs.kde.org/show_bug.cgi?id=476385 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423031] [Wayland] Modifier keys to move (shift), copy (ctrl) and create a link (ctrl+shift) don't work if pressed after I start to drag the file/folder
https://bugs.kde.org/show_bug.cgi?id=423031 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 483515] New: window outline doesn't match title bar when window is maximized horizontally or vertically
https://bugs.kde.org/show_bug.cgi?id=483515 Bug ID: 483515 Summary: window outline doesn't match title bar when window is maximized horizontally or vertically Classification: Plasma Product: Breeze Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com CC: kwin-bugs-n...@kde.org, uhh...@gmail.com Target Milestone: --- Created attachment 167145 --> https://bugs.kde.org/attachment.cgi?id=167145=edit screenshots showing the bug SUMMARY The Breeze window decoration outline does not fully align with windows that are maximized only horizontally or vertically. Windows that are maximized normally (filling the entire screen) appear correctly. When windows are maximized in only one direction, the following issues occur: 1. The rounded top corners of the title bar become straight. However, the outline is still drawn with a curve slicing over the now straight corner. 2. Horizontally-maximized windows should have no outline on the left or right sides of the window, but an outline is drawn on both the left and right side of the title bar (but only the title bar). 3. Vertically-maximized windows should have no outline on the top or bottom of the window, but an outline is drawn at the top of the titlebar. I have attached screenshots showing unmaximized, vertically-maximized, and horizontally-maximized window corners zoomed to 800%. STEPS TO REPRODUCE 1. Choose the "Breeze Dark" color scheme and a bright wallpaper to be able to better see the window outline. Make sure outline intensity in the Breeze window decoration settings is set to "medium" or higher for best visibility. 2. Maximize a window vertically (by middle-clicking the maximize button) or horizontally (by right-clicking the maximize button). OBSERVED RESULT The outline is erroneously drawn as described in the summary above. EXPECTED RESULT The outline should correctly match the window boundaries. SOFTWARE/OS VERSIONS Linux: KDE neon 6.0 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION This bug occurs in both X11 and Wayland. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483513] New: after color scheme edit, kcm_colors is unresponsive to further edits (X11 only)
https://bugs.kde.org/show_bug.cgi?id=483513 Bug ID: 483513 Summary: after color scheme edit, kcm_colors is unresponsive to further edits (X11 only) Classification: Applications Product: systemsettings Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com CC: noaha...@gmail.com, tantalising...@gmail.com, uhh...@gmail.com Target Milestone: --- SUMMARY After editing a color scheme, trying to edit a second color scheme does nothing. This bug happens in X11, but does not happen in Wayland. STEPS TO REPRODUCE 1. Go to System Settings → Colors & Themes → Colors. 2. Click the pencil icon to edit any theme. The KColorSchemeEditor window will appear. 3. Close the KColorSchemeEditor window. 4. Click the pencil icon to edit any theme. OBSERVED RESULT Nothing happens. EXPECTED RESULT The KColorSchemeEditor window should appear to allow editing the theme. SOFTWARE/OS VERSIONS Linux: KDE neon 6.0 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION This is possibly caused by the same underlying issue as bug #483511. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483511] New: saved copy of a color scheme doesn't appear in the list
https://bugs.kde.org/show_bug.cgi?id=483511 Bug ID: 483511 Summary: saved copy of a color scheme doesn't appear in the list Classification: Applications Product: systemsettings Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com CC: noaha...@gmail.com, tantalising...@gmail.com, uhh...@gmail.com Target Milestone: --- SUMMARY Saving a copy of a color scheme using the colors KCM in System Settings doesn't add the newly saved scheme to the list until navigating away from and back to the colors page. This bug happens in X11, but does not happen in Wayland. STEPS TO REPRODUCE 1. Go to System Settings → Colors & Themes → Colors. 2. Click the pencil icon to edit a theme, e.g. "Breeze Classic". 3. Click "Save As..." and give it a new name, e.g. "Breeze Classic 2", then click "Close". OBSERVED RESULT The new color scheme does not appear in the list. EXPECTED RESULT The new color scheme should appear in the list. SOFTWARE/OS VERSIONS Linux: KDE neon 6.0 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION I noticed that it takes much longer to open the window for editing a color scheme under X11 than it does in Wayland, where it appears pretty much instantly. Perhaps this may provide a clue? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477223] Setting an icc profile causes reduced system performance.
https://bugs.kde.org/show_bug.cgi?id=477223 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483068] must enter wireless password upon login when systemd boot is disabled
https://bugs.kde.org/show_bug.cgi?id=483068 --- Comment #2 from S. Christian Collins --- Yes, for me the issue only happens on X11. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 457565] Multiscreen: Window's shadow and outline bleed over when window is maximized or tiled to an edge adjacent to another screen
https://bugs.kde.org/show_bug.cgi?id=457565 --- Comment #10 from S. Christian Collins --- (In reply to Vince from comment #9) > Can anyone check if this is still an issue on Plasma 6? In Plasma 6, I'm seeing the shadow still bleeding over for tiled windows, but no longer for maximized windows. The outline doesn't bleed over at all, as far as I can see. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483068] New: must enter wireless password upon login when systemd boot is disabled
https://bugs.kde.org/show_bug.cgi?id=483068 Bug ID: 483068 Summary: must enter wireless password upon login when systemd boot is disabled Classification: Plasma Product: plasmashell Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Some of my startup scripts/applications fail to start with systemd boot enabled, so I have disabled it by creating "~/.config/startkderc" containing: [General] systemdBoot=false This worked without issue in Plasma 5, but in Plasma 6, this causes KDE Wallet to prompt for the wireless password every boot after logging in. This issue happens in X11, but not Wayland. The wireless network is set with the "All users may connect to this network" option, so no password prompt should be happening. STEPS TO REPRODUCE 1. Make sure you are on a laptop with a default wireless network that you auto-login to. 2. Make sure to enable "All users may connect to this network" in the wireless network options so that there should normally be no need for a wireless network password prompt. 3. Disable systemd boot. Here's a quick command to create/edit `startkderc`: kwriteconfig5 --file startkderc --group General --key systemdBoot false 4. Restart and log into a Plasma X11 session. OBSERVED RESULT A wireless password box pops up on login. The titlebar says "KDE Wallet Service" and the message reads "The application 'kded6' has requested to open the wallet 'kdewallet'. Please enter the password for this wallet below." EXPECTED RESULT I shouldn't need to enter the wireless network password as it is supposed to be remembered by the system. SOFTWARE/OS VERSIONS Linux: KDE neon User Edition 6.0 KDE Plasma Version: 6.0.0 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 483066] New: logout no longer works after disabling systemd boot
https://bugs.kde.org/show_bug.cgi?id=483066 Bug ID: 483066 Summary: logout no longer works after disabling systemd boot Classification: Plasma Product: plasmashell Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com Target Milestone: 1.0 SUMMARY Some of my startup scripts/applications fail to start with systemd boot enabled, so I have disabled it by creating "~/.config/startkderc" containing: [General] systemdBoot=false This worked without issue in Plasma 5, but in Plasma 6, disabling systemd boot causes logout to no longer work. Under X11, logging out stalls at a black screen with a mouse cursor. Under Wayland, logging out appears to do nothing. After trying to log out in Wayland, the shutdown and restart buttons will now also do nothing for the rest of the session. STEPS TO REPRODUCE 1. Disable systemd boot. Here's a quick command to create/edit `startkderc`: kwriteconfig5 --file startkderc --group General --key systemdBoot false 2. Restart and log into the desktop. 3. Click on the plasma menu, then choose "Log Out", and confirm on the following logout screen. OBSERVED RESULT Stuck on black screen with mouse cursor (X11) or nothing appears to happen, with shutdown, restart buttons becoming broken for the rest of the session (Wayland). EXPECTED RESULT The user should be logged out and back at the SDDM login screen. SOFTWARE/OS VERSIONS Linux: KDE neon User Edition 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Bug confirmed on three separate KDE neon installs (1 desktop, 1 laptop, 1 VirtualBox). -- You are receiving this mail because: You are watching all bug changes.
[KSystemLog] [Bug 482453] Unable to launch Ksystemlog with sudo privileges
https://bugs.kde.org/show_bug.cgi?id=482453 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482899] New: regression: dolphin can't write to folder with group write access
https://bugs.kde.org/show_bug.cgi?id=482899 Bug ID: 482899 Summary: regression: dolphin can't write to folder with group write access Classification: Applications Product: dolphin Version: 24.02.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: s_chriscoll...@hotmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY In the following examples, the user's login name will be "username". Dolphin 24.02.0 included with Plasma 6 cannot write to a folder that has group write access and a different owner (e.g., mode 775, "root:username" ownership). This is a regression from Plasma 5 (tested with Dolphin 21.12.3 in Kubuntu). This bug prevents writing to shared folders in VirtualBox, as the shared folders have "root:vboxsf" ownership, where the user being a member of the "vboxsf" group should be able to write to the shared folders. STEPS TO REPRODUCE 1. Create a folder "testfolder" in your home directory. 2. Change the folder owner while keeping the user's default group (e.g., "sudo chown root:username testfolder"). By default, this should already be file access mode 775 where group members have write access, but change this if it is not. 3. Exit and restart Dolphin (sometimes this is necessary to trigger the bug). 4. Open "testfolder" in Dolphin and try to create or copy a file/folder to this location. OBSERVED RESULT Dolphin forbids the user from creating/copying files within "testfolder". Performing the file operations via command line is necessary to write to the folder. EXPECTED RESULT Dolphin should recognize group write access to the folder and allow the user to write to the folder. SOFTWARE/OS VERSIONS Linux: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[kdesu] [Bug 482036] root apps not launching via desktop menu in plasma 6
https://bugs.kde.org/show_bug.cgi?id=482036 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com --- Comment #6 from S. Christian Collins --- This is easy to reproduce on KDE neon by installing "KSystemLog" from the repositories. Attempting to launch KSystemLog from the K menu will ask for your password, but the password is never accepted and the application can't be launched. -- You are receiving this mail because: You are watching all bug changes.
[knemo] [Bug 480151] Asks me for kwallet password at every startup to connect to wifi network
https://bugs.kde.org/show_bug.cgi?id=480151 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com --- Comment #2 from S. Christian Collins --- This is happening for me in KDE neon with Plasma 6.0.0, but only if I use X11. This bug does not happen when using Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482100] Maximize/minimize windows animations are very choppy because of the panel settings and Nvidia
https://bugs.kde.org/show_bug.cgi?id=482100 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481974] KMyMoney in Plasma 6 wants libKPim5IdentityManagement.so.5
https://bugs.kde.org/show_bug.cgi?id=481974 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481938] Unable to leave session via Desktop menu on Plasma 6.0.0
https://bugs.kde.org/show_bug.cgi?id=481938 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481940] krunner not launching due to org.kde.krunner.service file not installed.
https://bugs.kde.org/show_bug.cgi?id=481940 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 481306] New: radio station stream fails to play with Plasma browser integration plugin active
https://bugs.kde.org/show_bug.cgi?id=481306 Bug ID: 481306 Summary: radio station stream fails to play with Plasma browser integration plugin active Classification: Plasma Product: plasma-browser-integration Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Firefox Assignee: k...@privat.broulik.de Reporter: s_chriscoll...@hotmail.com Target Milestone: --- In Firefox, I was trying to listen to a Wisconsin, USA radio station stream for WOZN Madison, and the stream refused to start. After disabling plasma browser integration, it plays just fine. STEPS TO REPRODUCE 1. Have Plasma browser integration plugin enabled in Firefox. 2. Visit this site and attempt to listen to the radio stream: https://player.listenlive.co/72091/en OBSERVED RESULT An ad plays and then it tries to connect to the stream, but aborts and never connects. EXPECTED RESULT The radio stream should play. SOFTWARE/OS VERSIONS OS: KDE Neon 5.27 User Edition KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION The linked site does request user location info. I am not sure if the stream will play outside of the US or even the state of Wisconsin. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380939] plasmashell CPU usage climbs when using animated widgets on desktop
https://bugs.kde.org/show_bug.cgi?id=380939 --- Comment #7 from S. Christian Collins --- (In reply to Noah Davis from comment #6) > Is this still a problem? With Plasma 5.26.1, I didn't notice any issues with > an analog clock on the desktop with the second hand enabled. I haven't had this issue in a while now, so I think we can probably close this bug report. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 464225] copy/move symbolic link moves link destination instead
https://bugs.kde.org/show_bug.cgi?id=464225 --- Comment #14 from S. Christian Collins --- This bug is marked as "fixed in 5.108", but I have KDE Frameworks 5.108.0 and I can still repro the bug exactly as in my original instructions. Unless the "5.108" version is incomplete or pertaining to something other than frameworks? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469656] Dolphin cannot remember previously opened tabs
https://bugs.kde.org/show_bug.cgi?id=469656 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470050] Dolphin does not restore folders when opened through session restore
https://bugs.kde.org/show_bug.cgi?id=470050 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 469082] Freecell game modes automatically put unsafe cards on the foundation
https://bugs.kde.org/show_bug.cgi?id=469082 --- Comment #4 from S. Christian Collins --- (In reply to Stephan Kulow from comment #3) > this bug is in the freecell solver library used. which version do you have? libfreecell-solver0 is version 5.0.0-2. This is the same version that was used when the bug wasn't occurring, but kpat app was older. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 469082] Freecell game modes automatically put unsafe cards on the foundation
https://bugs.kde.org/show_bug.cgi?id=469082 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com --- Comment #2 from S. Christian Collins --- it should be noted that this bug is a regression introduced very recently, possibly with version 23.04.0. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468371] Kate window rules: "All Desktops" + "No titlebar and frame" = pager & taskbar only see Kate on Desktop #1
https://bugs.kde.org/show_bug.cgi?id=468371 --- Comment #4 from S. Christian Collins --- Created attachment 158053 --> https://bugs.kde.org/attachment.cgi?id=158053=edit screenshot of the Kate rules settings -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468371] Kate window rules: "All Desktops" + "No titlebar and frame" = pager & taskbar only see Kate on Desktop #1
https://bugs.kde.org/show_bug.cgi?id=468371 --- Comment #3 from S. Christian Collins --- Created attachment 158052 --> https://bugs.kde.org/attachment.cgi?id=158052=edit video showing the bug Here is a video of the bug in action. The first launch of Kate is only recognized by the pager and taskbar as being on Desktop 1, but the second launch is fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468371] Kate window rules: "All Desktops" + "No titlebar and frame" = pager & taskbar only see Kate on Desktop #1
https://bugs.kde.org/show_bug.cgi?id=468371 --- Comment #2 from S. Christian Collins --- Created attachment 158051 --> https://bugs.kde.org/attachment.cgi?id=158051=edit kwinrulesrc file from VirtualBox neon install (In reply to Ismael Asensio from comment #1) > I cannot reproduce. It this happening on X11 or Wayland? X11. Window rules in Wayland seems to be broken, so neither rule actually gets applied there. > Also, could you attach your ~/.config/kwinrulesrc file? It might have some > clues there. Here it is. I will also attach a video of the bug happening in a VirtualBox KDE neon install, though this bug is reproducible on my main desktop install as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 --- Comment #17 from S. Christian Collins --- With Plasma 5.27.4, the bug no longer happens on my laptop, but still happens in VirtualBox as reported in comment #9. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468371] New: Kate window rules: "All Desktops" + "No titlebar and frame" = pager & taskbar only see Kate on Desktop #1
https://bugs.kde.org/show_bug.cgi?id=468371 Bug ID: 468371 Summary: Kate window rules: "All Desktops" + "No titlebar and frame" = pager & taskbar only see Kate on Desktop #1 Classification: Plasma Product: kwin Version: 5.27.4 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: s_chriscoll...@hotmail.com CC: isma...@gmail.com Target Milestone: --- SUMMARY *** If you use window rules to have Kate appear on all desktops with no titlebar and frame, it works, but about 50% of the time, the pager and taskbar will think Kate is present only on the first desktop. *** STEPS TO REPRODUCE 1. Make sure you have multiple desktops enabled. I have 4. 2. Start Kate. 3. Click Kate's application icon in the titlebar and select "More Actions" -> "Configure Special Application Settings...". 4. Add the following window rules: • Virtual Desktop: Force: All Desktops • No titlebar and frame: Apply Initially: Yes 5. Close and restart Kate. OBSERVED RESULT Kate will appear on all desktops as expected, but there's about a 50% chance the pager and taskbar will think Kate is only present on the first desktop. When this happens, it is impossible to manage the Kate window from the taskbar (minimize, restore, etc.) when using any other desktop than the first. If you right-click on Kate's taskbar entry (from Desktop #1), under "Move to Desktop", it shows Kate as currently on "1 Desktop 1". Attempting to change this to "All Desktops" does nothing. EXPECTED RESULT The taskbar/pager should realize that Kate is running on all desktops and allow management of the window from any desktop. SOFTWARE/OS VERSIONS Linux: KDE neon 5.27 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I also run Dolphin with the same window rules, but it does not trigger this bug. WORKAROUND Close and restart Kate until the pager shows it present on all desktops. -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 446199] kstart5 ignores --desktop option
https://bugs.kde.org/show_bug.cgi?id=446199 --- Comment #8 from S. Christian Collins --- Thanks Erwan, I was able to make this work with wmctrl. However, it only works when using xorg. Does anybody know a workaround that works in Wayland? -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 464698] Sometimes the scrollbar doesn't move when clicking and dragging it
https://bugs.kde.org/show_bug.cgi?id=464698 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com --- Comment #8 from S. Christian Collins --- Whether or not the scrollbar works seems to do with how far to the right the mouse cursor is positioned when you click to drag the scrollbar. If the cursor is positioned more towards the left side of the scrollbar, it works. If it is positioned more to the right side, it doesn't. -- You are receiving this mail because: You are watching all bug changes.
[kstart] [Bug 375065] kstart --desktop is broken, autostart applications on wrong desktops
https://bugs.kde.org/show_bug.cgi?id=375065 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 446199] kstart5 ignores --desktop option
https://bugs.kde.org/show_bug.cgi?id=446199 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com --- Comment #5 from S. Christian Collins --- Until it's fixed, does anybody know a workaround for this bug? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 --- Comment #15 from S. Christian Collins --- I just tested and the bug still happens on my laptop and in Virtualbox as described in comments #6 and #9. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747
--- Comment #14 from S. Christian Collins ---
Created attachment 157048
--> https://bugs.kde.org/attachment.cgi?id=157048=edit
plasma configuration file-working now
Over the past few days, the issue of the icons moving to my secondary monitor
on has fixed itself on my desktop PC. I couldn't tell you why. Anyway, attached
is my plasma configuration file for that system in case it provides any clues.
Using Kompare between the first attachment ("plasma configuration file") and
this one shows differences, but TBH I don't understand what is going on. I'll
test on my other affected systems to see if it still happens there.
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 463603] Cannot install Wine because of Sane
https://bugs.kde.org/show_bug.cgi?id=463603 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466254] Error while installing package 'libjpeg.so.8.2.2' - latest release
https://bugs.kde.org/show_bug.cgi?id=466254 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 --- Comment #13 from S. Christian Collins --- Created attachment 156929 --> https://bugs.kde.org/attachment.cgi?id=156929=edit video of the bug in VirtualBox -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 --- Comment #12 from S. Christian Collins --- Created attachment 156928 --> https://bugs.kde.org/attachment.cgi?id=156928=edit VirtualBox plasma-org.kde.plasma.desktop-appletsrc 3-after re-login -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 --- Comment #11 from S. Christian Collins --- Created attachment 156927 --> https://bugs.kde.org/attachment.cgi?id=156927=edit VirtualBox plasma-org.kde.plasma.desktop-appletsrc 2-after icon move -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 --- Comment #10 from S. Christian Collins --- Created attachment 156926 --> https://bugs.kde.org/attachment.cgi?id=156926=edit VirtualBox plasma-org.kde.plasma.desktop-appletsrc 1-before icon move -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 --- Comment #9 from S. Christian Collins --- I have an update on this bug, along with hopefully some more insights on what might be going wrong. I was able to reproduce the bug in VirtualBox (same OS, fully updated), though the behavior of the monitors is swapped from my original report. If I place the icons on my secondary monitor in VirtualBox, then they always get moved to the primary monitor on login. For this test, I did the following steps: 1. Created "folder01" and "folder02" desktop folders on the primary screen (1366x768) in top-left position. 2. Dragged the icons to the secondary screen (1080x768), also in top-left position. 3. Logged off and back on. RESULT: The icons had moved back to the primary screen. I copied the ~/.config/plasma-org.kde.plasma.desktop-appletsrc file before the icons move, after the icons move, and after re-login. These are attached below. A notable change happens in this file under [ScreenMapping]: Before icon move: screenMapping=desktop:/folder02,0,ad5434dc-6a89-4476-99d9-c23bbe4122fd,desktop:/folder01,0,ad5434dc-6a89-4476-99d9-c23bbe4122fd After icon move: screenMapping=desktop:/folder02,1,ad5434dc-6a89-4476-99d9-c23bbe4122fd,desktop:/folder01,1,ad5434dc-6a89-4476-99d9-c23bbe4122fd After re-login: screenMapping=desktop:/folder01,0,ad5434dc-6a89-4476-99d9-c23bbe4122fd,desktop:/folder02,0,ad5434dc-6a89-4476-99d9-c23bbe4122fd I assume the number following the desktop folder name (0 or 1) indicates the screen the icons are on. You can see this getting set correctly after the icons are moved, but then being reset to 0 again upon login. Now, on my desktop system used in the original bug report, it would appear that my secondary monitor is identified as screen 0? If so, that would explain why on that system the icons get moved to the secondary monitor instead. So, something is resetting the icons' screen mapping to screen 0 on login. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 --- Comment #8 from S. Christian Collins --- This is still happening in 5.27.2. I thought I would outsmart the bug by changing my secondary monitor's mode from "Folder View" to "Desktop", but then my icons outright disappeared on login! So, I had to change it back. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466312] enable and configure screen with xrandr = no desktop
https://bugs.kde.org/show_bug.cgi?id=466312 --- Comment #7 from S. Christian Collins --- Yes. The kscreen-doctor command chain gives me a proper, usable desktop on the secondary monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466312] enable and configure screen with xrandr = no desktop
https://bugs.kde.org/show_bug.cgi?id=466312 --- Comment #5 from S. Christian Collins --- (In reply to Nate Graham from comment #4) > Instead of xrandr, If you instead run > > kscreen-doctor output.HDMI-0.disable > and > > kscreen-doctor output.HDMI-0.disable > to disable and re-enable your external screen, does Plasma react properly? Hi Nate. I assume you meant to write `kscreen-doctor output.HDMI-0.enable` for the second command. Unfortunately, this results in the screen being in "duplicate" mode rather than extending my desktop. All I could find for documentation was in "kscreen-doctor --help", which doesn't show all available options. By looking at the source code and experimenting, I finally figured out how to make this work with kscreen-doctor. At first, I had the display enabling and parameter setting in a single command, which resulted in the screen not becoming enabled, but by splitting it into two commands, it works. I have it running in a single line as follows: > kscreen-doctor output.HDMI-0.enable && kscreen-doctor > output.HDMI-0.mode.1280x1024@75 output.HDMI-0.position.1920,120 I will update my screen commands to use kscreen-doctor, since this is the officially supported way. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466312] enable and configure screen with xrandr = no desktop
https://bugs.kde.org/show_bug.cgi?id=466312 --- Comment #2 from S. Christian Collins --- (In reply to Nate Graham from comment #1) > Ultimately the same as Bug 460341 since KScreen will notice the change, > re-evaluate config data, and trigger the bug. > > *** This bug has been marked as a duplicate of bug 460341 *** Are you sure? That bug is about a display being disabled, whereas with my bug, the display is enabled and functions, but just doesn't have a wallpaper or desktop functionality. I can still drag windows to it, etc. Also, that bug appears to involve NVIDIA, but I can repro this bug in Virtualbox. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466312] New: enable and configure screen with xrandr = no desktop
https://bugs.kde.org/show_bug.cgi?id=466312 Bug ID: 466312 Summary: enable and configure screen with xrandr = no desktop Classification: Plasma Product: plasmashell Version: 5.27.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 SUMMARY *** I have keyboard shortcuts set up to disable and enable my secondary monitor: • disable: xrandr --output HDMI-0 --off • enable: xrandr --output HDMI-0 --mode 1280x1024 --rate 75 --pos 1920x120 The secondary monitor is enabled on boot and works fine, but if I disable and then re-enable the screen using the above shortcuts, the secondary monitor will be black with no desktop functionality. The cursor will show up and I can drag windows to it, but there are no wallpaper, icons, widgets, right-click menu, etc. This is a regression that I suspect is pretty recent. I was also able to reproduce this bug in Virtualbox using virtual screens and adapting the xrandr commands accordingly. Restarting plasmashell restores the secondary screen to full functionality. *** STEPS TO REPRODUCE 1. Ensure both screens are enabled and functioning correctly. 2. Run xrandr to get the screen name, resolution, position and active screen resolution & refresh rate. In my case, the line "HDMI-0 connected 1280x1024+1920+120" means screen name = "HDMI-0", resolution = "1280x1024", and position = "+1920+120". The active resolution and refresh rate is marked with an asterisk on the refresh rate. Use the values for your screen in the commands below. 3. Disable the screen: xrandr --output HDMI-0 --off 4. Re-enable the screen: xrandr --output HDMI-0 --mode 1280x1024 --rate 75 --pos 1920x120 OBSERVED RESULT The secondary screen (HDMI-0) is black with no desktop functionality. EXPECTED RESULT The secondary screen should behave normally. SOFTWARE/OS VERSIONS Linux: KDE neon 5.27 KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Video: EVGA NVIDIA GeForce GTX 980 Ti SC GAMING ACX 2.0+ w/ 6GB RAM NVIDIA video driver: 515.86.01 Screen #1 (DVI-I-1, screen 0, marked as primary): • Monitor: ASUS VG248QE 24" LCD Monitor • Resolution: 1920 x 1280 @ 120 Hz Screen #2 (HDMI-0, screen 1): • Monitor: Dell P170Sb 17" LCD Monitor • Resolution: 1280 x 1024 @ 75 Hz • Position relative to Screen #1: +1920+120 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466095] Plasma crashes in DesktopView::screenToFollow() on screen wake up when KScreen service is active
https://bugs.kde.org/show_bug.cgi?id=466095 --- Comment #6 from S. Christian Collins --- For me, the crash is indeed fixed in 5.27.1. However, now when I re-enable my secondary monitor with the xrandr command mentioned in comment #1, it's just a black screen (cursor shows, but no wallpaper or desktop functionality). I will file this as a separate bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 --- Comment #7 from S. Christian Collins --- (In reply to Marco Martin from comment #4) > did they move only the first time after upgrade, or they move back at every > reboot? They move back after every reboot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 S. Christian Collins changed: What|Removed |Added Status|NEEDSINFO |REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #6 from S. Christian Collins --- After upgrade to 5.27.1, this is still happening on my desktop system as reported above. Furthermore, I have noticed this also happens on my laptop when I connect an external screen. Here is the behavior I experience on that system: 1. If I plug in an external monitor (HDMI), the icons on my desktop move over to the secondary monitor. 2. If I move the icons back to my primary screen, unplug the secondary monitor, then plug it back in again, the icons stay on the primary screen. 3. If I reboot my computer and then repeat step 1, the icons move to the secondary monitor again. Here is the screen configuration for my laptop (OS and software versions are identical to the desktop): Screen #1 (LVDS, screen 0, primary): * Resolution: 1366 x 768 @ 60 Hz Screen #2 (HDMI-0, screen 1): Dell P170Sb 17" LCD Monitor * Resolution: 1280 x 1024 @ 75 Hz * Position relative to screen 0: -1280+368 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 462264] Plymouth Theme cut off on multi monitor setup
https://bugs.kde.org/show_bug.cgi?id=462264 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 466180] New: crash report details text box doesn't scroll to show all text
https://bugs.kde.org/show_bug.cgi?id=466180 Bug ID: 466180 Summary: crash report details text box doesn't scroll to show all text Classification: Applications Product: drkonqi Version: 5.27.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com Target Milestone: --- Created attachment 156564 --> https://bugs.kde.org/attachment.cgi?id=156564=edit screenshot showing the bug SUMMARY *** When submitting a crash report via drkonqi (in this case, adding new info to an existing bug), as I typed more info than could fit in the default window size, the text was just cut off (see attached screenshot). I continued typing, but I could only see the very tips of the letters appearing. No scrollbars appeared to allow viewing of the entire text field. The only way I could see all the text was by resizing the window. *** STEPS TO REPRODUCE 1. Report a crash using drkonqi. 2. When asked to enter details about the crash, type more details than can fit in the text box size. OBSERVED RESULT The text is cut off, and there is no way to view the new lines of text without resizing the crash handler window. EXPECTED RESULT I should be able to see the text I'm typing, and scrollbars should appear to let me view all of the text that has been entered. SOFTWARE/OS VERSIONS Linux: KDE Neon 5.27 User Edition KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466095] Plasma crashes on screen wake up
https://bugs.kde.org/show_bug.cgi?id=466095 --- Comment #1 from S. Christian Collins --- Created attachment 156563 --> https://bugs.kde.org/attachment.cgi?id=156563=edit New crash information added by DrKonqi plasmashell (5.27.0) using Qt 5.15.8 In my case, I get this segfault when disabling my secondary monitor via the command "xrandr --output HDMI-0 --off", which I have assigned to a keyboard shortcut. The crash happens almost immediately after my second screen turns off, and Plasma desktop remains terminated (black desktop, no panels) until I re-enable the secondary monitor via my shortcut for "xrandr --output HDMI-0 --mode 1280x1024 --rate 75 --pos 1920x120", after which my desktop, panels, icons, etc. all come back. I have only noticed this happening since the upgrade to Plasma 5.27, but since I don't use this feature very often, I can't be certain it was introduced with this release. -- Additional System Info: Video: EVGA NVIDIA GeForce GTX 980 Ti SC GAMING ACX 2.0+ w/ 6GB RAM NVIDIA video driver: 515.86.01 Screen #1 (DVI-I-1, screen 0, marked as primary): * Monitor: ASUS VG248QE 24" LCD Monitor * Resolution: 1920 x 1280 @ 120 Hz Screen #2 (HDMI-0, screen 1): * Monitor: Dell P170Sb 17" LCD Monitor * Resolution: 1280 x 1024 @ 75 Hz * Position relative to Screen #1: +1920+120 -- Backtrace (Reduced): #4 QWeakPointer::internalData() const (this=0x58) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer_impl.h:696 #5 QPointer::data() const (this=0x58) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qpointer.h:77 #6 QPointer::operator QScreen*() const (this=0x58) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qpointer.h:83 #7 DesktopView::screenToFollow() const (this=0x0) at ./shell/desktopview.cpp:120 #8 0x55e25628e51f in ShellCorona::screenInvariants() const (this=0x55e258056c80) at ./shell/shellcorona.cpp:828 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466095] Plasma crashes on screen wake up
https://bugs.kde.org/show_bug.cgi?id=466095 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 457565] Multiscreen: Window's shadow and outline bleed over when window is maximized or tiled to an edge adjacent to another screen
https://bugs.kde.org/show_bug.cgi?id=457565 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464417] After porting to OffscreenEffect the Invert effect causes glitches when rerendering window decoration buttons on mouse hover
https://bugs.kde.org/show_bug.cgi?id=464417 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465980] New: folder view in panel: grabbing scrollbar moves files instead
https://bugs.kde.org/show_bug.cgi?id=465980 Bug ID: 465980 Summary: folder view in panel: grabbing scrollbar moves files instead Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com CC: h...@kde.org Target Milestone: 1.0 Created attachment 156411 --> https://bugs.kde.org/attachment.cgi?id=156411=edit GIF file showing the bug SUMMARY *** If the folder view widget is added to the panel and the list of files in the popup is long enough to show a scrollbar, the scrollbar overlaps the file highlight rectangle following the cursor. If you attempt to drag the scrollbar while a file is highlighted, it will instead drag the underlying file. Please see the attached GIF file for an example. I didn't notice this bug until after the upgrade to Plasma 5.27.0, so I'm guessing it's a pretty recent regression. *** STEPS TO REPRODUCE 1. Add Folder View widget to the panel pointing to a folder with lots of files. 2. Click the Folder View icon to show the files in a popup. 3. Move the cursor across the file area over to the scrollbar (this will cause files to be highlighted along the way) and drag the scrollbar down/up. OBSERVED RESULT Instead of dragging the scrollbar, the underlying file is dragged. EXPECTED RESULT I should be able to scroll the view without accidentally grabbing a file. SOFTWARE/OS VERSIONS Linux: KDE neon 5.27 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463024] Plasma doesn't respect Sub-pixel rendering for system tray and desktop
https://bugs.kde.org/show_bug.cgi?id=463024 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747
--- Comment #3 from S. Christian Collins ---
I should also add that two of the icons on my desktop are folders located in
~/Desktop ("Handy-Dandy" and "Quick Access"), and the third is the Trash icon,
which appears in Dolphin as "trash:⁄.desktop".
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 --- Comment #2 from S. Christian Collins --- Created attachment 156258 --> https://bugs.kde.org/attachment.cgi?id=156258=edit x.org configuration file -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 --- Comment #1 from S. Christian Collins --- Created attachment 156257 --> https://bugs.kde.org/attachment.cgi?id=156257=edit plasma configuration file -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] New: desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 Bug ID: 465747 Summary: desktop icons moved to secondary monitor upon login Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 156256 --> https://bugs.kde.org/attachment.cgi?id=156256=edit video showing the bug I have three desktop icons that have been on my primary monitor for many months. After upgrading to Plasma 5.27, these icons moved to my secondary monitor. If I try to put them back to my primary monitor, they will be forced back to the secondary monitor at the next login, or when restarting plasmashell. I have attached a video showing this bug in action on my system. In the video, my primary monitor is on the left. To trigger the bug, I restart plasmashell via the command "kquitapp5 plasmashell && kstart plasmashell". I also disable my secondary monitor at one point via "xrandr --output HDMI-0 --off". This causes plasmashell to crash to a black screen, but I figure that should be a separate bug report. Neither of these bugs occurred prior to upgrading to Plasma 5.27.0. STEPS TO REPRODUCE 1. Have two or more monitors connected to the PC. 2. Place some icons on the desktop of the primary monitor. 3. Log off/on or restart plasmashell. OBSERVED RESULT The icons have been moved to the secondary monitor. EXPECTED RESULT The icons should stay where I put them. SOFTWARE/OS VERSIONS Linux: KDE neon 5.27 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Screen #1 (DVI-I-1, screen 0, primary): ASUS VG248QE 24" LCD Monitor * Resolution: 1920 x 1280 @ 120 Hz Screen #2 (HDMI-0, screen 1): Dell P170Sb 17" LCD Monitor * Resolution: 1280 x 1024 @ 75 Hz * Position relative to screen 0: +1920+120 -- You are receiving this mail because: You are watching all bug changes.
