On Saturday, February 15, 2025 4:41 PM, I wrote:
>> I installed Evince. Calling it brings up not even a GUI, just two error
>> messages:
>> Authorization required, but no authorization protocol specified
>> Cannot parse arguments: Cannot open display:
> Saturday, February 15, 2025 9:39 PM, Mak Nikulin replied:
> Looks like missed DISPLAY environment variable
>
> try
> echo $DISPLAY
> xhost
> Usually reports SI:localuser:...
echo $DISPLAY -> :0
xhost -> access control enabled, only authorized clients can connect
> echo $XAUTHORITY
>
> The last usually points to ~/.Xauthority.
echo $XAUTHORITY -> ~/.Xauthority
> I have no idea if evince might require some extra options related to
> Wayland when running from simple window managers like FVWM. I hope, it
> should be enough to have empty $WAYLAND_DISPLAY.
$WAYLAND_DISPLAY is empty.
> Some errors might be logged to ~/.xsession-errors or to systemd-journald
> journalctl --user -b -e
I do not have ~/.xsession-errors.
journalctl --user -b -e
Calling evince does not add anything to the output of that command.
Thanks.
________________________________________
From: Max Nikulin <maniku...@gmail.com>
Sent: Saturday, February 15, 2025 9:39 PM
To: debian-user@lists.debian.org
Subject: Re: fonts printing too thin from qpdfview (solved)
External Email: Use Caution
On 16/02/2025 04:41, Kleene, Steven (kleenesj) wrote:
> I installed Evince. Calling it brings up not even a GUI, just two error
> messages:
> Authorization required, but no authorization protocol specified
> Cannot parse arguments: Cannot open display:
Looks like missed DISPLAY environment variable
try
echo $DISPLAY
xhost
Usually reports SI:localuser:...
echo $XAUTHORITY
The last usually points to ~/.Xauthority. If you are trying to start
evince as another user then it should be able to read some Xauthority
cookie, but you should experience the same issue with other applications
as well.
I have no idea if evince might require some extra options related to
Wayland when running from simple window managers like FVWM. I hope, it
should be enough to have empty $WAYLAND_DISPLAY.
Some errors might be logged to ~/.xsession-errors or to systemd-journald
journalctl --user -b -e
