Ubuntu
bamf package

bamfdaemon crashed with SIGSEGV in g_type_create_instance()

Bug #602519 reported by Noccy
72
This bug affects 10 people
Affects Status Importance Assigned to Milestone
BAMF
Fix Released
Undecided
Jason Smith
bamf (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Popped up twice.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: bamfdaemon 0.2.32-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Uname: Linux 2.6.35-6-generic i686
Architecture: i386
Date: Wed Jul 7 04:10:26 2010
ExecutablePath: /usr/lib/bamf/bamfdaemon
ProcCmdline: /usr/lib/bamf/bamfdaemon
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x8052d57: mov (%edx),%eax
 PC (0x08052d57) ok
 source "(%edx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: bamf
StacktraceTop:
 ?? ()
 g_type_create_instance () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_object_newv () from /usr/lib/libgobject-2.0.so.0
 g_object_new () from /usr/lib/libgobject-2.0.so.0
Title: bamfdaemon crashed with SIGSEGV in g_type_create_instance()
UserGroups: adm admin cdrom dialout lpadmin plugdev pulse-access sambashare

Related branches

lp:ubuntu/maverick/bamf
Revision history for this message
Noccy (noccy) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 bamf_matcher_init (self=0x9b69470) at bamf-matcher.c:583
 g_type_create_instance (type=162985976)
 g_object_constructor (type=162985976,
 g_object_newv (object_type=162985976, n_parameters=0,
 g_object_new (object_type=162985976,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.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
Sebastien Bacher (seb128)
visibility: private → public
Revision history for this message
Jason Smith (jassmith) wrote :

*NULL == bad idea.

Fixed, thank you for the report. Temporary workaround can be provided by ensuring that $XDG_DATA_DIRS is properly set in your environment. I did not properly guard when this is NULL.

Changed in bamf:
assignee: nobody → Jason Smith (jassmith)
status: New → Fix Committed
Sebastien Bacher (seb128)
Changed in bamf:
status: Fix Committed → Fix Released
Changed in bamf (Ubuntu):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bamf - 0.2.44-0ubuntu1

---------------
bamf (0.2.44-0ubuntu1) maverick; urgency=low

  * New upstream release:
    - Fix potential NULL deref when XDG_DATA_DIRS is not set
      (lp: #602519)
  * debian/control:
    - updated for the new vala versioning
  * debian/libbamf0.symbols:
    - new version update
 -- Sebastien Bacher <email address hidden> Thu, 19 Aug 2010 19:16:15 +0200

Changed in bamf (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in bamf (Ubuntu Quantal):
status: New → Confirmed
Adolfo Jayme Barrientos (fitojb)
no longer affects: bamf (Ubuntu Quantal)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.