Bug 193182 - KMail's notifier in system tray ("New massages in") doesn't open mail component of Kontact
Summary: KMail's notifier in system tray ("New massages in") doesn't open mail compone...
Status: RESOLVED DUPLICATE of bug 174977
Alias: None
Product: kontact
Classification: Applications
Component: mail (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-19 05:00 UTC by Darek
Modified: 2009-08-20 21:25 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 Darek 2009-05-19 05:00:59 UTC
Version:            (using KDE 4.2.3)
Compiler:          cc
OS:                Linux (i686) release 2.6.28-12-generic
Installed from:    Ubuntu Packages

When Kontact is set to "always start" with specific component (Kontact's configuration --> Kontact), choosing "New massages in" from menu of KMail's system tray notifier (icon) opens also this component, not the KMail's folder in which these new messages are (that is: not the mail component of Kontact).

In my case choosing "New massages in" from KMail's system tray notifier menu opens Summary component, but one can easily reproduce that with Calendar or any other Kontact's component (setting it as a "always start with" component). The thing is that no matter what component is the starting component for Kontact (and whether anyone is set as such), KMail's system tray notifier (icon) should always open only it's own component (i.e. the mail one, and showing the right folder according to my choice from the list of folders with new massages).

That's a bug (in KDE 3.5 KMail's notifier was working well in this respect).
Comment 1 Matt Hubert 2009-07-03 20:28:19 UTC
Confirmed. (Although I don't remember this working in KDE 3.5 either...)
Comment 2 Christophe Marin 2009-08-20 21:25:51 UTC

*** This bug has been marked as a duplicate of bug 174977 ***