Bug 264763 - kopete freeze at startup/login
Summary: kopete freeze at startup/login
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-29 17:17 UTC by Jan
Modified: 2011-08-31 18:06 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan 2011-01-29 17:17:51 UTC
Version:           unspecified (using KDE 4.6.0) 
OS:                Linux

after the last upgrade to KDE SC 4.6 kopete sometimes freeze after starting it, latest when I change the status to online.
I have to kill kopete, kquitapp doesn't work. At the second start it works most of the time.
Sorry i can't provide more information by now. Please tell me how to get more information for you.

Reproducible: Sometimes




OS: Linux (x86_64) release 2.6.35-25-generic
Compiler: cc
Comment 1 Eugene Shalygin 2011-03-14 16:20:33 UTC
For me it started from 4.6.1 and happens on every login: kopete icon in the tray shows up (in grey colors) and that is all. I can not interact with the icon, only kill helps. Second time it always starts normally
Comment 2 Eugene Shalygin 2011-03-14 19:06:06 UTC
(In reply to comment #1)
It seems to be realted with KWallet. If I open in Konqueror a tab that needs wallet acces, wallet becomes activated and Kopete also returns to live
Comment 3 Valentin Rusu 2011-08-30 07:42:42 UTC
Can you confirm that still reproduces in KDE 4.7.1 or master?
Comment 4 Eugene Shalygin 2011-08-31 13:46:40 UTC
> Can you confirm that still reproduces in KDE 4.7.1 or master?
For me with 4.7.0 it works fine
Comment 5 Valentin Rusu 2011-08-31 18:06:49 UTC
User reports "WorksForMe" and I think my commit
http://commits.kde.org/kde-runtime/23e026094c0bc85c572968573c8d9a3b1e479f52
would have fixed this. Don't hesitate to reopen if that's not true for you.