banshee does not honour "actions" capability of notification daemon (was: annoying messages with banshee)

Bug #332806 reported by Oleksij Rempel
10
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Triaged
High
Unassigned

Bug Description

Seems like with new notification deamon, bashee do not work properly. Normaly after new song will come notification about new titel and timer, so this notification will disapera after five seconds. With new notification system it will show a lot of new notifications, and they will newer disapear.

lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04

apt-cache policy notify-osd
notify-osd:
  Installiert: 0.8-0ubuntu3
  Kandidat: 0.8-0ubuntu3
  Versions-Tabelle:
 *** 0.8-0ubuntu3 0
        500 http://de.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
Oleksij Rempel (olerem) wrote :
Revision history for this message
Alexander Sack (asac) wrote :

oops. thought this was about "song" notifications being displayed too late (async) and wondered whether that should be done synchronous instead (<= mpt).

In fact this is just an application bug not honouring actions capabilities of notification daemon. Since you said banshee, I am moving it there and tagging dxteam

Changed in notify-osd:
importance: Undecided → High
status: New → Triaged
description: updated
Revision history for this message
Michael B. Trausch (mtrausch) wrote :

It looks to me like Banshee *is* aware of the notifications and displaying a window to the user instead of popping up a useless notification using the notifications system. The notification is there to enable the user to quickly skip the current item, as well as notify them what the current item *is*.

If, like me, you *want* the old system in your session you can:

  killall notify-osd
  /usr/lib/notification-daemon/notification-daemon & disown

And you'll be running the trusty and more functional older utility instead. Get that into your GNOME/desktop environment autostart properties somehow or another in a script or whatever, and you're set.

Revision history for this message
Michael B. Trausch (mtrausch) wrote :

Oh, nevermind. notify-osd comes back to life periodically or something. sudo apt-get --purge remove the thing.

And would someone *please* remove notify-osd from the Ubuntu Desktop metapackage. That's just insane. Install it by default if you please, but do NOT make my system depend on it, please and thank you.

Revision history for this message
Chow Loong Jin (hyperair) wrote : Re: [Bug 332806] Re: banshee does not honour "actions" capability of notification daemon (was: annoying messages with banshee)

On Mon, 2009-02-23 at 08:36 +0000, Michael B. Trausch wrote:
> Oh, nevermind. notify-osd comes back to life periodically or something.
> sudo apt-get --purge remove the thing.
>
I think you'd probably want to modify one of the D-Bus files. I know
notification-daemon is auto-started by one of those files
-- /usr/share/dbus-1/services/org.freedesktop.Notifications.service to
be exact. By modifying that file to start notification-daemon instead of
notify-osd I think you could get back the old behaviour.

> And would someone *please* remove notify-osd from the Ubuntu Desktop
> metapackage. That's just insane. Install it by default if you please,
> but do NOT make my system depend on it, please and thank you.
Perhaps it would be better to have it in recommends rather than depends.
Or maybe make them both provide a metapackage, and then allow you to
choose which one you want through some debconf magic or whatever.

--
Chow Loong Jin

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.