Bug 2085290

Summary: [abrt] ksnip: qt_message_fatal(): ksnip killed by SIGABRT
Product: [Fedora] Fedora Reporter: Mr. Beedell, Roke Julian Lockhart (RJLB) <8ru2u4gz>
Component: qt5-qtbaseAssignee: Than Ngo <than>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 37CC: jgrulich, jreznik, kde-sig, rdieter, than, travier, vitaly
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ccd8e1271d57f1ed3e11f740222b3b1dd79e2725
Whiteboard: abrt_hash:2bd793f73d23a732ddc6e3d7095ade6db34fa030;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-12-05 21:07:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Mr. Beedell, Roke Julian Lockhart (RJLB) 2022-05-12 23:02:42 UTC 
Description of problem:
This occurred subsequent to my 1st graphical authentication of root from the TTY.

Version-Release number of selected component:
ksnip-1.9.2-2.fc36

Additional info:
reporter:       libreport-2.17.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-0.slice/session-9.scope
cmdline:        ksnip
crash_function: qt_message_fatal
executable:     /usr/bin/ksnip
journald_cursor: s=a6565a4f102f46b481ccc82860475de8;i=5fc1;b=bbc282c0f4a24df4b9f777a2df89d54a;m=1f93486fb;t=5debe9e3b2aa0;x=e2081a7c44c652dc
kernel:         5.18.0-0.rc5.20220506gitfe27d189e3f42e3.44.fc37.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (8 frames)
 #4 qt_message_fatal at global/qlogging.cpp:1914
 #5 QMessageLogger::fatal at global/qlogging.cpp:893
 #6 init_platform at kernel/qguiapplication.cpp:1254
 #7 QGuiApplicationPrivate::createPlatformIntegration at kernel/qguiapplication.cpp:1474
 #8 QGuiApplicationPrivate::createEventDispatcher at kernel/qguiapplication.cpp:1491
 #9 QCoreApplicationPrivate::init at kernel/qcoreapplication.cpp:835
 #10 QGuiApplicationPrivate::init at kernel/qguiapplication.cpp:1520
 #11 QApplicationPrivate::init at kernel/qapplication.cpp:513
Comment 1 Mr. Beedell, Roke Julian Lockhart (RJLB) 2022-05-12 23:02:45 UTC 
Created attachment 1879188 [details]
File: backtrace
Comment 2 Mr. Beedell, Roke Julian Lockhart (RJLB) 2022-05-12 23:02:46 UTC 
Created attachment 1879189 [details]
File: core_backtrace
Comment 3 Mr. Beedell, Roke Julian Lockhart (RJLB) 2022-05-12 23:02:47 UTC 
Created attachment 1879190 [details]
File: cpuinfo
Comment 4 Mr. Beedell, Roke Julian Lockhart (RJLB) 2022-05-12 23:02:48 UTC 
Created attachment 1879191 [details]
File: dso_list
Comment 5 Mr. Beedell, Roke Julian Lockhart (RJLB) 2022-05-12 23:02:49 UTC 
Created attachment 1879192 [details]
File: environ
Comment 6 Mr. Beedell, Roke Julian Lockhart (RJLB) 2022-05-12 23:02:50 UTC 
Created attachment 1879193 [details]
File: limits
Comment 7 Mr. Beedell, Roke Julian Lockhart (RJLB) 2022-05-12 23:02:51 UTC 
Created attachment 1879194 [details]
File: maps
Comment 8 Mr. Beedell, Roke Julian Lockhart (RJLB) 2022-05-12 23:02:52 UTC 
Created attachment 1879195 [details]
File: mountinfo
Comment 9 Mr. Beedell, Roke Julian Lockhart (RJLB) 2022-05-12 23:02:53 UTC 
Created attachment 1879196 [details]
File: open_fds
Comment 10 Mr. Beedell, Roke Julian Lockhart (RJLB) 2022-05-12 23:02:54 UTC 
Created attachment 1879197 [details]
File: proc_pid_status
Comment 11 Vitaly 2022-05-13 14:27:49 UTC 
Crashed in Qt internals. Changing component to qt5-qtbase.
Comment 12 Ben Cotton 2022-08-09 13:15:42 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.
Comment 13 Aoife Moloney 2023-11-23 00:11:51 UTC 
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 14 Aoife Moloney 2023-12-05 21:07:00 UTC 
Fedora Linux 37 entered end-of-life (EOL) status on None.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.