After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 773418 - gnome-terminal open in wrong VT
gnome-terminal open in wrong VT
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Wayland
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: wayland
 
 
Reported: 2016-10-24 12:07 UTC by Tapani Pälli
Modified: 2018-05-02 17:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tapani Pälli 2016-10-24 12:07:50 UTC 
Steps to reproduce:

1. run regular (in my case gnome3 desktop) environment with X
2. switch to another VT and launch weston there
3. switch back to first VT with X, launch gnome-terminal

Observation is that no gnome-terminal shows up, if I switch to VT that has Weston, I see it there. My expectation is that terminal would launch on the same VT I'm on.

I'm running Fedora release 24 and Gnome3 desktop and Weston 1.10.

Another observation (perhaps another bug) is that copy-paste from gnome-terminal in VT where X is can crash that terminal (after those steps), also I believe I've managed to crash gnome-terminal in X VT by killing Weston.

(Sorry if I filed this to wrong component.)
Comment 1 Tapani Pälli 2016-10-25 04:23:31 UTC 
add dependency to wayland tracker bug
Comment 2 Tapani Pälli 2016-10-25 07:26:17 UTC 
Additional note I forgot to add to description, I do not have WAYLAND_DISPLAY environment variable set in the X environment. I believe this could be used to detect which display server/compositor is preferred?
Comment 3 GNOME Infrastructure Team 2018-05-02 17:41:29 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/693.