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 1336 - Kickoff menu freezes Kicker panel
Summary: Kickoff menu freezes Kicker panel
Status: RESOLVED DUPLICATE of bug 1491
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 1491
  Show dependency tree / graph
 
Reported: 2012-11-22 22:25 CST by Kris
Modified: 2013-05-08 18:51 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Backtrace of when Kickoff freezes panel (4.97 KB, text/plain)
2012-11-23 07:49 CST, Kris 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kris 2012-11-22 22:25:30 CST 
Switching to the Kickoff menu causes the panel to completely freeze when I click the T icon -- no kickoff menu, no right-click context menu, other applets no longer respond, clock no longer updates. There's no crash.

I have to kill Kicker via TDE System Guard, and re-start it manually. Attempting to click the T icon causes the same symptoms.

I had to switch back to the "classic" menu to restore functionality.
Comment 1 Timothy Pearson 2012-11-22 22:56:41 CST 
When Kicker is frozen, can you please attach gdb to it and generate a backtrace for posting to this report?

You can do this easily by:
1.) Open Konsole
2.) Freeze kicker
3.) Run this command: gdb --pid `pidof kicker`
4.) Once gdb starts, type in: bt <enter>

Thanks!

Tim
Comment 2 Kris 2012-11-23 07:49:32 CST 
Created attachment 1015 [details]
Backtrace of when Kickoff freezes panel
Comment 3 Kris 2012-11-23 07:52:13 CST 
I have attached the backtrace.

I have also checked in top. It appears that the process kicker is using up anywhere from 98% to 105% of my CPU (it's dual-core, hence going over 100%). However, it does not appear to be actually doing anything, even after leaving it sit for several minutes.
Comment 4 Timothy Pearson 2012-11-23 13:50:26 CST 
At first glance it looks like there is some terrible code in kicker/kicker/ui/k_new_mnu.cpp starting at line 3460.  This is probably Bug 508 recurring, and the referenced section of code most likely needs a refactor to eliminate the possibility of incrementing the iterator past the list end.
Comment 5 Timothy Pearson 2013-05-08 18:51:50 CDT 
Marking this as duplicate of Bug 1491, even though this bug was reported first.  This is to simplify bug tracker houskeeping and does not reflect poorly on your bug report.

Thanks for reporting!

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