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 640776 - crash in File Manager: listening to music (rhyt...
crash in File Manager: listening to music (rhyt...
Status: RESOLVED DUPLICATE of bug 632576
Product: nautilus
Classification: Core
Component: general
2.32.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-01-27 22:30 UTC by asp
Modified: 2011-01-30 22:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32


Description asp 2011-01-27 22:30:32 UTC 
Version: 2.32.0

What were you doing when the application crashed?
listening to music (rhythmbox)


Distribution: Ubuntu 10.10 (maverick)
Gnome Release: 2.32.0 2010-09-27 (Ubuntu)
BugBuddy Version: 2.31.92

System: Linux 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:34:50 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10900000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ambiance
Icon Theme: ubuntu-mono-dark
GTK+ Modules: gnomesegvhandler

Memory status: size: 220475392 vsize: 220475392 resident: 39075840 share: 23789568 rss: 39075840 rss_rlim: 18446744073709551615
CPU usage: start_time: 1296167305 rtime: 818 utime: 746 stime: 72 cutime:42 cstime: 60 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

[Thread debugging using libthread_db enabled]
[New Thread 0xb2abfb70 (LWP 8540)]
[New Thread 0xb75d4b70 (LWP 8477)]
0x00c27416 in __kernel_vsyscall ()

+ Trace 225729

Thread 1 (Thread 0xb77d6860 (LWP 8471))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/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/libgnomesegvhandler.so
  • #5 <signal handler called>
  • #6 g_atomic_int_exchange_and_add
    from /lib/libglib-2.0.so.0
  • #7 g_variant_unref
    from /lib/libglib-2.0.so.0
  • #8 brasero_inhibit_suspend
    from /usr/lib/libbrasero-burn.so.1
  • #9 ??
    from /usr/lib/libbrasero-burn.so.1
  • #10 brasero_burn_record
    from /usr/lib/libbrasero-burn.so.1
  • #11 ??
    from /usr/lib/libbrasero-burn.so.1
  • #12 brasero_burn_dialog_run
    from /usr/lib/libbrasero-burn.so.1
  • #13 ??
    from /usr/lib/nautilus/extensions-2.0/libnautilus-brasero-extension.so
  • #14 ??
    from /usr/lib/nautilus/extensions-2.0/libnautilus-brasero-extension.so
  • #15 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/nautilus/extensions-2.0/libnautilus-brasero-extension.so
  • #21 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #23 ??
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #26 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #29 ??
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #31 ??
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #34 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 ??
    from /usr/lib/libgobject-2.0.so.0
  • #38 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #39 ??
    from /usr/lib/libgobject-2.0.so.0
  • #40 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #41 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #42 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #43 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #44 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #45 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #46 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #47 ??
    from /lib/libglib-2.0.so.0
  • #48 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #49 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #50 ??
  • #51 __libc_start_main
    from /lib/libc.so.6
  • #52 ?? 
A debugging session is active.

	Inferior 1 [process 8471] will be detached.

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


---- Critical and fatal warnings logged during execution ----

** GConf **: gconf_value_free: assertion `value != NULL' failed 
** GConf **: gconf_value_free: assertion `value != NULL' failed
Comment 1 Akhil Laddha 2011-01-28 01:23:29 UTC 
may be fixed in bug 632576

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. Thanks in advance!
Comment 2 Cosimo Cecchi 2011-01-30 22:36:17 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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