Rustup -self uninstall made my pc unrespondable

Helle.

I tryid installing rust useing "curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh"
And everything went fine.
After a while i did "rustup --self uninstall" and thats where everything broke.
My computer stopped beeing responsable at all. So I rebooted and I discovered that somehow there were no diskspace left. So I deleted ~/.cargo and ~./rust to free diskspace.

Now my problem is I can no longer log in gdm as the user I installed rust under.
Every other users works fine.
I don't know what files rust editet exept .bashrc
How do I fix my user so it can log in again?

Thanks.

rustup should only edit your bashrc during installation. I don't think it needs to update it when uninstalling.

are you still able to log into a console? e.g. use Ctrl - Alt - F3 to switch to a tty and log in with the user, then run dbus-run-session gnome-shell, it should print out the error messages so you can understand what went wrong.

you may also check the error messages in the system logs. assuming your system uses systemd, try the journalctl -u gdm command.

Yes I can log in with console as the rust user. But not gdm.

dbus-run-session gnome-shell
Failed to configure: Unsupported session type

the last enteies of journalctl -u gdm shows:
-- Boot a25bcd4674a74b72a479e215d02c7744 --
Oct 29 01:53:33 Lo-Laptop systemd[1]: Starting gdm.service - GNOME Display Manager...
Oct 29 01:53:33 Lo-Laptop systemd[1]: Started gdm.service - GNOME Display Manager.
Oct 29 01:53:33 Lo-Laptop gdm-launch-environment][1643]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm(uid=110) by (uid=0)
Oct 29 01:53:48 Lo-Laptop gdm-password][2523]: gkr-pam: unable to locate daemon control file
Oct 29 01:53:48 Lo-Laptop gdm-password][2523]: gkr-pam: stashed password to try later in open session
Oct 29 01:53:48 Lo-Laptop gdm-password][2523]: pam_unix(gdm-password:session): session opened for user heine(uid=1000) by heine(uid=0)
Oct 29 01:53:48 Lo-Laptop gdm-password][2523]: gkr-pam: unlocked login keyring
Oct 29 01:53:52 Lo-Laptop gdm3[1457]: Gdm: GdmDisplay: Session never registered, failing
Oct 29 01:59:27 Lo-Laptop systemd[1]: Stopping gdm.service - GNOME Display Manager...
Oct 29 01:59:27 Lo-Laptop gdm3[1457]: Gdm: Child process -1778 was already dead.
Oct 29 01:59:27 Lo-Laptop systemd[1]: gdm.service: Deactivated successfully.
Oct 29 01:59:27 Lo-Laptop systemd[1]: Stopped gdm.service - GNOME Display Manager.
Oct 29 01:59:27 Lo-Laptop systemd[1]: Starting gdm.service - GNOME Display Manager...
Oct 29 01:59:28 Lo-Laptop systemd[1]: Started gdm.service - GNOME Display Manager.
Oct 29 01:59:28 Lo-Laptop gdm-launch-environment][3623]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm(uid=110) by (uid=0)
Oct 29 02:00:02 Lo-Laptop gdm-password][4252]: gkr-pam: unable to locate daemon control file
Oct 29 02:00:02 Lo-Laptop gdm-password][4252]: gkr-pam: stashed password to try later in open session
Oct 29 02:00:02 Lo-Laptop gdm-password][4252]: pam_unix(gdm-password:session): session opened for user john(uid=1002) by john(uid=0)
Oct 29 02:00:02 Lo-Laptop gdm-password][4252]: gkr-pam: unlocked login keyring
Oct 29 02:00:11 Lo-Laptop gdm3[3618]: Gdm: Child process -3629 was already dead.
Oct 29 02:00:22 Lo-Laptop gdm-launch-environment][5439]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm(uid=110) by (uid=0)
Oct 29 02:00:34 Lo-Laptop gdm-password][5971]: gkr-pam: unable to locate daemon control file
Oct 29 02:00:34 Lo-Laptop gdm-password][5971]: gkr-pam: stashed password to try later in open session
Oct 29 02:00:34 Lo-Laptop gdm-password][5971]: pam_unix(gdm-password:session): session opened for user heine(uid=1000) by heine(uid=0)
Oct 29 02:00:35 Lo-Laptop gdm-password][5971]: gkr-pam: unlocked login keyring
Oct 29 02:00:38 Lo-Laptop gdm3[3618]: Gdm: GdmDisplay: Session never registered, failing
Oct 29 02:01:29 Lo-Laptop systemd[1]: Stopping gdm.service - GNOME Display Manager...
Oct 29 02:01:30 Lo-Laptop gdm3[3618]: Gdm: Child process -5479 was already dead.
Oct 29 02:01:30 Lo-Laptop systemd[1]: gdm.service: Deactivated successfully.
Oct 29 02:01:30 Lo-Laptop systemd[1]: Stopped gdm.service - GNOME Display Manager.
Oct 29 02:01:30 Lo-Laptop systemd[1]: Starting gdm.service - GNOME Display Manager...
Oct 29 02:01:30 Lo-Laptop systemd[1]: Started gdm.service - GNOME Display Manager.
Oct 29 02:01:30 Lo-Laptop gdm-launch-environment][6634]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm(uid=110) by (uid=0)
Oct 29 02:02:20 Lo-Laptop gdm-password][7212]: pam_unix(gdm-password:auth): authentication failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=john
Oct 29 02:02:29 Lo-Laptop gdm-password][7240]: gkr-pam: unable to locate daemon control file
Oct 29 02:02:29 Lo-Laptop gdm-password][7240]: gkr-pam: stashed password to try later in open session
Oct 29 02:02:29 Lo-Laptop gdm-password][7240]: pam_unix(gdm-password:session): session opened for user john(uid=1002) by john(uid=0)
Oct 29 02:02:29 Lo-Laptop gdm-password][7240]: gkr-pam: unlocked login keyring
Oct 29 02:02:38 Lo-Laptop gdm3[6628]: Gdm: Child process -6640 was already dead.

I'm not entirely sure, but I see two login users in the log, one for the user heine, one for john:

Oct 29 01:53:48 Lo-Laptop gdm-password][2523]: pam_unix(gdm-password:session): session opened for user heine(uid=1000) by heine(uid=0)
Oct 29 01:53:48 Lo-Laptop gdm-password][2523]: gkr-pam: unlocked login keyring
...
Oct 29 02:00:02 Lo-Laptop gdm-password][4252]: pam_unix(gdm-password:session): session opened for user john(uid=1002) by john(uid=0)
Oct 29 02:00:02 Lo-Laptop gdm-password][4252]: gkr-pam: unlocked login keyring
...

it seems the authentication already succeeded (there's one failed attempt for john, but I think that's just one time occur).

but after the successful authenticaion, the user session failed to start:

Oct 29 02:00:38 Lo-Laptop gdm3[3618]: Gdm: GdmDisplay: Session never registered, failing

I never had similar problems, but I guess it's caused by bad session script, possibly in the login shell script?

assuming it's caused by the rustup leftover and you are using bash, check ~/.bashrc or ~/.profile, remove lines refering rustup or cargo, e.g. the typical source $HOME/.cargo/env command added by rustup.

The user heine can't login. it just returns to gdm. The user john can login.

I already removed the lines from ~/.bashrc and ~/,profile

well, I'm out of ideas.

maybe some runtime states are corrupted due to disk full?

these are shots in the dark, but you may try them anyways:

  • remove everything in $XDG_RUNTIME_DIR, usually /run/user/$(id -u)/.

    this is safe, they will be recreated when you login again.

  • cleanup potentially corrupted gnome configurations, e.g. ~/.config/gnome-shell/ or ~/.config/gnome-session/ etc

    prefer renaming to removing, so you can recover them later if needed.

  • cleanup potentially corrupted session data, e.g. ~/.cache/gnome-shell etc.

    again, rename them so you can restore them.

  • lastly, try switching gdm to use xorg instead of wayland, if xorg works, than the failure is probably in mutter. this narrows the problem down a little bit. but I'm not familiar with that area.

It seeems more like a gdm/gnome problem than rust. I'll try their forum.
I suspeted it was rust ralated as as only thing I was messing with was rust.
I still don't understand why uninstalling rust would fill up my drive.

Thanks for your help.

good idea. they definitely have better knowledge to figure out the cause and solve the problem.

I think rustup is highly unlikely the real cause of the full disk, because all the "uninstall" command does is deleting the relevant directories. your drive was probably already (nearly) full. it just happened at the same time.

of course, "unlikely" doesn't mean it can be ruled out, bugs do exist in software. but the chances are low. however, low probability also means high information value. no matter if it's caused by rustup, please come back and inform us after your problem gets solved. it'd be very helpful.

I do know that I had 20G free space before I atempted to install rust. I did it all with the user heine.
That user have sudo access without password.
As of the filesystem is btrfs with compression.
I have 2 subvolumes one is / and the other is /home
Any other info I'd gladley give.

Also gnome warns me when I'm low on disk space. That dident happen this time.

btrfs (with compression) has the somewhat nasty behaviour that it can't store more data before the partition as reported by df is actually full. If gnome checks df it may not have warned you while it was still impossible to store things. I don't know exactly when it happens (I haven't seen the behaviour in a while), but see e.g. Ubuntu thinks Btrfs disk is full but it's not.

Rust needs a lot of space for compilation, much of those 20 GB will be used easily, thus it does appear likely that you ran out of disk space while working with Rust, not while uninstalling it (although the Rust compiler does report out of space errors while compiling, but maybe you missed those).

Note that uninstalling Rust will not clean up things like target directories in any project folders you have made, and those get a lot of data put into them. My apologies.