SIGSEGV when opening files

[Maykel Moya]

Well, the first symptom I got is that gedit is unable to run.

moya@jessy:~/work/maremme$ gedit
process 7178: type array 97 not a basic type
process 7178: type array 97 not a basic type
process 7178: type invalid 0 not a basic type
process 7178: type invalid 0 not a basic type
process 7178: type struct 114 not a basic type
Segmentation fault

I did a search on Google and found that http://fcp.surfsite.org/modules/newbb/viewtopic.php?topic_id=73440&forum=11&post_id=358014.

I'm able to run eog but unable to open any file, it SIGSEGV with the same 'process PID: type array 97 ...' messages.

gthumb SIGSEGV when launched.

I'd just updated gvfs, maybe that has been the trigger of the bug.

Regards,
maykel

----
moya@jessy:~/work/maremme$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04

moya@jessy:~/work/maremme$ apt-cache policy gnome-settings-daemon
gnome-settings-daemon:
  Instalados: 2.27.3-0ubuntu2
  Candidato: 2.27.3-0ubuntu2
  Tabla de versión:
 *** 2.27.3-0ubuntu2 0
         10 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
     2.26.0-0ubuntu4 0
        500 http://archive.ubuntu.com jaunty/main Packages

[Maykel Moya (mmoyar)]

The problem is gone after reverting gvfs back to 1.3.1-0ubuntu2 from 1.3.2-0ubuntu1 so I'm doubt now who the culprit is.

How can I link this bug to package gvfs?

Regards,
maykel

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

 If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

 If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
 I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[Ethan Baldridge (ethan-superiordocumentservices)]

There is no crash file generated by the programs.

It seems to be just about anything that uses the GTK+ file chooser dialog will crash with SIGSEGV - no .crash report is generated.

This is in Karmic.

~/src/agoban-0.6$ ./agoban

runs... then click on "open file":
process 21297: type array 97 not a basic type
process 21297: type array 97 not a basic type
process 21297: type invalid 0 not a basic type
process 21297: type invalid 0 not a basic type
process 21297: type struct 114 not a basic type
Segmentation fault

$ dpkg -l gnome-settings-daemon gvfs
||/ Name Version Description
+++-=======================================-=======================================-==============================================================================================
ii gnome-settings-daemon 2.27.3-0ubuntu2 GNOME settings daemon
ii gvfs 1.3.2-0ubuntu2 userspace virtual filesystem - server

[Ethan Baldridge (ethan-superiordocumentservices)]

Please don't close for required crash report when none is generated.

[Ethan Baldridge (ethan-superiordocumentservices)]

The segfault appears to be in dbus:

(gdb) run
Starting program: /usr/bin/gedit
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
process 28193: type array 97 not a basic type
process 28193: type array 97 not a basic type
process 28193: type invalid 0 not a basic type
process 28193: type invalid 0 not a basic type
process 28193: type struct 114 not a basic type

Program received signal SIGSEGV, Segmentation fault.
0x00c3f204 in ?? () from /lib/libdbus-1.so.3

Unfortunately I don't seem to see a dbus-dbg pacgake or the like available.

[Ethan Baldridge (ethan-superiordocumentservices)]

Sorry for the spam - meant to put this in the last one.

(gdb) bt
#0 0x00c3f204 in ?? () from /lib/libdbus-1.so.3
#1 0x00c2c62d in ?? () from /lib/libdbus-1.so.3
#2 0x00c2c699 in ?? () from /lib/libdbus-1.so.3
#3 0x00c2b5e7 in ?? () from /lib/libdbus-1.so.3
#4 0x00c2c770 in ?? () from /lib/libdbus-1.so.3
#5 0x00c2b5e7 in ?? () from /lib/libdbus-1.so.3
#6 0x00c310eb in dbus_message_iter_next () from /lib/libdbus-1.so.3
#7 0x04ef6eb2 in ?? () from /usr/lib/gio/modules/libgioremote-volume-monitor.so
#8 0x04efd2d4 in ?? () from /usr/lib/gio/modules/libgioremote-volume-monitor.so
#9 0x04efec41 in ?? () from /usr/lib/gio/modules/libgioremote-volume-monitor.so
#10 0x002c788c in IA__g_object_newv (object_type=137104720, n_parameters=0, parameters=0x0) at /build/buildd/glib2.0-2.21.3/gobject/gobject.c:1215
#11 0x002c84c2 in IA__g_object_new_valist (object_type=137104720, first_property_name=0x0, var_args=0xbfffec28 "") at /build/buildd/glib2.0-2.21.3/gobject/gobject.c:1278
#12 0x002c863e in IA__g_object_new (object_type=137104720, first_property_name=0x0) at /build/buildd/glib2.0-2.21.3/gobject/gobject.c:1060
#13 0x0021a3f3 in populate_union_monitor () at /build/buildd/glib2.0-2.21.3/gio/gunionvolumemonitor.c:522
#14 IA__g_volume_monitor_get () at /build/buildd/glib2.0-2.21.3/gio/gunionvolumemonitor.c:574
#15 0x047be025 in ?? () from /usr/lib/gedit-2/plugins/libfilebrowser.so
#16 0x047bed21 in ?? () from /usr/lib/gedit-2/plugins/libfilebrowser.so
#17 0x047bee50 in gedit_file_bookmarks_store_new () from /usr/lib/gedit-2/plugins/libfilebrowser.so
#18 0x047ca6f0 in ?? () from /usr/lib/gedit-2/plugins/libfilebrowser.so
#19 0x047cc59b in gedit_file_browser_widget_new () from /usr/lib/gedit-2/plugins/libfilebrowser.so
#20 0x047ce2df in ?? () from /usr/lib/gedit-2/plugins/libfilebrowser.so
#21 0x080b928c in gedit_plugin_activate ()
#22 0x0807da2d in gedit_plugins_engine_activate_plugins ()
#23 0x0809a208 in ?? ()
#24 0x002e336f in IA__g_type_create_instance (type=135657336) at /build/buildd/glib2.0-2.21.3/gobject/gtype.c:1674
#25 0x002c6d08 in g_object_constructor (type=135657336, n_construct_properties=2, construct_params=0x815cb68) at /build/buildd/glib2.0-2.21.3/gobject/gobject.c:1338
#26 0x002c788c in IA__g_object_newv (object_type=135657336, n_parameters=0, parameters=0x0) at /build/buildd/glib2.0-2.21.3/gobject/gobject.c:1215
#27 0x002c84c2 in IA__g_object_new_valist (object_type=135657336, first_property_name=0x0, var_args=0xbffff308 "\325\1") at /build/buildd/glib2.0-2.21.3/gobject/gobject.c:1278
#28 0x002c863e in IA__g_object_new (object_type=135657336, first_property_name=0x0) at /build/buildd/glib2.0-2.21.3/gobject/gobject.c:1060
#29 0x0806c098 in ?? ()
#30 0x0806c3f1 in gedit_app_create_window ()
#31 0x0806a920 in main ()

[Sebastien Bacher (seb128)]

did you enable apport as described on the wiki documentation?

[Sebastien Bacher (seb128)]

the stacktrace also lack debug symbols for libdbus and gvfs and gedit

[Maykel Moya (mmoyar)]

2009/7/17 Sebastien Bacher <email address hidden>:

> did you enable apport as described on the wiki documentation?
>
> ** Changed in: gnome-settings-daemon (Ubuntu)
>       Status: New => Incomplete
>
> --
> SIGSEGV when opening files
> https://bugs.launchpad.net/bugs/399842
> You received this bug notification because you are a direct subscriber
> of the bug.

Yes, I did enabled the apport, got the crash in /var/crash and used
apport-cli to send it. At the end of the process apport-cli launched a
Launchpad page I couldn't see.

[Ethan Baldridge (ethan-superiordocumentservices)]

Well I'll be darned - I thought Apport was enabled by default in Karmic. I guess not. My fault - I assumed it was somehow a type of crash that was bypassing the detection.

Sorry about that!

[Chris Coulson (chrisccoulson)]

Thanks Ethan - I'm going to close this one again for now, as you should be able to submit a crash report with Apport (and this bug doesn't look related to gnome-settings-daemon anyway.