Bug 339014

Summary:	Solid warns about DBus signal not found in UPower
Product:	[Unmaintained] solid	Reporter:	David Faure <faure>
Component:	libsolid-upower	Assignee:	Lukáš Tinkl <lukas>
Status:	RESOLVED FIXED
Severity:	normal	CC:	simonandric5
Priority:	NOR
Version:	4.13.2
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:	http://commits.kde.org/solid/d5f6f40eb8b6a420520cb7c726959048593d2cab	Version Fixed In:	5.5
Sentry Crash Report:

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