On Monday 31 March 2008, Stan Goodman said:
If you don't remember, could you try to reproduce the problem now that we know how to solve it?
I'm not sure that any of the 1.2.2.x paaragraphs is correct. The only diagnostic point to notice is that the file kickerrc had been altered to omit the two lines:
AutoHidePanel=false AutoHideDelay=3
which produced the effect that occured
This is incorrect. You can verify by creating a new user, logging in once, logging out again and seeing that those lines are not in kickerrc, but the panel does not hide. They may be involved but are not the smoking gun. If you have a copy of the kickerrc that caused the problem that would be great. If not could you try to reproduce the situation by repeating the following setups and comparing them with your original experience? It would let me turn "may not be the cause" to [X] and then look for another 1.2.2.x hypothesis. At the moment I'm minded to believe 1.2.2.2 was the cause.
1.2.2.1 No specific show trigger location was set. In this (default) case the screen edge where panel is positioned is the show trigger. This did not function at all. 1.2.2.2 A specific show trigger was set, but in a location inconsistent with the panel location (eg panel at bottom edge, trigger at top left) where User did not find it.
If any other sufferers of Disappearing Panel Syndrome (DIPS ;) have useful information, please share it. Will -- Desktop Engineer KDE Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org