Hide Forgot
abrt version: 1.1.18 architecture: i686 Attached file: backtrace, 27161 bytes cmdline: /usr/libexec/tracker-extract comment: Não sei se os erros reportados são problema no SElinux ou mesmo de algum erro que eu tenha comedito como meu Linux component: tracker Attached file: coredump, 26615808 bytes crash_function: __libc_free executable: /usr/libexec/tracker-extract kernel: 2.6.35.12-90.fc14.i686.PAE package: tracker-0.8.17-1.fc14 rating: 4 reason: Process /usr/libexec/tracker-extract was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1305058283 uid: 500 How to reproduce ----- 1.Simplesmente apareceu o aviso de erro. 2. 3.
Created attachment 498165 [details] File: backtrace
Package: tracker-0.8.17-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Não notei nada de errado, porem o sistema notou então vai ai o relatorio de erros. 2. 3.
Package: tracker-0.8.17-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Nâo sei o que está havendo, porém o SELinux está informando erros dessa natureza muitas vezes viu 2. 3.
Package: tracker-0.8.17-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Não notei nada de errado, porem o sistema notou ento vai ai o relatorio de erros. 2. 3.
Package: tracker-0.8.17-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.No notei nada de errado, porem o sistema notou ento vai ai o relatorio de erros. 2. 3.
Package: tracker-0.8.17-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2.Outro aviso que não sei por quê apareceu... 3.
Backtrace analysis found this bug to be similar to bug #710853, closing as duplicate. This bug seems to belong to component dbus-glib, dbus, gstreamer or gstreamer-plugins-base. Bugs which were found to be similar to this bug: rhythmbox: bug #628768, bug #655140 tracker: bug #710853 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 710853 ***