Your message dated Tue, 31 Jan 2012 13:17:38 +0000
with message-id <[email protected]>
and subject line Bug#640120: fixed in notify-osd 0.9.32-1
has caused the Debian Bug report #640120,
regarding Stop starting notify-osd via dbus activation
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
640120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640120
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xfce4-notifyd
Version: 0.2.2-1
Severity: normal
Hi,
there have been some recent changes in notification-daemon and the way
it is started. It previously was started via dbus activation on-demand.
This had the unpleasant side effect, that shipping different
notification systems either had to conflict with each other or divert
the dbus service file (or ship it under a different dbus service file
name where it no longer was clear which service would be started then).
In GNOME 3, the notification system is integrated into gnome-shell itself,
which is komparable with how kdebase-workspace does it.
As a consequence, the dbus service file was removed from
notification-daemon, as this could otherwise lead to a race when
gnome-shell is started [1]. In the GNOME 3 fallback or GNOME 2 case, we
start notification-daemon via the session manager now.
For GNOME 2, we ship a autostart file in gnome-session 2 in
/usr/share/gnome/autostart. gnome-session 3 will start
notification-daemon in the fallback case and we also ship a XDG
autostart file, which should handle non-GNOME environments.
It currently lists:
OnlyShowIn=LXDE;OPENBOX;GNOME;
AutostartCondition=GNOME3 unless-session gnome
I.e. XFCE is explicitly excluded, as I assumed that for XFCE the
preferred notification system is xfce4-notifyd.
We have been discussing that on IRC for a while, and we came to the
conclusion, that it should be up to the individual desktop environment
to depend on its notification system of choice.
The notification daemons should no longer be started via dbus activation
and instead by the session manager, so we have a defined and reliabe
behaviour.
If you can agree with that, please update xfce4-notifyd accordingly and
make the xfce4 metapackage depend/recommend xfce4-notifyd.
I also think, that individual applications should not directly depend on
notification-daemon directly. But this should be discussed / fixed
independently from this bug.
Cheers,
Michael
[1]
http://git.gnome.org/browse/notification-daemon/commit/?id=1ad20d22098bc7718614a8a87744a2c22d5438d0
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.0.0-1-486
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xfce4-notifyd depends on:
ii libc6 2.13-18
ii libcairo2 1.10.2-6.1
ii libdbus-1-3 1.4.14-1
ii libdbus-glib-1-2 0.94-4
ii libgdk-pixbuf2.0-0 2.23.5-3
ii libglib2.0-0 2.28.6-1
ii libgtk2.0-0 2.24.5-4
ii libpango1.0-0 1.28.4-3
ii libx11-6 2:1.4.4-1
ii libxfce4ui-1-0 4.8.0-3
ii libxfce4util4 4.8.1-3
ii libxfconf-0-2 4.8.0-3
Versions of packages xfce4-notifyd recommends:
ii libnotify-bin 0.7.3-2
xfce4-notifyd suggests no packages.
--- End Message ---
--- Begin Message ---
Source: notify-osd
Source-Version: 0.9.32-1
We believe that the bug you reported is fixed in the latest version of
notify-osd, which is due to be installed in the Debian FTP archive:
notify-osd_0.9.32-1.diff.gz
to main/n/notify-osd/notify-osd_0.9.32-1.diff.gz
notify-osd_0.9.32-1.dsc
to main/n/notify-osd/notify-osd_0.9.32-1.dsc
notify-osd_0.9.32-1_amd64.deb
to main/n/notify-osd/notify-osd_0.9.32-1_amd64.deb
notify-osd_0.9.32.orig.tar.gz
to main/n/notify-osd/notify-osd_0.9.32.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrew Starr-Bochicchio <[email protected]> (supplier of updated notify-osd
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Tue, 31 Jan 2012 13:53:39 +0100
Source: notify-osd
Binary: notify-osd
Architecture: source amd64
Version: 0.9.32-1
Distribution: unstable
Urgency: low
Maintainer: The Ayatana Packagers <[email protected]>
Changed-By: Andrew Starr-Bochicchio <[email protected]>
Description:
notify-osd - daemon that displays passive pop-up notifications
Closes: 541779 636669 640120
Changes:
notify-osd (0.9.32-1) unstable; urgency=low
.
* Merge new upstream release from Ubuntu.
- Drop Conflict/Replace on notify-daemon and alsdorf.(Closes: #541779).
- Fixes FTBFS with libnotify 0.7 (Closes: #636669).
* Remaining Debian changes:
- debian/control:
+ Update Standards-Version, change Maintainer and VCS fields.
+ Do not recommend notify-osd-icons, not in Debian.
- src/defaults.c: Use dynamic slot allocation (See: #550592)
- debian/rules: Generate debian/changelog.upstream
- notify-osd.{preinst, postrm}: Do not redirect output of dpkg-divert.
* Update Vcs-Browser field due to Aloith changes.
* debian/rules: Upstream didn't tag 0.9.32 properly in vcs. Use specific
rev number instead of tag to generate debian/changelog.upstream
* Don't install dbus activation file (Closes: #640120).
- Drop Replaces on notification-daemon added in Ubuntu.
- Drop postrm script and modify preinst to remove obsolete diversion.
Checksums-Sha1:
5946c986c484e775715f25582c6dc2d0f23e3022 1507 notify-osd_0.9.32-1.dsc
bb402d8f7dabf1b981a2bbde17886ce9813b3c13 629967 notify-osd_0.9.32.orig.tar.gz
fff521e708dc629cdece77d7275520d7970763c5 17621 notify-osd_0.9.32-1.diff.gz
a99dc3c1795673bbb5292f60c4fdd7837d295182 182444 notify-osd_0.9.32-1_amd64.deb
Checksums-Sha256:
3a1b549e469f3628d859de6e5cf013b9fc78ef93b2f59e170724715174077434 1507
notify-osd_0.9.32-1.dsc
bb6cfaabce7efda886c84a7eb9c23a7aed9a555e01513b90569dd12fa23f8d6a 629967
notify-osd_0.9.32.orig.tar.gz
37791031beef2a48a167e03b76245dff88c3bc1f3a39f78da2c503bd09f832c3 17621
notify-osd_0.9.32-1.diff.gz
f57275565b45126a1a6a9423a1eff1aad557447bee9406b5d8f23206cda1028e 182444
notify-osd_0.9.32-1_amd64.deb
Files:
1e6ec602ab99c1828a7b8552add28156 1507 x11 optional notify-osd_0.9.32-1.dsc
1dbdda5cf15c1d1ca117649b23180d32 629967 x11 optional
notify-osd_0.9.32.orig.tar.gz
01b255b9ce126f7e25ae3a83ee97707c 17621 x11 optional notify-osd_0.9.32-1.diff.gz
2e4a29591a0139240409e3935504350b 182444 x11 optional
notify-osd_0.9.32-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk8n5jUACgkQJKAUGKwVtQyftgCcDqoE0h98qMdqXhrE4OH/bGhi
4k8AnikZ+7Pb3c5Gmwh9UrWNyRoHfXnc
=ErMh
-----END PGP SIGNATURE-----
--- End Message ---
