GNOME Bugzilla – Bug 367608
crash in Terminal: j'essayais d'avoir le co...
Last modified: 2006-11-01 23:41:17 UTC
Version: 2.16.1 What were you doing when the application crashed? j'essayais d'avoir le contrôle du volume son dans tvtime en utilisant sox et les modules saa7134-alsa /saa7134-oss (sur les autres bureaux :gksu nautilus, ooowriter,firefox,synaptic): sudo rmmod saa7134-oss sudo modprobe saa7134-alsa http://gentoo-wiki.com/HARDWARE_saa7134 Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 56868864 vsize: 0 resident: 56868864 share: 0 rss: 17211392 rss_rlim: 0 CPU usage: start_time: 1162202077 rtime: 0 utime: 237 stime: 0 cutime:214 cstime: 0 timeout: 23 it_real_value: 0 frequency: 60 Backtrace was generated from '/usr/bin/gnome-terminal' (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 -1225865552 (LWP 5674)] [New Thread -1250255968 (LWP 5678)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 80411
Thread 1 (Thread -1225865552 (LWP 5674))
This is exactly the same stack trace as in bug 351179, up to frame #33. Now, bug 351179 was marked as a dup of bug 351319, which was fixed in time for 2.16.0. To be honest, I do not see why 351179 was is a dup of 351319... Reporter, could you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
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 351179 ***