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 522261 - nautilus-connect-server crashed with SIGSEGV in nautilus_connect_server_dialog_init()
nautilus-connect-server crashed with SIGSEGV in nautilus_connect_server_dialo...
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: Crashers
2.22.x
Other Linux
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-13 16:59 UTC by Sebastien Bacher
Modified: 2011-04-06 20:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Sebastien Bacher 2008-03-13 16:59:18 UTC 
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/201435

"nautilus-connect-server crashes if I try to execute.

+ Trace 192315

  • #0 nautilus_connect_server_dialog_init
    at nautilus-connect-server-dialog.c line 842
  • #1 IA__g_type_create_instance
    at /build/buildd/glib2.0-2.15.6/gobject/gtype.c line 1547
  • #2 IA__g_object_set_property
    at /build/buildd/glib2.0-2.15.6/gobject/gobjectnotifyqueue.c line 76
  • #3 pool_depth_list
    at /build/buildd/glib2.0-2.15.6/gobject/gparam.c line 904
  • #4 IA__g_param_spec_set_qdata
    at /build/buildd/glib2.0-2.15.6/gobject/gparam.c line 356
  • #5 IA__gtk_widget_new
    at /build/buildd/gtk+2.0-2.12.8/gtk/gtkwidget.c line 2738
  • #6 nautilus_connect_server_dialog_new
    at nautilus-connect-server-dialog.c line 957
  • #7 main
    at nautilus-connect-server-dialog-main.c line 152
  • #8 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #9 _start 






Comment 1


Alexander Larsson





          2009-03-11 15:11:34 UTC
        



It looks like g_vfs_get_supported_uri_schemes() returns NULL or something that we crash when dereferencing. I don't see how this could happen though. Even if there are no supported schemes we should return a NULL terminated array.







Comment 2


Cosimo Cecchi





          2011-04-06 20:17:44 UTC
        



I guess this can be closed as OBSOLETE.