Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1832312 - FreeCAD no longer works - PySide error
Summary: FreeCAD no longer works - PySide error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-pyside2
Version: 32
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Richard Shaw
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1750107
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-06 14:05 UTC by Przemo Firszt
Modified: 2020-05-23 02:44 UTC (History)
8 users (show)

Fixed In Version: python-pyside2-5.13.2-4.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-23 02:44:44 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Przemo Firszt 2020-05-06 14:05:46 UTC 
Description of problem:
FreeCAD no longer works.

Version-Release number of selected component (if applicable):
0.18

How reproducible:
always

Steps to Reproduce:
1. install FreeCAD
2. run "FreeCAD -t 0"

Actual results:
$ FreeCAD -t 0
FreeCAD 0.18, Libs: 0.18RUnknown
© Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2019
  #####                 ####  ###   ####  
  #                    #      # #   #   # 
  #     ##  #### ####  #     #   #  #   # 
  ####  # # #  # #  #  #     #####  #   # 
  #     #   #### ####  #    #     # #   # 
  #     #   #    #     #    #     # #   #  ##  ##  ##
  #     #   #### ####   ### #     # ####   ##  ##  ##

Sheet Metal workbench loaded
Traceback (most recent call last):
  File "<string>", line 38, in <module>
  File "/usr/lib64/freecad/Mod/Test/TestApp.py", line 27, in <module>
    import unittest
  File "/usr/lib64/python3.8/unittest/__init__.py", line 60, in <module>
    from .async_case import IsolatedAsyncioTestCase
  File "/usr/lib64/python3.8/unittest/async_case.py", line 1, in <module>
    import asyncio
  File "/usr/lib64/python3.8/asyncio/__init__.py", line 8, in <module>
    from .base_events import *
  File "/usr/lib64/python3.8/asyncio/base_events.py", line 18, in <module>
    import concurrent.futures
  File "/usr/lib64/python3.8/concurrent/futures/__init__.py", line 8, in <module>
    from concurrent.futures._base import (FIRST_COMPLETED,
  File "/usr/lib64/python3.8/concurrent/futures/_base.py", line 7, in <module>
    import logging
  File "/usr/lib64/python3.8/logging/__init__.py", line 28, in <module>
    from string import Template
  File "/usr/lib64/python3.8/string.py", line 80, in <module>
    class Template(metaclass=_TemplateMetaclass):
<class 'TypeError'>: 'Shiboken.ObjectType' object is not iterable


Expected results:
Full test suite run

Additional info:
The bug renders FreeCAD unusable - switching to some workbenches no longer works showing error window. The bug is related to https://bugzilla.redhat.com/show_bug.cgi?id=1750107
Comment 1 Jamel Abiadh 2020-05-09 19:49:44 UTC 
Same issue here when selecting the "part design" workbench

'Shiboken.ObjectType' object is not iterable
Traceback (most recent call last):
  File "<string>", line 42, in Initialize
  File "/usr/lib64/freecad/Mod/PartDesign/WizardShaft/WizardShaft.py", line 26, in <module>
    from .Shaft import Shaft
  File "/usr/lib64/freecad/Mod/PartDesign/WizardShaft/Shaft.py", line 25, in <module>
    from .SegmentFunction import SegmentFunction,  IntervalFunction,  StressFunction,  TranslationFunction
  File "/usr/lib64/freecad/Mod/PartDesign/WizardShaft/SegmentFunction.py", line 24, in <module>
    import numpy as np
  File "/usr/lib64/python3.8/site-packages/numpy/__init__.py", line 142, in <module>
    from . import core
  File "/usr/lib64/python3.8/site-packages/numpy/core/__init__.py", line 24, in <module>
    from . import multiarray
  File "/usr/lib64/python3.8/site-packages/numpy/core/multiarray.py", line 14, in <module>
    from . import overrides
  File "/usr/lib64/python3.8/site-packages/numpy/core/overrides.py", line 9, in <module>
    from numpy.compat._inspect import getargspec
  File "/usr/lib64/python3.8/site-packages/numpy/compat/__init__.py", line 14, in <module>
    from . import py3k
  File "/usr/lib64/python3.8/site-packages/numpy/compat/py3k.py", line 22, in <module>
    from pathlib import Path, PurePath
  File "/usr/lib64/python3.8/pathlib.py", line 592, in <module>
    class _PathParents(Sequence):
  File "/usr/bin/../lib64/python3.8/abc.py", line 85, in __new__
    cls = super().__new__(mcls, name, bases, namespace, **kwargs)
Comment 2 Richard Shaw 2020-05-19 14:03:29 UTC 
Please try the following update and see if it fixes the issue. If it does, please give the update karma.

https://bodhi.fedoraproject.org/updates/FEDORA-2020-10d152f626
Comment 3 Fedora Update System 2020-05-19 14:10:07 UTC 
FEDORA-2020-10d152f626 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-10d152f626
Comment 4 Fedora Update System 2020-05-20 05:48:27 UTC 
FEDORA-2020-10d152f626 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-10d152f626`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-10d152f626

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Fedora Update System 2020-05-23 02:44:44 UTC 
FEDORA-2020-10d152f626 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.