Happy New Year all, here's my first bug of the year.
Using Kontact on Mint 18.3 (KDE) it's been fine for ages then yesterday, this:
Kontact opens in Kmail which works fine. Choosing other modulkes from the sidebar I find Contacts (Kaddressbook) or Calendar (Korganizer) cause Kontact to crash. Other modules do not.
Running from a terminal doesn't provide much info except an invalid socket warning.
KCrash: crashing... crashRecursionCounter = 2
Following a crash the app has clearly not exited properly because socket errors keep on coming until I close the terminal.
*phil@phil-desktop* *~ $* QSocketNotifier: Invalid socket 53 and type 'Read', disabling...
Running Korganizer direct from a terminal is OK. Running Kaddressbook isn't. It opens for a fraction of a second, just long enough to see the window, then crashes. Similar error messages to the above.
As I have little idea what a socket is, I'm stumped!
The KDE reporting tool reports that the log isn't detailed enough to bother with and I can't find any useful advice online. Help?!
-- Phil Thane
www.pthane.co.uk phil@pthane.co.uk 01767 449759 07582 750607 Twitter @pthane
I'm replying to my own thread now! My original mail about Kontact was held for moderation by the ALUG mail system due something suspect about the headers. I sent the same message to my previous two LUGS (North Wales and Wrexham) and both let it straight through. I assume whoever runs the ALUG list has tightened some security setting that the others haven't. I have had trouble getting mail through to a few other recipients (all govt depts/agencies as it happens) so I'd like to find out what's going on. If you are the ALUG email admin would you mind looking at the headers of this message and telling me if anything looks suspicious? If you're not the admin, but know anything about email feel free to have a nosey! As for Kontact, I discovered that if I rename ~/.config forcing all KDE apps to reset then it doesn't crash. If I then revert to the original config and start renaming individual likely looking config files one at a time I go mad - there are a lot. I did manage to stop Calendar crashing it for a while and thought I was making progress, but the issue returned. So I gave up and installed Evoluton. Daft really because Kontact and the default KDE interface was the main reason I switched from Win95 to SuSE 8.0 long long ago. Maybe next time I do a fresh install I'll give the new Ubuntu/Gnome a go. -- Phil On Sun, 2018-01-07 at 16:38 +0000, Phil Thane wrote:
Happy New Year all, here's my first bug of the year. Using Kontact on Mint 18.3 (KDE) it's been fine for ages then yesterday, this: Kontact opens in Kmail which works fine. Choosing other modulkes from the sidebar I find Contacts (Kaddressbook) or Calendar (Korganizer) cause Kontact to crash. Other modules do not. Running from a terminal doesn't provide much info except an invalid socket warning. KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kontact path = /usr/bin pid = 5702 KCrash: Arguments: /usr/bin/kontact KCrash: Attempting to start /usr/lib/i386-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 51 and type 'Read', disabling... QSocketNotifier: Invalid socket 9 and type 'Read', disabling... QSocketNotifier: Invalid socket 11 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 27 and type 'Read', disabling...
[1]+ Stopped kontact
Following a crash the app has clearly not exited properly because socket errors keep on coming until I close the terminal. phil@phil-desktop ~ $ QSocketNotifier: Invalid socket 53 and type 'Read', disabling... QSocketNotifier: Invalid socket 44 and type 'Read', disabling... QSocketNotifier: Invalid socket 49 and type 'Read', disabling... QSocketNotifier: Invalid socket 41 and type 'Read', disabling... QSocketNotifier: Invalid socket 46 and type 'Read', disabling...
Running Korganizer direct from a terminal is OK. Running Kaddressbook isn't. It opens for a fraction of a second, just long enough to see the window, then crashes. Similar error messages to the above. As I have little idea what a socket is, I'm stumped! The KDE reporting tool reports that the log isn't detailed enough to bother with and I can't find any useful advice online. Help?! -- Phil Thane www.pthane.co.uk phil@pthane.co.uk 01767 449759 07582 750607 Twitter @pthane _______________________________________________ main@lists.alug.org.uk http://www.alug.org.uk/ https://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
That's why mine got thrown off, Phil (aiui.) I hadn't made sure the composing preferences were set to plain text along with the viewing option. (I say this fully expecting your problem to be more complex.)
Bev.
On 12/01/18 14:54, Phil Thane wrote:
I'm replying to my own thread now! My original mail about Kontact was held for moderation by the ALUG mail system due something suspect about the headers. I sent the same message to my previous two LUGS (North Wales and Wrexham) and both let it straight through. I assume whoever runs the ALUG list has tightened some security setting that the others haven't. I have had trouble getting mail through to a few other recipients (all govt depts/agencies as it happens) so I'd like to find out what's going on. If you are the ALUG email admin would you mind looking at the headers of this message and telling me if anything looks suspicious? If you're not the admin, but know anything about email feel free to have a nosey! As for Kontact, I discovered that if I rename ~/.config forcing all KDE apps to reset then it doesn't crash. If I then revert to the original config and start renaming individual likely looking config files one at a time I go mad - there are a lot. I did manage to stop Calendar crashing it for a while and thought I was making progress, but the issue returned. So I gave up and installed Evoluton. Daft really because Kontact and the default KDE interface was the main reason I switched from Win95 to SuSE 8.0 long long ago. Maybe next time I do a fresh install I'll give the new Ubuntu/Gnome a go. -- Phil On Sun, 2018-01-07 at 16:38 +0000, Phil Thane wrote:
Happy New Year all, here's my first bug of the year.
Using Kontact on Mint 18.3 (KDE) it's been fine for ages then yesterday, this:
Kontact opens in Kmail which works fine. Choosing other modulkes from the sidebar I find Contacts (Kaddressbook) or Calendar (Korganizer) cause Kontact to crash. Other modules do not.
Running from a terminal doesn't provide much info except an invalid socket warning.
KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kontact path = /usr/bin pid = 5702 KCrash: Arguments: /usr/bin/kontact KCrash: Attempting to start /usr/lib/i386-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 51 and type 'Read', disabling... QSocketNotifier: Invalid socket 9 and type 'Read', disabling... QSocketNotifier: Invalid socket 11 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 27 and type 'Read', disabling...
[1]+ Stopped kontact
Following a crash the app has clearly not exited properly because socket errors keep on coming until I close the terminal.
phil@phil-desktop ~ $ QSocketNotifier: Invalid socket 53 and type 'Read', disabling... QSocketNotifier: Invalid socket 44 and type 'Read', disabling... QSocketNotifier: Invalid socket 49 and type 'Read', disabling... QSocketNotifier: Invalid socket 41 and type 'Read', disabling... QSocketNotifier: Invalid socket 46 and type 'Read', disabling...
Running Korganizer direct from a terminal is OK. Running Kaddressbook isn't. It opens for a fraction of a second, just long enough to see the window, then crashes. Similar error messages to the above.
As I have little idea what a socket is, I'm stumped!
The KDE reporting tool reports that the log isn't detailed enough to bother with and I can't find any useful advice online. Help?!
-- Phil Thane
www.pthane.co.uk phil@pthane.co.uk 01767 449759 07582 750607 Twitter @pthane _______________________________________________ main@lists.alug.org.uk http://www.alug.org.uk/ https://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
main@lists.alug.org.uk http://www.alug.org.uk/ https://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
On Fri, Jan 12, 2018 at 02:54:38PM +0000, Phil Thane wrote:
I'm replying to my own thread now! My original mail about Kontact was held for moderation by the ALUG mail system due something suspect about the headers. I sent the same message to my previous two LUGS (North Wales and Wrexham) and both let it straight through. I assume whoever runs the ALUG list has tightened some security setting that the others haven't. I have had trouble getting mail through to a few other recipients (all govt depts/agencies as it happens) so I'd like to find out what's going on.
If you are the ALUG email admin would you mind looking at the headers of this message and telling me if anything looks suspicious? If you're not the admin, but know anything about email feel free to have a nosey!
You send HTML email which the list is configured by default to hold. SpamAssassin also seems to think there's a problem with your DKIM headers - it reports "T_DKIM_INVALID", which might explain the issues sending to other recipients though I can't be sure it's not some interaction involving the list. I don't see it with other list mails however.
J.
On Fri, 2018-01-19 at 09:40 +0000, Jonathan McDowell wrote:
On Fri, Jan 12, 2018 at 02:54:38PM +0000, Phil Thane wrote:
I'm replying to my own thread now! My original mail about Kontact was held for moderation by the ALUG mail system due something suspect about the headers. I sent the same message to my previous two LUGS (North Wales and Wrexham) and both let it straight through. I assume whoever runs the ALUG list has tightened some security setting that the others haven't. I have had trouble getting mail through to a few other recipients (all govt depts/agencies as it happens) so I'd like to find out what's going on.
If you are the ALUG email admin would you mind looking at the headers of this message and telling me if anything looks suspicious? If you're not the admin, but know anything about email feel free to have a nosey!
You send HTML email which the list is configured by default to hold. SpamAssassin also seems to think there's a problem with your DKIM headers - it reports "T_DKIM_INVALID", which might explain the issues sending to other recipients though I can't be sure it's not some interaction involving the list. I don't see it with other list mails however.
J.
I looked up DKIM and followed some online suggestions but I'm none the wiser. For example:
Woodpecker DKIM for Dummies (https://blog.woodpecker.co/cold-email/spf-dkim/)suggested using G tools to diagnose the issue(s).
Google reports:
SPF must allow Google servers to send mail on behalf of domain. All name servers should resolve to IP addresses. DKIM is not set up. DMARC is not set up. No Google mail exchangers found. Relayhost configuration?
Now as I don't use Gmail I assume I can ignore those relating to that, but the DKIM thing seems to be what Jonathan referred to.
Checking my mail server via Cpanel (only access I have) I see that DKIM and SPF are both enabled and active and have passed DNS checks.
ANy more suggestions anyone?
BTW, sent this as plain txt, let's see if it gets through...
-
Bev Nicolson -
Jonathan McDowell -
Phil Thane