Bug 678360

Summary: [abrt] seahorse-plugins-2.30.1-5.fc14: Process /usr/bin/seahorse-agent was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Robert V. Miciovici <robert.miciovici>
Component: seahorse-pluginsAssignee: Matthias Clasen <mclasen>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: mclasen, scott, sylvain, tbzatek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:ae54b22f3507112d0c249b3aee11935791f85ec3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 14:22:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Robert V. Miciovici 2011-02-17 17:12:54 UTC 
abrt version: 1.1.14
architecture: x86_64
cmdline: /usr/bin/seahorse-agent --variables
comment: dunno
component: seahorse-plugins
executable: /usr/bin/seahorse-agent
kernel: 2.6.35.10-74.fc14.x86_64
package: seahorse-plugins-2.30.1-5.fc14
reason: Process /usr/bin/seahorse-agent was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1296780818
uid: 500

backtrace
-----
[New Thread 2407]
[New Thread 2426]
warning: .dynamic section for "/lib64/libpthread.so.0" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib64/librt.so.1" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib64/libc.so.6" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib64/libresolv.so.2" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib64/ld-linux-x86-64.so.2" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib64/libnss_files.so.2" is not at the expected address (wrong library or version mismatch?)
warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
../../gdb/linux-thread-db.c:1048: internal-error: attach_thread: Assertion `ti_p->ti_tid != 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]
../../gdb/linux-thread-db.c:1048: internal-error: attach_thread: Assertion `ti_p->ti_tid != 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]

How to reproduce
-----
1.
2.
3.
dunno
Comment 1 Robert V. Miciovici 2011-02-17 17:12:57 UTC 
Created attachment 479367 [details]
File: backtrace
Comment 2 Scott Douglass 2011-02-17 19:29:26 UTC 
Package: seahorse-plugins-2.30.1-5.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.launched seahorse
2.
3.
Comment 3 Sylvain Arth 2011-02-18 09:06:04 UTC 
Package: seahorse-plugins-2.30.1-5.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.After a power failure
2.
3.


Comment
-----
Screen was not at the default and usual resolution but low
First login failed (xserver ?) and went back to my usual resolution
Then login was sucessful then I find the abrt warning
It's not the fisrt time such thing happens. It usually is without any power failure but leads tu unusuable tracebacks
Comment 4 Fedora End Of Life 2012-08-16 14:22:45 UTC 
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping