Bug 74392

Summary:	K hangs when selection link in K menu
Product:	[Unmaintained] kicker	Reporter:	Gerrit Holl <gerrit>
Component:	general	Assignee:	John Firebaugh <jfirebaugh>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	crussmann
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	RedHat Enterprise Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Gerrit Holl 2004-02-06 19:47:37 UTC

Version:            (using KDE KDE 3.2.0)
Installed from:    RedHat RPMs
Compiler:          (compiled by Red Hat) 
OS:          Linux

When I open the K menu in Fedora Core 1 with KDE 3.2.0 installed from Fedora Core 1 RPM's, KDE hangs: it simply does *nothing*: the application doesn't start, and the menu hangs at it place. When pressing escape a few times, the windows disappear again, but then i'm unable to switch to other virtual desktops: when I click on it, they do turn white, but nothing happens beyond that. This bug happens only sometimes, but once it started, restarting KDE is the only way to have the K menu work again like it should.

Comment 1 Tommi Tervo 2004-02-06 21:37:50 UTC

*** Bug 74398 has been marked as a duplicate of this bug. ***

Comment 2 Alexander Malashenko 2004-02-07 01:14:34 UTC

There is one more way to force the K Menu works in this situation. It is pressing "esc" or "Alt" button.

Comment 3 Lindsay 2004-02-09 22:37:35 UTC

I also have this behaviour under Fedora Core 1 and KDE 3.2.

I will choose a menu item and instead of running it, nothing will happen and KDE stops responding to mouse clicks.  

It is possible to use the arrow keys to move the menu selection, and then push Enter to select. 

Pressing alt or esc makes the menu dissappear and the mouse works again.

I have heard suggestions on the kde usenet group that this may be to do with the qt version 3.2.3 revision 0.2.  There is a mouse focus policy patch that mandrake seems to have:

http://rpms.mandrakeclub.com/rpms/mandrake-devel/cooker/i586/Mandrake/RPMS/qt3-common-3.2.3-11mdk.i586.html

Notice under changelog:

 Thu Jan 22 2004 Laurent MONTEL <lmontel@mandrakesoft.com> 3.2.3-9mdk
  - Add patch38: fix clipboard recursion crash
  - Add patch39: fix dnd mem leak
  - Add patch40: fix mouse policy (fix for kwin3)

Is it possible to have this patch applied to the Fedora qt rpm?

Comment 4 David Faure 2004-02-10 10:58:50 UTC

On Monday 09 February 2004 22:37, Lindsay wrote:
> Is it possible to have this patch applied to the Fedora qt rpm?

You'll need to ask that to the Fedora packager - KDE releases source code,
binary packages are out of our hands.

Comment 5 Lindsay 2004-02-11 05:19:04 UTC

I have erased the qt 3.2.3 rpm, and compiled and installed qt version 3.3.

I have not seen this behaviour today so far. 

However I'm not sure that I have configured my system correctly to use the new qt version. KDE runs fine, however if I su to another user from a terminal and then attemp to start a kde app, like konqueror, I get:

Comment 6 Lindsay 2004-02-11 05:22:08 UTC

I have erased the qt 3.2.3 rpm, and compiled and installed qt version 3.3.

I am not sure if this behaviour has stopped - more testing required.

I don't know if I've configured my system correctly to use the new qt. 

If I su to another user in a console from within KDE, and attempt to start a kde app e.g. konqueror, I get:

konqueror: error while loading shared libraries: libqt-mt.so.3: cannot open shared object file: No such file or directory

What paths need to be configured to show kde where to get the libraries from?

Comment 7 Than Ngo 2004-02-17 16:57:04 UTC

it's fixed in Red Hat package qt-3.3.0-2 or newer, which is available in rawhide.

For FC1, i will rebuild KDE 3.2.0 against new qt-3.3.0 this weekend.

Comment 8 John Firebaugh 2004-02-22 02:14:49 UTC


*** This bug has been marked as a duplicate of 68508 ***