Crash will be caused by poilcy routing and/or a second routing table.

[Martin Nicholas]

This bug:
https://bugs.kde.org/show_bug.cgi?id=342562
is being laid at your door by the KDE developers. Why they don't report it to you themselves is pure lazyness on their part.

[Alexander Sack (asac)]

Hi,

any info how to set the policy routing and second routing table to reproduce?

[Alexander Sack (asac)]

would be great if you could ask the kde bug reporter how to setup the repro env for this... thanks!

[Alexander Sack (asac)]

also ntrack-017 might fix this. they can check out the build in my ppa if they use ubuntu if they are brave and know how to go back to the official archive version after...

the ppa is here: https://launchpad.net/~asac/+archive/ubuntu/ntrack

[Martin Nicholas (throw-launchpad)]

This is at the very limit of my knowledge, but here's the route and policy that cause the segfault:

$ ip route list table vpn
0.0.0.0/1 via 188.X.65.129 dev tap0 src 188.X.65.130
unreachable default proto static
128.0.0.0/1 via 188.X.65.129 dev tap0 src 188.X.65.130
192.168.0.0/24 dev eth0 proto static scope link
192.168.88.0/24 dev virbr1 proto static scope link src 192.168.88.1
$ ip rule list
0: from all lookup local
3000: from 192.168.88.0/24 lookup vpn
32766: from all lookup main
32767: from all lookup default

This is to route packets from 192.168.88.0/24 via a VPN (tap0) iff it is up, so the default is "unreachable" in the VPN table.
Happens every KDE startup if the routes are in place, otherwise not.

[Martin Nicholas (throw-launchpad)]

Just added the ppa: and upgraded - no segfault now!

Ta.

[Alexander Sack (asac)]

this got fixed in 017