Bug 1428374

Summary: terminator dosn't start on wayland after update
Product: [Fedora] Fedora Reporter: Frederik <allyouneedis>
Component: terminatorAssignee: Dominic Hopf <dmaphy>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: dmaphy, mattrose
Target Milestone: ---   
Target Release: ---   
Hardware: noarch   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-02 14:01:08 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 Frederik 2017-03-02 12:34:30 UTC
Description of problem:
after update terminator dosn't start anymore
(updates repo)

Version-Release number of selected component (if applicable):
Version     : 1.91
Release     : 1.fc25

error message:
$ terminator
keybindings.reload failed to parse binding '<Alt><Meta>F3': Unhandled modifier '<Meta>'
keybindings.reload failed to parse binding '<Alt><Meta>F3': Unhandled modifier '<Meta>'
Traceback (most recent call last):
  File "/usr/bin/terminator", line 126, in <module>
    TERMINATOR.layout_done()
  File "/usr/lib/python2.7/site-packages/terminatorlib/terminator.py", line 402, in layout_done
    t = GdkX11.x11_get_server_time(window.get_window())
TypeError: argument window: Expected GdkX11.X11Window, but got __gi__.GdkWaylandWindow

How reproducible:
allways

Steps to Reproduce:
1. install/update terminator
2. start wayland session
3. run terminator

Actual results:
terminator crashes

Expected results:
terminator starts as it did before update

Additional info:
-

Comment 1 Frederik 2017-03-02 12:38:12 UTC
just for good measure here's the ticket for the update: https://bugzilla.redhat.com/show_bug.cgi?id=1397825

Comment 2 Matt Rose 2017-03-02 14:01:08 UTC

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