Bug 1266651

Summary: [abrt] kf5-baloo-file: qt_message_fatal(): baloo_file killed by SIGABRT
Product: [Fedora] Fedora Reporter: Sean McNeil <sean>
Component: kf5-balooAssignee: KDE SIG <kde-sig>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: jgrulich, kde-sig, kevin, ltinkl, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3516185a208d1f4792386423ebca670e262153c7
Whiteboard: abrt_hash:debcc1329212bc7fee90440335d16a3ac09a7986;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:01:56 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: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Sean McNeil 2015-09-26 04:27:45 UTC
Version-Release number of selected component:
kf5-baloo-file-5.13.0-1.fc22

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/bin/baloo_file
crash_function: qt_message_fatal
executable:     /usr/bin/baloo_file
global_pid:     4733
kernel:         4.1.7-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #5 qt_message_fatal at global/qlogging.cpp:1575
 #6 QMessageLogger::fatal at global/qlogging.cpp:777
 #7 QDBusRawTypeHandler::construct at qdbusmetaobject.cpp:133
 #8 construct at ../../src/corelib/kernel/qmetatype.h:2141
 #9 (anonymous namespace)::customConstruct at kernel/qvariant.cpp:1019
 #10 QVariant::QVariant at kernel/qvariant.cpp:1660
 #11 QMetaProperty::read at kernel/qmetaobject.cpp:2982
 #12 QObject::property at kernel/qobject.cpp:3898
 #13 checkCache at ../../../src/solid/devices/backends/udisks2/udisksdevicebackend.cpp:185
 #14 Solid::Backends::UDisks2::DeviceBackend::propertyExists at ../../../src/solid/devices/backends/udisks2/udisksdevicebackend.cpp:132

Comment 1 Sean McNeil 2015-09-26 04:27:50 UTC
Created attachment 1077310 [details]
File: backtrace

Comment 2 Sean McNeil 2015-09-26 04:27:52 UTC
Created attachment 1077311 [details]
File: cgroup

Comment 3 Sean McNeil 2015-09-26 04:27:54 UTC
Created attachment 1077312 [details]
File: core_backtrace

Comment 4 Sean McNeil 2015-09-26 04:27:55 UTC
Created attachment 1077313 [details]
File: dso_list

Comment 5 Sean McNeil 2015-09-26 04:27:57 UTC
Created attachment 1077314 [details]
File: environ

Comment 6 Sean McNeil 2015-09-26 04:27:59 UTC
Created attachment 1077315 [details]
File: limits

Comment 7 Sean McNeil 2015-09-26 04:28:01 UTC
Created attachment 1077316 [details]
File: maps

Comment 8 Sean McNeil 2015-09-26 04:28:03 UTC
Created attachment 1077317 [details]
File: mountinfo

Comment 9 Sean McNeil 2015-09-26 04:28:04 UTC
Created attachment 1077318 [details]
File: namespaces

Comment 10 Sean McNeil 2015-09-26 04:28:06 UTC
Created attachment 1077319 [details]
File: open_fds

Comment 11 Sean McNeil 2015-09-26 04:28:07 UTC
Created attachment 1077320 [details]
File: proc_pid_status

Comment 12 Sean McNeil 2015-09-26 04:28:09 UTC
Created attachment 1077321 [details]
File: var_log_messages

Comment 13 Fedora End Of Life 2016-07-19 18:01:56 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.