On 27/02/12 17:56, Michael Schwendt wrote:
On 27 February 2012 20:43, Bob Goodwin wrote:
I always have "rhgb disabled" and display as much information as
I can get, use the "text log-in", start from the command line
with "startx" every morning,
Congratulations, you'v
On 27 February 2012 20:43, Bob Goodwin wrote:
>>
>>> I always have "rhgb disabled" and display as much information as
>>> I can get, use the "text log-in", start from the command line
>>> with "startx" every morning,
>>
>> Congratulations, you've just found a test-case! :-)
On 26/02/12 11:20, Michael Schwendt wrote:
On Sun, 26 Feb 2012 09:52:40 -0500, BG (Bob) wrote:
I always have "rhgb disabled" and display as much information as
I can get, use the "text log-in", start from the command line
with "startx" every morning,
Congratulations,
On Sun, 26 Feb 2012 09:52:40 -0500, BG (Bob) wrote:
> I always have "rhgb disabled" and display as much information as
> I can get, use the "text log-in", start from the command line
> with "startx" every morning,
Congratulations, you've just found a test-case! :-) Run-lev
On 26/02/12 08:22, Michael Schwendt wrote:
On Fri, 24 Feb 2012 20:05:33 -0500, BG (Bob) wrote:
Perhaps just the XFCE Spin is affected?
Or just my copy?
So, a default install to harddisk of the XFCE Spin (Fedora 16 x86_64)
is not enough to reproduce the problem. ACLs on the device nod
On Fri, 24 Feb 2012 20:05:33 -0500, BG (Bob) wrote:
> > Perhaps just the XFCE Spin is affected?
>
> Or just my copy?
So, a default install to harddisk of the XFCE Spin (Fedora 16 x86_64)
is not enough to reproduce the problem. ACLs on the device node get set.
The test scanner is listed
On Sat, 25 Feb 2012 18:19:56 -0500, BG (Bob) wrote:
> But I do see the following at the end of /var/log/messages:
>
> Feb 25 17:38:08 box6 dbus-daemon[752]: dbus[752]: [system]
> Activating service name='net.reactivated.Fprint' (using
> servicehelper)
> Feb 25
On 25/02/12 17:13, Michael Schwendt wrote:
grep ACL /var/log/messages
.
That produces no output:
[root@box6 bobg]# grep ACL /var/log/messages
[root@box6 bobg]#
But I do see the following at the end of /var/log/messages:
Feb 25 17:38:08 box6 dbus-daemon[752]: dbu
On Sat, 25 Feb 2012 08:21:11 -0500, BG (Bob) wrote:
> In an off-list discussion with "g" I realized that I could run
> another "virgin" instance of F-16/64 from the XFCE Live Spin on
> the flash drive, the same one these installations are derived
> from. Why did it
On 24/02/12 19:17, Michael Schwendt wrote:
That's the wrong file. The device file would have been '012' in that
directory. I've done a "yum groupinstall XFCE" here for a very brief
test, but when logging into XFCE (albeit from GDM), the user access
ACL entry on the device file is set automaticall
On 24/02/12 19:17, Michael Schwendt wrote:
That's the wrong file. The device file would have been '012' in that
directory. I've done a "yum groupinstall XFCE" here for a very brief
test, but when logging into XFCE (albeit from GDM), the user access
ACL entry on the device file is set automatica
On Fri, Feb 24, 2012 at 06:07:02PM -0500, Bob Goodwin wrote:
> On 24/02/12 17:44, ny6...@gmail.com wrote:
> > On Fri, Feb 24, 2012 at 05:33:44AM -0500, Bob Goodwin wrote:
> >> On 24/02/12 02:25, Michael Schwendt wrote:
> >>> yum -y install sane-backends-drivers-scanners
> >> Did that, stil
On 24/02/12 19:17, Michael Schwendt wrote:
That's the wrong file. The device file would have been '012' in that
directory. I've done a "yum groupinstall XFCE" here for a very brief
test, but when logging into XFCE (albeit from GDM), the user access
ACL entry on the device file is set automatica
On Fri, 24 Feb 2012 18:07:02 -0500, BG (Bob) wrote:
> On 24/02/12 17:44, ny6...@gmail.com wrote:
> > On Fri, Feb 24, 2012 at 05:33:44AM -0500, Bob Goodwin wrote:
> >
> > There is a simple way to overcome this limitation. Find out what bus the
> > printer/scanner is on with lsusb. Then go into /dev
On 24/02/12 17:44, ny6...@gmail.com wrote:
On Fri, Feb 24, 2012 at 05:33:44AM -0500, Bob Goodwin wrote:
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 war
On Fri, Feb 24, 2012 at 05:33:44AM -0500, Bob Goodwin wrote:
> 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 a
On 24/02/12 11:43, Michael Schwendt wrote:
On Fri, 24 Feb 2012 11:40:10 -0500, BG (Bob) wrote:
What is the output for: rpm -qa systemd\*
[root@box6 usb]# rpm -qa systemd\*
systemd-sysv-37-13.fc16.x86_64
systemd-37-13.fc16.x86_64
systemd-units-37-13.fc16.x86_64
What does
On Fri, 24 Feb 2012 11:40:10 -0500, BG (Bob) wrote:
> > What is the output for: rpm -qa systemd\*
>
> [root@box6 usb]# rpm -qa systemd\*
> systemd-sysv-37-13.fc16.x86_64
> systemd-37-13.fc16.x86_64
> systemd-units-37-13.fc16.x86_64
What does
ps axuw|grep bus
print? In partic
On 24/02/12 11:24, Michael Schwendt wrote:
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 rec
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
>
>
>
> That see
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 swit
-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 name
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
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-
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 termina
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 tim
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 pe
On Thu, 23 Feb 2012 17:45:46 -0500, BG (Bob) wrote:
> [bobg@box6 ~]$ rpm -qa \*sane\*
> libsane-hpaio-3.11.12-1.fc16.x86_64
> sane-backends-drivers-cameras-1.0.22-8.fc16.x86_64
> xsane-0.998-4.fc16.x86_64
> sane-backends-libs-1.0.22-8.fc16.x86_64
> xsane-common-0.998-4.fc16
On 23/02/12 17:24, Michael Schwendt wrote:
On Thu, 23 Feb 2012 17:13:23 -0500, BG (Bob) wrote:
[bobg@box6 ~]$ /var/log/message
bash: /var/log/message: No such file or directory
It's /var/log/messagessorry for the typo in my earlier reply.
Have you really not taken a loo
On Thu, 23 Feb 2012 17:13:23 -0500, BG (Bob) wrote:
>
> [bobg@box6 ~]$ /var/log/message
> bash: /var/log/message: No such file or directory
It's /var/log/messagessorry for the typo in my earlier reply.
Have you really not taken a look at that file before?
> Something h
On 23/02/12 16:35, Michael Schwendt wrote:
On Thu, 23 Feb 2012 15:09:25 -0500, BG (Bob) wrote:
this is an up to date F-16/64 bit computer. I reported last week
that my trusty HP 5370 scanner didn't work, finally concluding
that it must have met it's end. Today I rece
On Thu, 23 Feb 2012 15:09:25 -0500, BG (Bob) wrote:
>
>
> this is an up to date F-16/64 bit computer. I reported last week
> that my trusty HP 5370 scanner didn't work, finally concluding
> that it must have met it's end. Today I received a new Canon
> LIDE 110 wh
On 02/23/2012 12:09 PM, Bob Goodwin wrote:
I suppose that it's possible that the required driver
is not included in Fedora-16 but I don't know how to determine
what is, at least I haven't yet.
You probably want to check the Linux hardware compatibility lists at
http://www.linux
this is an up to date F-16/64 bit computer. I reported last week
that my trusty HP 5370 scanner didn't work, finally concluding
that it must have met it's end. Today I received a new Canon
LIDE 110 which according to a Sane list I found is supposed to
work. It
34 matches
Mail list logo
