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 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.