On Tue, 18 Aug 2020 10:31:10 +0200, Emile CARCAMO said:
>       and don't forget to build tk with option -DTK_NO_SECURITY
>       as documented somewhere (I can't remember) to avoid xhost
>       (well known) warning issue.

Yowza.  This looks like a cargo-cult configuration, done that way only
because it used to be needed a long time ago in a Xsession far far away...

There shouldn't be any need for that, as the other (better) option is
to use xauth. And that *should* be getting done for you automatically
on a Fedora system - at least lightdm does it.  If you're using gdm and
it's *not* setting itup, that would qualify as a bug.

[~] xauth
Using authority file /run/lightdm/valdis/xauthority
xauth> info
Authority file:       /run/lightdm/valdis/xauthority
File new:             no
File locked:          no
Number of entries:    1
Changes honored:      yes
Changes made:         no
Current input:        (stdin):1
[~] xhost
access control enabled, only authorized clients can connect
SI:localuser:valdis

And I'm using the Fedora-supplied Tk/Tcl RPMs...


Attachment: pgph2ym2841Hv.pgp
Description: PGP signature

_______________________________________________
Exmh-users mailing list
Exmh-users@redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users

Reply via email to