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 466771 - crash in File Browser: abriendo el dialogo de p...
crash in File Browser: abriendo el dialogo de p...
Status: RESOLVED DUPLICATE of bug 440988
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-14 21:47 UTC by lucascaro
Modified: 2007-08-23 17:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description lucascaro 2007-08-14 21:47:42 UTC 
Version: 2.18.3

What were you doing when the application crashed?
abriendo el dialogo de propiedades de un directorio del navegador de archivos , siempre pero siempre pasa, sin excepcion


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

System: Linux 2.6.22-1-amd64 #1 SMP Sun Jul 29 13:54:41 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Industrial
Icon Theme: gnome

Memory status: size: 482811904 vsize: 482811904 resident: 40734720 share: 16764928 rss: 40734720 rss_rlim: 18446744073709551615
CPU usage: start_time: 1187012248 rtime: 2130 utime: 1903 stime: 227 cutime:8 cstime: 12 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 47757769136976 (LWP 6683)]
(no debugging symbols found)
0x00002b6f72b76c7f in waitpid () from /lib/libpthread.so.0

+ Trace 155242

Thread 1 (Thread 47757769136976 (LWP 6683))

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


----------- .xsession-errors (71346 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
***MEMORY-WARNING***: gconftool-2[1431]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this pro
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
***MEMORY-WARNING***: 
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-08-23 17:30:02 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 ***