In a fresh install of cauldron, using GDM as the DM and Plasma as the DE, invoking Konsole from the panel results in a shell with PS1 set to a null string. The use of "su -l" to any other userid including the same userid used to open Konsole gets the correct environment settings. $PS1 is normally set by /etc/bashrc, but even running ". /etc/bashrc" explicitly from the damaged shell doesn't change $PS1. I'll attach the results of "set" from the initial shell and from the correct su -l shell. The only time I've seen anything like this is years ago when scripts invoked from systemd service files got abbreviated environments compared to the login state of the userid being used. I was told this was deliberate, although I did not agree. Also, a logon on a getty tty gets the correct environment right off. I've never used GDM with Plasma. I'm only doing it now because SDDM doesn't work with Wayland, so that may be the root cause. Apparently, however Konsole creates the initial shell, it is doing it in a manner inconsistent with "su -l". As a workaround, you can make the first command issued "su -l (userid)".
Created attachment 12184 [details] "set" from damaged initial shell
Created attachment 12185 [details] "set" from am "su -l" session
Thanks for the report. Please always say explicitly what "a fresh install of cauldron" means: from which ISO, or NetInstall? And is the system up-to-date? Once again, on my own up-to-date M8/Cauldron system, what you describe does not happen - nor ever has, I imagine one would notice! Under Plasma (from LightDM), Konsole launched from its taskbar icon: [lewis@localhost ~]$ echo $PS1 [\u@\h \W]\$ without looking any further. But your attachments speak for themselves, so assigning this to KDE prople.
Assignee: bugsquad => kdeCC: (none) => lewyssmith
Sorry, all my fresh installs are network installs selectin Custom desktop and checking all the category boxes under Workstation, Server, and Graphical.
As a point of interest, this problem affects every terminal emulator I've tried (eterm, mrxvt) and not just Konsole.
CC: lewyssmith => (none)
Light at the end of the tunnel ! While testing alternate DMs for bug#28024, I've noticed that the behavior described here does *not* occur with lxdm, lightdm, or xdm. Because the behavior described in bug#28024 prevents me from signing on with SDDM (the userid and password fields are overlaid), I don't know whether this error occurs with SDDM. So, the problem appears to be GDM/Wayland in conjunction with an X-based DE.
New symptom: Desktop files which try to execute a shell script silently fail. If you set "Terminal=true" instead of "Terminal=false", you get a Konsole window with the error message: Warning: Could not find an interactive shell to start.
(In reply to Frank Griffin from comment #6) > Light at the end of the tunnel ! While testing alternate DMs for bug#28024, > I've noticed that the behavior described here does *not* occur with lxdm, > lightdm, or xdm. Because the behavior described in bug#28024 prevents me > from signing on with SDDM (the userid and password fields are overlaid), I > don't know whether this error occurs with SDDM. > > So, the problem appears to be GDM/Wayland in conjunction with an X-based DE. Adjusting the summary and CC'ing the Gnome maintainer group
CC: (none) => gnome, marja11, olavSummary: Konsole sessions open under Plasma with abbreviated environment variables => When logged in with GDM/Wayland, Konsole and all other terminal emulators open under Plasma with abbreviated environment variables
Summary: When logged in with GDM/Wayland, Konsole and all other terminal emulators open under Plasma with abbreviated environment variables => In Plasma, Konsole and all other terminal emulators open with abbreviated environment variables
This isn't a Gnome issue. Now that SDDM works, it happens there too.
This has suddenly stopped happening, so I guess it's been fixed.
Status: NEW => RESOLVEDResolution: (none) => FIXED