[X2Go-Dev] Bug#919: Bug#919: Windows 10 and Gnome Desktop
Please try disabling audio for the session. There is a known issue with x2go client for windows whereby if microphone input is unavailable, pulseaudio.exe constantly restarts. This causes numerous apps / shells on the Linux Desktop (even ones you wouldn't expect to use audio) to hang. --Mike#2 Sent from my Android Smartphone ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#883: Fixed
Control: fixed -1 4.0.5.0 Now that the aforementioned changes have been made to both x2goclient.git and to VcXsrv (X2Go/Arctica Builds), the fix will be included in the next release of x2goclient. Due to the potential for regressions from this fix, as well as the disruptive nature of the fix for #696, the next release of x2goclient will be 4.0.5.0 instead of 4.0.4.1. ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Cross-Compiling X2Go Client for Windows
Hi Heinz, At the X2Go Gathering 2015, I gave a talk on X2Go Client for Windows development: https://docs.google.com/presentation/d/1GxTHN4AiSRLtfbiQqRycMjrAn3OL_xWk0x3_p-Nop2k/edit?usp=sharing Although many components such as nxproxy have to be built with separate build systems and thus will have to be built manually, I would like there to be a more reproducible way to build X2Go Client itself (x2goclient.git - x2goclient.exe x2gohelper.exe). I love tools like pbuilder and mock for Linux. 2 possible solutions for this (cross-compilation environments) that look promising are: http://mxe.cc http://win-builds.org However, I think Mike#1 said that you told him there was a need to build X2Go Client for Windows via a Windows machine (the WinBuilder VM) rather than a cross-compilation environment. Can you explain the reason for that? Note that I am frequently updating this page: http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient I see 4 potential obstacles to using a cross-compilation environment: 1. We configure Qt for static builds (the Qt libraries are included withing x2goclient.exe): http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient#configuring_qt However, I doubt there is a need to configure Qt for static builds. If we have to distribute some Qt DLLs, so be it., Note that OpenSSL support in Qt should not be a problem; it is safe to assume that all the cross-compilation environments support that. 2. We have to use a version of libssh that is patched for Pageant support (upstream libssh wants to do redesign how they handle SSH agents before they accept the patch): http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient#installing_libssh 3. We would need to package libraries for the cross-compilation environments. For example, MXE lacks libssh. 4. At the end of the build, we need to combine all the 3rd party components (built with separate build systems) into the NSIS installer. This should be feasible though; MXE supports NSIS for example. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] Bug#883: Bug#883: Bug#883: Can be fixed by reverting winmultiwindow.patch
Hi Alex, I spoke with Jon Turney (jturney), the Cygwin XWin maintainer on #cygwin on Freenode. I also tested some options. It sounds like the best approach to making a full screen secondary monitor work is to launch VcXsrv (or Cygwin XWin) with these arguments: -nodecoration -screen 0 @2 For tertiary monitor, use @3 instead. This launches Cygwin XWin in root window mode (the default) rather than -multiwindow mode. -nodecoration hides the window decoration from the Windows OS. Can you please test this out and see if it meets your needs? If so, it should be a simple change to x2goclient to launch VcXsrv this way. Also, FYI: It is true that if you launch Cygwin XWin or VcXsrv in fullscreen mode, then it will always use the primary display, even when you tell it to use the secondary: -fullscreen -screen 0 @2 However, by telling either X server to use its older rendering engine, you can solve this problem: -fullscreen -engine 1 -screen 0 @2 I do not recommend this approach for x2goclient though because if you click out of the X server, then the X server minimizes. Note: these are the engines: -engine engine_type_id Override the server's automatically selected engine type: 1 - Shadow GDI 2 - Shadow DirectDraw - obsolete 4 - Shadow DirectDraw4 Non-Locking Engine 4 is the default. Engine 2 is not available on VcXsrv. Jon acknowledges that there is a secondary monitor limitation/bug with Engine 4. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] Bug#891: I have a fix for VcXsrv, but it needs discussion
On Sun, Jun 28, 2015 at 5:10 AM, Stefan Baur x2go-m...@baur-itcs.de wrote: Am 28.06.2015 um 02:54 schrieb Michael DePaulo: However, If I release X2Go Client 4.0.4.1 (or an update to 4.0.4.0) with this fix, then sessions started on X2Go Client for Windows 4.0.4.0-2015.06.24 and earlier can not be resumed on the new version. This could be very disruptive to users. Does anyone have any thoughts on this dilemma? Don't we have the x.x.x.x versioning scheme for such reasons? Bump the version number up in a position that indicates things may break and all should be good, no? I have asked people but I have never seen an official answer on what our 4 digit versioning scheme means exactly. I was under the impression that for A.B.C.D, it means this: A - Major version with compatibility implications. As an example of a compatibility implication, X2Go Server 4.x cannot accept connections from X2Go Client 3.x unless x2goserver-compat is installed. B - Major version without compatibility implications. C - Minor version D - Micro version (patch level) I am also under the impression that a bump in A, B or C means that things may break, but not in D. Therefore, the 1st version of X2Go Client for Windows with this change will be 4.0.5.0. We might release 4.0.4.1 before then, but it won't have the change. Or could you create a patch that allows toggling between the two modes of operation, and when the first reconnect fails, try it with the other mode? That's a good idea. I will need to add an option to VcXsrv like -[no]limitwglcolors, but that should be easy. I will look into this. - -Stefan [...] -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] My slides and related files from X2Go Gathering 2015
XSession, Polkit, and making apps “just work” https://docs.google.com/presentation/d/1EXx13YXzQcLQRXdQWthgo2xjqkLxbsiBDdVa78-o4Tc/edit?usp=sharing Related files: https://drive.google.com/folderview?id=0B2L_OrCln9ShM1NyQzktNHkyTmcusp=sharing X2Go Client for Windows Development (40 minutes): https://docs.google.com/presentation/d/1GxTHN4AiSRLtfbiQqRycMjrAn3OL_xWk0x3_p-Nop2k/edit?usp=sharing Windows X server benchmarks other related files: https://drive.google.com/folderview?id=0B2L_OrCln9ShflN1c1BPZF9aTkh3NkF1QklmV2tOMWRfMGxod3lsZ2pQWmVkb3pLMjhMUXMusp=sharing In the case of the latter presentation, I made some small corrections and added some info. You can view the versions from 2015-06-21 if you want to see exactly what I presented. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#896: Session Resume Fails with Failed to restore all the required visuals.
Package: x2goclient Version: 4.0.4.0 Severity: normal Tags: +build-win32 Sometimes when starting an X2Go session on a Windows client, and resuming it on a different machine (which may or may not be Windows), the session fails to resume and you get this error message: X2Go - 50 Failed to restore all the required visuals. Can't resume the NX session on this display. Screenshot: http://imgur.com/zQz69Cz On test configuration #1 at least, I am still able to resume the session on the original client, even after receiving the error on the new client. I have seen this issue occasionally over the last year or 2. I recall experiencing it when try resume a session over RDP. However, I have 2 other test configurations listed below. Note that the error message comes from nx-libs, not x2goclient. x2goclient passes the error message to the user. However, I am filing this bug under x2goclient since it is likely possible to fix it by launching VcXsrv on Windows with different options. In fact, at X2Go Gathering 2015, one of the QVD developers said that they experienced this issue with QVD client for iOS, and fixed it by launching their client-side X server with certain options: https://github.com/theqvd/qvd-client-ios/blob/master/QVDWrapper/wrapper/Services/QVDXvncService.m#L106 Right now I am able to reproduce it with this test configuration (#1): Server OS: Fedora 21 64-bit with latest updates x2goserver: 4.0.1.19-3.fc21 (from Fedora) x2goserver-xsession: 4.0.1.19-3.fc21 (from Fedora) nxagent: 3.5.0.31-0.0x2go1.1.git20150608.671.main.fc21 session-starting client OS: Windows 10 64-bit build 10130 session-starting x2goclient: 4.0.4.0-2015.06.24 session-starting hardware: physical, accessed locally session-resuming client OS: Windows XP 32-bit SP3 with last available updates session-resuming x2goclient: 4.0.4.0-2015.06.24 session-resuming hardware: Virtual. Running on the server's qemu-kvm hypervisor with virt-manager. QXL SPICE are used (the SPICE server is built into the hypervisor.) Driver is Red Hat QXL GPU 7/17/2013 5.1.0.10018. Color is set to 32-bit. Accessed over virt-viewer 2.0 from Windows. Also, at the X2Go Gathering 2015, we were able to reproduce this with the following 2 clients (but with a different server) (test config #2): Server Details: unknown session-starting client OS: Windows 7 64-bit SP1 with latest updated session-starting x2goclient: 4.0.4.0-2015.06.24 session-starting hardware: physical, accessed locally session-resuming client OS: X2Go TCE (version unknown) (based on Debian 7 Wheezy IIRC) session-resuming x2goclient: version unknown session-resuming hardware: physical, accessed locally ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#883: I will try Mike#1's suggestions, and I released the test build
Hi Mike#1, I will try your suggestions. Also, everyone, I just released X2Go Client for Windows 4.0.4.0-2015.06.24 instead of 4.0.4.0-2015.06.22 (because I did the build 1.5 days later.) The alternate build with the test fix (reverting the winmultiwindow.patch) is available: http://code.x2go.org/releases/binary-win32/x2goclient/releases/4.0.4.0-2015.06.24/non-default-builds/x2goclient-4.0.4.0-2015.06.24-bug883test1-setup.exe -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] [X2Go-User] Japsand Maintenance Aftermath a.k.a. Lessons Learned
Right now, I am able to connect to japsand fine. 1. That wiki URL loads successfully. 2. I connected to an LXDE X2Go session (only X2Go developers have access.) 3. I connected to an rdesktop session to the WinBuilder VM (although someone else was already logged in, so I canceled.) -Mike#2 On Wed, Jun 24, 2015 at 5:56 PM, Robert Dinse nan...@eskimo.com wrote: It would seem the Wiki is still down, when I try to go to: http://wiki.x2go.org/doku.php/doc:usage:pyhoca-gui I get cannot connect to server. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Wed, 24 Jun 2015, Mihai Moldovan wrote: Date: Wed, 24 Jun 2015 23:25:33 +0200 From: Mihai Moldovan io...@ionic.de Reply-To: x2go-u...@lists.x2go.org x2go-u...@lists.x2go.org To: x2go-proj...@lists.x2go.org x2go-proj...@lists.x2go.org, x2go-dev@lists.x2go.org x2go-dev@lists.x2go.org, x2go-u...@lists.x2go.org x2go-u...@lists.x2go.org Subject: [X2Go-User] Japsand Maintenance Aftermath a.k.a. Lessons Learned Hi Due to a hanging rm process, we had to restart the server today. After rebooting the machine, it was decided to also update the system to the latest packages version, but still staying on Debian Wheezy (for now.) The server is using a custom kernel module provided by Realtek for its RTL8168 ethernet NIC. An in-kernel driver is available, but proved to be too unreliable, leading to frequent network outages and even machine crashes whenever the network IO load was higher than a few hundred KB/s. The hosting provider has a wiki entry for this issue at this location: http://wiki.hetzner.de/index.php/Installation_des_r8168-Treibers/en Unfortunately, the current driver version as provided by Realtek, 8.040, seems to be incompatible with the old 3.2.0-4-amd64 (3.2.68-1+deb7u2) kernel provided by Debian. As of writing this, I do not know what happened exactly, but most likely the module caused a kernel panic during bootup. Reverting to an older version, 8.037, fixed this issue and let the server boot up correctly again. For future maintenance work, please use this older version, at least on Debian Wheezy. I put the module source code into /usr/src and created a symlink from /usr/src/r8168-current to /usr/src/r8168-8.037.00. --- Other updated packages include Java (version 7 co-installed, the alternatives symlink now point to version 7 instead of 6) and Jenkins, including its plugins. A test build run suggests the Jenkins update was successful. Mihai ___ x2go-user mailing list x2go-u...@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#883: Regression in VcXsrv
As I discussed with Stefan Mihai at X2Go Gathering 2015: 1. VcXsrv 1.1.2 is not affected, so this appears to be a regression in VcXsrv. 2. It is safe to assume that it is a regression in the multiwindow code in VcXsrv (and in other X servers for Windows), xorg-server/hw/xwin/winmultiwindow* 3. We should bisect released versions/builds of VcXsrv until we find which version was 1st affected, and then compare their source code in the aforementioned area to find what change probably caused the regression. If need be, we will build old git revisions in between those released versions. 4. I have started doing #3 and recording the results in this spreadsheet: https://docs.google.com/spreadsheets/d/1cVe7UELbJqLEFsE20v1-weUWyW-pQByTAkeUOIPs-uw/edit?usp=sharing -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#884: Bug#884: Bug#884: nxagent aborts session with 'Could not open default font 'fixed''
A quick look at some distros where nxagent works.
Out of the 5 dirs listed:
Ubuntu 14.04 contains:
/usr/share/fonts/ (no misc under it)
/usr/share/fonts/X11/misc/
RHEL 7.1 contains:
/usr/share/fonts/ (no misc under it)
/usr/share/X11/fonts/misc/
On Tue, Jun 2, 2015 at 12:21 PM, devsk internet_every...@yahoo.com wrote:
The folder /usr/X11R6 hasn't existed on Gentoo for years now (since move to
Xorg). Does the folder /usr/X11R6/lib/X11/fonts exist on other distros?
Also, the code seems to be making an attempt to look for ALTERNATE font
paths and many of those paths are there:
$ ls -al /usr/share/fonts/*/fonts.{alias,dir}
-rw-r--r-- 1 root root 3154 Apr 11 08:16 /usr/share/fonts/100dpi/fonts.alias
-rw-r--r-- 1 root root 17828 Jun 2 07:14 /usr/share/fonts/100dpi/fonts.dir
-rw-r--r-- 1 root root 3066 Apr 11 08:16 /usr/share/fonts/75dpi/fonts.alias
-rw-r--r-- 1 root root 17280 Jun 2 07:15 /usr/share/fonts/75dpi/fonts.dir
-rw-r--r-- 1 root root 2000 Jun 2 07:12 /usr/share/fonts/OTF/fonts.dir
-rw-r--r-- 1 root root 1689 Jun 2 07:14 /usr/share/fonts/Speedo/fonts.dir
-rw-r--r-- 1 root root 10298 Jun 2 07:10 /usr/share/fonts/TTF/fonts.dir
-rw-r--r-- 1 root root 13319 Jun 2 07:15 /usr/share/fonts/Type1/fonts.dir
-rw-r--r-- 1 root root 44001 Apr 11 08:07 /usr/share/fonts/corefonts/fonts.dir
-rw-r--r-- 1 root root 21736 Apr 10 17:51
/usr/share/fonts/croscorefonts/fonts.dir
-rw-r--r-- 1 root root 3234 Apr 11 08:16
/usr/share/fonts/cyrillic/fonts.alias
-rw-r--r-- 1 root root 6005 Jun 2 07:15 /usr/share/fonts/cyrillic/fonts.dir
-rw-r--r-- 1 root root 43905 Apr 10 17:51 /usr/share/fonts/dejavu/fonts.dir
-rw-r--r-- 1 root root 26289 Apr 11 08:07
/usr/share/fonts/liberation-fonts/fonts.dir
-rw-r--r-- 1 root root 16664 Apr 11 08:08 /usr/share/fonts/libertine/fonts.dir
-rw-r--r-- 1 root root 6209 Apr 11 08:16 /usr/share/fonts/misc/fonts.alias
-rw-r--r-- 1 root root 6721 Jun 2 07:15 /usr/share/fonts/misc/fonts.dir
-rw-r--r-- 1 root root 31892 Apr 11 08:07 /usr/share/fonts/roboto/fonts.dir
-rw-r--r-- 1 root root 5053 Apr 11 08:08
/usr/share/fonts/ttf-bitstream-vera/fonts.dir
-rw-r--r-- 1 root root 43334 Apr 10 17:51 /usr/share/fonts/urw-fonts/fonts.dir
-devsk
On Tuesday, June 2, 2015 9:13 AM, Mike Gabriel
mike.gabr...@das-netzwerkteam.de wrote:
On Di 02 Jun 2015 17:49:24 CEST, devsk wrote:
Hi,
As per suggestion I built the code from
https://github.com/ArcticaProject/nx-libs. And I still run into the
same issue.
Does anybody here know that part of the code (snippet in the report)?
Please take a look at [1] and make sure either of those paths exists
on your system.
You need the fixed fonts in the misc/ fontdir.
Is everything in place there?
Mike
[1]
https://github.com/ArcticaProject/nx-libs/blob/3.6.x/nx-X11/programs/Xserver/hw/nxagent/Font.c#L64
--
DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-dev
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] X2Go support in Q4OS
On Fri, May 29, 2015 at 3:33 AM, Q4OS Team i...@q4os.org wrote: Hi Mike, Mihai, On 05/29/2015 04:31 AM, Michael DePaulo wrote: Hi Pete, On Thu, May 28, 2015 at 9:51 PM, Mihai Moldovan io...@ionic.de wrote: [...] As long as the required (X2Go) packages are available on Q4OS, it should be working out of the box with Trinity. Unfortunately no, Q4OS needs to set env and take some tasks before launch a session. This is what our script does, see below. What is /usr/bin/start-q4os-x2go supposed to do? This is small dash compatible script, it takes some Q4OS specific tasks, set Q4OS environment and then launches default Trinity 'starttde' script. We can also modify the behavior of x2goserver to launch /usr/bin/start-q4os-x2go supposed if the user selects TRINITY in x2goclient Both methods look nice. I suppose the best way to detect Q4OS is to simply check /usr/bin/start-q4os-x2go to exist. Pete I just made a commit to x2goserver on both the release/4.0.1.x branch (which will become 4.0.1.20) and the master branch (which will become 4.1.0.0) to do that: release/4.0.1.x: http://code.x2go.org/gitweb?p=x2goserver.git;a=commit;h=c8cee419bca5126323ab7d8a86f22254a7564c8b master: http://code.x2go.org/gitweb?p=x2goserver.git;a=commit;h=9ec47ce0dfe7a9d4895dd0a6c8f2412603ff3b60 BTW, how does Q4OS install X2Go exactly? I downloaded the Q4OS 1.2.2 x64 iso. I don't see any x2goserver package, but I do see x2go-keyring_2011.12.07+wheezy~baikal~12~build1_all.deb . If Q4OS is accessing the baikal apt repo under http://packages.x2go.org/debian/ , then that is a problem because baikal provides x2goserver 4.0.0.x, which does not support trinity. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] X2Go support in Q4OS
On Fri, May 29, 2015 at 10:33 AM, Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: On Fr 29 Mai 2015 15:55:06 CEST, Ulrich Sibiller wrote: On Fri, May 29, 2015 at 3:39 PM, Q4OS Team i...@q4os.org wrote: Pretty quick, thanks .. the most preferred way to install X2Go Server in Q4OS is to use specific installer from 'Software Centre'. It will add debian-baikal repos and install X2Go Server from. We instructs our customers to set 'start-q4os-x2go' as 'Custom' command in Session preferences in X2Go Client now. It works perfectly for Trinity/Q4OS. So the new feature could be accessible for most Q4OS users after transition into the new Server's branch, when baikal lifetime cycle will finish. What about a directory (e.g. /etc/x2go/distsessions.d) where distributions can add additional session type files. This way any distribution / desktop environment can simply add their session without having to ask anyone for inclusion in the x2go packages. Uli Because unlike Thinlinc for example, the user selects the session type in X2Go Client before connecting, not after connecting. This would work, but it would require the user to manually type in the session type unless it is an already listed session type in X2Go Client. It would be very useful for letting system administrators override the session command though. Reportedly, FreeNX supports overrides via a file under /etc/. Why not do it the freedesktop.org way finally /usr/share/xsessions/*.desktop ? Of course, it may come in handy to have a second location, that is X2Go specific: /usr/share/x2gosessions/*.desktop I've been thinking about this lately. X2Go often must launch a different command than what the local display server must launch. The best example is that gnome flashback under X2Go needs gnome-session to be launched with --disable-acceleration-check. This applies to gnome-session 3.16 or later[1], or gnome-session 3.8 in ubuntu 14.04 with the latest update applied.[2] (I am about to write a fix for x2goserver to accommodate gnome flashback in Ubuntu 14.04. I will send a separate email about this.) So yes, we could do this, but we need /usr/share/x2gosessions/foo.desktop to take precedence over /usr/share/xsessions/foo.desktop . [1] https://bugzilla.gnome.org/show_bug.cgi?id=731173 [2] https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1251281 Or more generic: /usr/share/xsessions-remote/*.desktop Mike That's a valid point. We should discuss with FreeDesktop.org though. -Mike ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] X2Go support in Q4OS
Hi Pete, On Thu, May 28, 2015 at 9:51 PM, Mihai Moldovan io...@ionic.de wrote: Hi Pete On 27.05.2015 10:10 AM, Q4OS Team wrote: we are developing Q4OS distribution based on Trinity DE. We want to support the great X2Go product in our distro as perfect as possible, I would like to ask you, if it would be possible to add Q4OS item into X2Go Client 'session type' combobox. I don't know exactly the background, but suppose to add our startup session script '/usr/bin/start-q4os-x2go' into the Client source code. Generally possible, sure. But Q4OS is supposed to be using Trinity, right? So you'd really be interested in a Trinity menu entry. This one does already exist. What is /usr/bin/start-q4os-x2go supposed to do? As long as the required (X2Go) packages are available on Q4OS, it should be working out of the box with Trinity and I don't see any reason to add another menu entry just for Q4OS. Unless I'm missing something? Mihai In addition to what Mihai said, we can also modify the behavior of x2goserver to launch /usr/bin/start-q4os-x2go supposed if the user selects TRINITY in x2goclient, but x2goserver detects that it is running on Q4OS. We are already launching different GNOME and UNITY commands depending upon what Linux distro you are using. This is the x2goruncommand bash script in x2goserver 4.0.1.19. Our lines for launching trinity are 197 198. Our lines for launching GNOME or Unity are 93 through 167 (including comments whitespace). You don't need to read through all those lines; just note that we have flexibility in x2goserver. http://code.x2go.org/gitweb?p=x2goserver.git;a=blob;f=x2goserver/bin/x2goruncommand;h=e7e20e2b9433c1ec59cb300b3e43997f9152bb4d;hb=8a494e794402c1b124d861893d649726a9016eb7 -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#870: SSH_VERSION macro
Although this appears to be a bug in libssh, we should probably add #ifdefs in our code for libssh 0.7.0 or later. From #libssh on FreeNode: gladiac mikedep333: you can use SSH_VERSION macro to detect the libssh version ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#765: More Info
There are multiple ways to reproduce this bug. For example: 1. Let the server and x2goclient exchange an ecdsa key. Configure the server to only use rsa keys. Then attempt to connect with x2goclient. (This is what happened in the original bug report.) (This will happen when someone configures a server for FIPS compliance.) (Note that if both an rsa key and an ecdsa key are available, an ecdsa key will be exchanged.) 2. Let the server and x2goclient exchange an rsa key. Configure the server to only use ecdsa keys. Then attempt to connect with x2goclient. (This will produce the inverse error message.) 3. Let the server and x2goclient exchange an ecdsa key. Replace that key with an ecdsa key of a different length. Then attempt to connect with x2goclient. What will not reproduce this bug is configuring a server to only use rsa keys, and then connecting with x2goclient for the 1st time. (Which will exchange an rsa key.) ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#870: looks like libssh 0.7.0 is the culprit
Control: reassign -1 x2goclient Control: found -1 4.0.4.0 Control: found -1 4.0.3.2 I am getting a similar error when I attempting to build the x2goclient master branch (which will become 4.0.4.0 ) against libssh 0.7.0 on Windows. ./release\sshmasterconnection.o:sshmasterconnection.cpp:(.text+0x30ac): undefined reference to `_imp__ssh_forward_listen' Andrey, you installed this Fedora Testing update for libssh, right? 0.6.4-1.fc22 - 0.7.0-1.fc22 C:\x2gobuilds\x2goclient\client_buildmingw32-make -j4 mingw32-make -f Makefile.Release mingw32-make[1]: Entering directory 'C:/x2gobuilds/x2goclient/client_build' c:\Qt\4.8.6\bin\lrelease.exe ..\res\i18n\x2goclient_de.ts c:\Qt\4.8.6\bin\lrelease.exe ..\res\i18n\x2goclient_da.ts Updating '..\res\i18n\x2goclient_de.qm'... c:\Qt\4.8.6\bin\lrelease.exe ..\res\i18n\x2goclient_es.ts Generated 568 translation(s) (568 finished and 0 unfinished) Updating '..\res\i18n\x2goclient_da.qm'... Generated 568 translation(s) (568 finished and 0 unfinished) c:\Qt\4.8.6\bin\lrelease.exe ..\res\i18n\x2goclient_et.ts Updating '..\res\i18n\x2goclient_es.qm'... Generated 564 translation(s) (564 finished and 0 unfinished) Ignored 4 untranslated source text(s) c:\Qt\4.8.6\bin\lrelease.exe ..\res\i18n\x2goclient_fi.ts Updating '..\res\i18n\x2goclient_et.qm'... Generated 564 translation(s) (564 finished and 0 unfinished) Ignored 4 untranslated source text(s) c:\Qt\4.8.6\bin\lrelease.exe ..\res\i18n\x2goclient_fr.ts Updating '..\res\i18n\x2goclient_fi.qm'... Generated 568 translation(s) (568 finished and 0 unfinished) c:\Qt\4.8.6\bin\lrelease.exe ..\res\i18n\x2goclient_nb_no.ts Updating '..\res\i18n\x2goclient_fr.qm'... Generated 252 translation(s) (199 finished and 53 unfinished) Ignored 316 untranslated source text(s) c:\Qt\4.8.6\bin\lrelease.exe ..\res\i18n\x2goclient_nl.ts Updating '..\res\i18n\x2goclient_nb_no.qm'... c:\Qt\4.8.6\bin\lrelease.exe ..\res\i18n\x2goclient_pt.ts Generated 568 translation(s) (568 finished and 0 unfinished) Updating '..\res\i18n\x2goclient_nl.qm'... Generated 568 translation(s) (566 finished and 2 unfinished) c:\Qt\4.8.6\bin\lrelease.exe ..\res\i18n\x2goclient_ru.ts Warning: dropping duplicate messages in '..\res\i18n\x2goclient_pt.qm': * Context: EditConnectionDialog * Source: Session c:\Qt\4.8.6\bin\lrelease.exe ..\res\i18n\x2goclient_sv.ts UUpdating '..\res\i18n\x2goclient_pt.qm'... pdating '..\res\i18n\x2goclient_ru.qm'... Generated 0 translation(s) (0 finished and 0 unfinished) Ignored 568 untranslated source text(s) c:\Qt\4.8.6\bin\lrelease.exe ..\res\i18n\x2goclient_tr.ts Generated 554 translation(s) (545 finished and 9 unfinished) Ignored 14 untranslated source text(s) Updating '..\res\i18n\x2goclient_sv.qm'... c:\Qt\4.8.6\bin\lrelease.exe ..\res\i18n\x2goclient_zh_tw.ts Generated 568 translation(s) (568 finished and 0 unfinished) Updating '..\res\i18n\x2goclient_tr.qm'... c:\Qt\4.8.6\bin\uic.exe ..\src\ui\cupsprintsettingsdialog.ui -o ui_cupsprintsettingsdialog.h Generated 566 translation(s) (566 finished and 0 unfinished) Updating '..\res\i18n\x2goclient_zh_tw.qm'... c:\Qt\4.8.6\bin\uic.exe ..\src\ui\cupsprintwidget.ui -o ui_cupsprintwidget.h Generated 395 translation(s) (370 finished and 25 unfinished) Ignored 173 untranslated source text(s) c:\Qt\4.8.6\bin\uic.exe ..\src\ui\printdialog.ui -o ui_printdialog.h c:\Qt\4.8.6\bin\uic.exe ..\src\ui\printercmddialog.ui -o ui_printercmddialog.h c:\Qt\4.8.6\bin\uic.exe ..\src\ui\printwidget.ui -o ui_printwidget.h c:\Qt\4.8.6\bin\uic.exe ..\src\ui\xsettingsui.ui -o ui_xsettingsui.h c:\Qt\4.8.6\bin\uic.exe ..\src\ui\brokerpassdialog.ui -o ui_brokerpassdialog.h c:\Qt\4.8.6\bin\uic.exe ..\src\ui\contest.ui -o ui_contest.h c:\Qt\4.8.6\bin\uic.exe ..\src\ui\appdialog.ui -o ui_appdialog.h c:\Qt\4.8.6\bin\uic.exe ..\src\ui\helpdialog.ui -o ui_helpdialog.h c:\Qt\4.8.6\bin\uic.exe ..\src\ui\folderexplorer.ui -o ui_folderexplorer.h g++ -c -pipe -fno-keep-inline-dllexport -O2 -frtti -fexceptions -mthreads -Wall -Wextra -DUNICODE -DCFGCLIENT -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_THREAD_SUPPORT -I..\..\..\Qt\4.8.6\include\QtCore -I..\..\..\Qt\4.8.6\i nclude\QtNetwork -I..\..\..\Qt\4.8.6\include\QtGui -I..\..\..\Qt\4.8.6\include\QtSvg -I..\..\..\Qt\4.8.6\include -I..\src -I..\..\..\Qt\4.8.6\include\ActiveQt -Irelease -I. -I..\..\x2goclient -I. -I..\..\..\Qt\4.8.6\mkspecs\win32-g++-4.6 -o release\sharewidget.o ..\src\sharewidget.cpp g++ -c -pipe -fno-keep-inline-dllexport -O2 -frtti -fexceptions -mthreads -Wall -Wextra -DUNICODE -DCFGCLIENT -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_THREAD_SUPPORT -I..\..\..\Qt\4.8.6\include\QtCore -I..\..\..\Qt\4.8.6\i nclude\QtNetwork -I..\..\..\Qt\4.8.6\include\QtGui -I..\..\..\Qt\4.8.6\include\QtSvg
[X2Go-Dev] Bug#870: bug report and patch submitted to libssh
I reported the bug to libssh and submitted a patch: https://red.libssh.org/issues/194 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#864: Code for both Qt4 and Qt5
As mentioned here, code can be ported to Qt5 while retaining compatibility with Qt4: http://blog.qt.io/blog/2012/12/19/qt-5-0/ If/when we do port to Qt5, we should maintain compatibility with Qt4. For example, RHEL 7 CentOS 7 include Qt4, but not Qt5. Qt5 is available from EPEL, but EPEL makes Qt5 follow EPEL's rolling-release model. So to reduce risk to our users, we should keep the EL7 builds on Qt4. ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Fwd: libssh 0.7.0
-- Forwarded message -- From: Andreas Schneider a...@cryptomilk.org Date: Mon, May 11, 2015 at 5:24 AM Subject: libssh 0.7.0 To: lib...@libssh.org Hello, we have finally a new libssh release [1]. This version has support for ed25519 private and public keys as they are supported by OpenSSH since version 6.5. We would like to release more often but libssh is a spare time project of Aris and me. It is great that a lot of people contributed to this release! Thanks to all people who sent patches or reported bugs! We have several things on the TODO list for the next version: a) Public API for known_hosts file parsing b) All tests should run with cwrap.org libraries c) Support chacha20-poly1...@openssh.com cipher d) Support for more MACs Help is appreciated :) [1] https://www.libssh.org/2015/05/11/libssh-0-7-0/ -- Andreas Schneider GPG-ID: CC014E3D www.cryptomilk.orga...@cryptomilk.org ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#868: connection failed pscp error with folder sharing
Package: x2goclient Version: 4.0.3.2 Tags: build-win32 When the following conditions are met: 1. You are using X2Go Client for Windows 2. You are using Kerberos 5 (GSSAPI) authentication 3. Your server-side home directory is at a path other than /home/$USER Upon connecting to an X2Go server, whether you have any folders shared or not, you receive an error like: Connection failed pscp: unable to open /home/mike/.x2go/ssh/key.dK7060: no such file or directory (Connection failed is bolded) Furthermore, shared folders are not actually shared. If you attempt to share a folder after connecting, you receive the same error message. This bug appears to be a limitation of when Kerberos (GSSAPI) authentication was originally introduced in x2goclient 4.0.1.2. It was introduced in commit a77d761d on 2013-12-10. I will push a commit that fixes this bug. However, it overrides all paths like ~user with ~. In other words, it assumes that SshProcess::start_cp() will never be used to upload a file to another user's home dir, unless that other user's home dir is specified absolute. As a side note, this bug is present under the default configuration of SAMBA's winbind, which does support kerberos authentication. By default, smb.conf has set: template homedir = /home/%D/%U Where %D is the domain name, and %U is the username. ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#789: I fixed this: more info
This will be fixed in the 1st release of X2Go Client for Windows 4.0.4.0-x. The bug appeared to be caused by the fact that for at least 1 of the SSH Processes, procUuid/uuidStr is null. Thus HKEY_CURRENT_USER\\Software\\SimonTatham\\PuTTY\\Sessions would be deleted (recursively) instead of only the uuidStr subkey being deleted. I fixed it by simply adding a check to SshProcess::rmPuttyReg(). It now does nothing if uuidStr is empty or null. This is the safest solution IMHO. -Mike ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] libssh 0.6.5 has been released to address CVE-2015-3146
On Thu, Apr 30, 2015 at 11:35 AM, Michael DePaulo mikedep...@gmail.com wrote: Sent from my Android Smartphone -- Forwarded message -- From: Andreas Schneider a...@cryptomilk.org Date: Apr 30, 2015 10:33 AM Subject: libssh 0.6.5 has been released to address CVE-2015-3146 To: lib...@libssh.org Cc: ibssh versions 0.5.1 and above have a logical error in the handling of a SSH_MSG_NEWKEYS and SSH_MSG_KEXDH_REPLY package. A detected error did not set the session into the error state correctly and further processed the packet which leads to a null pointer dereference. This is the packet after the initial key exchange and doesn’t require authentication. This could be used for a Denial of Service (DoS) attack. The bug was found and reported by Mariusz Ziulek from the Open Web Application Security Project (OWASP). https://www.libssh.org/2015/04/30/libssh-0-6-5-security-and-bugfix-release/ -- Andreas Schneider GPG-ID: CC014E3D www.cryptomilk.orga...@cryptomilk.org I asked on IRC (#libssh on FreeNode) if it affects the ssh client functionality. They said it affects both server and client. I find a DoS attack on a client to be a bit odd, but I will update libssh anyway for X2Go Client for Windows 4.0.3.2-MMDD anyway. ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] improve Xinerama
On Fri, May 1, 2015 at 7:13 AM, Ulrich Sibiller ul...@gmx.de wrote: On Thu, Apr 30, 2015 at 5:18 AM, Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: IMHO, Xinerama enabled should be the default for nx-libs 3.6.x. Esp. if it does not require a xinerama.conf file anymore (i.e., an interaction by the remote session client). When X11 did the transition from 6.9 to 7.0 they did not add a single feature. Maybe the even did omit bugfixes. The only difference between those two is the source code structure and the build process. So I think all those cleanup things you are doing should not be mixed with code changes, do you? The difference is that we are moving from X.org 6.9 libraries to approximately X.org 7.7 libraries. (Whatever version the Linux distro provides.) Many new features have been added to those libraries since 6.9/7.0. So we cannot change our build system without adding new features. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Fwd: libssh 0.6.5 has been released to address CVE-2015-3146
Sent from my Android Smartphone -- Forwarded message -- From: Andreas Schneider a...@cryptomilk.org Date: Apr 30, 2015 10:33 AM Subject: libssh 0.6.5 has been released to address CVE-2015-3146 To: lib...@libssh.org Cc: ibssh versions 0.5.1 and above have a logical error in the handling of a SSH_MSG_NEWKEYS and SSH_MSG_KEXDH_REPLY package. A detected error did not set the session into the error state correctly and further processed the packet which leads to a null pointer dereference. This is the packet after the initial key exchange and doesn’t require authentication. This could be used for a Denial of Service (DoS) attack. The bug was found and reported by Mariusz Ziulek from the Open Web Application Security Project (OWASP). https://www.libssh.org/2015/04/30/libssh-0-6-5-security-and-bugfix-release/ -- Andreas Schneider GPG-ID: CC014E3D www.cryptomilk.orga...@cryptomilk.org ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] improve Xinerama
Hi Ulrich (see bottom reply), On Tue, Apr 28, 2015 at 6:46 AM, Ulrich Sibiller ul...@gmx.de wrote: Hello, I have been playing around with x2go and xinerama. While the current setup kind of works there are some problems with the current concept: - it uses LD_LIBRARY_PATH. Any software that fiddles around with LD_LIBRARY_PATH can break it (and there a lot (mostly commercial) programs doing that...) - it does not fully work on mixed architecture setups (32/64bit mix) because there's only one library in the distribution. (I haven't tested this but it AFAIK you cannot link a 32bit library to a 64 binary an vice versa.) - requesting xinerama information (xdpyinfo -ext XINERAMA) does only work for programs that are started inside the session. You cannot request Xinerama information by redirecting $DISPLAY for the calling program. You'd as well have to set the LD_LIBRARY_PATH variable. - connection to an other host using ssh -X other-host leads to a working shell that has a DISPLAY. However, it is not able to request the correct Xinerama information. - probably more The reason for all this is the chosen approach. Patching the libXinerama.so only works for clients actually able to access the patched library. If - for whatever reason - they are using the standard libXinerama this fails. So I really think the patched library should vanish completely. Instead nx-X11/programs/xserver/Xext/panoramix.c should be extended to do a lookup to the nx client side whenever an X client is asking the nxagent/x2goagent for Xinerama information. What do you think? Is there anything I am missing here? 1. We don't patch Xinerama. Rather, nx-libs, our X server, includes an outdated version: nx-X11/lib/Xinerama 2. We are indeed working on dropping as many of nx-libs's bundled libraries as possible. We replace them with the system's versions. Often this means modifying files under nx-X11/programs/xserver/ like the one you mentioned. I am not sure what the schedule is for libXinerama, but I assume it is on the list. All this work is being done on the nx-libs 3.6.x branch. http://code.x2go.org/gitweb?p=nx-libs.git;a=shortlog;h=refs/heads/3.6.x https://github.com/ArcticaProject/nx-libs/tree/3.6.x 3. Hopefully someone can comment on the timetable for dropping the bundled libXinerama. Still, just because we dropped libXinerama doesn't mean we will immediately release nx-libs 3.6.0; We will probably drop other libraries 1st. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] [X2Go-Commits] [buildscripts] 01/01: Initial (untested) code for Raspbian support
Sorry for not getting back to you earlier,
On Sat, Apr 4, 2015 at 4:24 PM, Mihai Moldovan io...@ionic.de wrote:
On 04.04.2015 05:20 PM, git-ad...@x2go.org wrote:
This is an automated email from the git hooks/post-receive script.
x2go pushed a commit to branch feature/raspbian
in repository buildscripts.
commit e13114a13588afca0a3acdfba9b28191274609c8
Author: Mike DePaulo mikedep...@gmail.com
Date: Sat Apr 4 11:19:23 2015 -0400
Initial (untested) code for Raspbian support
---
bin/build-deb-package | 86
+++
home/.dupload.conf.x2go | 16 +
2 files changed, 80 insertions(+), 22 deletions(-)
diff --git a/bin/build-deb-package b/bin/build-deb-package
index 30e0609..88d731d 100755
--- a/bin/build-deb-package
+++ b/bin/build-deb-package
@@ -22,11 +22,33 @@ export PATH=${HOME}/bin:${PATH}
[...]
+if [[ -e /etc/dpkg/origins/raspbian ]]; then
+ DEB_DISTS_SUPPORTED=raspbian
+ DEB_ARCHS_SUPPORTED=armhf
+ DEB_ARCHS_SUPPORTED_COMMA=armhf
Better use:
typeset -a DEB_ARCHS_SUPPORTED
DEB_ARCHS_SUPPORTED+=(armhf)
(no need for DEB_ARCHS_SUPPORTED_COMMA, it won't work anyway.)
Ack
+ DEB_PRIMARY_ARCH=armhf
+else
+ DEB_DISTS_SUPPORTED=debian ubuntu
+ DEB_ARCHS_SUPPORTED=amd64 i386
+ DEB_ARCHS_SUPPORTED_COMMA=amd64,i386
Same here:
typeset -a DEB_ARCHS_SUPPORTED
DEB_ARCHS_SUPPORTED+=(amd64 i386)
Ack
+ DEB_PRIMARY_ARCH=amd64
+fi
+
[...]
@@ -43,7 +65,11 @@ test -f ${HOME}/.buildscripts/${PREFIX}.conf .
${HOME}/.buildscripts/${PRE
: ${NO_DELAY:=no}
: ${FORCE_BUILD:=no}
-: ${DEB_BUILD_FOR:=debian:${DEBIAN_DISTROS} ubuntu:${UBUNTU_DISTROS}}
+if [[ $DEB_DISTS_SUPPORTED==debian ubuntu ]]; then
This will always return true.
Better: if [ ${DEB_DISTS_SUPPORTED} = debian ubuntu ]; then
Ack
And even better:
leave : ${DEB_BUILD_FOR:=debian:${DEBIAN_DISTROS}
ubuntu:${UBUNTU_DISTROS}} in place, override via
if [ ${DEB_DISTS_SUPPORTED} = raspbian ]; then
+ : ${DEB_BUILD_FOR:=debian:${DEBIAN_DISTROS} ubuntu:${UBUNTU_DISTROS}}
remove
+elif [[ $DEB_DISTS_SUPPORTED==raspbian ]]; then
remove
+ : ${DEB_BUILD_FOR:=raspbian:${RASPBIAN_DISTROS}}
DEB_BUILD_FOR=raspbian:${RASPBIAN_DISTROS}
+fi
This is the coding style that Mike#1 used when he wrote the script. I
would rather remain consistent.
+fi
[...]
@@ -144,10 +170,16 @@ prepare_workspace() {
# by default we build for all current debian versions
if [ x${ARGV2_CODENAME} != x ]; then
- if grep -qs ${ARGV2_CODENAME} ${DEBIAN_DISTROS}; then
- DEB_BUILD_FOR=debian:${ARGV2_CODENAME}
- elif grep -qs ${ARGV2_CODENAME} ${UBUNTU_DISTROS}; then
- DEB_BUILD_FOR=ubuntu:${ARGV2_CODENAME}
+ if [[ $DEB_DISTS_SUPPORTED==raspbian ]]; then
if [ ${DEB_DISTS_SUPPORTED} = raspbian ]; then
+ if grep -qs ${ARGV2_CODENAME}
${RASPBIAN_DISTROS}; then
+ DEB_BUILD_FOR=raspbian:${ARGV2_CODENAME}
+ fi
+ elif [[ $DEB_DISTS_SUPPORTED==debian ubuntu ]]; then
else
+ if grep -qs ${ARGV2_CODENAME}
${DEBIAN_DISTROS}; then
+ DEB_BUILD_FOR=debian:${ARGV2_CODENAME}
+ elif grep -qs ${ARGV2_CODENAME}
${UBUNTU_DISTROS}; then
+ DEB_BUILD_FOR=ubuntu:${ARGV2_CODENAME}
+ fi
fi
fi
return 0
@@ -176,7 +208,7 @@ clear_pkgdist() {
test -z ${CODENAMES} || grep ${CODENAMES}
${line} || break
if [ x${EXTRA_ARCHS_ONLY} = x ]; then
- for l_ARCH in amd64 i386; do
+ for l_ARCH in ${DEB_ARCHS_SUPPORTED};
do
Remember the DEB_ARCHS_SUPPORTED change from above? Now we need:
for l_ARCH in ${DEB_ARCHS_SUPPORTED[@]}; do
Ack
[ x${SKIP_ARCH} !=
x${l_ARCH} ] {
mkdir -p --
${PKGDIST}/${l_DIST}/${l_CODENAME}/${l_ARCH}
rm -f --
${PKGDIST}/${l_DIST}/${l_CODENAME}/${l_ARCH}/dupload.conf
@@ -271,7 +303,7 @@ build_packages() {
else
dch --distribution ${VERSION}
--force-distribution -l ~git${DATE}.${GITREV}+${l_CODENAME}.${COMPONENT}.
Development-Snapshot!!! Auto-built ${l_DIST} ${l_CODENAME} package for
${REPOS_SERVER} repository (Git commit: ${GIT_OBJECT_ID}).
fi
- mkdir -p --
${PKGDIST}/${l_DIST}/${l_CODENAME}/{amd64,i386}
+ mkdir -p --
${PKGDIST}/${l_DIST}/${l_CODENAME}/{${DEB_ARCHS_SUPPORTED_COMMA}}
That won't work.
typeset tmp_arch=
for tmp_arch in
[X2Go-Dev] Raspberry Pi Builds and How to Handle Authentication/Signing
Hi guys, 1st of all, I recall that someone else offered to setup a Raspberry Pi for X2Go Jenkins builds, but I forget who it was. I also cannot find anything about it in my IRC logs or emails. Anyway, I started (but did not finish) adapting buildscripts.git for Raspberry Pi builds with Raspbian: http://code.x2go.org/gitweb?p=buildscripts.git;a=shortlog;h=refs/heads/feature/raspbian (For one thing, I need to replace the logic that always calls qemubuilder with logic to use regular (chroot) pbuilder.) For those of you who are unfamiliar, the challenge with Raspbian is that while Debian's armhf binaries are ARMv7 hard-float, Raspbian's armhf binaries are ARMv6 hard-float. This is a necessary complication to maximize performance out of the Raspberry Pi 1. Even on the Raspberry Pi 2, which does support ARMv7 hard-float, Raspbian users are currently still using these binaries. I figured I would setup my Raspberry Pi 2 at my apartment as a Jenkins slave. However, it appears that I would need to upload the packages to code.x2go.org with dupload, which would in turn call scp in batch mode. That means setting up SSH public key authentication. We would also have to figure out package signing. So before I continue, I want to know: 1. Should I continue setting this up, or should we try to use qemubuilder on japsand with a Raspberry Pi version of QEMU? 2. If I continue setting this up, how should we setup the SSH and GPG keys? -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] FYI: I updated the Fedora Rawhide mock files onjenkins
On Tue, Mar 31, 2015 at 6:10 PM, Mihai Moldovan io...@ionic.de wrote: On 31.03.2015 11:21 PM, Michael DePaulo wrote: I believe you are mistaken. The newly X2Go rawhide RPMs are for fc23 rather than fc22: http://packages.x2go.org/fedora/rawhide/heuler/x86_64/rpms/nx-libs/ This indicates that the mock config files are being used. Please trust me when I say they are not. This is merely incidental, because the config files in use don't specify the fedora release version, so the default one as specified in the rawhide image is used. Ack. I think these were the old versions: https://git.fedorahosted.org/cgit/mock.git/tree/etc/mock?id=mock-1.2.2 (Mock 1.2.2 was released on 2014-11-18). I've restored the old config files from the original mock .deb package and renamed your set to name.new. In order to really use the stuff in /etc/mock, I'll have to rewrite the RPM build script to create temporary config files to be used when invoking mock, I just haven't come around that yet, sorry! Ack BTW, an easy solution to this problem is etckeeper + git: https://packages.debian.org/wheezy/etckeeper Ah, that's actually a very nice idea for tracking config files! I will set it up, OK? Please give me some time to actually get the automatic mock config file generation set up. The current manual approach I did last week is brain-dead. Mihai Will do. -Mike ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#807: Please record and send a PulseAudio debug log
Please record and send a PulseAudio debug log. You do not need to be using a debug build to do this: 1. Run x2goclient.exe with --debug 2. Reproduce this problem. You can exit x2goclient when done. 3. Assuming your %USERPROFILE% is C:\Users\mike.DEPAULO, look under C:\Users\mike.DEPAULO\.x2go\pulse\ 4. Sort the subfolders by date. The newest (or only) subfolder will whose name begins with tmp contain the pulse.log file. This is the droid we're looking for. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] Maintaining VcXsrv and where to host it
On Mar 8, 2015 12:17 PM, Mihai Moldovan io...@ionic.de wrote: On 08.03.2015 05:07 PM, Michael DePaulo wrote: I will import it to code.x2go.org after work today. Please don't. I'll do it based on your github archive, then, whenever I get home at night. I still need to change a few scripts and make them available for git repo creation. Mihai Ack. ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Maintaining VcXsrv and where to host it
Hi everybody, This is something I wanted to discuss at our meeting today: http://wiki.x2go.org/doku.php/2015-03:day-2015-03-05?s[]=meeting Intro: For those who do not know, VcXsrv is a port of the X.org X server to Windows. Specifically, the MS Visual C compiler. X2Go Client for Windows bundles and uses it. So does PyHoca-GUI. SourceForge lots you create personal git repos based off of official project repos. So here is my branch on my personal git repo: https://sourceforge.net/u/mikedep333/vcxsrv/ci/xp-1.15.2.x-x2gochanges/tree/ The differences from usptream VcXsrv are: 1. I am currently maintaining the 1.15.2.x branch, rather than the 1.16.x branch of upstream. Upstream never maintains previous branches/releases. 2. I applied the nx-libs compatibility/bugfix patch from Alex, winmultiwindow.patch . I am keeping this on a branch with the suffix -x2gochanges branch because my convo with Alex indicated that upstream would not accept it. 3. I am maintaining Windows XP compatibility for the time being. 4. I respond quickly to security vulnerabilities in xorg-server and all the other bundled components (e.g., openssl, freetype2, X11 libs) Upstream simply updates/upgrades each component to the latest versions (even unreleased master branches often) on a seemingly arbitrary schedule. There are a few problems with using SourceForge: 1. SourceForge's support for git is terrible. Whenever I attempted a request merge from branch Y on my repo to the master branch on the usptream VcXsrv repo, it treid to merge my master branch instead. 2. SourceForge has recently done terrible things as GitHub has gained popularity: https://en.wikipedia.org/wiki/SourceForge#DevShare_adware_controversy 3. My repo isn't very visible because it is a personal git repo, not a project repo. 4. Upstream VcXsrv (1 developer, marha) is horribly unresponsive. They ignore bugs and merge requests for CVEs. Only once have I gotten an email reply to a merge request. He had a valid reason to reject the merge request, but he didn't actually reject it, so it is still open. I never had a bug report replied to. So effectively, staying on SourceForge does not enable us to upstream anything. Here is what I propose: 1. Host VcXsrv on both code.x2go.org and https://github.com/arcticaproject , simiilar to how nx-libs is hosted. 2. Prefer github for issue tracking. If an issue does affect X2Go users, then use the X2Go BTS and link to the github issue tracker. 3. Create a README.md similar to the one for nx-libs 3.6.x https://github.com/ArcticaProject/nx-libs/blob/3.6.x/README.md 4. Do not rename VcXsrv. State in the README.md that Arctica and X2Go are maintaining branch X or branch Y currently, or possibly even 2 branches at once. This is analogous to Linux distros maintaining a version of a package. 5. In the README.md or the github releases page, link to our builds under: http://code.x2go.org/releases/binary-win32/3rd-party/vcxsrv-modified-by-x2go-project/ 6. Rebase to VcXsrv 1.16.x in time for X2Go Client 4.0.4.0. 7. Pull from upstream VcXsrv (the master branch) continuously. 8. Hopefully receive many pull requests via GitHub :) -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#789: I reproduced it
On Thu, Mar 5, 2015 at 7:18 AM, Oleksandr Shneyder o.shney...@phoca-gmbh.de wrote: Hm, I think something has changed in Putty since I developed this feature. I didn't see this behavior earlier, when I used x2go client parallel to putty on my Windows machine. I'll check this. I think we have always been using PuTTY 0.63 for this feature. 0.64 just came out, but I have not switched the X2Go Client for Windows builds over to it. Nor have I tested it with X2Go Client for Windows. There is no need to use plink any more anyway, since libssh used in Windows client has native GSSAPI support. Are you sure? Windows uses Microsoft SSPI, not GSSAPI. https://encrypted.google.com/search?hl=enq=microsoft%20sspi%20vs%20gssapi regards, Alex If you want to rebuild libssh: 1. I have my settings for building libssh here: http://code.x2go.org/gitweb?p=x2goclient-contrib.git;a=blob;f=libssh/0.6.4-x2go1-mingw482_bin/CMake-Show-My-Changes.txt;h=66391e0cfebf4542938dcd71ab1b87dd9c03eca2;hb=HEAD 2. Rather than building 0.6.4 itself, you need to build 0.6.4 with these patches. 3 of the patches are the 3 commits made immediately after 0.6.4 released: http://code.x2go.org/gitweb?p=x2goclient-contrib.git;a=tree;f=libssh/0.6.4-x2go1-mingw482_src;h=a778703ad4118245b33e759d59b2fcb4fd370c37;hb=HEAD 3. The libssh developers recommend using the HEAD of the 0.6.x branch. You would still apply the pageant patch from #2. I got the MinGW 4.8.2 patch upstreamed on this branch, so no need to apply that: https://git.libssh.org/projects/libssh.git/log/?h=v0-6 4. #libssh on FreeNode has multiple developers who are very helpful. -Mike#2 Am 03.03.2015 um 13:59 schrieb Michael DePaulo: I reproduced this bug on my system: X2Go Client for Windows 4.0.3.2-20150301-debug Windows 10 64-bit (build 9926 with latest patches) I've CC'd the developer who added Windows Kerberos support, Alex. I've attached the Sessions registry key before and after. The test session I created, uss-phoenix, was clearly deleted. HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions\uss-phoenix\ However, there is no indication in the debug log (attached) that the Sessions key or its subkey was touched. I'll take a look at the x2goclient source code to figure out what is going on. -Mike#2 [...] ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#625: Making this grave due to data loss
Control: severity -1 grave Control: tags -1 build-win32 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#789: Merging this with #625
Control: forcemerge 625 -1 I just noticed the email about this being a duplicate. Thank you for help with bug triaging. ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#789: reassign correctly
Control: reassign -1 x2goclient ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#510: Dup of #496, shortcut configuration is #741
Hi Rob, Sorry to hear that you ran into this bug. The crashing bug is #496. I will mark it as a dup. I wish I could tell you an ETA on when it will be fixed. The fact that you cannot change the shortcuts is #741. #741 will be fixed as part of nx-libs (which includes the x2goagent package) 3.5.0.29. That new version of nx-libs should be out within days. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#775: About X servers
Hi Samo, Sorry to hear that you are running into these issues. The situation with X2Go Client for Windows and X servers is this: We support using an external X server, but we both bundle and maintain VcXsrv on a 1.15.2.x branch.[1] We intend to make any source code changes necessary to VcXsrv to fix integration issues with X2Go. In fact, we already made one X2Go integration change (bug #594, winmultiwindow.patch). However, those changes are slow to be made because we have few developers who spend pro bono time maintaining X2Go Client for Windows. Patches are welcome. These bugs/issues can also be fixed on contract. So in conclusion, we do intend to fix these issues, regardless of what piece of software is at fault. However, we cannot give an ETA. -Mike#2 [1] The VcXsrv 1.15.x branch we are maintaining is here: https://sourceforge.net/u/mikedep333/vcxsrv/ci/xp-1.15.2.x-x2gochanges/tree/ We may rebase to a newer VcXsrv branch soon. ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] 2nd Online ΞX2Go Developer Meeting (2015-03-05/4pm)
On Sun, Mar 1, 2015 at 2:18 PM, Mihai Moldovan io...@ionic.de wrote: On 01.03.2015 08:16 PM, Mihai Moldovan wrote: The correct date of course is March 3rd 2015. Now I'm messing up myself. The correct date is March *5th* 2015. I just read the log from the entire previous meeting: http://wiki.x2go.org/doku.php/wiki:development:planning:whiteboard?s[]=meeting If you intend to conduct the next meeting over IRC, please post the log again. An agenda (list of topics) before the meeting would be very much appreciated too. -Mike ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] FYI: I just submitted gtkperf for inclusion in Cygwin
https://cygwin.com/ml/cygwin-apps/2015-02/msg00321.html This will enable us to performance test X servers for Windows (Cygwin/X, VcXsrv, potentially vanilla builds of X.org with MinGW) more easily. One of the Cygwin/X maintainers (Jon Turney) was especially helpful. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] versioning of X2Go Client
On Wed, Feb 18, 2015 at 12:32 AM, Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: On Mi 18 Feb 2015 06:23:59 CET, Mihai Moldovan wrote: On 18.02.2015 06:09 AM, Mike Gabriel wrote: my recommendations for X2Go Client versioning: o release X2Go Client as is on Git master as 4.0.3.2 o merge feature/cleanup branch to master (discussion at our next meeting) o version bump to 4.0.4.0 o release 4.0.4.0 whenever it suits you Thanks for bringing that up. Yes, that's exactly the plan. This said, I explicitly built the preview version from my bugfix/osx (/features/cleanup) branch to have it tested more widely. While the code changes were minimal, as already discussed in private, (FIXME: also put this up the mailing list tomorrow!) I didn't test more sophisticated features like the broker or LDAP and there is a chance some resources (images) are not yet correctly wrapped up in my wrapper. I suspect I got it all, but more testing is never a bad idea. The benefit of this build to the user of course is a way more stable client which doesn't need to be restarted every time a subsequent session is started. 4.0.3.2 will be released based on current master, not my restructured branch(es). @Heinz, Stefan: IMHO, this is a very got point in time where the X2Go team could release the next X2Go LTS bundle. If needed, I can help with that now. If this shall be done some time later (I really disrecommend that), then you can pull me in via a coaching contract for that (because, no idea when this will be and where I will be by that time). My understanding of LTS is still very fuzzy. Does LTS merely mean that it's supported for an extended period of time, living in its own directory on packages.x2go.org and that any bugfixes for master are supposed to be backported to the LTS release? It means: o extra branches in Git that only get security issues and heavy breakage cherry-picked o dual release scheme (LTS version, main release version) o separate URLs for obtaining packages (see [1]) o support of those LTS branches in Git (and their binary release) for a defined period of time (until the next bundle release, basically) o AND: I have seen several people using the Baikal LTS Bundle!!! Mike [1] http://wiki.x2go.org/doku.php/download:baikal As the Windows maintainer, I would like a 4.0.4.0 release to happen in the coming months so that I can upgrade (rather than update) multiple Windows dependencies such as PulseAudio 5.0 - 6.0. Also, I agree that now is the perfect time for an LTS since Ubuntu 14.04, RHEL7 and SLE12 were all released last year. Also, this LTS release will support Debian Jessie I presume. -Mike ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] Status of fixing CVE-2015-0255 (2015-02-10)
Hi MIke#1 Mihai, On Tue, Feb 17, 2015 at 4:34 PM, Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: Hi Mike#2, On Di 17 Feb 2015 18:48:26 CET, Mihai Moldovan wrote: On 17.02.2015 02:39 PM, Michael DePaulo wrote: On Mon, Feb 16, 2015 at 8:14 AM, Michael DePaulo mikedep...@gmail.com wrote: I am looking into fixing the recently announced X.org vulnerability (CVE-2015-0255) in nx-libs. http://www.x.org/wiki/Development/Security/Advisory-2015-02-10/ It looks like nx-libs is affected. It also looks like some distros (Fedora, Debian) have fixed it, while others (RHEL 5, 6 and 7, Debian LTS) have not. It also looks like the X.org 1.16.x commits are easier to apply to nx-libs than the X.org 1.17.x commits are. The 1.17.x commits are linked to on that advisory page. The X.org 1.16.x commits are here: the branch: http://cgit.freedesktop.org/xorg/xserver/log/?h=server-1.16-branch the prereq: http://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.16-branchid=747cea16c4de1f48e838e1388301a2e24a3da6c4 the fix itself: http://cgit.freedesktop.org/xorg/xserver/commit/?h=server-1.16-branchid=8f61533b16635a0a13f4048235246edb138fa40b -Mike#2 Status Update: I managed to backport the prereq commit to nx-libs 3.6.x. http://code.x2go.org/gitweb?p=nx-libs.git;a=commit;h=a1cd16d6d05b197fff110d26b458d8bd6cf3c560 LGTM, thanks! Mihai Please directly apply the patch on top of the 3.6.x code and push to 3.6.x branches (Arctica/X2Go nx-libs repo). I will backport the patch to the 3.5.0.x branch for X2Go (and Arctica) (or you may do it yourself: Please use the Git commit from the 3.6.x branch in debian/patches/ for this). Similar to how I backported the other 40 patches you provided. Thanks+Greets, Mike Done. I had to backport 2 more commits as prereqs. However, they are non-intrusive. I will wait for review (e.g., from Mihai) before backporting from 3.6.x to 3.5.0.x. I did do a test build successfully (on Ubuntu 14.04 64-bit.) -Mike ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] [X2Go-Commits] [nx-libs] 28/52: CVE-2014-0210: unvalidated length fields in fs_read_list() from xorg/lib/libXfont commit 5fa73ac18474be3032ee7af9c6e29deab163ea39
On Mon, Feb 16, 2015 at 3:29 AM, Ulrich Sibiller ulrich.sibil...@gmail.com wrote: On Sun, Feb 15, 2015 at 10:02 PM, Mihai Moldovan io...@ionic.de wrote: Just as a heads-up: I would have moved this into the for loop condition like so: The code might offer a lot of possibilities for improvement. However, as all this is derived from the original X11 code I would prefer leaving it as is (and fix it upstream). This will make it a lot easier to backport later patches and it will also make the nx transition to current X11 much easier. Maybe add FIXME: comments to not forget those ideas. Uli +1 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] [X2Go-Commits] [nx-libs] 23/52: CVE-2014-0210: unvalidated length fields in fs_read_query_info() from xorg/lib/libXfont commit 491291cabf78efdeec8f18b09e14726a9030cc8f
On Mon, Feb 16, 2015 at 12:20 AM, Mihai Moldovan io...@ionic.de wrote: On 15.02.2015 09:17 PM, Mihai Moldovan wrote: Will do (later), but only once I'm through all the other commits. http://code.x2go.org/gitweb?p=nx-libs.git;a=commitdiff;h=e29bbd5bf0565eaf7c02f85a57b87f66531fa6b3;hp=5fc2f57fb5520bb61e2c1f8b6fd2522b203b3b9d Thanks. However, it is worth noting that the CentOS 7 patch (that you linked to) differs from both the upstream patch and the CentOS 5 patch. If you feel that upstream's patch was insufficient, we should tell them about it. -Mike ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] [X2Go-Commits] [nx-libs] 13/52: LZW decompress: fix for CVE-2011-2895 From xorg/lib/Xfont commit d11ee5886e9d9ec610051a206b135a4cdc1e09a0
On Mon, Feb 16, 2015 at 12:25 AM, Mihai Moldovan io...@ionic.de wrote: On 15.02.2015 09:15 PM, Michael DePaulo wrote: On a related note, upstream has this follow-up commit: http://cgit.freedesktop.org/xorg/lib/libXfont/commit/?id=bd48ad11fd11412c62c3ac8ed5d52c4f10a985aa It was not backported to RHEL5 though. http://code.x2go.org/gitweb?p=nx-libs.git;a=commitdiff;h=6acafc9334828da22446380c81af81bde14b5d86;hp=b04f11915e29d9563d279e1326f61b50ea414dba Thanks! ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] Fixes for 2011-2014 X.org CVEs and potential regressions in nx-libs
2015-02-15 8:31 GMT-05:00 Mike DePaulo mikedep...@gmail.com: bQBuWYZZrHSq5sOQcsDIQWu+r/7qcjvr+dyRT+OpvosVpZFpWXshb9a7gEBqB85/ Sorry, please ignore that email. I told ThunderBird with the EnigMail extension to send the email about CVEs being mitigated by -nolisten TCP twice because the 1st time produced an error message. For whatever reason, the 1st time it was sent, but it was sent encrypted. The 2nd time, it was sent successfully, and was signed. ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] [X2Go-Commits] [nx-libs] 13/52: LZW decompress: fix for CVE-2011-2895 From xorg/lib/Xfont commit d11ee5886e9d9ec610051a206b135a4cdc1e09a0
On Sun, Feb 15, 2015 at 2:11 PM, Mihai Moldovan io...@ionic.de wrote:
On 14.02.2015 05:47 PM, git-ad...@x2go.org wrote:
This is an automated email from the git hooks/post-receive script.
x2go pushed a commit to branch 3.6.x
in repository nx-libs.
commit af55da1e9c1a6a352b24823a8f7062c288ffbbc0
Author: Mike DePaulo mikedep...@gmail.com
Date: Sun Feb 8 19:15:20 2015 -0500
LZW decompress: fix for CVE-2011-2895 From xorg/lib/Xfont commit
d11ee5886e9d9ec610051a206b135a4cdc1e09a0
Specially crafted LZW stream can crash an application using libXfont
that is used to open untrusted font files. With X server, this may
allow privilege escalation when exploited
---
nx-X11/lib/font/fontfile/decompress.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/nx-X11/lib/font/fontfile/decompress.c
b/nx-X11/lib/font/fontfile/decompress.c
index a4c5468..553b315 100644
--- a/nx-X11/lib/font/fontfile/decompress.c
+++ b/nx-X11/lib/font/fontfile/decompress.c
@@ -261,6 +261,8 @@ BufCompressedFill (BufFilePtr f)
*/
while ( code = 256 )
{
+ if (stackp - de_stack = STACK_SIZE - 1)
+ return BUFFILEEOF;
Personally, I would have written that as
if ((stackp - de_stack) = (STACK_SIZE - 1))
But that's my personal style and I like to over-parenthesis.
Both the upstream commit and the RHEL5 patch have it written this way,
but I agree that your style is better.
http://cgit.freedesktop.org/xorg/lib/libXfont/commit/?id=d11ee5886e9d9ec610051a206b135a4cdc1e09a0
ftp://ftp.redhat.com/redhat/linux/enterprise/5Server/en/os/SRPMS/libXfont-1.2.2-1.0.6.el5_11.src.rpm
(cve-2011-2895.patch)
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] [X2Go-Commits] [nx-libs] 13/52: LZW decompress: fix for CVE-2011-2895 From xorg/lib/Xfont commit d11ee5886e9d9ec610051a206b135a4cdc1e09a0
On Sun, Feb 15, 2015 at 3:01 PM, Michael DePaulo mikedep...@gmail.com wrote:
On Sun, Feb 15, 2015 at 2:11 PM, Mihai Moldovan io...@ionic.de wrote:
On 14.02.2015 05:47 PM, git-ad...@x2go.org wrote:
This is an automated email from the git hooks/post-receive script.
x2go pushed a commit to branch 3.6.x
in repository nx-libs.
commit af55da1e9c1a6a352b24823a8f7062c288ffbbc0
Author: Mike DePaulo mikedep...@gmail.com
Date: Sun Feb 8 19:15:20 2015 -0500
LZW decompress: fix for CVE-2011-2895 From xorg/lib/Xfont commit
d11ee5886e9d9ec610051a206b135a4cdc1e09a0
Specially crafted LZW stream can crash an application using libXfont
that is used to open untrusted font files. With X server, this may
allow privilege escalation when exploited
---
nx-X11/lib/font/fontfile/decompress.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/nx-X11/lib/font/fontfile/decompress.c
b/nx-X11/lib/font/fontfile/decompress.c
index a4c5468..553b315 100644
--- a/nx-X11/lib/font/fontfile/decompress.c
+++ b/nx-X11/lib/font/fontfile/decompress.c
@@ -261,6 +261,8 @@ BufCompressedFill (BufFilePtr f)
*/
while ( code = 256 )
{
+ if (stackp - de_stack = STACK_SIZE - 1)
+ return BUFFILEEOF;
Personally, I would have written that as
if ((stackp - de_stack) = (STACK_SIZE - 1))
But that's my personal style and I like to over-parenthesis.
Both the upstream commit and the RHEL5 patch have it written this way,
but I agree that your style is better.
http://cgit.freedesktop.org/xorg/lib/libXfont/commit/?id=d11ee5886e9d9ec610051a206b135a4cdc1e09a0
ftp://ftp.redhat.com/redhat/linux/enterprise/5Server/en/os/SRPMS/libXfont-1.2.2-1.0.6.el5_11.src.rpm
(cve-2011-2895.patch)
On a related note, upstream has this follow-up commit:
http://cgit.freedesktop.org/xorg/lib/libXfont/commit/?id=bd48ad11fd11412c62c3ac8ed5d52c4f10a985aa
It was not backported to RHEL5 though.
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] [X2Go-Project] Invitation
2015-01-30 7:37 GMT-05:00 Mike Gabriel mike.gabr...@das-netzwerkteam.de: Hi Heinz, On Fr 30 Jan 2015 13:25:08 CET, Heinz-M. Graesing wrote: (2015-02-05) 4pm to 6pm works for me if it is UTC time. Mike Whether it is UTC or CET, I will be unable to attend. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#767: PyHoca-GUI with Pageant: An unknown error occurred during authentication
Package: pyhoca-gui Version: 0.5.0.3-20150124 tags +win32 When attempting to connect to a server using Pageant (Discover SSH keys or use SSH agent for X2Go authentication), you get this error: An unknown error occurred during authentication This is a regression between 0.5.0.0-pre02 (the previous build) and 0.5.0.3-20150124 (the current build.) I've attached the debug logs. (On Windows, logs are under %AppData%\pyhoca-gui\ ) 0.5.0.0-pre02 bundles paramiko 1.14.0. 0.5.0.3-20150124 bundles paramiko 1.15.2 This appears to be a regression in paramiko, #461: https://github.com/paramiko/paramiko/issues/461 @ThiefMaster's commit fixes the issue fine. The paramiko maintainer seems to be away, so it has not been merged yet. I will release a new build of PyHoca-GUI with the paramiko commit applied. PyHoca-GUI.9696.Pageant.0.5.0.3-20150124.log Description: Binary data PyHoca-GUI.5260.Pageant.0.5.0.0-pre02.log Description: Binary data ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#755: Bug#755: cannot upgrade x2goServer on fedora 20 using yum
On Sun, Jan 25, 2015 at 8:29 AM, ura u...@ureka.org wrote: ok, i just removed them. yum upgrade did nothing and yum run is not a valid yum directive. in any case, after re-installing the packages and running yum update, i now see no warnings in yum and the x2go client/server connection is running fine. thanks again. Ura, Great :) On Sat, Jan 24, 2015 at 11:43 PM, Orion Poplawski or...@cora.nwra.com wrote: I could probably have the Fedora x2goserver package provide x2goserver-extensions to help with such situations. Orion, Yes, please do so when you get a chance. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#749: Bug#749: X2Go Client: broker access - zero conf
On Fri, Jan 16, 2015 at 8:44 AM, Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: Package: x2goclient Severity: wishlist Just discussed an idea with Stefan on VideoChat. How about providing code in X2Go Client that tries to auto-detect local network broker setups automatically (zeroconf X2Go Client). Approaches would be: o retrieve the domain's SRV records and check if special records for X2Go Broker setups can be found o use a similar approach like browsers use for wpad.dat o make this configurable in X2Go Client settings Mike + Stefan [...] 2 other local network options are: o zeroconf (Avahi/Bonjour) o SSDP/UPnP. https://en.wikipedia.org/wiki/Avahi_(software) https://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol However, on Windows at least, firewalls are likely to block them. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#755: Bug#755: cannot upgrade x2goServer on fedora 20 using yum
Yes, you should do so and then reinstall the x2goserver and x2goserver-xesssion packages. Doing so will reinstall the necessary dependencies (e.g., nxagent). Of course, you should do so via a local console or command-line SSH, not via an X2Go session. And if you have made any changes to files under /etc/x2go/, you should back them up 1st. -Mike#2 On Sun, Jan 25, 2015 at 7:38 AM, ura u...@ureka.org wrote: thanks for responding here. i just ran: yum remove x2goserver-extensions and yum also elected to remove x2goserver, agent and xsession as dependencies. do you advise to remove all of these too? The problem is based on these circumstances: 1. You have X2Go installed from packages.x2go.org. The version string starts with: 4.0.1.18-0 2. The version of x2goserver in the fedora 20 updates repo has a higher version string: 4.0.1.18-5 3. You have the package x2goserver-extensions installed from packages.x2go.org. This is normal. 4. The x2goserver packages in Fedora 20 (both the base repo and the updates repo) do not include the x2goserver-extensions package. Orion, It looks like the files that are in the packages.x2go.org x2goserver-extensions package[1] are included in the Fedora x2goserver[2] package, correct? if so, I think Ura can solve this problem by removing x2goserver-extensions, and then running yum update. or: yum shell remove x2goserver-extensions upgrade run I could probably have the Fedora x2goserver package provide x2goserver-extensions to help with such situations. -Mike#2 [1] http://packages.x2go.org/fedora/20/main/x86_64/rpms/x2goserver/ [2] http://koji.fedoraproject.org/koji/buildinfo?buildID=602993 [...] ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] Bug#742: Executing parec seems unnecessary now that X2Go Client for Windows 4.0.3.0 uses PulseAudio 5.0
On Sat, Jan 24, 2015 at 10:47 PM, Mihai Moldovan io...@ionic.de wrote: On 25.01.2015 01:11 AM, Michael DePaulo wrote: Also, I did not bother to update the changelog because I feel this is a very minor change, and I do not want to bombard users with too many details in the changelog. I will confirm on x2go-project that doing so is OK. Please do document the change. This is make it easier to find out when this feature/workaround has been removed, should the removal ever cause problems in the future. This is especially useful for non-coders, who do not wish to dig through git archives in order to track a problem down. Mihai Done. Thanks. -Mike ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#742: This should be pending now
fixed #742 4.0.3.2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#742: Bug#742: Bug#742: Executing parec seems unnecessary now that X2Go Client for Windows 4.0.3.0 uses PulseAudio 5.0
Control: close -1 4.0.3.2 On Sat, Jan 24, 2015 at 6:30 PM, Michael DePaulo mikedep...@gmail.com wrote: [...] On Mi 14 Jan 2015 20:05:46 CET, George Trakatelis wrote: [...] The attached patch saves x2goclient from calling slotStartParec() once per second unnecessarily. thanks for providing this patch, George. Thanks! I'll test the patch for regressions. If there are none, I will commit it. (I will however delete that 1 line rather than comment it out.) I tested it successfully on XP 32-bit and on Windows 8.1 64-bit. So I applied it (after deleting that one commented out line.) Also, I did not bother to update the changelog because I feel this is a very minor change, and I do not want to bombard users with too many details in the changelog. I will confirm on x2go-project that doing so is OK. Thanks, -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#752: Bug#752: Bug#752: x2go windows client garbles local audio
Ignore my last email. I am not sure what fixed it, but I am glad the latest release fixed it for you. :) -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#752: Bug#752: x2go windows client garbles local audio
On Tue, Jan 20, 2015 at 1:22 PM, Hopkins, Bill bill.hopk...@level3.com wrote: Package: X2Go Client Version: V.4.0.2.0 (Qt – 4.8.5) There was no error message associated with the problem. To bring on the problem, all I have to do is start the X2Go client; it does not require me connecting to a server. I am listening to streaming audio on my laptop, with the audio going to a speaker system with subwoofer. When I start up the X2Go client, it switches the audio output device to the lame laptop speakers. I can make the audio go back to the nice speakers by unplugging the audio cable and plugging it back in. However, the sound is then slight distorted; the level of distortion varies periodically, and it becomes so bad that the music is almost completely replace by static. The laptop is running Windows 7 Professional (it remains up-to-date via Microsoft Tuesday Patches). The laptop is a Dell Studio 1558, with a quad-core i5 processor, 8 GB memory, 256GB SSD. Since the problem occurs without a connection, the version of the server software is irrelevant. Two connections are configured, both with audio disabled (which is why I’m wondering why the client is messing with the audio at all). By the way, I tried using reportbugs on my server, but Ubuntu takes umbrage, and I didn’t think you wanted the report sent to Debian (which is what it seems to want me to do). So I used the email option. Thanks! Great product. Most responsive remote desktop product I’ve used. [...] Hi Bill, Thanks, and sorry you ran into this issue. It sounds like PulseAudio is causing this problem. (X2Go Client for Windows 4.0.2.0 later bundle PulseAudio 5.0.) With X2Go Client for Windows 4.0.2.0, pulseaudio.exe is started as soon as you launch X2Go Client. With X2Go Client for Windows 4.0.3.1, pulseaudio.exe is started once you actually launch a session that uses audio. Of course, that change wouldn't actually fix the problem (unless you never use audio.) I would like you to do the following to collect more output from PulseAudio: 1. Install the latest debug build of X2Go Client for Windows http://code.x2go.org/releases/binary-win32/x2goclient/releases/4.0.3.1-20150119/non-default-builds/ 2. Reproduce the problem by starting a session with audio enabled. 3. Look in the folder %USERPROFILE%\.x2go\pulse . You should see 1 or more folders with random names like tmp.Hp8872. Open up the newest folder, and you should see the file pulse.log. Reply back with that file attached. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#670: Bug#670: Bug#670: window border and control disappears after maximize and move
Sorry for not replying earlier. I need to manage my email better. On Mon, Jan 5, 2015 at 5:20 AM, Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: @Mike#2: can you provide a diff of the vcxsrv code used in X2Go Client 4.0.2.1+hotfix1+build6 and in the MS Win X2Go Client version 4.0.3.0? You do not want me to do that. The diff is 38.2 MB. Upstream VcXsrv was upgraded (not updated) from 1.14.3 (19 Sep 2013) to 1.15.2 (5 July 2014). x2goclient 4.0.2.1+* uses https://sourceforge.net/u/mikedep333/vcxsrv/ci/1.14.3.2/ x2goclient 4.0.3.0 uses: https://sourceforge.net/u/mikedep333/vcxsrv/ci/1.15.2.1-xp+vc2013+x2go1/tree/ The only difference I made on top of upstream VcXsrv, other than changing version strings and updating the build process for XP compatibility, was adding Alex's winmultiwindow.patch: https://sourceforge.net/u/mikedep333/vcxsrv/ci/978ec71bbf4345f477fd4f937deb3a4b481862e2/ On Mon, Jan 19, 2015 at 8:23 AM, x2go.guilla...@zitta.fr wrote: I tested x2go 4.0.3.1 with several version of external VcXsrv (1.15.0.2, 1.15.1, 1.16.1, 1.16.2) without problem. (command line option: -multiwindow -notrayicon -clipboard) When I switch back to internal X server and problem is back too. Thanks for doing this investigation. It sounds like there are 2 possible causes. 1. The command line options passed to VcXsrv. When you use the internal X server, X2Go Client figures out what options to pass based on your session preferences. So they probably differ than those you listed. 2. Alex's winmultiwindow.patch , which only VcXsrv 1.15.2.1-xp+vc2013+x2go1 VcXsrv 1.15.2.2-xp+vc2013+x2go1 include. The +x2go1 in the version string denotes that we made an X2Go-specific change. Specifically, that patch. In order to narrow this problem down, please try the following: 1. Configure x2goclient to use a custom X-server, but specify X2Go Client's own internal X-server as the executable. On 32-bit windows: C:\Program Files\x2goclient\VcXsrv\vcxsrv.exe On 64-bit windows: C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe 2. Specify the same command-line options as before. 3. Restart x2goclient and try to reproduce the bug. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#723: Bug#723: AW: Bug#723: Bug#723: x2go sessions insta-break with some GUI software (ROOT TBrowser)
On Mon, Jan 12, 2015 at 5:45 AM, Babutzka, Martin (EKP) martin.babut...@kit.edu wrote: Hey Mikes :-) Thanks for your replies. We resolved the problem by recommending the x2go client version 4.0.2.1 to our users which includes a sufficiently old Vcxsrv. We are fine with this solution. Please keep this upstream-bug in vcxsrv in mind for the case more applications show the problem and replicated bug reports are created. Thanks for your efforts on the x2go-software! Martin [...] No problem. I'm glad you have a workaround for the time being. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] jenkins.x2go.org in trouble
On Tue, Jan 13, 2015 at 12:41 AM, Michael DePaulo mikedep...@gmail.com wrote: On Mon, Jan 12, 2015 at 12:33 AM, Michael DePaulo mikedep...@gmail.com wrote: On Sun, Jan 11, 2015 at 11:58 PM, Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: Hi Alex, hi Heinz, hi Michael, the build system on jenkins.x2go.org seems to have some troubles at the moment. Can either of you take a look? I any help is needed I will be happy to provide it during this week. Greets, Mike [...] I will take a look tomorrow evening. Sorry, I'll look at it either tomorrow morning or tomorrow evening. several builds were failing but hung indefinitely. You can see 2 of the logs here: http://jenkins.x2go.org:8080/view/All/job/x2gobroker+nightly+debian-sid/163/console http://jenkins.x2go.org:8080/view/All/job/x2gobroker+nightly+debian-jessie/148/console I fixed the problem in the short term by killing those qemubuilder processes. Builds are now working. But there is a build queue of 85 right now. However, we do not want the problem to happen again. Mike#1 thinks that it is because we ran into the limit of 8 loop devices on the host (japsand.) However, the limit has been set to 64 since before the machine was last rebooted: mikedep333@japsand:/etc/modprobe.d$ cat /etc/modprobe.d/loop.conf options loop max_loop=64 I'll look into this later. Maybe we specified the limit on loop devices incorrectly. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] jenkins.x2go.org in trouble
On Mon, Jan 12, 2015 at 12:33 AM, Michael DePaulo mikedep...@gmail.com wrote: On Sun, Jan 11, 2015 at 11:58 PM, Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: Hi Alex, hi Heinz, hi Michael, the build system on jenkins.x2go.org seems to have some troubles at the moment. Can either of you take a look? I any help is needed I will be happy to provide it during this week. Greets, Mike [...] I will take a look tomorrow evening. Sorry, I'll look at it either tomorrow morning or tomorrow evening. ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#739: Connection failed errors when using GSSAPI on Windows (PuTTY+Krb5)
Package: x2goclient Version: 4.0.3.1 Client OS: Windows 8.1 64-bit with all available updates Server OS: Fedora 21 64-bit with most available updates Server krb5 client: samba winbind 4.1.14-1.fc21 x2goagent: 3.5.0.28 x2goserver: 4.0.1.18 x2goserver-extensions: 4.0.1.18 x2goserver-xsession: 4.0.1.18 (with fix for #632 applied) When I attempt to use GSSAPI authentication on Windows, with either x2goclient 4.0.3.1-20141214 or x2goclient 4.0.3.2 development build (2015-01-11 9363860), I see 2 error messages come up when I start a new session on the aforementioned host: Message 1: Connection failed : cp: missing destination file operand after '/home/DEPAULO/mike/.x2go/C-mike-50-1420995172_stDMATE_dp32/krb5cc' Try 'cp --help' for more information Message 2: Connection failed pscp: unable to open /home/mike/.x2go/ssh/key.Hp6896: no such file or directory Message 1 is on top of message 2. If I reconnect to a session, I only receive message #2. Under both versions of x2goclient, the X2go Session appears to start successfully. e.g., I see my mate desktop launch. And I can actually interact with it. However, whenever I connect with 4.0.3.1-20141214, as soon as I dismiss error message #2, x2goclient terminates entirely. On 4.0.3.2, these error messages are harmless (but annoying.) I've attached the log from the 4.0.3.2 development build (2015-01-11 9363860). I've also attached the server's samba configuration. C:\x2gobuilds\x2goclient\distx2goclient.exe --debug x2go-INFO-1 Starting x2goclient... x2go-WARNING-1 Can't load translator: :/x2goclient_en_us x2go-WARNING-2 Can't load translator: :/qt_en_US x2go-DEBUG-onmainwindow.cpp:1203 Removing apps from tray x2go-DEBUG-onmainwindow.cpp:1171 Plugging apps in tray. x2go-DEBUG-onmainwindow.cpp:9797 Getting Xorg settings. x2go-INFO-3 Started x2goclient. x2go-DEBUG-onmainwindow.cpp:490 $HOME=C:/Users/mike.DEPAULO x2go-DEBUG-onmainwindow.cpp:2118 Reading 24 sessions from config file. QPixmap::scaled: Pixmap is a null pixmap x2go-DEBUG-onmainwindow.cpp:9523 Starting win servers... x2go-DEBUG-onmainwindow.cpp:9875 C:/Users/mike.DEPAULO/.x2go/etc/sshd_config created. x2go-DEBUG-onmainwindow.cpp:9292 got localhost x2go-DEBUG-onmainwindow.cpp:9314 Port is free: 7022 x2go-DEBUG-onmainwindow.cpp:9931 Creating desktop: x2go_mike x2go-DEBUG-onmainwindow.cpp:2663 Starting session via smartcard, ssh-agent or kerberos token. x2go-DEBUG-onmainwindow.cpp:1203 Removing apps from tray x2go-INFO-8 Starting connection to server: mothership:22 x2go-DEBUG-onmainwindow.cpp:2697 Start new ssh connection to server:mothership:22 krbLogin: true x2go-DEBUG-sshmasterconnection.cpp:198 starting ssh connection with kerberos authentication x2go-DEBUG-sshmasterconnection.cpp:206 SshMasterConnection, instance SshMasterConnection(0x352a728) created x2go-DEBUG-sshmasterconnection.cpp:442 SshMasterConnection, instance SshMasterConnection(0x352a728) entering thread x2go-DEBUG-sshmasterconnection.cpp:478 libSsh not inited yet, initting x2go-DEBUG-sshmasterconnection.cpp:522 setting SSH DIR to C:/Users/mike.DEPAULO/ssh x2go-DEBUG-sshmasterconnection.cpp:140 writing key in registry: HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys x2go-DEBUG-sshmasterconnection.cpp:141 unknown@22:dropship-hv=0x6e69737470323536,0x4b8023dd13807ed21388588a5ebb90d11a3aa1e368e25edeb8d23cefc82799f21bb2f68f7dfb568e7d839480172ebe68058d6a7b4debc41acc465ac43fc745525 x2go-DEBUG-sshmasterconnection.cpp:140 writing key in registry: HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys x2go-DEBUG-sshmasterconnection.cpp:141 unknown@22:opensuse-131=0x6e69737470323536,0x4b58c6f1873a34a728cbb26e64983fb1ff27e6bc9ac407f7b7b09b085477066513821bf042401160f41c9515e5904aa1488907cd7c1b114cba1a351f2043e81c9 x2go-DEBUG-sshmasterconnection.cpp:140 writing key in registry: HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys x2go-DEBUG-sshmasterconnection.cpp:141 unknown@22:mothership=0x6e69737470323536,0x4b836e035b5757ea09b21c7aeac8bffaaec0b822e89a0e8eb6746638bcf5b71147625857699aec76952733d340e30fb8a6d7f194b183ab8a9543f88c37e86db63 x2go-DEBUG-sshmasterconnection.cpp:140 writing key in registry: HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys x2go-DEBUG-sshmasterconnection.cpp:141 rsa2@22:galactica=0x23,0xd2ba2d273a28a2ef5fad170ef744a1c284ce0418a74509408a821ebb07e9b627d936f86392e05f0e2540c1172cc711a54b9020665c236ddc4f2941bed75f59c543798515937326e08375119ac092fc74627eb6d3f278ba719bd31816ca5b6ab143485a93b1b8eacfec01551cd51f0b05a194983780f212be3c4b07cc2c3c7b83d5527e68d562de281beddf7b02713dd5c0d3c876554d50278d3f6336bbd15b31843cd27be62452c8c8dbe5b83b63ac71259a20343988e142b365c71c45f74b013a5a1d65e69c7d4c66103ca7bea6700f8987d702b2a17ab9da8ce72d975a71953d66a2afd342a9512f1214d566a9878d67f8153cd5039f6822d248c0662dc925 x2go-DEBUG-sshmasterconnection.cpp:140 writing key in registry: HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys x2go-DEBUG-sshmasterconnection.cpp:141
Re: [X2Go-Dev] [X2Go-User] Shifting my focus in X2Go
On Sat, Jan 10, 2015 at 5:23 PM, Robert Dinse nan...@eskimo.com wrote: I was just wondering if there was any hope of sound ever working on the MacOS client? Also any hope of it working full screen without putting the X server in full screen (which breaks virtual desktops)? [...] I am X2Go's Windows maintainer, not its Mac maintainer. However, I have worked with the upstream PulseAudio project to resolve a number of Windows issues. And it looks Mac OS X support in PulseAudio is still being maintained. So it should be feasible to get audio working on the Mac OS X X2Go Client. http://www.freedesktop.org/wiki/Software/PulseAudio/Ports/OSX/ -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#723: Bug#723: Bug#723: x2go sessions insta-break with some GUI software (ROOT TBrowser)
On Fri, Jan 9, 2015 at 9:55 AM, Babutzka, Martin (EKP) martin.babut...@kit.edu wrote: Some updates on this bug: I've tested several VcXsrv-Versions from http://code.x2go.org/releases/binary-win32/3rd-party/vcxsrv-modified-by-x2go-project/ The bug purely occurs with the more recent versions of VcXsrv - like 1.15.2.0 and 1.15.2.1 The bug does NOT occur with the older versions 1.14 (tested 1.14.3.2). So the bug is caused by changes made in VcXsrv from version 1.14 to 1.15. I used the debug version vcxsrv-debug.1.15.2.1-xp+vc2013+x2go1.installer.exe to receive the following trace of the SIGFAULT: [...] Hi Martin, This is a bug that I do intend to fix when I get a chance, even if it means fixing the bug in the VcXsrv code. However, I am not an expert at C, and I probably will not fix this anytime soon. (Patches from others are welcome.) However, in the meantime, you can follow this workaround: 1. Install VcXsrv (VcXsrv-xp) 1.14.3.2 and remember where you installed it. 2. Configure X2Go Client for Windows to use that vcxsrv.exe as an external X server: Options - Settings - X-Server settings If you have a large number of users or machines that need these settings, you can save the settings a registry key that can be exported and imported per-user-account and per-machine. The reg key is: [HKEY_CURRENT_USER\Software\Obviously Nice\x2goclient\settings] -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#616: Finally managed to record the issue on tape
The way I see it, there are 2 parts of the issue. 1. Something is happening for 5 seconds. 2. During those 5 seconds, X2Go Client is displaying the Hourglass-and-Pointer. We should be able to fix the issue by solving either part. Perhaps there is some Qt feature we need to adjust in order to fix part #2? -Mike#2 On Fri, Jan 9, 2015 at 4:30 AM, Oleksandr Shneyder o.shney...@phoca-gmbh.de wrote: Hello Stefan, Actually, I don't see it as a problem at all, but I understand your point. I'll see, what I can do about it. regards, Alex Am 08.01.2015 um 17:51 schrieb Stefan Baur: Am 24.11.2014 um 15:38 schrieb Oleksandr Shneyder: I tried to launch newest client from nightly builds on Win7. I see a waiting pointer on the start of x2go client. But in this time I can use X2Go Client without problem and UI is responsible at that time. Did I understand you right? You have 5 sec. delay and during this delay you can't use a UI? Sorry for not replying sooner. No, we're talking about the same cursor. Hourglass-and-Pointer, not Hourglass. So while yes, one can use the UI during these 5 seconds, it nevertheless is confusing to the user. The initial reaction of the average user is Oh, that thing's busy, I should wait. A non-technical user will not differentiate between Hourglass-and-Pointer and Hourglass. Since previous versions of X2GoClient did not exhibit this behavior, I am expecting complaints about a sudden slow startup (from non-technical users, that are not aware of the difference between those two cursor types) when I roll this thing out. Is there no way we can avoid this? Maybe start the background processes and the reaper only when a session is in the startup phase, and not immediately when x2goclient.exe start? -Stefan [...] ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#715: Bug#715: Proposed patch
Hi Mike#1, On Mon, Jan 5, 2015 at 5:13 AM, Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: Hi Michael, On Mo 05 Jan 2015 05:12:04 CET, Michael DePaulo wrote: Tags: patch I would like someone who knows Perl better, such as theUser2, to review this patch. Although this is a very small patch, theUser2 advised me to be careful when creating full paths. I tested it successfully under CentOS 5 and CentOS 6. I intended to use make_path instead of mkpath if File::Path 2.06 or later was detected. However, I could not figure out how to write a statement like use File::Path( make_path) if File::Path-VERSION is 2.06 or later. Specifically, it appears that use statements are executed at compile time in Perl, so they cannot be used within an if block. And I cannot just specify use File::Path for all versions of File::Path because make_path is not exported by default. EPEL 5: http://perldoc.perl.org/5.8.8/File/Path.html EPEL 6: http://perldoc.perl.org/5.10.1/File/Path.html Latest: http://perldoc.perl.org/File/Path.html I recommend a more conditional approach testing the existence of the make_path (and the mkpath) function during runtimed using the defined command. See: http://stackoverflow.com/questions/433752/how-can-i-determine-if-a-perl-function-exists-at-runtime Mike [...] I will follow that advice for runtime, but I still need to figure out what to do at compile time. http://perldoc.perl.org/functions/use.html Because use takes effect at compile time, it doesn't respect the ordinary flow control of the code being compiled. In particular, putting a use inside the false branch of a conditional doesn't prevent it from being processed. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#715: Proposed patch
Tags: patch I would like someone who knows Perl better, such as theUser2, to review this patch. Although this is a very small patch, theUser2 advised me to be careful when creating full paths. I tested it successfully under CentOS 5 and CentOS 6. I intended to use make_path instead of mkpath if File::Path 2.06 or later was detected. However, I could not figure out how to write a statement like use File::Path( make_path) if File::Path-VERSION is 2.06 or later. Specifically, it appears that use statements are executed at compile time in Perl, so they cannot be used within an if block. And I cannot just specify use File::Path for all versions of File::Path because make_path is not exported by default. EPEL 5: http://perldoc.perl.org/5.8.8/File/Path.html EPEL 6: http://perldoc.perl.org/5.10.1/File/Path.html Latest: http://perldoc.perl.org/File/Path.html perl-File-Path-epel5-compat-v3.patch Description: Binary data ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#714: Cannot connect to epel5 servers: Undefined subroutine main::LOG_UPTO
Package: x2goserver Version: 4.0.1.18 Severity: grave Server: CentOS 5.11 64-bit Server distro's version of Perl: 5.8.8-43.el5_11 Client: x2goclient 4.0.3.1 Client OS: Windows 8.1 64-bit While I was verifying the fix for #699, I noticed that whenever I attempt to connect to my CentOS 5 server, I get the error: Connection failed Undefined subroutine main::LOG_UPTO called at /usr/bin/x2golistsessions line 35. This bug prevents X2Go Server from being used at all on epel5 distros (RHEL 5, CentOS 5, SL 5, OL 5). It appears that the cause is that the LOG_UPTO() function is not available on CentOS 5's version of Perl, 5.8.8. It is available on CentOS 6 (Perl 5.10.1), hence why my CentOS 6 system is not affected. http://perldoc.perl.org/5.8.8/Sys/Syslog.html http://perldoc.perl.org/5.10.1/Sys/Syslog.html ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#714: Actually a packaging problem
This is actually a problem with our packaging. A 3rd-party RPM exists to provide a newer version of Sys::Syslog that is sufficient, and this is stated on the wiki. The bug is that yum is not informing the user of the need to install that newer version. The wiki states the following, and the 2nd sentence is false: One approach is to download required packages manually. Yum will tell you what is needed, when you ask it to install x2goserver. http://wiki.x2go.org/doku.php/doc:installation:x2goserver?#rhel_5 For reference: The RPM that I used (and tested successfully) was: http://flexbox.sourceforge.net/centos/5/x86_64/perl-Sys-Syslog-0.27-1.el5.x86_64.rpm Apparently 32-bit users should use this noarch RPM instead: http://flexbox.sourceforge.net/centos/5/i386/perl-Sys-Syslog-0.27-1.noarch.rpm ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#715: Cannot create X2Go Session Database on EPEL 5
Package: x2goserver Version: 4.0.1.18 Severity: grave Server OS: CentOS 5.11 64-bit Client: 4.0.3.1 When you attempt to connect to a CentOS 5 server, you get a Connection failed error. The error includes the text unable to open database file(1) . This bug prevents EPEL 5 users from using X2Go Server at all. The underlying problem appears to be that x2godbadmin fails to create the session database: [batmin@centos-5 log]$ sudo /usr/sbin/x2godbadmin make_path is not exported by the File::Path module Can't continue after import errors at /usr/sbin/x2godbadmin line 25 BEGIN failed--compilation aborted at /usr/sbin/x2godbadmin line 25. Newer versions of File::Path provide make_path, but I was unable to find an EPEL 5 RPM that provides a sufficiently new version of File::Path . This bug appears to be a regression that was introduced by commit bad455e : http://code.x2go.org/gitweb?p=x2goserver.git;a=commit;h=bad455edefdce83da6a1f3b42e6626030e8b82d2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] (Jenkins Question) Rebuilding main packages for EPEL 5.
On Dec 21, 2014 8:33 PM, Michael DePaulo mikedep...@gmail.com wrote: Hi Mike#1 and others, I want to rebuild the main packages for EPEL 5 so that we can fix bug #699. I've already rebuilt and tested the nightly EPEL 5 packages; bug #699 was successfully fixed on them. However, it appears that in order to rebuild any package for EPEL 5, I must rebuild them for every release of every Linux distro. http://jenkins.x2go.org:8080/view/All%20Releases/?auto_refresh=false Should I just do that via Jenkins? Or would it be disruptive? For example, would users be prompted to update even when they do not have to? I think that would happen for EPEL users at least, because the nightly EPEL 5 nx-libs packages now have git20141222 in their version strings. (nx-libs.git was last updated 2 weeks ago, but I rebuilt it under nightly on 2014-12-22 (UTC +1:00).) -Mike Mike#1, please advise. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#710: Error connecting to CentOS 5 Server: Connection Failed Undefined subroutine X2Go::Server::DB::PostgreSQL::LOG_UPTO
Package: x2goserver Version: 4.1.0.0-preview Server: CentOS 5.11 64-bit with latest updates [batmin@centos-5 ~]$ x2goversion Undefined subroutine main::LOG_UPTO called at /usr/lib64/x2go/x2gosyslog line 28. x2goagent: 3.5.0.29 x2goserver: 4.1.0.0-preview x2goserver-common: 4.1.0.0-preview x2goserver-extensions: 4.1.0.0-preview x2goserver-xsession: 4.1.0.0-preview X2go Client for Windows: 4.0.3.1-20141214-debug After fixing bug #699, when I attempt to connect to the CentOS 5 server with X2Go Client, I get this Connection Failed error pop-up window: x2go-DEBUG-onmainwindow.cpp:3382 Undefined subroutine X2Go::Server::DB::PostgreSQL::LOG_UPTO called at /usr/lib/perl5/vendor_perl/5.8.8/X2Go/Server/DB/PostgreSQL.pm line 42. Compilation failed in require at /usr/lib/perl5/vendor_perl/5.8.8/X2Go/Server/DB.pm line 40. BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.8.8/X2Go/Server/DB.pm line 40. Compilation failed in require at /usr/bin/x2golistsessions line 27. BEGIN failed--compilation aborted at /usr/bin/x2golistsessions line 27. Clicking OK results in you not connecting. I've attached the full log from x2goclient.exe --debug C:\Program Files (x86)\x2goclient-4.0.3.1-20141214x2goclient.exe --debug x2go-INFO-1 Starting x2goclient... x2go-WARNING-1 Can't load translator: :/x2goclient_en_us x2go-WARNING-2 Can't load translator: :/qt_en_US x2go-DEBUG-onmainwindow.cpp:1203 Removing apps from tray x2go-DEBUG-onmainwindow.cpp:1171 Plugging apps in tray. x2go-DEBUG-onmainwindow.cpp:9755 Getting Xorg settings. x2go-INFO-3 Started x2goclient. x2go-DEBUG-onmainwindow.cpp:490 $HOME=C:/Users/mike.DEPAULO x2go-DEBUG-onmainwindow.cpp:2104 Reading 23 sessions from config file. QPixmap::scaled: Pixmap is a null pixmap x2go-DEBUG-onmainwindow.cpp:9497 Starting win servers... x2go-DEBUG-onmainwindow.cpp:9833 C:/Users/mike.DEPAULO/.x2go/etc/sshd_config created. x2go-DEBUG-onmainwindow.cpp:9266 got localhost x2go-DEBUG-onmainwindow.cpp:9294 Port already used: 7022 x2go-DEBUG-onmainwindow.cpp:9266 got localhost x2go-DEBUG-onmainwindow.cpp:9288 Port is free: 7023 x2go-DEBUG-onmainwindow.cpp:9889 Creating desktop: x2go_mike x2go-DEBUG-onmainwindow.cpp:1203 Removing apps from tray x2go-INFO-8 Starting connection to server: centos-5:22 x2go-DEBUG-onmainwindow.cpp:2683 Start new ssh connection to server:centos-5:22 krbLogin: false x2go-DEBUG-onmainwindow.cpp:2778 SSH connection established. x2go-DEBUG-onmainwindow.cpp:3038 Continue normal x2go session x2go-DEBUG-onmainwindow.cpp:3382 Undefined subroutine X2Go::Server::DB::PostgreSQL::LOG_UPTO called at /usr/lib/perl5/vendor_perl/5.8.8/X2Go/Server/DB/PostgreSQL.pm line 42. Compilation failed in require at /usr/lib/perl5/vendor_perl/5.8.8/X2Go/Server/DB.pm line 40. BEGIN failed--compilation aborted at /usr/lib/perl5/vendor_perl/5.8.8/X2Go/Server/DB.pm line 40. Compilation failed in require at /usr/bin/x2golistsessions line 27. BEGIN failed--compilation aborted at /usr/bin/x2golistsessions line 27. x2go-DEBUG-onmainwindow.cpp:1461 Close event received. x2go-INFO-6 Closing x2goclient... x2go-DEBUG-onmainwindow.cpp:1314 Saving settings... x2go-DEBUG-onmainwindow.cpp:1323 Saved settings. x2go-DEBUG-onmainwindow.cpp:1345 Waiting for the SSH connection to finish... x2go-DEBUG-onmainwindow.cpp:1347 Waited for the SSH connection to finish. x2go-INFO-7 Closed x2goclient. C:\Program Files (x86)\x2goclient-4.0.3.1-20141214___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] (Jenkins Question) Rebuilding main packages for EPEL 5.
Hi Mike#1 and others, I want to rebuild the main packages for EPEL 5 so that we can fix bug #699. I've already rebuilt and tested the nightly EPEL 5 packages; bug #699 was successfully fixed on them. However, it appears that in order to rebuild any package for EPEL 5, I must rebuild them for every release of every Linux distro. http://jenkins.x2go.org:8080/view/All%20Releases/?auto_refresh=false Should I just do that via Jenkins? Or would it be disruptive? For example, would users be prompted to update even when they do not have to? I think that would happen for EPEL users at least, because the nightly EPEL 5 nx-libs packages now have git20141222 in their version strings. (nx-libs.git was last updated 2 weeks ago, but I rebuilt it under nightly on 2014-12-22 (UTC +1:00).) -Mike ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#699: Fix committed, but only the nightly repo is fixed yet
I committed the fix to buildscripts.git and updated buildscripts.git on japsand.x2go.org (which builds uploads the packages.) However, for reasons explained in the linked email, I have only rebuilt the nightly packages with the key, not the main (stable release) packages yet. And the 4.1.0.0 x2goserver nightly package is very unstable. http://lists.x2go.org/pipermail/x2go-dev/2014-December/008891.html To any users affected by this bug, I hope to have the main packages rebuilt (and therefore fixed) ASAP. ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#699: Bug#699: epel 5 repos have signature errors
On Fri, Dec 12, 2014 at 9:18 PM, Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: Control: tag -1 pending Hi Michael, On Fr 12 Dez 2014 15:22:30 CET, Michael DePaulo wrote: As reported here: http://lists.x2go.org/pipermail/x2go-user/2014-December/002705.html A CentOS 5 user is getting these errors: error: nx-libs-3.5.0.28-0.0x2go1.1.git20141114.546.main.el5.centos: Header V4 RSA/SHA1 signature: BAD, key ID 5bfe2b6e error: libXcomp-3.5.0.28-0.0x2go1.1.git20141114.546.main.el5.centos: Header V4 RSA/SHA1 signature: BAD, key ID 5bfe2b6e etc The cause appears to be that CentOS 5 cannot handle V4 signatures, only V3. http://adminotes.blogspot.fr/2011/12/centos-6-rpm-sign-problem-v4-signatures.html I hope this (and a previous commit) fixes the issue: http://code.x2go.org/gitweb?p=buildscripts.git;a=commitdiff;h=3c79b61da0e25e7df61206d0d6ac986e457ff7af I have just triggered rebuilds of nightly packages nx-libs and x2goserver. Can you check (once the have built) if those packages are now installable on Centos5? Thanks, Mike Hi Mike#1, I just setup a CentOS 5.11 64-bit VM and tried to install the nightly packages. I am still getting the errors like both Michael Dubois and I get with the stable release packages. error: nx-libs-3.5.0.29-0.0x2go1.0.git20141213.552.heuler.el5.centos: Header V4 RSA/SHA1 signature: BAD, key ID 5bfe2b6e -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] How should we implement disabling microphone input in x2goclient?
Hi guys, If you read this email convo: [X2Go-User] Pulseaudio doesn't start on Win7 It becomes clear that X2Go Client for Windows needs a way to pass record=0 to pulseaudio.exe in config.pa. This will disable microphone input. There are 3 ways to do this that I can think of. Which do you think I should implement? Implementing more than one way should be possible. If I do implement more than one way, we need to figure out what overrides what. 1. A command-line argument like --microphone=on|off (proposed by Stefan). This would affect all sessions. 2. Under Options - Settings, add a new tab like PulseAudio settings or Sound settings with the microphone on or off option. This would affect all sessions. 3. A session preference. Probably under Settings - Sound. This might be problematic, since it would be a Windows-client-specific session preference. This would obviously be on a per-session basis. 4. Perhaps a registry key under HKEY_LOCAL_MACHINE rather than HKEY_CURRENT_USER. Only an administrator would have permission to change this reg key. I am leaning towards both 1 and 2. By default, microphone input will be enabled. But if a user toggles it via #2, or if x2goclient is called with the argument from #1, then it will be changed to on or off. So hypothetically, this could happen: 1. it defaults to on. 2. A user turns it off via #2. 3. It is turned on again via #1. 4. The user starts x2goclient again without the argument from #1. It is still on. Another variation is to have #1 forcibly override #2, but only for the current instance of x2goclient So hypothetically, this could happen: 1. it defaults to on 2. A user turns it off via #2 3. It is turned on again via #1, but only for the current instance of x2goclient. The GUI for #2 is greyed out, but only for the current instance. 4. The user starts x2goclient without the argument from #1. it is off again. -Mike ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#642: Changes in X2Go Client for Windows to enable it conform to Visual Studio's stricter type checking
Hi George, see below On Tue, Dec 2, 2014 at 6:48 PM, George Trakatelis trakate...@uom.edu.gr wrote: Hi Michael, I built x2goclient 4.0.3.0 with MSVC2010's nmake. Unfortunately couldn't do so with Visual Studio 2010 IDE. I have made a lot of progress, but I am having trouble finding a build of libssh that includes the .lib file(s), and that is new enough. I think the .lib file(s) are specific to MSVC. I attach a release build of libssh 0.6.3 (please rename .doc to .zip). The sources are from libssh-0.6.3-762055b-pageant-support-mingw482.src.zip with a minor patch to enable libssh compile under MSVC2010. Please share that patch. When I try to generate the VS2010 project files under CMake 3.0.2, I get these 2 errors: You have called ADD_LIBRARY for library ssh_threads_shared without any source files. This typically indicates a problem with your CMakeLists.txt file CMake Error: CMake can not determine linker language for target: ssh_threads_shared I've attached the log from CMake. The 0.5.0 win32 build that includes the .lib file appears to be too old I'm not aware of the build you are referring to. It doesn't matter anymore, but I was referring to this: http://www.libssh.org/files/win32/0.5/ Which is linked to from here: http://www.libssh.org/get-it/ I get this error during compile: .\sshmasterconnection.cpp(297) : error C3861: 'ssh_channel_accept_forward': identifier not found That seems to be a missing function declaration from libssh.h. Apparently, something like ... LIBSSH_API ssh_channel ssh_channel_accept_forward(ssh_session session, int timeout_ms, int *destination_port); ... is missing. It sounds like libssh 0.5 is too old. Let's not worry about it since we have 0.6.3 working. Please let me know if the attached ssh.lib (for compiling) and ssh.dll (for runtime) are ok. They work :) I had to copy over the .h files, but that took me minimal time. Please share the aforementioned patch though. George I committed an update to the x2goclient changelog. This bug should be marked as fixed based on that commit. Also, I am keeping rough notes on how to compile X2Go Client under VS2010 here: https://docs.google.com/spreadsheets/d/1F5cVkCesXzTlo4oDJrGTdVFB074kkY-5q5-hgJUiXr4/edit?usp=sharing Think of that as the delta against the MinGW instructions: http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient -Mike Could NOT find NSIS (missing: NSIS_MAKE) Found ZLIB: C:/Users/mike.DEPAULO/Downloads/zlib128-dll/include Found OpenSSL: optimized;C:/OpenSSL-Win32/lib/VC/ssleay32MD.lib;debug;C:/OpenSSL-Win32/lib/VC/ssleay32MDd.lib;optimized;C:/OpenSSL-Win32/lib/VC/libeay32MD.lib;debug;C:/OpenSSL-Win32/lib/VC/libeay32MDd.lib Looking for include file pthread.h Looking for include file pthread.h - not found Found Threads: TRUE Could NOT find GSSAPI (missing: GSSAPI_LIBRARIES GSSAPI_INCLUDE_DIR) Could NOT find NaCl (missing: NACL_LIBRARIES NACL_INCLUDE_DIRS) Looking for argp.h Looking for argp.h - not found Looking for pty.h Looking for pty.h - not found Looking for termios.h Looking for termios.h - not found Looking for unistd.h Looking for unistd.h - not found Looking for util.h Looking for util.h - not found Looking for 3 include files winsock2.h, ..., wspiapi.h Looking for 3 include files winsock2.h, ..., wspiapi.h - found Looking for include files winsock2.h, ws2tcpip.h Looking for include files winsock2.h, ws2tcpip.h - found Looking for openssl/aes.h Looking for openssl/aes.h - found Looking for openssl/blowfish.h Looking for openssl/blowfish.h - found Looking for openssl/des.h Looking for openssl/des.h - found Looking for openssl/ecdh.h Looking for openssl/ecdh.h - found Looking for openssl/ec.h Looking for openssl/ec.h - found Looking for openssl/ecdsa.h Looking for openssl/ecdsa.h - found Looking for isblank Looking for isblank - not found Looking for strncpy Looking for strncpy - found Looking for vsnprintf Looking for vsnprintf - found Looking for snprintf Looking for snprintf - not found Looking for poll Looking for poll - not found Looking for select Looking for select - not found Looking for getaddrinfo Looking for getaddrinfo - not found Looking for ntohll Looking for ntohll - not found Looking for htonll Looking for htonll - not found Looking for _strtoui64 Looking for _strtoui64 - found Looking for _vsnprintf_s Looking for _vsnprintf_s - found Looking for _vsnprintf Looking for _vsnprintf - found Looking for _snprintf Looking for _snprintf - found Looking for _snprintf_s Looking for _snprintf_s - found Performing Test HAVE_GCC_THREAD_LOCAL_STORAGE Performing Test HAVE_GCC_THREAD_LOCAL_STORAGE - Failed Performing Test HAVE_MSC_THREAD_LOCAL_STORAGE Performing Test HAVE_MSC_THREAD_LOCAL_STORAGE - Success Performing Test HAVE_GCC_VOLATILE_MEMORY_PROTECTION Performing Test HAVE_GCC_VOLATILE_MEMORY_PROTECTION - Failed Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE) You have called ADD_LIBRARY for library
[X2Go-Dev] Bug#642: Bug#642: Bug#642: Changes in X2GoClient for Windows to enable it conform to Visual Studio's stricter type checking
On Thu, Oct 30, 2014 at 2:44 AM, George Trakatelis trakate...@uom.edu.gr wrote: ... To avoid any ambiguity I re-attach the correct patch files. ... Sorry for the delay. I will test out the patches this weekend. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#496: log output
I've attached the x2goclient (4.0.3.0-20141021-debug) log and the VcXsrv log of when this bug is triggered The X-Server command line options I am passing are shown in the .png. They are: -multiwindow -notrayicon -clipboard -logverbose 3 -logverbose 3 does not do anything. On IRC, user nkef posted a practically identical VcXsrv log: http://pastebin.com/raw.php?i=5Dj2rx5y VCXSrv.--help.log Description: Binary data VCXSrv.0.log Description: Binary data x2goclient-4.0.3.0-20141021.log Description: Binary data ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#646: PyHoca-GUI for Windows 0.5.0.0-pre02 has PyCrypto 2.6.0 with CVE-2013-1445
package: pyhoca-gui version: 0.5.0.0-pre02 NOTE: This bug is specifically about the Windows builds of PyHoca-GUI. When I built PyHoca-GUI 0.5.0.0-pre02 for for Windows, I used the latest Windows build of PyCrypto, 2.6, available here (and linked to from the wiki): http://www.voidspace.org.uk/python/modules.shtml#pycrypto Unfortunately, there is a vulnerability (CVE-2013-1445) in 2.6. 2.6.1 was released to fix it: https://github.com/dlitz/pycrypto/blob/7fd528d03b5eae58eef6fd219af5d9ac9c83fa50/ChangeLog I am attempting to find a Windows build of PyCrypto 2.6.1 for Python 2.7 32-bit. This is blocking my release of PyHoca-GUI 0.5.0.0 for Windows. if I cannot find one, I will try to build PyCrypto 2.6.1 myself. I welcome any help. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#646: Found a build!
http://blog.tkbe.org/archive/pre-compiled-binaries-for-pycrypto-2-6-1-py27-on-win7/ In case that blog ever goes down, here are the direct links and md5sums: https://www.dropbox.com/s/8kf7vrlc59bxqi3/pycrypto-2.6.1-cp27-none-win32.whl?dl=0 aa791ce84cc2713f468fcc759154f47f https://www.dropbox.com/s/nd6h6ay0z4u6u0o/pycrypto-2.6.1.win32-py2.7.exe?dl=0 1a8cec46705cc83fcd77d24b6c9d079c ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] Dang Nabbit, OpenSSL 2014-10-15 vulns and X2Go Client for Windows
On Fri, Oct 17, 2014 at 2:54 AM, Henning Heinold h.hein...@tarent.de wrote: On Thu, Oct 16, 2014 at 07:49:16PM -0400, Michael DePaulo wrote: So more OpenSSL vulnerabilities were announced yesterday: https://www.openssl.org/news/secadv_20141015.txt Also note that VcXsrv 1.16.1.0 was released on 2014-10-13. (1.16.0.0 was never released.) I will not be upgrading to that on such short notice. -Mike#2 Hi Mike, do you have access to windows 8.1? There where some reports on the irc channel that VcXsrv does not work on it. Maybe you test can if the new VcXsrv works on 8.1 again. Bye Henning Hi Henning and others, 1. I think I mentioned this on IRC. I have tested every bundled version of VcXsrv on Windows 8.1 64-bit, because that is what my primary home computer runs. I purposely did not install October 2014's Optional update, KB2995388, because it breaks VMware Workstation 10, and therefore presumably also VMware Player 6. http://blogs.vmware.com/workstation/2014/10/workstation-10-issue-recent-microsoft-windows-8-1-update.html Maybe KB2995388 is at fault for VcXsrv not working. These monthly Optional update rollups make so many changes to Windows 8.1. They are more like mini service packs. 2. FYI: I successfully tested 1.15.2.1-xp+vc2013+x2go1 on Windows XP 32-bit SP3. 3. Nightly builds of x2goclient-4.0.3.0-2014.10.18-f74084f-setup.exe with all 3 OpenSSL updates are building now. http://code.x2go.org/releases/binary-win32/x2goclient/heuler/mingw32-4.8/qt-4.8/ http://code.x2go.org/releases/binary-win32/x2goclient/heuler/mingw32-4.4/qt-4.8/ (I still intend to officially launch only the mingw32-4.8 build). -Mike ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Dang Nabbit, OpenSSL 2014-10-15 vulns and X2Go Client for Windows
So more OpenSSL vulnerabilities were announced yesterday: https://www.openssl.org/news/secadv_20141015.txt And OpenSSL 1.0.1j was released. My normal process would be Update Cygwin OpenSSL binaries and Win32 OpenSSL binaries and then re-release X2Go Client for Windows 4.0.2.1 with a new build # at the end. However, 1. We are about to release X2Go Client 4.0.3.0. 2. I recently discovered that VcXsrv also bundles a copy of OpenSSL in its source tree.[1][2] It then appears to statically link against it. I do not know exactly to what degree it uses OpenSSL, I suspect it merely uses its cryptography functions in limited ways. This would probably make it unaffected by most OpenSSL vulns, but I do not wish to do an analysis. So what I think I'll do is this: 1. Update VcXsrv's OpenSSL source code and rebuild VcXsrv. The version string will bump from 1.15.2.0-xp+vc2013+x2go1 to 1.15.2.1-xp+vc2013+x2go1. 2. Release X2Go Client 4.0.3.0 with the updated/rebuilt VcXsrv, the Updated Cygwin OpenSSL, and the updated Win32 OpenSSL. Note that we will still be bundling the very latest Cygwin packages, except for OpenSSH. I will keep Cygwin OpenSSH at 6.6.1p1-2, rather than 6.7p1-1, because there has not been enough time to test such a large change to X2Go Client for Windows. Cygwin's OpenSSH was updated on 2014-10-11. Also note that VcXsrv 1.16.1.0 was released on 2014-10-13. (1.16.0.0 was never released.) I will not be upgrading to that on such short notice. -Mike#2 [1] http://sourceforge.net/p/vcxsrv/code/ci/master/tree/openssl/ [2] http://sourceforge.net/u/mikedep333/vcxsrv/ci/xp-latestmsvc2013-x2gochanges/tree/openssl/ ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#472: Bug#472: Bug#472: Debian now has diffie-hellman-group1-sha1 disabled
On Mon, Oct 13, 2014 at 9:34 AM, Oleksandr Shneyder o.shney...@phoca-gmbh.de wrote: And why is it a problem for X2Go? Is libssh not working any more? Then it should be fixed in libssh, not in x2go? Am 11.10.2014 22:48, schrieb Mike Gabriel: Control: severity -1 important HI Alex (DEKKER), hi Alex (Schneyder), On Sa 11 Okt 2014 13:07:00 CEST, Alex DEKKER wrote: As of Version: 1:6.7p1-1 of openssh-server, it appears that Debian [and presumably upstream]'s sshd now has diffie-hellman-group1-sha1 disabled. This means that connections from x2goclient will fail. I was able to work around this by adding: KexAlgorithms curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 to /etc/ssh/sshd_config, but obviously at some point support for diffie-hellman-group1-sha1 is going to go away completely, rather than just being disabled by default. Thanks for bringing this up. Did not realize so far. @Alex Schneyder: do you think you can find a fix for this. This actually is a release blocker of 4.0.3.0... And it endangers the status of X2Go Client in Debian, as well. Mike [...] Looking through the libssh git logs, it appears that libssh 0.6 was the first version to add support for a non-sha1 key exchange method, ecdh_sha2_nistp256 [1]. 0.6 also added support for curve25519-sha...@libssh.org [1]. In a few hours or so, I will test if using a libssh 0.6.x linked version of x2goclient fixes this bug. Jessie does include libssh 0.6.3 (Thanks to our DD, Mike#1)[2]. -Mike#2 [1] http://git.libssh.org/projects/libssh.git/log/?id=libssh-0.6.0qt=grepq=sha2 [2] https://packages.debian.org/jessie/libssh-4 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#472: Another Test
On Mon, Oct 13, 2014 at 7:22 PM, Michael DePaulo mikedep...@gmail.com wrote [..] The bad news: I can confirm that X2Go Client for Windows 4.0.2.1+hotfix+build6 (and all prior versions/builds) ARE AFFECTED by this bug and ARE UNABLE to connect to a Debian Jessie server with openssh-server 6.7p1-2 (from sid) installed. Said version of X2go Client for Windows bundles and uses libssh 0.5.5. The good news: I can confirm that X2Go Client for Windows 4.0.3.0 nightly builds (mingw 4.8 tested) ARE NOT AFFECTED by this bug and ARE ABLE to connect to a Debian Jessie server with openssh-server 6.7p1-2 (from sid) installed. Said version of X2Go Client bundles and uses libssh 0.6.3. [...] -Mike#2 X2Go Client (binary package: x2goclient) 4.0.2.1-1 as it exists in Debian Jessie right now IS NOT AFFECTED. It IS ABLE to connect the aforementioned server. It is using Debian Jessie's libssh (binary package: libssh-4) 0.6.3-3+b1. Note that when you connect and perform the key exchange, ~/.ssh/known_hosts (Windows: %USERPROFILE%/ssh/known_hosts) will have a line like the following added: 192.168.1.37 ecdsa-sha2-nistp256 host-id Whereas for the old key exchange, a line like this would be added: 192.168.1.37 ssh-rsa host-id -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#566: X2Go issue (in src:x2goclient) has been marked as pending for release
Thanks! Applied. On Thu, Oct 9, 2014 at 1:20 PM, George Trakatelis trakate...@uom.edu.gr wrote: Dear Michael, With regard to bug #566 and proposed patch bug566.test.v2.patch, please review a minor addition of mine to the aforementioned patch which aids debugging of x2goclient. With bug566.test.v2.patch applied, SSH_OPTIONS_SSH_DIR is correctly set in X2GoFree for Windows but its new value is not passed to x2goDebug. Attached bug566.aid-debugging.patch corrects just that. -- George -Original Message- From: Mike DePaulo [mailto:mikedep...@gmail.com] Sent: Wednesday, September 17, 2014 2:44 PM To: 566-submit...@bugs.x2go.org Cc: cont...@bugs.x2go.org; 5...@bugs.x2go.org Subject: Bug#566: X2Go issue (in src:x2goclient) has been marked as pending for release tag #566 pending fixed #566 4.0.3.0 thanks Hello, X2Go issue #566 (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=0e3aff0 The issue will most likely be fixed in src:x2goclient (4.0.3.0). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit 0e3aff054195de9eb09e7c280aca017f9e891c10 Author: Mike DePaulo mikedep...@gmail.com Date: Wed Sep 17 07:44:07 2014 -0400 Update changelog: Last commit (2ffcad0) fixes bug #566 diff --git a/debian/changelog b/debian/changelog index a58e2b3..00ff9c3 100644 --- a/debian/changelog +++ b/debian/changelog @@ -45,7 +45,7 @@ x2goclient (4.0.3.0-0x2go1) UNRELEASED; urgency=low [ Mike DePaulo ] * New upstream release (4.0.3.0): - Windows: Fix not being able to add the server to the known_hosts file when - the username has non-English characters. + the username has non-English characters. (Fixes: #566) (NOTE: This fix only works when the non-English characters are in the same language as the Windows system locale AKA Language for non-Unicode programs. Bug #611 was written for fixing the issue for languages other ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] X2Go-WinBuilder VM disk space issue
On Thu, Sep 11, 2014 at 9:19 AM, Michael DePaulo mikedep...@gmail.com wrote: Hi Mike#1 and others, A few hours ago, the D: drive of the X2Go-WinBuilder VM had about 3GB of space free. I was installing mingw 4.8 on it (about 1GB), and was trying to clear up space, when all of a sudden it ran out of space. I am not sure why. Don't be surprised if nightly/jekins Windows builds fail for now. The builds take place on D:. I will try to clean up space when I get home at the end of today. I will use WinDirStat to find the disk usage. Also, Mike#1, if you could increase the size of virtual hard disk for drive D: that would be much appreciated. Once you do, I can go into Windows disk management and extend the NTFS partition filesystem to use the new space. You have my permission to shutdown the VM to do this. -Mike Mike#1, Last time you tried to increase the disk size, the winbuilder VM took forever to shutdown due to Windows Updates and you did not complete the task. Windows Updates will not be released until Patch Tuesday next week. Could you please increase the disk size? -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#636: Tested Successfully, 4.0.3.0 should include this
Hi Mike#1, I successfully tested both folder sharing and PulseAudio audio playback when using Dash. (I manually replaced sh.exe on my system with x2goclient for windows installed.) (woglinde suggested these 2 tests.) I expect to have the nightly Windows builds and build instructions updated within a few days. Please do not release x2goclient 4.0.3.0 until then. (We're also trying to fix #616 before 4.0.3.0 is released.) -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#616: bug 616 should be fixed before x2go client 4.0.3.0 is released
Hi Alex, Stefan and I believe that this bug (#616) should be fixed before X2Go Client 4.0.3.0 is released. Please let us know if you have any ideas on how to fix it. Mihai, Mike#1 thought you may be able to help also. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#616: bug 616 should be fixed before x2go client 4.0.3.0 is released
On Thu, Oct 9, 2014 at 7:54 AM, Oleksandr Shneyder o.shney...@phoca-gmbh.de wrote: Hi Mike, I cannot reproduce this bug. Can you? regards, Alex Am 09.10.2014 13:37, schrieb Michael DePaulo: Hi Alex, Stefan and I believe that this bug (#616) should be fixed before X2Go Client 4.0.3.0 is released. Please let us know if you have any ideas on how to fix it. Mihai, Mike#1 thought you may be able to help also. -Mike#2 Hi Alex, (Is there a reason why you did not CC others?) I cannot reproduce it either. Stefan can though. ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] Bug#630: X2Go issue (in src:x2goserver) has been marked as closed
On Tue, Oct 7, 2014 at 4:11 AM, Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: Hi Mike#2, On Di 07 Okt 2014 04:10:40 CEST, Michael DePaulo wrote: On Mon, Oct 6, 2014 at 5:29 PM, Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: close #630 thanks Hello, we are very hopeful that X2Go issue #630 reported by you has been resolved in the new release (4.0.1.18) of the X2Go source project »src:x2goserver«. You can view the complete changelog entry of src:x2goserver (4.0.1.18) below, and you can use the following link to view all the code changes between this and the last release of src:x2goserver. http://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=8af2d72466b1ea3c8bc7fc247dcbb49f61c742c3;hp=9c4a4495d84f3508674a8aa4d7b307277f31589b If you feel that the issue has not been resolved satisfyingly, feel free to reopen this bug report or submit a follow-up report with further observations described based on the new released version of src:x2goserver. Thanks a lot for contributing to X2Go!!! light+love X2Go Git Admin (on behalf of the sender of this mail) --- X2Go Component: src:x2goserver Version: 4.0.1.18-0x2go1 Status: RELEASE Date: Mon, 06 Oct 2014 22:27:42 +0200 Fixes: 630 Changes: x2goserver (4.0.1.18-0x2go1) RELEASED; urgency=medium . [ Horst Schirmeier ] * New upstream release (4.0.1.18): - Remove stale X11 lock files in cases where x2goagent mysteriously disappeared (e.g., due to kill -9 or a crash). (Fixes: #630). ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev The X2Go stable (main) PPA is still on 4.0.1.17. https://launchpad.net/~x2go/+archive/ubuntu/stable Could one of you 4 guys[1] who has permissions to update the X2Go PPA please do so? -Mike#2 [1] https://launchpad.net/~x2go/+members This normally happens within 24h after I have update the build-main branch in our Git repo. Mike [...] Gotcha. 4.0.1.18 has been available for 7 hours now :) Is this automated? ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] [X2Go-Commits] [x2goserver] 01/02: debian/control: Upgrade x2goserver-xsession from Suggests: to Recommends:.
I strongly approve of this change!
Sent from my Android Smartphone
On Oct 3, 2014 10:18 AM, git-ad...@x2go.org wrote:
This is an automated email from the git hooks/post-receive script.
x2go pushed a commit to branch release/4.0.1.x
in repository x2goserver.
commit f5b3c63c983d36e594626f470fdd5229560bfa4f
Author: Mike Gabriel mike.gabr...@das-netzwerkteam.de
Date: Fri Oct 3 15:08:56 2014 +0200
debian/control: Upgrade x2goserver-xsession from Suggests: to
Recommends:.
---
debian/changelog |2 ++
debian/control |2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/debian/changelog b/debian/changelog
index 67deb50..07afc25 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -7,6 +7,8 @@ x2goserver (4.0.1.17-0x2go1) UNRELEASED; urgency=medium
mysteriously disappeared (e.g. kill -9). (Fixes: #626).
- Make sure that incompletely started up sessions get wiped from the
session DB after 10 seconds.
+ * debian/control:
++ Upgrade x2goserver-xsession from Suggests: to Recommends:.
-- Mike Gabriel mike.gabr...@das-netzwerkteam.de Thu, 02 Oct 2014
12:18:58 +0200
diff --git a/debian/control b/debian/control
index f531e7f..2fee7cb 100644
--- a/debian/control
+++ b/debian/control
@@ -44,11 +44,11 @@ Recommends:
fontconfig,
xinit,
x2goserver-extensions (= ${source:Version}),
+ x2goserver-xsession (= ${source:Version}),
xfonts-base,
Suggests:
x2goserver-printing (= ${source:Version}),
x2goserver-compat (= ${source:Version}),
- x2goserver-xsession (= ${source:Version}),
x2goserver-fmbindings (= ${source:Version}),
x2goserver-pyhoca (= ${source:Version}),
rdesktop,
--
Alioth's /srv/git/_hooks_/post-receive-email on /srv/git/
code.x2go.org/x2goserver.git
___
x2go-commits mailing list
x2go-comm...@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-commits
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] Question about how x2goclient tells x2goserver what session type to launch
On Wed, Oct 1, 2014 at 5:52 AM, Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: Hi Michael, On Mi 01 Okt 2014 01:41:19 CEST, Michael DePaulo wrote: Ping MIke#1 I should have some free time to work on this feature this week. On Sun, Sep 14, 2014 at 9:25 AM, Michael DePaulo mikedep...@gmail.com wrote: Ping Mike#1 On Sat, Aug 16, 2014 at 11:14 AM, Michael DePaulo mikedep...@gmail.com wrote: Mike#1 (or anyone else who can answer this), You linked me to this MATE commit as an example of how I should add Cinnamon support to x2goclient (bug #571): http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=468be3aa8d457ec4bc429e76f4c26f4bbf27f0d0 I thought that x2goclient merely specified a session type with a string like MATE. So I do not understand the logic in ONMainWindow::runCommand() and SessionButton::slot_cmd_change( const QString command ), where command is changed from MATE to mate-session and then back. Furthermore, 1. pyhoca-gui doesn't do anything like that: http://code.x2go.org/gitweb?p=pyhoca-gui.git;a=commitdiff;h=af60d3076e8cb45ea8e330ff0f4405d4428c4e36;hp=a12f581df11af39c67eecc0518fbaad96b3af1bf 2. With my proposal for fixing #569, there are 3 possible commands that can be used to launch Cinnamon. -Mike With Cinnamon's fix in x2goserver for bugs #569 and #572, there are a total of 4 possible commands to launch cinnamon. The magic to launch the Cinnamon variants should go into x2goruncommand. X2Go Client should send command=CINNAMON to X2Go Server. For UNITY, the command is changed from UNITY to unity and then back. Should I just use CINNAMON and cinnamon? This is a whacky hacky magic to capture different kinds of user input... It aims at rewriting some user given command that gets entered into the command field if Other desktop session is used as session type. This, of course, fails for GNOMEv3 derived desktops as most of the gnome-like sessions require command line arguments (gnome-session arg). But in X2Go, we don't transmit command line args to x2goruncommand. So a user's custom command gnome-session args will boil down to command=GNOME. However, e.g. for MATE this mech works... The user can use MATE as custom command, but also mate-session. Everything gets rewritten to MATE before it gets sent to the server. For Cinnamon, please copy+paste+adapt your changes from what we have for GNOME or UNITY (making all of the following a valid X2Go Server command: cinnamon, CINNAMON). For other desktop shells (those that can be launched via a single command without args), please copy+paste+adapt from what I did for MATE. Thanks+Greets, Mike [...] Great, thank you! -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] How should the new desktop environments be listed in X2Go Client?
On Sun, Sep 14, 2014 at 10:45 AM, Michael DePaulo mikedep...@gmail.com wrote: Hi devs (and users), For X2Go Client (4.0.3.0): Bug #571 is to add Cinnamon Bug #607 is to add Openbox Bug #608 is to add IceWM Bug #609 is to add Trinity 1st of all, should I list them in all caps like the others? UNITY for example is actually written as Unity on its project page, but we list it on all caps. 2nd, in what order should they be listed? The current list of desktop environment sessions in X2Go Client is: KDE GNOME LXDE XFCE MATE UNITY (other types of sessions) Mike already told me to add them below UNITY, which I agree with. There are 3 reasonable orders I can think of: 1. List them in alphabetical order: Cinnamon IceWM Openbox Trinity 2. List the full desktop environments before the window managers, list them in alphabetical order: Cinnamon Trinity IceWM Openbox 3. List them in descending order of popularity (this is just my educated guess on their popularity): Cinnamon Trinity Openbox IceWM -Mike#2 I'm learning towards not listing them in all caps, and listing them in order #3. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#616: not pending
tags - pending ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#566: Bug#566: X2Go Client for Windows 4.0.2.1 cannot create C:\Users\username\ssh\known_hosts file when the local Windows account username has non-Ascii characters
On Tue, Sep 16, 2014 at 12:09 PM, George Trakatelis trakate...@uom.edu.gr wrote: Hi Mike, First of all, patch bug566.test.v2.patch definitely solves the problem as described in bug #566. I have tried successfully both the release and the debug builds you uploaded both in Windows 8.1 Pro and Windows 7 Professional SP1 with all the Microsoft updates installed. Great :) I'll update debian/changelog. That update will mark this bug as pending for release. Now, with regard to bug #397: 1st of all, you were talking about a home dir with non-Ascii characters on the client machine, correct? Yes. Bug #397 refers to when the user's home folder on the server has non-Ascii characters. That is why the bug is filed against x2goserver. Besides, our fix for #397 is not to make homedirs with non-Ascii characters work. Our fix is to present a better error message and cleanly abort the session. I see. Normally I would say that we should clone this bug (566) for X2Go Client for Linux. However, the bug report is already extremely long, I think we should just file a new one and link to this one. Could you please file one? I was only testing an analogous to bug #566 situation in Linux. To be honest, I had to get round Ubuntu's policy for POSIX user names by using usermod. That test revealed that nxproxy (in Ubuntu 14.04) crashes when path names with non-Ascii characters are used, but is it really a situation that deserves to be filed as a bug? I mean it's common for Windows users to have user names in their native language. On the other hand, Ubuntu (and I suppose Unix in general) dictates exactly what characters are permitted in a user name. If one by-passes this rule, erroneous program behavior may be observed. Can we call it a bug of the program? I don’t know. You decide! -George The way I see it, it is an issue, not a bug. You could also call it a limitation. Still, we should show the user a better error message when a home dir with non-english characters is detected on Linux. So please report a bug about it. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#566: Bug#566: X2Go Client for Windows 4.0.2.1 cannot create C:\Users\username\ssh\known_hosts file when the local Windows account username has non-Ascii characters
Hi George, See inline responses. On Tue, Sep 16, 2014 at 1:50 AM, Γεώργιος Τρακατέλης trakate...@uom.edu.gr wrote: Dear Mike, Two things. 1. Please make a preview build of X2Go Client for Windows with the patch applied and inform me when you do so. I'd rather test a complete preview package of X2Go Client 4.0.3.0 for Windows. Done: 4.0.3.0-pre01. The debug build is available too, and I manually updated the shortcuts in the debug build.[1] http://code.x2go.org/releases/binary-win32/x2goclient/previews/4.0.3.0/ I will now announce this on the mailing list. 2. Before writing this reply I had a recollection of initially having bumped onto a similar bug that was dismissed due to the fact that the submitter's system was not POSIX compliant. I searched for the bug but I couldn't find it. Then I decided to give bug #566 a try on Linux, but Ubuntu 14.04 does not allow non-Ascii characters in user names. After that, I did a more thorough search and finally found the aforementioned bug. It is bug #397! I'm wondering why that bug was filed as an x2goserver bug instead of x2goclient. Bug #397 refers to when the user's home folder on the server has non-Ascii characters. That is why the bug is filed against x2goserver. Normally I would say that we should clone this bug (566) for X2Go Client for Linux. However, the bug report is already extremely long, I think we should just file a new one and link to this one. Could you please file one? The good news: I managed to change my (linux test) home folder to /home/néstor using usermod (changing to /home/Γιώργος is impossible (Γιώργος=George in Greek)). Findings: x2goclient managed to create known_hosts but the nxproxy module failed *** longjmp causes uninitialized stack frame ***: /user/lib/nx/bin/nxproxy terminated In bug #397, Néstor gives another reason for failure Error: The remote NX proxy closed the connection. which implies x2goserver rejected the connection, so I stopped there. Could you possibly test it? (If you cannot type an é, just copy-paste néstor) -George 1st of all, you were talking about a home dir with non-Ascii characters on the client machine, correct? If so, that test is not applicable to #397 for the aforementioned reason. In order to properly test the fix for #397 on Ubuntu, we would have to build a nightly build of x2goserver 4.0.1.16 or 4.1.0.0 from source. It is not fixed in 4.0.1.15. (AFAIK, there are no automated nightly x2goserver builds for Ubuntu. Only for Debian, Fedora and EPEL.[2]) Besides, our fix for #397 is not to make homedirs with non-Ascii characters work. Our fix is to present a better error message and cleanly abort the session. -Mike#2 [1] http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient#build_x2go_client_from_source_debug_build [2] http://jenkins.x2go.org:8080/view/Server/ ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#566: Bug#566: X2Go Client for Windows 4.0.2.1 cannot create C:\Users\username\ssh\known_hosts file when the local Windows account username has non-Ascii characters
Control: severity 566 grave Dear George, Thank you for your research. Over the next day or so, I will apply bug566.test.v2.patch, which will then be included in both the MinGW 4.4 and the MinGW 4.8 nightly builds. Once you (or someone else) confirms that the patch fixes this bug for said installations, I will mark this bug as fixed. I've already cloned this bug. The clone will be for handling languages other than the Language for non-Unicode programs; i.e., using Unicode. I am marking this original bug as severity grave because it makes the package in question unusable or mostly so[1] for a significant number of users. Getting this original bug fixed for x2goclient 4.0.3.0 will be a high priority for me. Also, I tried to shorten the title of this bug (and correct a typo: cannon - cannot) but I ran into a bug with the debbugs software. I'm trying to correct the title. -Mike [1] http://bugs.x2go.org/Developer.html#severities On Mon, Sep 15, 2014 at 1:26 AM, George Trakatelis trakate...@uom.edu.gr wrote: Dear Mike, I have built libssh 0.6.3 in Visual Studio 2013 (with UNICODE and _UNICODE defined in all projects) and debugged a tiny test app with function calls analogous to those used in x2goclient. I'm afraid preprocessor definitions are not enough to make an application/program/library support Unicode. One could migrate existing programs following a list of guidelines http://msdn.microsoft.com/en-us/library/cc194801.aspx For example, a function that fails in libssh (used in ssh_path_expand_tilde(), which is always called to replace a ~ with the actual home folder path in a string) is strdup. To make libssh unicode-friendly strdup has to be replaced by _strdup http://msdn.microsoft.com/en-us/library/y471khhc.aspx _strdup would benefit from preprocessor definitions for Unicode support as it would be converted to the proper Unicode function. Imho, the only option for now is patch bug566.test.v2.patch as it corrects the problem in the vast majority of Windows installations. Remember that foreign Windows installations set by default the Language for non-Unicode programs to that particular foreign language. -George -Original Message- From: Michael DePaulo [mailto:mikedep...@gmail.com] Sent: Tuesday, September 9, 2014 4:16 PM To: 5...@bugs.x2go.org Cc: George Trakatelis; Mike Gabriel Subject: Re: [X2Go-Dev] Bug#566: X2Go Client for Windows 4.0.2.1 cannot create C:\Users\username\ssh\known_hosts file when the local Windows account username has non-Ascii characters [...] Hi Mike#1 and George, 1. I believe the best approach is to try to compile libssh with unicode support, and pass unicode values to it. There is no guarantee that a user's username (and home dir path) is in the same language as the language that is set for non-Unicode programs. After all, the Language for non-Unicode programs is called the system locale, it applies to all users on the system. If we have to for the 4.0.3.0 release of x2goclient, we should fix this bug for the system locale only, and then fix the bug for all languages/locales later. 2. See bug 474 for George's patch for compiling libssh with MinGW 4.8.2. It worked :) 3. I made some progress compiling libssh 0.6.3 with Unicode support. With MinGW 4.4, when I specified the following values in CMAKE, libssh built successfully, but it did not seem to change anything. CMAKE_EXE_LINKER_FLAGS:STRING=-municode CMAKE_MODULE_LINKER_FLAGS:STRING=-municode CMAKE_SHARED_LINKER_FLAGS:STRING=-municode CMAKE_STATIC_LINKER_FLAGS:STRING=-municode With MinGW 4.8.2, when I specify those values, libssh fails to build. I've attached the output. This is a positive sign because it implies that MinGW 4.8.2 supports -municode, whereas MinGW 4.4 did not. I plan to try to resolve this build failure later tonight. -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#566: Ding! Build is ready
George, Please test this build or later: http://code.x2go.org/releases/binary-win32/x2goclient/heuler/mingw32-4.8/qt-4.8/x2goclient-4.0.3.0-2014.09.16-2ffcad0-setup.exe -Mike#2 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
