[sane-devel] Mustek ScanExpress 1248UB gt68xx (GT-6816) not working

2008-04-23 Thread Chris Lale 
I have a new Mustek ScanExpress 1248UB USB scanner known to work in Windows98se.
I have installed it in Debian Etch (Stable) and Lenny (Testing) using Debian
packages. The same fault occurs in both systems: when an image is scanned
(scanimage --format pnm > outfile.pnm), the scanner buzzes and clicks, the
scanner head lights up but does not travel down the glass plate. The resulting
image file is non-zero size but completely blank.

This is what I have done.

I installed sane, sane-utils and libsane.

I put the firmware file SBSfw.usb from the manufacturer's CD into
/usr/share/sane/gt68xx/. (diff shows that this is an exact copy of the file
downloaded from http://www.meier-geinitz.de/sane/gt68xx-backend/)

I checked /etc/sane.d/gt68xx.conf. The section for 1248 UB looks like this:
# Autodetect Mustek ScanExpress 1248 UB
usb 0x055f 0x021f

# sane-find-scanner
[...]
found USB scanner (vendor=0x055f, product=0x021f [USB Scanner], chip=GT-6816) at
libusb:005:004
[...]

# scanimage -L
device `gt68xx:libusb:005:004' is a Mustek ScanExpress 1248 UB flatbed scanner

# scanimage -d test -T
scanimage: scanning image of size 157x196 pixels at 8 bits/pixel
scanimage: acquiring gray frame, 8 bits/sample
scanimage: reading one scanline, 157 bytes...   PASS
scanimage: reading one byte...  PASS
scanimage: stepped read, 2 bytes... PASS
scanimage: stepped read, 4 bytes... PASS
scanimage: stepped read, 8 bytes... PASS
scanimage: stepped read, 16 bytes...PASS
scanimage: stepped read, 32 bytes...PASS
scanimage: stepped read, 64 bytes...PASS
scanimage: stepped read, 128 bytes...   PASS
scanimage: stepped read, 256 bytes...   PASS
scanimage: stepped read, 255 bytes...   PASS
scanimage: stepped read, 127 bytes...   PASS
scanimage: stepped read, 63 bytes...PASS
scanimage: stepped read, 31 bytes...PASS
scanimage: stepped read, 15 bytes...PASS
scanimage: stepped read, 7 bytes... PASS
scanimage: stepped read, 3 bytes... PASS

# scanimage -d gt68xx -T
scanimage: scanning image of size 2563x3531 pixels at 8 bits/pixel
scanimage: acquiring gray frame, 8 bits/sample
scanimage: reading one scanline, 2563 bytes...  PASS
scanimage: reading one byte...  PASS
scanimage: stepped read, 2 bytes... PASS
scanimage: stepped read, 4 bytes... PASS
scanimage: stepped read, 8 bytes... PASS
scanimage: stepped read, 16 bytes...PASS
scanimage: stepped read, 32 bytes...PASS
scanimage: stepped read, 64 bytes...PASS
scanimage: stepped read, 128 bytes...   PASS
scanimage: stepped read, 256 bytes...   PASS
scanimage: stepped read, 512 bytes...   PASS
scanimage: stepped read, 1024 bytes...  PASS
scanimage: stepped read, 2048 bytes...  PASS
scanimage: stepped read, 4096 bytes...  PASS
scanimage: stepped read, 4095 bytes...  PASS
scanimage: stepped read, 2047 bytes...  PASS
scanimage: stepped read, 1023 bytes...  PASS
scanimage: stepped read, 511 bytes...   PASS
scanimage: stepped read, 255 bytes...   PASS
scanimage: stepped read, 127 bytes...   PASS
scanimage: stepped read, 63 bytes...PASS
scanimage: stepped read, 31 bytes...PASS
scanimage: stepped read, 15 bytes...PASS
scanimage: stepped read, 7 bytes... PASS
scanimage: stepped read, 3 bytes... PASS
[About 30 seconds of buzzing and clicking]

I would be grateful for any suggestions.

-- 
Chris.

[sane-devel] SOLVED Mustek ScanExpress 1248UB gt68xx (GT-6816) not working

2008-04-23 Thread Chris Lale 
Chris Lale wrote:
> I have a new Mustek ScanExpress 1248UB USB scanner known to work in 
> Windows98se.
> I have installed it in Debian Etch (Stable) and Lenny (Testing) using Debian
> packages. The same fault occurs in both systems: when an image is scanned
> (scanimage --format pnm > outfile.pnm), the scanner buzzes and clicks, the
> scanner head lights up but does not travel down the glass plate. The resulting
> image file is non-zero size but completely blank.
[...]

The scanner was attached to a Belkin USB hub. When I connected it directly to
the USB port on the motherboard it worked fine. Looks like a problem with the 
hub.

-- 
Chris.

[sane-devel] How do I scan as a normal user?

2008-04-28 Thread Chris Lale 
[...]
>>
>> On 4/25/08, Marc Shapiro  wrote:
[...]
>>>   I'm not sure what
>>>  changed that, but it now recognizes the scanner if I run scanimage, or
>>>  xscanimage as root, but NOT if I run as a normal user.  
[...]

If you are running Debian, the answer is simple. Simply add users to the group
"scanner" (Debian should have created this group for you). If you are running
the Gnome desktop: Desktop -> Administration -> Users and Groups, Users tab ->
Add user. If you add yourself, remember to logout and login again to activate
your membership of the group for that session.

-- 
Chris.

[sane-devel] Double-free following scan on ubuntu hardy 8.04 with epjitsu fi-60f

2008-04-29 Thread Chris Lale 
Jeff Kowalczyk wrote:
> On Mon, 28 Apr 2008 21:01:08 -0400, m. allan noah wrote:
> 
>> well, i've just committed a patch to fix this, but please test, as i
>> never saw the error message in the first place...
> 
> Does anyone have a good procedure for patching and rebuilding
> released ubuntu .debs to test upstream changes? Or a way to build new debs
> from sane snapshots at a particular revision? The originally reported
> platform (Ubuntu) is not my familiar source-based system (Gentoo).
> 
> 

This is how you could do it in Debian [1].

Basic method for a package "somepackage" version "0.7.1-1" is as follows. (This
does not change the version number, but that is explained in the 
documentation.):

0.
Get the source package.

1. put
somepackage_0.7.1-1.diff.gz
somepackage_0.7.1.orig.tar.gz
somepackage_0.7.1-1.dsc
in a directory.

2.  Run
dpkg-source -x somepackage_0.7.1-1.dsc to recreate build directory.

3. cd to
somepackage-0.7.1
Do what you need.

4. Run
dpkg-buildpackage -rfakeroot
Completes with message
dpkg-buildpackage: full upload (original source is included)

5. Run checks:
lintian somepackage_0.7.1-1_i386.changes
and
linda somepackage_0.7.1-1_i386.changes
Both should complete with no errors reported.

debc somepackage_0.7.1-1_i386.changes | less
On inspection, files contained in package should look OK.

# debi somepackage_0.7.1-1_i386.changes
should install package OK.

# dpkg --purge somepackage
removes package.


[1] http://www.us.debian.org/doc/maint-guide/

Hope that helps.

-- 
Chris.