Bug 1396834 - gtk3 problem with ssh -X (Ubuntu 16.10 X server)
Summary: gtk3 problem with ssh -X (Ubuntu 16.10 X server)
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk3
Version: 26
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-20 18:02 UTC by Paul Eggert
Modified: 2018-05-03 20:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-03 20:41:02 UTC
Type: Bug


Attachments (Terms of Use)

Description Paul Eggert 2016-11-20 18:02:11 UTC
Description of problem:

When I log in from my Ubuntu 16.10 laptop to a Fedora 24 server via "ssh -X" and then run the shell command "emacs" to get an X-based Emacs, I occasionally get this diagnostic sent to stderr:

Xlib:  extension "XInputExtension" missing on display "localhost:10.0".

I can reliably reproduce the problem by hovering the mouse pointer over the word "File" in the upper-left-hand corner of Emacs.

This appears to be related to GNOME bug 766233; see:

https://bugzilla.gnome.org/show_bug.cgi?id=766233

Version-Release number of selected component (if applicable):

$ rpm -q gtk3
gtk3-3.20.9-1.fc24.x86_64
$ rpm -q emacs
emacs-25.1-2.fc24.x86_64

Comment 1 Paul Eggert 2016-11-20 18:51:54 UTC
I do not see this problem when connecting via ssh -X from my Ubuntu 16.04 desktop. So it appears that something is different about Ubuntu 16.10, when it connects to Fedora.

Comment 2 Fedora End Of Life 2017-07-25 23:57:30 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 3 Paul Eggert 2017-07-26 03:21:53 UTC
I am still seeing this problem with Fedora 26, when logging in from an Ubuntu 17.04 laptop, so I am changing the version number of this bug report to 26. (There is still no problem in connecting from Ubuntu 16.04.2 LTS to Fedora 26.) The version-release number of the components in question are now:

$ rpm -q gtk3
gtk3-3.22.16-1.fc26.x86_64
$ rpm -q emacs
emacs-25.2-3.fc26.x86_64

Comment 4 Fedora End Of Life 2018-05-03 08:19:22 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 5 Paul Eggert 2018-05-03 20:41:02 UTC
I no longer observe the problem when logging into Fedora 28 from either Ubuntu 18.04 or Ubuntu 17.10, so I am closing the bug. Perhaps it was fixed upstream.


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