Ask Your Question

0xee's profile - activity

2014-04-09 13:38:54 -0600 commented question [FC20] Dual head with bumblebee with Lenovo W520 panning instead of displaying desktop properly

I'm currently havinv a similar problem. In my case, intel-virtual-output fails. Could you provide your bumblebee-nvidia.conf, to lead me in the right direction? Thank you!

2013-10-03 18:23:26 -0600 received badge  Famous Question (source)
2013-09-03 06:22:42 -0600 received badge  Notable Question (source)
2013-09-03 04:15:05 -0600 received badge  Editor (source)
2013-09-03 04:11:40 -0600 received badge  Popular Question (source)
2013-09-02 14:18:15 -0600 received badge  Student (source)
2013-09-02 14:06:03 -0600 asked a question Black screen on GDM start, Gnome works

When I boot my Fedora 19 (all updates applied, kernel 3.10.10, nvidia drivers; on a Lenovo W530), I can see the nvidia logo flash, but afterwards the screen stays black (also no cursor, just pitch black), and no gdm comes up. I tried lightdm instead of gdm, which works, but I can't use it because it's not able to lock the screen with gnome.

If I change to tty2 when I see the black screen, I can login and start gnome by using startx, and systemctl status gdm tells me that gdm is active/running, But if I try to lock the screen, everything goes black and I can't even switch to another virtual terminal

Xorg log shows no errors and /var/log/messages only shows 6 occurrences of this message:

Sep 2 20:39:37 w530-fedora sysinit[595]: Unable to connect to X server

and the last line is:

Sep 2 20:39:37 w530-fedora dbus-daemon[623]: dbus[623]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.7" (uid=0 pid=693 comm="/usr/sbin/gdm ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.8" (uid=0 pid=780 comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")

i have already googled a lot, but most people experience errors only after login, not when starting gdm.

Thanks for any help!

Edit: I was able to fix the problem. Somehow the gdm user account had expired, which apparently prevented gdm from getting an x session. Reactivating the account with chage -E -1 gdm fixed it.