On Sunday, February 16, 2025 10:41 PM, Max Nikulin wrote: > Steven, it seems you have managed to print your PDF file, so perhaps you > should stop debugging evince (unless you need it for some feature with > worse support in okular or browsers ...
That is my preference at this point. I'm very satisifed now printing from firefox. I share your curiosity about evince but would just as soon not continue debugging the problem, given the apparent complexity. Again, though, I thank the many readers who provided helpful suggestions and ultimately led me to a happy solution. ________________________________________ From: Greg Wooledge <g...@wooledge.org> Sent: Sunday, February 16, 2025 10:54 PM To: debian-user@lists.debian.org Subject: Re: fonts printing too thin from qpdfview (solved) External Email: Use Caution > On 17/02/2025 01:23, Kleene, Steven (kleenesj) wrote: > > On Sunday, February 16, 2025 8:53 AM, I wrote: > > > That should not *literally* be ~/.Xauthority of course. > > > > Yes, the output is literally > > /u/steve/.Xauthority A thought just occurred to me. Having your home directory outside of /home might *conceivably* cause certain things to fail. Programs that have an AppArmor profile might have been set up to allow full access to /home but not to /u. Or, programs that are started through a systemd unit file might be configured with similar access restrictions which work for users in /home but not users in other locations. I have no idea whether evince has an AppArmor profile or a systemd unit file, or whether you're invoking it as a systemd service if the latter is true. Might be worth looking into.
