After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 648856 - Double click on bookmarks causes segmentation fault
Double click on bookmarks causes segmentation fault
Status: RESOLVED DUPLICATE of bug 648872
Product: nautilus
Classification: Core
Component: Sidebar
3.0.x
Other Linux
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-04-28 09:09 UTC by Daniele Bartolini
Modified: 2011-04-28 18:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniele Bartolini 2011-04-28 09:09:12 UTC
_Double-clicking_ a bookmark item in the "Computer" section of "Places" sidebar causes a segmentation fault.

Nautilus: 3.0.1

Message reported:

(nautilus:2986): Gtk-CRITICAL **: gtk_tree_model_get_iter: assertion `path != NULL' failed

(nautilus:2986): Gtk-CRITICAL **: gtk_tree_model_filter_get_value: assertion `GTK_TREE_MODEL_FILTER (model)->priv->stamp == iter->stamp' failed

(nautilus:2986): GLib-GObject-WARNING **: gtype.c:4201: type id `0' is invalid

(nautilus:2986): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced
Segmentation fault
Comment 1 André Klapper 2011-04-28 11:11:44 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so (probably the Details section on how to attach gdb to a running process). Thanks in advance!
Comment 2 Cosimo Cecchi 2011-04-28 18:08:18 UTC
The warnings seem to indicate this is a duplicate of bug 648872


Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 648872 ***