[konsole] [Bug 519979] Empty "Command" field in profile triggers "Could not find" warning instead of resolving the user's login shell via getpwuid()

https://bugs.kde.org/show_bug.cgi?id=519979

vindicator <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #1 from vindicator <[email protected]> ---
I'll jump in here as I've also just experienced this issue myself.
I was conversing with googAI, walking through the issue and found `Command` was
set to use bash (probably me at some point?), when the desire was just to let
`$SHELL` be used.

Only if the `shell` in `/etc/passwd` is not set should a warning come up if
`Command` is left blank. If it's blank, it should reasonably be assumed that
`$SHELL` should be used.

I was going to set it to `$SHELL` now, but then realized I was already logged
in, so it'd use the `shell` that was previously set in `/etc/passwd` before I
changed it. (I'm surprised this issue/report is as new as it is)

So I do think it'd be nice if the `/etc/passwd` would be checked instead of
just the `$SHELL` variable, so one doesn't need to log out/in for the `usermod`
change to go into effect.

Fallback/Preference order:
Konsole "Command" parameter
$SHELL (compared with "shell" value in "/etc/passwd")
/usr/bin/sh
/bin/sh
{/usr/bin,/bin}/{variety,of,shells,hardcoded}

-- 
You are receiving this mail because:
You are watching all bug changes.