** Also affects: linux (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/2064275
Title:
Blank screen after logging in Wayland using HP
I'm not sure you even need to undo the changes in /etc/default/grub and
etc/environment if the bug is still happening. But sure...
--
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/2063228
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Importance: Undecided => Medium
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Status: Incomplete => Triaged
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-control-center
Sounds like we're correct in assigning this to the kernel then.
Next please try some older kernels to identify when the problem started:
https://kernel.ubuntu.com/mainline/?C=M;O=D
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
Release BlueZ 5.75 to Oracular:
https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.75.tar.xz
** Affects: bluez (Ubuntu)
Importance: Medium
Assignee: Daniel van Vugt (vanvugt)
Status: Triaged
** Tags: oracular
** Changed in: bluez (Ubuntu
The xrandr output looks correct but the attached MonitorsUser.xml.txt
looks suspicious in that it confirms the monitors don't have any
separate positional information. If deleting monitors.xml didn't work
then next please try:
1. sudo rm /dev/dri/card0 # (should be the "Unknown Display")
2. rm
Did you log in again after deleting the file?
Is one of the two different names "Unknown Display"?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/2064196
Title:
Are you sure Settings is showing both Iiyama and Philips or is it
perhaps showing one of them twice? (bug 2060268)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
If you delete ~/.config/monitors.xml and log in again, can you configure
the monitors correctly after that?
** Tags added: multimonitor nvidia
** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Status: New =>
I wonder if this is due to bug 2060268...
** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu)
** Also affects: nvidia-graphics-drivers-470 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages,
** 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/2062950
Title:
RE: Flickering problems on external monitor with HDMI after
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Tags added: flicker
--
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/2064017
Title:
Xserver Display flickers when mouse
Please try adding this to /etc/environment:
MUTTER_DEBUG_FORCE_KMS_MODE=simple
and then 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/2063228
Title:
screen sometimes
*** This bug is a duplicate of bug 2028165 ***
https://bugs.launchpad.net/bugs/2028165
Okay, I can confirm that the 390 driver is causing boot issues on 24.04, both
laptop and desktop.
I've removed the Noble package from the PPA for now because I don't want to
break anyone else's shiny new
*** This bug is a duplicate of bug 2028165 ***
https://bugs.launchpad.net/bugs/2028165
@Ginés: Thanks for the feedback. Are you using a laptop or desktop? I've gotten
a few reports of black screens this week on 24.04
I guess I'll have to pull out the old GTX950 and try to troubleshoot it :(
*** This bug is a duplicate of bug 2028165 ***
https://bugs.launchpad.net/bugs/2028165
@Ginés: Theoretically, it should. I made a package for Noble/24.04 in the PPA
and it seemed to build/install correctly in my Xubuntu 24.04 VM
Keep in mind that the only Nvidia card I own is sitting in my
Please try adding kernel parameter:
i915.enable_psr=0
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** 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.
After editing /etc/default/grub, please also run:
sudo update-grub
and then 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/2063228
Title:
screen sometimes blinking
Status
Please try adding this to /etc/environment:
MUTTER_DEBUG_FORCE_KMS_MODE=simple
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/2062950
Title:
RE: Flickering problems on
** Description changed:
[ Impact ]
When the Nvidia 470 driver is used GTK 4 fails to render most text
labels.
[ Workaround ]
Install a newer Nvidia driver using the 'Additional Drivers' app if you
- can. Otherwise add GSK_RENDERER=gl to /etc/environment and reboot.
+ can.
*** This bug is a duplicate of bug 2061079 ***
https://bugs.launchpad.net/bugs/2061079
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 2061079, so it is being marked as such. Please
Thank you for reporting this bug to Ubuntu.
Ubuntu 23.04 (lunar) reached end-of-life on January 25, 2024.
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 it anymore.
Plymouth not displaying anything is covered by bug 1869655 already so
please try kernel parameter:
plymouth.use-simpledrm
which should solve that.
** Changed in: plymouth (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-550
(Ubuntu)
** Also affects: nvidia-graphics-drivers-545 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Not having a monitors.xml is fine. I was only concerned about the
possibility of monitors.xml containing bad data.
What if you choose 'Ubuntu on Xorg' on the login screen (menu in the
bottom right corner). Does that prevent the bug from occurring?
--
You received this bug notification because
Please try adding a kernel parameter:
i915.enable_psr=0
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Plymouth seems to be running, but also terminating within a couple of
seconds. Since it's designed to not display anything if it thinks it
won't run for very long then I think failing to see a Plymouth boot logo
is OK in this case. You might like to try the workaround for bug 1869655
which is to
Thanks. I don't see any errors relevant to this bug, only bug 2034664
(which you should have the fix for already?) and bug 1857392.
Next please try deleting the monitor layout settings:
rm ~/.config/monitors.xml
and then log in again. Does that improve the situation?
--
You received this
** Summary changed:
- Phantom monitor (simpledrm) shown in Settings after installing the Nvidia
driver
+ Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
** Description changed:
+ [ Impact ]
+
After installing Nvidia driver 545 on a single (27") monitor system,
*** This bug is a duplicate of bug 2060268 ***
https://bugs.launchpad.net/bugs/2060268
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 2060268, so it is being marked as such. Please
Next time you have a failed boot followed by a successful boot, please
run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Tags added: amdgpu
Also, are there any files in /var/crash ?
--
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/2063143
Title:
Frequent boot to black display
Status in linux package in Ubuntu:
Incomplete
Nelle,
Seems no one else is experiencing the issue I described above, so it's
probably a me problem. I will do more troubleshooting on my end. Thanks
for sharing your results.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Thanks. It was unclear from the first bug which monitor was flickering.
In the first bug it sounded like the laptop. In this second bug it
sounded like the external monitor. Now the video shows it's the laptop
screen.
Is it only the laptop screen flickering?
I'm wondering if this is due to a
Please run:
alsa-info
and attach the text file it creates.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is
Thanks for the bug report. Most likely the problem is an HDMI connection
problem. Please try a new HDMI cable if you can. If you can't then
please try temporarily running the external monitor at a lower
resolution to see if the flicker then goes away.
If the flicker still persists then please
** Tags added: jammy
--
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/2062534
Title:
GDM3 autologin might be racy on GCP resulting in inconsistent state of
the wayland setup of
Hi, I believe that kernel 5.15.0-105-generic may not have have solved
the issue entirely.
I upgraded to 104 from -proposed, and then when 105 was available, I
updated to 105, and then removed 104 and the -proposed repo entirely.
While, the issue does not present itself as frequently, I still
Here's a workaround/fix.
** Patch added: "nvidia-graphics-drivers-470_470.239.06-0ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2061079/+attachment/5767391/+files/nvidia-graphics-drivers-470_470.239.06-0ubuntu3.debdiff
--
You received this bug notification because you
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Status: Won't Fix => In Progress
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Importance: Undecided =
If you're careful you can just delete /dev/dri/card0 to work around it
:)
** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification
*** This bug is a duplicate of bug 2060268 ***
https://bugs.launchpad.net/bugs/2060268
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 2060268, so it is being marked as such. Please
** Changed in: gtk4 (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/2061079
Title:
GTK-ngl (new default backend) rendering
I'm guessing this might also be the cause of the oversized panning login
screen I get with Nvidia 470?
** Also affects: nvidia-graphics-drivers-470 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Also affects: nvidia-graphics-drivers-550 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-550 (Ubuntu)
Status: New => Fix Released
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: Invalid => Fix Released
** Changed in:
** Summary changed:
- GTK-ngl (new default backend) rendering issues with the nvidia driver
+ GTK-ngl (new default backend) rendering issues with the nvidia 470 driver
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Confirmed on Nvidia 470. The newer drivers 535 and 545 however do not
have the bug. I couldn't test 550 due to bug 2061738.
Please also be aware of bug 2059847.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470
Public bug reported:
Nvidia driver 550 fails to install any kernel module on Noble.
I've tried installing it multiple times through 'Additional Drivers' and
on the command line. The nvidia 550 packages install successfully but no
kernel module is installed.
This problem does NOT occur with 470,
** Also affects: nvidia-graphics-drivers-545 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: gtk4 (Ubuntu Noble)
** No longer affects: nvidia-graphics-drivers-545 (Ubuntu Noble)
** Changed in: nvidia-graphics-drivers-545 (Ubuntu)
Status: New => Invalid
** Also
** Also affects: nvidia-graphics-drivers-550 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-550 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
"Input/output error" suggests there's a disk problem but I suppose such
an error could occur in any kernel driver.
Next time the error pops up, please run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Package changed: xorg-server (Ubuntu) => linux (Ubuntu)
**
Thank you for reporting this bug to Ubuntu.
Ubuntu 23.04 (lunar) reached end-of-life on January 25, 2024.
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 it anymore.
** Tags added: noble
** Summary changed:
- Desktop environment fails to start
+ [nouveau] Xorg desktop environment fails to start with QEMU GPU passthrough
to NVIDIA
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
*** This bug is a duplicate of bug 2028165 ***
https://bugs.launchpad.net/bugs/2028165
Jonathan, either use the PPA in the bug description or use the "GA"
kernel (5.15.x). They're not going to fix this and the 6.2 kernel series
is EOL, so it's not wise to keep running that.
I've installed the 20240410 iso on a couple of machines and this bug is
as good as fixed.
The systemd task would be nice to complete but that's more for the sake
of bug 1914409. Right now I have more important bugs to focus on...
** Changed in: systemd (Ubuntu)
Status: In Progress =>
I didn't expect it to go that smoothly :D
Yes a bug should be logged against the DDX in that case. I don't know
where the code came from; maybe use https://github.com/Xilinx/mali-
userspace-binaries/issues/ ?
--
You received this bug notification because you are a member of Kernel
Packages,
Any message with (WW) or (EE) means you're still using Xorg, not
Wayland.
Switching a Xilinx system to Wayland used to be a manual process as
mentioned in bug 1961563. I was just hoping it had been simplified since
then. I don't know because I had to return the hardware before Wayland
support
Looks like the same problem. Either a bug in the DDX driver "ARMSOC", or
a bug in the kernel driver "xlnx". To figure out which I can only
recommend you try Wayland instead. Because if it's a kernel bug then
Wayland will display similar errors.
P.S. I no longer have the hardware to test.
--
You
** Summary changed:
- [nvidia] Corrupted/missing shell textures when switching users or resuming
from suspend
+ [nvidia] Corrupted/missing shell textures when switching users, switching VTs
or resuming from suspend
--
You received this bug notification because you are a member of Kernel
** Package changed: ubuntu => linux-xilinx-zynqmp (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu.
https://bugs.launchpad.net/bugs/2060458
Title:
ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed
Also bug 2060555.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/205
Title:
[RTL8822CE] i could not able to connect my bluetooth headphone or for
context any headphone to my
See also bug 205 having trouble with the same chip.
** Also affects: linux-hwe-6.5 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-6.5 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages,
Please reboot, try to connect them again, and after it fails run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
Please also specify how long ago and in which Ubuntu release it was
working.
** Summary changed:
- I cant connect my bluetooth keyboard, mouse and jbl
** Summary changed:
- Horizonral line artifact/ghosting when scaling windows to a certain width
+ [Intel N95] Horizonral line artifact/ghosting when scaling windows to a
certain width
** Package changed: xorg (Ubuntu) => mesa (Ubuntu)
** Package changed: mesa (Ubuntu) => linux (Ubuntu)
**
There's probably nothing to do in the kernel task here.
--
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/2060268
Title:
Phantom 46" monitor (simpledrm) shown in Settings after installing
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761623/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
no bluetooth detected
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761624/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761626/+files/acpidump.txt
** Also affects: nvidia-graphics-drivers-545 (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Phantom 46" monitor after
Public bug reported:
After installing Nvidia driver 545 on a single (27") monitor system,
Settings shows a phantom 46" monitor of the same resolution.
It looks like the phantom monitor is /dev/dri/card0 which is still controlled
by simpledrm, while Nvidia uses /dev/dri/card1.
---
ProblemType:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761621/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761615/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761613/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761612/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761616/+files/Lsusb.txt
--
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/2060268
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761625/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761614/+files/Lspci.txt
--
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/2060268
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761617/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761622/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It looks like i915 avoids this by deleting /dev/dri/card0 (simpledrm)
after /dev/dri/card1 (i915) exists. Although I don't really know exactly
where that's implemented.
** Summary changed:
- Phantom 46" monitor (simpledrm) after installing the Nvidia driver
+ Phantom 46" monitor (simpledrm)
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761620/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761611/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761619/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2060268/+attachment/5761618/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Sorry, but I don't believe that for a second. The fix is not difficult
or time-consuming, and they already had a patched version.
"Eventually 6.5+ based jammy kernels will not have it in lrm either. And we
will only keep it against older kernels in bionic..jammy (ga only)"
Unless they reverse
** Summary changed:
- Bluetooth earbuds not being 'set up' on new machine
+ T60 Bluetooth earbuds not being 'set up' on new machine
** Changed in: bluez (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is
Everyone is very busy with the 24.04 release as well as other
responsibilities. So don't take silence to imply anything :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
@vanvugt: I appreciate you opening the Jammy task, but I'm not holding my
breath for this to get fixed after reading
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2035189/comments/1
Basically, they knew this bug was coming when they removed the 390 package, but
they
It seems a few different manufacturers have products called 'T60' so
please mention the brand in the bug title.
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
I don't think the "simpledrm" reason listed in 2035189 holds up. Unless
you're in a virtual machine, SimpleDRM is only used for the few seconds
of initrd, or for the duration of the disk unlock prompt. Even if old
Nvidia drivers can't support SimpleDRM, they can support legacy
framebuffers which
It's not bug 2049927 because that's amdgpu and this is i915.
** This bug is no longer a duplicate of bug 2049927
[amdgpu] since Linux kernel 6.5.0-14 external monitors are no longer detected
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Summary changed:
- since Linux kernel 6.5.0-14 external monitors are no longer detected
+ [amdgpu] since Linux kernel 6.5.0-14 external monitors are no longer detected
** Tags added: amdgpu
--
You received this bug notification because you are a member of Kernel
Packages, which is
In case anyone is wondering, you won't start to see an improvement until
you have at least:
linux >= 6.8.0-20.20 and
plymouth >= 24.004.60-1ubuntu6
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Dmitry: Ubuntu devs made a conscious decision to drop the 390 driver and some
other branches:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2035189
So if they haven't fixed the Jammy version by now, it's probably not going to
happen.
Good news though: I patched
Public bug reported:
System hung indefinitely during a Software Update prompt. The update
related to audio. I had to hard restart the system.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-26-generic 6.5.0-26.26
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
** Tags removed: kinetic
** Tags added: mantic
** Tags added: fixed-in-linux-v6.9-rc1 fixed-upstream
** No longer affects: kwin (Ubuntu)
** No longer affects: mutter (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status:
*** This bug is a duplicate of bug 2003031 ***
https://bugs.launchpad.net/bugs/2003031
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 2003031, so it is being marked as such. Please
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Confirmed
** Summary changed:
- Kernel 6.8 -
Public bug reported:
I am trying to update ubuntu to 23.10 from 21.04 but it appears I have
both versions installed at the same partation at the same time...
Found Ubuntu 21.04 (21.04) on /dev/sda2
Adding boot menu entry for UEFI Firmware Settings ...
sudo do-release-upgrade
Checking for a new
** Changed in: linux (Ubuntu)
Status: Fix Committed => 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/1970069
Title:
Annoying boot messages interfering with splash
1 - 100 of 8794 matches
Mail list logo