hugin-devs team mailing list archive
-
hugin-devs team
-
Mailing list archive
-
Message #02738
[Bug 830574] Re: Hugin failed to start
The problem already exists after some updates.
Current versions are:
hugin: 2011.0.0-6.2
kdebase4: 4.6.5-4.2
kernel: 3.0.4-43.1
The error message has changed to "Speicherzugriffsfehler" only
/var/log/messages has the following entries:
Sep 9 19:01:21 linux kernel: [ 74.079029] hugin[3072]: segfault at 1b8 ip 00007fd5f9a479f9 sp 00007fffe670c990 error 4 in libwx_gtk2u_core-2.8.so.0.7.0[7fd5f9833000+3eb000]
Sep 9 19:01:26 linux kernel: [ 79.077061] hugin[3088]: segfault at 1b8 ip 00007fb29d9e29f9 sp 00007fff4bd6b9a0 error 4 in libwx_gtk2u_core-2.8.so.0.7.0[7fb29d7ce000+3eb000]
Sep 9 19:01:31 linux kernel: [ 83.869866] hugin[3102]: segfault at 1b8 ip 00007fcfb35799f9 sp 00007fff0abda6c0 error 4 in libwx_gtk2u_core-2.8.so.0.7.0[7fcfb3365000+3eb000]
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/830574
Title:
Hugin failed to start
Status in Hugin - Panorama Tools GUI:
New
Bug description:
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 1338 error_code 1 request_code 136 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.)
Hugin: 2011.0.0.14-16
OS:OpenSuse: 3.0.1-40
To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/830574/+subscriptions
References