Otter browser is experiencing crashes on startup on my amd64 -current laptop. The backtrace suggest libproxy and upstream otter suggested that this is a known issue at least on Linux systems which have libproxy-kde installed as they tend to pull in both qt versions (4 & 5)
Upstream provided a backlog chat with the qt upstream: http://wklej.org/id/2190844/ which suggests that libproxy is used by qt since 5.5 and they suggest building qt without it (lol). I'm not sure which change exactly started killing otter on startup. I did have a working browser 100% around the time it was bumped to the new beta (2 months, 3 weeks ago). The biggest suspects so far are: - bump to qt 5.5.1 3 weeks 3 days ago by zhuk@ - enabling kde support by aja@ 2 months 1 week ago (not likely as it's flavour only?) Here is the backtrace I get from otter: https://gist.github.com/mulander/ef25ad07e15cbe8a00b8f9738abb8e7f Workaround from upstream proving that otter starts up and works correctly with disabled system proxy: cat ~/.config/otter/otter.conf [Network] ProxyMode=noproxy Roughly I'm interested if anyone else can confirm that they get otter crashing on startup by default. Did anyone notice libproxy crashesh in other qt5 apps? Potentially also discussing if we should build qt without the -no-libproxy flag? Regards, Adam
