Red Hat Bugzilla – Bug 659920
[abrt] gnome-terminal-2.32.0-1.fc14: terminal_app_init: Process /usr/bin/gnome-terminal was killed by signal 6 (SIGABRT)
Last modified: 2012-03-30 09:02:42 EDT
abrt version: 1.1.14
Attached file: backtrace
comment: I was simply trying to launch the terminal when this occurred.
reason: Process /usr/bin/gnome-terminal was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
How to reproduce: 1. Clicked the gnome-terminal icon on the gnome panel
Created attachment 464709 [details]
I'm unable to launch gnome-terminal at all. It always fails with this error.
I found the following comment on a similar ubuntu bug which fixed this for me:
Apparently the problem was that while the schema files were copied correctly into /etc/gconf/schemas, they were not been properly installed into gconf.
Any ideas what would have caused this? I haven't manually built gnome-terminal from source and have only installed it from the official yum repositories.
OS Release: Fedora release 14 (Laughlin)
How to reproduce
I had package conflict between Nautilus-Elementary and Nautilus, thus 'yum update' didn't work.
I removed Nautilus-Elementary and installed Nautilus.
After this I ran 'yum update' and it said the update was successful. But awn crashed so I restarted my computer. Then Gnome Power Management crashed too. I logged in and tried to figure out what happened but the terminal (or anything which is GNOME related) crashes all the time.
Backtrace analysis found this bug to be similar to bug #755992, closing as duplicate.
Bugs which were found to be similar to this bug: bug #639456, bug #751904, bug #752246, bug #755992, bug #756018, bug #756047, bug #756391, bug #756546, bug #756837, bug #757179, bug #757366, bug #757369, bug #757603, bug #757682, bug #758087, bug #758715, bug #759713, bug #759733, bug #759835, bug #759951, bug #759952, bug #759953, bug #761373, bug #766222, bug #766436, bug #767386, bug #768092, bug #768677
This comment is automatically generated.
*** This bug has been marked as a duplicate of bug 755992 ***