GNOME Bugzilla – Bug 482843
crash in Computer: search in my homedirecto...
Last modified: 2007-12-21 03:13:50 UTC
Version: 2.18.3 What were you doing when the application crashed? search in my homedirectory ( nfs mount ) Distribution: Gentoo Base System release 1.12.10 Gnome Release: 2.18.3 2007-09-25 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.21-gentoo-r4 #11 SMP PREEMPT Thu Aug 16 17:01:31 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 92999680 vsize: 92999680 resident: 33259520 share: 22032384 rss: 33259520 rss_rlim: 4294967295 CPU usage: start_time: 1190793590 rtime: 3014 utime: 2666 stime: 348 cutime:541 cstime: 52 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 -1227848016 (LWP 23068)] [New Thread -1276863600 (LWP 9515)] 0xb7f248a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 167320
Thread 2 (Thread -1276863600 (LWP 9515))
Thread 1 (Thread -1227848016 (LWP 23068))
----------- .xsession-errors (158961 sec old) --------------------- Loading socket FrontEnd module ... Starting SCIM as daemon ... Loading socket Config module ... Creating backend ... Loading x11 FrontEnd module ... Starting SCIM as daemon ... SCIM has been successfully launched. Launching a SCIM daemon with Socket FrontEnd... Launching a SCIM process with x11... startkde: Shutting down... klauncher: Exiting on signal 1 received SIGHUP, reloading network configuration KWrited - Listening on Device /dev/pts/0 startkde: Running shutdown scripts... startkde: Done. --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui. More details can be found here: http://live.gnome.org/GettingTraces
Hello, i have had the debug option for this packages, see the resultat : ( roumano@dinoutoo.com it's the same as roumano@free.fr ... ) If you want, i can add the debug option to the glibc-2.5-r4 ( for the /lib/libthread_db.so.1 ... ) Memory status: size: 87416832 vsize: 87416832 resident: 28659712 share: 21798912 rss: 28659712 rss_rlim: 4294967295 CPU usage: start_time: 1191486508 rtime: 116 utime: 107 stime: 9 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) ... ... (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1227753808 (LWP 7760)] [New Thread -1301947504 (LWP 7823)] 0xb7f838a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 167636
Thread 2 (Thread -1301947504 (LWP 7823))
Thread 1 (Thread -1227753808 (LWP 7760))
----------- .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 ** Message: drive = 0 ** Message: volume = 0 (nautilus:7760): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed --------------------------------------------------
debug option does not help, see http://live.gnome.org/GettingTraces/DistroSpecificInstructions#head-48a730f2a3b1cc4497e8507a87ecc55320bdb493
More information about the problem : Memory status: size: 89210880 vsize: 89210880 resident: 30486528 share: 22106112 rss: 30486528 rss_rlim: 4294967295 CPU usage: start_time: 1191501632 rtime: 1303 utime: 1139 stime: 164 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1227721040 (LWP 4265)] [New Thread -1314550896 (LWP 26522)] 0xb7f8b8a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 167936
Thread 2 (Thread -1314550896 (LWP 26522))
----------- .xsession-errors (1030 sec old) --------------------- ... (nautilus:4265): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Cannot access memory at address 0x10 Cannot access memory at address 0x10 --------------------------------------------------
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 454799 ***