Bug 244762 - Parallel Port Scanner not found
Summary: Parallel Port Scanner not found
Alias: None
Product: Fedora
Classification: Fedora
Component: sane-backends   
(Show other bugs)
Version: 7
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-06-19 01:10 UTC by Brian Chadwick
Modified: 2008-06-17 01:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-06-17 01:38:46 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Brian Chadwick 2007-06-19 01:10:58 UTC
Description of problem:
My computer has 3 parallel ports. One is connected to a printer, and one is
connected to a parallel port scanner (Canon N640P). The scanner is not
recognised. (no devices found) .. the scanner works fine in FC6 with appropriate
editing of dll.conf and adding user to "lp" group. I have checked all ports by
moving the printer to each port and testing. All ports work. I have also
compiled sane-backends from sane's website, with the same result. I suspect
something in the kernel is stopping the use of the ports for a parallel scanner,
but I have exhausted my skill set.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Brian Chadwick 2007-06-19 02:09:57 UTC

I turned off various elements in the kernel relating to the parallel port ...

notably: ..

<off> Multi-IO cards (parallel and serial)
<off> AX88796 Parallel Port

<off> Support for user-space parallel port device drivers

After recompilation of the kernel, I can use the scanner as root, but not as
user, even though user is a member of group lp .... 

So, the kernel is doing something, which affects permissions etc ..

Comment 2 Bug Zapper 2008-05-14 13:10:58 UTC
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2008-06-17 01:38:44 UTC
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 is no longer maintained, which means that it will not 
receive any further security or bug fix updates. As a result we 
are closing this bug. 

If you can reproduce this bug against a currently maintained version 
of Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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