baobab crashed with SIGSEGV in g_strdup() after clicking About

[installshield_freak]

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

[Hans Joachim Desserud (hjd)]

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.

[Apport retracing service (apport)]

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

[Jeremy Bícha (jbicha)]

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.

[Hans Joachim Desserud (hjd)]

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

[Laurent Bonnaud (laurent-bonnaud)]

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

Package: baobab 3.6.0-0ubuntu1

[Launchpad Janitor (janitor)]

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