Bug 3746 - macOS client: New Connection does not work after login
Summary: macOS client: New Connection does not work after login
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client platforms (show other bugs)
Target Milestone: MediumPrio
Assignee: Pierre Ossman
: 5331 5598 7693 (view as bug list)
Depends on:
Blocks: 3047
  Show dependency treegraph
Reported: 2011-02-09 16:23 CET by Peter Åstrand
Modified: 2022-06-30 08:48 CEST (History)
3 users (show)

See Also:
Acceptance Criteria:


Description Peter Åstrand cendio 2011-02-09 16:23:12 CET
This problem was noticed on bug 2186 in comment #17, but we closed that bug without fixing this. The "New Connection" menu option, as well as all other menu options, are disabled after you have logged in.
Comment 1 Pierre Ossman cendio 2013-12-09 14:08:12 CET
Absolutely no idea what is wrong here. Time est pulled out of the nether region.
Comment 2 Peter Åstrand cendio 2014-10-29 10:11:25 CET
*** Bug 5331 has been marked as a duplicate of this bug. ***
Comment 3 Pierre Ossman cendio 2015-03-04 09:52:02 CET
I tried adding a system menu to vncviewer, but unfortunately that did not change anything. There is also something weird going on as the menu doesn't work even if you execute vncviewer directly. But it does work if you start vncviewer outside of its bundle.
Comment 4 Pierre Ossman cendio 2015-08-18 16:36:32 CEST
*** Bug 5598 has been marked as a duplicate of this bug. ***
Comment 5 Peter Åstrand cendio 2016-01-26 14:00:17 CET
Note that since we have implemented bug 5504, there's a workaround now: It is possible to drag a .tlclient file to the ThinLinc Client icon in the Dock. This will start a new client instance, even if you are logged in. You can probably also use the "open" command or Applescript.
Comment 8 Pierre Ossman cendio 2021-08-24 15:57:19 CEST
*** Bug 7693 has been marked as a duplicate of this bug. ***
Comment 9 Pierre Ossman cendio 2021-08-24 15:59:05 CEST
Somewhere along the line things have gotten worse. macOS is now not even displaying a disabled menu for vncviewer, and won't even update the name, instead showing the previously focused application.

We can confirm this on macOS 11 here, but we have a user report that this happens on 10.14 and 10.15 as well.
Comment 10 Pierre Ossman cendio 2021-08-25 14:01:52 CEST
We've now also tested 10.15.7 ourselves and confirmed the behaviour there.

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