Well, I still don't know much more ;-)
However, I did try to find out what is actually going on when
xscanimage crashes on startup:
It looks like there is a segfault occuring at the same position,
where otherwise the "** WARNING **: file gtkwidget.c: line 2813
..." warnings. Here's a backtrace:
Starting program: xscanimage umax:/dev/scanner
Program received signal SIGSEGV, Segmentation fault.
0x400a03fe in gtk_real_widget_queue_draw (widget=0x80a41a0) at gtkwidget.c:2813
(gdb) bt
#0 0x400a03fe in gtk_real_widget_queue_draw (widget=0x80a41a0) at gtkwidget.c:2813
#1 0x40055e91 in gtk_idle_invoke_function (idlef=0x80a3388) at gtkmain.c:903
#2 0x40055f49 in gtk_handle_idle () at gtkmain.c:934
#3 0x40055134 in gtk_main_iteration () at gtkmain.c:377
#4 0x40054d50 in gtk_main () at gtkmain.c:377
#5 0x804e962 in interface (argc=2, argv=0xbffff254) at xscanimage.c:1652
#6 0x804e9d6 in main (argc=2, argv=0xbffff254) at xscanimage.c:1681
#7 0x804c30e in ___crt_dummy__ ()
These crashes don't occur every time the program is started and
seem to occur more often, when the device is given on the command
line than when the device is selected in the dialog. Could there
be some sort of race condition somewhere?
Maybe, somebody else knows more ...
Peter
--
| Peter Daum (gator@cs.tu-berlin.de) __o (+49 30)
| http://www.cs.tu-berlin.de/~gator _'\<_ 691 46 35
| pgp messages welcome! _(_)/(_) ___________
--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com