Crash report gvfs-mount during logon

[Henk Bekkering]

Binary package hint: gdm

$ lsb_release -rd
Description: Ubuntu lucid (development branch)
Release: 10.04

Based on http://ubuntuforums.org/showthread.php?t=1186877 I created a script which mounts three smb shares.

$ cat sharemount.sh
#!/bin/sh
gvfs-mount smb://barbabenno/hbe
gvfs-mount smb://barbabenno/we
gvfs-mount smb://barbabenno/mp3

And I placed the sharemount.sh in the Startup applications.

After login, I got a crash report, which could not send a report.
I saw the following lines in \var\log\syslog

Apr 6 21:58:49 barbalala console-kit-daemon[843]: WARNING: Couldn't read /proc/1831/environ: Failed to open file '/proc/1831/environ': No such file or directory
Apr 6 21:58:49 barbalala gdm-simple-slave[2184]: WARNING: Unable to load file '/etc/gdm/custom.conf': No such file or directory
Apr 6 21:58:49 barbalala acpid: client 1691[0:0] has disconnected
Apr 6 21:58:49 barbalala acpid: client connected from 2186[0:0]
Apr 6 21:58:49 barbalala acpid: 1 client rule loaded
Apr 6 21:58:52 barbalala gdm-session-worker[2224]: WARNING: Unable to load file '/etc/gdm/custom.conf': No such file or directory
Apr 6 21:58:52 barbalala rtkit-daemon[1177]: Sucessfully made thread 2226 of process 2226 (n/a) owned by '114' high priority at nice level -11.
Apr 6 21:58:52 barbalala rtkit-daemon[1177]: Supervising 4 threads of 2 processes of 2 users.
Apr 6 21:58:52 barbalala gdm-simple-greeter[2221]: Gtk-WARNING: /build/buildd/gtk+2.0-2.20.0/gtk/gtkwidget.c:5636: widget not within a GtkWindow
Apr 6 21:58:53 barbalala rtkit-daemon[1177]: Sucessfully made thread 2229 of process 2226 (n/a) owned by '114' RT at priority 5.
Apr 6 21:58:53 barbalala rtkit-daemon[1177]: Supervising 5 threads of 2 processes of 2 users.
Apr 6 21:58:53 barbalala rtkit-daemon[1177]: Sucessfully made thread 2230 of process 2226 (n/a) owned by '114' RT at priority 5.
Apr 6 21:58:53 barbalala rtkit-daemon[1177]: Supervising 6 threads of 2 processes of 2 users.
Apr 6 21:58:54 barbalala gdm-session-worker[2224]: GLib-GObject-CRITICAL: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed
Apr 6 21:59:02 barbalala wpa_supplicant[826]: WPS-AP-AVAILABLE
Apr 6 22:00:02 barbalala wpa_supplicant[826]: WPS-AP-AVAILABLE

After login, I see one or none shares in ~/.gvfs
When I run the script manually, I can see all the three shares.

I am new in this, so I hope I provide enough information....

[Pedro Villavicencio (pedro)]

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.

[Sebastien Bacher (seb128)]

You can also retrace the crash file locally and add the stracktrace to the bug, you can unpack the crash file using apport-unpack to get it.

[Henk Bekkering (henk-bekkering)]

/etc/default/apport is already enabled, and there is a crash report file.

double click on the crash report says:

The problem cannot be reported:

The program crashed on an assertion failure, but the message could not be retrieved.
Apport does not support reporting these crashes.

What should I do (is it save to attach the crash file?)

[Henk Bekkering (henk-bekkering)]

I changed the status back to new to make sure this issue is looked at again.
If it was not correct to do so, please tell me (and I am sorry)

[Henk Bekkering (henk-bekkering)]

With apport-unpack I extracted the Stacktrace:

# cat Stacktrace
#0 0x00d11422 in __kernel_vsyscall ()
No symbol table info available.
#1 0x0085b641 in raise () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2 0x0085ea72 in abort () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#3 0x00255dd3 in g_assertion_message () from /lib/libglib-2.0.so.0
No symbol table info available.
#4 0x0025642d in g_assertion_message_expr () from /lib/libglib-2.0.so.0
No symbol table info available.
#5 0x00c7c802 in ?? () from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#6 0x00c7bb55 in ?? () from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#7 0x00c7c8fc in ?? () from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#8 0x00c7d5b1 in ?? () from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#9 0x00c86938 in gnome_keyring_find_network_password_sync ()
   from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#10 0x08064864 in ?? ()
No symbol table info available.
#11 0x08050667 in ?? ()
No symbol table info available.
#12 0x003b7107 in ?? () from /usr/lib/libsmbclient.so.0
No symbol table info available.
#13 0x003b7318 in ?? () from /usr/lib/libsmbclient.so.0
No symbol table info available.
#14 0x003b7b06 in ?? () from /usr/lib/libsmbclient.so.0
No symbol table info available.
#15 0x003b955b in ?? () from /usr/lib/libsmbclient.so.0
No symbol table info available.
#16 0x0805249f in ?? ()
No symbol table info available.
#17 0x08059b68 in ?? ()
No symbol table info available.
#18 0x080589fd in ?? ()
No symbol table info available.
#19 0x0805476e in ?? ()
No symbol table info available.
#20 0x0025acec in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#21 0x00258dcf in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#22 0x00dee96e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#23 0x008fe9de in clone () from /lib/tls/i686/cmov/libc.so.6

[Henk Bekkering (henk-bekkering)]

Some more info from the crashfile:

# cat Package
gvfs-backends 1.6.0-0ubuntu1

# cat ProcCmdline
/usr/lib/gvfs/gvfsd-smb --spawner :1.6 /org/gtk/gvfs/exec_spaw/0

# cat UnreportableReason
The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes.cat

# cat UserGroups
adm admin cdrom dialout lpadmin plugdev sambashare

[Charlie Kravetz (cjkgeek)]

The stacktrace above is not useable to find what caused this issue. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Sebastien Bacher (seb128)]

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

[Henk Bekkering (henk-bekkering)]

Nice to hear that there is a duplicate bug report, since I did not know how to add extra debug information.
I will wait for a week or so, so the new keyring is installed at my computer (I use the normal update mechanism).
If there is still an error then, I will let you know...