SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Yes I know, but I stated in previous posts, adding -l in command /bin/bash in the profile in Konsole and hitting apply, and restarting Konsole does not work and it is a KDE issue, but there is no definitive reason as to why.
This must mean that the arguments are not parsed correctly.
Or for some reason, Konsole does not like what is put in Command and backs up to /bin/bash or whatever shell is defined in /etc/passwd.
Konsole per se has completely no impact on shell being login or not.
It basically spawns bash and then controls stdin/stdout/stderr of it.
I haven't yet updated to the latest Plasma, so I cannot test it.
Can you try making the following script to be the shell command in the profile:
Code:
$ cat ~/bash.sh
#!/bin/bash
bash --login
?
It works correctly for me, i.e. login shell is spawned.
bash-5.1$ $ cat ~/bash.sh
#!/bin/bash
bash --login
bash: $: command not found
I took a course in speed reading, learning to read straight down the middle
of the page, and I was able to go through "War and Peace" in twenty minutes.
It's about Russia.
-- Woody Allen
slacker@vslack:~$
I am at a loss why konsole refuses to open with a login shell prompt instead of showing bash-5.15...
Sounds like someone at KDE forums is yanking your chain.
The default behaviour of Konsole since the KDE 3.x days has been to not use a login shell. The developers of KDE have long held the view that the login shell is supposed to be the one that is run when you login, not every time you open a new terminal. Personally, I don't understand what the harm is.
Anyhow, the way I fix this is to do the following:
1. Drag the shortcut to Konsole from the menu to the desktop
2. Select "copy here"
3. Right click on the new icon
4. Select "Properties"
5. Select "Application" tab
6. Change the contents of the "Command:" box to: "konsole -e /bin/bash -l"
(without quotes)
You don't have to use bash, you can use zsh if you prefer.
Sounds like someone at KDE forums is yanking your chain.
The default behaviour of Konsole since the KDE 3.x days has been to not use a login shell. The developers of KDE have long held the view that the login shell is supposed to be the one that is run when you login, not every time you open a new terminal. Personally, I don't understand what the harm is.
Anyhow, the way I fix this is to do the following:
1. Drag the shortcut to Konsole from the menu to the desktop
2. Select "copy here"
3. Right click on the new icon
4. Select "Properties"
5. Select "Application" tab
6. Change the contents of the "Command:" box to: "konsole -e /bin/bash -l"
(without quotes)
You don't have to use bash, you can use zsh if you prefer.
Coming from someone who isn't on -current and not a Plamsa5 user (although, I imagine konsole itself is pretty similar)... You used to be able to change the command within the profile settings. This ensures that every time you launch konsole or open a new tab, that it uses a login shell. From my understanding reading these posts, this setting seems to still be there, but seems to be broken and isn't used when creating a new shell.
It sounds like your method is an alternative to getting something that has been supported within konsole's UI itself. Maybe it can be used until the issue in konsole is found and fixed.
Here's a picture showing the command option within the profile settings. It was found on this site under the "Change terminal shell" section.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008
Rep:
Quote:
Originally Posted by bassmadrigal
Coming from someone who isn't on -current and not a Plamsa5 user (although, I imagine konsole itself is pretty similar)... You used to be able to change the command within the profile settings. This ensures that every time you launch konsole or open a new tab, that it uses a login shell. From my understanding reading these posts, this setting seems to still be there, but seems to be broken and isn't used when creating a new shell.
It sounds like your method is an alternative to getting something that has been supported within konsole's UI itself. Maybe it can be used until the issue in konsole is found and fixed.
Here's a picture showing the command option within the profile settings. It was found on this site under the "Change terminal shell" section.
I agree, I don't think that konsole is broken. I have two systems one with Slackware-current (up-to-date) installed three years ago and konsole works. Second system (new machine) with Slackware-current (up-to-date) installed ~month ago and konsole works also.
In this case konsole opens bash, and the next step is non-interactive shell configuration which is determined in .bashrc.
Of course it may be a bug, but @Jeebizz is only one reporting it which makes it less plausible.
Sounds like someone at KDE forums is yanking your chain.
The default behaviour of Konsole since the KDE 3.x days has been to not use a login shell. The developers of KDE have long held the view that the login shell is supposed to be the one that is run when you login, not every time you open a new terminal. Personally, I don't understand what the harm is.
<snip>
I agree, I don't know why you'd want to change how someones shell is expected to work. I want a consistent prompt/shell every time whether I'm ssh'ing in or logged into the gui. This isn't a new battle though, gnome terminal on Solaris did the same thing and fixed it the same way. For some reason I don't remember having as many issues with CDE, but things were simpler then and my memory may be faulty.
I have even worse gripes about vim defaults being completely different from classic vi (when run as "vi"), but that's another scab I'd rather not pick right now. /rant
Last edited by fourtysixandtwo; 08-23-2021 at 07:27 AM.
Sounds like someone at KDE forums is yanking your chain.
The default behaviour of Konsole since the KDE 3.x days has been to not use a login shell. The developers of KDE have long held the view that the login shell is supposed to be the one that is run when you login, not every time you open a new terminal. Personally, I don't understand what the harm is.
Anyhow, the way I fix this is to do the following:
1. Drag the shortcut to Konsole from the menu to the desktop
2. Select "copy here"
3. Right click on the new icon
4. Select "Properties"
5. Select "Application" tab
6. Change the contents of the "Command:" box to: "konsole -e /bin/bash -l"
(without quotes)
You don't have to use bash, you can use zsh if you prefer.
Still seems too many hoops just to get a fscking shell the way I want it, and I get the feeling the KDE devs are going the GNOME route and deciding whats best for me. I'll revisit this issue perhaps another time (right now I'm just feeling too lazy to bother with this), in the mean time I can use an alternate terminal like xfce's terminal.. Fsck this.
Still seems too many hoops just to get a fscking shell the way I want it, and I get the feeling the KDE devs are going the GNOME route and deciding whats best for me. I'll revisit this issue perhaps another time (right now I'm just feeling too lazy to bother with this), in the mean time I can use an alternate terminal like xfce's terminal.. Fsck this.
Do you really want a login shell or just a proper PS1 prompt?
If the latter, just define PS1 and whatever other variables you want in ~/.bashrc, and maybe put in your ~/.bash_profile something like I have:
Code:
# if running bash
if [ -n "${BASH_VERSION}" ]; then
# include .bashrc if it exists
if [ -f "${HOME}/.bashrc" ]; then
. "${HOME}/.bashrc"
fi
fi
Do you really want a login shell or just a proper PS1 prompt?
If the latter, just define PS1 and whatever other variables you want in ~/.bashrc, and maybe put in your ~/.bash_profile something like I have:
Code:
# if running bash
if [ -n "${BASH_VERSION}" ]; then
# include .bashrc if it exists
if [ -f "${HOME}/.bashrc" ]; then
. "${HOME}/.bashrc"
fi
fi
It's not the cleanest but it's simple and works.
Cheers!
I don't know what is considered "proper" in the world of UNIX-like as each has their own version, I just want my user@host_name back , with the witty fortunes just like when you boot up Slackware and login - but seems the devs at KDE know better than I and I shouldn't have that option anymore.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.