Do you want another log for that? Because (as I already mentioned above), this also reproduces when using a newly-created user, so that means no unsupported extensions.
Arkisto, kesäkuu 2021
Yeah, we now mos def need a video of the professor tasting Salmiakki Koskenkorva… perhaps joined by Rupert Baker having some fine tar liqueur (see the latest Objectivity video for reference).
The current accepted translation has a typo, making the already confusing option even more so: the word ”on” shouldn’t be there. The suggestion from Jani Järvi fixes this correctly.
Complex might be more appropriate (as with the previous), but requires a curator I think.
I can reproduce the crash at will with the steps I listed above, so I don’t have to wait for it to happen. It also doesn’t forcibly log me out, so I can enter those commands by just having a terminal window present when I trigger the issue. But I logged out here (after triggering) anyway since you instructed me to log in, in case it matters.
Also, there’s lots of noise in these from Boinc, thanks to #1876313.
@FlexW I’ve now rebased and pushed the changes, hope this works for you. I don’t see a way for me to merge this myself here, ”Only those with write access to this repository can merge pull requests.”
1. There’s nothing in /var/crash
2. There are no reports on the page for this computer.
3. Done, still nothing in /var/crash.
I don’t know if this means it’s not a true crash, although visually all the indications are there.
I also verified that this reproduces when using a newly-created user (with the only change from defaults for it being switching to Wayland), and also on another computer (also running 20.04). I am limited to using the one mouse that I have, so that all testing so far has been with the same mouse.