[hardy] /dev missing some entries, others have wrong permissions

Bug #180169 reported by Rob Hughes
4
Affects Status Importance Assigned to Milestone
sane-backends-extras (Debian)
Fix Released
Unknown
sane-backends-extras (Ubuntu)
Fix Released
High
Luca Falavigna
udev (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: udev

After a dist-upgrade, i'm see the same as in this thread:

http://ubuntuforums.org/showthread.php?t=613758

I searched, but couldn't find a bug report. As of now, I can't start X due to a missing /dev/input/*, I have no sound, since the /dev/snd/* entries are missing. There's probably other things missing as well. I tried reverting to an old kernel where everything worked, but that made no difference. Installed version of udev is 117-3.

Revision history for this message
oh (oystein-homelien) wrote :

I confirm 660 permissions on /dev/{null,zero} and lots of other devices which should be accessible by my user. Also /dev/input/mice is gone and i needed to symlink it. This happened about a week ago after dist-upgrade from gutsy. This is a killer bug and I still haven't found the solution.

Changed in udev:
status: New → Confirmed
Revision history for this message
oh (oystein-homelien) wrote :

After reading this thread http://ubuntuforums.org/showthread.php?t=613758&page=2, the problem was solved for me. I suspect removing libsane-extras (and its according udev rules file) was the fix. I am not 100% sure though, as I did apt-get update just before rebooting now since I did not have time to look more closely into this. Also, removing libsane-extras using "apt-get remove" did not work, so I had to use dpkg --purge. FYI, YMMV.

Revision history for this message
Rob Hughes (rob-robhughes) wrote :

Yep, looks like this whole mess is being caused by problems with libsane-extras.

Revision history for this message
Rob Hughes (rob-robhughes) wrote :

There, I changed the package name to match the true source of the problem.

Revision history for this message
Isma (isma-af) wrote :

I was having the same problem since I upgraded to hardy.
By purging libsane-extras everything works fine again, thank you. XD

Revision history for this message
Emanuel Steen (kozz) wrote :

I added a link to the debian bug for this issue. It is solved in version 1.0.18.14 in Debian.

The problem is that the udev rule uses the wrong name for a LABEL which makes the system unusable after installation of libsane-extras. This is serious since installing a package (even if is it from the universe respository) should not stop your system from booting.

Is it possible to sync with that Debian version, with regards to the feature freeze I mean? Or should I make a debdiff that only fixes this specific bug. Would be nice to have the fix before release of Hardy.

Changed in sane-backends-extras:
status: New → Confirmed
Changed in udev:
status: Confirmed → Invalid
Changed in sane-backends-extras:
status: Unknown → Fix Released
Revision history for this message
Emanuel Steen (kozz) wrote :

Attached a debdiff that fixes the problem. Only fixes the labels in the udev rules but should be an ok fix for Hardy to make the package not break the system :)

Revision history for this message
Luca Falavigna (dktrkranz) wrote :

Uploaded, thanks ;)
I switched Maintainer field according to https://wiki.ubuntu.com/DebianMaintainerField and used LP: #180169 notation to close this bug automatically.

Changed in sane-backends-extras:
assignee: nobody → dktrkranz
importance: Undecided → High
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sane-backends-extras - 1.0.18.12ubuntu1

---------------
sane-backends-extras (1.0.18.12ubuntu1) hardy; urgency=low

  [ Emanuel Steen ]
  * Fix labels in the udev rules (LP: #180169).

  [ Luca Falavigna ]
  * debian/control: update Maintainer field as per spec.

 -- Emanuel Steen <email address hidden> Tue, 18 Mar 2008 21:27:31 +0100

Changed in sane-backends-extras:
status: Fix Committed → 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.