Bug 1369073 - mutter gets killed by SIGSEGV when executed with already running window manager
Summary: mutter gets killed by SIGSEGV when executed with already running window manager
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: mutter
Version: 7.3
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Florian Müllner
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-22 12:40 UTC by Tomas Hudziec
Modified: 2017-08-01 22:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 22:41:41 UTC
Target Upstream Version:

Attachments (Terms of Use)
mutter backtrace (14.27 KB, text/plain)
2017-02-17 08:57 UTC, Tomas Pelka 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 778831 0 None None None 2017-02-17 13:31:58 UTC
Red Hat Product Errata RHBA-2017:2098 0 normal SHIPPED_LIVE gnome-shell-extensions, gnome-shell, mutter bug fix and enhancement update 2017-08-01 19:36:42 UTC

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
Note You need to log in before you can comment on or make changes to this bug.