Bug 1401317

Summary: Gnome segfaults after mutter update
Product: [Fedora] Fedora Reporter: Medic Momcilo <momcilo>
Component: mutterAssignee: Florian Müllner <fmuellner>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rawhideCC: fmuellner, jakub_o, kparal, momcilo, otaylor, sdodson, valdis.kletnieks, vondruch, walters
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-06 13:01:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Medic Momcilo 2016-12-04 17:18:41 UTC 
Description of problem:
After updating mutter component I couldn't logon to the graphical.target. GDM wouldn't show up at all (in both X and Wayland) - startx doesn't work also.

Version-Release number of selected component (if applicable):
3.23.2-2.fc26.x86_64

How reproducible:
Always

Steps to Reproduce:
1. dnf upgrade
2. reboot
3. 

Actual results:
Only pointer is shown, and it stays there. No GDM, no Gnome.

Expected results:
GDM login screen shows.


Additional info:
If you require any specific information don't hesitate to ask.
Comment 1 Vít Ondruch 2016-12-05 17:03:46 UTC 
Same here. Downgrade to mutter-3.23.1-2.fc26.x86_64 workarounded the problem.

This is content of my journal:

```
Dec 05 17:16:10 localhost.localdomain at-spi-bus-launcher[1501]: dbus-daemon[1506]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=42 pid=1458 comm="/usr/bin/gnome-shell " label="syst
Dec 05 17:16:10 localhost.localdomain at-spi-bus-launcher[1501]: dbus-daemon[1506]: Successfully activated service 'org.a11y.atspi.Registry'
Dec 05 17:16:10 localhost.localdomain at-spi-bus-launcher[1501]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Dec 05 17:16:10 localhost.localdomain rtkit-daemon[959]: Successfully made thread 1515 of process 1515 (/usr/bin/pulseaudio) owned by '42' high priority at nice level -11.
Dec 05 17:16:10 localhost.localdomain rtkit-daemon[959]: Supervising 1 threads of 1 processes of 1 users.
Dec 05 17:16:10 localhost.localdomain rtkit-daemon[959]: Supervising 1 threads of 1 processes of 1 users.
Dec 05 17:16:10 localhost.localdomain rtkit-daemon[959]: Successfully made thread 1518 of process 1515 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
Dec 05 17:16:10 localhost.localdomain rtkit-daemon[959]: Supervising 2 threads of 1 processes of 1 users.
Dec 05 17:16:10 localhost.localdomain rtkit-daemon[959]: Supervising 2 threads of 1 processes of 1 users.
Dec 05 17:16:10 localhost.localdomain rtkit-daemon[959]: Successfully made thread 1521 of process 1515 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
Dec 05 17:16:10 localhost.localdomain rtkit-daemon[959]: Supervising 3 threads of 1 processes of 1 users.
Dec 05 17:16:10 localhost.localdomain rtkit-daemon[959]: Supervising 3 threads of 1 processes of 1 users.
Dec 05 17:16:10 localhost.localdomain rtkit-daemon[959]: Successfully made thread 1524 of process 1515 (/usr/bin/pulseaudio) owned by '42' RT at priority 5.
Dec 05 17:16:10 localhost.localdomain rtkit-daemon[959]: Supervising 4 threads of 1 processes of 1 users.
Dec 05 17:16:10 localhost.localdomain abrtd[992]: '/var/spool/abrt/oops-2016-10-25-14:59:41-1238-2' is not a problem directory
Dec 05 17:16:10 localhost.localdomain gnome-shell[1458]: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
Dec 05 17:16:10 localhost.localdomain kernel: show_signal_msg: 36 callbacks suppressed
Dec 05 17:16:10 localhost.localdomain kernel: gnome-shell[1458]: segfault at 18 ip 00007fa1b48621bc sp 00007ffdc6e429d0 error 4 in libmutter.so.0.0.0[7fa1b47f6000+12c000]
Dec 05 17:16:10 localhost.localdomain audit[1458]: ANOM_ABEND auid=4294967295 uid=42 gid=42 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 pid=1458 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=1
Dec 05 17:16:10 localhost.localdomain systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Dec 05 17:16:10 localhost.localdomain 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-1530-0 comm="systemd" exe="/usr/lib/systemd/
Dec 05 17:16:10 localhost.localdomain systemd[1]: Started Process Core Dump (PID 1530/UID 0).
Dec 05 17:16:10 localhost.localdomain systemd-coredump[1531]: Core Dumping has been disabled for process 1458 (gnome-shell).
Dec 05 17:16:10 localhost.localdomain systemd-coredump[1531]: Process 1458 (gnome-shell) of user 42 dumped core.
Dec 05 17:16:10 localhost.localdomain org.gnome.Shell.desktop[1458]: (EE)
Dec 05 17:16:10 localhost.localdomain org.gnome.Shell.desktop[1458]: Fatal server error:
Dec 05 17:16:10 localhost.localdomain org.gnome.Shell.desktop[1458]: (EE) failed to read Wayland events: Connection reset by peer
Dec 05 17:16:10 localhost.localdomain org.gnome.Shell.desktop[1458]: (EE)
Dec 05 17:16:10 localhost.localdomain 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-1530-0 comm="systemd" exe="/usr/lib/systemd/s
Dec 05 17:16:10 localhost.localdomain gnome-session-binary[1378]: Unrecoverable failure in required component org.gnome.Shell.desktop
Dec 05 17:16:10 localhost.localdomain gnome-session[1378]: gnome-session-binary[1378]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Dec 05 17:16:10 localhost.localdomain gnome-session-binary[1378]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
```

And this might be the backtrace:

```
     [ {   "crash_thread": true
        ,   "frames":
              [ {   "address": 140366498529724
                ,   "build_id": "4ed11ccf28796de754272494ab2bc71b62eb0d53"
                ,   "build_id_offset": 442812
                ,   "function_name": "_meta_plugin_set_compositor"
                ,   "file_name": "/usr/lib64/libmutter.so.0.0.0"
                }
              , {   "address": 140366498530105
                ,   "build_id": "4ed11ccf28796de754272494ab2bc71b62eb0d53"
                ,   "build_id_offset": 443193
                ,   "function_name": "meta_plugin_manager_new"
                ,   "file_name": "/usr/lib64/libmutter.so.0.0.0"
                }
              , {   "address": 140366498506504
                ,   "build_id": "4ed11ccf28796de754272494ab2bc71b62eb0d53"
                ,   "build_id_offset": 419592
                ,   "function_name": "meta_compositor_manage"
                ,   "file_name": "/usr/lib64/libmutter.so.0.0.0"
                }
              , {   "address": 140366498598168
                ,   "build_id": "4ed11ccf28796de754272494ab2bc71b62eb0d53"
                ,   "build_id_offset": 511256
                ,   "function_name": "meta_display_open"
                ,   "file_name": "/usr/lib64/libmutter.so.0.0.0"
                }
              , {   "address": 140366498634732
                ,   "build_id": "4ed11ccf28796de754272494ab2bc71b62eb0d53"
                ,   "build_id_offset": 547820
                ,   "function_name": "meta_run"
                ,   "file_name": "/usr/lib64/libmutter.so.0.0.0"
                }
              , {   "address": 94364803298759
                ,   "build_id": "afd92357de0aa8a79227973a7b79ee822ff6dd8f"
                ,   "build_id_offset": 9671
                ,   "function_name": "main"
                ,   "file_name": "/usr/bin/gnome-shell"
                } ]
        } ]
}

```
Comment 2 Jakub 2016-12-05 23:15:11 UTC 
dmesg tells:
gnome-shell: segfault at 18 ip .... sp .... error 4 in libmutter.so.0.0f...
4 times with different id and numbers
and after that:
gnome-session-f: segfault at 0 ip ... sp ... error 4 in libgtk-3.so.o.2200.4f...

unfortunately i cannot downgrade as for mutter and for gnome-shell it says it was the lowest version.
Comment 3 Kamil Páral 2016-12-06 13:01:39 UTC 
The full traceback is already available in bug 1401886, duping to that one.

*** This bug has been marked as a duplicate of bug 1401886 ***