Le Lundi 19 Septembre 2005 19:59, Frederic a écrit :

Le Dimanche 18 Septembre 2005 01:02, Frederic a écrit :

...

Hi,

After having installed the latest security updates from YAST, I cannot use Kopete and Kooka anymore :-(

Here is the error for Kooka : lookup error: kooka: undefined symbol: _ZN11KMainWindow7setIconERK7QPixmap

Any idea on how I could solve this ? Will I have to upgrade to whole system to Suse 9.3 ?

Help ! Anybody ?

this is really what I hate about KDE. If an upgrade fucked up your kdelibwhatever you're unable to have things working again normally. WinXP => uninstall => reinstall and you're done Hope it will get better in the better in this area...

Le Mardi 20 Septembre 2005 21:26, Jos van Kan a écrit :

Frederic wrote:

...

this is really what I hate about KDE. If an upgrade fucked up your kdelibwhatever you're unable to have things working again normally. WinXP => uninstall => reinstall and you're done

Hope it will get better in the better in this area...

This is what I really hate about posters like these. Don't think, just gripe. If you flamed up your kdelibs you reinstall your kdelibs. But most of the time its just the configuration that's flamed up. So you rename them to .whatever_old and restart kde. This must be the 256th time this issue has turned up.

Now repeat after me: WinXP has its uses. You can check with it if your hardware is broken.

This is what I really hate about issues like these, before they you SHOULD have know the reason. Sorry for asking help. I'm not a genius like you.

Le Mardi 20 Septembre 2005 21:58, kanenas a écrit :

On Tuesday 20 September 2005 09:31, Frederic wrote:

...

Le Mardi 20 Septembre 2005 21:26, Jos van Kan a ιcrit :

...

Frederic wrote:

...

this is really what I hate about KDE. If an upgrade fucked up your kdelibwhatever you're unable to have things working again normally. WinXP => uninstall => reinstall and you're done

Hope it will get better in the better in this area...

This is what I really hate about posters like these. Don't think, just gripe. If you flamed up your kdelibs you reinstall your kdelibs. But most of the time its just the configuration that's flamed up. So you rename them to .whatever_old and restart kde. This must be the 256th time this issue has turned up.

Now repeat after me: WinXP has its uses. You can check with it if your hardware is broken.

This is what I really hate about issues like these, before they you SHOULD have know the reason. Sorry for asking help. I'm not a genius like you.

Hey, *not genius*, a polite "thanks for the help" and an apology for *your* mouthing off before even asking for help might end up adding a couple if iq points to your score...

First I've been asking for help several times, but that's not the point I know nobody is obliged to answer. Second I don't think I've been rude in anyway. I just don't like people who think that the solution is obvious and everybody should know. I didn't flamed up my kdelibs myself, as I said in the first post it was after a security upgrade with Yast. Nevermind "thanks for your help" I can live with brokens Kmix, Kate and Kopete. As usual, to solve the issue, I will format my drive and install Suse 10.0...