Bug 1033199

Summary: [abrt] mutter-wayland-3.10.1-1.fc20: _g_log_abort: Process /usr/bin/mutter-wayland was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Anonymous <lampshade>
Component: mutter-waylandAssignee: Florian Müllner <fmuellner>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: fmuellner, lampshade, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/0a71506e07c575240ab3e18b582830c328939615
Whiteboard: abrt_hash:de9f8ab62faa83922435ea855f5b9c6af7634d14
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:06:07 UTC Type: ---
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
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Anonymous 2013-11-21 17:05:30 UTC 
Description of problem:
I logged off from normal Xorg session. I changed another vt and logged as root. I typed: service gdm stop. Then logged off. Logged as a normal user and then typped: mutter-launch -- mutter-wayland --wayland
And crash occured.

Version-Release number of selected component:
mutter-wayland-3.10.1-1.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        mutter-wayland --wayland
crash_function: _g_log_abort
executable:     /usr/bin/mutter-wayland
kernel:         3.11.6-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 _g_log_abort at gmessages.c:255
 #5 clutter_device_manager_evdev_add_device at evdev/clutter-device-manager-evdev.c:1027
 #6 _clutter_device_manager_add_device at ./clutter-device-manager.c:342
 #7 evdev_add_device at evdev/clutter-device-manager-evdev.c:919
 #8 clutter_device_manager_evdev_probe_devices at evdev/clutter-device-manager-evdev.c:1127
 #9 clutter_device_manager_evdev_constructed at evdev/clutter-device-manager-evdev.c:1200
 #10 g_object_new_internal at gobject.c:1785
 #11 g_object_new_valist at gobject.c:2002
 #13 _clutter_events_evdev_init at evdev/clutter-device-manager-evdev.c:1378
 #14 clutter_init_real at ./clutter-main.c:1608
Comment 1 Anonymous 2013-11-21 17:05:45 UTC 
Created attachment 827364 [details]
File: backtrace
Comment 2 Anonymous 2013-11-21 17:05:52 UTC 
Created attachment 827365 [details]
File: cgroup
Comment 3 Anonymous 2013-11-21 17:05:55 UTC 
Created attachment 827366 [details]
File: core_backtrace
Comment 4 Anonymous 2013-11-21 17:05:58 UTC 
Created attachment 827367 [details]
File: dso_list
Comment 5 Anonymous 2013-11-21 17:06:02 UTC 
Created attachment 827368 [details]
File: environ
Comment 6 Anonymous 2013-11-21 17:06:06 UTC 
Created attachment 827369 [details]
File: limits
Comment 7 Anonymous 2013-11-21 17:06:10 UTC 
Created attachment 827370 [details]
File: maps
Comment 8 Anonymous 2013-11-21 17:06:14 UTC 
Created attachment 827371 [details]
File: open_fds
Comment 9 Anonymous 2013-11-21 17:06:19 UTC 
Created attachment 827372 [details]
File: proc_pid_status
Comment 10 Anonymous 2013-11-21 17:06:22 UTC 
Created attachment 827373 [details]
File: var_log_messages
Comment 11 Fedora End Of Life 2015-05-29 09:49:29 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 12 Fedora End Of Life 2015-06-29 13:06:07 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.