Bug 275153

Summary: Panel ignores screen width of the active screen when starting
Product: [Plasma] plasma4 Reporter: Miro Kropacek <miro.kropacek>
Component: panelAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: sonni.norlov
Priority: NOR    
Version: 4.6.3   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:

Description Miro Kropacek 2011-06-07 21:25:24 UTC 
Version:           unspecified (using KDE 4.6.3) 
OS:                Linux

I've got this problem since the first KDE4 releases. I've got dual screen, Thinkpad R60 + VGA output. LVDS is 1024x768, VGA is 1920x1080, intel graphics if it does matter.

My desktop looks like this: [LVDS1][VGA1], on VGA1 is my panel (taskbar, menu button, icons), on LVDS1 is empty space (extended desktop, i.e. not twin view etc).

So, after I set this and reboot, I get everything right (windows are reopened etc) but that panel is as wide as 1024 pixels! Only workaround for this I found is to grap "screen edge" in the panel settings, drag it to some side (left, up, right) and then again to the bottom. Then the first part of panel is correct and I can use "Maximize Panel" option and finally, everything is all right.

But you certainly agree it's quite annoying.

Btw this affects only the panel, window widths of applications are ok.

Reproducible: Always

Steps to Reproduce:
See above.

Actual Results:  
Panel width is taken from LCD monitor on notebook and not from LCD monitor where the panel is actually shown.

Expected Results:  
1920 pixel width for panel.
Comment 1 Sonni 2013-05-17 18:12:58 UTC 
I also see this issue on 4.10.2 whenever I switch between laptop screen and a larger external screen.
Comment 2 Nate Graham 2018-06-08 19:36:44 UTC 
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham