Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-18 Thread Mihai Moldovan
* On 11/17/2017 12:12 AM, Ulrich Sibiller wrote: > Thanks for clarification. But why not simply using all combinations in > parallel? Could do, but that doesn't really make sense if the plain hostname is working fine. I actually wonder if there's a subtle bug in general - what happens with

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-16 Thread Ulrich Sibiller
On Thu, Nov 16, 2017 at 5:15 PM, Mihai Moldovan wrote: > * On 11/16/2017 07:41 AM, Ulrich Sibiller wrote: >> Fine! Now that we debugged this with ~60 mails we finally have a working >> system. >> But to me it is still unclear what was causing the NIS problems!? > The gist is

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-16 Thread Mihai Moldovan
* On 11/16/2017 07:41 AM, Ulrich Sibiller wrote: > Fine! Now that we debugged this with ~60 mails we finally have a working > system. > But to me it is still unclear what was causing the NIS problems!? There wasn't a NIS issue to begin with. What we learned is that X authorization is a fragile

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-15 Thread Ulrich Sibiller
Am 15.11.2017 22:37 schrieb "Robert Kudyba" : *x2go* is not installed Yep, it did. No big deal, just yum install x2goserver x2goserver-xsession. Ahh success! Even with the NIS user. So should I remove the _copr_mikedep333-nx-libs-3.6.repo? Fine! Now that we debugged

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-15 Thread Mihai Moldovan
* On 11/15/2017 10:36 PM, Robert Kudyba wrote: > Ahh success! Even with the NIS user. So should I remove > the _copr_mikedep333-nx-libs-3.6.repo? Uhm... that depends. If you want to keep staying on the Arctica testing version of nx-libs, then no. If you want switch back the older nx-libs version

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-15 Thread Robert Kudyba
> On Nov 15, 2017, at 4:32 PM, Mihai Moldovan wrote: > > * On 11/15/2017 10:30 PM, Robert Kudyba wrote: >>> Hopefully it didn't remove any other needed package. Probably not, though. >>> >>> rpm -q '*x2go*’ >> >> Seems it did: >> rpm -q '*x2go*' >> package *x2go* is not

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-15 Thread Mihai Moldovan
* On 11/15/2017 10:30 PM, Robert Kudyba wrote: >> Hopefully it didn't remove any other needed package. Probably not, though. >> >> rpm -q '*x2go*’ > > Seems it did: > rpm -q '*x2go*' > package *x2go* is not installed Yep, it did. No big deal, just yum install x2goserver x2goserver-xsession.

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-15 Thread Robert Kudyba
> On Nov 15, 2017, at 4:27 PM, Mihai Moldovan wrote: > > * On 11/15/2017 10:23 PM, Robert Kudyba wrote: >> OK I had to remove and then installed successfully. Now how do I start? >> [root@sobolev yum.repos.d]# systemctl start x2goagent >> Failed to start x2goagent.service: Unit

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-15 Thread Mihai Moldovan
* On 11/15/2017 10:23 PM, Robert Kudyba wrote: > OK I had to remove and then installed successfully. Now how do I start? > [root@sobolev yum.repos.d]# systemctl start x2goagent > Failed to start x2goagent.service: Unit x2goagent.service not found. > [root@sobolev yum.repos.d]# systemctl start

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-15 Thread Robert Kudyba
> On Nov 15, 2017, at 4:16 PM, Mihai Moldovan wrote: > > * On 11/15/2017 10:14 PM, Robert Kudyba wrote: >> rpm -qa '*x2goagent*' >> x2goagent-3.5.0.34-0.0x2go1.0.git2017.778.heuler.fc26.x86_64 > > Ah, now that explains a great deal! You shouldn't be using that package with

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-15 Thread Mihai Moldovan
* On 11/15/2017 10:14 PM, Robert Kudyba wrote: > rpm -qa '*x2goagent*' > x2goagent-3.5.0.34-0.0x2go1.0.git2017.778.heuler.fc26.x86_64 Ah, now that explains a great deal! You shouldn't be using that package with Arctica's nx-libs version. What does yum install x2goserver-x2goagent do? If it

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-15 Thread Robert Kudyba
> On Nov 15, 2017, at 4:11 PM, Mihai Moldovan wrote: > > * On 11/15/2017 10:05 PM, Robert Kudyba wrote: >> I’m taking another shot with providing logs as there appears to be more than >> last time. Here are debug logs from the client and then server. I take it the >> core dumps

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-15 Thread Mihai Moldovan
* On 11/15/2017 10:05 PM, Robert Kudyba wrote: > I’m taking another shot with providing logs as there appears to be more than > last time. Here are debug logs from the client and then server. I take it the > core dumps from MATE, GLXINFO or XFCE won’t help? > > Seems to crash in a similar place,

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-14 Thread Robert Kudyba
On Tue, Nov 14, 2017 at 7:47 PM, Mihai Moldovan wrote: > On 11/14/2017 02:26 AM, Robert Kudyba wrote: > > Anything else I can provide? > > Can't think of anything useful currently. Something has to trigger the > crashes, > but I don't know what exactly. > > I cannot reproduce it

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-14 Thread Mihai Moldovan
On 11/14/2017 02:26 AM, Robert Kudyba wrote: > Anything else I can provide?  Can't think of anything useful currently. Something has to trigger the crashes, but I don't know what exactly. I cannot reproduce it myself, so my best guess is that some additional package (or configuration) is

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-13 Thread Robert Kudyba
> Not really, I fear. I'm unable to reproduce this. Have tested both with the >> current X2Go nx-libs release builds and Mike#2's copr repo for the arctica >> version. In both cases MATE starts up without segfaulting in xcb. >> >> However, for some reason I even have direct rendering available in

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-10 Thread Robert Kudyba
> Not really, I fear. I'm unable to reproduce this. Have tested both with the > current X2Go nx-libs release builds and Mike#2's copr repo for the arctica > version. In both cases MATE starts up without segfaulting in xcb. > > However, for some reason I even have direct rendering available in the

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-10 Thread Mihai Moldovan
On 11/10/2017 08:48 PM, Robert Kudyba wrote: > Does this help, from gdb /usr/bin/mate-session > /var/lib/systemd/coredump/core.mate-session.1000.d7ae5cd424f743dcbbdad920fbc58b7b.2731.151034029300 >   >       > [...] > Reading symbols from /usr/bin/mate-session...Reading symbols from >

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-10 Thread Robert Kudyba
> > > > Not to the best of my knowledge just have this: > > > > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. > [AMD/ATI] Cedar > > [Radeon HD 5000/6000/7350/8350 Series] > > rpm -qa | grep -i fglrx > > Similar results using XFCE: gdb /usr/bin/xfce4-panel

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-10 Thread Robert Kudyba
> > > Not to the best of my knowledge just have this: > > > > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. > [AMD/ATI] Cedar > > [Radeon HD 5000/6000/7350/8350 Series] > > rpm -qa | grep -i fglrx Does this help, from gdb /usr/bin/mate-session

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-10 Thread Robert Kudyba
> > If you set the old hostname again via "hostnamectl set-hostname > sobolev.dsm.fordham.edu", can you still "start" X2Go connections? (Even > if they > crash right away, that's separate issue.) > > I think I'll have to just use the real system's name (returned via > hostname) > instead of the

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-10 Thread Robert Kudyba
> Uhm, yes, because your syntax is invalid. > > The hosts file syntax is [ ...] > > You should have added sobolev to the 127.0.0.1 line - the last one is just > plain > bogus. > Got it I just added it the 1st line and it's now: 127.0.0.1 localhost localhost.localdomain localhost4

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-10 Thread Mihai Moldovan
On 11/10/2017 08:01 PM, Robert Kudyba wrote: > Just making this one change to the /etc/hosts file didn't change anything. > [...] > Just to confirm the /etc/hosts file now looks like this: > 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 > ::1 localhost

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-10 Thread Robert Kudyba
> > > hostnamectl set-hostname fedora.local.home.ionic.de > > > > Then, I edited /etc/hosts and added: > > > > 192.168.122.128 fedora fedora.local.home.ionic.de > > > > This leads to exactly the problem you described. > > > > > > If I change "fedora" to resolve to 127.0.0.1 instead (with > >

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-10 Thread Mihai Moldovan
On 11/10/2017 06:36 PM, Mihai Moldovan wrote: > HA! I was finally able to reproduce your issue locally! > > In a Fedora 26 VM, I set the hostname as follows: > > hostnamectl set-hostname fedora.local.home.ionic.de > > Then, I edited /etc/hosts and added: > > 192.168.122.128 fedora

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-10 Thread Robert Kudyba
Now on the working server we have a user reporting an issue where X2Go loses "focus". He gets a high-pitched clicking sound as he's typing in a window running under X2Go, e.g., an emacs window. When this happens, he needs to click someplace in the window in which he was working. He's using High

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-07 Thread Robert Kudyba
> > > There's also a slight possibility that the removal of libnxau in Arctica's > nx-libs version (with some code moves to libNX11) causes problems, but we > haven't seen a problem like this in other (though mostly Debian-based) > setups yet. > Would any logs show this problem? How can we

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-07 Thread Mihai Moldovan
On 11/06/2017 08:22 PM, Robert Kudyba wrote: > Could there be another package or service installed on the non-working machine > vs working that is causing this conflict? In theory yes, but it fails at such an early stage that it's very unlikely, that some other component is playing a big role in

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-06 Thread Robert Kudyba
> The important stuff is here: > >> Nov 05 15:00:39 ourschool.edu >> /usr/bin/x2gostartagent[1221]: started nxagent: NX_TEMP=/tmp x2goagent >> X2GO_NXAGENT_OPTIONS (' -extension XFIXES -nolisten tcp') NOLISTOPT >> ('-nolisten >> tcp') X2GODPIOPTION_ ('-dpi 72') XDMCPPOPT

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-06 Thread Mihai Moldovan
No, don't worry, your message made it to the list yesterday, c.f., http://lists.x2go.org/pipermail/x2go-dev/2017-November/012235.html On 11/05/2017 09:08 PM, Robert Kudyba wrote: > Wow is there a lot of stuff in there. Is there a way to narrow this down? Here > are some logs from the journal:

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-05 Thread Mihai Moldovan
On 11/05/2017 07:57 PM, Robert Kudyba wrote: > loglevel=debug *sigh* I just tested this myself. On Fedora, it looks like the debug syslog level is not written to any file in /var/log/. The only way to get to this information is to use journalctl (and just in case something aliases this to a

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-05 Thread Robert Kudyba
> > x2goserver-4.1.0.0-0.0x2go1.0.git20171105.1438.heuler.fc26.x86_64 > > Okay, so in that case you probably haven't set the loglevel to debug in > /etc/x2go/x2goserver.conf : > Nope been debug for a while now: [log] # possible levels are: emerg, alert, crit, err, warning, notice, info, debug

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-05 Thread Mihai Moldovan
On 11/05/2017 07:32 PM, Robert Kudyba wrote: > x2goserver-4.1.0.0-0.0x2go1.0.git20171105.1438.heuler.fc26.x86_64 Okay, so in that case you probably haven't set the loglevel to debug in /etc/x2go/x2goserver.conf :) Mihai signature.asc Description: OpenPGP digital signature

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-05 Thread Robert Kudyba
> > Nov 5 12:55:39 sobolev /usr/bin/x2gostartagent[5956]: creating new > session: > > localguy-158-1509904537_stDXFCE_dp32 987f364647dc4560b0c0eb10e7d16eeb > 5954 > > 65.78.12.82 58562 58563 58564 -1 -1 > > No, that's missing the new debug message. Are you sure you updated > x2goserver > before

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-05 Thread Mihai Moldovan
On 11/05/2017 07:03 PM, Robert Kudyba wrote: > I had to install the DMG client from Nov. 5 > as git20171029.1693.heuler.OSX_10_10.dmg > >  just > hung for 20 minutes with no real

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-05 Thread Robert Kudyba
> > One way this may go haywire looks like this: [...] > > I've added more debugging to x2gostartagent. FC26 have completed already, > so you > know the drill. Update the system, then start a new session (will fail, but > that's fine) and look at the syslog. > > I'm only interested in the new

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-05 Thread Mihai Moldovan
On 11/05/2017 03:41 PM, Mihai Moldovan wrote: > One way this may go haywire looks like this: [...] I've added more debugging to x2gostartagent. FC26 have completed already, so you know the drill. Update the system, then start a new session (will fail, but that's fine) and look at the syslog. I'm

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-05 Thread Mihai Moldovan
On 11/05/2017 03:03 PM, Robert Kudyba wrote: > more options  > >

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-05 Thread Robert Kudyba
> > The server that works, that's where the NFS share is mounted. The > workstation > > that fails, it uses the mounted NFS share from the server that works. > > You mean the server that works is where the NFS share is mounted *from* - > so for > the server, this is a local filesystem, while for

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-05 Thread Mihai Moldovan
On 11/04/2017 09:35 PM, Ulrich Sibiller wrote: > So you are using arctica with ADSL. ADSL connections have been > modified twice after 3.5.99.7, so maybe you should try the newest > version, at least for improved speed. True, I'd like to point out that these changes should at most affect the

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-04 Thread Robert Kudyba
> - is that server also the NIS server? > No it's the file server. Just wanted to remind that we experience the same errors with a local (non NIS) user. > - what NFS version are you using? > We do nightly DNF updates: qemu-block-nfs-2.9.1-1.fc26.x86_64 sssd-nfs-idmap-1.15.3-5.fc26.x86_64

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-04 Thread Robert Kudyba
> > It fails with NIS users and local users. On the working and non-working > machine, > > I try with a local user and both $HOME are set as follows: > > echo $HOME > > /home/localguy > > That's normal. When you did the plain xauth/nxagent tests I requested a few > mails ago, did you test with a

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-04 Thread Mihai Moldovan
On 11/03/2017 07:58 PM, Robert Kudyba wrote: > On another server that works OK I just killed an X2Go session from August! > student    21855  0.0  0.0 151456   632 ?        S    Aug31   0:23 > /usr/lib64/nx/../x2go/bin/x2goagent -extension XFIXES -nolisten tcp -nolisten > tcp -dpi 120 -D -auth

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-03 Thread Robert Kudyba
> > > Yes. > > That's weird, it sounds like sessions are accumulating in the database, > but not > printed out. This shouldn't happen, since sessions in the failed state > should be > automatically removed when executing this program (and also indirectly > through > this mechanism by

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-02 Thread Mihai Moldovan
On 11/02/2017 03:15 PM, Robert Kudyba wrote: > Both commands come back with nothing. Even when executed as root? I guess these sessions are still listed in the database and that x2gocleansessions (which should be running as part of either the x2goserver or x2gocleansessions systemd service file)

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-02 Thread Robert Kudyba
> On Nov 2, 2017, at 1:13 AM, Mihai Moldovan wrote: > > On 11/01/2017 02:31 PM, Robert Kudyba wrote: >>> ls -a /tmp/.X11-unix >>> ps axu | grep -iE '(nx|x2goagent)' >>> >>> Naturally on the server side. >> >> ls -a /tmp/.X11-unix >> . .. X0 > > Hum... if there are no stale

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-11-01 Thread Mihai Moldovan
On 11/01/2017 02:31 PM, Robert Kudyba wrote: >> ls -a /tmp/.X11-unix >> ps axu | grep -iE '(nx|x2goagent)' >> >> Naturally on the server side. > > ls -a /tmp/.X11-unix > .  ..  X0 Hum... if there are no stale X sockets, why is x2gostartagent counting up? What do ps axu | grep -iE

Re: [X2Go-Dev] new version 4.1.1.0 from Mac still crashes to Fedora 26

2017-10-29 Thread Mihai Moldovan
On 10/29/2017 10:23 PM, Robert Kudyba wrote: > Fresh upgrade from this morning.  Below are some debug client logs. I also > posted to pastebin a crash log from the Mac crash submit tool before hitting > send: > https://pastebin.com/ETfhdMZt Hum, the client is crashing? Has this been happening