Bug 350395 - Catch xrandr errors/Can configure black screen on notebook
Summary: Catch xrandr errors/Can configure black screen on notebook
Status: RESOLVED UNMAINTAINED
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 1.0.1
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Daniel Vrátil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-20 08:49 UTC by t_d_l_c
Modified: 2015-07-28 13:10 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
call xrandr --auto on xrandr errors (1.28 KB, patch)
2015-07-20 08:52 UTC, t_d_l_c
Details

Note You need to log in before you can comment on or make changes to this bug.
Description t_d_l_c 2015-07-20 08:49:13 UTC
On a notebook, in the "kcmshell4 display" - dialog it is possible to create a multihead configuration that blackens the notebook screen. This is not wrong as long as you have external screens activated. But if you save such a configuration as standard and unplug the external monitors, you still get a black screen on the notebook and can't see anything at all. 

This is not nice for user who put their notebook in a docking station to use two external monitors.

Our system is based on Ubuntu 12.04, but modified.


Reproducible: Always

Steps to Reproduce:
Tested on a notebook, in this case a lenovo X220i
1. Connect external vga-monitor to the notebook.
2. Open kcmshell4 display
3. Configure screens so that the notebook screen is deactivated and the vga screen is active.
4. Save as standard configuration.
5. Switch off the notebook.
6. Unplug vga monitor.
7. Switch on notebook.
8. Kdm starts, login 

Actual Results:  
Kdm crashes, screen remains black, no way to get out for a normal user. Workaround is deleting ~/.kde4/share/config/krandrrc and restart Kdm.

Expected Results:  
A sensible default monitor configuration is chosen, with the notebook screen enabled.

I have noticed that the multihead configuration is set in /usr/bin/krandrstartup. This script does not check the return value of xrandr, which could imho solve the problem. If xrandr returns an error, a sensible default configuration should be activated.
I will provide a patch, you can use it if you like it.
Comment 1 t_d_l_c 2015-07-20 08:52:57 UTC
Created attachment 93658 [details]
call xrandr --auto on xrandr errors
Comment 2 t_d_l_c 2015-07-27 09:23:21 UTC
KDE 4.12.0
Comment 3 Christoph Feck 2015-07-28 13:10:33 UTC
krandr is long unmaintained. You should use a distribution that offers kscreen, version 1.0.5 or newer.