On 24 March 2014 06:02:05 CET, Dale rdalek1...@gmail.com wrote:
Howdy,
This is confusing. A month or so ago, my HP 5300C scanner worked just
fine. I plugged it in today, it doesn't show up. When I type lsusb, I
get this:
root@fireball / # lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux
J. Roeleveld wrote:
I see a lot of errors about
Device not accepting address number error -62
Did you google for that?
Sounds like an issue with the scanner itself.
--
Joost
I did. I think that is where I got the idea to disable the autosuspend
thing. It made no difference tho. Funny
Yes, my system up to date and clean and I synced yesterday after a few
unsuccessful zsh builds with different USE flags(no changes after syncing).
Also, I rebuild ncurses 5.9 for sure.
PS: I have opened a bug #505500https://bugs.gentoo.org/show_bug.cgi?id=505500
2014-03-23 22:43 GMT+02:00
On 24 March 2014 08:04:08 CET, Dale rdalek1...@gmail.com wrote:
J. Roeleveld wrote:
I see a lot of errors about
Device not accepting address number error -62
Did you google for that?
Sounds like an issue with the scanner itself.
--
Joost
I did. I think that is where I got the idea to
On Mon, 24 Mar 2014 02:04:08 -0500, Dale wrote:
Oh, one hit I got said that error was a kernel bug. That was why I
upgraded, just in case. ;-) I also tried every USB port on this rig,
including ports that other devices work on. Still no joy.
A kernel bug was my first thought, or a
On Mar 24, 2014, at 7:02, Dale rdalek1...@gmail.com wrote:
Howdy,
This is confusing. A month or so ago, my HP 5300C scanner worked just
fine. I plugged it in today, it doesn't show up. When I type lsusb, I
get this:
root@fireball / # lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux
J. Roeleveld wrote:
On 24 March 2014 08:04:08 CET, Dale rdalek1...@gmail.com wrote:
J. Roeleveld wrote:
I see a lot of errors about
Device not accepting address number error -62
Did you google for that?
Sounds like an issue with the scanner itself.
--
Joost
I did. I think that is where
Neil Bothwick wrote:
On Mon, 24 Mar 2014 02:04:08 -0500, Dale wrote:
Oh, one hit I got said that error was a kernel bug. That was why I
upgraded, just in case. ;-) I also tried every USB port on this rig,
including ports that other devices work on. Still no joy.
A kernel bug was my
Matti Nykyri wrote:
On Mar 24, 2014, at 7:02, Dale rdalek1...@gmail.com wrote:
Howdy,
This is confusing. A month or so ago, my HP 5300C scanner worked just
fine. I plugged it in today, it doesn't show up. When I type lsusb, I
get this:
root@fireball / # lsusb
Bus 003 Device 001: ID
On Mon, 24 Mar 2014 03:56:31 -0500, Dale wrote:
A kernel bug was my first thought, or a missing option after an
upgrade. To eliminate software issues, I'd try booting from something
like an Ubuntu or Mint live CD, if it still doesn't work it looks
like a hardware problem.
Do you have
Hi,
several overlays have their own (additional) eclasses and
important packages like eselect.
What happens (and does it harm) if I use
different combinations of overlays at different times?
Many thanks for a mini-tutorial or reference to those,
Helmut
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24/03/14 21:33, Helmut Jarausch wrote:
What happens (and does it harm) if I use different combinations of
overlays at different times?
Generally speaking, I think it would be safer to remain with the
packages that are provided through the
Am Montag 24 März 2014, 11:33:22 schrieb Helmut Jarausch:
Hi,
several overlays have their own (additional) eclasses and
important packages like eselect.
What happens (and does it harm) if I use
different combinations of overlays at different times?
Many thanks for a mini-tutorial or
Dale rdalek1967 at gmail.com writes:
Howdy,
This is confusing. A month or so ago, my HP 5300C scanner worked just
fine.
Hello Dale,
I always keep old (very old) backups of the config file in
/etc/cups to see if when a software upgrade occurs, or
I have to use the admin page of cups
Thanks for the reply.
strace showed very detailed the last syscalls before the SIGSEV:
[pid 21801] sendmsg(9, {msg_name(0)=NULL,
msg_iov(2)=[{l\4\1\1\0\0\0\0\3\0\0\0X\0\0\0\1\1o\0\23\0\0\0/StatusNotifierItem\0\0\0\0\0\2\1s\0\32\0\0\0org.kde.StatusNotifierItem\0\0\0
Hi Dale,
the scanner part of my Brother DCP stopped suddenly also one month ago. My
troubles were caused by the upgrade from sane-backends-1.0.23 to 1.0.24-r1.
Downgrading immediately led to a working scanner again.
[snip]
Cheers,
Jörg
I have been chasing my tail with ruby tonight.
The masking of ruby18 meant that I had to unmerge a lot of ruby packages and
then portage chose what to merge afresh. All good to go I thought until
this was error showed up:
==
On Mon, 24 Mar 2014 20:23:55 +
Mick michaelkintz...@gmail.com wrote:
/usr/lib64/ruby/1.9.1/rubygems.rb:30:in `require': cannot load such
file -- rubygems/defaults (LoadError)
The missing file is there, I think:
# ls -la /usr/lib64/ruby/1.9.1/rubygems.rb
-rw-r--r-- 1 root root 34951
On Monday 24 Mar 2014 21:28:56 Tom Wijsman wrote:
On Mon, 24 Mar 2014 20:23:55 +
Mick michaelkintz...@gmail.com wrote:
/usr/lib64/ruby/1.9.1/rubygems.rb:30:in `require': cannot load such
file -- rubygems/defaults (LoadError)
The missing file is there, I think:
# ls -la
On Mon, 24 Mar 2014 22:44:23 +
Mick michaelkintz...@gmail.com wrote:
On Monday 24 Mar 2014 21:28:56 Tom Wijsman wrote:
On Mon, 24 Mar 2014 20:23:55 +
Mick michaelkintz...@gmail.com wrote:
/usr/lib64/ruby/1.9.1/rubygems.rb:30:in `require': cannot load
such file --
James wrote:
Dale rdalek1967 at gmail.com writes:
Howdy,
This is confusing. A month or so ago, my HP 5300C scanner worked just
fine.
Hello Dale,
I always keep old (very old) backups of the config file in
/etc/cups to see if when a software upgrade occurs, or
I have to use the admin
Jörg Schaible wrote:
Hi Dale,
the scanner part of my Brother DCP stopped suddenly also one month ago. My
troubles were caused by the upgrade from sane-backends-1.0.23 to 1.0.24-r1.
Downgrading immediately led to a working scanner again.
[snip]
Cheers,
Jörg
You can bet I'll try that
Jörg Schaible wrote:
Hi Dale,
the scanner part of my Brother DCP stopped suddenly also one month ago. My
troubles were caused by the upgrade from sane-backends-1.0.23 to 1.0.24-r1.
Downgrading immediately led to a working scanner again.
[snip]
Cheers,
Jörg
Gave the downgrade a try,
23 matches
Mail list logo
