[mythtv-commits] Ticket #1942: mythtv-0.19_p9163-r1 backend crash
MythTV
mythtv at cvs.mythtv.org
Tue Jun 13 02:01:11 UTC 2006
#1942: mythtv-0.19_p9163-r1 backend crash
-----------------------+----------------------------------------------------
Reporter: anonymous | Owner: ijr
Type: defect | Status: closed
Priority: minor | Milestone:
Component: mythtv | Version:
Severity: medium | Resolution: invalid
-----------------------+----------------------------------------------------
Comment (by bryce at bryceharrington.org):
Thanks, sorry for being a jerk, I didn't realize bugs were closed/invalid
when they just need more info, as a matter of policy as documented at that
howto. I guess mythtv must get a lot of bugs to require such a policy. I
had spent a lot of time searching for a solution before coming to this bug
tracker and was upset that it was rejected. But as stated in that howto,
it is no use getting upset at the person who may be able to fix the
problem.
Anyway, as I mentioned in the original bug report, the bug occurs very
infrequently, but has happened about once a week since I upgraded to 0.19.
(I was running 0.18.1 prior to that for several months on the same
hardware with the same driver, so I am assuming it is something in mythtv,
but don't really know.) I have set up mythbackend in gdb on the chance I
can get a backtrace the next time it crashes. I wish I knew a better way
to trigger the condition that produces the crash so I could provide this
requested information more quickly.
Well, I don't know if anyone looks at bugs once they're closed but figured
just in case I want to explain that I'm not refusing to provide this
information, I just do not have it and do not expect to get it quickly.
And I'm sorry for the smartass reply to ijr.
--
Ticket URL: <http://svn.mythtv.org/trac/ticket/1942>
MythTV <http://www.mythtv.org/>
MythTV
More information about the mythtv-commits
mailing list