hugin-devs team mailing list archive

[Yuv <700896@xxxxxxxxxxxxxxxxxx>]

Hi Terry,

thanks for testing.

You can dock again the overview by dragging it on the boder of the
preview.

I could not reproduce the crash here.  Tried with both the overview
docked and undocked.  Can you reproduce consistently?  I suspect a
spurious bug that has to do with images loading.

Hugin has an inconsistent behavior regarding FPW (and this already before the introduction of the overview):
* when I close Hugin with the FPW open, starting it again opens the empty FPW.
* when I close Hugin with the FPW closed, starting it again opens only the main window and I can not click on the button to open the FPW until there are images available (makes sense).

It is possible that the error you observe is due to opening the
FPW/Overview with images unavailable.  A shortcut to prevent it from
happening is to simply not open the FPW when starting Hugin without
images or a project file.

** Tags added: overview preview

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/700896

Title:
  hugin default branch (hg41621fb36f15) crashes

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  First time run of this version (Panorama-overview) was OK. Panosphere view was shown in pane to left of fast preview window. Selecting the little 'pin' icon changed panosphere view to separate window. Couldn't see how to switch it back to a FPW pane.
Second time I run this version, FPW opens after alignment, image briefly shown, then a mangled image appeared, then hugin crashed.
I ran again from terminal which provided the following;
(hugin:3157): Gdk-WARNING **: gdkdrawable-x11.c:952 drawable is not a pixmap or window

Gdk-ERROR **: The program 'hugin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadDrawable'.
  (Details: serial 35575 error_code 149 request_code 136 minor_code 11)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...

[1]+  Aborted                 (core dumped) hugin

Unfortunately, the abrt tool deletes the core dump, and not sure at this time how to get around that.
The binary was built on fedora 14 x86_64.

Hope this helps.

Cheers,
Terry