View Issue Details

IDProjectCategoryView StatusLast Update
0000095FreeCADBugpublic2010-05-27 09:45
Reporterunauthenticated Assigned Toyorik  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version0.9 
Summary0000095: draft_line fails
DescriptionFreeCAD 0.9, Libs: 0.9R2646
(c) Juergen Riegel, Werner Mayer 2001-2009
  ##### #### ### ####
  # # # # # #
  # ## #### #### # # # # #
  #### # # # # # # # ##### # #
  # # #### #### # # # # #
  # # # # # # # # # ## ## ##
  # # #### #### ### # # #### ## ## ##

Running the Python command 'Draft_Line' failed:
Traceback (most recent call last):
  File "/usr/lib/freecad/Mod/Draft/Draft.py", line 859, in Activated
    self.snap = snapTracker()
  File "/usr/lib/freecad/Mod/Draft/Draft.py", line 414, in __init__
    sg.addChild(self.switch)
  File "/usr/lib/pymodules/python2.6/pivy/coin.py", line 41220, in addChild
    return _coin.SoGroup_addChild(*args)
Additional Informationusing build 2646 on ubuntu lucid
file new
select line tool
click somewhere in the drawing area
=> draft_line failed
TagsNo tags attached.
FreeCAD Information

Activities

wmayer

2010-05-04 05:50

administrator   ~0000213

This is probably already fixed.

yorik

2010-05-04 12:19

administrator   ~0000214

yes, looks like one more pivy hassle... This is the official 0.9 in ubuntu lucid repo, I'll check here if it works normally.

yorik

2010-05-04 21:06

administrator   ~0000215

Hmm the same happens here... There must be something wrong with the ubuntu package. Annoying... Probably something to do with the way they compiled freecad or pivy?

yorik

2010-05-22 22:47

administrator   ~0000218

I'll close this, I think we have no way to fix this, the exact same package works fine on debian, I suppose the error comes from the way ubuntu people recompiled freecad & pivy (they are using python2.6 instead of 2.5, and there are probably other differences vs debian). The best would be to file a bug report on ubuntu itself... But I'm afraid they have noone there who understands some pivysh...

Or to use our brand-new version 0.10, available on our homepage for 32 and 64bits, for your convenience ;)

Feel free to reopen this if anyone has more information or feedback from ubuntu...

yorik

2010-05-27 00:08

administrator   ~0000222

reopening just to inform the bug report on ubuntu:
http://bugs.launchpad.net/ubuntu/+source/pivy/+bug/586172

yorik

2010-05-27 00:10

administrator   ~0000223

Further information on the forum:
http://forum.freecadweb.org/posting.php?mode=reply&f=10&t=378#pr2477

wmayer

2010-05-27 09:45

administrator   ~0000224

The problem is that pivy internals are accessed via the wrong swig interface which is caused by using different versions when building freecad and pivy.

Now, I have found a really cool way to circumvent this. I'm able to load the appropriate coin.py or soqt.py and do some parsing there to get the used swig version. This allows us to determine and use the correct swig interface at runtime.
So, thanks to the fix we're able to use the broken pivy package from Ubuntu or the properly rebuilt one.

Everything is checked-in in rev. 3180

Btw, this approach works with any swig-generated python binding.

Issue History

Date Modified Username Field Change
2010-05-03 16:10 unauthenticated New Issue
2010-05-04 05:50 wmayer Note Added: 0000213
2010-05-04 05:50 wmayer Assigned To => yorik
2010-05-04 05:50 wmayer Status new => assigned
2010-05-04 12:19 yorik Note Added: 0000214
2010-05-04 21:06 yorik Note Added: 0000215
2010-05-22 22:47 yorik Note Added: 0000218
2010-05-22 22:47 yorik Status assigned => closed
2010-05-22 22:47 yorik Resolution open => not fixable
2010-05-27 00:08 yorik Note Added: 0000222
2010-05-27 00:08 yorik Status closed => feedback
2010-05-27 00:08 yorik Resolution not fixable => reopened
2010-05-27 00:10 yorik Note Added: 0000223
2010-05-27 09:45 wmayer Note Added: 0000224
2010-05-27 09:45 wmayer Status feedback => closed
2010-05-27 09:45 wmayer Resolution reopened => fixed