Bug 227512

it should appear when you touch the border where the kicker taskbar is docked to. this is worksforme both with 

can you attach your kickerrc ? do you use compiz or kwin?

Created attachment 109628 [details]
kickerrc

Yes, I know that it *should* work like that, and that's what it did fine in SuSE 9.3. Nothing changed in configuration, only ran update to 10.2, and gave described symptoms.

amm       4691  4676  0 21:36 ?        00:00:01 kwin [kdeinit] -session 117f000002000113433521900000040370000_1165953127_753512

Apparently, I use kwin.

Note that the kickerrc comes from the present moment, so *after* I have disabled auto-hide (as it doesn't work for me, and it's quite unpleasant to work without the kicker..).

According to the config file the panel is not set to auto-hide, it's configured to allow normal windows to cover it. And all that works as it should here with that config file, as far as I can say. So, what exactly is the problem again?

Please re-read comment#3. As mentioned there, I have now disabled auto-hide. *If and when* I re-enable it, the kicker doesn't come up anymore at all.

We're of course interested in things that don't work, what would be the point of testing something that works? I still don't see any problem after changing the configuration here.

Ok, I did some more testing here. After changing the kicker configuration several times to different settings within OpenSuSE 10.2, now changing it back to auto-hide seems to work. Anyway, after updating from SuSE 9.3 (where auto-hide was set), and without those several times of changing the settings, the bug appeared as described above. (And it appeared consistently, also after re-booting and re-login several times.)

So maybe the problem rather lies in the update of the kicker configuation files when coming from SuSE 9.3, than in the kicker functionality itself?

Well, we still cannot check that without having the configuration file that doesn't work.

Well, I could only reproduce the error if I went back to my previous SuSE 9.3 configuration, and then did the upgrade to OpenSuSE 10.2 again, and during that process save all changes of kicker files... sorry that's a bit too much now that I got 10.2 finally working.

Anyway, the fact is that the symptoms just as described above have appeared directly after the upgrade. Sorry I cannot help you with more information at this moment.

Cannot reproduce, cannot fix.

Created attachment 111750 [details]
kicker crash messages

"Cannot reproduce, cannot fix." - maybe.

"Resolved" - no way.

It happened again, kicker crashed, didn't come out of auto-hide after that. kickerrc unchanged. No obvious reason (I had the calendar open, but I guess that shouldn't be considered as a reason...). I saved the crash messages, maybe that finally helps you to fix the bug.

No, it doesn't. It's a random crash without any debug symbols and you seem to be the only one having the problem.

You can install debuginfos and run kicker through valgrind - perhaps that will give you something useful.

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

Ok, so it seems I'm not the only one having this problem. (In any case, it would only mean the only one *who reports it here*.)

Unfortunately, the way to receive the requested info goes beyond my technical knowledge (especially without any more detailed instructions), so I cannot provide it.