First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 188092
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Stefan Briesenick <sbriesen@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Raimonds Cicans <ray@apollo.lv>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
99-iscan.rules.patch Simple workaround patch Raimonds Cicans 2007-08-08 11:52 0000 510 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 188092 depends on: Show dependency tree
Show dependency graph
Bug 188092 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2007-08-08 11:49 0000 
If package media-gfx/iscan is installed and Epson USB Multi Functional Printer
(MFP) is connected to computer, then installation of this printer in CUPS works
without problems but any attept to print return timeout error.

Reproducible: Always

Steps to Reproduce:
1. emerge media-gfx/iscan
2. connect Epson USB MFP & turn it on
3. install printer in CUPS
4. print testpage

Actual Results:  
No reaction from printer
CUPS printer status show timeout error

Expected Results:  
Test page printed

version of media-gfx/iscan - 2.7.0 (but I suspect other may have same problem)

Cause:
udev rules from media-gfx/iscan package change group of printer part of MFP
from 'lp' to 'scanner', but CUPS expect printer belongs to 'lp' group

------- Comment #1 From Raimonds Cicans 2007-08-08 11:52:42 0000 ------- 
Created an attachment (id=127274) [edit]
Simple workaround

Patch to /etc/udev/rules.d/99-iscan.rules file, to workaround tgis problem

------- Comment #2 From Stefan Briesenick 2007-08-08 23:03:17 0000 ------- 
ok, accepted. I will include this patch asap, but I'm not sure if I should
rev-bump it for this fix, which affects only very few people...

------- Comment #3 From Matthias Schwarzott 2007-08-18 16:56:18 0000 ------- 
Please: if you change anything there, also move the file away from name
99-*.rules to something other. If you keep the rules as they are the number
needs to be >50, as 50-udev.rules else overwrites the GROUP property (at the
moment).

------- Comment #4 From Stefan Briesenick 2007-08-19 22:14:00 0000 ------- 
there's a new release already there. So I will put all changes to this new
version first and then I try to patch the older versions also.

btw: I had the rules-number at 75 before. But then I found:

-rw-r--r-- 1 root root 53211  2. Mai 16:50 99-libgphoto2.rules
-rw-r--r-- 1 root root 61163  2. Mai 16:56 99-libsane.rules

so I thought it would be good to have it also at 99. Any suggestions for the
number? 70s? 60s? But please not 50s.

------- Comment #5 From Matthias Schwarzott 2007-08-21 12:15:38 0000 ------- 
Well, there seems not yet be some approved number scheme.
For new stuff without any needs I suggest 40. And in this case some packages
seem to use 55.
If you do not want to do multiple changes you can also keep it now on 99 as the
others did, and change that once we know what exactly we want to do :)

------- Comment #6 From Stefan Briesenick 2007-08-23 18:37:15 0000 ------- 
ok. ;-)

after some final checks, I will commit new version this weekend.

------- Comment #7 From Stefan Briesenick 2007-09-03 21:01:23 0000 ------- 
fixed + new version in portage.
First Last Prev Next    No search results available      Search page      Enter new bug