unity-settings-daemon crashes using xrandr
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-settings-daemon (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
turning the screen by running the command 'xrand -o right' turns the screen, but it then immediately comes back to normal. Then I get a crash message of unity-settings-
Unfortunately I failed to create a bug report by submitting the crash report, so I'll attach it to this report and hope you can find all the necessary information. Feel free to ask for more information or mark it as duplicate pointing to an existing bug report.
Software: Pretty vanilla Ubuntu 15.04
Hardware: Thinkpad Yoga 12
I first recognised the bug when using following script: https:/
This is the error message I get trying to run graphical applications from command line as mentioned above in the bug description: ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- - mir_display_ open
-------
simon@laptop:~$ eog
Maximum number of clients reached
** (eog:7631): WARNING **: Could not open X display
Maximum number of clients reachedgdk_
Failed to connect to Mir: Failed to connect to server socket: Datei oder Verzeichnis nicht gefunden
Unable to init server: Verbindung ist gescheitert: Verbindungsaufbau abgelehnt
(eog:7631): Gtk-WARNING **: cannot open display: :0 ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- -
simon@laptop:~$
-------
The two German texts are in English:
Datei oder Verzeichnis nicht gefunden --> File or folder not found
Verbindung ist gescheitert: Verbindungsaufbau abgelehnt --> Connection has failed: Connection establishment refused
This also leads to the problem that I cannot start any new applications at all. I first have to log off and on again.
The problem happens repeatedly some time after logging in. I don't get any visual error message.
It actually seems that it is not necessary to turn the screen to provoke this problem. So this may be another problem than the one original stated in this bug report. Please tell me if I shall open another bug report for it and how to debug this problem. A first glance at dmesg didn't show anything useful.