English
Ask Your Question
0

After update of Fedora 18 screen blinks 4-5 times; no GDM

asked 2013-02-20 10:55:40 +0000

Linuxghost gravatar image

updated 2013-07-13 06:38:15 +0000

After the update to kernel 3.7.7 i can no longer login. The screen blinks 4 or 5 times and no gdm. This shows up in the gdm-slave log;

gdm-simple-slave[1537]: WARNING: Failed to give slave programs access to the display. Trying to proceed. gdm-launch-environment][1552]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) gdm-launch-environment][1552]: pam_unix(gdm-launch-environment:session): session closed for user gdm gdm-simple-slave[1537]: GLib-GObject-CRITICAL: g_object_ref: assertion object->ref_count > 0' failed gdm-simple-slave[1537]: GLib-GObject-CRITICAL: g_object_unref: assertionobject->ref_count > 0' failed and in the messages; dbus-daemon[803]: dbus[803]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.4" (uid=0 pid=841 comm="/usr/sbin/gdm-binary ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.56" (uid=0 pid=1633 comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")

And in the messages;

dbus-daemon[803]: dbus[803]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.4" (uid=0 pid=841 comm="/usr/sbin/gdm-binary ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.56" (uid=0 pid=1633 comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")

Xorg finishes without errors, i'm using the intel GPU

edit retag flag offensive close merge delete

Comments

I'm sorry, i can't help you anymore.

lnxslck ( 2013-02-20 18:33:21 +0000 )edit

Anyone can???

Linuxghost ( 2013-02-22 16:31:50 +0000 )edit

Have you tried the answer given by FranciscoD?

lnxslck ( 2013-02-22 16:35:14 +0000 )edit

Maybe sssd is not installed. Can you install it?

lnxslck ( 2013-05-04 14:36:45 +0000 )edit

2 answers

Sort by ยป oldest newest most voted
0

answered 2013-05-03 15:21:37 +0000

This is probably the problem:

gdm-simple-slave[1030]: WARNING: Failed to give slave programs access to the display. Trying to proceed.

That error message is not helpful at all. In order to investigate why GDM can't be brought up, try to start X yourself. Then startx observe the output carefully. If it yells something about "missing library" do a yum distro-sync but with --disablerepo for all the external repositories.

edit flag offensive delete link more
0

answered 2013-02-22 14:37:25 +0000

There was a known bug I think that prevented gdm from starting. In a virtual terminal (ctrl alt f2), login as root and try:

systemctl restart gdm.service

This was fixed in an upgrade and should not occur with latest packages. Please update your system.

edit flag offensive delete link more

Comments

Thank you FranciscoD! After the last time GDM worked about 5 updates flew by. The system was distro-synced after my upgrade as adviced. Today still up-to-date. I have restarted gdm.service a dozen times after each update; the errors persist.

Linuxghost ( 2013-02-22 16:37:42 +0000 )edit

Could be some files from the previous installation. Try: http://fedorasolved.org/Members/fenris02/postupgradecleanup

FranciscoD_ ( 2013-05-05 07:50:16 +0000 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Use your votes!

  • Use the 30 daily voting points that you get!
  • Up-vote well framed questions that provide enough information to enable people provide answers.
  • Thank your helpers by up-voting their comments and answers. If a question you asked has been answered, accept the best answer by clicking on the checkbox on the left side of the answer.
  • Down-voting might cost you karma, but you should consider doing so for incorrect or clearly detrimental questions and answers.

Stats

Asked: 2013-02-20 10:55:40 +0000

Seen: 3,826 times

Last updated: Jul 13 '13