Yea that looks alot better then mine. il try to have some time tomorrow
and i nuke the cluster and make a clean install and do things in a bit
of a diffrent order i think
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Fresh ubuntu 24.04 install when running
su -s /bin/sh -c "keystone-manage db_sync " keystone
This ends up in /var/log/apache2/keystone.log
2024-04-29 12:47:10.184549 File
"/usr/lib/python3/dist-packages/pymysql/protocol.py", line 221, in
raise_for_error
2024-04-29
A temporary fix is to check out source package build and copy out
cephadmlib
apt source cephadm
cd ceph-19.2.0~git20240301.4c76c50/
debuild -us -uc
mkdir /usr/lib/python3/dist-packages/cephadmlib
cp -R ./debian/tmp/usr/lib/python3/dist-packages/cephadmlib/*
Can confirm this on fresh install of 24.04 LTS amd64
Its also in caracal cloud repo ppa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063456
Title:
package cephadm: dependency "cephadmlib" missing
Indeed, looks like this issue is related to initramfs-tools, be that
through an incompatibility introduced in either.
I tested with the package in Debian Sid dropbear-initramfs (2024.84-1)
and got the same error. Meanwhile, on a Debian Sid install, it works.
Based on the above, I added
The above was observed on a QEMU KVM VM using server installer defaults
as well as with specific curtin storage definitions.
I also reproduced the same on a QEMU KVM VM using desktop installer and
clicking next on all questions (except user).
--
You received this bug notification because you
Public bug reported:
dropbear-initramfs seems to fail on not figuring out what the root
device is. This applies both to autoinstall and manual install and is
observed on today's beta (ubuntu-24.04-beta-live-server-amd64.iso on
2024-04-12)
ubuntu@ubuntu-server:~$ sudo apt install
I think the fix is to use a dpkg >= 1.22.3, but I'm not sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058395
Title:
pbuilder-dist noble create fails on jammy
To manage notifications about
This is caused by base-files 13ubuntu7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058395
Title:
pbuilder-dist noble create fails on jammy
To manage notifications about this bug go to:
Public bug reported:
I want to report an issue which might well have been reported already,
although i could not find it. A few weeks ago I switched from Ubuntu LTS
20.04 towards the LTS 22.04 with Wayland as default.
I discovered that there is a sort of incompatibility between the
Upgrading from 21.10 to 22.04 same issue. "Searching for obsolete
software"
Burning 1 core for 100%
/var/log/dist-upgrade/apt.log is spammed with messages like
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0)
[ removing comment, wrong kernel version. I'm seeing issue on .107, not
.105 ]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966819
Title:
System will not suspend using HWE kernel.
To manage
Adding default-sample-rate = 48000 to /etc/pulse/daemon.conf got rid of
the distortion but I only get audio from my left channel. Do you have
any idea why that could be the case?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi. I think this happens for me as well. I just want to add that I only
get audio from my left channel. Things sound good with other cards and
the same card on other operating systems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
We followed the steps in "Install UEFI SecureBoot nVidia in Ubuntu Desktop
amd64 in Jammy Daily" Image version: 1st of March.
No Nividia drivers were found in Additional drivers after a minimal
installation.
Computer used: HP Z-book Fury 15" G7.
We tried additionial
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1960703/+attachment/5560542/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960703
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1960703/+attachment/5560541/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1960703/+attachment/5560540/+files/PaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960703
Title:
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1960703/+attachment/5560539/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1960703/+attachment/5560538/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1960703/+attachment/5560537/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1960703/+attachment/5560536/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960703
Public bug reported:
The TASCAM US-122L, in previous versions of Ubuntu worked okay, with an
occasional xrun reported by jackd, running with default settings (sample
rate: 48000, frames/period: 1024). In Ubuntu 21.10 the device loads
without problem, playback is perfect, but when the system load
** Description changed:
1) Ubuntu Desktop amd 64 20211008.1 daily build
- 2) udisks 2.9.4-1
+ 2) udisks 2.9.4-1
3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions
disk images, should be mounted automatically
4) the automount feature seems to be gone or
Public bug reported:
Description:Ubuntu 20.04.3 LTS
Release:20.04
unbound/focal,focal-updates,focal-security,now 1.9.4-2ubuntu1.2 amd64
[installed]
Hello,
We have an issue with unbound package.
In some case of usage we have a certain number of idle tcp-sessions wich blocks
any new
** Changed in: gnutls28 (Ubuntu Focal)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928648
Title:
expiring trust anchor compatibility issue
To manage
What about focal? It is currently broken to.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928648
Title:
expiring trust anchor compatibility issue
To manage notifications about this bug go to:
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485630/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Description changed:
I cannot resume from suspend. I am on Ubuntu 20.10, Gnome
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485629/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923050
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485628/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923050
Title:
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485627/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923050
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485625/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923050
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485626/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923050
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485624/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485623/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923050
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485622/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485621/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923050
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485620/+files/PaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923050
Title:
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485619/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923050
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485618/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923050
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485617/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923050
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485616/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923050
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485615/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923050
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485614/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923050
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485613/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1923050/+attachment/5485612/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923050
Title:
apport information
** Tags added: apport-collected
** Description changed:
I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither
pushing the power button or opening the lid solves the issue. The led
indicator continues to pulsate and there's no indication of any response
Public bug reported:
I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither
pushing the power button or opening the lid solves the issue. The led
indicator continues to pulsate and there's no indication of any response
from the computer.
I've tried switching between versions 450
I can confirm the workaround by boxeus works on Ubuntu 20.04 LTS. To
improve on that, the lines can be added to the /etc/dropbear-
initramfs/config config file instead to avoid upgrade issues. It is
loaded towards the end of /usr/share/initramfs-tools/scripts/init-
bottom/dropbear anyway.
Which version of Mint (or which upstream Ubuntu it is based on?) I
wonder if there is a way to get those rows into the configs rather than
editing packaged files?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No, Tim, it's connected via display port. I don't have any logitech gear
and disabling autostart for Dropbox does not help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841826
Title:
Going to
I have this problem as well on ubuntu 20.10 on a Thinkpad T14 with
integrated Geforce MX330 graphics. My laptop is closed and docked via a
thunderbolt 3 dock to a single external monitor.
I have tried the fix proposed here:
https://askubuntu.com/questions/1083720/ubuntu-goes-suspended-after-
I understand that it's particularly difficult to reproduce the bug
because it requires a mail server with a certificate problem. Since it
was blocking me, I temporarily dealt with this by not using the Snap
version of TB and returning to the versions from the official Ubuntu PPA
(in my case TB
Looking at the Error Console was the right idea, thanks. Here's the
error that is caught when clicking the "Confirm Security Exception"
button:
Exception { name: "NS_ERROR_FAILURE", message: "Component returned
failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIURI.port]", result:
2147500037,
By "nothing happens" I mean that the "Add Security Exception" window
stays open with seemingly no effect when clicking on the button "Confirm
Security Exception". Clicking multiple times doesn't change the state of
the window either. The only way to advance is to click "Cancel" which
closes the
Hi Olivier, thanks for your help.
snap run thunderbird
Gtk-Message: 11:39:31.230: Failed to load module "canberra-gtk-module"
Gtk-Message: 11:39:31.248: Failed to load module "canberra-gtk-module"
(directly at launch, then nothing when reproducing the issue)
Nothing either with journalctl -f |
Public bug reported:
Note: This bug is specific to the Snap version of Thunderbird, I can't
reproduce it with the Ubuntu-packaged version for example (which I have
installed on Ubuntu, used for multiple years and stopped using recently
to get the more recent versions of TB available with Snap).
I, too, confirm that the proposed updates solve the audio issue (for my
system info, please see the initial information in the bug report).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901922
The testing package of libasound2 built by @hui.wang has resolved the
issue for me as well. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901922
Title:
[Lenovo ThinkPad T14 Gen 1] No
I had the same issue. 4.7.0~pre1+git20180411-2ubuntu2 is installed on a
new server - and that does not have the fix in it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769485
Title:
freeipa
I have reported the issue upstream:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1030
** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1030
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1030
--
You received this bug notification
In our case we decided to spend the same effort on orchestrating for
images:ubuntu/focal/cloud (which comes without snapd) rather than
working around issues with snap on the thicker default image.
But the workaround above can be used, and I remember it was documented
elsewhere on launchpad or
Public bug reported:
After logging in, only a dummy device is available for audio playback
(resulting in no audible playback). When running "pactl load-module
module-detect" the sound card shows up, and playback works as expected.
If pulseaudio is restarted with "pulseaudio -k" the playback
Public bug reported:
Lenovo X201 I7 processor 16 GB Ram. 500MB Samsung disk clean. Ran disk
tests on the disk, no errors reported.
Previously ran Ubuntu 14 on this machine, without issues.
U 20 installs without issues on similar Lenovo X200 (with lower specs)
ProblemType: Bug
DistroRelease:
There cant be many computers on whihc Ubuntu fails to install
predictably. I will sell you this one to test Ubuntu further.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895544
Title:
Seems to be a downstream issue.
I downloaded the same package version but from the repos for Debian Sid
and it works.
http://ftp.debian.org/debian/pool/main/a/asterisk-opus/asterisk-
opus_13.7+20171009-2_amd64.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "dmesg.5.4.0"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892163/+attachment/5403212/+files/dmesg.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892163
Title:
** Attachment added: "lspci.5.4.0"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892163/+attachment/5403213/+files/lspci.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892163
Title:
More info, I am using wifi for the network. 5G
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892163
Title:
Major networking regression linux-image-5.4.0-42-generic
To manage notifications about
It works super nice, in 5.3.0
in 5.4.0 it just keeps going and going for over 10 minutes before I give
up.
It literally takes seconds in 5.3.0, I can send that one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm having lots of troubles with apport-collect since the network is so
bad in 5.4.0, I tried apport-bug --save linux.apport linux, but that
just locks up for 10 minutes.
Is there any way I can run this offline and then send it with 5.3.0?
Or what info do you need that I can run by hand and
Also, running sudo apport-collect will not work since it can't attach to
my firefox not running as root. But I did manage to get an authorization
twice into my cache.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When booting into linux-image-5.4.0-42-generic networking grinds to a
halt. It is 1x times slower than usual.
Selecting an older kernel like linux-image-5.3.0-62-generic makes
networking normal again.
Description:Ubuntu 18.04.4 LTS
Release:18.04
It seems the workaround above does not work on Ubuntu 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813394
Title:
DROPBEAR_IFDOWN=* takes interface down but leaves netplan config
To manage
Public bug reported:
Since initramfs networking is rather limited, a simple flag to reset
networking afterwards (or not to generate netplan files) would be
valuable. The intended effect is to allow fully featured networking
tools to set up the network afterwards.
Use cases include the following,
Public bug reported:
The first bullet point of Netplans' Key Goals is "Usable in initramfs
(few dependencies and fast)".
This is currently not supported in Ubuntu.
A basic approach would be to use the same /etc/netplan/*.yaml whenever
initramfs depends on networking.
Supporting netplan in
Digging even further back, it turns out that IFDOWN is in itself a
workaround for an equal issue dating back to ~2012. As such, the core of
the issue lies with how initramfs network setup overrides netplan.
Adding that package.
Given the very limited setup /etc/initramfs-tools/initramfs.conf
Investigating further reveals that the package is not adapted for
netplan in the first place. The maintainer is not on launchpad and the
package was imported from Debian Sid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This also applies when set up with static IP's in /etc/initramfs-
tools/initramfs.conf. That case is most prominently noticed as lacking
nameservers after boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I agree. I confirm this is still happening on Ubuntu 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813394
Title:
DROPBEAR_IFDOWN=* takes interface down but leaves netplan config
To manage
The situation where this arose is in testing our Ubuntu 20.04
orchestration. Previously we used a script to ensure boot coherence. We
use two mirrored system drives, mirroring everything to the extent that
the system must be completely bootable after pulling a drive/having one
drive fail
** Tags added: 20.04 asterisk-opus vocoder
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879387
Title:
Opus module fail to load (Ubuntu 20.04)
To manage notifications about this bug go to:
Public bug reported:
After clean install and installation of packages asterisk and asterisk-
opus the opus module for asterisk fail to load.
[May 18 21:55:40] ERROR[72682] loader.c: Error loading module
'codec_opus_open_source.so':
/usr/lib/asterisk/modules/codec_opus_open_source.so: undefined
** Changed in: asterisk-opus (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878456
Title:
Error loading module (20.04)
To manage notifications about this bug
Container management seems to be the source of the error, sudo just
suppresses it. So a potential fix is in LXD or related packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868456
Title:
Workaround:
echo "Set disable_coredump false" | sudo tee -a /etc/sudo.conf
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am seeing this as well. A workaround is to remove all snaps but core,
then unmount the snap core before purging with apt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878674
Title:
apt purge
** Changed in: grub2 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876974
Title:
Support multiple ESPs
To manage notifications about this bug go to:
OK, so for anyone hitting this error until there may be a fix: For cases
where snapd is not needed (and perhaps purged later), and orchestration
relies on cloud-init to finish, the workaround in the container is:
systemctl stop snapd.seeded.service
or on the host:
lxc exec $CONTAINERNAME --
Chad, were you able to find the config that caused the effect? There is a
similar issue open here:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878225
I am trying to find out if it is a regression or something in my config.
--
You received this bug notification because you are a
Have you tested this on amd64? I am seeing the same outputs on amd64 and
trying to find out if it is a regression or something in my config. A
similar report has suggestions it may be due to faulty network setup for
the container:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1806070
--
Public bug reported:
After asterisk and asterisk-opus install on Ubuntu 20.04, opus wont
load.
[May 13 17:35:46] ERROR[9306] loader.c: Error loading module
'codec_opus_open_source.so':
/usr/lib/asterisk/modules/codec_opus_open_source.so: undefined symbol:
opus_encode
[May 13 17:35:46]
This is fairly problematic when core functionality that is orchestrated
in the cloud moves from deb to snap. In our example, lxc (LXD command
line tool) was assumed to be in the path when building the
orchestration. Using the full path makes it less portable. It also makes
managing multiple
What would be the proper way to remove these logs when they contain a
pasword? `shred /var/log/installer && rm -rf /var/log/installer`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878115
Title:
I ran 'grub-install', and expected both efi to be updated. It updates
only the primary ESP.
Both 'dpkg-reconfigure grub-efi-amd64' and running 'grub-multi-install'
directly update both ESPs. So on the package updates part it looks like
we are good to go.
The part that I am missing, is making it
Public bug reported:
Subiquity has the brilliant feature of supporting installing to multiple
ESP's. See https://bugs.launchpad.net/subiquity/+bug/1817066 for
details.
grub-install does not mirror this feature this out of the box, but
updates the ESP on /boot/efi only by default on such an
Public bug reported:
While upgradiing from 18.04LTS -> 20.04LTS
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mbpfan 2.1.1-2
ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
Uname: Linux 4.15.0-96-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
I can confirm that this error is shown after clean installing Ubuntu 20.04 on a
Mac and rebooting.
My device is a late 2015 iMac. Seems to work well but as stated above users
shouldn't be presented such a error when there is actually no problem.
--
You received this bug notification because
Forgot to say, the bug report was done with kernel 5.3.0-40 with a
working touch screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868392
Title:
Touchscreen not working in 5.3.0-42
To manage
Public bug reported:
My Asus Zenbook touch screen works in 5.3.0-40, but stops working when I
boot into the 5.3.0-42 kernel.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
1 - 100 of 3109 matches
Mail list logo
