With this fix my upgrade Xubuntu 20.04.4 => 22.04 completed.
There was a non-fatal hiccup for Firefox converting to snap.
Reviewing the new instance ...
:D
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https:
Closed as "user error" => "invalid"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1860683
Title:
initramfs hang after today's updates
Status in initramfs-tools p
It definitely is the initramfs. After successfully mounting the root
filesystem (sda10) the following messages are displayed:
-- /scripts/init-bottom/udev: line 25: nuke: not found
-- done.
-- init: line 303: run-init: not found
-- Target filesystem does not have requested /sbin/init.
-- init: lin
** Package changed: ubuntu => initramfs-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1860683
Title:
initramfs hang after today's updates
Status i
It looks like /run/systemd/generator/-.mount is the culprit.
However, whatever I try issuing "sudo systemctl mask -.mount" fails with a
"systemctl: invalid option -- '.'" error message.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
** Attachment added: "/run/systemd"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691158/+attachment/4878269/+files/run.systemd.1691158.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
ht
** Attachment added: "sosreport md5"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691158/+attachment/4878268/+files/sosreport-DBurggraaff.1691158-20170517154949.tar.xz.md5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
** Attachment added: "/run/systemd md5"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691158/+attachment/4878270/+files/run.systemd.1691158.tar.xz.md5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ub
** Attachment added: "sosreport"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691158/+attachment/4878267/+files/sosreport-DBurggraaff.1691158-20170517154949.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I should also mention that the symptom started recently. I am not sure
exactly when but it did not occur before the last 3 or so kernel
updates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.l
Now imagine what happens when sda5 is mounted "behind my back" on /boot and a
new kernel is installed by the Software Updater: the new kernel ends up on sda5
and the /vmlinuz and /initrd.img "system" symlinks point the new files.
On a reboot Grub does not mount sda5: the "system" symlinks point t
"/boot != EFI partition. You should not be placing kernels in teh UEFI
partition."
My root filesystem (sda10 in this case) contains the kernels, the sda5 EFI
partition does not.
My sda10 partition does not contain a /boot/efi directory, so I created one and
rebooted: sda5 is still mounted on /bo
*Correction*: As e.g. reboots after a kernel upgrade fail I explicitely
umount /dev/sda5 in rc.local
--
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/1691158
Title:
systemd
As e.g. kernel upgrades fail I explicitely umount /dev/sda5 in rc.local
--
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/1691158
Title:
systemd mounts efi partition, but /et
** Attachment added: "/var/log/messages"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691158/+attachment/4877602/+files/messages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.la
root@riposo:~/works# fdisk /dev/sda
Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sda: 223.6 GiB, 240057409536 bytes, 468862128 sectors
Units: sectors of 1 * 5
** Attachment added: "/etc/fstab"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691158/+attachment/4877601/+files/fstab
--
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.ne
Public bug reported:
Systemd mounts /dev/sda5 on /boot despite the fact that /etc/fstab says:
/dev/sda5 /boot ext2 noauto,relatime 0 0
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu17
ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
Uname: Linux 4.8.0
Public bug reported:
For some users lightdm displays the user's background for a second or two and
then shows a solid blue background. Login etc. is OK.
I have seen this behavior for over a year now (so things already started with
14.04) on several boxes.
ProblemType: Bug
DistroRelease: Ubuntu
Resolved with 16.04.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1584488
Title:
lightdm: error found when loading /root/.profile
Status in lightdm package in Ubuntu:
Public bug reported:
Lightdm on Ubuntu 16.04, also with Ubuntu-Mate 16.04 and Xubuntu 16.04
but *not* with Lubuntu 16.04
When logging in via Other > root a popup is shown reading:
-- Error found when loading /root/.profile
-- mesg: ttyname failed: Inappropriate ioctl for device
-- As result the s
21 matches
Mail list logo
