baobab crashes with segmentation fault when trying to performe "scan folder" on a fat32 partition which is NOT included in "folders to scan"

[NeO]

 :~$ baobab /media/sda1/

(baobab:7666): Gtk-CRITICAL **: gtk_tree_store_get_value: assertion `VALID_ITER (iter, tree_store)' failed

(baobab:7666): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.18.2/gobject/gtype.c:3940: type id `0' is invalid

(baobab:7666): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced
Segmentation fault

sorry i dont have more time at the moment.
sda1 is fat32 and marked as do not scan in baobab preferences

cheers
OLI

Steps to reproduce:
1) Using baobab GUI, uncheck a mount point for scanning (eg. /media/disk).
2) Launch baobab from the terminal and specify that mount point (eg. baobab /media/disk).

[Hew (hew)]

Baobab is part of gnome-utils, changing sourcepackage.

Which version of Ubuntu did this occur on, have you tried Intrepid or Jaunty? Does this only happen with that partition, or does it crash on others? At what point does the crash occur if you specify the directory from within the GUI? Thanks in advance.

[Fabio Marzocca (thesaltydog)]

It is a strange way to launch baobab on a terminal over a de-selected partition! It looks like you are trying to cheat it by forcing scanning on a partition that you have deselected? From the GUI this doesn't happen.

[NeO (oli-n)]

I use Ubuntu 8.10 - the Intrepid Ibex - released in October 2008.
And indeed the launch in the terminal is kind to cheat, it first crashed from the GUI and there I had no error output.
And actually I just tried it again in the GUI it first seam to work fine, but when i removed all partitions from the folders to scan (using the preferences) and clicked scan folder and selected one then apply
and baobab crashed. And now i cant even restart it it always crashes with segmentation fault- eave in the terminal whenn i just type
***@***:~$ baobab
Segmentation fault
***@***:~$

Now i just removed the packages completely and reinstalled it but it still crashes like that!
How do i remove those settings ?

cheers
NeO

[Fabio Marzocca (thesaltydog)]

@Neo --> theat bug has been fixed upstream. Here it is a temporary workaround: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-utils/+bug/284923

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

I wonder if this can be closed because the gnome-utils package in bu #284923 is marked as "fix released"?

[Hew (hew)]

Bug 284923 describes the immediate segfault. This bug as originally reported is that the "cheating" method causes a crash, which I can reproduce with gnome-utils 2.25.2-0ubuntu1 .

[Fabio Marzocca (thesaltydog)]

This bug has been fixed upstream: http://bugzilla.gnome.org/show_bug.cgi?id=567834

[Sebastien Bacher (seb128)]

the new version is in jaunty

[Adam Niedling (krychek)]

I have the same issue with updated Jaunty:

$ baobab

** (baobab:14855): WARNING **: Throbber rest icon not found

(baobab:14855): Gtk-CRITICAL **: gtk_tree_store_get_value: assertion `VALID_ITER (iter, tree_store)' failed

(baobab:14855): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.20.1/gobject/gtype.c:3940: type id `0' is invalid

(baobab:14855): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced
Segmentation fault

The reproduction process is the same as the original reported described it. Trying to scan a fat32 partition which is set not to be checked in preferences. There is no error when the partition is set to be checked.

[Fabio Marzocca (thesaltydog)]

Sorry, but cannot reproduce the bug as reported in the first post of this thread. That bug has been fixed.

When I try to scan an unchecked volume from terminal, now I get an error warning dialog and baobab starts anyway on idle.

[Adam Niedling (krychek)]

Yes, if you do it from the terminal that is what happens.
But if you do it from the GUI you will get a segmentation fault. Could you try it from the GUI?

[Hew (hew)]

Thanks for your comments Adam. I have reproduced the crash and reported this similar issue as bug 369740.

[Fabio Marzocca (thesaltydog)]

@Hew: cannot land on the new bug page...

[Adam Niedling (krychek)]

Why is this set to Fix Released when this is still an issue?

[Adam Niedling (krychek)]

So this was fixed in Karmic. I'm setting this bug as a duplicate then.