Problem with QLog and accessing external databases

[Hb7DwKYc-aljY6fT9o]

Hello,

I need help. Since compiling QLog under 6.17.4-200.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Oct 19 18:47:49 UTC 2025 x86_64 GNU/Linux everything has been running well. I haven't filed this as a bug, as I think the app is fine, but suspect something is screwed with my Keyring - now.

If needed I will refile as a bug.

On launch of the app everything is fine, except the prompt for the keyring access has gone, If I go to settings, nothing happens there is a long pause and this box comes up:

In case the image doesn't load it says "Cannot get a password for QRZCOM from the Credential Store Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached".

If I click OK a similar warning box comes up for Log Book of the World:

"Cannot get a password for LoTW from the Credential Store Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached"

Then the same for eqsl:

"Cannot get a password for eQSL from the Credential Store Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached"

After pressing OK again I get:

Cannot get a password for QRZCOMAPI from the Credential Store Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached

Then I get (I have never used cloud log by the way):

"Cannot get a password for Cloudlog from the Credential Store, Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached"

Next the settings menus finally open. If I go to any of the logins, I have my call-sign saved but none of the passwords are visible. If I enter my QRZ.com password into the call book section, and try to 'save' it will not save. The test button will function correctly showing the link to web, my cal-sign and password are all good.

Then this error box pops up:

"Cannot save a password for QRZCOM to the Credential Store Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached"

This all suggests a password storage problem rather than a bug, but I'm a loss how to fix it. I would appreciate any help as I really have no knowledge of how keychains work and with QLog.

Many thanks
Bob

UPDATE

Following a hunch, it appears that if I disable SELinux QLog now asks to login to the key chain and the error on running Qlog from the command line:

(qlog:55490): dbind-WARNING **: 22:09:11.269: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.a11y.Bus: Permission denied

has gone. Only error now is:

Can now save passwords etc straightforwardly. However eQSL does not work properly yet. Download error now is:

QRZ.com anfd LOTW are fine.

First priotrity is to see the impact of SELinux as I don't want to run the machine unprotected and then to fix the eQSL access whcih is a separate issue (I think).

[aa5sh]

I am not a Linux user but I know something similar has come up in the past. Here is a discussion. It may have pointers to help or at least I think a few more details on your situation may be needed: #203

[Hb7DwKYc-aljY6fT9o]

Yes I think this is a related problem, though #203 a different flavour of Linux with a different desktop. I did make sure that gnome keyring is installed, though by doing so it didn't cure the problem. I noticed I am also getting these errors launching QLog from the command line:

(qlog:55490): dbind-WARNING **: 22:09:11.269: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.a11y.Bus: Permission denied

(qlog:55490): Gtk-WARNING **: 22:09:12.319: Theme parsing error: :1:0: Expected a valid selector

The first one is serious I think and needs further investigation.

[aa5sh]

Not sure if you made any headway. But since I know very little about Linux I passed these errors by ChatGPT this is what it said: 🟡 1. dbind-WARNING: AT-SPI: Error retrieving accessibility bus address

Meaning:
This comes from the GNOME Assistive Technology Service Provider Interface (AT-SPI). It’s trying to start the accessibility (a11y) D-Bus service but lacks permission or cannot find the right binary (org.a11y.Bus).

Causes:
• Missing or misconfigured at-spi2-core package.
• Running Qt in a minimal environment (e.g., over SSH, or without full GNOME session).
• Sandboxed or AppImage builds that block D-Bus.

Fix Options:
1. Install missing packages (most common fix):
sudo apt install at-spi2-core dbus-x11

🟡 2. Gtk-WARNING: Theme parsing error: :1:0: Expected a valid selector

Meaning:
This comes from GTK trying to parse a theme CSS line that Qt’s QGtkStyle calls indirectly. It’s purely cosmetic.

Fix Options:
• Update GTK theme:
sudo apt install gnome-themes-extra

Please take these as not from any knowledge on my part other than a quick check/google.

[Hb7DwKYc-aljY6fT9o]

Thanks aa5sh,

I'm not sure how I solved it exactly; but i got an SEL error related to QLog, which I created a module for (sorry I lost the details) and did relabeling a couple of times as it inconsistently fixed the error. I then deleted the keychain folder and replaced it with an earlier folder from a back-up and low and behold it now works as it did originally (ie., on asking for a database download/upload QLog now prompts for the keychain password (which is the same as before) and when entered all is well.

The other problem was to do was with accessing the eqsl.cc data for QLog. I found o-line somewhere that although a long password works with the eqsl.cc website, it may not with QLog. So I found if I limited the password length to no more than 14 characters, then all was well with QLog.

As for the information you got from AI, I've no way of knowing if that will help, but will look into that in due course as if I run QLog from the command line I still get a GTK error
"(qlog:191909): Gtk-WARNING **: 18:33:05.799: Theme parsing error: :1:0: Expected a valid selector"

Any Dbus errors seem to have gone away for now and may be related to the SELinux security set-up.

All the best
Bob