Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1630943 - laptop with lid closed and external monitor can't log in to wayland session
Summary: laptop with lid closed and external monitor can't log in to wayland session
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: RejectedBlocker AcceptedFreezeException
: 1635529 (view as bug list)
Depends On:
Blocks: F29FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2018-09-19 15:03 UTC by Kamil Páral
Modified: 2018-10-29 11:14 UTC (History)
10 users (show)

Fixed In Version: mutter-3.30.0-3.fc29
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-08 15:39:22 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
journal (395.33 KB, text/plain)
2018-09-19 15:10 UTC, Kamil Páral 		no flags Details
abrt: gnome-shell: backtrace (52.88 KB, text/plain)
2018-09-19 15:12 UTC, Kamil Páral 		no flags Details
abrt: gnome-shell: core_backtrace (15.12 KB, text/plain)
2018-09-19 15:12 UTC, Kamil Páral 		no flags Details
abrt: gnome-shell: var_log_messages (2.61 KB, text/plain)
2018-09-19 15:12 UTC, Kamil Páral 		no flags Details
abrt: xwayland: backtrace (22.65 KB, text/plain)
2018-09-19 15:13 UTC, Kamil Páral 		no flags Details
abrt: xwayland: core_backtrace (4.03 KB, text/plain)
2018-09-19 15:13 UTC, Kamil Páral 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME mutter issues 194 0 None None None 2018-09-25 07:49:02 UTC

Description Kamil Páral 2018-09-19 15:03:29 UTC 
Description of problem:
If I boot with laptop lid closed and an external monitor attached, I can't log in to a Wayland session (but I can use X11 one). The screen just goes black with a blinking cursor. I can switch to a text tty and I see that gnome-shell and Xwayland crashed. If I restart gdm service, they crash again (and gdm is not started), every time, until I open up the lid, and then gdm starts normally and I can log in to a wayland session.

Abrt tells me I can't report those crases because the traceback is unusable. So I'll attach what is included in abrt dirs manually. I don't know how to make it usable, I even tried local tracing and have all debuginfo's installed.

My hardware:
Thinkpad T480s
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07)


Version-Release number of selected component (if applicable):
gdm-3.30.0-3.fc29.x86_64
gnome-shell-3.30.0-3.fc29.x86_64
xorg-x11-server-Xorg-1.20.1-2.fc29.x86_64
xorg-x11-server-Xwayland-1.20.1-2.fc29.x86_64


How reproducible:
100%

Steps to Reproduce:
1. close the laptop lid, connect an external monitor
2. start the laptop (I do that using a docking station's power button)
3. boot into gdm
4. try to log in into a wayland session
5. see a black screen with a blinking cursor

Additional info:
We tried this on colleague's T480s, and the result was a bit different. After trying to log in, he was immediately thrown back to gdm, and the wayland session option was removed from the cog icon (so he could only log in to X11 session, which worked).
Comment 1 Kamil Páral 2018-09-19 15:10:41 UTC 
Created attachment 1484826 [details]
journal

Journal excerpt:
Sep 19 16:48:34 phoenix org.gnome.Shell.desktop[2039]: glamor: No eglstream capable devices found
Sep 19 16:48:34 phoenix kernel: show_signal_msg: 68 callbacks suppressed
Sep 19 16:48:34 phoenix kernel: gnome-shell[2039]: segfault at 1c ip 00007f4f6118dfa4 sp 00007ffd9d2e57e8 error 4 in libmutter-3.so.0.0.0[7f4f61169000+ea000]
Sep 19 16:48:34 phoenix kernel: Code: 00 c3 0f 1f 40 00 f3 0f 1e fa f3 0f 10 47 38 c3 66 0f 1f 44 00 00 f3 0f 1e fa 8b 47 3c c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa <48> 8b 47 1c 48 8b 57 24 c3 0f 1f 00 f3 0f 1e fa 48 8b 47 48 c3 0f 
Sep 19 16:48:34 phoenix audit[2039]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=2039 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=11 res=1
Sep 19 16:48:34 phoenix systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Sep 19 16:48:34 phoenix systemd[1]: Started Process Core Dump (PID 2130/UID 0).
Sep 19 16:48:34 phoenix audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@0-2130-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 19 16:48:34 phoenix org.gnome.Shell.desktop[2039]: (EE)
Sep 19 16:48:34 phoenix org.gnome.Shell.desktop[2039]: Fatal server error:
Sep 19 16:48:34 phoenix org.gnome.Shell.desktop[2039]: (EE) Error sending request: Broken pipe
Sep 19 16:48:34 phoenix org.gnome.Shell.desktop[2039]: (EE)
Sep 19 16:48:34 phoenix gnome-session[1963]: gnome-session-binary[1963]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Sep 19 16:48:34 phoenix audit[2129]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=2129 comm="Xwayland" exe="/usr/bin/Xwayland" sig=6 res=1
Sep 19 16:48:34 phoenix gnome-session-binary[1963]: Unrecoverable failure in required component org.gnome.Shell.desktop
Sep 19 16:48:34 phoenix gnome-session-binary[1963]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Sep 19 16:48:34 phoenix systemd-coredump[2131]: Process 2039 (gnome-shell) of user 1000 dumped core.
                                                
                                                Stack trace of thread 2039:
                                                #0  0x00007f4f6118dfa4 meta_logical_monitor_get_layout (libmutter-3.so.0)
                                                #1  0x00007f4f61225064 n/a (libmutter-3.so.0)
                                                #2  0x00007f4f6051dace ffi_call_unix64 (libffi.so.6)
                                                #3  0x00007f4f6051d48f ffi_call (libffi.so.6)
                                                #4  0x00007f4f5e50a31d n/a (libwayland-server.so.0)
                                                #5  0x00007f4f5e506c69 n/a (libwayland-server.so.0)
                                                #6  0x00007f4f5e5082e2 wl_event_loop_dispatch (libwayland-server.so.0)
                                                #7  0x00007f4f612097bb n/a (libmutter-3.so.0)
                                                #8  0x00007f4f61d5f26d g_main_context_dispatch (libglib-2.0.so.0)
                                                #9  0x00007f4f61d5f638 n/a (libglib-2.0.so.0)
                                                #10 0x00007f4f61d5f962 g_main_loop_run (libglib-2.0.so.0)
                                                #11 0x00007f4f6120aa92 meta_xwayland_start (libmutter-3.so.0)
                                                #12 0x00007f4f61209e28 meta_wayland_init (libmutter-3.so.0)
                                                #13 0x00007f4f611d05ce meta_init (libmutter-3.so.0)
                                                #14 0x00005568c111f93c n/a (gnome-shell)
                                                #15 0x00007f4f60f4a413 __libc_start_main (libc.so.6)
                                                #16 0x00005568c111fcee n/a (gnome-shell)
                                                
                                                Stack trace of thread 2045:
                                                #0  0x00007f4f61018301 __poll (libc.so.6)
                                                #1  0x00007f4f61d5f5a6 n/a (libglib-2.0.so.0)
                                                #2  0x00007f4f61d5f6d0 g_main_context_iteration (libglib-2.0.so.0)
                                                #3  0x00007f4f61d5f721 n/a (libglib-2.0.so.0)
                                                #4  0x00007f4f61d8848a n/a (libglib-2.0.so.0)
                                                #5  0x00007f4f610f458e start_thread (libpthread.so.0)
                                                #6  0x00007f4f61023513 __clone (libc.so.6)
                                                
                                                Stack trace of thread 2047:
                                                #0  0x00007f4f6101dd6d syscall (libc.so.6)
                                                #1  0x00007f4f61da711e g_cond_wait_until (libglib-2.0.so.0)
                                                #2  0x00007f4f61d31231 n/a (libglib-2.0.so.0)
                                                #3  0x00007f4f61d88fd2 n/a (libglib-2.0.so.0)
                                                #4  0x00007f4f61d8848a n/a (libglib-2.0.so.0)
                                                #5  0x00007f4f610f458e start_thread (libpthread.so.0)
                                                #6  0x00007f4f61023513 __clone (libc.so.6)
                                                
                                                Stack trace of thread 2048:
                                                #0  0x00007f4f61018301 __poll (libc.so.6)
                                                #1  0x00007f4f61d5f5a6 n/a (libglib-2.0.so.0)
                                                #2  0x00007f4f61d5f6d0 g_main_context_iteration (libglib-2.0.so.0)
                                                #3  0x00007f4f62039c6d n/a (libdconfsettings.so)
                                                #4  0x00007f4f61d8848a n/a (libglib-2.0.so.0)
                                                #5  0x00007f4f610f458e start_thread (libpthread.so.0)
                                                #6  0x00007f4f61023513 __clone (libc.so.6)
                                                
                                                Stack trace of thread 2046:
                                                #0  0x00007f4f61018301 __poll (libc.so.6)
                                                #1  0x00007f4f61d5f5a6 n/a (libglib-2.0.so.0)
                                                #2  0x00007f4f61d5f962 g_main_loop_run (libglib-2.0.so.0)
                                                #3  0x00007f4f61f5774a n/a (libgio-2.0.so.0)
                                                #4  0x00007f4f61d8848a n/a (libglib-2.0.so.0)
                                                #5  0x00007f4f610f458e start_thread (libpthread.so.0)
                                                #6  0x00007f4f61023513 __clone (libc.so.6)
                                                
                                                Stack trace of thread 2101:
                                                #0  0x00007f4f610fa67c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                                #1  0x00007f4f49bbe993 n/a (i965_dri.so)
                                                #2  0x00007f4f49bbe6eb n/a (i965_dri.so)
                                                #3  0x00007f4f610f458e start_thread (libpthread.so.0)
                                                #4  0x00007f4f61023513 __clone (libc.so.6)
Sep 19 16:48:34 phoenix audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@0-2130-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 19 16:48:34 phoenix systemd[1]: Started Process Core Dump (PID 2132/UID 0).
Sep 19 16:48:34 phoenix audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@1-2132-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 19 16:48:34 phoenix gdm-password][1923]: pam_unix(gdm-password:session): session closed for user kparal
Sep 19 16:48:34 phoenix audit[1923]: USER_END pid=1923 uid=0 auid=1000 ses=2 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_selinux,pam_loginuid,pam_selinux,pam_keyinit,pam_namespace,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_gnome_keyring,pam_umask acct="kparal" exe="/usr/libexec/gdm-session-worker" hostname=phoenix addr=? terminal=/dev/tty2 res=success'
Sep 19 16:48:34 phoenix audit[1923]: USER_LOGOUT pid=1923 uid=0 auid=1000 ses=2 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='uid=1000 exe="/usr/libexec/gdm-session-worker" hostname=? addr=? terminal=? res=success'
Sep 19 16:48:34 phoenix audit[1923]: CRED_DISP pid=1923 uid=0 auid=1000 ses=2 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_localuser,pam_unix,pam_gnome_keyring acct="kparal" exe="/usr/libexec/gdm-session-worker" hostname=phoenix addr=? terminal=/dev/tty2 res=success'
Sep 19 16:48:34 phoenix gdm[1051]: GdmDisplay: display lasted 1.725905 seconds
Sep 19 16:48:34 phoenix systemd-logind[962]: Session 2 logged out. Waiting for processes to exit.
Sep 19 16:48:34 phoenix pulseaudio[1941]: W: [pulseaudio] module.c: After module unload, module 'module-null-sink' was still loaded!
Sep 19 16:48:34 phoenix bluetoothd[953]: Endpoint unregistered: sender=:1.242 path=/MediaEndpoint/A2DPSource
Sep 19 16:48:34 phoenix bluetoothd[953]: Endpoint unregistered: sender=:1.242 path=/MediaEndpoint/A2DPSink
Sep 19 16:48:34 phoenix audit[2143]: USER_AUTH pid=2143 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_permit acct="gdm" exe="/usr/libexec/gdm-session-worker" hostname=phoenix addr=? terminal=/dev/tty1 res=success'
Sep 19 16:48:34 phoenix audit[2143]: USER_ACCT pid=2143 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_permit acct="gdm" exe="/usr/libexec/gdm-session-worker" hostname=phoenix addr=? terminal=/dev/tty1 res=success'
Sep 19 16:48:34 phoenix audit[2143]: CRED_ACQ pid=2143 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/libexec/gdm-session-worker" hostname=phoenix addr=? terminal=/dev/tty1 res=success'
Sep 19 16:48:34 phoenix systemd-logind[962]: Removed session 2.
Sep 19 16:48:34 phoenix systemd[1]: user-runtime-dir: Unit not needed anymore. Stopping.
Sep 19 16:48:34 phoenix systemd[1]: Stopping User Manager for UID 1000...
Sep 19 16:48:34 phoenix systemd[1931]: Stopping Virtual filesystem service...
Sep 19 16:48:34 phoenix systemd[1931]: Stopped target Default.
Sep 19 16:48:34 phoenix systemd[1931]: Stopping D-Bus User Message Bus...
Sep 19 16:48:34 phoenix systemd-logind[962]: New session c2 of user gdm.
Sep 19 16:48:34 phoenix systemd[1931]: Stopped D-Bus User Message Bus.
Sep 19 16:48:34 phoenix systemd[1]: Started Session c2 of user gdm.
Sep 19 16:48:34 phoenix gdm-launch-environment][2143]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Sep 19 16:48:34 phoenix audit[2143]: USER_START pid=2143 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_keyinit,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_umask acct="gdm" exe="/usr/libexec/gdm-session-worker" hostname=phoenix addr=? terminal=/dev/tty2 res=success'
Sep 19 16:48:34 phoenix systemd[1931]: Stopped Virtual filesystem service.
Sep 19 16:48:34 phoenix systemd[1931]: Stopped target Basic System.
Sep 19 16:48:34 phoenix systemd[1931]: Stopped target Paths.
Sep 19 16:48:34 phoenix systemd[1931]: Stopped target Sockets.
Sep 19 16:48:34 phoenix systemd[1931]: Closed Sound System.
Sep 19 16:48:34 phoenix systemd[1931]: Stopped target Timers.
Sep 19 16:48:34 phoenix systemd[1931]: Stopped Run backup.service daily.
Sep 19 16:48:34 phoenix systemd[1931]: Stopped Mark boot as successful after the user session has run 2 minutes.
Sep 19 16:48:34 phoenix systemd[1931]: Closed D-Bus User Message Bus Socket.
Sep 19 16:48:34 phoenix systemd[1931]: Reached target Shutdown.
Sep 19 16:48:34 phoenix systemd[1931]: Starting Exit the Session...
Sep 19 16:48:34 phoenix systemd-coredump[2140]: Process 2129 (Xwayland) of user 1000 dumped core.
                                                
                                                Stack trace of thread 2129:
                                                #0  0x00007efd7e9cc53f raise (libc.so.6)
                                                #1  0x00007efd7e9b6895 abort (libc.so.6)
                                                #2  0x00000000005943f0 OsAbort (Xwayland)
                                                #3  0x0000000000599689 AbortServer (Xwayland)
                                                #4  0x000000000059a4fd FatalError (Xwayland)
                                                #5  0x000000000042e61c xwl_log_handler (Xwayland)
                                                #6  0x00007efd7f0ce7a0 n/a (libwayland-client.so.0)
                                                #7  0x00007efd7f0ca4dd wl_proxy_marshal_array_constructor_versioned (libwayland-client.so.0)
                                                #8  0x00007efd7f0ca74e wl_proxy_marshal_constructor (libwayland-client.so.0)
                                                #9  0x00007efd7f0cb7f9 wl_display_roundtrip_queue (libwayland-client.so.0)
                                                #10 0x000000000042eadc xwl_screen_init (Xwayland)
                                                #11 0x000000000055ba0b AddScreen (Xwayland)
                                                #12 0x000000000043049e InitOutput (Xwayland)
                                                #13 0x000000000055f5e7 dix_main (Xwayland)
                                                #14 0x00007efd7e9b8413 __libc_start_main (libc.so.6)
                                                #15 0x000000000042e33e _start (Xwayland)
Comment 2 Kamil Páral 2018-09-19 15:12:30 UTC 
Created attachment 1484827 [details]
abrt: gnome-shell: backtrace
Comment 3 Kamil Páral 2018-09-19 15:12:38 UTC 
Created attachment 1484828 [details]
abrt: gnome-shell: core_backtrace
Comment 4 Kamil Páral 2018-09-19 15:12:47 UTC 
Created attachment 1484829 [details]
abrt: gnome-shell: var_log_messages
Comment 5 Kamil Páral 2018-09-19 15:13:24 UTC 
Created attachment 1484830 [details]
abrt: xwayland: backtrace
Comment 6 Kamil Páral 2018-09-19 15:13:32 UTC 
Created attachment 1484831 [details]
abrt: xwayland: core_backtrace
Comment 7 Kamil Páral 2018-09-19 15:15:57 UTC 
This feels like a possible blocker due to login shell not working (in certain configurations). We'll need to figure out whether this affects all laptops, or all intel cards, or just very specific hardware.
Comment 8 Adam Williamson 2018-09-24 17:38:54 UTC 
this actually crashed in mutter, so re-assigning there...I think the problem is that logical_monitor is NULL but meta_logical_monitor_get_layout isn't expecting that...
Comment 9 Adam Williamson 2018-09-24 17:46:43 UTC 
This is odd, I found:

https://gitlab.gnome.org/GNOME/mutter/issues/194

which looks a lot like the same problem, only it's supposed to have been fixed a month ago, and should surely have been in 3.30.0...
Comment 10 Geoffrey Marr 2018-09-24 19:32:57 UTC 
Discussed during the 2018-09-24 blocker review meeting: [1]

The decision to delay the classification of this as a blocker bug was made as we think this is potentially a blocker, but would like some more data on how common it is first (i.e. tests with other laptops and monitors).

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2018-09-24/f29-blocker-review.2018-09-24-16.05.txt
Comment 11 Adam Williamson 2018-09-25 15:10:36 UTC 
https://gitlab.gnome.org/GNOME/mutter/commit/68ec9ac017157def9b7c25dd8141dc0e93d9f918 is a further proposed fix for this.
Comment 12 Geoffrey Marr 2018-10-01 19:55:22 UTC 
Discussed during the 2018-10-01 blocker review meeting: [1]

The decision to classify this bug as a "RejectedBlocker" and an "AcceptedFreezeException" was made as we interpret this bug to only affect laptops with a closed lid. We do not see a clear criterion that would cause this to be a blocker and as such we reject it as a blocker. We do note that this is an annoying bug and grant it FreezeException status.

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2018-10-01/f29-blocker-review.2018-10-01-16.00.txt
Comment 13 Kamil Páral 2018-10-02 12:01:26 UTC 
Geoff, please don't forget to tag annoying rejected blockers as commonbugs, thanks.
Comment 14 Yanko Kaneti 2018-10-03 09:00:02 UTC 
*** Bug 1635529 has been marked as a duplicate of this bug. ***
Comment 15 Fedora Update System 2018-10-03 23:24:03 UTC 
mutter-3.30.0-3.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-b13062cd77
Comment 16 Kamil Páral 2018-10-04 08:45:35 UTC 
(In reply to Fedora Update System from comment #15)
> mutter-3.30.0-3.fc29 has been submitted as an update to Fedora 29.
> https://bodhi.fedoraproject.org/updates/FEDORA-2018-b13062cd77

Thanks, that fixes this issue. It doesn't fix bug 1630367, unfortunately.
Comment 17 Benjamin Berg 2018-10-04 09:04:47 UTC 
I just ran into this issue, and updating to 3.30.0-3 *did* fix the issue on wayland. However, on X11, the crash just changed, and it now crashes in 

#0  0x00007fd6c651fd89 meta_monitor_manager_get_monitor_for_connector (libmutter-3.so.0)

rather than meta_logical_monitor_get_layout.
Comment 18 Kamil Páral 2018-10-04 09:18:50 UTC 
I tested this with X11 and it doesn't crash for me. Benjamin, are you following the reproducer from comment 0 or using some other approach?
Comment 19 Benjamin Berg 2018-10-04 10:01:26 UTC 
Hm, I have two external monitors attached and the laptop lid is closed. So maybe the difference is the additional monitor?
Comment 20 Jonas Ådahl 2018-10-04 11:01:51 UTC 
What is the complete backtrace for the crash under X11? I doub't it's related as the Wayland one was strictly about sending Wayland events.
Comment 21 Benjamin Berg 2018-10-04 11:11:21 UTC 
I created bug #1636060 for the issue I was seeing.
Comment 22 Fedora Update System 2018-10-07 23:35:38 UTC 
mutter-3.30.0-3.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-b13062cd77
Comment 23 Fedora Update System 2018-10-08 15:39:22 UTC 
mutter-3.30.0-3.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.