[GH-ISSUE #516] MacOS Catalina - incorrect start/stop state in UI #404

New issue

Closed

opened 2026-05-05 06:18:07 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 06:18:07 -06:00

Owner

Originally created by @jtara on GitHub (Nov 30, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/516

Operating Systems

Server: MacOS Catalina 10.15.1

Client: MacOS Catalina 10.15.1

Barrier Version

2.3.2-Release-210c2b70, Build Date: October 3, 2019

Steps to reproduce bug

run Barrier (from Launchpad or upon login)
Click on Barrier icon on system menu
"stop" is greyed out
"start" is NOT greyed out
"start" seemingly does nothing (I tried out of curiosity, checked Activity to make sure it did not start a second copy)

Other info

When did the problem start to occur? - after upgrade to Catalina or after initial install on Catalina (I updated one machine, the other I recently installed Catalina from scratch, due to an SSD failure).
Is there a way to work around it? Yes - Quit and then start from LaunchPad
Does this bug prevent you from using Barrier entirely? No

Originally created by @jtara on GitHub (Nov 30, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/516 ### Operating Systems ### Server: MacOS Catalina 10.15.1 Client: MacOS Catalina 10.15.1 ### Barrier Version ### 2.3.2-Release-210c2b70, Build Date: October 3, 2019 ### Steps to reproduce bug ### 1. run Barrier (from Launchpad or upon login) 2. Click on Barrier icon on system menu 3. "stop" is greyed out 4. "start" is NOT greyed out 5. "start" seemingly does nothing (I tried out of curiosity, checked Activity to make sure it did not start a second copy) ### Other info ### * When did the problem start to occur? - after upgrade to Catalina or after initial install on Catalina (I updated one machine, the other I recently installed Catalina from scratch, due to an SSD failure). * Is there a way to work around it? Yes - Quit and then start from LaunchPad * Does this bug prevent you from using Barrier entirely? No

gitea-mirror

2026-05-05 06:18:07 -06:00

closed this issue
added the
macOS

bug
labels

gitea-mirror commented

2026-05-05 06:18:14 -06:00

Author

Owner

@simons-public commented on GitHub (May 5, 2020):

Can you post logs from the client or server (whichever one is having the issue in the UI)? The way the barrier UI checks the server/client state is from parsing the output from the client/server

@simons-public commented on GitHub (May 5, 2020): Can you post logs from the client or server (whichever one is having the issue in the UI)? The way the barrier UI [checks the server/client state is from parsing the output from the client/server](https://github.com/debauchee/barrier/blob/b6a1b5742006157c3fe746288961a9d2827a3f26/src/gui/src/MainWindow.cpp#L379-L399)

gitea-mirror commented

2026-05-05 06:18:15 -06:00

Author

Owner

@plessbd commented on GitHub (May 5, 2020):

Make sure your log level is NOTE or lower, ERROR and WARNING dont produce the output to allow the GUI to know what state barrier is in.

@plessbd commented on GitHub (May 5, 2020): Make sure your log level is NOTE or lower, ERROR and WARNING dont produce the output to allow the GUI to know what state barrier is in.

gitea-mirror referenced this issue

2026-05-05 07:57:53 -06:00

[PR #404] [MERGED] Fix: CMake now checks for required Qt5 libraries #1623