Bug 1369073

Summary: mutter gets killed by SIGSEGV when executed with already running window manager
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Hudziec <thudziec>
Component: mutterAssignee: Florian Müllner <fmuellner>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: tpelka, vbudikov
Target Milestone: rc   
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: 2017-08-01 22:41:41 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:
Attachments:
Description Flags
mutter backtrace none

Description Tomas Hudziec 2016-08-22 12:40:40 UTC 
Description of problem:
Mutter gets killed by SIGSEGV when executed from terminal with already running window manager.

Version-Release number of selected component (if applicable):
mutter-3.14.4-29.el7.x86_64
kernel-3.10.0-493.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. boot up into runlevel 5 and log in
2. in terminal run command: mutter

Actual results:
Window manager warning: Screen 0 on display ":0" already has a window manager; try using the --replace option to replace the current window manager.
Segmentation fault (core dumped)

Expected results:
Mutter should not cause segmentation fault.
Comment 3 Tomas Pelka 2017-02-17 08:57:30 UTC 
Created attachment 1251831 [details]
mutter backtrace

Still reproducible with mutter-3.22.2-1.el7
Comment 6 errata-xmlrpc 2017-08-01 22:41:41 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2098