Bug 488946 – crash in Open Folder: Went to lunch. This has ...

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 488946 - crash in Open Folder: Went to lunch. This has ...


Summary:	crash in Open Folder: Went to lunch. This has ...


Status:	RESOLVED DUPLICATE of bug 439977

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-22 10:32 UTC by peter.follo
Modified:	2007-10-22 11:31 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description peter.follo 2007-10-22 10:32:05 UTC

Version: 2.18.3

What were you doing when the application crashed?
Went to lunch. This has happen several times before.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 652070912 vsize: 652070912 resident: 367267840 share: 10711040 rss: 367267840 rss_rlim: 4294967295
CPU usage: start_time: 1193037433 rtime: 7452 utime: 6615 stime: 837 cutime:1 cstime: 21 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209125152 (LWP 1353)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 171895

Thread 1 (Thread -1209125152 (LWP 1353))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
from /usr/lib/libgnome-desktop-2.so.2
#5 ??
from /usr/lib/libgnome-desktop-2.so.2
#6 ??
from /usr/lib/libgnome-desktop-2.so.2
#7 gnome_bg_changes_with_size
from /usr/lib/libgnome-desktop-2.so.2
#8 ??
from /usr/lib/libeel-2.so.2
#9 ??
from /usr/lib/libeel-2.so.2
#10 ??
from /usr/lib/libeel-2.so.2
#11 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#12 g_closure_invoke
from /lib/libgobject-2.0.so.0
#13 ??
from /lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#15 g_signal_emit
from /lib/libgobject-2.0.so.0
#16 ??
from /usr/lib/libeel-2.so.2
#17 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#18 g_closure_invoke
from /lib/libgobject-2.0.so.0
#19 ??
from /lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#21 g_signal_emit
from /lib/libgobject-2.0.so.0
#22 ??
from /usr/lib/libgnome-desktop-2.so.2
#23 ??
from /usr/lib/libeel-2.so.2
#24 ??
from /usr/lib/libeel-2.so.2
#25 ??
#26 ??
#27 ??
from /lib/libglib-2.0.so.0
#28 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#29 ??
from /lib/libglib-2.0.so.0
#30 g_main_loop_run
from /lib/libglib-2.0.so.0
#31 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#32 main
#0 __kernel_vsyscall



----------- .xsession-errors (22 sec old) ---------------------
end from FAM server connection
end from FAM server connection
Fönsterhanterarvarning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3000449 (Poppupp)
Fönsterhanterarvarning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
end from FAM server connection
end from FAM server connection
end from FAM server connection
end from FAM server connection
end from FAM server connection
end from FAM server connection
end from FAM server connection
end from FAM server connection
end from FAM server connection
(nautilus:1353): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed
--------------------------------------------------

Comment 1 André Klapper 2007-10-22 11:31:24 UTC

Thanks for the bug report. 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 439977 ***