I'm having a problem with ~/.profile and ~/.xprofile as well....
A user's ~/.profile or ~/.xprofile can set aliases or modify paths and
affect further execution of Xsession.
example:
--in run_parts() --
for F in $(ls $1); do
if expr "$F" : '[[:alnum:]_-]\+$' > /dev/null 2>&1; then
if [ -f "$1/$F" ]; then
echo "$1/$F"
--
but if a user has set in their ~/.profile
alias ls='ls -CF'
then run_parts() breaks.
In my example, gnome-power-manager complained about the dbus service because /etc/X11/Xsession.d/75dbus_dbus-launch never ran
I propose moving the the ~/.profile and ~/.xprofile stanza later in
the script. Although a better solution might be to path-qualify all
the shell commands.
I've attached the patch for the change that worked for me.
I'm having a problem with ~/.profile and ~/.xprofile as well....
A user's ~/.profile or ~/.xprofile can set aliases or modify paths and
affect further execution of Xsession.
example:
--in run_parts() --
for F in $(ls $1); do
if expr "$F" : '[[:alnum:]_-]\+$' > /dev/null 2>&1; then
if [ -f "$1/$F" ]; then
echo "$1/$F"
--
but if a user has set in their ~/.profile
alias ls='ls -CF'
then run_parts() breaks.
In my example, gnome-power-manager complained about the dbus service because /etc/X11/ Xsession. d/75dbus_ dbus-launch never ran
I propose moving the the ~/.profile and ~/.xprofile stanza later in
the script. Although a better solution might be to path-qualify all
the shell commands.
I've attached the patch for the change that worked for me.