trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: September 2010

Network status indicator errors

From: Darrell Anderson <humanreadable@...>
Date: Sun, 19 Sep 2010 09:30:10 -0700 (PDT)
The following errors appear in the xsession logs:

QObject::connect: No such signal MediaImpl::warning(const QString&)
QObject::connect:  (sender name:   'unnamed')
QObject::connect:  (receiver name: 'unnamed')
QObject::connect: No such signal ConnectionManager::statusChanged(QString,NetworkStatus::EnumStatus)
QObject::connect:  (sender name:   'connection_manager')
QObject::connect:  (receiver name: 'networkstatusindicator')
QObject::connect: No such signal ConnectionManager::statusChanged(QString,NetworkStatus::EnumStatus)
QObject::connect:  (sender name:   'connection_manager')
QObject::connect:  (receiver name: 'networkstatusindicator')

I thought the problem might be related to the kded network status daemon. Yet I when I disable that daemon I still see the messages. Maybe the problem is still related to that daemon, I don't know.

Maybe the problem is related to a specific network status applet that typically runs on Debian systems. I think on Debian systems such an applet is presumed, but no such critter on Slackware.

Conversely, after quashing those messages, I'd like to know what specific applet (/usr/bin/???) or daemon the code is looking for. If an external package and not the internal kded daemon, there might be a build script floating around for that package. Possibly then I could install and test Trinity for what is expected to happen with those error messages.

I wish I knew C++ better, but here are some observations:

In kdelibs/networkstatus/connectionmanager.cpp, there are ConnectionManager::status and ConnectionManager::updateStatus functions, but no ConnectionManager::statusChanged. There is a ConnectionManager::slotStatusChanged function.

In kdelibs/networkstatus/connectionmanager.h: there is a void statusChanged function and void slotStatusChanged function.

Based upon the first message, I'm guessing there is a missing #include <mediaimpl.h> statement somewhere.

I'm curious why the error messages reference QObject and Qstring rather than TQObject and TQString.

Anyway, I hope that information helps!

Darrell