FS#28880 - [kdepim-kmail] stays in offline mode, unable to send emails

Attached to Project: Arch Linux
Opened by Jan Schumacher (wonko) - Monday, 12 March 2012, 20:14 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 12 March 2012, 20:45 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ronald van Haren (pressh)
Andrea Scarpino (BaSh)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
As reported under https://bugs.kde.org/show_bug.cgi?id=294441 and https://bbs.archlinux.org/viewtopic.php?id=135361, since v4.8 kmail switches to offline mode if the network connection is down, unstable or after resume from sleep and does not switch back to online mode when the connection is (re-)established, so emails can not be send.
To be exact, all akonadi remote sources are affected. This problem seems not to be permission related. All the details are listed on bugs.kde.org.

To send mail again kded4 has to be killed and restarted or set to the right state manually ('qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.setNetworkStatus "ntrack" 0').

This seems to be caused by the interplay between networkstatus (from package kdebase-runtime) and NTrack.
The kde network managment maintainer will have a look at this issue.

Building kdebase-runtime without NTrack seems to fix the issue.

As this problem is very annoying, maybe you might consider removing NTrack as a dependency for now. It is optional and gentoo (as reported by the kde network managment maintainer) seems to get along fine without it and open-suse removed it as a build dependency, too, because of problems, until it's stable again (http://lists.opensuse.org/opensuse-kde/2011-08/msg00192.html).

Additional info:
* package version(s) 4.8.0, 4.8.1

Steps to reproduce:
Running kde 4.8.0/4.8.1, resume from sleep or dis- and re-connect from network and try to send mail via kmail.
To fix/workaround: uninstall NTrack, build kdebase-runtime without NTrack.

I attach a modified PKGBUILD from abs (without NTrack, corrected source path) solving the issue, but only if NTrack is not installed at build time.
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Monday, 12 March 2012, 20:45 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#28850 
Comment by Jan Schumacher (wonko) - Monday, 12 March 2012, 20:19 GMT
PKGBUILD solving the issue
(application/x-gzip)    PKGBUILD.tar.gz (1 KiB)
Comment by Andrea Scarpino (BaSh) - Monday, 12 March 2012, 20:26 GMT
The package in [extra] works for me.

Did you try to open `akonadiconsole` to switch on the mail dispatcher agent?
Comment by Eric (wazyk) - Monday, 12 March 2012, 20:45 GMT
Not an issue of Mail Dispatcher Agent.

After boot, when network connection is established, the system is not notified (networkstatus kded daemon's job) that network is on and KDE thinks it is offline, until kded is restartd.

For me the problem occurs on a fresh install of kde 4.8 Arch x86_64.
I have another machine under Arch i686, updated from kde 4.7 (and previous) for which the issue is not present (Wifi through ipw2200, NetworkManger)
What is the common spec that make this happen (hardware, modules, daemons, acpi conf, etc.) ?

Mine:
Lenovo Thinkpad E520
Arch x86_64
Latest KDE SC 4.8
Broadcom brcmsmac module for Wifi, managed by NetworkManager

After boot, when running:
qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.Client.Status
I get value 1 which is not good. Value 4 is expected.


Loading...