With OpenSuse Leap 42 as the destination machine, Ubuntu 16.04.1 LTS as
the originating machine:
I can login with x2go as root fine, but if I try as any other user I
get standard input inappropriate ioctl for device.
I can ssh with the same user and get no error.
I have made sure I don't have mesg or stty in my .profile and .kshrc
(I am using ksh as the login shell) and if I did it would also cause the same
issue with ssh login.
Can anybody tell me what else to check?…
[View More]
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
[View Less]
Hi all,
I'm running x2go on CentOS 7.x using the following packages:
x2goclient-4.0.1.4-1.el6.x86_64
x2goserver-4.0.1.20-1.el6.x86_64
And when I run the server on my desktop, and then the client so I can
connect to the screen I've setup, I have some minor keyboard
problems. I can use Ctrl-Alt-Left to move inside the Full Screen x2go
session to another panel.
But I cannot move to the right at all, nor does running xev inside the
x2go session show me hitting those keys. Just to note, I'…
[View More]m not
running x2go and shadowing my :0 display (which might be better?)
because I want to lock my session when I leave the office, and pick it
up at home without worrying about people seeing my display while I'm
away.
In any case, my setxkbmap INSIDE my x2go session shows:
> setxkbmap -query
rules: base
model: pc104
layout: us
options: ctrl:nocaps
While outside it shows:
> setxkbmap -query
rules: evdev
model: pc104
layout: us
options: ctrl:nocaps
I'm actually using a tenkeyless CODE keyboard, but I don't think that
makes much difference here. Using the 'gnome-keybinding-properties' I
have the "Switch to workspace on the (left|right) of the current
workspace" setup to be Ctrl+Alt+Left or Ctrl+Alt+Right from what I
see.
Using 'xev' both inside and outside of the x2go client I see different
keycodes for my arrow keys. Outside, in the standard CentOS 7.x Gnome
desktop, I see keycoded 113 (left) and 114 (right), but inside x2go I
see 100 (left) and 102 (right) so there's some mapping going on
somewhere which isn't getting through properly.
For example, inside X2go session, when I press and release the left
arrow key, I get:
KeyPress event, serial 37, synthetic NO, window 0x7400001,
root 0x6e, subw 0x0, time 3164346691, (107,75), root:(109,832),
state 0x0, keycode 100 (keysym 0xff51, Left), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 37, synthetic NO, window 0x7400001,
root 0x6e, subw 0x0, time 3164346811, (107,75), root:(109,832),
state 0x0, keycode 100 (keysym 0xff51, Left), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
So I'm wondering a couple of things.
1. If I edit my ~/.x2go/config/config/keystrokes.cfg file, does it get
re-read automatically or do I have to stop and restart the x2goclient
or the entire x2goserver session to have my changes take effect?
2. Has anyone else seen this issue and have suggestions on how I can
maybe get around this?
Thanks,
John
P.S. I do also have various nx* packages installed, would these be
interferring?
> rpm -qa | grep nx | sort
freenx-0.7.3-9.4.el6.centos.x86_64
libNX_X11-3.5.0.32-3.el6.x86_64
libNX_Xcomposite-3.5.0.32-3.el6.x86_64
libNX_Xdamage-3.5.0.32-3.el6.x86_64
libNX_Xdmcp-3.5.0.32-3.el6.x86_64
libNX_Xext-3.5.0.32-3.el6.x86_64
libNX_Xfixes-3.5.0.32-3.el6.x86_64
libNX_Xinerama-3.5.0.32-3.el6.x86_64
libNX_Xpm-3.5.0.32-3.el6.x86_64
libNX_Xrandr-3.5.0.32-3.el6.x86_64
libNX_Xrender-3.5.0.32-3.el6.x86_64
libNX_Xtst-3.5.0.32-3.el6.x86_64
nxagent-3.5.0.32-3.el6.x86_64
nxclient-3.5.0-7.x86_64
nx-libs-3.5.0.32-3.el6.x86_64
nxproxy-3.5.0.32-3.el6.x86_64
Thanks!
John
[View Less]
1
0
Apt-get dist-upgrade
by "BOTZ Franck (Administrateur Systèmes et Résea ux) - DDT 67/SIDSIC/Pôle Infra"
17 Jan '17
17 Jan '17
Hi
When I dist-upgrade my ubuntu 16.04 x2gobroker, i'"ve got the following
error :
Des erreurs ont été rencontrées pendant l'exécution :
x2gobroker-loadchecker
E: Sub-process /usr/bin/dpkg returned an error code (1)
Any ideas ?
Regards
Franck Botz
On Fri, Jan 13, 2017 at 8:40 PM, Mike DePaulo <mikedep333(a)gmail.com> wrote:
> On Fri, Jan 13, 2017 at 12:48 PM, Stefan Baur <X2Go-ML-1(a)baur-itcs.de>
> wrote:
>>
>> Am 13.01.2017 um 18:43 schrieb Stefan Baur:
>> > Getting the NX-libraries updated is a task that is actively being worked
>> > on - maybe Mike#1 or Ulrich can chime in on when they expect to be able
>> > to support GLX 1.3?
>>
>> Ulrich just replied to me off-…
[View More]list - I'm assuming by accident, as it was
>> sent from his smartphone.
>> His statement was that you shouldn't expect GLX 1.3 support in the
>> NX-libraries in the near future. :-(
>>
>> -Stefan
>>
>
> Well, we do have a workaround for GLX support.
> http://wiki.x2go.org/doku.php/wiki:development:glx-xlib-workaround?s[]=glx
>
> But:
>
> 1. It requires putting the environment variable in a /etc/X11/Xsession.d/
> script . These scripts get launched before the desktop environment is
> started.
> This is very easy shell scripting.
> Note that non-debian-derived distros often use other paths.
> Fedora/RHEL-derived distros use /etc/X11/xinit/xinitrc.d/ .
I think this could be added to x2go as an option. X2go could deliver
that mesa lib and set it the session.
> 2. The build instructions likely vary from distro to distro, and release to
> release.
>
> 3. I have not tested it with entire desktop environments. GNOME3 may have a
> check that will prevent it from working, even if it is otherwise capable of
> working.
Maybe is would help to let the x2goagent report newer version, too, in
that case (even if it is not implemented).
Thanks for reminding me, I had totally forgotten this!
Uli
[View Less]
Hallo!
I am looking for a solution to forward a local USB Device to the server. I would like to the local chipcard (not a sd-card!) reader by applications running on the server. Is there an easy way to manage this task?
Thankfully, Bernhard
Greetings.
Lately whenever I launch GTK+ applications over x2go, the
pull-down menus are usually not displayed properly or at all.
For example, if I launch the Xfce Terminal, I see the usual "File",
"Edit", "View", "Terminal", "Tabs", and "Help" labels in the pull-down
menu bar. If I click on these, they become underlined as though they
are active, but the corresponding pull-down menu doesn't (usually)
appear. Instead, a single pixel in the upper left corner of my desktop
turns white. The …
[View More]only exception is when I click on "Help" -- the first
time I do this, I do get a pull-down menu, but it's attached to the
upper left corner of my desktop, not to the "Help" label in the Terminal
window. The menu is very small, though, and I need to scroll through it
to see all the entries. The second or subquent times I try to view the
"Help" menu, I just get a single pixel.
Similar behaviour is observed in most other GTK+2 and GTK+3
applications, such as the GNOME Terminal and the GNOME Character Map.
The problem is reproducible when launhcing LibreOffice with
SAL_USE_VCLPLUGIN=gtk2 or SAL_USE_VCLPLUGIN=gtk3, but not with
SAL_USE_VCLPLUGIN=kde4 or SAL_USE_VCLPLUGIN=gen. Some (but not all) of
the applications output error messages like this to the console when I
try to activate a pull-down menu:
(gucharmap:26208): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
(gucharmap:26208): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
(gucharmap:26208): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: assertion 'width >= 0' failed
(gucharmap:26208): Gtk-WARNING **: Negative content width -7 (allocation 1, extents 4x4) while allocating gadget (node arrow, owner GtkMenu)
(gucharmap:26208): Gtk-WARNING **: Negative content width -7 (allocation 1, extents 4x4) while allocating gadget (node arrow, owner GtkMenu)
Claws Mail seems to be an exception; it uses GTK+ but its pull-down
menus work fine.
Anyone know what the cause might be and how I can work around it? I'm
running x2goserver-4.0.1.19 on an openSUSE Tumbleweed server and
x2goclient-4.0.5.0 on an openSUSE 13.2 client. The client desktop
environment is KDE 5.
Regards,
Tristan
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Tristan Miller
Free Software developer, ferret herder, logologist
https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
[View Less]
Dear x2goers
I've got an installation where users authenticate against an windows 2008 ad.
Unfortunately they have non posix user names starting with a number (e.g. 16xxxyyy).
My installation works via ssh and direct login on the machine not via x2go though.
Anybody found a solution for this problem?
Thanks in advance.
Ueli
Dear list,
since one of my last updates to my Debian systems x2go behaves differently:
XFCE is my primary window manager. When a user is already logged in
locally to a XFCE session it is not possible to login to the same
system using the XFCE session type in x2goclient.
These are the log messages I can see in the x2goclient log area:
8<=================
...
Info: Forwarding X11 connections to display ':0.0'.
Session: Session started at 'Sat Dec 17 21:19:46 2016'.
Info: Established X …
[View More]server connection.
Info: Using shared memory parameters 0/0K.
8<=================
Shortly, a black window pops up, immediately closes and this is what
is then appended to the x2goclient log area:
8<=================
Session: Terminating session at 'Sat Dec 17 21:19:48 2016'.
Session: Session terminated at 'Sat Dec 17 21:19:48 2016'.
8<=================
Using x2go works like a charm with the XFCE session type in case the
user is not logged in locally.
Any ideas or similar experiences?
Thanks for helping me out,
Rainer
[View Less]