Opened 12 years ago
Closed 9 years ago
#11257 closed Bug Report - General (Fixed)
Users running master with MBE=IPv6 get delayed OSD after recent socket merge
Reported by: | Owned by: | Raymond Wagner | |
---|---|---|---|
Priority: | minor | Milestone: | 0.28 |
Component: | MythTV - General | Version: | Master Head |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
When watching a recording, if ii is pressed, the initial progress bar comes up OK. The OSD is delayed 6 seconds and error messages appear in the frontend log. Also, the playback is stopped during the 6 second period.
Simple workaround; make the Master Server IP equal the Backend Server IP (IPv4) address and set the BE IPv6 address to ::1.
To duplicate:
Set the Master Server IP equal to the Backend Server IP6 e.g. fd00::1 Restart the BE Start a remote FE and begin playback Press i, then i again for the OSD
Full logs run with Master Server IP set to IPv4 and IPv6 addresses attached. Note the line with the IPv6 address that includes the port (followed by the port itself.)
Failed to connect to (FD00::B23:6543:6543) Host unreachable
Attachments (3)
Change History (7)
Changed 12 years ago by
Attachment: | with_ipv4.log added |
---|
Changed 12 years ago by
Attachment: | with_ipv6.log added |
---|
IPv6 case, On Screen Display takes 6 seconds to appear, playback stalls
comment:1 Changed 12 years ago by
Owner: | set to Raymond Wagner |
---|---|
Status: | new → assigned |
comment:2 Changed 11 years ago by
Retested on: v0.27-alpha-85-g0bcc449 (following the recent MythDownloadManager? and ImageCache? related commits.)
The 6 second delay is now gone. The only lines in the FE log after pressing pressing ii (to display the OSD) were:
2013-08-06 21:03:11.061985 W [14319/14319] CoreContext mythcorecontext.cpp:960 (SendReceiveStringList) - SendReceiveStringList(QUERY_SG_FILEQUERY,fd00::b23:6543...) called from UI thread 2013-08-06 21:03:11.065730 W [14319/14319] CoreContext mythcorecontext.cpp:960 (SendReceiveStringList) - SendReceiveStringList(QUERY_SG_FILEQUERY,fd00::b23...) called from UI thread
FWIW, tests were run prior to and then after clearing the FE cache directories. OK to close. (No idea if the two warning messages are acceptable.)
comment:3 Changed 10 years ago by
If this ticket is held open due to the Warning messages in comment 2, they were "temporarily moved" to LOG_DEBUG in [771f2b4]. From my perspective, it remains OK to close.
comment:4 Changed 9 years ago by
Milestone: | unknown → 0.28 |
---|---|
Resolution: | → Fixed |
Status: | assigned → closed |
Originally reported issue has been resolved. Closing.
IPv4 case, works A-OK