i think its just a typo, he means "Start" workbench
AppImages of v0.18 release builds
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
Re: AppImages of v0.18 release builds
Hi @looo thank you again for your work with appimage and conda.
I just started to use appimage late because I have just moved my personal pc from win10 to mint tessa.
FC 0.18.1 installed from PPA is just fast and clean also with all my WBs.
Using the stable Appimage, all the previous errors are gone [ FC 0.18 16110 (Git) BuildRevisionDate = 2019/04/04 RevisionHash = f7dccfaa909e5b9da26bf50c4a22ccca9bb10c40 ]
... but also with this appimage I'm still getting some performance issues...
I'm investigating to reduce the affected area that is triggered by my importing script...
I'll report it here later...
Re: AppImages of v0.18 release builds
Hi all,
when I want to open a workshop, I have this error message.
as requested in the other thread, I transmit this information:
OS: Ubuntu 16.04.6 LTS (LXDE/Lubuntu)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.16475 (Git) AppImage
Build type: Release
Branch: master
Hash: 5d211d87049f8dff90e12eace8c4d3f2684a90a1
Python version: 3.7.1
Qt version: 5.6.2
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: French/France (fr_FR)
with "Version: 0.19.16207 (Git) AppImage" , I did not have this problem
PS: I did not intervene in the folder / usr / lib / freecad / Mod, nor even in ./Freecad
when I want to open a workshop, I have this error message.
as requested in the other thread, I transmit this information:
OS: Ubuntu 16.04.6 LTS (LXDE/Lubuntu)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.16475 (Git) AppImage
Build type: Release
Branch: master
Hash: 5d211d87049f8dff90e12eace8c4d3f2684a90a1
Python version: 3.7.1
Qt version: 5.6.2
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: French/France (fr_FR)
with "Version: 0.19.16207 (Git) AppImage" , I did not have this problem
PS: I did not intervene in the folder / usr / lib / freecad / Mod, nor even in ./Freecad
https://github.com/Xav83130/Mini-CNC
Tuto FR-basic -PATH - https://github.com/Xav83130/Mini-CNC/wi ... Basic-Path (plus a jour)
Tuto FR-basic -PATH - https://github.com/Xav83130/Mini-CNC/wi ... Basic-Path (plus a jour)
Re: AppImages of v0.18 release builds
yes it would be interesting to see if these performance issues are related to conda or appimage.easyw-fc wrote: ↑Wed Apr 17, 2019 8:49 am Using the stable Appimage, all the previous errors are gone [ FC 0.18 16110 (Git) BuildRevisionDate = 2019/04/04 RevisionHash = f7dccfaa909e5b9da26bf50c4a22ccca9bb10c40 ]
... but also with this appimage I'm still getting some performance issues...
I'm investigating to reduce the affected area that is triggered by my importing script...
I'll report it here later...
I pushed a commit to ship the the libstdc++ within the appimage (0.19). I am not sure if libstdc++ is shiped with conda for the new toolchain or if this package only contains a link to system libstdc++... We will see.
ok this makes sense.
@triplus I see 0.18.1-stable not uploaded anymore. Also I am not sure if 0.19 is uploaded correctly. Do you know what is going on?
Re: AppImages of v0.18 release builds
For 0.18.1 I noticed this as well, maybe something with the "pruning"?
What issue are you seeing with 0.19_pre?
"fight the good fight"
Re: AppImages of v0.18 release builds
Sometimes a glitch can occur and for build or deploying phase to fail. It doesn't happen often and when it happens it's usually high load or network related. I took a quick look in the logs and it looks like an issue occurred regarding setting up Conda environment and the creation of the stable AppImage/DMG failed as a result. Such things usually get sorted out in less then 24 hours (next build). I manually triggered Travis build and binaries have been created and deployed successfully. As some might notice now we can deploy successfully to 0.18.1. A small change in the upload script is needed. As name and tag_name can differ. I temporary patched the travis.yml directly. As i don't know if ports cache repo is still maintained or not ATM. Next week i will try to make deployment to latest release working automatically. Update information for stable AppImage was restored (using latest).
P.S. I investigated the Qt Assistant issue a bit today and i feel i now have a general overview. I need to test a few things and i am not sure if i will have time to do that tomorrow or during the next week.
Re: AppImages of v0.18 release builds
@Xav-83
I can confirm libstdc++ issue was resolved testing the latest FreeCAD 0.19 AppImage. Theme still does look "old", only on FreeCAD 0.19.
@easyw-fc
Performance issue could be (low) Qt 5 (version) related. For example i still compile against slightly older version of Qt 5, compared to the one in AppImage, on Ubuntu 16.04. And (viewport) performance is much slower over there. Therefore newer Qt 5 versions might improve performance, when available on Conda.
@leong
If you temporary rename hidden .FreeCAD folder located in your home folder, and start the AppImage, does the issue persist?
P.S. Once some people can confirm FreeCAD 0.18.1, provided on releases page, works on the macOS, after Download page should get updated.
I can confirm libstdc++ issue was resolved testing the latest FreeCAD 0.19 AppImage. Theme still does look "old", only on FreeCAD 0.19.
@easyw-fc
Performance issue could be (low) Qt 5 (version) related. For example i still compile against slightly older version of Qt 5, compared to the one in AppImage, on Ubuntu 16.04. And (viewport) performance is much slower over there. Therefore newer Qt 5 versions might improve performance, when available on Conda.
@leong
If you temporary rename hidden .FreeCAD folder located in your home folder, and start the AppImage, does the issue persist?
P.S. Once some people can confirm FreeCAD 0.18.1, provided on releases page, works on the macOS, after Download page should get updated.
Re: AppImages of v0.18 release builds
@triplus seems to have it solved. I see 18.1 appimage and dmg uploaded to github release page.
Then this was a simple fix. Does this mean the appimage should also work on something like alpine-linux?
regarding the theming issue: Maybe including some other removed packages will also get the theme back. Maybe we should look for a solution to avaoid the gtk messages.
regarding dmgs:
Currently the conda-packages are not very stable (crash). If the problem is really caused by qt5.6.2 [1] maybe updating to 5.6.3 is a solution. If these versions are binary-compatible we can try to force the appimage using this version.
[1] https://bugreports.qt.io/browse/QTBUG-57404
Re: AppImages of v0.18 release builds
I see the pixbuf problem wasn't solved. I made some tests and it seems like setting
vanishes the warning. But gui doesn't look good.
Conda sets up some configuration files after the installation [1]. This adds the problems for the portable appimage.
Searching for similar problems I found [2] this config variable:
[1] https://github.com/conda-forge/gdk-pixb ... ink.sh#L21
[2] https://github.com/AppImage/AppImageKit ... -GTK3-apps
Code: Select all
export QT_STYLE_OVERRIDE=gtk2
Conda sets up some configuration files after the installation [1]. This adds the problems for the portable appimage.
Searching for similar problems I found [2] this config variable:
Code: Select all
export GDK_PIXBUF_MODULE_FILE=${PREFIX}/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache
[1] https://github.com/conda-forge/gdk-pixb ... ink.sh#L21
[2] https://github.com/AppImage/AppImageKit ... -GTK3-apps
Re: AppImages of v0.18 release builds
not possible because qt5.6.3-packages are only available for linux. So we have to wait for qt5.12 migration which will come hopefully soon.looo wrote: ↑Thu Apr 18, 2019 8:51 am regarding dmgs:
Currently the conda-packages are not very stable (crash). If the problem is really caused by qt5.6.2 [1] maybe updating to 5.6.3 is a solution. If these versions are binary-compatible we can try to force the appimage using this version.
[1] https://bugreports.qt.io/browse/QTBUG-57404