Bug 317259 - trash folder is invisible
Summary: trash folder is invisible
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: folders (show other bugs)
Version: 4.10.1
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-24 07:48 UTC by ihor
Modified: 2017-01-07 22:33 UTC (History)
2 users (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 ihor 2013-03-24 07:48:32 UTC
The common trash folder seems to be invisible or absent by default.

Reproducible: Always

Steps to Reproduce:
1. Just make a first-time start of KMail agent and take a look at the folders tree.
Actual Results:  
The common trash folder seems to be invisible or absent by default unless you create it on your own in the folders tree and restart kMail then. After restart KMail recognizes it correctly as the pertinent trash icon appears.  It's important to mention that while creating the trash folder one should use only small letters. 

Expected Results:  
The trash folder (like other system folders) must be functional and visible for a user right away after  KMail has been launched.
Comment 1 Tobias Leupold 2013-04-17 18:11:16 UTC
Same here on Gentoo with KMail 4.10.1. Using a completely new user, no Trash folder is visible when starting KMail for the first time.
Comment 2 dorian.soergel 2013-05-27 16:40:54 UTC
How could I fix it? Is it possible to recover the older folders in the trash?
Comment 3 Denis Kurz 2016-09-24 18:23:05 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 22:33:36 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.