Bug 511023 – crash in Computer: While selecting properti...

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 511023 - crash in Computer: While selecting properti...


Summary:	crash in Computer: While selecting properti...


Status:	RESOLVED DUPLICATE of bug 440988

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:	2008-01-21 12:49 UTC by Anivar Aravind
Modified:	2008-01-21 14:18 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description Anivar Aravind 2008-01-21 12:49:36 UTC

Version: 2.18.3

What were you doing when the application crashed?
While selecting properties of a Folder/file gnome crashes always.


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 117403648 vsize: 117403648 resident: 29188096 share: 14348288 rss: 29188096 rss_rlim: 4294967295
CPU usage: start_time: 1200891003 rtime: 12444 utime: 8871 stime: 3573 cutime:637 cstime: 60 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6dbc6b0 (LWP 3707)]
[New Thread 0xb4bc0b90 (LWP 7776)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 186192

Thread 1 (Thread 0xb6dbc6b0 (LWP 3707))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 __kernel_vsyscall
#7 raise
from /lib/i686/cmov/libc.so.6
#8 abort
from /lib/i686/cmov/libc.so.6
#9 g_logv
from /usr/lib/libglib-2.0.so.0
#10 g_log
from /usr/lib/libglib-2.0.so.0
#11 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
#32 node_find_closest
at gsequence.c line 1136
#0 __kernel_vsyscall



----------- .xsession-errors (441848 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-01-21 14:18:37 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 440988 ***