i3wm in qubes has ssh-agent running by default in dom0?
I had a bug again with my screen of the laptop, staying black after I had it go to sleep for a while. Thus, I could only see the part on my attached monitor.
while searching what was the problem of maybe i3wm or X, I saw this:
ps aux |grep i3
firex 8532 0.1 0.4 323748 17440 ? Ssl 18:58 0:16 i3
firex 8577 0.0 0.0 7928 1600 ? Ss 18:58 0:00 /usr/bin/ssh-agent /bin/sh -c exec -l /bin/bash -c "i3"
firex 8609 0.0 0.3 93664 13700 ? Ssl 18:58 0:08 i3bar --bar_id=bar-0 --socket=/run/user/1000/i3/ipc-socket.8532
firex 8616 0.0 0.0 231192 2088 ? S 18:58 0:00 /usr/bin/bash /usr/bin/qubes-i3-xdg-autostart
firex 8620 0.0 0.0 231192 2096 ? S 18:58 0:00 /usr/bin/bash /usr/bin/qubes-i3-xdg-autostart
firex 8623 0.0 0.0 231192 2096 ? S 18:58 0:00 /usr/bin/bash /usr/bin/qubes-i3-xdg-autostart
firex 8628 0.0 0.0 231192 2192 ? S 18:58 0:00 /usr/bin/bash /usr/bin/qubes-i3-xdg-autostart
firex 8640 0.0 0.0 231192 2192 ? S 18:58 0:00 /usr/bin/bash /usr/bin/qubes-i3-xdg-autostart
firex 8648 0.3 0.4 247032 17196 ? S 18:58 0:40 /usr/bin/python3 /usr/bin/qubes-i3status
firex 27067 0.0 0.0 230340 2408 pts/16 S+ 21:52 0:00 grep --color=auto i3
Is this expected?
usr/bin/ssh-agent /bin/sh -c exec -l /bin/bash -c “i3”