Any kernel 6.3 will do, so long as you're still using libmutter >= 45.0
--
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/2033735
Title:
[mantic] New 6.5.0.2 kernel + Intel GPU = no HDMI
Also are you sure it's a kernel issue and 6.3 *still* works?
I fixed a bug in mutter this week that would have previously kept the
discrete GPU awake even when it wasn't being used. That was a bug
though.
--
You received this bug notification because you are a member of Kernel
Packages, which
Can you explain what "on-demand" is and where it's set?
** Changed in: linux (Ubuntu)
Status: Opinion => 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/2033735
Title:
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3037
https://gitlab.gnome.org/GNOME/mutter/-/issues/3037
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/3037
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Yes I was referring to the linux task.
--
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/1965303
Title:
Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
Status in
I don't think this is a bug. When the Nvidia GPU is disabled it is
expected that the ports wired to it will also be disabled.
** Changed in: linux (Ubuntu)
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Tags added: amdgpu
** Summary changed:
- Xorg freeze
+ [amdgpu] Oops in dm_helpers_dp_mst_send_payload_allocation+0x90/0xd0 [amdgpu]
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
** Summary changed:
- [amdgpu] Oops in dm_helpers_dp_mst_send_payload_allocation+0x90/0xd0
** Summary changed:
- package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso
instalado paquete bluez script post-installation devolvió el código de salida
de error 1
+ package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso
instalado paquete bluez script
This seems like a significant enhancement that will affect the graphics
backends chosen by Plymouth and some desktop sessions, particularly
virtual machines. Surely this needs a feature freeze exception?
--
You received this bug notification because you are a member of Kernel
Packages, which is
Vincent, please log your own bug by running:
ubuntu-bug linux
--
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/2025079
Title:
[amdgpu] Multiple kernel errors and reboot
Status in
It looks like the Intel GPU exists but is disabled. And that both the
laptop screen and the external monitor are wired to the Nvidia GPU...
unless you have more than one external monitor attached?
--
You received this bug notification because you are a member of Kernel
Packages, which is
That's correct, it silently produces a text file. Please attach that
text file here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2036802
Title:
HDMI not detected on HP Zbook
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** No longer affects: nvidia-graphics-drivers-525 (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: Triaged => In Progress
** Changed in: mutter (Ubuntu)
Importance: High => Medium
--
You
Usually external monitor ports are wired to the discrete GPU. So that
would make it an Nvidia problem, not an Intel kernel problem...
Please run:
grep . /sys/class/drm/*/status > connections.txt
and attach the resulting text file here.
** Changed in: linux-hwe-6.2 (Ubuntu)
Status:
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2036802
Title:
HDMI not detected on HP Zbook Power 15 G9
Status in
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2861
https://gitlab.freedesktop.org/drm/amd/-/issues/2861
** Also affects: linux via
https://gitlab.freedesktop.org/drm/amd/-/issues/2861
Importance: Unknown
Status: Unknown
** Changed in: mutter (Ubuntu)
Importance:
Yes I think it's the "pipewire" package that owns Bluetooth audio now. A
new bug please.
--
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/2036428
Title:
Intel AX201 Bluetooth not
It looks like mutter is *asking* to be killed if any system calls take
too long:
setrlimit (RLIMIT_RTTIME...
and that only seems to happen on some Ryzen systems. Still, I'm not so
sure the default limit of 200ms (inherited from rtkit) is sensible if
the machine would otherwise recover. It's
Yeah I think the major kernel upgrade (or something around the same
time) caused one boot to be very slow.
--
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]
Workaround proposed:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3291
--
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
** Tags added: mantic
--
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/2036428
Title:
Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1
Status in
*** This bug is a duplicate of bug 2036428 ***
https://bugs.launchpad.net/bugs/2036428
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2036428, so it is being marked as such. Please
*** This bug is a duplicate of bug 2036428 ***
https://bugs.launchpad.net/bugs/2036428
Looks like kernel 6.5 is missing required firmware?
[ 38.846558] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 38.846638] Bluetooth: hci0: Failed to load Intel firmware file
** Changed in: xwayland (Ubuntu)
Status: Confirmed => Opinion
** No longer affects: xwayland (Ubuntu)
--
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]
** Also affects: xorg-server via
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1579
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: amdgpu
** Summary changed:
- gnome-shell gets SIGKILL'd when lock screen in Wayland
+ [amdgpu gnome-shell gets SIGKILL'd when lock screen in Wayland
** Summary changed:
- [amdgpu gnome-shell gets SIGKILL'd when lock screen in Wayland
+ [amdgpu] gnome-shell gets SIGKILL'd when
** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: New => Triaged
** Changed in:
*** This bug is a duplicate of bug 1876632 ***
https://bugs.launchpad.net/bugs/1876632
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1876632, so it is being marked as such. Please
Public bug reported:
Update to BlueZ 5.69 (or later) in Ubuntu 24.04
** Affects: bluez (Ubuntu)
Importance: Medium
Assignee: Daniel van Vugt (vanvugt)
Status: Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
*** This bug is a duplicate of bug 1965303 ***
https://bugs.launchpad.net/bugs/1965303
** This bug has been marked a duplicate of bug 1965303
Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
--
You received this bug notification because you are a member of Kernel
The affected releases are EOL, plus I don't use DVI anymore.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
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/859389
I haven't seen this issue in years and the affected releases are EOL
anyway.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This machine has been retired.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
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/1959652
Title:
[regression] Jammy
Kernel 6.5 seems to be working so far...
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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/2025120
Title:
Crash in
The data in comment #1 shows only two "VGA" controllers that could be
used:
46:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED
Graphics Family [1a03:2000] (rev 41) (prog-if 00 [VGA controller])
c1:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU117GLM [Quadro
** Summary changed:
- Screen blank crashes system
+ [Google_Puff] Screen blank crashes system
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Also if the leftover startup image is when KDE should be displaying then
you should log that as a bug against KDE or Kwin.
--
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/2035192
Title:
This sounds like a consequence of a common problem with Intel graphics
-- the kernel occasionally misdetects the screen resolution.
It's not a big deal if only the startup animations are affected but let
us know if you have similar problems on the desktop (such as when
resuming from sleep).
**
Removed the kernel task because there's no evidence yet the qxl driver
is doing anything wrong.
I might attempt a Plymouth fix for bug 1869655 and this before 23.10 but
that wouldn't be without risks.
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a
It looks like kernel 5.15 is only working because there's no graphics
driver there that supports the GPU. So it's defaulting to legacy
software rendering which kind of works... You can do the same in kernel
6.2 by using the kernel parameter "nomodeset".
** Package changed: xorg (Ubuntu) =>
It sounds like the main problem therefore is the Nvidia X driver. It's
refusing to light up HDMI without a custom config explicitly telling it
to use "PCI:193:0:0". But this might be Nvidia's intended behaviour so I
recommend checking the docs for solutions first:
** Package changed: gdm (Ubuntu Jammy) => gdm3 (Ubuntu 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/1965303
Title:
Migrate from fbdev drivers to simpledrm and DRM fbdev
> I can't collect logs because when I do ... the issue is gone
This supports the theory that it's a Plymouth race condition, fixed by
booting more slowly. Plymouth might be wanting to display the password
prompt before graphics support has "booted" in the kernel.
Actually now that I've said that
Sorry it looks like I was completely wrong. qxl *does* support the
preferred "modern" DRM/KMS graphics interface as shown in your log
files. This seems to be some kind of qxl kernel bug or maybe Plymouth
race condition.
I can only suggest collecting more Plymouth debug logs until the bug
happens
** Changed in: nvidia-graphics-drivers-530 (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-530 in Ubuntu.
https://bugs.launchpad.net/bugs/2025585
Title:
Nvidia 530 kernel
Thanks but I meant collecting drm_info while the bug was still
happening. It's good that it seems to be working now.
If the problem reoccurs in future then most likely it's a combination of
a hardware and kernel problem whereby the kernel can only detect support
for 30Hz when waking up. So if it
I take it that's a "Won't Fix" for 5.19 because it's superseded by 6.2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2033016
Title:
Dell S3222DGM Monitor and Intel Xe Graphics
*** This bug is a duplicate of bug 1875756 ***
https://bugs.launchpad.net/bugs/1875756
** This bug has been marked a duplicate of bug 1875756
Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Wi-Fi not enabled
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1875756 ***
https://bugs.launchpad.net/bugs/1875756
** This bug has been marked a duplicate of bug 1875756
Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Wi-Fi not enabled
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1875756 ***
https://bugs.launchpad.net/bugs/1875756
** This bug has been marked a duplicate of bug 1875756
Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Wi-Fi not enabled
--
You received this bug notification because you are a member of
Ubuntu 18.04 is no longer supported but see also bug 1875756.
** Changed in: linux-signed-hwe (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe in Ubuntu.
** Tags added: lunar
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
--
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/1875756
Title:
Qualcomm Atheros
*** This bug is a duplicate of bug 1875756 ***
https://bugs.launchpad.net/bugs/1875756
** This bug has been marked a duplicate of bug 1875756
Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Wi-Fi not enabled
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1875756 ***
https://bugs.launchpad.net/bugs/1875756
** This bug has been marked a duplicate of bug 1875756
Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Wi-Fi not enabled
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1875756 ***
https://bugs.launchpad.net/bugs/1875756
** This bug has been marked a duplicate of bug 1875756
Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Wi-Fi not enabled
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1875756 ***
https://bugs.launchpad.net/bugs/1875756
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1875756, so it is being marked as such. Please
*** This bug is a duplicate of bug 1875756 ***
https://bugs.launchpad.net/bugs/1875756
** This bug has been marked a duplicate of bug 1875756
Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Wi-Fi not enabled
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1875756 ***
https://bugs.launchpad.net/bugs/1875756
** This bug has been marked a duplicate of bug 1880639
Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] - Wi-fi
automatically disconnecting
** This bug is no longer a duplicate of bug 1880639
*** This bug is a duplicate of bug 1875756 ***
https://bugs.launchpad.net/bugs/1875756
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Your logs are full of errors from the ath10k_pci and r8169 kernel
drivers, so this is a kernel bug (or a hardware fault).
** Summary changed:
- Not able to see visible devices when wifi is turned on please verify.
+ [ath10k_pci] Not able to see visible devices when wifi is turned on please
*** This bug is a duplicate of bug 1682322 ***
https://bugs.launchpad.net/bugs/1682322
Actually we should merge this into bug 1682322.
** This bug has been marked a duplicate of bug 1682322
PCI/internal sound card not detected dummy drive only on Dell Inspiron 5567
--
You received this
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing
*** This bug is a duplicate of bug 1682322 ***
https://bugs.launchpad.net/bugs/1682322
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
See this document for currently supported Ubuntu releases:
I know but please open a second bug about networking.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2033229
Title:
[Dell Inspiron 5567] Touchpad stops responding
Status in
Please open a separate bug about networking/wifi.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2033229
Title:
[Dell Inspiron 5567] Touchpad stops responding
Status in
Wayland should be enabled already. It will only get hidden on each boot
if something crashed when trying to start it.
Also check that you haven't accidentally disabled it in
/etc/gdm3/custom.conf when you said you enabled it.
--
You received this bug notification because you are a member of
Thanks. This suggests a crash occurred when trying to launch with
Wayland and that option was removed automatically. So please open a
separate bug about the Wayland option being missing.
** Summary changed:
- Cursor stops moving but using peripherals it works
+ [Dell Inspiron 5567] Cursor stops
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 2028187
When reporting bugs in the future please use apport by using 'ubuntu-
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2026887
Title:
gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or
later if
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2026887
Title:
gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or
later if
*** This bug is a duplicate of bug 2026887 ***
https://bugs.launchpad.net/bugs/2026887
No that seems to be a different kernel issue if the flood of log
messages is anything to go by:
Jul 21 10:21:09 jcapc196 kernel: i915 :00:02.0: [drm] *ERROR* Fault errors
on pipe A: 0x0080
Jul 21
I think this sounds like it could still be a common bug to both mutter
and kwin so let's keep that open. Certainly the circumstances agree with
the error message and it sounds logical to me that the compositor could
be to blame.
** Also affects: kwin (Ubuntu)
Importance: Undecided
** Also affects: linux-hwe-6.2 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-6.2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
*** This bug is a duplicate of bug 1958191 ***
https://bugs.launchpad.net/bugs/1958191
Since you're the author of the original bug, the symptoms are identical
and it's a different source package now, we can reuse bug 1958191.
** This bug has been marked a duplicate of bug 1958191
[i915]
See also bug 2028199.
--
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/2023585
Title:
[nvidia] GPU has fallen off the bus
Status in linux package in Ubuntu:
Incomplete
Status in
It sounds like you've hit the problem Nvidia mentions in their
documentation:
http://us.download.nvidia.com/XFree86/Linux-x86_64/535.54.03/README/egpu.html
so I guess falling off the bus is just as bad as being unplugged.
Can you provide logs mentioning falling off the bus? I only recall a
** Tags added: amdgpu resume suspend-resume
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
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/2028193
Title:
Machine doesn't resume
** Tags removed: kinetic
** Tags added: lunar mantic
** Summary changed:
- bluetoothd crashed with SIGSEGV in avdtp_stream_set_transport transport_cb
accept_cb g_main_dispatch g_main_context_dispatch
+ bluetoothd crashed with SIGSEGV in avdtp_stream_set_transport() from
transport_cb() from
Thanks for the bug report. When the problem is happening, please open a
terminal and run:
journalctl -b0 > journal.txt
lspci -k > lspci.txt
dconf dump /org/gnome/shell/ > shellsettings.txt
and attach the resulting text files here. If you couldn't run those
while the problem is happening
*** This bug is a duplicate of bug 2026887 ***
https://bugs.launchpad.net/bugs/2026887
When the bug is happening just switch to a VT (like Ctrl+Alt+F4) and
run:
journalctl -b0 > journal.txt
then attach the resulting text file here.
To add to /etc/environment you need to edit the file as
*** This bug is a duplicate of bug 2026887 ***
https://bugs.launchpad.net/bugs/2026887
Actually I'm just assuming it's that bug. I can't see enough of your
logs to confirm. But you might like to try one of the workarounds:
* Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment
* Upgrade
** Summary changed:
- gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running
5.15 kernels (Failed to lock front buffer on /dev/dri/cardN:
drmModeAddFB2WithModifiers failed: Invalid argument)
+ gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if
This bug might be one of the issues fixed in 535.86.05:
> Fixed a bug that prevented displays from refreshing when using an
NVIDIA PRIME Display Offload sink.
But it's not available in Ubuntu yet.
** No longer affects: xorg-server (Ubuntu)
--
You received this bug notification because you are
The changelog needs fixing per comment #12.
** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
** Tags added: block-proposed
--
You received this bug notification because you
** Summary changed:
- screen rotates automatically by 90° when physical keyboard is disconnected
from tablet
+ [Chuwi Hi10 X tablet] screen rotates automatically by 90° when physical
keyboard is disconnected from tablet
** Package changed: xorg (Ubuntu) => linux-hwe-5.19 (Ubuntu)
** Also
*** This bug is a duplicate of bug 2026887 ***
https://bugs.launchpad.net/bugs/2026887
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2026887, so it is being marked as such. Please
Mike, please open a new bug by running:
ubuntu-bug linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1973827
Title:
Laptop freezes when recovering from suspend / sleep mode
Yes it's on my todo list.
--
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/2025120
Title:
Crash in 6.3.0-7 (ucsi_acpi_async_write [ucsi_acpi]) prevents booting,
while 6.2.0-21 always
It appears the nvidia driver doesn't support kernel 6.5 yet. This isn't
really an Ubuntu bug since Ubuntu doesn't support it officially yet
either.
nv-mm.h:88:16: error: too many arguments to function
‘get_user_pages’
** Changed in: nvidia-graphics-drivers-525 (Ubuntu)
Status: New =>
** Changed in: linux-hwe-5.15 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1983108
Title:
[nouveau] watchdog: BUG: soft lockup -
** Project changed: bluetooth => ubuntu
** No longer affects: ubuntu
--
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/1189721
Title:
Ralink RT3290 doesn't have a bluetooth driver
Status
I think "This was a regression introduced by Intel in 42.9!" should be
removed from the changelog. It's not something I wrote in the patch or
in the merge proposal.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in
That is unusual if even the 6.2 and 6.4 kernels can't find the HDMI
port. At this stage I would usually recommend a BIOS update but it seems
you already have the latest BIOS from Asus.
Since the kernel does seem to know about two DisplayPorts (presumably
USB-C), I would recommend finding a USB-C
Also your mesa graphics packages don't look like they are from Ubuntu.
Where are those from?
23.2.0.20230414.1+2061~u22.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
Thanks for the bug report. When the second monitor is plugged in, please
run:
sudo apt install drm-info
drm_info > drminfo.txt
grep . /sys/class/drm/*/status > connections.txt
journalctl -b0 > journal.txt
and attach the resulting text file here.
Please also clarify if you are using a
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
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
You might want to try kernel parameter 'acpi_backlight=vendor' which I was
reminded of by:
https://wiki.ubuntu.com/Kernel/Debugging/Backlight
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** 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
401 - 500 of 6827 matches
Mail list logo
