HP 4P scanner use

[NoOp]

On 05/23/2009 05:26 AM, Brian McKee wrote:
> On Sat, 2009-05-23 at 19:48 +1100, Alan Duval wrote:
> 
>> However I have the annoying problem that an error message "Failed to 
>> create file: Permission denied" occurs when I try to close XSane. I have 
>> to close this error message 3 times before XSane closes.
>> I started XSane from a user terminal but the same error message occurred 
>> when closing and no message  occurred in the terminal.
> 
> 
> 
>> When I typed users-admin in root this message occurred prior to the 
>> user-admin window opening:
>> ** (users-admin:6683): CRITICAL **: Cannot create session bus: Did not 
>> receive a reply.
> 
>> Could that have something to do with the XSane closing error?
> 
> I think that one is a red herring.

It's a bug:

# users-admin

** (users-admin:6049): CRITICAL **: Cannot create session bus: Did not
receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the
reply timeout expired, or the network connection was broken.
GConf Error: Failed to contact configuration server; some possible
causes are that you need to enable TCP/IP networking for ORBit, or you
have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details -  1: Failed
to get connection to session: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.)

However it does open the gui.

No issues with:

$ users-admin

The problem appears to deeper:
http://bugzilla.gnome.org/show_bug.cgi?id=555745
[Programs using Gconf fail if you start via "su"]
https://bugs.launchpad.net/gconf/+bug/328575
[Cannot start gnome-terminal because of gconf error]

For Alan: just run users-admin as a user rather than root:

$ users-admin

That will open the gui and you can click the 'Unlock' button to get the
password prompt.

> 
> My guess is that there is a file that has had root ownership set in
> previous runs that we now need to be a bit more permissive.
> 
> To prove that out - install 'strace'  (e.g. 'sudo aptitude install
> strace' in a terminal or use Synaptic etc - your choice)
> 
> Then run strace -e trace=file xsane | grep Permission
> That should show ever file system call done by the xsane program and
> cull through that output looking for Permission denied errors.
> 
> Recreate your problem while watching the output and let's see what you
> get.
> 
> Brian
> 

Might be better to just purge xsane and then reinstall so that it clears
out the config files as well:

$ sudo apt-get purge xsane
$ sudo apt-get install xsane

Rename the xsane folder in /home/<username>/.sane/xsane to
/home/<username>/.sane/xsanex-x. For some reason the purge will not
clear that folder unless you purge sane as well. Also check to see if
you have the same in /root/.sane/xsane - if so rename that one as well.
Note: rename rather than remove just in case you need to revert back.

You should _not_ have to run xsane as root.

Note: I have an HP C5100A (photo, negative, slide scanner) connected to
a scsi, with xsane I'v have issues with the images in the past (comes
out as single line). Doing the above cleared the problem for me on
Jauney. Note: xsane worked fine on my USB connected Canon MP750.

With sane ($ sudo apt-get install sane) you can simply use the
xscanimage gui utility:

$ xscanimage

It's pretty basic, but works quite well.