• We had to restore from a backup today after a failed software update. Backup was from 0000 EDT and restored it at 0800 EDT so we lost about 8hrs. Today is 07/20/2024. More info here.

"Config File Not Writable" on Boot (Manjaro) - Solved

ghosty999

Member
Joined
Oct 18, 2022
Messages
59
Reaction score
34
Credits
550
Hello :)
I'm getting this on boot just after the grub OS selection screen. Only just started recently. It allows me to boot if I select OK. Is it just a case of changing the permissions on the mentioned file?
Thanks!
 

Attachments

  • 123.jpeg
    123.jpeg
    81.6 KB · Views: 227
  • 1234.jpg
    1234.jpg
    32.4 KB · Views: 227


What do the permissions look like of that file?
Code:
ls -l /var/lib/sddm/.config/sddm-greeterrc
 
What do the permissions look like of that file?
Code:
ls -l /var/lib/sddm/.config/sddm-greeterrc
Says no such file exists. At a GUI level it looks like this. Only .config file is this one:
 

Attachments

  • 12345.png
    12345.png
    79.7 KB · Views: 220
You can try creating the file like this.
Code:
sudo touch /var/lib/sddm/.config/sddm-greeterrc
Then seeing what happens next time you reboot?
 
Last edited:
You can try creating the file like this.
Code:
sudo touch /var/lib/sddm/.config/sddm-greeterrc
Then seeing what happens next time you reboot?
Thanks I'll try this too... but I think I found the issue :(

"It means that for some reason, files that SDDM requires have become read only. That can also mean ssd failure. You can try to chown the files and folder that SDDM can't write to, but if it happens again, or the rest of the OS starts acting weird, check your hardware."
 

Attachments

  • 642542.jpeg
    642542.jpeg
    234.4 KB · Views: 204
If that is the case if you to do a "touch" somewhere on the root filesystem you should get a read only as well? Also be sure to check "dmesg" output if your ssd is giving errors you should see them there as well including i/o errors.
 
If that is the case if you to do a "touch" somewhere on the root filesystem you should get a read only as well? Also be sure to check "dmesg" output if your ssd is giving errors you should see them there as well including i/o errors.
Results attached :)
 

Attachments

  • 643534.png
    643534.png
    17.3 KB · Views: 217
  • output.txt
    77 KB · Views: 248
There are quite a few errors about your nvm ssd but no i/or errors yets.
[ 2437.692185] nvme 0000:03:00.0: [ 0] RxErr (First)
[ 2439.615785] nvme 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 2439.615792] nvme 0000:03:00.0: device [15b7:5006] error status/mask=00000001/0000e000
With the screenshot where you touched the file, the file should exist now. What happens when you restart your system now?
 
There are quite a few errors about your nvm ssd but no i/or errors yets.

With the screenshot where you touched the file, the file should exist now. What happens when you restart your system now?
Just restarted and same error message upon boot.

Could it be the failing RAM has corrupted this file?
 

Staff online

Members online


Top