You are not logged in.
This is what I have in kwinrc
[$Version]
update_info=kwin3_plugin.upd:kde3.2,kwin.upd:kde3.0r1,kwin.upd:kde3.2Xinerama,kwin_focus1.upd:kwin_focus1,kwin_focus2.upd:kwin_focus2,kwin_on_off.upd:kwin_on_off
[Desktops]
Name_1=
Name_2=
Name_3=
Name_4=
Number=4
No OpenGL stuff
Offline
Are you sure you're looking at your .kde4 folder?? my kwinrc file is huge...
Offline
Are you sure you're looking at your .kde4 folder?? my kwinrc file is huge...
yep,, 120% sure..
Offline
Had a problem with kde4 upgrade which was a first for me...prevented me from log-in as root.
Solved the problem in ..../usr/share/config/kdm/kdmrc.....file which is huge!!!!
Many options therein.
Perhaps this is included in your upgrade altho kdemod may not have same.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Were you using KDE3 before? It may be compatibility problem with your configuration files.
First, try creating new system user and run KDE as this user. If you succeed, you need to remove all KDE configuration files from your home directory.
Offline
I tried with a new user, but the same error there too. So it seems it is a systemwide problem.
@lilsirecho, what u did with the file you mentioned.
I tried with starting kdemod from kdm as well as startx, both have the same problem. Moreover, in kde4 too I get the same problem.
Offline
I located ....allowrootlogin.... and set it to true.
You may have a conflict between kdecommon and the newer kde4 format which is supposed to delete kde common.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
DId change allowrootlogin to true, but to no avail, getting same error.
One more thing, In the "session type" of kdm, I'm not able to see "pekwm" which I'm using right now and there is one option "MWM" in which I can login but dont know how to use it.
Moreover, when I tried to install amarok and k3b, they asked for kdelibs3 and qt3 even though kdemod versions of those packages were already installed.!!!
Offline
same here. since today I cannot log in to KDE4 from [extra] anymore. kdm loads fine and I can log in to gnome / xfce / openbox from KDM but KDE or KDE-failsafe just drop me back to KDM after loading halfway through. new user did not help, reinstalling KDE4 did not help and cannot see anything too weird in /var/log/*
also tried disabling desktop effects and logging in as root both to no avail. dbus and hal are started just fine.
hope we can get this solved some time soon.
stefan
"root# su - bofh"
OS: F10_x64, Arch, Centos5.3, RHEL4.7, RHEL5.3
Desktop Hardware: Dell Precision M65 laptop, core2duo, 2gb, 80gb 7200rpm
Registered linux user #459910 since 1998
Offline
the last change in my kde packages before this issue started seem to have been an upgrade of kdebase from 4.1.1-1 to 4.1.1-2 on 6 sept 2008
stefan
"root# su - bofh"
OS: F10_x64, Arch, Centos5.3, RHEL4.7, RHEL5.3
Desktop Hardware: Dell Precision M65 laptop, core2duo, 2gb, 80gb 7200rpm
Registered linux user #459910 since 1998
Offline
well i tried defaulting back to init 3 and run X by hand, didnt make any difference. It starts fluxbox just fine but for the life of me kde4 will not run anymore. What else is odd that on my x64 laptop this issue does not occur with the same config and package selection apart from virtualbox.
anyone having this as well, not being able to start kde4 from KDM or anyone who has solved it already? Could it be related to kdebase 4.1.1-2_x86?
stefan
"root# su - bofh"
OS: F10_x64, Arch, Centos5.3, RHEL4.7, RHEL5.3
Desktop Hardware: Dell Precision M65 laptop, core2duo, 2gb, 80gb 7200rpm
Registered linux user #459910 since 1998
Offline
Don't know if it's the same issue, but I couldn't start KDE 4.1 with xorg-server > 1.4.2...
Some days ago I updated xorg-server from testing from 1.4.2 to 1.4.99.906 and KDE crashed badly. Gnome would work fine.
I reverted back to 1.4.2 and I could finally run it.
Unfortunately, I didn't test with 1.5.0.
eaZy
no masters to rule us, no gods to fool us
Offline
well i am not sure if all problems are related but as for me, I am running the stock xorg-server and have not upgraded against [testing].
stefan
"root# su - bofh"
OS: F10_x64, Arch, Centos5.3, RHEL4.7, RHEL5.3
Desktop Hardware: Dell Precision M65 laptop, core2duo, 2gb, 80gb 7200rpm
Registered linux user #459910 since 1998
Offline
for me, testing is not activated, but still the same issue..
Offline
i finally solved my problem. I started kde4 and let it fail once again. Then I switched to console and checked my ~/.xsession-errors.
$ cat /home/stefan/.xsession-errors
kdeinit4: preparing to launch /usr/bin/kcminit_startup
kdeinit4: preparing to launch /usr/bin/ksmserver
ksmserver: error while loading shared libraries: libQtWebKit.so.4: cannot open sharedobject file: No such file or directory
startkde: Shutting down...
klauncher: Exiting on signal 1
somehow libQtWebKit.so.4 was missing suddenly on my computer. To solve this I reinstalled not KDE but rather QT
$ su -c "pacman -S qt"
and all was well again, apart from one little thing. This problem made me use XFCE again for a week and secretly I am starting to perfer it over KDE4. fonts, icons and the taskmanager are so much better. even the tray icons for KDE apps looked better on XFCE then plasma.
well at least it works now. maybe this helps others too.
stefan
"root# su - bofh"
OS: F10_x64, Arch, Centos5.3, RHEL4.7, RHEL5.3
Desktop Hardware: Dell Precision M65 laptop, core2duo, 2gb, 80gb 7200rpm
Registered linux user #459910 since 1998
Offline
@Stefan,
I have posted my .xsession-errors above. COuld you please point out any issues there. I was not able to find out anything. It seemed to me as though knotify4 was the troublemaker and reinstalled the package which owned knotify4, but still no help.
Offline
mmm your problem is different. I would guess it has something to do with X itself, but then gnome would not work either. is your xorg.log file showing anything weird? what if you reinstall qt, xorg and run hwd/nvidia-xconfig all over again, does that help?
stefan
"root# su - bofh"
OS: F10_x64, Arch, Centos5.3, RHEL4.7, RHEL5.3
Desktop Hardware: Dell Precision M65 laptop, core2duo, 2gb, 80gb 7200rpm
Registered linux user #459910 since 1998
Offline
I dont have nvidia, but I tried re-running xconfig and set stuff according to the best of my knowledge (which had worked earlier), but now nothing helps.
Offline
I did an installation of KDE4 to check how things are going, and I'm hit with this bug as well. I login and get bumped back to the login manager again. This is annoying, well, but there has to be a way to fiz this, let me research a bit more. Oh, and the same happens with kdemod and kde from extra.
And the error is this: Couldn't start knotify from knotify4.desktop: "KDEInit could not launch '/usr/bin/knotify4'."
Last edited by kensai (2008-09-22 04:25:30)
Offline
i got the same issue on my laptop with a nvidia 7300go (asus ak6m laptop). the thing is, it would completely lock my laptop before i upgraded to the nvidia drivers from abs. no i'm in kde... i got the widgets working, but kwin crashes??? so i'm in kde with everything working but kwin, which is rather weird. i'll in stall the debug packages, so that i can give you a probable reason. i guess this is all somehow connected. i'll try the nv drivers, so that i can rule out another nvidia fuck-up.
update: ok, it IS a nvidia problem. sorry i'm not sure it's really related to this thread any more.
Last edited by eNTi (2008-09-22 13:48:42)
Offline
I did an installation of KDE4 to check how things are going, and I'm hit with this bug as well. I login and get bumped back to the login manager again. This is annoying, well, but there has to be a way to fiz this, let me research a bit more. Oh, and the same happens with kdemod and kde from extra.
And the error is this: Couldn't start knotify from knotify4.desktop: "KDEInit could not launch '/usr/bin/knotify4'."
THat is what i figured out some time back, but how to fix that.
Offline
holy crap, this issue drove me bonkers until i got rid of it.
now i dont have any detailed explanation as to what the problem is but ill back-track what i did and see if it helps you guys.
First, start from a clean plate by deleting ~/.kde4 the reboot and login. Go to system settings > advance > service manager and basically disable any services you dont need.
Then from system settings > advance > session manager select "start with an empty session" under "On Login".
I've not experience the problem going on 3 days now. I even have compiz running on autostart and few widgets off kde-look.
good luck.
btw, i use kdm to login
Last edited by bijoux (2008-09-23 04:56:20)
Offline
holy crap, this issue drove me bonkers until i got rid of it.
now i dont have any detailed explanation as to what the problem is but ill back-track what i did and see if it helps you guys.
First, start from a clean plate by deleting ~/.kde4 the reboot and login. Go to system settings > advance > service manager and basically disable any services you dont need.
Then from system settings > advance > session manager select "start with an empty session" under "On Login".
I've not experience the problem going on 3 days now. I even have compiz running on autostart and few widgets off kde-look.
good luck.btw, i use kdm to login
but how do you change "settings>advance>service manager" unless and until you log in. I'm not able to go beyond login screen of kdm.
Offline
but how do you change "settings>advance>service manager" unless and until you log in. I'm not able to go beyond login screen of kdm.
install fluxbox or any other wm, login that way and issue systemsettings in the terminal.
Anyways it didn't work for me so I retired completely from KDE4.
Offline
install fluxbox or any other wm, login that way and issue systemsettings in the terminal.
Anyways it didn't work for me so I retired completely from KDE4.
I did the same and when clicked "service manager" I got the error "unable to contact kded" Clicked "ok" on that error message and then got "KDE service confirguration" in which everything was "gray" and inactive, nothing could be selected or disabled.
Offline