Comment # 15 on bug 1004769 from Christian Herenz

(In reply to Wolfgang Bauer from comment #13)
> (In reply to Christian Herenz from comment #11)
> > I am using also anaconda, and this bug forces me (and other potential users)
> > to manually (or via a script) to edit the .bashrc file after login and
> > before log-out.
> 
> You don't have to edit .bashrc though.
> Just set the paths in a start script for anaconda.
> 

Which I would do in my .bashrc, as I want anaconda in every interactive shell.

> > On a side-note:
> > Why does startkde care about my paths in .bashrc at all?
> 
> Because the paths set in .bashrc affect *any* program run in the user
> session.

.bashrc should affect only interactive shells.  Thus, imho,  startkde should
spawn in a non-interactive shell and not execute anything in .bashrc.  I see
that in opensuse /etc/profile sources ${HOME}/.bashrc - but, for example, they
don't do that in debian.  I always thought that the standard logic is to source
~/.profile  in non-interactive shells, where the user has the choice to specify
whether he wants (or not) his .bashrc to be sourced or not.


> Messing with the paths in .bashrc might cause other problems though, like
> applications trying to load different/incompatible versions of Qt libraries.
> 

When those applications are loaded from an interactive shell, I agree, this
might happen. 

> What openSUSE version are you actually using?

42.3

> > additionally, see the 
> > anaconda bugtracker - where they blame it on KDE:
> > https://github.com/ContinuumIO/anaconda-issues/issues/1206
> 
> And in another openSUSE forum thread, GNOME fails to start.
> https://forums.opensuse.org/showthread.php/528969-Unable-to-log-in-after-
> installing-anaconda
> 
> Would you/they blame that on KDE too?

I don't blame it on kde, rather on the way opensuse uses the ${HOME}/.bashrc  -
which seems to be a bit unorthodox.