Hi, regarding https://bugs.trinitydesktop.org/show_bug.cgi?id=2729
I am wondering why m_config.readBoolEntry( "Empty", true ) would report false, when in the config file it is still true and m_config.sync() was called.
Any ideas?
regards
On 2018/04/11 03:24 AM, deloptes wrote:
Hi, regarding https://bugs.trinitydesktop.org/show_bug.cgi?id=2729
I am wondering why m_config.readBoolEntry( "Empty", true ) would report false, when in the config file it is still true and m_config.sync() was called.
Any ideas?
regards
That sounds weird. It should give you true in that case. Are you looking at the correct config file? Any local config file overwriting a global one perhaps? Cheers Michele
Michele Calgaro wrote:
That sounds weird. It should give you true in that case. Are you looking at the correct config file? Any local config file overwriting a global one perhaps?
I have no idea really - I tried tail - but it does not say that something writes to the file in the meanwhile.
The file is .trinity/share/config/trashrc
If I could understand why it is not written to the file, although sync is called, we could find the proper solution for this bug.
regards
On 2018/04/11 02:13 PM, deloptes wrote:
Michele Calgaro wrote:
That sounds weird. It should give you true in that case. Are you looking at the correct config file? Any local config file overwriting a global one perhaps?
I have no idea really - I tried tail - but it does not say that something writes to the file in the meanwhile.
The file is .trinity/share/config/trashrc
If I could understand why it is not written to the file, although sync is called, we could find the proper solution for this bug.
regards
Yeah, that sounds funny. I will need to spend some time to investigate more in detail then. After I am done with bug 2784, I will look into this, since this bug is on R14.0.5 bug list and you have done a lot of analysis already :-)
Cheers Michele
Michele Calgaro wrote:
Yeah, that sounds funny. I will need to spend some time to investigate more in detail then. After I am done with bug 2784, I will look into this, since this bug is on R14.0.5 bug list and you have done a lot of analysis already :-)
That would be great, thanks! Should I update 2729 with additional information let me know.
regards
-
deloptes -
Michele Calgaro