Bug 323873 - kmail adding new filter crashes kontact
Summary: kmail adding new filter crashes kontact
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: commands and actions (show other bugs)
Version: 4.11
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-21 23:52 UTC by guyl
Modified: 2013-08-23 10:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description guyl 2013-08-21 23:52:28 UTC 
Kontact crashes when I try to create a filter on from

Reproducible: Always

Steps to Reproduce:
1. open kontact read message
2. right click create filter
3. everytime the software crashes
Actual Results:  
open kontact read message
2. right click create filter
3. everytime the software crashes


When I open the filter option from the file menu it does not crash
Comment 1 Laurent Montel 2013-08-22 07:12:12 UTC 
Need backtrace
Comment 2 guyl 2013-08-22 15:20:16 UTC 
Hi please guide me in creating a backtrace for you, the auto backtrace app 
does not come up on crash
 -
Guy Lapointe

On Thu - Aug 22, 2013 7:12:12 AM you wrote:
> https://bugs.kde.org/show_bug.cgi?id=323873
> 
> Laurent Montel <montel@kde.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
> CC|                            |montel@kde.org
> 
> --- Comment #1 from Laurent Montel <montel@kde.org> ---
> Need backtrace
Comment 3 Jekyll Wu 2013-08-23 03:54:19 UTC 
run these in konsole :

$ gdb `which kontact`
gdb > set args --nofrk
gdb > run
.....
gdb > bt

See http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB for more information.
Comment 4 guyl 2013-08-23 05:01:03 UTC 
Thx anyway Jekyll but I cannot reproduce it anymore reboot seemed to have 
solved the issue
 -
Guy Lapointe

On Fri - Aug 23, 2013 3:54:19 AM you wrote:
> https://bugs.kde.org/show_bug.cgi?id=323873
> 
> Jekyll Wu <adaptee@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
> Status|UNCONFIRMED                 |NEEDSINFO
>          Resolution|---                         |BACKTRACE
> 
> --- Comment #3 from Jekyll Wu <adaptee@gmail.com> ---
> run these in konsole :
> 
> $ gdb `which kontact`
> gdb > set args --nofrk
> gdb > run
> .....
> gdb > bt
> 
> See
> http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful
> _crash_reports#Retrieving_a_backtrace_with_GDB for more information.
Comment 5 Jekyll Wu 2013-08-23 10:51:01 UTC 
Then close this report for now.