simple-scan crashed with SIGSEGV in g_closure_invoke()

Bug #920578 reported by T Loften
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
simple-scan (Ubuntu)
New
Undecided
Unassigned

Bug Description

When you press the button to start scanning ( simple scan ) 50/50 will clash with Gemtek WUBR-177G [Ralink RT2571W]... both usb devices will crash and stop working ... .... Need to re-start before the will start working again .

below is - ls usb

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 045e:075d Microsoft Corp. LifeCam Cinema
Bus 001 Device 004: ID 04a9:1717 Canon, Inc. MP510 <----- Scanner
Bus 001 Device 005: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 001 Device 006: ID 15a9:0004 Gemtek WUBR-177G [Ralink RT2571W] <----- Wifi Card
Bus 003 Device 002: ID 045e:0707 Microsoft Corp. Wireless Laser Mouse 8000
Bus 003 Device 003: ID 045e:0717 Microsoft Corp.
Bus 003 Device 004: ID 045e:0714 Microsoft Corp.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: simple-scan 3.2.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.2.0-10-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Jan 23 12:43:08 2012
DriverPackageVersions:
 libsane 1.0.22-7ubuntu1
 libsane-extras N/A
 hplip 3.11.12-2
 hpoj N/A
ExecutablePath: /usr/bin/simple-scan
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: HP Pavilion 061 EX259AA-ABA s7520n
ProcCmdline: simple-scan
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-10-generic root=UUID=8bfe9424-39f2-40ab-802d-f39fbf07a15a ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x415a8a: movl $0x1,0x18(%rax)
 PC (0x00415a8a) ok
 source "$0x1" ok
 destination "0x18(%rax)" (0xaaaaaaaaaaaaaac2) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: simple-scan
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_by_name () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: simple-scan crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to precise on 2012-01-19 (3 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 03/14/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 3.04
dmi.board.name: Opal
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 1.02
dmi.chassis.type: 3
dmi.chassis.version: 1111
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr3.04:bd03/14/2006:svnHPPavilion061:pnEX259AA-ABAs7520n:pvr0nx1104RE101OPAL00:rvnASUSTekComputerINC.:rnOpal:rvr1.02:cvn:ct3:cvr1111:
dmi.product.name: EX259AA-ABA s7520n
dmi.product.version: 0nx1104RE101OPAL 00
dmi.sys.vendor: HP Pavilion 061

Revision history for this message
T Loften (tloften) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #843361, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
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.