before the issue, wifi app was configured not to start automatically because I sometimes change the mac after logging in. I usually enable it afterwards with iftop and then systemctl start NetworkManager.service && sudo nm-applet
Back to the issue: I can log in to recovery mode, filesystem is read and write, unsure that ‘network’ enables the network.
I can also root it.
If I execute sudo apt update output reads: failed to fetch http…. Could not connect to 127.0.0.1:8118, connection refused. I don’t know how to fix this.
8118 should be tor.
If I execute sudo apt install -f or dpkg –configure -a I get the regular list of packages I should delete with autoremove and the broken package I believe caused this issue during upgrade:
libfreerdp2-2
and a dpkg error:
/usr/sbin/update-info-dir: 11 /etc/environment: debug: not found dpkg: error processing package install-info (-configure) errors were encountered while processing install-info sub process /usr/bin/dpkg returned an error code (1)
lsb_release -a shows distro is 23.10
secondary questions: is there any way to access my data as root? I can cd to media and to my home directory, but this last directory appears as empty.
How do I change the font’s color as root? Very dark blue, cannot read anything
thanks
@ceciline02 in a recovery mode what is the error when you try to mount the file system?
in recovery mode as root I executed:
mount -o remount,rw /
mount --all
then cd’ed to /media/home, ls’ed and got no results.
I also don’t know if changes to make the system writable are made on the go or if I have to reboot. I rebooted and the system is still in read only mode.
ETA: another command that might be relevant:
dpkg --configure -a
returns
error processing package install-info (–configure), installed install-info package post installation script subprocess returned error exit status 127
mount --allonly does something if the mount point is in/etc/fstab@ceciline02 when you execute those commands — not even sure if this would help — does dmesg say anything? Even before you go to mount them on boot maybe dmesg might say something about the disks? Or any log in var log?
dmesg prints a large log that I cannot copy, the only red lines I read regard bluetooth, but the log is huge and I can only see a fraction of it.
I can cd to /var/log and ls it, what file do I have to open? or what do I do now?
@ceciline02 you can pipe dmesg into less I think. Dmesg | less and then use the forward slash to search but also you can use the up and down arrows to go up and down.
Sooo, I guess a couple of things.
What error do you get when you try to boot it not in rescue mode?
Was your /home directory a separate partition?
I don’t think networking neccesarily starts in rescue mode, so you getting a response that 127.0.0.1:8118 is unreachable probably makes sense (your tor proxy will rely on the network service afterall)
wifi app was configured not to start automatically
With
nmtui(or nmcli) you can activate WiFi connection.I can cd to media and to my home directory, but this last directory appears as empty.
Does
mount /homeimprove that ?Does mount /home improve that ?
no
Im reading about nmtui
feel free to suggest other approaches
How about booting from Linux live medium (For example Ubuntu installation iso on pen drive, and choose Try without installing) and from there see if you can get to your home files.
