At the mercy of KDE plasma auto decide the location of "Desktop taskbar panel"

The only effected way to “make” “desktop taskbar panel” on the correct monitor is via method 1:

  1. right click on “taskbar panel” > enter edit mode > click on “manage desktop and panels” > panels and desktop management - plasma > drag "taskbar panel from a screen to desired screen.
    method 2
  2. i learnt that : xrandr has no control over which screen the “taskbar panel” should be on.

This is my 2 monitors… eDP-1 is laptop own monitor (which taskbar panel shld be on)
HDMI-1 is the monitor located above laptop monitor.

This is xrandr output of my monitors.
i used to thought “–primary” is the option in xrandr that will determine which monitor the"taskbar panel" will be located. But apparently i was wrong.
Hence i have no idea what “–primary” option is for, seems like useless.

I have made this cmd in .bashrc as an alias, thinking if at anytime anywhere the DE setting on monitor were messed up, i can use this cmd below to set everything in the order i want…
well… it did all good, except for “taskbar panel” always located at wrong monitor.
when i bring laptop to my friend’s house and plugged hdmi to her tv screen, the executed the xrandr cmd below… somehow everything is good, even the “taskbar panel” location. But why it does not always at the right location when at home ? ?

 $ xrandr --output eDP-1 --mode 1920x1080 --pos 0x0 --primary --rotate normal --below HDMI-1 --output HDMI-1 --mode 1920x1080 --pos 0x-1080 --above eDP-1 --rotate normal --rate 60
Screen 0: minimum 320 x 200, current 1920 x 2160, maximum 16384 x 16384
eDP-1 connected primary 1920x1080+0+1080 (normal left inverted right x axis y axis) 344mm x 194mm
   1920x1080     60.01*+  59.97    59.96    59.93  
   1680x1050     59.95    59.88  
   1400x1050     59.98  
   1600x900      59.99    59.94    59.95    59.82  
   1280x1024     60.02  
   1400x900      59.96    59.88  
   1280x960      60.00  
   1440x810      60.00    59.97  
   1368x768      59.88    59.85  
   1280x800      59.99    59.97    59.81    59.91  
   1280x720      60.00    59.99    59.86    59.74  
   1024x768      60.04    60.00  
   960x720       60.00  
   928x696       60.05  
   896x672       60.01  
   1024x576      59.95    59.96    59.90    59.82  
   960x600       59.93    60.00  
   960x540       59.96    59.99    59.63    59.82  
   800x600       60.00    60.32    56.25  
   840x525       60.01    59.88  
   864x486       59.92    59.57  
   700x525       59.98  
   800x450       59.95    59.82  
   640x512       60.02  
   700x450       59.96    59.88  
   640x480       60.00    59.94  
   720x405       59.51    58.99  
   684x384       59.88    59.85  
   640x400       59.88    59.98  
   640x360       59.86    59.83    59.84    59.32  
   512x384       60.00  
   512x288       60.00    59.92  
   480x270       59.63    59.82  
   400x300       60.32    56.34  
   432x243       59.92    59.57  
   320x240       60.05  
   360x202       59.51    59.13  
   320x180       59.84    59.32  
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 160mm x 90mm
   1920x1080     60.00*+  50.00    59.94  
   1920x1080i    60.00    50.00    59.94  
   1600x1200     60.00  
   1680x1050     59.88  
   1280x1024     60.02  
   1440x900      59.90  
   1280x960      60.00  
   1280x800      59.91  
   1280x720      60.00    50.00    59.94  
   1024x768      60.00  
   800x600       60.32    56.25  
   720x576       50.00  
   720x480       60.00    59.94  
   640x480       60.00    59.94  

Is there and cmdline cmd that enable me to set the “taskbar panel” at a certain monitor (instead of at it’s mercy) ? or the onlyway is GUI way ? surely that’s not linux mentality

i have run these 2 xrandr cmd below:

 $ xrandr --output eDP-1 --mode 1920x1080 --pos 0x0 --primary --rotate normal --below HDMI-1 --output HDMI-1 --mode 1920x1080 --pos 0x-1080 --above eDP-1 --rotate normal --rate 60


 $ xrandr --output eDP-1 --mode 1920x1080 --pos 0x0 --rotate normal --below HDMI-1 --output HDMI-1 --mode 1920x1080 --primary --pos 0x-1080 --above eDP-1 --rotate normal --rate 60

but it makes no diff… the taskbar panel won’t change it (undesired) location (on wrong screen).


Are you experiencing the same issues in both Wayland and X11?

Try to use Plasma 6 on Wayland, many things were added and fixed for it.

You don’t need any additional script, use only Plasma settings app, and simply set “primary” your monitor where you want the panel to appear.

1 Like

I don’t know about wayland. i only run x11 so far…

i have not use wayland before… i am on x11… even though, it should have this kind of issue on x11… this issue has being so for months… one of the upgrade (i think) causes this issue. it used to be all fine… until one of the update or upgrade make the issue surfaced. So, right now, x11 is no longer recommended using ?

If Wayland works OK for you I’d switch to it. I’ve been using it since some time last year (on Plasma5) and it generally performs really well, probably better than X11 at least in my case.

X11 is falling by the wayside.

(I’m on Stable branch).

1 Like

Wayland is now default for KDE. All you should need to do is select it at the login screen. See if it makes any difference for you, and report back.

Not for manjaro anymore (or yet if you are on Stable).

and I’m presuming Stable without any evidence to the contrary (unless I missed it).

I’m not sure it was understood - my point was that while kde intended to ship wayland as default for plasma 6 (and did) … manjaro has patched plasma-workspace so that x11 will continue to be the default.

1 Like

Interesting. For several installations (in recent weeks (23.1.3-240113 ISO) they have defaulted to Wayland. These were all VM’s, but that shouldn’t make a difference. I’ll triple check that tomorrow.

They pushed the change to Testing and Unstable sometime within the last day or 2.
It also had some unintended affects.
I nabbed Archs copy, because I’m on Unstable and I can :wink:

1 Like

X11 has serious non-fixable bugs, and some are low level, and no one is stepping in to fix them, even Red Hat stopped its team to patch Xorg.

Compared to X11, Wayland bugs are being worked on, both from Wayland, KDE and even other parties like GNOME in an effort to unify them and have the correct implementations everywhere.

i just installed wayland for plasma (weird, maybe i have uninstalled wayland sometime ago, and i must have forgotten that). and after messing around (to test out) found out that --primary option in xrandr is NOT the “main factor” determining where taskbar panel will be displayed.

The Main “factor” that determine where taskbar panel located is ONLY thru :
“panels and desktops management - plasma (you can drag panels and desktops around to move them to different screens)”.

I am confidence ,because i have tested it out.
how i do it:
i purposely dragged taskbar panel to hdmi screen. then executed my xrandr script above. … the result is :
taskbar panel remain at same screen, didn’t go back to “–primary” screen.

I also found out that :
xrandr render my hdmi screen on x11 as: HDMI-1
xrandr render my hdmi screen on wayland as: HDMI-A-1

so, the conclusion is , xrandr cmd can’t determine where taskbar panel will be located, it will have to be done via gui method! amazingly crazy for linux !

I still wish there is a cmd line can do the job instead of having to do it via gui method… so unlinux like! so many mouse clicks have to go thru to restore a simple taskbar panel that being place at wrong location.

To make it more accurate:
i just tested that “primary” setting in “display configuration- system settings” , found out that this method affect the location of taskbar panel as medmedin has said.
**this image is borrowed from medmedin… not mine. **

xrandr --primary DOES NOT affect the location of taskbar panel at all… So weird. GUI “primary” works, but cmdline “primary” does not work.
this is a simple xrandr --primary cmd: i tested these cmdline, but my taskbar just does not relocate from 1 screen to another …

some kind of bug here.

gosh! because xrandr does not work properly. i was recommened to use wayland. now when i switched to wayland i have to ditch xrandr… talk about hen and egg…

i have not even solve this issue yet… but the thread closed already… how now ? i need to open another thread just to continue with the same issue but a variant (instead of x11, now is wayland) ?
switching to wayland also bring clipboard issue on my vim. just another day with linux…more issue to spend time on

xrandr is specific to X11, on Wayland use Plasma GUI or kscreen-doctor.
kscreen-doctor --help

1 Like

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.