Device Redirection fails in XRDP Version 0.9.5 [ when enable-printing is true ]

2018-03-08 Thread Amarjeet Singh
Hi Team,


I am using Guacamole [ Latest version from GIT ] for RDP.

XRDP Version : 0.9.5
Ubuntu : 16.0.4
Local Operating System : Windows 10
Browser : Chrome

When I pass the parameter *enable-printing* to *true *then Device
Redirection fails in Ubuntu 16.0.4

Expected output : Folder GUAC redirects to the Ubuntu *thinclient_drives* and
Download folder inside the GUAC folder.

Actual Output : Folder GUAC redirects  to the Ubuntu *thinclient_drives *but
When I click on that folder it shows loading and there is no Download
folder .

When I don't pass the parameter enable-printing then Device redirection
doesn't fails and works as expected.


Thanks and Regards,
Amarjeet Singh


RE: Login screen issues

2018-03-08 Thread harry.devine
What is the screen supposed to look like?  I made the change in my 
login-override.css in my extension as follows:

div.login-ui {
  position: absolute;
}

The screen looks exactly the same to me.  Should I put all of the CSS 
properties into my override?  And was this supposed to either swap the banner 
and login controls, or put them side-by-side?

Thanks,
Harry

From: Mike Jumper [mailto:mike.jum...@guac-dev.org]
Sent: Wednesday, March 07, 2018 4:24 PM
To: user@guacamole.apache.org
Subject: Re: Login screen issues

On Wed, Mar 7, 2018 at 6:42 AM, 
> wrote:
We have our security banner implemented on the log in screen as seen below.  
One of our users is complaining that the login username and password boxes are 
not visible and there are no scroll bars.  How can I either swap the login area 
and have the security banner on the bottom, or possibly have them side by side?

There were recent changes which should allow the login interface to scroll, 
added as part of the TOTP changes:

https://github.com/apache/guacamole-client/commit/a426f59765471adb72dc011a56b50d9c403d4ab4

Can you see whether this is still an issue with a recent build of 
guacamole-client from git? If the above solves the problem, you can work around 
the issue for the time being by including the same CSS rule within your 
extension (assuming you are using an extension to add that warning text).

- Mike