Bug 379996 - IMAP resource crashing when trying to configure
Summary: IMAP resource crashing when trying to configure
Status: RESOLVED DUPLICATE of bug 379155
Alias: None
Product: kdepim
Classification: Applications
Component: general (show other bugs)
Version: 5.5.*
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-19 07:21 UTC by Gerd Fleischer
Modified: 2017-05-24 08:55 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gerd Fleischer 2017-05-19 07:21:13 UTC
The imap resource crashes for me if I try to call the configure dialog.

xsession-errors says
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_imap_resource" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' crashed! 1 restarts left.
Pass a valid window to KWallet::Wallet::openWallet().

OpenSUSE rpms kmail, kdepim-runtime 5.5.1/17.04.1
Comment 1 wonko 2017-05-19 09:30:19 UTC
Same here

org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_imap_resource" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' crashed! 1 restarts left.
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_imap_resource" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' crashed! 0 restarts left.

I rm-ed .config/akonadi* .cache/akonadi* .local/share/akonadi etc
still the same error

#rpm -qa |grep -E "akonadi|kmail|kdepim"                                                 
akonadi-contact-17.04.0-1.1.x86_64
libakonadi4-4.14.10-5.1.x86_64
kmail-account-wizard-17.04.0-1.1.x86_64
libakonadiprotocolinternals1-1.13.0-9.2.x86_64
libKF5Libkdepim5-17.04.0-1.1.x86_64
kmailtransport-17.04.0-1.1.x86_64
akonadi-search-17.04.0-1.1.x86_64
kdepim-apps-libs-17.04.0-1.1.x86_64
kdepim-addons-17.04.0-1.1.x86_64
libKF5LibkdepimAkonadi5-17.04.0-1.1.x86_64
akonadiconsole-17.04.0-1.1.x86_64
libkdepimlibs4-4.14.10-5.1.x86_64
akonadi-server-17.04.0-1.1.x86_64
akonadi-import-wizard-17.04.0-1.1.x86_64
akonadi-search-lang-17.04.0-1.1.noarch
akonadi-server-sqlite-17.04.0-1.1.x86_64
kdepim-runtime-17.04.0-1.1.x86_64
kmail-application-icons-17.04.0-1.1.x86_64
kdepimlibs4-4.14.10-5.1.x86_64
libkdepim-17.04.0-1.1.x86_64
akonadi-calendar-tools-17.04.0-1.1.x86_64
kmail-17.04.0-1.1.x86_64
akonadi-mime-17.04.0-1.1.x86_64
Comment 2 Christophe Marin 2017-05-19 10:15:14 UTC
there's no crash window with a backtrace ?
Comment 3 wonko 2017-05-19 10:38:32 UTC
I don't see any backtrace. Where should I look?

btw. If i use the akonadiconsole and select Configure Natively the same error message is printed to stderr in the konsole where I (re)started akonadi:

org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_imap_resource" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' crashed! 1 restarts left.

Nothing else happens. No Window is opened.
Comment 4 Gerd Fleischer 2017-05-19 13:31:15 UTC
No backtrace window. Just nothing happens.
Comment 5 pipapo 2017-05-21 11:52:01 UTC
It's the same here with neon 5.8.6 based on ubuntu 16.04.1.
Comment 6 Gerd Fleischer 2017-05-21 12:03:57 UTC
How to debug this?
I installed debug packages but not more information,
gdb also (but I'm not an expert with this).
Comment 7 Gerd Fleischer 2017-05-21 13:06:37 UTC
I guess this is a copy of
Bug 379155 - Imap resources crash when trying to open settings
??

This is fixed in trunk, but 17.04 branch?
Comment 8 Gerd Fleischer 2017-05-23 18:29:02 UTC
openSUSE has updated packages with patches included.
Fixed for me now.
And will be in 17.04.2.
Comment 9 Wolfgang Bauer 2017-05-24 08:55:07 UTC
(In reply to Gerd Fleischer from comment #8)
> openSUSE has updated packages with patches included.
> Fixed for me now.

Ok, so I think we can mark this as duplicate then.

*** This bug has been marked as a duplicate of bug 379155 ***