[mythtv] mythfrontend exits after playing 1 recording (or LiveTV)

[Martin Moeller]

Hi again.

Since I upgradeded recently to latest CVS (first about a week ago and
again tonight) my frontend have exited immediately after on of the
following occurs:

1) I've watched LiveTV and press ESC.
2) I've watched a recording and press ESC.
3) A recording has played all the way through.

It gives me the following output:

-= LiveTV =-

2004-08-31 22:36:10 Connecting to backend server: 192.168.33.11:6543
(try 1 of 5)
2004-08-31 22:36:10 Using protocol version 13
2004-08-31 22:36:10 Using protocol version 13
2004-08-31 22:36:10 Using protocol version 13
2004-08-31 22:36:11 Opening OSS audio device '/dev/dsp'.
2004-08-31 22:36:11 Audio fragment size: 4096
2004-08-31 22:36:11 Using XV port 140
Found 2 Xinerama Screens.
Using screen 1, 1024x768+1280+0
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  141
  Minor opcode:  14
  Resource id:  0x1d0
Couldn't get the color key color, and we need it.
You likely won't get any video.
2004-08-31 22:36:12 Changing from None to WatchingLiveTV
2004-08-31 22:36:28 prebuffering pause

Minor variances in Resource id. I believe the rest is identical

-= Recording =-

2004-08-31 22:41:42 Connecting to backend server: 192.168.33.11:6543
(try 1 of 5)
2004-08-31 22:41:42 Using protocol version 13
2004-08-31 22:41:45 Using protocol version 13
Error loading image file:
/usr/local/share/mythtv/themes/default/1_20040831214300_20040831215000.nuv.png
2004-08-31 22:41:47 Opening OSS audio device '/dev/dsp'.
2004-08-31 22:41:47 Audio fragment size: 4096
2004-08-31 22:41:47 Using XV port 140
Found 2 Xinerama Screens.
Using screen 1, 1024x768+1280+0
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  141
  Minor opcode:  14
  Resource id:  0x1d0
Couldn't get the color key color, and we need it.
You likely won't get any video.
2004-08-31 22:41:48 Changing from None to WatchingPreRecorded

It worked fine with CVS of, of 3 months ago or so.
I tried running it in gdb also, but it didn't seem to get anything
usable out of it. I'm willing to try again with a debug
mythfrontend/backend if that could help.

I'm wondering if this is related to Xinerama in some way. I have not
seen similar problems with a recently setup backend which was done from
scratch (my setup at home have been running since around 0.8 without any
major database surgery). The error doesn't seem to have anything to do
with the database though...

Anyone else having similar problems?
-- 
Martin Moeller <martin at martinm-76.dk>