Re: [X2Go-Dev] ATTN: Alex - Questions regarding x2goclient.exe --portable and session specification

2012-02-17 Thread Oleksandr Shneyder
Am 17.02.2012 08:53, schrieb newsgroups.ma...@stefanbaur.de:
 Am 17.02.2012 07:27, schrieb Mike Gabriel:
 Hi Stefan,

 On Fr 17 Feb 2012 01:27:57 CET newsgroups.ma...@stefanbaur.de wrote:

 Hi Alex,

 another question regarding the Windows client and its portable mode:

 Is everything in the C:Program Filesx2goclient directory
 self-contained and not relying on absolute path names by default,
 or does a truly portable install require additional pre- or
 post-install tweaks?
 In other words, can I copy/move the entire folder to another
 drive/medium (Network share, USB memory stick, CD-ROM,...) and it
 should still work?

 You could try it out and report here?!? And if your experiments fail,
 you could ask again?!? 
 
 Uh, no. Works for me when it wasn't designed for it isn't a suitable
 base for a commercial deployment. I'm not taking any chances here.
 There's just too much involved that may make it work on my system, yet
 break at the customers' sites.
 If Alex says it *should* work, from his knowedge and understanding of
 x2goclients' internal working, then I will test and report back any errors.
 
 
 Your success stories being documented in the wiki would be an awesome
 thing to occur!!!
 
 I *am* updating the wiki with information gathered re: x2goclient.exe as
 my time permits - but just as in your case, my time is limited and I
 have to prioritize some tasks over others. So before embarking on an
 hours-long testing trip, I'd like to know if it's worth my time or if
 I'm wasting it, because what I'm trying out is not supported anyway.
 
 -Stefan
 ___
 X2Go-Dev mailing list
 X2Go-Dev@lists.berlios.de
 https://lists.berlios.de/mailman/listinfo/x2go-dev

portable mode was developed for running x2goclient from flash drives or
ROM mediums without installation of x2goclient on system.

-- 
Oleksandr Shneyder
Dipl. Informatik
X2go Core Developer Team

email:  oleksandr.shney...@obviously-nice.de
web: www.obviously-nice.de

-- X2go - everywhere@home



signature.asc
Description: OpenPGP digital signature
___
X2Go-Dev mailing list
X2Go-Dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev


Re: [X2Go-Dev] New major distribution builds available for X2go

2012-02-17 Thread Oleksandr Shneyder
Am 16.02.2012 23:24, schrieb Jan Engelhardt:
 
 On Thursday 2012-02-16 09:06, Oleksandr Shneyder wrote:

 http://code.x2go.org/gitweb?p=nx-libs.git;a=commitdiff;h=07f9dfa05ab83e094e823b4af8478b25addd0fa5

 Unfortunately, this patch breaking functionality of Xinerama. It rename
 libXinerama* to libNX_Xinerama*, which make impossible for X clients to
 find a modified version of Xinerama library under
 /usr/lib/nx/X11/Xinerama and they using a system libXinerama instead.

 Simple making links
 /usr/lib/nx/X11/Xinerama/libNX_Xinerama* -
 /usr/lib/nx/X11/Xinerama/libXinerama*
 don't work, because due to new build procedure libXinerama is linked
 against libNX_Xext and libNX_X11, not libXext and libX11.
 
 I don't know about the Xinerama/ subdirectory, it does not get installed
 by nx-libs.

It is a X2Go patch. It enable support for more as one display (for
example thinclients with multihead)

 But symlinking of /usr/lib/nx/X11/libXext.so.6 to
 /usr/lib/nx/X11/libNX_Xext.so.6 should work (talking about LD_LIBRARY_PATH-
 using programs) as long as the SONAME stays NX_Xext for automatic
 dependency finding of rpm (and perhaps deb?).

It is wrong solution. Only (nx|x2go)agent should be linked against
nx-libs. X-clients should be linked against system X libraries.
Exception is libXinerama. Against this library should be linked both -
agent and client. But in case of agent libXinerama should use libXext
and libX11 from nx-libs and in case of clients it should use the same
libraries from system. For this reasons we exporting
LD_LIBRARY_PATH=/usr/lib/nx/X11 by start of agent and
LD_LIBRARY_PATH=/usr/lib/nx/X11/Xinerama (*but not /usr/lib/nx/X11*) by
start of desktop environment.

 As solution, I can suggest:

 leave libNX_Xinerama* under /usr/lib/nx/X11/
 make symbolic links /usr/lib/nx/X11/libNX_Xinerama* -
 /usr/lib/nx/X11/Xinerama/libXinerama*

 link system libraries libX11 and libXext into /usr/lib/nx/X11/Xinerama
 /usr/lib/libX11* - /usr/lib/nx/X11/Xinerama/libNX_X11*
 /usr/lib/libXext* - /usr/lib/nx/X11/Xinerama/libNX_Xext*
 
 You cannot touch my xorg-x11 libs.

I don't want to touch your xorg-x11 libs, I just want to make links from
them to /usr/lib/nx/X11/Xinerama/ :
ln -s /usr/lib/libX11.so.6 /usr/lib/nx/X11/Xinerama/libNX_X11.so.6
ln -s /usr/lib/libXext.so.6 /usr/lib/nx/X11/Xinerama/libNX_Xext.so.6

libXinerama should use a system libX11 and libXext. But because of your
patch now it linked against libNX_X11 and libNX_Xext. This is why we
should create such symbolic links.

 ___
 X2Go-Dev mailing list
 X2Go-Dev@lists.berlios.de
 https://lists.berlios.de/mailman/listinfo/x2go-dev

regards,
Alex
-- 
Oleksandr Shneyder
Dipl. Informatik
X2go Core Developer Team

email:  oleksandr.shney...@obviously-nice.de
web: www.obviously-nice.de

-- X2go - everywhere@home



signature.asc
Description: OpenPGP digital signature
___
X2Go-Dev mailing list
X2Go-Dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev


[X2Go-Dev] Font colour in x2goclient in case of dark system theme

2012-02-17 Thread Milan Knížek
Hello,

the x2goclient has hardcoded light appearance for the various widgets
(main window, session list, login window, progress of logging in),
which does not work well with dark system theme: the white font is not
distinquishable from the background.

I have checked the Qt documentation and there seems to be more ways
on how to accomplish that. So far, I have used three various methods:

  labelname-setStyleSheet(QLabel { color : black; });

or

  cpal.setColor ( QPalette::Text, Qt::black);

or

  QString fonttemplate=(font color='black'%1/font);
  nameLabel-setTextFormat ( Qt::RichText );
  nameLabel-setText ( fonttemplate.arg( text ) );

which kind of works, though it requires to be written repeatedly
throughout the code (sessionbutton.cpp, onmainwindow.cpp,
onmainwindow_part4.cpp) for individual widgets and so far I am not able
to use a single approach for all widget types (QLabel, QMenu,
QPushButton, etc.). The first method seems to be the most general and
simplest, however.

Is there a way to set application-wide font colour for anything
that appears in the widgets, but not in app menu and other windows
(Settings, Session Settings, etc.), because these are styled with the
system-wide dark theme?

Where in the code?

P.S. Sorry for possibly stupid question, but since I am not a coder, it
is rather a trial  error approach and a lot of googling...

Regards,
Milan

-- 
http://www.milan-knizek.net/
About linux and photography (Czech only)
O linuxu a fotografování
___
X2Go-Dev mailing list
X2Go-Dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev


Re: [X2Go-Dev] Font colour in x2goclient in case of dark system theme

2012-02-17 Thread John A. Sullivan III
On Fri, 2012-02-17 at 16:33 +0100, Milan Knížek wrote:
 Hello,
 
 the x2goclient has hardcoded light appearance for the various widgets
 (main window, session list, login window, progress of logging in),
 which does not work well with dark system theme: the white font is not
 distinquishable from the background.
 
 I have checked the Qt documentation and there seems to be more ways
 on how to accomplish that. So far, I have used three various methods:
 
   labelname-setStyleSheet(QLabel { color : black; });
 
 or
 
   cpal.setColor ( QPalette::Text, Qt::black);
 
 or
 
   QString fonttemplate=(font color='black'%1/font);
   nameLabel-setTextFormat ( Qt::RichText );
   nameLabel-setText ( fonttemplate.arg( text ) );
 
 which kind of works, though it requires to be written repeatedly
 throughout the code (sessionbutton.cpp, onmainwindow.cpp,
 onmainwindow_part4.cpp) for individual widgets and so far I am not able
 to use a single approach for all widget types (QLabel, QMenu,
 QPushButton, etc.). The first method seems to be the most general and
 simplest, however.
 
 Is there a way to set application-wide font colour for anything
 that appears in the widgets, but not in app menu and other windows
 (Settings, Session Settings, etc.), because these are styled with the
 system-wide dark theme?
 
 Where in the code?
 
 P.S. Sorry for possibly stupid question, but since I am not a coder, it
 is rather a trial  error approach and a lot of googling...
snip
I don't think it is stupid at all.  I have found myself sometimes
frustrated at white text boxes with no borders on white backgrounds
making it almost impossible to see where to click to enter the field.
Thanks for bringing it to the fore - John

___
X2Go-Dev mailing list
X2Go-Dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev


Re: [X2Go-Dev] X2Go bindings for Xfce and others

2012-02-17 Thread Mike Gabriel

Hi Milan,

On Do 09 Feb 2012 08:10:46 CET Milan Knížek wrote:


If you find it useful, will you add the x2gofmbinding to git?


Your idea has just been uploaded as a code x2goserver add-on package  
called x2goserver-fmbindings (after discussion with and enrolment of  
Alex this morning):

http://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=3a1746539fe58fb31aab0eb6862647d279890edf

Thanks + Keep up the good work,
Mike



--

DAS-NETZWERKTEAM
mike gabriel, dorfstr. 27, 24245 barmissen
fon: +49 (4302) 281418, fax: +49 (4302) 281419

GnuPG Key ID 0xB588399B
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

pgp2PCLgt9XSc.pgp
Description: Digitale PGP-Unterschrift
___
X2Go-Dev mailing list
X2Go-Dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev


Re: [X2Go-Dev] [PATCH] Re: x2godesktopsharing SIGSEV - how to compile with debugging info?

2012-02-17 Thread Mike Gabriel

Hi All,

On Mo 13 Feb 2012 22:10:26 CET Milan Knížek wrote:


V Sun, 12 Feb 2012 22:48:02 +0100
Milan Knížek knizek.co...@gmail.com napsáno:


Hello,

I get Segmentation fault when I right-click on x2godesktopsharing
icon in the system tray and choose Activate Desktop Sharing. (Arch
Linux.)


The segfault was due to non-existent x2godesktopsharing group in the
system.

This involves two matters:

x Arch Linux does not allow for group names longer then 16 characters.

x x2godesktopsharing should check for existence of the group and quit
nicely otherwise.

Since I am not a coder, I was able to solve only the first issue -
patches are attached. (The debian postinst script should probably
handle the original group name as well - e.g. move the members to the
new group.)

It would be nice if it is accepted upstream, since a similar limitation
might also exist on other *nix systems.


I need some feedback from the other devs how to handle this. We/I  
changed from group x2godesktopshare to x2godesktopsharing more or less  
recently, but was not aware of gid-lenght limitations in POSIX.


What do other devs think of reverting the group name change?

Mike


--

DAS-NETZWERKTEAM
mike gabriel, dorfstr. 27, 24245 barmissen
fon: +49 (4302) 281418, fax: +49 (4302) 281419

GnuPG Key ID 0xB588399B
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

pgpECOjRQf0QW.pgp
Description: Digitale PGP-Unterschrift
___
X2Go-Dev mailing list
X2Go-Dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-dev


Re: [X2Go-Dev] New major distribution builds available for X2go

2012-02-17 Thread Mike Gabriel

Hi Alex, hi Jan,

@Alex: Could you please check if my last commit on nx-libs.git fixes  
Xinerama support in with X2Go?

http://code.x2go.org/gitweb?p=nx-libs.git;a=commitdiff;h=ec47c22c264bd2f1d2ce6e434b503a701dc129f7

On Fr 17 Feb 2012 09:16:59 CET Oleksandr Shneyder wrote:


I don't want to touch your xorg-x11 libs, I just want to make links from
them to /usr/lib/nx/X11/Xinerama/ :
ln -s /usr/lib/libX11.so.6 /usr/lib/nx/X11/Xinerama/libNX_X11.so.6
ln -s /usr/lib/libXext.so.6 /usr/lib/nx/X11/Xinerama/libNX_Xext.so.6

libXinerama should use a system libX11 and libXext. But because of your
patch now it linked against libNX_X11 and libNX_Xext. This is why we
should create such symbolic links.


The below dir tree reflects what gets installed with the latest  
libnx-x11 package for Debian/Ubuntu. This installation approach  
results from the debhelper .install and .link file  
(debian/libnx-x11.install, debian/libnx-x11.links) -- not from the  
nx-X11 Makefile.


The nx-X11 Makefile still has to be tweaked to do the same. (Jan?)

Greets,
Mike

.
├── libXcomp.a
├── libXcompext.so - libXcompext.so.3.5.0
├── libXcompext.so.3 - libXcompext.so.3.5.0
├── libXcompext.so.3.5.0
├── libXcompshad.a
├── libXcompshad.so - libXcompshad.so.3.5.0
├── libXcompshad.so.3 - libXcompshad.so.3.5.0
├── libXcompshad.so.3.5.0
├── libXcomp.so - libXcomp.so.3.5.0
├── libXcomp.so.3 - libXcomp.so.3.5.0
├── libXcomp.so.3.5.0
├── nxagent
├── nxauth
├── nxproxy
└── X11
├── libNX_expat.so
├── libNX_expat.so.0 - libNX_expat.so
├── libNX_expat.so.0.4.0 - libNX_expat.so
├── libNX_fontconfig.so
├── libNX_fontconfig.so.1 - libNX_fontconfig.so
├── libNX_fontconfig.so.1.0.4 - libNX_fontconfig.so
├── libNX_fontenc.so
├── libNX_fontenc.so.1 - libNX_fontenc.so
├── libNX_fontenc.so.1.0 - libNX_fontenc.so
├── libNX_freetype.so
├── libNX_freetype.so.6 - libNX_freetype.so
├── libNX_freetype.so.6.3.7 - libNX_freetype.so
├── libNX_FS.so
├── libNX_FS.so.6 - libNX_FS.so
├── libNX_FS.so.6.0 - libNX_FS.so
├── libNX_ICE.so
├── libNX_ICE.so.6 - libNX_ICE.so
├── libNX_ICE.so.6.4 - libNX_ICE.so
├── libNX_SM.so
├── libNX_SM.so.6 - libNX_SM.so
├── libNX_SM.so.6.0 - libNX_SM.so
├── libNX_X11.so
├── libNX_X11.so.6 - libNX_X11.so
├── libNX_X11.so.6.2 - libNX_X11.so
├── libNX_Xau.so
├── libNX_Xau.so.6 - libNX_Xau.so
├── libNX_Xau.so.6.0 - libNX_Xau.so
├── libNX_Xaw.so
├── libNX_Xaw.so.7 - libNX_Xaw.so
├── libNX_Xaw.so.7.0 - libNX_Xaw.so
├── libNX_Xcomposite.so
├── libNX_Xcomposite.so.1 - libNX_Xcomposite.so
├── libNX_Xcomposite.so.1.0 - libNX_Xcomposite.so
├── libNX_Xcursor.so
├── libNX_Xcursor.so.1 - libNX_Xcursor.so
├── libNX_Xcursor.so.1.0.2 - libNX_Xcursor.so
├── libNX_Xdamage.so
├── libNX_Xdamage.so.1 - libNX_Xdamage.so
├── libNX_Xdamage.so.1.0 - libNX_Xdamage.so
├── libNX_Xdmcp.so
├── libNX_Xdmcp.so.6 - libNX_Xdmcp.so
├── libNX_Xdmcp.so.6.0 - libNX_Xdmcp.so
├── libNX_Xext.so
├── libNX_Xext.so.6 - libNX_Xext.so
├── libNX_Xext.so.6.4 - libNX_Xext.so
├── libNX_Xfixes.so
├── libNX_Xfixes.so.3 - libNX_Xfixes.so
├── libNX_Xfixes.so.3.0 - libNX_Xfixes.so
├── libNX_Xft.so
├── libNX_Xft.so.1 - libNX_Xft.so
├── libNX_Xft.so.1.1 - libNX_Xft.so
├── libNX_Xft.so.2 - libNX_Xft.so
├── libNX_Xft.so.2.1.2 - libNX_Xft.so
├── libNX_Xinerama.so
├── libNX_Xinerama.so.1 - libNX_Xinerama.so
├── libNX_Xinerama.so.1.0 - libNX_Xinerama.so
├── libNX_Xmu.so
├── libNX_Xmu.so.6 - libNX_Xmu.so
├── libNX_Xmu.so.6.2 - libNX_Xmu.so
├── libNX_Xmuu.so
├── libNX_Xmuu.so.1 - libNX_Xmuu.so
├── libNX_Xmuu.so.1.0 - libNX_Xmuu.so
├── libNX_Xpm.so
├── libNX_Xpm.so.4 - libNX_Xpm.so
├── libNX_Xpm.so.4.11 - libNX_Xpm.so
├── libNX_Xrandr.so
├── libNX_Xrandr.so.2 - libNX_Xrandr.so
├── libNX_Xrandr.so.2.0 - libNX_Xrandr.so
├── libNX_Xrender.so
├── libNX_Xrender.so.1 - libNX_Xrender.so
├── libNX_Xrender.so.1.2.2 - libNX_Xrender.so
├── libNX_Xt.so
├── libNX_Xt.so.6 - libNX_Xt.so
├── libNX_Xt.so.6.0 - libNX_Xt.so
├── libNX_Xtst.so
├── libNX_Xtst.so.6 - libNX_Xtst.so
├── libNX_Xtst.so.6.1 - libNX_Xtst.so
├── libXcomp.so
├── libXcomp.so.1 - libXcomp.so
├── libximcp.so
├── libximcp.so.2 - libximcp.so
├── libxlcDef.so
├── libxlcDef.so.2 - libxlcDef.so
├── libxlcUTF8Load.so
├── libxlcUTF8Load.so.2 - libxlcUTF8Load.so
├── libxlibi18n.so
├── libxlibi18n.so.2 - libxlibi18n.so
├── libxlocale.so
├── libxlocale.so.2 - libxlocale.so
├── libxomGeneric.so
├── libxomGeneric.so.2 - libxomGeneric.so
└── Xinerama
├── libNX_X11.so.6 - ../../../libX11.so.6
├── libNX_Xext.so.6 - ../../../libXext.so.6
├── libNX_Xinerama.so - libNX_Xinerama.so.1.0
├── libNX_Xinerama.so.1 - libNX_Xinerama.so.1.0
├── libNX_Xinerama.so.1.0
├──