|
Bugzilla – Full Text Bug Listing |
| Summary: | Gnome login failure due to Xwayland crash | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Andreas Strand <8494> |
| Component: | GNOME | Assignee: | Daike Yu <yu.daike> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | 8494, hvdheuvel, qzhao, sndirsch, Ulrich.Windl, xiaoguang.wang, yfjiang, yu.daike |
| Version: | Leap 15.3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
supportconfig
supportconfig coredump messages.txt journalctl journalctl |
||
|
Description
Andreas Strand
2021-03-28 10:35:02 UTC
Hi Andreas, Thanks for reporting, to gather the log, please set Enable=True in the [debug] section of /etc/gdm/custom.conf and reboot. After reboot, reproduce the issue, then attach the supportconfig (in supportutils package) tarball. Finally, if there is a relevant coredump file (eg. gnome-shell, gdm etc.), would you also possibly attach it please. Created attachment 847836 [details]
supportconfig
Hi Yifan,
Found this in messages.txt. Maybe could be related.
2021-03-30T20:05:39.515138+02:00 localhost gnome-shell[2539]: Connection to xwayland lost
Not sure how to find core dump files. Or if there are any.
When logging in as wayland session, there were error: > 2021-03-30T20:05:24.162528+02:00 localhost gnome-shell[2365]: The XKEYBOARD keymap compiler (xkbcomp) reports: > 2021-03-30T20:05:24.162637+02:00 localhost gnome-shell[2365]: > Internal error: Could not resolve keysym XF86WWAN > 2021-03-30T20:05:24.162737+02:00 localhost gnome-shell[2365]: > Internal error: Could not resolve keysym XF86RFKill > 2021-03-30T20:05:24.162835+02:00 localhost gnome-shell[2365]: Errors from xkbcomp are not fatal to the X server When logging in as X session, there were error: > 2021-03-30T20:05:53.472384+02:00 localhost /usr/lib/gdm/gdm-x-session[3164]: (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6) > 2021-03-30T20:05:53.472425+02:00 localhost /usr/lib/gdm/gdm-x-session[3164]: (**) Option "xkb_model" "pc105" > 2021-03-30T20:05:53.472483+02:00 localhost /usr/lib/gdm/gdm-x-session[3164]: (**) Option "xkb_layout" "se" > 2021-03-30T20:05:53.472532+02:00 localhost /usr/lib/gdm/gdm-x-session[3164]: (**) Option "xkb_options" "terminate:ctrl_alt_bksp" > 2021-03-30T20:05:53.494640+02:00 localhost /usr/lib/gdm/gdm-x-session[3182]: The XKEYBOARD keymap compiler (xkbcomp) reports: > 2021-03-30T20:05:53.494749+02:00 localhost /usr/lib/gdm/gdm-x-session[3182]: > Internal error: Could not resolve keysym XF86WWAN > 2021-03-30T20:05:53.494835+02:00 localhost /usr/lib/gdm/gdm-x-session[3182]: > Internal error: Could not resolve keysym XF86RFKill Could you change keyboard layout to English, then do the test. (In reply to xiaoguang wang from comment #3) Sorry the format is not right. When logging in as X session, there were error: > 2021-03-30T20:05:53.472384+02:00 localhost /usr/lib/gdm/gdm-x-session[3164]: (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6) > 2021-03-30T20:05:53.472425+02:00 localhost /usr/lib/gdm/gdm-x-session[3164]: (**) Option "xkb_model" "pc105" > 2021-03-30T20:05:53.472483+02:00 localhost /usr/lib/gdm/gdm-x-session[3164]: (**) Option "xkb_layout" "se" > 2021-03-30T20:05:53.472532+02:00 localhost /usr/lib/gdm/gdm-x-session[3164]: (**) Option "xkb_options" "terminate:ctrl_alt_bksp" > 2021-03-30T20:05:53.494640+02:00 localhost /usr/lib/gdm/gdm-x-session[3182]: The XKEYBOARD keymap compiler (xkbcomp) reports: > 2021-03-30T20:05:53.494749+02:00 localhost /usr/lib/gdm/gdm-x-session[3182]: > Internal error: Could not resolve keysym XF86WWAN > 2021-03-30T20:05:53.494835+02:00 localhost /usr/lib/gdm/gdm-x-session[3182]: > Internal error: Could not resolve keysym XF86RFKill Could you change keyboard layout to English, then do the test. Hi Andreas, Except for what xiaoguang mentioned, here is some ideas about the coredump: https://doc.opensuse.org/documentation/leap/tuning/html/book-sle-tuning/cha-tuning-systemd-coredump.html So "coredumpctl" could give some hint here, and usually the coredump file could be found in /var/lib/systemd/coredump/. It makes sense to upload the most recent core dumps somewhere (depending on the file size). From the log in the comment#2, you might be able to find the coredump for XWalyand. Created attachment 847917 [details]
supportconfig
Created attachment 847918 [details]
coredump
Hi Yifan and Xiaoguang, thank you for the coredump instructions. In messages.txt I found: 2021-04-01T15:27:12.182457+02:00 localhost gnome-shell[19543]: (EE) Segmentation fault at address 0x18 2021-04-01T15:27:12.182584+02:00 localhost gnome-shell[19543]: Fatal server error: 2021-04-01T15:27:12.182648+02:00 localhost gnome-shell[19543]: (EE) Caught signal 11 (Segmentation fault). Server aborting 2021-04-01T15:27:13.063372+02:00 localhost systemd-coredump[19869]: Process 19543 (Xwayland) of user 1000 dumped core. I also tried with English(US) keyboard, there was no difference. I was not able to login with option Gnome. I also tried without my external MS 600 USB keyboard, there was no difference, I was not able to login with option Gnome. I uploaded most recent supportconfig and most recent core dump. (In reply to Andreas Strand from comment #8) > I also tried with English(US) keyboard, there was no difference. I was not > able to login with option Gnome. > I also tried without my external MS 600 USB keyboard, there was no > difference, I was not able to login with option Gnome. > > I uploaded most recent supportconfig and most recent core dump. In the log I find the keyboard layout is still "se", it was not changed. > 2021-04-01T15:19:24.767717+02:00 localhost /usr/lib/gdm/gdm-x-session[12811]: #011Option "XkbLayout" "se" You can use Yast->"System keyboard Layout" to change it. And I has one question, the system was fresh installed, was the home folder of user me__10 created newly or used in previous system? Created attachment 847954 [details]
messages.txt
2021-04-02T15:50:51.354704+02:00 localhost /usr/lib/gdm/gdm-x-session[12934]: The XKEYBOARD keymap compiler (xkbcomp) reports:
2021-04-02T15:50:51.354801+02:00 localhost /usr/lib/gdm/gdm-x-session[12934]: > Internal error: Could not resolve keysym XF86WWAN
2021-04-02T15:50:51.354852+02:00 localhost /usr/lib/gdm/gdm-x-session[12934]: > Internal error: Could not resolve keysym XF86RFKill
2021-04-02T15:50:51.377317+02:00 localhost /usr/lib/gdm/gdm-x-session[12917]: #011Option "XkbLayout" "us"
Yes, the home folder me__10 should have been created during install. I also created another user with another home folder, same result. I changed the keyboard layout but probably run the supportconfig out of order, sorry about that. I uploaded messages.txt again after new test with US keyboard. Same result, unable to login option Gnome. I'm thinking I will download the ISO and do a fresh install again. To find out if the problem persist. I will name the home folder something else this time. Just to make sure. Hello Yifan and Xiaoguang, I have reinstalled system with latest iso. New home folder. Unfortunatly problem persists. Enable gdm debug info, Change file /etc/gdm/custom.conf [debug] # Uncomment the line below to turn on debugging Enable=true Reproduce the issue, then collect the log by command: journalctl -b Created attachment 848216 [details]
journalctl
Quick analysis of the coredump suggests that Xwayland crashed on a NULL pointer dereference in glamor_egl_fds_from_pixmap(): > (gdb) bt > #0 0x00007f7a6efc118b in raise () from /lib64/libc.so.6 > #1 0x00007f7a6efc2585 in abort () from /lib64/libc.so.6 > #2 0x0000564e6ef7800a in OsAbort () at utils.c:1350 > #3 0x0000564e6ef7db53 in AbortServer () at log.c:879 > #4 0x0000564e6ef7e975 in FatalError (f=f@entry=0x564e6efa0f70 "Caught signal %d (%s). Server aborting\n") at log.c:1017 > #5 0x0000564e6ef750a3 in OsSigHandler (signo=11, sip=<optimized out>, unused=<optimized out>) at osinit.c:156 > #6 <signal handler called> > #7 glamor_egl_fds_from_pixmap (screen=screen@entry=0x564e6ff7ebc0, pixmap=pixmap@entry=0x564e70e74850, fds=fds@entry=0x7fff86d64bf0, > strides=strides@entry=0x7fff86d64c00, offsets=offsets@entry=0x7fff86d64c10, modifier=modifier@entry=0x7fff86d64bc0) at xwayland-glamor-gbm.c:524 > #8 0x0000564e6ee2679a in _glamor_fds_from_pixmap (screen=0x564e6ff7ebc0, pixmap=0x564e70e74850, fds=0x7fff86d64bf0, strides=0x7fff86d64c00, offsets=0x7fff86d64c10, > size=0x0, modifier=0x7fff86d64bc0) at glamor.c:848 > #9 0x0000564e6ee27fee in glamor_fds_from_pixmap (screen=<optimized out>, pixmap=<optimized out>, fds=<optimized out>, strides=<optimized out>, > offsets=<optimized out>, modifier=<optimized out>) at glamor.c:870 > #10 0x0000564e6eedb889 in dri3_fds_from_pixmap (pixmap=<optimized out>, fds=fds@entry=0x7fff86d64bf0, strides=strides@entry=0x7fff86d64c00, > offsets=offsets@entry=0x7fff86d64c10, modifier=modifier@entry=0x7fff86d64bc0) at dri3_screen.c:96 > #11 0x0000564e6eedb2d4 in proc_dri3_buffers_from_pixmap (client=0x564e70e89490) at dri3_request.c:522 > #12 0x0000564e6ef3f038 in Dispatch () at dispatch.c:478 > #13 0x0000564e6ef4303c in dix_main (argc=14, argv=0x7fff86d64e18, envp=<optimized out>) at main.c:280 > #14 0x00007f7a6efac34d in __libc_start_main () from /lib64/libc.so.6 > #15 0x0000564e6ee1a23a in _start () at ../sysdeps/x86_64/start.S:120 > (gdb) frame 7 > #7 glamor_egl_fds_from_pixmap (screen=screen@entry=0x564e6ff7ebc0, pixmap=pixmap@entry=0x564e70e74850, fds=fds@entry=0x7fff86d64bf0, > strides=strides@entry=0x7fff86d64c00, offsets=offsets@entry=0x7fff86d64c10, modifier=modifier@entry=0x7fff86d64bc0) at xwayland-glamor-gbm.c:524 > 524 if (!xwl_pixmap->bo) > (gdb) l glamor_egl_fds_from_pixmap > 510 > 511 _X_EXPORT int > 512 glamor_egl_fds_from_pixmap(ScreenPtr screen, PixmapPtr pixmap, int *fds, > 513 uint32_t *strides, uint32_t *offsets, > 514 uint64_t *modifier) > 515 { > 516 struct xwl_pixmap *xwl_pixmap; > 517 #ifdef GBM_BO_WITH_MODIFIERS > 518 uint32_t num_fds; > 519 int i; > (gdb) > 520 #endif > 521 > 522 xwl_pixmap = xwl_pixmap_get(pixmap); > 523 > 524 if (!xwl_pixmap->bo) > 525 return 0; > 526 > 527 #ifdef GBM_BO_WITH_MODIFIERS > 528 num_fds = gbm_bo_get_plane_count(xwl_pixmap->bo); > 529 *modifier = gbm_bo_get_modifier(xwl_pixmap->bo); > (gdb) which looks like https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/47/diffs?commit_id=036794bebce72a3fa2f95996d2e537ff568e0ff1 to me. This upstream fix is shipped in xorg-server 1.20.4, a newer version than that in Leap 15.3 (1.20.3). I've put together a temporary fix at https://build.opensuse.org/package/show/home:yudaike:branches:SUSE:SLE-15-SP2:Update/xorg-x11-server. Would you please check if that makes any difference? Thanks. Andreas, you'll need to update xorg-x11-server-wayland package in https://download.opensuse.org/repositories/home:/yudaike:/branches:/SUSE:/SLE-15-SP2:/Update/pool-leap-15.3/x86_64/ *** Bug 1184543 has been marked as a duplicate of this bug. *** (In reply to Stefan Dirsch from comment #18) > *** Bug 1184543 has been marked as a duplicate of this bug. *** After installation (not GNOME Live) it seems I could not log in (there was no error message, just the GNOME login reappeared after having entered use and password), when in fact wayland had crashed (AMD Ryzen 4700 in a Lenovo E15 2nd gen). I managed to log in using the setting "GNOME with X11". There should be some useful indication to the user if wayland crashed. Maybe wayland just isn't ready for the users. (In reply to Ulrich Windl from comment #20) > (In reply to Stefan Dirsch from comment #18) > > *** Bug 1184543 has been marked as a duplicate of this bug. *** > > After installation (not GNOME Live) it seems I could not log in (there was > no error message, just the GNOME login reappeared after having entered use > and password), when in fact wayland had crashed (AMD Ryzen 4700 in a Lenovo > E15 2nd gen). I managed to log in using the setting "GNOME with X11". > > There should be some useful indication to the user if wayland crashed. Maybe > wayland just isn't ready for the users. And this is now with or without the fix i.e an updated xorg-x11-server-wayland package? Sorry for the delay, I caught up in work. I installed server, server-extra and server-wayland from https://download.opensuse.org/repositories/home:/yudaike:/branches:/SUSE:/SLE-15-SP2:/Update/pool-leap-15.3/x86_64/ I am able to login into option Gnome now. So that works. Another new problem that might need to be reported in new bug is that Welcome screen and my pwd manager application, not Firefox though, haven't tested more apps yet, are rendered as "see through". I only see the outer see through "3D" frame of the window. There is no content at all. Will test more tomorrow or friday. This is after installing above server packages and logging into option Gnome. Created attachment 848375 [details]
journalctl
After succesful login into option Gnome with new server packages.
(In reply to Andreas Strand from comment #23) > Sorry for the delay, I caught up in work. > > I installed server, server-extra and server-wayland from > https://download.opensuse.org/repositories/home:/yudaike:/branches:/SUSE:/ > SLE-15-SP2:/Update/pool-leap-15.3/x86_64/ > > I am able to login into option Gnome now. So that works. > > Another new problem that might need to be reported in new bug is that > Welcome screen and my pwd manager application, not Firefox though, haven't > tested more apps yet, are rendered as "see through". I only see the outer > see through "3D" frame of the window. There is no content at all. Will test > more tomorrow or friday. This is after installing above server packages and > logging into option Gnome. I see. Would you please open another bug report for the new problem, so we can track it more clearly? Thanks for all the help :) (In reply to Stefan Dirsch from comment #21) > And this is now with or without the fix i.e an updated > xorg-x11-server-wayland package? Due to bug 1182499 I was not able to install any updates so far. (In reply to Ulrich Windl from comment #26) > (In reply to Stefan Dirsch from comment #21) > > > And this is now with or without the fix i.e an updated > > xorg-x11-server-wayland package? > > Due to bug 1182499 I was not able to install any updates so far. ? You won't find the test package in any official update repository. For you the same applies as to Andreas: (In reply to Stefan Dirsch from comment #17) > Andreas, you'll need to update xorg-x11-server-wayland package in > > https://download.opensuse.org/repositories/home:/yudaike:/branches:/SUSE:/ > SLE-15-SP2:/Update/pool-leap-15.3/x86_64/ After updating and switching back to "normal" GNOME, login succeeds, but the greeting window is without contents (i.e.: transparent with only a thin frame around). So exactly the same results as Andreas had. See comment#23 and comment#25. So let's close this ticket. SUSE-RU-2021:1320-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1184072,1184543 CVE References: JIRA References: Sources used: SUSE Linux Enterprise Workstation Extension 15-SP3 (src): xorg-x11-server-1.20.3-22.5.30.1 SUSE Linux Enterprise Workstation Extension 15-SP2 (src): xorg-x11-server-1.20.3-22.5.30.1 SUSE Linux Enterprise Module for Development Tools 15-SP3 (src): xorg-x11-server-1.20.3-22.5.30.1 SUSE Linux Enterprise Module for Development Tools 15-SP2 (src): xorg-x11-server-1.20.3-22.5.30.1 SUSE Linux Enterprise Module for Basesystem 15-SP3 (src): xorg-x11-server-1.20.3-22.5.30.1 SUSE Linux Enterprise Module for Basesystem 15-SP2 (src): xorg-x11-server-1.20.3-22.5.30.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. openSUSE-RU-2021:0640-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1184072,1184543 CVE References: JIRA References: Sources used: openSUSE Leap 15.2 (src): xorg-x11-server-1.20.3-lp152.8.24.1 Note: Not fixed in the GNOME Live image yet (as per yesterday). This is still happening for me on the following xorg-x11-server-1.20.3-22.5.36.1.x86_64 xorg-x11-server-wayland-1.20.3-22.5.36.1.x86_64 xorg-x11-fonts-7.6-13.6.1.noarch xorg-x11-Xvnc-1.9.0-19.9.1.x86_64 xorg-x11-essentials-7.6_1-1.22.noarch xorg-x11-fonts-converted-7.6-13.6.5.noarch xorg-x11-fonts-core-7.6-13.6.1.noarch xorg-x11-fonts-legacy-7.6-13.6.1.noarch xorg-x11-driver-video-7.6_1-9.10.x86_64 xorg-x11-server-extra-1.20.3-22.5.36.1.x86_64 xorg-x11-Xvnc-module-1.9.0-19.9.1.x86_64 xorg-x11-libX11-ccache-7.6-bp153.1.12.noarch Still the this issue at various times during the day where systemd reports "Stopped GNOME Shell on Wayland." (openSUSE 15.3 - 5.3.18-59.24-default) --- cut here--- 2021-09-30T00:11:01.231861+02:00 area51b systemd[2880]: Stopped GNOME Shell on Wayland. 2021-09-30T13:26:47.929077+02:00 area51b systemd[2807]: Stopped GNOME Shell on Wayland. 2021-10-02T15:38:12.063696+02:00 area51b systemd[2815]: Stopped GNOME Shell on Wayland. --- cut here--- Current session just stops, I am logged-out and am required to login on the desktop again # journalctl /usr/bin/gnome-shell shows this : --- cut here--- > Oct 02 15:37:59 area51b gnome-shell[2845]: Failed to obtain high priority context > Oct 02 15:37:59 area51b gnome-shell[2845]: Failed to obtain high priority context > Oct 02 15:38:00 area51b gnome-shell[2845]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. > Oct 02 15:38:00 area51b gnome-shell[2845]: Will monitor session c1 > Oct 02 15:38:01 area51b gnome-shell[2845]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. > Oct 02 15:38:01 area51b gnome-shell[2845]: Will monitor session c1 > Oct 02 15:38:01 area51b gnome-shell[2845]: Failed to get PolKit permission: Polkit.Error: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.bolt.enroll is n> > Oct 02 15:38:01 area51b gnome-shell[2845]: Error checking authorization for action id org.freedesktop.bolt.enroll: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.fre> > Oct 02 15:38:01 area51b gnome-shell[2845]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation > Oct 02 15:38:01 area51b gnome-shell[2845]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1637]: reference to undefined property "MetaWindowXwayland" > Oct 02 15:38:01 area51b gnome-shell[2845]: Window manager warning: "XF86MonBrightnessCycle" is not a valid accelerator > Oct 02 15:38:01 area51b gnome-shell[2845]: Registering session with GDM > Oct 02 15:38:05 area51b gnome-shell[2845]: Error checking authorization for action id org.freedesktop.bolt.enroll: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.fre> > Oct 02 15:38:05 area51b gnome-shell[2845]: Error checking authorization for action id org.freedesktop.bolt.enroll: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.fre> > Oct 02 15:38:05 area51b gnome-shell[2845]: Error checking authorization for action id org.freedesktop.bolt.enroll: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.fre> > Oct 02 15:38:06 area51b gnome-shell[2845]: Error checking authorization for action id org.freedesktop.bolt.enroll: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.fre> > Oct 02 15:38:06 area51b gnome-shell[2845]: Error checking authorization for action id org.freedesktop.bolt.enroll: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.fre> > Oct 02 15:38:06 area51b gnome-shell[2845]: Error checking authorization for action id org.freedesktop.bolt.enroll: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.fre> > Oct 02 15:38:06 area51b gnome-shell[2845]: Error checking authorization for action id org.freedesktop.bolt.enroll: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.fre> > Oct 02 15:38:06 area51b gnome-shell[3185]: Failed to obtain high priority context > Oct 02 15:38:06 area51b gnome-shell[3185]: Failed to obtain high priority context > Oct 02 15:38:07 area51b gnome-shell[3185]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. > Oct 02 15:38:07 area51b gnome-shell[3185]: Will monitor session 1 .... > Oct 02 15:38:09 area51b gnome-shell[3185]: Failed to get PolKit permission: Polkit.Error: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.bolt.enroll is not registered > Oct 02 15:38:09 area51b gnome-shell[3185]: Error checking authorization for action id org.freedesktop.bolt.enroll: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.bolt.enroll is not registered > Oct 02 15:38:09 area51b gnome-shell[3185]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation > Oct 02 15:38:09 area51b gnome-shell[3185]: Could not create transient scope for PID 3497: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 3497 does not exist. > Oct 02 15:38:10 area51b gnome-shell[3185]: JS WARNING: [/home/hvdheuvel/.local/share/gnome-shell/extensions/sound-output-device-chooser@kgshank.net/convenience.js 109]: reference to undefined property "id" > Oct 02 15:38:10 area51b gnome-shell[2845]: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 51 failed: Permission denied > Oct 02 15:38:10 area51b gnome-shell[2845]: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 69 failed: Permission denied > Oct 02 15:38:10 area51b gnome-shell[2845]: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 54 failed: Permission denied > Oct 02 15:38:11 area51b gnome-shell[3185]: Window manager warning: "XF86MonBrightnessCycle" is not a valid accelerator > Oct 02 15:38:11 area51b gnome-shell[2845]: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 54 failed: Permission denied > Oct 02 15:38:11 area51b gnome-shell[2845]: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 69 failed: Permission denied > Oct 02 15:38:11 area51b gnome-shell[2845]: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 51 failed: Permission denied > Oct 02 15:38:11 area51b gnome-shell[3185]: GNOME Shell started at Sat Oct 02 2021 15:38:08 GMT+0200 (CEST) > Oct 02 15:38:11 area51b gnome-shell[3185]: Registering session with GDM > Oct 02 15:38:11 area51b gnome-shell[2845]: Connection to xwayland lost > Oct 02 15:38:12 area51b gnome-shell[3185]: Error checking authorization for action id org.freedesktop.bolt.enroll: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.bolt.enroll is not registered > Oct 02 15:38:12 area51b gnome-shell[3185]: Error checking authorization for action id org.freedesktop.bolt.enroll: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.bolt.enroll is not registered --- cut here --- Shall I open a new bug after following the debug suggestion in Comment#1? This is an autogenerated message for OBS integration: This bug (1184072) was mentioned in https://build.opensuse.org/request/show/1034269 Factory / xorg-x11-server |