Comment # 3 on bug 1203458 from James Fehlig

(In reply to Daniel Scott from comment #2)
> The last log entry was from August. However it updated when I ran it from
> the command line sudo virt-manager --debug
> 
> [Thu, 15 Sep 2022 10:50:17 virt-manager 15306] DEBUG (cli:204) Version 4.1.0
> launched with command line: /usr/bin/virt-manager --debug
> [Thu, 15 Sep 2022 10:50:17 virt-manager 15306] DEBUG (virtmanager:170)
> virt-manager version: 4.1.0
> [Thu, 15 Sep 2022 10:50:17 virt-manager 15306] DEBUG (virtmanager:171)
> virtManager import: /usr/share/virt-manager/virtManager
> [Thu, 15 Sep 2022 10:50:17 virt-manager 15306] DEBUG (cli:195) Uncaught
> exception:
> Traceback (most recent call last):
>   File "/usr/bin/virt-manager", line 8, in <module>
>     virtmanager.runcli()
>   File "/usr/share/virt-manager/virtManager/virtmanager.py", line 274, in
> runcli
>     main()
>   File "/usr/share/virt-manager/virtManager/virtmanager.py", line 198, in
> main
>     leftovers = _import_gtk(leftovers)
>   File "/usr/share/virt-manager/virtManager/virtmanager.py", line 73, in
> _import_gtk
>     raise Exception("Error starting virt-manager: No graphical display
> found")
> Exception: Error starting virt-manager: No graphical display found

This is a different problem. Does the terminal used to start virt-manager have
a valid DISPLAY? Can be checked with 'echo $DISPLAY'.