Opened 6 years ago
Closed 5 years ago
Last modified 5 years ago
#13476 closed Bug Report - General (Abandoned)
mythcommflag Raspberry Pi 4 Mythtv Master Raspbian Buster
| Reported by: | Mike Bibbings | Owned by: | cpinkham |
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | MythTV - Mythcommflag | Version: | v30-fixes |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
mythcommflag fails (exit code 140) with mpeg2 (SD) recorded programs, it works for h264 (HD) recorded programs.
running mythcommflag manually also errored seg fault. Attached : gdbcommands file gdb_mythcommflag.20190818113330.6101.log #gdb backtrace mythcommflag.20190818113330.6101.log.zip # log file
I also tried on a Pi3 running mythtv-light 30 Raspbian Stretch, same problem, exit code 140 for mpeg2, h264 does not error.
It seems the problem is arm related, as mythcommflag works on other systems e.g. amd64 Xubuntu 18.04, Debian Buster.
Attachments (3)
Change History (6)
Changed 6 years ago by
| Attachment: | gdbcommands added |
|---|
Changed 6 years ago by
| Attachment: | gdb_mythcommflag.20190818113814.6160.log added |
|---|
Changed 6 years ago by
| Attachment: | mythcommflag.20190818113814.6160.log.zip added |
|---|
comment:1 Changed 5 years ago by
comment:2 Changed 5 years ago by
| Resolution: | → Abandoned |
|---|---|
| Status: | new → closed |
| Version: | Master Head → v30-fixes |
mythbackend is not officially supported on Raspberry Pi. Since this is now working on master, I am closing it.
comment:3 Changed 5 years ago by
| Milestone: | needs_triage → unknown |
|---|
Note: See
TracTickets for help on using
tickets.
After a comment on mythtv forum https://forum.mythtv.org/viewtopic.php?f=46&t=3699&sid=f27fff36bc46c3c5ce6754b8df4ecf67&start=15#p17739
I have rechecked on my pi4 and mythtv 31 commercial flagging for mpeg2 is no longer failing with exit code 140.
It looks like some later changes to master which became mythtv 31 relatively recently resolved the issue. Current master (32-pre) is also ok, no error code 140.
Suggest this ticket is changed to Version fixes/30.