#168 Baghira CVS causes kicker to crash when kmenu is clicked

[mlgill]

When Baghira CVS is the selected theme, clicking on
kmenu in the bottom kicker bar will immediately cause
the entire kicker (including Mac OS bar) to crash.
Clicking on any of my applications within kicker
(konsole, firefox, kontact, etc.) does NOT produce a
crash. Thus, the problem is specific to kmenu. Also,
the problem is immediately remedied by changing to a
different theme (I tried keramik) or by installing a
Baghira rpm (i.e. an older
version--baghira-0.7.1.guru.suse100.kde35, which I
compiled for kde 3.5 from an SRPM).

The problem started around the first week of Feb. 2006
(I don't recall when I updated my CVS code). I tried
updating the Baghira CVS code last night (Feb 14, 2006)
and the problem persists.

My baghirarc is attached. The backtrace is below:

KCrash: Application 'kicker' crashing...
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x2a001f1
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x2a001f1
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x2a001f1
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x2a001f1
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0xc0003f

[mlgill]

[Thomas Luebking]

Logged In: YES
user_id=931498

thanks for the rc, unfortunately, the above is not a
backtrace (rather looks asif you started kicker from a
shell and copied the output, most are X mourns about
invalid window accesses - as kicker just disappered :)

you should get a nice dialog window where KDE tells you
kicker just crashed, this should not happen, where to bug
report blablabla AND A SECOND TAB that will open the
backtrace (i.e. the backtrace is then performed, lasts a
short time)
a backtrace means, that the stack is parsed (using gdb) and
the debugger checks in which function of which class in
which library the crash occured (doesn't work if the lib
was stripped, the output is then incomplete)

[mlgill]

Ok, I think this is the correct backtrace. SUSE may strip some libraries, so let me know if I need to install some extra debug files.

[mlgill]

Logged In: YES
user_id=1452968

Hi Thomas,
I think I have now correctly attached the backtrace. Sorry I
gave you the wrong information the first time...I've not
done this before.

[Thomas Luebking]

Logged In: YES
user_id=931498

thanks, that's the proper backtrace.
also the crash does not occur in baghira directly, but when
calling some ktoolbar function (as there is no toolbar in
the kmenu, i assume)

btw, do you use some patched version of kmenu (i mean sth.
else than a plain popupmenu) as there usually is no
toolbutton in kmenu (why i couldn't reproduce the crash so
far)

[Thomas Luebking]

Logged In: YES
user_id=931498

ok, should be fixed (was a real bug in baghira :)
try out latest cvs (baghira.cpp, rev. 1.56 - sf.net may
need one or two hours to sync the anon servers)

[mlgill]

Logged In: YES
user_id=1452968

Hi Thomas,
Yup, that fixed it--I downloaded and recompiled the latest
CVS. My kmenu worked fine when I restarted X. I think you
figured this out, but I do not have a modified kmenu--just
whatever ships with SUSE.
Thanks! I will post on the sourceforge site to tell anyone
else with this problem to download the latest CVS.