Hello, Im not sure if this is related, but today I upgraded to kdebase 3.4.1-2 in testing and when kde started, i had reoccouring pop-ups every 2-3 seconds saying that kded crashed with SIGABRT. This also happened with a "clean new user"

I went back to 3.4.1-1 in extra and everything is find again.

im using standard kde packages and options
glibc-2.3.5-5
qt 3.3.4-8
nvidia 6629 drivers

Tobias Powalowski wrote:

Hi KDE users, some of you out there seem to have problems on KDE startup, this thread is to collect info about this specific issue. Here is my setup that works: glibc-2.3.4-2 qt 3.3.4-8 normal kde packages standard kde options no xcompmgr bash as shell using kdm as login manager using standard arch kernel26 md5sums of packages: e3ca920943382e740eddaa42a31121d9 qt-3.3.4-8.pkg.tar.gz f21780c4cc4daa653134013934de1b03 kdelibs-3.4.1-1.pkg.tar.gz 448264288b508d7e9c8d6292f67501eb kdebase-3.4.1-1.pkg.tar.gz d56cbbb399db792284e217368090a7b6 glibc-2.3.4-2.pkg.tar.gz I have no problems at all, as many other kde users so please help together on that issue. Now i need to know: Does this issues arises after update or fresh install? Does it happen with a clean new user? Does it happen from startx or kdm? Are you using special kde extensions? What shell are you using? Are you using any package from Testing? Did you run pacman -Syu before installing KDE? Did you try to install kde again? md5sum of qt,kdelibs,kdebase? Are you using nvidia drivers? Do you run kcompmgr/xcompmgr? What kernel are you running? output from: startx > info 2>&1 ? Please send me the info file crash output? please send me the crash output Try recompiling: qt,kdelibs and kdebase from abs and tell me the success. This thread goes out to: colnago,harald_u,bpiniot,pholie,purkurr,Marko,jw,pointer The faster you find a solution, the faster it can be fixed! my time is limited and i don't have the crash( as many others) so please it's up to you to feed me and the others with input, that we can solve the issue. @ All who think that a longer testing period would be helpfull, i can tell you the answers would be: why should i use testing? i wait for the movement to extra. Keep in mind i don't want to cause trouble on your pcs, but you should also keep in mind arch is bleeding edge software,i have only limited hardware/time and i'm the only dev that works on kde.
here is the forum link for discussion:
http://bbs.archlinux.org/viewtopic.php?t=12947

greetings from tpowa P.S.: Kwin crash on logout has been identified as kde bug, don't report it here! my mail is tpowa (@) archlinux.org
------------------------------------------------------------------------

_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch


_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to