Bug 2698 - systemd + gdm: failure
Summary: systemd + gdm: failure
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 2120
  Show dependency treegraph
 
Reported: 2011-09-10 22:06 CEST by Guillaume Rousse
Modified: 2011-10-22 23:33 CEST (History)
4 users (show)

See Also:
Source RPM: gdm
CVE:
Status comment:


Attachments
.xsession-errors file (8.33 KB, application/octet-stream)
2011-09-10 22:07 CEST, Guillaume Rousse
Details
syslog except, with gdm messages (329.18 KB, application/octet-stream)
2011-09-10 22:08 CEST, Guillaume Rousse
Details

Description Guillaume Rousse 2011-09-10 22:06:58 CEST
Since friday, gdm has reverted to its old greeter windows, and is unable to create any functional user session.

I'm attaching .xsession-errors file, which shows a crash in gnome-session, as well as some issues with gsettings-data-convert respwaning too fast. I'm also attaching full syslog output, with gdm debug messages.
Comment 1 Guillaume Rousse 2011-09-10 22:07:42 CEST
Created attachment 779 [details]
.xsession-errors file
Comment 2 Guillaume Rousse 2011-09-10 22:08:42 CEST
Created attachment 780 [details]
syslog except, with gdm messages
Manuel Hiebel 2011-09-10 22:15:54 CEST

CC: (none) => fundawang

Comment 3 Guillaume Rousse 2011-09-11 10:27:21 CEST
Also, switching from gdm greeter screen to another VT is not possible.
Comment 4 Guillaume Rousse 2011-09-11 22:02:04 CEST
This appear to be a bit more complex...

When booting with systemd, they are actually two instances of gdm running: one with the old greeter dialog on VT2, and another one with the new greeter on VT1. The last one appears only after the first one, which explained why I originally missed it. None of them is functionning, tough.

when booting with sysinit, there is only one instance of gdm, with the old greeter, on VT2, but it seems to be unable to run gnome-shell, as it fallback into gnome-classical. This last issue seems to be related with this warning in .xsession-errors:
gnome-session[3803]: WARNING: Session 'gnome' runnable check failed: Quitté avec
 le code 1
Comment 5 Guillaume Rousse 2011-09-12 09:35:51 CEST
I guess the second problem (when using sysint) is the same as #2628 (permission issue), as closing the first gnome-classical session launched by gdm with old greeter leads to gdm with the new greeter, wich works as expected.
Comment 6 Guillaume Rousse 2011-09-12 20:59:58 CEST
Here are some issues identified from the logs in the systemd scenario, leading to potential suspects.

1) gdm

This occurs once:
Sep 12 15:44:53 localhost dbus[1646]: [system] Activating service name='org.freedesktop.login1' (using servicehelper)
Sep 12 15:44:53 localhost dbus[1646]: [system] Activated service 'org.freedesktop.login1' failed: Launch helper exited with unknown return code 1

This occurs once:
Sep 12 15:44:53 localhost gnome-session[2052]: DEBUG(+): fill: *** Launching helper '/usr/lib64/gnome-session-check-accelerated' to know if session is runnable
Sep 12 15:44:53 localhost gnome-session[2052]: WARNING: Session 'gdm-shell' runnable check failed: Quitté avec le code 1
Sep 12 15:44:53 localhost gnome-session[2052]: DEBUG(+): fill: *** Session is not runnable
Sep 12 15:44:53 localhost gnome-session[2052]: DEBUG(+): fill: *** Getting session 'gdm-fallback'

This occurs multiple times:
Sep 12 15:44:55 localhost gdm-password][2473]: AccountsService-DEBUG(+): Failed to identify the current session: Unable to lookup session information for process '2473'


2) gnome-session

This occurs multiple times:
Sep 12 19:48:06 localhost gnome-session[4542]: GLib-GObject-WARNING: invalid unclassed pointer in cast to `GtkWindow'
Sep 12 19:48:06 localhost gdm[6748]: ******************* START **********************************
Sep 12 19:48:06 localhost gdm[6748]: [Thread debugging using libthread_db enabled]
Sep 12 19:48:06 localhost gdm[6748]: [New Thread 0x7f353bfff710 (LWP 4655)]
Sep 12 19:48:06 localhost gdm[6748]: [New Thread 0x7f3543314710 (LWP 4653)]
Sep 12 19:48:06 localhost gdm[6748]: [New Thread 0x7f3543b15710 (LWP 4652)]
Sep 12 19:48:06 localhost gdm[6748]: 0x00007f35489d0e7d in waitpid () from /lib64/libpthread.so.0
Sep 12 19:48:06 localhost gdm[6748]: #0  0x00007f35489d0e7d in waitpid () from /lib64/libpthread.so.
[...]

3) RealtimeKit1:

Once (several occurences):
Sep 12 13:44:54 localhost rtkit-daemon[2318]: Failed to make ourselves RT: Operation not permitted

Then multiple times:
Sep 12 19:49:51 localhost dbus[2604]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Sep 12 19:49:51 localhost systemd[1]: Unit rtkit-daemon.service entered failed state.
Sep 12 19:49:51 localhost dbus[2604]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Sep 12 17:49:51 localhost rtkit-daemon[8626]: pthread_create failed: Resource temporarily unavailable
Sep 12 17:49:51 localhost rtkit-daemon[8626]: Demoting known real-time threads.
Sep 12 17:49:51 localhost rtkit-daemon[8626]: Demoted 0 threads.
Sep 12 19:49:51 localhost gnome-session[8606]: DEBUG(+): GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
Sep 12 19:49:51 localhost systemd[1]: rtkit-daemon.service: main process exited, code=exited, status=1
Sep 12 19:49:51 localhost systemd[1]: Unit rtkit-daemon.service entered failed state.

4) gsettings-data-convert
Multiple times:
Sep 12 19:45:46 localhost kernel: gsettings-data-[4675] trap int3 ip:7f0eab5cb539 sp:7fffb4334e30 error:0
Sep 12 19:45:46 localhost gnome-session[4542]: WARNING: Application 'gsettings-data-convert.desktop' killed by signal
Sep 12 19:45:46 localhost gnome-session[4542]: WARNING: App 'gsettings-data-convert.desktop' respawning too quickly
Sep 12 19:45:46 localhost gnome-session[4542]: WARNING: Error on restarting session managed app: Component 'gsettings-data-convert.desktop' crashing too quickly

Currently, RealtimeKit is my favorite candidate, as it doesn't crash in sysinit case, contrarily to gsettings-data-convert, which is probably a different issue. It seems similar to
https://bugzilla.redhat.com/show_bug.cgi?id=655321
Comment 7 Guillaume Rousse 2011-09-13 20:31:42 CEST
I just tested the following scenarios:
- systemd with multi-user target: OK
- systemd with graphical target and KDM: OK

So the problem seems to be the combination of systemd and gdm. BTW, how to enable gettys on free virtual terminal when using graphical target ? It would make debugging this issue a bit easier.

Summary: gdm is unable to create user session => systemd + gdm: failure

Manuel Hiebel 2011-09-13 20:51:14 CEST

CC: (none) => eugeni, mageia

Comment 8 John Balcaen 2011-09-13 21:13:00 CEST
(In reply to comment #7)
> So the problem seems to be the combination of systemd and gdm. BTW, how to
> enable gettys on free virtual terminal when using graphical target ? It would
> make debugging this issue a bit easier.
If i'm not wrong it's related to plymouth, maybe you should try to disable plymouth.

CC: (none) => balcaen.john

Funda Wang 2011-09-14 06:07:22 CEST

CC: fundawang => (none)

Comment 9 Colin Guthrie 2011-09-16 20:17:18 CEST
Out of curiosity what is the output from:

systemctl list-units| grep plym

I simply get:
plymouth-start.service    loaded failed failed        Show Plymouth Boot Screen
Comment 10 Guillaume Rousse 2011-09-26 11:17:00 CEST
Everything works OK when disabling speedboot.
Comment 11 Colin Guthrie 2011-09-26 11:22:58 CEST
Cool :)

Thanks for letting me know. I meant to do this by now (rip out speedboot) but haven't had time yet.

At least we know this will work :D
Manuel Hiebel 2011-10-07 14:40:16 CEST

Blocks: (none) => 2120

Comment 12 D Morgan 2011-10-22 23:33:53 CEST
closing as speeboot is now disabled by default when systemd is enabled.

Please test the packages from core/updates_testing and reopen this bugreport if still valid.

Status: NEW => RESOLVED
CC: (none) => dmorganec
Resolution: (none) => FIXED


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