https://bugs.kde.org/show_bug.cgi?id=453121
--- Comment #19 from m.eik michalke <bugs.kde....@ad.gelduntergang.biz> --- (In reply to m.eik michalke from comment #18) > after that kontact was *instantly* able to fetch contacts and calendars. so > all i'm missing is a way to tell kontact/akonadi to try IPv4 first. i've tried configuring the port forwarding for IPv6, but am still struggling with that (the router has an IPv6 address, but the server i'm trying to reach uses a local IPv4 address and is therefore only available via NAT and the router's IPv4 address). actually, i really think this should be considered a bug. there is a working network configuration via IPv4 that all other clients i tried are able to discover and use without any warnings or errors, only akonadi is now unable to do the same, alltough older versions are also perfectly fine with this setup. i'm ok with preferring IPv6 by default, but if that fails, kontact shouldn't simply give up but try IPv4 as well. i configured /etc/gai.conf so that the system prefers IPv4 over IPv6 globally, but kontact seems to ignore this. if i can't find any solution or at least a usable workaround for this problem, i'm stuck with kubuntu 20.04 on multiple machines, as i can't afford to break contacts and calendars on those, too. -- You are receiving this mail because: You are watching all bug changes.
