Bug 348893

Summary:	KScreen causes login to fail after first attempt
Product:	[Plasma] KScreen	Reporter:	Jared Sutton <jpsutton>
Component:	libkscreen	Assignee:	Daniel Vrátil <dvratil>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	jpsutton, mail, sebas
Priority:	NOR	Keywords:	triaged
Version First Reported In:	5.3.1
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jared Sutton 2015-06-08 19:48:41 UTC

After installing Plasma 5.3.1 on a fresh ArchLinux installation, I am able to login to Plasma a single time; every subsequent login attempt causes both screens to go black.  At that point, the X server sometimes crashes back to the display manager immediately, but sometimes hangs indefinitely.

I discovered that deleting the "~/.local/share/kscreen" directory allows me to login one more time.  The aforementioned directory (and a single file inside it) is re-created automatically and I am then unable to login after that (same symptoms as described above).  While I'm logged in, if I disable the kscreen service from "System Settings", I am able to login without an issue. However, upon logging in after doing this, if I try to start kscreen from systemsettings, both screens go black once again and eventually crash back to the display manager.

I originally saw this issue while running Plasma 5 on Fedora 21 on the same hardware.

Reproducible: Always

Steps to Reproduce:
1. Install ArchLinux, "plasma", and "sddm" packages.
2. Login to Plasma, then log out.
3. Attempt to log back into Plasma.

Actual Results:  
Both screens will turn black (sometimes crashing back to the display manager, and sometimes not)

Expected Results:  
The screens should have remained on and I should have been shown a Plasma Desktop.

I am running a workstation with an nVidia 8600 GTS and 2 displays which are both connected via DVI. I am running the nVidia legacy 340xx driver.

Comment 1 George Kiagiadakis 2015-09-27 15:05:00 UTC

I've faced a similar issue here. I once connected my laptop to an external monitor and configured it with kscreen, but then afterwards, when I disconnected the monitor, kde crashed back to the login manager. Afterwards, kde login would crash all the time unless the monitor was connected. Deleting ~/.local/share/kscreen helped.

Comment 2 Sebastian Kügler 2016-05-04 02:01:48 UTC

Jared, George, could you post the content of the files in ~/.local/share/kscreen after setting it up, and then after rebooting?

Apparently, kscreen ends up saving a config that blows up once applied. It would be interesting to see what kscreen tries to apply.

It would also be useful to see the output from kded5, in order to acquire that, you can stop kded5 and restart it from a terminal, like so:

kquitapp5 kded5
kded5

There will be some unrelated stuff. If you have Plasma 5.6, you may enable logging for kscreen by configuring categorized logging in ~/.config/QtProject/qtlogging.ini (create the file if it isn't there):

[Rules]
kscreen.*=true

Comment 3 George Kiagiadakis 2016-05-22 09:55:04 UTC

(In reply to Sebastian Kügler from comment #2)
> Jared, George, could you post the content of the files in
> ~/.local/share/kscreen after setting it up, and then after rebooting?

I'm sorry but I no longer have the appropriate setup available.

Comment 4 Sebastian Kügler 2016-05-23 07:26:02 UTC

Setting to NEEDSINFO for now.

Comment 5 Andrew Crouthamel 2018-09-26 22:06:28 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Andrew Crouthamel 2018-10-27 02:00:31 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!