Bug 1303274

Summary: [abrt] kf5-baloo-file: qt_message_fatal(): baloo_file_extractor killed by SIGABRT
Product: [Fedora] Fedora Reporter: Max <maxpatera>
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, ltinkl, me, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/6941e7987dd4fba411e80605f999f61f6c44b193
Whiteboard: abrt_hash:1654e2ac86fee7ad379d4d6710531a306553fe4a;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:41:24 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 Max 2016-01-30 03:49:48 UTC
Version-Release number of selected component:
kf5-baloo-file-5.18.0-1.fc22

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/bin/baloo_file_extractor --bdata /run/media/max/7D48-07C9/.cache
crash_function: qt_message_fatal
executable:     /usr/bin/baloo_file_extractor
global_pid:     12500
kernel:         4.2.8-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 qt_message_fatal at global/qlogging.cpp:1578
 #3 QMessageLogger::fatal at global/qlogging.cpp:781
 #4 QXcbConnection::QXcbConnection at qxcbconnection.cpp:526
 #5 QXcbIntegration::QXcbIntegration at qxcbintegration.cpp:177
 #6 QXcbIntegrationPlugin::create at qxcbmain.cpp:50
 #7 loadIntegration at kernel/qplatformintegrationfactory.cpp:56
 #8 QPlatformIntegrationFactory::create at kernel/qplatformintegrationfactory.cpp:73
 #9 init_platform at kernel/qguiapplication.cpp:1019
 #10 QGuiApplicationPrivate::createPlatformIntegration at kernel/qguiapplication.cpp:1176
 #11 QGuiApplicationPrivate::createEventDispatcher at kernel/qguiapplication.cpp:1193

Comment 1 Max 2016-01-30 03:49:54 UTC
Created attachment 1119568 [details]
File: backtrace

Comment 2 Max 2016-01-30 03:49:55 UTC
Created attachment 1119569 [details]
File: cgroup

Comment 3 Max 2016-01-30 03:49:55 UTC
Created attachment 1119570 [details]
File: core_backtrace

Comment 4 Max 2016-01-30 03:49:56 UTC
Created attachment 1119571 [details]
File: dso_list

Comment 5 Max 2016-01-30 03:49:57 UTC
Created attachment 1119572 [details]
File: environ

Comment 6 Max 2016-01-30 03:49:58 UTC
Created attachment 1119573 [details]
File: limits

Comment 7 Max 2016-01-30 03:49:59 UTC
Created attachment 1119574 [details]
File: maps

Comment 8 Max 2016-01-30 03:50:00 UTC
Created attachment 1119575 [details]
File: mountinfo

Comment 9 Max 2016-01-30 03:50:00 UTC
Created attachment 1119576 [details]
File: namespaces

Comment 10 Max 2016-01-30 03:50:01 UTC
Created attachment 1119577 [details]
File: open_fds

Comment 11 Max 2016-01-30 03:50:02 UTC
Created attachment 1119578 [details]
File: proc_pid_status

Comment 12 Max 2016-01-30 03:50:03 UTC
Created attachment 1119579 [details]
File: var_log_messages

Comment 13 Fedora End Of Life 2016-07-19 18:41:24 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.