Fedora Account System
Red Hat Associate
Red Hat Customer
abrt 1.0.7 detected a crash. architecture: x86_64 cmdline: python /usr/bin/gtkpycad component: PythonCAD executable: /usr/bin/gtkpycad kernel: 2.6.31.12-174.2.22.fc12.x86_64 package: PythonCAD-0.1.36-8.fc12 reason: tools.py:648:setRadius:ValueError: Invalid radius: 0 release: Fedora release 12 (Constantine) backtrace ----- tools.py:648:setRadius:ValueError: Invalid radius: 0 Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/PythonCAD/Interface/Gtk/gtkimage.py", line 498, in __daEvent event, _tool) File "/usr/lib/python2.6/site-packages/PythonCAD/Interface/Gtk/gtkentities.py", line 367, in circle_tp_motion_notify_cb tool.setSecondPoint(_ix, _iy) File "/usr/lib/python2.6/site-packages/PythonCAD/Generic/tools.py", line 760, in setSecondPoint self.setRadius(_radius) File "/usr/lib/python2.6/site-packages/PythonCAD/Generic/tools.py", line 648, in setRadius raise ValueError, "Invalid radius: %g" % _r ValueError: Invalid radius: 0 Local variables in innermost frame: self: <PythonCAD.Generic.tools.TwoPointCircleTool object at 0x1416d50> radius: 0.0 _r: 0.0 comment ----- See 'how to reproduce'. This does not happen everytime but I guess, so 7 out of 10. The ValueError should only raise, if I actually klick twice and 'select' an radius of 0, but not yet with just moving to a radius of 0. How to reproduce ----- 1. start 2. Draw->Basic->Cycle (2 Pts) 3. Klick on the window and not moving the mouse 4. See the backtrace in the console
Created attachment 396539 [details] File: backtrace
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. 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 prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
Package: PythonCAD-0.1.36-9.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. start 2. Draw->Basic->Cycle (2 Pts) 3. Klick on the window and not moving the mouse 4. See the backtrace in the console Comment ----- Try to reproduce #568734 on F-14
Rebasing to F-14, because this bug is still there. (Not heavily using this programm, just noted this bug a while ago, and tried to reproduce this again.)
Package: PythonCAD-0.1.36-9.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Not sure, but I think the author didn't consider that some values won't get entered. 2. Not much documentation on it, so trial and error might reproduce it. Twice in two days for me! 3. This seems to happen within the first 10 minutes or so. Comment ----- It's just a theory, but it looks like somewhere in the logic the program is not taking into account that there may not be a valid value entered. Maybe it covers for 0, and I could be off here, but usually you still have to cover for a NULL, or no value, which normally isn't the same as a 0. Then again, like I say I may really be off here and it might be something else altogether. I'm just basing this on personal experience though I used to program quite a lot and have had a chance to deal with issues such as this (and worse).
PythonCAD-0.1.37-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/PythonCAD-0.1.37-1.fc16
PythonCAD-0.1.37-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/PythonCAD-0.1.37-1.fc15
PythonCAD-0.1.37-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/PythonCAD-0.1.37-1.fc14
Package PythonCAD-0.1.37-1.fc14: * should fix your issue, * was pushed to the Fedora 14 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing PythonCAD-0.1.37-1.fc14' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/PythonCAD-0.1.37-1.fc14 then log in and leave karma (feedback).
PythonCAD-0.1.37-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
PythonCAD-0.1.37-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
PythonCAD-0.1.37-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.