Created attachment 1123603 [details] Result from running `strace usbguard list-devices` Description of problem: On a fresh (unconfigured) installation of usbguard, I cannot interact with the daemon. Version-Release number of selected component (if applicable): usbguard-0.4-4.fc23.x86_64 How reproducible: don't know yet Steps to Reproduce: 1. install usbguard 2. start daemon with systemd as root/sudo: `systemctl start usbguard.service` 3. run `usbguard list-devices` to interact with the daemon Actual results: I get an error: Lexer.cpp:5151: ERROR: IPC protocol violation! The CLI and the usbguard-daemon aren't compatible. Expected results: some interaction Additional info: This issue might be caused by me setting umask to 0077 for all users. $ systemctl -l status usbguard.service ● usbguard.service - USBGuard daemon Loaded: loaded (/usr/lib/systemd/system/usbguard.service; disabled; vendor preset: disabled) Active: active (running) since Fr 2016-02-12 18:34:57 CET; 10min ago Main PID: 22912 (usbguard-daemon) CGroup: /system.slice/usbguard.service └─22912 /usr/sbin/usbguard-daemon -k -c /etc/usbguard/usbguard-daemon.conf Feb 12 18:34:57 hostname systemd[1]: Started USBGuard daemon. Feb 12 18:34:57 hostname systemd[1]: Starting USBGuard daemon... Feb 12 18:34:57 hostname usbguard-daemon[22912]: [2016-02-12 18:34:57.083184] warning: The configured rule file doesn't yet exists. Starting with an empty rule set.
I should probably add that the user account I was running `usbguard` from is member of group "wheel", which is permitted to IPC with usbguard by default. Running `usbguard` as root doesn't work around this error either.
This issue is not present in usbguard 0.5-1 from https://copr.fedorainfracloud.org/coprs/mildew/usbguard/
Hello, thanks for the report! What locale to you use on your system? Could you please test whether running $ LC_NUMERIC=C usbguard list-devices works?
No, it doesn't, still the same error message.
Sorry, I forgot to answer the first part of your question. My locale is LANG=de_DE.UTF-8
usbguard- and -applet-qt- 0.5-9.fc24.x86_64 work fine, no crash any more. Thank you!
(In reply to Christian Stadelmann from comment #6) > usbguard- and -applet-qt- 0.5-9.fc24.x86_64 work fine, no crash any more. > Thank you! Thanks for letting me know. I'll push an update to Fedora repositories once I figure out some minor build system issues in the upstream code.
usbguard-0.5.10-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-86faff2b57
usbguard-0.5.10-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-ab3c68099a
usbguard-0.5.10-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-ca3dc9fed5
usbguard-0.5.10-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-ca3dc9fed5
usbguard-0.5.10-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-86faff2b57
usbguard-0.5.10-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-ab3c68099a
usbguard-0.5.10-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
usbguard-0.5.10-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.