Problems with single app

[aaron]

Hi @ecf,

Welcome to the forum.

I’m not sure I quite understand what you’re trying to achieve with the%u substitution. Are you trying to use the ThinLinc client to open a local file, remotely?

The behaviour you’re seeing in the screenshot is because there is no window manager being started with the application. Using tl-single-app will ensure that a minimal window manager is started along with the application itself, and things should work a lot better. More info here:

Does ThinLinc support publishing single applications as well as desktops?

This article introduces publishing single applications with ThinLinc, and discusses some of the benefits and limitations of doing so. Introduction Each ThinLinc session is built around a server-side process called Xvnc. Xvnc is the main process in any ThinLinc session, and is essentially an X server and VNC server combined. Applications publish their graphical output to Xvnc just as they would to a normal X server, but instead of ending up on a physical screen, it gets translated into the VNC …

Another option would be to create a ThinLinc profile which only launches the desired application. This approach is described in the following article:

Running a single app using ThinLinc

Sometimes you don't need to run a complete desktop in your ThinLinc session. In that case, you can run a single application instead. This tutorial shows three ways to set up ThinLinc to run just one program instead of an entire desktop. It is assumed that the ThinLinc server and client are installed and configured before starting this guide. To be able to run an application with ThinLinc, the application needs to be installed on the same machine as the ThinLinc server.   Configuration using …

One final point, we always recommend running the latest version of the ThinLinc client and server (at time of writing, 4.19.0). So if you have the possibility to upgrade, it would be a good idea to do this first.

Hope that helps!