Version-Release number of selected component: kdeconnectd-1.0.3-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/libexec/kdeconnectd crash_function: qt_message_fatal executable: /usr/libexec/kdeconnectd global_pid: 14956 kernel: 4.10.13-200.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #2 qt_message_fatal at global/qlogging.cpp:1682 #4 QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) at qxcbconnection.cpp:595 #5 QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) at qxcbintegration.cpp:186 #6 QXcbIntegrationPlugin::create(QString const&, QStringList const&, int&, char**) at qxcbmain.cpp:56 #7 QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) 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 #12 QGuiApplicationPrivate::init() at kernel/qguiapplication.cpp:1297
Created attachment 1279974 [details] File: backtrace
Created attachment 1279975 [details] File: cgroup
Created attachment 1279976 [details] File: core_backtrace
Created attachment 1279977 [details] File: dso_list
Created attachment 1279978 [details] File: environ
Created attachment 1279979 [details] File: limits
Created attachment 1279980 [details] File: maps
Created attachment 1279981 [details] File: mountinfo
Created attachment 1279982 [details] File: namespaces
Created attachment 1279983 [details] File: open_fds
Created attachment 1279984 [details] File: proc_pid_status
Created attachment 1279985 [details] File: var_log_messages
from var_log_messages: localhost.localdomain kdeconnectd[14956]: QXcbConnection: Could not connect to display :0 likely invalid xauth issue and dup of bug #1370222 (or something worse) *** This bug has been marked as a duplicate of bug 1370222 ***