This is strange indeed, as both notify-osd and notification-daemon get
D-BUS activated when needed. What could happen is that they crash when
being activated the first time, which would give the "The name
org.freedesktop.Notifications was not provided by any .service files"
error.
I could paper over this in Jockey by catching and ignoring the error,
but that would just hide the actual problem. Do you get a crash of
notify-osd in /var/crash/ and/or dmesg when this happens?
** Changed in: jockey (Ubuntu Oneiric)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/819506
Title:
jockey-gtk crashed with GError in function():
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.Notifications was not provided by any .service files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/819506/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
