Opened 6 years ago

Closed 6 years ago

#11037 closed Bug Report - General (fixed)

OSD message is not working

Reported by: warpme@… Owned by: Raymond Wagner
Priority: minor Milestone: 0.26
Component: MythTV - User Interface Library Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

After 0.25.2->0.26 upgrade I can't working OSD message. I'm using perl to send messages to OSD.

sub send_osd_notify_to_host {
  my ($text,$timeout,$ip) = @_;
  print ("Notify via OSD at IP=$ip with text: \"$text\"\n") if ($debug);
  my $msg = "<mythmessage version=\"1\">
            <text>$text</text>
            <timeout>$timeout</timeout>
        </mythmessage>";
  my $mythnotify_fh = IO::Socket::INET->new(PeerAddr=>$ip,Proto=>'udp',PeerPort=>6948);
  if ($mythnotify_fh) {
    print $mythnotify_fh $msg;
    $mythnotify_fh->close;
    print ("Notify via OSD Done\n") if ($debug);
  }
}

In 0.26 I was able to get it working once, but only once and honestly speaking I don't remember what conditions make it working. I was trying to test this feature by using mythutil utility, unfortunately I get constantly help screen for when calling "mythutil --message "test" ".

Change History (3)

comment:1 Changed 6 years ago by warpme@…

Well, reverting 8532584f4c (Fix UI message interface availability when using MythWelcome?) seems to returning OSD message to working state so this commit is somehow problematic...

comment:2 Changed 6 years ago by Raymond Wagner

Component: MythTV - Video/OSD RenderingMythTV - User Interface Library
Milestone: unknown0.26
Owner: set to Raymond Wagner
Status: newaccepted

comment:3 Changed 6 years ago by Raymond Wagner <rwagner@…>

Resolution: fixed
Status: acceptedclosed

In 3e5bd14de5a0dd4da4c18cdb1a661959f4f8ad9f/mythtv:

Properly initializes UDP message listener.

This properly initializes the ServerPool? reference to NULL in the UDP
Listener class, following 8532584f4, allowing its current state to be
properly detected, and allowing it to be brought up and down
successfully.

Fixes #11037

Note: See TracTickets for help on using tickets.