Settings for Logitech Optical Trackman unavailable

Bug #94597 reported by Jakub Turski
48
This bug affects 4 people
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: kde-systemsettings

In mouse settings, I see a tab for 'Cordless Optical Trackman' - which is the trackball I'm using. However, the settings are grayed out, and below I see the following message:

"You have a Logitech Mouse connected, and libusb was found at compile time, but it was not possible to access this mouse. This is probably caused by a permissions problem - you should consult the manual on how to fix this."

Problem is, it doesn't specify *which* device's permissions or *which* manual should we consult :) I tried to strace the application, and found that it's trying to get to /dev/bus/usb/* files. Still, I believe it should be configured by default (best :) or at least the message should be more explanatory...

Regards,

KT.

Revision history for this message
buntu_hugenewbie11 (dwozniak) wrote :

I have the same problem using ubuntu Feisty and KDE. Weird part is it seems to have just recently occurrred as my mouse was working fine last week so it might be an update I put on.

Revision history for this message
M Bianciotto (marco-bianciotto) wrote :

The problem is still there in Gutsy, (with the MX1000 mouse) and the workaround explained in help:/kcontrol/mouse/index.html is no more appropriate because it refers to hotplug and not to udev.
It would be really helpful to give an hint on what file(s) the permission problem is, to ease debugging.

Thanks,

Marco

Changed in kde-systemsettings:
status: New → Confirmed
Revision history for this message
Adam Spain (adamspain) wrote :

Changing bug to be against kdebase as the mouse applet seems to be part of the kcontrol binary package.

Revision history for this message
Adam Spain (adamspain) wrote :

They seem to have had the same problem in openSUSE, but it seems they closed the bug without really fixing it:

https://bugzilla.novell.com/show_bug.cgi?id=223868

Revision history for this message
Raumkraut (raumkraut) wrote :

The issue seems to stem from changes made, way back when, to how udev parses it's .rules files. The effect of this is that the /etc/udev/logitechmouse.rules file supplied with Ubuntu (including Hardy) is basically ignored by udev.
Attached is my modification to said file (as supplied by Hardy), which sets the group for the relevant node within /dev/bus/usb/ to plugdev. Replacing the ubuntu-supplied file, doing `sudo udevcontrol reload_rules`, and re-plugging your mouse should activate it.

With this all in place I can now use logitech_applet (it's in the repos) to view and set the resolution, etc as a normal user.
*However* there still seems to be a bug in the admin interface, as changing the resolution of the mouse works only once. After applying a new resolution, the same error message as originally encountered appears and any further attempts to apply changes seem to have no effect. Closing and reopening the settings window resets the behaviour, allowing another - single - alteration.

Revision history for this message
Raumkraut (raumkraut) wrote :

Additionally, whatever changes you make in the mouse settings interface don't seem to survive a reboot (I've just checked).
Instead, you need to tell udev to set the resolution, etc, every time a logitech device is detected. What I have done is install logitech_applet (as mentioned before), and use something like the following in the logitechmouse.rules file (this one is the line for the MX510):

SYSFS{idProduct}=="c01d", SYSFS{idVendor}=="046d", MODE="660", GROUP="plugdev", RUN+="/usr/bin/logitech_applet -e -s 800"

`logitech_applet -h` to list available options.

Thomas Weissel (xapient)
Changed in kdebase:
assignee: nobody → xapient
Revision history for this message
drakesoft (powerschorsch21) wrote :

I have still the same Problem at kubuntu amd64 alpha3 9.05 [jaunty]

Revision history for this message
Daniel Sandlian (sandliman) wrote :

I can confirm that it is still a problem on Kubuntu 64 Jaunty Beta.

Bus 005 Device 002: ID 046d:c508 Logitech, Inc. Cordless Trackball

[ 7.037030] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.0/input/input4
[ 7.060122] generic-usb 0003:046D:C508.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:1d.0-2/input0

Any other info needed?

Revision history for this message
Jonathan Kolberg (bulldog98) wrote :

I can confirm this bug in karmic and lucid

Revision history for this message
Jonathan Kolberg (bulldog98) wrote :

the patch still works, but it should be saved as /lib/udev/rules.d/95-logitechmouse.rules

Revision history for this message
Harald Sitter (apachelogger) wrote :

I do believe upstream might want to distribute a udev rule, this certainly affects more distros than just Ubuntu.

affects: kdebase-workspace (Ubuntu) → kde-workspace (Ubuntu)
Changed in kde-workspace (Ubuntu):
assignee: xapient (xapient) → nobody
importance: Undecided → Low
Revision history for this message
Peter Antoniac (pan1nx) wrote :

The patch should be more inline with the new udev. I have it like this:

Revision history for this message
Peter Antoniac (pan1nx) wrote :

Ah, and another one, you reload the rules with:

sudo udevadm control --reload-rules

Hope this helps...

Revision history for this message
Rohan Garg (rohangarg) wrote :

Reassigning to udev since the rules file should be distributed by udev.

affects: kde-workspace (Ubuntu) → udev (Ubuntu)
Changed in udev (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.