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

ghosty999

Member
Joined
Oct 18, 2022
Messages
53
Reaction score
26
Credits
500
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: 92
  • 1234.jpg
    1234.jpg
    32.4 KB · Views: 97


f33dm3bits

Gold Member
Gold Supporter
Joined
Dec 11, 2019
Messages
6,391
Reaction score
4,847
Credits
46,972
What do the permissions look like of that file?
Code:
ls -l /var/lib/sddm/.config/sddm-greeterrc
 
OP
ghosty999

ghosty999

Member
Joined
Oct 18, 2022
Messages
53
Reaction score
26
Credits
500
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: 80

f33dm3bits

Gold Member
Gold Supporter
Joined
Dec 11, 2019
Messages
6,391
Reaction score
4,847
Credits
46,972
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:
OP
ghosty999

ghosty999

Member
Joined
Oct 18, 2022
Messages
53
Reaction score
26
Credits
500
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: 91

f33dm3bits

Gold Member
Gold Supporter
Joined
Dec 11, 2019
Messages
6,391
Reaction score
4,847
Credits
46,972
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.
 
OP
ghosty999

ghosty999

Member
Joined
Oct 18, 2022
Messages
53
Reaction score
26
Credits
500
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: 97
  • output.txt
    77 KB · Views: 130

f33dm3bits

Gold Member
Gold Supporter
Joined
Dec 11, 2019
Messages
6,391
Reaction score
4,847
Credits
46,972
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?
 
OP
ghosty999

ghosty999

Member
Joined
Oct 18, 2022
Messages
53
Reaction score
26
Credits
500
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?
 

f33dm3bits

Gold Member
Gold Supporter
Joined
Dec 11, 2019
Messages
6,391
Reaction score
4,847
Credits
46,972


Top