bamfdaemon crashed with SIGSEGV in g_type_interfaces()

Bug #1059188 reported by klaipedetis
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bamf (Ubuntu)
New
Undecided
Unassigned

Bug Description

?

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: bamfdaemon 0.3.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.5.3-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sun Sep 30 20:21:50 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/bamf/bamfdaemon
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120926)
ProcCmdline: /usr/lib/bamf/bamfdaemon
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb6ea7850 <g_type_interfaces+208>: mov 0x4(%esi),%eax
 PC (0xb6ea7850) ok
 source "0x4(%esi)" (0x09fa9000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: bamf
StacktraceTop:
 g_type_interfaces () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_by_name () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 bamf_view_close ()
 ?? ()
 ?? () from /usr/lib/i386-linux-gnu/libunity-webapps.so.0
Title: bamfdaemon crashed with SIGSEGV in g_type_interfaces()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
klaipedetis (voron-68) 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 #1058764, 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
tags: removed: need-i386-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.