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 670648 - nautilus crashed with SIGSEGV in set_floating_bar_status()
nautilus crashed with SIGSEGV in set_floating_bar_status()
Status: RESOLVED DUPLICATE of bug 670591
Product: nautilus
Classification: Core
Component: Crashers
3.3.x
Other Linux
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-02-22 22:58 UTC by Sebastien Bacher
Modified: 2012-08-01 18:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastien Bacher 2012-02-22 22:58:42 UTC 
The bug got reported on https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/929064

"Crashed ramdomly after no particular action.

nautilus 3.3.5 (duplicates with newer versions)

+ Trace 229719

  • #0 g_type_check_instance_cast
    at /build/buildd/glib2.0-2.31.16/./gobject/gtype.c line 3993
  • #1 set_floating_bar_status
    at nautilus-window-slot.c line 533
  • #2 nautilus_window_slot_set_status
    at nautilus-window-slot.c line 567
  • #3 nautilus_view_display_selection_info
    at nautilus-view.c line 2948
  • #4 update_status_idle_callback
    at nautilus-view.c line 8847
  • #5 g_main_dispatch
    at /build/buildd/glib2.0-2.31.16/./glib/gmain.c line 2510
  • #6 g_main_context_dispatch
    at /build/buildd/glib2.0-2.31.16/./glib/gmain.c line 3047
  • #7 g_main_context_iterate
    at /build/buildd/glib2.0-2.31.16/./glib/gmain.c line 3118
  • #8 g_main_context_iterate
    at /build/buildd/glib2.0-2.31.16/./glib/gmain.c line 3055
  • #9 g_main_context_iteration
    at /build/buildd/glib2.0-2.31.16/./glib/gmain.c line 3179 






Comment 1


Cosimo Cecchi





          2012-08-01 18:36:47 UTC
        



I think this is just another variation of bug 670591.
Feel free to reopen if it still happens with a version after that patch was introduced (3.3.91).

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