x2go-commits

x2go-commits@lists.x2go.org

1 participants
37910 discussions

page changed: events:gsoc2013
by wiki-admin＠x2go.org 14 Mar '13

14 Mar '13

A page in your DokuWiki was added or changed. Here are the details: Date : 2013/03/14 20:35 Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1 IP-Address : 46.142.39.109 Hostname : 109-39-142-46.pool.kielnet.net Old Revision: http://wiki.x2go.org/doku.php/events:gsoc2013?rev=1363091657 New Revision: http://wiki.x2go.org/doku.php/events:gsoc2013 Edit Summary: [Interface between LightDM's remote login feature and X2Go Session Broker] User : sunweaver @@ -70,14 +70,8 @@ * To make the client<->broker communication more robust, this shall be changed to X2Go Client * However, transparent backward compatibility must be granted at the same time: new X2Go Clients must continue to be able to speak the older broker protocol, new X2Go Session Brokers must be able to understand old X2Go Clients * Good knowledge of Qt4 and Cplusplus are required for this task - ==== Interface between LightDM's remote login feature and X2Go Session Broker ==== - - * The remote login feature in LightDM uses UCCS for session brokerage. The UCCS is a very public service. The main caveat is: UCCS offers to store user passwords and these passwords (at time of Ubuntu 12.10 and Ubuntu 13.04) get stored in plaintext at Canonical (or at least can be easily unhashed). A site admin surely would love to have such a web portal as UCCS at hand, so that the remote login feature can be used on the local network without Canonical as the brokerage provide in the loop. - * This code project is to provide a drop-in replacement for the Ubuntu package ''lightdm-remote-session-uccsconfigure'' that replaces UCCS with the X2Go Session Broker as session brokerage provide - * The users shall then be able to use LightDM's remote login feature to launch X2Go and RDP sessions. The session profiles will be provided by the X2Go Session Broker - * Versatile skills are needed for this: C, Cplusplus, XML, JSON, Python. ==== PyHoca-PubAppDaemon - transparent X2Go Published Applications Integration into local Desktops ==== * This idea focuses on X2Go integration into Unity desktops (for providing hybrid fat/thin clients) -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: doc:installation:x2goclient
by wiki-admin＠x2go.org 14 Mar '13

14 Mar '13

A page in your DokuWiki was added or changed. Here are the details: Date : 2013/03/14 20:27 Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1 IP-Address : 46.142.39.109 Hostname : 109-39-142-46.pool.kielnet.net Old Revision: http://wiki.x2go.org/doku.php/doc:installation:x2goclient?rev=1363121153 New Revision: http://wiki.x2go.org/doku.php/doc:installation:x2goclient Edit Summary: [Fedora] User : sunweaver @@ -55,9 +55,9 @@ ===== Fedora ===== - **Warning:** This is not a supported installation. Do **NOT** expect any support from the developers of x2go, Fedora or Mandriva. + **Warning:** This is not a supported installation. Do **NOT** expect any support from the developers of X2Go, Fedora or Mandriva. There are currently no Fedora packages for X2Go, but there are packages for Mandriva. For this installation all packages were downloaded from http://www.pbone.net. - Start a terminal, go to a suitable folder, e g Download. -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: wiki:bugs
by wiki-admin＠x2go.org 14 Mar '13

14 Mar '13

A page in your DokuWiki was added or changed. Here are the details: Date : 2013/03/14 20:21 Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1 IP-Address : 46.142.39.109 Hostname : 109-39-142-46.pool.kielnet.net Old Revision: http://wiki.x2go.org/doku.php/wiki:bugs?rev=1363292473 New Revision: http://wiki.x2go.org/doku.php/wiki:bugs Edit Summary: [Open / Closed Bugs] User : sunweaver @@ -10,10 +10,10 @@ If you know either the X2Go component or the bug number you can also access the information directly: - * [[http://bugs.x2go.org/<nnn>]] (where <nnn> is the bug number) - * [[http://bugs.x2go.org/<x2go-component>]] (where <x2go-component is a valid X2Go component) + * http://bugs.x2go.org/<nnn> (where <nnn> is the bug number) + * http://bugs.x2go.org/<x2go-component> (where <x2go-component is a valid X2Go component) A complete list of X2Go components with open/closed bugs can be viewed with this URL: * [[http://bugs.x2go.org/cgi-bin/pkgindex.cgi?indexon=src]] -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: wiki:bugs
by wiki-admin＠x2go.org 14 Mar '13

14 Mar '13

A page in your DokuWiki was added or changed. Here are the details: Date : 2013/03/14 20:21 Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1 IP-Address : 46.142.39.109 Hostname : 109-39-142-46.pool.kielnet.net Old Revision: http://wiki.x2go.org/doku.php/wiki:bugs?rev=1363292427 New Revision: http://wiki.x2go.org/doku.php/wiki:bugs Edit Summary: [Open / Closed Bugs] User : sunweaver @@ -11,9 +11,9 @@ If you know either the X2Go component or the bug number you can also access the information directly: * [[http://bugs.x2go.org/<nnn>]] (where <nnn> is the bug number) - * [[http://bugs.x2go.org/<x2go-component]] (where <x2go-component is a valid X2Go component) + * [[http://bugs.x2go.org/<x2go-component>]] (where <x2go-component is a valid X2Go component) A complete list of X2Go components with open/closed bugs can be viewed with this URL: * [[http://bugs.x2go.org/cgi-bin/pkgindex.cgi?indexon=src]] -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: wiki:bugs
by wiki-admin＠x2go.org 14 Mar '13

14 Mar '13

A page in your DokuWiki was added or changed. Here are the details: Date : 2013/03/14 20:20 Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1 IP-Address : 46.142.39.109 Hostname : 109-39-142-46.pool.kielnet.net Old Revision: http://wiki.x2go.org/doku.php/wiki:bugs?rev=1363292356 New Revision: http://wiki.x2go.org/doku.php/wiki:bugs Edit Summary: [Bug submitter used a non-appropriate title] User : sunweaver @@ -104,8 +104,10 @@ </code> ==== Bug submitter used a non-appropriate title ==== + + People sometimes use inappropriate titles when submitting bugs. Also, the summarizing title of a bug can be improved, once we know what the reason for the occuring error really is. <code> To: <nnn>@bugs.x2go.org Cc: control(a)bugs.x2go.org, <nnn>-submitter(a)bugs.x2go.org -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: wiki:bugs
by wiki-admin＠x2go.org 14 Mar '13

14 Mar '13

A page in your DokuWiki was added or changed. Here are the details: Date : 2013/03/14 20:19 Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1 IP-Address : 46.142.39.109 Hostname : 109-39-142-46.pool.kielnet.net Old Revision: http://wiki.x2go.org/doku.php/wiki:bugs?rev=1363292283 New Revision: http://wiki.x2go.org/doku.php/wiki:bugs Edit Summary: User : sunweaver @@ -81,8 +81,10 @@ """ </code> ==== Bug has been reported against the wrong X2Go Component ==== + + Even for X2Go power-users and developers it is not always easy to tell, what X2Go component causes a certain buggy behaviour in X2Go. Once a problem has been narrowed down, we might need to reassign a bug to another X2Go component. <code> To: <nnn>@bugs.x2go.org Cc: control(a)bugs.x2go.org, <nnn>-submitter(a)bugs.x2go.org -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: wiki:bugs
by wiki-admin＠x2go.org 14 Mar '13

14 Mar '13

A page in your DokuWiki was added or changed. Here are the details: Date : 2013/03/14 20:18 Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1 IP-Address : 46.142.39.109 Hostname : 109-39-142-46.pool.kielnet.net Old Revision: http://wiki.x2go.org/doku.php/wiki:bugs?rev=1363292151 New Revision: http://wiki.x2go.org/doku.php/wiki:bugs Edit Summary: [New version with a bug fixed has been released] User : sunweaver @@ -59,8 +59,12 @@ """ </code> ==== New version with a bug fixed has been released ==== + + As part of the X2Go release workflow, bugs that have been fixed for this release have to be closed. Normally, most bugs are already marked (tagged) as pending. + + Some pending bugs, though, may only have been fixed on the master branch, but not yet on a release branch. If the release is taken from a release branch, take a look at the released component's changelog before closing bugs that are not yet to be closed. <code> To: <nnn>@bugs.x2go.org Cc: control(a)bugs.x2go.org, <nnn>-submitter(a)bugs.x2go.org -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: wiki:bugs
by wiki-admin＠x2go.org 14 Mar '13

14 Mar '13

A page in your DokuWiki was added or changed. Here are the details: Date : 2013/03/14 20:15 Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1 IP-Address : 46.142.39.109 Hostname : 109-39-142-46.pool.kielnet.net Old Revision: http://wiki.x2go.org/doku.php/wiki:bugs?rev=1363292086 New Revision: http://wiki.x2go.org/doku.php/wiki:bugs Edit Summary: [Bug has been fixed in X2Go Git] User : sunweaver @@ -38,8 +38,10 @@ Very common control sequence are shown below: ==== Bug has been fixed in X2Go Git ==== + + Bugs are only closed on releases of X2Go components. To mark a bug as fixed whilst it is not yet included in a release, we tag the bug as pending: <code> To: <nnn>@bugs.x2go.org Cc: control(a)bugs.x2go.org, <nnn>-submitter(a)bugs.x2go.org -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page added: wiki:bugs
by wiki-admin＠x2go.org 14 Mar '13

14 Mar '13

A page in your DokuWiki was added or changed. Here are the details: Date : 2013/03/14 20:14 Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1 IP-Address : 46.142.39.109 Hostname : 109-39-142-46.pool.kielnet.net Old Revision: --- New Revision: http://wiki.x2go.org/doku.php/wiki:bugs Edit Summary: created User : sunweaver ====== X2Go Bug Tracker ====== The X2Go project uses the ''debbugs'' as bug tracking system (BTS) software. The ''debbugs'' tracker is the software that's also used by the Debian project for tracking issues in the multitude of Debian packages. Before X2Go had a bug tracker, the quest was: we need a BTS that is easily scriptable and a BTS that fully maps issue tracking to the developers' mail clients. Furthermore, we did not want a bug tracker that could be fed with content by clicking around on a web page. The choice has been well thought of, you may find that there are better bug tracking systems in the world. For X2Go, we think we have found what we wanted. ===== Open / Closed Bugs ===== If you know either the X2Go component or the bug number you can also access the information directly: * [[http://bugs.x2go.org/<nnn>]] (where <nnn> is the bug number) * [[http://bugs.x2go.org/<x2go-component]] (where <x2go-component is a valid X2Go component) A complete list of X2Go components with open/closed bugs can be viewed with this URL: * [[http://bugs.x2go.org/cgi-bin/pkgindex.cgi?indexon=src]] ===== Reporting Bugs ===== How to report a bug is explained [[http://bugs.x2go.org/Reporting.html|here]] In a nutshell send a mail like the one below (everything that is written in <pointed-brackets> needs being replaced by some proper value. <code> To: submit(a)bugs.x2go.org Subject: <a-really-good-short-description-of-the-problem> Body: """ Package: <name-of-x2go-component> Version: <a.b.c.d> """ </code> ===== Controlling Bugs ===== The full control command set is documented [[http://bugs.x2go.org/server-control.html|here]] Very common control sequence are shown below: ==== Bug has been fixed in X2Go Git ==== <code> To: <nnn>@bugs.x2go.org Cc: control(a)bugs.x2go.org, <nnn>-submitter(a)bugs.x2go.org Subject: Issue resolved in X2Go Git Body: """ tag #<nnn> pending thanks The reported issue has been resolved with this commit: <http-URL-to-Gitweb-of-commitdiff> Thanks, <my-name> """ </code> ==== New version with a bug fixed has been released ==== <code> To: <nnn>@bugs.x2go.org Cc: control(a)bugs.x2go.org, <nnn>-submitter(a)bugs.x2go.org Subject: Issue resolved in <x2go-component> <version> Body: """ close #<nnn> thanks The reported issue has been resolved in the lately release version <version> of <x2go-component>. Thanks for reporting this issue, <my-name> """ </code> ==== Bug has been reported against the wrong X2Go Component ==== <code> To: <nnn>@bugs.x2go.org Cc: control(a)bugs.x2go.org, <nnn>-submitter(a)bugs.x2go.org Subject: <a-good-subject-line> Body: """ reassign #<nnn> <another-x2go-component> thanks The reported issue is actually a bug in <another-x2go-component>. Reassigning. <further-info-if-any> Thanks for reporting this issue, <my-name> """ </code> ==== Bug submitter used a non-appropriate title ==== <code> To: <nnn>@bugs.x2go.org Cc: control(a)bugs.x2go.org, <nnn>-submitter(a)bugs.x2go.org Subject: <a-good-subject-line> Body: """ retitle #<nnn> <better-title> thanks <further-info-if-any> Thanks for reporting this issue, <my-name> """ </code> -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

page changed: usage:x2goclient
by wiki-admin＠x2go.org 13 Mar '13

13 Mar '13

A page in your DokuWiki was added or changed. Here are the details: Date : 2013/03/13 22:55 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.152 Safari/537.22 IP-Address : 46.59.161.206 Hostname : port-27460.pppoe.wtnet.de Old Revision: http://wiki.x2go.org/doku.php/usage:x2goclient?rev=1363215171 New Revision: http://wiki.x2go.org/doku.php/usage:x2goclient Edit Summary: [Getting started (my first Session Profile)] User : kjellski @@ -18,15 +18,42 @@ After the [[doc:installation:x2goclient | installation]] of ''x2goclient'' an application link can be found in the menu of your Desktop Environment. On GNU/Linux systems it will be integrated into the ''Internet'' menu section. ===== Getting started (my first Session Profile) ===== + When you launch the ''x2goclient'' for the first time, it will start the ''new session'' dialogue automatically. - When you launch the ''x2goclient'' for the first time, it will start the ''new session'' dialogue automatically. On the first tab, fill out the ''Session Name'', type the IP of the host in the ''Host'' and add your username to the ''Login'' field. If you use a non-standard ssh port on your host, change that as well, in the ''SSH Port'' field. + When you open the graphical user interface of the x2goclient, you'll be welcomed with a form to fill in your session details. The x2goclient manages sessions for each server you want to connect to. You can make settings for each one, and we'll go through the first together. - Moving down to the ''Session Type'' field, select your desktop environment. If your environment is not on the list, use the "Custom Desktop" option, and specify the command that starts the desktop or VM. + * At first you'll choose a name for you session. Choose something catchy, like "work-serverroom" or "home-garage". + * Then you'll need to enter how the server can be reached. You can enter an IP or a name for the host. If you choose a name, make sure it's resolvable from where you'll use the client. + * Now set the username with which you are able to connect to the server. The user must have the right to log in to the server by SSH. + * You can change the port for the server, but most probably it's the default SSH port, 22. + * Now you can set, if you want to use RSA or DSA Keys, which one to use. For example: "/home/x2gouser/.ssh/id_rsa" + * You could also just use a ssh-agent if you've got that available. + * There is also the availability to use a proxy to connect to the x2goserver for which you could provide a set of different credentials and key to authenticate against. + * The ''Session Type'' field is used to select your desktop environment. If your environment is not on the list, use the "Custom Desktop" option, and specify the command that starts the desktop or VM on the remote side. You can also use a specific application provided by the remote side. - Lastly, if you are using something other than a US keyboard, go to the ''Settings'' tab, and specify the keyboard layout there. Click Ok and start your session by selecting it on the main window. + The next Tab shows your connection settings: + + * You can adjust the bandwidth you have to be used by the x2goclient. + * Also there is an option to actively adjust the compression methods for the image processing. + + + On the Settings tab you will be able to adjust your clients configuration for convenient day-to-day usage: + + * A whole set of Display settings can be used to configure the display for this session permanently. + * You can set the exact keyboard layout and the language to be used for it. + * The audio settings enable you to use the remote audio system locally and hear what would normally be heard on the remote side. + * The last point in this tab enables the client side printing support to let you print locally from the remote side. + + + The last Tab for the session preferences is used to configure the folder sharing options: + + * You can use the x2goclient to share folders between the local client and the remote side you will connect to. This enables you to share documents and files between both sides. + + + We now went through all the settings available to the specific session. Press okay to save it and you'll see it on the main window, in the session list. ===== Configure Client Settings ===== FIXME -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

x2go-commits