[arch-general] Display Manager issue
Good Morning folks, my DM is behaving strange. The systems boote to a bblank screen with a mouse cursor. To be able tologin I have to press Ctrl+Alt-F2 followed by Alt+F1. The journal does not provide any clue that somethings going wrong. Any ideas? Thanks Frank
On 16.09.2014 07:28, Frank Zimmermann wrote:
my DM is behaving strange.
Can you maybe provide information which DM it is? Could be related to that. Did you change anything in the Xorg.conf files? Do you have set up xrandr defaults recently?
The systems boote to a bblank screen with a mouse cursor. To be able tologin I have to press Ctrl+Alt-F2 followed by Alt+F1. The journal does not provide any clue that somethings going wrong. Any ideas?
Thanks Frank
Best, Heiko
On 2014-09-16 07:57:33, Heiko Becker wrote:
On 16.09.2014 07:28, Frank Zimmermann wrote:
my DM is behaving strange.
Can you maybe provide information which DM it is? Could be related to that.
I see the same for quite a while. With Lightdm. I disabled xdm in the meantime and startx instead, which does not expose the same symptoms of X-fckup.
Did you change anything in the Xorg.conf files?
Lol. This is arch. Of course we did. The transition "working" -> "not working" wasn't triggered by config editing but by a pacman -Syu though.
On Tue, 16 Sep 2014 08:06:25 +0200 "Martin S. Weber" <Ephaeton@gmx.net> wrote:
On 2014-09-16 07:57:33, Heiko Becker wrote:
On 16.09.2014 07:28, Frank Zimmermann wrote:
my DM is behaving strange.
Can you maybe provide information which DM it is? Could be related to that.
I see the same for quite a while. With Lightdm. I disabled xdm in the meantime and startx instead, which does not expose the same symptoms of X-fckup.
Did you change anything in the Xorg.conf files?
Lol. This is arch. Of course we did. The transition "working" -> "not working" wasn't triggered by config editing but by a pacman -Syu though.
Exactly the same issue here but with KDE using KDM switch to using "Startx" no more problems . It appears to be a permissions thing but i have been unable to pin it down . Pete . -- Please note: No trees were killed in the sending of this message. However a large number of electrons were terribly inconvenienced.
On 16 September 2014 07:28, Frank Zimmermann <frank.zimmermann.berlin@freenet.de> wrote:
Good Morning folks,
my DM is behaving strange. The systems boote to a bblank screen with a mouse cursor. To be able tologin I have to press Ctrl+Alt-F2 followed by Alt+F1. The journal does not provide any clue that somethings going wrong.
X and lightdm don't log to the journal. check their log files -- damjan
Am Di, 16. Sep, 2014 um 10:51 schrieb Damjan Georgievski <gdamjan@gmail.com>:
On 16 September 2014 07:28, Frank Zimmermann <frank.zimmermann.berlin@freenet.de> wrote:
Good Morning folks,
my DM is behaving strange. The systems boote to a bblank screen with a mouse cursor. To be able tologin I have to press Ctrl+Alt-F2 followed by Alt+F1. The journal does not provide any clue that somethings going wrong.
X and lightdm don't log to the journal. check their log files
-- damjan I tried lxdmand lightdm both show same behavior, no changes to xorg.conf etc.
KR FRank
On Tue, 2014-09-16 at 12:37 +0200, Frank Zimmermann wrote:
I tried lxdmand lightdm both show same behavior, no changes to xorg.conf etc.
Doesn't provide any of those files useful information $ sudo cat /var/log/lightdm/lightdm.log $ sudo cat /var/log/lightdm/x-0-greeter.log $ sudo cat /var/log/lightdm/x-0.log $ grep EE /var/log/Xorg.0.log ?
Am Di, 16. Sep, 2014 um 1:13 schrieb Ralf Mardorf <ralf.mardorf@rocketmail.com>:
On Tue, 2014-09-16 at 12:37 +0200, Frank Zimmermann wrote:
I tried lxdmand lightdm both show same behavior, no changes to xorg.conf etc.
Doesn't provide any of those files useful information $ sudo cat /var/log/lightdm/lightdm.log $ sudo cat /var/log/lightdm/x-0-greeter.log $ sudo cat /var/log/lightdm/x-0.log $ grep EE /var/log/Xorg.0.log ? In Xorg.0.log I get the following: systemd-logind: failed to get session: PID 212 does not belong to any known session
2014-09-16 9:43 GMT-03:00 Frank Zimmermann < frank.zimmermann.berlin@freenet.de>:
In Xorg.0.log I get the following: systemd-logind: failed to get session: PID 212 does not belong to any known session
Are you sure the Xorg server is running as root or inside a session? It just might be that the login manager is doing some weird thing the new Xorg can't allow anymore. I get the same kind of error when using bumblebee: bumblebeed[529]: [19535.167046] [ERROR][XORG] (EE) systemd-logind: failed to get session: PID 10552 does not belong to any known session I can use the Xorg server without any problems though. Any other useful log? Also, are you checking the system journal instead of only the user one? -- Mateus Rodrigues Costa
On Tue, 2014-09-16 at 14:24 -0300, Mateus Rodrigues Costa wrote:
system journal
IIUC the first thing he did, was to check the system journal :(.
I do not use login manager but did you try to put "needs_root_rights = yes" in /etc/x11/Xwrapper.config to fix root/user permission arizing with the new xorg-server version ?
participants (8)
-
Damjan Georgievski
-
fabien boitier
-
Frank Zimmermann
-
Heiko Becker
-
Martin S. Weber
-
Mateus Rodrigues Costa
-
pete nikolic
-
Ralf Mardorf