Bug 532981 – crash in Home Folder:

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 532981 - crash in Home Folder:


Summary:	crash in Home Folder:


Status:	RESOLVED DUPLICATE of bug 522534

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:

Depends on:
Blocks:

Reported:	2008-05-13 17:11 UTC by alano.br
Modified:	2008-05-13 17:53 UTC

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

Description alano.br 2008-05-13 17:11:46 UTC

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Fri Apr 18 23:08:22 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola

Memory status: size: 538439680 vsize: 538439680 resident: 43786240 share: 19546112 rss: 43786240 rss_rlim: 18446744073709551615
CPU usage: start_time: 1210683590 rtime: 5216 utime: 4663 stime: 553 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x2ba8c58c0240 (LWP 3899)]
0x00002ba8bf1b6edf in waitpid () from /lib/libpthread.so.0

+ Trace 197638

Thread 1 (Thread 0x2ba8c58c0240 (LWP 3899))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 istr_hash
at nautilus-directory-async.c line 170
#6 ??
from /usr/lib/libglib-2.0.so.0
#7 dequeue_pending_idle_callback
at nautilus-directory-async.c line 848
#8 directory_load_callback
at nautilus-directory-async.c line 1035
#9 ??
from /usr/lib/libgnomevfs-2.so.0
#10 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#11 ??
from /usr/lib/libglib-2.0.so.0
#12 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#13 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#14 main
at nautilus-main.c line 556
#15 __libc_start_main
from /lib/libc.so.6
#16 _start
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (169 sec old) ---------------------
(npviewer.bin:18975): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64
(npviewer.bin:18975): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64
(npviewer.bin:18975): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64
(npviewer.bin:18975): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64
(npviewer.bin:18975): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64
(npviewer.bin:18975): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64
(npviewer.bin:18975): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64
(npviewer.bin:18975): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-05-13 17:53:34 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 522534 ***