On Sunday, February 16, 2025 8:53 AM, I wrote:

>> > echo $XAUTHORITY -> ~/.Xauthority

On Sunday, February 16, 2025 11:18 AM, Greg Wooledge wrote:

> That should not *literally* be ~/.Xauthority of course.

Yes, the output is literally
  /u/steve/.Xauthority

Going back decades, I always put users under /u (and listed that in
/etc/passwd) and in group 100 ("users" in /etc/group).  Now I'm the only
active user.  I keep /u because I probably have that built into some shell
files instead of "~".

Having said that, I do have a single user sktest, which I added during
bookworm installation, under /home.  I set up the same fvwm and .xinitrc
initializations there and called startx.  There was still no
/home/sktest/.xsession-errors, although I do see the code for it in
/etc/X11/Xsession.

> So... I wonder if your HOME directory's permissions are screwed up.
> What does ls -ld ~ give you?  Might as well check all of them while
> we're at it:  ls -ld / /home ~

For /u/steve,
drwxr-xr-x 23 root  root  4096 Feb 13 08:56 /
drwxr-xr-x  3 root  root  4096 Dec 20  2022 /home
drwxr-xr-x 33 steve users 4096 Feb 16 12:54 /u/steve

For /home/sktest,
drwxr-xr-x 23 root   root   4096 Feb 13 08:56 /
drwxr-xr-x  3 root   root   4096 Dec 20  2022 /home
drwxr-xr-x  7 sktest sktest 4096 Feb 16 12:54 /home/sktest

I see that sktest is the only member of group 1000 (sktest).  All other users
(me and former users still listed) are in group 100 (users), which again goes
way back.

> Also, is there anything that looks like an xsession-$USER file in /tmp?
> Or any regular files in /tmp owned by you that have X session output
> in them?

No and no.  Here's the output of "ls -a /tmp | egrep steve":

drwx------  2 steve users  4096 Feb 16 10:31 acroread_1047_100
drwxr-xr-x  2 steve users  4096 Jan  9 13:40 hsperfdata_steve
-rw-r--r--  1 steve users     0 Jan 19 13:23 
qtsingleapp-smplay-ca73-417-lockfile
-rw-------  1 steve users   144 Feb 16 12:54 serverauth.vYofRhWUfe
drwx------  2 steve users  4096 Feb 16 12:54 
Temp-6400d4ac-eccd-4d88-981d-b4c9e8d1baf8
-r--r--r--  1 steve users    11 Feb 16 12:54 .X0-lock

Now for evince.  If I call it from sktest's window (but not from steve's), I
get these errors:

libGL error: MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
libGL error: glx: failed to create dri3 screen
libGL error: failed to load driver: i915
libGL error: MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
libGL error: glx: failed to create dri2 screen
libGL error: failed to load driver: i915

After this, these new lines are added to the output of "journalctl --user -b -e"

Feb 16 12:52:53 drx dbus-daemon[1338857]: [session uid=1000 pid=1338857] 
Activating via systemd: service name='org.freedesktop.portal.Desktop' 
unit='xdg-desktop-portal.service' requested by ':1.36' (uid=1000 pid=1342515 
comm="evince")
Feb 16 12:52:53 drx systemd[1338834]: Starting xdg-desktop-portal.service - 
Portal service...
Feb 16 12:52:53 drx dbus-daemon[1338857]: [session uid=1000 pid=1338857] 
Activating via systemd: service name='org.freedesktop.impl.portal.desktop.gtk' 
unit='xdg-desktop-portal-gtk.service' requested by ':1.37' (uid=1000 
pid=1342519 comm="/usr/libexec/xdg-desktop-portal")
Feb 16 12:52:53 drx systemd[1338834]: Starting xdg-desktop-portal-gtk.service - 
Portal service (GTK/GNOME implementation)...
Feb 16 12:52:53 drx xdg-desktop-por[1342523]: cannot open display:
Feb 16 12:52:53 drx systemd[1338834]: xdg-desktop-portal-gtk.service: Main 
process exited, code=exited, status=1/FAILURE
Feb 16 12:52:53 drx systemd[1338834]: xdg-desktop-portal-gtk.service: Failed 
with result 'exit-code'.
Feb 16 12:52:53 drx systemd[1338834]: Failed to start 
xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation).

If I try evince a second time, these lines are added:

Feb 16 12:53:43 drx xdg-desktop-por[1342519]: Failed to create settings proxy: 
Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gtk: 
Timeout was reached
Feb 16 12:53:43 drx xdg-desktop-por[1342519]: No skeleton to export

As I mentioned earlier, calling evince as steve causes different errors
  Authorization required, but no authorization protocol specified
  Cannot parse arguments: Cannot open display:

and no new lines in the output of "journalctl --user -b -e".

Thanks.  Sorry for the non-standard parts of my configuration.  I have never
felt they were a problem, but they do have an effect here.

________________________________________
From: Greg Wooledge <g...@wooledge.org>
Sent: Sunday, February 16, 2025 11:18 AM
To: debian-user@lists.debian.org
Subject: Re: fonts printing too thin from qpdfview (solved)

External Email: Use Caution


On Sun, Feb 16, 2025 at 13:53:21 +0000, Kleene, Steven (kleenesj) wrote:
> echo $DISPLAY -> :0
> xhost -> access control enabled, only authorized clients can connect
>
> >      echo $XAUTHORITY
> >
> > The last usually points to ~/.Xauthority.
>
> echo $XAUTHORITY -> ~/.Xauthority

That should not *literally* be ~/.Xauthority of course.

hobbit:~$ declare -p XAUTHORITY
declare -x XAUTHORITY="/home/greg/.Xauthority"

> I do not have ~/.xsession-errors.

Well now, *that* is quite strange.

One of the things that the Debian /etc/X11/Xsession script does is this:


ERRFILE=$HOME/.xsession-errors
[...]
# attempt to create an error file; abort if we cannot
if (umask 077 && touch "$ERRFILE") 2> /dev/null && [ -w "$ERRFILE" ] &&
  [ ! -L "$ERRFILE" ]; then
  chmod 600 "$ERRFILE"
elif ERRFILE=$(mktemp 2> /dev/null); then
  if ! ln -sf "$ERRFILE" "${TMPDIR:=/tmp}/xsession-$USER"; then
    message "warning: unable to symlink \"$TMPDIR/xsession-$USER\" to" \
             "\"$ERRFILE\"; look for session log/errors in" \
             "\"$TMPDIR/xsession-$USER\"."
  fi
else
  errormsg "unable to create X session log/error file; aborting."
fi


So... I wonder if your HOME directory's permissions are screwed up.
What does ls -ld ~ give you?  Might as well check all of them while
we're at it:  ls -ld / /home ~

Here, I'll start:

hobbit:~$ ls -ld / /home ~
drwxr-xr-x  24 root root  4096 Feb  9 09:03 //
drwxr-xr-x   7 root root  4096 Feb 17  2024 /home/
drwxr-xr-x 231 greg greg 65536 Feb 16 11:15 /home/greg/

Also, is there anything that looks like an xsession-$USER file in /tmp?
Or any regular files in /tmp owned by you that have X session output
in them?

Reply via email to