Don't run bluetooth applet when no bluetooth hardware is present

Bug #272150 reported by Wouter Stomp
6
Affects Status Importance Assigned to Milestone
bluez-gnome (Ubuntu)
Invalid
Wishlist
Unassigned
gnome-bluetooth (Ubuntu)
Invalid
Undecided
Unassigned
hal (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gnome-bluetooth

Bluetooth applet is always started in ubuntu and uses about 1,6mb of memory on my system. This happens even though I have absolutely no bluetooth hardware in my system. Ubuntu should easily be able to detect if bluetooth hardware is present on the computer and only start the bluetooth applet in these cases.

Revision history for this message
mmomjian (matthew-momjian) wrote :

I think you can remove it from Preferences > Sessions. You suggest that ubuntu "should easily be able to detect if bluetooth hardware is present", but that IS the function of what you are reporting. The computer can't tell if bluetooth hardware is present unless it's running a small daemon; 1.6MB is really not that much. If you want no automatic bluetooth support, you can disable it.

Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :

I know you can remove it yourself, and I do want automatic bluetooth support, but the point is that it should not be run by default without purpose. The applet is not needed to detect the hardware, there are lower level mechanisms which are already running for this such as hal. And saving 1,6mb is definitely worth saving when you are running ubuntu on computers with little memory, e.g. 256mb.

Revision history for this message
Mario Limonciello (superm1) wrote :

The idea is supposed to be that you have the applet running though in the event that you actually do hook up say a USB bluetooth dongle. You can't exactly spawn a userspace applet with HAL, can you?

Changed in gnome-bluetooth:
status: New → Invalid
Changed in bluez-gnome:
importance: Undecided → Wishlist
status: New → Incomplete
Revision history for this message
Neil Perry (nperry) wrote :

This bug is still marked as Incomplete so we are now going to close this bug report. Please upgrade to the latest release Karmic 9.10 - If this bug is still reproducible please reopen the bug by setting the status to New. Thanks

Changed in bluez-gnome (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
dino99 (9d9) wrote :
Changed in hal (Ubuntu):
status: New → Incomplete
status: Incomplete → Invalid
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.