wayland issueshttps://gitlab.freedesktop.org/groups/wayland/-/issues2023-06-20T21:52:36Zhttps://gitlab.freedesktop.org/wayland/wayland/-/issues/379Lowering inactive developers/maintainers to reporters2023-06-20T21:52:36ZSimon Sercontact@emersion.frLowering inactive developers/maintainers to reportersI've been looking at the list of people with push access to the wayland org. Some people have made significant contributions in the past (thanks!), but are no longer active (they haven't reviewed/merged/submitted patches in a long time)....I've been looking at the list of people with push access to the wayland org. Some people have made significant contributions in the past (thanks!), but are no longer active (they haven't reviewed/merged/submitted patches in a long time). Having a lot of people with developer/maintainer access is suboptimal regarding security: the more people have this role, the more likely credentials with write access to all repos under the org can be leaked.
It would be nice to lower the permissions of people who don't need developer/maintainer access to reporter only. The role can be increased again if these people start contributing again.
This is about the wayland org only, if someone is active in one project under the org but not others we should give them permissions on the specific project instead of the whole org.
Here is a list: @bryce, @rdp.effort, @gfxstrand, @krh, @sardemff7
Please, speak up in the next month if you want to retain your developer/maintainer access!2023-06-10https://gitlab.freedesktop.org/wayland/wayland/-/issues/378input lag mouse cursor | Cursor delay2023-05-10T11:01:39ZIgnI VerTiKalCaDinput lag mouse cursor | Cursor delayMoving the cursor on Wayland is delayed. It feels like he's lethargic. On x11 everything is fine. On Windows too. On Wayland, it feels like the cursor is 1-2 frames late for the actual movement of the mouse.
If you need a video for proof...Moving the cursor on Wayland is delayed. It feels like he's lethargic. On x11 everything is fine. On Windows too. On Wayland, it feels like the cursor is 1-2 frames late for the actual movement of the mouse.
If you need a video for proof, I can provide it in slow-mo.
Also, the problem is not in the mouse, as I tested it on two and the same problems.https://gitlab.freedesktop.org/wayland/weston/-/issues/752multiple GPU support in drm backend2023-05-11T10:44:25Zsophia gongmultiple GPU support in drm backendHi,
i'm going to enable two gpu in our system, one gpu for client gfx render, both gpu for display output. weston 11 develops a new feature to support multi backend, could this feature support multi gpu in our case? could someone introd...Hi,
i'm going to enable two gpu in our system, one gpu for client gfx render, both gpu for display output. weston 11 develops a new feature to support multi backend, could this feature support multi gpu in our case? could someone introduce more details about how multi backend implement? thanks!
Sophiahttps://gitlab.freedesktop.org/wayland/wayland/-/issues/377Some games (specially source and tf2c) dont run under wayland2023-05-03T05:51:03ZshrekniSome games (specially source and tf2c) dont run under waylandSource games and sdk-s dont start on wayland but on x11 i can start tgem and playSource games and sdk-s dont start on wayland but on x11 i can start tgem and playhttps://gitlab.freedesktop.org/wayland/weston/-/issues/749Kicad very sluggish when some of its windows are hidden2023-05-02T10:09:00ZNicolas GoyKicad very sluggish when some of its windows are hiddenHello.
First I am sorry if this is not directly a wayland, as I am trying to find what causes it.
I run wayland, with sway 1.8.1, and I use kicad under xwayland.
The issue is quite simple to explain and reproduce, if any of kicad wind...Hello.
First I am sorry if this is not directly a wayland, as I am trying to find what causes it.
I run wayland, with sway 1.8.1, and I use kicad under xwayland.
The issue is quite simple to explain and reproduce, if any of kicad window is not directly visible, the whole application becomes very sluggish, with mini freezes all over the place.
I would really like to help pinpoint and fix this issue as it is the only major issue making kicad hard to use on wayland (xwayland).
References: https://gitlab.com/kicad/code/kicad/-/issues/7207#note_1357779464https://gitlab.freedesktop.org/wayland/wayland/-/issues/375Wayland resolution options for Sony A8H TV2023-04-27T07:59:34ZCahal DallettWayland resolution options for Sony A8H TVI am using an Intel NUC to drive a Sony A8H 65" TV. I've installed Ubuntu 22.10 and 23.04, and the maximum resolution is 1920x1080. However, the Sony A8H is a 4k television. It can support 3840x2160. The NUC has Intel Iris Plus Graph...I am using an Intel NUC to drive a Sony A8H 65" TV. I've installed Ubuntu 22.10 and 23.04, and the maximum resolution is 1920x1080. However, the Sony A8H is a 4k television. It can support 3840x2160. The NUC has Intel Iris Plus Graphics 655 which should also theoretically handle 4k. I also purchased a new HDMI cable rated for 8k just to eliminate that as a potential bottleneck.
Thank you!https://gitlab.freedesktop.org/wayland/weston/-/issues/744xssstart: X11 extension MIT-SCREEN-SAVER not supported2023-04-19T12:55:14ZOquirellaxssstart: X11 extension MIT-SCREEN-SAVER not supportedI am trying to run clicklock under weston (xwayland) (https://github.com/zpfvo/clicklock) which should be started using xssstart but i get the following error message:
xssstart: X11 extension MIT-SCREEN-SAVER not supported
xdpinfo tells...I am trying to run clicklock under weston (xwayland) (https://github.com/zpfvo/clicklock) which should be started using xssstart but i get the following error message:
xssstart: X11 extension MIT-SCREEN-SAVER not supported
xdpinfo tells me only the following extensions are available:
number of extensions: 19
BIG-REQUESTS
Composite
DAMAGE
DOUBLE-BUFFER
Generic Event Extension
MIT-SHM
Present
RANDR
RENDER
SHAPE
SYNC
X-Resource
XC-MISC
XFIXES
XFree86-VidModeExtension
XInputExtension
XKEYBOARD
XTEST
XVideo
Any idea why this extension is missing or not supported?https://gitlab.freedesktop.org/wayland/weston/-/issues/743Unable to fork repository due to max limit reached2023-04-19T08:15:39ZAshwin PrabhakarUnable to fork repository due to max limit reachedHi, I am trying to fork the weston repository. I have the fork button greyed out with "You have reached your project limit". I would appreciate if someone can help me with the access.Hi, I am trying to fork the weston repository. I have the fork button greyed out with "You have reached your project limit". I would appreciate if someone can help me with the access.https://gitlab.freedesktop.org/wayland/weston/-/issues/740Assert when pressing the power button of a screen2023-06-13T16:35:18ZLink MauveAssert when pressing the power button of a screenWhen pressing the power button of a screen, it triggered an assert with this stack trace, but I couldn’t reproduce afterwards:
```rust
(gdb) bt
#0 0x00007f1f367e88ec in () at /usr/lib/libc.so.6
#1 0x00007f1f36799ea8 in raise () at /us...When pressing the power button of a screen, it triggered an assert with this stack trace, but I couldn’t reproduce afterwards:
```rust
(gdb) bt
#0 0x00007f1f367e88ec in () at /usr/lib/libc.so.6
#1 0x00007f1f36799ea8 in raise () at /usr/lib/libc.so.6
#2 0x00007f1f3678353d in abort () at /usr/lib/libc.so.6
#3 0x00007f1f3678345c in () at /usr/lib/libc.so.6
#4 0x00007f1f367929f6 in () at /usr/lib/libc.so.6
#5 0x00007f1f367158ba in weston_coord_surface_to_global (view=0xcd2a9, view@entry=0x5603ba01e710, coord=...) at ../libweston/compositor.c:722
#6 0x00007f1f305281a6 in get_panel_size (shell=0x5603ba0630a0, height=<synthetic pointer>, width=<synthetic pointer>, view=0x5603ba01e710) at ../desktop-shell/shell.c:340
#7 get_output_panel_size (height=<synthetic pointer>, width=<synthetic pointer>, output=0x5603b97a1e50, shell=0x5603ba0630a0) at ../desktop-shell/shell.c:368
#8 get_output_work_area (shell=0x5603ba0630a0, output=0x5603b97a1e50, area=area@entry=0x7ffcb6fb8ff0) at ../desktop-shell/shell.c:395
#9 0x00007f1f305296eb in get_maximized_size (height=<synthetic pointer>, width=<synthetic pointer>, shsurf=0x5603b9fbe530) at ../desktop-shell/shell.c:2506
#10 set_fullscreen (shsurf=0x5603b9fbe530, fullscreen=<optimized out>, output=0x0) at ../desktop-shell/shell.c:2539
#11 0x00007f1f3052d858 in shell_reposition_view_on_output_change (view=0x5603b9fa4bd0) at ../desktop-shell/shell.c:4678
#12 shell_output_changed_move_layer (shell=<optimized out>, layer=0x5603ba063388, data=<optimized out>) at ../desktop-shell/shell.c:4701
#13 0x00007f1f3052d8d2 in shell_for_each_layer (func=0x7f1f3052d6f0 <shell_output_changed_move_layer>, data=0x0, shell=0x5603ba0630a0) at ../desktop-shell/shell.c:4689
#14 shell_output_destroy (shell_output=0x5603ba05f6e0) at ../desktop-shell/shell.c:4710
#15 0x00007f1f3671c5fe in weston_signal_emit_mutable (data=0x5603b97a2f70, signal=0x5603b97a30c0) at ../shared/signal.c:52
#16 weston_compositor_remove_output (output=0x5603b97a2f70) at ../libweston/compositor.c:6778
#17 0x00007f1f3671c760 in weston_output_disable () at ../libweston/compositor.c:6787
#18 0x00005603ba0605d0 in ()
#19 0x00007f1f3698b28e in drm_head_disable (head=0x5603b97a2f70) at ../compositor/main.c:2564
#20 drm_heads_changed (listener=<optimized out>, arg=0x5603b9793fd0) at ../compositor/main.c:2592
#21 0x00007f1f3670f2b1 in wl_signal_emit (data=0xcd2a9, signal=0x5603b97943f8) at /usr/include/wayland-server-core.h:491
#22 weston_compositor_call_heads_changed (data=0xcd2a9) at ../libweston/compositor.c:5596
#23 0x00007f1f366dca63 in wl_event_loop_dispatch_idle (loop=loop@entry=0x5603b9791c30) at ../wayland/src/event-loop.c:969
#24 0x00007f1f366dcb74 in wl_event_loop_dispatch (loop=0x5603b9791c30, timeout=timeout@entry=-1) at ../wayland/src/event-loop.c:1032
#25 0x00007f1f366d9e67 in wl_display_run (display=0x5603b9791b40) at ../wayland/src/wayland-server.c:1471
#26 0x00007f1f3698fc37 in execute_autolaunch (config=0x5603b9791e10, wet=0x7ffcb6fb9640) at ../compositor/main.c:3692
#27 wet_main (argc=<optimized out>, argv=<optimized out>, test_data=0x0) at ../compositor/main.c:4077
#28 0x00007f1f36784790 in () at /usr/lib/libc.so.6
#29 0x00007f1f3678484a in __libc_start_main () at /usr/lib/libc.so.6
#30 0x00005603b962f055 in _start ()
```https://gitlab.freedesktop.org/wayland/weston/-/issues/738Kiosk-shell keyboard focus lost after modal dialogs2023-07-27T09:12:39ZFredrik GustafssonKiosk-shell keyboard focus lost after modal dialogsWeston 11.0.1
Open a modal dialog in the Weston kiosk shell close the dialog via keyboard actions. I.e. in a simple default "Ok" button scenario just press enter to close the dialog. After close the keyboard focus is lost and continued n...Weston 11.0.1
Open a modal dialog in the Weston kiosk shell close the dialog via keyboard actions. I.e. in a simple default "Ok" button scenario just press enter to close the dialog. After close the keyboard focus is lost and continued navigation via keyboard is not possible. Clicking with the mouse restores the keyboard focus.
The issue does not reproduce with desktop-shell.https://gitlab.freedesktop.org/wayland/weston/-/issues/737QT Modal windows issus2023-04-26T02:21:18ZNoah-LijcQT Modal windows issusMy current version of Weston is 10.0, but due to stability issues, I cannot upgrade it. However, when using QT, I found that a bug from Weston 9.0 has been fixed. This bug prevented the use of modal windows, but now after commit (a8da208...My current version of Weston is 10.0, but due to stability issues, I cannot upgrade it. However, when using QT, I found that a bug from Weston 9.0 has been fixed. This bug prevented the use of modal windows, but now after commit (a8da208453ccc748bf331e83956b85d43ef0f05f), modal windows can be used again. However, after closing a modal window and clicking on the main window, Weston crashes and commit (5699dbaae7df083e1f34ca88c37f21db669495b0) did not fix this crash bug(The Wayland connection broke. Did the Wayland compositor die?).
May I ask if this problem can be solved? Or is it the case that this issue has already been fixed in Weston 11.0? Can you provide the corresponding commit? Looking forward to your reply.https://gitlab.freedesktop.org/wayland/wayland/-/issues/373White border around screen2023-04-06T06:10:33ZTonnyWhite border around screen<!--
This repository is for the Wayland protocol description and the libwayland IPC helper
library only. Issues with Wayland during day-to-day usage are almost
certainly a bug in your compositor and **not** a bug with in this
repository....<!--
This repository is for the Wayland protocol description and the libwayland IPC helper
library only. Issues with Wayland during day-to-day usage are almost
certainly a bug in your compositor and **not** a bug with in this
repository.
Please remove this comment before filing your bug.
-->
Turn off the display and light up it after several minutes,there will be a white border around the screen.
This phenomenon only occurs with wayland.
laptop,14 inch lcd ips
i5-8250u(uhd620)+nvidia mx150
![202304041807145514_Screenshot_20230404_180700](/uploads/342cd6924def85e013019c9360450f8e/202304041807145514_Screenshot_20230404_180700.png)![downloadfile](/uploads/0abf6bcfa8cec6d2b3d3c6fd0fda4881/downloadfile.png)https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/136Desktop image protocol2023-09-02T07:24:17ZDallas StrouseDesktop image protocol[Inochi2D](https://inochi2d.com) is currently working on a UI rewrite that is based off of the Microsoft Windows Fluent design.
The [Mica](https://learn.microsoft.com/en-us/windows/apps/design/style/mica) style involves taking the backg...[Inochi2D](https://inochi2d.com) is currently working on a UI rewrite that is based off of the Microsoft Windows Fluent design.
The [Mica](https://learn.microsoft.com/en-us/windows/apps/design/style/mica) style involves taking the background, specifically a portion for the Mica Alt design, and blurring it. Wayland allows applications to have transparent areas, however there is no protocol for blurring portions of a window (there is https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/43/, however it specifies that the compositor decides how windows are blurred. This isn't desired in this case).
For the main Mica design, it seems to use the main color of the background, however that could probably be done with the help of the accent color portal.
A protocol that gives applications a portion of the background that the application is sitting on would work to allow application designs such as this. Alternatively, the whole background can be sent and a portion of it told to be used.https://gitlab.freedesktop.org/wayland/weston/-/issues/732Configure mouse button as a combination of keyboard keys2023-03-23T13:46:41ZCristian CocosConfigure mouse button as a combination of keyboard keys[Apologies if this is not the most appropriate venue for this question. Suggestions as to where to post this welcome.]
I know how to map one mouse button onto **one** keyboard key, but how do you map one mouse button onto a **combinatio...[Apologies if this is not the most appropriate venue for this question. Suggestions as to where to post this welcome.]
I know how to map one mouse button onto **one** keyboard key, but how do you map one mouse button onto a **combination of** keyboard keys? What is the HWDB syntax? This below doesn't work: the latest 9000x assignment is the one that overrides all the previous 9000x assignments. I am thus hoping that there's a way to somehow list a combination of keyboard keys onto one 9000x line. Is that even possible?
What I am trying to achieve is to map the 90004 mouse button onto `key_leftmeta + key_pagedown` and the 90005 button onto `key_leftmeta + key_pageup`. The code below actually maps 90004 onto `key_pagedown` and 90005 onto `key_pageup`.
```
# 70-mouse-remap.hwdb
# Remap buttons on Logitech M585/M590 mouse:
evdev:name:Logitech M585/M590:*
KEYBOARD_KEY_90004=key_leftmeta
KEYBOARD_KEY_90004=key_pagedown
KEYBOARD_KEY_90005=key_leftmeta
KEYBOARD_KEY_90005=key_pageup
```
Clear Linux 38620, Wayland, kernel 6.2.7https://gitlab.freedesktop.org/wayland/weston/-/issues/731Chromium not fullscreen after disconnect hdmi monitor and then reconnect2023-04-11T11:30:34ZescherstairChromium not fullscreen after disconnect hdmi monitor and then reconnectThis issue has been originally posted on [Toradex Community](https://community.toradex.com/t/chromium-not-fullscreen-after-disconnect-hdmi-monitor-and-then-reconnect/18541), but Toradex engineers think that it depends on how Weston behav...This issue has been originally posted on [Toradex Community](https://community.toradex.com/t/chromium-not-fullscreen-after-disconnect-hdmi-monitor-and-then-reconnect/18541), but Toradex engineers think that it depends on how Weston behaves.
This is what happens:
- a Chromium window is opened in kiosk mode (fullscreen) on Weston running on NXP iMX8M device
- after the HDMI cable is unplugged, and the re-plugged, the Chromium window is no more at fullscreen (you can see in the image posted on the Toradex Community).
Can someone confirm if this is a Weston behavior or not?
Thankshttps://gitlab.freedesktop.org/wayland/weston/-/issues/730assert fails for subsurface with destroyed parent2023-03-30T15:07:05ZColin Kinlochassert fails for subsurface with destroyed parentAn assert is triggered when a client interacts with a subsurface after it's parent is destroyed.
Before [this MR](https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/4197) was merged `gtkwaylandsink` would trigger [this ...An assert is triggered when a client interacts with a subsurface after it's parent is destroyed.
Before [this MR](https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/4197) was merged `gtkwaylandsink` would trigger [this assert](https://gitlab.freedesktop.org/wayland/weston/-/blob/main/libweston/compositor.c#L1589) (`assert(view->geometry.parent)`).
Weston crashes at the start of the third video when running:
```
gst-play-1.0 test.mp4 test.mp4 test.mp4 --videosink="gtkwaylandsink"
```https://gitlab.freedesktop.org/wayland/wayland/-/issues/370Java AWT, loses focus after switching between windows2023-05-11T11:16:49ZAleksanderJava AWT, loses focus after switching between windowsAfter switching between windows (using alt + tab), the window running on Java awt does not receive focus, it remains on the previous tab.After switching between windows (using alt + tab), the window running on Java awt does not receive focus, it remains on the previous tab.https://gitlab.freedesktop.org/wayland/wayland/-/issues/369libwayland-server.so.0.21.0 ends in segfault and then somehow shuts down my s...2023-03-15T10:21:10ZVeldoralibwayland-server.so.0.21.0 ends in segfault and then somehow shuts down my system.Hi
I'm currently having a problem with my device (a Lenovo T16 Gen2) running Arch Linux (Kernel 6.2.6.arch1-1) with Gnome 43.2 on Wayland 1.21.0.
When working with the device during the day, it works as intended.
But when going home fr...Hi
I'm currently having a problem with my device (a Lenovo T16 Gen2) running Arch Linux (Kernel 6.2.6.arch1-1) with Gnome 43.2 on Wayland 1.21.0.
When working with the device during the day, it works as intended.
But when going home from work, I'll lock my screen and keep it running, in case I have to work during the night-hours.
Last night I had to work on 2 a.m. and didn't see my lock-screen, moreover my GDM-login screen.
So, the device must've rebooted. When I logged in, all my programs, that I have left open, were closed.
(No data has been lost, since I save everything before going home)
While taking a look at the journalctl, I found this message:
```
kernel: gnome-shell[2257]: segfault at 0 ip 00007f1b1cae1aba sp 00007ffc1b10c400 error 4 in libwayland-server.so.0.21.0[7f1b1cae0000+8000] likely on CPU 4 (core 8, socket 0)
```
It then gets followed by alot of `systemd-coredumps`
<details><summary>Click to expand</summary><code>
Process 2257 (gnome-shell) of user 1035 dumped core.
Stack trace of thread 2257:
#0 0x00007f1b1cae1aba n/a (libwayland-server.so.0 + 0x8aba)
#1 0x00007f1b1cae601c n/a (libwayland-server.so.0 + 0xd01c)
#2 0x00007f1b1cae49e2 wl_event_loop_dispatch (libwayland-server.so.0 + 0xb9e2)
#3 0x00007f1b1d16484d n/a (libmutter-11.so.0 + 0x16484d)
#4 0x00007f1b1debeafb g_main_context_dispatch (libglib-2.0.so.0 + 0x5aafb)
#5 0x00007f1b1df1b5d9 n/a (libglib-2.0.so.0 + 0xb75d9)
#6 0x00007f1b1debe0cf g_main_loop_run (libglib-2.0.so.0 + 0x5a0cf)
#7 0x00007f1b1d0d0a6b meta_context_run_main_loop (libmutter-11.so.0 + 0xd0a6b)
#8 0x0000560e48da448d n/a (gnome-shell + 0x248d)
#9 0x00007f1b1ce3c790 n/a (libc.so.6 + 0x23790)
#10 0x00007f1b1ce3c84a __libc_start_main (libc.so.6 + 0x2384a)
#11 0x0000560e48da4715 n/a (gnome-shell + 0x2715)
Stack trace of thread 2260:
#0 0x00007f1b1cf139df __poll (libc.so.6 + 0xfa9df)
#1 0x00007f1b1df1b53f n/a (libglib-2.0.so.0 + 0xb753f)
#2 0x00007f1b1debc382 g_main_context_iteration (libglib-2.0.so.0 + 0x58382)
#3 0x00007f1b1debc3d2 n/a (libglib-2.0.so.0 + 0x583d2)
#4 0x00007f1b1deec7c5 n/a (libglib-2.0.so.0 + 0x887c5)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2268:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b05d0c4ee n/a (iris_dri.so + 0x10c4ee)
#3 0x00007f1b05cbc8bc n/a (iris_dri.so + 0xbc8bc)
#4 0x00007f1b05d0c41c n/a (iris_dri.so + 0x10c41c)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2264:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b05d0c4ee n/a (iris_dri.so + 0x10c4ee)
#3 0x00007f1b05cbc8bc n/a (iris_dri.so + 0xbc8bc)
#4 0x00007f1b05d0c41c n/a (iris_dri.so + 0x10c41c)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2271:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b05d0c4ee n/a (iris_dri.so + 0x10c4ee)
#3 0x00007f1b05cbc8bc n/a (iris_dri.so + 0xbc8bc)
#4 0x00007f1b05d0c41c n/a (iris_dri.so + 0x10c41c)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2274:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b05d0c4ee n/a (iris_dri.so + 0x10c4ee)
#3 0x00007f1b05cbc8bc n/a (iris_dri.so + 0xbc8bc)
#4 0x00007f1b05d0c41c n/a (iris_dri.so + 0x10c41c)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2275:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b05d0c4ee n/a (iris_dri.so + 0x10c4ee)
#3 0x00007f1b05cbc8bc n/a (iris_dri.so + 0xbc8bc)
#4 0x00007f1b05d0c41c n/a (iris_dri.so + 0x10c41c)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2283:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b05d0c4ee n/a (iris_dri.so + 0x10c4ee)
#3 0x00007f1b05cbc8bc n/a (iris_dri.so + 0xbc8bc)
#4 0x00007f1b05d0c41c n/a (iris_dri.so + 0x10c41c)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2282:
#0 0x00007f1b1cf139df __poll (libc.so.6 + 0xfa9df)
#1 0x00007f1b1df1b53f n/a (libglib-2.0.so.0 + 0xb753f)
#2 0x00007f1b1debc382 g_main_context_iteration (libglib-2.0.so.0 + 0x58382)
#3 0x00007f1b14162fde n/a (libdconfsettings.so + 0x5fde)
#4 0x00007f1b1deec7c5 n/a (libglib-2.0.so.0 + 0x887c5)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2372:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b1b5965a1 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so + 0x15965a1)
#3 0x00007f1b1b5964a2 n/a (libmozjs-102.so + 0x15964a2)
#4 0x00007f1b1b74783e n/a (libmozjs-102.so + 0x174783e)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2370:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b1b5965a1 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so + 0x15965a1)
#3 0x00007f1b1b5964a2 n/a (libmozjs-102.so + 0x15964a2)
#4 0x00007f1b1b74783e n/a (libmozjs-102.so + 0x174783e)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 6434:
#0 0x00007f1b1cf139df __poll (libc.so.6 + 0xfa9df)
#1 0x00007f1aa076e8c7 n/a (libpulse.so.0 + 0x338c7)
#2 0x00007f1aa075846c pa_mainloop_poll (libpulse.so.0 + 0x1d46c)
#3 0x00007f1aa076242c pa_mainloop_iterate (libpulse.so.0 + 0x2742c)
#4 0x00007f1aa07624e1 pa_mainloop_run (libpulse.so.0 + 0x274e1)
#5 0x00007f1aa0772c02 n/a (libpulse.so.0 + 0x37c02)
#6 0x00007f1aa070fc67 n/a (libpulsecommon-16.1.so + 0x5bc67)
#7 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#8 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2375:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b1b5965a1 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so + 0x15965a1)
#3 0x00007f1b1b5964a2 n/a (libmozjs-102.so + 0x15964a2)
#4 0x00007f1b1b74783e n/a (libmozjs-102.so + 0x174783e)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2374:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b1b5965a1 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so + 0x15965a1)
#3 0x00007f1b1b5964a2 n/a (libmozjs-102.so + 0x15964a2)
#4 0x00007f1b1b74783e n/a (libmozjs-102.so + 0x174783e)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2288:
#0 0x00007f1b1cf139df __poll (libc.so.6 + 0xfa9df)
#1 0x00007f1b1df1b53f n/a (libglib-2.0.so.0 + 0xb753f)
#2 0x00007f1b1debe0cf g_main_loop_run (libglib-2.0.so.0 + 0x5a0cf)
#3 0x00007f1b1d1d18f1 n/a (libmutter-11.so.0 + 0x1d18f1)
#4 0x00007f1b1deec7c5 n/a (libglib-2.0.so.0 + 0x887c5)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2273:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b05d0c4ee n/a (iris_dri.so + 0x10c4ee)
#3 0x00007f1b05cbc8bc n/a (iris_dri.so + 0xbc8bc)
#4 0x00007f1b05d0c41c n/a (iris_dri.so + 0x10c41c)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2371:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b1b5965a1 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so + 0x15965a1)
#3 0x00007f1b1b5964a2 n/a (libmozjs-102.so + 0x15964a2)
#4 0x00007f1b1b74783e n/a (libmozjs-102.so + 0x174783e)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2269:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b05d0c4ee n/a (iris_dri.so + 0x10c4ee)
#3 0x00007f1b05cbc8bc n/a (iris_dri.so + 0xbc8bc)
#4 0x00007f1b05d0c41c n/a (iris_dri.so + 0x10c41c)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2267:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b05d0c4ee n/a (iris_dri.so + 0x10c4ee)
#3 0x00007f1b05cbc8bc n/a (iris_dri.so + 0xbc8bc)
#4 0x00007f1b05d0c41c n/a (iris_dri.so + 0x10c41c)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2272:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b05d0c4ee n/a (iris_dri.so + 0x10c4ee)
#3 0x00007f1b05cbc8bc n/a (iris_dri.so + 0xbc8bc)
#4 0x00007f1b05d0c41c n/a (iris_dri.so + 0x10c41c)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2265:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b05d0c4ee n/a (iris_dri.so + 0x10c4ee)
#3 0x00007f1b05cbc8bc n/a (iris_dri.so + 0xbc8bc)
#4 0x00007f1b05d0c41c n/a (iris_dri.so + 0x10c41c)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2266:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b05d0c4ee n/a (iris_dri.so + 0x10c4ee)
#3 0x00007f1b05cbc8bc n/a (iris_dri.so + 0xbc8bc)
#4 0x00007f1b05d0c41c n/a (iris_dri.so + 0x10c41c)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2373:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b1b5965a1 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so + 0x15965a1)
#3 0x00007f1b1b5964a2 n/a (libmozjs-102.so + 0x15964a2)
#4 0x00007f1b1b74783e n/a (libmozjs-102.so + 0x174783e)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2259:
#0 0x00007f1b1cf190dd syscall (libc.so.6 + 0x1000dd)
#1 0x00007f1b1df0fa35 g_cond_wait (libglib-2.0.so.0 + 0xaba35)
#2 0x00007f1b1de88fc4 n/a (libglib-2.0.so.0 + 0x24fc4)
#3 0x00007f1b1deee43e n/a (libglib-2.0.so.0 + 0x8a43e)
#4 0x00007f1b1deec7c5 n/a (libglib-2.0.so.0 + 0x887c5)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2262:
#0 0x00007f1b1cf139df __poll (libc.so.6 + 0xfa9df)
#1 0x00007f1b1df1b53f n/a (libglib-2.0.so.0 + 0xb753f)
#2 0x00007f1b1debe0cf g_main_loop_run (libglib-2.0.so.0 + 0x5a0cf)
#3 0x00007f1b1e11fe4c n/a (libgio-2.0.so.0 + 0x10fe4c)
#4 0x00007f1b1deec7c5 n/a (libglib-2.0.so.0 + 0x887c5)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2286:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b05d0c4ee n/a (iris_dri.so + 0x10c4ee)
#3 0x00007f1b05cbc8bc n/a (iris_dri.so + 0xbc8bc)
#4 0x00007f1b05d0c41c n/a (iris_dri.so + 0x10c41c)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 39022:
#0 0x00007f1b1cf190dd syscall (libc.so.6 + 0x1000dd)
#1 0x00007f1b1df0fff3 g_cond_wait_until (libglib-2.0.so.0 + 0xabff3)
#2 0x00007f1b1de88f93 n/a (libglib-2.0.so.0 + 0x24f93)
#3 0x00007f1b1de89137 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x25137)
#4 0x00007f1b1deeee06 n/a (libglib-2.0.so.0 + 0x8ae06)
#5 0x00007f1b1deec7c5 n/a (libglib-2.0.so.0 + 0x887c5)
#6 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#7 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2368:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b1b5965a1 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so + 0x15965a1)
#3 0x00007f1b1b5964a2 n/a (libmozjs-102.so + 0x15964a2)
#4 0x00007f1b1b74783e n/a (libmozjs-102.so + 0x174783e)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2369:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b1b5965a1 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so + 0x15965a1)
#3 0x00007f1b1b5964a2 n/a (libmozjs-102.so + 0x15964a2)
#4 0x00007f1b1b74783e n/a (libmozjs-102.so + 0x174783e)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2270:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b05d0c4ee n/a (iris_dri.so + 0x10c4ee)
#3 0x00007f1b05cbc8bc n/a (iris_dri.so + 0xbc8bc)
#4 0x00007f1b05d0c41c n/a (iris_dri.so + 0x10c41c)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 2263:
#0 0x00007f1b1ce9b766 n/a (libc.so.6 + 0x82766)
#1 0x00007f1b1ce9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
#2 0x00007f1b05d0c4ee n/a (iris_dri.so + 0x10c4ee)
#3 0x00007f1b05cbc8bc n/a (iris_dri.so + 0xbc8bc)
#4 0x00007f1b05d0c41c n/a (iris_dri.so + 0x10c41c)
#5 0x00007f1b1ce9ebb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007f1b1cf20d90 n/a (libc.so.6 + 0x107d90)
ELF object binary architecture: AMD x86-64
</code></details>
After that happened, all services report a `Broken Pipe` or `Connection reset by peer`...
<details><summary>Click to expand</summary><code>
Mar 14 22:11:54 systemd[1]: systemd-coredump@0-39059-0.service: Deactivated successfully.
Mar 14 22:11:54 evince[31439]: Error reading events from display: Broken pipe
Mar 14 22:11:54 xdg-desktop-por[2706]: Error reading events from display: Broken pipe
Mar 14 22:11:54 nautilus[4159]: Error reading events from display: Broken pipe
Mar 14 22:11:54 flameshot[2504]: Error reading events from display: Connection reset by peer
Mar 14 22:11:54 polkitd[1151]: Unregistered Authentication Agent for unix-session:3 (system bus name :1.60, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Mar 14 22:11:54 xdg-desktop-por[2631]: Error reading events from display: Connection reset by peer
Mar 14 22:11:54 gsd-wacom[2525]: Error reading events from display: Broken pipe
Mar 14 22:11:54 gsd-color[2482]: Error reading events from display: Broken pipe
Mar 14 22:11:54 gsd-keyboard[2489]: Error reading events from display: Broken pipe
Mar 14 22:11:54 thunderbird[3652]: Error reading events from display: Connection reset by peer
Mar 14 22:11:54 chromium.desktop[3891]: X connection to :0 broken (explicit kill or server shutdown).
Mar 14 22:11:54 chromium.desktop[3891]: [3891:3970:0314/221154.801454:ERROR:connection.cc(46)] X connection error received.
Mar 14 22:11:54 gnome-shell[2657]: (EE) failed to write to Xwayland fd: Broken pipe
Mar 14 22:11:54 Web Content[3894]: Error reading events from display: Broken pipe
Mar 14 22:11:54 gsd-media-keys[2492]: Error reading events from display: Broken pipe
Mar 14 22:11:54 systemd[2143]: org.gnome.Shell@wayland.service: Main process exited, code=dumped, status=11/SEGV
Mar 14 22:11:54 systemd[2143]: org.gnome.SettingsDaemon.Wacom.service: Main process exited, code=exited, status=1/FAILURE
Mar 14 22:11:54 gsd-xsettings[2729]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Mar 14 22:11:54 gsd-power[2494]: Error reading events from display: Broken pipe
Mar 14 22:11:54 gsd-xsettings[2729]: xft_settings_set_xresources: assertion 'dpy != NULL' failed
Mar 14 22:11:54 gsd-xsettings[2729]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist
Mar 14 22:11:54 gsd-xsettings[2729]: xft_settings_set_xresources: assertion 'dpy != NULL' failed
Mar 14 22:11:54 gsd-xsettings[2729]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist
Mar 14 22:11:54 gsd-xsettings[2729]: xft_settings_set_xresources: assertion 'dpy != NULL' failed
Mar 14 22:11:54 gsd-xsettings[2729]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist
Mar 14 22:11:54 gsd-xsettings[2729]: xft_settings_set_xresources: assertion 'dpy != NULL' failed
</code></details>
The services start to fail with exit-code...
<details><summary>Click to expand</summary><code>
Mar 14 22:11:54 systemd[2143]: org.gnome.SettingsDaemon.Color.service: Main process exited, code=exited, status=1/FAILURE
Mar 14 22:11:54 systemd[2143]: org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, status=1/FAILURE
Mar 14 22:11:54 systemd[2143]: org.gnome.SettingsDaemon.MediaKeys.service: Main process exited, code=exited, status=1/FAILURE
Mar 14 22:11:54 systemd[2143]: org.gnome.SettingsDaemon.Power.service: Main process exited, code=exited, status=1/FAILURE
Mar 14 22:11:54 systemd[2143]: xdg-desktop-portal-gnome.service: Main process exited, code=exited, status=1/FAILURE
Mar 14 22:11:54 systemd[2143]: xdg-desktop-portal-gnome.service: Failed with result 'exit-code'.
Mar 14 22:11:54 systemd[2143]: xdg-desktop-portal-gnome.service: Consumed 32.202s CPU time.
Mar 14 22:11:54 systemd[2143]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Mar 14 22:11:54 systemd[2143]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Mar 14 22:11:54 systemd[2143]: org.gnome.SettingsDaemon.XSettings.service: Main process exited, code=exited, status=1/FAILURE
Mar 14 22:11:54 systemd[2143]: org.gnome.SettingsDaemon.Wacom.service: Failed with result 'exit-code'.
Mar 14 22:11:54 systemd[2143]: org.gnome.SettingsDaemon.Color.service: Failed with result 'exit-code'.
Mar 14 22:11:54 systemd[2143]: org.gnome.SettingsDaemon.Keyboard.service: Failed with result 'exit-code'.
Mar 14 22:11:54 systemd[2143]: org.gnome.SettingsDaemon.MediaKeys.service: Failed with result 'exit-code'.
Mar 14 22:11:54 systemd[2143]: org.gnome.SettingsDaemon.Power.service: Failed with result 'exit-code'.
Mar 14 22:11:54 systemd[2143]: app-gnome-Flameshot-2504.scope: Consumed 3.431s CPU time.
Mar 14 22:11:54 systemd[2143]: org.gnome.SettingsDaemon.XSettings.service: Failed with result 'exit-code'.
Mar 14 22:11:54 systemd[2143]: app-gnome-thunderbird-3652.scope: Consumed 3min 35.636s CPU time.
Mar 14 22:11:54 systemd[2143]: org.gnome.Shell@wayland.service: Failed with result 'core-dump'.
Mar 14 22:11:54 systemd[2143]: org.gnome.Shell@wayland.service: Triggering OnFailure= dependencies
</code></details>
And finally, the services begin to stop...
<details><summary>Click to expand</summary><code>
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME Wayland Session (session: gnome).
Mar 14 22:11:54 systemd[2143]: Stopped target Current graphical user session.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME Session.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME Wayland Session.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME session X11 services.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME Session (session: gnome).
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME accessibility target.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME color management target.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME date & time target.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME maintenance of expirable data target.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME keyboard configuration target.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME keyboard shortcuts target.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME power management target.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME printer notifications target.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME RFKill support target.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME FreeDesktop screensaver target.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME file sharing target.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME smartcard target.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME sound sample caching target.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME USB protection target.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME Wacom tablet support target.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME XSettings target.
Mar 14 22:11:54 systemd[2143]: Stopping Accessibility services bus...
Mar 14 22:11:54 systemd[2143]: Stopping Virtual filesystem service...
Mar 14 22:11:54 systemd[2143]: Stopping Virtual filesystem metadata service...
Mar 14 22:11:54 systemd[2143]: Stopping Virtual filesystem service - disk device monitor...
Mar 14 22:11:54 systemd[2143]: Stopping GNOME accessibility service...
Mar 14 22:11:54 systemd[2143]: Stopped GNOME color management service.
Mar 14 22:11:54 systemd[2143]: Stopping GNOME date & time service...
Mar 14 22:11:54 systemd[2143]: Stopping GNOME maintenance of expirable data service...
Mar 14 22:11:54 systemd[2143]: Stopped GNOME keyboard configuration service.
Mar 14 22:11:54 systemd[2143]: Stopped GNOME keyboard shortcuts service.
Mar 14 22:11:54 systemd[2143]: Stopped GNOME power management service.
Mar 14 22:11:54 systemd[2143]: Stopping GNOME printer notifications service...
Mar 14 22:11:54 systemd[2143]: Stopping GNOME RFKill support service...
Mar 14 22:11:54 systemd[2143]: Stopping GNOME FreeDesktop screensaver service...
Mar 14 22:11:54 systemd[2143]: Stopping GNOME file sharing service...
Mar 14 22:11:54 systemd[2143]: Stopping GNOME smartcard service...
Mar 14 22:11:54 systemd[2143]: Stopping GNOME sound sample caching service...
Mar 14 22:11:54 systemd[2143]: Stopping GNOME USB protection service...
Mar 14 22:11:54 systemd[2143]: Stopped GNOME Wacom tablet support service.
Mar 14 22:11:54 systemd[2143]: Stopped GNOME XSettings service.
Mar 14 22:11:54 systemd[2143]: Stopped target GNOME session X11 services.
Mar 14 22:11:54 systemd[2143]: Disable GNOME Shell extensions after failure was skipped because of an unmet condition check (ConditionPathExists=/run/user/1035/gnome-shell-disable-extensions).
Mar 14 22:11:54 systemd[2143]: Stopping Portal service...
Mar 14 22:11:54 systemd[2143]: Stopping flatpak document portal service...
Mar 14 22:11:54 systemd[2143]: Stopping sandboxed app permission store...
Mar 14 22:11:54 systemd[2143]: Stopped Virtual filesystem metadata service.
Mar 14 22:11:54 systemd[2143]: Stopped sandboxed app permission store.
Mar 14 22:11:54 kernel: rfkill: input handler enabled
Mar 14 22:11:54 tracker-miner-f[2798]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Mar 14 22:11:54 systemd[2143]: Stopped Virtual filesystem service - disk device monitor.
Mar 14 22:11:54 systemd[2143]: Stopped flatpak document portal service.
Mar 14 22:11:54 systemd[1]: run-user-1035-doc.mount: Deactivated successfully.
Mar 14 22:11:54 systemd[1]: run-user-1035-gvfs.mount: Deactivated successfully.
Mar 14 22:11:54 systemd[2143]: Stopped GNOME FreeDesktop screensaver service.
Mar 14 22:11:54 systemd[2143]: Stopped GNOME smartcard service.
Mar 14 22:11:54 systemd[2143]: Stopped GNOME date & time service.
Mar 14 22:11:54 systemd[2143]: Stopped GNOME maintenance of expirable data service.
Mar 14 22:11:54 systemd[2143]: org.gnome.SettingsDaemon.Housekeeping.service: Consumed 1.575s CPU time.
Mar 14 22:11:54 systemd[2143]: Stopped GNOME RFKill support service.
Mar 14 22:11:54 systemd[2143]: Stopped GNOME accessibility service.
Mar 14 22:11:54 systemd[2143]: Stopped GNOME file sharing service.
Mar 14 22:11:54 systemd[2143]: Stopped GNOME sound sample caching service.
Mar 14 22:11:54 systemd[2143]: Stopped Accessibility services bus.
Mar 14 22:11:54 systemd[2143]: Stopped GNOME USB protection service.
Mar 14 22:11:54 systemd[2143]: Stopped Portal service.
Mar 14 22:11:54 systemd[2143]: xdg-desktop-portal.service: Consumed 1.525s CPU time.
Mar 14 22:11:54 systemd[2143]: Stopped Virtual filesystem service.
</code></details>
After a while, it seems that the system is shutting down.
```
Mar 14 22:12:01 systemd[2143]: Stopped target Tasks to be run before GNOME Session starts.
Mar 14 22:12:01 systemd[2143]: Stopped target Session services which should run early before the graphical session is brought up.
Mar 14 22:12:01 systemd[2143]: Reached target Shutdown running GNOME Session.
Mar 14 22:12:01 systemd[2143]: Stopping Monitor Session leader for GNOME Session...
Mar 14 22:12:01 systemd[2143]: Starting Restart DBus after GNOME Session shutdown...
Mar 14 22:12:01 systemd[2143]: Stopped target Shutdown running GNOME Session.
Mar 14 22:12:01 systemd[2143]: Reached target Shutdown running GNOME Session.
Mar 14 22:12:01 systemd[2143]: Stopped target Shutdown running GNOME Session.
```
Since I've reinstalled the system two days ago, I can only say how it was since then. And since I've reinstalled the device, I've got the phenomena every time. Yesterday I've noticed it only in the morning, but I wasn't quite sure, if I logged out or locked the system. But the log from that night tells me, that the system did the same again:
```
Mar 13 20:21:35 kernel: gnome-shell[34245]: segfault at 0 ip 00007faff8bd9aba sp 00007ffdd1c433b0 error 4 in libwayland-server.so.0.21.0[7faff8bd8000+8000] likely on CPU 2 (core 4, socket 0)
Mar 14 22:11:53 kernel: gnome-shell[2257]: segfault at 0 ip 00007f1b1cae1aba sp 00007ffc1b10c400 error 4 in libwayland-server.so.0.21.0[7f1b1cae0000+8000] likely on CPU 4 (core 8, socket 0)
```
> Crontab is not installed, just for those who might think, that I have a cronjob running, that shuts down my system automatically.
Am I doing something wrong or is there a bug in wayland?
Because it's quite annoying, when the notebook doesn't work like it should.
Thanks for taking time for my issue.
~ Veldorahttps://gitlab.freedesktop.org/wayland/wayland/-/issues/368Gnome Shell + Wayland + Telegram + Screen Locking = CRASH2023-03-15T10:21:10ZМарк КоренбергGnome Shell + Wayland + Telegram + Screen Locking = CRASHsee
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6503
and
https://github.com/telegramdesktop/tdesktop/issues/25892
.
In short, Gnome-Shell segfaults every time I lock the screen if Telegram is running. Before, TG was crashing ev...see
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6503
and
https://github.com/telegramdesktop/tdesktop/issues/25892
.
In short, Gnome-Shell segfaults every time I lock the screen if Telegram is running. Before, TG was crashing every time. After investigation they fix something in locking. And now GnomeShell\\Wayland crashes, so I basically can not debug Telegram.
I have unusual configuration of displays (the embedded screen of my laptop is high-res and switched off. main disaply is external one (HDMI)). Crash does not happen if I lock the screen with unplugged external monitor of my laptop.
Please tell me how to debug.
```
gnome-shell[660893]: segfault at 0 ip 00007fd2eda73709 sp 00007fff0f6cc3f0 error 4 in libwayland-server.so.0.21.0[7fd2eda71000+8000] likely on CPU 0 (core 0, socket 0)
```https://gitlab.freedesktop.org/wayland/wayland/-/issues/367xwayland on nvidia causes flickering and wierd framebuffer bugs2023-05-11T11:16:27ZLeah filler-namexwayland on nvidia causes flickering and wierd framebuffer bugsI recently got sway working with my nvidia gpu, and it was working perfectly, except for when i recompiled sway with xwayland, then wierd flickering came up, and framebuffer bugs and all sorts of wierd behaviour. I don't think this is a ...I recently got sway working with my nvidia gpu, and it was working perfectly, except for when i recompiled sway with xwayland, then wierd flickering came up, and framebuffer bugs and all sorts of wierd behaviour. I don't think this is a bug with my compositor as this didn'ẗ happen before enabling xwayland. ( i'm new to wayland, xwayland, and stuff like that so i don't even know if this is the right place to report this ) I have attatched a video that shows some of the stuff i'm seeing. I also notice that some windows or even regions of windows turn completely black at random times. ( video file: https://static.realfx.rocks/tmp/IMG_3180.mov )
Thanks in advance for any help or responses !