Bug#986821: freecad: Garbled menu makes freecad unusable

Tobias Frost tobi at debian.org
Thu Apr 15 18:40:12 BST 2021


On Thu, Apr 15, 2021 at 04:44:12PM +0200, Michael Jarosch wrote:
> Am 13.04.21 um 15:18 schrieb Tobias Frost:
> > On Mon, Apr 12, 2021 at 11:48:26PM +0200, Michael Jarosch wrote:
> > > Am 12.04.21 um 15:52 schrieb Tobias Frost:
> > > So, I guess, it's my 'special' Ironlake GPU, again.
> > Ok, Let me downgrade the bug serverity then…
> 
> Hello!
> 
> Sorry, I have to revert my conclusion: Tried another Thinkpad-machine, a
> T530 with an Intel Core i7-3520M-CPU, which does not carry an Ironlake-GPU,
> anymore, but an HD-4000 ("Ivy-Bridge"). So, the problem seems to be bigger
> than just affecting a single GPU-generation(, if this is a GPU problem, at
> all).

mmm. strange.. but unfortunatly I cant reproduce it:

I've tested freecad also on different machines, one being a Tuxedo Infinity Book
with a Intel i7-8550U, and its fine.

My third machine, a rusty Thinkpad E130 powered by an i3-3227-U.. Also works…

(The first machine is a Ryzen with a nvidia gpu, so not really comparable,
where I use freecad almost daily and was mentioned in an early reply to this
bug report)

What you can try:
- check what over packages have been updated that could bring the breakage
  (maybe some kernel or intel gfx thingy?)
- temporarily rename ~/.FreeCAD to something else, to rule out that there is
  something in the config.
- 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)
 
Cheers,
-- 
tobi



More information about the debian-science-maintainers mailing list