Hide Forgot
abrt version: 1.1.18 architecture: x86_64 Attached file: backtrace, 9591 bytes cmdline: /usr/bin/gconftool-2 --shutdown component: GConf2 Attached file: coredump, 9269248 bytes crash_function: initable_init executable: /usr/bin/gconftool-2 kernel: 2.6.35.12-88.fc14.x86_64 package: GConf2-2.31.91-1.fc14 rating: 4 reason: Process /usr/bin/gconftool-2 was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) How to reproduce: Don't know how this happened... time: 1303325976 uid: 500
Created attachment 496070 [details] File: backtrace
Package: GConf2-2.31.91-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I do not remember...
Package: GConf2-2.31.91-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Using firefox
Package: GConf2-2.31.91-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Je ne sais pas comment cela s'est produit. 2. 3.
Package: GConf2-2.31.91-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. watching youtube 2. friend message at empathy
Package: GConf2-2.31.91-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. Don't know
Package: GConf2-2.31.91-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.normal use... nothing fancy 2. 3.
Package: GConf2-2.31.91-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.no idea 2. 3.
Package: GConf2-2.31.91-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- I don't know, see it a report it
Package: GConf2-2.31.91-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. On first boot after being forced to enable SELinux again and relabel filesystem 2. unknown how to recreate yet 3.
Backtrace analysis found this bug to be similar to bug #658318, closing as duplicate. Bugs which were found to be similar to this bug: bug #658318, bug #669344, bug #677551 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 658318 ***