Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#23074 - [MPD] GDM slower to up.

Attached to Project: Arch Linux
Opened by Alexandre (alexcortes) - Monday, 28 February 2011, 04:14 GMT
Last edited by Angel Velasquez (angvp) - Thursday, 23 June 2011, 17:09 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Angel Velasquez (angvp)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description: Using MPD daemon (with pulseaudio). It's working fine, but GDM delay 25sec to up, if MPD is removed from daemon array GDM is up in 2sec/3sec. If MPD be backgrouded or not is same delay.

Boot not show errors.
Using "mpd" user for MPD. if i use my "user" is same.


Additional info:

gdm 2.32.0-5
mpd 0.16.1-1

Attached: mpd.conf - rc.conf

   mpd.conf (13.1 KiB)
   rc.conf (3.5 KiB)
This task depends upon

Closed by  Angel Velasquez (angvp)
Thursday, 23 June 2011, 17:09 GMT
Reason for closing:  Upstream
Additional comments about closing:  Please report this to mpd and gnome
Comment by Karol Babioch (johnpatcher) - Monday, 14 March 2011, 09:13 GMT
Experiencing the same issue, getting the following errors whenever mpd is started up using the DAEMONS array within rc.conf:

Mar 14 08:41:55 localhost rtkit-daemon[2997]: Warning: PolicyKit call failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Mar 14 09:41:55 localhost gdm-simple-slave[2929]: WARNING: unable to determine if seat can activate sessions: Activation of org.freedesktop.ConsoleKit timed out
Mar 14 09:41:56 localhost console-kit-daemon[3517]: WARNING: Failed to acquire org.freedesktop.ConsoleKit
Mar 14 09:41:56 localhost console-kit-daemon[3517]: WARNING: Could not acquire name; bailing out
Mar 14 09:41:56 localhost pulseaudio[2995]: main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.

It seems to me that mpd is somehow blocking dbus. Couldn't find such an issue in the upstream bug tracker, so maybe there is something wrong with Arch here? How to check this? Which configuration files do I/you need to take a look at?
Comment by Alexandre (alexcortes) - Monday, 14 March 2011, 18:17 GMT
I don't find any other form to resolve.
For me, if i use MPD like normal user (.xinitrc) it's fail, but up normally if i try again after the end of login.
Comment by Jelle van der Waa (jelly) - Thursday, 31 March 2011, 12:17 GMT
and what if you try inittab instead of starting gdm via the DAEMONS array ( works better than daemons here )
Comment by Alexandre (alexcortes) - Thursday, 31 March 2011, 20:00 GMT
Exactly the same for me.

Thanks.

EDIT: Problem continues
Comment by André Prata (nDray) - Friday, 08 April 2011, 01:15 GMT
I can confirm this.
MPD, even "backgrounded", is slowing down the GDM launch, and even the runlevel 3 login!

What happens at runlevel 5 is that GDM takes very long to start and, when it does, sometimes, the user list is empty.
At runlevel 3, I enter the username, then the password, and it immediately tells me the last login, but the prompt takes a very long time to show up.

It affects only the first login. If I logout and log back in again, it does so without any lag.

EDIT: It started today only. I'm guessing the conflict is with pulseaudio, that Gnome3 brought and I don't remember ever having it before...
Comment by Jun Wu (quark) - Wednesday, 04 May 2011, 04:30 GMT
Experience the same here.

mpd 0.16.2-3

MPD (no matter started directly or in background) is not only slowing down GDM, but also tty login. Usually 10 to 25 seconds.
Also confirms that it only slow down the first login.

Besides the slow down, MPD is causing other troubles.
If I login a tty and use startx to start gnome3, the first time (the session slowed down by MPD), gnome3 always choose fallback mode.
When I login again (no matter whether logout the first session), gnome3 can start normally.
No obvious differences found in environment variables of these two sessions.

As Karol Babioch (johnpatcher) says, it seems mpd is blocking dbus.... but i wonder how dbus can be blocked ?

Loading...