could someone having the issue trigger the bug then do
$ journalctl -b 0 > journal
and add the journal file to the report?
(or do 'journalctl -f', trigger the bug and see if anything is printed in the log)
could someone having the issue trigger the bug then do
$ journalctl -b 0 > journal
and add the journal file to the report?
(or do 'journalctl -f', trigger the bug and see if anything is printed in the log)