FreeCAD 0.20.2 on Debian Bullseye/Intel : graphic issue
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
Re: FreeCAD 0.20.2 on Debian Bullseye/Intel : graphic issue
Sorry, I don't know where to do that. Can't find it in Preferences.
My question is why it works in realthunder's Appimage and not in the other FreeCAD-Builds? There must be some different code when change to V0.20.2.
Now I have compiled FreeCAD from the source - but the same issue
Regards
Andreas
My question is why it works in realthunder's Appimage and not in the other FreeCAD-Builds? There must be some different code when change to V0.20.2.
Now I have compiled FreeCAD from the source - but the same issue
Regards
Andreas
Re: FreeCAD 0.20.2 on Debian Bullseye/Intel : graphic issue
I've set Xft.dpi to 96 in .Xresources and merged that in with xrdb. After that:
holm@trollo:~ $ xrdb -query | grep dpi
Xft.dpi: 96
holm@trollo:~ $
..startet freecad..nothing changed.
The xdpyinfo screen setting gets automatically calculated from the monitor data read out over the DVI connection:
screen #0:
dimensions: 3840x1200 pixels (1049x321 millimeters)
resolution: 93x95 dots per inch
That is a "virtual" screen consisting of two concatenated displays, automatically generated from the Nvidia Xserver (Blob).
There is no proper way to change that!
Besides of that, why are the wrong set of icons get displayed in FreeCad?
Icons in the bars at top are ok so far on the left side, but they get cut on the right side more and more until they are completely unreadable.
it seems that this error is accumulating and gets worse and worse the more right the icon is placed.
Textfonts are cutted in vertical direction, that seems to not accumulating in horizontal direction.
Why is FreeCad the one and only program that seems to have such a problem with
the dpi values calculated from the X-server? FreeCad seems to do something in an entirely different way as other programs.
Regards,
Holm
holm@trollo:~ $ xrdb -query | grep dpi
Xft.dpi: 96
holm@trollo:~ $
..startet freecad..nothing changed.
The xdpyinfo screen setting gets automatically calculated from the monitor data read out over the DVI connection:
screen #0:
dimensions: 3840x1200 pixels (1049x321 millimeters)
resolution: 93x95 dots per inch
That is a "virtual" screen consisting of two concatenated displays, automatically generated from the Nvidia Xserver (Blob).
There is no proper way to change that!
Besides of that, why are the wrong set of icons get displayed in FreeCad?
Icons in the bars at top are ok so far on the left side, but they get cut on the right side more and more until they are completely unreadable.
it seems that this error is accumulating and gets worse and worse the more right the icon is placed.
Textfonts are cutted in vertical direction, that seems to not accumulating in horizontal direction.
Why is FreeCad the one and only program that seems to have such a problem with
the dpi values calculated from the X-server? FreeCad seems to do something in an entirely different way as other programs.
Regards,
Holm
Re: FreeCAD 0.20.2 on Debian Bullseye/Intel : graphic issue
FreeCADm is using OpenGL, so changes are that there are problem with Mesa LIbraries.
It is not the only program that use OpenGL, Qt or Coin3D libs, so probably other programs have similar problems.
https://wiki.freecad.org/PySide
https://wiki.freecad.org/Scenegraph/en
Some hints could be here.
viewtopic.php?p=253204#p253204
But most important, what version of FreeCAD are you using, see:
http://forum.freecadweb.org/viewtopic.php?f=3&t=2264
To have an idea how to supply "correct FreeCAD version info". your mileage may vary if you use as example a distribution complied version of FreeCAD.
Hope it help.
Regards
Carlo D.
GitHub page: https://github.com/onekk/freecad-doc.
- In deep articles on FreeCAD.
- Learning how to model with scripting.
- Various other stuffs.
Blog: https://okkmkblog.wordpress.com/
- In deep articles on FreeCAD.
- Learning how to model with scripting.
- Various other stuffs.
Blog: https://okkmkblog.wordpress.com/
- adrianinsaval
- Veteran
- Posts: 5541
- Joined: Thu Apr 05, 2018 5:15 pm
Re: FreeCAD 0.20.2 on Debian Bullseye/Intel : graphic issue
Change the dpi settings in your desktop environment, I think you are running mate right? See https://wiki.archlinux.org/title/MATE#C ... PI_setting
I don't know why FreeCAD behaves this way, but I've seen many reports and almost always there is some font dpi setting somewhere that when adjusted fixes the issue. This seems to be some sort of xorg+Qt bug that is not present on all versions, as you may have heard scaling in xorg is a mess. Most of the reports of this that I've seen are from xfce users but I've also seen some mate user reports, perhaps these desktop environments are missing some component or env variable that Qt requires to do proper scaling.
I don't know why FreeCAD behaves this way, but I've seen many reports and almost always there is some font dpi setting somewhere that when adjusted fixes the issue. This seems to be some sort of xorg+Qt bug that is not present on all versions, as you may have heard scaling in xorg is a mess. Most of the reports of this that I've seen are from xfce users but I've also seen some mate user reports, perhaps these desktop environments are missing some component or env variable that Qt requires to do proper scaling.
Re: FreeCAD 0.20.2 on Debian Bullseye/Intel : graphic issue
Thank you, that was it... A bit deep in the MATE-System. Now it works.adrianinsaval wrote: ↑Wed Feb 22, 2023 10:52 am Change the dpi settings in your desktop environment, I think you are running mate right? See https://wiki.archlinux.org/title/MATE#C ... PI_setting
Regards
Andreas
PS: But why does it not affect realthunder's Appimage? This works if dpi is set or not.
- adrianinsaval
- Veteran
- Posts: 5541
- Joined: Thu Apr 05, 2018 5:15 pm
Re: FreeCAD 0.20.2 on Debian Bullseye/Intel : graphic issue
appimages come with their own libraries and a script that sets up an environment from them, they can't be directly compared to a system installation, maybe it has a version of qt that doesn't have this bug or they include something that is missing in your system, can be many things.
Re: FreeCAD 0.20.2 on Debian Bullseye/Intel : graphic issue
..it isn't the only program that uses OpenGL or mesa on my system. but it is the only one showing that bug.
Setting the Fonts DPI to fixed 96 in the background menu changed nothing here, maybe that's different after an Mate-restart, but I don't want to end the session for now, will report here.
..but setting QT_AUTO_SCREEN_SCALE_FACTOR=0 before starting freecad drives out the problem here, but I don't think that this is a final soultion.
I people complaining that often about this bug..on different os's and different X-Servers..maybe it is time to report that problem upstream to the Qt people?
Do you want to know this?:
Code: Select all
OS: FreeBSD 13.1-STABLE (MATE)
Word size of FreeCAD: 64-bit
Version: 0.20.2.14555 (Git shallow)
Build type: Release
Branch: main
Hash: 5e661bb545c8a17b55487393153e0329526364b9
Python 3.9.16, Qt 5.15.8, Coin 4.0.0, Vtk 9.2.2, OCC 7.7.0
Locale: C/Default (C)
This software uses open source components whose copyright and other proprietary rights belong to their respective owners:
Boost 1_81
https://www.boost.org
Coin3D 4.0.0
https://coin3d.github.io
Eigen 3.4.0
https://eigen.tuxfamily.org
FreeType 2.12.1
https://freetype.org
KDL
https://www.orocos.org/kdl
libarea
https://github.com/danielfalck/libarea
Open CASCADE Technology 7.7.0
https://www.opencascade.com/open-cascade-technology/
Point Cloud Library
https://www.pointclouds.org
PyCXX 6.2.8
http://cxx.sourceforge.net
Python 3.9.16
https://www.python.org
Qt for Python (PySide) 5.15.2
https://wiki.qt.io/Qt_for_Python
Qt 5.15.8
https://www.qt.io
Salome SMESH
https://salome-platform.org
Qt for Python (Shiboken) 5.15.2
https://wiki.qt.io/Qt_for_Python
vtk 9.2.2
https://www.vtk.org
Xerces-C 3.2.4
https://xerces.apache.org/xerces-c
Zipios++
http://zipios.sourceforge.net
zlib 1.2.12
https://zlib.net
Regards,
Holm
Re: FreeCAD 0.20.2 on Debian Bullseye/Intel : graphic issue
Yes as this tell what version you are using or at least give a good idea.holm wrote: ↑Wed Feb 22, 2023 6:11 pm ..it isn't the only program that uses OpenGL or mesa on my system. but it is the only one showing that bug.
...
Do you want to know this?:
...Code: Select all
OS: FreeBSD 13.1-STABLE (MATE) Word size of FreeCAD: 64-bit ...
Regards,
Holm
For technical details, probably adrianinsaval has told you most relevant info.
But you are not using Linux but FreeBSD that is another different thing, with a different stack of and a different kernel, and probably you are using the Linux compatibility layer of how it is called, so your case is different from a "standard use case".
Regards
Carlo D.
GitHub page: https://github.com/onekk/freecad-doc.
- In deep articles on FreeCAD.
- Learning how to model with scripting.
- Various other stuffs.
Blog: https://okkmkblog.wordpress.com/
- In deep articles on FreeCAD.
- Learning how to model with scripting.
- Various other stuffs.
Blog: https://okkmkblog.wordpress.com/
- adrianinsaval
- Veteran
- Posts: 5541
- Joined: Thu Apr 05, 2018 5:15 pm
Re: FreeCAD 0.20.2 on Debian Bullseye/Intel : graphic issue
I don't think they are going to fix anything on qt5 anymore, we would need to see if this is happening with qt6 too. Besides that, I do not have clear reproductions steps and don't even know what component is causing trouble here, it seems this might be somehow related to hardware too.
Re: FreeCAD 0.20.2 on Debian Bullseye/Intel : graphic issue
No, no Linux compatibility layer aka Linuxulator is involved here, it's compiled one the machine it should run to trough FreeBSD's ports system.onekk wrote: ↑Wed Feb 22, 2023 6:30 pm [..]
Yes as this tell what version you are using or at least give a good idea.
For technical details, probably adrianinsaval has told you most relevant info.
But you are not using Linux but FreeBSD that is another different thing, with a different stack of and a different kernel, and probably you are using the Linux compatibility layer of how it is called, so your case is different from a "standard use case".
Regards
Carlo D.
(cd /usr/ports/cad/freecad; make all install clean)
It where possible to run a Linux Version aka appimage on my machine, I could try this but I can predict the results already, it would be the same.
I agree with you that there may be something wrong with X11, Qt and the mesa libs, but as long as FreeCad is the only Application that triggers the bug it is clearly a FreeCAD issue, since others are able to tolerate that library bugs w/o any bad behavior. I'm using KiCad on a regular basis w/o problems
and it is "supported" in the same way as FreeCAD on FreeBSD.
For sure it's possible fitghing unlovable customers with the hint that they run on a unsupported system, but I don't think that this makes things any better as long as the same bug appears on debian Linux systems.
Sorry, but I don't dress my pants with a crane.
Regards,
Holm