With that new user you have freedom to experiment.
First just to triple check what should definitely be true:
rm -rf /home/newuser/* rm -rf /home/newuser/.* cp /home/normaluser/.xinitrc /home/newuser/.xinitrc
Then restart x, thunar terminal and firefox should definitely not be there anymore. Reopen them(1), restart X, they probably will be. Then
find /home/newuser/
and you have your suspect list.
You could probably make this even a little more precise with inotify, but the results of that find command should be quite a short list anyhow, and the problematic file will definitely be in the list.
1) I'd suggest just reopening terminal and not the others. Both thunar and firefox can each create a boatload of config and cache files on their first run in a fresh user. Terminal will create some, but far fewer.
Thanks for all your helpful suggestions. As it turns out, I was wrong. When testing with the new user, I accidentally left the checkbox checked when logging out and so my session was saved intentionally. So I cannot reproduce the problem with a new user.
I'm happy to try some more stuff - maybe I could copy over some files from my existing user to the new one? I'm just not sure where to start looking.
You have to make this directory readonly (chmod 444), otherwise it gets filled with session files again and again.
Nevertheless if you remove them or not.
Thanks for the tip, but I'd rather figure out what's causing this than treat a symptom. Making that directory read-only strikes me as a very hacky workaround.
]]>Trilby wrote:EDIT: also, unless I missed it, there's a lot of talk of looking in ~/.config, but xfce's session cache is stored (appropriately so) in ~/.cache
I tried trashing everything in ~/.cache/sessions, still no luck.
You have to make this directory readonly (chmod 444), otherwise it gets filled with session files again and again.
Nevertheless if you remove them or not.
First just to triple check what should definitely be true:
rm -rf /home/newuser/*
rm -rf /home/newuser/.*
cp /home/normaluser/.xinitrc /home/newuser/.xinitrc
Then restart x, thunar terminal and firefox should definitely not be there anymore. Reopen them(1), restart X, they probably will be. Then
find /home/newuser/
and you have your suspect list.
You could probably make this even a little more precise with inotify, but the results of that find command should be quite a short list anyhow, and the problematic file will definitely be in the list.
1) I'd suggest just reopening terminal and not the others. Both thunar and firefox can each create a boatload of config and cache files on their first run in a fresh user. Terminal will create some, but far fewer.
]]>See if it happens with a different user
It does indeed. I just created a completely fresh user. The only thing I copied over was my .xinitrc:
#!/bin/sh
# Source scripts in /etc/X11/xinit/xinitrc.d/
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
setxkbmap -option compose:rwin
exec startxfce4
Opened Thunar, Terminal, and Firefox as the new user, and all three of them showed up again after a reboot.
]]>EDIT: also, unless I missed it, there's a lot of talk of looking in ~/.config, but xfce's session cache is stored (appropriately so) in ~/.cache
I tried trashing everything in ~/.cache/sessions, still no luck.
GVim has now also decided to show up on boot, which is new as of today.
Checked ~/.config/autostart and /etc/xdg/autostart, and it looks like what's in there is what I would expect to be in there - programs I've actually requested to have autostart.
]]>https://bbs.archlinux.org/viewtopic.php?id=164354
Workaround is in the last post, works fine for me now.
You can get the link to a post from the date above the specific post
https://bbs.archlinux.org/viewtopic.php … 5#p1285385
Also, people with this problem, try and make a new clean user and see if the problem persists (this seems to be my advice for so many threads now)
]]>Workaround is in the last post, works fine for me now.
]]>grep -r firefox ~/.cache ~/.config ~/.local
EDIT: also, unless I missed it, there's a lot of talk of looking in ~/.config, but xfce's session cache is stored (appropriately so) in ~/.cache
]]>youngian wrote:start xfce4 with this in my ~/.xinitrc:
exec startxfce4
That is what I was fishing for. I assume, then, you are not starting any of the offending applications in there.
Purging the config files seems to have worked for this reboot. I'll see if the problem reoccurs on future reboots.
Cool; standing by...
Still does not work for me. I even did a link
xfce4-session -> /dev/null
in .config - nothing! The way xfce is started is exactly the same in my case. Could it be important that I use the LXDM as my display manager?
]]>start xfce4 with this in my ~/.xinitrc:
exec startxfce4
That is what I was fishing for. I assume, then, you are not starting any of the offending applications in there.
Purging the config files seems to have worked for this reboot. I'll see if the problem reoccurs on future reboots.
Cool; standing by...
]]>Also, purge all of the files in ~/.config/xfce4-session/.
Edit: And how do you start xfce4?
I start xfce4 with this in my ~/.xinitrc:
exec startxfce4
Purging the config files seems to have worked for this reboot. I'll see if the problem reoccurs on future reboots.
]]>