0.2.3 crashes when trying to list recordings & empty timers list

[kml]

I compiled the new 0.2.3 plugin and tried it out with 0.2.3 dongle. Didn't succeed that well.

When I try to list the recordings, the screen goes black and mvp stops responding to anything.

The vompserver.log just tells that the mvp closed the TCP connection:

19:46:57.496933 [debug]  TCP - TCP has closed socket
19:46:57.497008 [debug]  TCP - TCP has closed socket
19:46:57.497023 [debug]  Client - Received packet, length = 32
19:46:57.497036 [debug]  Client - Detected connection closed
19:46:57.497050 [debug]  Client - MVP client destructor
19:46:57.497062 [debug]  Client - Clean config
19:46:57.507608 [debug]  Config - 2

Tried it with vdr-1.4.0 and vdr-1.3.46. I have the US version of the mvp and
I've been running quite succesfully all the previous versions of vomp including 0.2.2.

Another thing is that for some reason the timer list is empty (and is also empty for
0.2.2). Could it be something to do with vdradmin-am I'm running.
Anybody else use vomp and vdradmin-am? My entries in the timers.conf look like this:

1:T-8438-4097-33:2006-06-02:1925:2003:99:99:Rallin MM-sarja| Kreikka:<vdradmin-am><epgid>506</epgid><autotimer>2</autoti
mer><bstart>5</bstart><bstop>5</bstop><pattern>Rallin MM-sarja</pattern></vdradmin-am>

Does the vompserver get confused with the vdradmin-am tags?

Thanks,

'' kml

[davep]

Another thing is that for some reason the timer list is empty (and is also empty for
0.2.2). Could it be something to do with vdradmin-am I'm running.
Anybody else use vomp and vdradmin-am? My entries in the timers.conf look like this:

1:T-8438-4097-33:2006-06-02:1925:2003:99:99:Rallin MM-sarja| Kreikka:<vdradmin-am><epgid>506</epgid><autotimer>2</autoti
mer><bstart>5</bstart><bstop>5</bstop><pattern>Rallin MM-sarja</pattern></vdradmin-am>

Does the vompserver get confused with the vdradmin-am tags?

I don't think so. I'm running VDR 1.4.0 and the CVS version of vompserver together with vdradmin-am. This is the format of my timers.conf entries:

1:T-9018-16384-16832:2006-05-31:2058:2234:99:99:Silent Britain:<vdradmin-am><epgid>10752</epgid><bstart>2</bstart><bstop>4</bstop></vdradmin-am>

Dave

[MarkC]

I have to agree... Chris and I both use vdradmin-am, and I'm currently running the 0.2.3 dongle with CVS vompserver. Nothing has changed since the release, so my setup sounds the same as yours! (vdr 1.4).

The fact that you're having trouble with recordings AND timers is very strange.

When VOMP crashes with the recording list, does the server side crash too, or just the client?

Could you try to telnet to the MVP (log in as root), kill the running client (killall -9 vompclient), then run /vompclient -d, please? That will show some logging on the client side that might give us a clue.

[Chris]

kml: I doubt it could be anything to do with vdradmin-am. As Mark said, I use it too - though I havn't had an empty timers or recordings list for some time. I have added it as a bug and I will investigate.

[MarkC]

kml: Do you still have this problem? Or has anyone else experienced it?

We can't replicate the bug and we don't know what could be causing it.