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,

[X2Go-Dev] Bug#651: x2goclient segfault on update to 4.0.3 on ubuntu 14.04

2017-11-15 Thread Mihai Moldovan
* On 11/15/2017 09:29 AM, Rob Izzard wrote: > wow, this was a long time ago :) Yeah, I went through some old bug reports. Sometimes they are still valid but require more input, other times they either look like duplicates or like reports that were fixed meanwhile - but never marked as such. And