hugin-devs team mailing list archive

[tmodes <1305138@xxxxxxxxxxxxxxxxxx>]

Which Hugin version? Try at least the last released version 2013.0.

** Changed in: hugin
       Status: New => Incomplete

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

Title:
  Hugin aborts on startup

Status in Hugin - Panorama Tools GUI:
  Incomplete

Bug description:
  I am on Ubuntu. I have used Hugin intermittently, the last time I can
  find for sure was in August 2012. Hugin used to work but after some
  system update (I don't know which) it crashes after the splash screen
  comes up. I uninstalled Hugin and reinstalled. It still crashes.
  Otherwise the system patches are up to date.

  Ubuntu 12.04
  Intel® Core™2 Quad CPU Q9000 @ 2.00GHz × 4 
  64 bit

  /usr/share/hugin/data/plugins/shooting_pattern.py
     CAT:initial distribution
     NAM:6-1-1 Shooting Pattern
     fails @api-max
  /usr/share/hugin/data/plugins/woa.py
     CAT:Control Points
     NAM:Warped Overlap Analysis
     fails @api-max
  /usr/share/hugin/data/plugins/crop_cp.py
     CAT:Control Points
     NAM:Crop Control Points
     fails @api-max
  /usr/share/hugin/data/plugins/top_five.py
     CAT:Control Points
     NAM:keep 5 CPs per image pair
     fails @api-max
  The program 'hugin' received an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadRequest (invalid request code or no such operation)'.
    (Details: serial 1159 error_code 1 request_code 153 minor_code 19)
    (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.)

  I assume the X Window error is the source of the abort. I don't know
  enough about the program to know if the api-max messages are relevant
  to the crash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1305138/+subscriptions