Bug 722687

Summary: [abrt] tkgate-2.0-10.beta10.fc14: __libc_message: Process /usr/bin/tkgate was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Gary Morris <gwmorris>
Component: tkgateAssignee: Thibault North <thibault.north>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: chitlesh, thibault.north
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:72ee37ab2ee75a640b76c3eb3f1f629d44a5073a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 16:30:33 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 Gary Morris 2011-07-16 14:27:20 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 28341 bytes
cmdline: tkgate
component: tkgate
Attached file: coredump, 130699264 bytes
crash_function: __libc_message
executable: /usr/bin/tkgate
kernel: 2.6.35.13-92.fc14.i686
package: tkgate-2.0-10.beta10.fc14
rating: 4
reason: Process /usr/bin/tkgate was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1310825340
uid: 503

comment
-----
Yeah, somewhere in there is buggy or mishandled code, but I doubt I could ever
say where! I guess this is probably written in C/C++ anyway, neither of which I do
much of anything with if I can avoid it, so I can't help there. If it's Java, I may be
able to do something. I know how close they are in certain syntax, I just despise
using header files, and there are always dozens of constants and those "alias"
type things, oh yeah TypeDefs. If I didn't write it, I'm gonna be a while fixing it.

Hope you get this figured out, it might be a cool program if it can run without
continually crashing!

How to reproduce
-----
1. All seemed OK.
2. Then, the program just "aborted", stopped
3. That's it!

Comment 1 Gary Morris 2011-07-16 14:27:22 UTC
Created attachment 513489 [details]
File: backtrace

Comment 2 Gary Morris 2011-07-22 15:25:29 UTC
Package: tkgate-2.0-10.beta10.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. All seemed OK.
2. Then, the program just "aborted", stopped
3. About the same as last time, I had to log in to a console and kill the process, it was LOCKED!


Comment
-----
I made some comments last time, not really much to add. I had JUST started to log in and the screensaver kicked in and froze. No more GUI until I killed the process!

Comment 3 Gary Morris 2011-07-23 13:45:30 UTC
Package: tkgate-2.0-10.beta10.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. All seemed OK.
2. Then, the program just "aborted", stopped
3. About the same as last time, I had to log in to a console and kill the process, it was LOCKED!


Comment
-----
I made some comments last time, not really much to add. I had JUST started to log in and the screensaver kicked in and froze. No more GUI until I killed the process!

07-23-2011: Just about the same thing. I had to open a console and kill it again, then everything seems to work OK (for now).

Comment 4 Chitlesh GOORAH 2011-12-05 12:07:39 UTC
Ok, I don't understand anything except you despise using headers.

Can you please attach the schematic/file you are using when tkgate freezes ?
If this issue occurs everytime, then define the step-by-step actions you performed till tkgate freezes.

Comment 5 Fedora End Of Life 2012-08-16 16:30:35 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