GNOME Bugzilla – Bug 541014
crash in Computer: J'ouvrais un fichier tex...
Last modified: 2008-07-01 10:51:41 UTC
Version: 2.20.0 What were you doing when the application crashed? J'ouvrais un fichier texte modifié avec gedit sur ubuntu 8.04 mais créé avec le bloc notes de windows... Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: SphereCrystal Memory status: size: 62517248 vsize: 62517248 resident: 27607040 share: 16121856 rss: 27607040 rss_rlim: 4294967295 CPU usage: start_time: 1214872616 rtime: 496 utime: 468 stime: 28 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6c0e940 (LWP 6394)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 201801
Thread 1 (Thread 0xb6c0e940 (LWP 6394))
----------- .xsession-errors --------------------- ** Message: GetValue variable 1 (1) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) (nautilus:4280): Eel-WARNING **: No extension, not implemented yet seahorse nautilus module initialized Initializing gnome-mount extension (nautilus:6394): Eel-WARNING **: No extension, not implemented yet --------------------------------------------------
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 355018 ***