Bug 252018

Summary: Warn about disable accounts, give directions about what to do.
Product: [Unmaintained] kopete Reporter: Manuel López-Ibáñez <lopezibanez>
Component: generalAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version First Reported In: 1.0.0   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Manuel López-Ibáñez 2010-09-22 10:53:51 UTC
Version:           1.0.0 (using KDE 4.4.2) 
OS:                Linux

I just launched Kopete KDE4 for the first time and both IRC and MSN account do not show up. The console shows:

onnecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kopete(2445)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know "/home/manu/.kde/share/apps/kabc" 
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
kopete(2445)/kdecore (KLibrary) kde4Factory: The library "/usr/lib/kde4/kopete_history.so" does not offer a qt_plugin_instance function.
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/manu/.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.
kopete(2445)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "kopete_msn" '! 
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
kopete(2445)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "kopete_irc" '! 
kopete(2445)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "" '! 


Reproducible: Always




OS: Linux (i686) release 2.6.32-25-generic
Compiler: cc
Comment 1 Pino Toscano 2010-09-22 10:59:15 UTC
There are no more IRC and MSN plugins.
The IRC plugin has no been ported (bug #167884).
The MSN plugin has been replaced by the new WLM one.
Comment 2 Manuel López-Ibáñez 2010-09-22 11:21:05 UTC
So how I move an account from the MSN plugin to the WLM one?

The new kopete looks great but for someone that will not think to run kopete from a console, there is no warning message about their missing accounts, they are just missing and without any hope or help. I can deal with this but I can imagine some people I convinced to use GNU/Linux+KDE will be totally at loss. Why not inform users why their accounts are missing?
Comment 3 Manuel López-Ibáñez 2010-09-22 11:45:16 UTC
I found the answer myself:

   1. ~/.kde/share/config/kopeterc, replace all instances of “MSNProtocol” with “WlmProtocol”.
   2. ~/.kde/share/apps/kopete/contactlist.xml, replace all instances of “MSNProtocol” with “WlmProtocol”.
   3. ~/.kde/share/apps/kopete/, rename directory “msnpictures” to “wlmpictures”
   4. (If using the History plugin) ~/.kde/share/apps/kopete/logs/, rename directory “MSNProtocol” to “WlmProtocol”
   5. (If using the OTR plugin) ~/.kde/share/apps/kopete_otr/privkeys, replace all instances of “MSN Messenger” with “WLM Messenger”
   6. (If using the OTR plugin) ~/.kde/share/apps/kopete_otr/fingerprints, replace all instances of “MSN Messenger” with “WLM Messenger”


From http://www.tolaris.com/2009/08/18/upgrading-from-kubuntu-8-04-to-9-04/

I change this bug to ask to provide some warning to the user and, if the above steps cannot be automatic, at least tell the user about them. The same for the IRC plugin (point to the bug report, perhaps someone may contribute a fix or fund someone to work on it).
Comment 4 Andrew Crouthamel 2018-11-05 03:09:01 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-11-16 05:28:09 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 6 Justin Zobel 2022-12-09 22:13:00 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 7 Bug Janitor Service 2022-12-24 05:23:46 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2023-01-08 05:17:01 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!