From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesse Gibbons Subject: bug#36900: key-mon crashes on launch Date: Fri, 02 Aug 2019 16:40:53 -0600 Message-ID: <0c086cf749e6b5b09ddbcbb2b59d8b0d79d514b5.camel@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:60786) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1htgFP-0004Hf-GI for bug-guix@gnu.org; Fri, 02 Aug 2019 18:42:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1htgFO-00034m-DZ for bug-guix@gnu.org; Fri, 02 Aug 2019 18:42:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:49139) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1htgFO-00034e-8k for bug-guix@gnu.org; Fri, 02 Aug 2019 18:42:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1htgFO-0006fT-5a for bug-guix@gnu.org; Fri, 02 Aug 2019 18:42:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Received: from eggs.gnu.org ([2001:470:142:3::10]:60499) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1htgEM-0004EB-Im for bug-guix@gnu.org; Fri, 02 Aug 2019 18:41:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1htgEL-0002YM-Hk for bug-guix@gnu.org; Fri, 02 Aug 2019 18:40:58 -0400 Received: from mail-pf1-x42f.google.com ([2607:f8b0:4864:20::42f]:42428) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1htgEL-0002XU-1Q for bug-guix@gnu.org; Fri, 02 Aug 2019 18:40:57 -0400 Received: by mail-pf1-x42f.google.com with SMTP id q10so36693707pff.9 for ; Fri, 02 Aug 2019 15:40:56 -0700 (PDT) Received: from piranhaplant.local ([199.68.53.171]) by smtp.googlemail.com with ESMTPSA id q24sm8776439pjp.14.2019.08.02.15.40.53 for (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Fri, 02 Aug 2019 15:40:54 -0700 (PDT) List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 36900@debbugs.gnu.org 1. install key-mon 2. run key-mon it crashes: (.key-mon-real:5006): Gtk-WARNING **: 16:23:06.088: Unable to locate theme engine in module_path: "adwaita", (.key-mon-real:5006): Gtk-WARNING **: 16:23:06.092: Unable to locate theme engine in module_path: "adwaita", Traceback (most recent call last): File "/gnu/store/jkjmj9l72rmnh642dyprnpwgmz4mn6cx-key-mon- 1.17/bin/.key-mon-real", line 3, in km.main() File "/gnu/store/jkjmj9l72rmnh642dyprnpwgmz4mn6cx-key-mon- 1.17/lib/python2.7/site-packages/keymon/key_mon.py", line 1032, in main keymon = KeyMon(opts) File "/gnu/store/jkjmj9l72rmnh642dyprnpwgmz4mn6cx-key-mon- 1.17/lib/python2.7/site-packages/keymon/key_mon.py", line 130, in __init__ self.devices = xlib.XEvents() File "/gnu/store/jkjmj9l72rmnh642dyprnpwgmz4mn6cx-key-mon- 1.17/lib/python2.7/site-packages/keymon/xlib.py", line 80, in __init__ self.record_display = display.Display() File "/gnu/store/4xl1xl2fp6c0c9f9pm1xm10x1qgbwp08-python2-xlib- 0.14/lib/python2.7/site-packages/Xlib/display.py", line 85, in __init__ self.display = _BaseDisplay(display) File "/gnu/store/4xl1xl2fp6c0c9f9pm1xm10x1qgbwp08-python2-xlib- 0.14/lib/python2.7/site-packages/Xlib/display.py", line 67, in __init__ apply(protocol.display.Display.__init__, (self, ) + args, keys) File "/gnu/store/4xl1xl2fp6c0c9f9pm1xm10x1qgbwp08-python2-xlib- 0.14/lib/python2.7/site-packages/Xlib/protocol/display.py", line 121, in __init__ raise error.DisplayConnectionError(self.display_name, r.reason) Xlib.error.DisplayConnectionError: Can't connect to display ":1": No protocol specified One possible reason it crashes is the python2-xlib is far outdated. The package was added in patch db62afa55ad443cc50bcafe64eb3ba239eae9c11 (2015) and has been version 0.14 ever since. The website says it has been migrated to github, which says the most recent stable release is 0.25. It looks like there is a similar issue (though not identical) htt ps://github.com/python-xlib/python-xlib/issues/53 which was fixed. I will see if updating python2-xlib fixes this, and if so I will send a patch. Any objections? -- -Jesse