I am currently using CodeLite 17.0.0 together with wxWidgets 3.2.1.
I am building CodeLite from source on my Red Hat Enterprise Linux 8 and it worked fine in the past.
Recently I upgraded my RHEL 8 to v8.8 and this somehow broke my CodeLite.
After doing some investigation, I figured out that its related to #1661 and by deleting the .codelite directory in my home directory, results in CodeLite being able to start again.
However, after a system restart, I again run into the same issue where CodeLite won't start.
From what I could tell so far, .codelite/config/codelite.xml looks fine after I deleted the entire .codelite directory and restarted CodeLite, but when I do a system restart, this codelite.xml somehow gets "cleaned", i.e. its simply empty after a restart.
I suspect this is my issue, but I don't have the faintest idea why this happening.
Could you please assist?
Many thanks in advance!
Version
Self compiled
Operating system
Linux
Steps to reproduce
- Upgrade RHEL from 8.7 to 8.8
- Delete .codelite
- Restart CodeLite and wait for a few minutes until the basics are configured
- Close CodeLite
- Restart RHEL
- Attempt to start CodeLite after a system reboot, which fails
Relevant log output
[Main] Failed to load configuration file: config/codelite.xml. Working directory: /home/evn/.codelite
What happened?
Hello @eranif ,
I am currently using CodeLite 17.0.0 together with wxWidgets 3.2.1.
I am building CodeLite from source on my Red Hat Enterprise Linux 8 and it worked fine in the past.
Recently I upgraded my RHEL 8 to v8.8 and this somehow broke my CodeLite.
After doing some investigation, I figured out that its related to #1661 and by deleting the
.codelite
directory in my home directory, results in CodeLite being able to start again.However, after a system restart, I again run into the same issue where CodeLite won't start.
From what I could tell so far,
.codelite/config/codelite.xml
looks fine after I deleted the entire.codelite
directory and restarted CodeLite, but when I do a system restart, thiscodelite.xml
somehow gets "cleaned", i.e. its simply empty after a restart.I suspect this is my issue, but I don't have the faintest idea why this happening.
Could you please assist?
Many thanks in advance!
Version
Self compiled
Operating system
Linux
Steps to reproduce
Relevant log output