[GH-ISSUE #497] Server wont start anymore, unrecognized option `--enable-cypto' #390

New issue

Closed

opened 2026-05-05 06:15:17 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 06:15:17 -06:00

Owner

Originally created by @haivala on GitHub (Nov 18, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/497

Operating Systems

Server: Arch

Client: Windows 10

Barrier Version

2.3.2-1

Steps to reproduce bug

Updated and starting by barriers --enable-crypto does not work anymore

 ~  barriers --enable-cypto
barriers: unrecognized option `--enable-cypto'
Try `barriers --help' for more information.

Other info

Started happening after latest update
I can run the GUI version and it works as usual
Does this bug prevent you from using Barrier entirely? No

What to do?

Originally created by @haivala on GitHub (Nov 18, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/497 ### Operating Systems ### Server: Arch Client: Windows 10 ### Barrier Version ### 2.3.2-1 ### Steps to reproduce bug ### Updated and starting by `barriers --enable-crypto` does not work anymore ``` ~  barriers --enable-cypto barriers: unrecognized option `--enable-cypto' Try `barriers --help' for more information. ``` ### Other info ### * Started happening after latest update * I can run the GUI version and it works as usual * Does this bug prevent you from using Barrier entirely? No What to do?

gitea-mirror

2026-05-05 06:15:17 -06:00

closed this issue
added the
windows

linux

invalid
labels

gitea-mirror commented

2026-05-05 06:15:26 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Nov 18, 2019):

You made a typo, you put --enable-cypto, instead of --enable-crypto.

@AdrianKoshka commented on GitHub (Nov 18, 2019): You made a typo, you put `--enable-cypto`, instead of `--enable-crypto`.

gitea-mirror commented

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

Author

Owner

@shymega commented on GitHub (Nov 29, 2019):

@haivala Can you please confirm that @AdrianKoshka's comment resolved the issue? I'd be grateful to know in case it did not resolve matters.
Cheers.

@shymega commented on GitHub (Nov 29, 2019): @haivala Can you please confirm that @AdrianKoshka's comment resolved the issue? I'd be grateful to know in case it did not resolve matters. Cheers.

gitea-mirror commented

2026-05-05 06:15:32 -06:00

Author

Owner

@haivala commented on GitHub (Dec 5, 2019):

It did. Sorry for the issue.

@haivala commented on GitHub (Dec 5, 2019): It did. Sorry for the issue.

gitea-mirror referenced this issue

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

[PR #390] reimplement how stdin is read on the cli New PR #1618