Opened 5 years ago

Closed 5 years ago

#12154 closed Bug Report - Hang/Deadlock (Unverified)

3458cc3 causes FE to hang during playback

Reported by: Bill Meek <keemllib@…> Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

With the above commit applied, when watching a recording and pressing the Volume Down control on my keyboard the screen goes black and in about 2 seconds returns to the recording only it appers to be paused. Pressing P doesn't restart it.

Nor does pressing any other 'typical' MythTV key like Enter, i, Left Arrow etc.

I can use Ctrl-Alt-Left/Right/Up/Down? to navigate between my four screens. The programs running on the other 3 screens run OK and accept keyboard input fine.

mythfrontend must be killed and restarted to recover.

Also note that while watching a recording, the same symptoms can be duplicated by using Ctrl-Alt-<any arrow> to view another screen.

I'm running on Ubuntu 14.04 with lightdm FWIW. The Nvidia version is: 304.117.

The git bisect was done while the backend was running on v0.28-pre-1419-g62eaa39.

Git bisect results, gdb during the hang and FE logs are attached.

Attachments (3)

fe-hung-bisect (4.0 KB) - added by Bill Meek <keemllib@…> 5 years ago.
git bisect
fe-hung-gdb+version (142.8 KB) - added by Bill Meek <keemllib@…> 5 years ago.
gdb output + full mythfrontend --version
fe-hung-mythfrontend.log (14.1 KB) - added by Bill Meek <keemllib@…> 5 years ago.
FE log

Download all attachments as: .zip

Change History (5)

Changed 5 years ago by Bill Meek <keemllib@…>

Attachment: fe-hung-bisect added

git bisect

Changed 5 years ago by Bill Meek <keemllib@…>

Attachment: fe-hung-gdb+version added

gdb output + full mythfrontend --version

Changed 5 years ago by Bill Meek <keemllib@…>

Attachment: fe-hung-mythfrontend.log added

FE log

comment:1 Changed 5 years ago by Bill Meek <keemllig@…>

After all that, I started looking in Setup via the GUI.

"Vertical scaling" was set to 2 (which I've had for years.) I reset it to 0 and the symptoms went away. However, when I changed it back to 2, the symptoms didn't come back.

AlwaysOnTop? was set to 0 during the above. I'll keep trying to duplicate this, but for now it's OK to close. Sorry for the noise, but at least it's documented.

comment:2 Changed 5 years ago by stuartm

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