[opensuse] Running remote aps stopped working after upgrade from 42.1 to 42.2
Hello,
I usually ssh to a system and run various applications. I do have ssh
configured to allow root access from a specfic IP to a specific IP. I
can't seem to get the following applications to work there were several
others. I just can't seem to remember then right now.
ssh -X -Y -p xxxx remote_host
firefox &
seamonkey &
....
ssh -X -Y -p xxxx remote_host sudo yast2
ssh -X -Y -p xxxx root@remote_host
yast2 &
yast2 --qt &
running either of the above the only thing I see/get on my ssh window is
qt5ct: using qt5ct plugin
Before the upgrade I could run yast2 on a Leap 42.2 or Leap 42.1 system.
Now nothing ever shows up.
these work
yast2 --gtk &
yast2 --ncurses
libreoffice &
chromium &
Any ideas?
Thanks,
--
Boyd Gerber
On 03/09/2017 11:29 AM, Boyd Lynn Gerber wrote:
I usually ssh to a system and run various applications. I do have ssh configured to allow root access from a specfic IP to a specific IP. I can't seem to get the following applications to work there were several others. I just can't seem to remember then right now.
ssh -X -Y -p xxxx remote_host
This works for me ssh jsa@myremote-host -p xxxx /usr/bin/xdg-su -c /sbin/yast2 I do not find that I nded -X or -Y because allow xll forwarding is set on in my ssh config. I use KDE/Plasma and I found that anything can be started by just substituting the entire Command in the kde menu, which is often a bit more than just the application name. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
John Andersen wrote:
This works for me ssh jsa@myremote-host -p xxxx /usr/bin/xdg-su -c /sbin/yast2
&--- Patrick Shanahan wrote:
I use: ssh -X <user>@<domain> and su to root after I get there
and I seem to have no problems running graphic applications.
--- How are those options different from him using ssh -X -Y -p xxxx remote_host sudo yast2 or ssh -X -Y -p xxxx root@remote_host yast2 & yast2 --qt & I.e. does 'sudo' not work (the 1st case), or does logging in _as_root_ (2nd case) and then running the X-app, not work any more? @Boyd: In both cases, have you looked at the contents of "DISPLAY" ? Usually ssh would set DISPLAY to something like: "localhost:10" (or such.) When you say "doesn't work" you don't indicate what it does (i.e. does it hang, or just return to the command prompt?)... It might be sudo isn't preserving 'DISPLAY', in the 1st case, and, perhaps, 'ssh' isn't preserving it in the 2nd case, but those are just guesses... Good luck! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday 2017-03-10 13:39, L A Walsh wrote:
John Andersen wrote:
This works for me ssh jsa@myremote-host -p xxxx /usr/bin/xdg-su -c /sbin/yast2
How are those options different from him using
ssh -X -Y -p xxxx remote_host sudo yast2 or ssh -X -Y -p xxxx root@remote_host yast2 & yast2 --qt &
I.e. does 'sudo' not work (the 1st case), or does logging in _as_root_ (2nd case) and then running the X-app, not work any more?
The issue is the Applicaion doesn't display on the computer I'm ssh-ing
in from. I have never had a problem since SUSU/OpenSUSE 8.X I can't
remember.
I have let the connection wait 2 hours and still nothing is displaying.
I was doing it without any problems on Leap 42.1.
I would see
qt5ct: using qt5ct plugin
and then yast2 would be displayed on my computer using 42.1.
The DISPLAY has to be set properly or yast2 --gtk & would not come up.
or chromium.
I still using the same Desktop just the newer version. I believe I'm
using KDE/Plasma.
Just doesn't make sense that some Applications like chromium or
libreoffice don't have a problem.
I use firefox, seamonkey and yast2 a lot and to suddenly have them not
working/displaying on my Desktop is really frustrating.
What doesn't make sense is any remote Linux system doesn't display
seamonkey or firefox. RH, Centos, OpenSUSE any version.
OpenSUSE yast2 from 13.2-Leap 42.2. All don't ever come up with a
DISPLAY.
--
Boyd Gerber
On 03/10/2017 02:03 PM, Boyd Lynn Gerber wrote:
The issue is the Applicaion doesn't display on the computer I'm ssh-ing in from. I have never had a problem since SUSU/OpenSUSE 8.X I can't remember.
I have let the connection wait 2 hours and still nothing is displaying.
If you wait two minutes you are doing it wrong. If its not displaying in 20 seconds its not going to display. Things to check: What ssh protocol on the other end? 1 or 2? Does the other end allow X-11 forwarding? Can you connect with just a simple ssh command (not trying to run yast or anything else). You've yet to tell us if you've4 tried the things we have mentioned or you prefer to echo back the same complaint multiple times. Ball is in your court. Whining won't solve the problem. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday 2017-03-10 21:04, John Andersen wrote:
On 03/10/2017 02:03 PM, Boyd Lynn Gerber wrote:
The issue is the Applicaion doesn't display on the computer I'm ssh-ing in from. I have never had a problem since SUSU/OpenSUSE 8.X I can't remember.
I have let the connection wait 2 hours and still nothing is displaying.
If you wait two minutes you are doing it wrong. If its not displaying in 20 seconds its not going to display.
Things to check: What ssh protocol on the other end? 1 or 2?
Only protocol 2. The sshd_config has not changed in over 5 years. I told you most apps run. If all the things your asking weren't there no applications would work.
Does the other end allow X-11 forwarding? Can you connect with just a simple ssh command (not trying to run yast or anything else).
yes, Al I sead in my first email. chormium, liebreoffice work. Many Many more only a handful do not work.
You've yet to tell us if you've4 tried the things we have mentioned or you prefer to echo back the same complaint multiple times.
No your the one not listening. This configuration has worked since openSUSE 8.X. Almost since the very first release of openSUSE. This exact same configuration was working with Leap 42.1 to any Linux Distribution. Only the upgrade to Leap 42.2 a small few things don't work anymore.
Ball is in your court. Whining won't solve the problem.
I not whining. I am stating facts. yast2 --gtk works only yast2 --qt
doesn't. Firefox will not work. Gwenview will not work. Ocular will
not work. xeyes works as almost all X applications. The
sshd_configuration has to be correct or nothing would work!
--
Boyd Gerber
On 2017-03-13 03:52, Boyd Lynn Gerber wrote:
On Friday 2017-03-10 21:04, John Andersen wrote:
On 03/10/2017 02:03 PM, Boyd Lynn Gerber wrote:
The issue is the Applicaion doesn't display on the computer I'm ssh-ing in from. I have never had a problem since SUSU/OpenSUSE 8.X I can't remember.
I have let the connection wait 2 hours and still nothing is displaying.
If you wait two minutes you are doing it wrong. If its not displaying in 20 seconds its not going to display.
Things to check: What ssh protocol on the other end? 1 or 2?
Only protocol 2. The sshd_config has not changed in over 5 years.
I told you most apps run. If all the things your asking weren't there no applications would work.
Does the other end allow X-11 forwarding? Can you connect with just a simple ssh command (not trying to run yast or anything else).
yes, Al I sead in my first email. chormium, liebreoffice work. Many Many more only a handful do not work.
You've yet to tell us if you've4 tried the things we have mentioned or you prefer to echo back the same complaint multiple times.
No your the one not listening. This configuration has worked since openSUSE 8.X. Almost since the very first release of openSUSE. This exact same configuration was working with Leap 42.1 to any Linux Distribution. Only the upgrade to Leap 42.2 a small few things don't work anymore.
Ball is in your court. Whining won't solve the problem.
I not whining. I am stating facts. yast2 --gtk works only yast2 --qt doesn't. Firefox will not work. Gwenview will not work. Ocular will not work. xeyes works as almost all X applications. The sshd_configuration has to be correct or nothing would work!
Sorry, it wasn't clear from your initial post that some apps work and some doesn't, I assume now that using the exact same ssh command. And you haven't commented on what we wrote, so we could only speculate. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
Boyd Lynn Gerber wrote:
The DISPLAY has to be set properly or yast2 --gtk & would not come up. or chromium.
But you said this didn't work: ssh -X -Y -p xxxx root@remote_host yast2 & yast2 --qt & Right? Also in this: ssh -X -Y -p xxxx remote_host sudo yast2 You need to show 'DISPLAY' after your sudo, like: sudo bash -c 'echo "DISP=$DISPLAY"; yast2' I'm betting you have some improved su/sudo or config files with them that improve your security by wiping 'DISPLAY' -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-03-11 13:48, L A Walsh wrote:
I'm betting you have some improved su/sudo or config files with them that improve your security by wiping 'DISPLAY'
One day I could not connect because the "port" was wrong, gave some misleading error. Another day because I wrote the local network name of the server instead of the internet name. Another day because the DNS had not been updated to the changed remote IP, it had failed. The user name can also be wrong (the OP is using default). All that has to be verified. Then also go in one step. Not "sudo" and "ssh" in one line. Go one command by one, check what works what doesn't. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
On 03/11/2017 06:48 AM, L A Walsh wrote:
I'm betting you have some improved su/sudo or config files with them that improve your security by wiping 'DISPLAY'
That's why using 'ssh -Y' alone (without -X) enables trusted X11 forwarding and isn't subjected to X11 SECURITY extension restrictions. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-03-11 22:09, David C. Rankin wrote:
On 03/11/2017 06:48 AM, L A Walsh wrote:
I'm betting you have some improved su/sudo or config files with them that improve your security by wiping 'DISPLAY'
That's why using 'ssh -Y' alone (without -X) enables trusted X11 forwarding and isn't subjected to X11 SECURITY extension restrictions.
I understand you should use either -Y or -X, but not both. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
On Saturday 2017-03-11 04:48, L A Walsh wrote:
Boyd Lynn Gerber wrote:
The DISPLAY has to be set properly or yast2 --gtk & would not come up. or chromium.
But you said this didn't work:
ssh -X -Y -p xxxx root@remote_host yast2 & yast2 --qt &
Right?
yes, but yast --gtk & does
Also in this: ssh -X -Y -p xxxx remote_host sudo yast2
You need to show 'DISPLAY' after your sudo, like: sudo bash -c 'echo "DISP=$DISPLAY"; yast2'
I'm betting you have some improved su/sudo or config files with them that improve your security by wiping 'DISPLAY'
would make sense if
yast2 --ncurses
yast2 --gtk
didn't work.
--
Boyd Gerber
On 03/10/2017 1:39 PM, L A Walsh wrote:
How are those options different from him using
ssh -X -Y -p xxxx remote_host sudo yast2
They differ in that my way works, and his way doesn't. If you look at the command line in KDE's menu, you will see that they package yast2 as below:
This works for me ssh jsa@myremote-host -p xxxx /usr/bin/xdg-su -c /sbin/yast2
A default install does not allow logging in as root so you have to log in as a user, and then run the program EXACTLY as set up in the default Desktop menuing system. The menuing system does exactly
/usr/bin/xdg-su -c /sbin/yast2 and delivers a graphical Yast.
Your way delivers a text mode yast if anything at all. These things are wrapped in xdg-su because they need a password for root. Firefox and seamonkey don't need a password, so they don't need the xdg-su wrapper. However, that doesn't mean they will run if the target machine's sshd does not allow forwarding X11. Even his -X parameter doesn't get around that. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Boyd Lynn Gerber
Hello,
I usually ssh to a system and run various applications. I do have ssh configured to allow root access from a specfic IP to a specific IP. I can't seem to get the following applications to work there were several others. I just can't seem to remember then right now.
ssh -X -Y -p xxxx remote_host
firefox & seamonkey & ...
ssh -X -Y -p xxxx remote_host sudo yast2
ssh -X -Y -p xxxx root@remote_host yast2 & yast2 --qt &
running either of the above the only thing I see/get on my ssh window is qt5ct: using qt5ct plugin
Before the upgrade I could run yast2 on a Leap 42.2 or Leap 42.1 system. Now nothing ever shows up.
these work yast2 --gtk & yast2 --ncurses libreoffice & chromium &
Any ideas?
I use: ssh -X <user>@<domain> and su to root after I get there and I seem to have no problems running graphic applications. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-03-09 20:29, Boyd Lynn Gerber wrote:
Hello,
I usually ssh to a system and run various applications. I do have ssh configured to allow root access from a specfic IP to a specific IP. I can't seem to get the following applications to work there were several others. I just can't seem to remember then right now.
ssh -X -Y -p xxxx remote_host
The normal syntax is ssh -X -p number remote_user@remote_host then su to root if wanted. If the "number" is wrong you will get no response. You don't use -X and -Y in the same command. If you don't specify the "remote_user@" the system will try the same username as you have on the client. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
participants (6)
-
Boyd Lynn Gerber -
Carlos E. R. -
David C. Rankin -
John Andersen -
L A Walsh -
Patrick Shanahan