Bug 576093 – crash in File Browser: Read DVD

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 576093 - crash in File Browser: Read DVD


Summary:	crash in File Browser: Read DVD


Status:	RESOLVED DUPLICATE of bug 406462

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.20.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-03-20 15:33 UTC by dobrakowskirafal
Modified:	2009-03-20 16:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description dobrakowskirafal 2009-03-20 15:33:33 UTC

Version: 2.20.0

What were you doing when the application crashed?
Read DVD 


Distribution: Debian squeeze/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: ThinIce
Icon Theme: Mist

Memory status: size: 132632576 vsize: 132632576 resident: 33538048 share: 25149440 rss: 33538048 rss_rlim: 18446744073709551615
CPU usage: start_time: 1237197434 rtime: 1510 utime: 1380 stime: 130 cutime:106 cstime: 9 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb68e4750 (LWP 3473)]
0xb7ee4424 in __kernel_vsyscall ()

+ Trace 213650

Thread 1 (Thread 0xb68e4750 (LWP 3473))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at gspawn.c line 382
#3 IA__g_spawn_command_line_sync
at gspawn.c line 694
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 <signal handler called>
#7 IA__gtk_widget_get_toplevel
at gtkwidget.c line 7349
#8 gtk_widget_get_screen_unchecked
at gtkwidget.c line 6700
#9 IA__gtk_widget_has_screen
at gtkwidget.c line 6773
#10 recompute_idle_func
at gtkentry.c line 5162
#11 gdk_threads_dispatch
at gdk.c line 498
#12 g_idle_dispatch
at gmain.c line 3922
#13 IA__g_main_context_dispatch
at gmain.c line 1814
#14 g_main_context_iterate
at gmain.c line 2448
#15 IA__g_main_loop_run
at gmain.c line 2656
#16 IA__gtk_main
at gtkmain.c line 1205
#17 main
at nautilus-main.c line 565
#0 __kernel_vsyscall



----------- .xsession-errors (345270 sec old) ---------------------
 URL loaded: https://websmp110.sap-ag.de/~form/handler?_APP=00200682500000002027&_EVENT=DISPLAY&PORTAL=SUPPORT&_SCENARIO=01100035870000000202&_HIER_KEY=501100035870000000694&_FRAME=HIERARCHY&_UNLINK=X
 URL loaded: https://websmp110.sap-ag.de/~form/handler?_APP=00200682500000002033&_EVENT=DISPLAY&_FRAME=NAVIGATION&_HIER_KEY=501100035870000000694&_SCENARIO=01100035870000000202&
 URL loaded: https://websmp110.sap-ag.de/~form/handler?_APP=00200682500000001952&_EVENT=CREATE_SEA
 URL loaded: https://websmp110.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&PORTAL=SUPPORT&_SCENARIO=01100035870000000202&_HIER_KEY=501100035870000000694&
 URL loaded: https://websmp110.sap-ag.de/~form/handler?_APP=00200682500000002119&_EVENT=BODY&PORTAL=SUPPORT&_SCENARIO=01100035870000000202&_HIER_KEY=501100035870000000694
 URL loaded: https://websmp110.sap-ag.de/~form/handler?_FRAME=HIERARCHY&_APP=00200682500000002027&_EVENT=DISPLAY&_HIER_KEY=501100035870000000694&_HIER_KEY=601100035870000119530&_LEVEL_ID=A_1_2&_SCENAR
 URL loaded: https://websmp110.sap-ag.de/~form/handler?_APP=00200682500000002033&_EVENT=DISPLAY&_FRAME=NAVIGATION&_HIER_KEY=501100035870000000694&_HIER_KEY=601100035870000119530&_SCENARIO=011000358700
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 palfrey 2009-03-20 16:47:52 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 406462 ***