You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Thursday, February 5th 2004, 3:53pm

KDE 3.2 and Kicker Hang Problem

I have just installed KDE 3.2 on my Suse 8.2 system and Kicker is causing the system to freeze. What happens is that I can move the mouse on the screen, but I can't type anything and I can't execute any actions within KDE. After a few minutes, the system comes back up again. I am sure it's the kicker (the panel on the bottom of the screen) because when I disable the kicker, there's no problem.

Some observations:
1) When I type in kicker at the command prompt, I get the following output:
kicker: WARNING: QT(Warn): QObject::connect: Cannot connect (null)::changed() to KickPimMenu::onEventViewChanged()
kicker: WARNING: QT(Warn): QObject::connect: Cannot connect (null)::changed() to KickPimMenu::onEmailViewChanged()

2) When booting up, I am told there is a configuraiton problem with my etc/X11/qtrc.rpmnew file?

Any thoughts or suggestions? Thanks.

PS I am a newbie.

2

Thursday, February 5th 2004, 4:01pm

That seems to be a problem concerning the KickPIM applet.

Try to remove the applet from your kicker and check if the problem is still there. I will look at it these days (I am the author of KickPIM).

Greetings
Bert Speckels.