Hugin freezes after alignment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hugin (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I just tried to do another long (14 picture) panorama (also with a tripod).
This one had a wide brightness range, which was eventually going to cause a problem, but I told it to go ahead and align it anyway.
In two different runs-through, I got two slightly different results:
1: Alignment finished, but I could see a problem between what appeared to be photos 8 and 9.
I tried to call up the window where I could manually enter control points.
Window comes up - blank. Nothing more. Had to kill the process.
2: The second time around, I noticed that it could find no control points between Photo 8 and 9.
Not surprising, but when it finished, it put up a window, and then an error box but both were blank, and nothing further was possible, except killing the process.
A third time, I started Hugin from the terminal.
some gtk-critical warnings and some info came up immediately, but until I reached the blank-window=
Then, I got:
"(hugin:4321): Gtk-WARNING **: gtk_widget_
(hugin:4321): Gtk-WARNING **: gtk_widget_
"
The gtk critical warnings i then noted were also widget-based, so I will mention that there were 12 identical lines:
"(hugin:4321): Gtk-CRITICAL **: IA__gtk_
"
I will attach a text file with the complete terminal output.
This appears to be a freeze/endless loop, as when I brought up HTOP, one or other of my CPU cores was (almost) always at a full 100%
-------
scott@scott-
Linux scott-Asus-
scott@scott-
Ubuntu 17.10
artful
scott@scott-
QLubuntu
scott@scott-
hugin:
Installed: 2018.1.
Candidate: 2018.1.
Version table:
*** 2018.1.
500 http://
100 /var/lib/
2017.
500 http://
(I was using 2017.0.0~rc2+dfsg-2 (Standard for [L]ubuntu 17.10) originally, but noted that
elsewhere, a more recent version was available, and thought that perhaps the "bug" (?) had been fixed there. Alas, no...
Hugin itself prints "2018.1.
(I don't print the pkgs for enblend/enfuse here, as it never gets that far...)
-------
The attached screenshot shows what the desktop with the empty window and empty Error box looks like, after going away to a different desktop (to file this bug) and then returning to it.
Part of the window gets erased, but not redrawn with anything, and hence remains blank, and the rest doesn't even get redrawn.
The error box gets erased and redrawn blank.