Version: 0.80.2 (using KDE 4.3.2) Compiler: gcc 4.4.1 Using built-in specs. Target: x86_64-manbo-linux-gnu. OS: Linux Installed from: Mandriva RPMs I'm trying to import my several years of pidgin IM history using kopete "Import History"/"Get History From Pidgin" function but it is being unsuccessful. No history is shown or imported and in the details text area, *many* "WARNING" messages are shown. One "WARNING" message example is the following: "WARNING: Cannot find matching account for example@hotmail.com (msn)." I have this account configured in kopete but the protocol is not called "msn" but "WLM Messenger" (or something similar). It would be nice if the import function recognized those two protocol are the same or at least asked the user to what account, if any, that history belonged to. Even if that account does not exist any more import it any way. It is a IM *history* log after all. Another "WARNING" message example is the following: "WARNING: Cannot find 000000000 (icq) in your contact list. Found logs will not be imported." That contact does not exist *now* but it existed in the past, obviously. It would be very nice to import the history of contact that, now, don't exist. It is a IM *history* log after all. Another "WARNING" message example is the following: "WARNING: Cannot parse date "(2008-05-29 09:45:32)". You may want to edit the file containing this date manually. (Example recognized date strings: "05/31/2008 15:24:30".)" I get a huge number of these warnings. The data format in the pidgin history log is not being recognized by the import function. The import function must find a way to recognize different date formats since they change depending on the localization used. Ask the user if necessary.
http://reviewboard.kde.org/r/2334/ mostly fixes this bug (I hope). Things still to be done: - asking user for datetime format if not recognized ("(yyyy-MM-dd hh:mm:ss)" already added) - importing logs for non-existing contacts (requires more work)
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!
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!
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!
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!
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!