[kde] [Bug 491666] New: I have a new install of Fedora 40 with KDE. Installing conda from a command line promt breaks new Konsole shells (no cursor, cammands do not execute)
bugzilla_noreply at kde.org
bugzilla_noreply at kde.org
Tue Aug 13 14:14:55 BST 2024
https://bugs.kde.org/show_bug.cgi?id=491666
Bug ID: 491666
Summary: I have a new install of Fedora 40 with KDE. Installing
conda from a command line promt breaks new Konsole
shells (no cursor, cammands do not execute)
Classification: I don't know
Product: kde
Version: unspecified
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: joanna.m.leng at gmail.com
Target Milestone: ---
***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org
If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
SUMMARY
I have a new install of Fedora 40 with KDE. I want to use it with conda so I
tried a conda command to see if it came with the system and got a message to
say I could install it there through the shell command line. Installing conda
this way through a shell request means there were no conda environments not
even base until I run the "conda init" command and when I did that new Konsole
shells now have no cursor and while I can type in the shell the commands do not
execute.
STEPS TO REPRODUCE
1. Take a new install Fedora 40 with KDE.
2. Start a new Konsol shell and type “conda list”. I got a text message back
saying something along the lines of do you want to install conda press y so I
pressed y and conda installed.
3. When I typed "conda list" I was told there were no conda environments.
4. I typed "conda list env" and could see a base environment but was told to
run the "conda init" command.
5. I did some looking through google and run the command "conda init --system"
and nothing seemed to happen so then I typed "conda --user" again nothing
seemed to happen so I typed "conda init" I was then told to stop that shell and
start a new one. I did that but the new shell had no cursor and while I could
type into it nothing happened. something happened.
6. I was then told to stop that shell and start a new one. I did that but the
new shell had no cursor and while I could type into it nothing happened. The
cursor I had un until them was of the format <userid>@<machine>:~$
7. I edited my .bashrc file in my home directory. Initially commented out the
conda stuff at the end of the file but no change when I started a new shell.
8. Then I put ‘echo ".bashrc running"’ at the top of my .bashrc file and
started a new shell. The shell had no cursor but did have the message printed
to screen ".bashrc running" in it.
9. Then after the first logial command in the .bashrc I put a different print
to screen command see below it is with my print to screen line.
# Source global definitions
if [ -f /etc/bashrc ];
then . /etc/bashrc
fi
echo "source global definitions have run"
I started a new shell and I go the same as last time, the old message printed
but this new message did not print to screen.
10. I then commented out this logical operation and replaced it with
. /etc/bashrc
echo "source global definitions have run"
This time when I open a new shell I got the 2 messages to screen, the first
saying ".bashrc running" which is right at the top of the file and then "source
global definitions have run" and I had a cursor. Unfortunately, this cursor is
not the same as my original one. The original cursor was
<unername>@<machinename>:~$ while the new one is bash-5.4$
11. When I type the command
-f /etc/bashrc
or
f /etc/bashrc
if get the error message
"bash: f: command not found"
OBSERVED RESULT
In my new Fedor 40 install I would open a Konsole shell through the menu in the
bottom left of the screen. The cursor would have the format
<unserid>@<machinename>:~$ and I could type in command lines that would execute
for example the “ls -ln” command would print a list of files and directories
for me. Once I installed the conda through the shell and ran the command “conda
init” new shells had no cursor and commands did not execute.
EXPECTED RESULT
I hoped that when I was given this message to install conda through the shell
it would do it so I could see the environments and that I would be able to
start Konsole shells in the same way with the same old cursor and it would
execute my commands. I would either not expect to see this message if it does
not work or to be directed to install in a different way. Now my system does
not work I would like to know how to fix it.
SOFTWARE/OS VERSIONS
Windows:
macOS:
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Fedora 40 (https://fedoraproject.org/workstation/download)
installed stright from the download at this link.
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list