Toolbox and Distrobox not using my bashrc file

[viscid nebula]

Who
Happens exclusively to my main user. I migrated my home folder from a PopOS installation a while back, and decided to change usernames by simply renaming my home folder rather than doing it properly through system tools. I have a symlink at my /home/oldusername leading to my current /home/osom because some things break otherwise.

What
On my daily user account, Toolbox and Distrobox does not recognize my .bashrc file when entering the container, and falls back to the file present at /etc/bashrc or /etc/bash.bashrc inside the container. I need to run bash once again to fully initialize my user config files. This does not happen on other user accounts.

When
All the time while I'm using my main user account.

Where
Distribution: Fedora Silverblue 37

For the osom user, both distrobox and toolbox applies the default bashrc file. I need to run bash again for it to run with my configs. I then run bash again with the --rcfile option to demonstrate the original container bashrc configs.

In the third picture, I login to another user on the computer (toolbox doesn't work when switching users via su due to a dbus related issue, https://github.com/containers/podman/issues/15262), where both toolbox and distrobox has seemingly no issues transferring over my bashrc

[viscid nebula]

This also happens when connecting to my user on bare metal over SSH as well

[ruby flint]

Hmm this is interesting

[viscid nebula]

Update, I figured out this happens to all login shells