All those warning messages distracted me from what should have been obvious:
In my Fedora system, I hadn't installed enblend
With that fixed, I seem to have things working with the hugin executable I 
just built.

Are all those warnings normal?  Or are they something that should be 
investigated?

The system hang seems to be unrelated to either those warnings or the 
missing enblend.  Probably more random issues with that 340 driver.  
Probably I ought to buy a newer display card.
I mainly use open office calc and firefox on Fedora (I prefer to use hugin 
on Windows where I currently can't build it).  The nouveaux driver had 
problems like this all the time using just calc and firefox.  The nVidia 
driver never has problems in calc and firefox.  It messes up on operations 
like restoring after sleep.  Before starting this hugin experimentation, I 
never had any crashes using the 340 driver that weren't on mode changes.  
So maybe something else is going on.  But likely not a hugin issue.


On Saturday, January 22, 2022 at 11:25:07 AM UTC-5 [email protected] 
wrote:

> I ran the hugin I built.  I did not do the LD_LIBRARY_PATH thing Bruno 
> suggested in the other thread, because my system does have the lib64 setup 
> (lib is 64 bit) and because ldd indicated hugin had access to all the .so 
> files it needed without that.  I'll investigate whether something else 
> needs that after I reboot Linux (I'm typing this on windows before 
> rebooting a hung Linux machine).
>
> hugin initially seemed to be working.  I loaded a project I had stitched 
> (with poor results, but no specific malfunctions) using the Windows binary 
> release of hugin.
> Is there some problem in moving a hugin project from Windows to Fedora 
> and/or from the released hugin build to latest (today) from mercurial?
>
> When I stitched that, it gave the usual prompts (overwrite the previous 
> result files, etc.) then flashed a bunch of things on screen, then hung my 
> system (I think kdm is hung).
> The log file (on a fileserver, so I can see before rebooting linux) ends 
> with:
> Blending exposure layer 0...
> execvp(enblend, -f2658x5011, --compression=LZW, -o, 20220115_155306 - 
> 20220115_155319_exposure_0000.tif, --, 20220115_155306 - 
> 20220115_155319_exposure_layers_0000.tif) failed with error 2!
>
> The konsole window I ran it from scrolled through lots of error messages, 
> the still visible ones are variants on these:
> (PTBatcherGUI:4786): Gtk-WARNINGS **: 10:58:16.593: for_size smaller than 
> min_size (0 < 14) while measuring gadget (node check, owner GtkCheckButton)
> (PTBatcherGUI:4786): Gtk-WARNINGS **: 10:58:16.593: Negative content 
> height -2 (allocation 0, extents 1,1) while allocating gadget (node check, 
> owner GtkCheckButton) 
>
> The batch processor window is up with a status of failed.  Other windows 
> opened by the stitch action, closed right before the system hung.
>
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/1d0605e1-a44f-4ea8-a06d-95d52ecf5465n%40googlegroups.com.

Reply via email to