This commit enables the desktop to show the current keyboard layout
by using gkbd-keyboard-display command.
Signed-off-by: Simental Magana, Marcos <marcos.simental.magana(a)intel.com>
---
When a user clicks the 'show keyboard layout' option, a pop-up
notification shows an d error saying gkbd-keyboard-display command
is unavailable.
This patch fixes that, successfully showing a preview of the selected
keyboard layout.
bundles/desktop | 1 +
1 file changed, 1 insertion(+)
diff --git a/bundles/desktop b/bundles/desktop
index ff26085..4f2c16a 100644
--- a/bundles/desktop
+++ b/bundles/desktop
@@ -31,6 +31,7 @@ gtk3
ibus
iso-codes
json-glib
+libgnomekbd
libgweather
libnotify
librsvg
--
2.13.3
Hi Natalia,
On Thu, Jul 06, 2017 at 10:58:21PM +0000, Marin Perez, Natalia wrote:
> Hi guys,
>
> I'm currently trying the guide that you posted here: https://github.com/01org/cc-oci-runtime/wiki/Clear-Containers-and-Kubernete… and I'm having this error.
>
> root(a)ip-172-31-39-225:~/go/src/github.com/kubernetes-incubator/cri-o# make && make install
> go build -o crio \
> -tags "selinux seccomp libdm_no_deferred_remove" \
> github.com/kubernetes-incubator/cri-o/cmd/crio
>
> # github.com/kubernetes-incubator/cri-o/cmd/crio
> /usr/lib/go-1.8/pkg/tool/linux_amd64/link: running gcc failed: fork/exec /usr/bin/gcc: cannot allocate memory
>
> Makefile:72: recipe for target 'crio' failed
> make: *** [crio] Error 2
>
> Not sure if it's because I'm using Kubernetes version 1.7 instead of the 1.6 version that is being used in the guide or if it may probably be something else in my server configuration. Could you please provide some guidance on this?
>
> Thank you !
I'm including our Clear Containers mailing list.
>
> Best regards,
> Natalia Marín
>
--
Regards,
Miguel Bernal Marin Open Source Technology Center
https://clearlinux.org Intel Corporation
Hello!
There's this patch for glibc in Clear Linux:
https://raw.githubusercontent.com/clearlinux-pkgs/glibc/e54b638ef6b5f838e99…
It makes it possible to selectively override individual entries of the
system default /usr/share/defaults/etc/nsswitch.conf in the (normally
missing) /etc/nsswitch.conf.
While testing the stateless patches I ran into a segfault related to
nsswitch.conf. This can be reproduced like this:
$ start_qemu.sh clear-16280-kvm.img
...
root(a)clr-e2025fd6e74646a2a5101fda26464c73 ~ # touch /etc/nsswitch.conf
root(a)clr-e2025fd6e74646a2a5101fda26464c73 ~ # id
Segmentation fault (core dumped)
strace shows that it aborts directly after reading nsswitch.conf:
root(a)clr-e2025fd6e74646a2a5101fda26464c73 ~ # strace -e trace=open id
open("/var/cache/ldconfig/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3</var/cache/ldconfig/ld.so.cache>
...
open("/usr/share/locale/en/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 3</etc/nsswitch.conf>
open("/usr/share/defaults/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 3</usr/share/defaults/etc/nsswitch.conf>
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} ---
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped)
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
