Bug 651093 – crash in CD/DVD Creator: als sudo (alte)System-Da...

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 651093 - crash in CD/DVD Creator: als sudo (alte)System-Da...


Summary:	crash in CD/DVD Creator: als sudo (alte)System-Da...


Status:	RESOLVED DUPLICATE of bug 602500

Product:	brasero
Classification:	Applications
Component:	general
Version:	2.32.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	2.26
Assigned To:	Brasero maintainer(s)
QA Contact:	Brasero maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-05-25 21:07 UTC by a
Modified:	2011-05-26 01:06 UTC

See Also:
GNOME target:	---
GNOME version:	2.31/2.32

Description a 2011-05-25 21:07:19 UTC

Version: 2.32.1

What were you doing when the application crashed?
als sudo (alte)System-Dateien einer vorherigen Installation von einer mobilen Platte (USB) auf eine Festplatte verschoben


Distribution: Ubuntu 11.04 (natty)
Gnome Release: 2.32.1 2011-04-14 (Ubuntu)
BugBuddy Version: 2.31.92

System: Linux 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 11001000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ambiance
Icon Theme: ubuntu-mono-dark
GTK+ Modules: gnomesegvhandler

Memory status: size: 826966016 vsize: 826966016 resident: 177201152 share: 33632256 rss: 177201152 rss_rlim: 18446744073709551615
CPU usage: start_time: 1306357521 rtime: 561 utime: 495 stime: 66 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7ffb383f3700 (LWP 9798)]
[New Thread 0x7ffb4b108700 (LWP 27976)]
[New Thread 0x7ffb57e9a700 (LWP 26540)]
0x00007ffb5e9a081d in waitpid () from /lib/x86_64-linux-gnu/libpthread.so.0

+ Trace 227253

Thread 1 (Thread 0x7ffb6315e9c0 (LWP 26512))

#0 waitpid
from /lib/x86_64-linux-gnu/libpthread.so.0
#1 g_spawn_sync
at /build/buildd/glib2.0-2.28.6/./glib/gspawn.c line 392
#2 g_spawn_command_line_sync
at /build/buildd/glib2.0-2.28.6/./glib/gspawn.c line 706
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomesegvhandler.so
#4 <signal handler called>
#5 nautilus_file_peek_display_name
at nautilus-file.c line 3793
#6 nautilus_file_get_display_name
at nautilus-file.c line 3816
#7 selection_changed_callback
at nautilus-information-panel.c line 1129
#8 g_closure_invoke
at /build/buildd/glib2.0-2.28.6/./gobject/gclosure.c line 767
#9 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.28.6/./gobject/gsignal.c line 3252
#10 g_signal_emit_valist
at /build/buildd/glib2.0-2.28.6/./gobject/gsignal.c line 2983
#11 g_signal_emit_by_name
at /build/buildd/glib2.0-2.28.6/./gobject/gsignal.c line 3077
#12 fm_directory_view_send_selection_change
at fm-directory-view.c line 2377
#13 process_old_files
at fm-directory-view.c line 2922
#14 display_pending_files
at fm-directory-view.c line 2936
#15 display_pending_callback
at fm-directory-view.c line 3036
#16 g_timeout_dispatch
at /build/buildd/glib2.0-2.28.6/./glib/gmain.c line 3882
#17 g_main_dispatch
at /build/buildd/glib2.0-2.28.6/./glib/gmain.c line 2440
#18 g_main_context_dispatch
at /build/buildd/glib2.0-2.28.6/./glib/gmain.c line 3013
#19 g_main_context_iterate
at /build/buildd/glib2.0-2.28.6/./glib/gmain.c line 3091
#20 g_main_loop_run
at /build/buildd/glib2.0-2.28.6/./glib/gmain.c line 3299
#21 IA__gtk_main
at /build/buildd/gtk+2.0-2.24.4/gtk/gtkmain.c line 1257
#22 main
at nautilus-main.c line 544


	Inferior 1 [process 26512] will be detached.

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

Comment 1 Fabio Durán Verdugo 2011-05-26 01:06:12 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 602500 ***