Arch Linux

dienadel

Member

Registered: 2005-12-23

Posts: 179

Can't start KDE

Hello!

This is a very extrange problem, and this is the 4th time that happens. I can't reproduce it, because, sometimes it has happen in a fresh install, and another after a few days.

The problem is that i can't enter in KDE. It stops in the second step (inicialating services...), and don't pass to the 3rd step. Here is information:

Type "startx" from console 1. X starts ok, and, as said, KDE stops in the second step, as waiting for something.. In the console output, this is the only thing:
startkde: starting up...

After a minute moreless, the "KDE startup theme" disapears, but the console output doesn't change.
I kill "KDE" by Ctrl+Alt+Supr, and, the console output is:

kdeinit: Fatal IO error: client killed
   "   : sending SIGHUP  to children
klauncher :  Exiting on signal 1
DCOP aborting while waiting  for answer from "kded"
kdeinit: Sending SINGTERM to children
kdeinit: Exit.
xinit:  connection to X server lost
Colgar (hangup)
GOT SIGHUP
<<system promp>> startkde : shutting down...
Warning : connect() failed : No such file or directory
Error: Can't connect kdeinit!

<<Until here, kded process exists>>
<<<After 2-3 minutes these new messages appear>>:

kded: Fatal IO error client killed
startkde: Running shutdown scripts...
startkde : Done.

<<At this moment, no kded process in top output>>

<<there is noy system promp, but with "enter" it appears>>

In the logs, the only error is in kdm.log:

QSettings: error creating /tmp/0122279125/.qt
QSettings: failed to open file '/tmp/0122279125/.qt/qt_plugins_3.3rc'
QSettings::sync: filename is null/empty
QSettings: error creating /tmp/0122279125/.qt
QSettings: failed to open file '/tmp/0122279125/.qt/qt_plugins_3.3rc'
QSettings::sync: filename is null/empty
QSettings: error creating /tmp/0122279125/.qt
QSettings: failed to open file '/tmp/0122279125/.qt/qt_plugins_3.3rc'
QSettings::sync: filename is null/empty

This happens with a new created user, and with all the users of the system.
The problem is only with KDE, no with X, as windowmaker (for example) works perfect.

I don't know. Where can be the solution, or, at least, a direction where to see???? If more infomation neede, please, ak me. I use only KDE, and i can't use arch with this type of "thing".

A lot of Thanks!

dienadel

pikass

Member

From: Schwartz space

Registered: 2005-11-28

Posts: 85

Re: Can't start KDE

Include the new installation a new .kde folder? Maybe just some kind of misconfiguration or non compatibility. Did you try to move your .kde folder? ( if you dont have a new one)

dienadel

Member

Registered: 2005-12-23

Posts: 179

Re: Can't start KDE

Everything is normal, as it would be.

I've finish to make a new instalation of Arch. This time, in the first try to enter kde, the problem has appear.

But, Until now, i've never can to solve this. Except this time! i can't say a lot, as it has happen a few minutes ago, and, i don't really know if is related, as is the first time i make this, so i can't say if this would solve the previous times error.

Well, i've stop iptables, and i can enter in KDE!!!
I log out KDE, start again KDE, and the same error. Shutdown X, stop iptables, and can enter KDE!!!

More, with iptables up, i've enter KDE. The same error, stopped in step 2. Gone to another console (without killing KDE) and stop iptables. Return to the initial console and, yes! step 3, step 4... and, inside KDE!!!

So, the problem is with iptables.rules. Here they are:

*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -i eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT
COMMIT

Any comment?

Thanks

Dienadel

dojo

Member

Registered: 2005-11-02

Posts: 97

Re: Can't start KDE

You should permit input to the lo-Interface.

Greets

Sunnemer

badran

Member

Registered: 2007-01-29

Posts: 3

Re: Can't start KDE

I added
iptable -A INPUT -i lo -j ACCEPT

to my firewall script... at /etc/ppp/firewall-standalone

and it is working

Last edited by badran (2007-01-29 09:22:09)