Oops killed Konquer

[The PIT]

Upgraded to KDE 3.3 this evening as per instructions and everything has gone well except Konquer bombs out just like Windows explorer can do in Winblows.

It's nice too see the error message and the useless attempt at debugging which it can't do as I haven't installed it.

Interesting that KDE is trying too mimic Winblows in having one front end which is okay until it goes wrong.

Anyway I've uninstalled it and re-installed gone back to the orginal version and still no go. The dependances also seem correct as well.

Distro Suse 9.1 so any ideas apart from a re-install of Suse.

It's rather funny this as my work machine I didn't follow any instructions and slapped KDE 3.3 on in the completley wrong order and it worked.

[leech]

I've been noticing that KDE has been trying to mimic windows for far too long, which is why I generally use Gnome. But I've given KDE a chance a few times... My question is, anything really all new and ground-breaking in KDE 3.3? I installed it on my Debian system and it looked just the same as the old KDE... granted, I didn't really play around with it that much. Though I noticed they finally have a centralized place for themes... about freaking time!

Leech

[Marshmallowman]

Hwo did you install, from a suse installation package or straight from bzipped source code?

On the KDE site they have konstruct, which will download and install kde automatically, and if you use the default install it will install in your user directory , so It won't overwrite your old kde, so you can change between the 2.

However if you are getting klauncher and io-slave error I know which files you can delete to sort stuff those out (trashed kded cache and temp files can cause it)

[The PIT]

Downloaded all the rpms stuck them on CD and then installed all the art and libs as instructed. I then installed the adds I wanted and then chose what ever I wanted. Looks like KDE have missed something in the instructions.

I thought Kconstruct was for messing aroound with the tarballs and compiling the source. I'll have a look now and when I get home I'll get the KDE error message.

[The PIT]

Mmm Kconstruct looks a bit lack a slegdehammer to crack a nut. Looks complex to setup and knowing the differances between distros likely to stuff up.

[Marshmallowman]

it can be very misleading.

for me it was

download konstruct.(10 seconds)
unzip to directory in my home dir.
at console

cd meta\kde
make install

edit .bashrc to set 4 envirnomental variables to actually use the new kde
(old one is still installed and fully functional)

it does all the downloading and installing automatically...just wait 4 hours and you'll have a fresh pile of steaming KDE wating for you.

PS uncomment the p4 OWN_CFLAGS line in gar.conf.mk file it will optimise it for p4 (uncomment the athlon lline for athlon)

It really is very simple...it hides all the real complexity fro your completely...and the side product of it installing in usermode is a bonus...(in case you feck it up with to much tweaking)

[The PIT]

What do you have to set the variables too or does this vary slightly with distro's??
I'm in XP at the moment so I can't just look too see if it obivous.

[The PIT]

Fun trying that.

Got a problem with the C complier right at the end which is now having an insanity attack.

After finding all the other bits and bobs I needed some undocumented I decided to give up for the night.

[Marshmallowman]

konstruct, is not really distro specific..it trys to configure to suit your distro on the fly

The variables to set are

export QTDIR=~/kde3.3.1
export KDEDIR=~/kde3.3.1
export KDEDIRS=~/kde3.3.1

export LD_LIBRARY_PATH=~/kde3.3.1/lib
export PATH=~/kde3.3.1/bin:$PATH


full instructions here

http://developer.kde.org/build/konstruct/stable/README

edit to add missing link

[The PIT]

Problem is complier insanity error message.
Probably best if I start over again since it's a clean install and I have messed around a bit. Since I've got the space might as well stick all the damn librarys on as well.