Public bug reported:
I can rollback to old kernel and audio works fine there.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19
Uname: Linux 5.13.0-37-generic x86_64
NonfreeKernelModules:
Public bug reported:
I can rollback to old kernel and audio works fine there.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19
Uname: Linux 5.13.0-37-generic x86_64
NonfreeKernelModules:
point taken, apologies for addressing the wrong audience, who indeed
volunteer their time to help.
I do not quite agree with the metaphor, as my old parcel deliverer has taken an
old working delivery back and pushed me a new delivery that doesn't work in my
environment - without prior notice or
Some additional discussion at https://forum.snapcraft.io/t/creating-
wireguard-connection-on-network-manager-snap/29182/
I cannot understand how it would still create a "tunnels:" stanza on the
latest version of netplan.
But I think I found an explanation now:
The NM snap is not actually using
(In reply to Mantas M. (grawity) from comment #6)
> The magic disappears in Firefox's AppArmor profile, which doesn't allow it to
> access `/tmp/krb5cc_*`. As an easy workaround until the Snap configuration is
> fixed, edit `/etc/krb5.conf` to relocate your Kerberos ticket cache somewhere
>
The magic disappears in Firefox's AppArmor profile, which doesn't allow
it to access `/tmp/krb5cc_*`. As an easy workaround until the Snap
configuration is fixed, edit `/etc/krb5.conf` to relocate your Kerberos
ticket cache somewhere Firefox *can* access it:
```
[libdefaults]
Being on Ubuntu 22.04, the .deb package has been removed and one is
forced to use the snap version.
kerberos does not work with the latest version and this is quite a
blocker for me as there is no alternative (other than switching
browsers).
--
You received this bug notification because you are
As reported here, there is an issue with the PCI controller on the
unmatched board that must be fixed in Linux (cf [1]) and u-boot: for
u-boot, the upstream commit a398a51ccc68c0a7aee14f8328dc86a1a4cfba85
("pci: Work around PCIe link training failures") should be cherry-picked
for 22.04.
Thanks
A similar patch that solves the same issue was actually merged for 5.18
[1].
I encountered this bug with our current u-boot (2022.01+dfsg-2ubuntu1)
and linux kernel (5.15.0-1004.4): I applied the patch in [1] on top of
5.15.0-1004.4 successfully and it solved the problem. So as you already
tagged
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
Change the key would need to go with adding
AutostartCondition=GSettings... to the .desktop for the binary to not be
started
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965996
Title:
Disable
Robert, the change will mean the binary is going to be started at every
login, even if it's low cost it doesn't seem needed, shouldn't we simply
drop the ubuntu-settings override to set the key to true for ubuntu
sessions?
--
You received this bug notification because you are a member of Ubuntu
I'm not seeing a significant drop in SMB transfer rate between kernels
5.13.0-1015-raspi and 5.13.0-1016-raspi:
+ uname -r
5.13.0-1015-raspi
+ dd of=samba/juergh/foo if=/dev/zero bs=1G count=10
10+0 records in
10+0 records out
10737418240 bytes (11 GB, 10 GiB) copied, 96.5918 s, 111 MB/s
+ dd
Reminder: Please do continue trying to get mini-buildd fixed in a way to
work in Jammy and get it uploaded before release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965973
Title:
Remove
I think this request is reasonable and added a few more details to the
description.
After checking with Doko to be sure I agree and will remove this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Removing packages from jammy:
mini-buildd 1.1.19 in jammy
mini-buildd 1.1.19 in jammy amd64
mini-buildd 1.1.19 in jammy arm64
mini-buildd 1.1.19 in jammy armhf
mini-buildd 1.1.19 in jammy i386
mini-buildd
fwiw it is "invalid" here as apt has nothing to do with it, as it did
what it is supposed to do, upgrade a package: It has no business in the
contents, similar to a parcel deliverer. It is probably more productive
you figure out what exactly is not working in foo.deb vs. foo.snap and
report this
This bug is awaiting verification that the linux-aws/5.4.0-1070.74
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists,
Is it possible to update the version of this package in official Ubuntu
20.04+ repos to reflect this change?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965145
Title:
CMake definitions (.cmake
** Package changed: snap (Ubuntu) => snapd (Ubuntu)
** Tags added: impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966053
Title:
Installing Ubuntu 21.10 fails because the installer hangs at
Public bug reported:
I have two monitors: the inbuilt laptop one, 1920x1080 at 125% scaling
shifted slightly down to match the relative heights on my desk, and an
external one, 1920x1080 at 100% scaling, primary. I have the dock set to
autohide.
When I open the dock by mousing to the side of the
Public bug reported:
My Lenovo desktop running Ubuntu 21.10 became unstable and bloated and
in the interest of time, I decided to just reinstall the entire system
using a fresh installation iso.
The system boots properly and the installer works without hassle until
it tries to install firefox
** Description changed:
The Django 3.2 transition is currently being blocked in proposed by
mini-buildd because it is severely outdated. mini-buildd's current
version in Jammy is 1.1.19, which is an old experimental version. The
two options to fix this would either be to move it back to
When I did below operation it could show the full desktop.
For 3840 x 2160
$ xrandr --output DP-5 --scale 2x2
For 7680 x 4320
$ xrandr --output DP-5 --scale 4x4
** Tags added: oem-priority originate-from-1965860 sutton
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
On ThinkStation with Nvidia T400.
1. Enter os,and enter Settings -> Displays
2. Change the Scale from 100% to 200% and aplly keep changes
3. Turn on the Fractional scaling
4. Turn off the Fractional scaling
5. Turn on and off again and again, each time the screen size is
Apologies for my rookie message, but I'm trying to track the roadmap for
a 20.04 fix/roll-out. Is this the place to ask? Virtual cookies/beers as
thanks in advance :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello,
Thank you for your feedback.
I hope we will have a solution, which we can deploy across our entire fleet. I
thank you and wish you good luck. Thank you for your work on this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
The Django 3.2 transition is currently being blocked in proposed by
mini-buildd because it is severely outdated. mini-buildd's current
version in Jammy is 1.1.19, which is an old experimental version. The
two options to fix this would either be to move it back to
Hey Dan. I've been trying to backport it to 21.10 (available in
ppa:dgadomski/lp1948008-desktop-icons) but it seems to work only one-way
for now. I am looking into this.
20.04 on the other hand seems even more complicated, I will look into it
right after I get 21.10 working, but can't provide any
Any news ? :'(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948008
Title:
Copying and pasting files between desktop and Nautilus does not work
To manage notifications about this bug go to:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: psychtoolbox-3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958673
Good morning! I noticed that this report started with a request to move
Focal 20.04 up to 1.20.14, but it looks like only Jammy was moved up? Is
there a plan to move Focal up as well?
I selfishly ask as one of the MATE+NVIDIA495/510 sufferers (i.e.,
/xrdp start
Starting xrdp (via systemctl): xrdp.serviceJob for xrdp.service failed
because the control
process exited with error code.
See "systemctl status xrdp.service" and "journalctl -xeu xrdp.service" for
details.
failed!
In /var/log/xrdp.log, I see
The package follows the exact same notion as the other cd-boot-images-*
packages. Simple data package, only built from other packages in the
archive. Subscribing foundations and promoting.
Override component to main
cd-boot-images-riscv64 1 in jammy: universe/misc -> main
cd-boot-images-riscv64 1
*** This bug is a duplicate of bug 1966046 ***
https://bugs.launchpad.net/bugs/1966046
** This bug is no longer a duplicate of bug 1965324
jammy/linux-oem-5.17: 5.17.0-1002.2 -proposed tracker
** This bug has been marked a duplicate of bug 1966046
jammy/linux-oem-5.17: -proposed
** Changed in: gnome-shell (Ubuntu Jammy)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964442
Title:
[jammy][regression] gnome-shell PolicyKit password
Public bug reported:
How to recreate my error:
I ran it on CM4 arm64 architechture with Ubuntu Server 20.04 with :
netplan.io at 0.103-0ubuntu5~20.04.6 arm64
network-manager snap at 20/stable: 1.22.10-11
- Install network manager snap:
sudo snap install network-manager
- Remove network
Yes, unfortunately there is no way to fix it in that case. The udev
rules properly avoid starting brltty when the iManufacturer field is
changed from FTDI to the actual manufacturer of the device, but not when
it is left to FTDI.
--
You received this bug notification because you are a member of
** Changed in: neutron (Ubuntu Hirsute)
Status: New => Won't Fix
** Changed in: openvswitch (Ubuntu Hirsute)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu)
Assignee: (unassigned) => Sergio Costas (rastersoft-gmail)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965537
Title:
Desktop
Test on WVB4-DVT2-A2, BIOS 1.2.0. reboot 50 times consecutively.
Didn't see consecutive Bluetooth tx timeout.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965467
Title:
Need to reset MT7921 BT
Riding on the same MIR, let me promote the newly added riscv64
equivalent of cd-boot-images to main.
** Also affects: cd-boot-images-riscv64 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I reviewed nftables 1.0.2-1ubuntu1 as checked into jammy. This shouldn't
be considered a full audit but rather a quick gauge of maintainability.
nftables is a replacement for iptables etc - it provides userspace tooling
to control the Netfilter packet classification system within the Linux
Attaching the updated debdiff in case we do decide we want this (even in
the broken state)
** Patch added: "nftables_1.0.2-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/1966017/+attachment/5572129/+files/nftables_1.0.2-1ubuntu2.debdiff
--
You received this bug
Turns out I wasn't looking closely enough at the autopkgtest logs from
my local testing - I was trying to run the tests with the pre-built
binary packages and whilst it would indicate the internaltest-py.sh
tests were passing, they were actually completely failing without any
error indication:
** Tags removed: verification-needed-focal
** Tags added: 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/1965467
Title:
Need to reset MT7921 BT when the firmware hang or
Thanks for your attention to this bug report. I don't quite see how it's
invalid - the upgrading behavior implemented here is breaking systems
without prior notice (and without offering any choice).
The least that could have been done is warn during one update cycle and
switch over sometimes
At the moment you are kind of getting around the "wrong symbols" by not using
the map (missing 1d507ce7f1d) and thereby not using the wrong symbols
(nft_set_optimize/nft_get_optimize).
But that explains (as you already know and said above) why it is all @base.
--
You received this bug
@Steve - don't you also need
http://git.netfilter.org/nftables/commit/?id=e98a9b83cd52c7c75bedb3dad46539b197ed17ba
?
And then an updated symbols file for it?
As well as
http://git.netfilter.org/nftables/commit/?id=1d507ce7f1d3c12481ee24bd1dcac2fc1984ee9f
actually. You said you tried, but what
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: software-properties (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965661
Maybe this was caused by an Ubuntu config change? Building 5.14.20 and
5.14.1 from git results in failure now. Only the mainline debs of those
versions succeed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kpcli (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896338
Title:
Please upgrade to newest upstream release
To manage notifications
FYI - Fixup uploaded as part of 0.6.3-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950631
Title:
[FFe] wrap swtpm in an apparmor profile
To manage notifications about this bug go to:
FYI - I got positive feedback for my MR and in general from Foundations,
I'll upload this to Jammy now. This will address bug 1950631, the
security request by sarnold and a general stabilization update. =>
0.6.3-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
** Changed in: yaru
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965941
Title:
Oval buttons in Java apps on 22.04/Yaru
To manage notifications about this bug go to:
Got a Team ack on MM, uploading this now ...
Uploading to ubuntu (via ftp to upload.ubuntu.com):
Uploading needrestart_3.5-5ubuntu2.dsc: done.
Uploading needrestart_3.5-5ubuntu2.debian.tar.xz: done.
Uploading needrestart_3.5-5ubuntu2_source.buildinfo: done.
Uploading
** Changed in: apt (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/1965960
Title:
apt installs snap packages
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1945011 ***
https://bugs.launchpad.net/bugs/1945011
** This bug has been marked a duplicate of bug 1945011
kernel BUG at fs/inode.c:1676! during Live CD ubiquity partman with NTFS
partitions
--
You received this bug notification because you are a
Can you please try "reboot=" kernel parameter? the value can be "bios,
acpi, kbd, triple, efi, or pci".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917471
Title:
[Regression] Bus Fatal Error
I have expected this to happen not just for USB input devices but for
all USB devices, like your external drives. I just don't have any other
devices at hand to verify.
For reference, here's a related question on AskUbuntu:
https://askubuntu.com/questions/1394480/keyboard-mouse-stop-working-
** Changed in: gnome-bluetooth3 (Ubuntu)
Assignee: Ioanna Alifieraki (joalif) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964600
Title:
[MIR] gnome-bluetooth3
To manage
It's again waking with a black screen in which only mouse and
Fn+Ctrl+Alt+F?? keys work. I've attached the jountalctl -b0 output from
prior to reboot, probably more relevant than grabbing the actual reboot.
Mär 23 07:09:16 aletheia kernel: Restarting tasks ... done.
Mär 23 07:09:16 aletheia
It looks like the problem is with unpacking .../firefox-locale-en as
the history and term logs show.
Ran another test this time with no Internet and minimum install and no errors
were encountered.
Ran yet another test with Internet connection and no downloading and again the
problem with
Thanks for outlining your steps in detail.
In my former tests I did use "minimal" instead of "normal" and did not yet
purge+install open-vm-tools.
Let me try exactly yours to be closer to your case...
1. I get the ISO from
https://cdimage.ubuntu.com/daily-live/current/jammy-desktop-amd64.iso
Public bug reported:
I just installed Ubuntu-22.04 last week and have noticed lots of command
line apps seem to hang for 10-30sec before working. Eventually that got
annoying enough that I looked into it.
Anyway, apps like "telnet" (yep, I'm that old) and oddly enough sudo
showed this issue
And one further log file re above comment
** Attachment added: "term.log"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965805/+attachment/5572107/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@brian-murray Brian - re comment # 11
Re tested same machine and same ISO also same results - here are the log
files from /var/log/apt
** Attachment added: "history.log"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965805/+attachment/5572106/+files/history.log
--
You received
I can reproduce the issue with jammy-desktop-amd64.iso daily build
20/Mar/2022 from https://cdimage.ubuntu.com/daily-live/current/jammy-
desktop-amd64.iso
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This concerns xubuntu-wallpapers 22.04 in Ubuntu jammy.
Please add the Xubuntu backdrop from the trusty release, i.e.
https://3.bp.blogspot.com/-pLKk0mvZIQE/U05l_GluNyI/SPM/X6PzqUZhH_s/s1600/xubuntu-
trusty.png
I miss that mouse.
** Affects: xubuntu-artwork
OK then next please try https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.14/
If it works then next try: https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.14.10/
If it fails then try: https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.13/
We need to find the version where the black screen
both of those exhibit the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965968
Title:
post jammy update, black/flickering screen on boot
To manage notifications about this bug go to:
Hi Jeff,
Now it fail to install Ubuntu server 22.04 with the latest ISO image, but it
can pass after update subiquity to the latest. If the latest subiquitythe can
be merged into ISO image?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks for your attention.
For the record, I saw the same errors mentioned in this bug after the
Firefox install timed out, which is why I posted the screenshot. (I
thought it might provide additional detail about the root cause.)
After the snap install timed out, the entire install process
Heh, two separate bugs on screen at the same time...
Next please try these kernels:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14.20/
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14.21/
And please keep i915.enable_psr=0
--
You received this bug notification because you are a
(If this were a build time testsuite, our log comparison process would
pick up changes. We could *maybe* do something akin to how we try to
detect new failing tests in openjdk in qrt's notes_testing/openjdk/
where we maybe compare our current adt runs of nftables against a prior
run, and look for
So this looks okay, there are unfortunately a bunch of errors in the
tests with v1.0.2 against a 5.15 kernel because the 'egress' hook
support was only added in 5.16
(https://git.kernel.org/linus/42df6e1d221dddc0f2acf2be37e68d553ad65f96).
This results in the following output in a jammy VM:
96
** Changed in: ukui-desktop-environment (Ubuntu)
Status: In Progress => Fix Released
** Changed in: ubuntukylin-meta (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The upgrade dialog says:
```
Upgrade to the firefox snap
Starting in Ubuntu 22.04, all new releases of firefox are
only available to Ubuntu users through the snap package.
This package update will transition your system over
i915.enable_psr=0 did not fix the black screen issue, but did appear to
remove the flickering purple streaks, fwiw.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965968
Title:
post jammy update,
This also effects the https://cdimage.ubuntu.com/daily-
live/current/jammy-desktop-arm64.iso
is there any fix to it yet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947046
Title:
EFI stub:
301 - 382 of 382 matches
Mail list logo
