Apache Guacamole XRDP desktop shows sometimes blurry - guacamole

I'm using Apache Guacamole 1.2.0 and XRDP 0.9.12 on Ubuntu 20.04.
When looking at the remote desktop the fonts are shown sometimes reasonably sharp (alas still less than when opening an RDP connection directly), but often become blurry/blocky, as shown in the following screenshot.
It's possible to "provoke" this by letting the browser window loosing the input focus. But it also happens while working on the remote desktop. By triggerings repaints (e.g. by going with the mouse over the text) the fonts become sharp again at the repainted screen regions while staying blurry at the other screen regions.
The RDP connection settings in Guacamole are configured like this:
I played a bit with the font smoothing and caching options, but could not improve the situation.
Is there any way to keep the fonts from "going blurry"?
Best regards,
Bernd

I reinstalled with compiled versions xrdp 0.9.14 and xorgxrdp 0.2.14 - I had to do this anyway, because file sharing does not work between Guacamole and xrdp 0.9.12.
As a "side effect", the blocky/blurry appearance is gone now, too.
Either it has been fixed with the newer version or my old installation was somehow faulty.

Related

Microsoft Edge Chromium and an App-V'ed plugin

I'm experiencing the combination of a locally installed Microsoft Edge Chromium Enterprise Edition and Microsoft App-V. I try to App-V a browser plugin for a locally installed Microsoft Edge Chrome Enterprise.
I have an App-V bubble and Internet Explorer is started with this bubble in the background using the /appvve command-line option.
My first suggestion was:
Replace the file path to iexplore.exe to the new file path of msedge.exe, eg.
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --site-per-process -url https://www.website.com /appvve:[App-V PackageID]_[App-V PackageVersionID]
This works only when MS Edge has no running instances already.
The --site-per-process option should help isolate the process of Edge Chromium.
When Microsoft Edge is already opened, there is some magic: the bubble is active for some seconds and after that the App-V bubble is closed.
ProcessExplorer of SysInternals does a great work: it tells me a secondary process of Edge Chromium is started with the bubble on the background.
Then the subprocesses of the secundary started instance are brought to the primaraly started instance and when this all is done, the secondary started instance - including the App-V bubble - is closed.
The webpage is opened, but the connection to the App-V bubble is lost.
The same happens when MS Edge-with-app-v is running bubble-a and you want start a secondary instance with bubble-b.
Could anyone tell me how to tell MS Edge to really isolate its processes and how it could work with multiple loaded App-V bubbles?
The only way I have successfully got around this is with the --no-sandbox, --app, and --user-data-dir switches.
For example:
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --no-sandbox --user-data-dir"%LOCALAPPDATA%\Microsoft\Edge\AppV --app="https://www.website.com" /appvve:[App-V PackageID]_[App-V PackageVersionID]
This opens up the page in an App window and uses its own directory so the process isn't merged with existing or new instances of Edge that launch in the default directory.
I found this kept crashing until --no-sandbox was introduced. however, I'm a little on edge as the Sandbox helps keeps this secure. I'm also wondering how the Sandbox is interfering with App-V.
This is a workaround, but I do think MS will need to investigate this further as clearly the --site-per-process isn't separating each tab, at least not how we would expect.
While I have not tried to virtualize this under App-V, I am aware that others have done so, for example NickIT.
Off hand, I would guess that RunVirtual is what you are looking for.

Can I use powerline without patched fonts?

As part of work, I frequently remote login to my workstation from a different laptop every week or so. Powerline works perfectly with the patched fonts on the workstation itself, but it looks and works horrible if I don't have the patched fonts. The cursor is 2 characters to the left of the end of line and messes up my commands.
It's not really practical for me to keep installing fonts on every new machine that I login from. Is there a way to have powerline work without the fancy patched fonts and glyphs? I'd be happy if it just uses stock characters in a font like 'inconsolata' so that I can login remotely in peace.

viewing a X3DOM file locally

I am running Linux Mint 17.1 (Rebecca)
on my Dell 4x Intel(R) Core(TM) i3-5005U CPU.
I have done X3D in a viewer in the past, but am now
try to do X3DOM in a Google Chrome v42 browser.
I can, for example display
examples.x3dom.org/example/x3dom_helloWorld.xhtml
from x3dom.org website. But when I copy locally to my machine
and try to view I get
"XMLHttpRequest cannot load file:///home/andrewmneiderer/src/Web3D/X3DOM/x3dom.swf. Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https, chrome-extension-resource."
Has anyone seen this error and have suggestions on what to do?
I wonder why this is not stated in the current documentation, but I remembered that I read it. You can find it in the documentation of previous versions http://x3dom.org/download/1.5.1/docs/html/notes/platforms.html#chrome
Recent releases of Chrome require you to enable WebGL. Please use the
following command parameters when launching chrome:
--enable-webgl
--use-gl=desktop
--log-level=0
--allow-file-access-from-files
--allow-file-access
The last two options enable the browser to load textures from disk. You will need this if you are developing your site
locally.
Furthermore there is an option --disable-web-security which has been mentioned here: http://x3dom.org/docs-old/notes/cors.html#chrome
Besides from that, I think you should try to get a machine with native WebGL support since this Flash version of X3DOM is just a fallback method which might lack the performance features of the native version.
Chrome on all systems (by default) does not enable loading of resources from the local disk - even when the parent HTML comes from the local disk. Firefox, IE, and (I think) Safari all allow local file loading. If you need to load X3D files using X3D from your local disk, then you need to implement a local web server. It is not necessary to run a full-blown Apache server. Google 'local web server' for various options.

Google Chrome does not render page after losing focus in AwesomeWM

I have installed fresh Arch Linux with linux-ck and awesomewm. After that I have installed google-chrome and started it. Everything works well, but if I open other application (chrome lose focus) and then got back to the chrome, it freezes. Mouse cursor works as expected (cursor changes after hovering link, input field, etc) but view is not updated.
Everything works well again if I change desktop to the second and go back to the first again (mod+2, mod+1). Chrome works, responses etc well.
I bet this issue has something in common with hardware acceleration. If I run some game (steam), lose focus, get back to the game - it shows last rendered screen before focus has been lost (sound is ok, game is responsible but does not update screen).
I use nvidia. Do I need some extra configuration to handle it ?
You want to disable "Use hardware acceleration when available" in Chrome settings.
For me, disabling hardware acceleration as Alex pointed out solved the issue. This bug has been brought forward before in awesome's issues GitHub page.
Apparently, the problem is not awesome. Graphics drivers might be involved but the main suspect seems to be the compositing manager. Running awesome with the "--no-argb" flag and disabling the comp manager seems to solve the problem.
The problem was xcompmgr which caused "freezing" view. I switched it to unagi and all of the problems have gone.

nVidia updated driver issue. Ubuntu 13.10

Same issue as most other people, can't boot after upgrading graphics drivers. All I get is a flashing cursor in top left. Can't switch tty with alt+f1/f2 etc or ctrl+alt+f1/f2 etc can't get grub to load with holding shiftkey on boot. Completely lost. Ubuntu 13.10.
I know what to do IF I get to the prompt or terminal. But I can't even get there.
Best regards.
Can be loaded in text mode.
Press 'e' to edit
Add in the right place 'nomodeset' and CTRL+X
P.S. images for example

Resources