Bug 417115 - Apps launched with "Run in terminal" not working under wayland
Summary: Apps launched with "Run in terminal" not working under wayland
Status: RESOLVED DUPLICATE of bug 408497
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-wayland (show other bugs)
Version: 5.17.5
Platform: unspecified Linux
: NOR major
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-03 19:03 UTC by Johann Höchtl
Modified: 2020-02-24 16:55 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johann Höchtl 2020-02-03 19:03:21 UTC
SUMMARY

When starting vim from Kicker under wayland, nothing happens.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT
vim (and likely any other application with "Run in terminal" option set) opens within terminal application

Linux/KDE Plasma: 
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.0

ADDITIONAL INFORMATION
Works in Plasma on X
Comment 1 Johann Höchtl 2020-02-05 19:13:57 UTC
I think the titel should be changed as the problem is actually a more fundamental one (I think)

Wayland plasma seems to be spawned without using a shell at at all. As such some important environment variables get not set.

The way to go seems to be to define user environment variables in ~/.config/environment.d/<name>.conf

systemctl --user show-environment will output environment variables configured there, cf. https://github.com/systemd/systemd/pull/5131
Comment 2 David Edmundson 2020-02-09 15:44:44 UTC
I don't think I understand.

What env vars are missing and where are they defined when you run on X?
Comment 3 Johann Höchtl 2020-02-09 16:00:38 UTC
The problem I have originally reported is that when I am running plasma under wayland, a menu entry for neovim is set to [x] Run in terminal. This does not work, as no terminal is opened.

This works when running under X

My suspicion is, that for this to work, environment variables are required to be set? I only noticed that none of the environment variables set eg. in .profiles or .bashrc are available to programs started from the KDE start menu because the way the kwin_wayland user session is spawned, does not require a login shell.

And maybe this is the reason too that the [ ] Run in terminal option does not work?
Comment 4 Patrick Silva 2020-02-09 17:05:28 UTC
Same problem with htop, see bug 408497
Comment 5 Bug Janitor Service 2020-02-24 04:33:11 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Johann Höchtl 2020-02-24 14:34:37 UTC
So this is very likely a duplicate of #408497

I cannot add more specifics. My suspicion for the bug I described is that the command shell used to display console programs when running under X is set in places which are not read when running under Wayland.

This is just an assumption.
Comment 7 Nate Graham 2020-02-24 16:55:08 UTC

*** This bug has been marked as a duplicate of bug 408497 ***