Bug 279113 - akonadi crash on ssl error
Summary: akonadi crash on ssl error
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 4.10
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords: triaged
: 282722 283838 289308 292655 294424 296728 296856 301881 302459 304110 309788 310243 311586 317386 322181 324442 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-08-02 00:08 UTC by Malcolm Lashley
Modified: 2018-10-29 08:19 UTC (History)
27 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (6.89 KB, text/plain)
2011-10-20 11:38 UTC, Forger
Details
New crash information added by DrKonqi (17.52 KB, text/plain)
2011-12-03 17:34 UTC, Gunnar R. Bartels
Details
New crash information added by DrKonqi (4.53 KB, text/plain)
2011-12-16 12:51 UTC, bosyber
Details
New crash information added by DrKonqi (5.91 KB, text/plain)
2012-01-02 15:59 UTC, Dave Corrie
Details
New crash information added by DrKonqi (6.15 KB, text/plain)
2012-01-10 11:12 UTC, karaluh
Details
New crash information added by DrKonqi (6.51 KB, text/plain)
2012-06-11 09:57 UTC, Martin Kampas
Details
New crash information added by DrKonqi (12.52 KB, text/plain)
2013-03-11 22:28 UTC, GGG
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Malcolm Lashley 2011-08-02 00:08:55 UTC
Application: akonadi_imap_resource (4.7)
KDE Platform Version: 4.7.00 (4.7.0) (Compiled from sources)
Qt Version: 4.7.3
Operating System: Linux 2.6.39-gentoo x86_64
Distribution: "Gentoo Base System release 2.0.3"

-- Information about the crash:
- What I was doing when the application crashed:
kmail2 was chugging thru being busy and generally unresponsive after I restarted after a switch from the mysql backend to the sqlite backend. I left it unattended - about an hour later I returned to find the 'certificate check' popup for the ssl connection to my IMAP server, upon clicking 'accept permanently' (why is this never permanent - I don't know ;-) - akonadi crashed. Kmail2 remains unresponsive.

- Custom settings of the application:
3rd restart after recently switching from mysql backend to sqlite backend after the 4.7.0 upgrade.

-- Backtrace:
Application: Akonadi Resource (akonadi_imap_resource), signal: Segmentation fault
[KCrash Handler]
#6  0x00007fafbce8bed0 in vtable for Akonadi::CollectionFetchJob () from /usr/lib64/libakonadi-kde.so.4
#7  0x00007fafbc4c049d in QMetaObject::invokeMethod (obj=0x94c680, member=<value optimized out>, type=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1138
#8  0x00007fafbb187887 in invokeMethod (this=0x9e50a0, errorData=<value optimized out>) at /usr/include/qt4/QtCore/qobjectdefs.h:424
#9  KIMAP::SessionPrivate::handleSslError (this=0x9e50a0, errorData=<value optimized out>) at /var/tmp/portage/kde-base/kdepimlibs-4.7.0/work/kdepimlibs-4.7.0/kimap/session.cpp:121
#10 0x00007fafbb18a182 in KIMAP::Session::qt_metacall (this=0x9a6a90, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fafa400deb0) at /var/tmp/portage/kde-base/kdepimlibs-4.7.0/work/kdepimlibs-4.7.0_build/kimap/session.moc:117
#11 0x00007fafbc4cb03a in QObject::event (this=0x9a6a90, e=<value optimized out>) at kernel/qobject.cpp:1217
#12 0x00007fafbb8a5644 in QApplicationPrivate::notify_helper (this=0x6a1f90, receiver=0x9a6a90, e=0x7fafa41f7cd0) at kernel/qapplication.cpp:4462
#13 0x00007fafbb8aa1ca in QApplication::notify (this=<value optimized out>, receiver=0x9a6a90, e=0x7fafa41f7cd0) at kernel/qapplication.cpp:4341
#14 0x00007fafb99fda86 in KApplication::notify (this=0x7fffb2f7fd70, receiver=0x9a6a90, event=0x7fafa41f7cd0) at /var/tmp/portage/kde-base/kdelibs-4.7.0/work/kdelibs-4.7.0/kdeui/kernel/kapplication.cpp:311
#15 0x00007fafbc4b6e5b in QCoreApplication::notifyInternal (this=0x7fffb2f7fd70, receiver=0x9a6a90, event=0x7fafa41f7cd0) at kernel/qcoreapplication.cpp:731
#16 0x00007fafbc4ba614 in sendEvent (receiver=0x0, event_type=0, data=0x67fec0) at kernel/qcoreapplication.h:215
#17 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x67fec0) at kernel/qcoreapplication.cpp:1372
#18 0x00007fafbc4e1ba3 in sendPostedEvents (s=0x6a6140) at kernel/qcoreapplication.h:220
#19 postEventSourceDispatch (s=0x6a6140) at kernel/qeventdispatcher_glib.cpp:277
#20 0x00007fafb784f6ae in g_main_dispatch (context=0x6a50e0) at gmain.c:2441
#21 g_main_context_dispatch (context=0x6a50e0) at gmain.c:3014
#22 0x00007fafb784fe98 in g_main_context_iterate (context=0x6a50e0, block=1, dispatch=1, self=<value optimized out>) at gmain.c:3092
#23 0x00007fafb785012d in g_main_context_iteration (context=0x6a50e0, may_block=1) at gmain.c:3155
#24 0x00007fafbc4e1d3f in QEventDispatcherGlib::processEvents (this=0x69eb20, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#25 0x00007fafbb94ab0e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#26 0x00007fafbc4b6222 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#27 0x00007fafbc4b6464 in QEventLoop::exec (this=0x7fffb2f7fce0, flags=...) at kernel/qeventloop.cpp:201
#28 0x00007fafbc4ba8cb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#29 0x00007fafbcbab336 in Akonadi::ResourceBase::init (r=0x78aba0) at /var/tmp/portage/kde-base/kdepimlibs-4.7.0/work/kdepimlibs-4.7.0/akonadi/resourcebase.cpp:393
#30 0x0000000000418018 in init<ImapResource> (argc=<value optimized out>, argv=<value optimized out>) at /usr/include/akonadi/resourcebase.h:188
#31 main (argc=<value optimized out>, argv=<value optimized out>) at /var/tmp/portage/kde-base/kdepim-runtime-4.7.0/work/kdepim-runtime-4.7.0/resources/imap/imapresource.cpp:598

Reported using DrKonqi
Comment 1 Kevin Ottens 2011-09-17 13:50:36 UTC
Looks like some sort of database corruption issue (in which case the ssl error would just be a trigger, the crash itself is in the collection fetch job). Reassigning to the server component.
Comment 2 Forger 2011-10-20 11:38:48 UTC
Created attachment 64733 [details]
New crash information added by DrKonqi

akonadi_imap_resource (4.7) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4

- Unusual behavior I noticed:

Once for a while a message pops out, stating that "There is currently no session to the IMAP server available" - sometimes it results in a crash and sometimes a SSL certificate dialog is shown.
Closing the dialog with 'remember forever' option doesn't work; the dialog keeps appearing on every subsequent connection attempt.

- Custom settings of the application:
This particular account is using a self-signed certificate.

-- Backtrace (Reduced):
#8  0x00007fa1a3378567 in KIMAP::SessionPrivate::handleSslError(KSslErrorUiData const&) () from /usr/lib/libkimap.so.4
#9  0x00007fa1a337ae72 in KIMAP::Session::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkimap.so.4
#10 0x00007fa1a4753a5e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x00007fa1a3aed424 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#12 0x00007fa1a3af2291 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
Comment 3 Christophe Marin 2011-11-18 00:06:46 UTC
*** Bug 282722 has been marked as a duplicate of this bug. ***
Comment 4 Christophe Marin 2011-11-18 00:06:46 UTC
*** Bug 283838 has been marked as a duplicate of this bug. ***
Comment 5 Gunnar R. Bartels 2011-12-03 17:34:39 UTC
Created attachment 66341 [details]
New crash information added by DrKonqi

akonadi_imap_resource (4.7) on KDE Platform 4.7.2 (4.7.2) "release 5" using Qt 4.7.4

- What I was doing when the application crashed:

After a SSL-Certificate Error popped up, I decided to go on. When I was asked if I wanted to permanently accept the certificate, it crashed.

-- Backtrace (Reduced):
#7  0x00007fccdfd451d7 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., member=<optimized out>, obj=<optimized out>) at /usr/include/QtCore/qobjectdefs.h:426
#8  KIMAP::SessionPrivate::handleSslError (this=0x8732c0, errorData=<optimized out>) at /usr/src/debug/kdepimlibs-4.7.2/kimap/session.cpp:121
#9  0x00007fccdfd5e732 in KIMAP::Session::qt_metacall (this=0x8c5150, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fcca000fcf0) at /usr/src/debug/kdepimlibs-4.7.2/build/kimap/session.moc:117
#10 0x00007fcce10d414a in QObject::event (this=0x8c5150, e=<optimized out>) at kernel/qobject.cpp:1226
#11 0x00007fcce048cbe4 in notify_helper (e=0x7fcca00196d0, receiver=0x8c5150, this=0x6afb00) at kernel/qapplication.cpp:4481
Comment 6 bosyber 2011-12-16 12:51:36 UTC
Created attachment 66808 [details]
New crash information added by DrKonqi

akonadi_imap_resource (4.7) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4

- What I was doing when the application crashed:
waiting for kmail to update my "LogistiQ" IMAP mail, I click on accept cetificate forever (does it never take hold?), crash.


- Custom settings of the application:
The certificate is from "banan.cz"; my email is found at imap.logist-iq.eu. But that's a site hosted by banan.cz (including email), without a separate certificate as of yet, and thus akonadi justly asks if it should be trusted, but it seems to fail to
accept to do that permanently.

-- Backtrace (Reduced):
#7  0x00007f966672d567 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., member=<optimized out>, obj=<optimized out>) at /usr/include/qt4/QtCore/qobjectdefs.h:426
#8  KIMAP::SessionPrivate::handleSslError (this=0x1ecb850, errorData=<optimized out>) at ../../kimap/session.cpp:121
#9  0x00007f966672fe72 in KIMAP::Session::qt_metacall (this=0x1f5e670, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7f96480233e0) at ./session.moc:117
#10 0x00007f9667b09a5e in QObject::event (this=0x1f5e670, e=<optimized out>) at kernel/qobject.cpp:1217
#11 0x00007f9666ea3424 in notify_helper (e=0x7f9648023390, receiver=0x1f5e670, this=0x1d84fe0) at kernel/qapplication.cpp:4486
Comment 7 Christophe Marin 2011-12-18 20:53:44 UTC
*** Bug 289308 has been marked as a duplicate of this bug. ***
Comment 8 Christophe Marin 2011-12-18 20:55:13 UTC
from bug 289308

-- Information about the crash:
- What I was doing when the application crashed: i was creating a new pop3
account, and identifying ssl type accepted automatically.

-- 
from bug 283838

was fetching mails with kmail2 from an imap account with a self-signed
certificate. Akonadi informed me that this certificate is not valid while I was
away. And when I was back I choose accept permanently and got the crash.
I would assume due to the delay between asking about the certificate and
accepting it, some session timed out or something. Though I have no clue of the
architecture of akonadi.

-- 
from bug 282722
* akonadi pops a message that there's an ssl certificate issue (wrong server
address)
* no from here you can do: continue, settings, cancel. choose settings
  * correct the server address
  * apply the new settings
* now hit cancel and not continue
* wait for akonadi to die
Comment 9 Johan Erlands 2011-12-21 15:49:08 UTC
I have had this problem until I got 4.7.3, very strange. Maybe it remembers the certificate (I have used the certificate with older versions without problem).
Comment 10 Dave Corrie 2012-01-02 15:59:14 UTC
Created attachment 67342 [details]
New crash information added by DrKonqi

akonadi_imap_resource (4.7) on KDE Platform 4.7.2 (4.7.2) "release 5" using Qt 4.7.4

- What I was doing when the application crashed:

Whilst checking for new messages on an IMAP account in kmail an SSL cert error occurred. I elected to trust the cert forever and the crash followed.

-- Backtrace (Reduced):
#7  0x00007f4830be31d7 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., member=<optimized out>, obj=<optimized out>) at /usr/include/QtCore/qobjectdefs.h:426
#8  KIMAP::SessionPrivate::handleSslError (this=0xae16f0, errorData=<optimized out>) at /usr/src/debug/kdepimlibs-4.7.2/kimap/session.cpp:121
#9  0x00007f4830bfc732 in KIMAP::Session::qt_metacall (this=0x9c4380, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7f4810017370) at /usr/src/debug/kdepimlibs-4.7.2/build/kimap/session.moc:117
#10 0x00007f4831f7214a in QObject::event (this=0x9c4380, e=<optimized out>) at kernel/qobject.cpp:1226
#11 0x00007f483132ac34 in notify_helper (e=0x7f48100171b0, receiver=0x9c4380, this=0x6aa360) at kernel/qapplication.cpp:4481
Comment 11 karaluh 2012-01-10 11:12:26 UTC
Created attachment 67651 [details]
New crash information added by DrKonqi

akonadi_imap_resource (4.7) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4

- What I was doing when the application crashed:
...................................

-- Backtrace (Reduced):
#9  0x006ed9d0 in invokeMethod (val9=<optimized out>, val8=<optimized out>, val7=<optimized out>, val6=<optimized out>, val5=<optimized out>, val4=<optimized out>, val3=<optimized out>, val2=<optimized out>, val1=<optimized out>, val0=<optimized out>, member=<optimized out>, obj=<optimized out>) at /usr/include/qt4/QtCore/qobjectdefs.h:426
#10 KIMAP::SessionPrivate::handleSslError (this=0xb5410be8, errorData=...) at ../../kimap/session.cpp:121
#11 0x006f0496 in KIMAP::Session::qt_metacall (this=0xb5403618, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x9222100) at ./session.moc:117
#12 0x00d09b7d in metacall (argv=0x9222100, idx=15, cl=QMetaObject::InvokeMetaMethod, object=0xb5403618) at kernel/qmetaobject.cpp:237
[...]
#15 0x00d1bb52 in QObject::event (this=0xb5403618, e=0x95a3b38) at kernel/qobject.cpp:1217
Comment 12 Christophe Marin 2012-01-29 14:17:11 UTC
*** Bug 292655 has been marked as a duplicate of this bug. ***
Comment 13 Christophe Marin 2012-03-30 16:17:15 UTC
*** Bug 296856 has been marked as a duplicate of this bug. ***
Comment 14 Christophe Marin 2012-03-30 16:17:39 UTC
*** Bug 294424 has been marked as a duplicate of this bug. ***
Comment 15 Christophe Marin 2012-03-30 16:17:49 UTC
*** Bug 296728 has been marked as a duplicate of this bug. ***
Comment 16 Martin Kampas 2012-06-11 09:57:32 UTC
Created attachment 71727 [details]
New crash information added by DrKonqi

akonadi_imap_resource (4.8) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed:

The same scenario, though I attach my report as the most recent one is from KDE 4.7.x and the bug is still there and unconfirmed.

Akonadi popped up a message box with IMAP connection error - SSL verification has failed. The certificate expired just couple of hours before. Continue->Accept for current session only->Crash.

-- Backtrace (Reduced):
#8  0xb65a839a in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., member=<optimized out>, obj=<optimized out>) at /usr/include/qt4/QtCore/qobjectdefs.h:434
#9  KIMAP::SessionPrivate::handleSslError (this=0x892b020, errorData=...) at /var/tmp/portage/kde-base/kdepimlibs-4.8.2/work/kdepimlibs-4.8.2/kimap/session.cpp:121
#10 0xb65ab0a2 in KIMAP::Session::qt_static_metacall (_o=0x8ae6ca0, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0x6c6f6f62) at /var/tmp/portage/kde-base/kdepimlibs-4.8.2/work/kdepimlibs-4.8.2_build/kimap/session.moc:96
[...]
#12 0xb730fef9 in QObject::event (this=0x8b294d8, e=0x8ae6ca0) at kernel/qobject.cpp:1195
#13 0xb686782a in QApplicationPrivate::notify_helper (this=0x88fc9e8, receiver=0x8b294d8, e=0x8932590) at kernel/qapplication.cpp:4554
Comment 17 Jekyll Wu 2012-07-06 19:11:54 UTC
*** Bug 301881 has been marked as a duplicate of this bug. ***
Comment 18 Jekyll Wu 2012-07-26 23:41:29 UTC
*** Bug 304110 has been marked as a duplicate of this bug. ***
Comment 19 Jekyll Wu 2012-11-09 03:19:37 UTC
*** Bug 309788 has been marked as a duplicate of this bug. ***
Comment 20 Jekyll Wu 2013-02-26 04:10:23 UTC
*** Bug 310243 has been marked as a duplicate of this bug. ***
Comment 21 Jekyll Wu 2013-02-26 04:10:35 UTC
*** Bug 302459 has been marked as a duplicate of this bug. ***
Comment 22 Jekyll Wu 2013-02-26 04:11:58 UTC
*** Bug 311586 has been marked as a duplicate of this bug. ***
Comment 23 GGG 2013-03-11 22:28:35 UTC
Created attachment 77971 [details]
New crash information added by DrKonqi

akonadi_imap_resource (4.10) on KDE Platform 4.10.1 using Qt 4.8.4

- What I was doing when the application crashed:

I has detached from the network and then it reattached. Shortly after that imap part of Kmail crashed.

-- Backtrace (Reduced):
#7  0x00007fd42e9466a7 in KIMAP::SessionPrivate::handleSslError(KSslErrorUiData const&) () from /usr/lib/libkimap.so.4
#8  0x00007fd42fd015ae in QObject::event (this=0x210c9f0, e=<optimized out>) at kernel/qobject.cpp:1194
#9  0x00007fd42f08d8ec in QApplicationPrivate::notify_helper (this=this@entry=0x1ee9020, receiver=receiver@entry=0x210c9f0, e=e@entry=0x7fd40001f2f0) at kernel/qapplication.cpp:4567
#10 0x00007fd42f09025b in QApplication::notify (this=0x7fff4ae9db10, receiver=0x210c9f0, e=0x7fd40001f2f0) at kernel/qapplication.cpp:4428
#11 0x00007fd42d1feaf6 in KApplication::notify (this=0x7fff4ae9db10, receiver=0x210c9f0, event=0x7fd40001f2f0) at ../../kdeui/kernel/kapplication.cpp:311
Comment 24 Martin 2013-03-28 07:45:24 UTC
*** Bug 317386 has been marked as a duplicate of this bug. ***
Comment 25 Jekyll Wu 2013-09-03 08:10:45 UTC
*** Bug 324442 has been marked as a duplicate of this bug. ***
Comment 26 Jekyll Wu 2013-09-03 08:11:32 UTC
*** Bug 322181 has been marked as a duplicate of this bug. ***
Comment 27 Kevin Ottens 2013-11-16 07:27:01 UTC
The IMAP resource has a new maintainer, reassigning to him.
Comment 28 Christian Mollekopf 2013-11-20 10:18:30 UTC
Does this still apply to >=4.11.3?
Comment 29 Valery Mamonov 2013-11-20 10:23:07 UTC
As for me, I can't reproduce the bug in Kmail 4.11.3
Sometimes i faced with expired server certificates, but accepted them with
no problems.
Don't know about other users, sorry.


2013/11/20 Christian Mollekopf <mollekopf@kolabsys.com>

> https://bugs.kde.org/show_bug.cgi?id=279113
>
> Christian Mollekopf <mollekopf@kolabsys.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|CONFIRMED                   |NEEDSINFO
>                  CC|                            |mollekopf@kolabsys.com
>          Resolution|---                         |WAITINGFORINFO
>
> --- Comment #28 from Christian Mollekopf <mollekopf@kolabsys.com> ---
> Does this still apply to >=4.11.3?
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>
Comment 30 tblu 2013-11-20 18:03:07 UTC
I cannot reproduce it either in kmail 4.11.3



Valery Mamonov <valerymamonov@gmail.com> ha scritto:
>https://bugs.kde.org/show_bug.cgi?id=279113
>
>--- Comment #29 from Valery Mamonov <valerymamonov@gmail.com> ---
>As for me, I can't reproduce the bug in Kmail 4.11.3
>Sometimes i faced with expired server certificates, but accepted them
>with
>no problems.
>Don't know about other users, sorry.
>
>
>2013/11/20 Christian Mollekopf <mollekopf@kolabsys.com>
>
>> https://bugs.kde.org/show_bug.cgi?id=279113
>>
>> Christian Mollekopf <mollekopf@kolabsys.com> changed:
>>
>>            What    |Removed                     |Added
>>
>>
>----------------------------------------------------------------------------
>>              Status|CONFIRMED                   |NEEDSINFO
>>                  CC|                           
>|mollekopf@kolabsys.com
>>          Resolution|---                         |WAITINGFORINFO
>>
>> --- Comment #28 from Christian Mollekopf <mollekopf@kolabsys.com> ---
>> Does this still apply to >=4.11.3?
>>
>> --
>> You are receiving this mail because:
>> You are on the CC list for the bug.
>>
>
>-- 
>You are receiving this mail because:
>You are on the CC list for the bug.

-- Inviato dal mio cellulare Android con K-9 Mail.
Comment 31 Andrew Crouthamel 2018-09-25 03:45:39 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 32 Andrew Crouthamel 2018-10-27 02:25:14 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!