Am 15.04.21 um 19:40 schrieb Tobias Frost:
My third machine, a rusty Thinkpad E130 powered by an i3-3227-U.. Also
works…
…and the E130 uses the same GPU core as my T530. Now, it's getting
complicated!
What you can try:
- check what over packages have been updated that could bring the breakage
(maybe some kernel or intel gfx thingy?)
This would be a bit of work… I apt update/upgrade about every day, but I
don't use freecad as often as I upgrade the system…
Kernel is 5.10.0-5-amd64, now, but I guess this was upgraded, lately. No
change, whatsoever.
- temporarily rename ~/.FreeCAD to something else, to rule out that there is
something in the config.
Done that, no change.
- Can you ensure that all freecad packages are updated... (I think a versioned
depdency is missing, possibly #980474) I tried manually to get to an
invalid combination,
but the only "solution" was package freecad at 0.19 and freecad-common at
0.18, which makes freecad stop working, but with an different error (no
python
module named freecad, completly empty main window)
On my system, there is freecad, freecad-common, freecad-python3,
libfreecad-python3-0.19 and every single package is labeled as
0.19.1+dfsg1-2.
Another try: I'm using Gnome on all my 3 systems(, which should all have
the same Gnome version numbers, since I use Debian Testing on all of
those machines). Do you use another Desktop Environment?
Greets!
