[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Another try. This time with feeling.....
From:       Lubos Lunak <l.lunak () suse ! cz>
Date:       2004-09-22 11:56:40
Message-ID: 200409221356.40226.l.lunak () suse ! cz
[Download RAW message or body]

On Tuesday 21 of September 2004 17:02, Gary L. Greene, Jr wrote:
> On Tuesday 21 September 2004 05:45 am, David Faure wrote:
> > On Tuesday 21 September 2004 04:05, Gary L. Greene, Jr wrote:
> > > Additionally to this, the minicli run dialog pops up on the wrong
> > > desktop.
> >
> > Broken Suse Qt patch.

 No, bug in Xlib.

> > What happened to the good old "looking up in bugs.kde.org" method?
>
> I did, and reopened the bug report becuase it has not been truely resolved.

 And I closed it again, because it's no KDE bug (which would be actually 
visible in the bugreport if people didn't feel this strange urge to make life 
of developers more difficult by adding offtopic rubbish to bugreports).

> There has not been a patch made available on b.k.o nor in Qt-copy.

 Because the bug is neither in KDE nor in qt-copy.

> Additionally, I've yet to see any change in Qt-3.3.3 or 3.3.4 that may be
> attributed to fixing this. If you can point me to where a reliable fix for
> this is, then please, by al means point me there.

 Packagers have been notifiied about this problem almost two weeks ago, so if 
you still have the problem, complain to them:
----------  Forwarded Message  ----------

Subject: bug #12620 - alt+f2 on wrong desktop etc.
Date: Saturday 11 of September 2004 13:07
From: Lubos Lunak <l.lunak@suse.cz>
To: kde-packager@kde.org

 Hello,

 to all packagers who also provide Qt packages and use the immodule patch:
 Due to a bug in Xlib, the patch causes bug #12620 and its various duplicates
 (taskbar, pager, window list etc. stop working after a short time). Please
 apply the attached Xlib patch to your X packages if you can, or apply the
 attached Qt patch which works around the problem.


(Just in case somebody would ask again: If your Qt package doesn't have the 
immodule patch, and the attached Qt patch therefore doesn't apply, then you 
indeed don't need it.)

-- 
Lubos Lunak
KDE developer
---------------------------------------------------------------------
SuSE CR, s.r.o.  e-mail: l.lunak@suse.cz , l.lunak@kde.org
Drahobejlova 27  tel: +420 2 9654 2373
190 00 Praha 9   fax: +420 2 9654 2374
Czech Republic   http://www.suse.cz/

["imInsClbk.c.patch" (text/x-diff)]

--- lib/X11/imInsClbk.c.sav	2004-03-04 18:46:38.000000000 +0100
+++ lib/X11/imInsClbk.c	2005-02-08 10:33:01.340890472 +0100
@@ -254,8 +254,8 @@ _XimUnRegisterIMInstantiateCallback(
 		    _XUnregisterFilter( display, RootWindow(display, 0),
 					_XimFilterPropertyNotify,
 					(XPointer)NULL );
-		    XSelectInput( display, RootWindow(display, 0),
-				  NoEventMask );
+		    /*XSelectInput( display, RootWindow(display, 0),
+				  NoEventMask );*/
 		}
 		else
 		    picb->next = icb->next;

["qximinputcontext_x11.cpp.patch" (text/x-diff)]

--- src/input/qximinputcontext_x11.cpp.sav	2005-02-08 10:05:52.000000000 +0100
+++ src/input/qximinputcontext_x11.cpp	2005-02-08 12:11:25.539564520 +0100
@@ -482,8 +482,11 @@ void QXIMInputContext::init_xim()
 		  ximServerName.ascii());
     else {
 	Display *dpy = QPaintDevice::x11AppDisplay();
+	XWindowAttributes attr; // XIM unselects all events on the root window
+	XGetWindowAttributes( dpy, QPaintDevice::x11AppRootWindow(), &attr );
 	XRegisterIMInstantiateCallback(dpy, 0, 0, 0,
 				       (XIMProc) xim_create_callback, 0);
+	XSelectInput( dpy, QPaintDevice::x11AppRootWindow(), attr.your_event_mask );
     }
 #else // !USE_X11R6_XIM
     else if ( XSetLocaleModifiers ("") == 0 )


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]