[sane-devel] Segfault with xscanimage but not with scanimage

My system is debian squeeze, my scanner is epson perfection 2400 Photo. >From an xwindow terminal both xsane and xscanimage terminate with a segmentation fault after the scanner is selected and the scan command is given but before the scanner actually runs. Both these programs will not fail when

[sane-devel] Segfault with Lide210

Hi there, stef wrote: > Le vendredi 23 septembre 2011 14:40:26, vous avez ?crit : > > Hi Stef, > > > > thanks again for the response! > > > > Here is the gdb output, hope that it helps: > > > > uli at pu:~/build/sane-1.0.22/sane-backends$ > > gdb ./frontend/.libs/scanimage > > GNU gdb 6.8-debia

[sane-devel] Segfault with Lide210

Le vendredi 23 septembre 2011 14:40:26, vous avez ?crit : > Hi Stef, > > thanks again for the response! > > Here is the gdb output, hope that it helps: > > uli at pu:~/build/sane-1.0.22/sane-backends$ > gdb ./frontend/.libs/scanimage > GNU gdb 6.8-debian > Copyright (C) 2008 Free Software Founda

[sane-devel] Segfault with Lide210

Hi Stef, thanks again for the response! Here is the gdb output, hope that it helps: uli at pu:~/build/sane-1.0.22/sane-backends$ gdb ./frontend/.libs/scanimage GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

[sane-devel] Segfault with Lide210

Le jeudi 22 septembre 2011 22:35:09 Uli Fouquet, vous avez ?crit : > Hi stef, > > stef wrote: > > Le jeudi 22 septembre 2011 11:58:21 Uli Fouquet, vous avez ?crit : > [snip] > > > > root at pu:~# scanimage -L > > > device `genesys:libusb:002:006' is a Canon LiDE 210 flatbed scanner > > > > > > S

[sane-devel] Segfault with Lide210

Hi stef, stef wrote: > Le jeudi 22 septembre 2011 11:58:21 Uli Fouquet, vous avez ?crit : [snip] > > root at pu:~# scanimage -L > > device `genesys:libusb:002:006' is a Canon LiDE 210 flatbed scanner > > > > Strange enough: a scan is performed, but the process finishes with a > > segfault: > >

[sane-devel] Segfault with Lide210

Le jeudi 22 septembre 2011 11:58:21 Uli Fouquet, vous avez ?crit : > Hi there, > > After purchasing a Canon Lide 210 scanner one week ago everything went > well. I compiled and installed Sane 1.0.22 from sources, fiddled a bit > around with the permission settings and scanning worked fine on my >

[sane-devel] Segfault with Lide210

Hi there, After purchasing a Canon Lide 210 scanner one week ago everything went well. I compiled and installed Sane 1.0.22 from sources, fiddled a bit around with the permission settings and scanning worked fine on my (otherwise outdated, I know) Ubuntu 8.04. Unfortunately, starting today, I get

[sane-devel] segfault in sane_net_get_devicesconnectingto network saned

m. allan noah gmail.com> writes: > > Please register for an account on alioth, and I will give you git > commit perms to maintain the brother.desc files. You will also want to > go thru the archives of this mailing list and find prior reports which > we have ignored, and stay subscribed to the l

[sane-devel] segfault in sane_net_get_devicesconnectingto network saned

m. allan noah gmail.com> writes: > > Nope. That is brother's problem. They don't support us, we don't > support them. :) Seriously? Just because Brother provide a binary only driver, you won't list their USB id's in the libsane udev rules (so that the USB device will get a working set of perm

[sane-devel] segfault in sane_net_get_devicesconnectingto network saned

m. allan noah gmail.com> writes: > > why not try running saned under xinetd, and see if it plays nicer? No go, but in just ensuring that xinetd was running the server, by using strace the problem had new light shone on it. The root issue seems to be a permissions issue on /usr/local/... brs

[sane-devel] segfault in sane_net_get_devicesconnectingto network saned

m. allan noah gmail.com> writes: > Hi, > Ok- let me first appologize if you took Julien the wrong way. You see, > any program that uses sane-backends is effectively pulling the > backends into it's running process, giving it all manner of options to > screw things up. Yes, understood, complete

[sane-devel] segfault in sane_net_get_devicesconnecting to network saned

Julien BLACHE jblache.org> writes: > > Hi, Hi, > Did you contact Brother asking them to contribute the code to their > driver to SANE? Of course I did, in the context of the printer driver. There was no point in talking about the scanner driver once they made their position on their "propr

[sane-devel] segfault in sane_net_get_devicesconnecting to network saned

Brian J. Murrell wrote: Hi, >> That's what you get for using a proprietary backend that isn't properly >> integrated in the system (udev/consolekit). > > So, is this just comment on the permissions issue or the the segfault -- which > is the original point of this report/thread? [X] All of the

[sane-devel] segfault in sane_net_get_devicesconnectingto network saned

On Tue, May 11, 2010 at 4:29 PM, Brian J. Murrell wrote: > m. allan noah gmail.com> writes: >> >> Nope. That is brother's problem. They don't support us, we don't >> support them. :) > > Seriously? ?Just because Brother provide a binary only driver, you won't list > their USB id's in the libsane

[sane-devel] segfault in sane_net_get_devicesconnectingto network saned

On Tue, May 11, 2010 at 4:02 PM, Brian J. Murrell wrote: > Thanx for all the help! No problem. Glad to help. > P.S. Can you add this printer: > > Bus 002 Device 002: ID 04f9:01e9 Brother Industries, Ltd > > to the list of printers in the udev rules file. ?It's a Brother DCP-7040. Nope. That is

[sane-devel] segfault in sane_net_get_devicesconnectingto network saned

why not try running saned under xinetd, and see if it plays nicer? allan On Tue, May 11, 2010 at 2:42 PM, Brian J. Murrell wrote: > m. allan noah gmail.com> writes: >> > > Hi, > >> Ok- let me first appologize if you took Julien the wrong way. You see, >> any program that uses sane-backends is

[sane-devel] segfault in sane_net_get_devicesconnecting to network saned

Ok- let me first appologize if you took Julien the wrong way. You see, any program that uses sane-backends is effectively pulling the backends into it's running process, giving it all manner of options to screw things up. In the absence of source code, it can be very difficult to identify the culpr

[sane-devel] segfault in sane_net_get_devicesconnecting to network saned

Julien BLACHE jblache.org> writes: > > Hi, Hi, > That's what you get for using a proprietary backend that isn't properly > integrated in the system (udev/consolekit). So, is this just comment on the permissions issue or the the segfault -- which is the original point of this report/thread? >

[sane-devel] segfault in sane_net_get_devices connecting to network saned

Brian J. Murrell wrote: Hi, > FWIW, this is just a perennial, frustratingly-in-every-release-of-Ubuntu > permission problem. If I run xsane as root, it works just fine, to the local > device that is, as proof that the brscan3 driver works at least. That's what you get for using a proprietary

[sane-devel] segfault in sane_net_get_devices connecting to network saned

Brian J. Murrell interlinx.bc.ca> writes: > > Well, it did back when I posted the original message here. Since then > I have upgraded to Ubuntu Lucid and now I just get a USB error in a dialog. FWIW, this is just a perennial, frustratingly-in-every-release-of-Ubuntu permission problem. If I

[sane-devel] segfault in sane_net_get_devices connecting to network saned

m. allan noah gmail.com> writes: > > more data: which driver is in use on scanner server, It's the "brscan3" /usr/lib/sane/libsane-brother3.so.1.0.7 driver. > and is it the > same version of sane-backends? I'd assume so. > also, what happens if you connect to > localhost saned on the server?

[sane-devel] segfault in sane_net_get_devices connecting to network saned

more data: which driver is in use on scanner server, and is it the same version of sane-backends? also, what happens if you connect to localhost saned on the server? allan On Thu, May 6, 2010 at 3:58 PM, Brian J. Murrell wrote: > Using sane 1.0.20 on Ubuntu Karmic, when I try to connect to a sc

[sane-devel] segfault in sane_net_get_devices connecting to network saned

Using sane 1.0.20 on Ubuntu Karmic, when I try to connect to a scanner provided over the network by another machine running saned, xsane gets a segfault with the following stack trace: #0 sane_net_get_devices (device_list=0xbfffce9c, local_only=0) at net.c:1263 #1 0x00131e92 in sane_dll_get_dev

[sane-devel] Segfault with xsane-0.96

On Sun, 2004-09-05 at 09:20, Oliver Rauch wrote: > Am Sam, 2004-09-04 um 20.56 schrieb Vitaly Lipatov: > > On Saturday 04 September 2004 19:53, Henning Meier-Geinitz wrote: > > > Hi, > > > > > > On Sat, Sep 04, 2004 at 06:09:56PM +0400, Vitaly Lipatov wrote: > > > > When I try run xsane-0.96-pre1 w

[sane-devel] Segfault with xsane-0.96

Am Sam, 2004-09-04 um 20.56 schrieb Vitaly Lipatov: > On Saturday 04 September 2004 19:53, Henning Meier-Geinitz wrote: > > Hi, > > > > On Sat, Sep 04, 2004 at 06:09:56PM +0400, Vitaly Lipatov wrote: > > > When I try run xsane-0.96-pre1 with old settings in > > > .sane/xsane, I get an Segmentation

[sane-devel] Segfault with xsane-0.96

Vitaly Lipatov wrote: >> http://www.xsane.org/ >> "Latest news". It's a known issue. > It is too hard to explain it to users. Can we have some > workaround? SegFault is a bad way to recommend users remove old > settings. It's on the todo list. JB. -- Julien BLACHE

[sane-devel] Segfault with xsane-0.96

On Saturday 04 September 2004 19:53, Henning Meier-Geinitz wrote: > Hi, > > On Sat, Sep 04, 2004 at 06:09:56PM +0400, Vitaly Lipatov wrote: > > When I try run xsane-0.96-pre1 with old settings in > > .sane/xsane, I get an Segmentation fault. ... > http://www.xsane.org/ > "Latest news". It's a known

[sane-devel] Segfault with xsane-0.96

When I try run xsane-0.96-pre1 with old settings in .sane/xsane, I get an Segmentation fault. Backtrace from gdb: #0 0x0806872c in preview_create_preset_area_menu () #1 0x08069f92 in preview_new () #2 0x080b3ea8 in xsane_device_dialog () Will I send my configuration file for example? -- Lav Vi

[sane-devel] Segfault with xsane-0.96

Hi, On Sat, Sep 04, 2004 at 06:09:56PM +0400, Vitaly Lipatov wrote: > When I try run xsane-0.96-pre1 with old settings in .sane/xsane, > I get an Segmentation fault. > Backtrace from gdb: > #0 0x0806872c in preview_create_preset_area_menu () > #1 0x08069f92 in preview_new () > #2 0x080b3ea8 in

[sane-devel] segfault when using transparency unit with epson

Hi, I've upgraded to 1.0.11, this indeed solved the problem. Thanks a lot! regards, Markus Henning Meier-Geinitz writes: > Hi, > > On Sat, Mar 29, 2003 at 09:26:05PM +0100, Markus Hoenicka wrote: > > Is this a known problem? Would upgrading to the "unstable" branch > > (1.0.10-1) help? >

[sane-devel] segfault when using transparency unit with epson

Hi, On Sat, Mar 29, 2003 at 09:26:05PM +0100, Markus Hoenicka wrote: > Is this a known problem? Would upgrading to the "unstable" branch > (1.0.10-1) help? I don't know, but there are backported SANE packages for Woody (1.0.11): http://people.debian.org/~aurel32/sane.html Bye, Henning

[sane-devel] segfault when using transparency unit with epson

Hi, I've just plugged in an Epson 1200 SCSI scanner with a transparency unit. The computer runs Debian 3.0 with sane 1.0.7-2.1 and the other sane components from the "stable" branch. Scanning without the transparency unit works fine from xsane and xscanimage. However, as soon as I try to use the t

[sane-devel] segfault while canceling (mustek/scsi)

Hi, [responding to myself:] On Mon, Mar 03, 2003 at 12:38:28AM +0100, Henning Meier-Geinitz wrote: > The crash happens with different Mustek SCSI scanners. So it sure > looks like a mustek backend problem. Finally, the reason for the bug is known: it's in sanei_scsi.c, function sanei_scsi_flush_

[sane-devel] segfault while canceling (mustek/scsi)

Hi, I'm have been hunting a bug for quite some time now. Silvio Vogt found out that cancelling a scan on Mustek SCSI scanners leads to a segmentation fault. I can reproduce this bug sometimes. It happens when scanning with a graphical frontend. When I scan and cancel that scan the frontend crashe

[sane-devel] segfault

Hi, On Thu, May 02, 2002 at 11:12:04PM -0400, Vladimir Dergachev wrote: > System: PIII-500mhz, One unsupported (yet) USB scanner. No supported usb > scanners. scanimage segfaults, gdb trace at the bottom of this e-mail. This one doesn't look like the usual crash in libusb. Nevertheless, please ch

[sane-devel] segfault

--2fSbKhQ/kwrfWINy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, May 02, 2002 at 11:12:04PM -0400, Vladimir Dergachev wrote: > Program received signal SIGSEGV, Segmentation fault. > sane_sm3600_init (version_code=0xb278, authCB=0x8049270 > ) > at sm3600.c:

[sane-devel] segfault

On Fri, 3 May 2002, Tim Waugh wrote: > On Thu, May 02, 2002 at 11:12:04PM -0400, Vladimir Dergachev wrote: > > > Program received signal SIGSEGV, Segmentation fault. > > sane_sm3600_init (version_code=0xb278, authCB=0x8049270 > > ) > > at sm3600.c:384 > > 384 DBG(DEBUG_JUNK,

[sane-devel] segfault

Hopefully this would be of use to somebody. System: PIII-500mhz, One unsupported (yet) USB scanner. No supported usb scanners. scanimage segfaults, gdb trace at the bottom of this e-mail. best Vladimir Dergachev --

[sane-devel] Segfault in snapscan

Hi, > The latest snapscan update in CVS leads to a segfault in sane_exit > everytime a use scanimage -L or any other frontend: Only on machines that don't have a SnapScan scanner attached >:-) Fixed in CVS now. Thanks, Oliver

[sane-devel] Segfault in snapscan

Hi, The latest snapscan update in CVS leads to a segfault in sane_exit everytime a use scanimage -L or any other frontend: hmg@hmg1:$ SANE_DEBUG_SNAPSCAN=255 scanimage -L [sanei_debug] Setting debug level of snapscan to 255. [snapscan] sane_snapscan_init [snapscan] sane_snapscan_init: Snapscan ba

[sane-devel] SEGFAULT in sanei_scsi_close()

Hi, On Mon, Dec 24, 2001 at 12:57:44PM -0500, Karl Heinz Kremer wrote: > I am trying to debug a problem with the EPSN backend. Whenever > the backend is running in batch mode to scan via the ADF, the > frontend will crash with a segmentation fault in sanei_scsi_close(). > > The reason seems to be

[sane-devel] SEGFAULT in sanei_scsi_close()

Karl Heinz Kremer wrote: > > I am trying to debug a problem with the EPSN backend. Whenever > the backend is running in batch mode to scan via the ADF, the > frontend will crash with a segmentation fault in sanei_scsi_close(). > > The reason seems to be that one for the free list elements is not

[sane-devel] SEGFAULT in sanei_scsi_close()

--OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I am trying to debug a problem with the EPSN backend. Whenever the backend is running in batch mode to scan via the ADF, the frontend will crash with a segmentation