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 605133 - Nautilus crashed with SIGSEGV in g_shell_quote()
Nautilus crashed with SIGSEGV in g_shell_quote()
Status: RESOLVED NOTGNOME
Product: nautilus
Classification: Core
Component: general
unspecified
Other Linux
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-12-21 13:32 UTC by Sense Hofstede
Modified: 2010-04-17 10:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sense Hofstede 2009-12-21 13:32:54 UTC
Nautilus crashed with SIGSEGV in g_shell_quote() when trying to open a file in Nautilus that was associated with a custom, home-brewed application that wasn't installed from the repositories.

  • #0 IA__g_shell_quote
    at /build/buildd/glib2.0-2.20.1/glib/gshell.c line 198
  • #1 launch_gnome_app_install_mimetype
    at nautilus-mime-actions.c line 1385
  • #2 activate_callback
    at nautilus-mime-actions.c line 1449
  • #3 file_list_file_ready_callback
    at nautilus-file.c line 6986
  • #4 call_ready_callbacks_at_idle
    at nautilus-directory-async.c line 1908
  • #5 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.20.1/glib/gmain.c line 1814
  • #6 g_main_context_iterate
    at /build/buildd/glib2.0-2.20.1/glib/gmain.c line 2448
  • #7 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.20.1/glib/gmain.c line 2656
  • #8 IA__gtk_main
    at /build/buildd/gtk+2.0-2.16.1/gtk/gtkmain.c line 1205
  • #9 main
    at nautilus-main.c line 518

This bug was originally reported by ubuntu.diego with Apport on Launchpad in Ubuntu at <https://launchpad.net/bugs/418979>; the downstream report contains more information, including a ThreadStacktrace -- the Trace provided in this bug report is a Stacktrace -- ProcMaps and ProcStatus.
Comment 1 Marcus Carlson 2010-04-17 10:25:43 UTC
This is a downstream problem and should be OK to close (as I see it...)
Comment 2 Cosimo Cecchi 2010-04-17 10:37:03 UTC
Yes, that's due to an Ubuntu patch AFAICS.