Whenever I view the "Desktop Grid" these days, the lower-right quadrant contains an extra set of add/remove desktop buttons. I find myself accidentally clicking on them regularly when I try to switch to that desktop. In the latter case, this causes the windows that were located on that desktop to be moved to another. This is an extremely annoying bug, which I'm hoping will be fixed soon. The other issue is that the desktop names are also duplicated on the screen in weird locations. I will attach the relevant screenshots to this post when I get the opportunity to do so. It's surprising that there's no "Attach Files" function on this submission page to be honest. Reproducible: Always
Created attachment 95321 [details] The "Desktop Grid"
Created attachment 95322 [details] "Desktop Grid" Settings
Created attachment 95323 [details] "Compositor" Settings
I assume you cannot interact with the window not placed in the bottom/right corner?
multiscreen? please post the output of "xrandr -q"
(In reply to Martin Gräßlin from comment #4) > I assume you cannot interact with the window not placed in the bottom/right > corner? I'm not sure that I understand what you mean, but I'll attempt to answer what I think you're asking. I can navigate to the bottom-right desktop by clicking on it as usual. The problem is that I often click on those extra add/remove buttons by mistake. When I'm switching between desktops quickly, I don't always remember that they're there.
I assume Martin thought the input windows of different screens would overlay each other and the upper (for the screen with the "inner" buttons) would block input for the lower, but afair that's no problem) Please attach the output of "xrandr -q", this smells like a "clone" setup of differently sized screens, ie. the smaller one shows the upper leaft area of the bigger one (and no: it doesn't matter how many panels you've attached, please let us see the xrandr configuration ;-)
(In reply to Thomas Lübking from comment #7) > I assume Martin thought the input windows of different screens would overlay > each other and the upper (for the screen with the "inner" buttons) would > block input for the lower, but afair that's no problem) > > Please attach the output of "xrandr -q", this smells like a "clone" setup of > differently sized screens, ie. the smaller one shows the upper leaft area of > the bigger one (and no: it doesn't matter how many panels you've attached, > please let us see the xrandr configuration ;-) Yep, I was getting to it :-). After viewing the output of "xrandr -q", I decided to play around some more. That's why I wasn't able to reply to your first comment as quickly as I would have liked to. The output used to be as below, until I disabled the second monitor (which fixed the problem). I don't know why HDMI3 defaults to 1360x768, given that the TV it's connected to runs at 1920x1080. I can't seem to increase its resolution via KDE's "Display Configuration" (System Settings) module either. Is there another way I can force HDMI3 to default to 1920x1080 each time KDE logs in? Screen 0: minimum 8 x 8, current 1920 x 1848, maximum 32767 x 32767 DP1 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.00*+ 1600x1200 60.00 1680x1050 59.88 1280x1024 75.02 60.02 1440x900 59.90 1280x960 60.00 1152x864 75.00 1024x768 75.08 70.07 60.00 832x624 74.55 800x600 72.19 75.00 60.32 56.25 640x480 75.00 72.81 66.67 60.00 720x400 70.08 HDMI3 connected 1360x768+0+1080 (normal left inverted right x axis y axis) 1600mm x 900mm 1360x768 60.37*+ 1920x1080 60.00 50.00 59.94 1920x1080i 60.00 60.00 50.00 59.94 1280x1024 60.02 1280x720 60.61 60.00 50.00 59.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x576i 50.00 720x480 60.00 59.94 720x480i 60.00 59.94 640x480 60.00 59.94 VGA1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Did you alter the layout? The screens in that configuration should not cover each other. "xrandr --output HDMI-3 --mode 1920x1080" should set it to FullHD, does "kcmshell5 kscreen" not show higher resolutions for it or is applying them just w/o effect?
(In reply to Thomas Lübking from comment #9) > Did you alter the layout? The screens in that configuration should not cover > each other. Yes, I was moving them around last night. You're right that the problem only exists when the displays are covering each other. If I move one of them to the side, it doesn't occur anymore. > "xrandr --output HDMI-3 --mode 1920x1080" should set it to FullHD, does > "kcmshell5 kscreen" not show higher resolutions for it or is applying them > just w/o effect? Thanks, that command did set HDMI3 to Full HD. However, KScreen still only shows it as HD immediately afterwards. This surely has to be a bug, right? The other thing is that KScreen doesn't list, or allow me to change to, any other resolutions for either display. I will attach a screenshot to illustrate my point shortly. Going back to the output of "xrandr -q", note the plus (default) sign in the "1360x768 60.37*+" line. How can I get it to be displayed on the "1920x1080" line instead? I tried to force HDMI3 to Full HD upon login by adding "xrandr --output HDMI3 --mode 1920x1080" to my "/usr/share/sddm/scripts/Xsetup" file, but this had no effect.
Created attachment 95349 [details] "Display" Settings
(In reply to Xavion from comment #10) > Yes, I was moving them around last night. You're right that the problem > only exists when the displays are covering each other. If I move one of > them to the side, it doesn't occur anymore. We'd need a good resolution for the conflict here first. Outputs can intersect their viewports randomly. While we can skip those items (and for 5.5 the desktop as well) if a screen intersects a screen that we've already visited, this would in eg. your case mean that you've no visible buttons on the smaller screen (which still only shows a section of the bigger, so this is "correct", but feels a bit odd) > Thanks, that command did set HDMI3 to Full HD. However, KScreen still only > shows it as HD immediately afterwards. This surely has to be a bug, right? Seems so. I've a slider there to select all available modes. => File a bug against kscreen. > note the plus (default) sign in the "1360x768 60.37*+" line. This is the default resolution (usually hinted by the monitors EDID data) > How can I get it to be displayed on the "1920x1080" line instead? /etc/X11/xorg.conf.d/10-hdmimode.conf ------- Section "Monitor" Identifier "HDMI3" Option "PreferredMode" "1920x1080" EndSection ------- however, hardcoding such in a config isn't scaling too good (fails with the next different screen) > I tried to force HDMI3 to Full HD upon login by adding "xrandr --output > HDMI3 --mode 1920x1080" to my "/usr/share/sddm/scripts/Xsetup" file, but kscreen will hammer it's configuration afterwards - you could try to deactivate the daemon in "kcmshell5 kded"
(In reply to Thomas Lübking from comment #12) > Seems so. I've a slider there to select all available modes. => File a bug > against kscreen. I should clarify that I also see the slider when I launch "kcmshell5 kscreen" via "sudo". Maybe you assumed I would do this, but actually I didn't try it until later. It's only when I launch "kcmshell5 kscreen" as a regular user that I don't see the slider. > /etc/X11/xorg.conf.d/10-hdmimode.conf > ------- > Section "Monitor" > Identifier "HDMI3" > Option "PreferredMode" "1920x1080" > EndSection > ------- > > however, hardcoding such in a config isn't scaling too good (fails with the > next different screen) Actually, it failed with this screen too :-). It also caused my computer to hang on boot, so I had to delete the file via the GParted Live CD. Don't worry, I'm generally a forgiving person: I was only mad at you for about fifteen minutes :-). > kscreen will hammer it's configuration afterwards - you could try to > deactivate the daemon in "kcmshell5 kded" I figured out that the reason it wasn't working from the "/usr/share/sddm/scripts/Xsetup" file is that I had to add the "xrandr --addmode HDMI3 1920x1080" line first. Now that I've done so, KScreen doesn't get in the way anymore and the "Desktop Grid" bug has gone away.
(In reply to Xavion from comment #13) > I should clarify that I also see the slider when I launch "kcmshell5 > kscreen" via "sudo". Maybe you assumed I would do this No, you should not require special permissions to alter the screen. What happens if you (close the kcm/systemsettings before) mv ~/.local/share/kscreen ~/.local/share/not.kscreen > > /etc/X11/xorg.conf.d/10-hdmimode.conf > > ------- > > Section "Monitor" > > Identifier "HDMI3" > > Option "PreferredMode" "1920x1080" > > EndSection > > ------- > > > > however, hardcoding such in a config isn't scaling too good (fails with the > > next different screen) > > Actually, it failed with this screen too :-). It also caused my computer to > hang on boot, so I had to delete the file via the GParted Live CD. Sorry about that. Fyi, Ctrl+Alt+F2 should bring you to a textshell from where you can login and manipulate the system (and it's always good to have a tinycore or grml linux iamge available, added as memdisk entry to your grub ;-) /var/log/Xorg.0.log should hold interesting information in this case, since that should rather not happen. > "/usr/share/sddm/scripts/Xsetup" file is that I had to add the "xrandr > --addmode HDMI3 1920x1080" line first. Errrrrr...... are you sure the panel actually has a native 1080p resolution? > Now that I've done so, KScreen doesn't get in the way anymore Do you maybe also have the 1080p available in kscreen now?
(In reply to Thomas Lübking from comment #14) > No, you should not require special permissions to alter the screen. > What happens if you (close the kcm/systemsettings before) > mv ~/.local/share/kscreen ~/.local/share/not.kscreen After doing that, KScreen shows the slider for both monitors. However, if I save those changes (and therefore create a new "~/.local/share/kscreen/" entry), the slider is no longer available after logging back into KDE! > Sorry about that. Fyi, Ctrl+Alt+F2 should bring you to a textshell from > where you can login and manipulate the system (and it's always good to have > a tinycore or grml linux iamge available, added as memdisk entry to your > grub ;-) Yes, I know all about Ctrl+Alt+F2. The problem was that the system was so severely frozen that I couldn't even switch consoles. Thanks for the heads-up about TC and Grml, though; I'll look into those when I get a spare moment. > /var/log/Xorg.0.log should hold interesting information in this case, since > that should rather not happen. I can remember that kind of thing happening in the past when I was trying to get my old NVIDIA card going properly with Nouveau. You're right that it shouldn't happen, but it's the sort of thing I've learned to live with every now and then. > Errrrrr...... are you sure the panel actually has a native 1080p resolution? Yes, mate: I'm certain. I spend hours each week watching the NBA on ESPN in Full HD via that panel :-). After doing so for a good couple of years, I'd know by now if it was limited to Regular HD. I think the need to add "xrandr --addmode HDMI3 1920x1080" to "/usr/share/sddm/scripts/Xsetup" stems from the fact that the panel's native modes haven't been autodetected yet (when SDDM launches X/KDE). > Do you maybe also have the 1080p available in kscreen now? When KScreen actually shows me the slider, 1080p is available for both monitors. Similarly, both are set to that resolution by default when KScreen launches these days. Before fixing the SDDM problem, however, HDMI3 was always stuck on 720p in KScreen.
(In reply to Xavion from comment #15) > After doing that, KScreen shows the slider for both monitors. However, if I > save those changes (and therefore create a new "~/.local/share/kscreen/" > entry), the slider is no longer available after logging back into KDE! Please file a bug against kscreen about that - might not be a "bug" at all, but still relevant knowledge. > I can remember that kind of thing happening in the past when I was trying to > get my old NVIDIA card going properly with Nouveau. Still an nvidia card? Binary driver? Which version? Does this change anything: Section "Device" Identifier "Default nvidia Device" Driver "nvidia" Option "NoLogo" "True" # less spam Option "CoolBits" "1" # more features in nvidia-settings Option "TripleBuffer" "True" #alsways good Option "ModeValidation" "HDMI-3: NoEdidMaxPClkCheck, NoTotalSizeCheck" EndSection
(In reply to Thomas Lübking from comment #16) > Please file a bug against kscreen about that - might not be a "bug" at all, > but still relevant knowledge. Okay, I've just filed the report and you can view it here: https://bugs.kde.org/show_bug.cgi?id=355006. I didn't mention anything about (re)moving "~/.local/share/kscreen/" first because that looks to have been a fluke. When I retested it just now, I didn't even see the resolution slider when "~/.local/share/kscreen/" was absent. > Still an nvidia card? Binary driver? Which version? No, I can't see myself getting another NVIDIA (or an AMD for that matter). Firstly, my half-arsed gaming career looks to be a thing of the past. Secondly, those proprietary drivers don't support KMS. Thirdly, the reverse-engineered OSS drivers are unstable. Whereas, Intel's proprietary driver doesn't crash and it supports KMS out of the box.
This issue report is quite old. Can you please confirm, that it still persists with KDE 5.23?
(In reply to kde.org from comment #18) > This issue report is quite old. Can you please confirm, that it still > persists with KDE 5.23? I haven't seen it for a while. It's certainly no longer occurring with KDE v5.23.2. I'll mark this as fixed.