| Summary: | The zsh configuration file at "/usr/share/zsh/manjaro-zsh-config" had corrupted zsh and bash badly. | ||
|---|---|---|---|
| Product: | [Applications] konsole | Reporter: | toastwest646 |
| Component: | emulation | Assignee: | Konsole Developer <konsole-devel> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | major | ||
| Priority: | NOR | ||
| Version: | master | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
output of all the errors that were emitting from that single zsh configuration file
attachment-23793-0.html |
||
Created attachment 145791 [details] attachment-23793-0.html Not Konsole. Programs that run under Konsole have different configurations, but their bugs and issues don’t fall on Konsole. Le sam. 22 janv. 2022 à 16:03, <bugzilla_noreply@kde.org> a écrit : > https://bugs.kde.org/show_bug.cgi?id=448958 > > Bug ID: 448958 > Summary: The zsh configuration file at > "/usr/share/zsh/manjaro-zsh-config" had corrupted zsh > and bash badly. > Product: konsole > Version: master > Platform: Manjaro > OS: Linux > Status: REPORTED > Severity: major > Priority: NOR > Component: emulation > Assignee: konsole-devel@kde.org > Reporter: toastwest646@gmail.com > Target Milestone: --- > > Created attachment 145758 [details] > --> https://bugs.kde.org/attachment.cgi?id=145758&action=edit > output of all the errors that were emitting from that single zsh > configuration > file > > SUMMARY > *** > I downloaded Manjaro with KDE 21.2.1 several days ago and I initially tried > installing node version manager, which I'd never had trouble with in the > past, > so I tried to run source ~/.zshrc to load the nvm directory to the > terminals > executable path which did not work at all, I got an error message that said > bash: setopt: command not found...bash: setopt: command not found... get > sent > out. I was eventually able to get everything to work on my personal text > editors terminal, so I didn't realize there was something really wrong > with zsh > till this morning when I tried to run a program from terminal Konsole and > zsh > responded with an error of not knowing that program. So I started to > troubleshoot and try to figure out why zshell wasn't installing properly, I > went and got the script for nvm directly from github and loaded it into > zshells > .zshrc file and tried to run source ~/.zshrc again but this time I was > getting > like a really huge stream of errors not just from zshell but bash was > spewing > out a lot of errors after the command source ~/.zshrc was given I knew it > was a > massive config file that was was corrupting the shells. > So I found a directory that had a really massive configuration file and it > was > the one causing both shells from operating > I was able to fix all issues of > > STEPS TO REPRODUCE > 1. Try to install an application while that configuation file is loaded in > your > default shell > 2. Try to update anything on that shell and it won't work > 3. run the command source ~/.zshrc for a shell thats effected with this > config > file > > OBSERVED RESULT > My text editors terminal wasn't affected because it didn't have a > reference to > a corrupt config file > > EXPECTED RESULT > A very slowed down shell, and unable > > SOFTWARE/OS VERSIONS > Linux/KDE Plasma: Konsole, Yakuza > (available in About System) > KDE Plasma Version: 5.23.4 > KDE Frameworks Version: 5.89.0 > Qt Version: 5.15.2 > > ADDITIONAL INFORMATION > I've included the error messages from the terminals output and I was also > able > to go back and get a exact copy of the config > file. > > -- > You are receiving this mail because: > You are the assignee for the bug. |
Created attachment 145758 [details] output of all the errors that were emitting from that single zsh configuration file SUMMARY *** I downloaded Manjaro with KDE 21.2.1 several days ago and I initially tried installing node version manager, which I'd never had trouble with in the past, so I tried to run source ~/.zshrc to load the nvm directory to the terminals executable path which did not work at all, I got an error message that said bash: setopt: command not found...bash: setopt: command not found... get sent out. I was eventually able to get everything to work on my personal text editors terminal, so I didn't realize there was something really wrong with zsh till this morning when I tried to run a program from terminal Konsole and zsh responded with an error of not knowing that program. So I started to troubleshoot and try to figure out why zshell wasn't installing properly, I went and got the script for nvm directly from github and loaded it into zshells .zshrc file and tried to run source ~/.zshrc again but this time I was getting like a really huge stream of errors not just from zshell but bash was spewing out a lot of errors after the command source ~/.zshrc was given I knew it was a massive config file that was was corrupting the shells. So I found a directory that had a really massive configuration file and it was the one causing both shells from operating I was able to fix all issues of STEPS TO REPRODUCE 1. Try to install an application while that configuation file is loaded in your default shell 2. Try to update anything on that shell and it won't work 3. run the command source ~/.zshrc for a shell thats effected with this config file OBSERVED RESULT My text editors terminal wasn't affected because it didn't have a reference to a corrupt config file EXPECTED RESULT A very slowed down shell, and unable SOFTWARE/OS VERSIONS Linux/KDE Plasma: Konsole, Yakuza (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I've included the error messages from the terminals output and I was also able to go back and get a exact copy of the config file.