x2go-dev

x2go-dev@lists.x2go.org

2 participants
5403 discussions

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

Bug#628: x2goclient can not be compiled on Raspberry PI
by Heinrich Schuchardt 26 Jan '15

26 Jan '15

In the Rasbian repository I find http://archive.raspbian.org/raspbian/pool/main/x/x2goclient/x2goclient_4.0.… So obviously it was possible to compile this version of x2go-client for the Raspberry and Debian package with version 4.x is available. Hence I suggest to close #628 as fixed. Best regards Heinrich Schuchardt

1 0

Bug#768: Mediastreamer as addition and long-term replacement of client-side PulseAudio
by Stefan Baur 26 Jan '15

26 Jan '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 package: x2goclient severity: wishlist Alex (see CC) has an interesting concept for replacing the client-side pulseaudio with something that can handle compression and is more easily available on all 3 major client platforms. This bug serves as a reminder so the idea doesn't get lost, and so that Alex can outline his ideas in a central location. - -Stefan - -- 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) iQEcBAEBAgAGBQJUxl5BAAoJEG7d9BjNvlEZAg4H/RkbPfvHLf/htfYLs2znnXkT CRv5SzEBEsP3uNb4Lh9W1vw/yFIthoFSTjZoQO3ffK+cV9/CUMEd+OFklejOpaRM TLx58efTbizsZkw25NzGLJ4v7cRnzY3BgslSLKX4cdK0FDIIc3H38pv5kGKU7wL9 pY5yGbLvsUcuNBU3hYZFKR4QBwumhbVMZgqSeEC+lBT80Sjhxlbmr0F/mX332rGz uLtRVqIH59KhK10Xxt4wb7o5tID0qcTJqsSHlOktjR5DtDIpwk3+U8X5H7UdgfH+ gzQ3QC0/cbFGnksDZDMz5sa1pf1EgaAdbOk6OiQbQo5ASoStdyuXK2FIe9z95VY= =EQXk -----END PGP SIGNATURE-----

1 0

FYI, libssh 0.7 will support diffie-hellman-group-exchange-sha256
by Michael DePaulo 26 Jan '15

26 Jan '15

For those who do not know, x2goclient uses libssh. http://www.mail-archive.com/libssh@libssh.org/msg01906.html

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev