[Bug 1993631] [NEW] GNOME-Shell freezes with Realizing HW cursor failed: Failed to allocate gbm_bo

2022-10-20 Thread Sebastian Heiden
Public bug reported: I'm using GNOME-Shell on Wayland with the latest nvidia-515 driver. I regularly encounter freezes of the entire desktop environment with the GNOME-Shell error "Realizing HW cursor failed: Failed to allocate gbm_bo: Das Argument ist ungültig" ProblemType: Bug DistroRelease:

[Bug 1992667] [NEW] Application windows invisible (on DG2 graphics)

2022-10-12 Thread Sebastian Heiden
Public bug reported: When using GNOME Shell with Wayland, all application windows become invisible from time to time. This usually happens right after starting GNOME Shell for the first time or after having a VRAM intensive application open, such as a game. I have installed the latest linux-oem-6

[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2022-05-09 Thread Sebastian Heiden
Try nvidia.NVreg_PreserveVideoMemoryAllocations=1 as suggested by @vanvugt You may wanna change the file path of the temporary file thought for better performance. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2022-05-09 Thread Sebastian Heiden
I'm using a RTX 3080 Ti on a Z690 Desktop motherboard and enabling the S0ix option fixed the problem for me. I've added the following option "nvidia.NVreg_EnableS0ixPowerManagement=1" to GRUB_CMDLINE_LINUX_DEFAULT. -- You received this bug notification because you are a member of Ubuntu Desktop

[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

2022-03-21 Thread Sebastian Heiden
** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnom

[Bug 1965701] Re: Background image and icons missing after suspend

2022-03-21 Thread Sebastian Heiden
*** This bug is a duplicate of bug 1876632 *** https://bugs.launchpad.net/bugs/1876632 I've checked out bug #1876632 and it doesn't look like a duplicate bug to me. This bug is about missing images and icons, whilst bug #1876632 is about corrupted icons, which seems like a clear difference to

[Bug 1965701] Re: Background image and icons missing after suspend

2022-03-20 Thread Sebastian Heiden
** Attachment added: "Gnome Shell Icons missing" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965701/+attachment/5571172/+files/Screenshot%20from%202022-03-21%2000-20-23.png ** Description changed: After resuming the system from suspend the lockscreen image, background imag

[Bug 1965701] [NEW] Background image and icons missing after suspend

2022-03-20 Thread Sebastian Heiden
Public bug reported: After resuming the system from suspend the lockscreen image, background image and some of the icons are missing. This includes most of the ubuntu-dock icons, but also some of the gnome shell icons. Restarting gdm3 using `sudo service gdm3 restart` resolves the issue. Proble

[Bug 1946367] Re: DisplayPort MST Hub only recognizes one of two displays using Wayland (NVIDIA)

2021-10-20 Thread Sebastian Heiden
Seems to suddenly work now ** Changed in: mutter (Ubuntu) Status: New => Invalid -- 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/1946367 Title: DisplayPort MST Hub only recog

[Bug 1946367] Re: DisplayPort MST Hub only recognizes one of two displays using Wayland (NVIDIA)

2021-10-09 Thread Sebastian Heiden
I have linked the upstream bug report: https://gitlab.gnome.org/GNOME/mutter/-/issues/1966 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1966 https://gitlab.gnome.org/GNOME/mutter/-/issues/1966 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1966

[Bug 1870922] Re: GUI Scaling does not work with multiple monitors

2020-04-05 Thread Sebastian Heiden
Yeah, bug #1870922 probably has the same cause. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870922 Title: GUI Scaling does not work with multiple monitors To manage notifi

[Bug 1870922] Re: GUI Scaling does not work with multiple monitors

2020-04-05 Thread Sebastian Heiden
I mean bug #1870758 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870922 Title: GUI Scaling does not work with multiple monitors To manage notifications about this bug go to

[Bug 1870922] Re: GUI Scaling does not work with multiple monitors

2020-04-05 Thread Sebastian Heiden
I don't think this issue is similar to the aforementioned issue. I was using the scaling factor 2, but other scaling factors different than 2 don't work either, except 1. And no, I do not have the experimental fractional scaling enabled, but it didn't work either. I have attached the journalctl