GNOME Bugzilla – Bug 490324
crash in Volume Control: no se
Last modified: 2007-10-27 17:26:47 UTC
Version: 2.18.0 What were you doing when the application crashed? no se Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 42323968 vsize: 42323968 resident: 13975552 share: 10264576 rss: 13975552 rss_rlim: 4294967295 CPU usage: start_time: 1193355188 rtime: 66 utime: 53 stime: 13 cutime:5 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-volume-control' (no debugging symbols found) Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208719120 (LWP 4590)] (no debugging symbols found) 0x00344402 in __kernel_vsyscall ()
+ Trace 172891
Thread 1 (Thread -1208719120 (LWP 4590))
----------- .xsession-errors (58 sec old) --------------------- V4L2Grabber::~V4L2Grabber(): deleted. ~ScimInputContextPlugin() Reiniciando tvtime. Leyendo la configuración de /etc/tvtime/tvtime.xml Leyendo la configuración de /root/.tvtime/tvtime.xml /root/.tvtime/stationlist.xml: No existing NTSC-JP station list "US-Cable". ICE default IO error handler doing an exit(), pid = 4582, errno = 0 Reiniciando tvtime. Leyendo la configuración de /etc/tvtime/tvtime.xml Leyendo la configuración de /root/.tvtime/tvtime.xml /root/.tvtime/stationlist.xml: No existing PAL-60 station list "US-Cable". Reiniciando tvtime. Leyendo la configuración de /etc/tvtime/tvtime.xml Leyendo la configuración de /root/.tvtime/tvtime.xml Gracias por usar tvtime. --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 471133 ***