Bug 1880290

Summary: Segfault on starting Qt application
Product: [Fedora] Fedora Reporter: Vitaly <vitaly>
Component: qt5-qtbaseAssignee: Than Ngo <than>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jgrulich, jreznik, kde-sig, onyeibo, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-21 15:59:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vitaly 2020-09-18 08:36:12 UTC 
Description of problem:
Segfault on Qt application (Telegram Desktop) start.

Version-Release number of selected component (if applicable):
5.15.1-1.fc34

How reproducible:
Always.

Steps to Reproduce:
1. Download Telegram Desktop's RPM from RPM Fusion Koji: http://koji.rpmfusion.org/koji/buildinfo?buildID=16663
2. Install with RPM Fusion repo enabled.
3. Run /usr/bin/telegram-desktop

Actual results:
Segmentation fault:

#0  0x00007fb448beed6b _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x287d6b)
#1  0x00007fb448f9aed2 _ZN15QGuiApplication11screenAddedEP7QScreen (libQt5Gui.so.5 + 0x113ed2)
#2  0x00007fb448f8b22c _ZN22QWindowSystemInterface17handleScreenAddedEP15QPlatformScreenb (libQt5Gui.so.5 + 0x10422c)
#3  0x00007fb4342c42a0 _ZN14QXcbConnection17initializeScreensEv (libQt5XcbQpa.so.5 + 0x632a0)
#4  0x00007fb43429fbc0 _ZN14QXcbConnectionC1EP19QXcbNativeInterfacebjPKc (libQt5XcbQpa.so.5 + 0x3ebc0)
#5  0x00007fb4342a2843 _ZN15QXcbIntegrationC1ERK11QStringListRiPPc (libQt5XcbQpa.so.5 + 0x41843)
#6  0x00007fb44b71b46f _ZN21QXcbIntegrationPlugin6createERK7QStringRK11QStringListRiPPc (libqxcb.so + 0x246f)
#7  0x00007fb448f93f3b _ZN27QPlatformIntegrationFactory6createERK7QStringRK11QStringListRiPPcS2_ (libQt5Gui.so.5 + 0x10cf3b)
#8  0x00007fb448f9e680 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 0x117680)
#9  0x00007fb448f9fc90 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x118c90)
#10 0x00007fb448bc6e96 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x25fe96)
#11 0x00007fb448fa25e4 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x11b5e4)
#12 0x00007fb4482ebef9 _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5 + 0x16cef9)
#13 0x0000564fca929c0d _ZN4Core8Launcher18executeApplicationEv (telegram-desktop + 0x9f5c0d)
#14 0x0000564fca92ad98 _ZN4Core8Launcher4execEv (telegram-desktop + 0x9f6d98)
#15 0x0000564fca37475c main (telegram-desktop + 0x44075c)
#16 0x00007fb44788e192 __libc_start_main (libc.so.6 + 0x28192)
#17 0x0000564fca3a1dce _start (telegram-desktop + 0x46ddce)

Stack trace of thread 3277:
#0  0x00007fb44795c94f __poll (libc.so.6 + 0xf694f)
#1  0x00007fb4480d7842 _xcb_conn_wait.part.0 (libxcb.so.1 + 0xd842)
#2  0x00007fb4480d91cc xcb_wait_for_event (libxcb.so.1 + 0xf1cc)
#3  0x00007fb4342c0c70 _ZN14QXcbEventQueue3runEv (libQt5XcbQpa.so.5 + 0x5fc70)
#4  0x00007fb448a2f4bc _ZN14QThreadPrivate5startEPv (libQt5Core.so.5 + 0xc84bc)
#5  0x00007fb44b4b83f9 start_thread (libpthread.so.0 + 0x93f9)
#6  0x00007fb447967ad3 __clone (libc.so.6 + 0x101ad3)


Expected results:
Successful launch.

Additional info:
Comment 1 Vitaly 2020-09-21 15:59:58 UTC 
Building Telegram Desktop without LTO fixed this issue.