Fedora Account System
Red Hat Associate
Red Hat Customer
Version-Release number of selected component: libgnomekbd-3.26.1-1.fc30 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: gkbd-keyboard-display -l default crash_function: get_preferred_height_for_width executable: /usr/bin/gkbd-keyboard-display journald_cursor: s=0322542d8a744f7e9c0139b3a1acd662;i=6559;b=af32c843b7e34cb6b102289eef896672;m=321ec47a3;t=5852c8e1472b2;x=2b4b737600f78f0a kernel: 5.0.4-300.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 get_preferred_height_for_width at gkbd-keyboard-drawing.c:2145 #1 gtk_widget_query_size_for_orientation at gtksizerequest.c:246 #2 gtk_widget_compute_size_for_orientation at gtksizerequest.c:399 #3 gtk_widget_get_preferred_height_for_width at gtksizerequest.c:601 #4 gtk_box_compute_size_for_orientation at gtkbox.c:1986 #5 gtk_box_get_content_size at gtkbox.c:2079 #6 gtk_css_custom_gadget_get_preferred_size at gtkcsscustomgadget.c:124 #7 gtk_css_gadget_get_preferred_size at gtkcssgadget.c:683 #8 gtk_box_get_preferred_height_and_baseline_for_width at gtkbox.c:2046 #9 gtk_widget_query_size_for_orientation at gtksizerequest.c:242 Potential duplicate: bug 1500721
Created attachment 1549202 [details] File: backtrace
Created attachment 1549203 [details] File: cgroup
Created attachment 1549204 [details] File: core_backtrace
Created attachment 1549205 [details] File: cpuinfo
Created attachment 1549206 [details] File: dso_list
Created attachment 1549207 [details] File: environ
Created attachment 1549208 [details] File: exploitable
Created attachment 1549209 [details] File: limits
Created attachment 1549210 [details] File: maps
Created attachment 1549211 [details] File: mountinfo
Created attachment 1549212 [details] File: open_fds
Created attachment 1549213 [details] File: proc_pid_status
*** Bug 1699481 has been marked as a duplicate of this bug. ***
*** Bug 1704834 has been marked as a duplicate of this bug. ***
*** Bug 1713960 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Added French input method, and tried to see the keyboard layout. I did this, removed methods a few times---I wasn't sure which I wanted to use. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: gkbd-keyboard-display -l default crash_function: get_preferred_height_for_width executable: /usr/bin/gkbd-keyboard-display journald_cursor: s=7b0489368c2c48cea2e6385bf380f635;i=79ba8;b=5aa60bed1f664dd98e009a9f1de6c6e6;m=2ef3df95f5;t=589de704dbd59;x=9a1e04d34e5adeab kernel: 5.0.17-300.fc30.x86_64 package: libgnomekbd-3.26.1-1.fc30 reason: gkbd-keyboard-display killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1715286 has been marked as a duplicate of this bug. ***
*** Bug 1715298 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Added Typing Booster keyboard input method, switched to it, in corresponding Gnome Shell dropdown menu clicked on "Show Keyboard Layout". reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: gkbd-keyboard-display -l default crash_function: get_preferred_height_for_width executable: /usr/bin/gkbd-keyboard-display journald_cursor: s=62900d571cda47109566bcdcfdecc7e4;i=13b03;b=33c1142b893c452f90b91667fdbc1139;m=e3c9e208b;t=58a8d5709ba56;x=c552e93cdd223bf kernel: 5.1.5-300.fc30.x86_64 package: libgnomekbd-3.26.1-1.fc30 reason: gkbd-keyboard-display killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1717404 has been marked as a duplicate of this bug. ***
*** Bug 1727513 has been marked as a duplicate of this bug. ***
*** Bug 1733056 has been marked as a duplicate of this bug. ***
*** Bug 1734224 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Run command: gkbd-keyboard-display -l us,intl gkbd-keyboard-display -l intl gkbd-keyboard-display -l default I guess any -l option value not known keyboard name will dump core. Previously reported as: https://bugzilla.redhat.com/show_bug.cgi?id=1572234 reporter: libreport-2.10.1 backtrace_rating: 4 cmdline: gkbd-keyboard-display -l us,intl crash_function: get_preferred_height_for_width event_log: executable: /usr/bin/gkbd-keyboard-display journald_cursor: s=419c81e514024c48a9310795ec5a8bcf;i=92097;b=e92e686750944c56a99bd90440521faf;m=2e86211926;t=5912e14dd74e8;x=25f2420cebb2c4b5 kernel: 5.2.9-200.fc30.x86_64 package: libgnomekbd-3.26.1-1.fc30 reason: gkbd-keyboard-display killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1972
*** Bug 1751341 has been marked as a duplicate of this bug. ***
*** Bug 1759238 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. 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 '30'. 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 30 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 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.