GNOME Bugzilla – Bug 414097
crash in Zapping TV Viewer: recording tv
Last modified: 2007-05-12 23:40:25 UTC
Version: 0.10cvs6 What were you doing when the application crashed? recording tv Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.19-1.2911.fc6 #1 SMP Sat Feb 10 15:51:47 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 140066816 vsize: 0 resident: 140066816 share: 0 rss: 27308032 rss_rlim: 0 CPU usage: start_time: 1172889744 rtime: 0 utime: 1386 stime: 0 cutime:1155 cstime: 0 timeout: 231 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/zapping' (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 1522928 (LWP 6034)] [New Thread 157768592 (LWP 6055)] [New Thread 147278736 (LWP 6054)] [New Thread 112442256 (LWP 6039)] (no debugging symbols found) 0x00750402 in __kernel_vsyscall ()
+ Trace 115371
Thread 2 (Thread 157768592 (LWP 6055))
----------- .xsession-errors (392410 sec old) --------------------- 2007-02-26 22:46:21.332 rebuffering (28893 32768) 2007-02-26 22:46:21.581 rebuffering (28202 32768) 2007-02-26 22:46:22.146 rebuffering (28477 32768) 2007-02-26 22:46:22.401 rebuffering (26668 32768) 2007-02-26 22:46:22.649 rebuffering (31369 32768) 2007-02-26 22:46:22.979 rebuffering (31066 32768) 2007-02-26 22:46:23.246 rebuffering (28647 32768) 2007-02-26 22:46:23.501 rebuffering (31022 32768) 2007-02-26 22:46:23.750 rebuffering (27418 32768) 2007-02-26 22:46:24.081 rebuffering (19974 32768) 2007-02-26 22:46:24.397 rebuffering (4097 32768) 2007-02-26 22:46:25.033 rebuffering (20123 32768) 2007-02-26 22:46:25.347 rebuffering (23887 32768) ...Too much output, ignoring rest... --------------------------------------------------
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 398582 ***