On Thursday 07 May 2015 09:17:37 Mark Wendt wrote:
> On Thu, May 7, 2015 at 9:10 AM, Gene Heskett <[email protected]> wrote:
> > On Thursday 07 May 2015 08:44:26 Gene Heskett wrote:
> > > On Thursday 07 May 2015 05:07:08 Mark Wendt wrote:
> > > > On Thu, May 7, 2015 at 3:20 AM, Gene Heskett <[email protected]>
> >
> > wrote:
> > > > > I have been able to export the x session to this box forever,
> > > > > and it has worked nominally well, till now.
> > > > >
> > > > > But this machine now has debian 7.8 (wheezy) on it, and the
> > > > > lathe just got its drive reformatted and has the
> > > > > binary-hybrid.iso installed on it.
>
> <snippage>
>
> > > ISTR I had to do that at some point back in the fog of ancient
> > > history. That should not be whats killing me now I would think.
> > > It would be one heck of a regression if thats the case. OTOH, I
> > > was never able to use ssh -X because of a similar error, and now
> > > even -Y only works for text terminal's?
> > >
> > > Thanks Mark.
> >
> > Slight correction, a different application that still uses an X
> > remote display, update-manager, still works from the 10.04-4 LTS
> > install thats on the milling machine, on this screen here. So some
> > of it works.
> >
> > Cheers, Gene Heskett
>
> I'm confused a bit. Up above, you said you were having the problems
> on the lathe machine, but in the paragraph just above this, the
> problem is now on the mill machine?
>
> Mark
When attempting run linuxcnc, yes, update-manager will run and remote its
display on the shop,10.04-4 LTS machine, but not on the lathe which is
the new binary-hybrid.iso install.
This is the refusal to run update-manager of the lathe's install, from an
ssh -Y session here:
gene@lathe:~$ sudo update-manager
X11 connection rejected because of wrong authentication.
/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning:
could not open display
warnings.warn(str(e), _gtk.Warning)
X11 connection rejected because of wrong authentication.
[ ERROR:UpdateManager.BugHandler] No exception handler installed.
Traceback (most recent call last):
File "/usr/bin/update-manager", line 37, in <module>
app = Application(APP_NAME, LOCALE_DIR, frontend='Gtk')
File "/usr/lib/pymodules/python2.7/UpdateManager/Application.py", line
120, in __init__
self._load_frontend(frontend)
File "/usr/lib/pymodules/python2.7/UpdateManager/Application.py", line
201, in _load_frontend
"frontend", FrontendBase)
File "/usr/lib/pymodules/python2.7/UpdateManager/Application.py", line
240, in _load_meta
obj = symbol(*module_args, **module_kwargs)
File "/usr/lib/pymodules/python2.7/UpdateManager/Frontend/Gtk/__init__.py",
line 59, in __init__
gtk.init_check()
RuntimeError: could not open display
So WTH is this wrong authenification?
The above was snapshoted after commenting out the extra line
in /etc/ssh/sshd_config and restarting the ssh daemons on both machines.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users