https://bugs.kde.org/show_bug.cgi?id=343034

Andre Heinecke <aheine...@intevation.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |UPSTREAM

--- Comment #13 from Andre Heinecke <aheine...@intevation.de> ---
Can you check your ntrack Version, we had a customer that encountered the same
problem in their KMail deployment and after some analysis we were pretty sure
that the ntrack library was to blame. As KDE services just forward the network
status from that library and ntrack reported it was offline when kmail wrongly
thought it was offline, too.

So we updated ntrack to 017 as they changed the way they discover the online
state a bit (  https://launchpad.net/ntrack/+announcement/13058 ). This solved
the problem for the customer who has not seen further disconnect / connect
problems since deploying libntrack-017

Please check if libntrack installed on your system is >= 017 If so reopen this
bug or comment please. I really think this is an upstream problem and you
should ask your distributors to ship ntrack 017 or built it from source or so.

Packages for Ubuntu trusty are published here:
http://apt.intevation.org/dists/trusty/kdepim-4.14/binary-amd64/ntrack/

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to