[hotlobster]

Hi

After many test, it seems LIRC.Stop fonction is broken. It always enable it like LIRC.Start:

Code:

curl --get "http://localhost:8080/xbmcCmds/xbmcHttp?command=ExecBuiltIn&parameter=LIRC.Stop"

xbmc log gives:

Code:

INFO: LIRC Initialize: sucessfully started on: /dev/lircd

And XBMC keeps receiving lirc commands.

I'm with svn rev 22283

Thanks.

[hotlobster]

I bump myself. This is a really annoying bug as i can't stop sending lirc event to xbmc.


Could a dev point me in the right direction to check myself what portion of code could be compromised ?

Thanks.

[hotlobster]

Hi

Anybody could help me on this issue ? I'm really stuck with this behavior.

As when i'm on VDR side ( i don't use xbmc pvr for the moment ), booth vdr and xbmc are controlled simultaneously by lirc nows.

On what i saw, it's the g_RemoteControl.Disconnect() function that messes but i don't see why it doesn't works:

Code:

void CRemoteControl::Disconnect()
{
  if (!m_used)
    return;

  if (m_fd != -1)
  {
    m_bInitialized = false;
    if (m_file != NULL)
      fclose(m_file);
    m_fd = -1;
    m_file = NULL;
    if (m_inotify_wd >= 0) {
      inotify_rm_watch(m_inotify_fd, m_inotify_wd);
      m_inotify_wd = -1;
    }
    if (m_inotify_fd >= 0)
      close(m_inotify_fd);
  }
}

[hotlobster]

ok, perhaps I'm the only guy on this forum using this LIRC.stop event feature.
So I will continue to speak to myself. Better than nothing..
I've opend a ticket on Track about this.

http://trac.xbmc.org/ticket/7150

I'm really not sure of what i told, but it seems the bug came after this patch:

http://trac.xbmc.org/changeset/22140


Regards.

[hotlobster]

I'm a poor lonesome cowboy...

[bobo1on1]

Fixed in r23181.

This wasn't at the top of the priority list.

[hotlobster]

Thanks for the fix. Was importantfor me , when browsing TV on vdr, xmbc was launching random movies on his side and used cpu.

Regards.