Description of problem: KMess is able to login to live service, but do not show any contact. The contact list is empty. It is a known problem in kmess community and a patch is available here http://kmess.org/board/viewtopic.php?f=4&t=20549 Version-Release number of selected component (if applicable): KMess 2.0.6.1 How reproducible: Always Steps to Reproduce: 1. Login into KMess 2. There is no contact available :( Note : this bug may also affect Mageia 1. The patch can be backported in 1.
Hi, thanks for reporting this bug. As there is no maintainer for this package I had the committers in CC.
Keywords: (none) => PATCH, UPSTREAMCC: (none) => dmorganec, oliver.bgrSource RPM: (none) => kmess
Yes, the same in Mageia 1. There is a patched package in Mandriva already. http://lists.mandriva.com/bugs/2011-11/msg00615.php
CC: (none) => jyri2000
Hi, The same is here in Mageia1 64bit. Just wanted to try this messenger, but was not able to add contacts to the list, new groups can't be created either. If there is a patched version for Mageia1, will it be in backports? Thank you.
CC: (none) => schlecht
still no maintainer for kmess
CC: (none) => marja11
(In reply to comment #2) > Yes, the same in Mageia 1. > There is a patched package in Mandriva already. > http://lists.mandriva.com/bugs/2011-11/msg00615.php cc'ing Funda, who committed kmess in Mandriva a lot
(In reply to comment #5) > (In reply to comment #2) > > Yes, the same in Mageia 1. > > There is a patched package in Mandriva already. > > http://lists.mandriva.com/bugs/2011-11/msg00615.php > > cc'ing Funda, who committed kmess in Mandriva a lot now really cc'ing :/
CC: (none) => fundawang
Wow, Funda, you are really good, I saw you already committed the fixed package, thx a lot. I hope it'll be let in, despite freeze
Assignee: bugsquad => fundawang
oh I don't have seen this br, for info we have one for mga1 5709, so no need to open another one, I will add it for the qa, thanks funda
Assignee: fundawang => bugsquad
assigning to Funda again, because I now understand it was accidentally re-assigned to bugsquad. It can be closed when the update is pushed
The bug is corrected in chauldron Maybe this bug should be closed as it do not concern 1 ?
(In reply to comment #10) > The bug is corrected in chauldron > Maybe this bug should be closed as it do not concern 1 ? Yes indeed, thanks for the reminder.
Status: NEW => RESOLVEDResolution: (none) => FIXED