sound-indicator still shows Rhythmbox even though I did "sudo aptitude remove rhythmbox"

[Colin Keenan]

Binary package hint: indicator-sound

I like Banshee better, so I uninstalled Rhythmbox (sudo aptitude remove rhythmbox). Even after re-boot, I still see Rythmbox listed as an option in the drop-down menu from the sound icon in the indicator applet. If I click on Rhythmbox from the sound indicator menu, nothing happens, of course.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: indicator-sound 0.6.5.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.38-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Thu Mar 24 15:32:52 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: indicator-sound
UpgradeStatus: Upgraded to natty on 2011-03-23 (1 days ago)
indicator-applet-session.log:
 Binding '<Super>S' failed!

 Using user icon for 'Guest Session' from file: (null)
 g_variant_get_string: assertion `value != NULL' failed
indicator-applet.log:
 Looking at Module: libapplication.so
 Connected to Application Indicator Service.
 new_application_item ("Set Up Chat...")

[Colin Keenan (colinkeenan)]

This bug went away after the latest sudo aptitude full-upgrade. Or else, it went away when I finally stopped using gnome-panel for the notification area applet.

I kept using a gnome-panel for notification area for gnote and checkgmail until I finally discovered how to make them show up in the indicator applet (i.e. Unity Panel Systray):

1. gsettings get com.canonical.Unity.Panel systray-whitelist

to find out what apps are already allowed in the indicator applet, then

2. gsettings set com.canonical.Unity.Panel systray-whitelist "COPY AND PASTE THE OUTPUT FROM 1. THEN ADD NEW APPS TO IT"

So, to get gnote and checkgmail to show up in systray, the command I used for step 2. was

gsettings set com.canonical.Unity.Panel systray-whitelist ['JavaEmbeddedFrame', 'Mumble', 'Wine', 'Skype', 'Checkgmail', 'Gnote']

[Conor Curran (cjcurran)]

Hi,

Thanks for reporting this.

I can't reproduce the issue. By removing rhythmbox that would mean the desktop file for the application should also be removed. The menu will not 'load' any player from its whitelist if it cannot properly create an GAppInfo instance from the desktop file. Maybe for some reason the desktop file was left lying around. Is it alright to close this bug ?

Conor

[Colin Keenan (colinkeenan)]

OK - it probably was the launcher which I did eventually find in ~/.local/share/applications when doing a backup of that folder. I guess that's what fixed it, not the latest upgrade or removal of gnome-panel.

You can close this bug, I guess, but most people won't know to look in ~/.local/share/applications for a desktop file to delete. That should be done automatically when removing the application. I also deleted a lot of other launchers from stuff I had removed. Could be those launchers are ones I created or that had something to do with the old menu system. I don't know, but they need to be automatically cleaned up somehow since you wouldn't expect the average user to even realize there is a .local directory in the first place.

[Conor Curran (cjcurran)]

ah point taken Colin.
Will keep this on my radar.

Thanks for the detailed feedback !

[Conor Curran (cjcurran)]

Hi Colin,

Package uninstall scripts generally don't touch anything in a user dir.

How did this desktop file get placed in that local directory ?

Conor

[Colin Keenan (colinkeenan)]

I can't be sure, but it could be that the "Startup Applications" program creates launchers in that directory when adding new stuff to the list. Seems like most of the stuff in there is stuff I had at one time or another added to the Startup Applications. Even though Rhythmbox was in indicator-volume all the time, it took a while to start the first time, so I added it to the Startup Applications.

I'll test that theory out now because I didn't do that for Banshee and it's not yet in the ~/.local/... directory.

Well, adding it to Startup Applications didn't put it there. Unless I have to log off and back on. I'll try that now.

[Colin Keenan (colinkeenan)]

No, it's not from Startup Applications.

Maybe it's from adding stuff to the old menu system. I'll start a gnome-panel, add the menus, and add Banshee to someplace it wasn't before, and see if that works.

That's it! I added Banshee directly to the "Applications" menu even though it was already in "Applications -> Sound and Video" or whatever, and now there is a "Banshee" desktop file in ~/.local/...

And, now I've deleted it. So, that's why only some people will have that local launcher while most won't.

[Conor Curran (cjcurran)]

Hi Colin,

Thanks for the feedback. It seems as if this is a particular situation, one which others should not generally experience.
Marking invalid.

Conor

[Colin Keenan (colinkeenan)]

Is there an application that does a search and destroy on launcher files that are trying to launch applications no longer on the system?

[OneStyle07 (damir-o-s-07)]

If someone still has this bug after removing the player do this :
install dconf editor,open it,go to com->canonical->indicator->sound and in interested-media-players remove the player you don't need and add the one you need (for me i use 2 of them so now it's ['beatbox','banshee'] )

[Daniel Dietrich (shaddowy2)]

I had the same problem with Precise Beta 2. I want to add, even "sudo apt-get purge rhythmbox" wouldn't delete those desktop files.
I have found the reason why they were created, at least in my case: I edited some menu entries with the program "alacarte", so for example I hid Rhythmbox as I didn't want it to show up in Unity. With the de-installation of the music player those files weren't deleted. Even deleting the menu entry inside Alacarte, where I created/modified it, didn't delete the entry at .local/share/applications. So Alacarte is to blame here. I think I found the corresponding bug report for it: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/340285 There is even a patch attached to solve the problem.
I can't recommend the use of Alacarte any more after watching its bug tracker :(