Hi,
On Sunday 16 May 2004 12:13, Tom Payne wrote:
> In short, I posted the patch which only Martin Stubenschrott tested. He
> said it worked sometimes but not always, but didn't give any more detail
> which wasn't really enough information for me to fix it :-)
Well, finally I gave it another try, and found out the problem, why 2 of my
KDE tray icons were not working. I had set up kludges for those programs
(Kopete, JuK), but defined role = "*", and so also the tray icon was moved to
this frame. I changed both kludges and it works now for ALL of my KDE apps
without any other kludges :)
The only remaining thing is the small kbluetoothd problem (copied from my old
message):
The kbluetoothd deamon, also works, but when trying to close the app, the
close confirmation dialog also goes into the tray icon with 22 (or 24, i dont
know) pixel size, making it impossible to close the daemon.
When then try to close it by pressing ctrl-c in the shell i started
kbluetoothd, Ion crashes completely.
But this time I give you some more info :)
> xprop //on the icon of the bluetooth daemon
_KDE_NET_USER_TIME(CARDINAL) = 2257551767
WM_COMMAND(STRING) = { "kbluetoothd" }
_NET_WM_USER_TIME(CARDINAL) = 489579
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
_NET_WM_STATE(ATOM) =
_NET_STARTUP_ID(UTF8_STRING) = 0x30
_KDE_NET_WM_SYSTEM_TRAY_WINDOW_FOR(WINDOW): window id # 0xb5
WM_CLIENT_LEADER(WINDOW): window id # 0x3000002
WM_WINDOW_ROLE(STRING) = "unnamed"
_NET_WM_PID(CARDINAL) = 8568
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING
WM_NAME(STRING) = "kbluetoothd"
WM_LOCALE_NAME(STRING) = "en_US"
WM_CLASS(STRING) = "kbluetoothd", "Kbluetoothd"
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
Initial state is Normal State.
window id # of group leader: 0x3000002
WM_NORMAL_HINTS(WM_SIZE_HINTS):
user specified location: -1000, -1000
program specified location: -1000, -1000
user specified size: 22 by 22
program specified size: 22 by 22
window gravity: NorthWest
WM_CLIENT_MACHINE(STRING) = "maxauth"
> xprop // on the confirmation window
>
_KDE_NET_USER_TIME(CARDINAL) = 2257551500
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
_NET_WM_USER_TIME(CARDINAL) = 489579
_NET_STARTUP_ID(UTF8_STRING) = 0x30
XdndAware(ATOM) = ATOM
_MOTIF_DRAG_RECEIVER_INFO(_MOTIF_DRAG_RECEIVER_INFO) = 0x6c, 0x0, 0x5, 0x8,
0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xc0, 0x41, 0x10, 0x0, 0x0, 0x0
_NET_WM_NAME(UTF8_STRING) = 0x41, 0x75, 0x74, 0x6f, 0x6d, 0x61, 0x74, 0x69,
0x63, 0x61, 0x6c, 0x6c, 0x79, 0x20, 0x73, 0x74, 0x61, 0x72, 0x74, 0x20, 0x4b,
0x42, 0x6c, 0x75, 0x65, 0x74, 0x6f, 0x6f, 0x74, 0x68, 0x44, 0x3f, 0x20, 0x2d,
0x20, 0x4b, 0x42, 0x6c, 0x75, 0x65, 0x74, 0x6f, 0x6f, 0x74, 0x68, 0x44
WM_CLIENT_LEADER(WINDOW): window id # 0x3000002
WM_WINDOW_ROLE(STRING) = "questionYesNoCancel"
_NET_WM_PID(CARDINAL) = 8568
_NET_WM_STATE(ATOM) =
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DIALOG,
_NET_WM_WINDOW_TYPE_NORMAL
_MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x4, 0x0, 0x1, 0x3, 0x0
WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING,
_NET_WM_CONTEXT_HELP
WM_NAME(STRING) = "Automatically start KBluetoothD? - KBluetoothD"
WM_LOCALE_NAME(STRING) = "en_US"
WM_CLASS(STRING) = "kbluetoothd", "Kbluetoothd"
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
Initial state is Normal State.
window id # of group leader: 0x3000002
WM_NORMAL_HINTS(WM_SIZE_HINTS):
user specified location: 510, 429
program specified location: 510, 429
user specified size: 360 by 112
program specified size: 360 by 112
program specified minimum size: 360 by 112
program specified maximum size: 359 by 111
window gravity: NorthWest
WM_CLIENT_MACHINE(STRING) = "maxauth"
WM_TRANSIENT_FOR(WINDOW): window id # 0x3000007
KBlueToothD has no real user interface, but after starting it only shows a
system tray icon with a context menu on button press.
I wonder why the confirmation dialog is also shown in this frame since it
doesn't seem to set _KDE_NET_WM_SYSTEM_TRAY_WINDOW_FOR, may be it has to do
something with the WM_TRANSIENT_FOR hint?
Anyways, I am using your patch for a whole month now without any real
problems, so apart from the kbluetoothd problem your patch is ready for
widespread use IMHO.
Thanks again for the patch.
--
Martin
