Bug 7246 - Windows client --loop shortcut often confusing
Summary: Windows client --loop shortcut often confusing
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client platforms (show other bugs)
Version: 1.3.1
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Peter Åstrand
: 7308 (view as bug list)
Depends on:
Reported: 2018-09-03 10:07 CEST by Pierre Ossman
Modified: 2023-11-15 10:51 CET (History)
4 users (show)

See Also:
Acceptance Criteria:
* New installations of the Windows client should not add the "loop" shortcut * Upgrade of existing Windows client should remove the "loop" shortcut that earlier versions added

windows 11 start menu (444.22 KB, image/png)
2022-03-29 10:20 CEST, Pierre Ossman

Description Pierre Ossman cendio 2018-09-03 10:07:35 CEST
We added a "loop" function to the client on bug 3633 to make it easier to deploy the client on dedicated ThinLinc terminals. As part of this we also started adding a start menu shortcut to launch the client in this mode.

However we've had several reports that users are getting confused by this function and accidentally starting the loop version rather than the normal one. They are then stuck with a client that they cannot easily get rid of.

We should consider not adding this shortcut by default as it is a niche feature that is not relevant for the vast majority of Windows users. A dedicated terminal most likely has a lot of other customisation, so having a custom launcher for the ThinLinc client shouldn't be a lot of extra work.
Comment 4 Pierre Ossman cendio 2018-09-04 13:07:55 CEST
The previous commits were for bug 7245.
Comment 5 Karl Mikaelsson cendio 2019-01-22 09:52:51 CET
*** Bug 7308 has been marked as a duplicate of this bug. ***
Comment 7 Pierre Ossman cendio 2022-03-29 10:20:39 CEST
Created attachment 1030 [details]
windows 11 start menu

This seems to be worse on Windows 11 where the loop version is suggested after install. See attached screenshot.

Note You need to log in before you can comment on or make changes to this bug.