[Desktop-packages] [Bug 1903957] Re: [snap] chromium won't run over a remote X session
X11 connection rejected because of wrong authentication.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1903957
Title:
[snap] chromium won't run over a remote X session
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
Since upgrading to Ubuntu 20.04.1 LTS from 18.04.5 LTS, starting Chromium
Browser over a remote X session fails with
```
peter@fs-peter:~$ chromium-browser
KiTTY X11 proxy: Unsupported authorisation protocol
[28937:28937:1112/080948.455990:ERROR:browser_main_loop.cc(1426)] Unable to
open X display.
peter@fs-peter:~$
```
The same happens for apps like `chrome-dominoes` (which, of course, is
the critical issue ;) ).
Other applications run over remote X fine (Firefox, Jamulus, several
other applications).
Apparently this is not the same as #1897224.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-3:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p1 ext4 229G 36G 181G 17% /
tmpfs tmpfs 7.7G 16M 7.7G 1% /dev/shm
/dev/nvme0n1p1 ext4 229G 36G 181G 17% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-11-07 (370 days ago)
InstallationMedia: Kubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
Lsusb:
Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA
6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E
SATA 6Gb/s bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 04f3:0110 Elan Microelectronics Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
|__ Port 8: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 4: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
1.5M
|__ Port 4: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid,
1.5M
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-lowlatency
root=UUID=bf22c190-dfc3-4cc0-aa69-df0f50d8c822 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-53.59-lowlatency 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
36 Done2020-11-11T23:18:24Z 2020-11-11T23:18:35Z Auto-refresh snap
"chromium"
Snap.ChromeDriverVersion: ChromeDriver 86.0.4240.193
(4b1dc838fc8d2b55f2147e7a642b20baf443da5c-refs/branch-heads/4240@{#1411})
Snap.ChromiumVersion: Chromium 86.0.4240.193 snap
Tags: focal snap
Uname: Linux 5.4.0-53-lowlatency x86_64
UpgradeStatus: Upgraded to focal on 2020-10-04 (39 days ago)
UserGroups: Jamulus adm audio cdrom dip lpadmin lxd minidlna plugdev
sambashare sudo
_MarkForUpload: True
acpidump:
Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon:
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
Error executing command as another user: Not authorized
This incident has been reported.
dmi.bios.date: 12/18/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.30
dmi.board.name: Z370M-ITX/ac
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd12/18/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ370M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1903957/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1903957] Re: [snap] chromium won't run over a remote X session
same here, firefox, octave, etc cannot be open. The classic one is ok.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1903957
Title:
[snap] chromium won't run over a remote X session
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
Since upgrading to Ubuntu 20.04.1 LTS from 18.04.5 LTS, starting Chromium
Browser over a remote X session fails with
```
peter@fs-peter:~$ chromium-browser
KiTTY X11 proxy: Unsupported authorisation protocol
[28937:28937:1112/080948.455990:ERROR:browser_main_loop.cc(1426)] Unable to
open X display.
peter@fs-peter:~$
```
The same happens for apps like `chrome-dominoes` (which, of course, is
the critical issue ;) ).
Other applications run over remote X fine (Firefox, Jamulus, several
other applications).
Apparently this is not the same as #1897224.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-3:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p1 ext4 229G 36G 181G 17% /
tmpfs tmpfs 7.7G 16M 7.7G 1% /dev/shm
/dev/nvme0n1p1 ext4 229G 36G 181G 17% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-11-07 (370 days ago)
InstallationMedia: Kubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
Lsusb:
Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA
6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E
SATA 6Gb/s bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 04f3:0110 Elan Microelectronics Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
|__ Port 8: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 4: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
1.5M
|__ Port 4: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid,
1.5M
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-lowlatency
root=UUID=bf22c190-dfc3-4cc0-aa69-df0f50d8c822 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-53.59-lowlatency 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
36 Done2020-11-11T23:18:24Z 2020-11-11T23:18:35Z Auto-refresh snap
"chromium"
Snap.ChromeDriverVersion: ChromeDriver 86.0.4240.193
(4b1dc838fc8d2b55f2147e7a642b20baf443da5c-refs/branch-heads/4240@{#1411})
Snap.ChromiumVersion: Chromium 86.0.4240.193 snap
Tags: focal snap
Uname: Linux 5.4.0-53-lowlatency x86_64
UpgradeStatus: Upgraded to focal on 2020-10-04 (39 days ago)
UserGroups: Jamulus adm audio cdrom dip lpadmin lxd minidlna plugdev
sambashare sudo
_MarkForUpload: True
acpidump:
Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon:
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
Error executing command as another user: Not authorized
This incident has been reported.
dmi.bios.date: 12/18/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.30
dmi.board.name: Z370M-ITX/ac
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd12/18/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ370M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1903957/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~de
[Desktop-packages] [Bug 1999830] Re: external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR*
** Description changed: - ubuntu 22.04.1 - 5.15.0-56-generic - mutter 42.5-0ubuntu1 - using gdm3 - nvidia Driver Version: 525.60.11 (nvidia-driver-525) - prime select to on-demand - 1 external display, 1 internal LCD ``` Added device '/dev/dri/card1' (nvidia-drm) using non-atomic mode setting. Added device '/dev/dri/card0' (i915) using atomic mode setting. Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card1' Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card0' Dec 15 22:13:34 gnome-shell[3203]: Boot VGA GPU /dev/dri/card0 selected as primary Dec 15 22:13:35 gnome-shell[3203]: Secondary GPU initialization failed (Failed to create gbm_surface: No such file or directory). Falling back to GPU-less > Dec 15 22:13:35 gnome-shell[3203]: Using public X11 display :1, (using :2 for managed services) Dec 15 22:13:35 gnome-shell[3203]: Using Wayland display name 'wayland-0' ``` + 0. open a terminal `journalctl -f` 1. Open the display setting, switch to join displays, choose external display as primary. 2. try to change some settings like scale, position of the screen, refresh rate, etc, then applay 3. repeat above step several times - After 2 or 3 changes the external screen freeze forever. Internal screen is still responsible. Get into journal : + After 2 changes the external screen freeze forever. Internal screen is still responsible. On each `Apply` The journal recorded an kernel error about nvidia_drm and flooded with clutter-frame-clock error. ``` Dec 15 22:18:52 gnome-shell[3203]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Dec 15 22:18:52 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: Invalid argument Dec 15 22:19:25 gnome-shell[3203]: Failed to allocate onscreen framebuffer for /dev/dri/card1: Failed to create dumb drm buffer: Cannot allocate memory Dec 15 22:19:25 kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to map NvKmsKapiMemory 0x5> Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Dec 15 22:19:26 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: Invalid argument Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached ``` - one may ignore the KMS update and clutter-frame-clock part since they are always flooding the log. + one may ignore the drmModeAtomicCommit warning, they are always flooding the log (though it may be related issue) + + The clutter warning then flood the log forever till reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1999830 Title: external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* Status in mutter package in Ubuntu: New Bug description: - ubuntu 22.04.1 - 5.15.0-56-generic - mutter 42.5-0ubuntu1 - using gdm3 - nvidia Driver Version: 525.60.11 (nvidia-driver-525) - prime select to on-demand - 1 external display, 1 internal LCD ``` Added device '/dev/dri/card1' (nvidia-drm) using non-atomic mode setting. Added device '/dev/dri/card0' (i915) using atomic mode setting. Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card1' Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card0' Dec 15 22:13:34 gnome-shell[3203]: Boot VGA GPU /dev/dri/card0 selected as primary Dec 15 22:13:35 gnome-shell[3203]: Secondary GPU initializatio
[Desktop-packages] [Bug 1999830] Re: external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR*
** Summary changed: - external screen freeze during display setting when using wayland + external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1999830 Title: external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* Status in mutter package in Ubuntu: New Bug description: - ubuntu 22.04.1 - 5.15.0-56-generic - mutter 42.5-0ubuntu1 - using gdm3 - nvidia Driver Version: 525.60.11 (nvidia-driver-525) - prime select to on-demand - 1 external display, 1 internal LCD ``` Added device '/dev/dri/card1' (nvidia-drm) using non-atomic mode setting. Added device '/dev/dri/card0' (i915) using atomic mode setting. Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card1' Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card0' Dec 15 22:13:34 gnome-shell[3203]: Boot VGA GPU /dev/dri/card0 selected as primary Dec 15 22:13:35 gnome-shell[3203]: Secondary GPU initialization failed (Failed to create gbm_surface: No such file or directory). Falling back to GPU-less > Dec 15 22:13:35 gnome-shell[3203]: Using public X11 display :1, (using :2 for managed services) Dec 15 22:13:35 gnome-shell[3203]: Using Wayland display name 'wayland-0' ``` 0. open a terminal `journalctl -f` 1. Open the display setting, switch to join displays, choose external display as primary. 2. try to change some settings like scale, position of the screen, refresh rate, etc, then applay 3. repeat above step several times After 2 changes the external screen freeze forever. Internal screen is still responsible. On each `Apply` The journal recorded an kernel error about nvidia_drm and flooded with clutter-frame-clock error. ``` Dec 15 22:18:52 gnome-shell[3203]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Dec 15 22:18:52 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: Invalid argument Dec 15 22:19:25 gnome-shell[3203]: Failed to allocate onscreen framebuffer for /dev/dri/card1: Failed to create dumb drm buffer: Cannot allocate memory Dec 15 22:19:25 kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to map NvKmsKapiMemory 0x5> Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Dec 15 22:19:26 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: Invalid argument Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached ``` one may ignore the drmModeAtomicCommit warning, they are always flooding the log (though it may be related issue) The clutter warning then flood the log forever till reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1999830/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999830] [NEW] external screen freeze during display setting when using wayland
Public bug reported: - ubuntu 22.04.1 - 5.15.0-56-generic - mutter 42.5-0ubuntu1 - using gdm3 - nvidia Driver Version: 525.60.11 (nvidia-driver-525) - prime select to on-demand - 1 external display, 1 internal LCD ``` Added device '/dev/dri/card1' (nvidia-drm) using non-atomic mode setting. Added device '/dev/dri/card0' (i915) using atomic mode setting. Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card1' Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card0' Dec 15 22:13:34 gnome-shell[3203]: Boot VGA GPU /dev/dri/card0 selected as primary Dec 15 22:13:35 gnome-shell[3203]: Secondary GPU initialization failed (Failed to create gbm_surface: No such file or directory). Falling back to GPU-less > Dec 15 22:13:35 gnome-shell[3203]: Using public X11 display :1, (using :2 for managed services) Dec 15 22:13:35 gnome-shell[3203]: Using Wayland display name 'wayland-0' ``` 1. Open the display setting, switch to join displays, choose external display as primary. 2. try to change some settings like scale, position of the screen, refresh rate, etc, then applay 3. repeat above step several times After 2 or 3 changes the external screen freeze forever. Internal screen is still responsible. Get into journal : ``` Dec 15 22:18:52 gnome-shell[3203]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Dec 15 22:18:52 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: Invalid argument Dec 15 22:19:25 gnome-shell[3203]: Failed to allocate onscreen framebuffer for /dev/dri/card1: Failed to create dumb drm buffer: Cannot allocate memory Dec 15 22:19:25 kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to map NvKmsKapiMemory 0x5> Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Dec 15 22:19:26 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: Invalid argument Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached ``` one may ignore the KMS update and clutter-frame-clock part since they are always flooding the log. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1999830 Title: external screen freeze during display setting when using wayland Status in mutter package in Ubuntu: New Bug description: - ubuntu 22.04.1 - 5.15.0-56-generic - mutter 42.5-0ubuntu1 - using gdm3 - nvidia Driver Version: 525.60.11 (nvidia-driver-525) - prime select to on-demand - 1 external display, 1 internal LCD ``` Added device '/dev/dri/card1' (nvidia-drm) using non-atomic mode setting. Added device '/dev/dri/card0' (i915) using atomic mode setting. Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card1' Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card0' Dec 15 22:13:34 gnome-shell[3203]: Boot VGA GPU /dev/dri/card0 selected as primary Dec 15 22:13:35 gnome-shell[3203]: Secondary GPU initialization failed (Failed to create gbm_surface: No such file or directory). Falling back to GPU-less > Dec 15 22:13:35 gnome-shell[3203]: Using public X11 display :1, (using :2 for managed services) Dec 15 22:13:35 gnome-shell[3203]: Using Wayland display name 'wayland-0' ``` 1. Open the display setting, switch to join displays, choose external display as primary. 2. try to change some settings like scale, position of the screen, refresh rate, etc, then applay 3. repeat above step several
[Desktop-packages] [Bug 1967707] Re: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached"
maybe related: > [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID > 0x0100] Failed to map NvKmsKapiMemory Failed to map NvKmsKapiMemory > 0x62c80dd4 Mutter 42.5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1967707 Title: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached" Status in Mutter: New Status in mutter package in Ubuntu: Triaged Bug description: Nvidia Wayland sessions sometimes flood the log with: [ 13.105877] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.106163] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.112490] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.125302] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.142242] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached I've been seeing the issue for months although it only seems to happen *after* something has gone wrong in mutter. Not by default. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1967707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967707] Re: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached"
flooded with ` gnome-shell[3217]: (../clutter/clutter/clutter-frame- clock.c:332):clutter_frame_clock_notify_presented: code should not be reached` Then flooded with: > Page flip discarded: drmModeAtomicCommit: Invalid argument > Failed to post KMS update: drmModeAtomicCommit: Invalid argument Then external screen freeze but internal LCD works fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1967707 Title: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached" Status in Mutter: New Status in mutter package in Ubuntu: Triaged Bug description: Nvidia Wayland sessions sometimes flood the log with: [ 13.105877] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.106163] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.112490] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.125302] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.142242] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached I've been seeing the issue for months although it only seems to happen *after* something has gone wrong in mutter. Not by default. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1967707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870597] Re: libinput says "your system is too slow"
The problem come back again after recent updates in ubuntu 20.04. System is stuttering when moving mouse and typing on keyboard: mutter3.36.9-0ubuntu0.20.04.2 xserver-xorg-input-libinput 0.29.0-1 libinput10:amd64 1.15.5-1ubuntu0.3 GNOME Shell 3.36.9 xorg-server 2:1.20.13-1ubuntu1~20.04.3 5.15.0-46-generic Lot of errors like following in journald: ``` /usr/lib/gdm3/gdm-x-session[4273]: (EE) client bug: timer event16 debounce short: scheduled expiry is in the past (-2ms), your system is too slow /usr/lib/gdm3/gdm-x-session[4273]: (EE) client bug: timer event16 debounce: scheduled expiry is in the past (-1ms), your system is too slow ``` Other DE does not have this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870597 Title: libinput says "your system is too slow" Status in GNOME Shell: Unknown Status in libinput: Fix Released Status in Linux: Confirmed Status in libinput package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm- x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892087] [NEW] screenshot a select area does not work
Public bug reported: Shift+Prt Scrn or invoke the screenshot app then select the `select the area to grab`. After area selected the save dialogue does not show up. screenshot a window or desktop works as normal. ubuntu 20.04 ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1892087 Title: screenshot a select area does not work Status in gnome-screenshot package in Ubuntu: New Bug description: Shift+Prt Scrn or invoke the screenshot app then select the `select the area to grab`. After area selected the save dialogue does not show up. screenshot a window or desktop works as normal. ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1892087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825066] [NEW] gsd-xsettings have tons of error in syslog
Public bug reported: double monitors on nvidia card. I get tons of err like this: ``` Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist ``` ubuntu 18.04 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1825066 Title: gsd-xsettings have tons of error in syslog Status in gnome-settings-daemon package in Ubuntu: New Bug description: double monitors on nvidia card. I get tons of err like this: ``` Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist ``` ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1825066/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 693219] Re: Starting a Google Video chat crashes pidgin
The video chat still crash the latest pidign: ii pidgin 1:2.10.3-0ubuntu1.1 graphical multi-protocol instant messaging client for X -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/693219 Title: Starting a Google Video chat crashes pidgin Status in Pidgin: New Status in “pidgin” package in Ubuntu: Confirmed Bug description: Binary package hint: pidgin If I, or a buddy on my list, attempt to start a video chat on Google chat, Pidgin crashes. $ lsb_release -rd Description: Ubuntu 10.10 Release: 10.10 $ apt-cache policy pidgin pidgin: Installed: 1:2.7.3-1ubuntu3.2 Candidate: 1:2.7.3-1ubuntu3.2 Version table: *** 1:2.7.3-1ubuntu3.2 0 500 http://us.archive.ubuntu.com/ubuntu/ maverick-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:2.7.3-1ubuntu3.1 0 500 http://security.ubuntu.com/ubuntu/ maverick-security/main amd64 Packages 1:2.7.3-1ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: pidgin 1:2.7.3-1ubuntu3.2 ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7 Uname: Linux 2.6.35-23-generic x86_64 NonfreeKernelModules: wl Architecture: amd64 Date: Tue Dec 21 18:35:13 2010 EcryptfsInUse: Yes InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: pidgin To manage notifications about this bug go to: https://bugs.launchpad.net/pidgin/+bug/693219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
