https://bugzilla.novell.com/show_bug.cgi?id=632256 https://bugzilla.novell.com/show_bug.cgi?id=632256#c2 --- Comment #2 from Ginko Bonsai 2010-08-19 08:50:05 UTC --- If I run bluetooth-applet as root, I get: # bluetooth-applet ** Message: adding killswitch idx 1 state 0 ** Message: killswitch 1 is 0 ** Message: killswitches state 0 ** Message: killswitch 1 is 0 ** Message: killswitches state 0 GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) libnotify-Message: Unable to get session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. The applet then starts (and looks normal) and I can switch on and off bluetooth as expected. When I switch on bluetooth, a second applet running as my normal user appears in the task bar - probably the one started per default at system startup. However, I thought that the applet should normally run with normal user privileges. Also, when I lend my laptop to somebody, I don't want to give them root access just so they can turn bluetooth on and off...? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=632256 https://bugzilla.novell.com/show_bug.cgi?id=632256#c4 Kay Sievers changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |kasievers@novell.com InfoProvider|kasievers@novell.com | --- Comment #4 from Kay Sievers 2010-09-06 11:00:51 UTC --- Other distros ship a rule to grant user access to the killswitch device, like: KERNEL=="rfkill", TAG+="udev-acl" Some people don't like this approach, but there is currently no proper way to solve this problem. People think about a new D-Bus service to manage this, but nothing like this is currently implemented. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=632256 https://bugzilla.novell.com/show_bug.cgi?id=632256#c6 Kay Sievers changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|kasievers@novell.com | --- Comment #6 from Kay Sievers 2010-09-06 11:37:22 UTC --- I think it's ok because of the lack of real alternatives at the moment. We should probably just include a comment in the rules file, that states, that it's planned to replace this with a properly managed system service. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.