trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: December 2014

Re: [trinity-users] well, got kmail working, but . . .

From: "Timothy Pearson" <kb9vqf@...>
Date: Fri, 19 Dec 2014 19:32:46 -0600
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224

> . . . in the standard linux tradition, i did some stuff and then got
> the trinity kmail. but this is what the commandline also gave me:
>
> dep@deportable:~$ kmail
> TQSettings::sync: failed to open '/etc/tqt3/tqt_plugins_3.5rc.tmp' for
> writing
> TQSettings::sync: failed to open '/etc/tqt3/tqt_plugins_3.5rc.tmp' for
> writing
> TQSettings::sync: failed to open '/etc/tqt3/tqt_plugins_3.5rc.tmp' for
> writing

This doesn't seem to cause user-visible problems; I'm not sure why TDE
applications try to write into /etc/tqt3.  Sometime I'll have to sit down
and figure it out; filing a low-priority bug report wouldn't be a bad
idea.

> [TDE NM Backend ERROR]
> [/build/buildd/tdelibs-trinity-14.0.0-r1231/tdecore/tdehw/networkbackends/network-manager/network-manager.cpp:1224]
> org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.freedesktop.NetworkManager was not provided by any .service files
> [TDE NM Backend ERROR]
> [/build/buildd/tdelibs-trinity-14.0.0-r1231/tdecore/tdehw/networkbackends/network-manager/network-manager.cpp:1224]
> org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.freedesktop.NetworkManager was not provided by any .service files
> [TDE NM Backend ERROR]
> [/build/buildd/tdelibs-trinity-14.0.0-r1231/tdecore/tdehw/networkbackends/network-manager/network-manager.cpp:1803]
> org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.freedesktop.NetworkManager was not provided by any .service files

All of the above just means you don't have NetworkManager
installed/running, therefore the TDE network manager library won't work
and kmail won't know whether you are online or offline.  If it can't
figure out your online status it assumes you are always offline, which
means that it will keep checking even if your network cable is unplugged. 
Thus, in this situation, kmail essentially falls back to is the way it
always worked--in R14 there was a new feature added so that kmail will
suspend checking if it is aware the network connection is unavailable.

> dep@deportable:~$ WeaverThreadLogger: thread (ID: 1) suspended.
> WeaverThreadLogger: thread (ID: 3) suspended.
> WeaverThreadLogger: thread (ID: 2) suspended.
> WeaverThreadLogger: thread (ID: 4) suspended.

Perfectly normal, means everything is working fine.

> kmail: WARNING: FolderStorage::getMsg was asked for an invalid index.
> idx =1 count()=1

That's a bit weirder; haven't seen that one before.  Is one of your
mailboxes corrupt?  If you don't see any weird behaviour then I guess just
ignore it.

Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iFYEARELAAYFAlSU0b4ACgkQLaxZSoRZrGFddwDfU6YJKqMOFVEiM+ExVmTqb65B
3CJtWAvPhSUBiwDfY6QrWFD0snSfDxQ3vDtRm/w2Y9LtZlqoEzatOA==
=wzRl
-----END PGP SIGNATURE-----