Bug 278189

Summary:	manual folder sorting dont work on top level
Product:	[Applications] kmail2	Reporter:	Hynek "rADOn" Fabian <radonek>
Component:	folders	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	creideiki+kdebugs, dmitry.torokhov, kollix, montel
Priority:	NOR
Version:	2.1.1
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:

Description Hynek "rADOn" Fabian 2011-07-21 09:59:04 UTC

Version:           2.1.1 (using KDE 4.6.4) 
OS:                Linux

With folder sorting set to manual, I can drag&move folders within subfolder. However, top-level folders wont budge. This happens for both builtin (inbox, trash, sent mail) or hand-created folders.

Reproducible: Always

Steps to Reproduce:
Right click on folders header, select sort order "Manually", pick "inbox", drag it up or down.

Actual Results:  
Depends. For IMAP folders (tried gmail, exchange), nothing happens. For local folders, sometimes nothing, sometimes horizontal line is sometimes drawn where drop would end (correct), and on button release context menu pops asking for either "copy" (WTF?) or "cancel". Selecting "copy", folder is then 1) moved where wanted, 2) moved elsewhere or 3) not moved at all. Depends on some strange but consistent rules, I only figured out that move to top works and move to bottom allways fail.

Expected Results:  
See the horizontal line, release button, folder is moved.

Comment 1 Dmitry Torokhov 2011-11-28 21:18:42 UTC

Still happens here with 4.7.3.

Comment 2 Laurent Montel 2012-02-23 07:39:01 UTC

I confirm it

Comment 3 Denis Kurz 2016-09-24 18:01:38 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:54:41 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.