Bug 841755 - GDM does not display greeter
Summary: GDM does not display greeter
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Dan Mashal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-20 07:28 UTC by Stef Walter
Modified: 2012-07-31 02:59 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
: 844463 (view as bug list)
Environment:
Last Closed: 2012-07-31 02:59:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Stef Walter 2012-07-20 07:28:13 UTC
Description of problem:

After updating to latest rawhide GDM does not display a greeter.

Version-Release number of selected component (if applicable):

Installed Packages
Name        : gdm
Arch        : x86_64
Epoch       : 1
Version     : 3.5.4

Name        : dconf
Arch        : x86_64
Version     : 0.13.4
Release     : 1.fc18


Log messages:


[root@stef-rawhide gdm]# tail /var/log/gdm/\:0-greeter.log

** (gnome-settings-daemon:1823): CRITICAL **: unable to create file '/run/user/42/dconf': Is a directory.  dconf will not work properly.

** (gnome-settings-daemon:1823): CRITICAL **: unable to create file '/run/user/42/dconf': Is a directory.  dconf will not work properly.

** (gnome-settings-daemon:1823): CRITICAL **: unable to create file '/run/user/42/dconf': Is a directory.  dconf will not work properly.

** (gnome-settings-daemon:1823): CRITICAL **: unable to create file '/run/user/42/dconf': Is a directory.  dconf will not work properly.

** (gnome-settings-daemon:1823): CRITICAL **: unable to create file '/run/user/42/dconf': Is a directory.  dconf will not work properly.

Comment 1 Yanko Kaneti 2012-07-20 11:31:34 UTC
I've had a similar symptom that got "fixed" by downgrading dconf

Comment 2 Jens Petersen 2012-07-23 08:58:22 UTC
Rawhide gdm hasn't started for me for some weeks.

It would be great if this could be fixed,
so that gdm might work once a rawhide install boots again...

Comment 3 Stef Walter 2012-07-23 11:15:11 UTC
Updating rawhide fixed this for me.

Comment 4 Dan Mashal 2012-07-24 04:05:06 UTC
I can confirm that I experienced this issue yesterday after installing Rawhide on a working F17 system. I will try an update and see if it helps.

Thanks,
Dan

Comment 5 Jens Petersen 2012-07-24 04:48:56 UTC
Okay miracle - gdm is working for me now too. :-)

To reproduce:

1. install fresh f17
2. update to latest f17 packages
3. yum install fedora-release-rawhide
4. yum update --enablerepo=rawhide gdm  (and a couple of other broken deps)
5. reboot and gdm comes up for me

Comment 6 Dan Mashal 2012-07-24 15:33:27 UTC
It does not for me in a Virtualbox VM.

Also libgphoto2 causes yum update to fail.

Comment 7 Ray Strode [halfline] 2012-07-24 21:59:29 UTC
there were a couple of issues:

1) dconf change its file format for dconf profiles
2) the mass rebuild meant that gdm got in one compose and the required corresponding gnome-shell didn't make the cut.

Comment 8 John Ellson 2012-07-28 16:48:51 UTC
I'll add to this bug, if I may, because I think its probably related.  Still no GDM screen for me in a rawhide virtual-host console:

kernel-3.6.0-0.rc0.git2.1.fc18.x86_64
gdm-3.5.4.2-2.fc18.x86_64
dconf-0.13.4-2.fc18.x86_64
xorg-x11-server-Xorg-1.12.99.903-2.20120726.fc18.x86_64


# tail /var/log/gdm/:0.log
memory space from 0x7f0877b77000 to 0x7f0879b75000
memory space from 0x7f0872b77000 to 0x7f0876b77000
slots start: 1, slots end: 7
done reset
(II) UXA(0): Driver registered support for the following operations:
(II)         solid
(II)         copy
(II)         composite (RENDER acceleration)
(II)         put_image
Xorg: privates.c:560: dixPrivatesSize: Assertion `!screen_specific_private[type]' failed.

Comment 9 Jens Petersen 2012-07-30 05:10:51 UTC
(In reply to comment #8)
> I'll add to this bug, if I may, because I think its probably related.

Does X start for you?

For me currently X can't start from a rawhide install.
(Above testing was done on a F17 install + some Rawhide packages.)

Comment 10 John Ellson 2012-07-30 15:32:45 UTC
No.  Or at least, it hangs halfway with a blank screen. Sounds like you might have the same issue with Rawhide?

/var/log/Xorg.0.log  just ends with:
[    22.583] memory space from 0x7fca48f21000 to 0x7fca4af1f000
[    22.583] memory space from 0x7fca43f21000 to 0x7fca47f21000
[    23.287] slots start: 1, slots end: 7
[    23.287] done reset
[    23.288] (II) UXA(0): Driver registered support for the following operations:
[    23.288] (II)         solid
[    23.288] (II)         copy
[    23.288] (II)         composite (RENDER acceleration)
[    23.288] (II)         put_image


which is the same as /var/log/gdm/:0.log ends, but without the:
Xorg: privates.c:560: dixPrivatesSize: Assertion `!screen_specific_private[type]' failed.

The system is usable from ssh login, and no process is running away with cpu cycles.

Comment 11 John Ellson 2012-07-30 16:36:11 UTC
Still broken with:  kernel-3.6.0-0.rc0.git4.1.fc18.x86_64

/var/log/messages contains:

Jul 30 12:16:52 rawhide-64 gdm-simple-slave[800]: DEBUG(+): GdmSimpleSlave: Started X server
Jul 30 12:16:52 rawhide-64 dbus-daemon[486]: dbus[486]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.8" (uid=0 pid=603 comm="/usr/sbin/gdm-binary -nodaemon ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.20" (uid=0 pid=800 comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")
Jul 30 12:16:53 rawhide-64 abrt[805]: Not dumping repeating crash in '/usr/bin/Xorg'
Jul 30 12:16:53 rawhide-64 gdm-simple-slave[800]: DEBUG(+): GdmServer: child (pid:803) done (signal:6)
Jul 30 12:16:53 rawhide-64 gdm-simple-slave[800]: DEBUG(+): GdmSimpleSlave: server died with signal 6, (Aborted)
Jul 30 12:16:53 rawhide-64 gdm-simple-slave[800]: DEBUG(+): slave finished
Jul 30 12:16:53 rawhide-64 gdm-simple-slave[800]: DEBUG(+): GdmSimpleSlave: Stopping simple_slave
Jul 30 12:16:53 rawhide-64 gdm-simple-slave[800]: DEBUG(+): GdmSlave: Stopping slave
Jul 30 12:16:53 rawhide-64 gdm-simple-slave[800]: DEBUG(+): GdmSignalHandler: Removing handler 10: signum=11 0x40c390
Jul 30 12:16:53 rawhide-64 gdm-simple-slave[800]: DEBUG(+): GdmSlave: Stopping slave
Jul 30 12:16:53 rawhide-64 gdm-simple-slave[800]: DEBUG(+): GdmSignalHandler: Finalizing signal handler
Jul 30 12:16:53 rawhide-64 gdm-simple-slave[800]: DEBUG(+): Slave finished
Jul 30 12:16:53 rawhide-64 gdm-binary[603]: DEBUG(+): GdmDisplay: Finishing display: /org/gnome/DisplayManager/Displays/_5
Jul 30 12:16:53 rawhide-64 gdm-binary[603]: DEBUG(+): GdmDisplay: Unmanaging display
Jul 30 12:16:53 rawhide-64 gdm-binary[603]: DEBUG(+): GdmDisplay: unmanage display
Jul 30 12:16:53 rawhide-64 gdm-binary[603]: DEBUG(+): GdmSlaveProxy: Killing slave
Jul 30 12:16:53 rawhide-64 gdm-binary[603]: DEBUG(+): GdmCommon: sending signal 15 to process 800
Jul 30 12:16:53 rawhide-64 gdm-binary[603]: DEBUG(+): GdmCommon: process (pid:800) done (status:0)
Jul 30 12:16:53 rawhide-64 gdm-binary[603]: DEBUG(+): GdmSlaveProxy: slave died with exit status 0
Jul 30 12:16:53 rawhide-64 gdm-binary[603]: DEBUG(+): GdmSlaveProxy: Disposing slave proxy
Jul 30 12:16:53 rawhide-64 gdm-binary[603]: DEBUG(+): GdmSlaveProxy: Killing slave
Jul 30 12:16:53 rawhide-64 gdm-binary[603]: WARNING: GdmDisplay: display lasted 0.887870 seconds
Jul 30 12:16:53 rawhide-64 gdm-binary[603]: DEBUG(+): GdmLocalDisplayFactory: display status changed: 4
Jul 30 12:16:53 rawhide-64 gdm-binary[603]: DEBUG(+): GdmDisplayStore: Unreffing display: 0x214ece0
Jul 30 12:16:53 rawhide-64 gdm-binary[603]: WARNING: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors

Comment 12 Ray Strode [halfline] 2012-07-30 18:15:44 UTC
that bug is actually distinct from the other two mentioned in comment 7 (which were actually distinct from each other).

Let's clone this bug instead of muddying it up more (I'll clone it).

Comment 13 Ray Strode [halfline] 2012-07-30 18:19:04 UTC
The clone is bug 844463

Comment 14 Jens Petersen 2012-07-31 02:59:27 UTC
(In reply to comment #10)
> No.  Or at least, it hangs halfway with a blank screen. Sounds like you
> might have the same issue with Rawhide?

Ok, which driver are you using?

I got Rawhide X and gdm working for me with cirrus driver on kvm
(I have to turn off selinux to get rawhide to boot and the default
virt qxl driver seems to have problems).

(I asked since I thought possibly you were thinking gdm was not working
because X seems very slow now with debugging kernel.)

I am closing this one out since gdm has clearly been working now in rawhide
for a while: as Ray says bug 844463 seems to be a different issue.


Note You need to log in before you can comment on or make changes to this bug.