Bug 5527 - Unclear title on last page of ThinLinc installer after upgrade
Summary: Unclear title on last page of ThinLinc installer after upgrade
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Server Installer (show other bugs)
Version: 4.3.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Samuel Mannehed
URL:
Keywords: prosaic
Depends on:
Blocks:
 
Reported: 2015-05-12 07:58 CEST by Henrik Andersson
Modified: 2021-06-14 16:01 CEST (History)
1 user (show)

See Also:
Acceptance Criteria:


Attachments
Screenshot of message in mind. (62.17 KB, image/png)
2015-05-12 07:59 CEST, Henrik Andersson
Details

Description Henrik Andersson cendio 2015-05-12 07:58:30 CEST
New 'installers' might miss that running tl-setup is a required step for completing the installation of ThinLinc, if we say one should run it to continue upgrading.
Comment 1 Henrik Andersson cendio 2015-05-12 07:59:09 CEST
Created attachment 626 [details]
Screenshot of message in mind.
Comment 2 Samuel Mannehed cendio 2015-11-25 16:25:35 CET
I don't understand what this bug is about? The message in the screenshot is only shown when doing an upgrade of the ThinLinc server. If you do a fresh install you instead get this text:

"Before using ThinLinc, you must configure it using /opt/thinlinc/sbin/tl-setup. Run ThinLinc Setup now"
Comment 3 Henrik Andersson cendio 2015-11-26 08:50:21 CET
(In reply to comment #2)
> I don't understand what this bug is about? The message in the screenshot is
> only shown when doing an upgrade of the ThinLinc server. If you do a fresh
> install you instead get this text:
> 
> "Before using ThinLinc, you must configure it using
> /opt/thinlinc/sbin/tl-setup. Run ThinLinc Setup now"

We have two different messages; one for installation and one for upgrade. The title in the screenshot tells that the installation is done, but a more proper title would be that upgrade is done.
Comment 4 Samuel Mannehed cendio 2021-06-14 16:01:51 CEST
Moving back to milestone "LowPrio" since solving this will require some restructuring. The strings for the summary message at the end are setup before we know if it's an update or not.

The confusion caused by this should be minor - this isn't very important.

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