Hello again,
For your information, today I stopped scanning with the problematic HP5300C.
I bought a second-hand CanoScan LiDe30 which is running fine with xsane.
Thanks for your time anyway,
Bert verbeek
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
Op Tuesday 22 July 2008, schreef Julien BLACHE:
>
> I've just realized a couple of minutes ago that the patch containing
> some Avision fixes that may help with this problem was never enabled
> in the package.
>
> I'm building libsane 1.0.19-15 right now with the patch enabled as it
> should have b
Op Friday 11 July 2008, schreef René Rebe:
> Hi Julien,
>
> Patches, especially for stuff I can not reproduce welcome.
Hello Rene,
first of all, thanks for your time in advance.
As I like to get this scanner going again, I started today reading in the tree
of the debian sane-backends source pac
approx. 7 minutes as you described, but the
buttons are not working and when I move the windows they turn grey and are
not redrawn.
So the segfault is gone, but the xsane program is still not working for my
HP5300C.
--
M.vr.gr.
Bert Verbeek
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
Op Friday 06 June 2008, schreef Debian Bug Tracking System:
> This is an automatic notification regarding your Bug report
> which was filed against the libsane package:
>
> #474706: xsane segfaults when trying a preview or scan
>
> It has been closed by Julien BLACHE <[EMAIL PROTECTED]>.
>
> Their
Op Wednesday 09 April 2008, schreef Julien BLACHE:
>
> That's something else, unrelated to -4, I think, as there was no code
> changes to avision :)
Tomorrow, I remembered that I recently had a problem with a scanner of my own,
a Lide20, and reread Bug#439780. This was about switching off the usb
Op Monday 07 April 2008, schreef u:
>
> Please try to scan with scanimage from the command line first; if that
> too segfaults, enable debug in the avision backend and save the
> output:
> SANE_DEBUG_AVISION=255 scanimage > /dev/null 2> scan.log
>
> Then, try to obtain a backtrace:
> - install l
pty and
scans don't work. Deleting this file, and starting xsane again says: no
devices.
* Lenny with kernel 2.6.24-1-686 (no k7 version available anymore?):
scanimage -L: shows the correct result as shown above.
xsane: segfaults at startup.
I'm stuck here, any help would be appreciate
Op Saturday 22 March 2008, schreef Brice Goglin:
> This might be fixed in Xserver 1.5 thanks to some x86emu patches,
> could you try the Xorg 7.4 packages using
> deb http://pkg-xorg.alioth.debian.org/7.4/ ./
> in /etc/apt/sources.list ?
>
> thanks,
> Brice
Hello Brice,
after strugling with dep
Op Sunday 13 January 2008, schreef Brice Goglin:
> Bert and Ties,
> you might want to try adding
> Option "NoDDC" "true"
> to section Device in xorg.conf and see if that helps.
It helps indeed for me,
uptill now its a fine workaround,
both for the 1.3 and 1.4 xservers
I'm back on a regular L
Op Tuesday 04 September 2007, schreef Bert Verbeek:
> > the phosphor screensaver is just a wrapper around the phosphor
> > xscreensaver. What version of xscreensavers have you installed? if you
>
> xscreensavers_5.03-2
>
> > downgrade to a earlier version of xsc
Op Monday 17 December 2007, schreef Julien Cristau:
>
> Hi Bert,
>
> can you install xserver-xorg-core-dbg to get more info in the backtrace?
Hello Julien,
no problem,
the gdb results on xserver-xorg-core-dbg from unstable:
Bert
--
Reading symbols from /usr/lib/xorg/modules/libi
Op Friday 14 December 2007, schreef u:
>
> It would be even better to do that with Xserver 1.4 from unstable.
ok, testing + xserver 1.4 from unstable
the output looks the same to me.
I attached the corresponding /var/log/Xorg.0.log.
Bert
-
(no debugging symbols found)
0xb7a
Op Friday 14 December 2007, schreef Brice Goglin:
>
> With Xserver 1.3 then? That's an interesting point. Could you log in
> through ssh and attach a gdb with
> gdb -p $(pidof X)
> then interrupt with ctrl-c, enter 'bt full' to see which code is being
> run, then enter 'c' to continue, wait a b
Op Wednesday 05 December 2007, schreef Bert Verbeek:
>
> xserver-xorg-core_1.2.0-4 runs exactly the same as 1.1.1-21etch1,
> the same minor imperfections I mentioned before (In KDE).
>
> Bert
I removed the synaptics input device from my xorg.conf file,
as this laptop doesn'
Op Wednesday 05 December 2007, schreef Brice Goglin:
>
> Ok then the problem is in xserver-xorg-core 1.3 in testing. You could try 1.2
> from
> http://snapshot.debian.net/archive/2007/02/26/debian/pool/main/x/xorg-server/xserver-xorg-core_1.2.0-4_i386.deb
>
> so that we know more about when the
my earlier mails.
It didn't bring up X in testing.
--
M.vr.gr.
Bert Verbeek
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Op Wednesday 05 December 2007, schreef Brice Goglin:
>
> You probably need to downgrad xserver-xorg-input-kbd, -mouse and
> -synaptics to stable/etch as well.
>
> Brice
Hello Brice,
Good news,
I did what you proposed and I got X back in the testing installation,
thanks for this workaround.
KD
Hello,
I also noticed there was a newer xserver-xorg-video-trident package in
unstable.
I updated xserver-xorg (and everything it depends on) via apt-pinning to X
1:7.3+7.
No solution, it locks up the laptop as well.
--
M.vr.gr.
Bert Verbeek
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
Op Tuesday 04 December 2007, schreef u:
>
> Does downgrading *only* xserver-xorg-core to stable (from 2:1.3.0.0.dfsg-12
> to 2:1.1.1-21) fix the problem? For both vesa and trident drivers?
>
> Brice
I downloaded to xserver-xorg-core_1.1.1-21etch1_386.deb.
unfortunately not,
X complains about mod
Package: xserver-xorg
Version: 1:7.2-5
Severity: important
I'm trying to upgrade a Debian stable installation on an older
Toshiba S1800 laptop. An upgrade to testing succeeded, however X will
not start anymore and hangs the laptop. Ctrl-Alt-Del, Ctrl-Alt-BkSp,
Ctrl-Alt-F1, and ssh from an othe
Op maandag 3 september 2007 23:06, schreef Sune Vuorela:
> On Monday 03 September 2007, Bert Verbeek wrote:
> > Package: kscreensaver
> > Version: 4:3.5.7-1
> > Severity: normal
> >
> >
> > Since my last update of my Debian testing, the scripting option
Package: kscreensaver
Version: 4:3.5.7-1
Severity: normal
Since my last update of my Debian testing, the scripting option of the
Phosphor screensaver stopped working. It is not available in the
KDE Control Center anymore. Can you add it again?
Thanks in advance,
Bert Verbeek
-- System
="yes", RUN+="/bin/sh -c 'test -e
/sys/$env{DEVPATH}/power/level && echo on >
/sys/$env{DEVPATH}/power/level'"
But after plugging in the device no 'level' entry exists in the /sys/
tree for the device, as far as I can see. So this solution is n
Hello Justin,
My last report on this 'bug' ;-)
Some weeks ago, my keyboard 'fortunately' started to fail occasionally on some
keys in a terminal as well. Changing to a different keyboard solved this
problem.
The firefox problem is gone as well, that re-appeared sometimes during the
last six
On Thursday 20 April 2006 17:03, Justin Pryzby wrote:
> I would suggest to use some window manager which supports "shading",
> and then you can avoid the "mouse" events
> and only send a single "focus" event, then some keyboard activity,
> then an "unfocus" to kill strace.
>
> BTW, does it r
On Sunday 02 April 2006 00:39, Eric Dorland wrote:
>
> It's not a general problem with the keyboard? Ie you only see it with
> firefox?
No, all other apps are working fine, that's the weird thing.
> Do you have any other machines you can reproduce this on?
I'm trying at the moment on another At
Package: firefox
Version: 1.5.dfsg+1.5.0.1-3
Severity: grave
Justification: renders package unusable
I have a weird problem with firefox 1.0.7/1.5 for some time now. It makes the
program totally unusable for me at the moment.
The problem:
Alphabetic/numeric keyboard entries are not arriving i
28 matches
Mail list logo
