WARNING: DCOPReply<QString>: cast to
'TQString' error
QObject::connect: No such signal
ConnectionManager::statusChanged(NetworkStatus::EnumStatus)
QObject::connect: (sender
name: 'connection_manager')
QObject::connect: (receiver name:
'networkstatusindicator')
QObject::connect: No such signal
ConnectionManager::statusChanged(NetworkStatus::EnumStatus)
QObject::connect: (sender
name: 'connection_manager')
QObject::connect: (receiver name:
'networkstatusindicator')
So again, seems there is some kind of
Debianization here looking for some
kind of network manager that does not exist on
Slackware.
That looks more like OpenSUSE code IMHO. I'm not
going to spend a lot of
time tracking them down right now, as they are pretty
much harmless and
fall into the irritant category.
[...]
Actually this it a Qt warning, when an inexistent signal (or wrongly defined) is connected to a slot. I think that the code is unfinished or something like this.
Yet since most/all of the Trinity code has been modified to use the tqtinterface, why would the messages reference QObject rather than TQObject?
The stock Slackware does not provide any network status indicators. Whereever this code is being generated, a test is needed to verify the expected status tool is actually running.