simple-scan-team team mailing list archive

[Tim Rupp <caphrim007@xxxxxxxxx>]

It seems random, but given enough scans, it almost always occurs.

It appears to happen right after a scan finishes and the page is/would
be displayed in the UI.

I only ever click the scan button. I do not crop, resize, rotate, etc
the image. I switch between text scanning and photo scanning depending
on the quality and size of the image that is output by each.

I've used the following scan settings

  - single page
  - photo
    - photo resolution 300 dpi
  - text
    - text resolution 300 dpi
  - scan side front and page
  - page size automatic

I think I can find an HP scanner that it should work with.

Are there any compilation options I can re-compile simplescan with that
would provide better insight? Debugger anything?

On 03/20/2012 06:20 AM, Michael Nagel wrote:
> Does the crash happen when performing a certain action in the program or is it more random?
> Do you have another scanner so you could test if it depends on the backend involved?
>

-- 
You received this bug notification because you are a member of Simple
Scan Development Team, which is the registrant for Simple Scan.
https://bugs.launchpad.net/bugs/947684

Title:
  Segmentation fault when scanning

Status in Simple Scan:
  New

Bug description:
  I have a Brother MFC-465CN. simple-scan is crashing periodically with
  the following backtrace from GDB

  
  Program received signal SIGSEGV, Segmentation fault.
  page_view_page_size_changed_cb (p=<optimized out>, self=0x7815d0) at page-view.c:4089
  4089		self->priv->update_image = TRUE;
  (gdb) bt
  #0  page_view_page_size_changed_cb (p=<optimized out>, self=0x7815d0) at page-view.c:4089
  #1  _page_view_page_size_changed_cb_page_size_changed (_sender=<optimized out>, self=<optimized out>) at page-view.c:224
  #2  0x00007ffff668e0a4 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #3  0x00007ffff66a002a in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #4  0x00007ffff66a96b1 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #5  0x00007ffff66a9a3d in g_signal_emit_by_name () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #6  0x00000000004129ba in page_set_page_info (self=0x781540, info=<optimized out>) at page.c:410
  #7  0x0000000000418e07 in application_scanner_page_info_cb (info=<optimized out>, scanner=<optimized out>, self=<optimized out>)
      at simple-scan.c:928
  #8  _application_scanner_page_info_cb_scanner_got_page_info (_sender=0x7815d0, info=0x7fffe837f240, self=0x781540) at simple-scan.c:458
  #9  0x00007ffff668e0a4 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #10 0x00007ffff66a002a in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #11 0x00007ffff66a96b1 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #12 0x00007ffff66a9a3d in g_signal_emit_by_name () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #13 0x000000000041f751 in scanner_notify_idle_cb (self=0x85be10) at scanner.c:3106
  #14 _scanner_notify_idle_cb_gsource_func (self=0x85be10) at scanner.c:3120
  #15 0x00007ffff63cda5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #16 0x00007ffff63ce258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #17 0x00007ffff63ce792 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #18 0x00007ffff78deedd in gtk_main () from /usr/lib/libgtk-3.so.0
  #19 0x000000000041ae7f in application_main (args=0x7fffffffe208, args_length1=1) at simple-scan.c:2214
  #20 0x00007ffff573d30d in __libc_start_main (main=0x40c450 <main>, argc=1, ubp_av=0x7fffffffe208, init=<optimized out>, 
      fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe1f8) at libc-start.c:226
  #21 0x000000000040c499 in _start ()

  
  I'd really like to figure out why and fix it.

  It crashes right after it finishes scanning a page

  I'm using 3.2.1 compiled from source.

  I notice there are several "optimized out" strings in there, so the
  backtrace may not be sufficient. If not, can someone inform me on the
  configure commands necessary to compile simple-scan to get the most
  useful debug information? Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/947684/+subscriptions