GNOME Bugzilla – Bug 372960
crash in Home Folder: Choice of Qt contrôl (fr...
Last modified: 2006-11-09 20:32:17 UTC
What were you doing when the application crashed? Choice of Qt contrôl (fr:dans thème, détail du theme, passage au theme Qt) Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 91811840 vsize: 0 resident: 91811840 share: 0 rss: 29179904 rss_rlim: 0 CPU usage: start_time: 1163080930 rtime: 0 utime: 2988 stime: 0 cutime:2772 cstime: 0 timeout: 216 it_real_value: 0 frequency: 15 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1227192656 (LWP 6609)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 84737
Thread 1 (Thread -1227192656 (LWP 6609))
see also the next bug #372960 and the #352265 Many test, and the bug sem's to happen when I go out the QT control theme. Some bug of the deskbar in the same time: (french name) volume, and monteur systéme et moniteur réseau in the same time ~5 gnome-netstatus-rapport-d-anomalies.txt. one of them (the first I think) Memory status: size: 41447424 vsize: 0 resident: 41447424 share: 0 rss: 11968512 rss_rlim: 0 CPU usage: start_time: 1163080941 rtime: 0 utime: 654 stime: 0 cutime:628 cstime: 0 timeout: 26 it_real_value: 0 frequency: 16 Backtrace was generated from '/usr/libexec/gnome-netstatus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225754960 (LWP 6685)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 84741
Thread 1 (Thread -1225754960 (LWP 6685))
*** Bug 372961 has been marked as a duplicate of this bug. ***
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 364396 *** *** This bug has been marked as a duplicate of 364396 ***