Bug 399196 - Kontact crash when trying to import calendar (search)
Summary: Kontact crash when trying to import calendar (search)
Status: RESOLVED WORKSFORME
Alias: None
Product: kontact
Classification: Applications
Component: calendar (show other bugs)
Version: 5.7.3
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-09-28 21:23 UTC by Marco Richetta
Modified: 2018-10-30 20:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Before typing for search. (49.12 KB, image/png)
2018-09-28 21:23 UTC, Marco Richetta
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Richetta 2018-09-28 21:23:03 UTC
Created attachment 115301 [details]
Before typing for search.

SUMMARY
When trying to import a new calendar, Kontact crashes just after you type a letter on the search box.

STEPS TO REPRODUCE
1. Kontact
2. Calendar
3. File - Import - Obtain new (I have it in Spanish so I don't know the real translation on English)
4. Type on the search box.

OBSERVED RESULT
Attached on the image

EXPECTED RESULT
Calendars that match your search

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.12.6
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5

ADDITIONAL INFORMATION
If you open KOrganizer directly, the functionality is correct.
Comment 1 Laurent Montel 2018-09-29 14:09:31 UTC
Hi,
Could you provide a backtrace please ?
thanks
Comment 3 Marco Richetta 2018-10-02 12:52:26 UTC
Hi!

After posting the bug I changed to the language of Kontact from Spanish to English to make sure I correctly explained the steps.
After that change I can't open Kontact anymore because it crashes everytime.

Anyway, I tried to generate the backtrace or at least provide some useful debugging info.

GDB
===

> gdb kontact
> gdb run

[Depuración de hilo usando libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Nuevo Thread 0x7fffc89f0700 (LWP 10767)]
"Here are 22 more memory addresses"
KSycoca unavailable. Kontact will be unable to find plugins.

Thread 1 "kontact" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.

KONTACT
=======

Trying to open kontact normally pops up a notification of the crash.
On the crash handler, I go to Developer Information and generate the backtrace.
It has some records like this
#1  0x00007f585b966747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1

It provides me a list of packages that can help on provide better information but I don't understand what I have to install. This is the list:

/usr/bin/kontact
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
/usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5
/usr/lib/x86_64-linux-gnu/libkontactprivate.so.5

I installed kdelibs5-dbg like it says on the Guideline, then searched for dbg packages for kontact or Qt5 but I'm not sure what to install.

I hope this may be helpful.
Comment 4 Andrew Crouthamel 2018-10-21 05:03:33 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
mark the bug 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 5 Marco Richetta 2018-10-22 14:04:43 UTC
I described the issues I have trying to provide the backtrace.
If that's not enough please let me know so I can keep trying on debugging.