Subject: Re:  kppp, different keyboard layouts, klaptopdaemon can't connect to
the systemtray

Additional info:

the bug is easy to reproduce:
configure another keyboard layout. Now, you can see it in the systemtray. Then 
logout please and login again. The Icon is now in the left upper edge.


Kind regards,
Andreas Hartmann

Working on it ...

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

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

I forgot to close this one, it should be already fixed.

There are not yet fixed all problems :-).

If you start a internet session with kppp, which is docked into the systemtray, the tray isn't reset correctly when stopping the internet session and kppp itself isn't closed.
The two "LED's" disappear, but the place, which is reserved for them in the tray, is not freed again.
It is freed when kppp is totaly closed.

Maybe this is a problem of kppp - but I cannot say this.

I cannot remove Amarok icon from system tray _at all_.
When I do m_pTray->hide() it hides for a moment and then reappears.
annma reported that the icon goes away, but the place is still reserved.
In 3.1 all this works brilliant.

kde3.2-beta1 compiled using konstruct1103.
I deleted my .kde dir and started from scratch -> klaptop is in the top left corner.
Other things in the systray are klipper, kalendar and irkick.
If I open klaptops config menu and toggle the "Show battery monitor" checkbox (with applying each state), it appears, where it should, in the tray. But only until the next restart of kde.

Rolf (Comment#8),

Yes, in KDE3.2-beta1 (3.1.93) the bug is present (klaptop, keyboard... in the top left).
It has been fixed after 3.1.93 was released.

It hasn't been fixed as of 2003-11-07 (my latest build).

Turn the machine power on, boot, login -> kxkb icon is in the top-left corner.
Logout, login again without rebooting -> kxkb icon is in tray.
Logout, reboot, login -> kxkb is in top-left corner.
Logout, login again without rebooting -> kxkb icon is in tray.
ad nauseum..

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

It's working for me in kde-3.2.0_rc1.

Can somebody still reproduce the problem?

It's working for me. I've got no problems with actual KDE_3_2_BRANCH.

it's also working for me on CVS HEAD ... closing with Lubos' "should be fixed"
and two confirmations =)

this problem is back in KDE 3.5.1 and so is "klaptop applet displays in upper
left corner" (http://bugs.kde.org/show_bug.cgi?id=68232) 

Yes, it happens in 3.5.1 (I saw with kxkb). This is in a kiosk environment and
we are using for teaching computer usage and it is very annoying that every day
the icon is in the upper left corner if I don't remove the content of
$KDEHOME/share/config/session . There is usually one file with a kwin_A LONG
NUMBER name. The problem appears randomly, so as soon as I have such a file, i
will post it.
I did not saw it with 3.4.x and 3.5.0.

Yes, it happens in 3.5.1 (I saw with kxkb). This is in a kiosk environment and
we are using for teaching computer usage and it is very annoying that every day
the icon is in the upper left corner if I don't remove the content of
$KDEHOME/share/config/session . There is usually one file with a kwin_A LONG
NUMBER name. The problem appears randomly, so as soon as I have such a file, i
will post it.
I did not saw it with 3.4.x and 3.5.0.

Should be already fixed for 3.5.2.

This problem happens to me with the kxkb system tray icon.  I have discovered
that it can be fixed with the following:

1. Right-click on the system tray icon and select "Configure…"
2. Uncheck "Enable keyboard layouts"
3. Click "Apply"
4. Check "Enable keyboard layouts"
5. Click "OK"

However, this works only for the current login session; as soon as KDE is
restarted, the icon goes back to the upper left-hand corner.  Can anyone
suggest a permanent fix I can use until KDE 3.5.2 comes out?

Yes, a workaround is that you put the following into a file in 
$KDEDIR/env (eg. /opt/kde3/env) and make it executable:
-------
#!/bin/bash
rm -f $HOME/.kde/share/config/session/kwin*
-------

it deletes the files causing the problem on every login. It might delete 
something else as well, so use with care. For me it works.