Opened 16 years ago
Closed 16 years ago
#7423 closed defect (fixed)
Edit recording schedule from OSD brings up progfinder then segfault
| Reported by: | gigem | Owned by: | gigem |
|---|---|---|---|
| Priority: | major | Milestone: | unknown |
| Component: | MythTV - General | Version: | 0.22rc1 |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
Start playing a recording.
Using the OSD menu, choose "Schedule Recordings"/"Edit Recording Schedule".
The progfinder comes up instead of the rule editor.
At this point, presssing escape to exit the progfinder causes a segfault.
Note that this behavior was produced from a frontend built with --compile_type=profile. The gdb-profile.txt backtrace is from that build.
When I rebuilt the frontend with --compile_type=debug, the results were slightly different. The progfinder still came up instead of the rule editor. Pressing escape at this point, however, resulted in the "Please wait" playback startup message and the frontend was unresponsive after that. The gdb-debug.txt backtrace is from pressing control-c at that point.
Attachments (3)
Change History (5)
Changed 16 years ago by
| Attachment: | gdb-profile.txt added |
|---|
comment:1 Changed 16 years ago by
| Owner: | changed from Isaac Richards to gigem |
|---|---|
| Status: | new → assigned |
This looks to be a MythUI porting issue. Since I've started to look into it, however, I'm going to take ownership of it. Stuart, don't be surprised, though, if I ask for your help or give this to you outright. #7422 is probably related to the same underlying problem, so I'm going to do the same with it.
Refs #7422
Changed 16 years ago by
| Attachment: | 7423-2.patch added |
|---|
Proposed fix to be committed after more testing
comment:2 Changed 16 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Fixed a typo which caused ProgFinder? to be run instead of ScheduleEditor? when done so from the OSD.
Fixed ScheduleEditor? and ViewScheduled? to notify TV they are finished when run from the OSD.
Fixed RecordingRule? to start a new rule when trying to edit a previously deleted rule. This is how pre-0.22 behaved. A future change might present a popup letting the user choose whether or not to proceed.
Backtrace from --compile_type=profile build