Bug 339014 - Solid warns about DBus signal not found in UPower
Summary: Solid warns about DBus signal not found in UPower
Status: RESOLVED FIXED
Alias: None
Product: solid
Classification: Unmaintained
Component: libsolid-upower (show other bugs)
Version: 4.13.2
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Lukáš Tinkl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-11 15:31 UTC by David Faure
Modified: 2014-11-09 03:27 UTC (History)
1 user (show)

See Also:
Latest Commit: http://commits.kde.org/solid/d5f6f40eb8b6a420520cb7c726959048593d2cab
Version Fixed In: 5.5
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description David Faure 2014-09-11 15:31:53 UTC 
Almost all KDE apps output this:
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
due to a signal signature change.

How about
1) using QMetaObject to find out the signature of the signal
or if that fails
2) using Introspect and parsing the XML (urgh, I know).

Reproducible: Always

Steps to Reproduce:
1. https://bugs.kde.org/show_bug.cgi?id=330278 for an example
Comment 1 Lukáš Tinkl 2014-11-07 14:20:11 UTC 
Fix warning: No such signal org::freedesktop::UPower::Device...

The signature change can be detected at runtime using Qt's QMetaObject
introspection mechanism. That prevents us from emitting the two
pesky warnings at runtime, polluting our konsoles.

Google is full of that warning, and there is also:
https://bugzilla.redhat.com/show_bug.cgi?id=1056769

REVIEW: 121007

http://commits.kde.org/solid/d5f6f40eb8b6a420520cb7c726959048593d2cab