Hello

I am using KDE 4.1.3 "release 69.3" and a Logitech MX 1000 Mouse. The mouse is working but I can not access futher data like batterie amount.

In the systemsetting from KDE I am told that libusb was found but that I can not access the data form the mouse, there might be a user rights problem.

Can someone imagine where I can check the user rights - which file is ment?

THanks a lot
Michale

Linux does not support accessing this data due to the proprietary protocol used to access it, according to here http://www.linux.com/feature/46017

Actually cancel the above: apparently support must have been implemented after that review was done, otherwise this bug could never have been filed: https://bugzilla.redhat.com/show_bug.cgi?id=183127

I would recommend filing a feature request in the KDE bug tracker, asking for support for showing the charge level of mouses that support the feature.

In the meantime, you could probably write a script that would retrieve the value for you, and show it on your desktop using the Command Monitor.

Thanks

for the update, I am unsure if I really should write a feature request since the KDE error message already points out that there might only some false user rights which prevent the access.
The question would be which right are expected for which file? Is there a possibility to run this in a debug mode to find out which file it might be? Could I use strace?

Thanks a lot
Michael

PS I have removed the SOLVED

For the time being, can you try starting systemsettings (or the concerned app) as root (sudo/kdesudo/kdesu) from konsole and see if it works.

The settings in question would be with regard to interacting with HAL, which is on the System Message Bus. Thus we would be looking into querying what D-Bus security mechanisms need to be altered. I do not know if starting system settings as root will have an effect, but D-Bus will probably log an "Access Denied" message somewhere...

Hello,

LinuxIsInnovation wrote:For the time being, can you try starting systemsettings (or the concerned app) as root (sudo/kdesudo/kdesu) from konsole and see if it works.

I have started the systemsettings as root and voila I see the battery charge status, what I can not as normal user. I have checked the file at /var/log/* for hints but found non. Also the strace does not help since the console output stops when the systemsettings menu is displayed.

So the question is now which file needs to be changed?

THanks a lot
Mihcael

The file /etc/dbus-1/system.d/hal.conf is what probably governs access. If we can find out what it is trying to access then we can grant it the needed permissions.

Hello,

bcooksley wrote:The file /etc/dbus-1/system.d/hal.conf is what probably governs access. If we can find out what it is trying to access then we can grant it the needed permissions.

I will check at first the current rights of the file, but I have no clue how to check starting from the file who is acessing it.
On the other hand I did not find a usabel documentation which tells me how to start the mouse and keyboard module directly something like
"systemsettings -TAG mouse". I want to do this since the start of systemsettings without any parameter passes the control to an other processe and gives the console free so that there is only the output from the start is visible but not this what happens when I klick on the mouse and keyboardmodule.

Michael

I read the code that handles Logitech Mouses ( located at http://websvn.kde.org:80/trunk/KDE/kdeb ... hmouse.cpp ) and it appears that it interfaces with the device over libusb directly.

Try adding your user into the 'plugdev' group and logging out + log back in then re-test.
If that doesn't work then we will need to alter a udev configuration file.

Thx, will do so.
will not be at my pc with in the next 10 hours, sorry.
Michael

bcooksley wrote:Try adding your user into the 'plugdev' group and logging out + log back in then re-test.

Hello,

there is no group plugdev a all with the openSUSE 11.0..... What can I do?
I have not see anything else in the code.

bcooksley wrote:Try adding your user into the 'plugdev' group and logging out + log back in then re-test.
If that doesn't work then we will need to alter a udev configuration file.

Damn... forgot 'plugdev' exists in Debian, not anywhere else.

Try creating the file "99-evdev.rules in /etc/udev/rules.d/ with this

Code: Select all

KERNEL="mouse*", BUS="usb", SYSFS{product}=="USB Receiver", SYSFS{manufacturer}=="Logitech", MODE="0664", GROUP="users", OWNER="root", NAME="input/mouse2"

You will need to restart udev for this to come into effect. Note that I am not sure if it will work. Do you use the "evdev" driver in /etc/X11/xorg.conf? If you do, change the "NAME" item to reflect the device entry in xorg.conf ( less "/dev/" )
( Example /dev/input/mouse1 -> input/mouse1 )

Hello,

unfortunately the udev.rules is not working. Since in my xorg.conf is "evdev" not mentioned at all I guess that I do not use it

Here is the section for my mouse from the xorg.conf. The MX310 is the only Model which works with my MX1000, Strange it is a cordless mouse and the cradle is connected via USB but the conf file is generted with PS2. How every it works.

Code: Select all

Section "InputDevice"
  Driver       "mouse"
  Identifier   "Mouse[1]"
  Option       "Buttons" "5"
  Option       "Device" "/dev/input/mice"
  Option       "Name" "MX310"
  Option       "Protocol" "ExplorerPS/2"
  Option       "Vendor" "Logitech"
  Option       "ZAxisMapping" "4 5"
EndSection

So when I log in as root I can see the batterie status but I can not change the resolution from 400 to 800 cpi...

-bushveld

Could you try with this: ( file is /etc/udev/rules.d/99-logitech.rules )

Code: Select all

KERNEL="mouse*", BUS="usb", SYSFS{manufacturer}=="Logitech", MODE="0664", GROUP="users", OWNER="root", NAME="input/mice"

Make sure to restart the udev service after making this change ( "service udev restart" as root )