Bug 144444 - libusbscanner - setup for a "cold plugged" scanner
libusbscanner - setup for a "cold plugged" scanner
Product: Fedora
Classification: Fedora
Component: sane-backends (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nils Philippsen
Depends On:
  Show dependency treegraph
Reported: 2005-01-06 21:44 EST by Michal Jaegermann
Modified: 2007-11-30 17:10 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-06-07 09:07:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
proposed patch to fix "no-one seems to know how" case (1.58 KB, patch)
2005-01-06 21:45 EST, Michal Jaegermann
no flags Details | Diff

  None (edit)
Description Michal Jaegermann 2005-01-06 21:44:15 EST
Description of problem:

A comment in /etc/hotplug/usb/libusbscanner says

    # If the scanner is "cold plugged," this event will likely occur 
    # before the root filesystem is writeable, but no-one seems to
    # know how to fix that.

What about the attached patch?  It seems to work for me just fine.
OTOH this may be only important when nobody is actually logged on
a console but a scanner can be used by remote logins.  Not a "normal"
situation but not unheard of either.  After a console login
pam reapplies permission given in /etc/security/console.perms
with a link which already exists.

Version-Relesase number of selected component (if applicable):
Comment 1 Michal Jaegermann 2005-01-06 21:45:40 EST
Created attachment 109454 [details]
proposed patch to fix "no-one seems to know how" case
Comment 2 Sitsofe Wheeler 2005-01-07 04:15:08 EST
This sounds related to bug #142727
Comment 3 Nils Philippsen 2006-04-05 10:15:19 EDT
"Long, long time ago..."

sane-backends-1.0.17-0.fc4.2 which includes your patch (thanks!) is building
right now and should hit FC4 updates-testing shortly.

Note You need to log in before you can comment on or make changes to this bug.