does this still happen for you?

if so, do you have gnome-keyring installed on your system?

1)Yes, it's still happening.
2)I have the gnome-keyring deb installed.

You're using the flatpak from flathub and not from KDE's flatpak repo, right?

(In reply to Tobias Fella from comment #3)
> You're using the flatpak from flathub and not from KDE's flatpak repo, right?

Yep.  Flathub is the only remote I have configured.

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

I provided the requested info.

Yes, sorry, I've reset the status so the bug won't be closed

Hi, sorry for getting back to this so late. I'm a bit confused by the error, according to the libQuotient source, the "7" should actually be a string that's more useful than "Other error" (which is code 7). There's been two releases of both neochat and libQuotient since your bug report, would you mind updating and checking if it still happens?

It's still happening with NeoChat 23.04.0 (flatpak).  I also tried uninstalling and deleting the app data (with the --delete-data flatpak flag) and reinstalling: it didn't make a difference.  Here's the terminal output from following the same steps as in the original report:

flatpak run org.kde.neochat 
Gtk-Message: 20:18:55.345: Failed to load module "xapp-gtk3-module"
Qt: Session management error: None of the authentication protocols specified are supported
quotient.jobs: Won't proceed with the abandoned request: "GET https://m/.well-known/matrix/client"
quotient.jobs: "GetWellknownJob" stopped with empty network reply
quotient.jobs: No valid HTTP headers from GET https://m/.well-known/matrix/client
quotient.jobs: "GetWellknownJob" status NetworkError: Host m not found
quotient.jobs: "GetWellknownJob": retry #1 in 5 s
quotient.jobs: Won't proceed with the abandoned request: "GET https://ma/.well-known/matrix/client"
quotient.jobs: "GetWellknownJob" stopped with empty network reply
quotient.jobs: No valid HTTP headers from GET https://ma/.well-known/matrix/client
quotient.jobs: "GetWellknownJob" status NetworkError: Host ma not found
quotient.jobs: "GetWellknownJob": retry #1 in 5 s
quotient.jobs: Won't proceed with the abandoned request: "GET https://mat/.well-known/matrix/client"
quotient.jobs: "GetWellknownJob" stopped with empty network reply
quotient.jobs: No valid HTTP headers from GET https://mat/.well-known/matrix/client
quotient.jobs: "GetWellknownJob" status NetworkError: Host mat not found
quotient.jobs: "GetWellknownJob": retry #1 in 5 s
quotient.jobs: Won't proceed with the abandoned request: "GET https://matr/.well-known/matrix/client"
quotient.jobs: "GetWellknownJob" stopped with empty network reply
quotient.jobs: No valid HTTP headers from GET https://matr/.well-known/matrix/client
quotient.jobs: "GetWellknownJob" status NetworkError: Host matr not found
quotient.jobs: "GetWellknownJob": retry #1 in 5 s
quotient.jobs: Won't proceed with the abandoned request: "GET https://matri/.well-known/matrix/client"
quotient.jobs: "GetWellknownJob" stopped with empty network reply
quotient.jobs: No valid HTTP headers from GET https://matri/.well-known/matrix/client
quotient.jobs: "GetWellknownJob" status NetworkError: Host matri not found
quotient.jobs: "GetWellknownJob": retry #1 in 5 s
quotient.jobs: Won't proceed with the abandoned request: "GET https://matrix/.well-known/matrix/client"
quotient.jobs: "GetWellknownJob" stopped with empty network reply
quotient.jobs: No valid HTTP headers from GET https://matrix/.well-known/matrix/client
quotient.jobs: "GetWellknownJob" status NetworkError: Host matrix not found
quotient.jobs: "GetWellknownJob": retry #1 in 5 s
quotient.jobs: Won't proceed with the abandoned request: "GET https://matrix.o/.well-known/matrix/client"
quotient.jobs: "GetWellknownJob" stopped with empty network reply
quotient.jobs: No valid HTTP headers from GET https://matrix.o/.well-known/matrix/client
quotient.jobs: "GetWellknownJob" status NetworkError: Host matrix.o not found
quotient.jobs: "GetWellknownJob": retry #1 in 5 s
quotient.jobs: Won't proceed with the abandoned request: "GET https://matrix.or/.well-known/matrix/client"
quotient.jobs: "GetWellknownJob" stopped with empty network reply
quotient.jobs: No valid HTTP headers from GET https://matrix.or/.well-known/matrix/client
quotient.jobs: "GetWellknownJob" status NetworkError: Host matrix.or not found
quotient.jobs: "GetWellknownJob": retry #1 in 5 s
quotient.jobs: Won't proceed with the abandoned request: "GET https://matrix.org/.well-known/matrix/client"
quotient.jobs: "GetWellknownJob" stopped with empty network reply
quotient.main: .well-known URL for "matrix.org" is "https://matrix-client.matrix.org"
quotient.e2ee: Error loading pickling key - please fix your keychain: "org.freedesktop.DBus.Error.ServiceUnknown"
ASSERT: "maybePicklingKey.has_value()" in file /run/build/libquotient/Quotient/connection.cpp, line 379

So the error now has a string, "org.freedesktop.DBus.Error.ServiceUnknown", instead of the 7 it had before.

Is gnoe-keyring running?

Meant to say "gnome-keyring", of course

I think so?  I don't really understand gnome-keyring, but the deb package is installed along with seahorse.  Running seahorse shows a bunch of keys.  I also tried running neochat while Seahorse is open and unlocked, and I got the same error message.

Also, gnome-keyring version shows:
gnome-keyring: 40.0

Extra information: I AM able to log in to the Quaternion flatpak, so whatever the issue is it doesn't affect all libquotient clients.

There's been an update to the flatpak that probably fixes this; can you check?

I just checked and it works perfectly now.  Thank you so much!