Bug 357263 - Crash when opening addressbook entry (group) from kmail
Summary: Crash when opening addressbook entry (group) from kmail
Status: RESOLVED WORKSFORME
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-12-28 16:42 UTC by David Tonhofer
Modified: 2018-12-01 03:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Tonhofer 2015-12-28 16:42:53 UTC
Application: kaddressbook (4.14.10)
KDE Platform Version: 4.14.14
Qt Version: 4.8.6
Operating System: Linux 4.2.8-200.fc22.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
Opened addressbook group.
Kmail displays a dialog saying that it is working
Then crashes
The addressbook seems to be foobared underneath though; addressbook group has wrong contents (that's why I wanted to open it)

-- Backtrace:
Application: KAddressBook (kaddressbook), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x00007fc8ee7c39c8 in raise () at /lib64/libc.so.6
#7  0x00007fc8ee7c565a in abort () at /lib64/libc.so.6
#8  0x00007fc8ef0fdb5d in __gnu_cxx::__verbose_terminate_handler() () at /lib64/libstdc++.so.6
#9  0x00007fc8ef0fb9a6 in  () at /lib64/libstdc++.so.6
#10 0x00007fc8ef0fb9f1 in  () at /lib64/libstdc++.so.6
#11 0x00007fc8ef0fbc59 in __cxa_rethrow () at /lib64/libstdc++.so.6
#12 0x00007fc8ef794cfe in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#13 0x00007fc8ef79a6a9 in QCoreApplication::exec() () at /lib64/libQtCore.so.4
#14 0x0000000000405560 in main ()

Reported using DrKonqi
Comment 1 Andrew Crouthamel 2018-11-01 13:49:58 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Bug Janitor Service 2018-11-16 11:37:15 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 3 Bug Janitor Service 2018-12-01 03:51:14 UTC
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!