[Touch-packages] [Bug 1463263] Re: X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from 14.10
** Changed in: mir (Ubuntu)
Assignee: (unassigned) = Chris Halse Rogers (raof)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1463263
Title:
X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from
14.10
Status in mir package in Ubuntu:
New
Bug description:
More detail posted here:
http://ubuntuforums.org/showthread.php?t=2281659p=13300597
surfrock66@sr66-blade:~$ lsb_release -rd
Description: Ubuntu 15.04
Release: 15.04
I performed an in-place upgrade from 14.10 - 15.04. Now, GTK apps
will not X11 forward. I was under the impression that Mir would not be
in place until 15.10 which was when I would have probably held back on
upgrading; I believe that other gtk packages have been modified with
hooks in preparation to support Mir, and that these updates have
broken X11 forwarding
Some sample command output from the client I am using to connect from:
surfrock66@sr66-blade:/$ easytag
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
(easytag:13278): Gtk-WARNING **: cannot open display:
surfrock66@sr66-blade:/$ baobab
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
surfrock66@sr66-blade:/$ gedit
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
(gedit:13348): Gtk-WARNING **: cannot open display:
The server does have an X session running, and I can X11 forward from
other devices so I know my client (X11 server) works.
I've done some research:
http://ubuntuforums.org/showthread.php?t=2266456
http://ubuntuforums.org/showthread.php?t=2256737
x2go still works, but X11 forwarding was a huge part of my workflow
and I'm extremely ticked off, I've been trying to troubleshoot it
since the day 15.04 came out.
Host server is my home server; a Dell poweredge SC 1425 in my server
closet.
I ran tried from 3 clients, got the same results on each:
Debian Sid laptop over the LAN, ssh session using a shortcut created when
it was working on 14.10
Windows work laptop using Cygwin over the WAN, ssh session using a
shortcut created when it was working on 14.10
Windows work laptop using MobaXterm over the WAN, fresh ssh session.
All 3 clients can successfully run an X11 forwarded client from
another computer (all 3 were my System76 desktop running from my
house)
I have an alias to connect to my server; the command is ssh -p
-X IP and in that, echo $DISPLAY returns a blank line. If I get
into the server over x2go or VNC, echo $DISPLAY returns :0.
On my laptop (the client machine, with the X11 Server):
surfrock66@sr66-darter:~$ egrep -i forward /etc/ssh/sshd_config
X11Forwarding yes
On the server (the X11 client):
surfrock66@sr66-blade:~$ egrep -i forward /etc/ssh/sshd_config
X11Forwarding yes
From this client laptop, I invoke X-11 forwarded apps in 2 ways; the
aliased ssh connection string, and from a shortcut in my awesomeWM
menu. Here's the strings for both (I blocked the port numbers):
# SSH Shortcuts
alias hda='ssh -p -X hda.surfrock66.com'
alias mc='ssh -p teh3l3m3...@mc.teh3l3m3nts.com'
alias sr66-darter='ssh -p -X 192.168.1.65'
alias sr66-dell='ssh -p -X 192.168.1.47'
#alias sr66-hp='ssh -p 192.168.1.10'
alias sr66-hp='ssh -p -X sr66-hp.hda.surfrock66.com'
alias sr66-nas='ssh -p surfrock66@192.168.1.36'
alias sr76='ssh -p -X sr76.hda.surfrock66.com'
All of them are initiating client sessions that should permit X11
forwarding. Now for the AwesomeWM shortcuts:
myhdaforwardedapps = {
{ Baobab, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
baobab' },
{ EasyTag, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
easytag' },
{ File Manager, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
pcmanfm' },
{ Terminator, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
terminator' },
}
All of these shortcuts worked before the upgrade.
I am happy to provide any additional information.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1463263/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help :
[Touch-packages] [Bug 1463263] Re: X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from 14.10
The following mir-related packages are installed:
surfrock66@sr66-blade:~/.scripts$ dpkg --get-selections | grep -v deinstall |
grep -i mir
libmirclient8:amd64 install
libmircommon3:amd64 install
libmirprotobuf0:amd64 install
mir-client-platform-mesa2:amd64 install
** Package changed: ubuntu = mir (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1463263
Title:
X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from
14.10
Status in mir package in Ubuntu:
New
Bug description:
More detail posted here:
http://ubuntuforums.org/showthread.php?t=2281659p=13300597
surfrock66@sr66-blade:~$ lsb_release -rd
Description: Ubuntu 15.04
Release: 15.04
I performed an in-place upgrade from 14.10 - 15.04. Now, GTK apps
will not X11 forward. I was under the impression that Mir would not be
in place until 15.10 which was when I would have probably held back on
upgrading; I believe that other gtk packages have been modified with
hooks in preparation to support Mir, and that these updates have
broken X11 forwarding
Some sample command output from the client I am using to connect from:
surfrock66@sr66-blade:/$ easytag
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
(easytag:13278): Gtk-WARNING **: cannot open display:
surfrock66@sr66-blade:/$ baobab
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
surfrock66@sr66-blade:/$ gedit
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
(gedit:13348): Gtk-WARNING **: cannot open display:
The server does have an X session running, and I can X11 forward from
other devices so I know my client (X11 server) works.
I've done some research:
http://ubuntuforums.org/showthread.php?t=2266456
http://ubuntuforums.org/showthread.php?t=2256737
x2go still works, but X11 forwarding was a huge part of my workflow
and I'm extremely ticked off, I've been trying to troubleshoot it
since the day 15.04 came out.
Host server is my home server; a Dell poweredge SC 1425 in my server
closet.
I ran tried from 3 clients, got the same results on each:
Debian Sid laptop over the LAN, ssh session using a shortcut created when
it was working on 14.10
Windows work laptop using Cygwin over the WAN, ssh session using a
shortcut created when it was working on 14.10
Windows work laptop using MobaXterm over the WAN, fresh ssh session.
All 3 clients can successfully run an X11 forwarded client from
another computer (all 3 were my System76 desktop running from my
house)
I have an alias to connect to my server; the command is ssh -p
-X IP and in that, echo $DISPLAY returns a blank line. If I get
into the server over x2go or VNC, echo $DISPLAY returns :0.
On my laptop (the client machine, with the X11 Server):
surfrock66@sr66-darter:~$ egrep -i forward /etc/ssh/sshd_config
X11Forwarding yes
On the server (the X11 client):
surfrock66@sr66-blade:~$ egrep -i forward /etc/ssh/sshd_config
X11Forwarding yes
From this client laptop, I invoke X-11 forwarded apps in 2 ways; the
aliased ssh connection string, and from a shortcut in my awesomeWM
menu. Here's the strings for both (I blocked the port numbers):
# SSH Shortcuts
alias hda='ssh -p -X hda.surfrock66.com'
alias mc='ssh -p teh3l3m3...@mc.teh3l3m3nts.com'
alias sr66-darter='ssh -p -X 192.168.1.65'
alias sr66-dell='ssh -p -X 192.168.1.47'
#alias sr66-hp='ssh -p 192.168.1.10'
alias sr66-hp='ssh -p -X sr66-hp.hda.surfrock66.com'
alias sr66-nas='ssh -p surfrock66@192.168.1.36'
alias sr76='ssh -p -X sr76.hda.surfrock66.com'
All of them are initiating client sessions that should permit X11
forwarding. Now for the AwesomeWM shortcuts:
myhdaforwardedapps = {
{ Baobab, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
baobab' },
{ EasyTag, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
easytag' },
{ File Manager, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
pcmanfm' },
{ Terminator, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
terminator' },
}
All of these shortcuts worked before the upgrade.
I am happy to provide any
[Touch-packages] [Bug 1463263] Re: X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from 14.10
The gdk_mir_display_open error is just GDK/GTK trying to use Mir
because it found no X11 server ($DISPLAY is blank). That's not a Mir
bug.
You are not trying to use Mir, and Mir does not seem to be responsible
for the breakage either. If the system was not broken then $DISPLAY
would be set to something correct (like :0) and GDK would not be
trying to fall back to Mir.
** Changed in: mir (Ubuntu)
Status: New = Invalid
** Package changed: mir (Ubuntu) = ubuntu
** Changed in: ubuntu
Status: Invalid = New
** Also affects: mir
Importance: Undecided
Status: New
** Changed in: mir
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1463263
Title:
X11 Forwarding is broken following upgrade to Ubuntu Server 15.04 from
14.10
Status in Mir:
Invalid
Status in Ubuntu:
New
Bug description:
More detail posted here:
http://ubuntuforums.org/showthread.php?t=2281659p=13300597
surfrock66@sr66-blade:~$ lsb_release -rd
Description: Ubuntu 15.04
Release: 15.04
I performed an in-place upgrade from 14.10 - 15.04. Now, GTK apps
will not X11 forward. I was under the impression that Mir would not be
in place until 15.10 which was when I would have probably held back on
upgrading; I believe that other gtk packages have been modified with
hooks in preparation to support Mir, and that these updates have
broken X11 forwarding
Some sample command output from the client I am using to connect from:
surfrock66@sr66-blade:/$ easytag
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
(easytag:13278): Gtk-WARNING **: cannot open display:
surfrock66@sr66-blade:/$ baobab
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
surfrock66@sr66-blade:/$ gedit
gdk_mir_display_open
Failed to connect to Mir: Failed to connect to server socket: No such
file or directory
Unable to init server: Could not connect: Connection refused
(gedit:13348): Gtk-WARNING **: cannot open display:
The server does have an X session running, and I can X11 forward from
other devices so I know my client (X11 server) works.
I've done some research:
http://ubuntuforums.org/showthread.php?t=2266456
http://ubuntuforums.org/showthread.php?t=2256737
x2go still works, but X11 forwarding was a huge part of my workflow
and I'm extremely ticked off, I've been trying to troubleshoot it
since the day 15.04 came out.
Host server is my home server; a Dell poweredge SC 1425 in my server
closet.
I ran tried from 3 clients, got the same results on each:
Debian Sid laptop over the LAN, ssh session using a shortcut created when
it was working on 14.10
Windows work laptop using Cygwin over the WAN, ssh session using a
shortcut created when it was working on 14.10
Windows work laptop using MobaXterm over the WAN, fresh ssh session.
All 3 clients can successfully run an X11 forwarded client from
another computer (all 3 were my System76 desktop running from my
house)
I have an alias to connect to my server; the command is ssh -p
-X IP and in that, echo $DISPLAY returns a blank line. If I get
into the server over x2go or VNC, echo $DISPLAY returns :0.
On my laptop (the client machine, with the X11 Server):
surfrock66@sr66-darter:~$ egrep -i forward /etc/ssh/sshd_config
X11Forwarding yes
On the server (the X11 client):
surfrock66@sr66-blade:~$ egrep -i forward /etc/ssh/sshd_config
X11Forwarding yes
From this client laptop, I invoke X-11 forwarded apps in 2 ways; the
aliased ssh connection string, and from a shortcut in my awesomeWM
menu. Here's the strings for both (I blocked the port numbers):
# SSH Shortcuts
alias hda='ssh -p -X hda.surfrock66.com'
alias mc='ssh -p teh3l3m3...@mc.teh3l3m3nts.com'
alias sr66-darter='ssh -p -X 192.168.1.65'
alias sr66-dell='ssh -p -X 192.168.1.47'
#alias sr66-hp='ssh -p 192.168.1.10'
alias sr66-hp='ssh -p -X sr66-hp.hda.surfrock66.com'
alias sr66-nas='ssh -p surfrock66@192.168.1.36'
alias sr76='ssh -p -X sr76.hda.surfrock66.com'
All of them are initiating client sessions that should permit X11
forwarding. Now for the AwesomeWM shortcuts:
myhdaforwardedapps = {
{ Baobab, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
baobab' },
{ EasyTag, xterm -e 'ssh -X -p ### surfrock66@192.168.1.22 -t
easytag' },
{ File Manager, xterm
