Bug 360563 - black screen on session restore until removing ~/.local/share/kscreen
Summary: black screen on session restore until removing ~/.local/share/kscreen
Status: RESOLVED WORKSFORME
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.5.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Kügler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-15 15:08 UTC by Martin Steigerwald
Modified: 2022-10-21 08:54 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
broken ~/.local/share/kscreen that led to black display (688 bytes, application/x-xz)
2016-03-15 15:10 UTC, Martin Steigerwald
Details
~/.local/share/kscreen directory at three states (775 bytes, application/gzip)
2016-03-21 09:33 UTC, Alexey Shildyakov
Details
Step 2. Open System settings (136.42 KB, image/png)
2016-03-21 09:56 UTC, Alexey Shildyakov
Details
Step 3. Enable second monitor (151.36 KB, image/png)
2016-03-21 09:56 UTC, Alexey Shildyakov
Details
Step 4. Copied and freezed image with small interacting part (that area is green) (3.15 MB, image/png)
2016-03-21 10:02 UTC, Alexey Shildyakov
Details
Step 8. System Settings after enabled second monitor, removed kscreen dir (1.64 MB, image/png)
2016-03-21 10:03 UTC, Alexey Shildyakov
Details
Step 9. After unified screen (412.42 KB, image/png)
2016-03-21 10:06 UTC, Alexey Shildyakov
Details
Screenshot from this morning's resume (1.95 MB, image/png)
2016-03-23 23:07 UTC, jamese
Details
output of kscreen-console bug when black screen is present (22.72 KB, text/plain)
2016-03-23 23:09 UTC, jamese
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Steigerwald 2016-03-15 15:08:18 UTC
On logging in yesterday after plugging to the second screen at work I got a black screen on logging. After removing ~/.local/share/kscreen for the affected user login worked just fine.

Reproducible: Sometimes

Steps to Reproduce:
I have no idea how to reproduce this reliably. It tends to happen on changing multiscreen setups between home and work or no second screen when holding a training. I have an external Fujitsu Display both at home and at work, different ones.

Actual Results:  
Black screen.

Expected Results:  
As long as there is a suitable display to display things on, and in a laptop there always is a suitable display, the internal one, on session login display something useful.

I will attach the broken ~/.local/share/kscreen

This happened with mostly Plasma 5.5.4 + self compiled KDE Frameworks + KDEPIM on Debian Sid with a setup similar like this one (the display at work is a different Fujitsu display):

ms@merkaba:~> phoronix-test-suite system-info

Phoronix Test Suite v5.2.1
System Information

Hardware:
Processor: Intel Core i5-2520M @ 3.20GHz (4 Cores), Motherboard: LENOVO 42433WG, Chipset: Intel 2nd Generation Core Family DRAM, Memory: 16384MB, Disk: 300GB INTEL SSDSA2CW30 + 480GB Crucial_CT480M50, Graphics: Intel HD 3000 (1300MHz), Audio: Conexant CX20590, Monitor: P24T-7 LED, Network: Intel 82579LM Gigabit Connection + Intel Centrino Advanced-N 6205

Software:
OS: Debian unstable, Kernel: 4.5.0-rc7-tp520-btrfstrim+ (x86_64), Desktop: KDE Frameworks 5, Display Server: X Server 1.18.2, Display Driver: intel 2.99.917, OpenGL: 3.3 Mesa 11.1.2, Compiler: GCC 5.3.1 20160307, File-System: btrfs (ecryptfs), Screen Resolution: 3840x1080

Intel driver is set to "uxa" acceleration due to lockup issues with "sna".

Qt is 5.5.1+dfsg-16, kscreen is 4:5.5.4-1.
Comment 1 Martin Steigerwald 2016-03-15 15:10:59 UTC
Created attachment 97913 [details]
broken ~/.local/share/kscreen that led to black display

Fujitsu Siemens Computers GmbH-P24T-7 is home display connected via displayport via Minidock.

Fujitsu Siemens Computers GmbH-P23T-6 is office display connected via displayport to hdmi adapter.
Comment 2 Alexey Shildyakov 2016-03-21 09:31:01 UTC
I've the same issue try to explain it more.
The bug is reproducible every time for me.

1. Plug in second monitor
2. Open the System Settings -> Display and Monitor, the new attached screen is disabled
3. Enable new display and press Apply.
4. The screen is modified. It copies current displayed image, moves it down from top of monitor and fixed the image (system is still responsible and all actoins and movements will be at top part of screen). I backuped the "kscreen" directory as "kscreen.bad"
5. Logout the KDE session
6. Remove ~/.local/share/kscreen
7. Login again. I backuped "kscreen" directory at the moment as "kscreen.immediate.after.bad.conf.removed"
8. Open System settings- -> Display and Monitor. The second screen is enabled now.
9. Unifies screens
10. All is working now. I backuped "kscreen" directory at the moment as "kscreen.bak"
11. Unplug and plug the second monitor now works fine.
Comment 3 Alexey Shildyakov 2016-03-21 09:33:19 UTC
Created attachment 97997 [details]
~/.local/share/kscreen directory at three states
Comment 4 Alexey Shildyakov 2016-03-21 09:34:28 UTC
It reproduces on Ubuntu 14.04 LTS, 15.10 and 16 (dev)
Now I'm on 15.10 with kscreen-5.4.2-0ubuntu1 amd64
Comment 5 Alexey Shildyakov 2016-03-21 09:56:06 UTC
Created attachment 97998 [details]
Step 2. Open System settings
Comment 6 Alexey Shildyakov 2016-03-21 09:56:42 UTC
Created attachment 97999 [details]
Step 3. Enable second monitor
Comment 7 Alexey Shildyakov 2016-03-21 10:02:10 UTC
Created attachment 98000 [details]
Step 4. Copied and freezed image with small interacting part (that area is green)
Comment 8 Alexey Shildyakov 2016-03-21 10:03:07 UTC
Created attachment 98001 [details]
Step 8. System Settings after enabled second monitor, removed kscreen dir
Comment 9 Alexey Shildyakov 2016-03-21 10:06:29 UTC
Created attachment 98002 [details]
Step 9. After unified screen

seems the primary display now second (NOT gray in dropbox "laptop screen"). As you can see, custom wallpapers doesn't work here. If laptop screen is closed, the custom wallpapers will be appeared.
Comment 10 Alexey Shildyakov 2016-03-21 10:07:55 UTC
How to reproduce? Because in according to step 11 all works fine from that point.

12. Unplug the laptop from second screen
13. Reboot it

and all goes from step 1 now.
Comment 11 Martin Steigerwald 2016-03-21 10:19:48 UTC
Alexey, I do not understand whether you are really seeing the *same* bug. Do you have a *black* screen on session *login* with a certain kscreen configuration?

If yes, thats the same bug.

If not, its likely a different bug and I kindly ask you to open a new bug report instead of hijacking this one.

Thank you,
Martin
Comment 12 Alexey Shildyakov 2016-03-21 10:22:51 UTC
Yes. I will see black screen if login after step 5 and don't remove ~/.local/share/kscreen
Comment 13 Martin Steigerwald 2016-03-21 10:29:23 UTC
Okay. Thank you for the detailed description. Which ~/.local/share/kscreen in your archive correspondends to the black screen on login state?
Comment 14 Alexey Shildyakov 2016-03-21 10:33:28 UTC
As I wrote above, the "kscreen.bad"
Comment 15 Martin Steigerwald 2016-03-21 10:40:20 UTC
Alexey, okay, got confused by

4. The screen is modified. It copies current displayed image, moves it down from top of monitor and fixed the image (system is still responsible and all actoins and movements will be at top part of screen). I backuped the "kscreen" directory as "kscreen.bad"

that didn´t sound like a black screen to me.
Comment 16 Alexey Shildyakov 2016-03-21 13:33:56 UTC
Maybe for me this is two bugs in case first involves second.
Comment 17 jamese 2016-03-21 23:54:25 UTC
This happens for me, using a DisplayPort connection as well running on an Intel Iris Pro with the "intellinuxgraphics" drivers from intel.
I have to rm  the kscreen settings .local/share/kscreen/* and then kill sddm, losing everything including running virtual machines and try to log in again.

 
Reading an unrelated issue #336225 it's possible that fixes for the various issues with KDE and multiple monitors is landing in 5.6 with fixes from Qt.  Can't be sure, though.
Comment 18 Alexey Shildyakov 2016-03-22 06:46:03 UTC
(In reply to jamese from comment #17)
> Reading an unrelated issue #336225 it's possible that fixes for the various
> issues with KDE and multiple monitors is landing in 5.6 with fixes from Qt. 
> Can't be sure, though.

Are you sure with bug #336225 as it is about kaddressbook? 
What steps reproduce this bug (black screen)?
Comment 19 jamese 2016-03-23 22:57:26 UTC
Sorry, #356225, but I can't find a link to edit my comment to correct the typo.

I thought this sounded familiar and looking back through my bug list I found #349482 which I resolved as a duplicate of #353975 as it was getting more interest. This may be a duplicate of that?

Other thing worth noting is that I have two U2414H screens and Alexey's screenshots show the same screen type. Mine are on an MST chain using Displayport 1.2 - so DP cable from laptop to first screen (DP1-1) which has a DP cable to the terminating screen (DP1-2)

All these issues happen for me when switching from multi-screen to laptop only and back to multi-screen.

Last thing to note is that when I switch to runlevel 1 to rm .local/share/kscreen/* and then kill SDDM after I have no desktop, the text  from the shell is cloned perfectly onto all three screens.
Comment 20 jamese 2016-03-23 23:07:18 UTC
Created attachment 98051 [details]
Screenshot from this morning's resume

Plugged in DP cable and got all three screens with two panels on DP1-2 and one on Laptop. Switch primary from laptop to DP1-1 and this was the result.

Laptop screen black, mouse can go into it, can drag application windows into it. No right click context menu, can't drag widgets into it, can't create widgets on it.

I get three notification messages in the systray, possibly related to the original 3 panels.
Comment 21 jamese 2016-03-23 23:09:23 UTC
Created attachment 98055 [details]
output of kscreen-console bug when black screen is present
Comment 22 Alexey Shildyakov 2016-03-25 08:24:51 UTC
Also, when I click second time to button "Apply" after step 4, the screen became black.
Comment 23 Justin Zobel 2022-10-21 00:17:44 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 24 Martin Steigerwald 2022-10-21 08:54:04 UTC
I did not see this in a very long time. Thus closing.

Alexey, feel free to reopen in case you still see this.