Bug 196452 - lancelot is froozing on click when kopete is open.
Summary: lancelot is froozing on click when kopete is open.
Status: RESOLVED DUPLICATE of bug 196809
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-lancelot (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Ivan Čukić
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-14 11:14 UTC by krun
Modified: 2009-06-21 13:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description krun 2009-06-14 11:14:30 UTC
Version:            (using KDE 4.2.90)
OS:                Linux
Installed from:    Ubuntu Packages

When i click on lancelot menu and kopete is open (can by only in tray).
All panel became frozen and i must restart plasma-desktop or close kopete, then everything works good to time when i do this again. I'm not sure but i thing that lancelot is broken after last upgrade, befor (after upgrade to beta2 on kubuntu (this broken update without all packages) before upgrade lancelot) everything works great.
Comment 1 Ivan Čukić 2009-06-14 11:18:38 UTC
Please try whether it is sufficient just to call 'killall lancelot' to unlock plasma.
Comment 2 Ivan Čukić 2009-06-14 15:03:57 UTC
Can you reproduce it always (after log-out / log-in)? (since "It works for me TM")
Comment 3 krun 2009-06-14 22:13:51 UTC
Ok, as i observe problem exists when i have error in kopete (when kopete can't connect to skype). It's probably kopete problem, but not only:)
Comment 4 Bastien Jansen 2009-06-18 18:05:41 UTC
Same kind of problem here. After a few hours running (7 or 8hrs), lancelot began freezing plasma-desktop. After approx. 20s I get a white rectangle (instead of the menu) that stays on top of other windows.

If I close kopete, it still happens after a killall lancelot and a plasma-desktop restart... 

Maybe this is related to #196809 ?
Comment 5 Ivan Čukić 2009-06-21 13:17:45 UTC
Marking as duplicate so that all discussion goes to the bug 196809

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