Unwanted xscreensaver process spawned by startkde (KDE4)

2009-10-20 Thread Davide Mancusi
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:

dav...@macco:~$ ps aux | grep xscr
davide1580  0.0  0.0   7272   820 pts/1R+   20:59   0:00 grep 
--colour=auto xscr
davide3361  0.0  0.2  55196  2296 ?S20:04   0:00 
/usr/bin/xscreensaver -nosplash
dav...@macco:~$ ps aux | grep ssh-
davide2689  0.0  0.0   7272   820 pts/1R+   21:02   0:00 grep 
--colour=auto ssh-
davide3377  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:

dav...@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


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: gdm, kdm, xdm can't startkde

2005-09-17 Thread Mr Mike
On Fri, 16 Sep 2005 17:37:46 +0200, Jonathan Kaye wrote:

 Hi people,
 This one's driving me crazy. I'm running Debian Etch 2.6.8-2-386 and
 recently upgraded from xfree86 to xorg. Everything is fine except this
 one problem. I can't start kde (my desktop of preference nor gnome nor xfce
 from any display manager. Say I'm using gdm. I boot up and the gdm screen
 comes on as usual and I login normally but instead of going into kde (or
 gnome or xfce) an xterm opens. I can then enter (as me, not root)
 startkde and everything is fine after that. I've read about similar 
 problems dating as far back as 2001 but none of the solutions I've tried
 has helped. My .xsession-errors file gives me this:
 
 /etc/gdm/Xsession: Beginning session setup...
 /etc/gdm/Xsession: Executing /usr/bin/startkde failed, will try to run
 x-terminal-emulator
 
 which is not very helpful. It doesn't tell me WHY startkde failed. I've
 checked in various /var/log's but nothing revealing has appeared.
 
 If I use kdm I get into an infinite loop. Selecting kde and logging in just
 takes you right back to the login window and round and round we go.
 
Actually, it does tell you..  It is saying it can't find the startkde
script in /usr/bin.  At the command line type which startkde and it will
tell you what directory it is located in..  My guess is maybe /opt/kde/bin
or maybe some other 'not so usual' directory...  then in
/usr/share/xsessons, edit the kde.desktop file and change the 'exec' and
'try exec' lines to the correct path to your startkde script..

mr mike..



 Judging from looking at similar problems reported in various lists,
 these symptoms can come from a variety of causes. Any help here would be
 greatly appreciated.
 Cheers,
 Jonathan



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: gdm, kdm, xdm can't startkde

2005-09-17 Thread Jonathan Kaye
Mr Mike wrote:


 Actually, it does tell you..  It is saying it can't find the startkde
 script in /usr/bin.  At the command line type which startkde and it will
 tell you what directory it is located in..  My guess is maybe /opt/kde/bin
 or maybe some other 'not so usual' directory...  then in
 /usr/share/xsessons, edit the kde.desktop file and change the 'exec' and
 'try exec' lines to the correct path to your startkde script..
 
 mr mike..

Actually, it doesn't because startkde is in /usr/bin:
[EMAIL PROTECTED]:~$ whereis startkde
startkde: /usr/bin/startkde
[EMAIL PROTECTED]:~$ locate startkde
/usr/bin/startkde

thanks for trying,
Jonathan



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



gdm, kdm, xdm can't startkde

2005-09-16 Thread Jonathan Kaye
Hi people,
This one's driving me crazy. I'm running Debian Etch 2.6.8-2-386 and
recently upgraded from xfree86 to xorg. Everything is fine except this
one problem. I can't start kde (my desktop of preference nor gnome nor xfce
from any display manager. Say I'm using gdm. I boot up and the gdm screen
comes on as usual and I login normally but instead of going into kde (or
gnome or xfce) an xterm opens. I can then enter (as me, not root)
startkde and everything is fine after that. I've read about similar 
problems dating as far back as 2001 but none of the solutions I've tried
has helped. My .xsession-errors file gives me this:

/etc/gdm/Xsession: Beginning session setup...
/etc/gdm/Xsession: Executing /usr/bin/startkde failed, will try to run
x-terminal-emulator

which is not very helpful. It doesn't tell me WHY startkde failed. I've
checked in various /var/log's but nothing revealing has appeared.

If I use kdm I get into an infinite loop. Selecting kde and logging in just
takes you right back to the login window and round and round we go.

Judging from looking at similar problems reported in various lists, these
symptoms can come from a variety of causes. Any help here would be greatly
appreciated.
Cheers,
Jonathan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



startkde fehler nach woody update auf kde 3.1.4

2003-10-10 Thread Lutz Kittler
Hi,

ich habe auf 2 Rechnern ein kde update von 3.1.3 auf 3.1.4
unter woody gemacht.
Auf einem Rechner gibt es keine Problem, beim zweiten erfolgt
Fehlerabbruch bei startkde.
Ich habe schon mal in den Listen gesucht und nur gefunden,
dass man alle relevanten Files in /tmp und ~/.kde loeschen
soll. Aber auch wenn ich die Files alle loesche passiert genau
dasselbe.
Einige kdeinit-Prozesse ueberleben den Absturz.
Ich habe einige Files, Directorylistings und einen Teil
von ps -ax angehaengt.
Auffaellig für mich ist nur, dass auf dem Rechner, wo startkde
abstürzt das sticky-Bit bei /tmp/.ICE-unix fehlt.

Hat jemand eine Idee was da passiert und was ich tun könnte ?
Wie kann man ein ausführlicheres Protokoll von startkde in
den .xsession-errors erhalten ?

# cat .xsession-errors
startkde: Starting up...
iceauth:  creating new authority file /home/lutz/.ICEauthority
kbuildsycoca running...
kdeinit: Pipe closed unexpectedly: No such file or directory

#ps ax
 1117 ?S  0:00 /usr/bin/kdm
 1193 ?S  0:00 kdeinit: Running...  
 1196 ?S  0:00 kdeinit: dcopserver --nosid
 1199 ?S  0:00 kdeinit: klauncher   
 2458 ?S  0:02 /etc/X11/X -dpi 75 vt7 -auth 
/var/lib/kdm/A:0-PjtgI9
 2459 ?S  0:00 -:0 
 2463 ?S  0:00 /usr/bin/kdm_greet


#ls -alt /tmp
total 40
drwxrwxrwt8 root root 4096 Okt  9 19:33 .
drwx--3 root root 4096 Okt  9 19:33 0997337040
-r--r--r--1 root root   11 Okt  9 19:33 .X0-lock
drwxrwxrwt2 root root 4096 Okt  9 19:33 .X11-unix
drwx--2 lutz software 4096 Okt  9 19:33 kde-lutz
drwxrwxrwx2 lutz software 4096 Okt  9 19:32 .ICE-unix
drwx--2 lutz software 4096 Okt  9 19:32 ksocket-lutz
drwxrwxrwt2 root root 4096 Okt  9 19:32 .font-unix
drwxr-xr-x   35 root root 4096 Jul 16 19:56 ..

/tmp/0997337040:
total 12
drwxrwxrwt   12 root root 4096 Okt  9 20:28 ..
drwx--3 root root 4096 Okt  9 19:33 .
drwx--2 root root 4096 Okt  9 19:33 .qt

/tmp/0997337040/.qt:
total 16
-rw-r--r--1 root root 1227 Okt  9 19:33 qt_plugins_3.1rc
drwx--2 root root 4096 Okt  9 19:33 .
drwx--3 root root 4096 Okt  9 19:33 ..
-rw---1 root root0 Okt  9 19:33 .qt_plugins_3.1rc.lock
-rw-r--r--1 root root   22 Okt  9 19:33 qtrc
-rw---1 root root0 Okt  9 19:33 .qtrc.lock

/tmp/kde-lutz:
total 708
drwxrwxrwt   12 root root 4096 Okt  9 20:28 ..
drwx--2 lutz software 4096 Okt  9 19:33 .
-rw-r--r--1 lutz software   705684 Okt  9 19:33 ksycoca
-rw-r--r--1 lutz software  484 Okt  9 19:33 ksycocastamp

/tmp/ksocket-lutz:
total 8
drwxrwxrwt   12 root root 4096 Okt  9 20:28 ..
drwx--2 lutz software 4096 Okt  9 19:32 .
srwxr-xr-x1 lutz software0 Okt  9 19:32 
klauncherRn2Vjc.slave-socket
srw---1 lutz software0 Okt  9 19:32 kdeinit-:0

/tmp/.font-unix:
total 8
drwxrwxrwt   12 root root 4096 Okt  9 20:28 ..
drwxrwxrwt2 root root 4096 Okt  9 19:32 .

/tmp/.ICE-unix:
total 8
drwxrwxrwt   12 root root 4096 Okt  9 19:32 ..
drwxrwxrwx2 lutz software 4096 Okt  9 19:32 .
srwxrwxrwx1 lutz software0 Okt  9 19:32 dcop1196-1065720777


#ls -alt ~lutz
-rw---1 lutz software  173 Oct  9 19:33 .xsession-errors
-rw---1 lutz software0 Oct  9 19:33 .Xauthority
-rw-r--r--1 lutz software 1166 Oct  9 19:33 .gtkrc-kde
-rw-r--r--1 lutz software   59 Oct  9 19:32 
.DCOPserver_debian-e6530__0
lrwxrwxrwx1 lutz software   38 Oct  9 19:32 
.DCOPserver_debian-e6530_:0
 - /home/lutz/.DCOPserver_debian-e6530__0
-rw---1 lutz software  201 Oct  9 19:32 .ICEauthority
drwx--4 lutz software 4096 Oct  9 19:32 .kde
-rw-r--r--1 lutz software8 Oct  9 19:32 .wmrc

#ls -alt ~lutz/.kde
  drwx--2 lutz software 4096 Sep  2  2002 Autostart
  drwx--   12 lutz software 4096 Feb 11  2003 share
  lrwxrwxrwx1 lutz software   17 Oct  9 19:32 socket-debian-e6530 
- /tmp/ksocket-lutz
  lrwxrwxrwx1 lutz software   13 Oct  9 19:32 tmp-debian-e6530 - 
/tmp/kde-lutz


Danke im Voraus

Lutz




-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)



Re: startkde fehler nach woody update auf kde 3.1.4

2003-10-10 Thread Uwe Kerstan
* Lutz Kittler [EMAIL PROTECTED] [10-10-2003 13:44]:

 Ich habe schon mal in den Listen gesucht und nur gefunden,
 dass man alle relevanten Files in /tmp und ~/.kde loeschen
 soll.

~/.qt, ~/.mcop, ~/.mcoprc, /tmp/ksocket-*, /tmp/kde-*, 
~/.DCOPserver* und ~/.MCOP-random-seed löschen.
~/.kde, ~/.kderc und ~/.gtkrc-kde eventuell sichern.

Gruss Uwe


pgp0.pgp
Description: PGP signature


Starting KDE with startx (was: Re: startkde)

2000-12-01 Thread Rogerio Brito
On Nov 28 2000, Robert Epprecht wrote:
 Sorry, but I must ask again: 
 How do I have KDE2 and Gnome on a potato system and start either or? 

To start KDE, just put exec startkde in your personal
~/.xsession file. To start GNOME, put exec gnome-session.
This way, you can choose which one you'd like in a given
day. :-)


[]s, Roger...

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
  Rogerio Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



Re: startkde

2000-11-30 Thread Robert Epprecht
Josh McKinney [EMAIL PROTECTED] writes:

 You need to have X started to run KDE.

Ah, I see (thought 'startkde' would do that )

  You can edit your /etc/X11/xinit/xinitrc file, at the bottom it will have 
 the stuff about starting gnome probably, you can just comment out the gnome 
 part and put 'exec startkde'

Hmm, sounds easy, but I must confess to my shame, that I do not quite under-
stand how it is working. 
/etc/X11/xinit/xinitrc just does '. /etc/X11/Xsession' I do not understand
this X stuff well enough (and aren't fluent in bash syntax either) and
couldn't even find out, how Xsession finds out to start gnome...

While I can start gnome with 'startx' the only way I found to start KDE2
is to give startx a nonsense parameter ('startx nonsense'), which gives
me a X session with grey dotted background and a kind of terminal 'window'
where I can type 'startkde'. Still this does not look right ;-) (and the
KDE session can only be terminated by CTRL+ALT+BACKSPACE)

Sorry, but I must ask again: 
How do I have KDE2 and Gnome on a potato system and start either or? 

Thank you for your help,
Robert Epprecht.



Re: startkde

2000-11-30 Thread David Bellows
Hello,

 Sorry, but I must ask again:
 How do I have KDE2 and Gnome on a potato system and start either or?
 

to get KDE I type this whole line:
startx startkde

for Gnome I type:
startx gnome-session

Good luck,
David Bellows



startkde

2000-11-22 Thread Robert Epprecht
Hello,

I have installed KDE2 on my potato system from kde.tdyc.com
I want to have both, Gnome and KDE2. Gnome works as it should.

If I do 'startkede' I get:
   xsetroot:  unable to open display ''

So I set DISPLAY to ':0' and try again:
   _X11TransSocketUNIXConnect: Can't connect: errno = 111
   xsetroot:  unable to open display ':0'
   [ ... many more ]

I tried: 'DISPLAY=localhost:0' but only get a lot of lines saying
  _X11TransSocketINETConnect: Can't connect: errno = 111

What did I miss?

Thanks a lot for help,
Robert Epprecht.



Re: startkde

2000-11-22 Thread Josh McKinney
You need to have X started to run KDE.  You can edit your 
/etc/X11/xinit/xinitrc file, at the bottom it will have the stuff about 
starting gnome probably, you can just comment out the gnome part and put 'exec 
startkde'

On approximately Wed, Nov 22, 2000 at 09:28:36AM +0100, Robert Epprecht wrote:
 Hello,
 
 I have installed KDE2 on my potato system from kde.tdyc.com
 I want to have both, Gnome and KDE2. Gnome works as it should.
 
 If I do 'startkede' I get:
xsetroot:  unable to open display ''
 
 So I set DISPLAY to ':0' and try again:
_X11TransSocketUNIXConnect: Can't connect: errno = 111
xsetroot:  unable to open display ':0'
[ ... many more ]
 
 I tried: 'DISPLAY=localhost:0' but only get a lot of lines saying
   _X11TransSocketINETConnect: Can't connect: errno = 111
 
 What did I miss?
 
 Thanks a lot for help,
 Robert Epprecht.
 
 
 -- 
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null



Re: KDE1.1: startkde?

1999-07-06 Thread Mark Brown
On Tue, Jul 06, 1999 at 12:30:11AM +0200, Attila Csosz wrote:

 I've installed KDE 1.1 but I've a symlink to a nonexistant file. It's a bug?

 lrwxrwxrwx   1 root root   28 JÚL  5 21:15 
 /usr/X11R6/bin/startkde - debian/tmp/usr/X11R6/bin/kde

 Currently I use 'kde' instead of 'startkde'.

Yes - it's a bug (the symlink points into the build tree - the
maintainer needs to make sure that all symlinks within debian/tmp are
relative to debian/tmp and not the root of the build tree).

Broken symlinks in packages are almost always bugs, even if it's just a
missing dependancy.

-- 
Mark Brown  mailto:[EMAIL PROTECTED]   (Trying to avoid grumpiness)
http://www.tardis.ed.ac.uk/~broonie/
EUFShttp://www.eusa.ed.ac.uk/societies/filmsoc/


pgp3VEyj01gKW.pgp
Description: PGP signature


KDE1.1: startkde?

1999-07-05 Thread Attila Csosz
I've installed KDE 1.1 but I've a symlink to a nonexistant file. It's a bug?

lrwxrwxrwx   1 root root   28 JÚL  5 21:15 /usr/X11R6/bin/startkde 
- debian/tmp/usr/X11R6/bin/kde

Currently I use 'kde' instead of 'startkde'.

Thanks
 Attila

 
-- 
---
- Debian 2.1 Linux  / 2.2.9 / qmail   -
- Mail: [EMAIL PROTECTED]-


Re: startkde cannot connect to X server

1998-11-19 Thread Rainer Clasen
Hi!

Stephan Böni ([EMAIL PROTECTED]):
 i have installed kde on debian linux 2.0.
 commands like startx or startkde return the error cannot connect to x
 server.
 what's wrong?

If running startx says cannot connect to xserver this usually indicates
that your Xserver isn't configured properly. Install doc-linux-text and read
/usr/doc/HOWTO/XFree86-HOWTO.gz and /usr/doc/X11/* . *THEN* run either
XF86Setup or xf86config to configure your xserver.

startkde is run within X. see /usr/doc/kdebase/README.Debian.

Rainer

-- 
KeyID=58341901 fingerprint=A5 57 04 B3 69 88 A1 FB  78 1D B5 64 E0 BF 72 EB


pgpdjXQTFqSmX.pgp
Description: PGP signature


startkde cannot connect to X server

1998-11-18 Thread Stephan Böni




Hi

i have 
installed kde on debian linux 2.0.
commands like startx or startkde return the error cannot connect to 
x server.
what's 
wrong?

steph