Skip to content
This repository was archived by the owner on Sep 16, 2021. It is now read-only.
This repository was archived by the owner on Sep 16, 2021. It is now read-only.

Unresponsiveness/crash when name is queried on a newly found renderer #156

@anantkamath

Description

@anantkamath

If a client listening to the FoundRenderer signal queries the FriendlyName or any other property of the newly found renderer immediately, the renderer dbus service freezes. This and all subsequent calls then result in errors ["org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."]

I'm testing with my own C++ QtDBus client on Arch linux with dleyna-renderer-0.5.0. The same behaviour is also observed with https://github.com/linuxdeepin/deepin-movie which uses PyQt.

Steps to reproduce:

  1. Start client that listens to the FoundRenderer signal
  2. Turn on a DLNA renderer (eg. TV)
  3. Try to read the FriendlyName or any other property upon receiving the signal
    This results in a crash/freeze

Adding an usleep(1000*1000); after the signal is received, before trying to read the FriendlyName prevents the crash for some reason.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions