[kde] [Bug 324243] Presence of ~/.kde/env/path.sh prevents log in to Linux Mint 15 KDE (64 bit)

[Rob Burness]

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

--- Comment #2 from Rob Burness <rcburness at gmail.com> ---
I made the following change to path.sh, placed it in /home/rob/.kde/env and
sourced $HOME/.kde/env/path.sh instead of $HOME/.kde_old/env/path.sh in my
.bashrc so ssh, konsole, and cron would have the paths and environment:

# Adding rcss directories so all machines in rcss have access to the same
settings:

|...+....1....+....2....+....3....+....4....+....5....+....6....+....7.]..+....8....+....9....+...10....+...11....+...12....+...13....+...14....+...15....+...16....+...17....+...18....+...19....+...20.
00007 #export
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:"$HOME"/Dropbox/shared_rcss_complex:/usr/local/share/rcss"
00008 export
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/share/rcss:"$HOME"/Dropbox/shared_rcss_complex"

The problem has gone away.  I simply moved /usr/local/share/rcss in front
of the $HOME/Dropbox/shared_rcss_complex directory.  After moving from LM
14 KDE to LM 15 KDE I had to copy /usr/local/share/rcss from 14's root to
15's root as the upgrade package had no way of knowing I was using
/usr/local/share.

It is difficult for me to see how changing the order of assignments in the
export PATH statement would enable me to now see the login screen.  I
wonder if something else got updated/fixed/or changed.

Anyway thank you for your help and suggestion.  I guess that fixed the
problem or someone fixed something somewhere else.  I have learned my
lesson about relying on just using /usr/local/... and now also use Dropbox
to have machines keep current and share common routines.


On Sat, Sep 14, 2013 at 10:55 AM, Jekyll Wu <adaptee at gmail.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=324243
>
> --- Comment #1 from Jekyll Wu <adaptee at gmail.com> ---
> Can't reproduce.
>
> The problem sounds highly related with some specific setup in your system.
> Please try doing some bisect by commenting parts of the file to isolate and
> identify the problematic part ( should be the $PATH line, I guess) and the
> problematic element in that line .
>
> --
> You are receiving this mail because:
> You reported the bug.
>

-- 
You are receiving this mail because:
You are the assignee for the bug.