Bug 1318018 - [abrt] sddm: QObject::connect(): sddm killed by SIGSEGV
Summary: [abrt] sddm: QObject::connect(): sddm killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: sddm
Version: 23
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Martin Bříza
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:1224a5da87d80dbdd0ab18de4e1...
: 1344852 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-15 18:55 UTC by M_M
Modified: 2016-12-20 19:28 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 19:28:09 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (52.55 KB, text/plain)
2016-03-15 18:55 UTC, M_M
no flags Details
File: cgroup (198 bytes, text/plain)
2016-03-15 18:55 UTC, M_M
no flags Details
File: core_backtrace (5.73 KB, text/plain)
2016-03-15 18:55 UTC, M_M
no flags Details
File: dso_list (3.96 KB, text/plain)
2016-03-15 18:55 UTC, M_M
no flags Details
File: environ (72 bytes, text/plain)
2016-03-15 18:55 UTC, M_M
no flags Details
File: exploitable (82 bytes, text/plain)
2016-03-15 18:55 UTC, M_M
no flags Details
File: limits (1.29 KB, text/plain)
2016-03-15 18:55 UTC, M_M
no flags Details
File: maps (18.99 KB, text/plain)
2016-03-15 18:55 UTC, M_M
no flags Details
File: mountinfo (2.91 KB, text/plain)
2016-03-15 18:55 UTC, M_M
no flags Details
File: namespaces (85 bytes, text/plain)
2016-03-15 18:55 UTC, M_M
no flags Details
File: open_fds (1.38 KB, text/plain)
2016-03-15 18:55 UTC, M_M
no flags Details
File: proc_pid_status (1016 bytes, text/plain)
2016-03-15 18:55 UTC, M_M
no flags Details
File: var_log_messages (424 bytes, text/plain)
2016-03-15 18:55 UTC, M_M
no flags Details

Description M_M 2016-03-15 18:55:20 UTC
Version-Release number of selected component:
sddm-0.13.0-4.fc23

Additional info:
reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        /usr/bin/sddm
crash_function: QObject::connect
executable:     /usr/bin/sddm
global_pid:     1091
kernel:         4.4.4-301.fc23.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 QCoreApplication::notify at kernel/qcoreapplication.cpp:1038
 #10 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:965

Potential duplicate: bug 1297238

Comment 1 M_M 2016-03-15 18:55:26 UTC
Created attachment 1136701 [details]
File: backtrace

Comment 2 M_M 2016-03-15 18:55:27 UTC
Created attachment 1136702 [details]
File: cgroup

Comment 3 M_M 2016-03-15 18:55:28 UTC
Created attachment 1136703 [details]
File: core_backtrace

Comment 4 M_M 2016-03-15 18:55:30 UTC
Created attachment 1136704 [details]
File: dso_list

Comment 5 M_M 2016-03-15 18:55:31 UTC
Created attachment 1136705 [details]
File: environ

Comment 6 M_M 2016-03-15 18:55:32 UTC
Created attachment 1136706 [details]
File: exploitable

Comment 7 M_M 2016-03-15 18:55:33 UTC
Created attachment 1136707 [details]
File: limits

Comment 8 M_M 2016-03-15 18:55:35 UTC
Created attachment 1136708 [details]
File: maps

Comment 9 M_M 2016-03-15 18:55:37 UTC
Created attachment 1136709 [details]
File: mountinfo

Comment 10 M_M 2016-03-15 18:55:38 UTC
Created attachment 1136710 [details]
File: namespaces

Comment 11 M_M 2016-03-15 18:55:40 UTC
Created attachment 1136711 [details]
File: open_fds

Comment 12 M_M 2016-03-15 18:55:41 UTC
Created attachment 1136712 [details]
File: proc_pid_status

Comment 13 M_M 2016-03-15 18:55:43 UTC
Created attachment 1136713 [details]
File: var_log_messages

Comment 14 webdesigner 2016-06-11 18:29:32 UTC
*** Bug 1344852 has been marked as a duplicate of this bug. ***

Comment 15 Fedora End Of Life 2016-11-24 16:06:11 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora  'version'
of '23'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 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 this bug is closed as described in the policy above.

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.

Comment 16 Fedora End Of Life 2016-12-20 19:28:09 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.


Note You need to log in before you can comment on or make changes to this bug.