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 607951 - crash in Disk Mounter:
crash in Disk Mounter:
Status: RESOLVED DUPLICATE of bug 595785
Product: gnome-applets
Classification: Other
Component: Disk Mounter (drivemount)
unspecified
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-01-24 17:33 UTC by wolcendo
Modified: 2010-01-24 21:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description wolcendo 2010-01-24 17:33:37 UTC 
What were you doing when the application crashed?



Distribution: Debian squeeze/sid
Gnome Release: 2.28.2 2009-12-18 (Debian)
BugBuddy Version: 2.28.0

System: Linux 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10605000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux
GTK+ Modules: gnomebreakpad

Memory status: size: 46112768 vsize: 46112768 resident: 12955648 share: 10907648 rss: 12955648 rss_rlim: 18446744073709551615
CPU usage: start_time: 1264352104 rtime: 44 utime: 41 stime: 3 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]
0xb7858424 in __kernel_vsyscall ()

+ Trace 220234

Thread 1 (Thread 0xb6586750 (LWP 19563))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
  • #7 g_simple_async_result_complete
    from /usr/lib/libgio-2.0.so.0
  • #8 ??
    from /usr/lib/gio/modules/libgvfsdbus.so
  • #9 ??
    from /usr/lib/gio/modules/libgvfsdbus.so
  • #10 ??
    from /usr/lib/gvfs/libgvfscommon.so
  • #11 ??
    from /lib/libdbus-1.so.3
  • #12 ??
    from /lib/libdbus-1.so.3
  • #13 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #14 ??
    from /usr/lib/gvfs/libgvfscommon.so
  • #15 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #18 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #19 bonobo_generic_factory_main_timeout
    from /usr/lib/libbonobo-2.so.0
  • #20 bonobo_generic_factory_main
    from /usr/lib/libbonobo-2.so.0
  • #21 panel_applet_factory_main_closure
    from /usr/lib/libpanel-applet-2.so.0
  • #22 panel_applet_factory_main
    from /usr/lib/libpanel-applet-2.so.0
  • #23 ??
  • #24 __libc_start_main
    from /lib/i686/cmov/libc.so.6
  • #25 ?? 
A debugging session is active.

	Inferior 1 [process 19563] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (97 sec old) ---------------------
** (rhythmbox:19376): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
(rhythmbox:19376): Rhythmbox-WARNING **: Could not open device /dev/radio0
** (rhythmbox:19376): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (rhythmbox:19376): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
(rhythmbox:19376): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(rhythmbox:19376): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
** (rhythmbox:19376): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (rhythmbox:19376): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2010-01-24 21:26:54 UTC 
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!

This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 595785 ***