https://bugs.kde.org/show_bug.cgi?id=351395
--- Comment #9 from Jan-Matthias Braun <[email protected]> --- So, I got it! I don't know how but I used the heuristic approach to track the offender. As the crash happens in slotEditorTextChanged I moved the connect back in the constructor, as is was obviously too early to work when not replying to anything. This worked out and then I just invested the 5 minutes to find the earliest non-offending position in the constructor, which is exactly after the call to readConfig() (and before setupStatusBar(...)). I hope this helps someone who actually knows what is happening. The patch I am going to attach now has the connect a hand full of lines later, as there are a lot of connects already so I think it is fitting. Honestly, it doesn't crash right now so I am happy. :-) -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
