Bug 1303275

Summary: [abrt] plasma-systemsettings: qt_message_fatal(): systemsettings5 killed by SIGABRT
Product: [Fedora] Fedora Reporter: Max <maxpatera>
Component: plasma-systemsettingsAssignee: Rex Dieter <rdieter>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: jgrulich, ltinkl, me, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/24bfa58c80ee40969e192ba8a4bd019df95ad032
Whiteboard: abrt_hash:c006969ab22ee7a31828ba6d70758bd601ba3262;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:41:27 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:55:24 UTC 
Version-Release number of selected component:
plasma-systemsettings-5.5.3-1.fc22

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/bin/systemsettings5
crash_function: qt_message_fatal
executable:     /usr/bin/systemsettings5
global_pid:     13328
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:55:29 UTC 
Created attachment 1119581 [details]
File: backtrace
Comment 2 Max 2016-01-30 03:55:30 UTC 
Created attachment 1119582 [details]
File: cgroup
Comment 3 Max 2016-01-30 03:55:31 UTC 
Created attachment 1119583 [details]
File: core_backtrace
Comment 4 Max 2016-01-30 03:55:32 UTC 
Created attachment 1119584 [details]
File: dso_list
Comment 5 Max 2016-01-30 03:55:33 UTC 
Created attachment 1119585 [details]
File: environ
Comment 6 Max 2016-01-30 03:55:34 UTC 
Created attachment 1119586 [details]
File: limits
Comment 7 Max 2016-01-30 03:55:35 UTC 
Created attachment 1119587 [details]
File: maps
Comment 8 Max 2016-01-30 03:55:35 UTC 
Created attachment 1119588 [details]
File: mountinfo
Comment 9 Max 2016-01-30 03:55:37 UTC 
Created attachment 1119589 [details]
File: namespaces
Comment 10 Max 2016-01-30 03:55:38 UTC 
Created attachment 1119590 [details]
File: open_fds
Comment 11 Max 2016-01-30 03:55:39 UTC 
Created attachment 1119591 [details]
File: proc_pid_status
Comment 12 Max 2016-01-30 03:55:40 UTC 
Created attachment 1119592 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 18:41:27 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.