On Fri, Oct 22, 2021 at 12:39 PM Leander Hutton via test
<test(a)lists.fedoraproject.org> wrote:
Hello, I recently upgraded to FL35 and noticed that Darktable under a Wayland session
causes a hard lock of the whole session. Both the package that ships with the distro and
the release version compiled from source. I did a fresh install from the FL35 beta ISO on
this machine to test but before on FL34 the application worked fine.
Upon opening the program it will lock up and then the whole compositor and I have to
force a hard reset. It is fine on an X11 session. This is a Dell XPS 9310 with Intel
integrated Xe graphics so nothing terribly exotic in terms of hardware.
Unfortunately as the whole machine becomes hosed obtaining logs is proving difficult. But
I can attempt again and see if I can capture some output from Darktable if that would be
help.
Following the hard reset, there should still be logs available if you
have a persistent journal (the default). You can grab the entire
previous boot with:
journalctl -b -1 > journal.log
And attach that log file to a bug report.
It might also be useful to add drm.debug=0x06 as a kernel parameter, e.g.
grubby --args=drm.debug=0x06 --update-kernel=ALL
Reboot. Reproduce the problem. Hard reset (or possibly remote ssh will
still be functional). And then grab the log. To remove that boot
param:
grubby --remove-args=drm.debug=0x06 --update-kernel=ALL
--
Chris Murphy