[Expired for live-installer (Ubuntu Bionic) because there has been no
activity for 60 days.]
** Changed in: live-installer (Ubuntu Bionic)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
[Expired for live-installer (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: live-installer (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
[Expired for base-installer (Ubuntu Bionic) because there has been no
activity for 60 days.]
** Changed in: base-installer (Ubuntu Bionic)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
[Expired for initramfs-tools (Ubuntu Bionic) because there has been no
activity for 60 days.]
** Changed in: initramfs-tools (Ubuntu Bionic)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Public bug reported:
Crackling sound on headphones.
Sometimes sound is good after reboot and fails after some time or after
suspend
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
Uname: Linux
So I looked into this a bit more and based on
http://www.postfix.org/postconf.5.html#smtp_tls_CAfile is doesn't appear
to me that the ca-certificates.crt file needs to be in the chroot at
all. What happens if you just delete the chroot copy? Looking in the
git history, I can see we used to
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1955903
Title:
Xorg freeze
Status in xorg package in Ubuntu:
New
Bug
You have been subscribed to a public bug:
Every so often, whether I close the lid of the laptop or not, the screen
will go blank and neither pressing a key nor moving the mouse will show
anything. The only thing I can do to recover is hold the power button
down for 10 seconds to restart.
I don't understand why this is a won't fix bug.
If users pick a long NIC name by themselves, then it's users'
responsibility to fix it. But apparently this is not the case, it's an
unexpected behavior caused by internal conflicts of different linux
components.
--
You received this bug
I could fix it by executing the following workaround:
pacmd load-module module-alsa-source device=hw:2,2
The actual hw numbers might vary, depending on your specific board and
how many other audio devices you have connected.
Now I have switched to pipewire and that doesn't work anymore.
I even
** Package changed: ubuntu => console-setup (Ubuntu)
** Tags added: impish
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1955901
Title:
Romanian Keymap for German
** Also affects: network-manager (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
** Changed in: network-manager (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: network-manager (Ubuntu)
You have been subscribed to a public bug:
Description of problem:
gnome-keyboard-properties for Romanian language in German keyboards "Romanian
(Germany)" and "Romanian (Germany without Accents)" is still using the
incorrect characters for ș, ț, Ș and Ț. Instead of a comma underneath the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
I believe this is actually a bug in the QA website which misses the step
to setup /dev in the test scenario
https://iso.qa.ubuntu.com/qatracker/testcases/1318/info - so reassigning
there and marking the apt task as Invalid, but keeping it around rather
than deleting it, as it's related.
**
Thanks for your bug report. I believe you meant ubuntu-base, not ubuntu-
core (the snap based one)
How did you test this? This seems to me like you forgot to populate
/dev, either statically or by bind mounting the /dev from the host.
The tarball only contains an empty /dev, and the permissions
16 matches
Mail list logo
