Bug#747465: notification-daemon crashes and missing dbus configuration

[intrigeri]

Control: retitle -1 notification-daemon crashes
Control: severity -1 important

Hi,

Maximilian Gerhard wrote (08 May 2014 14:32:14 GMT) :
> When I start notification-daemon in an LXDE environment and try to send
> a notification via notifiy-send, the expected notification popup appears but
> notification-daemon crashes now with the following message in terminal:

> (notification-daemon:2280): GLib-CRITICAL **: Source ID 17 was not found when attempting to remove it

I'm experiencing a very similar bug (up-to-date Debian sid, GNOME
Flashback):

  $ /usr/lib/notification-daemon/notification-daemon 

  (notification-daemon:5179): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -23 and height 27

  (notification-daemon:5179): GLib-CRITICAL **: Source ID 17 was not found when attempting to remove it
  Trace/breakpoint trap

Triggered by:

  $ notify-send "blabla blablab blabl$RANDOM" "sdfsdf sdfsf wfw efwefwef wefw efwefwefwefwe fwefa\n wefwe wef wz"

The first line output by notification-daemon is displayed once
notify-send is run, and the two last ones seem to be displayed once
the notification disappears from screen.

Note that the notification text is truncated, will report separately
in case it's an entirely different issue (looks like #684474).

And on Wheezy (GNOME fallback, aka. GNOME "classic" there), I "only"
get a truncated notification, and:

  (notification-daemon:3238): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -23 and height 27

... but notification-daemon is not crashing. So, there's a regression
that affects GNOME Flashback in Jessie.

Maximilian, may you please share how exactly you can reproducibly
trigger the bug you reported, so that we can know if yours is the same
bug as the one I'm experiencing?

> Another execution of notify-send does nothing anymore.

Indeed, notification-daemon is not running anymore :(

> I found out that notifications work correct if I provide the
> following file
> /usr/share/dbus-1/services/org.gnome.Notifications.service with
> content:

Apparently, the decision of shipping a dbus activation file (or not)
is now the responsibility of desktop environments that need it.

While I see why there's a user experience regression compared to
Squeeze (in DEs that don't ship such a file), once combined with the
fact that notification-daemon crashes so easily, I don't think that's
a bug in notification-daemon itself. Retitling this bug report
accordingly, to focus on one single problem at a time (which is what
a bug report should be about, IMO).

Cheers,
--
  intrigeri
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc