Ubuntu
baobab package

baobab crashed with SIGSEGV in g_strdup() after clicking About

Bug #1020810 reported by installshield_freak
76
This bug affects 10 people
Affects Status Importance Assigned to Milestone
baobab
Fix Released
Medium
baobab (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Steps to reproduce:

Go into baobab and Click in the Global menu and navigate to About: The program abruptly closes and throws an error.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: baobab 3.5.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5
Uname: Linux 3.5.0-3-generic i686
ApportVersion: 2.2.5-0ubuntu2
Architecture: i386
Date: Tue Jul 3 22:48:24 2012
ExecutablePath: /usr/bin/baobab
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120627)
ProcCmdline: baobab
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6bb6616: movdqu (%edi),%xmm1
 PC (0xb6bb6616) ok
 source "(%edi)" (0x00004e14) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: baobab
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 g_strdup () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_strdupv () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: baobab crashed with SIGSEGV in g_strdup()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
installshield_freak (installshield-freak) wrote :
visibility: private → public
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thanks for reporting this issue and making Ubuntu better.

I was able to reproduce this issue with baobab 3.5.3-0ubuntu1 on Ubuntu Quantal, by following the instructions above.

Hans Joachim Desserud (hjd)
Changed in baobab (Ubuntu):
status: New → Confirmed
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_strdup (str=0x4e14 <Address 0x4e14 out of bounds>) at /build/buildd/glib2.0-2.33.3/./glib/gstrfuncs.c:355
 g_strdupv (str_array=0x806d600) at /build/buildd/glib2.0-2.33.3/./glib/gstrfuncs.c:2431
 _g_type_boxed_copy (type=160108992, value=0x806d600) at /build/buildd/glib2.0-2.33.3/./gobject/gtype.c:4237
 boxed_proxy_collect_value (value=0xbfd04478, n_collect_values=1, collect_values=0xbfd044a0, collect_flags=0) at /build/buildd/glib2.0-2.33.3/./gobject/gboxed.c:229
 g_object_set_valist (object=0x9907180, first_property_name=first_property_name@entry=0x8061b06 "program-name", var_args=0xbfd04594 "\247\032\006\b\247\032\006\b", var_args@entry=0xbfd04558 "\240\032\006\b\367\032\006\b\264\377\005\b\357\032\006\b\343\376\005\b\346\032\006\b\374\036\006\b\334\032\006\b #\006\b\317\032\006\b\002") at /build/buildd/glib2.0-2.33.3/./gobject/gobject.c:1942

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 baobab (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Jeremy Bícha (jbicha)
summary: - baobab crashed with SIGSEGV in g_strdup()
+ baobab crashed with SIGSEGV in g_strdup() after clicking About
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Thank you for taking the time to report this bug and help make Ubuntu better!

I am no longer able to duplicate this bug with baobab 3.5.92-0ubuntu1. Please try this version and report back whether you're still experiencing this bug or not.

Changed in baobab (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

I am still able to reproduce this issue with baobab 3.5.92-0ubuntu1 on an up to date Quantal system (i386).

Adolfo Jayme Barrientos (fitojb)
Changed in baobab (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :

This bug still exists in the baobab version present in the final quantal release, see bug #1065879.

Package: baobab 3.6.0-0ubuntu1

Sebastien Bacher (seb128)
Changed in baobab (Ubuntu):
status: Confirmed → In Progress
Bug Watch Updater (bug-watch-updater)
Changed in baobab:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package baobab - 3.6.2-0ubuntu2

---------------
baobab (3.6.2-0ubuntu2) raring; urgency=low

  * debian/control.in: build-depends on libgirepository1.0-dev
 -- Sebastien Bacher <email address hidden> Mon, 05 Nov 2012 18:57:04 +0100

Changed in baobab (Ubuntu):
status: In Progress → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in baobab:
status: New → Fix Released
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.