[X2Go-Dev] Bug#1208: Bug#1208: Bug#1208: Messed up session when resuming from Published Apps mode to Fullscreen desktop mode in thinclient mode
Am 25.09.2017 um 15:24 schrieb Ulrich Sibiller: >>> Let's say you suspended a session in "Published Apps" mode from a local >>> desktop (might be Linux or Windows, it doesn't matter) then try to resume >>> it from a TCE running the client in thinclient mode. >>> This will work, you can resume the session but the display is completely >>> broken : no desktop, no decorations, corrupted display and no widget to >>> logoff so you're stuck there unless someone kills your session from the >>> server. >>> >>> It would be better to simply block the ability to resume a Published Apps >>> session in a mode where it just can't be done such as the thinclient mode. >> The question is: How do we handle that? >> --no-public-applications as a commandline option? We could hardcode that >> into an X2Go-TCE-startup script then. > No, that should work automatically. As long as there's a window > manager on the client side everything will work fine. > And that's easily checkable by x2goclient. Wait a minute - we are running a Display Manager in X2Go-TCE ... in the live edition at least. So Window decorations should be there, just no task bar. Walid - did you change anything in your TCE setup compared to X2Go-TCE-Live, branch "feature/openbox"? What SHOULD happen is that X2GoClient starts up in fullscreen, but any popup it shows (like asking for a keyfile's password, or displaying that there's no route to host) should have window decorations. And I'd assume that the same window manager would put window decorations around PubApp windows once the session resumes. (Of course, it will still be almost unusable, as there's no task bar, no logoff button, and no menu, but I'm surprised to hear that there are no window decorations.) -Stefan -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 signature.asc Description: OpenPGP digital signature ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#1208: Bug#1208: Bug#1208: Messed up session when resuming from Published Apps mode to Fullscreen desktop mode in thinclient mode
On Mon, Sep 25, 2017 at 2:51 PM, Stefan Baur wrote: > Am 23.09.2017 um 22:25 schrieb Walid MOGHRABI: > >> Let's say you suspended a session in "Published Apps" mode from a local >> desktop (might be Linux or Windows, it doesn't matter) then try to resume it >> from a TCE running the client in thinclient mode. >> This will work, you can resume the session but the display is completely >> broken : no desktop, no decorations, corrupted display and no widget to >> logoff so you're stuck there unless someone kills your session from the >> server. >> >> It would be better to simply block the ability to resume a Published Apps >> session in a mode where it just can't be done such as the thinclient mode. > > The question is: How do we handle that? > --no-public-applications as a commandline option? We could hardcode that > into an X2Go-TCE-startup script then. No, that should work automatically. As long as there's a window manager on the client side everything will work fine. And that's easily checkable by x2goclient. Uli ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#1219: Bug: After Session starts on server&client, message appers on client: "The remote proxy closed the connection while negotiating the session. This may be due to the wrong authentic
Package: x2goserver Version: 4.0.1.20 I guess it's the x2goserver package that has the bug?? I don't know about what package precisely!... ***How to Reproduce the bug:*** Install, following the correct and proper instructions, the x2goclient and the x2goserver on respectively your client and your server. (My client is Kali Linux 2017 latest version) (My server is a Raspberry Pi Version 3) Once the server packages are correctly installed in the server, and once the client package(s) is correctly installed in the client: open your x2go client by issuing "x2goclient" in your terminal (my client terminal is root, so I actually issue the command to open the client as root, but I don't get any kind of problem) create a new session with the correct details, and select LXDE protocol. (My rpi3 has lxde package installed and correctly working) Keep in mind the rpi is booted on the cli environment, that's why I'm using the LXDE protocol. Ok then start the connection (after insterting the proper password) Status "connecting" will show up in the x2go client. wait a few minutes and a window from the x2go client will pop up saying: "The remote proxy closed the connection while negotiating the session. This may be due to the wrong authentication credentials passed to the server." Looking at the logs at /var/log/syslog on the x2go server, the output is: root@myrpithree:~# tail -f /var/log/syslog | grep x2go Sep 24 14:11:56 myrpithree /usr/sbin/x2gocleansessions[3591]: myrpithree-50-1506280314_stDLXDE_dp24: state file for this session does not exist: /tmp/.x2go-myrpithree/C-myrpithree-50-1506280314_stDLXDE_dp24/state (this can be ignored during session startups) Sep 24 14:12:00 myrpithree /usr/sbin/x2gocleansessions[3591]: myrpithree-50-1506280314_stDLXDE_dp24: state file for this session does not exist: /tmp/.x2go-myrpithree/C-myrpithree-50-1506280314_stDLXDE_dp24/state (this can be ignored during session startups) Sep 24 14:12:03 myrpithree /usr/sbin/x2gocleansessions[3591]: myrpithree-50-1506280314_stDLXDE_dp24: state file for this session does not exist: /tmp/.x2go-myrpithree/C-myrpithree-50-1506280314_stDLXDE_dp24/state (this can be ignored during session startups) Sep 24 14:12:40 myrpithree /usr/bin/x2gostartagent: successfully started X2Go agent session with ID myrpithree-50-1506280314_stDLXDE_dp24 ^C The session has been successfully started, however I still get that boring message on the client and thus I do not get the RDP window (meanwhile the connection is still on both in the server and in the client, in fact if I try once again the the client it will say that the previous connection is still on.)! I've see this bug is around for quite some years, ANY TEMPORARY SOLUTION PLEASE? DO YOU WANT ME TO POST MORE OUTPUTS OR SOMETHING? PLEASE LET ME KNOW. - ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options! ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#1208: Bug#1208: Messed up session when resuming from Published Apps mode to Fullscreen desktop mode in thinclient mode
Am 23.09.2017 um 22:25 schrieb Walid MOGHRABI: > Let's say you suspended a session in "Published Apps" mode from a local > desktop (might be Linux or Windows, it doesn't matter) then try to resume it > from a TCE running the client in thinclient mode. > This will work, you can resume the session but the display is completely > broken : no desktop, no decorations, corrupted display and no widget to > logoff so you're stuck there unless someone kills your session from the > server. > > It would be better to simply block the ability to resume a Published Apps > session in a mode where it just can't be done such as the thinclient mode. The question is: How do we handle that? --no-public-applications as a commandline option? We could hardcode that into an X2Go-TCE-startup script then. -Stefan -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 signature.asc Description: OpenPGP digital signature ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#1218: Bug#1218: Improve User Experience when connecting to a session that is supposed to use agent-cached credentials or a keyfile
I suggest to grey out the password field and change the "ok" button to "reconnect" On Mon, Sep 25, 2017 at 11:46 AM, Stefan Baur wrote: > package: x2goclient > priority: wishlist > > Whe an X2Go session is set to use agent-cached credentials or a keyfile, > clicking on the session tile will automatically start a connection > (unless a keyfile is used and it is password-protected - in that case, a > small pop-up is shown that asks for the keyfile's password). > > If the connection is suspended - be it by a user-initiated suspend > command or due to loss of connection - X2GoClient shows the same > login/password dialog that is shown on initial connect for a session > that is not set up to use agent-cached credentials or a keyfile. > > This is confusing to the user - as simply clicking "OK" without using > the password field is enough to reconnect. There's no need to show an > editable user name field and a password entry field. > > Suggested change: > When the client detects a connection loss/suspend, it should return to > its default "select a tile" screen, if the session was using > agent-cached credentials or a keyfile. > If logging in with the agent-cached credentials/keyfile does not work, a > popup similar to the one asking for the keyfile password should appear, > only with a different visual design and textual description, so users > have a chance to understand they are being prompted for the login > password, rather than the keyfile password. > > -- > BAUR-ITCS UG (haftungsbeschränkt) > Geschäftsführer: Stefan Baur > Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 > Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 > > > ___ > x2go-dev mailing list > x2go-dev@lists.x2go.org > https://lists.x2go.org/listinfo/x2go-dev ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#1218: Improve User Experience when connecting to a session that is supposed to use agent-cached credentials or a keyfile
package: x2goclient priority: wishlist Whe an X2Go session is set to use agent-cached credentials or a keyfile, clicking on the session tile will automatically start a connection (unless a keyfile is used and it is password-protected - in that case, a small pop-up is shown that asks for the keyfile's password). If the connection is suspended - be it by a user-initiated suspend command or due to loss of connection - X2GoClient shows the same login/password dialog that is shown on initial connect for a session that is not set up to use agent-cached credentials or a keyfile. This is confusing to the user - as simply clicking "OK" without using the password field is enough to reconnect. There's no need to show an editable user name field and a password entry field. Suggested change: When the client detects a connection loss/suspend, it should return to its default "select a tile" screen, if the session was using agent-cached credentials or a keyfile. If logging in with the agent-cached credentials/keyfile does not work, a popup similar to the one asking for the keyfile password should appear, only with a different visual design and textual description, so users have a chance to understand they are being prompted for the login password, rather than the keyfile password. -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 signature.asc Description: OpenPGP digital signature ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#1217: X2GoClient does not auto-resume sessions in public application mode
package: x2goclient X2Goclient is supposed to auto-resume a suspended session if the following conditions are all met: - The session settings provided by X2GoClient upon connect match the session settings of the suspended session, AND - There is exactly one suspended session with matching settings, AND - X2GoClient was NOT started with --no-autoresume However, this fails for sessions of the "published application" type, and the reconnect session chooser popup is shown. Desktop sessions and single application sessions are not affected. -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 signature.asc Description: OpenPGP digital signature ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#1216: Issue with minimizing X2GoClient via minimize button in window decoration (Windows)
package: x2goclient With "Display icon in system tray" and all of its sub-checkboxes checked, x2goclient is supposed to minimize to the system tray. It correctly does so when a connection starts, but an error occurs if one tries to minimize the application manually using the minimize button in the window decoration. Expected behavior: X2GoClient only displays a tray icon. Actual behavior: While the tray icon remains, X2GoClient momentarily vanishes from the task bar, only to return to the task bar a fraction of a second later. Clicking on that task bar entry pops up a "wireframe" of the X2GoClient window with no content. Content only becomes visible once you right-click the tray icon and select "Restore". -Stefan -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 signature.asc Description: OpenPGP digital signature ___ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
