[Ubuntu-x-swat] [Bug 1947516] Re: Invisible mouse cursor in games (TF2, CS:GO, LoL, HL2) Wayland Ubuntu 21.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xwayland (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1947516 Title: Invisible mouse cursor in games (TF2, CS:GO, LoL, HL2) Wayland Ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1947516/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1935082] Re: [MIR] egl-wayland
> After installing libnvidia-egl-wayland1 and restarting the Wayland compositor, how do you verify that this package is being used? Does this work with any Wayland compositor in the archive or only specific ones? The main scenario that we support is Gnome shell, with its default compositor (Mutter), which comes by default with Ubuntu 21.10. As for verifying that libnvidia-egl-wayland1 is in use, you probably can't, at least directly. You will notice, though, if 3D applications run unaccelerated. > How do you enable KMS? How do you verify that KMS has been enabled? If you install the driver using the ubuntu-drivers tool (or if you install Ubuntu 21.10, and select the proprietary drivers) Wayland support will be enabled by default, as long as your GPU is supported by the NVIDIA 470 driver: https://help.ubuntu.com/community/NvidiaDriversInstallation > Can you expand upon the 'not Wayland native 3D application'? Is the idea to test the X11 compatibility layer? Or is this also not an X11 application? What application will you use for testing this, is this in the archive already or is it packaged elsewhere? 3D acceleration on Wayland already works on native applications (using the GTK3, GTK4, QT5 toolkits, etc). Applications which use their own toolkit, such as Firefox, may also feature Wayland support. GTK2 apps, apps that rely on Wine, and older QT apps can be assumed to run on X11 (XWayland) when Gnome Shell is running on Wayland. To check that you are running a Wayland compositor: $ echo $XDG_SESSION_TYPE You can also get a list of the apps which run on X11 on your system using the following command: $ xlsclients > Can you expand upon the 'single GPU' bit? What happens on systems with eg two > or more GPUs? If your system has an integrated (AMD or Intel) GPU, and an NVIDIA discrete GPU, the Gnome session will run off the integrated GPU, and you will have to tell the shell to use the discrete GPU for selected applications. Thanks ** Changed in: egl-wayland (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to egl-wayland in Ubuntu. https://bugs.launchpad.net/bugs/1935082 Title: [MIR] egl-wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/egl-wayland/+bug/1935082/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1870597] Re: libinput says "your system is too slow"
Launchpad has imported 3 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=212461.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2021-03-28T08:17:23+00:00 dor.askayo wrote:
Issue description
Distinct input events can incorrectly share the same timestamp, even
though they were actually generated a few milliseconds (or even seconds)
apart and a "SYN_REPORT" event occurred between them. See example output
below.
...
Event: time 1616757853.303892, -- SYN_REPORT
Event: time 1616757853.337911, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 2
Event: time 1616757853.337911, -- SYN_REPORT
Event: time 1616757853.372886, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 2
Event: time 1616757853.372886, -- SYN_REPORT
Event: time 1616757853.406914, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 2
Event: time 1616757853.406914, -- SYN_REPORT
Event: time 1616757853.440892, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 2
Event: time 1616757853.440892, -- SYN_REPORT
Event: time 1616757853.474907, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 2
Event: time 1616757853.474907, -- SYN_REPORT
Event: time 1616757853.508886, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 2
Event: time 1616757853.508886, -- SYN_REPORT
Event: time 1616757853.508886, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e4
Event: time 1616757853.508886, type 1 (EV_KEY), code 97 (KEY_RIGHTCTRL), value 0
Event: time 1616757853.508886, -- SYN_REPORT
Reproduction steps
To reproduce the above:
1. Run evtest and select a device that supports emulated repeat events. (such
as a keyboard)
2. Press and hold a key for a few seconds and then release.
3. Notice that the "release" event (value 2) incorrectly shares the same
timestamp as the last repeat event "value 0".
Prior work
* A similar issue was fixed in 6c7e54bd5fda ("Input: reset device timestamp on
sync") by making sure the timestamp is reset after a "SYN_REPORT" event is
generated, forcing a new timestamp to be created for following events. However,
it only handled the case of events that were sent to the input_handle_event()
function, and didn't cover "SYN_REPORT" events that were generated internally
in the input core, such as emulated repeat events.
* Another similar issue was fixed by cb5a89cdbaec ("Input: fix stale timestamp
on key autorepeat events") which made sure that each repeat event got an
updated timestamp. However, it didn't prevent those timestamps from becoming
stale and used by following events.
Proposed fix
The attached patch resets the timestamp similarly to 6c7e54bd5fda
("Input: reset device timestamp on sync"), but does so in every case a
"SYN_REPORT" event is generated by the input core. The idea being that
the next event sequence would then be forced to get a new timestamp.
Related issues
* https://bugzilla.kernel.org/show_bug.cgi?id=206929 - The original bug report
where this issue was reported, which was only partially fixed by cb5a89cdbaec
("Input: fix stale timestamp on key autorepeat events"). While "repeat" events
had their timestamps update correctly, the "release" event did not.
* https://gitlab.freedesktop.org/libinput/libinput/-/issues/571#note_83 -
An issue about errors constantly being printed by libinput about delay in
handling of events. The investigation of this issue revealed the reported bug.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870597/comments/22
On 2021-03-28T09:16:55+00:00 dor.askayo wrote:
Created attachment 296099
0001-Input-reset-timestamp-after-SYN_REPORT-events.patch
Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870597/comments/23
On 2021-06-15T08:10:50+00:00 michel wrote:
I suspect you need to just submit the patch by e-mail according to the
kernel development process. Running
scripts/get_maintainer.pl 0001-Input-reset-timestamp-after-SYN_REPORT-
events.patch
in a kernel tree prints the maintainers and lists where the patch should
be sent to.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870597/comments/25
** Changed in: linux
Status: Unknown => Confirmed
** Changed in: linux
Importance: Unknown => Medium
** Bug watch added: Linux Kernel Bug Tracker #206929
https://bugzilla.kernel.org/show_bug.cgi?id=206929
** Bug watch added: gitlab.freedesktop.org/libinput/libinput/-/issues #571
[Ubuntu-x-swat] [Bug 1870597] Re: libinput says "your system is too slow"
There is a kernel regression that causes some of the problem: https://bugzilla.kernel.org/show_bug.cgi?id=212461 But other than that it should be mostly fixed, not entirely, in GNOME 40. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Bug watch added: Linux Kernel Bug Tracker #212461 https://bugzilla.kernel.org/show_bug.cgi?id=212461 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=212461 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1870597 Title: libinput says "your system is too slow" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1947826] Re: External monitor stopped working after update
It appears you're just missing a driver for the Nvidia RTX 3060 Mobile chip (which is what external monitor connectors are usually wired to). Please open the 'Additional Drivers' app and install the latest Nvidia driver. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid ** Tags added: nvidia -- 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/1947826 Title: External monitor stopped working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1947826/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1947826] Re: External monitor stopped working after update
** Package changed: ubuntu => xorg (Ubuntu) -- 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/1947826 Title: External monitor stopped working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1947826/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1947826] [NEW] External monitor stopped working after update
You have been subscribed to a public bug: After an unattended update from Ubuntu, the external monitor stopped working. The monitor works fine if I log into Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 20 13:52:16 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: xpad, 0.4, 5.11.0-36-generic, x86_64: installed xpad, 0.4, 5.11.0-37-generic, x86_64: installed xpad, 0.4, 5.11.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9a60] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1539] NVIDIA Corporation Device [10de:2520] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:153a] InstallationDate: Installed on 2021-09-11 (38 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Acer Nitro AN515-57 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=3262607a-bb5e-4ffc-8e4d-c697a539cb73 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/29/2021 dmi.bios.release: 1.3 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Scala_TLS dmi.board.vendor: TGL dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd04/29/2021:br1.3:efr1.2:svnAcer:pnNitroAN515-57:pvrV1.03:sku:rvnTGL:rnScala_TLS:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-57 dmi.product.sku: dmi.product.version: V1.03 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- External monitor stopped working after update https://bugs.launchpad.net/bugs/1947826 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
