[plasmashell] [Bug 356883] trapd00r's .dir_colors crashes plasma shell

[Tristan Miller via KDE Bugzilla]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

--- Comment #3 from Tristan Miller  ---
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.

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

[plasmashell] [Bug 356883] trapd00r's .dir_colors crashes plasma shell

[via KDE Bugzilla]

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

--- Comment #2 from thedoogs...@gmail.com ---
Created attachment 96222
  --> https://bugs.kde.org/attachment.cgi?id=96222=edit
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.

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

[plasmashell] [Bug 356883] trapd00r's .dir_colors crashes plasma shell

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from David Edmundson  ---
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?

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

[plasmashell] [Bug 356883] trapd00r's .dir_colors crashes plasma shell

[via KDE Bugzilla]

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

thedoogs...@gmail.com changed:

   What|Removed |Added

   Platform|Other   |Slackware Packages

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