Bug 1415442
| Summary: | [abrt] gnome-session: match(): gnome-session-binary killed by SIGSEGV | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ed <samudhio> | ||||||||||||||||||||||||||||
| Component: | gnome-session | Assignee: | Ray Strode [halfline] <rstrode> | ||||||||||||||||||||||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||||||
| Version: | 25 | CC: | bugzilla49, jmccann, rstrode | ||||||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/c1625c4ba3429ba560debdfd55b9bec27ad1e23f | ||||||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:0c098393568d73dcb47e133167496341ce1cd434;VARIANT_ID=workstation; | ||||||||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||||||
| Last Closed: | 2017-12-12 10:48:24 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: | |||||||||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||||||
|
Description
Ed
2017-01-22 03:09:44 UTC
Created attachment 1243256 [details]
File: backtrace
Created attachment 1243257 [details]
File: cgroup
Created attachment 1243258 [details]
File: core_backtrace
Created attachment 1243259 [details]
File: dso_list
Created attachment 1243260 [details]
File: environ
Created attachment 1243261 [details]
File: exploitable
Created attachment 1243262 [details]
File: limits
Created attachment 1243263 [details]
File: maps
Created attachment 1243264 [details]
File: mountinfo
Created attachment 1243265 [details]
File: namespaces
Created attachment 1243266 [details]
File: open_fds
Created attachment 1243267 [details]
File: proc_pid_status
Created attachment 1243268 [details]
File: var_log_messages
I believe I am having the same problem. If I update gnome-session, the login screen shows up, but after I log in the screen freezes and do not show the desktop. In order to solve the problem I logged in a console session and downgraded gnome-session packages (gnome-session-wayland-session, gnome-session, gnome-session-xsession. @carlos: how i can downgrade in my system for test that ? thanks Hi, the command I used was: dnf downgrade gnome-session gnome-session-wayland-session gnome-session-xsession -y @carlos indeed that solve the problem , using the previous version it work , so this confirm this bug i guess but i think sadly only few ppl is having this bug tho :( I am uploading a log that has the session after update (with problems) and then another session after doing the downgrade. One thing that I notice that happens with the new package is: Jan 26 23:58:51 myhost gnome-keyring-daemon[2789]: module_instances: assertion 'funcs != NULL && "instances"' failed Jan 26 23:58:51 myhost gnome-keyring-daemon[2789]: module_instances: assertion 'funcs != NULL && "instances"' failed Jan 26 23:58:51 myhost gnome-keyring-daemon[2789]: egg_error_message: assertion 'error' failed Jan 26 23:58:51 myhost gnome-keyring-daemon[2789]: couldn't find secret store module: (unknown) Jan 26 23:58:51 myhost gnome-keyring-daemon[2789]: lookup_login_keyring: assertion 'GCK_IS_SESSION (session)' failed Jan 26 23:58:51 myhost gnome-keyring-daemon[2789]: create_credential: assertion 'GCK_IS_SESSION (session)' failed Jan 26 23:58:51 myhost gnome-keyring-daemon[2789]: egg_error_message: assertion 'error' failed Jan 26 23:58:51 myhost gnome-keyring-daemon[2789]: couldn't create login credential: (unknown) This do not happen with the old packages. 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. |