Bug 675592

Summary: [abrt] gkrellm-2.3.4-3.fc14: after calling strftime
Product: [Fedora] Fedora Reporter: bugzilla
Component: gkrellmAssignee: Hans de Goede <hdegoede>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: bugzilla, gary, hdegoede, Stof, ville.skytta
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:a42186c18e891c22d96a0fe92a19970c4b6409f5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 848819 907632 (view as bug list) Environment:
Last Closed: 2012-08-16 13:21:25 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
File: backtrace none

Description bugzilla 2011-02-06 21:19:36 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/gkrellm --server resolver.local.thestof.com --sm-client-id 1016911d10f8a000129348564400000020510153
comment: The software will crash at random intervals, ranging from minuts to hours or days. The grellmd on the remote host keeps on running.
component: gkrellm
crash_function: gkrellm_abort
executable: /usr/bin/gkrellm
kernel: 2.6.35.10-74.fc14.i686.PAE
package: gkrellm-2.3.4-3.fc14
rating: 4
reason: Process /usr/bin/gkrellm was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1297026963
uid: 500

How to reproduce
-----
1. Start gkrellmd on another host
2. Connect to the gkrellmd on the other host with the command line option --server
3. Let it run

Comment 1 bugzilla 2011-02-06 21:19:38 UTC
Created attachment 477333 [details]
File: backtrace

Comment 2 Stof 2011-02-06 22:38:48 UTC
Forgot to mention that the remote host is an FC9 x86_64 machine.

Comment 3 Stof 2011-02-25 13:14:18 UTC
It also happens with an FC14 x86_64 machine as a remote host.

Hope this helps.

Comment 4 Hans de Goede 2012-01-23 08:40:29 UTC
*** Bug 783774 has been marked as a duplicate of this bug. ***

Comment 5 Gary Thomas 2012-01-23 11:02:19 UTC
I see these messages on the machine where it fails:

$ gkrellm -s thor.analogue-micro-ltd.com
gkrellm segmentation fault:  Clock  (update_monitor)
Warning: Missing charsets in String to FontSet conversion

Note: this happens consistently on my system where the gkrellm (local graphic
program) runs and the server is on a machine 6000+ miles away.  If I saturate
the network link, eventually gkrellm will die like this...

Comment 6 Stephan Bergmann 2012-06-14 09:27:56 UTC
Machine was under heavy load at time of crash, trying to run lots of JVMs (some of which also failed with strange symptoms, so this might just be a bad out-of-memory condition).

backtrace_rating: 4
Package: gkrellm-2.3.5-9.fc17
Architecture: x86_64
OS Release: Fedora release 17 (Beefy Miracle)

Comment 7 Stephan Bergmann 2012-06-14 09:28:02 UTC
Created attachment 591787 [details]
File: backtrace

Comment 8 Fedora End Of Life 2012-08-16 13:21:29 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