Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1138886 - gnome-shell killed by SIGTRAP when logging in
Summary: gnome-shell killed by SIGTRAP when logging in
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 21
Hardware: i686
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-05 23:56 UTC by Chris Murphy
Modified: 2015-12-02 16:16 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 03:44:41 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
core_backtrace (1.78 KB, text/plain)
2014-09-05 23:58 UTC, Chris Murphy 		no flags Details
journal (185.65 KB, text/plain)
2014-09-06 00:00 UTC, Chris Murphy 		no flags Details
lspci (11.42 KB, text/plain)
2014-09-06 00:02 UTC, Chris Murphy 		no flags Details
maps (47.50 KB, text/plain)
2014-09-06 00:03 UTC, Chris Murphy 		no flags Details
coredump.tar.bz2 (1.72 MB, application/x-tar)
2014-09-06 00:06 UTC, Chris Murphy 		no flags Details
proc_pid_status (796 bytes, text/plain)
2014-09-06 00:07 UTC, Chris Murphy 		no flags Details
var_log_messages (1.66 KB, text/plain)
2014-09-06 00:09 UTC, Chris Murphy 		no flags Details
journal drm.debug=15 (218.48 KB, text/plain)
2014-09-06 00:48 UTC, Chris Murphy 		no flags Details
gdb backtrace attempt TC7 (5.56 KB, text/plain)
2014-09-13 05:11 UTC, Chris Murphy 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1138963 0 unspecified CLOSED caribou killed by SIGABRT when logging in 2022-05-16 11:32:56 UTC

Internal Links: 1138963

Description Chris Murphy 2014-09-05 23:56:10 UTC 
Description of problem: Rebooted from a successful F21 installation, when logging in, a message appears "Oh no! Something has gone wrong."


Version-Release number of selected component (if applicable):
gnome-shell-3.13.90-1.fc21.i686

How reproducible:
Always


Steps to Reproduce:
1. Install Fedora-Live-Workstation-i686-21_Alpha-TC6.iso
2. Reboot
3. Login

Actual results:

Oh no! Something has gone wrong.
gnome-session[1036]: WARNING: Application 'gnome-shell.desktop' killed by signal 5

Note that gnome-shell works OK when booted from USB stick. But upon reboot, gnome-shell crashes when logging in.

Expected results:

No crash.

Additional info:

Still occurs when choosing classic mode.
Comment 1 Chris Murphy 2014-09-05 23:58:29 UTC 
Created attachment 934923 [details]
core_backtrace
Comment 2 Chris Murphy 2014-09-06 00:00:08 UTC 
Created attachment 934924 [details]
journal

journalctl -b -l -o short-monotonic
Comment 3 Chris Murphy 2014-09-06 00:02:20 UTC 
Created attachment 934926 [details]
lspci

lspci -vvnn
Comment 4 Chris Murphy 2014-09-06 00:03:17 UTC 
Created attachment 934927 [details]
maps
Comment 5 Chris Murphy 2014-09-06 00:06:47 UTC 
Created attachment 934928 [details]
coredump.tar.bz2
Comment 6 Chris Murphy 2014-09-06 00:07:48 UTC 
Created attachment 934929 [details]
proc_pid_status
Comment 7 Chris Murphy 2014-09-06 00:09:22 UTC 
Created attachment 934930 [details]
var_log_messages
Comment 8 Chris Murphy 2014-09-06 00:48:21 UTC 
Created attachment 934932 [details]
journal drm.debug=15

Booted with drm.debug=15. Once at gdm, I ssh'd in and ran journalctl -f, then back on the problem machine I logged in. Thus this starts right before the problem manifests.
Comment 9 Chris Murphy 2014-09-06 01:56:02 UTC 
Reproduces with 
gnome-screenshot-3.13.90-1.fc21.i686
gnome-shell-3.13.91-1.fc21.i686
mutter-3.13.91-1.fc21.i686
And most of the updates listed in bodhi FEDORA-2014-10210
Comment 10 Chris Murphy 2014-09-06 19:15:20 UTC 
FEDORA-2014-10210 updates fully applied from repo. I get the same visual "On no! Something has gone wrong." But there are two crashes in journal. First /usr/libexec/caribou, then /usr/bin/gnome-shell. Filed bug 1138963 for caribou crash.
Comment 11 Chris Murphy 2014-09-13 05:11:25 UTC 
Created attachment 937159 [details]
gdb backtrace attempt TC7

Same results with Fedora-Live-Workstation-i686-21_Alpha-TC7.iso. This is an attempt to use gdb --core= on the coredump.
Comment 12 Fedora End Of Life 2015-11-04 15:09:47 UTC 
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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.
Comment 13 Fedora End Of Life 2015-12-02 03:44:44 UTC 
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.
Note You need to log in before you can comment on or make changes to this bug.