[ Resent to the sane-devel list because moderator approval is required for emails this big - I've now removed the log file contents ]
On Sunday, October 12, 2003, at 05:14 PM, Karl Heinz Kremer wrote: > Terry, > > I'm still waiting for the log output with SANE_DEBUG_EPSON=128 > > From the xsane log, it looks like xsane has a problem with the > resolution list, but it;s not clear why, and if the backend plays a > role in this crash. > > If you want us to resolve this problem, please provide all the > information that is requested. > > I will try to CC all relevant emails to you, but I cannot promise that > I will always remember. The list archives are online, so even if you > are not subscribed to the list, you can follow the discussion. > > Karl Heinz > > > On Saturday, October 11, 2003, at 04:52 PM, Terry Boldt wrote: > >> Sending this message to the mailing list as you requested. >> >> I am requesting that any resoultion to the problem or discussion of >> the prolem >> be 'cc' to me since I do not subscribe to the sane mailing list. If >> you >> insist I will subscribe, but would rather not since my mail box is >> getting >> full already and I am trying to keep the input managable. >> >> Please do overlook the question on the "copy" function after the >> xsane debug >> output and the gdb back trace output. >> >> I am far from an expert on these matters, but from the xsane output >> and the >> gdb backtrace output, it would appear that the problem is in xsane. >> But that >> is my guess based on ignorance of the issue. >> >> On Friday 10 October 2003 21:11, you wrote: >>> Try to delete the file ~/.sane/xsane/EPSON:<your scanner name>.drc >>> and >>> give it >>> another try. >> >> No effect whatsoever. It is the presence of the 'xsane.rc' file that >> is >> causing the problems. This file causes a seg fault if I attempt to >> use the >> Epson Perfection 1660 Photo scanner with the libsane-epson backend. I >> can use >> the HP laserJet 1220 scanner no problems whatsoever. >> >> It is only after the message box displays that it is scaning for >> devices. It >> then displays both scanners for me to choose from. If I choose the HP >> LaserJet 1220, it continues no problem. If I choose the "Epson GT-8300 >> Flatbed scanner [Epson:/dev/usb/scanner0]" option, then it seg >> faults when >> xsane.rc is present. >> >> ran >> >> export XSANE_DEBUG=128 >> xsane > /tmp/xsane.log 2>&1 >> >> The output is below: >> [ ... log file content removed ] >> ---------------------------------------------------------------------- >> ---------------------------------------------- >> ran gdb xsane and executed backtrace on seg fault. The output follows: >> >> >> Program received signal SIGSEGV, Segmentation fault. >> 0x42079318 in strcmp () from /lib/i686/libc.so.6 >> (gdb) bt >> #0 0x42079318 in strcmp () from /lib/i686/libc.so.6 >> #1 0x08054183 in xsane_option_menu_lookup (menu_items=0x81d9330, >> string=0xbfffe020 "50") at xsane-front-gtk.c:908 >> #2 0x080544ab in xsane_option_menu_new (parent=0x81d9330, >> str_list=0x81d6af8, >> val=0xbfffe020 "50", option_number=136167224, >> desc=0x80b2ea1 "Set scan resolution", >> option_menu_callback=0x808d0bc, >> settable=1, widget_name=0x81b9d70 "") at xsane-front-gtk.c:998 >> #3 0x080545d2 in xsane_option_menu_new_with_pixmap (window=0x8100520, >> parent=0x81d07a8, xpm_d=0x80bb020, desc=0x80b2ea1 "Set scan >> resolution", >> str_list=0x81d6af8, val=0xbfffe020 "50", data=0xbfffe018, >> option=10, >> option_menu_callback=0x808d0bc, settable=1, >> widget_name=0x80b2dc9 "GtkMenuResolution") at >> xsane-front-gtk.c:1031 >> #4 0x0808d3cc in xsane_resolution_widget_new (parent=0x81d07a8, >> well_known_option=10, resolution=0x80bca14, image_xpm=0x80bb020, >> desc=0x80b2ea1 "Set scan resolution", >> widget_name=0x80b2dc9 "GtkMenuResolution") at xsane.c:1221 >> #5 0x0808f46f in xsane_update_xsane_callback () at xsane.c:1702 >> #6 0x0809afb4 in xsane_panel_build () at xsane.c:6827 >> #7 0x0809cf9c in xsane_device_dialog () at xsane.c:7273 >> #8 0x403e4d01 in g_cclosure_marshal_VOID__VOID () >> from /usr/lib/libgobject-2.0.so.0 >> #9 0x403d00c0 in g_closure_invoke () from >> /usr/lib/libgobject-2.0.so.0 >> #10 0x403e48b4 in signal_emit_unlocked_R () from >> /usr/lib/libgobject-2.0.so.0 >> #11 0x403e3888 in g_signal_emit_valist () from >> /usr/lib/libgobject-2.0.so.0 >> #12 0x401a3fdf in gtk_signal_emit () from /usr/lib/libgtk-x11-2.0.so.0 >> #13 0x400d79e2 in gtk_button_clicked () from >> /usr/lib/libgtk-x11-2.0.so.0 >> #14 0x400d89ab in gtk_real_button_released () from >> /usr/lib/libgtk-x11-2.0.so.0 >> #15 0x403e4d01 in g_cclosure_marshal_VOID__VOID () >> from /usr/lib/libgobject-2.0.so.0 >> #16 0x403d0467 in g_type_class_meta_marshal () >> from /usr/lib/libgobject-2.0.so.0 >> #17 0x403d00c0 in g_closure_invoke () from >> /usr/lib/libgobject-2.0.so.0 >> #18 0x403e413f in signal_emit_unlocked_R () from >> /usr/lib/libgobject-2.0.so.0 >> #19 0x403e3888 in g_signal_emit_valist () from >> /usr/lib/libgobject-2.0.so.0 >> #20 0x401a3fdf in gtk_signal_emit () from /usr/lib/libgtk-x11-2.0.so.0 >> #21 0x400d7932 in gtk_button_released () from >> /usr/lib/libgtk-x11-2.0.so.0 >> #22 0x400d882b in gtk_button_button_release () >> from /usr/lib/libgtk-x11-2.0.so.0 >> #23 0x401610e4 in _gtk_marshal_BOOLEAN__BOXED () >> from /usr/lib/libgtk-x11-2.0.so.0 >> #24 0x403d0467 in g_type_class_meta_marshal () >> from /usr/lib/libgobject-2.0.so.0 >> #25 0x403d00c0 in g_closure_invoke () from >> /usr/lib/libgobject-2.0.so.0 >> #26 0x403e4369 in signal_emit_unlocked_R () from >> /usr/lib/libgobject-2.0.so.0 >> #27 0x403e3689 in g_signal_emit_valist () from >> /usr/lib/libgobject-2.0.so.0 >> #28 0x401a3fdf in gtk_signal_emit () from /usr/lib/libgtk-x11-2.0.so.0 >> #29 0x40247413 in gtk_widget_event_internal () >> from /usr/lib/libgtk-x11-2.0.so.0 >> #30 0x40160e67 in gtk_propagate_event () from >> /usr/lib/libgtk-x11-2.0.so.0 >> #31 0x4015fb45 in gtk_main_do_event () from >> /usr/lib/libgtk-x11-2.0.so.0 >> #32 0x40311f21 in gdk_event_dispatch () from >> /usr/lib/libgdk-x11-2.0.so.0 >> #33 0x40426f65 in g_main_dispatch () from /usr/lib/libglib-2.0.so.0 >> #34 0x40427f98 in g_main_context_dispatch () from >> /usr/lib/libglib-2.0.so.0 >> #35 0x404282ad in g_main_context_iterate () from >> /usr/lib/libglib-2.0.so.0 >> #36 0x40428a1f in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 >> #37 0x4015f39f in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 >> #38 0x0809eac5 in xsane_interface (argc=1, argv=0xbffff8f4) at >> xsane.c:7946 >> #39 0x0809f1b4 in main (argc=1, argv=0xbffff8f4) at xsane.c:8133 >> #40 0x420158d4 in __libc_start_main () from /lib/i686/libc.so.6 >> >> ---------------------------------------------------------------------- >> --------------------------------------------------------- >> >> Do you have any idea what is causing the cropping of the image when >> printed. I >> had tried this before only using the Epson scanner. Tried again with >> the HP >> LaserJet 1220. Same thing, the side of the iamge gets cut off and not >> printed. I can save to a file and the whole image selected in the >> preview >> window is there and I can then print using GIMP and the whole image is >> printed. Just printing from xsane is the problem. >> >> Any ideas? >> >> ---------------------------------------------------------------------- >> -------------------------------------------------------- >>> >>> Also, try to find Henning's reply either in the mailing list >>> archives, >>> or your inbox. >>> And please, the next time send your messages to the Sane mailing >>> list. >> >> Ok. >> >>> >>> Karl Heinz >>> >>> On Friday, October 10, 2003, at 07:52 PM, Terry Boldt wrote: >>>> An update on my experiments with xsane and xscanimage. I just sent >>>> the >>>> following message to the xsane developer: >>>> -------------------------------------------------------------------- >>>> --- >>>> --------------------------------- >>>> >>>> Okay - I have conducted the tests with xscanimage and xsane. The >>>> results: >>>> >>>> If I invoke xsane twice with the libsane-epson backend, on the >>>> second >>>> invokation I get a seg fault. I have to delete the xsane.rc file to >>>> invoke a >>>> second (or more) time. If I switch to the libsane-epkowa backend, no >>>> problem. >>>> >>>> There is no such problem with xscanimage. I can invoke xscanimage as >>>> many >>>> times as desired with either the libsane-epson or the libsane-epkowa >>>> backends, no problems. >>>> >>>> I will report these findings to the sane develovers also. I have no >>>> idea if >>>> the prblem is in xsane, sane or libsane-epson. >>>> >>>> One other problem that is cropping up. If I use the "copy" function >>>> and print >>>> to my HP Deskjet 3820 inkjet printer, the left side of the image is >>>> cropped. >>>> If I save the image, the full image is saved and I can then print it >>>> from >>>> GIMP no problem. >>>> >>>> This problem persists using either libsane-epson or libsane-epkowa >>>> backends. I >>>> am guessing (based on my vast ignorance of the code) that the >>>> problem >>>> is >>>> probably in sane and not xsane. >>>> >>>> Regards, >>>> Terry D. Boldt >>>> -------------------------------------------------------------------- >>>> --- >>>> --------------------------------- >>>> >>>> >>>> I hope this added information is helpful. If there is more >>>> information >>>> that >>>> you desire, let me know and I will do my very best to obtain it and >>>> send to >>>> you. If it is not obvious how to obtain the information or it >>>> requires >>>> special techniques, you may have to send me the steps to follow to >>>> obtain it, >>>> however. >>>> >>>> Regards, >>>> Terry D. Boldt >>>> >>>> On Friday 10 October 2003 07:07, you wrote: >>>>>> Yesterday I upgraded to sane 1.0.12 and xsane 0.92. Experienced >>>>>> seg >>>>>> faults when invoking xsane. I commented out "epson" in dll.conf >>>>>> and >>>>>> added "epkowa". This forced sane to use the Epson Kowa backend >>>>>> libsane-epkowa. Seg faults ceased. The Epson Kowa backend to sane >>>>>> works >>>>>> great. You might try and see if they will allow it to be >>>>>> distributed >>>>>> with sane. It is GPL or an approved variant I believe. >>>>>> >>>>>> Running RH 8.0 with Kernal 2.4.18-17.8.0 >>>>>> >>>>>> and gcc 3.2.2 to compile all source (sane, xsane and Epson Kowa >>>>>> source). >>>>> >>>>> From the last line I gather that you did compile Sane 1.0.12 >>>>> yourself >>>>> and >>>>> did not install an RPM package. >>>>> >>>>> Can you (in addition to the information that Henning already >>>>> requested), >>>>> also send the contents of your epson.conf file. Also, are you using >>>>> the scanner kernel module (scanner.o) or libusb? >>>>> >>>>> When you upgraded, did you remove the old Sane version? Which >>>>> version >>>>> were you running before? Was this also compiled by yourself, or did >>>>> you >>>>> replace Red Hat's packaged version? >>>>> >>>>> I've never heard about a crash with 1.0.12 before, so please >>>>> provide >>>>> as much information as you can. >>>>> >>>>> Karl Heinz >> >> >> _______________________________________________ >> sane-devel mailing list >> sane-devel@lists.alioth.debian.org >> http://lists.alioth.debian.org/mailman/listinfo/sane-devel >
