bamfdaemon crashed with SIGSEGV in g_type_interfaces()

Bug #1058764 reported by Rene
104
This bug affects 17 people
Affects Status Importance Assigned to Milestone
BAMF
New
High
Marco Trevisan (Treviño)
bamf (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Cannot provide specific details since I do not know what the bamfdaemon does. It crashed when i used the U1 music store web interface (artist search).

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
ApportVersion: 2.5.3-0ubuntu1
Architecture: i386
Date: Sat Sep 29 22:44:14 2012
ExecutablePath: /usr/lib/bamf/bamfdaemon
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120311)
ProcCmdline: /usr/lib/bamf/bamfdaemon
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb6f0b850 <g_type_interfaces+208>: mov 0x4(%esi),%eax
 PC (0xb6f0b850) ok
 source "0x4(%esi)" (0x0838f004) 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: Upgraded to quantal on 2012-09-29 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Rene (rene-ca) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_interfaces (type=type@entry=137838624, n_interfaces=n_interfaces@entry=0xbfcbb69c) at /build/buildd/glib2.0-2.34.0/./gobject/gtype.c:3581
 signal_id_lookup (itype=137838624, quark=<optimized out>) at /build/buildd/glib2.0-2.34.0/./gobject/gsignal.c:345
 signal_parse_name (detail_p=<synthetic pointer>, itype=137838624, name=0x8089353 "closed", force_quark=<optimized out>) at /build/buildd/glib2.0-2.34.0/./gobject/gsignal.c:1044
 signal_parse_name (force_quark=1, detail_p=<synthetic pointer>, itype=137838624, name=0x8089353 "closed") at /build/buildd/glib2.0-2.34.0/./gobject/gsignal.c:3374
 g_signal_emit_by_name (instance=instance@entry=0x8374110, detailed_signal=detailed_signal@entry=0x8089353 "closed") at /build/buildd/glib2.0-2.34.0/./gobject/gsignal.c:3385

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in bamf (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bamf (Ubuntu):
status: New → Confirmed
visibility: private → public
Changed in bamf (Ubuntu):
importance: Medium → High
Changed in bamf:
importance: Undecided → High
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
Revision history for this message
Blaž Triglav (blaztriglav) wrote :

Just to add a piece of information, for me this is only happening on laptops I upgraded directly from 12.04 to 12.10. On a clean install, this bug does not happen.

Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :

Mh, it seems caused by the webapps, but I can't easily riproduce it nor I see evident issues on the codepath.

I hope to investigate further on it.

Revision history for this message
Blaž Triglav (blaztriglav) wrote :

Yes, in my case it is webapps as well, gmail is unusable, the error pops up after a minute or so of using it and the entire OS slows down to a crawl, menus stop working and at least a log-out/log-in or a restart is required to get the system operational again.

The vast majority of the time I don't even manage to send an error report because the OS just stops responding.

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.