** Also affects: linux-hwe-5.19 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-5.19 (Ubuntu)
Status: New => Fix Released
** Description changed:
[ Impact ]
gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder
Lake systems running
The kernel is only seeing the built-in display as "connected":
/sys/class/drm/card0-DP-1/status:disconnected
/sys/class/drm/card0-DP-2/status:disconnected
/sys/class/drm/card0-eDP-1/status:connected
If we assume one of those DP ports is actually the HDMI port then the
problem would be a
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1989044
Title:
Verified against thermald-2.4.9-1ubuntu0.3,
~~~
LP#2018275,
LP#2018236,
LP#2012260,
LP#2007579,
LP#1989044,
LP#1981087
~~~
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1995606
Title:
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1995606
Title:
** Tags added: originate-from-2012475 somerville
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1995606
Title:
Upgrade thermald to 2.5.1 for Jammy (22.04)
Status in OEM Priority
** No longer affects: mutter (Ubuntu Jammy)
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided
@ Kai-Heng NOT THAT I'M AWARE OF
(Why I booted the various ISOs (20.04.5 with 5.15, 22.04.2 with 5.19,
and 23.04 with 6.2) under the same settings which had wifi..)
IF the WLAN/RF_KILL can be toggled with a keyboard combination & I
accidentally hit that, that for sure is possible as the
When it wasn't working:
[4.500054] iwlwifi :01:00.0: RF_KILL bit toggled to disable radio.
Does the system have any hardware rfkill button/switch?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Please install later kernel by issuing `sudo apt install linux-generic-
hwe-20.04` and reboot.
--
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/2016388
Title:
Kernel Panic on shutdown /
** Changed in: linux-gcp (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2020319
Title:
Encountering an issue with
Public bug reported:
It occurs on start up[
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libnvidia-compute-535-server 535.54.03-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-46-generic x86_64
NonfreeKernelModules:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2027744
Title:
package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to
install/upgrade:
Public bug reported:
Crash report appeared on my screen.
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-25-generic 6.2.0-25.25
ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12
Uname: Linux 6.2.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
doesn't apply to iotg or tegra kernels
** Tags removed: verification-needed-focal verification-needed-jammy
** Tags added: verification-done-focal verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux-azure (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2027615
Title:
Azure: MANA: Fix doorbell
** Changed in: linux-azure (Ubuntu Lunar)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2027615
Title:
Azure: MANA: Fix doorbell
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-gcp (Ubuntu)
Status: New => Invalid
** Changed in: linux-gcp (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-gcp (Ubuntu Jammy)
Importance: Undecided => Medium
And I also cannot log in here:
https://discourse.ubuntu.com
--
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/2027567
Title:
No more HDMI
Status in linux package in Ubuntu:
New
Bug
I wanted to correct the wiki by updating the PPA here:
https://wiki.ubuntu.com/Kernel/FAQ
But when I try to login to the wiki using Ubuntu One it says invalid
email/password combination.
But it is exactly the same email/password combination that I use for
launchpad.net.
Is the wiki limited to
I am experiencing a similar issue on ThinkPad t460s
suspend works the majority of the time, but every few days, I will try
to wake up from suspend and get input/output errors on everything. I am
able to wake the machine and log in, but can't do anything from there
but force a restart from the
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in Ubuntu.
https://bugs.launchpad.net/bugs/2022887
Title:
add Fintek F81604 can
> sudo apt install nvidia-driver-535 linux-modules-nvidia-535-generic
> sudo apt remove nvidia-dkms-535
Not changing anything!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
This bug is awaiting verification that the linux/5.4.0-155.172 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, change
This bug is awaiting verification that the linux/5.4.0-155.172 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, change
** Package changed: linux-nvidia-tegra (Ubuntu) => linux-nvidia-tegra-
igx (Ubuntu)
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-tegra in
** Tags removed: need-duplicate-check
--
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/2027708
Title:
package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to
install/upgrade:
Public bug reported:
was playing mount and blade got it work before but now its not working has me
confused got and error report finally with this info wondering If I broke it
somehow when I compiled drivers. If you don't mind taking a look I know its
silly to ask help for a proton windows
@kleber-souza do you have any reference for which kind of bugs were
resolved between 5.15.0-73-generic and 5.15.0-76.83 that might have
addressed this? Our testing indicates that the newer kernel version is
stable. It would be good to know what specifically caused this issue
--
You received this
Thx for the diff, xnox.
I've incl. it in the latest v2.28
and kicked off a PPA test build, available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp2020469
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
I can't add much in terms of data. But this is a +1. My symptoms were virtually
identical to Chad Wagner's
This happened july 1st 2023 on my machine, the day the check started. It got
stuck at 98%.
Only cure I could find was to reboot the system.
--
You received this bug notification because
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-gcp (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux-gcp (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux-gcp (Ubuntu Jammy)
Assignee: (unassigned)
** Description changed:
- [Summary]
+ [Impact]
+ add Fintek F81604 can controller support
- adds support for Fintek USB to 2CAN controller
+ [Test Plan]
+ 1. compile test.
+ 2. check f81604 can controller functionalities on the hardware.
+ 3. test kernel is provided to the customer.
+
+
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1981087
Title:
thermald prematurely throttling GPU
Status in
I'm setting the importance to Critical per #6 at
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
** Changed in: mutter (Ubuntu Jammy)
Importance: High => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg
** Tags added: s390x
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2020469
Title:
Package
It seems like NVIDIA Driver metapackage 535 leads to kernel panics in my
case while NVIDIA Driver metapackage 525 works fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2025538
Title:
** Description changed:
[ Impact ]
gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder
Lake systems running older kernels such as 5.15.
[ Test Plan ]
Try to log into gnome-shell. Verify there is a picture on the screen.
[ Where problems could occur ]
Fix proposed: https://salsa.debian.org/gnome-
team/mutter/-/merge_requests/100
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in Ubuntu.
https://bugs.launchpad.net/bugs/2026887
Title:
gnome-shell 42.9 Wayland sessions
** Changed in: linux (Ubuntu)
Status: New => 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/2027645
Title:
[Lenovo Legion 5] Brightness option is not working and not
Verified with unigine-super of phoronix-test-suite
~~~
$phoronix-test-suite benchmark unigine-super
~~~
didn't observe the significant difference compared to upstream thermald 2.5.3.
~~~
- thermald-2.4.9_1ubuntu-0.3
>
>
>
> Unigine Superposition 1.0:
>
See also: bug 1899626, bug 1944094, bug 1995173
** Summary changed:
- britness option is not working and not showing in system menu
+ [Lenovo Legion 5] Brightness option is not working and not showing in system
menu
** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)
** Changed in:
This bug is awaiting verification that the linux/5.15.0-79.86 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' to 'verification-done-jammy'. If the problem
still exists, change
This bug is awaiting verification that the linux/5.15.0-79.86 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' to 'verification-done-jammy'. If the problem
still exists, change
This bug is awaiting verification that the linux/5.15.0-79.86 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' to 'verification-done-jammy'. If the problem
still exists, change
This bug is awaiting verification that the linux/5.15.0-79.86 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' to 'verification-done-jammy'. If the problem
still exists, change
This bug is awaiting verification that the linux/5.15.0-79.86 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' to 'verification-done-jammy'. If the problem
still exists, change
** Description changed:
- Hi Ubuntu Team,
+ [ Impact ]
- MY ISSUE:
- I installed today my PC with Ubuntu IOT Desktop(22.04.2 LTS (Jammy
Jellyfish)).
- But with updated for all packages and with reboot PC, i have error with
starting gdm and access to /dev/dri/card0.
+ gnome-shell/mutter 42.9
Public bug reported:
When viewing
https://paris2024.sapsailing.com/gwt/RaceBoard.html?regattaName=OSG2024TEV2023+-+Men%27s+Windsurfing=iQFOiL+men+-+R4=OSG2024TEV2023+-+Men%27s+Windsurfing=83eb5c2a-d3ab-4e22-8422-1e4ab154ed34=b8220cee-9ec7-4640-b8d8-f40e079456d5=FULL_ANALYSIS
syslog is flooded
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas:
This bug was fixed in the package linux-aws-6.2 - 6.2.0-1007.7~22.04.1
---
linux-aws-6.2 (6.2.0-1007.7~22.04.1) jammy; urgency=medium
* jammy/linux-aws-6.2: 6.2.0-1007.7~22.04.1 -proposed tracker (LP:
#2026280)
* Revert variable symbol length modversion in all the jammy kernels
This bug was fixed in the package linux-azure-6.2 - 6.2.0-1007.7~22.04.1
---
linux-azure-6.2 (6.2.0-1007.7~22.04.1) jammy; urgency=medium
* jammy/linux-azure-6.2: 6.2.0-1007.7~22.04.1 -proposed tracker (LP:
#2026281)
* Revert variable symbol length modversion in all the jammy
It's a regression introduced in mutter 42.9 by Intel:
https://gitlab.gnome.org/GNOME/mutter/-/commit/1fd96e30f5f8a61d70d51f9012112e01818161a7
Although they would probably argue it's not a regression so long as you
have a new enough kernel. Since we don't always have a new enough kernel
in jammy
Nevermind. This bug is affecting regular Ubuntu Desktop too, for those
running the original 22.04 release. It shouldn't happen if you're using
22.04.2 though because that has a new enough kernel to support the
hardware, in theory.
** Also affects: mutter (Ubuntu)
Importance: Undecided
Suggested workarounds:
* Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment
* sudo apt install linux-generic-hwe-22.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in Ubuntu.
Cannot reproduce this on any recent MAAS.
--
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/1797581
Title:
Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
kernel panic
** Changed in: maas
Status: Incomplete => Invalid
--
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/1797581
Title:
Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-intel-iotg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in Ubuntu.
** Summary changed:
- [intel] gnome-shell Wayland sessions fail to start on intel-iotg kernels
(Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
failed: Invalid argument)
+ [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels
(Failed to lock
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Kinetic)
Status: New => Won't Fix
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed
** Tags removed: verification-needed-focal verification-needed-jammy
** Tags added: verification-done-focal verification-done-jammy
--
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/2019131
69 matches
Mail list logo
