Bug 493197 – crash in Open Folder: trying to view propertie...

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 493197 - crash in Open Folder: trying to view propertie...


Summary:	crash in Open Folder: trying to view propertie...


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:	2007-11-03 22:35 UTC by jguarini
Modified:	2007-11-05 07:47 UTC

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

Description jguarini 2007-11-03 22:35:17 UTC

Version: 2.18.3

What were you doing when the application crashed?
trying to view properties of file


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 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: 387055616 vsize: 387055616 resident: 40534016 share: 17563648 rss: 40534016 rss_rlim: 18446744073709551615
CPU usage: start_time: 1194071511 rtime: 864 utime: 756 stime: 108 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 0x2abd747cfbc0 (LWP 3979)]
(no debugging symbols found)
0x00002abd6de5dc7f in waitpid () from /lib/libpthread.so.0

+ Trace 174964

Thread 1 (Thread 0x2abd747cfbc0 (LWP 3979))

#0 waitpid
from /lib/libpthread.so.0
#1 ??
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib/libc.so.6
#4 abort
from /lib/libc.so.6
#5 g_logv
from /usr/lib/libglib-2.0.so.0
#6 g_log
from /usr/lib/libglib-2.0.so.0
#7 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#8 ??
from /usr/lib/libgtk-x11-2.0.so.0
#9 ??
#10 ??
#11 g_sequence_sort_changed_iter
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_list_store_set_valist
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_list_store_set
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib/libeel-2-2.18.so
#16 eel_mime_application_chooser_new
from /usr/lib/libeel-2-2.18.so
#17 ??
#18 ??
#19 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#20 ??
from /usr/lib/libglib-2.0.so.0
#21 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#22 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#23 main
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (57459 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 André Klapper 2007-11-05 07:47:05 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 ***