-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.bash_profile content deleted #6281
Comments
@mook-as to help here to see what could be going on. |
This happened to me on my work computer where I had not backed up my dot files yet. I'm a ZSH user, so in my case my |
@nwwells Thanks for letting us know! Is there anything unusual about your |
No it was just a normal .zshrc file!
Nathan Wells
…On Fri, Jan 12, 2024 at 11:47 AM Jan Dubois ***@***.***> wrote:
@nwwells <https://github.com/nwwells> Thanks for letting us know! Is
there anything unusual about your ~/.zshrc in any way? Is it a symlink,
like mine? If yes, does it point to Dropbox/iCloud/Google Drive/OneDrive or
similar?
—
Reply to this email directly, view it on GitHub
<#6281 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAH5Y4IFYKTVFNZ2UOFP3YDYOFSI5AVCNFSM6AAAAABBQUITI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBZGYZTCOJTGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hello...this has happened to me too. I installed rancher desktop with automatic PATH enabled and then it has overwritten everything I had in my bash_profile with the rancher desktop PATH |
I just lost my .*rc to this app. Really disappointing... |
I experienced the same losing my .zshrc :-/ |
Wiped my .bashrc and .bashprofile, had to restore from backup. I don't use .zshrc (at least I don't think I do), but it didn't wipe that for me and actually appended properly. |
This issue is a regression from Rancher Desktop 1.11. It is a race condition that happens after either a fresh install or a factory reset, when the first-run dialog is closed again very quickly after it is displayed. The problem has been fixed in #6352 and will be released in a 1.12.2 patch release in the next day or two, once it has passed further testing. Sorry for not catching this regression in time! |
It wiped my ~/.bash_profile file in 1.14.2 on Mac .. Need to mention that I downgraded from 1.16 to 1.14.2 and the wipe happened. my ~/.bash_profile was just a normal profile file.. no symlinks or etc .. |
Yes, but unfortunately there was another situation where this data loss could occur: when you had no internet access while the first-run dialog was displayed (#7154). That issue has been fixed in 1.15.0, and has additional fixes for extended attributes on profile files in 1.15.1.
Out of curiosity, why did you have to downgrade? |
I've experienced this before on Dec 18, but it has since happened 3 more times this Friday (5-Jan-2024): After a factory-reset, and restarting Rancher Desktop with automatic
PATH
management enabled, my~/.bash_profile
was replaced with an empty file that just had the Rancher Desktop boilerplate:Once I perform another factory-reset, the file gets deleted completely because it is now empty.
I use symlinks into Dropbox for
~/.bash_profile
(and~/.bashrc
):It is the symlink that gets deleted on the second factory-rest.
Since the older version is still on Dropbox, it is simple to restore. Here are some screenshots from when it happened:
The very last screenshot is from an instance that used manual path management, so the factory-reset didn't remove the path management logic because it was never added to the file. Still on a restart the file was overwritten.
I sometimes didn't discover that
.bash_profile
was destroyed until later (when I had to create a new terminal window), so I'm not sure if this is really true, but I believe this always happened when I initiated the factory-reset from the GUI, and restarted the app (via a hotkey) immediately once the window was closed (this was part of QASE testing, where many test cases ask for a factory-reset followed by a restart).I've not been able to reliably reproduce the problem, even though it happened 3 times this Friday.
Open questions
.bash_profile
stored as a symlink?.bashrc
and.bash_profile
symlink to the same file?Candidate?
After looking through the sources, the only way I can see this happening is if
fs.promises.stat('~/.bash_profile')
returnedENOENT
(or ifos.homedir()
did return an incorrect value):rancher-desktop/pkg/rancher-desktop/integrations/pathManagerImpl.ts
Lines 73 to 78 in 459e1a7
But the file exists, and I don't see how
HOME
could not be set correctly, so this still doesn't make sense.The text was updated successfully, but these errors were encountered: