If you enable the option to export your custom MSN emoticons, your contacts using MSN Live won't receive them. The problem has been solved in SVN already. The patch is also available. I modified kdenetwork-3.5.7-r1.ebuild to include the patch, then re-emerged kdenetwork. The patch was applied without problems, the package was compiled and installed. The newly compiled Kopete is now able to send custom emoticons (it was verified with two MSN Live users). Reproducible: Always Steps to Reproduce: 1. Enable "Export custom emoticons" for the MSN protocol. 2. Send a custom emoticon. Actual Results: The contact reports an empty message. Expected Results: The contact should see the custom emoticon.
Created attachment 132707 [details, diff] Patch to fix the bug
Created attachment 132708 [details] Modified ebuild to include patch
Thanks for reporting. However, I have some questions: It seems your patch contains the changes applied in upstream's r704400 and r717106. What does the latter have to do with this issue? If the former is supposed to fix the emoticons issue, why is the upstream bug (http://bugs.kde.org/show_bug.cgi?id=129929) still opened?
Tomorrow, KDE 3.5.8 will be tagged and released about a week later. If this is fixed in upstream's svn, it should be in it. We'll keep this bug open for now to test with 3.5.8 but I don't see us fixing it in 3.5.7.
> It seems your patch contains the changes applied in upstream's r704400 and > r717106. What does the latter have to do with this issue? Nothing, it seems. I just used the patch you can find in the URL link of this bug report, which solved this problem. I ignore why they mixed two, apparently, unrelated things in the same patch and reported that it fixed only one. > If the former is supposed to fix the emoticons issue, why is the upstream bug > (http://bugs.kde.org/show_bug.cgi?id=129929) still opened? That's a very good question, and I completely ignore the answer. It should have been closed when they committed those changes. Perhaps the developer forgot to close it? > Tomorrow, KDE 3.5.8 will be tagged and released about a week later. If this is > fixed in upstream's svn, it should be in it. I'm aware 3.5.8 is coming soon. Thing is that it's not a bug only present in 3.5.7, but it also exists in previous versions (the bug report in KDE shows that it was reported since 3.5.2). I just checked the ebuilds and 3.5.5 is the latest stable version in portage, both 3.5.6 and 3.5.7 are marked ~ for all architectures. I don't feel like downgrading KDE just to test the patch in 3.5.5 and 3.5.6, but it should solve the problem there too. All I wanted to do was to share the patch. After all, adding a patch to any package in portage is quite easy. > We'll keep this bug open for now to test with 3.5.8 but I don't see us fixing > it in 3.5.7. I will upgrade to 3.5.8 when it comes out, so I won't need the patch anymore, neither anyone upgrading to it. It's not a critical bug, so it's OK if you don't include it for previous versions of KDE.
(In reply to comment #5) >> Tomorrow, KDE 3.5.8 will be tagged and released about a week later. >>If this is fixed in upstream's svn, it should be in it. > I just checked the ebuilds and 3.5.5 is the latest stable version in portage, > both 3.5.6 and 3.5.7 are marked ~ for all architectures. You should *really* sync. 3.5.7 has been marked stable for quite some time now. :-) > All I wanted to do was to share the patch. After all, > adding a patch to any package in portage is quite easy. Yes, thanks, don't get me wrong: It's nice of you to share it. It's just that on the upstream bug people still complain that it doesn't work even with the patch included. I'm going to take a look at this once 3.5.8 is in Portage.
This is fixed in 3.5.8.
