From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 23198@debbugs.gnu.org
Subject: bug#23198: GNOME: Execution of "gkbd-keyboard-display" failed: Command not found
Date: Wed, 02 Dec 2020 09:26:08 +0100 [thread overview]
Message-ID: <483945656b6694d54da6a3fb8f8ed7fde0b1a61d.camel@student.tugraz.at> (raw)
In-Reply-To: <87wpof667v.fsf@gmail.com>
Hello Chris,
Am Samstag, den 02.04.2016, 14:39 -0700 schrieb Chris Marusich:
> Hi,
>
> I'm using GuixSD v0.10.0 with GNOME. In GNOME, when you have enabled
> a
> second keyboard input (via "Settings" > "Region and Language" >
> "Input
> Sources"), if you click on "Show Keyboard Layout" from the keyboard
> input selection drop-down menu in the upper right corner of the GUI,
> the
> following error is displayed on your screen:
>
> Execution of "gkbd-keyboard-display" failed: Command not found
>
> I'm guessing this is happening because that command is just not
> present.
> To fix it, do we just need to package up whatever it is that normally
> provides that command?
The bug you're describing concerns an old version of Guix System with
an old version of GNOME. While the interface has been changed, I
believe, that this might have been fixed at some point between then and
now.
Using gnome-desktop-service on a fairly up-to-date Guix System,
entering the "Region and Language" settings and clicking on the "eye"
icon of an input source, I do see a keyboard layout being spawned even
without that command being (visibly) provided.
Does the same hold for you? Can this bug be closed?
Regards, Leo
next prev parent reply other threads:[~2020-12-02 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 21:39 bug#23198: GNOME: Execution of "gkbd-keyboard-display" failed: Command not found Chris Marusich
2020-12-02 8:26 ` Leo Prikler [this message]
2022-01-04 23:40 ` zimoun
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=483945656b6694d54da6a3fb8f8ed7fde0b1a61d.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=23198@debbugs.gnu.org \
--cc=cmmarusich@gmail.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).