me-tv-development team mailing list archive

[Jeff Bailes <thepizzaking@xxxxxxxxx>]

Public bug reported:

When I attempt to start me-tv 0.6.3, the window pops up but then
disappears after a second or so.  This is the output I get:

jeff@ me-tv
09/29/08 02:21:04: Me TV 0.6.3
29/09/08 02:21:05: Setting display channel to '7 Digital' (8)
29/09/08 02:21:05: Waiting for signal lock ...
29/09/08 02:21:06: Got signal lock
received X error event: BadWindow (invalid Window parameter)
The program 'me-tv' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadGC (invalid GC parameter)'.
  (Details: serial 53 error_code 13 request_code 70 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.)

** Affects: me-tv
     Importance: Undecided
         Status: New

-- 
Failure to start, BadWindow error.
https://bugs.launchpad.net/bugs/275376
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: New

Bug description:
When I attempt to start me-tv 0.6.3, the window pops up but then disappears after a second or so.  This is the output I get:

jeff@ me-tv
09/29/08 02:21:04: Me TV 0.6.3
29/09/08 02:21:05: Setting display channel to '7 Digital' (8)
29/09/08 02:21:05: Waiting for signal lock ...
29/09/08 02:21:06: Got signal lock
received X error event: BadWindow (invalid Window parameter)
The program 'me-tv' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadGC (invalid GC parameter)'.
  (Details: serial 53 error_code 13 request_code 70 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.)