Hide Forgot
Description of problem: Click on 'Share on Youmagine' Version-Release number of selected component: cura-13.10-1.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/python /usr/bin/cura crash_function: dequeue_pending_request executable: /usr/bin/python2.7 kernel: 3.11.7-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: Dec 14 14:50:32 Elias abrt-hook-ccpp[7039]: Saved core dump of pid 6791 (/usr/bin/python2.7) to /var/tmp/abrt/ccpp-2013-12-14-14:50:30-6791 (129847296 bytes) Truncated backtrace: Thread no. 1 (10 frames) #4 dequeue_pending_request at xcb_io.c:177 #6 XGetSelectionOwner at GetSOwner.c:41 #7 gdk_selection_owner_get_for_display at gdkselection-x11.c:216 #8 gtk_selection_convert at gtkselection.c:1066 #9 wxClipboard::GetData at src/gtk/clipbrd.cpp:597 #10 _wrap_Clipboard_GetData at src/gtk/_misc_wrap.cpp:35696 #11 ext_do_call at /usr/src/debug/Python-2.7.5/Python/ceval.c:4408 #12 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.5/Python/ceval.c:2779 #13 PyEval_EvalCodeEx at /usr/src/debug/Python-2.7.5/Python/ceval.c:3330 #14 fast_function at /usr/src/debug/Python-2.7.5/Python/ceval.c:4194
Created attachment 836655 [details] File: backtrace
Created attachment 836656 [details] File: cgroup
Created attachment 836657 [details] File: core_backtrace
Created attachment 836658 [details] File: dso_list
Created attachment 836659 [details] File: environ
Created attachment 836660 [details] File: limits
Created attachment 836661 [details] File: maps
Created attachment 836662 [details] File: open_fds
Created attachment 836663 [details] File: proc_pid_status
Immediately when you click the button? Or after you enter the token?
A second after clicking the button. I did not enter the token. I tried to reproduce by first restarting Cura, but this time it worked.
I got a similar crash when adding the token, but after, it worked. I'll try with clean config directory. Could you please backup and remove your cura config directory and try to reproduce? It's ~/.cura
I tried it, I used the default settings in the first start wizard, and then I clicked on 'Share on Youmagine', but no crash. Even when I add the token, no crash. However I noticed that I can not close the dialog that pops up when clicking on 'Share on Youmagine', but maybe that's another problem.
I've noticed that too, will try to resolve that. Are you Ok if I close this?
Sure.
OK, in the mean time, could you please test and add karma to this update? https://admin.fedoraproject.org/updates/cura-13.11.2-1.fc19,CuraEngine-13.11.2-1.fc19,ultimaker2-marlin-firmware-13.11-2.1.fc19 Thanks.
Results with the update are exactly the same as described in comment 13, so I also removed "~/.cura". No crashes. (However that does not necessarily mean this bug has been fixed) Do I need to add karma or not?
If the update works in general and you do not observe any serious problems, give it a plus, please. Thanks
Done.
Thanks. BTW I might be able to reproduce this, so reopenning: Try: 0. Remove ~/.cura 1. Load an STL file 2. While the STL is being sliced, click Share on Youmagine (before slicing is finished) 3. SIGABRT
https://github.com/daid/Cura/issues/662 https://github.com/daid/Cura/issues/663
(In reply to Miro Hrončok from comment #20) > Thanks. > > BTW I might be able to reproduce this, so reopenning: > > Try: > > 0. Remove ~/.cura > 1. Load an STL file > 2. While the STL is being sliced, click Share on Youmagine (before slicing > is finished) > 3. SIGABRT Hmm, sometimes that crashes, but not always. But I found something that crashes always, it might be related to this bug: 0. Remove ~/.cura 1. Load an STL file 2. While the STL is being sliced, click Share on Youmagine (before slicing is finished) 3. Click on 'Save toolpath' 4. In the file dialog, select 'Cancel' 5. SIGABRT I found that Steps 0 and 2 are redundant and not needed to reproduce the bug.
1. Load an STL file 2. After slicing click on 'Save toolpath' 4. In the file dialog, select 'Cancel' 5. SIGABRT This way? I cannot reproduce that in 13.11.2.
No, excuse me, I only installed CuraEngine-13.11.2-1.fc19 and ultimaker2-marlin-firmware-13.11-2.1.fc19. I seem to have missed the cura-13.11.2-1.fc19 package. After having installed that, I also can't reproduce comment 23. But the following is reproducible instead: 1. Load an STL file 2. After slicing click on 'Share on Youmagine' 3. Click on 'Save toolpath' 4. In the file dialog, select 'Cancel' 5. SIGABRT
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.