Current value unavailable in Cricket grapher
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cricket (Debian) |
Fix Released
|
Unknown
|
|||
cricket (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: cricket
Description: Ubuntu 10.04.1 LTS
Release: 10.04
cricket:
Installed: 1.0.5-11
Candidate: 1.0.5-11
Version table:
*** 1.0.5-11 0
500 http://
100 /var/lib/
The current value data is missing/incorrect in Cricket grapher. Searching bug reports found same bug reported in earlier version of Ubuntu under bug #64403 (also listed as duplicate to 54659). A patch was listed in #64403 to fix issue with x86_64 architecture.
The file (RRD/Format.pm) supplied with cricket 1.0.5-11 is close to patch listed in bug #64403. However the slight difference did cause the current value data to be incorrect (either 0 or -nan). By modifying RRD/Format.pm to same as listed in patch for but #64403, the current value is displayed correctly by the Cricket grapher on my system architecture (x86_64).
I am unable to test package on other x86_64 systems to determine if anything specific to my platform, but the following patch fixes issue on my host.
--- Format.pm.orig 2010-12-07 22:46:23.526041539 -0600
+++ /usr/share/
@@ -164,7 +164,7 @@
- $self->{'liveHead'} = "Q";
+ $self->{'liveHead'} = "Q Q";
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: cricket 1.0.5-11 [modified: usr/share/
ProcVersionSign
Uname: Linux 2.6.32-26-server x86_64
Architecture: amd64
Date: Tue Dec 7 23:18:22 2010
InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2)
PackageArchitec
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cricket
Related branches
tags: | added: patch |
tags: |
added: patch-forwarded-debian removed: patch |
Changed in cricket (Debian): | |
status: | Unknown → New |
Changed in cricket (Debian): | |
status: | New → Fix Released |
Slight correction of previous comment:
The version of Format.pm supplied with cricket 1.0.5-11 is patched in manner described in comments for bug #64403 but the fix for my host was to use the patch in the attachment for bug #64403. It appears the incorrect version of patch was applied to 1.0.5-11 and needs to be updated to listed difference.