By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 429

Summary: Kicker crashes because of Esc key
Product: TDE Reporter: Luc <lucmove>
Component: systemAssignee: Timothy Pearson <kb9vqf>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bugwatch, darrella, mutantturkey, ogldelphi, robxu9
Priority: P5    
Version: 3.5.12 [Trinity]   
Hardware: i386   
OS: Linux   
Compiler Version: TDE Version String:
Application Version: Application Name:

Description Luc 2011-02-03 00:05:43 CST
I press Ctrl+Esc to bring up the application menu - the one on the far left end of the taskbar/Kicker. The menu opens up so I can select an application to run. I change my mind, I don't want to run any application anymore, so instead of selecting an application, I press Esc to dismiss the menu. Kicker crashes.  I can reproduce this bug about nine out of every 10 times.

Kicker restarts itself most of the time. When it doesn't restart itself, I can press a key shortcut to "Run a Command" and launch Kicker from there.

Another way to dismiss the menu is to click on the desktop/elsewhere not on the menu. That makes the menu close without crashing. It's always the Esc key that makes Kicker crash.

In case it's relevant: my Esc and Caps Lock keys are swapped.
Comment 1 Robert Xu 2011-03-12 20:50:35 CST
Hi,

Can you please install the kdebase-kde3-dbg package and save the crash log that comes up when Kicker crashes? This will give us the necessary backtrace that we can use to investigate further.
Comment 2 RJ 2011-08-15 02:08:56 CDT
Can't reproduce this one. Does anybody else?

Debian Squeeze TDE 3.5.12
Comment 3 Calvin Morrison 2011-11-30 09:47:39 CST
I can't reproduce this either. related to the libart issues?
Comment 4 Timothy Pearson 2011-12-19 13:39:47 CST
Never seen this, but the description strongly suggests a libart problem.

Marking as duplicate of 554; if a bactrace shows that this is not the case please reopen this bug report.

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