hi, everybody . . .
so i'm using tde 14.0.5 atop ubuntu 18.04. all was tickety boo until yesterday, when kmail would no longer connect and download my mail after due course it says the connection to the server unexpectedly closed. after fiddling with this for awhile, i decided it might be useful to start kmail from the cl and see what it had to say. it was this:
[TDE NM Backend ERROR] [/build/buildd/tdelibs-trinity-14.0.5/tdecore/tdehw/networkbackends/network-manager/network-manager.cpp:1707] Attempting to access the network-manager VPN service returned: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager.VPN.Plugin was not provided by any .service files dep@dep-desktop:~$ WeaverThreadLogger: thread (ID: 1) suspended. WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 4) 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
i haven't the foggiest notion what any of this means and, more important, i have no idea how to fix it. anyone here ever cncounter this? anyone know how i can fix it?
thanks.
dep Sent with ProtonMail. Because privacy matters.
dep wrote:
[TDE NM Backend ERROR]
[[/build/buildd/tdelibs-trinity-14.0.5/tdecore/tdehw/networkbackends/network-manager/network-manager.cpp:1707]
[Attempting to access the network-manager VPN service returned: [org.freedesktop.DBus.Error.ServiceUnknown: The name [org.freedesktop.NetworkManager.VPN.Plugin was not provided by any [.service files
this is network-manager related - nothing to do with kmail
dep@dep-desktop:~$ WeaverThreadLogger: thread (ID: 1) suspended. WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 4) 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
this is when you shut down kmail and has nothing to do with the described problem
i haven't the foggiest notion what any of this means and, more important, i have no idea how to fix it. anyone here ever cncounter this? anyone know how i can fix it?
can you connect to your mail server - is it mail server at all?
BTW you were using this proton mail thingie - yes?
On Wednesday, January 16, 2019 4:12 PM, deloptes deloptes@gmail.com wrote:
dep wrote:
[TDE NM Backend ERROR]
[[/build/buildd/tdelibs-trinity-14.0.5/tdecore/tdehw/networkbackends/network-manager/network-manager.cpp:1707]
[Attempting to access the network-manager VPN service returned: [org.freedesktop.DBus.Error.ServiceUnknown: The name [org.freedesktop.NetworkManager.VPN.Plugin was not provided by any [.service files
this is network-manager related - nothing to do with kmail
Okay -- it's kmail that's not working, but it's a Trinity error, no?
dep@dep-desktop:~$ WeaverThreadLogger: thread (ID: 1) suspended. WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 4) 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
this is when you shut down kmail and has nothing to do with the described problem
Only the last five lines. The first four lines appear instantly when I *start* kmail.
i haven't the foggiest notion what any of this means and, more important, i have no idea how to fix it. anyone here ever cncounter this? anyone know how i can fix it?
can you connect to your mail server - is it mail server at all?
BTW you were using this proton mail thingie - yes?
I haven't any idea as to the architecture but yes, there is the ProtonMail Bridge, which is a piece of middleware that handles the encryption/decryption of messages. KMail accesses it through ports 1143 and 1025 which are 1000 above the customary, with the host being 127.0.0.1.
The same configuration was working fairly well until yesterday.
dep Sent with ProtonMail. Because privacy matters.
dep wrote:
dep@dep-desktop:~$ WeaverThreadLogger: thread (ID: 1) suspended. WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 4) 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
this is when you shut down kmail and has nothing to do with the described problem
Only the last five lines. The first four lines appear instantly when I *start* kmail.
so are you sure you don't have anything running twice - I mean kmail?
i haven't the foggiest notion what any of this means and, more important, i have no idea how to fix it. anyone here ever cncounter this? anyone know how i can fix it?
can you connect to your mail server - is it mail server at all?
BTW you were using this proton mail thingie - yes?
I haven't any idea as to the architecture but yes, there is the ProtonMail Bridge, which is a piece of middleware that handles the encryption/decryption of messages. KMail accesses it through ports 1143 and 1025 which are 1000 above the customary, with the host being 127.0.0.1.
The same configuration was working fairly well until yesterday.
Did you reboot in the mean while? Does it work after reboot?
On Thursday, January 17, 2019 2:21 AM, deloptes deloptes@gmail.com wrote:
so are you sure you don't have anything running twice - I mean kmail?
yup, at least if the command killall kmail followed by top are any indication.
Did you reboot in the mean while? Does it work after reboot?
i've rebooted a few times, no joy. i've looked at ~/.xsession-errors and there's nothing pertinent. (though i did see an error that the dropbox binary is not found, which raises another issue: where might i edit things that autostart? dropbox did, though i've long since deleted it, and protonmail bridge does. might be useful to remove it from autostart and then start it manually -- in fact, i'd prefer to do it that way. any idea how to go over the autostart stuff and prune the stuff i don't want?)
at this point i'm not sure whether it is kmail or protonmail bridge that's causing the problem. the error thrown: "The connection to the server DrippingWithIrony was unexpectedly closed or timed out. It will be re-established automatically if possible." I am not certain that it ever gets established.
the issue is this: the only linux mail client officially supported by protonmail bridge is thunderbird, which i'd use if it supported maildir, but it doesn't and i see no reason to think it ever will. configuring protonmail bridge is actually fairly straightforward -- both incoming and outgoing use 127.0.0.1. imap is port 1143; smtp is 1025. there is an elaborate password, which i get from protonmail bridge itself.
starting the bridge from a terminal throws this:
dep@dep-desktop:~$ Desktop-Bridge DEBU[0000] main init goroutine=1 pid=12511 pkg=init INFO[0000] init error: <nil> goroutine=1 pid=12511 pkg=init
and it seems then to start. i do not know, though, what normal behavior would be -- could be that it's working just fine.
would be nice if there were a privacy-oriented email service that used gpg or the like and didn't read/scan/track email. best i can tell, there isn't, which is why i use protonmail.
dep Sent with ProtonMail. Because privacy matters.
dep wrote:
On Thursday, January 17, 2019 2:21 AM, deloptes deloptes@gmail.com wrote:
so are you sure you don't have anything running twice - I mean kmail?
yup, at least if the command killall kmail followed by top are any indication.
Did you reboot in the mean while? Does it work after reboot?
i've rebooted a few times, no joy. i've looked at ~/.xsession-errors and there's nothing pertinent. (though i did see an error that the dropbox binary is not found, which raises another issue: where might i edit things that autostart? dropbox did, though i've long since deleted it, and protonmail bridge does. might be useful to remove it from autostart and then start it manually -- in fact, i'd prefer to do it that way. any idea how to go over the autostart stuff and prune the stuff i don't want?)
~/.trinity/Autostart/
or the files sourced
at this point i'm not sure whether it is kmail or protonmail bridge that's causing the problem. the error thrown: "The connection to the server DrippingWithIrony was unexpectedly closed or timed out. It will be re-established automatically if possible." I am not certain that it ever gets established.
sometimes strace helps in such cases
the issue is this: the only linux mail client officially supported by protonmail bridge is thunderbird, which i'd use if it supported maildir, but it doesn't and i see no reason to think it ever will. configuring protonmail bridge is actually fairly straightforward -- both incoming and outgoing use 127.0.0.1. imap is port 1143; smtp is 1025. there is an elaborate password, which i get from protonmail bridge itself.
don't know - you should be able to check those even with telnet
starting the bridge from a terminal throws this:
dep@dep-desktop:~$ Desktop-Bridge DEBU[0000] main init goroutine=1 pid=12511 pkg=init INFO[0000] init error: <nil> goroutine=1 pid=12511 pkg=init
and it seems then to start. i do not know, though, what normal behavior would be -- could be that it's working just fine.
would be nice if there were a privacy-oriented email service that used gpg or the like and didn't read/scan/track email. best i can tell, there isn't, which is why i use protonmail.
no one argues against. I just asked because I recall you were writing about it, so it looks like kmail is not able to authenticate against your local protonmail instance.
what happens if you check in the settings of the account for example security or something - could be ssl certificate expired or who knows what.
regards
On Thursday, January 17, 2019 2:59 PM, deloptes deloptes@gmail.com wrote:
~/.trinity/Autostart/
or the files sourced
All I found in that directory was a file, .directory, which listes many translations of the word "Autostart".
at this point i'm not sure whether it is kmail or protonmail bridge that's causing the problem. the error thrown: "The connection to the server DrippingWithIrony was unexpectedly closed or timed out. It will be re-established automatically if possible." I am not certain that it ever gets established.
sometimes strace helps in such cases
I have no idea what the results are supposed to look like, so I have no idea whether it's showing anything anomalous. Perhaps you would be able to read it, but I can make no sense of it.
the issue is this: the only linux mail client officially supported by protonmail bridge is thunderbird, which i'd use if it supported maildir, but it doesn't and i see no reason to think it ever will. configuring protonmail bridge is actually fairly straightforward -- both incoming and outgoing use 127.0.0.1. imap is port 1143; smtp is 1025. there is an elaborate password, which i get from protonmail bridge itself.
don't know - you should be able to check those even with telnet
Not sure how I'd do that, but a check of the ports tells me that the bridge is listening:
Desktop-Bridge 4392 dep 11u IPv4 34290 0t0 TCP 127.0.0.1:1143 (LISTEN) Desktop-Bridge 4392 dep 12u IPv4 33466 0t0 TCP 127.0.0.1:1025 (LISTEN)
Which I imagine is expected behavior. Nor are there failure to login errors from kmail.
no one argues against. I just asked because I recall you were writing about it, so it looks like kmail is not able to authenticate against your local protonmail instance.
Right. I can view mail through the webmail version of Protonmail -- that's how I'm writing this -- but after months of being able, with reasonable success, to use ProtonMail bridge I now can't, and I can't figure out any diagnostics for determining what got broken.
what happens if you check in the settings of the account for example security or something - could be ssl certificate expired or who knows what.
If there were a certificate problem, wouldn't kmail throw an error? There are no security settings as such with Protonmail Bridge, and the settings in kmail appear to be correct.
What I need to find out is if kmail is actually communicating with Protonmail Bridge. If it is, then I need to find out if Protonmail Bridge is communicating with the server in Switzerland. And I have no idea how to do either of those things.
dep Sent with ProtonMail. Because privacy matters.
dep wrote:
On Thursday, January 17, 2019 2:59 PM, deloptes deloptes@gmail.com wrote:
~/.trinity/Autostart/
or the files sourced
All I found in that directory was a file, .directory, which listes many translations of the word "Autostart".
ok so it is not autostarted by entry there - I don't remember where TDE is writing which apps were running when it stopped, so that it starts them next time .... there should be something in ~/.trinity
at this point i'm not sure whether it is kmail or protonmail bridge that's causing the problem. the error thrown: "The connection to the server DrippingWithIrony was unexpectedly closed or timed out. It will be re-established automatically if possible." I am not certain that it ever gets established.
sometimes strace helps in such cases
I have no idea what the results are supposed to look like, so I have no idea whether it's showing anything anomalous. Perhaps you would be able to read it, but I can make no sense of it.
the issue is this: the only linux mail client officially supported by protonmail bridge is thunderbird, which i'd use if it supported maildir, but it doesn't and i see no reason to think it ever will. configuring protonmail bridge is actually fairly straightforward -- both incoming and outgoing use 127.0.0.1. imap is port 1143; smtp is 1025. there is an elaborate password, which i get from protonmail bridge itself.
don't know - you should be able to check those even with telnet
Not sure how I'd do that, but a check of the ports tells me that the bridge is listening:
Desktop-Bridge 4392 dep 11u IPv4 34290 0t0 TCP 127.0.0.1:1143 (LISTEN) Desktop-Bridge 4392 dep 12u IPv4 33466 0t0 TCP 127.0.0.1:1025 (LISTEN)
Which I imagine is expected behavior. Nor are there failure to login errors from kmail.
telnet 127.0.0.1 1143 telnet 127.0.0.1 1025
no one argues against. I just asked because I recall you were writing about it, so it looks like kmail is not able to authenticate against your local protonmail instance.
Right. I can view mail through the webmail version of Protonmail -- that's how I'm writing this -- but after months of being able, with reasonable success, to use ProtonMail bridge I now can't, and I can't figure out any diagnostics for determining what got broken.
does the bridge have some debugging option?
what happens if you check in the settings of the account for example security or something - could be ssl certificate expired or who knows what.
If there were a certificate problem, wouldn't kmail throw an error? There are no security settings as such with Protonmail Bridge, and the settings in kmail appear to be correct.
yes indeed - it looks like that while it is trying to do something the connection breaks and you get the error
What I need to find out is if kmail is actually communicating with Protonmail Bridge. If it is, then I need to find out if Protonmail Bridge is communicating with the server in Switzerland. And I have no idea how to do either of those things.
Meet your best friend Wireshark ;-)
you can try also tdedebugdialog 5006 kmail and perhaps also tdeio and generic, but I am not sure if what you are using has debug, or you can install it - I think someone mentioned it is not compiled
regards
I just nuked my KMail configuration and rebuilt it from scratch. No idea how it got corrupted, but it apparently did.
Thanks to deloptes for his assistance, which didn't provide a direct answer but got me thinking in different directions.
-
deloptes -
dep