Bug 257847 - Plasma not showing up: wrong state saved?
Summary: Plasma not showing up: wrong state saved?
Status: RESOLVED DUPLICATE of bug 259183
Alias: None
Product: plasma4
Classification: Plasma
Component: multiscreen (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-25 08:06 UTC by kaouete
Modified: 2011-12-17 10:42 UTC (History)
1 user (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 kaouete 2010-11-25 08:06:58 UTC
Version:           unspecified (using KDE 4.5.3) 
OS:                Linux

Hi,

In some case (detailed after), my plasma desktop doesn't show when switching from multiscreen to one screen.

Reproducible: Didn't try

Steps to Reproduce:
 - use kde with two screen, more precisely, I have one panel on each screens, they are next to each other, the first one is my laptop LVDS and the second one is a screen connected to the dock station through DVI (my laptop has only VGA itself without the dock)
 - shut down the computer in this state
 - start it up removed from the dock (thus with only LVDS)

Actual Results:  
plasma seems to be showing up somewhere else, but not on my screen, there is no error, just no panels nor any window that should open at start (such as kwallet window asking me for password…)
I can shut down kde using Exit and disconnect.

Expected Results:  
everything working :)

There is a way to fix it:
-> edit .kde4/share/config/plasma-desktoprc
-> look for "-1" values for some min and max settings
-> remove them all! (the complete line min=-1 and max=-1)
-> restart kde, I get a correct state where it works.

This bug apparead with kde 3.5.2 I think.
Comment 1 Reza 2011-12-17 00:54:50 UTC
I can reproduced this in 4.7.3
The panel on main screen was not displayed, but next time you restart with second monitor attached. the panels were displayed properly
Comment 2 Reza 2011-12-17 10:42:56 UTC

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