Accessing the scheduled recordings window cause crash

[Matthew Vermeulen]

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

[Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount)]

Hi Matthew, can you please try --verbose and see if that gives you any more information?

[Matthew Vermeulen (mattvermeulen)]

I don't think there's any extra info on the crash in there... this is the last few seconds of output (once I wait for all the updating of the EPG to finish)... If it'd help at all I can provide the full output..

14/09/08 22:20:11: Writing PAT/PMT header
14/09/08 22:20:13: Writing PAT/PMT header
14/09/08 22:20:15: Writing PAT/PMT header
14/09/08 22:20:17: Writing PAT/PMT header
14/09/08 22:20:18: Command: DELETE FROM SCHEDULED_RECORDING WHERE (START_TIME+DURATION)<1221373218;
14/09/08 22:20:18: Command: SELECT * FROM SCHEDULED_RECORDING
14/09/08 22:20:19: Writing PAT/PMT header
14/09/08 22:20:21: Writing PAT/PMT header
14/09/08 22:20:21: Command: SELECT * FROM SCHEDULED_RECORDING
14/09/08 22:20:21: Command: SELECT * FROM SCHEDULED_RECORDING
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 13301 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.)

[Matthew Vermeulen (mattvermeulen)]

On a related note, I've been seeing this same issue since 0.5.30 ...

[Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount)]

Interesting, so not before 0.5.30?

[Matthew Vermeulen (mattvermeulen)]

Well, 0.5.30 was the earliest I remember seeing it, and I never actually ran
any later releases from the 0.5.x series - I waited until 0.6.0 before
upgrading.

[Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount)]

Try 0.6.1.

[Matthew Vermeulen (mattvermeulen)]

No change :(

[Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount)]

Ok, can you change the video output, try xshm?

[Matthew Vermeulen (mattvermeulen)]

How would I go about doing that... there doesn't seem to be an option in preferences or in ~/.me-tv/xine.config ?

[Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount)]

gconf-editor, /apps/me-tv

[Matthew Vermeulen (mattvermeulen)]

It still crashes... that's not a good sign, is it? ;)

[Matthew Vermeulen (mattvermeulen)]

Still occurs in 0.6.2 :(

[Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount)]

Ok, I'm lost. Can you tell me a bit about your computer?

* Video driver/card
* Linux version
* Does this error occur on any other application?

[Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount)]

Bump

[Matthew Vermeulen (mattvermeulen)]

Sorry for not replying earlier, I wasn't feeling too well when I first got your request and then promptly forgot about it :(

In short,
Hardware:
AMD Athlon64 X2 3800+
nvidia chipset (ethernet etc.)
Nvidia geforce 7600GS 512Mb PCI-E graphics card
1G RAM

Software:
Ubuntu 8.04.1
linux kernel 2.6.24-21-generic
Graphics driver nvidia-glx-new

To the best of my knowledge, I havn't seen this error with other apps before - I'll try to have a bit of a poke around on the weekend and see what happens...

[Matthew Vermeulen (mattvermeulen)]

Here's some other output, from me-tv 0.6.4 - not certain its related... basically i installed 0.6.4, started it, tried to go to the scheduled recordings window, and it crashed with the same error as usual. When I start it again now, the window will appear (the main me-tv window) but then it seems to try to open another window (the scheduled recordings??).. in any case, i think the big difference in this output is the BadWindow and BadGC errors... hope this helps in some way...

matthew@matthew-desktop:~/build/me-tv-0.6.4$ me-tv --verbose
09/30/08 01:23:09: Me TV 0.6.4
30/09/08 01:23:09: Removing /apps/me-tv/profiles
30/09/08 01:23:09: Scanning DVB devices ...
30/09/08 01:23:09: Opening frontend device: /dev/dvb/adapter0/frontend0
30/09/08 01:23:09: Using 'DiBcom 7000MA/MB/PA/PB/MC' (/dev/dvb/adapter0/frontend0)
30/09/08 01:23:09: Using glade file '/usr/share/me-tv/glade/me-tv.glade'
30/09/08 01:23:10: Profile constructor
30/09/08 01:23:10: Channel 'ABC HDTV' added to profile
30/09/08 01:23:10: Loaded channel: ABC HDTV
30/09/08 01:23:10: Channel 'ABC2' added to profile
30/09/08 01:23:10: Loaded channel: ABC2
30/09/08 01:23:10: Channel 'ABC1' added to profile
30/09/08 01:23:10: Loaded channel: ABC1
30/09/08 01:23:10: Channel 'ABC3' added to profile
30/09/08 01:23:10: Loaded channel: ABC3
30/09/08 01:23:10: Channel 'ABC DiG Radio' added to profile
30/09/08 01:23:10: Loaded channel: ABC DiG Radio
30/09/08 01:23:10: Channel 'ABC Dig Jazz' added to profile
30/09/08 01:23:10: Loaded channel: ABC Dig Jazz
30/09/08 01:23:10: Channel 'SBS HD' added to profile
30/09/08 01:23:10: Loaded channel: SBS HD
30/09/08 01:23:10: Channel 'SBS' added to profile
30/09/08 01:23:10: Loaded channel: SBS
30/09/08 01:23:10: Channel 'SBS NEWS' added to profile
30/09/08 01:23:10: Loaded channel: SBS NEWS
30/09/08 01:23:10: Channel 'SBS 2' added to profile
30/09/08 01:23:10: Loaded channel: SBS 2
30/09/08 01:23:10: Channel 'SBS RADIO 1' added to profile
30/09/08 01:23:10: Loaded channel: SBS RADIO 1
30/09/08 01:23:10: Channel 'SBS RADIO 2' added to profile
30/09/08 01:23:10: Loaded channel: SBS RADIO 2
30/09/08 01:23:10: Loaded profile: Default
30/09/08 01:23:10: Updating EPG
30/09/08 01:23:10: Setting display channel to 'ABC HDTV' (1)
30/09/08 01:23:10: Stopping engine
30/09/08 01:23:10: Engine stopped
30/09/08 01:23:10: Thread 'Stream' created
30/09/08 01:23:10: Creating StreamThread
30/09/08 01:23:10: StreamThread created
30/09/08 01:23:10: Removing demuxers
30/09/08 01:23:10: Waiting for signal lock ...
30/09/08 01:23:10: Got signal lock
30/09/08 01:23:10: Found 8 associations
30/09/08 01:23:10: Video PID: 516
30/09/08 01:23:10: Teletext PID: 580
30/09/08 01:23:10: TeleText: Language: 'eng', Type: 0, Magazine Number: 1, Page Number: 82
30/09/08 01:23:10: AC3 PID: 654
30/09/08 01:23:10: Setting video PID filter to 516 (0x204)
30/09/08 01:23:10: Setting AC3 PID filter to 654 (0x28E)
30/09/08 01:23:10: Setting teletext PID filter to 580 (0x244)
30/09/08 01:23:10: Finished setting up DVB
30/09/08 01:23:10: Starting stream thread
30/09/08 01:23:10: Thread 'Stream' started
30/09/08 01:23:10: Writing PAT/PMT header
30/09/08 01:23:10: Thread 'EPG Thread' created
30/09/08 01:2...

[Matthew Vermeulen (mattvermeulen)]

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

[Michael Lamothe (lamothe-deactivatedaccount-deactivatedaccount)]

Hi Matthew, happy to open this back up if it appears again.