Bug 270280 - Crash on manual filtering of DIMAP account
Summary: Crash on manual filtering of DIMAP account
Status: RESOLVED DUPLICATE of bug 270281
Alias: None
Product: kmail2
Classification: Applications
Component: filtering (show other bugs)
Version: Git (master)
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-07 07:20 UTC by Ryan Rix
Modified: 2011-04-07 07:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Rix 2011-04-07 07:20:35 UTC
Version:           Git (master) (using Devel) 
OS:                Linux

Application: kmail (2.0.89)
KDE Platform Version: 4.6.41 (4.7 >= 20110106) (Compiled from sources)
Qt Version: 4.7.1
Operating System: Linux 2.6.35.11-83.fc14.x86_64 x86_64
Distribution: "Fedora release 14 (Laughlin)"

-- Information about the crash:
- What I was doing when the application crashed:
At the end of a manual filtering operation KMail will crash with the attached backtrace. manual and automatic filtering on a different account works perfectly fine, however. As far as I can tell from the backtrace, it's crashing in the progress bar code, but other items which use a progress bar work just fine. Looks like it's emitting a signal which is caught by itself or something that's causing the codepath to repeat until the stack goes snap.

- Unusual behavior I noticed:
Well, automatic filtering doesn't work and manual filtering is janky. not exactly sure what is going on, but it seems related to https://bugs.kde.org/show_bug.cgi?id=257984 . This filtering bug could be triggering some issue in this code.

- Custom settings of the application:
dIMAP account

KMail
Version 2.0.89
Using KDE Development Platform 4.6.41 (4.7 >= 20110106)

I'll rebuild trunk tonight, I think, have to clear out more disk space, first though...

The crash can be reproduced every time.


Reproducible: Always
Comment 1 Ryan Rix 2011-04-07 07:33:24 UTC
Stupid BZ timed out and didn't bother telling me it submitted this twice

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