[mythtv-users] Error opening jump program file buffer

[Douglas Peale]

This bug has existed for too long.

taken from http://code.mythtv.org/trac/ticket/9177#comment:30
>
>Comment (by mdean):
>
>Please take all the discussion and "me too" posts to the users mailing
>list.  This ticket is already long enough that it will be hard for
>developers to find the important/relevant information in the 30 comments.
>
>The generic error message, "Error opening jump program file buffer,"
>describes the final symptom of many different problems--the file MythTV is
>supposed to play back in Live TV doesn't exist.  This problem can be
>caused by system or MythTV misconfiguration or, in some cases, MythTV code
>failures.
>
>Therefore, it is quite possible some of these "me too" posts are actually
>seeing different problems (such as having incorrect file system
>permissions, using NFS without disabling file system attribute caching,
>having incorrect times on frontend or backend systems, having
>misconfigured Input Connections, or many other problems with the
>underlying system) and can fix their configurations.  This applies
>especially to those who have only NTSC (SDTV) channels and a single tuner
>(because, obviously, they cannot have a case where they switch from SDTV
>to HDTV channels).
>
>Until we know it's a MythTV code failure, discussion should occur on list.
>And, even once we find it's a MythTV code failure, we need to identify
>whether it's the same issue that was reported here or if it needs its own
>ticket.  And, if you are not seeing the same issue as the original
>reporter, posting to this ticket is not going to help you get your issue
>fixed (as you won't get instructions on how to fix system misconfiguration
>here and the developer who fixes this issue will be focused on the
>originally reported issue).
>
>In other words, having the message, "Error opening jump program file
>buffer," in your logs messages does /not/ mean you are seeing the same
>issue as the original reporter.

The way I read that post, "Until we know it's a MythTV code failure, discussion should occur on list." it implies that the
developers are currently assuming that all "error opening jump program file buffer" errors are configuration errors and not bugs.

"And, even once we find it's a MythTV code failure, we need to identify whether it's the same issue that was reported here or if
it needs its own ticket"

Given that many different kinds of errors generate the "Error opening jump program file buffer" I would like to know how we as
users are supposed to identify the cause of the problem so we can fix our configurations or open new tickets.

Perhaps the many different causes of "Error opening jump program file buffer" should be broken out and each given its own error
message.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
Url : http://www.mythtv.org/pipermail/mythtv-users/attachments/20110611/b63ddcf8/attachment.bin