hugin-devs team mailing list archive

[Bruno Postle <720549@xxxxxxxxxxxxxxxxxx>]

I use Hugin over remote-X almost exclusively (currently running Hugin on
fedora f13 and displaying on f14 over wifi). The Fast Preview window and
overview are very responsive, the Mask tab is _extremely_ slow and the
Control Points tab is quite slow - other than that it is difficult to
see much diffference to running it locally.

I do have a problem with running an older version of Hugin on centos4,
the Fast Preview crashes immediately, but the rest of the application is
ok - I'm not worried about this since current Hugin doesn't build on
centos4/5 anyway.

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

Title:
  hugin crashes at startup with remote display

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  A friend had made some nice pictures while on vacation that I wanted
  to show him how to stitch. My main machine is upstairs, but we were
  downstairs on the beamer. So I stitched the pano in an older version
  of hugin (forgot to do the chanting required to go to the newer
  version), and then needed a new feature so couldn't evade having to do
  the chants. Anyway, newer hugins crash with a remote display.

  I suspected that it is the openGL, as Hugin remembers if I had the GL-
  preview open. However this turns out not to be the case. On my normal
  workstation I opened hugin, closed the GL window, quit hugin. Next I
  started hugin again, and indeed it didn't pop up the GL window. Next
  with display on the beamer and still it crashes.

  So... while older versions of hugin can run on one machine and display
  on another this no longer works on recent hugin versions. (I have a hg
  version from december).

  assurancetourix:~/knop> hugin DSC05514-DSC05527.pto
  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 697 error_code 1 request_code 138 minor_code 1)
    (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.)
  assurancetourix:~/knop>