Version: 1.9.1 (using KDE 3.5.1, Debian Package 4:3.5.1-2 (testing/unstable)) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.15 I use Kontact with Kmail and Kaddressbook embebed into it. I have groups in Kaddressbook, so some of my contacts are "Family", "Friends"... I open Kontact and select Kmail and create new email. In the right of recipients I press "Select..." so a window appear and I can select the recipients. In the top there is a "List" button which shows me: All Distribution lists Recent recipients Selected recipients So there is a bug because there don't appear my Kaddressbook groups. In fact, I close this window and go back to Kontact and select Kaddressbook, just it. After that I go again to the compose window, press "Select..." and the window appears again, but in this time the List button shows me: All Distribution lists Recent recipients Selected recipients Family Friends (all my groups) ... In fact, I can't get to see them always, in many cases is impossible to see them. I think with previous versions this bug didn't occur.
Please, could someone confirm this bug? I'd like to add that now it fails ALWAYS, so it's not possible for me to filter my contats by group when sending an email because the groups just don't appear in the recipient select window. This bug is making Kmail very unusable for me. Please, could someone confirm this bug?
I can confirm this bug. The groups from kaddressbook do not show up in kmail. even the "All" field is empty. And i created 2 contacts in kaddressbook, with email adresses, names. This is on kde 3.5.1-5 that came with fedora5, but the bug is older, i just thought the fedora install was "tired", but the new install had the bug too, so... Anyway, it is possible to select in kaddressbook the contacts to email, right-clik -> send email message. And it works.
This might be the same problem as bug 120532. In my case too, even the "All" field is empty. I´m using KDE 3.5.1 on opensuse10.0. Peter
Could be related to bug 121337. 121337 is fixed in KDE 3.5.2 which is due out any time now - when it's out, could you upgrade and see whether *this* bug is fixed too.
It is now working for me.
*** This bug has been marked as a duplicate of 121337 ***