Comment 9 for bug 1001204

Revision history for this message
paul summers (paulsum) wrote :

know that this would happen again, so I installed a completely new install of mythbuntu (32 bit) , updated to all the usual updates, and installed 0.26 (repository method)... and lo and behold BUG... perhaps it is the amd and nvidia combo LOL... won't be able to test it on an intel processor until i can get one....

in any case it is a strange bug, because mythcommflag is still running, i.e this crash did not disrupt the commercial detection... so i guess that means it "relaunched" where it left off...

being a new install, i have recorded 14 shows, (so 14 mythcommflag queued jobs, but only 12 listed metadata lookups, so maybe it is the metadata lookup that is the problem no?)

but out of the 14 mythcommflag jobs, only 2 failed with exit status 140. (as listed in the job queue)