I haven't give much thought nor put any effort to investigate further. I noticed there is a related issue opened upstream https://gitlab.gnome.org/World/secrets/-/issues/624. It's becoming a bit annoying to always have to press "wait" until the app start/init completes. NB: my F42 is not a clean/fresh install, but rather an upgraded system from previous version. [dacbarbos@vivobookone ~]$ printenv XDG_CURRENT_DESKTOP GNOME [dacbarbos@vivobookone ~]$ [dacbarbos@vivobookone ~]$ dnf info secrets Updating and loading repositories: keybase 100% | 30.8 KiB/s | 3.5 KiB | 00m00s Repositories loaded. Installed packages Name : secrets Epoch : 0 Version : 9.6 Release : 3.fc42 Architecture : noarch Installed size : 1.8 MiB Source : secrets-9.6-3.fc42.src.rpm From repository : fedora Summary : Manage your passwords URL : https://gitlab.gnome.org/World/secrets License : GPL-3.0-only Description : Secrets is a password manager which integrates perfectly with the GNOME : desktop and provides an easy and uncluttered interface for the management of : password databases. : : Features: : * Create or import KeePass safes : * Assign a color and additional attributes to entries : * Add attachments to your encrypted database : * Generate cryptographically strong passwords : * Change the password or keyfile of your database : * Quickly search your favorite entries : * Automatic database lock during inactivity : * Adaptive interface : * Support for two-factor authentication Vendor : Fedora Project [dacbarbos@vivobookone ~]$ Reproducible: Always Steps to Reproduce: 1. Open/run Secrets app 2. Observe hang/freeze 3. Actual Results: Unresponsiveness gets detected and I'm offered to either kill the app or wait a bit longer. This loop repeats itself until app's init logic completes. Expected Results: The app completes initialization and PW input field accepts typing the password to unlock the database. Additional Information: N/A
Same situation on my similar desktop environmement. The problem starts a month ago, where the input field of the password field was unable to accept an input for some time. Now the entire UI take 10 minutes to start. ctrace showed that a ressource was also unavailable short time, before the application became usable: [pid 5737] clock_gettime(CLOCK_MONOTONIC, {tv_sec=969, tv_nsec=852692000}) = 0 [pid 5737] clock_gettime(CLOCK_MONOTONIC, {tv_sec=969, tv_nsec=852732160}) = 0 [pid 5737] ppoll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}, {fd=14, events=POLLIN}], 3, {tv_sec=15, tv_nsec=87958000}, NULL, 8) = 1 ([{fd=5, revents=POLLIN}], left {tv_sec=13, tv_nsec=417715434}) [pid 5737] clock_gettime(CLOCK_MONOTONIC, {tv_sec=971, tv_nsec=523176431}) = 0 [pid 5737] recvmsg(5, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="/\0\0\0\0\0\f\0\2\323\16\0", iov_len=2808}, {iov_base="", iov_len=1288}], msg_iovlen=2, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_DONTWAIT|MSG_CMSG_CLOEXEC) = 12 [pid 5737] recvmsg(5, {msg_namelen=0}, MSG_DONTWAIT|MSG_CMSG_CLOEXEC) = -1 EAGAIN (Die Ressource ist zur Zeit nicht verfügbar) [pid 5737] clock_gettime(CLOCK_MONOTONIC, {tv_sec=971, tv_nsec=523433102}) = 0 [pid 5737] clock_gettime(CLOCK_MONOTONIC, {tv_sec=971, tv_nsec=523489395}) = 0
The problem is related to an 2 years old gnome settings. The application was starving and was using Xwayland, for any reason i do not know. After recreation of my user and a new setup the problem disappeared and Secrets started very fast and it was running using wayland.
I have to correct my previous analysis. I was able to fix the problem by reset of my gnome configuration. After this, the applications started and run without any problem. But as time going by, the application becomes remarkable slow again.
This message is a reminder that Fedora Linux 42 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13. 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 '42'. 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 42 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.