x2go-commits August 2015

x2go-commits@lists.x2go.org

3 participants
43 discussions

page changed: doc:faq:start
by wiki-admin＠x2go.org 21 Aug '15

21 Aug '15

A page in your DokuWiki was added or changed. Here are the details: Date : 2015/08/21 01:08 Browser : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.37 Safari/537.36 IP-Address : 96.245.198.248 Hostname : pool-96-245-198-248.phlapa.fios.verizon.net Old Revision: http://wiki.x2go.org/doku.php/doc:faq:start?rev=1440117653 New Revision: http://wiki.x2go.org/doku.php/doc:faq:start Edit Summary: Add: Why not just use X11 forwarding over SSH? This is what Keith Package recommended. User : mikedep333 @@ -22,9 +22,9 @@ Nowadays the NX libs shipped with X2Go work as a replacement for the NXv3 that are not maintained by NoMachine anymore. (This FAQ article has been written by Mike Gabriel, if someone does not agree with the given information on NoMachine, please be so kind to contact me, so that we can discuss it and possibly correct errors in the given information). - ==== Why are you using the terms "nx-libs" and "NX libraries" when X2Go uses the 2 executables nxproxy & nxagent? ==== + ==== Why are you using the terms "nx-libs" and "NX libraries"? X2Go clearly uses the 2 executables nxproxy & nxagent? ==== Basically: - That is the term that was always used. @@ -43,8 +43,22 @@ Only the 1st 3 are libraries. Having separate tarballs made maintenance more difficult, so they were combined into one as the X2Go project started redistributing them. + + ==== Why not just use X11 forwarding over SSH? This is what Keith Package recommended. ==== + + You are probably referring to the [[http://keithp.com/~keithp/talks/lbxpost/|LBX post-mortem]] + + It is true that X11 forwarding's performance can be improved by SSH's zlib compression and by the use of XCB rather than xlib. + + However, nx-libs performs 3 additional performance improvements: + + - nx-libs caches images, so that they do not have to be resent. For example, opening up your "start menu" is very fast the 2nd and 3rd time that you do so. + - zlib is generic lossless compression, so it is not well-suited for images. nx-libs acheives better performance by using compression methods such as JPEG (default, lossy) or PNG (lossless.) + - XCB applications are still partially hindered by round-trips, and nx-libs eliminates more of those round-trips. See [[https://lwn.net/Articles/343506/|Bart Massey's explanation]] for more info. + + The 1st 2 performance improvements also reduce bandwidth usage; which has the effect of improving performance when other users are sharing the same WAN link. ==== What is the difference to LTSP? Why a free thin client environment? ==== LTSP requires a high bandwidth on your network. It can efficiently be used in Local Area Networks (LANs) only. -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: doc:faq:start
by wiki-admin＠x2go.org 21 Aug '15

21 Aug '15

A page in your DokuWiki was added or changed. Here are the details: Date : 2015/08/21 00:40 Browser : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.37 Safari/537.36 IP-Address : 96.245.198.248 Hostname : pool-96-245-198-248.phlapa.fios.verizon.net Old Revision: http://wiki.x2go.org/doku.php/doc:faq:start?rev=1440117410 New Revision: http://wiki.x2go.org/doku.php/doc:faq:start Edit Summary: Rework: Is X2Go compatible with NoMachine's NX or freeNX? User : mikedep333 @@ -6,9 +6,9 @@ ==== Is X2Go compatible with NoMachine's NX or freeNX? ==== No. It is not possible to use NX client to log on to an X2Go server and vice versa. - Even though X2Go uses the same libraries, X2Go aims for an even greater integration into the Linux environment. + X2Go does use the same libraries for graphics, keyboard/mouse input, and clipboard sharing. However, X2Go aims for an even greater integration into the Linux environment. Therefore, X2Go performs session handling in an incompatible manner. X2Go also performs SSH authentication in a different manner than NoMachine does. ==== Can I install FreeNX and X2Go Server on one system? ==== -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: doc:faq:start
by wiki-admin＠x2go.org 21 Aug '15

21 Aug '15

1 0

page changed: doc:faq:start
by wiki-admin＠x2go.org 21 Aug '15

21 Aug '15

A page in your DokuWiki was added or changed. Here are the details: Date : 2015/08/21 00:36 Browser : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.37 Safari/537.36 IP-Address : 96.245.198.248 Hostname : pool-96-245-198-248.phlapa.fios.verizon.net Old Revision: http://wiki.x2go.org/doku.php/doc:faq:start?rev=1440117319 New Revision: http://wiki.x2go.org/doku.php/doc:faq:start Edit Summary: Forgot to add heading for "Server" FAQ" User : mikedep333 @@ -52,8 +52,10 @@ However, X2Go is not a mere solution for local area networks, but it also allows for the integration of a mobile network into the system. Nomachine’s NX libraries - used by X2Go - enable the transport of whole desktop sessions over a narrow bandwith connection through the internet. Further bonuses of X2Go are that you can pause a desktop session and take it to a different thin client for further use. + + ===== Server FAQ ===== ==== What are the packages x2goserver-home and x2goserver-one for? ==== Both packages (''x2goserver-home'', ''x2goserver-one'') are obsolete as of April 2011. They have been removed from the current .deb repositories and they should not be used anymore (in fact they break your system). On .deb based system they will automatically be uninstalled with an update of the ''x2goserver'' package. -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: doc:faq:start
by wiki-admin＠x2go.org 21 Aug '15

21 Aug '15

A page in your DokuWiki was added or changed. Here are the details: Date : 2015/08/21 00:35 Browser : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.37 Safari/537.36 IP-Address : 96.245.198.248 Hostname : pool-96-245-198-248.phlapa.fios.verizon.net Old Revision: http://wiki.x2go.org/doku.php/doc:faq:start?rev=1440116127 New Revision: http://wiki.x2go.org/doku.php/doc:faq:start Edit Summary: Add: Why are you using the terms "nx-libs" and "NX libraries" when X2Go uses the 2 executables nxproxy & nxagent? User : mikedep333 @@ -1,9 +1,9 @@ ====== FAQ ====== For those who want to find reasons for certain behavious of X2Go, read here: [[http://wiki.x2go.org/doku.php/wiki:development:debugging|How To Debug or Troubleshoot your X2Go installation]] - ===== Server FAQ ===== + ===== NX FAQ ===== ==== Is X2Go compatible with NoMachine's NX or freeNX? ==== No. It is not possible to use NX client to log on to an X2Go server and vice versa. @@ -22,8 +22,30 @@ Nowadays the NX libs shipped with X2Go work as a replacement for the NXv3 that are not maintained by NoMachine anymore. (This FAQ article has been written by Mike Gabriel, if someone does not agree with the given information on NoMachine, please be so kind to contact me, so that we can discuss it and possibly correct errors in the given information). + + ==== Why are you using the terms "nx-libs" and "NX libraries" when X2Go uses the 2 executables nxproxy & nxagent? ==== + + Basically: + + - That is the term that was always used. + - Libraries are created also from the source package. + - Those libraries define the NX protocol. + + Note that originally, "nx-libs" was not a single git repo. Instead, it was 7 separate tarballs: + + - nxcomp + - nxcompext + - nxcompshad + - nxproxy + - nxagent + - nxauth + - nx-X11 + + Only the 1st 3 are libraries. + + Having separate tarballs made maintenance more difficult, so they were combined into one as the X2Go project started redistributing them. ==== What is the difference to LTSP? Why a free thin client environment? ==== LTSP requires a high bandwidth on your network. It can efficiently be used in Local Area Networks (LANs) only. -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: doc:faq:start
by wiki-admin＠x2go.org 21 Aug '15

21 Aug '15

A page in your DokuWiki was added or changed. Here are the details: Date : 2015/08/21 00:15 Browser : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.37 Safari/537.36 IP-Address : 96.245.198.248 Hostname : pool-96-245-198-248.phlapa.fios.verizon.net Old Revision: http://wiki.x2go.org/doku.php/doc:faq:start?rev=1440115224 New Revision: http://wiki.x2go.org/doku.php/doc:faq:start Edit Summary: Update FAQ about NoMachine compatibility User : mikedep333 @@ -3,11 +3,15 @@ For those who want to find reasons for certain behavious of X2Go, read here: [[http://wiki.x2go.org/doku.php/wiki:development:debugging|How To Debug or Troubleshoot your X2Go installation]] ===== Server FAQ ===== - ==== Is X2Go compatible with nomachines NX or freeNX? ==== + ==== Is X2Go compatible with NoMachine's NX or freeNX? ==== - No even though X2Go uses the same libraries, X2Go aims for an even greater integration into the Linux environment. It’s not possible to use NX client to log on to an X2Go server and vice versa. + No. It is not possible to use NX client to log on to an X2Go server and vice versa. + + Even though X2Go uses the same libraries, X2Go aims for an even greater integration into the Linux environment. + + X2Go also performs SSH authentication in a different manner than NoMachine does. ==== Can I install FreeNX and X2Go Server on one system? ==== Yes - the NX libraries of X2Go are actually the most recent versions of NXv3 libs available (including our own patch set). NoMachine is about to drop the NXv3 development branch completely and NXv4 will be released as closed source only :-(. -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: doc:faq:start
by wiki-admin＠x2go.org 21 Aug '15

21 Aug '15

A page in your DokuWiki was added or changed. Here are the details: Date : 2015/08/21 00:00 Browser : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.37 Safari/537.36 IP-Address : 96.245.198.248 Hostname : pool-96-245-198-248.phlapa.fios.verizon.net Old Revision: http://wiki.x2go.org/doku.php/doc:faq:start?rev=1438801205 New Revision: http://wiki.x2go.org/doku.php/doc:faq:start Edit Summary: Move Client FAQ after Server FAQ User : mikedep333 @@ -39,8 +39,31 @@ ==== Do I need a PostgreSQL database to run X2Go Server? ==== No. The postgres database is only needed if you are planing to use more than one connected server (server array). By default X2Go Server installs with SQLite3 support enabled. To set up X2Go with PostgreSQL as DB backend you have to edit the X2Go Server's configuration in /etc/x2go. + ===== Client FAQ ===== + + ==== Is there an MS Windows Client? ==== + + Yes, there are two: [[doc:installation:x2goclient#ms_windows|X2Go Client]] and [[doc:installation:pyhoca-gui#ms_windows|PyHoca-GUI]]. + + ==== Is there a MacOS Client? ==== + + [[doc:installation:x2goclient#macos_x|Yes!]] + + ==== Why is there no sound using Linux? ==== + Probably because the server does not listen to client connections. Check whether the file ''/etc/pulse/default.pa'' on the client contains the line: + <code> + load-module module-native-protocol-tcp auth-cookie=".pulse-cookie" + </code> + If not, add it. Alternatively you can load the module at runtime: + <code> + pactl load-module module-native-protocol-tcp 'auth-cookie=".pulse-cookie"' + </code> + + ==== Can I use x2goprint with Windows Clients? ==== + + To set a print target, you'll need ''x2goclient''. For example you can use the RDP tunneling feature of X2Go. FIXME ===== Session FAQ ===== ==== How do I change the keyboard layout? ==== @@ -91,36 +114,8 @@ This KB article shows one solution for this: [[http://kb.mozillazine.org/Firefox_:_FAQs_:_Run_more_than_one_instance_in_Li… kb.mozillazine.org/Firefox_:_FAQs_:_Run_more_than_one_instance_in_Linux]] - - - ===== Client FAQ ===== - - ==== Is there an MS Windows Client? ==== - - Yes, there are two: [[doc:installation:x2goclient#ms_windows|X2Go Client]] and [[doc:installation:pyhoca-gui#ms_windows|PyHoca-GUI]]. - - ==== Is there a MacOS Client? ==== - - [[doc:installation:x2goclient#macos_x|Yes!]] - - - - ==== Why is there no sound using Linux? ==== - Probably because the server does not listen to client connections. Check whether the file ''/etc/pulse/default.pa'' on the client contains the line: - <code> - load-module module-native-protocol-tcp auth-cookie=".pulse-cookie" - </code> - If not, add it. Alternatively you can load the module at runtime: - <code> - pactl load-module module-native-protocol-tcp 'auth-cookie=".pulse-cookie"' - </code> - - - ==== Can I use x2goprint with Windows Clients? ==== - - To set a print target, you'll need ''x2goclient''. For example you can use the RDP tunneling feature of X2Go. FIXME ===== Known Issues ===== ==== Can't login to x2goserver with an ECDSA key ==== -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

[x2goclient] branch master updated (4b86435 -> 9dea920)
by git-admin＠x2go.org 12 Aug '15

12 Aug '15

This is an automated email from the git hooks/post-receive script. x2go pushed a change to branch master in repository x2goclient. from 4b86435 - xsettingswidget: compile only on Windows. new 9dea920 Add support for new style command line options of xfreerdp on direct RDP connections. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: debian/changelog | 2 ++ src/onmainwindow.cpp | 81 +++++++++++++++++++++++++++++++++--------------- src/settingswidget.cpp | 72 ++++++++++++++++++++++++++++++++---------- src/settingswidget.h | 3 +- 4 files changed, 115 insertions(+), 43 deletions(-) -- Alioth's /srv/git/code.x2go.org/x2goclient.git//..//_hooks_/post-receive-email on /srv/git/code.x2go.org/x2goclient.git

1 1

[x2goclient] branch master updated (3030896 -> 4b86435)
by git-admin＠x2go.org 12 Aug '15

12 Aug '15

This is an automated email from the git hooks/post-receive script. x2go pushed a change to branch master in repository x2goclient. from 3030896 onmainwindow.cpp: include sshd PID file path option in quotes to support whitespaces within the var directory path on Windows. new 4b86435 - xsettingswidget: compile only on Windows. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: debian/changelog | 4 ++++ src/xsettingswidget.cpp | 4 ++-- src/xsettingswidget.h | 3 ++- 3 files changed, 8 insertions(+), 3 deletions(-) -- Alioth's /srv/git/code.x2go.org/x2goclient.git//..//_hooks_/post-receive-email on /srv/git/code.x2go.org/x2goclient.git

1 1

Build failed in Jenkins: x2goclient+nightly+debian-sid #355
by jenkins＠x2go.org 12 Aug '15

12 Aug '15

See <http://jenkins.x2go.org:8080/job/x2goclient+nightly+debian-sid/355/changes> Changes: [ionic] onmainwindow.cpp: include sshd PID file path option in quotes to support whitespaces within the var directory path on Windows. ------------------------------------------ [...truncated 1813 lines...] Preparing to unpack .../libqt4-scripttools_4%3a4.8.7+dfsg-3_amd64.deb ... Unpacking libqt4-scripttools:amd64 (4:4.8.7+dfsg-3) ... Selecting previously unselected package libqt4-svg:amd64. Preparing to unpack .../libqt4-svg_4%3a4.8.7+dfsg-3_amd64.deb ... Unpacking libqt4-svg:amd64 (4:4.8.7+dfsg-3) ... Selecting previously unselected package libqt4-test:amd64. Preparing to unpack .../libqt4-test_4%3a4.8.7+dfsg-3_amd64.deb ... Unpacking libqt4-test:amd64 (4:4.8.7+dfsg-3) ... Selecting previously unselected package qt4-linguist-tools. Preparing to unpack .../qt4-linguist-tools_4%3a4.8.7+dfsg-3_amd64.deb ... Unpacking qt4-linguist-tools (4:4.8.7+dfsg-3) ... Selecting previously unselected package qt4-qmake. Preparing to unpack .../qt4-qmake_4%3a4.8.7+dfsg-3_amd64.deb ... Unpacking qt4-qmake (4:4.8.7+dfsg-3) ... Selecting previously unselected package libqt4-dev. Preparing to unpack .../libqt4-dev_4%3a4.8.7+dfsg-3_amd64.deb ... Unpacking libqt4-dev (4:4.8.7+dfsg-3) ... Selecting previously unselected package libssh-4:amd64. Preparing to unpack .../libssh-4_0.6.3-4.1_amd64.deb ... Unpacking libssh-4:amd64 (0.6.3-4.1) ... Selecting previously unselected package zlib1g-dev:amd64. Preparing to unpack .../zlib1g-dev_1%3a1.2.8.dfsg-2+b1_amd64.deb ... Unpacking zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ... Selecting previously unselected package libssl-dev:amd64. Preparing to unpack .../libssl-dev_1.0.2d-1_amd64.deb ... Unpacking libssl-dev:amd64 (1.0.2d-1) ... Selecting previously unselected package libssh-dev. Preparing to unpack .../libssh-dev_0.6.3-4.1_amd64.deb ... Unpacking libssh-dev (0.6.3-4.1) ... Selecting previously unselected package xorg-sgml-doctools. Preparing to unpack .../xorg-sgml-doctools_1%3a1.11-1_all.deb ... Unpacking xorg-sgml-doctools (1:1.11-1) ... Selecting previously unselected package x11proto-core-dev. Preparing to unpack .../x11proto-core-dev_7.0.27-1_all.deb ... Unpacking x11proto-core-dev (7.0.27-1) ... Selecting previously unselected package libxau-dev:amd64. Preparing to unpack .../libxau-dev_1%3a1.0.8-1_amd64.deb ... Unpacking libxau-dev:amd64 (1:1.0.8-1) ... Selecting previously unselected package libxdmcp-dev:amd64. Preparing to unpack .../libxdmcp-dev_1%3a1.1.2-1_amd64.deb ... Unpacking libxdmcp-dev:amd64 (1:1.1.2-1) ... Selecting previously unselected package x11proto-input-dev. Preparing to unpack .../x11proto-input-dev_2.3.1-1_all.deb ... Unpacking x11proto-input-dev (2.3.1-1) ... Selecting previously unselected package x11proto-kb-dev. Preparing to unpack .../x11proto-kb-dev_1.0.6-2_all.deb ... Unpacking x11proto-kb-dev (1.0.6-2) ... Selecting previously unselected package xtrans-dev. Preparing to unpack .../xtrans-dev_1.3.5-1_all.deb ... Unpacking xtrans-dev (1.3.5-1) ... Selecting previously unselected package libxcb1-dev:amd64. Preparing to unpack .../libxcb1-dev_1.10-3+b1_amd64.deb ... Unpacking libxcb1-dev:amd64 (1.10-3+b1) ... Selecting previously unselected package libx11-dev:amd64. Preparing to unpack .../libx11-dev_2%3a1.6.3-1_amd64.deb ... Unpacking libx11-dev:amd64 (2:1.6.3-1) ... Selecting previously unselected package libxpm-dev:amd64. Preparing to unpack .../libxpm-dev_1%3a3.5.11-1+b1_amd64.deb ... Unpacking libxpm-dev:amd64 (1:3.5.11-1+b1) ... Selecting previously unselected package man2html-base. Preparing to unpack .../man2html-base_1.6g-7_amd64.deb ... Unpacking man2html-base (1.6g-7) ... Selecting previously unselected package libldap2-dev:amd64. Preparing to unpack .../libldap2-dev_2.4.41+dfsg-1_amd64.deb ... Unpacking libldap2-dev:amd64 (2.4.41+dfsg-1) ... Processing triggers for man-db (2.7.0.2-5) ... Processing triggers for systemd (220-4) ... Setting up libitm1:amd64 (5.2.1-15) ... Setting up liblsan0:amd64 (5.2.1-15) ... Setting up libtsan0:amd64 (5.2.1-15) ... Setting up libubsan0:amd64 (5.2.1-15) ... Setting up libcilkrts5:amd64 (5.2.1-15) ... Setting up libatomic1:amd64 (5.2.1-15) ... Setting up libgomp1:amd64 (5.2.1-15) ... Setting up libasprintf0v5:amd64 (0.19.5.1-1) ... Setting up libkeyutils1:amd64 (1.5.9-5+b1) ... Setting up libsasl2-modules-db:amd64 (2.1.26.dfsg1-13) ... Setting up libsasl2-2:amd64 (2.1.26.dfsg1-13) ... Setting up libldap-2.4-2:amd64 (2.4.41+dfsg-1) ... Setting up libmagic1:amd64 (1:5.22+15-2) ... Setting up libxml2:amd64 (2.9.2+dfsg1-3) ... Setting up libexpat1:amd64 (2.1.0-7) ... Setting up libpng12-0:amd64 (1.2.50-2+b2) ... Setting up libfreetype6:amd64 (2.5.2-4) ... Setting up ucf (3.0030) ... Setting up fonts-dejavu-core (2.35-1) ... Setting up fontconfig-config (2.11.0-6.3) ... Setting up libfontconfig1:amd64 (2.11.0-6.3) ... Setting up fontconfig (2.11.0-6.3) ... Regenerating fonts cache... done. Setting up libxau6:amd64 (1:1.0.8-1) ... Setting up x11-common (1:7.7+9) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults [....] Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix[?25l[?1c7[1G[[32m ok [39;49m8[?25h[?0c. Setting up libice6:amd64 (2:1.0.9-1+b1) ... Setting up libsm6:amd64 (2:1.2.2-1+b1) ... Setting up libxdmcp6:amd64 (1:1.1.2-1) ... Setting up libxcb1:amd64 (1.10-3+b1) ... Setting up libx11-data (2:1.6.3-1) ... Setting up libx11-6:amd64 (2:1.6.3-1) ... Setting up libxt6:amd64 (1:1.1.4-1+b1) ... Setting up libaudio2:amd64 (1.9.4-3) ... Setting up libavahi-common-data:amd64 (0.6.31-5) ... Setting up libavahi-common3:amd64 (0.6.31-5) ... Setting up libdbus-1-3:amd64 (1.8.20-1) ... Setting up libavahi-client3:amd64 (0.6.31-5) ... Setting up libglib2.0-0:amd64 (2.44.1-1.1) ... No schema files found: doing nothing. Setting up libcroco3:amd64 (0.6.8-3+b1) ... Setting up liblcms2-2:amd64 (2.6-3+b3) ... Setting up libjpeg62-turbo:amd64 (1:1.4.1-1) ... Setting up libmng1:amd64 (1.0.10+dfsg-3.1+b3) ... Setting up libunistring0:amd64 (0.9.3-5.2+b1) ... Setting up libxext6:amd64 (2:1.3.3-1) ... Setting up libxpm4:amd64 (1:3.5.11-1+b1) ... Setting up libxrender1:amd64 (1:0.9.8-1+b1) ... Setting up libjbig0:amd64 (2.1-3.1) ... Setting up libssl1.0.0:amd64 (1.0.2d-1) ... Setting up file (1:5.22+15-2) ... Setting up gettext-base (0.19.5.1-1) ... Setting up libkrb5support0:amd64 (1.13.2+dfsg-2) ... Setting up libk5crypto3:amd64 (1.13.2+dfsg-2) ... Setting up libkrb5-3:amd64 (1.13.2+dfsg-2) ... Setting up libgssapi-krb5-2:amd64 (1.13.2+dfsg-2) ... Setting up gettext (0.19.5.1-1) ... Setting up intltool-debian (0.35.0+20060710.2) ... Setting up po-debconf (1.0.18) ... Setting up debhelper (9.20150628) ... Setting up libcups2:amd64 (2.0.3-10) ... Setting up libcups2-dev:amd64 (2.0.3-10) ... Setting up libpthread-stubs0-dev:amd64 (0.3-4) ... Setting up qtcore4-l10n (4:4.8.7+dfsg-3) ... Setting up libqtcore4:amd64 (4:4.8.7+dfsg-3) ... Setting up libqt4-xml:amd64 (4:4.8.7+dfsg-3) ... Setting up libqtdbus4:amd64 (4:4.8.7+dfsg-3) ... Setting up qtchooser (52-gae5eeef-2) ... Setting up qdbus (4:4.8.7+dfsg-3) ... Setting up libqt4-dbus:amd64 (4:4.8.7+dfsg-3) ... Setting up libqt4-network:amd64 (4:4.8.7+dfsg-3) ... Setting up libqt4-script:amd64 (4:4.8.7+dfsg-3) ... Setting up libqt4-sql:amd64 (4:4.8.7+dfsg-3) ... Setting up libqt4-xmlpatterns:amd64 (4:4.8.7+dfsg-3) ... Setting up libtiff5:amd64 (4.0.3-13) ... Setting up libqtgui4:amd64 (4:4.8.7+dfsg-3) ... Setting up libqt4-declarative:amd64 (4:4.8.7+dfsg-3) ... Setting up libqt4-designer:amd64 (4:4.8.7+dfsg-3) ... Setting up libqt4-qt3support:amd64 (4:4.8.7+dfsg-3) ... Setting up libqt4-dev-bin (4:4.8.7+dfsg-3) ... Setting up libqt4-help:amd64 (4:4.8.7+dfsg-3) ... Setting up libqt4-scripttools:amd64 (4:4.8.7+dfsg-3) ... Setting up libqt4-svg:amd64 (4:4.8.7+dfsg-3) ... Setting up libqt4-test:amd64 (4:4.8.7+dfsg-3) ... Setting up qt4-linguist-tools (4:4.8.7+dfsg-3) ... Setting up qt4-qmake (4:4.8.7+dfsg-3) ... Setting up libqt4-dev (4:4.8.7+dfsg-3) ... Setting up libssh-4:amd64 (0.6.3-4.1) ... Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ... Setting up libssl-dev:amd64 (1.0.2d-1) ... Setting up libssh-dev (0.6.3-4.1) ... Setting up xorg-sgml-doctools (1:1.11-1) ... Setting up x11proto-core-dev (7.0.27-1) ... Setting up libxau-dev:amd64 (1:1.0.8-1) ... Setting up libxdmcp-dev:amd64 (1:1.1.2-1) ... Setting up x11proto-input-dev (2.3.1-1) ... Setting up x11proto-kb-dev (1.0.6-2) ... Setting up xtrans-dev (1.3.5-1) ... Setting up libxcb1-dev:amd64 (1.10-3+b1) ... Setting up libx11-dev:amd64 (2:1.6.3-1) ... Setting up libxpm-dev:amd64 (1:3.5.11-1+b1) ... Setting up man2html-base (1.6g-7) ... Setting up libldap2-dev:amd64 (2.4.41+dfsg-1) ... Processing triggers for libc-bin (2.19-18) ... Processing triggers for systemd (220-4) ... [ 0%] Reading package lists [ 0%] Building dependency tree [100%] Building dependency tree [ 0%] Reading state information [ 76%] Reading state information [ 0%] Reading extended state information [ 0%] Initializing package states [ 0%] Writing extended state information [ 0%] Reading task descriptions [ 0%] Building tag database Current status: 0 broken [-1], 90 updates [-19]. -> Finished parsing the build-deps dpkg-source: warning: extracting unsigned source package (x2goclient_4.0.5.1-0x2go1~git20150812.1114+sid.heuler.1.dsc) dpkg-source: info: extracting x2goclient in x2goclient-4.0.5.1 dpkg-source: info: unpacking x2goclient_4.0.5.1-0x2go1~git20150812.1114+sid.heuler.1.tar.gz -> Building the package dpkg-buildpackage: source package x2goclient dpkg-buildpackage: source version 4.0.5.1-0x2go1~git20150812.1114+sid.heuler.1 dpkg-buildpackage: source distribution unstable dpkg-buildpackage: source changed by Jenkins <jenkins(a)japsand.x2go.org> sh: 1: gcc: not found dpkg-architecture: warning: couldn't determine gcc system type, falling back to default (native compilation) dpkg-buildpackage: host architecture amd64 dpkg-source --before-build x2goclient-4.0.5.1 dpkg-checkbuilddeps: Unmet build dependencies: build-essential:native dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting dpkg-buildpackage: warning: (Use -d flag to override.) -> received termination message from inside qemu with exit-code 0, killing child process (qemu:14077) -> successfully killed qemu forking: mount -o loop /var/cache/pbuilder/build//qemu.13883.dev /var/cache/pbuilder/build//qemu.13883 -> running post-run process running host command: cp -p "/var/cache/pbuilder/build//qemu.13883"/*_* "/home/_jenkins_/pkg-dist/heuler/x2goclient/debian/sid/amd64" 2>/dev/null || true forking: umount /var/cache/pbuilder/build//qemu.13883 -> clean up COW device files + '[' yes = yes ']' + unset DEBSIGN_PARAM + '[' -n F4A7678C9C6B0B2B ']' + DEBSIGN_PARAM[1]=-kF4A7678C9C6B0B2B + DEBSIGN_PARAM[2]=/home/_jenkins_/pkg-dist/heuler/x2goclient/debian/sid/amd64/x2goclient_4.0.5.1-0x2go1~git20150812.1114+sid.heuler.1_amd64.changes + debsign -kF4A7678C9C6B0B2B /home/_jenkins_/pkg-dist/heuler/x2goclient/debian/sid/amd64/x2goclient_4.0.5.1-0x2go1~git20150812.1114+sid.heuler.1_amd64.changes debsign: Can't find or can't read changes file /home/_jenkins_/pkg-dist/heuler/x2goclient/debian/sid/amd64/x2goclient_4.0.5.1-0x2go1~git20150812.1114+sid.heuler.1_amd64.changes! + cleanup + typeset temp_dir= + for temp_dir in '"${temp_cleanup[@]}"' + '[' -n '' ']' + for temp_dir in '"${temp_cleanup[@]}"' + '[' -n /var/lib/jenkins/tmp/tmp.QbUXMOSLKcfZhOy0BYFd8m64 ']' + '[' -d /var/lib/jenkins/tmp/tmp.QbUXMOSLKcfZhOy0BYFd8m64 ']' + rm -Rf -- /var/lib/jenkins/tmp/tmp.QbUXMOSLKcfZhOy0BYFd8m64 Build step 'Execute shell' marked build as failure

1 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

x2go-commits August 2015