baobab crashed with SIGSEGV in g_utf8_validate()

Bug #284923 reported by smmalis37
36
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-utils
Fix Released
Critical
gnome-utils (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-utils

Launching baobab causes immediate segfault.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/baobab
NonfreeKernelModules: nvidia
Package: gnome-utils 2.24.0-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: baobab
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-utils
StacktraceTop:
 g_utf8_validate () from /usr/lib/libglib-2.0.so.0
 gconf_value_list_from_primitive_list ()
 gconf_engine_set_list () from /usr/lib/libgconf-2.so.4
 gconf_client_set_list () from /usr/lib/libgconf-2.so.4
 ?? ()
Title: baobab crashed with SIGSEGV in g_utf8_validate()
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin cdrom dialout lp lpadmin plugdev pulse pulse-access pulse-rt sambashare

Tags: apport-crash
Revision history for this message
smmalis37 (smmalis37) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:g_utf8_validate () from /usr/lib/libglib-2.0.so.0
gconf_value_list_from_primitive_list (list_type=GCONF_VALUE_STRING, list=0x9a5e6c0,
gconf_engine_set_list (conf=0x990a7f8,
gconf_client_set_list (client=0x9909d58,
baobab_init () at baobab.c:648

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gnome-utils:
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in gnome-utils:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
smmalis37 (smmalis37) wrote :

The backtrace looks exactly like the Stacktrace apport created, only with less detail.

Revision history for this message
Sebastien Bacher (seb128) wrote :

you don't get glib details if you install libglib2.0-0-dbg?

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you get a valgrind log?

Revision history for this message
Sebastien Bacher (seb128) wrote :

you can read https://wiki.ubuntu.com/Valgrind which has the required instruction

Revision history for this message
smmalis37 (smmalis37) wrote :

Here we go, something went wrong with the debug symbols before. Heres the important GDB lines:

"Program received signal SIGSEGV, Segmentation fault.
0xb74280ab in IA__g_utf8_validate (
    str=0x57e58955 <Address 0x57e58955 out of bounds>, max_len=-1, end=0x0)
    at /build/buildd/glib2.0-2.18.2/glib/gutf8.c:1573
1573 /build/buildd/glib2.0-2.18.2/glib/gutf8.c: No such file or directory.
 in /build/buildd/glib2.0-2.18.2/glib/gutf8.c"

"(gdb) thread apply all backtrace full

Thread 1 (Thread 0xb6d27700 (LWP 16291)):
#0 0xb74280ab in IA__g_utf8_validate (
    str=0x57e58955 <Address 0x57e58955 out of bounds>, max_len=-1, end=0x0)
    at /build/buildd/glib2.0-2.18.2/glib/gutf8.c:1573
 p = <value optimized out>
#1 0xb7cd0522 in gconf_value_list_from_primitive_list ()
   from /usr/lib/libgconf-2.so.4
No symbol table info available.
#2 0xb7ce0ade in gconf_engine_set_list () from /usr/lib/libgconf-2.so.4
No symbol table info available.
#3 0xb7ce3fdb in gconf_client_set_list () from /usr/lib/libgconf-2.so.4
No symbol table info available.
#4 0x08052f88 in ?? ()
No symbol table info available.
#5 0x080539fa in main ()
No symbol table info available."

Revision history for this message
Thomas Sibley (thomas-sibley) wrote :

I'm also experiencing this issue. Baobab was working just fine until I unchecked some of the volumes it crawls for a "filesystem" scan and then tried to do such a scan (at which point it segfaulted and continued to do so upon re-running it).

Revision history for this message
Thomas Sibley (thomas-sibley) wrote :

Blowing away ~/.gconf/apps/baobab/ makes it stop segfaulting. I am able to reproduce the segfault by going into Baobab's Preferences and unchecking the root partition (leaving only two external usb HDs I have attached).

The problem key is /apps/baobab/properties/skip_scan_uri_list. When one of the values is "file:///" Baobab will segfault as reported above.

For the record, this is the backtrace I get:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6dc9700 (LWP 10098)]
0xb74ca0ab in IA__g_utf8_validate (
    str=0x57e58955 <Address 0x57e58955 out of bounds>, max_len=-1, end=0x0)
    at /build/buildd/glib2.0-2.18.2/glib/gutf8.c:1573
1573 /build/buildd/glib2.0-2.18.2/glib/gutf8.c: No such file or directory.
 in /build/buildd/glib2.0-2.18.2/glib/gutf8.c
(gdb) bt
#0 0xb74ca0ab in IA__g_utf8_validate (
    str=0x57e58955 <Address 0x57e58955 out of bounds>, max_len=-1, end=0x0)
    at /build/buildd/glib2.0-2.18.2/glib/gutf8.c:1573
#1 0xb7d72522 in gconf_value_list_from_primitive_list ()
   from /usr/lib/libgconf-2.so.4
#2 0xb7d82ade in gconf_engine_set_list () from /usr/lib/libgconf-2.so.4
#3 0xb7d85fdb in gconf_client_set_list () from /usr/lib/libgconf-2.so.4
#4 0x08052f88 in ?? ()
#5 0x080539fa in main ()

Revision history for this message
smmalis37 (smmalis37) wrote :

Went into gconf editor apps/baobab/properties/skip_scan_uri_list, removed the "file:///" entry and it works now. Thanks!

Changed in gnome-utils:
status: Incomplete → Confirmed
Revision history for this message
Fabio Marzocca (thesaltydog) wrote :

I have openend bug on upstream: http://bugzilla.gnome.org/show_bug.cgi?id=560476

Changed in gnome-utils:
status: Confirmed → Triaged
Changed in gnome-utils:
status: Triaged → Fix Committed
Revision history for this message
Adam Niedling (krychek) wrote :

I had the same issue and smmalis37's workaround fixed it.

Revision history for this message
Fabio Marzocca (thesaltydog) wrote :

The bug is fixed upstream in trunk.

Changed in gnome-utils:
status: Unknown → Fix Released
Revision history for this message
Pedro Villavicencio (pedro) wrote :

the new version containing the fix is already on jaunty, marking this as fixed, thanks for reporting.

Changed in gnome-utils:
status: Fix Committed → Fix Released
Changed in gnome-utils:
importance: Unknown → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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