Bug 1949865 - [abrt] keepassxc: qt_message_fatal(): keepassxc killed by SIGABRT
Summary: [abrt] keepassxc: qt_message_fatal(): keepassxc killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: qt5-qtbase
Version: 34
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:8e61cd3732bda3f26973d766835...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-15 09:31 UTC by cooperbang
Modified: 2022-06-08 00:56 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-08 00:56:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (37.08 KB, text/plain)
2021-04-15 09:31 UTC, cooperbang
no flags Details
File: core_backtrace (3.21 KB, text/plain)
2021-04-15 09:31 UTC, cooperbang
no flags Details
File: cpuinfo (1.85 KB, text/plain)
2021-04-15 09:31 UTC, cooperbang
no flags Details
File: dso_list (781 bytes, text/plain)
2021-04-15 09:31 UTC, cooperbang
no flags Details
File: environ (2.95 KB, text/plain)
2021-04-15 09:31 UTC, cooperbang
no flags Details
File: limits (1.29 KB, text/plain)
2021-04-15 09:31 UTC, cooperbang
no flags Details
File: maps (3.90 KB, text/plain)
2021-04-15 09:31 UTC, cooperbang
no flags Details
File: mountinfo (2.57 KB, text/plain)
2021-04-15 09:31 UTC, cooperbang
no flags Details
File: open_fds (143 bytes, text/plain)
2021-04-15 09:31 UTC, cooperbang
no flags Details
File: proc_pid_status (1.38 KB, text/plain)
2021-04-15 09:31 UTC, cooperbang
no flags Details

Description cooperbang 2021-04-15 09:31:26 UTC
Version-Release number of selected component:
keepassxc-2.6.4-1.fc34

Additional info:
reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-90741f26-187d-40a2-811d-494d9dd1bf99.scope
cmdline:        keepassxc -platform xdg
crash_function: qt_message_fatal
executable:     /usr/bin/keepassxc
journald_cursor: s=3de56b232bba4d249bd4450baf3a7b47;i=1c5ce;b=d5441da93f3e40bc89393110f1441a83;m=1416e7808;t=5bfff3998b99d;x=100ee1a19644f6d4
kernel:         5.11.13-300.fc34.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 qt_message_fatal at global/qlogging.cpp:1914
 #3 QMessageLogger::fatal at global/qlogging.cpp:893
 #4 init_platform at kernel/qguiapplication.cpp:1254
 #5 QGuiApplicationPrivate::createPlatformIntegration at kernel/qguiapplication.cpp:1474
 #6 QGuiApplicationPrivate::createEventDispatcher at kernel/qguiapplication.cpp:1491
 #7 QCoreApplicationPrivate::init at kernel/qcoreapplication.cpp:834
 #8 QGuiApplicationPrivate::init at kernel/qguiapplication.cpp:1520
 #9 QApplicationPrivate::init at kernel/qapplication.cpp:513
 #10 QApplication::QApplication at kernel/qapplication.cpp:501
 #11 Application::Application at /usr/src/debug/keepassxc-2.6.4-1.fc34.x86_64/src/gui/Application.cpp:62

Comment 1 cooperbang 2021-04-15 09:31:31 UTC
Created attachment 1772097 [details]
File: backtrace

Comment 2 cooperbang 2021-04-15 09:31:33 UTC
Created attachment 1772098 [details]
File: core_backtrace

Comment 3 cooperbang 2021-04-15 09:31:35 UTC
Created attachment 1772099 [details]
File: cpuinfo

Comment 4 cooperbang 2021-04-15 09:31:36 UTC
Created attachment 1772100 [details]
File: dso_list

Comment 5 cooperbang 2021-04-15 09:31:38 UTC
Created attachment 1772101 [details]
File: environ

Comment 6 cooperbang 2021-04-15 09:31:39 UTC
Created attachment 1772102 [details]
File: limits

Comment 7 cooperbang 2021-04-15 09:31:41 UTC
Created attachment 1772103 [details]
File: maps

Comment 8 cooperbang 2021-04-15 09:31:42 UTC
Created attachment 1772104 [details]
File: mountinfo

Comment 9 cooperbang 2021-04-15 09:31:43 UTC
Created attachment 1772105 [details]
File: open_fds

Comment 10 cooperbang 2021-04-15 09:31:45 UTC
Created attachment 1772106 [details]
File: proc_pid_status

Comment 11 Germano Massullo 2021-04-15 10:00:57 UTC
Do you consent to shift this bugreport and its attachments from private to public? It's the only way I let darktable developers know about this bug

Comment 12 Germano Massullo 2021-04-15 10:01:23 UTC
(In reply to Germano Massullo from comment #11)
> Do you consent to shift this bugreport and its attachments from private to
> public? It's the only way I let darktable developers know about this bug

err I meant keepassxc developers

Comment 13 cooperbang 2021-04-15 10:18:22 UTC
yes, it´s ok. thanks.

Comment 14 Germano Massullo 2021-04-15 21:27:58 UTC
Upstream says the crash is not caused by KeepassXC, but Qt

Comment 15 Ben Cotton 2022-05-12 16:37:15 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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 '34'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 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 16 Ben Cotton 2022-06-08 00:56:41 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

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


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