Bug 382351 - plasma launchers (alt-f2 or panel) log all stdout and stderr into .xsession-errors
Summary: plasma launchers (alt-f2 or panel) log all stdout and stderr into .xsession-e...
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.19.5
Platform: Debian testing Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-14 19:21 UTC by Alex
Modified: 2021-04-05 15:23 UTC (History)
4 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 Alex 2017-07-14 19:21:55 UTC
The plasma-desktop in debian testing(buster) (4:5.8.7.1-1) logs all stderr from programs started via the panel (icons-only-taskmanager) or the runner (alt-f2) to .xsession-errors, which grows to hundreds of megabytes depending on the program.

Steps to reproduce:
- create a small script*, place it in ~/bin/test.sh and chmod +x ~/bin/test.sh
- press alt-f2
- run "~/bin/test.sh"
- run tail ~/.xsession-errors in a terminal

Expected behaviour:
- output is discarded

Actual behaviour:
- All output is logged into the .xsession-errors file, which grows bigger and bigger

* Simplest testscript:
#!/bin/bash
echo test

See also: Bug 360757. Seems to be the same issue, but I think it is assigned to the wrong project.
Comment 1 Alexander Mentyu 2017-11-23 07:29:26 UTC
Cannot confirm this bug in:

Distribution: KDE neon Developer Edition - Stable Branches
Plasma: 5.11.3
Frameworks: 5.41.0
Qt: 5.9.1
Kernel 4.10.0-38-generic
Type: 64-bit
Comment 2 Alex 2017-11-23 07:42:46 UTC
Were there changes about this?

Can you try to reproduce some of the many ways this fails and check if its really gone? Its a common bug since at least 2010 with related forum posts from 2004, it would be that great when it's really solved.
https://www.google.com/search?q=plasma%20xsession-errors

I can test later with 5.10.5
Comment 3 Justin Zobel 2020-11-11 23:55:17 UTC
(In reply to Alexander Schier from comment #2)
> Were there changes about this?
> 
> Can you try to reproduce some of the many ways this fails and check if its
> really gone? Its a common bug since at least 2010 with related forum posts
> from 2004, it would be that great when it's really solved.
> https://www.google.com/search?q=plasma%20xsession-errors
> 
> I can test later with 5.10.5

Alexander were you able to test with a more recent version?

I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 4 Alex 2020-11-15 11:12:37 UTC
It still happens.

Steps to reproduce:

- For a clean start delete .xsession-errors and logout and login again.
- Press Alt-F2 and run "ls"
- .xsession-errors now contains the output of ls
Comment 5 Nate Graham 2021-03-21 03:32:12 UTC
I cannot reproduce on openSUSE Tumbleweed with Plasma 5.21.  However I have no .xsession-errors file at all and none ever seems to be created, so perhaps that is masking it.
Comment 6 Alex 2021-03-21 10:17:09 UTC
I currently cannot reproduce with Alt+F2, but I can reproduce the issue with programs pinned to the panel (panel icons and icons-only-taskbar).

Plasma 5.20.5, KF 5.78.0 on Debian Bullseye
Comment 7 Nate Graham 2021-03-21 11:11:20 UTC
Any chance you can upgrade to 5.21 and/or turn on systemd startup (`kwriteconfig5 --file startkderc --group General --key systemdBoot true`) and reboot and see if that helps?
Comment 8 Bug Janitor Service 2021-04-05 04:33:26 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 9 Alex 2021-04-05 10:51:51 UTC
Let's keep it open until I have time to test with latest plasma, bot.
Comment 10 Justin Zobel 2021-04-05 11:54:48 UTC
Sounds like this might be a downstream issue in Debian. I can't reproduce it on Solus Plasma either.
Comment 11 Alex 2021-04-05 12:03:29 UTC
Are there good backports of latest plasma for Debian?
It still does not seem to be in unstable and I would like to always run the latest version, not only for bugreports.
Comment 12 Nate Graham 2021-04-05 15:23:21 UTC
Since two of us cannot reproduce it in a newer version, let's keep it closed and re-open only if it's confirmed to still be broken for you.

I don't know how you can upgrade to the latest version in Debian, sorry.