[Magick-bugs] ImageMarick 6.3.2-8 issue with fvwm2

[Rich Cook]

What it tells you is that your window manager is calling display as  
"./display," and that it is not passing any weird arguments to it.   
Maybe you knew that already, but I didn't, nor could anyone else  
reading your original question.
So next, wouldn't you like to know what display did when it was  
called?  If so, then answer these:

What about the modified version of the script?  What was its output?   
It will tell you how display responds to its invocation.

On Sep 12, 2007, at 2:03 PM, Toufique, Imam wrote:

> I looked at that log file before even I thought about replying your  
> e-mail.  The output for that file did not make sense to me.  Since  
> an earlier version of the this tool works "within" fvwm2, I can't  
> think of anything that would tell me that fvwm2 is the issue here.   
> Anyways, here is the display.debug output:
>
> display launched on Wed Sep 12 13:56:04 PDT 2007 as ./display
>
>
> -----Original Message-----
> From: Rich Cook [mailto:rcook at llnl.gov]
> Sent: Wednesday, September 12, 2007 1:15 PM
> To: Toufique, Imam
> Cc: magick-bugs at imagemagick.org
> Subject: Re: [Magick-bugs] ImageMarick 6.3.2-8 issue with fvwm2
>
> You are hilarious.  You have to actually read the file to get
> information from it.  LOL  It shows how the command is being executed
> by fvwm2, which might give you your answer.
>
> I have a better version of the script for you.  Let's say the path to
> the "real" display is /usr/local/bin/display.  Then your script
> should be like this.  If display is somewhere else, you'll have to
> change /usr/local/bin/display to whatever is correct.
> When you're done, then do this:
>
> cat $HOME/display.debug
>
>
> #!/usr/bin/env bash
> exec $HOME/display.debug 2>&1
> echo display launched on $(date) as $0 "$@"
> /usr/local/bin/display  "$@"
>
>
>   Note:  don't forget to do the chmod 775 thing on the script that's
> very important
>
> On Sep 12, 2007, at 12:52 PM, Toufique, Imam wrote:
>
>> I did exactly what you said, and the file appears in my home dir.
>> I am not sure what that proved though.
>>
>> Thanks for your help.
>>
>>
>> -----Original Message-----
>> From: Rich Cook [mailto:rcook at llnl.gov]
>> Sent: Wednesday, September 12, 2007 12:36 PM
>> To: Toufique, Imam
>> Cc: magick-bugs at imagemagick.org
>> Subject: Re: [Magick-bugs] ImageMarick 6.3.2-8 issue with fvwm2
>>
>> You need to find out what it means to "launch from an fvwm2 window
>> manager."  What does it do exactly?
>> One way to do this is to create a shell script, call it "display" and
>> put it in your PATH before ImageMagick's display.  Put the following
>> in the script:
>>
>> #!/usr/bin/env bash
>> echo display launched on $(date) as $0 $* > $HOME/display.debug
>>
>> Be sure to make this script executable:
>> chmod 755 display
>>
>> Now try to "launch from within fvwm2" .  A file called display.debug
>> should appear in your home directory.  If not, temporarily move the
>> "real" display program to display.backup and replace it with the
>> script from above.  If that doesn't work,  then fvwm2 is not actually
>> running display and your problem is with fvwm2, which it actually is
>> anyway.
>>
>>
>> On Sep 12, 2007, at 12:15 PM, Toufique, Imam wrote:
>>
>>> Hi,
>>>
>>>
>>>
>>> We have been using ImageMagick 6.1.7-5 version where we actually can
>>> launch the "display" command from fvwm2 window manager directly (not
>>> with any xterm support).  Recently we have compiled 6.3.5-8 version
>>> and
>>> we can no longer launch the "display" program within fvwm2
>>> anymore.  We
>>> launch this within an xterm as usual, but it no longer works  
>>> directly
>>> from an fvwm2 window manager.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Imam
>>>
>>> _______________________________________________
>>> Magick-bugs mailing list
>>> Magick-bugs at imagemagick.org
>>> http://studio.imagemagick.org/mailman/listinfo/magick-bugs
>>>
>>
>> -- 
>> ✐Richard Cook
>> ✇ Lawrence Livermore National Laboratory
>> Bldg-453 Rm-4037, Mail Stop L-557
>> 7000 East Avenue,  Livermore, CA, 94550, USA
>> ☎ (office) (925) 423-9605
>> ☎ (fax) (925) 423-6961
>> ---
>> Information Management & Graphics Grp., Services & Development Div.,
>> Integrated Computing & Communications Dept.
>> (opinions expressed herein are mine and not those of LLNL)
>>
>
> -- 
> ✐The primary task of most software projects is to discover and
> resolve these unknowns rather than to build a system. -- Philip G.
> Armour
> -- 
> Richard Cook
> ✇ Lawrence Livermore National Laboratory
> Bldg-453 Rm-4037, Mail Stop L-557
> 7000 East Avenue,  Livermore, CA, 94550, USA
> ☎ (office) (925) 423-9605
> ☎ (fax) (925) 423-6961
> ---
> Information Management & Graphics Grp., Services & Development Div.,
> Integrated Computing & Communications Dept.
> (opinions expressed herein are mine and not those of LLNL)
>

-- 
✐The primary task of most software projects is to discover and  
resolve these unknowns rather than to build a system. -- Philip G.  
Armour
-- 
Richard Cook
✇ Lawrence Livermore National Laboratory
Bldg-453 Rm-4037, Mail Stop L-557
7000 East Avenue,  Livermore, CA, 94550, USA
☎ (office) (925) 423-9605
☎ (fax) (925) 423-6961
---
Information Management & Graphics Grp., Services & Development Div.,  
Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)