Bug 493423 – crash in File Browser: ver las propiedades del ...

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 493423 - crash in File Browser: ver las propiedades del ...


Summary:	crash in File Browser: ver las propiedades del ...


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-04 16:38 UTC by learusb
Modified:	2007-11-05 07:46 UTC

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

Description learusb 2007-11-04 16:38:17 UTC

Version: 2.18.3

What were you doing when the application crashed?
ver las propiedades del archivo


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

System: Linux 2.6.21-2-amd64 #1 SMP Tue Jul 10 21:39:38 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Mist

Memory status: size: 311173120 vsize: 311173120 resident: 30007296 share: 17162240 rss: 30007296 rss_rlim: 18446744073709551615
CPU usage: start_time: 1194193903 rtime: 267 utime: 232 stime: 35 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 0x2ac23f4cfbc0 (LWP 16770)]
(no debugging symbols found)
0x00002ac238b5dc7f in waitpid () from /lib/libpthread.so.0

+ Trace 175148

Thread 1 (Thread 0x2ac23f4cfbc0 (LWP 16770))

#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 (47302 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 André Klapper 2007-11-05 07:46:33 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 ***