6.5.13 > "Test amd64/build failed (rc=2, on=amd64, time=0:07:36,
log=amd64/log)".
@superm1
In 6.6.6 this issue seems fixed FYI.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/203
No, this was an issue happening in monitors connected via HDMI.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window sh
Bug fixed with kernel 6.6.x, more info, please see here:
https://gitlab.gnome.org/GNOME/mutter/-/issues/3036
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2039570
Title:
[amdgpu]
** No longer affects: linux (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2039570
Title:
[amdg
Public bug reported:
When I connect the laptop to the sound bar hdmi and the sound bar to the
monitor, it tries to connect and Ubuntu detects it, but nothing appears
on the screen.
My HDMI works as it should, tested directly when it's connected to the
monitor. I have tried on a laptop other than
Here, there's an issue opened in Gitlab Gnome about mutter that could be
related to this issue (thanks again to Michel Dänzer):
https://gitlab.gnome.org/GNOME/mutter/-/issues/3036
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3036
https://gitlab.gnome.org/GNOME/mutter/-/issues/30
I opened a report here in freedesktop:
https://gitlab.freedesktop.org/drm/amd/-/issues/2993#note_2172154
And as Michel Dänzer says, it's possible this is an issue related to
Mutter. Here in these logs from journalctl gnome-shell I attach here,
you can see the messages that appear just when, upon
Public bug reported:
OS: Ubuntu 23.10
The version of the package: gnome-shell 45.0-1ubuntu2
What you expected to happen: Should work with no glitches or crashes
when you are dealing with multiple windows like Nautilus, Steam,
Telegram and/or Firefox.
What happened instead: Apparently gnome-shel
Confirmed. This fixed the issue.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1969422
Title:
gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from
meta_
Public bug reported:
Few days ago it was working perfectly, but today I saw in gdm the button
to change the session wayland/xorg isn't there. Ubuntu only loads Xorg
by default.
Laptop: MSI Alpha 17 A4DEK
CPU: AMD Ryzen 7 4800
GPU: AMD Radeon RX 5600m
ProblemType: Bug
DistroRelease: Ubuntu 22.04
I have the same bug here. You can activate or turn it off but the
bluetooth is always "off", for me happens sometimes when I reboot.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad
I have the same fail, since I updated Nvidia version (to 410), and then
even returning to 396, Vulkan doesn't work, with vulkaninfo appears in
terminal the same text as nastys.
But with "sudo vulkaninfo" Vulkan works.
PD: I have Ubuntu 18.04 with Gnome, and Nvidia's drivers.
--
You received thi
I was having the same fail/mistake but in Ubuntu 18.04 (Gnome and
vanilla desktop), I don't know why but since 2 weeks ago (since an
update of gnome-control-center I think, but I'm not sure) the lock
screen just doesn't work and neither the settings, it's like zhiwei
said, it doesn't allow any chan
13 matches
Mail list logo
