@Rrizun If you are using bonds, this is the issue:
https://bugs.launchpad.net/bugs/2106671
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100963
Title:
cloud-init fails with MAAS since Feb 4 update
My pleasure @Rrizun In your deployments, do you happen to use
OpenVSwitch bridges with your deployments?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100963
Title:
cloud-init fails with MAAS since
For the time being until we figure out what is going on you can override
/ downgrade cloud-init during deployments using the following preseed
file:
#cloud-config
debconf_selections:
maas: |
{{for line in str(curtin_preseed).splitlines()}}
{{line}}
{{endfor}}
late_commands:
maas: [wget, '
@James I'm testing that as we speak - I'll report back shortly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100963
Title:
cloud-init fails with MAAS since Feb 4 update
To manage notifications abo
My Noble Results are in (Snippet from the build process):
cloudimg.image.qemu.cloudimg: Preparing to unpack
.../cloud-init_24.4.1-0ubuntu0~24.04.2_all.deb ...
cloudimg.image.qemu.cloudimg: Unpacking cloud-init (24.4.1-0ubuntu0~24.04.2)
over (24.4.1-0ubuntu0~24.04.1) ...
cloudimg.image.qemu.cloud
OK! Third time's a charm!
Built a new image (Note the snippet from build):
cloudimg.image.qemu.cloudimg: Preparing to unpack
.../cloud-init_24.4.1-0ubuntu0~20.04.2_all.deb ...
cloudimg.image.qemu.cloudimg: Unpacking cloud-init (24.4.1-0ubuntu0~20.04.2)
over (24.4.1-0ubuntu0~20.04.1) ...
cloudim
You are right! The .2 deb is missing:
[ ] cloud-init_24.4.1-0ubuntu0~20.04.1.debian.tar.xz2025-02-17
19:23103K
[TXT] cloud-init_24.4.1-0ubuntu0~20.04.1.dsc 2025-02-17 19:232.1K
[ ] cloud-init_24.4.1-0ubuntu0~20.04.1_all.deb 2025-02-17 19:25
556K
[
I spoke too soon about Focal. It seems like the patch does not contain a
full fix.
Even though the deployment is successful, you can not SSH to the machine
and the host name also does not correctly set.
I reverted the tag and attaching the cloud-init logs as well as the
journals.
Please let me k
Deployment Screenshot
** Attachment added: "Screenshot from 2025-03-15 20-26-37.png"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2100963/+attachment/5865063/+files/Screenshot%20from%202025-03-15%2020-26-37.png
** Tags removed: verification-needed verification-needed-focal
** Tag
Hello @Timo,
I went ahead and built a Custom MAAS image using Focal (packer-
maas/ubuntu). This build was modified to pull the new cloud-init package
from focal-proposed:
==> cloudimg.image.qemu.cloudimg: + apt-get install -y --allow-downgrades
cloud-init=24.4.1-0ubuntu0~20.04.1 grub-efi-amd64-b
Focal Tag has been updated to verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100963
Title:
cloud-init fails with MAAS since Feb 4 update
To manage notifications about this b
Hello @Timo! Thank you so much for the quick turnaround on this issue.
I also tested building a fresh Jammy image with the new package and it
deploys fine w/o any issues now.
Output snippet from the build log:
cloudimg.image.qemu.cloudimg: Get:1 http://archive.ubuntu.com/ubuntu
jammy-proposed/m
I hit this exact same issue while building and deploying Ubuntu images
using packer-maas.
The solution as suggested above was to use the older version of cloud-
init during the image build process:
apt-get install -y --allow-downgrades cloud-init=23.1.2-0ubuntu0~22.04.1
This is concerning, as I
Public bug reported:
Hello OpenStack Team!
We came across in interesting issue affecting the post deletion cleanup
of volume backed instances on Charmed OpenStack Jammy/Yoga.
After spending some time investigating, I am able to reproduce this on
my own cloud.
The general workflow is:
1. Create
Alan Baghumian has proposed merging ~alanbach/curtin:hacking-doc-update into
curtin:master.
Commit message:
Updated HACKING.rst to include the build/test
dependency script.
Requested reviews:
Server Team CI bot (server-team-bot): continuous-integration
curtin developers (curtin-dev)
For
Alan Baghumian has proposed merging ~alanbach/curtin:lp1979280 into
curtin:master.
Commit message:
Add support for RHEL 10 family.
LP: #1979280
Requested reviews:
curtin developers (curtin-dev)
Related bugs:
Bug #1979280 in curtin: "Deploying Alma linux 9 - unsupported RHEL ve
** Tags removed: verification-needed verification-needed-jammy
verification-needed-noble verification-needed-oracular
** Tags added: verification-done verification-done-jammy
verification-done-noble verification-done-oracular
--
You received this bug notification because you are a member of Ubu
Alan Baghumian has proposed merging ~alanbach/curtin:lp2090874 into
curtin:master.
Commit message:
Add support for arm64 bootloader artifact
detection support for rpm based distributions.
LP: #2090874
Requested reviews:
curtin developers (curtin-dev)
Related bugs:
Bug #2090874 in
** Attachment added: "Noble Verification Screenshot - SSH"
https://bugs.launchpad.net/ubuntu/+source/python-libmaas/+bug/2077382/+attachment/5843437/+files/lp2077382-noble-verification-cli.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Attachment added: "Jammy Verification Screenshot - SSH"
https://bugs.launchpad.net/ubuntu/+source/python-libmaas/+bug/2077382/+attachment/5843436/+files/lp2077382-jammy-verification-cli.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Attachment added: "Oracular Verification Screenshot - SSH"
https://bugs.launchpad.net/ubuntu/+source/python-libmaas/+bug/2077382/+attachment/5843438/+files/lp2077382-oracular-verification-cli.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Hi Mauricio, as discussed, also adding the verification screenshots
taken from SSH as described in the original test plan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077382
Title:
[SRU] support
** Attachment added: "Jammy Verification Screenshot - MAAS UI"
https://bugs.launchpad.net/ubuntu/+source/python-libmaas/+bug/2077382/+attachment/5843174/+files/lp2077382-jammy-verification-maas-ui.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Hello @Mauricio! Sure thing. I just did a manual verification following
these steps:
1) Used the script to deploy machines using python3-libmass in mod-new
2) Prevented the script from releasing them to validate and take a screen shot
from the MAAS UI
Adding the screenshots.
--
You received th
** Attachment added: "Oracular Verification Screenshot - MAAS UI"
https://bugs.launchpad.net/ubuntu/+source/python-libmaas/+bug/2077382/+attachment/5843176/+files/lp2077382-oracular-verification-maas-ui.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Attachment added: "Noble Verification Screenshot - MAAS UI"
https://bugs.launchpad.net/ubuntu/+source/python-libmaas/+bug/2077382/+attachment/5843175/+files/lp2077382-noble-verification-maas-ui.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Tags removed: verification-needed verification-needed-jammy
verification-needed-noble verification-needed-oracular
** Tags added: verification-done verification-done-jammy
verification-done-noble verification-done-oracular
--
You received this bug notification because you are a member of Ubu
And the last one!
Oraculat verification has been also completed successfully.
** Attachment added: "Oracular Verification Screenshot"
https://bugs.launchpad.net/ubuntu/noble/+source/python-libmaas/+bug/2077382/+attachment/5842633/+files/lp2077382-oracular-verification.png
--
You received th
Hello Again @Timo
Noble verification has been also completed successfully.
** Attachment added: "Noble verification Screenshot"
https://bugs.launchpad.net/ubuntu/noble/+source/python-libmaas/+bug/2077382/+attachment/5842632/+files/lp2077382-noble-verification.png
--
You received this bug no
Hello @Timo
I modified the verification python script attached above after enabling
jammy-proposed and completed the verification for Jammy.
def install_python_libmaas_modified():
print_colored("Installing Modified version of
python3-libmaas=0.6.8-0ubuntu0.22.04.2", "yellow")
subprocess.
Debdiff for Plucky
** Patch added: "Debdiff for Plucky"
https://bugs.launchpad.net/ubuntu/+source/python-libmaas/+bug/2077382/+attachment/5831503/+files/lp2077382-python3-libmaas-plucky.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Refreshed debdiff for Jammy
** Patch added: "Refreshed debdiff for Jammy"
https://bugs.launchpad.net/ubuntu/+source/python-libmaas/+bug/2077382/+attachment/5831500/+files/lp2077382-python3-libmaas-jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
^^ I removed the patch flag from debdiffs to satisfy this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077382
Title:
[SRU] support additional parametes on deploy()
To manage notifications about
Debdiff for Oracular
** Patch added: "Debdiff for Oracular"
https://bugs.launchpad.net/ubuntu/+source/python-libmaas/+bug/2077382/+attachment/5831502/+files/lp2077382-python3-libmaas-oracular.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Debdiff for Noble
** Patch added: "Debdiff for Noble"
https://bugs.launchpad.net/ubuntu/+source/python-libmaas/+bug/2077382/+attachment/5831501/+files/lp2077382-python3-libmaas-noble.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Just a quick update, our client completed the PPA testing process on
their end.
They were able to use the PPA packages to perform deployments using the
newly added parameters.
Best,
Alan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Please make sure to update the following variables before using:
maas_endpoint = "/MAAS/api/2.0/"
maas_apikey = ""
test_system_id = ""
** Attachment removed: "SRU Automated Test Script"
https://bugs.launchpad.net/ubuntu/+source/python-libmaas/+bug/2077382/+attachment/5821222/+files/maas-pytho
Attaching an automated deployment test script.
Please update the following variables before using:
maas_endpoint = "/MAAS/api/2.0/"
maas_apikey = ""
test_system_id = ""
** Attachment added: "SRU Automated Test Script"
https://bugs.launchpad.net/ubuntu/+source/python-libmaas/+bug/2077382/+att
** Description changed:
[ Impact ]
* This SRU is not addressing an existing problem but adds support for
two additional optional parameters being ephemeral_deploy and
enable_hw_sync on deploy(). For more details please see (1).
+
+
+ [ Test Plan ]
+
+ * Pre-Requisits: A MAAS controll
Hello @James I just tested the Focal Proposed packages on my Sapphire
Rapids Compute Node:
$ juju config nova-compute-focal cpu-mode
custom
$ juju config nova-compute-focal cpu-model
Cascadelake-Server-noTSX
$ juju config nova-compute-focal cpu-model-extra-flags
-mpx
Before Upgrade:
ubuntu@no
** Patch added: "Jammy Debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-libmaas/+bug/2077382/+attachment/5808702/+files/lp2077382-python3-libmaas-jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Description changed:
- This is a SRU bug report for this feature that has already been merged
- upstream (1).
+ [Impact]
- This implements support for ephemeral_deploy as well as enable_hw_sync
- on deploy().
+ * This SRU is not addressing an existing problem but adds support for
+ two addit
** Also affects: python-libmaas (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: python-libmaas (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: python-libmaas (Ubuntu Oracular)
Importance: High
Assignee: Alan Baghumian (alanbach
)
Importance: High
Assignee: Alan Baghumian (alanbach)
Status: In Progress
** Changed in: python-libmaas (Ubuntu)
Assignee: (unassigned) => Alan Baghumian (alanbach)
** Changed in: python-libmaas (Ubuntu)
Status: New => In Progress
** Changed in: python-libmaas (
I am experiencing a very similar issue on a new AMD Ryzen 7 machine
running Jammy + 6.5 HWE kernel, when USB Ethernet adapter is under heavy
load:
Jul 4 13:09:21 kvm-09 kernel: [ 2383.690610] [ cut here
]
Jul 4 13:09:21 kvm-09 kernel: [ 2383.690615] NETDEV WATCHDOG: enxe
I just rebuilt and installed fresh packages on Noble using the supplied
patch above and all good now!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/2062177
Title:
Remmina crashes aft
I just rebuilt and installed fresh packages on Noble using the supplied
patch above and all good now!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062177
Title:
Remmina crashes after RDP connectio
We have now confirmed at three different locations that Live-Migration
from PKRU PRE-5.15.0-85.95 to PKRU 5.15.0-85.95 compute nodes breaks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2
I'm not 100% if this trace is directly related to the NIC driver,
however it was int middle of two "Unit Hang" messages, so I pasted it
here. Might be a bi-product.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
Sun Jun 4 13:25:23 2023] [ cut here ]
[Sun Jun 4 13:25:23 2023] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0
timed out
[Sun Jun 4 13:25:23 2023] WARNING: CPU: 11 PID: 0 at
net/sched/sch_generic.c:477 dev_watchdog+0x27a/0x290
[Sun Jun 4 13:25:23 2023] Modules linked
I disabled APMS under Advanced Settings in BIOS, but that did not make a
difference. Also, upgraded one of the nodes to Focal HWE 5.15 kernel and
both are still having the same issues
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
This NIC is supported by the 5.4.0 Focal LTS kernel, however, any
changes on the switch side or even disconnecting and connecting the
Ethernet cable causes the card to hang:
Jun 03 18:32:58 kvm-02 kernel: e1000e :00:1f.6 eno1: Detected Hardware Unit
Hang:
TDH
This is still happening, any progress on the fix?
Mar 26 19:41:36 juju-868061-case00356962-2 zvol_wait[123774]: cannot open
'rpool/export/vault/block': dataset does not exist
Mar 26 19:41:36 juju-868061-case00356962-2 sudo[120459]:
pam_unix(sudo:session): session closed for user root
Mar 26 19:4
The network-manager package in Bionic and Focal install as symlink to
NetworkManager.service correctly:
https://packages.ubuntu.com/search?searchon=contents&keywords=network-
manager.service&mode=exactfilename&suite=bionic&arch=any
https://packages.ubuntu.com/search?searchon=contents&keywords=net
The network-manager package in Bionic and Focal install as symlink to
NetworkManager.service correctly:
https://packages.ubuntu.com/search?searchon=contents&keywords=network-
manager.service&mode=exactfilename&suite=bionic&arch=any
https://packages.ubuntu.com/search?searchon=contents&keywords=net
This is happening on a default Jammy GNOME install. No extra extensions.
This starts when the machine reaches high uptime usually 2 weeks+
journalctl is full of:
Aug 18 11:28:09 veloci gnome-shell[2558]: Key repeat discarded, Wayland
compositor doesn't seem to be processing events fast enough!
This is happening on a default Jammy GNOME install. No extra extensions.
This starts when the machine reaches high uptime usually 2 weeks+
journalctl is full of:
Aug 18 11:28:09 veloci gnome-shell[2558]: Key repeat discarded, Wayland
compositor doesn't seem to be processing events fast enough!
Just tested the above image with eog 3.36.3-0ubuntu1 (Focal) and it
crashed (Virtual Machine with 2 CPU cores and 4GB RAM). Tested with eog
42.0-1 (Jammy) and it worked.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to eog in Ubuntu.
https
Just tested the above image with eog 3.36.3-0ubuntu1 (Focal) and it
crashed (Virtual Machine with 2 CPU cores and 4GB RAM). Tested with eog
42.0-1 (Jammy) and it worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Just tested the above image with eog 3.36.3-0ubuntu1 (Focal) and it
crashed (Virtual Machine with 2 CPU cores and 4GB RAM). Tested with eog
42.0-1 (Jammy) and it worked.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to eog in Ubuntu.
ht
Just tested with gdm3 3.36.3-0ubuntu0.20.04.4 (Focal) and this is still
happening.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774081
Title:
/etc/gdm3/Init/Default not evaluated
To manage notifi
Just tested with gdm3 3.36.3-0ubuntu0.20.04.4 (Focal) and this is still
happening.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1774081
Title:
/etc/gdm3/Init/Default not evaluated
This is also affecting Virsh (KVM/QEMU) based virtual machines. Just
tested with The latest Focal update (gnome-settings-daemon
3.36.1-0ubuntu1.1) and the machine was turned off without any
notifications.
--
You received this bug notification because you are a member of Desktop
Packages, which is
This is also affecting Virsh (KVM/QEMU) based virtual machines. Just
tested with The latest Focal update (gnome-settings-daemon
3.36.1-0ubuntu1.1) and the machine was turned off without any
notifications.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
This is also affecting Virsh (KVM/QEMU) based virtual machines. Just
tested with The latest Focal update (gnome-settings-daemon
3.36.1-0ubuntu1.1) and the machine was turned off without any
notifications.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
This is no longer reproducible. I always create volumes this way and it
works. The latest version tested with Jammy Jellyfish: 1:4.0.0-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/551432
Title:
v
This is no longer reproducible. I use this function all the time and it
just works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/337763
Title:
virt-manager reboot action is non-functional
To manag
Just tested with Focal's Nautilus 1:3.36.3-0ubuntu1.20.04.1 and was not
able to reproduce this issue. Should be fixed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1576252
Title:
L
Just tested with Focal's Nautilus 1:3.36.3-0ubuntu1.20.04.1 and this
does not happen.
Followed the same scenario and renamed 2 out of 4 sample files:
1) Using Nautilus itself.
2) Closed Nautilus and renamed the files in terminal.
In both cases Nautilus automatically regenerated the thumbnails.
Just tested with Focal's Nautilus 1:3.36.3-0ubuntu1.20.04.1 and this
does not happen.
Followed the same scenario and renamed 2 out of 4 sample files:
1) Using Nautilus itself.
2) Closed Nautilus and renamed the files in terminal.
In both cases Nautilus automatically regenerated the thumbnails.
Just tested with Focal's Nautilus 1:3.36.3-0ubuntu1.20.04.1 and was not
able to reproduce this issue. Should be fixed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1576252
Title:
Just tested with Focal's Nautilus 1:3.36.3-0ubuntu1.20.04.1 and was not
able to reproduce this issue. Should be fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576252
Title:
Launching nautilus
Just tested with Focal's Nautilus 1:3.36.3-0ubuntu1.20.04.1 and this
does not happen.
Followed the same scenario and renamed 2 out of 4 sample files:
1) Using Nautilus itself.
2) Closed Nautilus and renamed the files in terminal.
In both cases Nautilus automatically regenerated the thumbnails.
I just tested this with Bionic and it seems to be fixed. Previewed files
~/.cache/.fr- no longer exist after closing file-roller.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/14442
I just tested this with Bionic and it seems to be fixed. Previewed files
~/.cache/.fr- no longer exist after closing file-roller.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444210
Title:
Preview
I just tested this with Bionic and it seems to be fixed. Previewed files
~/.cache/.fr- no longer exist after closing file-roller.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/14
I just did a test myself and the bug is still present. Simply re-install
your nova-common package and there goes the SSH key permissions. As
others mentioned, it is indeed this line in the postinst script:
find /var/lib/nova -type f -exec chmod 0644 "{}" + -o -type d -exec
chmod 0755 "{}" +
--
Y
Thank you all for investigating and fixing this.
--
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/1959085
Title:
Ubuntu 22.04 boot stuck in initramfs, when installed
Thank you all for investigating and fixing this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959085
Title:
Ubuntu 22.04 boot stuck in initramfs, when installed with zfs
encryption
To manage no
Thank you all for investigating and fixing this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1959085
Title:
Ubuntu 22.04 boot stuck in initramfs, when installed with zfs
encrypt
I confirmed this is happening. Here are two ways to reproduce:
1) Grabbed jammy-desktop-amd64.iso nightly build (Feb 2). Installing a
system using this ISO, while choosing Encryption + ZFS lands you on this
error.
2) Installed Impish using an ISO from October 12, choosing Encryption +
ZFS. The sy
I confirmed this is happening. Here are two ways to reproduce:
1) Grabbed jammy-desktop-amd64.iso nightly build (Feb 2). Installing a
system using this ISO, while choosing Encryption + ZFS lands you on this
error.
2) Installed Impish using an ISO from October 12, choosing Encryption +
ZFS. The sy
I confirmed this is happening. Here are two ways to reproduce:
1) Grabbed jammy-desktop-amd64.iso nightly build (Feb 2). Installing a
system using this ISO, while choosing Encryption + ZFS lands you on this
error.
2) Installed Impish using an ISO from October 12, choosing Encryption +
ZFS. The sy
*** This bug is a duplicate of bug 1959085 ***
https://bugs.launchpad.net/bugs/1959085
I performed some tests last night and confirm this is indeed unrelated
to Ubiquity and related to #1959085.
** This bug has been marked a duplicate of bug 1959085
Ubuntu 21.10 boot stuck in initramfs
--
This seems to be related to #1959085, going to try it later to confirm
that Ubiquity is not the culprit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960974
Title:
Ubiquity 22.04.4 - ZFS Encrypted
I just found this, I encountered this exact same issue with Jammy
Desktop installer last night and filed a bug here : #1960974
--
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.n
I just found this, I encountered this exact same issue with Jammy
Desktop installer last night and filed a bug here : #1960974
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1959085
Ti
I just found this, I encountered this exact same issue with Jammy
Desktop installer last night and filed a bug here : #1960974
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959085
Title:
Ubuntu 21.
Public bug reported:
1) Booted Ubuntu Jammy Desktop ISO made using UNetbootin
2) Started installer
3) Picked Erase Disk + ZFS + Encryption
4) Installation completed successfully and the machine reboots
5) After asking decryption password, the system drops in a busybox shell, with
permission denie
** Attachment added: "Decryption password prompt"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960974/+attachment/5561119/+files/PXL_20220216_001903736.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Package: zfs-dkms
Version: 2.0.3-1~bpo10+1
Severity: normal
-- System Information:
Debian Release: 10.10
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-0.bpo.5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TA
ote:
> Am 18.04.2016 um 18:09 schrieb Alan Baghumian:
> > Hi Guys,
> >
> > Regarding transparency of selected text in Evolution, the package needs
> > to be recompiled using webkitgtk 2.4.10+ and that will fix it.
>
> I thought webkit needed a rebuild against gtk 3.20, not e
Hi Guys,
Regarding transparency of selected text in Evolution, the package needs
to be recompiled using webkitgtk 2.4.10+ and that will fix it.
- AlanOn Mon, 2016-04-18 at 17:48 +0200, Christoph Anton Mitterer wrote:
> On Mon, 2016-04-18 at 17:42 +0200, Michael Biebl wrote:
> >
> > No idea about t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 04 Mar 2010 20:29:28 -0800
Source: jalali-calendar
Binary: jalali-calendar
Architecture: source all
Version: 1.6.9-1
Distribution: unstable
Urgency: low
Maintainer: Debian Arabic Packaging Team
Changed-By: Alan Baghumian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 21 Jun 2010 06:47:42 +0300
Source: myspell-hy
Binary: myspell-hy
Architecture: source all
Version: 0.20.0-1
Distribution: unstable
Urgency: low
Maintainer: Alan Baghumian
Changed-By: Alan Baghumian
Description:
myspell-hy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 22 Oct 2009 20:15:56 -0700
Source: balsa
Binary: balsa balsa-dbg
Architecture: source amd64
Version: 2.4.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian GNOME Maintainers
Changed-By: Alan Baghumian
Description
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 22 Oct 2009 20:15:56 -0700
Source: balsa
Binary: balsa balsa-dbg
Architecture: source amd64
Version: 2.4.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian GNOME Maintainers
Changed-By: Alan Baghumian
Description
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 23 Sep 2009 22:14:36 -0700
Source: myspell-fa
Binary: myspell-fa
Architecture: source all
Version: 0.20070816-2
Distribution: unstable
Urgency: low
Maintainer: Debian Arabic Packaging Team
Changed-By: Alan Baghumian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 20 Sep 2009 19:40:06 -0700
Source: myspell-hy
Binary: myspell-hy
Architecture: source all
Version: 0.10.1-2
Distribution: unstable
Urgency: low
Maintainer: Alan Baghumian
Changed-By: Alan Baghumian
Description:
myspell-hy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Guys,
A temporary workaround for the problem is to edit /etc/default/rcS file
and set FSCKFIX to yes. At least it wont stop your boot process asking
for manual fsck run.
Hopefully maintainers can put together soon to fix this.
Thanks,
Alan
--
1 - 100 of 311 matches
Mail list logo
