unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: John Kehayias via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "36900@debbugs.gnu.org" <36900@debbugs.gnu.org>
Subject: bug#36900: key-mon crashes on launch
Date: Sat, 14 Aug 2021 20:40:32 +0000	[thread overview]
Message-ID: <gb0tdk_sl0n7S8_4CwuCy7E6wuEZgyNUtRFCq3SO9Xn5T8-cwUW82jj41pHHjHydlrr479ONgKoMWtusZ_pal5URLDz_JIYfhKTXk-pIe2Q=@protonmail.com> (raw)
In-Reply-To: <sF3NKFLUVbmYhJ6DqLdF0BqHuwcjDnnoXPVBJ6mTXkEOtGQoq3NHVoXcg_NZsWeJYGpXICXp-kjrAwlp_Pgf8iRrk8CFUTb9jCfOxJo9rBQ=@protonmail.com>

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Saturday, August 14th, 2021 at 4:34 PM, John Kehayias wrote:

> Are there any updates on this, did anyone get it to work? I just tried with the same issue on opening display for me too.
>
> I'm seeing the same thing in trying to package autokey, but with the error displayed in a graphical window on the X server (and yet it says it doesn't know the protocol). This also uses python-xlib, gtk, etc.
>

Of course immediatly after I found a workaround, for key-mon and my case: allow all to connect to X with `xhost +`. Certainly not the ideal thing to do as it disables authentication with X, but show the problem.

Does anyone know the proper way to deal with this for these python packages?




      reply	other threads:[~2021-08-14 20:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 22:40 bug#36900: key-mon crashes on launch Jesse Gibbons
2019-08-02 23:21 ` Tobias Geerinckx-Rice
2019-08-03  1:54 ` Jesse Gibbons
2021-01-03 21:16 ` Alexandros Theodotou
2021-01-03 21:58   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-01-03 22:20     ` Alexandros Theodotou
2021-01-09 14:49 ` Alexandros Theodotou
2021-08-14 20:34 ` John Kehayias via Bug reports for GNU Guix
2021-08-14 20:40   ` John Kehayias via Bug reports for GNU Guix [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='gb0tdk_sl0n7S8_4CwuCy7E6wuEZgyNUtRFCq3SO9Xn5T8-cwUW82jj41pHHjHydlrr479ONgKoMWtusZ_pal5URLDz_JIYfhKTXk-pIe2Q=@protonmail.com' \
    --to=bug-guix@gnu.org \
    --cc=36900@debbugs.gnu.org \
    --cc=john.kehayias@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).