Thanks for the information and help.
I do have latest release.
The bug report you reference says:
“Creating the file at /etc/rmagic/ makes the error go away.”
But is it’s not clear to me how to create it (with any useful content?).
I just created an empty file in /etc/rmagic/standard.ini,
And indeed that error goes away, but I still then get:
# rmagic
Can't call method "Sections" on an undefined value at /usr/share/rmagic/wadg/rm/Settings.pm line 1124.
Seems that it is trying to get some (additional?) settings from a parameter file, but I haven’t given any parameters.
-------------------------------------------
Gregory Guthrie
-------------------------------------------
[statistics]
Thanks, yes, I found another post from you saying to just delete the “Include = standard.ini” instead of providing an empty one, and yes that got rid of that error!
I seem to be inching through various errors! Now I get:
c# rmagic
Report Magic 2.21
Copyright (C) 1999-2003 Wadsack-Allen. All rights reserved.
rmagic: WARNING: The setting "[graphs] Reverse_Time" is not recognized. It will be ignored.
gd warning: one parameter to a memory allocation multiplication is negative or zero, failing operation gracefully
Can't call method "can" on an undefined value at /usr/share/rmagic/wadg/rm/Settings.pm line 918.
The code there is:
unless( $g->can( $self->val( 'graphs', 'Format' ) ) ) {
/etc/rmagic.ini does have the line:
Format = png
And no reports generated.
Any hints?! J
Index: rmagic-2.21/wadg/rm/Settings.pm =================================================================== --- rmagic-2.21.orig/wadg/rm/Settings.pm 2007-10-06 12:54:34.000000000 +0200 +++ rmagic-2.21/wadg/rm/Settings.pm 2007-10-06 12:56:08.000000000 +0200 @@ -907,7 +907,7 @@ # Check GD for support of desired output format. If none # given or not capable, then set output format accordingly. # - my $g = new GD::Image(0,0); + my $g = new GD::Image(1,1); if( defined $self->val( 'graphs', 'Format' ) ) { if( $self->val( 'graphs', 'Format' ) =~ /jpe?g/i ) {
Yeah! Thanks.
Odd that the Debian package lacks this patch (from 2007!).