Opened 12 years ago

Closed 12 years ago

#4366 closed defect (fixed)

Channel scanner crash

Reported by: anonymous Owned by: Isaac Richards
Priority: critical Milestone: unknown
Component: mythtv Version: head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

As soon as I try to scan for channels on my system, mythtv-setup crashes with a segmentation fault.

Attachments (3)

bt.txt (8.9 KB) - added by cg@… 12 years ago.
backtrace
bt2.txt (4.9 KB) - added by cg@… 12 years ago.
Another backtrace
tanthrix-bt.txt (16.9 KB) - added by Tanthrix 12 years ago.
Another backtrace from an A180 scanning crash

Download all attachments as: .zip

Change History (7)

Changed 12 years ago by cg@…

Attachment: bt.txt added

backtrace

Changed 12 years ago by cg@…

Attachment: bt2.txt added

Another backtrace

Changed 12 years ago by Tanthrix

Attachment: tanthrix-bt.txt added

Another backtrace from an A180 scanning crash

comment:1 Changed 12 years ago by Tanthrix

Attached above is a backtrace (hopefully done properly) of mythtv-setup and the segfault that I get when doing a channel scan with my Avermedia A180. To achieve that, all I did was enter into mythtv-setup and do a channel scan of existing transports; the segfault occurs any time myth actually finds a channel and locks onto it during the scanning.

All my existing QAM channels work fine in Myth, I simply cannot scan for new ones or make changes. I tried using "scan" to see if it might be a problem with my card, but it worked fine. I was able to create a full, working channels.conf without problem. I also tried making a new myth database from scratch to see if maybe it was some weird config issue on my end, but I got the same problem.

I believe this has been going on ever since I upgraded to trunk 0.21.20070905-1, 14446M from 0.20.0 or thereabouts. At the very least, I know that since it was working the only changes I have made to this system are with upgrading Myth. No kernel/driver upgrades for my DVB card or anything else. Thanks for looking into this.

comment:2 Changed 12 years ago by cg@…

I'm the original reporter of this ticket. My trouble seems to be related to using VNC for scanning channels and lots of X11-errors that are generated by the scanner. Also, when using a real display (i.e. without vnc), the scanner crashes about once in ten times, though I've not been able to get a backtrace as it doesn't seem to crash when running in GDB (at least after 20 times it didn't).

comment:3 Changed 12 years ago by anonymous

I just upgraded to trunk as of a few days ago, and my channel scanning issue is fixed.

comment:4 Changed 12 years ago by Stuart Auchterlonie

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.