Bug 795110 - [abrt] gnome-shell-3.3.5-2.fc17: Process /usr/bin/gnome-shell was killed by signal 6 (SIGABRT)
Summary: [abrt] gnome-shell-3.3.5-2.fc17: Process /usr/bin/gnome-shell was killed by s...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 19
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:87e91b0daa7bb100fcaef56aafe...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-19 13:02 UTC by Jared Smith
Modified: 2015-02-17 14:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 14:07:50 UTC
Type: ---


Attachments (Terms of Use)
File: dso_list (21.50 KB, text/plain)
2012-02-19 13:02 UTC, Jared Smith
no flags Details
File: build_ids (7.33 KB, text/plain)
2012-02-19 13:02 UTC, Jared Smith
no flags Details
File: var_log_messages (4.77 KB, text/plain)
2012-02-19 13:02 UTC, Jared Smith
no flags Details
File: backtrace (57.67 KB, text/plain)
2012-02-19 13:02 UTC, Jared Smith
no flags Details
File: maps (56.19 KB, text/plain)
2012-02-19 13:02 UTC, Jared Smith
no flags Details

Description Jared Smith 2012-02-19 13:02:31 UTC
libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
comment:        Click on your username in the top bar, select System Settings.  Select Universal Access.  Select the Typing tab.  Turn on the Typing Assistant, and then attempt to turn it back off.  This will crash Gnome shell.
executable:     /usr/bin/gnome-shell
kernel:         3.3.0-0.rc3.git6.2.fc18.i686
pid:            8032
pwd:            /home/wanda
reason:         Process /usr/bin/gnome-shell was killed by signal 6 (SIGABRT)
time:           Sun 19 Feb 2012 06:24:42 AM EST
uid:            1000
username:       wanda

backtrace:      Text file, 59059 bytes
build_ids:      Text file, 7503 bytes
dso_list:       Text file, 22017 bytes
maps:           Text file, 57535 bytes
var_log_messages: Text file, 4881 bytes

environ:
:XDG_VTNR=3
:XDG_SESSION_ID=18
:HOSTNAME=wanda
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:SHELL=/bin/bash
:TERM=dumb
:HISTSIZE=1000
:GNOME_KEYRING_CONTROL=/tmp/keyring-esmBi1
:IMSETTINGS_MODULE=none
:USER=wanda
:USERNAME=wanda
:MAIL=/var/spool/mail/wanda
:PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/home/wanda/.local/bin:/home/wanda/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/wanda
:XMODIFIERS=@im=none
:GNOME_KEYRING_PID=7562
:LANG=en_US.utf8
:GDM_LANG=en_US.utf8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:XDG_SEAT=seat0
:HOME=/home/wanda
:SHLVL=1
:LOGNAME=wanda
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-AQySpJGsGd,guid=dcc44a43116dbcb331c8f20200001a88
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=3
:XDG_RUNTIME_DIR=/run/user/wanda
:DISPLAY=:0
:XAUTHORITY=/var/run/gdm/auth-for-wanda-jTSDjt/database
:_=/usr/bin/gnome-session
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/7574,unix/unix:/tmp/.ICE-unix/7574
:SSH_AUTH_SOCK=/tmp/keyring-esmBi1/ssh
:GPG_AGENT_INFO=/tmp/keyring-esmBi1/gpg:0:1
:DESKTOP_AUTOSTART_ID=109d4c5ee7adc1fa24132965045230636500000075740000

Comment 1 Jared Smith 2012-02-19 13:02:35 UTC
Created attachment 564176 [details]
File: dso_list

Comment 2 Jared Smith 2012-02-19 13:02:37 UTC
Created attachment 564177 [details]
File: build_ids

Comment 3 Jared Smith 2012-02-19 13:02:39 UTC
Created attachment 564178 [details]
File: var_log_messages

Comment 4 Jared Smith 2012-02-19 13:02:41 UTC
Created attachment 564179 [details]
File: backtrace

Comment 5 Jared Smith 2012-02-19 13:02:43 UTC
Created attachment 564180 [details]
File: maps

Comment 6 Fedora End Of Life 2013-04-03 16:39:29 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 7 Fedora End Of Life 2015-01-09 17:01:21 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 8 Fedora End Of Life 2015-02-17 14:07:50 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.