simple-scan crashed with SIGSEGV in dbus_connection_dispatch()

[Colan Schwartz]

Left it running and found this crash report.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: simple-scan 3.6.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
Uname: Linux 3.8.0-26-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.2
Architecture: amd64
Date: Wed Jul 10 14:59:50 2013
DriverPackageVersions:
 libsane 1.0.23-0ubuntu1
 libsane-extras N/A
 hplip 3.13.3-1
 hpoj N/A
ExecutablePath: /usr/bin/simple-scan
InstallationDate: Installed on 2010-05-10 (1157 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
MarkForUpload: True
ProcCmdline: simple-scan
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-26-generic root=UUID=3c864589-1f17-472b-a1f3-cfd34aa59f84 ro splash
SegvAnalysis:
 Segfault happened at: 0x7fbc8fb46bed <dbus_connection_dispatch+829>: mov 0x8(%rdx),%rax
 PC (0x7fbc8fb46bed) ok
 source "0x8(%rdx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: simple-scan
StacktraceTop:
 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
 avahi_simple_poll_dispatch () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3
 avahi_simple_poll_loop () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3
 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3
Title: simple-scan crashed with SIGSEGV in dbus_connection_dispatch()
UpgradeStatus: Upgraded to raring on 2013-05-20 (51 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse logcheck lp lpadmin mail netdev plugdev powerdev sambashare tape vboxusers video
dmi.bios.date: 10/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FA
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 990FXA-UD3
dmi.board.vendor: AMD Corporation
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Apport retracing service (apport)]

StacktraceTop:
 dbus_connection_dispatch (connection=0x7fbc6c0969c0) at ../../dbus/dbus-connection.c:4623
 dispatch_timeout_callback (t=<optimized out>, userdata=0x7fbc6c0964f0) at ../avahi-common/dbus-watch-glue.c:105
 avahi_simple_poll_dispatch (s=s@entry=0x7fbc6c095ee0) at simple-watch.c:570
 avahi_simple_poll_iterate (s=s@entry=0x7fbc6c095ee0, timeout=timeout@entry=-1) at simple-watch.c:605
 avahi_simple_poll_loop (s=0x7fbc6c095ee0) at simple-watch.c:646

[Michael Nagel (nailor)]

did you attach/detach a scanner of another usb device during that period?
did your scanner go to / return from powersave mode?

[Colan Schwartz (colan)]

I don't have another USB scanner, but the power saving mode switching is possible as my device does that. It's a brother MFC-8480DN if that helps at all. I can't remember the exact details.

[Michael Nagel (nailor)]

can you try to reproduce it when your device goes powersave?

[penalvch (penalvch)]

Colan Schwartz, thank you for reporting this and helping make Ubuntu better.

As per https://wiki.ubuntu.com/Releases your release is EOL.

If you have an issue in a supported release (ex. 16.04) please file a new report, and feel free to subscribe me to it.