--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
02-24-2012, 06:25 AM
Michael Schwendt
Scan does not work on either F-16 box -
On Thu, 23 Feb 2012 17:45:46 -0500, BG (Bob) wrote:
There's something in the package dependencies that doesn't look correct.
Since the split-off of the -cameras and -scanners subpackages, nothing
depends on these separate packages anymore. They are installed only for
the default GNOME Desktop Spin via the "comps" file.
--
Fedora release 16 (Verne) - Linux 3.2.7-1.fc16.x86_64
loadavg: 0.03 0.07 0.13
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
02-24-2012, 09:33 AM
Bob Goodwin
Scan does not work on either F-16 box -
On 24/02/12 02:25, Michael Schwendt wrote:
yum -y install sane-backends-drivers-scanners
Did that, still no device found!
However for the first time ever I ignored the warning not to run
as root and xsane found the Canon LIDE-110 scanner and copied as
expected! A permissions problem?
Box9, as root, found the HP-5370 scanner and copied a page as
expected.
As a matter of interest, my installs are from the XFCE spin on a
flash drive. I then add the applications I want via yum mostly.
Don't know why this computer was different from the other but I
may have inadvertently removed something?
Next to find the permissions problem but this is good progress
for this early hour when I should be sleeping.
Thanks much for your expert help.
Bob
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
02-24-2012, 10:34 AM
Michael Schwendt
Scan does not work on either F-16 box -
On Fri, 24 Feb 2012 05:33:44 -0500, BG (Bob) wrote:
> > yum -y install sane-backends-drivers-scanners
>
> Did that, still no device found!
If the scanner is plugged in, what do you get when running
the /usr/bin/sane-find-scanner command in a terminal?
> However for the first time ever I ignored the warning not to run
> as root and xsane found the Canon LIDE-110 scanner and copied as
> expected! A permissions problem?
Very likely. If you run "lsusb" as root with the scanner being plugged in,
what Bus/Device numbers does it print? For example:
Bus 001 Device 004: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110
^^^ ^^^
If you then substitute your Bus/Device numbers in the following command
appropriately, what do you get when you execute it?
getfacl /dev/bus/usb/001/004
^^^ ^^^
(!)
> As a matter of interest, my installs are from the XFCE spin on a
Which may be an important detail. There's another list for XFCE:
http://lists.fedoraproject.org/pipermail/xfce/
It could be that the XFCE Spin is missing something in its setup.
--
Fedora release 16 (Verne) - Linux 3.2.7-1.fc16.x86_64
loadavg: 0.95 0.46 0.21
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
02-24-2012, 11:16 AM
Bob Goodwin
Scan does not work on either F-16 box -
On 24/02/12 06:34, Michael Schwendt wrote:
On Fri, 24 Feb 2012 05:33:44 -0500, BG (Bob) wrote:
yum -y install sane-backends-drivers-scanners
Did that, still no device found!
If the scanner is plugged in, what do you get when running
the /usr/bin/sane-find-scanner command in a terminal?
found USB scanner (vendor=0x04a9, product=0x1909, chip=GL124?)
at libusb:001:006
# Your USB scanner was (probably) detected. It may or may not
be supported by
# SANE. Try scanimage -L and read the backend's manpage.
However for the first time ever I ignored the warning not to run
as root and xsane found the Canon LIDE-110 scanner and copied as
expected! A permissions problem?
Very likely. If you run "lsusb" as root with the scanner being plugged in,
what Bus/Device numbers does it print? For example:
Bus 001 Device 004: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110
^^^ ^^^
Bus 001 Device 006: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110
If you then substitute your Bus/Device numbers in the following command
appropriately, what do you get when you execute it?
Do I need to chown bobg here? It looks like it ought to work as
is for bobg with 664 ownership?
As a matter of interest, my installs are from the XFCE spin on a
Which may be an important detail. There's another list for XFCE:
http://lists.fedoraproject.org/pipermail/xfce/
It could be that the XFCE Spin is missing something in its setup.
Ok will look there later.
Thank you.
Bob
.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
02-24-2012, 12:50 PM
Michael Schwendt
Scan does not work on either F-16 box -
On Fri, 24 Feb 2012 07:16:43 -0500, BG (Bob) wrote:
The user access ACL entry is missing. That explains why your ordinary
user cannot access the device. (I assume that udev and systemd work fine
on your machine, or have you noticed issues that might be relevant?)
> Do I need to chown bobg here? It looks like it ought to work as
> is for bobg with 664 ownership?
That won't survive a reboot, and when removing+readding the device the
problem would reappear.
Do you run with SELinux enabled and enforcing?
Do you get denials in /var/log/audit/audit.log? (it could be that XFCE
doesn't run the SELinux troubleshooter, so you would not learn about
SELinux problems)
What happens if you switch to "permissive mode" temporarily (either
at boot time) or by running "setenforce 0" as root, then plug in the
scanner?
--
Fedora release 16 (Verne) - Linux 3.2.7-1.fc16.x86_64
loadavg: 0.01 0.04 0.05
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
02-24-2012, 01:34 PM
Bob Goodwin
Scan does not work on either F-16 box -
On 24/02/12 08:50, Michael Schwendt wrote:
On Fri, 24 Feb 2012 07:16:43 -0500, BG (Bob) wrote:
The user access ACL entry is missing. That explains why your ordinary
user cannot access the device. (I assume that udev and systemd work fine
on your machine, or have you noticed issues that might be relevant?)
Do I need to chown bobg here? It looks like it ought to work as
is for bobg with 664 ownership?
That won't survive a reboot, and when removing+readding the device the
problem would reappear.
Do you run with SELinux enabled and enforcing?
Yes
Do you get denials in /var/log/audit/audit.log? (it could be that XFCE
doesn't run the SELinux troubleshooter, so you would not learn about
SELinux problems)
I don't get any SELinux warnings but then I don't know if that
function is working either. The log data is overwhelming! I see
nothing that seems to pertain to "sane." But I could have missed
it ... I tried checking the end of the log immediately after
xsane errored, saw nothing I recognized as a problem, but would I?
What happens if you switch to "permissive mode" temporarily (either
at boot time) or by running "setenforce 0" as root, then plug in the
scanner?
Did that, unplug scanner, run setenforce 0, plug in scanner and
try "xsane" again, same error, device not available. Is there a
command to verify it's actually switched to permissive? There's
so much to know!
Is there something I need to enable under "Users and Groups"
possibly? I looked there but didn't see anything I recognized as
applicable?
Bob
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
02-24-2012, 02:32 PM
Daniel J Walsh
Scan does not work on either F-16 box -
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/24/2012 09:34 AM, Bob Goodwin wrote:
> On 24/02/12 08:50, Michael Schwendt wrote:
>> On Fri, 24 Feb 2012 07:16:43 -0500, BG (Bob) wrote:
>>
>>> [bobg@box6 ~]$ getfacl /dev/bus/usb/001/006 getfacl: Removing
>>> leading '/' from absolute path names # file:
>>> dev/bus/usb/001/006 # owner: root # group: root user::rw-
>>> group::rw- other::r--
>> The user access ACL entry is missing. That explains why your
>> ordinary user cannot access the device. (I assume that udev and
>> systemd work fine on your machine, or have you noticed issues
>> that might be relevant?)
>>
>>> Do I need to chown bobg here? It looks like it ought to work
>>> as is for bobg with 664 ownership?
>> That won't survive a reboot, and when removing+readding the
>> device the problem would reappear.
>>
>> Do you run with SELinux enabled and enforcing?
>
> Yes
>
>> Do you get denials in /var/log/audit/audit.log? (it could be that
>> XFCE doesn't run the SELinux troubleshooter, so you would not
>> learn about SELinux problems)
>
> I don't get any SELinux warnings but then I don't know if that
> function is working either. The log data is overwhelming! I see
> nothing that seems to pertain to "sane." But I could have missed it
> ... I tried checking the end of the log immediately after xsane
> errored, saw nothing I recognized as a problem, but would I?
>
>> What happens if you switch to "permissive mode" temporarily
>> (either at boot time) or by running "setenforce 0" as root, then
>> plug in the scanner?
>>
>
> Did that, unplug scanner, run setenforce 0, plug in scanner and try
> "xsane" again, same error, device not available. Is there a command
> to verify it's actually switched to permissive? There's so much to
> know!
>
> Is there something I need to enable under "Users and Groups"
> possibly? I looked there but didn't see anything I recognized as
> applicable?
>
> Bob
>
>
getenforce
I doubt there is a SELinux problem if this a happens in permissive mode.
ausearch -m avc -ts recent
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9HrZkACgkQrlYvE4MpobP2lgCfVTm5olovP3 YKQKScW3ESIx0V
qDcAnjI6c8+p1udWreC5IjIwuqL/MWe/
=JS0w
-----END PGP SIGNATURE-----
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
02-24-2012, 03:10 PM
Bob Goodwin
Scan does not work on either F-16 box -
On 24/02/12 10:32, Daniel J Walsh wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/24/2012 09:34 AM, Bob Goodwin wrote:
Did that, unplug scanner, run setenforce 0, plug in scanner and try
"xsane" again, same error, device not available. Is there a command
to verify it's actually switched to permissive? There's so much to
know!
Is there something I need to enable under "Users and Groups"
possibly? I looked there but didn't see anything I recognized as
applicable?
Bob
getenforce
I doubt there is a SELinux problem if this a happens in permissive mode.
ausearch -m avc -ts recent
"getenforce" is what I needed to instill confidence in the command.
[root@box6 usb]# setenforce 0
[root@box6 usb]# getenforce
Permissive
Tried plugging in both [USB] scanners with same result, device is
not available.
That seems to indicate there's no SELinux problem.
Thanks Dan,
Bob
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
02-24-2012, 03:24 PM
Michael Schwendt
Scan does not work on either F-16 box -
On Fri, 24 Feb 2012 11:10:26 -0500, BG (Bob) wrote:
> [root@box6 usb]# getenforce
> Permissive
>
>
> Tried plugging in both [USB] scanners with same result, device is
> not available.
>
> [root@box6 usb]# ausearch -m avc -ts recent
> <no matches>
>
>
> That seems to indicate there's no SELinux problem.
Okay. I'm running out of ideas as currently I don't have XFCE running
anywhere to take a look. Perhaps something's missing in the XFCE setup?
What does "systemd-loginctl" print (as root or normal user)?
Do you see messages about attaching/removing the scanner when you
keep "udevadm monitor" running in a terminal as root?
What is the output for: rpm -qa systemd*
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Scan does not work on either F-16 box -
