Bug 18396 - kmail does not show 'unread' count in Folder List as default
Summary: kmail does not show 'unread' count in Folder List as default
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
Keywords: 6sta1, UPSTREAM
Depends on:
Blocks: 17523
  Show dependency treegraph
Reported: 2016-05-07 14:23 CEST by Maurice Batey
Modified: 2017-03-16 21:33 CET (History)
2 users (show)

See Also:
Source RPM: kdepim-16.04.0-1.mga6.src.rpm
Status comment:


Description Maurice Batey 2016-05-07 14:23:28 CEST
Description of problem:

Version-Release number of selected component (if applicable):

  Kmail 5.2.0

How reproducible:

Steps to Reproduce:

1. Receive 'n' emails

2. Inbox does not show 'n' on right of folder name 

3. Need to:

    a. R.click in 'Name' section above folder list
    b. In 'View Columns' section, select 'Unread'.

4. A problem can still now arise because - although an 'Unread' column now appears to the right of the folder names - neither that nor the count may be visible if the Message Body window is too far to the left, as the count begins under the 'r' of '"unread"!

Needs to ensure that the count is visible...
Maurice Batey 2016-05-07 19:47:04 CEST

Keywords: (none) => 6sta1

Marja Van Waes 2016-05-08 11:22:39 CEST

CC: (none) => marja11
Blocks: (none) => 17523
Assignee: bugsquad => mageia

Comment 1 Maurice Batey 2016-05-08 14:48:24 CEST
Already reported upstream:


Have appended appropriate remarks...

Keywords: (none) => UPSTREAM

Marja Van Waes 2016-05-08 15:30:41 CEST

See Also: (none) => https://bugs.kde.org/show_bug.cgi?id=362813

Comment 2 Maurice Batey 2016-05-10 19:05:29 CEST
Have now found that if disable the Unread Column, Unread counts now appear appended to Folder names, as of old!

(They did NOT appear before I enabled the Unread Column!)
Comment 3 Nicolas Lécureuil 2016-07-11 18:17:37 CEST
Is it still valid with Plasma 5.7 and KDE Applications 16.04.3 ?
Comment 4 Maurice Batey 2016-07-11 20:14:36 CEST
Well, since disabling the Unread Column (as reported above) I've been at the original status quo.

I raised the bug because it seems to me the Unread Column defaulting to Enabled is going to throw other KMail users, too, who will be puzzled at the apparent disappearance of the familiar 'unread' count.

Their problem could be avoided by changing that default setting...
Comment 5 Maurice Batey 2016-07-13 18:36:06 CEST
There is a secondary problem w.r.t. Unread Count.

If, for example, the "Setting/Config Kmail/Misc/Open this folder on startup" is set to "Inbox", then the Inbox line has a blue background, and the Unread count (normally appearing in black) in that line is in a dull yellow, and very difficult to read against the blue.
   How can that colour  (or the background colour) be changed?

Also, any attempt to change the "Setting/Config Kmail/Misc/Open this folder on startup" folder appears to be IGNORED ( as is the earlier attempt to change the font size of the Message List) and one is stuck with Inbox as the unchangeable default!

[This is with KMail 5.2.3 now, by the way.]
Samuel Verschelde 2016-08-25 16:22:35 CEST

Assignee: mageia => kde

Comment 6 Nicolas Lécureuil 2017-03-14 17:24:30 CET
is it still valid with plasma 5.8.6 ?

CC: (none) => mageia

Comment 7 Maurice Batey 2017-03-14 18:38:36 CET
Problem gone with the new KMail 5.4.3!

(However, 5.4.3 has some new faults:

   o Is quite unstable (also reported on Fedora) - Kmail keeps bombing out...

   o Each time Kmail is started, the headers of the Message List (Subject, From, Date) have been left-justified without gaps, and have to be pulled apart right-wards with the cursor!

Will keep an eye on this, looking for subsquent repairs during Cauldron updates.)
Comment 8 Nicolas Lécureuil 2017-03-16 21:33:08 CET
closing as the main bug is fixed.

Please report new kmail bugs on kde bugzilla, laurent will see them easily

Resolution: (none) => FIXED

Note You need to log in before you can comment on or make changes to this bug.