Bug 1368821

Summary: [abrt] lxqt-about: qt_message_fatal(): lxqt-about killed by SIGABRT
Product: [Fedora] Fedora Reporter: a.thiaville
Component: tigervncAssignee: Jan Grulich <jgrulich>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: bphinz, helio, jgrulich, projects.rg, rdieter, ti.eugene, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/5baa28938ea326f8fd40887fe627681b787e8a69
Whiteboard: abrt_hash:049a5e957fcbce839e7b12d399d9de4d7c107366;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-12 08:59:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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 a.thiaville 2016-08-21 15:50:37 UTC 
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
Comment 1 a.thiaville 2016-08-21 15:50:43 UTC 
Created attachment 1192611 [details]
File: backtrace
Comment 2 a.thiaville 2016-08-21 15:50:44 UTC 
Created attachment 1192612 [details]
File: cgroup
Comment 3 a.thiaville 2016-08-21 15:50:46 UTC 
Created attachment 1192613 [details]
File: core_backtrace
Comment 4 a.thiaville 2016-08-21 15:50:47 UTC 
Created attachment 1192614 [details]
File: dso_list
Comment 5 a.thiaville 2016-08-21 15:50:49 UTC 
Created attachment 1192615 [details]
File: environ
Comment 6 a.thiaville 2016-08-21 15:50:50 UTC 
Created attachment 1192616 [details]
File: limits
Comment 7 a.thiaville 2016-08-21 15:50:52 UTC 
Created attachment 1192617 [details]
File: maps
Comment 8 a.thiaville 2016-08-21 15:50:54 UTC 
Created attachment 1192618 [details]
File: mountinfo
Comment 9 a.thiaville 2016-08-21 15:50:55 UTC 
Created attachment 1192619 [details]
File: namespaces
Comment 10 a.thiaville 2016-08-21 15:50:56 UTC 
Created attachment 1192620 [details]
File: open_fds
Comment 11 a.thiaville 2016-08-21 15:50:58 UTC 
Created attachment 1192621 [details]
File: proc_pid_status
Comment 12 a.thiaville 2016-08-21 15:51:00 UTC 
Created attachment 1192622 [details]
File: var_log_messages
Comment 13 Raphael Groner 2016-08-28 14:02:48 UTC 
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.
Comment 14 Raphael Groner 2016-08-30 16:49:16 UTC 
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.
Comment 15 Jan Grulich 2016-09-12 08:59:42 UTC 

*** This bug has been marked as a duplicate of bug 1371102 ***