Bug 25382 - Qt5 libs segfaults when run
Summary: Qt5 libs segfaults when run
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-30 01:03 CEST by Thierry Vignaud
Modified: 2021-05-17 02:52 CEST (History)
2 users (show)

See Also:
Source RPM: qtbase5-5.13.0-5.mga8
CVE:
Status comment:


Attachments

Description Thierry Vignaud 2019-08-30 01:03:01 CEST
Description of problem:
Qt libs can be run as program in order to get info. But they segfaults

$ /usr/lib64/libQt5Core.so.5
This is the QtCore library version Qt 5.13.0 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 8.3.1 20190719)
Copyright (C) 2016 The Qt Company Ltd.
Contact: http://www.qt.io/licensing/

Installation prefix: /usr
Library path:        lib64
Include path:        include/qt5
Erreur de segmentation (core dumped)

$ gdb -q /usr/lib64/libQt5Core.so.5
(gdb) r
Starting program: /usr/lib64/libQt5Core.so.5 
This is the QtCore library version Qt 5.13.0 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 8.3.1 20190719)
Copyright (C) 2016 The Qt Company Ltd.
Contact: http://www.qt.io/licensing/

Installation prefix: /usr
Library path:        lib64
Include path:        include/qt5

Program received signal SIGSEGV, Segmentation fault.
qDetectCpuFeatures () at tools/qsimd.cpp:538
538         quint64 f = detectProcessorFeatures();
Thierry Vignaud 2019-08-30 01:03:35 CEST

CC: (none) => mageia
Assignee: bugsquad => kde

Comment 1 Nicolas Lécureuil 2021-01-08 15:27:41 CET
is this still valid on cauldron ?
i can't reproduce
Comment 2 Aurelien Oudelet 2021-05-17 02:52:15 CEST
(In reply to Nicolas Lécureuil from comment #1)
> is this still valid on cauldron ?
> i can't reproduce

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
CC: (none) => ouaurelien
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.