Bug#648474: notification-daemon holds up gnome3-fallback start sequence

November 11th, 2011 - 05:00 pm ET by Joachim Breitner | Report spam
Package: notification-daemon
Version: 0.7.3-1
Severity: normal

Hash: SHA1

Hi,

I just finally upgraded to GNOME3, which I use in the fallback mode
to make use of xmonad. The session start takes a long time, and the
culprit is the notification daemon. This is the output from .xsession-errors
with gnome-session --debug:

gnome-session[17213]: DEBUG(+): GsmAutostartApp: starting notification-daemon
.desktop: command=/usr/lib/notification-daemon/notification-daemon startup-id
abe6cc85ee9fc9f13210479925733300000172130018
[... wait some time ...]
gnome-session[17213]: WARNING: Application 'notification-daemon.desktop' failed to register before timeout

Maybe it lost support for the gnome-session startup protoocl?

Greetings,
Joachim


Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages notification-daemon depends on:
ii libatk1.0-0 2.2.0-2
ii libc6 2.13-21
ii libcairo2 1.10.2-6.1
ii libcanberra-gtk3-0 0.28-3
ii libgdk-pixbuf2.0-0 2.24.0-1
ii libglib2.0-0 2.28.8-1
ii libgtk-3-0 3.0.12-2
ii libx11-6 2:1.4.4-2

notification-daemon recommends no packages.

notification-daemon suggests no packages.

/etc/xdg/autostart/notification-daemon.desktop changed:
[Desktop Entry]
Name=Notification Daemon
Comment=Display notifications
Exec=/usr/lib/notification-daemon/notification-daemon
Terminal=false
Type=Application
NoDisplay=true
OnlyShowIn=LXDE;OPENBOX;GNOME;
AutostartCondition=GNOME3 unless-session gnome
X-GNOME-Autostart-Phase=Initialization






To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 6 repliesReplies Make a reply

Replies

#1 Joachim Breitner
November 12th, 2011 - 06:10 pm ET | Report spam

Hi,

I debugged this some more, the reason is that the notification-daemon is
both autostarted by /etc/xdg/autostart/notification-daeomon.desktop
(from the notification-daemon package) and
by /usr/share/gnome-session/sessions/gnome-fallback.desktop. So one
starts, and the otherone quits immediately (due to the DBUS name being
taken) and gnome-session will wait endlessly. Possible solutions:
* Remove the autostart file again.
* Remove the notification-daemon entry from the session definition.
* Ignore the autostart file in the gnome-fallback session somehow.
* (Or maybe find a way to use dbus activation without race conditions.)

Greetings,
Joachim


Joachim "nomeata" Breitner
Debian Developer
| ICQ# 74513189 | GPG-Keyid: 4743206C
JID: | http://people.debian.org/~nomeata






To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

Similar topics