On Sun, Jan 08, 2017 at 09:59:29AM +0100, Adam Wolk wrote: > On Sun, Jan 08, 2017 at 12:40:18AM +0000, Stuart Henderson wrote: > > On 2017/01/07 18:26, Adam Wolk wrote: > > > On Sun, Jan 01, 2017 at 09:45:00PM +0100, Adam Wolk wrote: > > > > On Sun, Jan 01, 2017 at 09:20:50PM +0100, Adam Wolk wrote: > > > > > On Sun, Jan 01, 2017 at 03:58:10PM +0100, Adam Wolk wrote: > > > > > > Hi ports@ > > > > > > > > > > > > Attaching a bump to the latest otter browser weekly > > > > > > > > > > > > Feedback? OK's? > > > > > > > > > > Just got noticed from upstream tag a new beta will be > > > > > released shortly. Will follow up with a diff after > > > > > upstream tarballs show up. > > > > > > > > > > Regards, > > > > > Adam > > > > > > > > > > > > > Attaching the diff for the new 0.9.12 beta full upstream > > > > changelog since 0.9.11 will show up on http://otter-browser.org > > > > in a day or two. > > > > > > > > Feedback? OK's? > > > > > > Ping. > > > > Runtime seems fine, but I see a segfault at shutdown (which I don't > > see with the current amd64 snapshot packages) - any ideas? > >
Looks like it's an upstream Qt issue: https://github.com/OtterBrowser/otter-browser/issues/889 https://bugreports.qt.io/browse/QTBUG-50829 > > $ otter-browser > > No language dictionaries for the language: "C" > > Segmentation fault (core dumped) > > I was able to reproduce the crash when closing the browser using the windows > manager (ie. super - shift - q in i3) the crash doesn't seem to happen on > option > exit (Menu -> exit). > > I'll bring the issue up with upstream. > > Regards, > Adam >
