Bug 440935 - bluetooth properties: power switch toggle buttons always insensitive
Summary: bluetooth properties: power switch toggle buttons always insensitive
Status: RESOLVED NORESPONSE
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Factory
Hardware: Other Other
: P3 - Medium : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 441550
  Show dependency tree / graph
 
Reported: 2008-11-03 03:24 UTC by Vincent Untz
Modified: 2011-04-02 18:14 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Screenshot (24.76 KB, image/png)
2008-11-04 21:49 UTC, Vincent Untz 		Details
lshal output (141.07 KB, text/plain)
2008-11-04 21:50 UTC, Vincent Untz 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Untz 2008-11-03 03:24:12 UTC 
Thanks to bug 422194, we now have a way to disable bluetooth in bluetooth-properties: there is a toggle button for power switch. However, this toggle button is always insensitive, so it's quite useless.

Also, I'm wondering if it's planned to add this to the context menu of the tray icon.
Comment 1 JP Rosevear 2008-11-04 21:49:49 UTC 
The button will never sensitize if the following call:

	message = dbus_message_new_method_call("org.freedesktop.Hal", udi,
				"org.freedesktop.Hal.Device.KillSwitch",
								"GetPower");

fails to return something other than 0.

Gathering lshal output.
Comment 2 Vincent Untz 2008-11-04 21:49:51 UTC 
Created attachment 249794 [details]
Screenshot
Comment 3 Vincent Untz 2008-11-04 21:50:12 UTC 
Created attachment 249795 [details]
lshal output
Comment 4 JP Rosevear 2008-11-04 21:53:20 UTC 
Danny, Seife should hal be returning a value here?
Comment 5 Danny Al-Gaaf 2008-11-05 12:30:15 UTC 
If you call a non existing interface, as it looks to me in this case, you get always 0 and a dbus_error
Comment 6 Larry Finger 2011-04-02 18:14:26 UTC 
The version with which you had the bug is now obsolete. I'll close this as NORESPONSE. If you can still reproduce it in current 11.4, please reopen the bug and move it to the appropriate version. Thanks!