Red Hat Bugzilla – Bug 1002524
[abrt] gnome-shell-3.8.3-2.fc19: g_logv: Process /usr/bin/gnome-shell was killed by signal 5 (SIGTRAP)
Last modified: 2015-02-19 11:02:08 EST
Description of problem:
screen suddenly froze for no apparent reason and I had to kill X. I do not know how to reproduce it.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (5 frames)
#0 g_logv at /lib64/libglib-2.0.so.0
#1 g_log at /lib64/libglib-2.0.so.0
#2 g_wakeup_new at /lib64/libglib-2.0.so.0
#3 g_main_context_new at /lib64/libglib-2.0.so.0
#4 g_dbus_connection_send_message_with_reply_sync at /lib64/libgio-2.0.so.0
Created attachment 791730 [details]
Created attachment 791731 [details]
Created attachment 791732 [details]
Created attachment 791733 [details]
Created attachment 791734 [details]
Created attachment 791735 [details]
Created attachment 791736 [details]
Created attachment 791738 [details]
Created attachment 791739 [details]
Created attachment 791740 [details]
Three similar crashes of gnome shell occurred after a fresh install of fedora 19. However, I did preserve the /home partition so that the configuration directories such as ~/.config ~/.gnome2 ~/.gconf contained files accumulated from previous upgrades.
I 'rm -rf' these directories and restarted gnome to repopulate them and then reconfigured them. So far I have had no further crashes.
i dont know
reason: Process /usr/bin/gnome-shell was killed by signal 5 (SIGTRAP)
runlevel: N 5
Steps to reproduce on my fc 19 box:
1) open gnome-terminal
2) login as root $ su -
3) open some file with gedit # gedit /var/log/messages &
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.
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
Thank you for reporting this bug and we are sorry it could not be fixed.