Description of problem: The Mayavi2 (3D scientific data visualization and plotting tool) crashes. To reproduce it: 1) Open Mayavi2 2) Add a Data Source 3) Create a Point Load Source 4) Add module or filter 5) Click on Axes After a few seconds, the program crashes. It happens every time. Version-Release number of selected component: Mayavi-4.3.0-7.fc19 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/bin/python /usr/bin/mayavi2 crash_function: wxEvtHandler::SearchDynamicEventTable executable: /usr/bin/python2.7 kernel: 3.11.3-201.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 wxEvtHandler::SearchDynamicEventTable at src/common/event.cpp:1412 #1 wxEvtHandler::ProcessEvent at src/common/event.cpp:1297 #3 wxScrollHelperEvtHandler::ProcessEvent at src/generic/scrlwing.cpp:208 #4 wxEvtHandler::ProcessEvent at src/common/event.cpp:1308 #6 gtk_window_button_press_callback at src/gtk/window.cpp:1634 #7 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #12 gtk_widget_event_internal at gtkwidget.c:5017 #13 gtk_widget_event at gtkwidget.c:4814 #14 gtk_propagate_event at gtkmain.c:2490 #15 gtk_main_do_event at gtkmain.c:1685
Created attachment 811139 [details] File: backtrace
Created attachment 811140 [details] File: cgroup
Created attachment 811141 [details] File: core_backtrace
Created attachment 811142 [details] File: dso_list
Created attachment 811143 [details] File: environ
Created attachment 811144 [details] File: exploitable
Created attachment 811145 [details] File: limits
Created attachment 811146 [details] File: maps
Created attachment 811147 [details] File: open_fds
Created attachment 811148 [details] File: proc_pid_status
Created attachment 811149 [details] File: var_log_messages
Is there a reason you filed this bug as private?
No. I made a private report because the Bug Reporting Tool advised me to do so. Feel free to make it public. Regards, Alejandro
Hmm, I don't seem to be able to uncheck the private bug box. Can you?
I am not able to uncheck the private option either. Maybe it is because it has been assigned?
Making this bug public as per request, as there's no reason to keep this bug private.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.