Bug 263765 - panel maximum width stunted after switching primary displays with TwinView
Summary: panel maximum width stunted after switching primary displays with TwinView
Status: RESOLVED FIXED
Alias: None
Product: plasma4
Classification: Plasma
Component: multiscreen (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-20 17:15 UTC by Ivan D Vasin
Modified: 2011-06-15 21:13 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
xorg.conf (1.99 KB, text/plain)
2011-01-20 17:15 UTC, Ivan D Vasin
Details
narrowed panel (153.67 KB, image/jpeg)
2011-01-20 17:19 UTC, Ivan D Vasin
Details
narrowed panel with stunted resize handles (161.51 KB, image/jpeg)
2011-01-20 17:21 UTC, Ivan D Vasin
Details
normal panel with stunted resize handles (163.34 KB, image/jpeg)
2011-01-20 17:22 UTC, Ivan D Vasin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan D Vasin 2011-01-20 17:15:46 UTC
Created attachment 56244 [details]
xorg.conf

Version:           unspecified (using KDE 4.5.5) 
OS:                Linux

i'm not sure what is a minimal set of steps to reproduce this, but it happens every time on my setup.  here is what i have:

  * a MacBook Pro with an NVIDIA GeForce GT 330M
  * a MacBook Pro laptop display with max resolution 1440x900
  * an Asus VW246 (a.k.a. Ancor Communications Inc VW246) external display with max resolution 1920x1080
  * NVIDIA TwinView configured via nvidia-settings so that:
    * the external display is primary with auto resolution and positioned absolutely at +1440+0
    * the laptop display has auto resolution and is positioned absolutely at +0+461
  * unmanaged windows set to show on the external display via systemsettings
  * a single plasma panel at the bottom of the primary display with maximum width

in other words, xinerama is off, and i am not directly using xrandr for the multi-screen setup.

Reproducible: Always

Steps to Reproduce:
with this setup, here are the steps to reproduce my problem:
  1. shut down with the external display connected.
  2. disconnect the external display.
  3. boot up and log in to KDE.
  4. shut down.
  5. connect the external display.
  6. boot up and log in to KDE.

Actual Results:  
  1. after step 3, the panel moves to the the laptop display and resizes so that maximum and current width are 1440 px.
  2. after step 6, the panel returns to the external display, but the current and maximum width remain at 1440 px.

Expected Results:  
  1. same as actual result 1.
  2. after step 6, the panel returns to the external display at its original maximum and current width of 1920 px.

in other words, not only does is the panel's width stunted when i return to the original multi-screen setup, but the resize handles and Maximize action are stunted likewise too.  the only way i have found to return the panel to its true maximum width of 1920 px is to remove it and re-add it.  even then, the resize handles are still stunted, and Maximize shortens the panel again to 1440 px.
Comment 1 Ivan D Vasin 2011-01-20 17:19:50 UTC
Created attachment 56245 [details]
narrowed panel

this is what i see after the second reboot.
Comment 2 Ivan D Vasin 2011-01-20 17:21:29 UTC
Created attachment 56246 [details]
narrowed panel with stunted resize handles

this is what i see when i subsequently unlock the panel and click the plasma ball.
Comment 3 Ivan D Vasin 2011-01-20 17:22:41 UTC
Created attachment 56247 [details]
normal panel with stunted resize handles

this is what i see after i remove the panel, re-add it, and click the plasma ball.
Comment 4 Aaron J. Seigo 2011-01-20 18:03:33 UTC
should be fix in 4.6. try it when it comes out and if the fixes made for these issues in 4.6 don't fix your specific use case (though it should, as it sounds identical to one of the handful of use cases i fixed), please re-open the report.
Comment 5 Ivan D Vasin 2011-01-26 21:11:15 UTC
all issues are still present with KDE 4.6.0.
Comment 6 Aaron J. Seigo 2011-01-26 21:16:14 UTC
even if you stop plasma-desktop, delete plasma-desktoprc and start plasma-desktop against? (note: NOT plasma-desktop-appletsrc, just plasma-desktoprc!)
Comment 7 Ivan D Vasin 2011-02-03 17:35:00 UTC
(In reply to comment #6)
> even if you stop plasma-desktop, delete plasma-desktoprc and start
> plasma-desktop against? (note: NOT plasma-desktop-appletsrc, just
> plasma-desktoprc!)

prior to logging in after upgrading to 4.6.0, i removed everything under $HOME/.kde for good measure.  of course, i backed up and later restored the most important settings and data, but plasma-desktoprc was not one of these.

part of the problem seemed to fix itself not too long after i upgraded.  i'm not sure what did it, since i don't recall making any significant changes to my plasma settings.  now the panel's width is restored to the screen's maximum of 1920 px, as expected.  but the panel's maximum width is still stunted to 1440 px--the panel settings popup is 1440 px wide, and "More Settings -> Maximize" sets the width to 1440 px.  once again the only way (afaik) to widen the panel to 1920 px is to remove it and re-add it.

i tried removing plasma-desktoprc again, but it didn't help.
Comment 8 Aaron J. Seigo 2011-02-03 20:11:02 UTC
"the panel settings popup is 1440 px wide"

this implies that there is still somewhere an actual 1440px wide screen. if you open up the "Configure display" panel (left clicking on the monitor icon in the system tray brings it up), what does it show?

because what this means is that either the popup thinks it's on the wrong screen, this phantom small screen, or that Kephal is misreporting screen sizes .. but that doesn't make too much sense since both the popup and the panel use Kephal for that. hmm..

aha! in 4.6.0 it was still using QDesktopWidget for that! and yes, that does screw up in those cases. i'm not sure if that's what is triggering it in this case, but i'll backport that change.
Comment 9 Ivan D Vasin 2011-04-01 17:13:00 UTC
(In reply to comment #8)
> aha! in 4.6.0 it was still using QDesktopWidget for that! and yes, that does
> screw up in those cases. i'm not sure if that's what is triggering it in this
> case, but i'll backport that change.

should this be fixed in 4.6.1, then?  it isn't.
Comment 10 Ivan D Vasin 2011-06-15 21:13:48 UTC
this was still broken in 4.6.3, but it's fixed in 4.6.4.  thanks!