Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1510733 - [abrt] kdeconnectd: qt_message_fatal(): kdeconnectd killed by SIGABRT
Summary: [abrt] kdeconnectd: qt_message_fatal(): kdeconnectd killed by SIGABRT
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-connect
Version: 26
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Jiri Eischmann
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:6850db307c2fdbcab1ccd9a4f98...
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-08 06:11 UTC by vikram goyal
Modified: 2018-05-29 11:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-05-29 11:41:14 UTC

Attachments (Terms of Use)
File: backtrace (deleted)
2017-11-08 06:11 UTC, vikram goyal
no flags Details
File: cgroup (deleted)
2017-11-08 06:11 UTC, vikram goyal
no flags Details
File: core_backtrace (deleted)
2017-11-08 06:11 UTC, vikram goyal
no flags Details
File: cpuinfo (deleted)
2017-11-08 06:11 UTC, vikram goyal
no flags Details
File: dso_list (deleted)
2017-11-08 06:11 UTC, vikram goyal
no flags Details
File: environ (deleted)
2017-11-08 06:11 UTC, vikram goyal
no flags Details
File: limits (deleted)
2017-11-08 06:11 UTC, vikram goyal
no flags Details
File: maps (deleted)
2017-11-08 06:12 UTC, vikram goyal
no flags Details
File: open_fds (deleted)
2017-11-08 06:12 UTC, vikram goyal
no flags Details
File: proc_pid_status (deleted)
2017-11-08 06:12 UTC, vikram goyal
no flags Details
File: var_log_messages (deleted)
2017-11-08 06:12 UTC, vikram goyal
no flags Details

Description vikram goyal 2017-11-08 06:11:34 UTC
Description of problem:
the crash happened at login

Version-Release number of selected component:

Additional info:
reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/kdeconnectd
crash_function: qt_message_fatal
executable:     /usr/libexec/kdeconnectd
journald_cursor: s=fb30be056aa442a3be1bcc9d571455a0;i=3a559;b=4fc1069a0ad54015862d40bced899b61;m=5ee02c8f1e;t=55d725e274232;x=765c4451dfabdf60
kernel:         4.13.9-200.fc26.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 qt_message_fatal at global/qlogging.cpp:1682
 #3 QMessageLogger::fatal at global/qlogging.cpp:793
 #4 QXcbConnection::QXcbConnection at qxcbconnection.cpp:595
 #5 QXcbIntegration::QXcbIntegration at qxcbintegration.cpp:186
 #6 QXcbIntegrationPlugin::create at qxcbmain.cpp:56
 #7 QPlatformIntegrationFactory::create at kernel/qplatformintegrationfactory.cpp:71
 #8 init_platform at kernel/qguiapplication.cpp:1094
 #9 QGuiApplicationPrivate::createPlatformIntegration at kernel/qguiapplication.cpp:1257
 #10 QGuiApplicationPrivate::createEventDispatcher at kernel/qguiapplication.cpp:1274
 #11 QCoreApplicationPrivate::init at kernel/qcoreapplication.cpp:787

Potential duplicate: bug 1264244

Comment 1 vikram goyal 2017-11-08 06:11:44 UTC
Created attachment 1349259 [details]
File: backtrace

Comment 2 vikram goyal 2017-11-08 06:11:46 UTC
Created attachment 1349260 [details]
File: cgroup

Comment 3 vikram goyal 2017-11-08 06:11:48 UTC
Created attachment 1349261 [details]
File: core_backtrace

Comment 4 vikram goyal 2017-11-08 06:11:51 UTC
Created attachment 1349262 [details]
File: cpuinfo

Comment 5 vikram goyal 2017-11-08 06:11:53 UTC
Created attachment 1349263 [details]
File: dso_list

Comment 6 vikram goyal 2017-11-08 06:11:55 UTC
Created attachment 1349264 [details]
File: environ

Comment 7 vikram goyal 2017-11-08 06:11:57 UTC
Created attachment 1349265 [details]
File: limits

Comment 8 vikram goyal 2017-11-08 06:12:00 UTC
Created attachment 1349266 [details]
File: maps

Comment 9 vikram goyal 2017-11-08 06:12:02 UTC
Created attachment 1349267 [details]
File: open_fds

Comment 10 vikram goyal 2017-11-08 06:12:04 UTC
Created attachment 1349268 [details]
File: proc_pid_status

Comment 11 vikram goyal 2017-11-08 06:12:06 UTC
Created attachment 1349269 [details]
File: var_log_messages

Comment 12 Rex Dieter 2017-11-08 11:47:14 UTC
from var_log_messages:

Nov 08 11:27:49 kdeconnectd[6603]: QXcbConnection: Could not connect to display :1

Comment 14 Fedora End Of Life 2018-05-03 08:15:07 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 15 Fedora End Of Life 2018-05-29 11:41:14 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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

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.