With 1.1.1b-1ubuntu2.3 it's a bit different. The system doesn't seem to
freeze anymore, but network traffic stops working. Happend about 1-2
hours after a fresh reboot (after applying updates). It still answered
to PINGs, but no other network traffic. Neither SSH, nor HTTP/HTTPS or
XMPP. After down
Public bug reported:
Yesterday, I've updated openssl on my Raspberry Pi 3B+ running disco
arm64 from 1.1.1b-1ubuntu2.1 to 1.1.1b-1ubuntu2.2 . That was at 10:41
CEST. About 12:36 the system froze. I was able to reset the system at
around 17:17. It froze again at around 17:55. Reset it again 19:09,
I have this, too, on a Raspberry Pi 3 with arm64 Ubuntu. However, I've
also upgraded my Raspberry Pi 2 with armhf and there, NetworkManager
still autoconnects just fine after boot. The configuration looks
identical on both machines.
--
You received this bug notification because you are a member o
*** This bug is a duplicate of bug 1726930 ***
https://bugs.launchpad.net/bugs/1726930
** This bug has been marked a duplicate of bug 1726930
System fails to start (boot) on battery due to read-only root file-system
--
You received this bug notification because you are a member of Ubuntu
This bug reappeared (with cifs/smb mounts in fstab) after upgrade to
17.10 "artful" for me. The fix in #5 worked just fine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/157
Confirmed on a hp Spectre x360 13-4104ng.
On battery power, the system DOESN'T boot up.
With the charger connected, the system boots up just fine.
See https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458 for my
apport logs.
--
You received this bug notification because you are a me
Yes, this seems to be a duplicate of your bug.
On battery power, the system DOESN'T boot up.
With the charger connected, the system boots up just fine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https
The change in the fstab seems to have worked only once. Today, it
doesn't boot again (with the changed fstab). I've tried switching from
UEFI to Legacy mode without luck, too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sy
I changed my fstab from
UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 errors=remount-ro 0 1
to
UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 rw,errors=remount-ro 0
1
and it now boots fine again. I don't know why that is necessary now and
why the update didn't notify me or made the change
Public bug reported:
After not touching my notebook since 30th September (where I did the
dist-upgrade to artful and installed all available updates), I did all
available updates today (20th October) and the system didn't boot after
that.
The last message I see is "Reached target Bluetooth". Befo
10 matches
Mail list logo
