Yes it's the kernel. Reverting to kernel 6.8 has fixed the performance
issue on 535. I am yet to test 6.8 with 560...
And it appears the missing information in NVIDIA Settings is still
missing, so that's unrelated to the performance regression.
** Summary changed:
- [regression] Very poor perfor
These results are weirdly consistent and repeatable across purges,
reinstalls and reboots:
SLOW: Nvidia-560 + Linux 6.8
SLOW: Nvidia-560 + Linux 6.11
SLOW: Nvidia-535 + Linux 6.11
FAST: Nvidia-535 + Linux 6.8
FAST: Nvidia-550 + Linux 6.11
I'm currently testing on a Turing card, if that's importan
GNOME 46.5 seems to have the same issue as 47.0 so I don't think it's a
Mutter regression.
** Changed in: mutter (Ubuntu)
Status: New => Invalid
** Summary changed:
- [regression] Very poor performance in Nvidia Wayland sessions with kernel 6.11
+ [regression] Very poor performance in Nvi
Same issue in 535. Is it the new kernel perhaps?
** Summary changed:
- Very poor performance in Nvidia-560 Wayland sessions
+ [regression] Very poor performance in Nvidia Wayland sessions
** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** Also a
** Changed in: linux-hwe-6.8 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2080498
Title:
Default session type changed from Xorg to Way
The fix has stopped working in Oracular kernel 6.11. Looks like the
reason is no '/sys/devices/platform/simple-framebuffer.0/drm/card0'
file.
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of K
Technically the fix in ubuntu-drivers-common (bug 2060268) isn't a fix
for this, but I expect it will provide a permanent workaround.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: nvidia-graphics-drivers-550 (Ubuntu)
Status: Confirmed => Invalid
** Als
The fix seems to be in 535.183.01-0ubuntu2 too.
** Changed in: nvidia-graphics-drivers-535 (Ubuntu Oracular)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubunt
Also that was using Wayland, not Xorg.
--
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/2080814
Title:
[nouveau] Screen freeze
Status in linux package in Ubuntu:
New
Bug description:
Assuming the bug is in journal-1.txt, it looks like the nouveau kernel
graphics driver that's crashing. To solve that I suggest installing an
official Nvidia driver from the 'Additional Drivers' app.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Summary changed:
- Xorg freeze
+ [nouvea
** Summary changed:
- Bluetoth turning off every reboot and i need to reinstall e restart the
modules everytime
+ [QCA9377] Bluetoth turning off every reboot and i need to reinstall e restart
the modules everytime
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
Please try adding this to /etc/environment:
MUTTER_DEBUG_KMS_THREAD_TYPE=user
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/2067657
Title:
Cursor response to touchpad sp
Does the session menu on the login screen list:
(a) Ubuntu, Ubuntu on Xorg
(b) Ubuntu, Ubuntu on Wayland
(c) Nothing, or no menu?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/208
Are there any crash files in /var/crash when the bug occurs?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2080498
Title:
Default session type changed from Xorg to Wayland in so
** Also affects: egl-wayland (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2080282
Title:
Apps run on the discrete Nvidia GPU
Please also try uninstalling libnvidia-egl-wayland1. If that forces the
removal of the Nvidia driver then you should be able to install an older
Nvidia driver from the archive that doesn't depend on libnvidia-egl-
wayland1.
If you find the bug is now fixed without libnvidia-egl-wayland1, try
reins
*** This bug is a duplicate of bug 2062951 ***
https://bugs.launchpad.net/bugs/2062951
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 2062951, so it is being marked as such. Please look
I think it's important for us to distinguish between the default session
in a new install (which is meant to be Wayland), and failing to choose
Xorg when Xorg was used in the previous login. The latter sounds like
more of a bug, and closer to what was initially reported here.
We'll need to zoom in
** Summary changed:
- Default session type changed from Xorg to Wayland in some new installs of
22.04 on Nvidia hybrids since kernel 6.8
+ Default session type changed from Xorg to Wayland in some installs of 22.04
on Nvidia hybrids since kernel 6.8
--
You received this bug notification becaus
The default session type is meant to be remembered. So GDM's preference
of default should actually be irrelevant if the user has ever logged in
prior to the kernel update.
If previous successful logins used Xorg and suddenly it's going to
Wayland then perhaps the attempt to use Xorg is crashing an
Another possibility is that Wayland really was being attempted first
even on older kernels, and mutter was just failing to start for one
reason or another, resulting in an automatic fallback to Xorg.
** Tags added: hybrid multigpu
** Tags removed: regression-update
** Tags added: regression-rele
** Summary changed:
- ラップトップをタブレットとして使用する際画面回転を認識しない
+ [Lenovo Yoga 7 14ARB7] Screen rotation support is intermittent
** Package changed: xorg (Ubuntu) => linux-hwe-6.8 (Ubuntu)
** Also affects: iio-sensor-proxy (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-shell (
Please run these on an affected machine:
lspci -k > lspci.txt
journalctl -b0 > journal.txt
dpkg -l > packages.txt
and attach the resulting text files here.
** Summary changed:
- Latest NVIDIA 550 driver update in Ubuntu 22.04 causes libadwaita apps to
fail launching in Wayland
+ Wayland
Jammy was also fixed via bug 2060268 in
https://launchpad.net/ubuntu/+source/ubuntu-drivers-
common/1:0.9.6.2~0.22.04.7
** Also affects: ubuntu-drivers-common (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Jammy)
Importance: Unde
Noble is now Fix Released per bug 2060268.
** Changed in: ubuntu-drivers-common (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bug
** Also affects: pipewire (Ubuntu)
Importance: Undecided
Status: New
--
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/2080192
Title:
High fidelity playback won't be enabled for b
I don't think BlueZ is involved here. It's the libinput Xorg driver
that's claiming anything with buttons as a keyboard. Although this may
need to be patched as a udev rule in udev, systemd, or somewhere else.
So shipping the rule in 'bluez' may still make sense.
** Also affects: xserver-xorg-inpu
It looks like the Nvidia kernel driver just stopped accepting new frames
from the Wayland session:
Sep 06 18:52:38 Nexus kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR*
[nvidia-drm] [GPU ID 0x0a00] Flip event timeout on head 0
Sep 06 18:52:41 Nexus kernel: [drm:nv_drm_atomic_commit [n
You don't have the fix installed. The fix is in:
ubuntu-drivers-common 1:0.9.7.6ubuntu3.1
and not in:
ubuntu-drivers-common 1:0.9.7.6ubuntu3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
http
The price of that one is quite high. But for me personally it's the only
USB-C cable I found that never has random signal dropouts. Also this
will make you feel better about the purchase:
https://www.youtube.com/watch?v=AD5aAd8Oy84
--
You received this bug notification because you are a member of
Test cases verified on Jammy using ubuntu-drivers-common
1:0.9.6.2~0.22.04.7 -
* [ Test Plan - Nvidia case ]
* [ Regression Test Plan - Intel/AMD graphics ] (Intel)
* [ Regression Test Plan - Nvidia+LUKS ]
Combined with comment #90, that makes Jammy verification done.
** Tags removed: verificat
We're only missing [ Regression Test Plan - Nvidia+LUKS ] now (comment
#87), if anyone can help with that. It requires the primary GPU be
Nvidia, so probably not a laptop but a desktop.
The other test cases have all been completed for Noble in comments #81,
#86, #88, #89. So that may be as good as
Sounds like the problem is still the cable to me. Especially if Windows
is reporting faulty USB.
Cables are the part most likely to be manufactured to a lower spec than
you need here. It's probably not the laptop or monitor's fault. Please
try to get hold of a Thunderbolt 3 or higher cable.
Just
I believe that is due to the machine missing an Nvidia driver AND
running an older kernel that may not support the current GPU. Although
if you have successfully updated the kernel already then it should be
6.8 which is new enough.
To avoid reinstalling (a newer) Ubuntu, you can try accessing the
Oh. I just realised it's a relatively new model AMD CPU but has no
integrated graphics. So the Nvidia GPU is the only GPU. Also you don't
seem to have any active Nvidia driver.
Such a new machine should be running a newer Ubuntu release to minimise
compatibility problems so please install 24.04.1
As mentioned in bug 2078814, such a new machine should be running a
newer Ubuntu release to minimise compatibility problems so please
install 24.04.1 LTS instead: https://ubuntu.com/download/desktop
And regardless, I don't think this 6.2 kernel is supported anymore.
** Changed in: linux-hwe-6.2 (
Thanks. Kernel 6.2.0.26 is not the latest version so it looks like the
update procedure isn't working.
Please make sure the laptop is connected to the internet and then:
1. Open 'Software & Updates'
2. Set 'Download from:' = 'Main server'
3. Close 'Software & Updates'
4. In a Terminal run:
Thanks for the bug report. That kernel looks old and should have been
updated by now. Please try:
sudo apt install linux-generic-hwe-22.04
and reboot.
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: New => Incomplete
--
You r
Thanks for the bug report. That kernel looks old and should have been
updated by now. Please try:
sudo apt install linux-generic-hwe-22.04
and reboot.
** Summary changed:
- I cannot change or control display brightness
+ [Lenovo LOQ 15ARP9] I cannot change or control backlight brightness
**
I should clarify: "Thunderbolt" cable means Thunderbolt 3 or higher. You
won't be able to plug in earlier versions :)
--
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/2077766
Title:
[i915]
Could not verify on Noble:
[ Regression Test Plan - Nvidia+LUKS ]
I tried a couple of times but the installer keeps crashing. Looks like
the main reason is:
Volume group "ubuntu-vg" has insufficient free space (60256 extents):
60264 required
on a completely blank disk.
--
You received thi
Verified these both fixed on Noble using ubuntu-drivers-common
1:0.9.7.6ubuntu3.1 -
* [ Test Plan - Nvidia case ]
* [ Regression Test Plan - Intel/AMD graphics ] (Intel)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-driv
> During boot, when does exactly "/bin/rm /dev/dri/card0" run? Would
that run in the initrd environment? I ask because of comment #37, which
said they lost the display during the luks password prompt. Although I
believe that's because of the workaround they were using then, which was
to disable sim
** Description changed:
[ Impact ]
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/dr
Sorry I was on leave and didn't notice how many questions needed
answering:
> It may be obvious to you that it's safe to remove /dev/dri/card0 (see
comment #71), but it's not clear to me what creates that device, why,
and when.
The device is created by whatever DRM driver loads first. The fix wor
> I changed the screen mode back to 5k as when its in the tk mode
Can you explain what you mean there?
> Should I try adjust the file with the resolution for the screen ?5120
x 1440 (32:9)
Yes it's worth a try. Although drm_info isn't listing 5K as supported by
the kernel, the kernel might also
** Summary changed:
- Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)
+ Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8
** Summary changed:
- Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8
+ Random flickering with Intel i915 (Gen9 GPUs in 6th-8th
*** This bug is a duplicate of bug 2062951 ***
https://bugs.launchpad.net/bugs/2062951
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 2062951, so it is being marked as such. Please look
** Changed in: ubuntu-drivers-common (Ubuntu Noble)
Milestone: ubuntu-24.04.1 => noble-updates
--
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/2060268
Title:
Pha
** Changed in: ubuntu-drivers-common (Ubuntu Noble)
Milestone: ubuntu-24.04.1 => noble-updates
** Changed in: ubuntu-drivers-common (Ubuntu Noble)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Danny, this bug is closed. And comment #10 is bug 2062426.
--
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/2059149
Title:
Crash
Status in linux package in Ubuntu:
Expired
Bug descript
*** This bug is a duplicate of bug 2063827 ***
https://bugs.launchpad.net/bugs/2063827
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 2063827, so it is being marked as such. Please look
> Finally, and pardon my ignorance, but could /dev/dri/card0 be used for
non-graphical things, like servers doing gpu calculations? And in that
case, removing it could break that workload?
"servers doing gpu calculations" would use /dev/dri/render*, not
/dev/dri/card*. Only the "render" nodes are
Thanks. That does confirm the kernel thinks this is the max resolution:
2560x1440@59.95 preferred driver phsync nvsync
so please go to comment #4 :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
I've extended the test plan to mention the particular hardware required.
As for testing multiple Nvidia driver versions, that's not required.
Because the phantom monitor comes from simpledrm and not from nvidia.
There are no separate per-driver fixes. Although it's always advisable
you're starting
Maybe a full debug log from the kernel would be helpful (assuming the
graphics driver goes quiet around the time the freeze happens and
doesn't keep flooding with unrelated information). Please try this
kernel parameter:
drm.debug=0xf
Then reproduce the bug again and collect new logs.
--
You
Yes I had ssh in mind.
It's often helpful to try and identify the exact kernel revision where a
bug started, or vanished. You can do so using these:
https://kernel.ubuntu.com/mainline/?C=M;O=D
If we know the minor revision where things changed it's often easy to
then identify the offending ker
Thanks for the bug report. I can see two main problems here:
1. The amdgpu kernel graphics driver is emitting warnings that look like
crashes.
2. The rtw_8821ce kernel wifi driver is flooding the system log (this is
probably the performance issue).
So I can only suggest trying an older Ubuntu r
It sounds like no environment variables are helping so you can remove
them all.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2077349
Title:
[HP Laptop 15-dw1xxx] Little display
Thanks. You can remove MUTTER_DEBUG=kms now. Those logs look perfectly
well behaved, as in my suspicion that page flips might be getting lost
was wrong and nothing is getting lost. This means something else is
freezing. So I can only suggest killing the frozen process like:
sudo killall -USR1 gn
Though I wonder if the kernel has decided at boot time that the native
5K resolution is off the list. Please check with:
sudo apt install drm-info
sudo drm_info
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Yes quite a few people have reported similar problems this year with
Ubuntu's newer kernels. But I don't recall any of them being proven to
be obvious software bugs. Just a more conservative bandwidth
calculation, usually solved with a new cable.
If you want to go to maximum quality, I recommend t
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
--
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/2077822
Title:
Bluetooth killing headphones
Status in blu
I've noticed through multiple bug reports that recent kernels have
become pedantic about bandwidth requirements and therefore which
resolutions they are willing to offer.
Also 5120x1440 at 60Hz is right near the limit of what the i7-8565U can
do:
https://ark.intel.com/content/www/us/en/ark/produc
Thanks. I can see the variable was honoured this time:
Aug 23 12:42:32 stella gnome-shell[1104]: Added device '/dev/dri/card1' (i915)
using non-atomic mode setting.
Aug 23 12:42:33 stella kernel: intel ips :00:1f.6: i915 driver attached,
reenabling gpu turbo
Strange that kernel message alwa
Whoops. Actually MUTTER_DEBUG_FORCE_KMS_MODE=simple should not work
because that feature didn't exist in Mutter 42.
Please try this instead:
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8
** Package changed: xorg (Ubuntu) => linux-hwe-6.8 (Ubuntu)
** Package changed: linux-hwe-6.8 (Ubuntu) => linux (Ubuntu)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
** Summary changed:
- Ubuntu 24.04 LTS VBox VM does not boot anymore
+ Ubuntu 24.04 LTS VBox VM does not boot anymore ["vmwgfx seems to be running
on an unsupported hypervisor"]
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
** Package changed: nvidia-graphics-drivers-525 (Ubuntu) => firefox
(Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu.
https://bugs.launchpad.net/bugs/2077706
Title:
Failed to load module "ca
** No longer affects: mutter (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2077265
Title:
Gnome desktop freeze after kernel update
Status in linux-hwe-6.8 package in U
Sounds like bug 2062951 to me. And yes the i5-7200U is a Gen9 GPU.
** Tags added: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2077220
Title:
(i915) external
Thanks for the bug report. It appears you're stuck in software rendering
mode because the proper Intel kernel graphics driver was never loaded:
Added device '/dev/dri/card0' (simpledrm) using atomic mode setting.
So that's why it's slow at least.
Next please run:
lspci -k > lspci.txt
jour
MUTTER_DEBUG_FORCE_KMS_MODE is not having the desired effect because I
forgot GNOME 42 uses a different variable. Please try:
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
in /etc/environment and reboot.
Similarly, MUTTER_DEBUG_KMS_THREAD_TYPE will have no effect because that
feature doesn't exist in GNOME
** Summary changed:
- Bluetooth not working, turning on and immediately turning off
+ [AR9285][Fujitsu Lifebook AH530] Bluetooth not working, turning on and
immediately turning off
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you
Thanks. Xorg is crashing in libglxserver_nvidia.so so it looks like an
Nvidia driver bug.
** Summary changed:
- Gnome Shell crash after some other program shutdown normally.
+ Xorg segfaults in libglxserver_nvidia.so so
** Package changed: gnome-shell (Ubuntu) => nvidia-graphics-drivers-535
(Ubu
Thanks but there's a mistake in lspci.txt so please run this again:
lspci > 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/2077499
Title:
Bluetooth not working, turning on a
It appears the messages in the bug description are actually status
messages from the kernel, and not bluetoothctl commands. So the UI
design of bluetoothctl is a little misleading. But it makes me think
even more that this is a kernel issue. Also I can't reproduce the
problem here.
Please see comm
This sounds like it's chip-specific. Please run:
lsusb > lsusb.txt
lspci > lspci.txt
dmesg > dmesg.txt
and attach the resulting text files here.
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packag
As a workaround, please try adding this to /etc/environment:
MUTTER_DEBUG_FORCE_KMS_MODE=simple
and reboot.
** Tags added: i915 psr regression-update
** Package changed: xorg (Ubuntu) => linux-hwe-6.8 (Ubuntu)
** Changed in: linux-hwe-6.8 (Ubuntu)
Importance: Undecided => Medium
** Summa
** Also affects: linux-hwe-6.8 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2062951
Title:
** Changed in: linux-hwe-6.8 (Ubuntu Noble)
Status: Confirmed => Invalid
** Changed in: linux-hwe-6.8 (Ubuntu Oracular)
Status: Confirmed => Invalid
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.8 (Ubuntu Jammy)
Im
*** This bug is a duplicate of bug 2062951 ***
https://bugs.launchpad.net/bugs/2062951
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 2062951, so it is being marked as such. Please look
Thanks. The logs say that GNOME is functioning just fine. This might be
related to the fact that it's using Intel Arrandale graphics which I
haven't tried in a long time.
Please try adding this to /etc/environment:
MUTTER_DEBUG_FORCE_KMS_MODE=simple
and reboot. If that doesn't solve it then pl
It sounds like you're referring to OBEX used to transfer files between
devices. But also since you're using Unity 7, I don't know what other
legacy components might be getting in the way here.
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu
The log looks like Wayland sessions are starting up just fine. I wonder
if this might be another simpledrm issue (even though simpledrm card0 is
clearly already removed before GNOME starts on Intel card1)... Please
try adding kernel parameter:
initcall_blacklist=simpledrm_platform_driver_init
*
Please explain what kind of messages you are talking about.
** Summary changed:
- the system bluetooth manager doesn't receive any messages and hardly send
them to paired devices. already have the problem with the 16.04, apparently not
fixed in your 24.04 release.
+ [Intel 8265] the system blu
That's the version of the VM's BIOS, not of the hypervisor, I assume.
--
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/2076520
Title:
Ubuntu 24.04 LTS VBox VM does not boot anymore
Stat
Thanks. Looks like there's a similar crash:
août 17 23:41:22 Aspire-E5-575G org.gnome.Shell.desktop[1570]: XIO: fatal IO
error 11 (Ressource temporairement non disponible) on X server ":0"
août 17 23:41:22 Aspire-E5-575G org.gnome.Shell.desktop[1570]: after 4519
requests (4519 known proce
That's great news, but surprising because the package hasn't changed for a year:
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2
** Changed in: nvidia-graphics-drivers-390 (Ubuntu Jammy)
Status: Confirmed => Incomplete
--
You received this bug not
Please clarify which driver version "seems to work now".
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2028165
Title:
nvidia-dkms-* FTBS with linux 6.5
Status in
Superseded by bug 2075327.
** Changed in: nvidia-graphics-drivers-550 (Ubuntu Jammy)
Status: In Progress => Won't Fix
** Changed in: nvidia-graphics-drivers-550 (Ubuntu Noble)
Status: In Progress => Won't Fix
** Changed in: nvidia-graphics-drivers-550 (Ubuntu Oracular)
Statu
** Tags added: regression-release
--
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/2076520
Title:
Ubuntu 24.04 LTS VBox VM does not boot anymore
Status in linux package in Ubuntu:
Con
https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.7.7
** Changed in: ubuntu-drivers-common (Ubuntu Oracular)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drive
This might be fixed by ubuntu-drivers-common in Oracular now (via bug
2060268).
--
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/2062426
Title:
simple-framebuffer: swiotlb buffer is full
Sounds like a bug in the guest driver (vmwgfx) in that case. Although
some quick googling for:
"vmwgfx seems to be running on an unsupported hypervisor"
reveals it can be storage related too. I guess because the hypervisor
uses similar mechanisms for sharing storage as it does for communicating
OK it sounds like Mutter is calculating an incorrect display timing.
I'm surprised the list of refresh rates is shorter because historically
Xorg has had more.
** No longer affects: linux (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notifica
*** This bug is a duplicate of bug 2066126 ***
https://bugs.launchpad.net/bugs/2066126
** This bug has been marked a duplicate of bug 2066126
[nvidia] Whole screen pans with cursor movement
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
** Package changed: bluez (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/2076407
Title:
Title: Bluetooth 5.4 Adapter (Ugreen CM749) Not Functioning on Ubuntu
Thanks. It does seem to suggest 59.88Hz is the preferred mode.
> First detailed timing is the preferred timing
> DTD 1: 1680x1050 59.883253 Hz 8:5 64.674 kHz119.00 MHz (478
> mm x 300 mm)
> DTD 2: 1680x1050 119.997987 Hz 8:5129.598 kHz238.46 MHz (478
> mm x 296 m
** Tags added: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2070096
Title:
[amdgpu] Graphics driver issue: Display goes black for a second at
random: [drm:l
1 - 100 of 4457 matches
Mail list logo
