The future of Wayland, and Sway's role in it

Re:The future of Wayland, and Sway's role in it by phkahler on Friday October 20, 2017 @10:02AM (#15515815)

I used the automatic reporting tool. Reproduction is simple. Run firefox on NV44 (Ben used to have one. I have a spare with less RAM if anyone cares about nouveau on that any more). Bring up cookie clicker in the browser and let it run for a bit. It will crash.

More recently gnome crashes right after login, but then doesn't when I login a second time. I don't think the automatic reporting is working for this one.

I figure at this point I'll let it slide until I upgrade and then get more vigilant about reporting problems. Unfortunately the auto-upgrade didn't work for me this time, so I'll reinstall 26 or 27 from scratch.

[ Parent | on HN ]

Re:The future of Wayland, and Sway's role in it by Sir_Cmpwn on Friday October 20, 2017 @10:11AM (#15515895)

Automatic reporting tool? We don't have one of those. Your report probably went to /dev/null.

Hacker News isn't the right place for your bug report, though, please file a GitHub issue here: https://github.com/swaywm/sway/issues/new

[ Parent | on HN ]

Re:The future of Wayland, and Sway's role in it by ibotty on Saturday October 21, 2017 @10:58AM (#15522029)

I am pretty sure it's abrt, this reports to downstream. I don't know whether they get passed upstream, but sometimes they do.

[ Parent | on HN ]