Bug 282032 - Tools->Addressbook action not working when running KMail in Kontact
Summary: Tools->Addressbook action not working when running KMail in Kontact
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: Git (master)
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-14 17:47 UTC by Daniel Vrátil
Modified: 2017-01-07 21:31 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Vrátil 2011-09-14 17:47:29 UTC
Version:           Git (master) (using Devel) 
OS:                Linux

When running KMail in Kontact (not standalone), the Tools->Address Book menu in composer causes Kontact window to popup, but the default plugin is activated instead of Contactsg.

This does not happen when running KMail as standalone, in that case the KAddressbook is started properly.

Reproducible: Always

Steps to Reproduce:
1) start Kontact and in Settings->Configure Kontact->Kontact Configuration selected any other plugin then Contacts
2) switch to Mail tab
3) open composer
4) click Tools->Address Book

Actual Results:  
Kontact window is moved to foreground and the default plugin chosen in step 1) is activated.

Expected Results:  
Kontact window should pop up to foreground, but Contacts plugin should be activated.
Comment 1 Laurent Montel 2011-10-05 16:36:30 UTC
I can reproduce this bug
Comment 2 Laurent Montel 2011-10-05 16:57:45 UTC
It's a pb with kontact not a problem with kmail
Comment 3 Denis Kurz 2016-09-24 18:23:44 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 21:31:42 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.