Thanks for the bug report.
Please try:
1. sudo rm /dev/dri/card0 # to work around bug 2060268, and then log in
again. Did that solve it?
2. When the problem starts happening please open a Terminal and run:
journalctl -b0 > journal.txt
xlsclients > xclients.txt
and attach the resulting
** Tags added: nvidia nvidia-wayland
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2062082
Title:
24.04 Wayland vs Nautilus performance problem
To manage notifications about this bug go to:
ht
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2062082
Title:
24.04 Wayland vs Nautilus performance problem
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
Public bug reported:
Apologies if I have misfiled this bug - this is a report of an issue
affecting Wayland in Ubuntu 24.04 beta.
Using 24.04 beta logging in with Wayland. Nautilus has very significant
performance issues. Doesn't happen when logging in with Xorg instead of
Wayland.
Opening Nauti
My issue is compounded by the fact that Ubuntu registers no network
interfaces in Ubuntu on vmwareplayer in NAT mode and it sees a
connection but can't connect in bridged mode. As a result I can't apply
updates on install or upgrade my NVIDIA drivers which may help resolve
the issue. I will try aga
(The latest version of the Ubuntu Desktop installer installs all
available updates at the end of the install. It's a nice feature in
cases like this.)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs
OK, so I just tried this out on the same host I did my Fedora 40
testing, a Windows 11 23H2 system with Intel graphics (no NVIDIA) and
VMWare Player 17.
I grabbed the Ubuntu 24.04 beta desktop image - ubuntu-24.04-beta-
desktop-amd64.iso - and booted it. From that environment I could
reproduce the
FWIW, I did my testing - which found this is broken for a Fedora 40
guest with mesa 24.0.4, but fixed with 24.0.5 - on a Windows 11 (23H2)
host. No idea what's different for Oliver, sorry :(
I guess I could try with an Ubuntu guest on my test setup, I've got a
bit of spare time today.
--
You rec
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2054827
Title:
[regression] GUI crashed after installed proposed package after mesa
updates
To manage notifications about this bug go to:
https:/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2054827
Title:
This bug was fixed in the package intel-compute-runtime -
23.43.27642.40-1ubuntu3
---
intel-compute-runtime (23.43.27642.40-1ubuntu3) noble; urgency=medium
* Fix detecting NEO driver with v6.8 kernel. (LP: #2061969)
-- Timo Aaltonen Wed, 17 Apr 2024 10:52:22 +0300
** Changed in
I was unable to complete the VMWare Workstation Player 17 install on a
Ubuntu 24.04 LTS host even though there is a Linux installer.
Note that this bug report says that the host is Windows 11.
Similarly, I was able to install VirtualBox on a Ubuntu 24.04 LTS host
but was unable to duplicate https
Then what is different to upstream? There seem to be more than one
report of success with 24.0.5
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2061118
Title:
Rendering issues in vmware with 3d
** Changed in: mesa (Ubuntu Noble)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2061118
Title:
Rendering issues in vmware with 3d on (GTK ngl backend)
T
Public bug reported:
Currently on Noble 'clinfo' etc doesn't detect the platform correctly,
and the NEO driver isn't getting used.
This was filed upstream and there is a fix available.
https://github.com/intel/compute-runtime/issues/710
** Affects: intel-compute-runtime (Ubuntu)
Importance:
@Timo, I have tried the latest daily with the new Mesa and there is no
change to behaviour it is still non-functional with 3D acceleration
enabled.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/20
Public bug reported:
[Impact]
Booting installed noble will result in gdm unable to show the login
screen. Instead of chasing why the software fallback doesn't work
properly, it makes more sense to add support for the platform so it can
use the native driver.
This needs a (squashed) patch which o
17 matches
Mail list logo
