Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MacOS Catalina - incorrect start/stop state in UI #516

Closed
jtara opened this issue Nov 30, 2019 · 2 comments
Closed

MacOS Catalina - incorrect start/stop state in UI #516

jtara opened this issue Nov 30, 2019 · 2 comments
Labels
bug Something isn't working macOS Related to macOS

Comments

@jtara
Copy link

jtara commented Nov 30, 2019

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
@AdrianKoshka AdrianKoshka added bug Something isn't working macOS Related to macOS labels Dec 2, 2019
@simons-public
Copy link

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

@plessbd
Copy link

plessbd commented 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 plessbd mentioned this issue May 5, 2020
Closed
This was referenced May 5, 2020
Merged
Open
simons-public added a commit to simons-public/barrier that referenced this issue May 12, 2020
@simons-public
Change log level on several status messages (Fixes debauchee#652, Fixes
8d1e628 
debauchee#516)

This changes the log level for several statuses (started server,
connected to server, server status:) from CLOG_NOTE or CLOG_INFO to
CLOG_PRINT so they will be printed to stdout regardless of the log
level. This allows the GUI to accurately report the status of the
`barriers` or `barrierc` processes in src/gui/src/MainWindow.cpp#L379-L399.
shymega added a commit that referenced this issue May 12, 2020
@shymega
Merge pull request #664 from simons-public/fix-gui-status
dc2869f 
Change log level on several status messages (Fixes #652, Fixes #516)
simons-public added a commit to simons-public/barrier that referenced this issue Jun 5, 2020
@simons-public
Change log level on several status messages (Fixes debauchee#652, Fixes
637d65a 
debauchee#516)

This changes the log level for several statuses (started server,
connected to server, server status:) from CLOG_NOTE or CLOG_INFO to
CLOG_PRINT so they will be printed to stdout regardless of the log
level. This allows the GUI to accurately report the status of the
`barriers` or `barrierc` processes in src/gui/src/MainWindow.cpp#L379-L399.
@simons-public simons-public mentioned this issue Jun 5, 2020
Merged
@ghost ghost mentioned this issue Nov 10, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working macOS Related to macOS
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@plessbd @jtara @AdrianKoshka @simons-public