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
Bug 1295028 - session becomes unresponsive when evolution/wayland starts
Summary: session becomes unresponsive when evolution/wayland starts
Alias: None
Product: Fedora
Classification: Fedora
Component: weston
Version: 23
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: WaylandRelated
TreeView+ depends on / blocked
Reported: 2016-01-01 04:14 UTC by smitna
Modified: 2016-12-20 17:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-12-20 17:31:47 UTC
Type: Bug

Attachments (Terms of Use)

Description smitna 2016-01-01 04:14:24 UTC
Description of problem:
See summary.

Version-Release number of selected component (if applicable):
Name        : weston
Version     : 1.9.0
Release     : 1.fc23
Architecture: x86_64

Name        : evolution
Version     : 3.18.3
Release     : 1.fc23
Architecture: x86_64

Steps to Reproduce:

1)  create ~/.config/weston.ini so that it contains only the following 2 lines:

2)  login to a weston session (weston-launch)

3)  open weston-terminal and run the following command:
$ dbus-run-session -- env GDK_BACKEND=wayland evolution

Actual results:

Session becomes unresponsive to further keyboard/mouse inputs including Ctrl-Alt-Backspace.
Exception:  magic SysRq key (

Additional info:

1)  substituting step 3 with a different wayland application seems to work fine; e.g.:
$ dbus-run-session -- env GDK_BACKEND=wayland epiphany

2)  substituting step 3 with a different GDK_BACKEND value seems to work fine; e.g.:
$ dbus-run-session -- env GDK_BACKEND=x11 evolution

3)  if ~/.config/weston.ini does not exist, all "Steps to Reproduce" after #1 seem to work fine.

Comment 1 Fedora End Of Life 2016-11-24 14:38:13 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 2 Fedora End Of Life 2016-12-20 17:31:47 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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

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

Note You need to log in before you can comment on or make changes to this bug.