Opened 14 years ago
Closed 11 years ago
#9654 closed Patch - Bug Fix (Works for me)
[PATCH] Fix SEGV faults in mythfrontend during backend selection
Reported by: | Owned by: | sphery | |
---|---|---|---|
Priority: | minor | Milestone: | 0.26 |
Component: | MythTV - User Interface Library | Version: | Master Head |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
This patch fixes several segv faults and logic problems with mythfrontend during backend configuration either after a fresh install or by specifying the -p option.
1 Can't select Manual dbase configuration with -p option
2 Can't Cancel
3 Segv after selecting Save on win32
4 Segv in ShowOkPopup? due to stale static data
5 Segv in MythScreenStack::PopScreen? due to null pointer
Attachments (1)
Change History (10)
Changed 14 years ago by
Attachment: | be-select.diff added |
---|
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
All apart from 1 are reproducible on both Linux & Windows. The exception is the seg fault when you select Save caused by a NULL m_XML in BackendSelection::Accept
- Start "mythfrontend -p", select language, tab to Manual and click. If your setup conforms to defaults you'll go to the root menu. If you have anything unusual you'll get a dialog - Cannot login.
- Start "mythfrontend -p", select language, tab to cancel and click, same result as 1.
- Win32 only: Start "mythfrontend -p", select language, tab to Save and click - SEGV
- Start "mythfrontend -p", select language, tab to cancel and click - Cannot login. Click cancel again - SEGV
comment:3 Changed 14 years ago by
Owner: | changed from stuartm to sphery |
---|---|
Status: | new → accepted |
comment:4 Changed 13 years ago by
Milestone: | unknown → 0.25 |
---|
comment:6 Changed 13 years ago by
Priority: | minor → blocker |
---|
comment:7 Changed 13 years ago by
Priority: | blocker → minor |
---|
comment:8 Changed 13 years ago by
Milestone: | 0.25 → unknown |
---|
All that is pending is:
Segv after selecting Save on win32
comment:9 Changed 11 years ago by
Milestone: | unknown → 0.26 |
---|---|
Resolution: | → Works for me |
Status: | accepted → closed |
Code has changed significantly since this ticket was opened, the one remaining issue on win32 may or may not be fixed, but we'd need an updated patch. I'd suggest a new ticket is created if the bug persists.
Are these issues reproducible on other platforms? I can't reproduce any of them.