[sane-devel] Canon Lide 60

2006-09-20 Thread Joaquín goicoechea
Tengo un scanner Cannon Lide 60 como root, xsane identifica el scanner como usuario, xsane no identifica el scanner. He probado crear un grupo con permisos para xsane, pero tampoco identifica el scanner. ?Como puedo hacer para que xsane identifique el scanner en modo usuario

[sane-devel] Canon LiDE 60 scan options

2006-04-16 Thread Philip Rhoades
People, I have been using an LiDE 20 satisfactorily for a while but waiting till the driver for the LiDE 60 was going. From the postings it seems that the 60 driver is now working OK and so I have switched over. The scan options interface is slightly different for the 60 - for example I have

[sane-devel] Canon LiDE 60 scan options

2006-04-16 Thread Philip Rhoades
Roger, On Sun, 2006-04-16 at 19:57 +0200, Roger Price wrote: On Sun, 16 Apr 2006, Philip Rhoades wrote: ... it appears that I am now forced into using one of: 75, 150, 300, 600, 1200 or 2400 . . is there some way to change this so I can use my traditional resolutions? From xsane's

[sane-devel] Canon LIDE 60 successfully added to /etc/sane.d/hotplug/libsane.db

2006-03-20 Thread J.F. Vasconcelos
Hi Bought a brand new Canon LIDE 60 and installed it in Debian Sarge. To get it working, had to add these lines IN /etc/sane.d/hotplug/libsane.db ADDED # Canon Inc.|LIDE 60 0x04a9 0x221c root:scanner0664 IN /etc/udev/libsane.rules ADDED # Canon Inc.|LIDE 60 SYSFS{idVendor}==04a9,

[sane-devel] Canon Lide 60

2006-02-06 Thread Stéphane VOLTZ
Le Dimanche 5 F?vrier 2006 12:18, CSORDAS Laszlo a ?crit?: Canon Lide 60 working with backend MEDION MD5345 (genesys) :-))) -destitute 4 speed button- csola Hello, did you configure anything or did it work 'out of the box' ? Regards, Stef

[sane-devel] Canon Lide 60

2006-02-06 Thread CSORDAS Laszlo
St?phane VOLTZ wrote: Le Dimanche 5 F?vrier 2006 12:18, CSORDAS Laszlo a ?crit : did you configure anything or did it work 'out of the box' ? Regards, Stef Nothing... ran at sight :-) -- next part -- An HTML attachment was scrubbed... URL:

[sane-devel] Canon LiDE 60 test report

2006-01-03 Thread Henning Meier-Geinitz
On 2006-01-02 21:05, Reinhard Mayr aka Czerwinski wrote: (gdb) run --mode Color image.pnm 2log Starting program: /usr/bin/scanimage --mode Color image.pnm 2log [Thread debugging using libthread_db enabled] [New Thread 1076312288 (LWP 19858)] Program exited normally. Ok, so there is no

[sane-devel] Canon LiDE 60 test report

2006-01-03 Thread Reinhard Mayr aka Czerwinski
On Tue, 03 Jan 2006 14:19:24 +0100, Henning Meier-Geinitz henn...@meier-geinitz.de wrote: Starting program: /usr/X11R6/bin/xsane image.pnm 2log [Thread debugging using libthread_db enabled] [New Thread 1086061088 (LWP 20069)] Program received signal SIGSEGV, Segmentation fault. [Switching

[sane-devel] Canon LiDE 60 test report

2006-01-02 Thread Reinhard Mayr aka Czerwinski
Hi, first of all: The scanner works when I connect the PCMCIA-USB adapter to the AC/DC adapter -- Thanks much for this hint! On Sat, 31 Dec 2005 16:13:26 +0100, Henning Meier-Geinitz henn...@meier-geinitz.de wrote: Hi, On 2005-12-31 15:48, Reinhard Mayr aka Czerwinski wrote: my answers

[sane-devel] Canon LiDE 60 test report

2005-12-31 Thread Henning Meier-Geinitz
Hi, On 2005-12-29 23:41, Reinhard Mayr aka Czerwinski wrote: 4. Color/8bit - All resolutions work. 1200 and 2400 are very slow ( 15 minutes per page) Did you test this at a USB 2 port? Iget approximately 6 minutes at 2400 dpi and 3 minutes at 1200 dpi. 5. Color/16bit

[sane-devel] Canon LiDE 60 test report

2005-12-31 Thread Henning Meier-Geinitz
Hi, On 2005-12-31 15:48, Reinhard Mayr aka Czerwinski wrote: my answers are inserted below: Your mail wasn't accepted by the list because it's just too big. I'll quote the important stuff so you don't need to resend it. Can we have a log file and gdb trace as mentioned in the article,

[sane-devel] Canon LiDE 60: Semi-success report

2005-12-06 Thread Henning Meier-Geinitz
Hi, On Mon, Dec 05, 2005 at 05:41:49PM +0100, Pierre Willenbrock wrote: Those corrupted horizontal lines are the result of a buffer overrun. I thought i did setup the words per line parameter correctly, but obviously i did not. In this case word seems to mean 1 byte while in other contexts it

[sane-devel] Canon LiDE 60: Semi-success report

2005-12-05 Thread Henning Meier-Geinitz
Hi, On Mon, Dec 05, 2005 at 12:00:30AM +0100, Reinhard Mayr aka Czerwinski wrote: sorry, I did not realize that there is a difference between current CVS and experimental. Are you really sure that you use experimental now? :-) Some of your errors occur for me with the normal CVS, but not

[sane-devel] Canon LiDE 60: Semi-success report

2005-12-05 Thread Pierre Willenbrock
Henning Meier-Geinitz schrieb: I only get backtracking here with high load of the computer. However I can confirm the horizontal lines. Looks like something connected to backtracking at 16 bit doesn't fully work yet. I don't have these lines in 8 bit mode. Those corrupted horizontal

[sane-devel] Canon LiDE 60: Semi-success report

2005-12-04 Thread Reinhard Mayr aka Czerwinski
Hi everyone, I did some tests with the LiDE 60 and the current CVS backend (20051204-14:10). These are my results: Lineart: 75: ok 150: ok 300: ok 600: ok 1200: ok 2400: freeze after 6 cm Gray/8 bit 75: ok 150: ok 300: ok 600: ok 1200: freeze after 4 cm 2400: freeze after 1.5 cm Gray/16 bit

[sane-devel] Canon LiDE 60: Semi-success report

2005-12-04 Thread Henning Meier-Geinitz
Hi, On Sun, Dec 04, 2005 at 02:19:36PM +0100, Reinhard Mayr aka Czerwinski wrote: I did some tests with the LiDE 60 and the current CVS backend (20051204-14:10). These are my results: Use the backend from experimental CVS. As mentioned in my success report, that one works much better, at

[sane-devel] Canon LiDE 60: Semi-success report

2005-12-04 Thread Reinhard Mayr aka Czerwinski
Hi again, sorry, I did not realize that there is a difference between current CVS and experimental. These are my results with the current experimental code: Lineart: 75: ok 150: ok 300: ok 600: ok 1200: ok 2400: ok gray/8bit: 75: ok 150: ok 300: ok 600: ok 1200: ok 2400: Error during read: