[mythtv-users] Mythbackend Segfault on Delete
t004 at kbocek.com
Sat Jan 20 04:26:43 UTC 2007
Does anyone have any suggestions for this problem? I was so hopeful after that
first burst of postings...
Kirk Bocek wrote:
> After I let all the startup messages settle down, as usual, I went into
> mythweb and attempted to delete one recording. the results:
> 2007-01-18 15:46:58.309 MainServer::HandleAnnounce Monitor
> 2007-01-18 15:46:58.310 adding: beryl as a client (events: 0)
> 2007-01-18 15:47:01.020 MainServer::HandleAnnounce Monitor
> 2007-01-18 15:47:01.020 adding: beryl as a client (events: 0)
> 2007-01-18 15:47:01.051 Preview Error: Previewer file
> '/mnt/mythtv/12282_20070118113500.mpg' is not valid.
> 2007-01-18 15:47:01.051 MainServer: Failed to make preview image.
> 2007-01-18 15:47:01.052 MainServer::HandleAnnounce FileTransfer
> 2007-01-18 15:47:01.052 adding: beryl as a remote file transfer
> 2007-01-18 15:47:07.554 RingBuf(/mnt/mythtv/12282_20070118113500.mpg.png):
> Could not open /mnt/mythtv/12282_20070118113500.mpg.png.
> 2007-01-18 15:47:11.574 MainServer::HandleAnnounce Monitor
> 2007-01-18 15:47:11.574 adding: beryl as a client (events: 0)
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1191237984 (LWP 7538)]
> 0x0000000000000000 in ?? ()
> So I tried touching the missing /mnt/mythtv/12282_20070118113500.mpg.png. I
> restarted mythbackend and tried again. Same segfault.
> So I tried manually deleting both files. I reran mythbackend. Same segfault.
> Do you think the issue might be with:
> adding: beryl as a remote file transfer
> This is a master server and everything is local.
> Gareth Glaccum wrote:
>> I think unfortunately that mine might be different. It seems that very
>> recently a patch for generating previews was applied. I think that this
>> should fix my issue. If one of you could perform the following:
>> (stop mythbackend)
>> in a terminal:
>> gdb mythbackend
>> Then cause the segfault
>> -> where
>> and submit the output (and last couple of lines) that may help in
>> determining where the issue is.
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
> mythtv-users mailing list
> mythtv-users at mythtv.org
More information about the mythtv-users