Hide Forgot
Version-Release number of selected component: lxqt-about-0.10.0-5.fc24 Additional info: reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/bin/lxqt-about crash_function: qt_message_fatal executable: /usr/bin/lxqt-about global_pid: 16429 kernel: 4.6.6-300.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #2 qt_message_fatal at global/qlogging.cpp:1648 #3 QMessageLogger::fatal at global/qlogging.cpp:790 #4 QXcbConnection::QXcbConnection at qxcbconnection.cpp:585 #5 QXcbIntegration::QXcbIntegration at qxcbintegration.cpp:179 #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:1058 #10 QGuiApplicationPrivate::createPlatformIntegration at kernel/qguiapplication.cpp:1227 #11 QGuiApplicationPrivate::createEventDispatcher at kernel/qguiapplication.cpp:1244
Created attachment 1192611 [details] File: backtrace
Created attachment 1192612 [details] File: cgroup
Created attachment 1192613 [details] File: core_backtrace
Created attachment 1192614 [details] File: dso_list
Created attachment 1192615 [details] File: environ
Created attachment 1192616 [details] File: limits
Created attachment 1192617 [details] File: maps
Created attachment 1192618 [details] File: mountinfo
Created attachment 1192619 [details] File: namespaces
Created attachment 1192620 [details] File: open_fds
Created attachment 1192621 [details] File: proc_pid_status
Created attachment 1192622 [details] File: var_log_messages
It could be useful to know what message gets tried to be logged. Can you reproduce this crash? Propably http://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/platforms/xcb/qxcbconnection.cpp#n594 594 if (Q_UNLIKELY(!m_connection || xcb_connection_has_error(m_connection))) 595 qFatal("QXcbConnection: Could not connect to display %s", m_displayName.constData()); ... but that would mean $DISPLAY is not set properly or the like. Also it could be a bug in XCB or XLIB.
I suppose you mean tigervnc-server instead of vnc-server. vnc and tightvnc are both orphaned in favor of tigervnc. Reassigning to ask for help there.
*** This bug has been marked as a duplicate of bug 1371102 ***