GNOME Bugzilla – Bug 595785
crash in IA__g_simple_async_result_complete, mount_reply
Last modified: 2018-09-21 16:53:49 UTC
What were you doing when the application crashed? I was trying to mount a Creative Zen media player (MTP device). Distribution: Debian squeeze/sid Gnome Release: 2.26.1 2009-04-14 (Debian) BugBuddy Version: 2.26.0 System: Linux 2.6.30-2-686 #1 SMP Wed Sep 16 17:17:28 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10603901 Selinux: No Accessibility: Disabled GTK+ Theme: ClearlooksClassic Icon Theme: Mist GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 37949440 vsize: 37949440 resident: 8757248 share: 6885376 rss: 8757248 rss_rlim: 18446744073709551615 CPU usage: start_time: 1253434773 rtime: 46 utime: 42 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/gnome-applets/drivemount_applet2' (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb7f56424 in __kernel_vsyscall ()
+ Trace 217719
Thread 1 (Thread 0xb6d50af0 (LWP 2114))
The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (23062 sec old) --------------------- (firefox-bin:21517): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:21517): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:21517): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:21517): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:21517): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:21517): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:21517): Gdk-WARNING **: XID collision, trouble ahead ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Hello, thanks for your response. I've installed debugging packages and I hope this report will be more useful than my previous one. In addition to mounting my MTP player, this problem also appears when I mount an audio CD. As far as I can see, the problem probably lies with the device mount applet, since I can mount media through Nautilus without a problem. I'm seeing quite a lot of "No symbol table info available" messages in this trace. Is this normal or am I still missing debugging-related packages? Thank you very much for your help :) Distribution: Debian squeeze/sid Gnome Release: 2.26.1 2009-04-14 (Debian) BugBuddy Version: 2.26.0 System: Linux 2.6.30-2-686 #1 SMP Wed Sep 16 17:17:28 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10603901 Selinux: No Accessibility: Disabled GTK+ Theme: ClearlooksClassic Icon Theme: Mist GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 38068224 vsize: 38068224 resident: 12533760 share: 10481664 rss: 12533760 rss_rlim: 18446744073709551615 CPU usage: start_time: 1253651846 rtime: 39 utime: 38 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/gnome-applets/drivemount_applet2' [Thread debugging using libthread_db enabled] 0xb800b424 in __kernel_vsyscall ()
+ Trace 217775
Thread 1 (Thread 0xb6d97af0 (LWP 9806))
----------- .xsession-errors (32883 sec old) --------------------- (firefox-bin:2291): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:2291): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:2291): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:2291): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:2291): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:2291): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:2291): Gdk-WARNING **: XID collision, trouble ahead ...Too much output, ignoring rest... --------------------------------------------------
*** Bug 607951 has been marked as a duplicate of this bug. ***
*** Bug 607943 has been marked as a duplicate of this bug. ***
*** Bug 607944 has been marked as a duplicate of this bug. ***
*** Bug 594429 has been marked as a duplicate of this bug. ***
*** Bug 611287 has been marked as a duplicate of this bug. ***
Created attachment 156702 [details] [review] Proposed fix It seems that this crash occurs when the mounting operation terminates. This operation is started by the applet in the mount_drive() function (drivemount/drive-button.c), which calls g_volume_mount(). When terminating, the operation calls GVFS' function mount_foreign_callback() in source file monitor/proxy/gproxyvolume.c, which in turn calls the callback function specified in the original call to g_volume_mount(), as per http://library.gnome.org/devel/gio/stable/GVolume.html#g-volume-mount However, the Disk Mounter applet uses NULL for the callback (correct according to the above g_volume_mount() specifications) but GVFS does _not_ check whether the callback is NULL or not. Hence the segfault. The solution I found was to add a check in GVFS, which seems to have completely fixed the problem. A simple patch is attached to this reply.
Confirming. Also, this bug was filled agains GNOME 2.26, Could you reproduce this in newer versions. If yes, could you update the "version" fields?
Moving to gvfs as per comment 8.
*** Bug 620117 has been marked as a duplicate of this bug. ***
*** Bug 621392 has been marked as a duplicate of this bug. ***
*** Bug 664449 has been marked as a duplicate of this bug. ***
last dupe in GNOME 2.32.x
Review of attachment 156702 [details] [review]: Patch looks OK but we should fix other stuff at the same time too (like g_volume_eject()) and also check if any changes are needed in the other volume monitors. bug 710995 is somewhat related.
Hal volume monitor is obsolete currently, changing component to client, because it is rather client issue and this issue seems to be still valid... Something like this has been fixed recently, but it seems there are more places where it should be fixed: commit fcbf262537f3d14035ac31107c7a4ba7a31905af
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gvfs/issues/116.