Bug 272973 - inconsistent display after switching to a stand-alone application
Summary: inconsistent display after switching to a stand-alone application
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.4.10
Platform: openSUSE Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-10 21:29 UTC by Christopher Yeleighton
Modified: 2017-01-07 22:44 UTC (History)
0 users

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 Christopher Yeleighton 2011-05-10 21:29:05 UTC
Version:           4.4.10 (using KDE 4.6.0) 
OS:                Linux

Kontact displays the content of the previous application after switching to a stand-alone application while marking the current application as active

Reproducible: Always

Steps to Reproduce:
  1. Launch KMail as a separate application.
  2. Launch Kontact.
  3. Tell Kontact to display the Task List.
  4. Tell Kontact to display the Mail.
  5. Use the window manager to switch back to Kontact.

Actual Results:  
  3. Active appliaction: Task List; application content: Task List.
  4. Kontact activates KMail.
  5. Active application: Mail; application content: Task List (??)

Expected Results:  
  5. Active application: Task List; application content: Task List.

OS: Linux (x86_64) release 2.6.37.6-0.5-desktop
Compiler: gcc

Workaround:
  6. Tell Kontact to switch to the Task List.
Comment 1 Denis Kurz 2016-09-24 19:28: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 kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:44:14 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.