me-tv-development team mailing list archive

[Michael Lamothe <michael.lamothe@xxxxxxxxx>]

Sorry, I know it's been a while since I've responded, but I've been busy
attempting a solution to this.  I've completely ripped out the xine
rendering engine and replaced it with a separate spawned xine process.
This has several advantages,

1. No memory leaks
2. If there is a memory leak when rendering then it gets cleaned up when the xine process exits.
3. If the renderer goes down it doesn't have to take the whole application with it.
4. I can "hot potato" any rendering based issues to xine
5. It might solve your issue

Please see if this helps, try revision 224.  This will be released as a
new series, 0.7.  There's a little issue with the mute button but apart
from that the new version seems to work well.  I've been running it for
2 days now.


** Changed in: me-tv
       Status: Incomplete => Fix Committed

-- 
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: Fix Committed

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.)