View Issue Details

IDProjectCategoryView StatusLast Update
0004696FreeCADBugpublic2022-01-25 18:26
Reportermcgiwer Assigned Tochennes  
Status assignedResolutionopen 
Platformamd64OSDebianOS Version10
Product Version0.19 
Summary0004696: Problems with startup from command line (attached logs)
DescriptionWhen I attempt to start a fresh (just downloaded from the website) FreeCAD from the console and add an " & " char at the end (to run it in background), I get a following error message thrown out in the terminal window:

/tmp/.mount_freecazyi6sl/AppRun: line 41: 21741 Aborted                 ${MAIN} "$@"
Steps To ReproduceAttempt to start FreeCAD from the console, adding after the command a space and the & character
Additional InformationFor security reasons, I had replaced in the attached debug log the path to the home folder
FreeCAD Information



2021-07-14 18:28

reporter   ~0015735


I had discovered that the issue was caused because xcb couldn't become loaded. I got able to fix this by typing in the console following command:

sudo xhost +si:localuser:$USER


2021-07-18 19:30

reporter   ~0015737

Last edited: 2021-07-18 20:44


Note: The path where freeCAD is placed has been truncated for security reasons

After updating python to the version 3.9, it stopped to work with following errors:

Python path configuration:
  PYTHONHOME = '/usr/lib/python3.9' (set manually)
  PYTHONPATH = (not set)
  program name = 'bin/freecad'
  isolated = 0
  environment = 1
  user site = 1
  import site = 1
  sys._base_executable = 'bin/freecad'
  sys.base_prefix = '/usr'
  sys.base_exec_prefix = '/usr'
  sys.executable = 'bin/freecad'
  sys.prefix = '/usr'
  sys.exec_prefix = '/usr'
  sys.path = [
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

Current thread 0x00007fd8b4507800 (most recent call first):
<no Python frame>
Additionally, I don't know why the "PYTHONPATH" variable is displayed as not beeing set, even if it's has been exported.

Enviromental informations:

  • System: Debian 10 (64-bit Linux)
  • FreeCAD version: 0.19.2
  • Installed Python versions: 2.7 (for copatibility reasons to be able to run some extensions), 3.9

Hopefully it helps


2021-08-11 17:20

administrator   ~0015806

It looks like this is two different bugs, and that the first one has been resolved -- is that correct?


2021-12-29 03:26

administrator   ~0016136

@mcgiwer Your original bug report appears to have been resolved and was related to your system configuration. My read is that your later post here is a totally separate bug, so I plan to close this one shortly. If that is not the case, please let me know.


2022-01-25 18:17

administrator   ~0016301

@mcgiwer ping


2022-01-25 18:23

reporter   ~0016304

@Kunda1 pong ;-p


2022-01-25 18:26

reporter   ~0016305

@chennes The both bugs are related to each other and I'm not sure why they are becomming thrown out. To add it, this issue has appeared suddenly because in not long time earlier, the FreeCAD was working correcly. I hope it's only a temporary problem


2022-03-03 13:55

administrator   ~0017068

This ticket has been migrated to GitHub as issue 6237.

Issue History

Date Modified Username Field Change
2021-07-02 16:50 mcgiwer New Issue
2021-07-02 16:50 mcgiwer Tag Attached: 0.19
2021-07-14 18:28 mcgiwer Note Added: 0015735
2021-07-18 19:30 mcgiwer Note Added: 0015737
2021-07-18 19:33 mcgiwer Note Edited: 0015737
2021-07-18 20:44 mcgiwer Note Edited: 0015737
2021-08-11 17:20 chennes Note Added: 0015806
2021-08-11 17:20 chennes Assigned To => chennes
2021-08-11 17:20 chennes Status new => feedback
2021-12-29 03:23 chennes Severity block => minor
2021-12-29 03:26 chennes Note Added: 0016136
2021-12-29 03:26 chennes Priority high => normal
2022-01-25 18:17 Kunda1 Note Added: 0016301
2022-01-25 18:23 mcgiwer Note Added: 0016304
2022-01-25 18:23 mcgiwer Status feedback => assigned
2022-01-25 18:26 mcgiwer Note Added: 0016305