Why are you coming back to these ancient tickets?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/826479
Title:
Comming back from suspend takes alot longer
To manage notifications about this bug go t
This bug is awaiting verification that the linux-nvidia/6.8.0-1028.31
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-noble-linux-nvidia' to 'verification-done-
noble-linux-nvidia'. If
Public bug reported:
A very loud beep occurs on Bluetooth headsets (at least my Bose
Quietcomfort 35) when initially connecting, and often when sound starts
playing, for example when resuming audio media after stopping or
pausing, or when starting a Youtube video It is so loud as to be painful
and
This bug is awaiting verification that the linux-nvidia/6.8.0-1028.31
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-noble-linux-nvidia' to 'verification-done-
noble-linux-nvidia'. If
All autopkgtests for the newly accepted
linux-restricted-modules-lowlatency-hwe-6.8 (6.8.0-60.63.1~22.04.1) for jammy
have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-470/unknown (amd64)
Please visit the excuses page
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
** Summary changed:
- External monitor freezes intermittently
+ [i915 + Nvidia + Xorg] External monitor freezes intermittently
** Changed in: nvidia-graphics-drivers-550 (Ubuntu)
Status: Incomplete => New
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => New
--
You receiv
** Changed in: rclone-browser (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/2059246
Title:
packaged version should not check for latest release
To manage
All autopkgtests for the newly accepted linux-meta-gke (6.8.0-1025.29) for
noble have finished running.
The following regressions have been reported in tests triggered by the package:
dpdk-kmods/unknown (arm64)
fwts/unknown (arm64)
glibc/2.39-0ubuntu8.4 (amd64)
glibc/unknown (arm64)
lxc/unknown (
All autopkgtests for the newly accepted linux-restricted-modules-aws
(5.4.0-1146.156) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/unknown (i386)
Please visit the excuses page listed below and invest
this is happening in 25.04 too. On my laptop which did not previously
show this problem. There was some speculation by me that it was due to a
race condition, happening on my 7840U laptop would mean this is much
more widespread, I think (it's hardly high end hardware).
--
You received this bug no
[Expired for mysql-8.0 (Ubuntu) because there has been no activity for
60 days.]
** Changed in: mysql-8.0 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20
All autopkgtests for the newly accepted linux-restricted-modules-azure
(5.4.0-1151.158) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/unknown (amd64, i386)
Please visit the excuses page listed below a
Same conditions as in #25, exept Steam installed from the Ubuntu repos.
Ugrade successful, no issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106202
Title:
Kubuntu 24.10 do-release-upgrade a
** Description changed:
I experience drop frame using 0.40.0-3ubuntu1. Here are the ways that
can reproduce the situation on my laptop:
+ ```
# Download a 720p VP9.2 60fps sample video from Youtube
yt-dlp -f 334+249 LXb3EKWsInQ -o test.webm
# Play the video
mpv test.webm --fs --star
This might be related to bug 2107597.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2102006
Title:
Xorg freeze
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
Thanks. I forgot to mention; please also tell us the date and time the
freeze occurred :)
** Tags added: i915 nvidia
** Tags added: hybrid multigpu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/21020
This might be related to bug 2102006 or bug 2108692.
** Tags added: hybrid i915 multigpu
** Tags added: freeze
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107597
Title:
[i915 + Nvidia + Xorg] E
** Tags added: nvidia
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2108692
Title:
One screen freezes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
Tesiing the upgrade procedure with method in #1 on bare metal, pristine
24.10 fully updated with steam.deb from the Steam website: upgrade was
flawless!
Again, this upgrade experience is so much faster and issue free than it
has been for several cycles.
I will attempt an upgrade with Ubuntu's Str
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
This bug is awaiting verification that the linux-
aws-6.11/6.11.0-1013.14~24.04.1 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-noble-linux-
aws-6.11' to 'verification-done-noble-lin
** Tags added: kubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106202
Title:
Kubuntu 24.10 do-release-upgrade and Steam (or other) dependencies
installed produces not booting desktop
To m
For months now using the latest/candidate/core24 channel of the firefox
snap has worked to reactivate the Nvidia driver (both on 24.10 and
25.04). However, I just got an update for the snap that breaks this even
in that channel. :(
--
You received this bug notification because you are a member of
I can confirm it work for a system without libc:i386 installed, too.
A nice irony is that this system runs all of the time (and has a screen
- an old TV, usually switched off), so I want the desktop, but not
anacron (I want to define when my backups etc. will run and you can't
mark anacron as "not
This bug is awaiting verification that the linux-
raspi-5.4/5.4.0-1129.142~18.04.1 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-bionic-linux-
raspi-5.4' to 'verification-done-bionic
This bug is awaiting verification that the linux-
raspi-5.4/5.4.0-1129.142~18.04.1 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-bionic-linux-
raspi-5.4' to 'verification-done-bionic
This bug is awaiting verification that the linux-
raspi-5.4/5.4.0-1129.142~18.04.1 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-bionic-linux-
raspi-5.4' to 'verification-done-bionic
This bug is awaiting verification that the linux-
raspi-5.4/5.4.0-1129.142~18.04.1 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-bionic-linux-
raspi-5.4' to 'verification-done-bionic
This bug is awaiting verification that the linux-
raspi-5.4/5.4.0-1129.142~18.04.1 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-bionic-linux-
raspi-5.4' to 'verification-done-bionic
This bug is awaiting verification that the linux-
raspi-5.4/5.4.0-1129.142~18.04.1 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-bionic-linux-
raspi-5.4' to 'verification-done-bionic
This bug is awaiting verification that the linux-gke/6.8.0-1025.29
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-noble-linux-gke' to 'verification-done-noble-
linux-gke'. If the prob
All autopkgtests for the newly accepted linux-meta-aws (6.11.0-1014.15) for
oracular have finished running.
The following regressions have been reported in tests triggered by the package:
fwts/unknown (amd64)
glibc/unknown (amd64)
lxc/unknown (amd64, arm64)
snapd/unknown (arm64)
zfs-linux/unknown
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072586
Title:
Running "dconf update" with different umask affects the permissions of
dconf
I happened to be testing the SRU against Jammy as well and I see the
same behaviour that you do - the .sources files move to .sources.save
but don't move back to .sources when the repository profile is removed.
Though, I don't believe this is actually related to the patch. I see all files
in sour
This bug is awaiting verification that the linux-gke/6.8.0-1025.29
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-noble-linux-gke' to 'verification-done-noble-
linux-gke'. If the prob
Public bug reported:
**Description:**
When using Nautilus (Gnome Files) in Ubuntu 24.04, if the user navigates via
keyboard into a directory that contains exactly one file or folder, the
selection is lost. This makes it impossible to interact with the item using the
Enter key or arrow keys, e
** Description changed:
[ Impact ]
This was originally reported by a user applying the DISA-STIG on Ubuntu
desktop [1], which requires a global umask of 077. The global dconf databases
in /etc/dconf/db are intended to be read by many users (mode 644).
dconf uses g_file_set_contents
** Merge proposal linked:
https://code.launchpad.net/~whershberger/ubuntu/+source/glib2.0/+git/glib2.0/+merge/485046
** Merge proposal linked:
https://code.launchpad.net/~whershberger/ubuntu/+source/glib2.0/+git/glib2.0/+merge/485047
** Merge proposal linked:
https://code.launchpad.ne
** Description changed:
[ Impact ]
This was originally reported by a user applying the DISA-STIG on Ubuntu
desktop [1], which requires a global umask of 077. The global dconf databases
in /etc/dconf/db are intended to be read by many users (mode 644).
dconf uses g_file_set_contents
All autopkgtests for the newly accepted linux-meta-aws (6.8.0-1029.31) for
noble have finished running.
The following regressions have been reported in tests triggered by the package:
dkms/unknown (amd64)
dpdk-kmods/unknown (arm64)
fwts/unknown (amd64, arm64)
glibc/unknown (amd64, arm64)
zfs-linu
** Changed in: glib2.0 (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: glib2.0 (Ubuntu Noble)
Status: Triaged => In Progress
** Changed in: glib2.0 (Ubuntu Oracular)
Status: Triaged => In Progress
** Changed in: glib2.0 (Ubuntu Plucky)
Status: Triaged =>
** Description changed:
+ [ Impact ]
+
+ This was originally reported by a user applying the DISA-STIG on Ubuntu
+ desktop [1], which requires a global umask of 077. The global dconf databases
+ in /etc/dconf/db are intended to be read by many users (mode 644).
+
+ dconf uses g_file_set_contents
** Description changed:
Description of the problem
While in the middle of a copy the network interface (which uses the r8169
driver) went offline. Downing and then upping the interface restored
connectivity.
Steps to reproduce:
1. Check out a large subversion repository over HTTPS?
Jakub, do you know, will it be the same bug on Debian for example?
Or is it solely on QT no matter what?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083744
Title:
Maximized windows are not remem
Thank you Robie.
It appears snapd has proposed the fix for this and it will be a matter
of time until this becomes available to pull. In light of the issue
originating from snapd and not the lxd-installer package itself I agree
that it is best to not introduce any change in this package.
We have
** Project changed: launchpad => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2109362
Title:
ipu7 25.04 xps 13 9350
To manage notifications about this bug go to:
https://bugs.launchpad.net/
You have been subscribed to a public bug:
xps 13 9350 camera doesn't work in ubuntu 25.04 using intel-ipu7-dkms
driver
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: intel-ipu7-dkms
--
ipu7 25.04 xps 13 9350
https://bugs.launchpad.net/bugs/2109362
You received this
Tested on jammy using landscape-client version 23.02-0ubuntu1~22.04.5.
I added the proposed source using a .sources file so that I could test
it was moved to a .save file after repository profile application.
Registered with landscape-server and applied a repository profile. The
resulting state o
Public bug reported:
Just installed the official 25.04 on Lenovo Yoga Slim 7X (Snapdragon X
Elite). The installer worked fine with the exception of 2 caveats:
1. Secure Boot had to be disabled
2. Sound hardware was not detected
Installation went fine (I chose full-disc install with encryption
en
Public bug reported:
my wifi card details:
```
root@lap01:~# lspci | grep -i network
:00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi
(rev 01)
root@lap01:~# lspci -n | grep 14.3
:00:14.3 0280: 8086:51f0 (rev 01)
```
modules related:
```
root@lap01:~# lsmod | gre
Thanks Zbigniew for the analysis. We should fix our glibc build to not
include the packaging metadata in /usr/lib/x86_64-linux-gnu/Scrt1.o and
then check if that is enough.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106208
Title:
Relocation overflow in GRUB when booting with RISC-V EDK II and
emulating NUMA.
To manage notificati
The environment variable ELF_PACKAGE_METADATA needs to be unset for
that. We should probably do that for all startup object files (crt0.o,
crt1.o, crti.o, crtn.o, Scrt1.o, gcrt1.o, Mcrt1.o).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
All autopkgtests for the newly accepted tzdata (2025b-0ubuntu0.24.10.1) for
oracular have finished running.
The following regressions have been reported in tests triggered by the package:
astroplan/unknown (ppc64el, s390x)
astropy/unknown (ppc64el, s390x)
chrony/unknown (ppc64el, s390x)
dask.dist
** Description changed:
[Impact]
In order to follow our policy on keeping the container stack (docker.io-
app, containerd-app, runc, runc-app, docker-buildx, and docker-
compose-v2) up-to-date in our supported releases, let's backport the
stack in Plucky to Oracular, Noble, Jammy, and
please ignore rtw88_core in lsmod output.
(it is my working dongle).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2109375
Title:
Intel Corporation Alder Lake-P PCH CNVi WiFi (rev 01) [8086:51f0]
For what is worth, I used landscape-client 23.02-0ubuntu1~20.04.4 (from
current updates, not proposed), and I don't see a crash. Maybe something
is missing from the test plan, like the removal of some locale/langpack
package, or the fix isn't needed anymore?
ubuntu@f:~$ locale
LANG=en_GB.UTF-8
LAN
Thanks for testing with network-manager! I feel better about not
including the Breaks:, as I think many people do use network-manager-
openvpn (I do on my laptops).
> New patch removing the breaks rule for network-manager-openvpn
A few minor requests:
1. It looks like the security team has updat
This was already fixed for Ubuntu 25.04 "plucky" because it was included
in upstream's gnome-control-center 48.0.
** Changed in: gnome-control-center (Ubuntu)
Status: Fix Committed => Fix Released
** No longer affects: gnome-control-center (Ubuntu Plucky)
--
You received this bug notific
This bug is awaiting verification that the linux-aws/6.8.0-1029.31
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-noble-linux-aws' to 'verification-done-noble-
linux-aws'. If the prob
1 - 100 of 226 matches
Mail list logo
