Daniel,
Tnx for the prompt reply. Here are my findings: re 1.: /var/crash is empty. There are no files. Just to let you know://Immediately after I logged in, I switched to one screen mode. The system did not crash. I assume, that older crash files should be in /var/crash from earlier crashes. Again: Nio files. re2.: Here is the required link. I replaced the string 'ID' with the content of whoopsie-id: https://errors.ubuntu.com/user/5fd549dc7d50ea7eb81a704d3d2508e0449eaf07c1bdac5a59b01203286966824e3c72d60dc218f5ed382637afa126117fc43d759958cb058b07afa624e85a14 Strange enough, it leads me to a Nautilus error with the date Oct. 15. I think I still ran Ubuntu 18.04 in October - to my best knowledge. And I cannot imagine, that Nautilus has got something to do with my system freeze. re 3.: I did not manage to find out what the workaround from bug 994921 could be. Nevertheless I send this email now and will revert to dual screen mode again and see what's happening. As I said: If the bug with the system freeze occurs, the system becomes unusable. There is even no reaction to key strokes. I only can force my system down be pressing the on/off button. If this is of any help: I still have an 18.04 partition running on the system, which runs flawlessly. Could this be of any help for error detection? Tnx for the time being, I will let you know of further outcomes. Regards, Thomas On 04.12.20 03:01, Daniel van Vugt wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It sounds like some part of the system has crashed. To > help us find the cause of the crash please follow these steps: > > 1. Look in /var/crash for crash files and if found run: > ubuntu-bug YOURFILE.crash > Then tell us the ID of the newly-created bug. > > 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where > ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. > Do you find any links to recent problems on that page? If so then please > send the links to us. > > 3. If step 2 also failed then apply the workaround from bug 994921, > reboot, reproduce the crash, and retry step 1. > > Please take care to avoid attaching .crash files to bugs as we are > unable to process them as file attachments. It would also be a security > risk for yourself. > > ** Tags added: radeon > > ** Summary changed: > > - Xorg freeze > + [radeon] Xorg freeze > > ** Package changed: xorg (Ubuntu) => ubuntu > > ** Changed in: ubuntu > Status: New => Incomplete > > ** Package changed: ubuntu => xorg-server (Ubuntu) > > ** Package changed: xorg-server (Ubuntu) => ubuntu > > ** Summary changed: > > - [radeon] Xorg freeze > + [radeon] Display freeze > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906686 Title: [radeon] Display freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1906686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
