Errors observed when starting AppImage.

Post here for help on using FreeCAD's graphical user interface (GUI).
Forum rules
and Helpful information
IMPORTANT: Please click here and read this first, before asking for help

Also, be nice to others! Read the FreeCAD code of conduct!
Post Reply
MrGadget49
Posts: 27
Joined: Mon Oct 03, 2022 6:31 am

Errors observed when starting AppImage.

Post by MrGadget49 »

Hello Everyone,

My name is Jody, and I've been using FreeCAD for about a year or more now, and think it is AWESOME! I'm a programmer by trade and have been doing computer graphics work since the mid 1970's. Mostly 2D stuff.

I've been running FreeCAD on a Debian VirtualBox from an AppImage and have observed the following errors on startup. Is this normal, or is there something wrong with my setup? FreeCAD seems to be working OK with a few exceptions, but before I address those, I'd like to make sure it's not my setup causing the problems.

Code: Select all

jody@debbie:~/Downloads$ ./FreeCAD_weekly-builds-30492-2022-10-02-conda-Linux-x86_64-py310.AppImage
FreeCAD 0.21, Libs: 0.21R30492 (Git)
© Juergen Riegel, Werner Mayer, Yorik van Havre and others 2001-2022
FreeCAD is free and open-source software licensed under the terms of LGPL2+ license.
FreeCAD wouldn't be possible without FreeCAD community.
  #####                 ####  ###   ####  
  #                    #      # #   #   # 
  #     ##  #### ####  #     #   #  #   # 
  ####  # # #  # #  #  #     #####  #   # 
  #     #   #### ####  #    #     # #   # 
  #     #   #    #     #    #     # #   #  ##  ##  ##
  #     #   #### ####   ### #     # ####   ##  ##  ##

Assembly4 workbench (v0.12.4) loaded
Sheet Metal workbench loaded
Xlib: sequence lost (0x1054e > 0x550) in reply type 0x0!
Xlib: sequence lost (0x10555 > 0x557) in reply type 0x0!
Xlib: sequence lost (0x1055c > 0x55e) in reply type 0x0!
Xlib: sequence lost (0x1056d > 0x56f) in reply type 0x0!
Xlib: sequence lost (0x10574 > 0x576) in reply type 0x0!
Xlib: sequence lost (0x1057b > 0x57d) in reply type 0x0!
[18630:18644:1004/023256.027763:ERROR:command_buffer_proxy_impl.cc(141)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
Xlib: sequence lost (0x105f2 > 0x5f4) in reply type 0x0!
Xlib: sequence lost (0x105f9 > 0x5fb) in reply type 0x0!
Xlib: sequence lost (0x10600 > 0x602) in reply type 0x0!
Here is my "About FreeCAD" info

Code: Select all

OS: Debian GNU/Linux 10 (buster) (MATE)
Word size of FreeCAD: 64-bit
Version: 0.21.30492 (Git) AppImage
Build type: Release
Branch: master
Hash: b4578fb3eae842eb510a1bc055d07d369a67ce94
Python 3.10.6, Qt 5.15.4, Coin 4.0.0, Vtk 9.1.0, OCC 7.6.3
Locale: English/United States (en_US)
Installed mods: 
  * lattice2 1.0.0
  * Assembly4 0.12.4
  * Curves 0.5.8
  * fasteners 0.4.13
  * sheetmetal 0.2.57
Any help or information will be appreciated!

Thanks,

Jody
openBrain
Veteran
Posts: 9034
Joined: Fri Nov 09, 2018 5:38 pm
Contact:

Re: Errors observed when starting AppImage.

Post by openBrain »

Welcome,

I guess this comes from OpenGL issues probably due to the virtualization.
You can either try to fine-tune OpenGL settings in VirtualBox, or launch FreeCAD with software OpenGL rendering only.
MrGadget49
Posts: 27
Joined: Mon Oct 03, 2022 6:31 am

Re: Errors observed when starting AppImage.

Post by MrGadget49 »

Thanks, I'll try your suggestions and let you know what i find out.

Jody
MrGadget49
Posts: 27
Joined: Mon Oct 03, 2022 6:31 am

Re: Errors observed when starting AppImage.

Post by MrGadget49 »

openBrain wrote: Tue Oct 04, 2022 7:20 am You can either try to fine-tune OpenGL settings in VirtualBox, or launch FreeCAD with software OpenGL rendering only.
You were correct. I didn't have any luck tuning VirtualBox, but launching FreeCAD with software rendering got rid of the messages.

Other than the those error messages, FreeCAD seems to be running fine. I'll probably just ignore them and only turn off the hardware rendering if I suspect that it may be causing a problem.

Thanks again for your help!

Jody
Post Reply