[Bug 1834762] Re: Screen locks after timeout with hidraw input
** Description changed: As the title says, when using the hidraw as input method, used by game controllers in games in Steam big picture mode especially, is not being detected by the gnome desktop, and so if you are playing a game using hidraw only, the screen timeout will come out, and the session will be blocked Steps to reproduce: - Open a game - Play a game with a controller using hidraw as input, such as the RPCS3 emulator - - The gnome-screenshot timeout will kick in and lock the session even when actively playing, as long no mouse or keyboard is used + - The gnome-screensaver timeout will kick in and lock the session even when actively playing, as long no mouse or keyboard is used What should happen - Hidraw should be detected in the same way a mouse or keyboard does I have NOT tested with a game using native evdev My config is: Steam + steam-devices packages installed, the steam devices has some rules for hidraw to be correctly working with my controller. I own a PS4 controller connected via bluetooth, but the same should happen on USB as well I used the RPCS3 emulator, which so far supports only hidraw as input method. ** Description changed: As the title says, when using the hidraw as input method, used by game controllers in games in Steam big picture mode especially, is not being detected by the gnome desktop, and so if you are playing a game using hidraw only, the screen timeout will come out, and the session will be blocked Steps to reproduce: - Open a game - Play a game with a controller using hidraw as input, such as the RPCS3 emulator - The gnome-screensaver timeout will kick in and lock the session even when actively playing, as long no mouse or keyboard is used What should happen - Hidraw should be detected in the same way a mouse or keyboard does I have NOT tested with a game using native evdev My config is: - Steam + steam-devices packages installed, the steam devices has some rules for hidraw to be correctly working with my controller. + Steam + steam-devices packages installed, the steam-devices package has some udev rules for hidraw to be correctly working with this controller. I own a PS4 controller connected via bluetooth, but the same should happen on USB as well I used the RPCS3 emulator, which so far supports only hidraw as input method. ** Description changed: - As the title says, when using the hidraw as input method, used by game + As the title says, when using hidraw as input method, used by game controllers in games in Steam big picture mode especially, is not being detected by the gnome desktop, and so if you are playing a game using - hidraw only, the screen timeout will come out, and the session will be - blocked + hidraw only, the blank screen and/or lock timeout will come out, and the + session will be blocked or the screen will become blank Steps to reproduce: - Open a game - Play a game with a controller using hidraw as input, such as the RPCS3 emulator - The gnome-screensaver timeout will kick in and lock the session even when actively playing, as long no mouse or keyboard is used What should happen - Hidraw should be detected in the same way a mouse or keyboard does I have NOT tested with a game using native evdev My config is: Steam + steam-devices packages installed, the steam-devices package has some udev rules for hidraw to be correctly working with this controller. I own a PS4 controller connected via bluetooth, but the same should happen on USB as well I used the RPCS3 emulator, which so far supports only hidraw as input method. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1834762 Title: Screen locks after timeout with hidraw input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1834762/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1834762] [NEW] Screen locks after timeout with hidraw input
Public bug reported: As the title says, when using the hidraw as input method, used by game controllers in games in Steam big picture mode especially, is not being detected by the gnome desktop, and so if you are playing a game using hidraw only, the screen timeout will come out, and the session will be blocked Steps to reproduce: - Open a game - Play a game with a controller using hidraw as input, such as the RPCS3 emulator - The gnome-screensaver timeout will kick in and lock the session even when actively playing, as long no mouse or keyboard is used What should happen - Hidraw should be detected in the same way a mouse or keyboard does I have NOT tested with a game using native evdev My config is: Steam + steam-devices packages installed, the steam devices has some rules for hidraw to be correctly working with my controller. I own a PS4 controller connected via bluetooth, but the same should happen on USB as well I used the RPCS3 emulator, which so far supports only hidraw as input method. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Description changed: As the title says, when using the hidraw as input method, used by game - controllers in games like Steam especially, is not being detected by the - gnome desktop, and so if you are playing a game using hidraw with the - controller, the screen timeout will come out, and the session will be + controllers in games in Steam big picture mode especially, is not being + detected by the gnome desktop, and so if you are playing a game using + hidraw only, the screen timeout will come out, and the session will be blocked Steps to reproduce: - Open a game - Play a game with a controller using hidraw as input, such as the RPCS3 emulator - The gnome-screenshot timeout will kick in and lock the session even when actively playing, as long no mouse or keyboard is used What should happen - Hidraw should be detected in the same way a mouse or keyboard does I have NOT tested with a game using native evdev My config is: Steam + steam-devices packages installed, the steam devices has some rules for hidraw to be correctly working with my controller. I own a PS4 controller connected via bluetooth, but the same should happen on USB as well I used the RPCS3 emulator, which so far supports only hidraw as input method. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1834762 Title: Screen locks after timeout with hidraw input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1834762/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
Hi, in debian testing this does not happen, neither in debian unstable or other distros with the same gnome-shell package version I confirm it's a regression from 18.10 to 19.04 In 18.10 it works fine -- 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/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823544] Re: Unreasonable NVIDIA GPU VRAM usage on gnome-shell
Yes but the amount of time I kept in the first test was not the same, I just do not have enough time to test In the first one my PC was up for almost a day unlike the second scenario where the uptime was just 1h and a couple of minutes -- 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/1823544 Title: Unreasonable NVIDIA GPU VRAM usage on gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823544] Re: Unreasonable NVIDIA GPU VRAM usage on gnome-shell
Ok, fine I uninstalled any non-official GNOME extension and in cold start I'm getting after 1.2h of uptime 200MB more than the normal, I am not 100% sure but I think this still persist Cold start: +-+ | NVIDIA-SMI 418.56 Driver Version: 418.56 CUDA Version: 10.1 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce GTX 106... Off | :1C:00.0 On | N/A | | 51% 30CP028W / 120W |225MiB / 3011MiB | 0% Default | +---+--+--+ +-+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=| |0 1501 G /usr/lib/xorg/Xorg18MiB | |0 1559 G /usr/bin/gnome-shell 49MiB | |0 2017 G /usr/lib/xorg/Xorg44MiB | |0 2154 G /usr/bin/gnome-shell 109MiB | +-+ 1.2h of uptime Mon Apr 8 13:53:34 2019 +-+ | NVIDIA-SMI 418.56 Driver Version: 418.56 CUDA Version: 10.1 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce GTX 106... Off | :1C:00.0 On | N/A | | 55% 33CP8 9W / 120W |447MiB / 3011MiB | 0% Default | +---+--+--+ +-+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=| |0 1501 G /usr/lib/xorg/Xorg18MiB | |0 1559 G /usr/bin/gnome-shell 49MiB | |0 2017 G /usr/lib/xorg/Xorg 124MiB | |0 2154 G /usr/bin/gnome-shell 204MiB | |0 7639 G ...quest-channel-token=920471993479850461346MiB | +-+ -- 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/1823544 Title: Unreasonable NVIDIA GPU VRAM usage on gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823544] Re: Unreasonable NVIDIA GPU VRAM usage on gnome-shell
apport information ** Tags added: apport-collected ** Description changed: GPU: NVIDIA GTX 1060 3GB Ubuntu: 19.04, Kernel Linux luky-pc 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux NVIDIA driver version: 418.56 Display settings: BenQ XL2411Z, 144Hz monitor, 1920x1080p I have noticed this strange behavior only on gnome-shell where the overall gnome-shell desktop VRAM usage was taking up to 1GB of GPU VRAM which does not happen on other desktops, or on Windows, happens after some hours of normal desktop usage Even the system RAM increases a lot during normal usage, but remains acceptable This behaviour can be observed by using "nvidia-smi" a tool from the NVIDIA proprietary driver gnome-shell VRAM usage on a cold start: 139MB, + 9 MB X.org VRAM usage on cold start: 48MB + 18MB Total: 214MB gnome-shell VRAM usage after some hours of normal usage: 445MB + 83 MB X.org VRAM usage after some hours of normal usage: 244MB + 18MB Total: 800MB On windows or other desktops the GPU VRAM usage remains the same + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu25 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 19.04 + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell 3.32.0-1ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=it_IT.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 + Tags: disco + Uname: Linux 5.0.0-8-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1823544/+attachment/5254040/+files/Dependencies.txt -- 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/1823544 Title: Unreasonable NVIDIA GPU VRAM usage on gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823544] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1823544/+attachment/5254042/+files/ProcCpuinfoMinimal.txt -- 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/1823544 Title: Unreasonable NVIDIA GPU VRAM usage on gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823544] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1823544/+attachment/5254041/+files/GsettingsChanges.txt -- 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/1823544 Title: Unreasonable NVIDIA GPU VRAM usage on gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823544] [NEW] Unreasonable NVIDIA GPU VRAM usage on gnome-shell
Public bug reported: GPU: NVIDIA GTX 1060 3GB Ubuntu: 19.04, Kernel Linux luky-pc 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux NVIDIA driver version: 418.56 Display settings: BenQ XL2411Z, 144Hz monitor, 1920x1080p I have noticed this strange behavior only on gnome-shell where the overall gnome-shell desktop VRAM usage was taking up to 1GB of GPU VRAM which does not happen on other desktops, or on Windows, happens after some hours of normal desktop usage Even the system RAM increases a lot during normal usage, but remains acceptable This behaviour can be observed by using "nvidia-smi" a tool from the NVIDIA proprietary driver gnome-shell VRAM usage on a cold start: 139MB, + 9 MB X.org VRAM usage on cold start: 48MB + 18MB Total: 214MB gnome-shell VRAM usage after some hours of normal usage: 445MB + 83 MB X.org VRAM usage after some hours of normal usage: 244MB + 18MB Total: 800MB On windows or other desktops the GPU VRAM usage remains the same ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "vram usage after some hours" https://bugs.launchpad.net/bugs/1823544/+attachment/5253737/+files/aftersomehours.png -- 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/1823544 Title: Unreasonable NVIDIA GPU VRAM usage on gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823544] Re: Unreasonable NVIDIA GPU VRAM usage on gnome-shell
vram usage on fresh start ** Attachment added: "freshstart.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+attachment/5253738/+files/freshstart.png -- 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/1823544 Title: Unreasonable NVIDIA GPU VRAM usage on gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
Okay, it's fine anyway I tested 18.10 again as well with another distribution with roughly the same packages and I was not able to reproduce the issue I'll try Debian testing -- 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/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1576859] Re: [nvidia] Graphics corruption when resuming from suspend
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 I never had this issue until the 19.04 update, I always used the NVIDIA proprietary driver. In Ubuntu 18.10 is working fine, so I suppose is some sort of regression... I'm curious to try this on another distribution. -- 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/1576859 Title: [nvidia] Graphics corruption when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1576859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
Hi Daniel, I've seen you marked my bug as this duplicate, but for me this doesn't happen on Ubuntu 18.10, only after the 19.04 upgrade -- 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/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Hi, I don't know if that's correct because in Ubuntu 18.10 I had no issue, I will provide more information once I'll get on my PC -- 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/1822179 Title: Resuming from sleep breaks desktop and lock screen background in GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822179/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)
Can be the same issue as https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1800465 Only happening with GDM in ubuntu 18.04 with updated nvidia drivers and ubuntu 18.10 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1769857 Title: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1445595] Re: Empty trash from Launcher results in Nautilus window opening
Still problem today. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1445595 Title: Empty trash from Launcher results in Nautilus window opening To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1445595/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
