Bug 505953 – crash in Home Folder: I selected "propierties"...

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 505953 - crash in Home Folder: I selected "propierties"...


Summary:	crash in Home Folder: I selected "propierties"...


Status:	RESOLVED DUPLICATE of bug 440988

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:	2007-12-27 19:25 UTC by chege
Modified:	2007-12-27 20:22 UTC

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

Description chege 2007-12-27 19:25:12 UTC

What were you doing when the application crashed?
I selected "propierties" on a .jpg file


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

System: Linux 2.6.22-3-vserver-amd64 #1 SMP Sun Nov 4 18:41:00 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 409288704 vsize: 409288704 resident: 37007360 share: 17293312 rss: 37007360 rss_rlim: 18446744073709551615
CPU usage: start_time: 1198779839 rtime: 1732 utime: 1053 stime: 679 cutime:3828 cstime: 1251 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 0x2b02c1aa5540 (LWP 5537)]
0x00002b02bb02b34f in waitpid () from /lib/libpthread.so.0

+ Trace 183254

Thread 1 (Thread 0x2b02c1aa5540 (LWP 5537))

#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 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 ??
from /usr/lib/libgtk-x11-2.0.so.0
#11 node_find_closest
at gsequence.c line 1136
#12 node_insert_sorted
at gsequence.c line 1301
#13 g_sequence_sort_changed_iter
at gsequence.c line 566
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_list_store_set_valist
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_list_store_set
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
from /usr/lib/libeel-2-2.18.so
#18 eel_mime_application_chooser_new
from /usr/lib/libeel-2-2.18.so
#19 is_directory_ready_callback
at fm-properties-window.c line 4436
#20 call_ready_callbacks_at_idle
at nautilus-directory-async.c line 1883
#21 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#22 ??
from /usr/lib/libglib-2.0.so.0
#23 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#24 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#25 main
at nautilus-main.c line 548
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (1258 sec old) ---------------------
** 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
** Message: drive = 0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Cosimo Cecchi 2007-12-27 20:22:04 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 ***