Bug 332394

Summary:	cannot accept invitation (configuration issue)
Product:	[Applications] kmail2	Reporter:	Diego Ercolani <diego.ercolani>
Component:	commands and actions	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	stefan.schwarzer
Priority:	NOR
Version:	4.11.5
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	what happens when I try to accept the invitation New crash information added by DrKonqi New crash information added by DrKonqi

Description Diego Ercolani 2014-03-21 09:22:11 UTC

I normally use kmail suite on my workplace, since about 3 months it's for me impossible to accept appointment invitation from kmail.
Today before opening the bug issue I tryied to create a new configuration for kmail and with this brand new configuration it works.

With my working configuration if I click on "accept invitation", kmail simply doesn't react. So as this can be a kind of realword bug, I ask you how can I give the correct informations to address this issue

Reproducible: Always

Comment 1 Diego Ercolani 2014-03-21 09:38:06 UTC

Created attachment 85660 [details]
what happens when I try to accept the invitation

It's a screencapture of the kmail behaviour

Comment 2 Stefan Schwarzer 2014-04-30 19:51:10 UTC

Created attachment 86377 [details]
New crash information added by DrKonqi

kontact (4.11.5) on KDE Platform 4.11.5 using Qt 4.8.6

- What I was doing when the application crashed:
open meeting invitation from exchange server,
try to accept invitation (click on accept)

- Unusual behavior I noticed:
no reply email gets sent
no entry is made in any of the calendars/no popup to ask for a specific calendar
button edge partly turns from solid to dashed
If I exit kontact at this point or later, kontact crashes with the attached backtrace

- Custom settings of the application:
38 kB of custom settings, for invitations mostly the suggested options to achieve MS exchange compatibility

-- Backtrace (Reduced):
#5  0x00007fd40a74b100 in KMime::Content::parent() const () from /usr/lib/libkmime.so.4
#6  0x00007fd40a74b11e in KMime::Content::topLevel() const () from /usr/lib/libkmime.so.4
[...]
#15 0x00007fd414070b1e in QObject::event (this=0x1c61a40, e=<optimized out>) at kernel/qobject.cpp:1194
#16 0x00007fd414a5e6cc in QApplicationPrivate::notify_helper (this=this@entry=0x15134d0, receiver=receiver@entry=0x1c61a40, e=e@entry=0x5af50a0) at kernel/qapplication.cpp:4567
#17 0x00007fd414a64d40 in QApplication::notify (this=0x7fffc14ac850, receiver=0x1c61a40, e=0x5af50a0) at kernel/qapplication.cpp:4353

Comment 3 Stefan Schwarzer 2014-04-30 19:51:14 UTC

Created attachment 86378 [details]
New crash information added by DrKonqi

kontact (4.11.5) on KDE Platform 4.11.5 using Qt 4.8.6

- What I was doing when the application crashed:
open meeting invitation from exchange server,
try to accept invitation (click on accept)

- Unusual behavior I noticed:
no reply email gets sent
no entry is made in any of the calendars/no popup to ask for a specific calendar
button edge partly turns from solid to dashed
If I exit kontact at this point or later, kontact crashes with the attached backtrace

- Custom settings of the application:
38 kB of custom settings, for invitations mostly the suggested options to achieve MS exchange compatibility

-- Backtrace (Reduced):
#5  0x00007fd40a74b100 in KMime::Content::parent() const () from /usr/lib/libkmime.so.4
#6  0x00007fd40a74b11e in KMime::Content::topLevel() const () from /usr/lib/libkmime.so.4
[...]
#15 0x00007fd414070b1e in QObject::event (this=0x1c61a40, e=<optimized out>) at kernel/qobject.cpp:1194
#16 0x00007fd414a5e6cc in QApplicationPrivate::notify_helper (this=this@entry=0x15134d0, receiver=receiver@entry=0x1c61a40, e=e@entry=0x5af50a0) at kernel/qapplication.cpp:4567
#17 0x00007fd414a64d40 in QApplication::notify (this=0x7fffc14ac850, receiver=0x1c61a40, e=0x5af50a0) at kernel/qapplication.cpp:4353

Comment 4 Denis Kurz 2016-09-24 18:08:45 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 5 Denis Kurz 2017-01-07 22:32:33 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.