simple-scan crashed with SIGSEGV in g_thread_create_proxy()

Bug #521070 reported by Brian Murray
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
simple-scan (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: simple-scan

I had scanned a document as text and then went on to scan again but this time as a photo when simple-scan crashed. My scanner is actually connected to another system and I'm using sane to connect to it. Here are some messages from the server's syslog file:

Feb 12 08:22:20 bizarro saned[5645]: check_host: access by remote host: ::ffff:192.168.10.2
Feb 12 08:22:20 bizarro saned[5645]: init: access granted to saned-user@::ffff:192.168.10.2
Feb 12 08:22:28 bizarro saned[5645]: process_request: bad status 22
Feb 12 08:22:28 bizarro saned[5645]: quit: exiting
Feb 12 08:22:39 bizarro saned[5647]: check_host: access by remote host: ::ffff:192.168.10.2
Feb 12 08:22:39 bizarro saned[5647]: init: access granted to saned-user@::ffff:192.168.10.2
Feb 12 08:22:48 bizarro saned[5647]: quit: exiting

ProblemType: Crash
Architecture: amd64
Date: Fri Feb 12 08:22:25 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/simple-scan
Package: simple-scan 0.8.2-0ubuntu1
ProcCmdline: simple-scan
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
SegvAnalysis:
 Segfault happened at: 0x40e58b: mov (%rax),%rdi
 PC (0x0040e58b) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: simple-scan
StacktraceTop:
 ?? ()
 g_thread_create_proxy (data=0xf9a4d0)
 start_thread (arg=<value optimized out>)
 clone ()
 ?? ()
Title: simple-scan crashed with SIGSEGV in g_thread_create_proxy()
Uname: Linux 2.6.32-13-generic x86_64
UserGroups: adm admin audio cdrom dialout dip family floppy fuse libvirtd lpadmin plugdev pulse pulse-access sambashare sbuild scanner video

Revision history for this message
Brian Murray (brian-murray) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote :

I had to end up unplugging the scanner's usb cable and replugging it in to get this working again.

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 scan_thread (scanner=0xe1c520) at scanner.c:759
 ?? () from /lib/libglib-2.0.so.0
 start_thread () from /lib/libpthread.so.0
 clone ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in simple-scan (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Robert Ancell (robert-ancell) wrote :

Does this still occur in simple-scan 0.9.4?

Changed in simple-scan (Ubuntu):
status: New → Incomplete
visibility: private → public
Revision history for this message
Brian Murray (brian-murray) wrote :

I tested it with 0.9.5-1ubuntu1 and it did not crash. Thanks!

Changed in simple-scan (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
nico (ponte-nicolas) wrote :

?????

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.