Bug 218716 - panel doesn't show when second display is disconnected
Summary: panel doesn't show when second display is disconnected
Status: RESOLVED DUPLICATE of bug 183280
Alias: None
Product: plasma4
Classification: Plasma
Component: multiscreen (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-14 22:35 UTC by Marc Haber
Modified: 2010-06-04 01:21 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Haber 2009-12-14 22:35:22 UTC
Version:            (using KDE 4.3.4)
OS:                Linux
Installed from:    Debian testing/unstable Packages

Hi,

my notebook has a Mobility Radeon 9600 M10 which I use with the open source radeon driver. The internal panel has 1400x1050, the external monitors which I usually use (one analog at home, one digital at work) both have 1600x1200 pixels. In both setups the external monitor is left of the internal panel, and thus screen 0 has a resolution of 3000x1200 with the lower right 1400x150 pixels not being visible. My main KDE panel is at the lower edge of the external display.

When I disconnect the external monitor and use xrandr to reconfigure the internal panel to be at pos 0x0, the main KDE panel does not display any more. It doesn't even display any more when I manually move the panel from the external display to upper edge of either display. It just doesn't show when there is no external display connected.

The panel used to behave correctly (showing on the internal display when the notebook is operated standalone, and on the external display when there is one connected) in KDE 3, and even in KDE 4.3.2 when I updated from KDE 3. The wrong behavior has started spontaneously after a week of not doing any updates, and has continued to show through all updates I did, including to KDE 4.3.4 which I am using right now. I am not aware of having done any changes to my KDE configuration which could have caused this issue.

Is there anything I can do to work around this issue or to help debugging it?

Greetings
Marc
Comment 1 Beat Wolf 2009-12-14 23:28:45 UTC

*** This bug has been marked as a duplicate of bug 183280 ***
Comment 2 Aaron J. Seigo 2010-06-04 01:21:39 UTC

*** This bug has been marked as a duplicate of bug 183280 ***