Opened 14 years ago
Closed 14 years ago
#9735 closed Bug Report - Crash (Invalid)
SIGSEGV in mythsetup
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | MythTV - General | Version: | 0.24-fixes |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
Forwarding upstream. I realize interest in mythsetup is low with web-based setup in the works, but forwarding since time frame of that feature is unknown and 0.24 is the current release and is widely used. Also didn't know if this might be more of a library problem that, if fixed, might help fix backend or frontend.
Originally filed here: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/763655
Attachments (2)
Change History (4)
Changed 14 years ago by
| Attachment: | var.log.mythtv.mythbackend.log.txt added |
|---|
Changed 14 years ago by
| Attachment: | ThreadStacktrace.txt added |
|---|
comment:1 Changed 14 years ago by
| Type: | Bug Report - General → Bug Report - Crash |
|---|
comment:2 Changed 14 years ago by
| Resolution: | → Invalid |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
I think this report is going to be impossible to fix from the information provided (including information in Ubuntu bug report). The crash was in mythtv-setup, but a mythbackend log was provided. The backtrace was created without debug symbols, so there's not much of any information in there, and there was no description at all about what actions the user performed that led to the crash.
Note, also, that I'll be fixing some mythtv-setup segfaults next week (#9654 (which has patches), and #9744 (which is likely a dup of #9654)), that may also fix the issue the user encountered.
I'm closing this as invalid, but if it's possible to get more information and a new backtrace with symbols, feel free to re-open it.