Kopete is very slow to start (about 10 minutes !)

Bug #99815 reported by Nicolas DERIVE
6
Affects Status Importance Assigned to Milestone
KDE Network
Invalid
Medium
kdenetwork (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: kopete

Kopete is very slow to start every time, it takes between 8 to 10 minutes to load. When launching it in a terminal, I get the thing in the file joined (because it is big !)

Revision history for this message
Nicolas DERIVE (kalon33) wrote :
Revision history for this message
Nicolas DERIVE (kalon33) wrote :

I've 3 msn accounts and 3 jabber ones, one IRC and one for kopete testing. I use Feisty.

Revision history for this message
Anthony Mercatante (tonio) wrote :

Probably an issue with your own settings, as nobody already repoted this kind of error.
What happens if you remove your ~/.kde/share/config/kopeterc and ~/.kde/share/apps/kopete datas and reconfigure kopete ?

Changed in kdenetwork:
status: Unconfirmed → Needs Info
Revision history for this message
Torsten Knodt (torsknod) wrote :

My kopete start is also very slow, also when opening a new chat window.
As a hint, I found two causes so far.
1.) my IMAP addressbook, requiring kmail to start first
2.) the enabled history plugin

Revision history for this message
Hans Harhoff Andersen (hansharhoff) wrote :

My kopete is also very slow to start. I have disabled the history plugin. Still slow. There is no output in terminal(at all)

Revision history for this message
Matt Rogers (mattr-kde) wrote :

turn off the statistics plugin if it's enabled.
addressbook associations in the contact list can also make kopete slower.

Revision history for this message
Alberto Torres (kungfoobar) wrote :

It is definitely the statistics plugin!
1 minute 30 to just open before it tries to connect. This time is reduced to almost nothing after disabling the plugin.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for kdenetwork (Ubuntu) because there has been no activity for 60 days.]

Daniel Hahler (blueyed)
Changed in kdenetwork (Ubuntu):
status: Invalid → Triaged
importance: Undecided → Medium
Revision history for this message
Daniel Hahler (blueyed) wrote :

Re-opening. I'm very much experiencing this currently:
With statistics plugin enabled: 1:20 to start, without:

real 0m3.448s
user 0m0.036s
sys 0m0.012s

Activating the statistics plugin already blocks the UI.
When starting with the plugin enabled, I'm getting the following before the (first) forking alone:
real 0m25.386s
user 0m0.036s
sys 0m0.012s

STDERR:

$ time kopete
kopete(4696) Kopete::IdentityManager::load: Created identity "CBNk7T72Y1"
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kopete(4696) Kopete::IdleTimer::IdleTimer: Using platform idle timer
kopete(4696)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know "/home/daniel/.kde/share/apps/kabc"
kopete(4696)/kdecore (KLibrary) kde4Factory: The library "/usr/lib/kde4/kopete_history.so" does not offer a qt_plugin_instance function.
Calling appendChild() on a null node does nothing.
kopete(4695): Communication problem with "kopete" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "

real 0m25.386s
user 0m0.036s
sys 0m0.012s
daniel@base [es:255] { ~ }
$ QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/daniel/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
kopete(4696)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "" '!
Calling appendChild() on a null node does nothing.
kopete(4696) Kopete::AccountManager::setOnlineStatus: category: 2 status title: "Online" status message: ""
Unknown signature value: 795
kopete(4696) OscarStatusManager::onlineStatusOf: Creating Kopete::OnlineStatus for ExtStatus, internal status: 8198
kopete(4696) OscarStatusManager::onlineStatusOf: Creating Kopete::OnlineStatus for ExtStatus, internal status: 8198
kopete(4696) OscarStatusManager::onlineStatusOf: Creating Kopete::OnlineStatus for ExtStatus, internal status: 8196
kopete(4696) OscarStatusManager::onlineStatusOf: Creating Kopete::OnlineStatus for ExtStatus, internal status: 8198
kopete(4696) OscarStatusManager::onlineStatusOf: Creating Kopete::OnlineStatus for ExtStatus, internal status: 8196
kopete(4696) OscarStatusManager::onlineStatusOf: Creating Kopete::OnlineStatus for ExtStatus, internal status: 8196

I can provide strace output (via "strace -f -t -o").

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!

Changed in kdenetwork (Ubuntu):
status: Triaged → Invalid
Changed in kdenetwork:
status: Unknown → Invalid
Changed in kdenetwork:
status: Invalid → Unknown
Changed in kdenetwork:
importance: Unknown → Medium
Changed in kdenetwork:
status: Unknown → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.