Hugin crashes after system update (x server?)

161 views
Skip to first unread message

Peter Suetterlin

unread,
May 31, 2013, 6:03:20 AM5/31/13
to hugi...@googlegroups.com

Hello list,

I am running a self-compiled hugin version from mercurial (current version:
20e34581ca6a), and use it a lot for panos and aligning stacks.

Two days ago I did an update of my system (openSUSE 12.1 with KDE SC 4.9), and
since that update hugin is crashing when I try to start it:

The program 'hugin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 1971 error_code 3 request_code 137 minor_code 4)
(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.)

The update wasn't large, the only thing that seemed related was a minor update
of the xorg-x11-server (7.6_1.10.4-36.5.1-> 7.6_1.10.4-36.9.2) claiming to fix
only some console switching issue.

My first try was to recompile hugin, but that didn't help. So I decided o
revert to the old version of the X server. But hugin still crashes! I tried
to follow the suggested 'sync' option and run it in gdb, but a backtrace only
gives a 'No stack'. That's where my skills end.

I had a closer look at the list of updates, but cannot really see what might
be the reason for the change. Does any of the Developers here have a hint
what I should be looking for?

Here's a list of packages that did get updated:

FreeCAD libphonon4 phonon-devel mkinitrd java-1_6_0-openjdk libtiff3 libcurl4
xorg-x11-server xorg-x11-Xvnc libcurl4-32bit libgnutls28 libtiff3-32bit
libtalloc2 libwbclient0-32bit libtdb1-32bit libtdb1 libtalloc2-32bit
libwbclient0 libtiff-devel libcurl-devel flash-player curl libgnutls-devel
libtevent0 libsmbclient0 flash-player-kde4 libldb1 libgphoto2-6 rawtherapee
darktable libgphoto2-6-lang photivo photivo-gimp libmpg123-0 mpg123 MPlayer
gmplayer wxcam handbrake-cli xine-ui libopencv2_4 opencv opencv-devel
plus a bunch of gambas3 packages

Thanks,

Pit

--
Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit
Institute for Solar Physics
Tel.: +34 922 405 590 (Spain) P.Suet...@royac.iac.es
+46 8 5537 8507 (Sweden) Peter.Su...@astro.su.se

Gnome Nomad

unread,
May 31, 2013, 6:26:12 AM5/31/13
to hugi...@googlegroups.com
Maybe try renaming your .hugin file (in your home directory)? When Hugin
crashed, it might have mangled its config file.

--
David W. Jones
gnome...@gmail.com
wandering the landscape of god
http://dancingtreefrog.com
http://www.clanjones.org/david/
http://dancing-treefrog.deviantart.com/
http://www.cafepress.com/otherend/

Peter Suetterlin

unread,
May 31, 2013, 7:09:19 AM5/31/13
to hugi...@googlegroups.com


Hi David,

Gnome Nomad wrote:
>
> Maybe try renaming your .hugin file (in your home directory)? When
> Hugin crashed, it might have mangled its config file.
>

thanks for the suggestion! I had tried that, too, but it didn't help.

But I finally found the reason: The update had overwritten the libglx.so from
the NVIDIA install, so I had no direct rendering support which crashed the GL
preview window. Why can't X error messages be somewhat more telling....

So after re-installing the NVidia driver things work again.

Gnome Nomad

unread,
Jun 1, 2013, 3:43:24 AM6/1/13
to hugi...@googlegroups.com
On 05/31/2013 01:09 AM, Peter Suetterlin wrote:
> Hi David,
>
> Gnome Nomad wrote:
>>
>> Maybe try renaming your .hugin file (in your home directory)? When
>> Hugin crashed, it might have mangled its config file.
>>
>
> thanks for the suggestion! I had tried that, too, but it didn't help.
>
> But I finally found the reason: The update had overwritten the libglx.so from
> the NVIDIA install, so I had no direct rendering support which crashed the GL
> preview window. Why can't X error messages be somewhat more telling....
>
> So after re-installing the NVidia driver things work again.
>
> Pit

Ah ha!
Reply all
Reply to author
Forward
0 new messages