KDE 3.0.2 does not start
I'm using SuSE 8.0 with KDE 3.0.2 updates installed. When I try to start KDE via "startx" the KDE initialisaion screen appears but after "system resources" have been initialized KDE crashes. I'm quite new to KDE - maybe somebody can give me a hint what might be wrong or how to interpret the following error messages (this also happens with KDE 3.0 and cleaning the /tmp directory also is of no use): DCOPServer up and running. DCOP Cleaning up dead connections. Mutex destroy failure: Device or resource busy mcop warning: user defined signal handler found for SIG_PIPE, overriding Mutex destroy failure: Device or resource busy Mutex destroy failure: Device or resource busy QObject::connect: No such slot KWrited::block_in(const char*,int) QObject::connect: (sender name: 'unnamed') QObject::connect: (receiver name: 'unnamed') /usr/lib/qt3/plugins/imageformats/libqjpeg.so: Feature JPEG already defined in /usr/lib/qt-3.0.3/plugins/imageformats/libqjpeg.so! [similar messages repeated multiple times] DCOP aborting call from 'anonymous-1047' to 'korgac' ICE default IO error handler doing an exit(), pid = 1050, errno = 2 DCOP aborting call from 'applet_proxy-1043' to 'kicker' DCOP aborting call from 'applet_proxy-1042' to 'kicker xinit: connection to X server lost. Thanks, Andreas
Hi, I have commented a couple of times here on awful stability problems that I have been having under kde (newest version) under SuSE 8.0. Frequent memory tests - both the SuSE boot Option and the sig11 kernel-compile script I found on the web - had found nothing but stability was persistently awful. Touching wood while I write this, but I seem to have found the solution, http://arstechnica.com/guide/building/bios/bios-1.html has the answers. If others here have suffered similarly (and I know several have) then maybe this can do something for you as well. hope this helps ;-) -- opinions personal, facts suspect. http://home.arcor.de/36bit/samba.html
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 . Thanks Andrew. I'm one of those who've had real instability with Suse8. But my IBM Thinkpad A22p doesn't have a single one of the bios adjustments he discusses. I'm about to try 8 again. Hope this isn't the same mess as before. In response to your message though I have upgraded bios, which was at 1.05 and is now at 1.08 . Carl On Saturday 14 September 2002 07:18 am, you wrote:
Hi,
I have commented a couple of times here on awful stability problems that I have been having under kde (newest version) under SuSE 8.0.
Frequent memory tests - both the SuSE boot Option and the sig11 kernel-compile script I found on the web - had found nothing but stability was persistently awful.
Touching wood while I write this, but I seem to have found the solution, http://arstechnica.com/guide/building/bios/bios-1.html has the answers.
If others here have suffered similarly (and I know several have) then maybe this can do something for you as well.
hope this helps ;-) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org
iEYEARECAAYFAj2Eyx4ACgkQnQ18+PFcZJspZQCePw0srJII+z0kBT1HfGQ0TQVv bT4AnRziJTDFwEE0SKHp7uSbQN3sA5nz =2BOw -----END PGP SIGNATURE-----
. I think I've found part of the reason for my problems, particularly why it deteriorated over 3 weeks: http://www.namesys.com/ This is the Reiser filesystem website. Under DOWNLOAD it says: CAUTIONWARNING 1. Don't use linux kernel 2.4.16 or earlier for reiserfs operations, as many of those releases contain critical bugs, some of the most serious of which are not in reiserfs but affect reiserfs. 2.4.16, 2.4.9, and 2.4.3 are especially bad. The SuSE release of 2.4.16 is ok, it contains some needed patches. 2.4.19 is the latest release at the time of writing, and it is solid and reliable. 2. For linux kernel 2.5.6 or 2.5.7 you need an additional patch that will allow the use of reiserfs: 01-revert_broken_alviro_cleanup.diff Suse, please release 2.4.19!
On Sunday 22 September 2002 23:42, Carl wrote:
. I think I've found part of the reason for my problems, particularly why it deteriorated over 3 weeks: http://www.namesys.com/
This is the Reiser filesystem website. Under DOWNLOAD it says:
CAUTIONWARNING
1. Don't use linux kernel 2.4.16 or earlier for reiserfs operations, as many of those releases contain critical bugs, some of the most serious of which are not in reiserfs but affect reiserfs. 2.4.16, 2.4.9, and 2.4.3 are especially bad. The SuSE release of 2.4.16 is ok, it contains some needed patches. 2.4.19 is the latest release at the time of writing, and it is solid and reliable. 2. For linux kernel 2.5.6 or 2.5.7 you need an additional patch that will allow the use of reiserfs: 01-revert_broken_alviro_cleanup.diff
Suse, please release 2.4.19! =================
Carl, 2.4.19 kernel is available now on the SuSE site under Mantel. Works well, is stable and if you have an Athlon, get that kernel as it makes a big difference on those machines! Patrick -- --- KMail v1.4.3 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206
On Sunday, 22 September 2002 23:21, Anders Johansson wrote:
On Monday 23 September 2002 05.42, Carl wrote:
The SuSE release of 2.4.16 is ok, it contains some needed patches.
Isn't that working then?
//Anders
True, it does say Suse. But I am looking for at least SOME way to explain these problems to my boss. In looking around at the newsgroups, linuxnewbie, and /., I can tell you that we have now lost a very large new population of users because they simply could not make Linux work. Meaning problem releases like RedHat's 'C compiler' release, Mandrake's 8.0 and 8.1 releases, and Suse's 8 release. We've lost them for a long time because of incumbant attitudes like "Well maybe you SHOULD be running Windows if you can't figure it out...". The best remark of discouragement I saw was, "I don't want to be configuring all the time anymore. I just want to turn on the computer and be able to get work done. I've been using Linux now for 2 years and things =haven't= gotten better." I realize this doesn't sit well with the acolytes. But these are facts. Even I am seriously ready for Apple if things don't improve. Packaging tangled? Yast2 buggy and destructive? K selects Keramik over Liquid for political reasons, despite popular opinion? (so Mosfet quits) New releases, not BETTER releases? I'm now beyond wondering what could be wrong. I have one machine up now with Suse8/K3.0.3 and my fonts got muggered up again when I dared to install my .ttf's, just like with 7.3 . As with 7.3, one illegible font (saudi.ttf) has been substituted for display by MOST fonts. I can select any of 90% of my fonts, and they all look like saudi. WTF?! I remove saudi and then all lettering is just BLOCKS. THROUGHOUT K! Completely unusable, and no apparent place to fix it. I personally believe KDE and Gnome's inability to get their shit together has now alone doomed Linux. Patrick, thanks for the refer to Mantel, but the one Mantel I tried was busted. I need to stick with official releases to cover my arse.
participants (5)
-
Anders Johansson -
Andreas Unterkircher -
Andrew Williams -
Carl -
Patrick