| Summary: | [abrt] hugin-2010.2.0-1.fc14: wxWindow::DoSetSize: Process /usr/bin/hugin was killed by signal 11 (SIGSEGV) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jason Herring <jaherring> | ||||||
| Component: | hugin | Assignee: | Bruno Postle <bruno> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 14 | CC: | bruno, denis.arnaud_fedora, jspaleta, stephan | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:ce50d5d37587b21024a81e1aa8120ebabb3d87d7 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-08-16 12:41:52 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Jason Herring
2011-02-10 09:27:35 UTC
Created attachment 478026 [details]
File: backtrace
Hi, I need more information. You say it crashed when saving. Do you mean you created a new project, added photos, aligned them and viewed them in the preview, but when you clicked File -> Save it crashed? ..or did it crash when you tried to stitch? I created a new project, saved it, added four very large PNG images, created anchor points, but did not yet stitch it. I went to save/exit and it crashed on the way out of the app. Sorry, hope you don't mind more questions. Did it crash during the save, or when you exited after that? i.e. did you get the .pto project. Package: hugin-2010.2.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Load my 6 images 2. Request an automatic generation of control points (20 per image and 103 generated instead of 100) 3. Select the two images (1 and 3) for which I have the 3 wrong control points in the control points sheet 4. Crash of Hugin Comment ----- I can reproduce the crash each time I am trying to suppress the 3 wrong points by selecting my two images. What is surpising is that if I select two images, 1 and 2, with their 20 control points, I have no problem. I have a crash if and only if I am trying to select the two images with the 3 wrong points. Hi Stephan, this doesn't seem to be the same problem, but can you please upload the .pto project that causes this problem? It would be very useful if I can reproduce the crash here. Hi Bruno, Perhaps I made a mistake when filling abrt report, but the association was made with this bug. I don't see how to upload a file, so I am giving an URL to access my .pto: http://peccini.fr/tempo/defect.pto Do not hesitate to request more information. Created attachment 481280 [details]
Modified pto project that resolves stephan's problem
Hi Stephan, the problem is that there is a single control point that refers to coordinates outside the photos. The good news is that Hugin 2010.4.0, which will be in f15, notices this and offers to delete it on opening the file. I'll upload the fixed project file here. A tip for the future: if you are scanning photos there is no need to crop them before loading them into Hugin. Hugin has a nice crop tool where you can indicate the areas you want removed. This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |