** Changed in: mutter (Ubuntu Mantic)
Status: Triaged => In Progress
--
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/2034619
Title:
[amdgpu] gnome-shell gets SIGKILL'd when lock sc
The problem is with kernel 6.2 which is in both 23.04 and 22.04 (hwe) so
affects both releases.
--
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/2031969
Title:
Ubuntu 23.04: Suspend & Powe
At least attach the logs from the previous (failed) boot:
$ journalctl -b -1
--
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/2038719
Title:
Monitor Issues
Status in linux package in Ubun
** Tags added: kern-8205
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2038745
Title:
NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox)
driver installed
Please attach logs from the failed (previous) boot. Something like:
$ journalctl -b -1
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Summary changed:
- linux (6.2.0-34.34) lunar; urgency=medium* lunar/linux: 6.2.0-34.34
-proposed tracker (LP: #2033779)
+ 6.2.0-34.3
This does not appear to be a blocker for Ubuntu 23.10; removing the
milestone.
** Changed in: linux (Ubuntu Mantic)
Milestone: ubuntu-23.10 => None
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
** Changed in: linux-firmware-raspi (Ubuntu Mantic)
Milestone: ubuntu-23.10 => mantic-updates
** Changed in: linux-firmware-raspi (Ubuntu Mantic)
Milestone: mantic-updates => None
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
My understanding is this will be able to go into the mantic release
pocket with the kernel respin currently in progress, so should not need
to be an SRU.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member o
marking this fix committed for linux, version 6.5.0-9.9 in mantic-
proposed should contain the fix.
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
Please continue to use MUTTER_DEBUG_KMS_THREAD_TYPE=user as a workaround
then. Also if you're still experiencing the bug please run:
sudo apt install drm-info
drm_info > drminfo.txt
and attach the resulting text file here.
--
You received this bug notification because you are a member of Ke
** Summary changed:
- bluetooth not working proper;ly
+ Intel AX210 Bluetooth not working properly in focal kernel 5.15
** Package changed: bluez (Ubuntu) => linux-hwe-5.15 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-
Public bug reported:
System halts just after filesystem journaling after USB install of LTS Ubuntu
22.04.2 to Ubuntu 22.04.3, never makes it to grub screen, can't boot system.
Another bug report from 2020 says their system gets past grub screen and
then gets stuck, I don't even make it that fa
Removing packages from mantic:
nvidia-graphics-drivers-450-server 450.248.02-0ubuntu2 in mantic
libnvidia-cfg1-440-server 450.248.02-0ubuntu2 in mantic amd64
libnvidia-cfg1-450-server 450.248.02-0ubuntu2 in mantic amd64
libnvidia-common-440-se
Now:
$ reverse-depends src:nvidia-graphics-drivers-450-server
Reverse-Depends
===
* libnvidia-decode-440-server (for libnvidia-decode-450-server)
* libnvidia-encode-440-server (for libnvidia-encode-450-server)
* libnvidia-fbc1-440-server (for libnvidia-fbc1-450-server)
* libnvi
The failure is strange, since it initially affected USB ports 3 and 2.
Several hours later, when I turned the machine back on, it recognized a
USB memory in a USB 2 port and subsequently recognized a 500 GB HDD in a
USB port 3. When I disconnected the HDD disk and reconnected a similar
one into USB
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2038765
** Tags added: iso-testing
--
You received this bug notification because you are a member of Kernel
Packages, which
** Description changed:
df: /sys/firmware/efi/efivars: Invalid argument appears on first display
- of the installer - I note that at the end of the installation curtin
- fails due to an efivars error - looking at syslog I saw various efivars
- errors so I'm filing this with the kernel since this
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2038774
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
Only started recently, but not all apps.
Some snap, flatpak, or deb.
Snap: youtube music desktop
Flatpak: Easy effects
Deb: MultiViewer
When in windowed mode the cursor is fine,
But in full screen mode in some apps it is invisible.
Ubuntu 20.04.3 LTS
Kernel: 5.15.0-86
Window
Public bug reported:
Only started recently, but not all apps.
Some snap, flatpak, or deb.
Snap: youtube music desktop
Flatpak: Easy effects
Deb: MultiViewer
When in windowed mode the cursor is fine,
But in full screen mode in some apps it is invisible.
Ubuntu 20.04.3 LTS
Kernel: 5.15.0-86
Window
Can't seem to trip the issue on a 24 core x86 instance, maybe this is
ARM64 specific.
--
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/2038768
Title:
arm64: linux: stress-ng filename stres
** Also affects: linux (Ubuntu Mantic)
Importance: High
Status: Incomplete
--
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/2038768
Title:
arm64: linux: stress-ng filename stress
All autopkgtests for the newly accepted linux-meta-nvidia-tegra
(5.15.0.1018.18) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
wireguard/unknown (amd64)
Please visit the excuses page listed below and investigate the failures,
p
I created a 1GB file and created a fresh ext4 file system on it and loop
back mounted it on /mnt, I created test directory /mnt/test and ran:
/stress-ng --filename 0 --temp-path /mnt/test --klog-check
Managed to trip the kernel crash again. So it appears to occur on a fresh ext4
file system too
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2038768
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
Running latest Ubuntu mantic (ext4 file system) with kernel: Linux
mantic-arm64 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 28
19:12:05 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux
How to reproduce:
Fire up a 24 instance ARM64 QEMU instance with Ubuntu Mantic Server.
Note that just running stress-ng with --filename 0 will reproduce the
issue. I'm testing this now on a cleanly formatted ext4 file system
--
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/2038
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/2038765
Title:
df: /sys/firmware/efi/efivars:
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038765/+attachment/5707866/+files/syslog
--
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/2038765
Titl
Public bug reported:
df: /sys/firmware/efi/efivars: Invalid argument appears on first display
of the installer - I note that at the end of the installation curtin
fails due to an efivars error - looking at syslog I saw various efivars
errors so I'm filing this with the kernel since this is the fir
Sorry, but that was a kind request, very respectful. Not with a single
word I did imply any malicious intent. How respectful is this treatment
of other people's wording? Anyway, it just doesn't make sense to mix
these things up, as mentioned earlier. Even if it will end up with the
same cause, a bu
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/2038759
Title:
ubuntu does not mount usb disk
Public bug reported:
A week ago this problem appeared and was corrected by changing the cat
file /sys/module/usbcore/parameters/autosuspend from 2 to -1
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-86-generic 5.15.0-86.96
ProcVersionSignature: Ubuntu 5.15.0-86.96-gener
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1018.18 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-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linu
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1018.18 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-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linu
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1018.18 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-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linu
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1018.18 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-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linu
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1018.18 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-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linu
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1018.18 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-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linu
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1018.18 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-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linu
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1018.18 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-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linu
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1018.18 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-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linu
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1018.18 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-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linu
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1018.18 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-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linu
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1018.18 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-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linu
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1018.18 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-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linu
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1018.18 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-jammy-linux-nvidia-tegra' to
'verification-done-jammy-linu
This bug is awaiting verification that the linux-aws/6.2.0-1015.15
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-lunar-linux-aws' to 'verification-done-lunar-
linux-aws'. If the prob
Does anyone know of a Linux distribution with the latest kernel version
6.6?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2034477
Title:
Keyboard and Touchpad Not Workin
I open mate-display-properties and I changed the screen resolution from 4K to
1920x1080,
then after reboot system I have 1920x1080.
Do these programs use a different configuration file?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvi
>From sudo /usr/bin/nvidia-bug-report.sh
{
/var/log/kern.log:
Oct 8 01:43:29 tele kernel: [ 260.464109] NVRM: API mismatch: the client has
the version 535.113.01, but
Oct 8 01:43:29 tele kernel: [ 260.464109] NVRM: this kernel module has the
version 525.125.06. Please
O
@polarbaerhh, First and foremost, I expect to be treated, and for others
to be treated, with respect. It was inappropriate for you to suggest
that users are maliciously manipulating and altering others' reports.
Please be mindful of your words, as I can bring your behavior to the
attention of your
At the present day
- I upgraded driver to nvidia-driver-535 , 535.113.01-0ubuntu0.22.04.1
- I installed xserver-xorg-dev to remove above error about `xorg-server.pc'
But when I'm trying save settings to /etc/X11/xorg.conf
I have warning:
={
WARNING: Unable to parse X.Org version string.
A fix may already be available at
https://gitlab.freedesktop.org/drm/amd/-/issues/2486
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2486
https://gitlab.freedesktop.org/drm/amd/-/issues/2486
--
You received this bug notification because you are a member of Kernel
Packages, whic
** Package changed: xorg (Ubuntu) => linux-signed-hwe-6.2 (Ubuntu)
** Summary changed:
- Xorg freeze amdgpu mst powersaving
+ amdgpu mst power saving null ptr deref
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in
** Changed in: linux-signed-hwe-6.2 (Ubuntu)
Status: New => Incomplete
** Changed in: linux-signed-hwe-6.2 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu
You have been subscribed to a public bug:
Reoccurrence of amdgpu MST power saving related null pointer deref.
Likely should be against kernel instead, but let's see whether ubuntu-
bug attached sensible part of logs.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcV
Duplicate of #2038748 which apparently got some more logs than this one.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2038749
Title:
amdgpu mst power saving null ptr der
Public bug reported:
Amdgpu tends to crash when attempting to unlock screen after power
saving has been triggered on MST screen(s).
Further details to be filled in post-reboot.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1
ProcVersionSigna
@cfgnunes: Please do not hijack and mangle other people's reports.
I did not have this experience with 22.04.3 LTS. The logs and the description
belong to 23.04. Changing only the summary is pointless.
Maybe the problem exists in other Ubuntu versions too. It probably has to do
with kernel vers
Exactly Endre. These are the major problems. Request to kernel team will
be to address these three problems on priority.
In addition to that there is one more problem that I might not have
mentioned earlier and that is the issue related to system Suspend
functionality. In my LENOVO V15 GEN4 AMN (A
418 is clean.
$ reverse-depends src:nvidia-graphics-drivers-418-server
No reverse dependencies found
$ reverse-depends src:nvidia-graphics-drivers-418-server -a source
No reverse dependencies found
$
Removing packages from mantic:
nvidia-graphics-drivers-418-server 418.226.00-0ubuntu5 in
Removing packages from mantic:
nvidia-graphics-drivers-440-server 440.95.01-0ubuntu2 in mantic
Comment: EOL, obsolete source package; LP: #2035189
1 package successfully removed.
** Changed in: nvidia-graphics-drivers-440-server (Ubuntu)
Status: Confirmed => Fix Released
--
You r
The reason for adding bumblebee is that Recommends and alternative
Depends on removed packages can cause them to be retained on end user
systems after upgrade. Better to remove the references than to try to
work out if nvidia would manage to not be affected.
--
You received this bug notification
Ok, on the correct package reverse-depends now shows:
$ reverse-depends src:nvidia-graphics-drivers-450-server
Reverse-Depends
===
* libnvidia-decode-440-server (for libnvidia-decode-450-server)
* libnvidia-encode-440-server (for libnvidia-encode-450-server)
* libnvidia-fbc1-440-se
65 matches
Mail list logo
