x2go-dev January 2015

x2go-dev@lists.x2go.org

46 participants
246 discussions

Bug#742: X2Go issue (in src:x2goclient) has been marked as pending for release
by Mike DePaulo 27 Jan '15

27 Jan '15

tag #742 pending fixed #742 4.0.3.2 thanks Hello, X2Go issue #742 (src:x2goclient) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=fd1151e The issue will most likely be fixed in src:x2goclient (4.0.3.2). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit fd1151e48ad325c18857f1d3daceb5b8e5edda9d Author: Mike DePaulo <mikedep333(a)gmail.com> Date: Sun Jan 25 09:52:38 2015 -0500 Update Changelog about #742 diff --git a/debian/changelog b/debian/changelog index 9e4d06b..e50be3b 100644 --- a/debian/changelog +++ b/debian/changelog @@ -58,6 +58,10 @@ x2goclient (4.0.3.2-0x2go1) UNRELEASED; urgency=medium functionality, not the SSH server functionality. 0.6.4 also added 4 features related to ECDSA keys. - Windows: Fix compatibility with PulseAudio 6.0 + - Windows: Remove workaround for audio input with old versions of + PulseAudio (calling parec once per second) + (Fixes: #742) + Thanks George Trakatelis (uom.edu.gr) for submitting this change. - Windows: Enable X2Go Client for Windows to build under VS2010 nmake (but not the VS2010 IDE due to a Qt4 Visual Studio Add-in limitation) Note that the official builds are still build under MinGW.

3 2

RfC: How should X2Go handle commercial offers/sponsorships and discussions related to that?
by Stefan Baur 27 Jan '15

27 Jan '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, and sorry for not making any further announcements lately. Things have been pretty busy here, and to top it off, I was sick with a severe cold and fever for a good part of the last week. As you may know, there is an "inner circle" in the X2Go project called the "core team" consisting mainly of the X2Go founders, core developers, and other people currently earning money with X2Go. During the first few weeks of my "reign", I tried to keep the commercial discussions amongst the core team members out of x2go-dev and out of x2go-project. (My rationale: use x2go-dev for development, use x2go-project for project policies and politics, commercial topics should not "spam" either of those.) This has led to a negative feedback from one of the core team members, stating that everything should be public. We obviously seem to have a different understanding of what "public" can mean. I would have considered a Wiki page public enough. Seems that not everybody agrees. Now, I don't think either of us is right or wrong here, it just shows that one can have a different viewpoint. So I would like to ask the x2go-dev community at large: Are you interested in reading all the gory details regarding sponsored development on X2Go, here on this mailing list? Please choose: a1) Yes, please discuss this on x2go-dev a2) Yes, please discuss this on x2go-project b) Please use a different (new) mailing list dedicated to that purpose c) No, please keep the mailing lists a community-only place d) I have an entirely different, better solution, namely: ____________ I will collect your feedback during the next two weeks and will make up my mind after that. Kind regards, Stefan X2Go Lead Evangelist/Project and Community Coordinator - -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUx2h6AAoJEG7d9BjNvlEZkqkIAJl2r9mNbmEChONrhpcaw8/g FNxfTOaKkEy2XRHOpXmVN4ufqgpLJaO/BI99IPVSe7ptmX+7+aSJ5b1YZ5BAAYaW CuZIPxlX62HanbHjgDg2CflBZXzHKt6yNRwnSkhw/6c7rpY06oz0zmFA24HD9tmL d8azqOQziJw3KjwM4vgE81S8AnSMs0aCrDxIyBdegJ3v7xEtL9sz/9HVuNeCtRAB HRLOEUma/wr49ecCpxv59alWimWUumV76pUb7Zrpv0PimDGUBx/sxUP/VbxXdq1c xnpvSjfMT2Mtw2iMfZ1QedmVmMKAMf75bP29JsNFuQpzGbwrfH1xkM6Ck2C8L9I= =ioP7 -----END PGP SIGNATURE-----

7 17

can you reject my reply to bug 215 ?
by x2go.guillaume＠zitta.fr 27 Jan '15

27 Jan '15

Hi, I used a wrong email address in my reply to bug 215. This is an address that shoul never be visible on public web pages. Can you reject my reply, so I can re-send it with my "x2go" address. Thanks

2 1

Bug#215: Possible fix or workaround
by Guillaume ZITTA 27 Jan '15

27 Jan '15

I had this trouble with 4.2.0.1, but after upgrade to 4.3.0.1 (and use and external vcxsrv due to bug #670), I can't reproduce the problem anymore. If it helps ...

1 0

Re: [X2Go-Dev] X2Go module purposes
by Mike 26 Jan '15

26 Jan '15

Resending to list not Stefan! On 01/26/2015 06:20 PM, Mike wrote: > On 01/26/2015 05:02 PM, Stefan Baur wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Am 26.01.2015 um 22:44 schrieb Short, Kermit: >>> It's certainly something I'd like to try, but if I recall >>> correctly, the firmware is only loosely based on LTS. The actual >>> OS on the thin client is heavily customized. >> Well, I hope I'm not talking out of my lower back here, but it can't >> be much more complicated than grabbing our packages, unpacking them, >> and checking for any dependencies that they need to have met. >> >> Possibly apply some ldd and strace to see where things are going wrong. > Yes, excellent advice! Although I'm a lazy admin and don't see the > need for ldd or strace here. The .deb package info is able to give us > all the reverse dependency information. Many ways to obtain it I'm > sure, apt-cache showpkg or using the package search on the Debian > website should revel all the needed information. Surely Ubuntu has a > similar webpage available. > >> >> >>> Working with debian packages is not something I've done much, and >>> then only to build them rather than deconstruct them. >> It's actually not that hard. If you have a copy of midnight commander >> (mc) installed, you can usually go inside them like any other virtual >> file system (like when you "open" a *.tar.gz file with mc). >> There are also command line tools available to unpack Debian/Ubuntu >> packages without installing them. > ar x some-package_0.1.2.deb . > dpkg --extract some-package_0.1.2.deb . > dpkg -x some-package_0.1.2.deb . > > Certainly there are other ways... >> >>> I do really like the idea of a chroot shell, though. I'm currently >>> using AIDE to look at changes pre and post build, and then I go >>> through interactive error messages on the IGEL to determine what >>> additional libraries are necessary. >>> >>> The last time I did this, there were several libraries provided by >>> the LTS footprint that were not provided on the IGEL, so it's a >>> little easier for me to do the scratch build, since I have to do >>> some by hand tracing anyway. >> That sounds really painful. In a first step, I'd try to parse the >> output of ldd for every executable I want to copy, then make sure I >> have those files either available on the IGEL, or know I have copy >> them over along with the executable. >> >> for example (this is on Debian Wheezy, not Ubuntu, but the process >> should be the same): >> >> dpkg -L libnx-x11 >> >> gives >> >> /. > <chopped some dpkg output> >> and just grabbing one sample from here, >> /usr/lib/nx/X11/libNX_Xrender.so.1, >> >> ldd /usr/lib/nx/X11/libNX_Xrender.so.1 gives >> >> linux-gate.so.1 => (0xb7702000) >> libNX_Xext.so.6 => not found >> libNX_X11.so.6 => not found >> libc.so.6 => /lib/i386-linux-gnu/i686/cmov/libc.so.6 >> (0xb7583000) >> /lib/ld-linux.so.2 (0xb7703000) >> >> As this is from a working system, I would assume the two "not found"s >> are harmless, but I need to make sure I have the other files on my >> target system in some way - either from the original OS image, or by >> copying them over. > If memory serves X2Go is setting LD_LIBRARY_PATH to where the libNX* > and probably other NX specific libs live. The dependency information > of the .deb file(s) should point these out without having to use ldd. >>> Being able to do this from a debian package in a root shell would >>> be very handy, though!! >> Well, I can't do more than suggest you try it and see if it turns out >> to be the easier way. :-) >> >> How large is that extra partition you can access, anyway? >> Large enough to untar a complete non-IGEL linux distribution there and >> chroot or possibly even kexec into it? >> >> Another option would be to offer one or more of your IGELs to >> interested developers so they can do the grunt work for you. >> >> - -Stefan > > Hopefully some of this can be of some help. If I can get away without > building things from scratch I'm all for it. Like I said I'm a lazy > admin, building software isn't one of my favorite things in life. > > Mike

1 0

Bug#761: Fwd: [Bug 1186025] New: [abrt] x2goclient: QProcess::terminate(): x2goclient killed by SIGSEGV
by Orion Poplawski 26 Jan '15

26 Jan '15

This looks very similar. Also, looks like bug 762 is duplicate of this. -------- Forwarded Message -------- Subject: [Bug 1186025] New: [abrt] x2goclient: QProcess::terminate(): x2goclient killed by SIGSEGV Date: Mon, 26 Jan 2015 20:43:59 +0000 From: bugzilla(a)redhat.com To: orion(a)cora.nwra.com https://bugzilla.redhat.com/show_bug.cgi?id=1186025 Bug ID: 1186025 Summary: [abrt] x2goclient: QProcess::terminate(): x2goclient killed by SIGSEGV Product: Fedora Version: 20 Component: x2goclient Assignee: orion(a)cora.nwra.com Reporter: christopher.bollinger(a)momentumtelecom.com QA Contact: extras-qa(a)fedoraproject.org CC: orion(a)cora.nwra.com Description of problem: Problem occurred upon breaking a connection. I closed the window showing my remote X display using the 'X' at the top right of the window. Version-Release number of selected component: x2goclient-4.0.3.1-1.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: x2goclient crash_function: QProcess::terminate executable: /usr/bin/x2goclient kernel: 3.17.8-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 QProcess::terminate at io/qprocess.cpp:2112 #1 ONMainWindow::termSession at ../onmainwindow.cpp:5952 #2 ONMainWindow::slotTermSessFromSt at ../onmainwindow.cpp:4573 #3 ONMainWindow::qt_static_metacall at moc_onmainwindow.cpp:366 #4 QMetaObject::activate at kernel/qobject.cpp:3567 #5 QAbstractButton::clicked at .moc/release-shared/moc_qabstractbutton.cpp:219 #6 QAbstractButtonPrivate::emitClicked at widgets/qabstractbutton.cpp:548 #7 QAbstractButtonPrivate::click at widgets/qabstractbutton.cpp:541 #8 QAbstractButton::mouseReleaseEvent at widgets/qabstractbutton.cpp:1123 #9 QToolButton::mouseReleaseEvent at widgets/qtoolbutton.cpp:723 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

Bug#641: Fwd: [Bug 1186049] New: [abrt] nxagent: nxagentFreeFontCache(): nxagent killed by SIGABRT
by Orion Poplawski 26 Jan '15

26 Jan '15

This seems to be a similar crash in nxagentReconnectFailedFonts(). -------- Forwarded Message -------- Subject: [Bug 1186049] New: [abrt] nxagent: nxagentFreeFontCache(): nxagent killed by SIGABRT Date: Mon, 26 Jan 2015 22:22:47 +0000 From: bugzilla(a)redhat.com To: orion(a)cora.nwra.com https://bugzilla.redhat.com/show_bug.cgi?id=1186049 Bug ID: 1186049 Summary: [abrt] nxagent: nxagentFreeFontCache(): nxagent killed by SIGABRT Product: Fedora Version: 21 Component: nx-libs Assignee: orion(a)cora.nwra.com Reporter: carlos.em.esteves(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: orion(a)cora.nwra.com Description of problem: x2Go Server with Mac Client, probleme with resolution the monitor... I don't now what caused this problem... Version-Release number of selected component: nxagent-3.5.0.28-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/lib64/nx/../x2go/bin/x2goagent -extension XFIXES -nolisten tcp -nolisten tcp -dpi 72 -D -auth /home/cares/.Xauthority -name X2GO-cares-50-1422299914_stDXFCE_dp32 :50 crash_function: nxagentFreeFontCache executable: /usr/lib64/nx/bin/nxagent kernel: 3.18.3-201.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #6 nxagentFreeFontCache at Font.c:199 #7 nxagentCloseDisplay at Display.c:1825 #8 AbortDDX at Init.c:455 #11 nxagentFailedFontReconnect at Font.c:1209 #12 nxagentReconnectFailedFonts at Font.c:1327 #13 nxagentReconnectSession at Reconnect.c:482 #14 nxagentHandleConnectionChanges at Reconnect.c:827 #15 nxagentHandleConnectionStates at Reconnect.c:218 #16 nxagentWakeupHandler at Handlers.c:589 #17 WakeupHandler at dixutils.c:472 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

X2Go module purposes
by Short, Kermit 26 Jan '15

26 Jan '15

Greetings! I've recently been able to build x2goclient from source. As I was working through that process, I began to wonder if everything needed to run the client is built with the client. Obviously there are various nxproxy dependencies, but there are also source trees for other components of x2go. For example, do I need to build libpam-x2go in order for the x2goclient? I'm thinking this is more of a server aspect, but I'm not positive. How about cups-x2go? The build I'm doing will be processed into a tarball and installed on various thin client devices, so I want to make sure that I know of every file and library I'll need to build/collect/install. Thanks! -- Kermit Short, RHCE, RHCVA Sr. Solutions Architect

2 7

Status of armhf-related builds/open bugs
by Stefan Baur 26 Jan '15

26 Jan '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, could you two please comment on http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=628 and http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=644 what is needed to fix the issues? Do we need remote access to armhf testing/build hardware, physical access, more debug logs, ...? - -Stefan PS: I don't want to promise anything yet, but from a recent off-list conversation, I think I might know somebody willing to sponsor some armhf hardware for us ... - -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUxfiSAAoJEG7d9BjNvlEZjugH/RAB38KMxMVQ5Ina6UbZZaXi 9UHUfgGKQwlSEJAFuXrB1c1XyNo9tWfsxHCwBiCyno2GnwGF7yL6QXbfPQwwGR43 FeQ2uiwzbfTqWnrE4m7jBcfTfMkiMBYgshnz6dOUEgg1eOdjP/131qbQHx+ydTrS 7Qlq5l8Wnw9hQ+/jxCOoQtu+vq3p2INaoJ2tbNvwC0NuYkmXaaMFnjOrmUNedlLa 0LzWQHaBeS4Hw6QK+04v25KUrRlggdC2LyvViEfg4VQP5fHOvNUT5KXzVC9PBmEv WxCAYM4ZtwOhRtq1jvSgDN2UNvdhq9RfreUqHkGGp/W2ZFzUo9XwFP3qcPs7ExU= =RXD/ -----END PGP SIGNATURE-----

3 4

Bug#644: x2goserver : The $SSH_CLIENT environment variable is not set
by Heinrich Schuchardt 26 Jan '15

26 Jan '15

Hello Franz, In #628 you wrote > But when I say > # apt-get download x2goclient > I get x2goclient_3.99.2.1-5_armhf.deb > And this version makes a lot of problems with an X2goserver 4.0.1.16. It remains unclear in #644 if you are still trying to use client 3.99.2.1-5_armhf.deb. Please, provide both for x2goserver and x2goclient the version, the architecture, the Linux distribution, and the apt repository you are using. Best regards Heinrich Schuchardt

1 0

← Newer
1
...
8
9
10
11
12
13
14
...
25
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev January 2015