tvtime crashed with SIGSEGV in __libc_start_main()

[Trevor Card]

Binary package hint: tvtime

tvtime crashes on start up. At first program just did not start but latest update to 10.10 alpha gives window for a few seconds before crashing. Other TV veiwers ( Kaffein and Me TV work ok )

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: tvtime 1.0.2-6ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-12.17-generic 2.6.35-rc6
Uname: Linux 2.6.35-12-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CheckboxSubmission: f110924a265c285e5beda38dcc710a11
CheckboxSystem: edda5d4f616ca792bf437989cb597002
CrashCounter: 1
Date: Mon Aug 2 00:08:49 2010
ExecutablePath: /usr/bin/tvtime
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100701)
ProcCmdline: tvtime
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x407400: mov 0x840(%rdi),%rax
 PC (0x00407400) ok
 source "0x840(%rdi)" (0x00000840) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: tvtime
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main (main=<value optimized out>,
 ?? ()
Title: tvtime crashed with SIGSEGV in __libc_start_main()
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:12978): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (Do:12953): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.
 (nm-applet:12980): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #509314, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.