Re: [X2Go-User] Can we have some old rpms in the x2go.repo?

[Mihai Moldovan]

* On 03/15/2018 05:23 AM, Norman Gaywood wrote:
> If I connect, suspend the session, resume the session. I can then move my
> session across screens.
> Worked for me a few times so far.
Hmm, I just tried that right now and couldn't. nxagent crashes, even after
suspending and resuming the session before moving it to another display.


> Not sure I can in a useful manner, but:
> I keep changing my connection screen size to many different sizes.
> I'm not sure how to report my physical workstation screen sizes but:
> Dell 27" 2560x1440, Dell 29" 2560x1018

Okay, with configuration I meant something like that:

 ___  ___
| P || S |
| 2560x1440 || 2560x1018 |
|   | ---
 ---

Where P denotes a primary display and S a secondary one. Marking just the
primary would also be okay, since there can only be one™.

In this configuration, the secondary display is east of the other one and
aligned at the top.

Anyway, I am retracting my initial assessment, I can reproduce the crashing when
moving nxagent windows around display, but only iff the display sizes differ.

With two displays of the same size, this doesn't happen.


> The workstation x2goclient is x2goclient-4.1.1.0-1.fc27.x86_64
> 
> All desktop environments on the server(s) are
> XFCE, xfce4-session-4.12.1-12.fc27.x86_64
> The server(s) are running:
> libNX_X11-6-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
> libXcompext3-3.5.0.33-0.0x2go1.1.git20180204.776.main.fc27.x86_64
> nxagent-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
> nx-libs-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
> nxproxy-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
> perl-X2Go-Log-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> perl-X2Go-Server-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> perl-X2Go-Server-DB-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-common-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-extensions-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-x2goagent-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-xsession-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> 
> The prod server would have mostly Windows x2go clients connecting, but some 
> Mac
> and some Linux, all different versions.
> The dev server would only have x2goclient-4.1.1.0-1.fc27.x86_64 connecting.
>   
> The servers (dev and prod) are Fedora  27 running:
> libNX_X11-6-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
> libXcompext3-3.5.0.33-0.0x2go1.1.git20180204.776.main.fc27.x86_64
> nxagent-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
> nx-libs-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
> nxproxy-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
> perl-X2Go-Log-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> perl-X2Go-Server-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> perl-X2Go-Server-DB-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-common-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-extensions-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-x2goagent-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
> x2goserver-xsession-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64

Everything's okay. You have an old version of libXcompext3 installed, but it's
an orphaned leaf and won't cause trouble since nothing links against it.

You may remove it manually if you wish.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Can we have some old rpms in the x2go.repo?

[Norman Gaywood]

On Thu, 15 Mar 2018 at 13:45, Mihai Moldovan  wrote:

>
> > The move across the screen segfault has happened to 3 users (including
> me) and
> > all have been linux clients (Fedora I think).
> > The move across screen segfault seems to go away sometimes for
> undermined reasons.
>
> I personally wasn't able to reproduce that either, but it seems to be
> depending
> on quite some factors.
>

If I connect, suspend the session, resume the session. I can then move my
session across screens.
Worked for me a few times so far.


> Can you tell me the display configuration (size and positioning) you are
> seeing
> this with and what window managers/desktop environments and operating
> systems
> are used on the client and server side?
>

Not sure I can in a useful manner, but:
I keep changing my connection screen size to many different sizes.
I'm not sure how to report my physical workstation screen sizes but:
Dell 27" 2560x1440, Dell 29" 2560x1018
The workstation x2goclient is x2goclient-4.1.1.0-1.fc27.x86_64

All desktop environments on the server(s) are
XFCE, xfce4-session-4.12.1-12.fc27.x86_64
The server(s) are running:
libNX_X11-6-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
libXcompext3-3.5.0.33-0.0x2go1.1.git20180204.776.main.fc27.x86_64
nxagent-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
nx-libs-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
nxproxy-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
perl-X2Go-Log-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
perl-X2Go-Server-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
perl-X2Go-Server-DB-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
x2goserver-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
x2goserver-common-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
x2goserver-extensions-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
x2goserver-x2goagent-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
x2goserver-xsession-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64

The prod server would have mostly Windows x2go clients connecting, but some
Mac and some Linux, all different versions.
The dev server would only have x2goclient-4.1.1.0-1.fc27.x86_64 connecting.

The servers (dev and prod) are Fedora  27 running:
libNX_X11-6-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
libXcompext3-3.5.0.33-0.0x2go1.1.git20180204.776.main.fc27.x86_64
nxagent-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
nx-libs-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
nxproxy-3.5.99.15-0.0build1.1.git20180308.2971.main.fc27.x86_64
perl-X2Go-Log-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
perl-X2Go-Server-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
perl-X2Go-Server-DB-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
x2goserver-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
x2goserver-common-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
x2goserver-extensions-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
x2goserver-x2goagent-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64
x2goserver-xsession-4.1.0.0-0.0x2go1.1.git20180302.1517.main.fc27.x86_64


-- 
Norman Gaywood, Computer Systems Officer
School of Science and Technology
University of New England
Armidale NSW 2351, Australia

ngayw...@une.edu.au  http://turing.une.edu.au/~ngaywood
Phone: +61 (0)2 6773 2412  Mobile: +61 (0)4 7862 0062

Please avoid sending me Word or Power Point attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Can we have some old rpms in the x2go.repo?

[Mihai Moldovan]

* On 03/15/2018 03:11 AM, Norman Gaywood wrote:
> So I've updated dev to the latest
> again 3.5.99.15-0.0build1.1.git20180308.2971.main.fc27
> 
> And I seem to get an nxagent segfault every time I move the session window 
> into
> another screen.
> 
> Same version in production and it was stable for a few days now. I could move 
> it
> across screens. I suspended and resumed several times.
> But, after logging out of production and logging back in again, I'm back to
> segfaulting when moving across screens.
> 
> It's a very strange problem :-(
> 
> Executive summary:
> 
> The segfault on connect I have not reproduced. But its been reported by 
> several
> of my users. I have around 50 logged in users at the moment. The login 
> segfault
> only happens to very few (5/6). Some of them seemed to be working now.

I've been unable to reproduce this on a 16.04 VM with two virtual heads, but
neither was the original reporter that tried connecting from a 16.04 with one
head to a 16.04 machine, that previously segfaulted on connect when using a
14.04 client box with dual head setup (with 21:9 displays or such).


> The move across the screen segfault has happened to 3 users (including me) and
> all have been linux clients (Fedora I think).
> The move across screen segfault seems to go away sometimes for undermined 
> reasons.

I personally wasn't able to reproduce that either, but it seems to be depending
on quite some factors.

Can you tell me the display configuration (size and positioning) you are seeing
this with and what window managers/desktop environments and operating systems
are used on the client and server side?



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Can we have some old rpms in the x2go.repo?

[Norman Gaywood]

So I've updated dev to the latest
again 3.5.99.15-0.0build1.1.git20180308.2971.main.fc27

And I seem to get an nxagent segfault every time I move the session window
into another screen.

Same version in production and it was stable for a few days now. I could
move it across screens. I suspended and resumed several times.
But, after logging out of production and logging back in again, I'm back to
segfaulting when moving across screens.

It's a very strange problem :-(

Executive summary:

The segfault on connect I have not reproduced. But its been reported by
several of my users. I have around 50 logged in users at the moment. The
login segfault only happens to very few (5/6). Some of them seemed to be
working now.

The move across the screen segfault has happened to 3 users (including me)
and all have been linux clients (Fedora I think).
The move across screen segfault seems to go away sometimes for undermined
reasons.



On Thu, 15 Mar 2018 at 12:36, Norman Gaywood  wrote:

> On Tue, 13 Mar 2018 at 20:29, Mihai Moldovan  wrote:
>
>> * On 03/13/2018 10:25 AM, Norman Gaywood wrote:
>>
>> https://snapshots.packages.x2go.org/20180302/fedora/27/main/x86_64/rpms/nx-libs/
>>
>>
>> > Fixing the bug could take weeks, so it would be good to roll back 1
>> version that
>> > seemed to be more stable while we wait.
>>
>> The other version has a different severe bug, related to Screen Savers
>> and DPMS.
>> Make sure to disable them, if you really want to downgrade.
>>
>
> Thanks for those snapshot links. I manage to use them an roll back 1
> version on the dev system to avoid:
>
> https://github.com/ArcticaProject/nx-libs/issues/679  (Coredump when
> connecting)
> https://github.com/ArcticaProject/nx-libs/issues/677  (nxagent crashes
> when moving the session window into another screen)
>
> I was about to roll back production, but users that were getting seg
> faults (on connecting or moving across screens) seemed to start working!
>
> So I've left production alone for now.
>
> Of the 5/6 users that hit these problems most of them seem to be
> connecting again.
>
> Seg faults are still occurring in nxagent and some users still have not
> connected successfully, but most seem fine and get on after a few retries.
>
> ???
>
> 3.5.99.14-0.0build1.1.git20180302.2954.main.fc27   (dev)
> 3.5.99.15-0.0build1.1.git20180308.2971.main.fc27   (prod)
>
> --
> Norman Gaywood, Computer Systems Officer
> School of Science and Technology
> University of New England
> Armidale NSW 2351, Australia
>
> ngayw...@une.edu.au  http://turing.une.edu.au/~ngaywood
> Phone: +61 (0)2 6773 2412  Mobile: +61 (0)4 7862 0062
>
> Please avoid sending me Word or Power Point attachments.
> See http://www.gnu.org/philosophy/no-word-attachments.html
>


-- 
Norman Gaywood, Computer Systems Officer
School of Science and Technology
University of New England
Armidale NSW 2351, Australia

ngayw...@une.edu.au  http://turing.une.edu.au/~ngaywood
Phone: +61 (0)2 6773 2412  Mobile: +61 (0)4 7862 0062

Please avoid sending me Word or Power Point attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Update: Problems after upgrading to recent x2go-server and x2go client releases

[Mihai Moldovan]

* On 03/13/2018 02:41 PM, h i wrote:
> When using the ppa:x2go/stable repository, something seemed strange when I ran
> the update manager in Ubuntu 14.04 and Ubuntu 16.04. I received a message 
> about
> a partial upgrade I've never seen since using Ubuntu. I've attached the 
> message.
> After running this partial upgrade, I started experiencing the flickering
> problems. Removed x2goserver entirely, and did a fresh install of the most
> update to date version. Still experiencing the flickering problems.

Hm, I don't know what a partial update means. If you upgraded successfully there
should be no partial upgrades.

Switching from stable to saimaa directly is not possible, though.

You will need to uninstall all X2Go packages first, then add the Saimaa
repository and reinstall.


> I no longer experience the flickering when maximizing/minimizing or moving the
> window from side-to side. Everything is working fine like it was prior to the
> most recent update from the ppa:x2go/stable repository. I think I'm going to
> stick with the Saimaa repository for now until the bugs are fixed from
> the ppa:x2go/stable  repository.  

Fine, but please follow the release announcements to know when that happens.


> Also going to stick with x2goclient 4.1.0.0 where there is no issue with
> clicking the session panel. I can click where I'm accustomed to clicking 
> again.

Note that X2Go Client prior to 4.1.1.1 won't work correctly with the new stable
release of X2Go Server due to Xinerama changes.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Can we have some old rpms in the x2go.repo?

[Norman Gaywood]

On Tue, 13 Mar 2018 at 20:29, Mihai Moldovan  wrote:

> * On 03/13/2018 10:25 AM, Norman Gaywood wrote:
>
> https://snapshots.packages.x2go.org/20180302/fedora/27/main/x86_64/rpms/nx-libs/
>
>
> > Fixing the bug could take weeks, so it would be good to roll back 1
> version that
> > seemed to be more stable while we wait.
>
> The other version has a different severe bug, related to Screen Savers and
> DPMS.
> Make sure to disable them, if you really want to downgrade.
>

Thanks for those snapshot links. I manage to use them an roll back 1
version on the dev system to avoid:

https://github.com/ArcticaProject/nx-libs/issues/679  (Coredump when
connecting)
https://github.com/ArcticaProject/nx-libs/issues/677  (nxagent crashes when
moving the session window into another screen)

I was about to roll back production, but users that were getting seg faults
(on connecting or moving across screens) seemed to start working!

So I've left production alone for now.

Of the 5/6 users that hit these problems most of them seem to be connecting
again.

Seg faults are still occurring in nxagent and some users still have not
connected successfully, but most seem fine and get on after a few retries.

???

3.5.99.14-0.0build1.1.git20180302.2954.main.fc27   (dev)
3.5.99.15-0.0build1.1.git20180308.2971.main.fc27   (prod)

-- 
Norman Gaywood, Computer Systems Officer
School of Science and Technology
University of New England
Armidale NSW 2351, Australia

ngayw...@une.edu.au  http://turing.une.edu.au/~ngaywood
Phone: +61 (0)2 6773 2412  Mobile: +61 (0)4 7862 0062

Please avoid sending me Word or Power Point attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Problems after upgrading to recent x2go-server and x2go client releases

[Mihai Moldovan]

* On 03/09/2018 10:23 PM, h i wrote:
> I think I might have to roll-back to the previous x2goserver version. At 
> least with our setup, we never had a flicker issue until this most recent  
> update.

I know, it's a new issue that only manifests with the new nx-libs 3.5.99.x 
release.

We currently do not know why it happens exactly, but it seems to only occur on
Windows 10 as the client platform (not Windows 7 for instance).

It looks like the window is constantly resizing to the same size - but we'll
have to figure out what generates so many resizing requests and why.


> Interesting. Yeah, I never had an issue with the sensitive area. 
> Understandable that others might have an issue.

You likely never tried changing settings within a tile using the drop-down
mechanism provided there. Others did... and were frustrated with the constant
starting of sessions even though they just wanted to change settings prior to
actually firing them off.


> What is Saimaa release, and why are there two separate releases for x2go now? 
>  
> 
> 
> Is the saimaa release from here:
> 
> https://launchpad.net/~x2go/+archive/ubuntu/saimaa

Yes, that's an Ubuntu repository for Saimaa.

Saimaa is an ESR release based on the earlier version of X2Go Server 4.0.1.x and
legacy nx-libs 3.5.0.x versions. It won't get normal bug fixes, only at most
security updates and doesn't contain all X2Go packages.

It's supposed to provide a fallback to the old state that was working for users
so that they can switch to something they know is working if they experience
problems with the new release.

More information also here: https://wiki.x2go.org/doku.php/download:saimaa

It's not meant to be used indefinitely, though. As problems in the new release
are fixed, users should migrate back to the stable version again.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Can't install X2goserver on Debian 9

[Mihai Moldovan]

* On 03/15/2018 01:16 AM, Nigra Truo wrote:
> [SOLVED]
> 
> I figured out what the culprit is. This is an older system and the intent to
> purge was based on the assumption that some old config or other depricated
> element might be still hanging around. So doing this here:
> 
> apt purge x2goserver x2goserver-common x2goserver-dbgsym x2goserver-extensions
> x2goserver-fmbindings x2goserver-printing x2goserver-pyhoca 
> x2goserver-x2goagent
> x2goserver-xsession libx2go-log-perl libx2go-server-db-perl 
> libx2go-server-perl
> 
> Fixes it. It removes all traces of x2go from the server, only when you
> especially mention each and every one package and purge it does it work, for
> example the users are contained in the x2goserver-common package, if you just 
> do
> a purge of x2goserver alone, that leaves most things still on the system.
> This gives you the possibility to wipe the slate clean and install it like it
> was a brand new linux install.

Oh, indeed, you should have purged both x2goserver and x2goserver-common...
maybe also the old db packages.

It looks like in your original message, apt-get only tried to purge these 
packages:

The following packages will be REMOVED:
  x2goserver* x2goserver-extensions* x2goserver-fmbindings* x2goserver-printing*
x2goserver-xsession*

So definitely not everything, for instance x2goserver-common is missing there.



Mihai



signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Can't install X2goserver on Debian 9

[Nigra Truo]

[SOLVED]

I figured out what the culprit is. This is an older system and the intent
to purge was based on the assumption that some old config or other
depricated element might be still hanging around. So doing this here:

apt purge x2goserver x2goserver-common x2goserver-dbgsym
x2goserver-extensions x2goserver-fmbindings x2goserver-printing
x2goserver-pyhoca x2goserver-x2goagent x2goserver-xsession libx2go-log-perl
libx2go-server-db-perl libx2go-server-perl

Fixes it. It removes all traces of x2go from the server, only when you
especially mention each and every one package and purge it does it work,
for example the users are contained in the x2goserver-common package, if
you just do a purge of x2goserver alone, that leaves most things still on
the system.
This gives you the possibility to wipe the slate clean and install it like
it was a brand new linux install.

Thanks for your assistance in solving this, I use X2go every day on my
server and was pretty lost without it.

Markus


On Wed, Mar 14, 2018 at 4:47 PM, Nigra Truo  wrote:

> Or asked otherwise:
> Where is */etc/x2go/x2gosql/sql* and *X2Go::Config module* coming from?
> Which x2go package provides it and why isn't it getting installed? I tried
> dpkg -i --force-confmiss on all packages to no avail. I mean on a brand new
> installed system, you would not have /etc/x2go/x2gosql/sql and the
> packages would have to provide it in any case to make the server function.
>
>
>
> On Wed, Mar 14, 2018 at 7:03 AM, Mihai Moldovan  wrote:
>
>> * On 03/14/2018 02:48 PM, Mihai Moldovan wrote:
>> > Please create /etc/x2go/x2gosql/sql manually with a line containing
>> > 'backend=sqlite'. That should allow you to purge the packages.
>> >
>> > Afterwards you should be able to reinstall them normally.
>>
>> Oh, and if this still doesn't help for purging, you'll have to modify the
>> scriptlets apt saved in /var/lib/dpkg/info/, like Jason already pointed
>> out.
>>
>> Edit x2goserver.postrm, libx2go-server-db-perl.postrm and
>> x2goserver-common.postrm (if they exist) and put a [ -d '/etc/x2go' ] &&
>> before
>> the rmdir calls, like in
>> https://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h
>> =561ee44138fa6bc02d1293539dac501a9dda1886
>>
>> Purging should seriously work after that.
>>
>>
>>
>> Mihai
>>
>>
>>
>
>
> --
> *Por sperto kaj lerno ne sufiĉas eterno.*
>



-- 
*Por sperto kaj lerno ne sufiĉas eterno.*
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Can't install X2goserver on Debian 9

[Nigra Truo]

Or asked otherwise:
Where is */etc/x2go/x2gosql/sql* and *X2Go::Config module* coming from?
Which x2go package provides it and why isn't it getting installed? I tried
dpkg -i --force-confmiss on all packages to no avail. I mean on a brand new
installed system, you would not have /etc/x2go/x2gosql/sql and the packages
would have to provide it in any case to make the server function.



On Wed, Mar 14, 2018 at 7:03 AM, Mihai Moldovan  wrote:

> * On 03/14/2018 02:48 PM, Mihai Moldovan wrote:
> > Please create /etc/x2go/x2gosql/sql manually with a line containing
> > 'backend=sqlite'. That should allow you to purge the packages.
> >
> > Afterwards you should be able to reinstall them normally.
>
> Oh, and if this still doesn't help for purging, you'll have to modify the
> scriptlets apt saved in /var/lib/dpkg/info/, like Jason already pointed
> out.
>
> Edit x2goserver.postrm, libx2go-server-db-perl.postrm and
> x2goserver-common.postrm (if they exist) and put a [ -d '/etc/x2go' ] &&
> before
> the rmdir calls, like in
> https://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=
> 561ee44138fa6bc02d1293539dac501a9dda1886
>
> Purging should seriously work after that.
>
>
>
> Mihai
>
>
>


-- 
*Por sperto kaj lerno ne sufiĉas eterno.*
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Can't install X2goserver on Debian 9

[Nigra Truo]

Now I get this error:
Setting up x2goserver (4.1.0.0-0x2go1.2+git20180302.1517+9.main.1) ...
Can't locate X2Go/Config.pm in @INC (you may need to install the
X2Go::Config module) (@INC contains: /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at
/usr/sbin/x2godbadmin line 30.

At this point the salient question is: Why is this not working? There is
nothing x2go on this server, I erased everything that the purge failed to
do. At this point, the system should be as fresh as a completely new box.
But for some reason, dpkg seems to remember that I erased something or that
something is missing. Where is that stored, how can I make dpkg / apt treat
this as though it does not know anything about the x2goserver package, like
it was never installed before? This is not the first time this happened,
dpkg seems to remember when things get erased and does not get that likely,
an admin erased something for a purpose and that it should be replaced
fresh when reinstalling it, instead of complaining that a config is not
there (while in a fresh install, there is nothing installed and all the
files need to be unpacked and installed from scratch)

Thanks,

Markus

On Wed, Mar 14, 2018 at 6:48 AM, Mihai Moldovan  wrote:

> * On 03/14/2018 03:19 AM, Nigra Truo wrote:
> > Thanks for the pointers. Yes, of course all apt commands are always
> executed
> > as root. Right now it is not so much about the bug that prevents
> purging, it
> > is more that I just can't reinstall x2goserver anymore. I see this
> message
> >
> > "X2Go is configured to use a non-SQLite DB backend, leaving the database
> > alone" and the server install fails.
> >
> > and can't find any documentation and reference to it, it is a show
> stopper
> > at this moment. Question: Where is x2go told to do that? Which config is
> > still left on the system? I cleaned up EVERYTHING x2go related, erased
> all
> > dirs and configs, I have never seen this message before. It is like apt /
> > dpkg remembers some setting that it is not supposed to remember (as the
> > package was purged)
>
> It's determined in a {pre,post}{inst,rm} scripts... which are buggy in
> that regard.
>
> We should ignore non-existing files instead of assuming a different SQL
> backend
> being used.
>
> Please create /etc/x2go/x2gosql/sql manually with a line containing
> 'backend=sqlite'. That should allow you to purge the packages.
>
> Afterwards you should be able to reinstall them normally.
>
>
> Mihai
>
>
>


-- 
*Por sperto kaj lerno ne sufiĉas eterno.*
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Some questions about X2go

[Torsten Kupke]

Hi Walid,

yes, currently I use a "MATE" session, because I can configure it more 
flexible. But the "Local desktop" session sometimes could be useful, 
when I worked on the console of the Ubuntu host and forgot to save my 
work before going home. Then I could use the "Local desktop" session to 
save the unsaved work. And sometimes there are things, which couldn't be 
saved in their actual state and must be worked on before saving. So the 
"Local desktop" session could be very useful to complete and save this work.


With RDP I could connect to an actual running Windows session (on the 
same working PC with two screens). All the Windows opened at work 
remained opened, and I could continue my work, as if I sat before the 
console. The RDP Window can be configured as large as the two screens 
are. On my single screen at home it displays scroll bars, so I can 
scroll to each edge. So if the full screen of X2go had scroll bars, 
instead of compressing its content, the "Local desktop" session could be 
much more useful.


Sincerely
tkansgar


Am 14.03.2018 um 19:22 schrieb Walid MOGHRABI:

Hi,

Do you really need desktop sharing (aka "see what you see on your opened local 
session on your remote computer") or do you just need to open a session on the 
remote machine the Windows RDP way (contrary to the TeamViewer/VNC way) ?
If so, you'll get far better performances and comfort opening a "MATE" session instead of 
a "Local desktop" session from your X2Go client.

Regards,
Walid Moghrabi

TRAVAUX.COM
BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403
13591 AIX EN PROVENCE CEDEX 3

- Mail original -

De: "Torsten Kupke" 
À: x2go-user@lists.x2go.org
Envoyé: Mercredi 14 Mars 2018 18:24:37
Objet: [X2Go-User] Some questions about X2go


Hi all,
on my working PC there is running Ubuntu 16.04 with MATE Desktop (isn't the 
same as Ubuntu MATE, right?) and a X2go Server with Desktop Sharing extension. 
On my home PC with Windows 10 I have installed the X2go Client and inside it 
configured a session connecting to the Ubuntu host according to 
https://wiki.x2go.org/doku.php/doc:usage:desktop-sharing . The connection is 
successful, but there are some issues:


 1. The Ubuntu host's desktop is spread over two 4/3 screens. But The 
Windows PC only has one screen with 1680x1050 Pixels. So the display from the 
Ubuntu host is highly horizontally compressed, so that the texts are nearly 
unreadable. OK, this behaviour is documented, but is there a way to get it more 
readable?
 2. If I (to solve the above issue) switch to something other than full 
screen mode in the session settings, the session crashes, when started. I have 
to close and restart the X2go Client. And then with settings set back to full 
screen mode the session runs again. Is there a way to avoid the crash without 
full screen mode?
 3. In full screen mode I cannot see any mouse cursor. So hitting any user 
elements inside or on the windows inside the display from the Ubuntu host is 
very difficult, since they are reduced to half the width. Is there a way to see 
a mouse cursor? Or is this due to the compressed display?
 4. Since mouse using is so difficult, I tried to close the windows from the Ubuntu host by 
pressing . But then I get a question from X2go to close the session. Is there a 
way to propagate key combinitions like  to the remote host?

Sincerely
tkansgar

___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user
---
DISCLAIMER: This e-mail is private and confidential and may contain proprietary 
or legally privileged information. It is for the intended recipient only. If 
you have received this email in error, please notify the author by replying to 
it and then destroy it. If you are not the intended recipient you must not use, 
disclose, distribute, copy, print or rely on this e-mail or any attachment. 
Thank you


___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Some questions about X2go

[Walid MOGHRABI]

Hi,

Do you really need desktop sharing (aka "see what you see on your opened local 
session on your remote computer") or do you just need to open a session on the 
remote machine the Windows RDP way (contrary to the TeamViewer/VNC way) ?
If so, you'll get far better performances and comfort opening a "MATE" session 
instead of a "Local desktop" session from your X2Go client.

Regards,
Walid Moghrabi

TRAVAUX.COM
BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403
13591 AIX EN PROVENCE CEDEX 3

- Mail original - 

De: "Torsten Kupke"  
À: x2go-user@lists.x2go.org 
Envoyé: Mercredi 14 Mars 2018 18:24:37 
Objet: [X2Go-User] Some questions about X2go 


Hi all, 
on my working PC there is running Ubuntu 16.04 with MATE Desktop (isn't the 
same as Ubuntu MATE, right?) and a X2go Server with Desktop Sharing extension. 
On my home PC with Windows 10 I have installed the X2go Client and inside it 
configured a session connecting to the Ubuntu host according to 
https://wiki.x2go.org/doku.php/doc:usage:desktop-sharing . The connection is 
successful, but there are some issues: 


1. The Ubuntu host's desktop is spread over two 4/3 screens. But The 
Windows PC only has one screen with 1680x1050 Pixels. So the display from the 
Ubuntu host is highly horizontally compressed, so that the texts are nearly 
unreadable. OK, this behaviour is documented, but is there a way to get it more 
readable? 
2. If I (to solve the above issue) switch to something other than full 
screen mode in the session settings, the session crashes, when started. I have 
to close and restart the X2go Client. And then with settings set back to full 
screen mode the session runs again. Is there a way to avoid the crash without 
full screen mode? 
3. In full screen mode I cannot see any mouse cursor. So hitting any user 
elements inside or on the windows inside the display from the Ubuntu host is 
very difficult, since they are reduced to half the width. Is there a way to see 
a mouse cursor? Or is this due to the compressed display? 
4. Since mouse using is so difficult, I tried to close the windows from the 
Ubuntu host by pressing . But then I get a question from X2go to close 
the session. Is there a way to propagate key combinitions like  to the 
remote host? 

Sincerely 
tkansgar 

___ 
x2go-user mailing list 
x2go-user@lists.x2go.org 
https://lists.x2go.org/listinfo/x2go-user
---
DISCLAIMER: This e-mail is private and confidential and may contain proprietary 
or legally privileged information. It is for the intended recipient only. If 
you have received this email in error, please notify the author by replying to 
it and then destroy it. If you are not the intended recipient you must not use, 
disclose, distribute, copy, print or rely on this e-mail or any attachment. 
Thank you
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Update: Problems after upgrading to recent x2go-server and x2go client releases

[h i]

Hello,

When using the ppa:x2go/stable repository, something seemed strange when I ran 
the update manager in Ubuntu 14.04 and Ubuntu 16.04. I received a message about 
a partial upgrade I've never seen since using Ubuntu. I've attached the 
message. After running this partial upgrade, I started experiencing the 
flickering problems. Removed x2goserver entirely, and did a fresh install of 
the most update to date version. Still experiencing the flickering problems.

I  uninstalled everything from x2goserver on our system. Also uninstalled any 
lingering package versions that might conflict with trying to install from the 
Saimaa repository.

After cleaning, I installed x2goserver from the Saimaa repository.

I no longer experience the flickering when maximizing/minimizing or moving the 
window from side-to side. Everything is working fine like it was prior to the 
most recent update from the ppa:x2go/stable repository. I think I'm going to 
stick with the Saimaa repository for now until the bugs are fixed from the 
ppa:x2go/stable  repository.

Also going to stick with x2goclient 4.1.0.0 where there is no issue with 
clicking the session panel. I can click where I'm accustomed to clicking again.

Why are there 2 repositories for x2go and which one should we use for the 
long-term?

Any help would be appreciated.

h.


From: x2go-user  on behalf of h i 

Sent: Friday, March 9, 2018 4:23 PM
To: x2go-user@lists.x2go.org
Subject: Re: [X2Go-User] Problems after upgrading to recent x2go-server and 
x2go client releases


Mihai,


Thanks for your response. Please see my responses below:


* On 03/07/2018 07:34 PM, h i wrote:
> >I've been experiencing problems with opening applications and resizing my 
> >x2go
> >client window after installing the newest version x2go-server.
>
>
> >The issues occurs on Ubuntu 14.04 and 16.04.
>
>
> >What happens now is that every time I maximize my x2go-client window, the 
> >images
> >on screen rapidly flicker and won't stop until I minimize the screen.

>>The flickering is a known problem, but as far as we can tell only appears on
>>Windows (and even then not with all X servers, but prominently with VcXsrv, 
>>that
>>we bundle). It's tracked here: 
>>https://github.com/ArcticaProject/nx-libs/issues/600

> Also, each time I move the window, a quick flicker occurs across the screen.

>Probably related to the move being something alike to a resize and thus also
>triggering the new xinerama code.


> >This never occurred before this new release.

>There is no known workaround currently, though it might be possible to just
>ignore multiple resize events in nxagent if the requested size doesn't change.
>We'll have to see how that goes.





I think I might have to roll-back to the previous x2goserver version. At least 
with our setup, we never had a flicker issue until this most recent  update.




> >On the client side, I upgraded to the 4.1.1.1 from 4.1.0.0 and experienced 
> >some
> >issues. I have to click on the outside/top-right edge of the session panel 
> >for
> >the login session window to appear. Any thing closer to the middle, and it 
> >won't
> >respond.

>This is not an issue, but an often requested new feature. I've changed the
>click-sensitive area to an upside-down L shape around the session settings that
>can be modified within the tile. Actually like this, where "s" denotes a
>click-sensitive area:

 ___
|sss|
|sss|
|sss|
|sss|
|sss|
|sss|
 ---

>The problem so far has been that users can normally edit some exposed settings
>within a tile, but doing so proved to be very difficult since an incorrect 
>click
>triggered a session startup instead of changing a setting, which was happening
>quite often.

>The sensitive area isn't small and figuring that out shouldn't take long
>usually, so I guess you've just been unlucky to always click on the right hand
>side which is typically insensitive but in the upper part.





Interesting. Yeah, I never had an issue with the sensitive area. Understandable 
that others might have an issue.





> >Once logged into a session, the flickering resulting
> >from moving/maximizing the window is much worse.
> >
>> Fortunately, I was able to revert back to x2go-client 4.1.0.0.

>Huh, the flickering should be always the same, whether a session has been
>started with 4.1.1.1 or 4.1.0.0. Though, potentially there could be a
>difference: versions prior to 4.1.1.1 won't be able to utilize the Xinerama
>feature in X2Go Server 4.1.0.0, so when connecting with older client versions
>Xinerama will always be disabled in nxagent.


>> However,is there a way to revert back to this previous version/configuration
>> of x2goserver. Right now, it is has been a lot of flickering 

Re: [X2Go-User] Can't install X2goserver on Debian 9

[Mihai Moldovan]

* On 03/14/2018 02:48 PM, Mihai Moldovan wrote:
> Please create /etc/x2go/x2gosql/sql manually with a line containing
> 'backend=sqlite'. That should allow you to purge the packages.
> 
> Afterwards you should be able to reinstall them normally.

Oh, and if this still doesn't help for purging, you'll have to modify the
scriptlets apt saved in /var/lib/dpkg/info/, like Jason already pointed out.

Edit x2goserver.postrm, libx2go-server-db-perl.postrm and
x2goserver-common.postrm (if they exist) and put a [ -d '/etc/x2go' ] && before
the rmdir calls, like in
https://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=561ee44138fa6bc02d1293539dac501a9dda1886

Purging should seriously work after that.



Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] Can't install X2goserver on Debian 9

[Mihai Moldovan]

* On 03/14/2018 03:19 AM, Nigra Truo wrote:
> Thanks for the pointers. Yes, of course all apt commands are always executed
> as root. Right now it is not so much about the bug that prevents purging, it
> is more that I just can't reinstall x2goserver anymore. I see this message
> 
> "X2Go is configured to use a non-SQLite DB backend, leaving the database
> alone" and the server install fails.
> 
> and can't find any documentation and reference to it, it is a show stopper
> at this moment. Question: Where is x2go told to do that? Which config is
> still left on the system? I cleaned up EVERYTHING x2go related, erased all
> dirs and configs, I have never seen this message before. It is like apt /
> dpkg remembers some setting that it is not supposed to remember (as the
> package was purged)

It's determined in a {pre,post}{inst,rm} scripts... which are buggy in that 
regard.

We should ignore non-existing files instead of assuming a different SQL backend
being used.

Please create /etc/x2go/x2gosql/sql manually with a line containing
'backend=sqlite'. That should allow you to purge the packages.

Afterwards you should be able to reinstall them normally.


Mihai




signature.asc
Description: OpenPGP digital signature
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user