Bug 1390926

Created attachment 1216412 [details]
File: backtrace

Created attachment 1216413 [details]
File: cgroup

Created attachment 1216414 [details]
File: core_backtrace

Created attachment 1216415 [details]
File: dso_list

Created attachment 1216416 [details]
File: environ

Created attachment 1216417 [details]
File: exploitable

Created attachment 1216418 [details]
File: limits

Created attachment 1216419 [details]
File: maps

Created attachment 1216420 [details]
File: mountinfo

Created attachment 1216421 [details]
File: namespaces

Created attachment 1216422 [details]
File: open_fds

Created attachment 1216423 [details]
File: proc_pid_status

Created attachment 1216424 [details]
File: var_log_messages

*** Bug 1403377 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

After kernel 4.9.3, the keymap became a different thing. Switching is also not possible. why?

reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        gkbd-keyboard-display -l default
crash_function: get_preferred_height_for_width
executable:     /usr/bin/gkbd-keyboard-display
global_pid:     3573
kernel:         4.9.3-200.fc25.x86_64
package:        libgnomekbd-3.22.0.1-1.fc25
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
reason:         gkbd-keyboard-display killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Unnoticed, X was switched. I switched from Xwayland to Xorg and I cured it. Clearly, I want to delete Xwayland because I can not use it.


(In reply to tacit.slager from comment #15)
> Similar problem has been detected:
> 
> After kernel 4.9.3, the keymap became a different thing. Switching is also
> not possible. why?

Similar problem has been detected:

typingbooster  in fr-fr looked like to be in qwerty, I wanted to make sure and by clicking on "display keyboard layout" in "lang and country" setting

reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        gkbd-keyboard-display -l default
crash_function: get_preferred_height_for_width
executable:     /usr/bin/gkbd-keyboard-display
global_pid:     11945
kernel:         4.10.14-200.fc25.x86_64
package:        libgnomekbd-3.22.0.1-1.fc25
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
reason:         gkbd-keyboard-display killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

(In reply to jibecfed from comment #17)
> Similar problem has been detected:
> 
> typingbooster  in fr-fr looked like to be in qwerty, I wanted to make sure
> and by clicking on "display keyboard layout" in "lang and country" setting

No, it typingbooster does not set any keyboard layout, it just uses
whatever keyboard layout is already set. I.e. when you select the
French "fr" keyboard layout first and then switch to typingbooster,
you will have a azerty layout, if you select the German keyboard
layout "de" first and then switch to typingbooster you will have a
quertz layout. For this it does not matter whether you are using
the fr-fr or any other variant of typingbooster.

Similar problem has been detected:

Crashes always when you show the keyboard layout of "Japanese (Kana kanji)".
But does not for other layout for Japanese, such as "Japanese (OADG 109A)".

reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        gkbd-keyboard-display -l default
crash_function: get_preferred_height_for_width
executable:     /usr/bin/gkbd-keyboard-display
global_pid:     4602
kernel:         4.10.17-200.fc25.x86_64
package:        libgnomekbd-3.22.0.1-1.fc25
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
reason:         gkbd-keyboard-display killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            483692

*** Bug 1494773 has been marked as a duplicate of this bug. ***

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.