[Bug 1904230] Re: System freeze after logging onto desktop session
Thanks. This looks most like the problem you describe. Unfortunately being an issue in LXDM or LXDE means it is no longer supported in 16.04 (since April 2019). Nov 18 19:58:57 monolith systemd[1]: Starting LXDE Display Manager... Nov 18 19:58:57 monolith systemd[1]: Started LXDE Display Manager. Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Main process exited, code=exited, status=1/FAILURE Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Unit entered failed state. Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Failed with result 'exit-code'. Nov 18 19:59:03 monolith systemd[1]: lxdm.service: Service hold-off time over, scheduling restart. Nov 18 19:59:03 monolith systemd[1]: Stopped LXDE Display Manager. Nov 18 19:59:03 monolith systemd[1]: Starting LXDE Display Manager... Nov 18 19:59:03 monolith systemd[1]: Started LXDE Display Manager. Nov 18 19:59:08 monolith systemd[1]: lxdm.service: Main process exited, code=exited, status=1/FAILURE Nov 18 19:59:08 monolith systemd[1]: lxdm.service: Unit entered failed state. Nov 18 19:59:08 monolith systemd[1]: lxdm.service: Failed with result 'exit-code'. Nov 18 19:59:08 monolith systemd[1]: lxdm.service: Service hold-off time over, scheduling restart. Nov 18 19:59:08 monolith systemd[1]: Stopped LXDE Display Manager. Nov 18 19:59:08 monolith systemd[1]: Starting LXDE Display Manager... Nov 18 19:59:08 monolith systemd[1]: Started LXDE Display Manager. Nov 18 19:59:13 monolith systemd[1]: lxdm.service: Main process exited, code=exited, status=1/FAILURE Nov 18 19:59:13 monolith systemd[1]: lxdm.service: Unit entered failed state. Nov 18 19:59:13 monolith systemd[1]: lxdm.service: Failed with result 'exit-code'. Nov 18 19:59:14 monolith systemd[1]: lxdm.service: Service hold-off time over, scheduling restart. Nov 18 19:59:14 monolith systemd[1]: Stopped LXDE Display Manager. Nov 18 19:59:14 monolith systemd[1]: Starting LXDE Display Manager... Nov 18 19:59:14 monolith systemd[1]: Started LXDE Display Manager. Nov 18 19:59:19 monolith systemd[1]: lxdm.service: Main process exited, code=exited, status=1/FAILURE Nov 18 19:59:19 monolith systemd[1]: lxdm.service: Unit entered failed state. Nov 18 19:59:19 monolith systemd[1]: lxdm.service: Failed with result 'exit-code'. ** Changed in: ubuntu Status: Incomplete => Won't Fix ** Package changed: ubuntu => lxdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904230] Re: System freeze after logging onto desktop session
'journalctl -b -1' comes back with: Specifying boot ID has no effect, no persistent journal was found I'm assuming though you're after the boot log for the previous session (that froze) so I've manually extracted this from /var/log/syslog in the attached archive (prevboot.txt). Unfortunately nothing new was added to /var/crash as a result of the freeze. Something additional to mention which may be related (given it's display related), I had to reboot the machine a couple of times to get this as it seemingly had issues starting the display manager. Visually the display kept flicking between the boot log and another one with some further logging info. The graphical login screen was never displayed. Syslog was showing messages as follows: Nov 18 19:58:57 monolith systemd[1]: Starting LXDE Display Manager... Nov 18 19:58:57 monolith systemd[1]: Started LXDE Display Manager. Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Main process exited, code=exited, status=1/FAILURE Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Unit entered failed state. Nov 18 19:59:02 monolith systemd[1]: lxdm.service: Failed with result 'exit-code'. Nov 18 19:59:03 monolith systemd[1]: lxdm.service: Service hold-off time over, scheduling restart. Nov 18 19:59:03 monolith systemd[1]: Stopped LXDE Display Manager. Only fix was to reboot it. I've attached the boot log for this one as 'prevboot1.txt'. This problem happened on two different boots. ** Attachment added: "boot logs" https://bugs.launchpad.net/ubuntu/+bug/1904230/+attachment/5435802/+files/logs.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904230] Re: System freeze after logging onto desktop session
The 'bash' crash is hopefully unrelated to this bug so I am ignoring that for now. But it might be related... Please try: 1. Reboot, log in and reproduce the freeze again. 2. Reboot again, don't log in but switch to a VT like Ctrl+Alt+F4 and log in to the text console there. 3. Run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904230] Re: System freeze after logging onto desktop session
I have managed to upload the crash report via another machine, the ID is 1904626. For some reason it appears to be associated with bash which makes me wonder if it is related - the timestamp is roughly 6 minutes after restarting the machine from the freeze which puts it in the right time frame but could be coincidental. I will endeavor to repeat the crash and see if a new one is reported. I've noted your comments regarding support and understand. The fact it crops up with two different desktops though - LXDM and Openbox could suggest though it's possibly part of 'X' rather than one of these. Unfortunately as you know, it's not possible to move from 2016 to 2020.04 in one move without going via 2018 first, I plan to do that over the next few months but there is a fair amount of work involved in ensuring everything is working after an upgrade so it's not something I have time for right now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904230] Re: System freeze after logging onto desktop session
Technically, support for desktops other than Unity on 16.04 only had a 3 year lifespan. That means it reached end-of-life in April 2019. So I'm not going to invest too much time digging further here. Could you possibly try installing Ubuntu 20.04? https://ubuntu.com/download/desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904230] Re: System freeze after logging onto desktop session
There is one crash report in the /var/crash folder which corresponds to the last time the system restarted due to this issue (other instances are >7 days so will have been removed). Running ubuntu-bug as requested generated a lot of dots but did not provide a bug ID: jon@monolith:/var/crash$ ubuntu-bug _bin_bash.500.crash *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (583.0 KB) E: Examine locally V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/E/V/K/I/C): S *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. [..] . jon@monolith:/var/crash$ There does not appear to be anything captured recently on https://errors.ubuntu.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904230] Re: System freeze after logging onto desktop session
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. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904230] Re: System freeze after logging onto desktop session
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1904230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
