simple-scan crashed with SIGSEGV in g_object_unref()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
simple-scan (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Got this. I did not notice any crash.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: simple-scan 3.2.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Sat Oct 8 15:39:39 2011
DriverPackageVe
libsane 1.0.22-2ubuntu2
libsane-extras N/A
hplip 3.11.7-1ubuntu3
hpoj N/A
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
MachineType: Acer TravelMate 7750G
ProcCmdline: simple-scan
ProcEnviron:
PATH=(custom, no user)
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7fb00e3f4b70: mov (%rdi),%rax
PC (0x7fb00e3f4b70) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: simple-scan
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
g_object_unref () from /usr/lib/
?? ()
simple_scan_unref ()
Title: simple-scan crashed with SIGSEGV in g_object_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare vboxusers
dmi.bios.date: 05/19/2011
dmi.bios.vendor: Acer
dmi.bios.version: V1.09
dmi.board.
dmi.board.name: BA70_HR
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: TravelMate 7750G
dmi.product.
dmi.sys.vendor: Acer
visibility: | private → public |
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #870587, 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.