Bug 23256

Summary: xscanimage says "xscanimage is a gimp plug-in..."
Product: [Retired] Red Hat Linux Reporter: Jonathan Kamens <jik>
Component: gimpAssignee: Matt Wilson <msw>
Status: CLOSED CURRENTRELEASE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-10-16 18:34:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Here's a patch to make xscanimage say 'ignore this:' first. none

Description Jonathan Kamens 2001-01-03 23:02:04 UTC 
I just upgraded to gimp-1.1.25-1 and sane-1.0.3-2.  Now, whenever I run
xscanimage from the command line, it prints, "xscanimage is a gimp plug-in
and must be run by the gimp to be used," then it starts up as it used to. 
It's supposed to be runnable from the command line OR from inside gimp, so
I don't understand why it's printing this message, and since it IS printing
this message, I don't understand why it's starting up.
Comment 1 Tim Waugh 2001-01-04 13:55:55 UTC 
The trick that xscanimage uses to shut gimp_main up (installing a no-nothing
print function) no longer works.
Comment 2 Tim Waugh 2001-01-04 13:56:55 UTC 
Created attachment 7043 [details]
Here's a patch to make xscanimage say 'ignore this:' first.
Comment 3 Tim Waugh 2001-01-08 15:11:10 UTC 
Hmm, on seconds thoughts this seems to be a deficiency on gimp's part.  xmorph
has the same trouble, for example.
Comment 4 Matt Wilson 2003-10-16 18:34:05 UTC 
I don't think this is a problem anymore.