Debian Wheezy 7.8 Trinity R14.0.1 KMail 1.9.10
It is a new installation of both Trinity and KMail on a new computer. Initially it worked fine and a pile of new messages downloaded. Now it won't download and I get the error message: 'could not connect to host localhost'
I have run it from a terminal, and I get:
john@Harrier:~$ kmail [TDE NM Backend ERROR] [/tmp/buildd/tdelibs-trinity-14.0.1/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] [/tmp/buildd/tdelibs-trinity-14.0.1/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] [/tmp/buildd/tdelibs-trinity-14.0.1/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 kmail: WARNING: Autosave directory /home/john/.trinity/share/apps/kmail/autosave/cur not found! john@Harrier:~$ WeaverThreadLogger: thread (ID: 1) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 4) suspended. WeaverThreadLogger: thread (ID: 2) suspended. Weaver dtor: destroying inventory. WeaverThreadLogger: thread (ID: 1) destroyed. WeaverThreadLogger: thread (ID: 2) destroyed. WeaverThreadLogger: thread (ID: 3) destroyed. WeaverThreadLogger: thread (ID: 4) destroyed. Weaver dtor: done ^C john@Harrier:~$
When I shut down KMail, the Konsole hung at <Weaver dtor: done>. I then did ^C to shut it down in the Konsole and shut the Konsole.
What do I do to get KMail working, or do I have to put this client back on Icedove and Mbox. :-(
Thanks, Lisi
On Wednesday 19 August 2015 00:55:47 Lisi Reisz wrote:
Debian Wheezy 7.8 Trinity R14.0.1 KMail 1.9.10
In view of what Slávek said above me, it might be pertinent to mention that I installed from his .cz repository.
Lisi
It is a new installation of both Trinity and KMail on a new computer. Initially it worked fine and a pile of new messages downloaded. Now it won't download and I get the error message: 'could not connect to host localhost'
I have run it from a terminal, and I get:
john@Harrier:~$ kmail [TDE NM Backend ERROR] [/tmp/buildd/tdelibs-trinity-14.0.1/tdecore/tdehw/networkbackends/network-m anager/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] [/tmp/buildd/tdelibs-trinity-14.0.1/tdecore/tdehw/networkbackends/network-m anager/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] [/tmp/buildd/tdelibs-trinity-14.0.1/tdecore/tdehw/networkbackends/network-m anager/network-manager.cpp:1803] org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files kmail: WARNING: Autosave directory /home/john/.trinity/share/apps/kmail/autosave/cur not found! john@Harrier:~$ WeaverThreadLogger: thread (ID: 1) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 4) suspended. WeaverThreadLogger: thread (ID: 2) suspended. Weaver dtor: destroying inventory. WeaverThreadLogger: thread (ID: 1) destroyed. WeaverThreadLogger: thread (ID: 2) destroyed. WeaverThreadLogger: thread (ID: 3) destroyed. WeaverThreadLogger: thread (ID: 4) destroyed. Weaver dtor: done ^C john@Harrier:~$
When I shut down KMail, the Konsole hung at <Weaver dtor: done>. I then did ^C to shut it down in the Konsole and shut the Konsole.
What do I do to get KMail working, or do I have to put this client back on Icedove and Mbox. :-(
Thanks, Lisi
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Wednesday 19 of August 2015 02:02:19 Lisi Reisz wrote:
Debian Wheezy 7.8 Trinity R14.0.1 KMail 1.9.10
In view of what Slávek said above me, it might be pertinent to mention that I installed from his .cz repository.
Lisi
Both official R14.0.1 packages, and preliminary stable builds are compiled from identical source packages. So you can expect identical behavior.
On Wednesday 19 August 2015 01:23:55 Slávek Banko wrote:
On Wednesday 19 of August 2015 02:02:19 Lisi Reisz wrote:
Debian Wheezy 7.8 Trinity R14.0.1 KMail 1.9.10
In view of what Slávek said above me, it might be pertinent to mention that I installed from his .cz repository.
Lisi
Both official R14.0.1 packages, and preliminary stable builds are compiled from identical source packages. So you can expect identical behavior.
I (mis?)understood from what you said previously that the mirrors might not be fully populated yet.
Lisi
On Wednesday 19 of August 2015 08:30:03 Lisi Reisz wrote:
On Wednesday 19 August 2015 01:23:55 Slávek Banko wrote:
On Wednesday 19 of August 2015 02:02:19 Lisi Reisz wrote:
Debian Wheezy 7.8 Trinity R14.0.1 KMail 1.9.10
In view of what Slávek said above me, it might be pertinent to mention that I installed from his .cz repository.
Lisi
Both official R14.0.1 packages, and preliminary stable builds are compiled from identical source packages. So you can expect identical behavior.
I (mis?)understood from what you said previously that the mirrors might not be fully populated yet.
Lisi
Ongoing synchronization refers to the official mirrors. On preliminary stable builds repository are the final R14.0.1 packages fully available. Preliminary stable builds repository operate independently of the official build-farm and official mirrors.
On Wednesday 19 August 2015 08:36:33 Slávek Banko wrote:
On Wednesday 19 of August 2015 08:30:03 Lisi Reisz wrote:
On Wednesday 19 August 2015 01:23:55 Slávek Banko wrote:
On Wednesday 19 of August 2015 02:02:19 Lisi Reisz wrote:
Debian Wheezy 7.8 Trinity R14.0.1 KMail 1.9.10
In view of what Slávek said above me, it might be pertinent to mention that I installed from his .cz repository.
Lisi
Both official R14.0.1 packages, and preliminary stable builds are compiled from identical source packages. So you can expect identical behavior.
I (mis?)understood from what you said previously that the mirrors might not be fully populated yet.
Lisi
Ongoing synchronization refers to the official mirrors. On preliminary stable builds repository are the final R14.0.1 packages fully available. Preliminary stable builds repository operate independently of the official build-farm and official mirrors.
We are at cross purposes. I know that. That is why I thought that the Preliminary stable builds repository might be complete and the others not.
Lisi
On Tuesday 18 August 2015 03:55:47 pm Lisi Reisz wrote:
Debian Wheezy 7.8 Trinity R14.0.1 KMail 1.9.10
It is a new installation of both Trinity and KMail on a new computer. Initially it worked fine and a pile of new messages downloaded. Now it won't download and I get the error message: 'could not connect to host localhost'
I have run it from a terminal, and I get:
john@Harrier:~$ kmail [TDE NM Backend ERROR] [/tmp/buildd/tdelibs-trinity-14.0.1/tdecore/tdehw/networkbackends/network-m anager/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] [/tmp/buildd/tdelibs-trinity-14.0.1/tdecore/tdehw/networkbackends/network-m anager/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] [/tmp/buildd/tdelibs-trinity-14.0.1/tdecore/tdehw/networkbackends/network-m anager/network-manager.cpp:1803] org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files kmail: WARNING: Autosave directory /home/john/.trinity/share/apps/kmail/autosave/cur not found! john@Harrier:~$ WeaverThreadLogger: thread (ID: 1) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 4) suspended. WeaverThreadLogger: thread (ID: 2) suspended. Weaver dtor: destroying inventory. WeaverThreadLogger: thread (ID: 1) destroyed. WeaverThreadLogger: thread (ID: 2) destroyed. WeaverThreadLogger: thread (ID: 3) destroyed. WeaverThreadLogger: thread (ID: 4) destroyed. Weaver dtor: done ^C john@Harrier:~$
When I shut down KMail, the Konsole hung at <Weaver dtor: done>. I then did ^C to shut it down in the Konsole and shut the Konsole.
What do I do to get KMail working, or do I have to put this client back on Icedove and Mbox. :-(
Thanks, Lisi
No answer, it seems like a network manager issue. I have the stray .service file error with no affect. I have had more issue with network manager issues than anything else. I stopped using it on my laptop, do not need it on my workstation, nothing to manage, always on connect once and forget it.
Kmail is rock solid, it is getting to be the one compelling reason to stay with TDE, tdepim actually.
On Wednesday 19 August 2015 08:13:15 Lisi Reisz wrote:
On Wednesday 19 August 2015 07:30:56 Lisi Reisz wrote:
On Wednesday 19 August 2015 03:27:33 Greg Madden wrote:
it seems like a network manager issue
Thanks, Greg. I'll investigate.
PEBKAC :-(
That's not very helpful for the archives. At one point some of the settings disappeared. Can't be more helpful than that because I don't know why. I reinstated them, but failed to notice that one of the vanished settings was the mailhost. So originally - settings correct, mail received. Then settings restored without mailhost. Mail not fetched. :-(
There is now a mailhost and mails are fetched.
But I still can't send. :-( Something somewhere must be set to off.
Lisi
On Wed, Aug 19, 2015 at 08:13:15AM +0100, Lisi Reisz wrote:
On Wednesday 19 August 2015 07:30:56 Lisi Reisz wrote:
On Wednesday 19 August 2015 03:27:33 Greg Madden wrote:
it seems like a network manager issue
Thanks, Greg. I'll investigate.
PEBKAC :-(
In my opinion, the only PEBKAC problem there is between the keyboard and chair of the person/people responsible for Network Manager. It is practically malware.
My experience with NM is that it is simply unreliable. It fights with the rest of the system (e.g. ifdown and ifup commands). I used to have NM running on my Debian laptop, and I frequently lost my network connection two or three times a week. Invariably, NM claimed the connection was up and everything was fine, and reconnection did nothing. Stopping and starting did nothing. Only a reboot fixed it, which is unforgiveable in my opinion.
Eventually, the sys admins at work badgered me into uninstalling NM. Since then, I've only lost the network connection a handful of times, and when it drops out,
sudo /etc/init.d/networking restart
fixes it immediately.
Somehow, NM has re-installed itself on my wife's PC, and since then she can't print to a network printer from some applications (while others work fine). Coincidence? I think not.
-
Greg Madden -
Lisi Reisz -
Slávek Banko -
Steven D'Aprano