[kmail2] [Bug 420474] Can't connect to receiving imap server

2020-06-27 Thread Damian 
https://bugs.kde.org/show_bug.cgi?id=420474

--- Comment #1 from Damian  ---
I am affected by this bug too. The file .xsession-errors show a stream of
messages like the one mentioned (org.kde.pim.kimap: Connection to server lost 
QAbstractSocket::SocketError(13)), and the UI reports thet the connection was
not successful (only once).

I was working with Kubuntu 19.10, but once I installed Kubuntu 20.04 it does
not work anymore. I have installed the KDE backports PPA but there is no update
to Akonadi/KMail, so the problem is not solved.

Debugging the connection with Wireshark I have observed that the TLS handshake
stops at "Server Hello Done", no "Client Key Exhange" step ever happens, as can
be seen in [1].

And as the OP said, the account can be successfully configured with
Thunderbird.

[1]:
https://www.thesslstore.com/blog/explaining-ssl-handshake/#the-tls-12-handshake-step-by-step

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 420474] Can't connect to receiving imap server

2020-06-27 Thread Damian 
https://bugs.kde.org/show_bug.cgi?id=420474

Damian  changed:

   What|Removed |Added

 CC||m...@dsthode.info

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 423579] New: Application: Kontact (kontact), signal: Segmentation fault

2020-06-27 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=423579

Bug ID: 423579
   Summary: Application: Kontact (kontact), signal: Segmentation
fault
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: john4deidre2...@xtra.co.nz
  Target Milestone: ---

Application: kontact (5.14.2 (20.04.2))

Qt Version: 5.15.0
Frameworks Version: 5.71.0
Operating System: Linux 5.7.5-1-default x86_64
Windowing system: X11
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:

i was just trying to start it from the menu.

it then crashed with the backtrace given

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault

[KCrash Handler]
#4  std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at
/usr/include/c++/10/bits/atomic_base.h:420
#5  QAtomicOps::loadRelaxed (_q_value=) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#6  QBasicAtomicInteger::loadRelaxed (this=) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107
#7  QtPrivate::RefCount::isShared (this=) at
../../include/QtCore/../../src/corelib/tools/qrefcount.h:101
#8  QList::append (this=0x100, t=@0x7ffe747df130: 0x55a9a3fc0730) at
../../include/QtCore/../../src/corelib/tools/qlist.h:622
#9  0x7fb61d85eba0 in QWidget::insertAction
(this=this@entry=0x55a9a3fc0730, before=, before@entry=0x0,
action=0x55a9a436a1b0) at kernel/qwidget.cpp:3130
#10 0x7fb61df0835b in KXMLGUI::ActionList::plug (index=,
container=0x55a9a3fc0730, this=0x55a9a80dc350) at
/usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:45
#11 KXMLGUI::ContainerNode::plugActionList (mergingIdxIt=..., mergingIdxIt=..., state=...,
this=0x55a9a3fbeb70) at
/usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:234
#12 KXMLGUI::ContainerNode::plugActionList (this=0x55a9a3fbeb70, state=...) at
/usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:204
#13 0x7fb61df083e1 in KXMLGUI::ContainerNode::plugActionList
(this=0x55a9a3ee2fc0, state=...) at
/usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:208
#14 0x7fb61df083e1 in KXMLGUI::ContainerNode::plugActionList
(this=0x55a9a676bb30, state=...) at
/usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory_p.cpp:208
#15 0x7fb61df0f721 in KXMLGUIFactory::plugActionList (this=0x55a9a40334c0,
client=0x55a9a79a2130, name=..., actionList=...) at
/usr/src/debug/kxmlgui-5.71.0-1.1.x86_64/src/kxmlguifactory.cpp:574
#16 0x7fb5b6715f50 in PimCommon::PluginInterface::initializePluginActions
(this=0x7ffe747df480, prefix=..., guiClient=0x55a9a79a2130) at
/usr/src/debug/pimcommon-20.04.2-1.1.x86_64/src/pimcommonakonadi/genericplugins/plugininterface.cpp:168
#17 0x7fb5b732d900 in KMMainWidget::initializePluginActions
(this=0x55a9a831a570) at
/usr/src/debug/kmail-20.04.2-1.1.x86_64/src/kmmainwidget.cpp:4217
#18 0x7fb5b74d0ab5 in KMailPart::guiActivateEvent (this=0x55a9a79a2100,
e=0x7ffe747df520) at
/usr/src/debug/kmail-20.04.2-1.1.x86_64/src/kmail_part.cpp:133
#19 0x7fb61ccf696f in QObject::event (this=0x55a9a79a2100,
e=0x7ffe747df6a0) at kernel/qobject.cpp:1291
#20 0x7fb61d8280cf in QApplicationPrivate::notify_helper (this=, receiver=0x55a9a79a2100, e=0x7ffe747df6a0) at
kernel/qapplication.cpp:3671
#21 0x7fb61cccab0a in QCoreApplication::notifyInternal2
(receiver=0x55a9a79a2100, event=0x7ffe747df6a0) at
../../include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325
#22 0x7fb61c11d91f in KParts::MainWindow::createGUI (this=0x55a9a44a7450,
part=0x55a9a79a2100) at
/usr/src/debug/kparts-5.71.0-1.1.x86_64/src/mainwindow.cpp:123
#23 0x7fb61e02488a in Kontact::MainWindow::selectPlugin
(this=0x55a9a44a7450, plugin=0x55a9a5ba8800) at
/usr/src/debug/kontact-20.04.2-1.1.x86_64/src/mainwindow.cpp:704
#24 0x7fb61cd01020 in doActivate (sender=0x55a9a43cebd0,
signal_index=7, argv=argv@entry=0x7ffe747df8d0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395
#25 0x7fb61ccfa340 in QMetaObject::activate (sender=,
m=m@entry=0x7fb61e042840 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe747df8d0)
at kernel/qobject.cpp:3946
#26 0x7fb61e02027f in Kontact::SidePaneBase::pluginSelected
(this=, _t1=) at
/usr/src/debug/kontact-20.04.2-1.1.x86_64/build/src/kontactprivate_autogen/EWIEGA46WW/moc_sidepanebase.cpp:141
#27 0x7fb61cd00fe6 in QtPrivate::QSlotObjectBase::call (a=0x7ffe747dfa10,
r=0x55a9a43cebd0, this=0x55a9a3ec2040) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#28 doActivate (sender=0x55a9a4552690, signal_index=15,
argv=argv@entry=0x7ffe747dfa10) at kernel/qobject.cpp:3886
#29

[Akonadi] [Bug 423575] Akonadi server reproducibly eats ∞ memory (possibly in Akonadi::Server::Connection::handleIncomingData() [connection.cpp:274])

2020-06-27 Thread Szőts Ákos 
https://bugs.kde.org/show_bug.cgi?id=423575

--- Comment #1 from Szőts Ákos  ---
Created attachment 129718
  --> https://bugs.kde.org/attachment.cgi?id=129718&action=edit
Flame graph

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 423575] New: Akonadi server reproducibly eats ∞ memory (possibly in Akonadi::Server::Connection::handleIncomingData() [connection.cpp:274])

2020-06-27 Thread Szőts Ákos 
https://bugs.kde.org/show_bug.cgi?id=423575

Bug ID: 423575
   Summary: Akonadi server reproducibly eats ∞ memory (possibly in
Akonadi::Server::Connection::handleIncomingData()
[connection.cpp:274])
   Product: Akonadi
   Version: 5.14.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: szots...@gmail.com
  Target Milestone: ---

Created attachment 129717
  --> https://bugs.kde.org/attachment.cgi?id=129717&action=edit
Top-down

A memory leak is present in akonadi-server versions ranging from 18.08 to
20.04: whenever KMail rechecks all folders of my Google IMAP account, memory
just grows but never shrinks.

I've created heaptrack summaries both for 18.04 and 20.04 of the leak which
show that the server starts eating memory. Last time it went up to 12 GB when I
stopped it.

You can reach the pictures showing the memory occupation and a backtrace file
here: https://mega.nz/#F!RQ4iBSRT!DmHq4qoDKpuVyewuAmazsA

I attach two of pictures for 20.04 here as well.

For 20.04 I have the heaptrack file stored locally which is 14 GB in size, but
I can upload it in case you need it.

It's not a classical memory leak since everything will be freed up upon exit
however I still consider a valid one.

-- 
You are receiving this mail because:
You are the assignee for the bug.