Bug 494164 – crash in Home Folder: none!

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 494164 - crash in Home Folder: none!


Summary:	crash in Home Folder: none!


Status:	RESOLVED DUPLICATE of bug 439977

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Duplicates:	494166 494167 494168 (view as bug list)
Depends on:
Blocks:

Reported:	2007-11-06 14:08 UTC by win0608
Modified:	2007-11-08 01:28 UTC

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

Description win0608 2007-11-06 14:08:15 UTC

What were you doing when the application crashed?
none!


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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: Fedora

Memory status: size: 118001664 vsize: 118001664 resident: 40681472 share: 23097344 rss: 40681472 rss_rlim: 4294967295
CPU usage: start_time: 1194357841 rtime: 748 utime: 632 stime: 116 cutime:0 cstime: 0 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 -1209149728 (LWP 2703)]
[New Thread -1213056112 (LWP 2969)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 175730

Thread 1 (Thread -1209149728 (LWP 2703))

#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_create_pixmap
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 (14 sec old) ---------------------
Smart Common Input Method 1.4.5
/usr/bin/ccsm
/usr/bin/compiz
/usr/bin/emerald
/usr/bin/metacity
Initializing nautilus-open-terminal extension
/usr/bin/kwin
Initializing nautilus-search-tool extension
** Message: <info>  您现在已连接到有线网络。
** Message: <info>  Activating dialup connection 'njxy via Modem'.
(nautilus:2703): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed
--------------------------------------------------

Comment 1 André Klapper 2007-11-08 01:27:24 UTC

*** Bug 494167 has been marked as a duplicate of this bug. ***

Comment 2 André Klapper 2007-11-08 01:27:28 UTC

*** Bug 494166 has been marked as a duplicate of this bug. ***

Comment 3 André Klapper 2007-11-08 01:27:28 UTC

*** Bug 494168 has been marked as a duplicate of this bug. ***

Comment 4 André Klapper 2007-11-08 01:28:50 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 ***