Bug 948202

Summary: [abrt] ktp-contact-list-0.6.0-1.fc18: convert: Process /usr/bin/ktp-contactlist was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Christos <christos.lazaridis+redhat.bugzilla>
Component: ktp-contact-listAssignee: Jaroslav Reznik <jreznik>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dvratil, jgrulich, jreznik, martin.klapetek, rdieter, salsabil42xoops
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:a9c349fb5d2ca93995a5f8566bcbad30864655a1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 20:27:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: xsession_errors none

Description Christos 2013-04-04 10:00:00 UTC
Version-Release number of selected component:
ktp-contact-list-0.6.0-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/ktp-contactlist
crash_function: convert
executable:     /usr/bin/ktp-contactlist
kernel:         3.8.5-201.fc18.x86_64
uid:            1000
ureports_counter: 1

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 convert at kernel/qvariant.cpp:886
 #2 qNumVariantToHelper<unsigned int> at kernel/qvariant.cpp:2437
 #3 QVariant::toUInt at kernel/qvariant.cpp:2479
 #4 KTp::ContactsFilterModel::Private::filterAcceptsContact at /usr/src/debug/ktp-common-internals-0.6.0/KTp/Models/contacts-filter-model.cpp:132
 #5 KTp::ContactsFilterModel::filterAcceptsRow at /usr/src/debug/ktp-common-internals-0.6.0/KTp/Models/contacts-filter-model.cpp:834
 #6 QSortFilterProxyModelPrivate::create_mapping at itemviews/qsortfilterproxymodel.cpp:327
 #7 QSortFilterProxyModelPrivate::source_to_proxy at itemviews/qsortfilterproxymodel.cpp:387
 #8 QSortFilterProxyModel::mapFromSource at itemviews/qsortfilterproxymodel.cpp:2531
 #9 sourceModelParentIndexChanged at /usr/src/debug/ktp-common-internals-0.6.0/KTp/Models/contacts-filter-model.cpp:410
 #10 KTp::ContactsFilterModel::Private::sourceModelParentIndexChanged at /usr/src/debug/ktp-common-internals-0.6.0/KTp/Models/contacts-filter-model.cpp:406

Comment 1 Christos 2013-04-04 10:00:06 UTC
Created attachment 731511 [details]
File: backtrace

Comment 2 Christos 2013-04-04 10:00:10 UTC
Created attachment 731512 [details]
File: cgroup

Comment 3 Christos 2013-04-04 10:00:13 UTC
Created attachment 731513 [details]
File: core_backtrace

Comment 4 Christos 2013-04-04 10:00:16 UTC
Created attachment 731514 [details]
File: dso_list

Comment 5 Christos 2013-04-04 10:00:20 UTC
Created attachment 731515 [details]
File: environ

Comment 6 Christos 2013-04-04 10:00:22 UTC
Created attachment 731516 [details]
File: limits

Comment 7 Christos 2013-04-04 10:00:25 UTC
Created attachment 731517 [details]
File: maps

Comment 8 Christos 2013-04-04 10:00:28 UTC
Created attachment 731518 [details]
File: open_fds

Comment 9 Christos 2013-04-04 10:00:30 UTC
Created attachment 731519 [details]
File: proc_pid_status

Comment 10 Christos 2013-04-04 10:00:32 UTC
Created attachment 731520 [details]
File: xsession_errors

Comment 11 Martin Klapetek 2013-04-04 11:19:48 UTC
Thanks for the report!

Can I ask what were you doing when this happened? Or did it happen all on its own? Also are you using grouping by groups or accounts?

Lastly, can you reproduce it?

Comment 12 Christos 2013-04-04 12:37:59 UTC
Hi,

The precise moment of the crash I was not using the application, so I cannot say how exactly one might be able to reproduce it, sorry it seemed like it happened on its own. I am using grouping by accounts. 

If I can help somehow please do let me know.

Comment 13 Christos 2013-05-30 15:16:26 UTC
Still happens with 0.6.2.... it also crashed on me using grouping by groups.

Comment 14 Martin Klapetek 2013-06-13 09:30:09 UTC
Thanks for the update. I'll transfer the bug to our main bugzilla now at bugs.kde.org and a reference here, if you don't have an account there, you can just post any updates here, but we'll track it there from now (as having bugs scattered among different bugzillas often leads to forgetting them).

Once it's fixed, I'll close this one as well.

Comment 15 Christos 2013-06-13 09:41:11 UTC
Thanks Martin, I'll follow the KDE bugzilla, please do post here the id#, thanks!

Comment 16 Martin Klapetek 2013-06-13 09:43:11 UTC
It's at the top in External trackers, I found your user in there so I added you in CC, please update if that mail is no longer valid :) Thanks.

http://bugs.kde.org/show_bug.cgi?id=321096

Comment 17 Christos 2013-06-13 09:46:01 UTC
sorry, I missed that... thanks!

Comment 18 Fedora End Of Life 2013-12-21 12:39:02 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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 Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 19 Fedora End Of Life 2014-02-05 20:27:14 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.