summaryrefslogtreecommitdiffstats
path: root/src/widgets/widgets/qlcdnumber.cpp
diff options
context:
space:
mode:
authorThiago Macieira <thiago.macieira@intel.com>2016-03-15 11:00:20 -0700
committerThiago Macieira <thiago.macieira@intel.com>2016-03-19 17:16:52 +0000
commit2e02de165115c9d67ac343ff0960ed80f9c09bc8 (patch)
treebdb47340786db8fdd97a34302eeb2767f340d7a4 /src/widgets/widgets/qlcdnumber.cpp
parent6ec89bec0a2f06365dc18bda6e95b6c253c19227 (diff)
Fix QtDBus deadlock inside kded/kiod
Whenever a message spy was installed, we failed to actually process looped-back messages by queueing them for processing by the spy. That had as a consequence that the caller got an error reply. Worse, since the message had been queued, QtDBus would attempt to deliver it later. Since that message had isLocal==true, bad things happened inside the manager thread. The correct solution is not to queue the message for the filter. If the message is local, then simply deliver directly, as we're still in the user's thread. This used to be the behavior in Qt 5.5. Task-number: QTBUG-51676 Change-Id: I1dc112894cde7121e8ce302ae51b438ade1ff612 Reviewed-by: David Faure <david.faure@kdab.com> Reviewed-by: Dmitry Shachnev <mitya57@gmail.com> Reviewed-by: Jan Kundrát <jkt@kde.org>
Diffstat (limited to 'src/widgets/widgets/qlcdnumber.cpp')
0 files changed, 0 insertions, 0 deletions