Exaile on ubuntu should use libnotify by default

Bug #397210 reported by Green Dragon
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Exaile
Invalid
Low
Unassigned
exaile (Ubuntu)
Fix Released
Undecided
Andrew Starr-Bochicchio

Bug Description

Current Song, Next Song, etc should show up using Ubuntu's built-in area like volume control, networking manager, etc use.

Revision history for this message
reacocard (reacocard) wrote :

there is already a tray buttons plugin that does just that.

Changed in exaile:
status: New → Invalid
Revision history for this message
Green Dragon (great-wyrm-green-dragon) wrote :

But why not change the standard to use Ubuntu's tray notification message?

Revision history for this message
reacocard (reacocard) wrote :

> But why not change the standard to use Ubuntu's tray notification message?

1) that's a completely different thing from what you asked

2) Ubuntu is not the only distro out there

Revision history for this message
Steve Dodier-Lazaro (sidi) wrote : Re: [Bug 397210] Re: Current Song, Next Song, etc should show up using Ubuntu's built-in area like volume control, networking manager, etc use.

If you refer to indicator-applet, it has STRICTLY NOTHING to do with a music
player.

Revision history for this message
Green Dragon (great-wyrm-green-dragon) wrote : Re: Current Song, Next Song, etc should show up using Ubuntu's built-in area like volume control, networking manager, etc use.

The thing when one changes the volume on one's computer using the keyboard could be used for changing music as well, or not?

Revision history for this message
Steve Dodier-Lazaro (sidi) wrote : Re: [Bug 397210] Re: Current Song, Next Song, etc should show up using Ubuntu's built-in area like volume control, networking manager, etc use.

Could you please make the effort of explaining what you say, Green Dragon ?
I don't understand half of the things you ask before it's just too vague.
Please detail what you are speaking about.

Revision history for this message
reacocard (reacocard) wrote : Re: Current Song, Next Song, etc should show up using Ubuntu's built-in area like volume control, networking manager, etc use.

> The thing when one changes the volume on one's computer using the keyboard could be used for changing music as well, or not?

No, that OSD is part of gnome and we cannot link into it.

Revision history for this message
Green Dragon (great-wyrm-green-dragon) wrote :

Alright, I can use my keyboard to change the volume on my computer. I also have a media side to it where I can go from one song to another. Why is that not part of the gnome upper right hand corner area? Does Ubuntu just not allow it or have they not thought about it enough?

Revision history for this message
reacocard (reacocard) wrote :

> Why is that not part of the gnome upper right hand corner area?

Because there's no common spec for interacting with media players, among other things. There are third-party panel applets that allow this sort of control, you just have to look for them.

I'd like to ask that you read the following document before you continue harassing us with your bugs, it contains some important guidelines for bug submission that will greatly enhance the usefulness of your bugs (and reduce the aggravation of the project owners :P)

How to ask smart questions: http://catb.org/esr/faqs/smart-questions.html

Revision history for this message
Green Dragon (great-wyrm-green-dragon) wrote :

In all seriousness every user would notice it and like it. It's not a joke bug.

Also, not everyone is a developer ;), questions do not need to be asked in a developer style (in my opinion). I'm just a bugsubmitter (which we talked about in another bug).

Revision history for this message
Steve Dodier-Lazaro (sidi) wrote : Re: [Bug 397210] Re: Current Song, Next Song, etc should show up using Ubuntu's built-in area like volume control, networking manager, etc use.

No, you're not; You're someone who wants to submit bugs (or here more likely
feature requests) without willing to take the time to find the good words to
explain one's ideas. I still did not understand what you meant, and a
screenshot is more than welcome. Also, Exaile can be controlled via the
GNOME Multimedia Keys plugin, and there is another plugin directly making
use of the Multimedia keys. There also is a Command Line Interface so that
you can bind keys to the CLI calls and control your player this way. I
really don't see what's lacking.

Revision history for this message
Green Dragon (great-wyrm-green-dragon) wrote : Re: Current Song, Next Song, etc should show up using Ubuntu's built-in area like volume control, networking manager, etc use.

I don't mean the keys on ones keyboard (the functionality of those can be changed - like if one changes their keyboard to a dvorak virtual layout for example)

I mean when the next song starts playing why not have that OSD show up in the same way as if one changes the volue on their computer.

Revision history for this message
Steve Dodier-Lazaro (sidi) wrote :

This is called a notification and there are two plugins that do it : a generic one and a notify-osd specific one (notify-osd is the notification daemon in Ubuntu).

Changed in exaile:
status: Invalid → Fix Committed
Revision history for this message
Green Dragon (great-wyrm-green-dragon) wrote :

Is this going to be the standard or are people going to have to select it from the option menu?

Revision history for this message
szczym (szczym) wrote :

I confirm the bug and in my opinion its not fixed yet. (im beginer on launchpad, plase exuse me if im wrong).

Exile on ubuntu should use by default the _ubuntu`s built in notification system_
Osd from exile might be optional off course.

Changed in exaile:
status: Fix Committed → Confirmed
szczym (szczym)
summary: - Current Song, Next Song, etc should show up using Ubuntu's built-in area
- like volume control, networking manager, etc use.
+ Exile on ubuntu should use by default the ubuntu`s built in notification
+ system.
Revision history for this message
Adam Olsen (arolsen) wrote : Re: Exile on ubuntu should use by default the ubuntu`s built in notification system.

This is probably a packaging issue.

Since we cannot on the target system even having the notification daemon installed, we do not use it by default. In Exaile, we took special care to make sure that it'll run on any system that has gstreamer and gtk+ installed. Gnome is not required.

However, if a distro wants the notify-osd or notify plugins to be enabled by default, it's simply a matter of shipping a default settings file (settings.ini) that has the built in OSD disabled and one of those plugins enabled.

Perhaps the Ubuntu .deb on our website should include this? Unfortunately, this is all we can guarantee, since none of the upstream developers (synic, reacocard, sjohannes) package for any of the distros out there. This is up to them.

Changed in exaile:
importance: Undecided → Low
importance: Low → Wishlist
assignee: nobody → Adam Olsen (arolsen)
importance: Wishlist → Low
Revision history for this message
Green Dragon (great-wyrm-green-dragon) wrote :

Although this does not show up on my Rythmbox anymore I am pretty sure they added this when switching songs their. Although Rythmbox has more then a few security holes (or at least I think they are those).

Revision history for this message
Adam Olsen (arolsen) wrote : Re: Exaile on ubuntu should use notification-daemon by default

What does Rhythmbox's possible security holes have to do with Exaile using notification-daemon?

summary: - Exile on ubuntu should use by default the ubuntu`s built in notification
- system.
+ Exaile on ubuntu should use notification-daemon by default
Revision history for this message
Green Dragon (great-wyrm-green-dragon) wrote :

Nothing; they just annoy me a bit. Also, to be honest, they make it a bit unusable (that is why I changed to Exaile - personally).

Revision history for this message
Adam Olsen (arolsen) wrote :

Ah, I see. So Rhythmbox does, or does not use the notification-daemon?

Revision history for this message
reacocard (reacocard) wrote :

With exaile 0.3.0, distributors can ship a custom default config with exaile, allowing ubuntu (or any distro) to make exaile use libnotify or any other notification system as default. Thus this is purely a packaging issue, not an exaile issue.

Changed in exaile:
assignee: Adam Olsen (arolsen) → nobody
status: Confirmed → Invalid
Revision history for this message
reacocard (reacocard) wrote :

assigning to sidi in ubuntu, since he has previously expressed interest in making this happen for xubuntu.

Changed in exaile (Ubuntu):
assignee: nobody → Steve Dodier (sidi)
status: New → Confirmed
Revision history for this message
Steve Dodier-Lazaro (sidi) wrote :

Exaile has a built-in plugin for notification-daemon and one for notify-osd. As all official Ubuntu distros using libnotify will use notify-osd in Karmic, we will disable the OSD and install the notify-osd plugin in Xubuntu. The built-in OSD will remain enabled in Ubuntu as the notify-osd plugin will not be shipped in Exaile's trunk. The notify-osd plugin will be recommanded by Exaile, which means it will be installed when you install Exaile, but you will have to enable it yourself. We can not put it by default as it is a plugin.

summary: - Exaile on ubuntu should use notification-daemon by default
+ Exaile on ubuntu should use libnotify by default
Revision history for this message
szczym (szczym) wrote :

So, as far as i understand, that bug will be squished with karmic, yes ?

Changed in exaile (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
reacocard (reacocard) wrote :

> So, as far as i understand, that bug will be squished with karmic, yes ?

If the packagers do their job, yes. They need to adjust the default settings.ini to disable the OSD and enable the notifyosd plugin. However, 0.3.0 has not yet been packaged for Karmic, so who knows....

Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

Arrg.... Just realized that the karmic package missed both the notify and notify-osd plugins. I'll add them in a new upload once the current package clears the NEW queue.

Steve: Does Xubuntu want to enable notify-osd support enabled by default? I'll patch settings.ini if that's the case.

Changed in exaile (Ubuntu):
assignee: Steve Dodier (sidi) → Andrew Starr-Bochicchio (andrewsomething)
Revision history for this message
Johannes Sasongko (sjohannes) wrote : Re: [Bug 397210] Re: Exaile on ubuntu should use libnotify by default

> Steve: Does Xubuntu want to enable notify-osd support enabled by
> default? I'll patch settings.ini if that's the case.

Just a reminder, if you decide to enable any of the notify plugins by
default, don't forget to disable the built-in OSD as well.

Revision history for this message
Steve Dodier-Lazaro (sidi) wrote :

Andrew, you can do it on the Ubuntu package if you want, but we were
actually planning to use xubuntu-default-settings for that, so that other
users can have the default OSD by default.

Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

Unless upstream feels strongly that we shouldn't, I'd rather do this directly in the Exaile package so that Ubuntu (GNOME) users will also use Notify-OSD. The way I've done it now is that I'm recommending python-notify and only suggesting notify-osd. That way Ubuntu (GNOME) and Xubuntu user will use Notify-OSD as it will already be installed.

 If I'm reading the code right, the notifyosd plugin will fall back to using what ever the native implementation of the notification-dameon is. So we don't need to force users to install notify-osd. Is that correct? And of course, if the user want to use Exaile's OSD they can still enable it.

Revision history for this message
reacocard (reacocard) wrote :

I would not be opposed to enabling notify-osd as the default for ubuntu. As I understand it all official ubuntu variants use notify-osd, and users who do not use an official variant will almost certainly know how to adjust it to their needs, so this change should enhance the user experience without any significant side-effects.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package exaile - 0.3.0.1-0ubuntu3

---------------
exaile (0.3.0.1-0ubuntu3) karmic; urgency=low

  * debian/exaile.install: Install notify and notify-osd plugins.
  * debian/control:
   - Add Recommends on python-notify and Suggests on notify-osd.
   - Add python-imaging Depends for exaile-plugin-contextinfo.
  * debian/patches/10_notify-osd_by_default.patch: (LP: #397210)
   - Enable Notify-OSD plugin by default as Exaile is part of the
     default Xubuntu desktop.

 -- Andrew Starr-Bochicchio <email address hidden> Thu, 24 Sep 2009 21:50:22 -0400

Changed in exaile (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Christopher (soft-kristal) wrote :

Exaile Install and notify-osd plugins fails with this error

E: /var/cache/apt/archives/exaile_0.3.0.1-0ubuntu3_all.deb: trying to overwrite '/usr/share/exaile/plugins/notify/notify_cover.py', which is also in package exaile-plugin-notification-daemon 0

Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

On Sat, Sep 26, 2009 at 9:50 AM, Christopher <email address hidden> wrote:
> Exaile Install and notify-osd plugins fails with this error
>
> E: /var/cache/apt/archives/exaile_0.3.0.1-0ubuntu3_all.deb: trying to
> overwrite '/usr/share/exaile/plugins/notify/notify_cover.py', which is
> also in package exaile-plugin-notification-daemon 0

In a PPA version, that plugin was in a separate binary package. So the
packages conflict. Please remove the PPA version before upgrading.

Revision history for this message
actionparsnip (andrew-woodhead666) wrote :

sudo dpkg --force-all -i /var/cache/apt/archives/exaile_0.3.0.1-0ubuntu3_all.deb

Should do it, it will overwrite the file in both packages and not error :)

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

Other bug subscribers

Remote bug watches

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