Bug 22126 - Kaddressbook crashes when creating a group.
Summary: Kaddressbook crashes when creating a group.
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-05 08:54 CET by Rubén Fernández
Modified: 2020-08-06 16:56 CEST (History)
4 users (show)

See Also:
Source RPM: kaddressbook-16.12.3-1.mga6
CVE:
Status comment:


Attachments

Description Rubén Fernández 2017-12-05 08:54:21 CET
Description of problem:

Kaddressbook crashes when creating a group.

When starting Kaddressbook from the command line I get this:
terminate called after throwing an instance of 'Akonadi::PayloadException'
  what():  Akonadi::PayloadException: Wrong payload type (requested: sp(0)<QByteArray>; present: sp(0)<KContacts::ContactGroup>
KCrash: Application 'kaddressbook' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0

Also, all groups created on Mageia 5 are gone.

Version-Release number of selected component (if applicable):
kaddressbook-16.12.3-1.mga6

How reproducible:
Always

Steps to Reproduce:
1. Open Kaddressbook.
2. Create a group.
3. Click OK without inputting any address into the group.
Marja Van Waes 2017-12-05 09:38:44 CET

Assignee: bugsquad => kde
CC: (none) => marja11

Comment 1 peter winterflood 2017-12-05 12:12:05 CET
I have validated this as a problem on a mga7 based build.
and added the following strace

strace -f kaddressbook

####lines up till i hit create excluded

[pid 17098] write(2, "QXcbConnection: XCB error: 3 (Ba"..., 129QXcbConnection: XCB error: 3 (BadWindow), sequence: 1724, resource id: 35667859, major code: 40 (TranslateCoords), minor code: 0
) = 129
[pid 17098] write(5, "\1\0\0\0\0\0\0\0", 8) = 8
[pid 17098] write(5, "\1\0\0\0\0\0\0\0", 8) = 8
[pid 17098] poll([{fd=5, events=POLLIN}, {fd=14, events=POLLIN}, {fd=23, events=POLLIN}], 3, 0) = 1 ([{fd=5, revents=POLLIN}])
[pid 17098] read(5, "\7\0\0\0\0\0\0\0", 16) = 8
[pid 17098] write(5, "\1\0\0\0\0\0\0\0", 8) = 8
[pid 17098] write(5, "\1\0\0\0\0\0\0\0", 8) = 8
[pid 17101] <... poll resumed> )        = 1 ([{fd=18, revents=POLLIN}])
[pid 17098] write(5, "\1\0\0\0\0\0\0\0", 8 <unfinished ...>
[pid 17101] ioctl(18, FIONREAD <unfinished ...>
[pid 17098] <... write resumed> )       = 8
[pid 17101] <... ioctl resumed> , [31]) = 0
[pid 17101] read(18, "\0\0\0\0\0\0\0\5d\n\0\0\0PLD:RFC822\377\377\377\377\0\0\0\0", 31) = 31
[pid 17101] write(5, "\1\0\0\0\0\0\0\0", 8) = 8
[pid 17098] write(5, "\1\0\0\0\0\0\0\0", 8 <unfinished ...>
[pid 17101] poll([{fd=17, events=POLLIN}, {fd=18, events=POLLIN}, {fd=20, events=POLLIN}, {fd=21, events=POLLIN}, {fd=22, events=POLLIN}], 5, -1 <unfinished ...>
[pid 17098] <... write resumed> )       = 8
[pid 17098] write(5, "\1\0\0\0\0\0\0\0", 8) = 8
[pid 17098] poll([{fd=5, events=POLLIN}, {fd=14, events=POLLIN}, {fd=23, events=POLLIN}], 3, 0) = 1 ([{fd=5, revents=POLLIN}])
[pid 17098] read(5, "\6\0\0\0\0\0\0\0", 16) = 8
[pid 17098] futex(0x7f7cea51e1a0, FUTEX_WAKE_PRIVATE, 2147483647) = 0
[pid 17098] write(2, "terminate called after throwing "..., 48terminate called after throwing an instance of ') = 48
[pid 17098] write(2, "Akonadi::PayloadException", 25Akonadi::PayloadException) = 25
[pid 17098] write(2, "'\n", 2'
)          = 2
[pid 17098] write(2, "  what():  ", 11  what():  ) = 11
[pid 17098] write(2, "Akonadi::PayloadException: Wrong"..., 116Akonadi::PayloadException: Wrong payload type (requested: sp(0)<QByteArray>; present: sp(0)<KContacts::ContactGroup>) = 116
[pid 17098] write(2, "\n", 1
)           = 1
[pid 17098] rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
[pid 17098] tgkill(17098, 17098, SIGABRT) = 0
[pid 17098] --- SIGABRT {si_signo=SIGABRT, si_code=SI_TKILL, si_pid=17098, si_uid=1000} ---
[pid 17101] <... poll resumed> )        = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
[pid 17100] <... poll resumed> <unfinished ...>) = ?
[pid 17103] <... poll resumed> <unfinished ...>) = ?
[pid 17099] <... poll resumed> <unfinished ...>) = ?
[pid 17101] +++ killed by SIGABRT (core dumped) +++
[pid 17100] +++ killed by SIGABRT (core dumped) +++
[pid 17099] +++ killed by SIGABRT (core dumped) +++
[pid 17103] +++ killed by SIGABRT (core dumped) +++
+++ killed by SIGABRT (core dumped) +++
Aborted (core dumped)


also the error is similar to, but not nessasarily the same as 

https://mail.kde.org/pipermail/kdepim-bugs/2010-December/046708.html

reported in an much older version.

CC: (none) => peter.winterflood

Comment 2 Florian Hubold 2017-12-05 14:15:09 CET
For reference, I cannot reproduce on mga6. kaddressbook does not crash, neither when adding a group without any member contacts nor when adding a group with members. This is what it looks like after creating a few groups (apart from this I've never used kaddressbook before):

[doktor5000@Mageia6]─[13:48:10]─[~] LC_ALL=C kaddressbook 
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: Subtree:  2 QSet(2)
org.kde.akonadi.ETM: collection: "Pers?nliche Kontakte"
org.kde.akonadi.ETM: Fetch job took  54 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 1
org.kde.akonadi.ETM: first fetched collection: "Pers?nliche Kontakte"
org.kde.akonadi.ETM: Fetch job took  1 msec
org.kde.akonadi.ETM: was item fetch job: items: 0
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: Subtree:  2 QSet(2)
org.kde.akonadi.ETM: Fetch job took  3 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 1
org.kde.akonadi.ETM: first fetched collection: "Pers?nliche Kontakte"
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: Subtree:  2 QSet(2)
org.kde.akonadi.ETM: Fetch job took  5 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 1
org.kde.akonadi.ETM: first fetched collection: "Pers?nliche Kontakte"
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: Subtree:  2 QSet(2)
org.kde.akonadi.ETM: Fetch job took  5 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 1
org.kde.akonadi.ETM: first fetched collection: "Pers?nliche Kontakte"
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: collection: "Pers?nliche Kontakte"
org.kde.akonadi.ETM: Fetch job took  2 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 1
org.kde.akonadi.ETM: first fetched collection: "Pers?nliche Kontakte"
org.kde.akonadi.ETM: Fetch job took  1 msec
org.kde.akonadi.ETM: was item fetch job: items: 2



(In reply to peter winterflood from comment #1)
> I have validated this as a problem on a mga7 based build.
> and added the following strace


@Peter: As this was originally reported against mga6, your test on mga7 might hit a totally different issue.

Status: NEW => UNCONFIRMED
CC: (none) => doktor5000
Ever confirmed: 1 => 0

Comment 3 peter winterflood 2017-12-05 15:44:58 CET
Thanks Florien 

yes I accept it maybe different

I too have never used kaddressbook before, so the only thing i did was to reproduce the actions Rubin took, and they look similar.
It is curious however now you have tested without error, that this is not a widespread problem as the first 3 people involved in this reproducer thought.

i will test on mga6 when i get some time, and add appropriate feedback.
Comment 4 Aurelien Oudelet 2020-08-06 16:56:33 CEST
This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Resolution: (none) => OLD
CC: (none) => ouaurelien
Status: UNCONFIRMED => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.