| Summary: | KDE2.1 freezes at startup | ||
|---|---|---|---|
| Product: | [Unmaintained] kdelibs | Reporter: | Mekanix <mekanix> |
| Component: | kdeinit | Assignee: | Unassigned bugs <unassigned-bugs-null> |
| Status: | CLOSED FIXED | ||
| Severity: | normal | CC: | esigra |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | FreeBSD Ports | ||
| OS: | FreeBSD | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Mekanix
2001-03-01 08:52:27 UTC
On Thursday 01 March 2001 00:52 you wrote: > Package: kdeinit > Version: KDE 2.1.0 > Severity: normal > Installed from: FreeBSD Ports > Compiler: gcc 2.95.2 > OS: FreeBSD > OS/Compiler notes: FreeBSD 4.2-STABLE > > I've just finished the portsinstall of KDE2.1 but it wont run. It just > hangs at startup at "Initialising peripherals". When I click *on* the > splashscreen/"startupwindow" (or wazzitcalled) the screen goes blanks and > still hangs. Does it work if you remove the following line X-KDE-Init=style from $KDEDIR/share/applnk/Settings/LookNFeel/style.desktop? Cheers Waldo -- bastian@kde.org | SuSE Labs KDE Developer | bastian@suse.com On Thu 1 Mar 2001 11:06:19 -0800 Waldo Bastian <bastian@kde.org> wrote: > Does it work if you remove the following line > X-KDE-Init=style > from $KDEDIR/share/applnk/Settings/LookNFeel/style.desktop? Yes it runs now if I keep my hand away for Controlcenter->Look'n'Feel->styles! But runs a bit unstable. kdeinit ocasionally hangs with some kioslave-stuff. But that's possible related to another bug-report of mine (#21191) where parts of kioslave fails to compile. Bjarne I have exactly the same problem as described. The workaround has worked for me as well. But I previously got the same results if I comment out the line that says LD_BIND_NOW=true kdeinit +kcminit from startkde. But as Bjarne says the system is completely unstable with both workaround (I haven't noticed any differences to be exact). Some unstability problems I can reproduce: -> It is common for the screensaver (with passowrd) not to recover when I write the password. -> kdeinit for the Control Center will eat 100% CPU if I click on information->block_devices or information Samba Status. Of course this causes Control Center to freeze. When this happens the only way to recover is to send signal 9 to the hung process which in turns makes the system totally unusable as trying to start _any_application from the panel or to browse with Konqueror windows already opened fail with a message indicating failure to communicate with klauncher. This sympton (kdeinit for xxxx eating 100% cpu ....) happens randomly (but often) for other applications too. Hope you can find a solution for this! jOrge -- Jorge Peixoto Vasquez Elect. Eng. Aker Security Solutions http://www.aker.com.br More info: when I kill the hung process (kdeinit... 100% ...) I can restore the system by starting kxkb again since it always hangs up two. In fact it is normal for two processes to hang up togheter one of them being kxkb. jOrge -- Jorge Peixoto Vasquez Elect. Eng. Aker Security Solutions http://www.aker.com.br I've been reading through the thread and I dicovered our pcs are not the only one to freeze on startup of kde. The only problem I could not trace down what's happened since the pcs completely hang and I must reboot (i.e. push the off button). I think it's because we are in init 5 mode so no way back to kill the application. Is there any *good* solution for that? We use it at university and it' pretty bothering to rebbot the machine every 2 or 3 logons... Thanks Alberto Azzalini azzalini at removeformailingme.ing.unitn.it Original problem might be a FreeBSD thread-support problem. Other problems reported to BR21123 seems to be totally unrelated. Cheers Waldo -- bastian@kde.org | SuSE Labs KDE Developer | bastian@suse.com Thank you for your bug report. The bug that your reported no longer applies to the latest development (CVS) version of KDE. This is most probably because the bug has been fixed the application has been substantially modified or the application = no=20 longer exists. The bug report will be closed. KDE now builds with proper threads support on FreeBSD and this freeze cann= ot=20 be reproduced any longer. |