GNOME Bugzilla – Bug 497365
crash in Computer: J'essayais d'accéder aux...
Last modified: 2007-11-16 13:44:47 UTC
Version: 2.18.3 What were you doing when the application crashed? J'essayais d'accéder aux propriétés d'un fichier html (extension .html) dont le contenu est plus que réduit : <FONT size="3"><b>Thierry CHARLES</b><br/> <i>Infass Systèmes</i><br/></FONT> <br/> <FONT size="2">Tel : 02.47.38.20.50<br/> Fax : 02.47.37.22.01<br/></FONT> J'ai eu le meme problème avec un fichier JNLP Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.18infass #1 PREEMPT Thu Oct 25 16:38:03 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gartoon Memory status: size: 79441920 vsize: 79441920 resident: 22745088 share: 14229504 rss: 22745088 rss_rlim: 4294967295 CPU usage: start_time: 1195217954 rtime: 290 utime: 271 stime: 19 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 0xb6d818c0 (LWP 17950)] (no debugging symbols found) 0xb75d1bf1 in waitpid () from /lib/libpthread.so.0
+ Trace 178112
Thread 1 (Thread 0xb6d818c0 (LWP 17950))
----------- .xsession-errors --------------------- ** 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 Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store)) aborting... Failed to read a valid object file image from memory. --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 440988 ***