| Summary: | trapd00r's .dir_colors crashes plasma shell | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | thedoogster |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | CC: | bshah, plasma-bugs-null, psychonaut |
| Priority: | NOR | ||
| Version First Reported In: | 5.4.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Slackware | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | The script that's executed (eval'd) and causes problems | ||
|
Description
thedoogster
2015-12-18 17:03:17 UTC
it's screwing up /usr/binstartkde which is a shell script and plasmashell isn't getting to be launched. Given it works normally, it's almost certainly your shell setup that's "broken" and not plasma. Please add some "echo" lines and see where it's breaking. Unfortunately I really don't have time to deal with every possible setup issue, so I won't spend time helping trying to fix this. Let me know if you find the cause and especially if you do "prove" that it's us doing something wrong. It *could* also be an env var so long that kdeinit can't copy it? Does this script affect your env vars at all? Created attachment 96222 [details]
The script that's executed (eval'd) and causes problems
The theory that this is caused by an environment variable so long that kdeinit can't copy it is likely. The variable would be LS_COLORS, and if you use this script before starting KDE, then the value of that variable is 7870 characters long.
Attached is the BASH code that actually gets eval'd.
I can reproduce this issue, and concur that long environment variables such as LS_COLORS seem to be the trigger. My .bashrc file exports a LS_COLORS variable that is 7869 bytes long. With KDE 4, this caused no problems. With KDE 5, the presence of this variable prevents me from logging in. I end up with a black screen that is unresponsive except for the mouse pointer, and my .xsession_errors contains the same "kdeinit5: Aborting. $DISPLAY is not set." error mentioned by the reporter. Removing the variable definition from .bashrc, or reducing its length, allows me to log in. Please consider reopening this bug report. An LS_COLORS variable of a few kilobytes is not particularly long, and not particularly uncommon. It should not lock up a desktop environment. Tested again today with Plasma 6.4.3 and the problem is no longer reproducible. |