Bug 1507656
| Summary: | Crashes trying to set keyboard map when logging in | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Peter <peter> | ||||||||||||||||||||||||||
| Component: | gnome-shell | Assignee: | Owen Taylor <otaylor> | ||||||||||||||||||||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||||
| Version: | 28 | CC: | debarshir, esauloff, faber, fedora, fmuellner, Gecko8211, gnome-sig, jfrieben, mcepl, michael.scheiffler, mikhail.v.gavrilov, otaylor, pantelis.fedora, riototype, yonatan.el.amigo | ||||||||||||||||||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/17c0afe54f67a23d7c28f69958affec29fd9d094 | ||||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:c50731d04df538049ea732054a5625b4389d0b2e;VARIANT_ID=workstation; | ||||||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||
| Clone Of: | |||||||||||||||||||||||||||||
| : | 1543128 (view as bug list) | Environment: | |||||||||||||||||||||||||||
| Last Closed: | 2019-05-28 19:05:31 UTC | Type: | --- | ||||||||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||||||||
| Bug Depends On: | |||||||||||||||||||||||||||||
| Bug Blocks: | 1543128 | ||||||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||||
|
Description
Peter
2017-10-30 20:08:21 UTC
Created attachment 1345587 [details]
File: backtrace
Created attachment 1345588 [details]
File: cgroup
Created attachment 1345589 [details]
File: core_backtrace
Created attachment 1345590 [details]
File: cpuinfo
Created attachment 1345592 [details]
File: dso_list
Created attachment 1345593 [details]
File: environ
Created attachment 1345594 [details]
File: exploitable
Created attachment 1345595 [details]
File: limits
Created attachment 1345596 [details]
File: maps
Created attachment 1345597 [details]
File: open_fds
Created attachment 1345598 [details]
File: proc_pid_status
Created attachment 1345599 [details]
File: var_log_messages
I am seeing this crash quite often on login, where gnome-shell crashes before having finished startup, and which results in an Xwayland crash: https://bugzilla.redhat.com/show_bug.cgi?id=1510078 Also, the crash has been present for a few releases: https://bugzilla.redhat.com/show_bug.cgi?id=1398128 https://bugzilla.redhat.com/show_bug.cgi?id=1398142 https://bugzilla.redhat.com/show_bug.cgi?id=1441490 More details and a few hints what might cause the bug can be found upstream: https://bugzilla.gnome.org/show_bug.cgi?id=782688 Just in case, this is the logging output before the crash from xkbcommon: Nov 29 20:17:53 hostname org.gnome.Shell.desktop[2161]: xkbcommon: ERROR: Couldn't find file "rules/evdev" in include paths Nov 29 20:17:53 hostname org.gnome.Shell.desktop[2161]: xkbcommon: ERROR: 1 include paths searched: Nov 29 20:17:53 hostname org.gnome.Shell.desktop[2161]: xkbcommon: ERROR: /usr/share/X11/xkb Nov 29 20:17:53 hostname org.gnome.Shell.desktop[2161]: xkbcommon: ERROR: 1 include paths could not be added: Nov 29 20:17:53 hostname org.gnome.Shell.desktop[2161]: xkbcommon: ERROR: /home/username/.xkb Nov 29 20:17:53 hostname org.gnome.Shell.desktop[2161]: xkbcommon: ERROR: Couldn't look up rules 'evdev', model 'pc105+inet', layout 'de,de,us,de', variant 'neo,nodeadkeys,,', options 'grp:sclk_toggle' Nov 29 20:17:53 hostname kernel: show_signal_msg: 51 callbacks suppressed Similar problem has been detected: just login into system with Wayland session reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: xkb_keymap_ref executable: /usr/bin/gnome-shell journald_cursor: s=76d2444e84524432975cafac5aee4189;i=43be;b=12b9130fb96040639cb156369526bbe1;m=33b743f;t=55fb15ea0db39;x=3a0c58ae732ae94b kernel: 4.15.0-rc2-amd-vega+ package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000 *** Bug 1538656 has been marked as a duplicate of this bug. *** Attempted to login. gnome-shell crashed. A second login succeeded. Happens maybe once a week or so. reason: xkb_keymap_ref(): gnome-shell killed by SIGSEGV time: Wed 23 May 2018 08:33:46 AM EDT cmdline: /usr/bin/gnome-shell package: gnome-shell-3.26.2-5.fc27 :May 23 08:33:28 gecko1.bugbane-hollow gnome-shell[14217]: GNOME Shell started at Wed May 23 2018 08:33:25 GMT-0400 (EDT) :May 23 08:33:41 gecko1.bugbane-hollow org.gnome.Shell.desktop[14217]: xkbcommon: ERROR: Couldn't find file "rules/evdev" in include paths :May 23 08:33:41 gecko1.bugbane-hollow org.gnome.Shell.desktop[14217]: xkbcommon: ERROR: 1 include paths searched: :May 23 08:33:41 gecko1.bugbane-hollow org.gnome.Shell.desktop[14217]: xkbcommon: ERROR: /usr/share/X11/xkb :May 23 08:33:41 gecko1.bugbane-hollow org.gnome.Shell.desktop[14217]: xkbcommon: ERROR: 1 include paths could not be added: :May 23 08:33:41 gecko1.bugbane-hollow org.gnome.Shell.desktop[14217]: xkbcommon: ERROR: /home/dswaner/.xkb :May 23 08:33:41 gecko1.bugbane-hollow org.gnome.Shell.desktop[14217]: xkbcommon: ERROR: Couldn't look up rules 'evdev', model 'pc105+inet', layout 'us,us', variant ',', options '' :May 23 08:33:44 gecko1.bugbane-hollow org.gnome.Shell.desktop[14217]: (EE) failed to read Wayland events: Broken pipe Today I logged in and out of the desktop about 12 times, and 4 times this abrt happened - the second login attempt always succeeded. Still happening in F28. *** Bug 1441490 has been marked as a duplicate of this bug. *** *** Bug 1398128 has been marked as a duplicate of this bug. *** *** Bug 1398142 has been marked as a duplicate of this bug. *** Would be great if this bug gets a higher priority assigned. I'm dealing with that issue for at least a year now. Background information: I installed the Fedora 28 with the language English (United Kingdom) and German keyboard layout. Further, a couple of other bugs seem to be related: bug 1559256 bug 1579811 bug 1584589 Thanks a lot in advance. This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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. Reopening as of comment #24. Do you still see this bug in Fedora 29? This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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. |