On Tuesday 08 May 2007, Julian Stacey wrote:
> > When I run su and put in my login password it is rejected as an
> > authentication failure. When I use the same password in sudo, it works!
> > Do you have a work around?
>
> Maybe sudo doesnt check if your UID is in group 0 in /etc/group.
> whereas
my god you are hard to help. i have to repeat EVERY message?
"...(give root password)..."
allan
On 5/7/07, Robin Stewart wrote:
> Allan
>
> When I run su and put in my login password it is rejected as an
> authentication failure. When I use the same password in sudo, it works!
> Do you have a w
Robin Stewart wrote:
> Allan
>
> When I run su and put in my login password it is rejected as an
> authentication failure. When I use the same password in sudo, it works!
> Do you have a work around?
Maybe sudo doesnt check if your UID is in group 0 in /etc/group.
whereas su does check & bounce
Hi,
configure (generated by Autoconf 2.61) fails and claims
not to find grep (which is bogus)
Running autoconf (2.59) locally solves the problem.
can someone please regenerate configure in cvs with autoconf 2.59
Bye,
Franz
Allan
When I run su and put in my login password it is rejected as an
authentication failure. When I use the same password in sudo, it works!
Do you have a work around?
Robin
The above comments are in response to m. allan noah's email of 07/05/07
18:18 as quoted below:
> try this:
>
> su -
try this:
su -
(give root password)
you now have a root shell.
then run the command i gave. logout of root shell when done.
allan
On 5/7/07, Robin Stewart wrote:
> Thank you very much for your help.
>
> I assume that running it as root means putting sudo in front.
>
> I can not run the comma
well, you are the first person to report having one, so you are going
to have to provide whatever extra info there is :) as root:
SANE_DEBUG_FUJITSU=30 scanimage --help 2>fi60.log
and send me fi60.log directly.
btw- you have doppler misspelled several times on your website...
allan
On 5/7/07,
Thank you very much for your help.
I assume that running it as root means putting sudo in front.
I can not run the command:
sudo SANE_DEBUG_AVISION=7 scanimage -L
it gives a command not found error.
Robin
The above comments are in response to m. allan noah's email of 07/05/07
17:36 as quoted
to find USB device 638 26a ...
[avision] sane_init: Trying to find USB device 686 4004 ...
[avision] sane_init: Trying to find USB device 686 400d ...
[avision] sane_init: Trying to find USB device 686 400e ...
[avision] sane_init: Trying to find USB device 638 a15 ...
Hello,
We have a Fujitsu fi-60F scanner that we would very much like to have
working in linux. This is a small document (A6) flatbed scanner and I
believe is the only one of its kind.
The system I'm testing on is FC5 with kernel 2.6.20 with SANE 1.0.18.
The product ID for this device is 0x10c
Thanks Allan, that works for me.
-Original Message-
From:
sane-devel-bounces+tomgarvin=amyskitchen@lists.alioth.debian.org
[mailto:sane-devel-bounces+tomgarvin=amyskitchen.net@lists.alioth.debian
.org] On Behalf Of m. allan noah
Sent: Saturday, May 05, 2007 7:33 AM
To: sane-devel@list
"...then run the same debug test as before..."
allan
On 5/7/07, Robin Stewart wrote:
> Using sudo gedit /etc/sane.d/avision.conf I have just removed the
> line. I then run
> scanimage -L and unfortunately no scanners were identified.
>
> Robin
>
> The above comments are in response to m. allan
Using sudo gedit /etc/sane.d/avision.conf I have just removed the
line. I then run
scanimage -L and unfortunately no scanners were identified.
Robin
The above comments are in response to m. allan noah's email of 07/05/07
12:17 as quoted below:
> drop the libusb line from the file, you likely
drop the libusb line from the file, you likely only need the vid/pid
line. then run the same debug test as before. lets make sure the
backend reads the file properly and looks for the scanner.
allan
On 5/7/07, Robin Stewart wrote:
> This is the avision.conf file as just adjusted by me. After the
Hi,
one thing to add. I've tested the Plustek-Backend on a
recent Debian system x86_64 AND CONFIG_USB_SUSPEND activated.
Result: no problems so far.
Gerhard
On Dienstag, 1. Mai 2007, Julien BLACHE wrote:
> JKD wrote:
>
> Hi,
>
> >> Connections remain ? Is the connection still open when the
On Freitag, 4. Mai 2007, Gerhard Jaeger wrote:
> On Freitag, 4. Mai 2007, Johannes Meixner wrote:
> >
> > Hello,
> >
> > I got a strange bug report from a user:
> > https://bugzilla.novell.com/show_bug.cgi?id=269921
> >
> > Short summary:
> > He uses a HP ScanJet 2200C USB scanner with the plust
This is the avision.conf file as just adjusted by me. After the
adjustment the scanner is still not being found by sane:
> #option disable-gamma-table
> #option disable-calibration
> #option force-a4
>
> #scsi AVISION
> #scsi FCPA
> #scsi MINOLTA
> #scsi MITSBISH MCA-S600C
> #scsi MITSBISH MCA-SS
17 matches
Mail list logo