lomoco udev rule not working

Bug #214226 reported by Bismark
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
lomoco (Ubuntu)
Fix Released
Medium
Unassigned
Nominated for Karmic by Søren Holm

Bug Description

Binary package hint: lomoco

When a mouse supported by lomoco (listed in /etc/udev/lomoco.rules) is detected it is suppose to run /lib/udev/udev.lomoco using the settings in /etc/default/lomoco.

My mouse is listed in lomoco.rules but when I unplug and plug it back in the rule does not fire.

I have to manually run lomoco to get it to set the resolution on my mouse properly.

$ lsb_release -rd
Description: Ubuntu hardy (development branch)
Release: 8.04

$ apt-cache policy lomoco
lomoco:
  Installed: 1.0beta1+1.0-5
  Candidate: 1.0beta1+1.0-5
  Version table:
 *** 1.0beta1+1.0-5 0
        500 http://us.archive.ubuntu.com hardy/universe Packages
        100 /var/lib/dpkg/status

Related branches

Revision history for this message
Jan Vlnas (jnv) wrote :

I can confirm this bug both on Gutsy and Hardy with Logitech MX510.
I've edited /etc/default/lomoco to use 800cp resolution (LOGITECH_MOUSE_RESOLUTION=800) but it is not set during startup.
There is possible workaround - see http://ubuntuforums.org/showthread.php?t=219894 - section 3 (add init.d rule to set up resolution on boot), but this won't set the resolution on hotplugging and resuming from suspend/hibernation.

Revision history for this message
Kjell Braden (afflux) wrote :

Confirmed. This is because of:

1.) /etc/udev/rules.d/025-lomoco.rules is named incorrectly, should be only two digits.
2.) /etc/udev/lomoco.rules seems to check for the wrong subsystem: changing to usb_endpoint fixed it for me.

will check wether it affects debian too.

Changed in lomoco:
importance: Undecided → Medium
status: New → Confirmed
status: Confirmed → Triaged
Revision history for this message
Darren Warner (launchpad-dazwin) wrote :

Confirmed in intrepid beta 1 using a Logitech MX310

I worked around it by commenting out the SUBSYSTEM != "usb_device" line at the top of /etc/udev/lomoco.rules

A few other points:

- According to /etc/udev/rules.d/README, files in this directory should not be symlinks.
- The README seems to indicate that the rule should be run at 80, not 25 (I'm certainly no udev expert though).

Revision history for this message
Sergei (msergei) wrote :

I can confirm this bug in K/Ubuntu 8.10.

These two steps made it to work again for me.

1. Running
cp /etc/udev/lomoco.rules lomoco.rules /etc/udev/rules.d/80-lomoco.rules
2. Editing to usb_device to usb_endpoint

This must be fixed as an update to 8.04 and 8.10!!!

Revision history for this message
UbuntuCleric (ubuntucleric) wrote :

Hi:

I also stumbled across this problem, but I fixed it in a slightly different way: I changed the "SUBSYSTEM != usb_device" to "ATTR{name} == Logitech USB-PS/2 Optical Mouse". How did you people know to change it to usb_endpoint? Using udevinfo, I get "SUBSYSTEM == input". I'm pretty confident I'm looking at the right entry because the ATTR{name} match works, and it is unique to that entry. Any help appreciated.

Cheers,
UbuntuCleric

Revision history for this message
Xavier (chantry-xavier) wrote :

I confirm this bug with package 1.0beta1+1.0-5 (up-to-date 8.10) and that the suggested workaround from Sergei works.
Any chances to get this applied?

Revision history for this message
Jan Vlnas (jnv) wrote :

In Ubuntu 9.04 rules file was correctly moved to /lib/udev/rules.d/40-lomoco.rules
But the problem still remains, my MX510 mouse resolution is not set on the system startup (with edited settings in /etc/default/lomoco). As far as I have tested, it seems that udev.lomoco script doesn't get executed. Therefore I think that bug exitsts in 40-lomoco.rules file.

This happens on freshly installed Ubuntu Jaunty, package lomoco from universe: 1.0beta1+1.0-5ubuntu1.

Shall I reopen this bug, report new one or is it only my problem?

Revision history for this message
Jan Vlnas (jnv) wrote :

Previously mentioned fix with "usb_endpoint" is a solution to this bug.
I've attached a patch which directly changes /lib/udev/rules.d/40-lomoco.rules file.

The rule actually causes lomoco to run twice when the device is connected, but it's still better than nothing.

I guess there is one more problem with udev rule, see bug #382229 I have just reported.

Revision history for this message
robled (robled) wrote :

I'm curious as to how you guys even have any udev entries for lomoco. I've just installed it on 9.04, but when I search the /etc directory for lomoco all I get is the defaut config file:

#find /etc -name lomoco
/etc/default/lomoco

Revision history for this message
Jan Vlnas (jnv) wrote :

NTolerance, lomoco rules are placed in /lib/udev/rules.d/ - although you are right it shouldn't be that way. Package supplied rules should go to the /etc/udev/rules.d/. This is yet another (although minor) bug in lomoco package.

Revision history for this message
Cybjit (cybjit) wrote :

I did not get the any of the fixes to work in karmic. I had to make changes to both
/lib/udev/udev.lomoco
/lib/udev/rules.d/40-lomoco.rules
to make it work.

Revision history for this message
Cybjit (cybjit) wrote :
Revision history for this message
Cybjit (cybjit) wrote :

Here is a patch against the package build instead.

Revision history for this message
B. Clausius (barcc) wrote :

Here is a debdiff based on Cybjit's patch.
If someone wants to test it, look in my ppa:
https://launchpad.net/~barcc/+archive/lomoco

Revision history for this message
Søren Holm (sgh) wrote :

Confirmed ..... The attached files works great for me. Please push the changes into karmic.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lomoco - 1.0beta1+1.0-5ubuntu3

---------------
lomoco (1.0beta1+1.0-5ubuntu3) karmic; urgency=low

  * udev/toudev.awk, udev/udev.lomoco:
    Make udev rule working (LP: #214226)

 -- <email address hidden> (B. Clausius) Thu, 08 Oct 2009 20:31:28 +0200

Changed in lomoco (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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