me-tv-development team mailing list archive

[Matthew Vermeulen <MattVermeulen@xxxxxxxxx>]

I think we can safely leave this bug for the time being, since I tried
downgrading a number of releases and I'm starting to see random crashes
and X errors everywhere, even where there were none before, which makes
me suspect that something is rather wrong with my computer. I'm planning
to upgrade to intrepid once the beta comes out (which hopefully fixes a
showstopper bug for me) and will post if this still occurs with a clean
install.

Thanks for all the work so far :)

-- 
Accessing the scheduled recordings window cause crash
https://bugs.launchpad.net/bugs/269991
You received this bug notification because you are a member of Me TV
Development, which is subscribed to Me TV.

Status in Me TV, it's TV for me computer: Incomplete

Bug description:
When trying to access the scheduled recordings window, either by pressing the "Schedule" button, or automatically after scheduling a recording (by clicking on a program in the EPG) me-tv will crash without warning.

Console output:

matthew@matthew-desktop:~/build/me-tv-0.6.0$ me-tv --debug
09/14/08 16:48:03: Me TV 0.6.0
Fontconfig error: "~/.fonts.conf", line 1: XML declaration not well-formed
14/09/08 16:48:04: Setting display channel to 'ABC HDTV' (1)
14/09/08 16:48:04: Waiting for signal lock ...
14/09/08 16:48:04: Got signal lock
The program 'me-tv' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 2469 error_code 2 request_code 58 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)