** No longer affects: systemd (Ubuntu)
** No longer affects: ubuntu-meta (Ubuntu)
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://b
** Changed in: gdm3 (Ubuntu)
Status: New => Fix Committed
--
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/1960226
Title:
Ubuntu Jammy Desktop fails to boot after ins
I was thinking gdm3 needed some investigation but this update was
published an hour ago:
https://launchpad.net/ubuntu/+source/gdm3/41.3-1ubuntu2
Fingers crossed.
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
2022-02-09 Fails
Ran 2 tests -
http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/244128/testcases/1300/results
--
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/1960226
Seems the problem is not ubiquity. Downgrading to 22.04.4 before
installing made no improvement.
** No longer affects: ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpa
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubunt
Given the bug doesn't occur for upgrades, maybe this change is relevant:
https://launchpad.net/ubuntu/+source/ubiquity/22.04.6
(the working image has 22.04.4)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu
I don't think this is a systemd bug. Here's the diff between working and
not working.
** Attachment added: "diff-0203-0205.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1960226/+attachment/5559919/+files/diff-0203-0205.txt
--
You received this bug notification because you are a
Although this is one of the changes:
https://launchpad.net/ubuntu/+source/ubuntu-meta/1.475
--
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/1960226
Title:
Ubuntu Jammy Des
2022-02-02 WORKS
2022-02-03 ?
2022-02-04 ?
2022-02-05 ?
2022-02-06 FAILS
2022-02-07 FAILS
2022-02-08 FAILS
** Changed in: systemd (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to s
I zsync'd the daily & completed 3 installs but did NOT experience this
issue
uEFI - sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
BIOS - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
the sony 'thingy' had two installs to it;
- one using normal uEFI, and
- the other using Secure-uEF
Retested Ubuntu Jammy daily ISO 2022-02-08 - again fails to boot to
desktop after install.
http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/244085/testcases/1300/results
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This also affects Ubuntu Jammy Canary desktop - tested daily ISO
2022-02-07
** Description changed:
Ubuntu Jammy Desktop fails to boot after install
Testing Ubuntu Jammy Desktop daily ISO - 2022-02-07
+
+ This also affects Ubuntu Jammy Canary desktop - tested daily ISO
+ 2022-02-07
A
@juliank
I will retest this again after release next daily ISO on other machines
as well.
--
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/1960226
Title:
Ubuntu Jammy Deskt
You have already left grub at this point and the kernel also started.
Reassigning to systemd in the meantime to debug this further as a
userspace boot issue. This might need further reassing.
You'll have to boot this verbosely, it's no use with a splash screen
enabled.
** Package changed: grub2
15 matches
Mail list logo
