github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #202] Logging level affects displaying the running status #168

New issue

Open

opened 2026-05-05 05:29:01 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 05:29:01 -06:00

Owner

Originally created by @MC-Mihai on GitHub (Dec 18, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/202

Operating Systems

2x Windows 10 (1x OS Build 17763.194, 1x not checked), Ubuntu 18.04 LTS, Fedora 29

Barrier Version

v2.2.0-snapshoot-00000000 on Ubuntu
v2.1.0-snapshoot-773a0081 on Fedora
2x v2.1.0-RELEASE on Windows

Steps to reproduce bug

Start Barrier
Go to "Change settings" from "Barrier" drop down menu
On the section"Logging" change "Logging level" to "Warning" from "Info"
Press "Ok"
Press Start (you can try to configure before)
Barrier shows "Barrier is starting" but never updates to "Barrier is running."

Other info

Doesn't seem to be affecting the functionality. At first I thought it was not starting at all, but it seems like it does start, although it does not display it. Only the options "Warning" and "Error" show this behavior, for both "Server" and "Client" options.

Originally created by @MC-Mihai on GitHub (Dec 18, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/202 ### Operating Systems ### 2x Windows 10 (1x OS Build 17763.194, 1x not checked), Ubuntu 18.04 LTS, Fedora 29 ### Barrier Version ### v2.2.0-snapshoot-00000000 on Ubuntu v2.1.0-snapshoot-773a0081 on Fedora 2x v2.1.0-RELEASE on Windows ### Steps to reproduce bug ### 1) Start Barrier 2) Go to "Change settings" from "Barrier" drop down menu 3) On the section"Logging" change "Logging level" to "Warning" from "Info" 4) Press "Ok" 5) Press Start (you can try to configure before) 6) Barrier shows "Barrier is starting" but never updates to "Barrier is running." ### Other info ### Doesn't seem to be affecting the functionality. At first I thought it was not starting at all, but it seems like it does start, although it does not display it. Only the options "Warning" and "Error" show this behavior, for both "Server" and "Client" options.

gitea-mirror commented

2026-05-05 05:29:04 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Dec 18, 2018):

I'm going to assume you've added Barrier in the windows firewall?

@AdrianKoshka commented on GitHub (Dec 18, 2018): I'm going to assume you've [added Barrier in the windows firewall](https://github.com/debauchee/barrier/wiki/Adding-Barrier-to-the-Windows-Firewall)?

gitea-mirror commented

2026-05-05 05:29:06 -06:00

Author

Owner

@MC-Mihai commented on GitHub (Dec 19, 2018):

As I said, it does not affect the functionality, but the display of its status. It's a visual bug and shouldn't have something to do with the firewall, otherwise its behavior should've been different on Linux.

@MC-Mihai commented on GitHub (Dec 19, 2018): As I said, it does not affect the functionality, but the display of its status. It's a visual bug and shouldn't have something to do with the firewall, otherwise its behavior should've been different on Linux.

gitea-mirror commented

2026-05-05 05:29:07 -06:00

Author

Owner

@jwestfall69 commented on GitHub (Jan 4, 2019):

The GUI status works by reading the stdout of the spawned cli barrier command and looks for specific strings (ie: connected to server) to determine and update the gui status. It appears those messages from the cli are printed at level "Note", which is below the level for "Warning". By setting the log level to "Warning" (or above) its causing the cli barrier to never print those "Note" messages needed by the gui for status updates.

@jwestfall69 commented on GitHub (Jan 4, 2019): The GUI status works by reading the stdout of the spawned cli barrier command and looks for specific strings (ie: connected to server) to determine and update the gui status. It appears those messages from the cli are printed at level "Note", which is below the level for "Warning". By setting the log level to "Warning" (or above) its causing the cli barrier to never print those "Note" messages needed by the gui for status updates.

No labels

Rows
Columns