Bug 157847

Summary: imap: making more than one sibling folders the children of another sibbling folder results in crash
Product: [Unmaintained] kmail Reporter: Jake <kde>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: backtrace to go with bug

Description Jake 2008-02-15 03:35:25 UTC 
Version:           1.9.6 (enterprise 20071221.751182) (using 3.5.8 "release 44.1" , openSUSE )
Compiler:          Target: x86_64-suse-linux
OS:                Linux (x86_64) release 2.6.22.17-0.1-default

I wanted to shorten my list of imap folders so i created a new folder called archive and tried to move 2 sibling folders into the archive folder. The move worked fine, I watched the progress messages when you click the up arrow in the lower right.

Those messages even said it was removing the folders. The folders even disappeared but then almost instantly reappeared in my listing. 

Seeing this I decided to shut down kmail and restart it, hoping the fresh look at the folder list on the server would correct its local cache(it does indeed). However, upon closing kmail, it crashes.

This does not happen if you move folders one at a time and it does not appear to be a fluke as I am able to reproduce it when moving other folders in the same fashion. I will attach a backtrace momentarily.

please let me know If you need anything else.
Comment 1 Jake 2008-02-15 04:00:33 UTC 
Created attachment 23580 [details]
backtrace to go with bug

i did a test case by creating an archive folder and an aaaaaa and aaabbb. I
sent myself 4 test emails then moved 2 into each aaa... folder. then moved
those folders into the archive folder, oddly this time, only one of the folders
was incorrectly displayed in both its old and new locations. however kmail
still crashed upon closing it. the folders were correctly listed upon
restarting.
Comment 2 Thomas McGuire 2008-02-15 16:20:55 UTC 
From the backtrace and the symptoms, I guess this is the same as bug 143627.

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