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
Created attachment 731511 [details] File: backtrace
Created attachment 731512 [details] File: cgroup
Created attachment 731513 [details] File: core_backtrace
Created attachment 731514 [details] File: dso_list
Created attachment 731515 [details] File: environ
Created attachment 731516 [details] File: limits
Created attachment 731517 [details] File: maps
Created attachment 731518 [details] File: open_fds
Created attachment 731519 [details] File: proc_pid_status
Created attachment 731520 [details] File: xsession_errors
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?
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.
Still happens with 0.6.2.... it also crashed on me using grouping by groups.
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.
Thanks Martin, I'll follow the KDE bugzilla, please do post here the id#, thanks!
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
sorry, I missed that... thanks!
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.
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.