jrohwer

[root@blikbrein ~]# rpm -qa |grep bluez libbluez3-4.33-3mdv2009.1 lib64bluez3-4.33-3mdv2009.1 bluez-4.33-3mdv2009.1 bluez-firmware-1.2-5mdv2009.1

There is no group plugdev on my system. However, I tried adding myself to haldaemon and messagebus groups, but this did not solve the situation either. Also, I tried editing the file /etc/dbus-1/system.d/bluetooth.conf: Original file reads: <!-- This configuration file specifies the required security policies for Bluetooth core daemon to work. --> <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"> <busconfig> <!-- ../system.conf have denied everything, so we just punch some holes --> <policy user="root"> <allow own="org.bluez"/> <allow send_destination="org.bluez"/> <allow send_interface="org.bluez.Agent"/> </policy> <policy at_console="true"> <allow send_destination="org.bluez"/> </policy> <policy context="default"> <deny send_destination="org.bluez"/> </policy> </busconfig> I tried adding a block: <policy user="myusername"> <allow own="org.bluez"/> <allow send_destination="org.bluez"/> <allow send_interface="org.bluez.Agent"/> </policy> as well as changing the "deny" to "allow" in the last policy, but again this did not solve the issue (after restarting the messagebus service). Any further ideas?

I cannot connect Bluetooth input devices (mouse and keyboard) as a normal user on my Dell Latitude D630 (Mandriva 2009.1). In the KDE Bluetooth Device Manager, the devices get picked up and shown as "connected" but they do not respond. If I then move the mouse, the status switches between "connected" and "not connected" but the mouse does not respond (i.e. cursor is not moved). When I try to add the device manually as a normal user, I get the following: $ hidd --search Searching ... Connecting to device 00:07:61:63:77:CD HID create error 13 (Permission denied) So it does seem to find the device but there is a permissions problem in connecting. When I run the command as root: # hidd --search then everything works as expected and I can connect the devices. However, this is a pain because 1. the devices do not connect automatically on startup and I have to manually issue this command every time, 2. the devices don't reconnect automatically after a timeout. Any ideas which permissions to set? Everything worked perfectly under 2009.0 and this is really annoying me.... --johann

When I suspend to ram (either using kpowersave, or typing "pm-suspend") at the command line and start up my laptop again, cpufreq stops working. I have traced this back to the fact that the symlink /sys/devices/system/cpu/cpu1/cpufreq -> /sys/devices/system/cpu/cpu0/cpufreq which links the cpufreq settings for the 2 processors, has disappeared after the resume. I also cannot create this symlink by hand (I must admit that I have very little knowledge of how sysfs works). I can still manually change the cpufreq settings for cpu0 with e.g. # echo "performance" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor and it affects the clock frequency of cpu0, but for cpu1 it is disabled, and it also doesn't work with kpowersave (presumably because it can't access cpu1). Has anyone experienced similar things or got a fix for this? System: Dell Latitude D630 with Intel Core2Duo T7300 processor OS: Mandriva 2008.0 x86_64 architecture