Unwanted xscreensaver process spawned by startkde (KDE4)
Guys, this is really driving me nuts.
Running KDE4 on sid. When I log in, there are always an
xscreensaver and a ssh-agent instance running, even though I log in
into an empty session:
davide@macco:~$ ps aux | grep xscr
davide 1580 0.0 0.0 7272 820 pts/1 R+ 20:59 0:00 grep --colour=auto xscr
davide 3361 0.0 0.2 55196 2296 ? S 20:04 0:00 /usr/bin/xscreensaver -nosplash
davide@macco:~$ ps aux | grep ssh-
davide 2689 0.0 0.0 7272 820 pts/1 R+ 21:02 0:00 grep --colour=auto ssh-
davide 3377 0.0 0.0 36016 268 ? Ss 20:04 0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/startkde
I'm happy about ssh-agent, I just want to get rid of
xscreensaver and use kscreensaver alone. If I just kill the process, it
pops up again next time I log in. $KDEHOME/{Autostart,env} are empty.
Grepping .kde and /etc/kde for "ssh" or "xscre" doesn't return
anything. Oh, and according to pstree, both processes are spawned by
startkde:
davide@macco:~$ pstree | grep -C4 xscreensaver
| `-{ksmserver}
|-kdm-+-Xorg
| `-kdm---startkde-+-kwrapper4
| |-ssh-agent
| `-xscreensaver
|-kglobalaccel
|-klogd
|-kmix
|-knotify4---4*[{knotify4}]
Does anyone have any idea of how I can get rid of that *insert
expletive* xscreensaver at login?
Davide
--
Time flies like an arrow. Fruit flies like a banana.
--
If anything can go wrong it wSegmentation fault
core dumped
Reply to: