SUMMARY *** The nightly flatpak let me connect to an account a few weeks ago. But when I start it now, it throws this error `Unable to read access token: org.freedesktop.DBus.Error.ServiceUnknown` and is stuck in an infinite loading loop. When I go to the settings, there is no account connected. When I tried to connect one today, neochat crashed with the following report: ``` PID: 20402 (neochat) Signal: 6 (ABRT) Timestamp: Sat 2022-11-26 14:43:10 CET (34min ago) Command Line: neochat Executable: /app/bin/neochat Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-flatpak-org.kde.neochat-20391.scope Unit: user@1000.service User Unit: app-flatpak-org.kde.neochat-20391.scope Slice: user-1000.slice Boot ID: cb20f7c350a74cf28b9b89a882207353 Machine ID: aaed9f33bbdd4ea696f3abba99c4043 Storage: /var/lib/systemd/coredump/core.neochat.1000.cb20f7c350a74cf28b9b89a882207353.20402.1669470190000000.zst (present) Size on Disk: 7.5M Message: Process 20402 (neochat) of user 1000 dumped core. Stack trace of thread 2: #0 0x00007fd80ca5949b n/a (/usr/lib/x86_64-linux-gnu/libc-2.33.so + 0x3949b) #1 0x00007fd80ca42857 n/a (/usr/lib/x86_64-linux-gnu/libc-2.33.so + 0x22857) #2 0x00007fd80d09dbb7 n/a (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.7 + 0x9dbb7) #3 0x0000003000000028 n/a (n/a + 0x0) ELF object binary architecture: AMD x86-64 ``` *** STEPS TO REPRODUCE 1. Install the nightly flatpak on Crystal Linux 2. run it 3. Connect an account if possible 4. Close the app and shutdown the computer 5. restart both OBSERVED RESULT No account connected, error, infinite loading, crash when trying to connect an account EXPECTED RESULT remember the connected account and let me connect new ones SOFTWARE/OS VERSIONS Operating System: Crystal Linux KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 6.0.9-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: TUXEDO Product Name: TUXEDO Aura 15 Gen1 System Version: Not Applicable ADDITIONAL INFORMATION
Alright, I seem to have fixed this by installing gnome-keyring. Maybe you can make it some sort of dependency?
(In reply to accounts from comment #1) > Alright, I seem to have fixed this by installing gnome-keyring. Maybe you > can make it some sort of dependency? Hhhh, but the error I got changed to `the name org.freedesktop.secrets was not provided by any .service file` which made me find that fix. So maybe this is not the fix for my original error, but for this very similar one. However, with this fixed, I also did not encounter the original error yet, so idk, it seems to be fixed.
That sounds like it would cause your original error, yes. Unfortunately we can't add dependencies outside of the flatpak
Nope, I got the first error and crash behaviour again. Sorry for the confusion. The other error was there because I ran the native arch package, but on the nightly flatpak, I still have this bug.
Please do flatpak uninstall --delete-data org.kde.neochat Then reinstall the flatpak login, restart neochat and check if it happens again instantly
I uninstalled, deleted its data, reinstalled and tried to login. It crashes after entering the password and hitting enter with the following crash details: PID: 2645 (neochat) UID: 1000 GID: 1000 Signal: 6 (ABRT) Timestamp: Mon 2022-12-05 22:48:26 CET (1min 3s ago) Command Line: neochat Executable: /app/bin/neochat Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-flatpak-org.kde.neochat-2636.scope Unit: user@1000.service User Unit: app-flatpak-org.kde.neochat-2636.scope Slice: user-1000.slice Owner UID: 1000 Boot ID: d248de07e68d4c529ac4d811ad16ce19 Machine ID: aaed9f33bbdd4ea696f3abba99c40432 Hostname: tuxedoaura15 Storage: /var/lib/systemd/coredump/core.neochat.1000.d248de07e68d4c529ac4d811ad16ce19.2645.1670276906000000.zst (present) Size on Disk: 6.3M Message: Process 2645 (neochat) of user 1000 dumped core. Stack trace of thread 2: #0 0x00007f4f7ce5949b n/a (/usr/lib/x86_64-linux-gnu/libc-2.33.so + 0x3949b) #1 0x00007f4f7ce42857 n/a (/usr/lib/x86_64-linux-gnu/libc-2.33.so + 0x22857) #2 0x00007f4f7d49dbb7 n/a (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.7 + 0x9dbb7) #3 0x0000003000000028 n/a (n/a + 0x0) ELF object binary architecture: AMD x86-64 I don't get any freedesktop related error and when I restart it, I don't get the infinite loop anymore, but the login screen as expected with no connected account.
Just a guess, this might be related to my password containing special characters.
*** Bug 467434 has been marked as a duplicate of this bug. ***
After some time, I tried to use Neochat again and now it works. I can't exactly say why because I reinstalled my distro and did all kinds of things in the meantime. But my guess is that it is because I enabled the "KDE-Passwortspeicher-System" (password storage system or something like that). I am not sure it this really was disabled before I reinstalled my distro, but I would guess so because a) it was disabled after the reinstall and b) I use another password manager, so saw no reason to enable it. So if this was only my bug, I could probably close it. But since someone else also encountered it, I will leave it open for now and suggest testing Neochat with password storage system disabled.
I don't think my report was a full duplicate, actually. What would seem to make sense to me is keeping this one for accounts being deleted after any failure to connect to them, because that's what both of our cases seem to have in common. And then reopen mine for handling unreachable servers better, so that NeoChat doesn't hang in the loading screen or crash later just because one of multiple accounts can't connect.
(In reply to Kevin Wolf from comment #10) > I don't think my report was a full duplicate, actually. > > What would seem to make sense to me is keeping this one for accounts being > deleted after any failure to connect to them, because that's what both of > our cases seem to have in common. > > And then reopen mine for handling unreachable servers better, so that > NeoChat doesn't hang in the loading screen or crash later just because one > of multiple accounts can't connect. You may be right - The crash is something different, loosing the account is probably something else. FWIW i know exactly why you lost the account, it's just in a part of the codebase i don't want to touch at the moment because the functionality is currently being implemented in libquotient, making the situation quite complex already
(I meant to say "loosing the account is the same bug", of course)