Dear all,
The X2Go Project is proud to announce a couple of new X2Go component releases:
- x2goserver (3.1.1.4)
- cups-x2go (3.0.0.4)
- x2goplasmabindings (with plasma-widget-x2go, 3.0.1.4)
- python-x2go (0.2.0.10)
All new packages will be available in our stable repositories (Debian,
Ubuntu) within the next 24h.
In the past months we skipped some minor announcements of release that
were related to inclusion of some X2Go components in Debian (being
available wheezy, partly in jessie).
In the new X2Go Server release several issues got addressed:
o Audio support (pulseaudio) with X2Go-proxied RDP sessions
o Media support (client-side shared folders) for X2Go-proxied RDP sessions
o XDCMP session type fixed
o Fix KWin crashes on Kubuntu 12.04 (sponsored by Rohloff AG, thanks
Mirco!!!)
o Fix Xinerama with x2goserver-xsession package installed (also:
thanks Mirco)
In cups-x2go Helmer Teles provided us with a patch that now allows to
specify the number of copies in a print job. Thanks to Helmer for that.
In Python X2Go we fixed these issues:
o Colour depth issues on Windows Clients (16 vs 17 bit) o Keyboard focus in X2Go-proxied RDP session against Windows 7 / 2008 o Fix session crashes due to left over bash-like commands o Prepare for DirectRDP session options...
A Windows version of PyHoca-GUI with latest Python X2Go in it will be
deferred till the release of PyHoca-GUI 0.2.0.5 (due in a couple of
weeks, I guess).
In the Plasma widget for X2Go we adapted the code to become aware of
the modified mount points for SSHfs shares (introduced with X2Go
Server 3.1.1.2).
light+love, Mike
x2goserver (3.1.1.4-0~x2go1) unstable; urgency=low
[ Jan Engelhardt ]
- New upstream version (3.1.1.4):
- Add -pie as linker flag. Fixes non-position-independent-executable (x2gosqlitewrapper.c). The executable is now completely position independent.
[ Mike Gabriel ]
- New upstream version (3.1.1.4):
- Fix x2gosessionlimit script.
- Wrap padsp around rdesktop calls if pulse is used as audio protocol.
- Add option ,,-r sound:local'' to rdesktop calls if pulse is enabled.
- Proxy X2Go client-side shares into remote desktop session.
- For applications inside of a session, use NX's Xrandr library instead of Xorg's Xrandr library (partially closes #28).
- Make sure when launching desktop session through the Xsession mechanism that the LD_LIBRARY_PATH variable stays intact. Closes #29.
- Only extend LD_LIBRARY_PATH by Xrandr extension for KDE. Breaks GNOME.
- /debian/control:
- Maintainer change in package: X2Go Developers
<x2go-dev@lists.berlios.de>. - Depend on nx-libs (>=3.5.0.15-0~) which has the Xrandr symlinks folder.
- Add rdesktop and pulseaudio-utils to Suggests.
- Priority: optional.
- Maintainer change in package: X2Go Developers
[ Oleksandr Shneyder ]
- New upstream version (3.1.1.4):
- Remove "-nolisten tcp" option with XDMCP sessions.
-- Mike Gabriel <mike.gabriel@das-netzwerkteam.de> Tue, 25 Sep 2012 13:15:11 +0200
cups-x2go (3.0.0.4-0~x2go1) unstable; urgency=low
[ Mike Gabriel ]
- New upstream version (3.0.0.4):
- Add more debug messages.
- Use proper project name where appropriate and possible (,,X2Go'').
- Maintainer change in package: X2Go Developers <x2go-dev@lists.berlios.de>.
[ Helmer Teles ]
- New upstream version (3.0.0.4):
- Fix ignoring number of copies to be printed for single pages.
-- Mike Gabriel <mike.gabriel@das-netzwerkteam.de> Tue, 25 Sep 2012 15:59:04 +0200
python-x2go (0.2.0.10-0~x2go1) unstable; urgency=low
- New upstream version (0.2.0.10):
- Use session type 'D' for X2Go-proxied RDP session when run in fullscreen mode. Fixes upstream issue #27.
- Indentation fix in defaults.py.
- Make Python X2Go aware of DirectRDP settings in session profiles.
- Ignore DirectRDP options in session profile config for now.
- Remove bashism from X2Go server command calls. Caused servers with no installed x2goserver-xsession package to crash desktop sessions (observed with KDE4 on Ubuntu 12.04).
- Handle 16bit and 17bit colour depth (Windows clients) as equal when resuming sessions.
- Maintainer change in package: X2Go Developers <x2go-dev@lists.berlios.de>.
-- Mike Gabriel <mike.gabriel@das-netzwerkteam.de> Tue, 25 Sep 2012 16:03:24 +0200
x2goplasmabindings (3.0.1.4-0~x2go1) unstable; urgency=low
- New upstream version (3.0.1.4):
- Fix version file.
-- Mike Gabriel <mike.gabriel@das-netzwerkteam.de> Tue, 25 Sep 2012 15:53:38 +0200
x2goplasmabindings (3.0.1.3-0~x2go1) unstable; urgency=low
- New upstream version (3.0.1.3):
- Make plasme-widget-x2go of new mount points of spool and mimebox share.
- Make plasma-widget-x2go aware of new path names in x2goserver (>= 3.1.1.3).
- /debian/control:
- Maintainer change in package: X2Go Developers
<x2go-dev@lists.berlios.de>. - Priorty: optional.
- Depend on x2goserver >= 3.1.1.2.
- Maintainer change in package: X2Go Developers
-- Mike Gabriel <mike.gabriel@das-netzwerkteam.de> Tue, 25 Sep 2012 15:48:05 +0200
--
DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Tuesday 2012-09-25 20:35, Mike Gabriel wrote:
The X2Go Project is proud to announce a couple of new X2Go component releases:
- x2goserver (3.1.1.4)
- cups-x2go (3.0.0.4)
- x2goplasmabindings (with plasma-widget-x2go, 3.0.1.4)
- python-x2go (0.2.0.10)
All new packages will be available in our stable repositories (Debian, Ubuntu) within the next 24h.
Does the delay also apply to the plain tarballs? (There's no cups-x2go update in http://code.x2go.org/releases/source/?C=M;O=D yet)
Hi Jan,
On Mi 26 Sep 2012 09:02:17 CEST Jan Engelhardt wrote:
On Tuesday 2012-09-25 20:35, Mike Gabriel wrote:
The X2Go Project is proud to announce a couple of new X2Go
component releases:
- x2goserver (3.1.1.4)
- cups-x2go (3.0.0.4)
- x2goplasmabindings (with plasma-widget-x2go, 3.0.1.4)
- python-x2go (0.2.0.10)
All new packages will be available in our stable repositories (Debian, Ubuntu) within the next 24h.
Does the delay also apply to the plain tarballs? (There's no cups-x2go update in http://code.x2go.org/releases/source/?C=M;O=D yet)
Sorry, forgot to sync cups-x2go and python-x2go tarball after tagging
and announcing the releases.
Now synced. Mike
--
DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Am 25.09.2012 20:35, schrieb Mike Gabriel:
Dear all,
The X2Go Project is proud to announce a couple of new X2Go component releases:
- x2goserver (3.1.1.4)
- cups-x2go (3.0.0.4) <snip>
Roughly 75%, if not more, of my servers required manual intervention during that upgrade, prompting me to confirm this:
Setting up cups-x2go (3.0.0.4-0~x2go1+squeeze~main~62~build1) ...
Configuration file `/etc/cups/cups-x2go.conf' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** cups-x2go.conf (Y/I/N/O/D/Z) [default=N] ?
What's strange about this is that the machines were are built using the same automated installation script, so these kind of failures should show up either on all or none.
Also, I don't remember deleting that file on any of these machines. So, if it has always been part of the package, it should always have been there.
On the other hand, if it was introduced at a later date (which would explain why not all of my machines are complaining; the newer ones might already have it), the upgrade script shouldn't complain that it expected a previous version to be there.
Does anyone know what might have caused this?
-Stefan
Hi Stéphane,
On Mi 26 Sep 2012 09:15:23 CEST Stefan Baur wrote:
Am 25.09.2012 20:35, schrieb Mike Gabriel:
Dear all,
The X2Go Project is proud to announce a couple of new X2Go component releases:
- x2goserver (3.1.1.4)
- cups-x2go (3.0.0.4) <snip>
Roughly 75%, if not more, of my servers required manual intervention
during that upgrade, prompting me to confirm this:Setting up cups-x2go (3.0.0.4-0~x2go1+squeeze~main~62~build1) ...
Configuration file `/etc/cups/cups-x2go.conf' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** cups-x2go.conf (Y/I/N/O/D/Z) [default=N] ?
What's strange about this is that the machines were are built using
the same automated installation script, so these kind of failures
should show up either on all or none.Also, I don't remember deleting that file on any of these machines. So, if it has always been part of the package, it should always have
been there.On the other hand, if it was introduced at a later date (which would
explain why not all of my machines are complaining; the newer ones
might already have it), the upgrade script shouldn't complain that
it expected a previous version to be there.Does anyone know what might have caused this?
/etc/cups/cups-x2go.conf has been there for a while...
The commit that changed that conffile is this: http://code.x2go.org/gitweb?p=cups-x2go.git;a=commitdiff;h=86e725ac8e514d40a...
Accepting that change is recommended. Why it occurred on some machines
and not on others, I do not know.
May be (just an idea)... The release of cups-x2go has been overdue and
the modification to cups-x2go.conf has been in Git (and so in the
nightly built packages) for quite a while (half a year apprx.). May it
be possible that some of your servers had been set up from the nightly
built package archive (ppa:x2go/ppa) within the last half year and
some other had been installed from the stable PPA (ppa:x2go/stable)?
Those installed from the nightly builds would have been silent during
upgrade, the others not...
Just guessing, Mike
--
DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Hi again,
On Mi 26 Sep 2012 09:26:40 CEST Mike Gabriel wrote:
Hi Stéphane,
Sorry, I got entangled with names here... I only realized that it
Stefan who asked the below question, not Stéphane.
However, my below answer also applies to nightly and stable builds for Debian.
Does anyone know what might have caused this?
/etc/cups/cups-x2go.conf has been there for a while...
The commit that changed that conffile is this: http://code.x2go.org/gitweb?p=cups-x2go.git;a=commitdiff;h=86e725ac8e514d40a...
Accepting that change is recommended. Why it occurred on some
machines and not on others, I do not know.May be (just an idea)... The release of cups-x2go has been overdue
and the modification to cups-x2go.conf has been in Git (and so in
the nightly built packages) for quite a while (half a year apprx.).
May it be possible that some of your servers had been set up from
the nightly built package archive (ppa:x2go/ppa) within the last
half year and some other had been installed from the stable PPA
(ppa:x2go/stable)? Those installed from the nightly builds would
have been silent during upgrade, the others not...Just guessing, Mike
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
-
Jan Engelhardt -
Mike Gabriel -
Stefan Baur