Bug 1297238

Summary: [abrt] sddm: QObject::connect(): sddm killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Mikael <mikael79>
Component: sddmAssignee: Martin Bříza <mbriza>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: jgrulich, ltinkl, mbriza, me, pierluigi.fiorini, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/212830f2fe96715530df4be1f6287d10dec45c6c
Whiteboard: abrt_hash:1224a5da87d80dbdd0ab18de4e1975089bcc8e33;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:38:59 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 Mikael 2016-01-11 00:13:40 UTC 
Version-Release number of selected component:
sddm-0.13.0-4.fc22

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/bin/sddm
crash_function: QObject::connect
executable:     /usr/bin/sddm
global_pid:     1411
kernel:         4.2.8-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 QObject::connect at kernel/qobject.cpp:2662
 #1 SDDM::Auth::Private::setSocket at /usr/src/debug/sddm-0.13.0/src/auth/Auth.cpp:141
 #2 SDDM::Auth::SocketServer::handleNewConnection at /usr/src/debug/sddm-0.13.0/src/auth/Auth.cpp:93
 #3 QMetaObject::activate at kernel/qobject.cpp:3713
 #4 QLocalServerPrivate::_q_onNewConnection at socket/qlocalserver_unix.cpp:274
 #5 QMetaObject::activate at kernel/qobject.cpp:3713
 #7 QSocketNotifier::activated at .moc/moc_qsocketnotifier.cpp:134
 #8 QSocketNotifier::event at kernel/qsocketnotifier.cpp:260
 #9 notify at kernel/qcoreapplication.cpp:1038
 #10 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:965
Comment 1 Mikael 2016-01-11 00:13:46 UTC 
Created attachment 1113424 [details]
File: backtrace
Comment 2 Mikael 2016-01-11 00:13:48 UTC 
Created attachment 1113425 [details]
File: cgroup
Comment 3 Mikael 2016-01-11 00:13:49 UTC 
Created attachment 1113426 [details]
File: core_backtrace
Comment 4 Mikael 2016-01-11 00:13:51 UTC 
Created attachment 1113427 [details]
File: dso_list
Comment 5 Mikael 2016-01-11 00:13:52 UTC 
Created attachment 1113428 [details]
File: environ
Comment 6 Mikael 2016-01-11 00:13:53 UTC 
Created attachment 1113429 [details]
File: limits
Comment 7 Mikael 2016-01-11 00:13:54 UTC 
Created attachment 1113430 [details]
File: maps
Comment 8 Mikael 2016-01-11 00:13:55 UTC 
Created attachment 1113431 [details]
File: mountinfo
Comment 9 Mikael 2016-01-11 00:13:56 UTC 
Created attachment 1113432 [details]
File: namespaces
Comment 10 Mikael 2016-01-11 00:13:57 UTC 
Created attachment 1113433 [details]
File: open_fds
Comment 11 Mikael 2016-01-11 00:13:58 UTC 
Created attachment 1113434 [details]
File: proc_pid_status
Comment 12 Mikael 2016-01-11 00:13:59 UTC 
Created attachment 1113435 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 18:38:59 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.