Hello people.
Almost every other time, the periferial devices don’t load on startup.
Only the modem does load.
I mean there’s no option to allow them or not, they just don’t appear.
Please point me to where I might add them manually, instead of having to reboot the PC, every time this happens.
Best regards
tzwcfq
June 15, 2022, 8:31pm
2
Try to run in dom0 terminal:
sudo systemctl --user restart qubes-widget@qui-devices
Also you can report this but in qubes-issues. This one looks similar:
opened 12:40PM - 17 Jul 20 UTC
closed 05:13PM - 05 Aug 20 UTC
T: bug
C: manager/widget
P: default
**Qubes OS version**
Qubes -release 4.1 April build
**Affected component(s) or… functionality**
Device Widget
**Brief summary**
Qubes device widget tray Icon disappeared and now its not there by any restart.
**To Reproduce**
I don't know the inciting event but Its not there now. It was there I first installed this version.
**Expected behavior**
Widget in tray icons
**Actual behavior**
No tray icon
**Screenshots**
_If applicable, add screenshots to help explain your problem._
**Additional context**
Discussed the issue with @marmarta in #5622
**Solutions you've tried**
none but logs of "systemctl --user status qubes-widget@qui-devices" providing below
qubes-widget@qui-devices.service - Qubes-Widet service
Loaded: loaded (/usr/lib/systemd/user/qubes-widget@.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2020-07-17 06:21:07 EDT; 1h 31min ago
Process: 6062 ExecStart=/usr/bin/widget-wrapper qui-devices (code=exited, status=1/FAILURE)
CPU: 192ms
Jul 17 06:21:07 dom0 systemd [5771]: qubes-widget@qui-devices.service: Scheduled restart job, restart counter is at 3.
Jul 17 06:21:07 dom0 systemd [5771]: Stopped Qubes Widet service.
Jul 17 06:21:07 dom0 systemd [5771]: qubes-widget@qui-devices.service: Start request repeated too quickly.
Jul 17 06:21:07 dom0 systemd [5771]: qubes-widget@qui-devices.service: Failed with result 'exit-code' .
Jul 17 06:21:07 dom0 systemd [5771]: Failed to start Qubes Widet service.
**Relevant [documentation](https://www.qubes-os.org/doc/) you've consulted**
_A list of links to the Qubes documentation (or other relevant software documentation) pages you have already consulted._
**Related, [non-duplicate](https://www.qubes-os.org/doc/reporting-bugs/#new-issues-should-not-be-duplicates-of-existing-issues) issues**
_A list of links to other bug reports, feature requests, or tasks in the qubes-issues tracker (or "none" if you didn't find any). Do not describe any other unreported bugs, features, or tasks here._
Hello.
Thank you, but this is the error message I get after that command:
“Failed to connect to bus: No such file or directory”
Regards.
tzwcfq
June 16, 2022, 9:55am
4
You can fix it like this:
But there must be some problems with your dom0 if you don’t have /lib/systemd/systemd --user process running so there may be more problems that you’ll face.
You can check the logs in dom0 for strings err or fail to check what was the root cause of this issue:
sudo journalctl
I couldn’t find neither err, nor fail using the Terminal\Find feature …
Thanks.