Closed avoiceofreason closed 7 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
You can pass -e SHELL=/bin/bash
or set the shell in Konsole from settings > Profiles, and this kind of stuff can be set using other methods as well.
In general I try not to mess with the users home directory (/config) unless absolutely necessary given the amount of time these images have been deployed and I don't know if I would mess up someones custom settings.
Thanks. In fact the SHELL env variable is already set to /bin/bash so passing to docker wouldn't change anything (?)
On further investigation it seems that konsole profile functionality looks pretty broken. The default profile is both builtin and hardcoded. You cannot change it, delete it, or convert it to a "Default.profile" in .local/share/konsole
Only option is to create a new profile with the correct command setting and setup as default.
Would have been nice to have done that on the standard webtop release but as you say that ship has sailed.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
This issue is locked due to inactivity
Is there an existing issue for this?
Current Behavior
On a clean install on webtop with a clean /config volume mapping, the default konsole profile appears to have a blank command parameter. This means konsole start with this error:
"Warning: Could not find '', starting '/bin/bash' instead. Please check your profile settings."
konsole >> settings >> configure konsole >> profiles Default profile is readonly but not editable
You can add another profile and add Command: /bin/bash and set as default to workaround
Expected Behavior
konsole should start /bin/bash with no errors
Steps To Reproduce
Start webtop docker container open https://domain:3001 to access webtop
open konsole
error: "Warning: Could not find '', starting '/bin/bash' instead. Please check your profile settings."
Environment
CPU architecture
x86-64
Docker creation
Container logs