Login fails with "Unexpected error" #7764
Comments
|
This also happens to me after updating wire-desktop today. Wire version: 3.35.3348 Using the correct password gives the message "Unexpected error", and prevents log in. Starting |
|
Same here after update: wire --enable-logging Edit: Also occurs with Wire snap app version 3.35.3348 (= latest/edge snap version) |
|
This happened after the incident couple of days ago when SSL certificate for app.wire.com expired. It was down for several hours. After the last update+restart login stopped working. The old version doesn't work either anymore.
|
|
thanks for reporting this! wire is working on a fix, but there is no release time yet. the reason for the problem is an error in handling a missing library on the underlying OS. as a workaround, you can manually set the safeStorage backend for electron with eg.: or these instructions may require some tweaking depending on your setup. for example, on debian without gnome, you may need to do this: apologies for the hickup, and thanks again for the reports! |
|
@fisx thanks, while we're here, do you have any idea why on https://wire.com/en/app-download Linux is marked as unsupported, and the latest version is from December 2022? |
Thank you for the update. |
If you use the debian package (debian- or ubuntu-based distros), you'll get the most recent version (today: On other distros, you can get today's release here. all releases are here. The reason linux is marked as unsupported is that we do care about Linux, but we don't have the capacity to commit to always preventing issues like this from happening. Many Wire developers are using wire on Linux, and we're hopeful to add official Linux support at some point in the future, but for now it's just available without any guarantees. Sorry, I myself wouldn't be very impressed by how this looks. We're doing what we can with the resources we have. |
have you tried as I said, it may need some tinkering. |
Doesn't work either. I guess I have to wait for a fix. |
|
(I updated the instructions in the wiki, hopefully this helps!) |
Does this mean that this bug could alternatively be worked around by installing the missing library? And, if so, which? |
|
We will be working on a fix for this internally but if you are still having issues i recommend using the webapp for the time being. Apologies for the issue. |
|
Thanks for the logs @sebastian-zero ! It seems your issue is related with AppArmor policies, could you see if editing the AppArmor profile of the Snap helps? See here. Unfortunately, we do not package the Snap on SnapCraft ourselves to edit those policies, the issue is likely to persist (without manually editing the profile file) until the maintainer is aware of he issue, I'll try to get in touch with them. |
Result of the investigation so far:Cause
Identified Issues (on Linux)
How to fix today
Plans to solve the issue
How can you help?
I will follow this thread best I can during the weekend, apologies to those affected, thank you for reporting the issue and for your patience |
|
Small update:
In a nutshell, I hope the Snap issue will be addressed soon, it doesn't seem we can provide a better experience than linking to a support page for people who don't run a desktop environment, I hope it's satisfying, I imagine users running a tiling window manager are not afraid of the command line 😄 . I'll let you know when the error handling is live, thanks for your patience |
|
Trying the workaround on Debian testing I get this when attempting to log in: Edit: |
|
@V-Gira thank you for your help! A bit off-topic suggestion to the Wire engineering team: Maybe it would be beneficial if Wire would focus on one Linux cross-distro distribution format like flatpak (or snap, but flatpak seems more popular) and maybe retire the 3rd party ppa in the long run. This could mean that Wire takes ownership of the flatpak (or snap). Another benefit for the Wire team: less testing efforts on new releases. |
What you are describing is exactly how I would personally envision limited Linux support, starting with the Flatpak and narowing it down to wayland+pipewire or xorg+pulseaudio. We"re not ready for that discussion yet (assigning resources to Linux support), but I certainly am 😆 I did manage to build a working Snap btw, the (much more knowledgeable than me) maintainer should be able to fix the issue I imagine. |
|
Hi, i have also experienced this issue and after enabling KDE Wallet on my system i managed to login initially. But, when i get prompted to input the account passcode i get redirected back to the login screen again. |
@bik0t I did test kwallet on an Arch VM, maybe you could try to see if you have better luck with a different version of kwallet? |
|
Hi @V-Gira , thank you for the reply. I am currently using If I do setup a passcode, after initially logging in, setting up the passcode and quitting the app, when I open it back I get stuck in the loop as described previously. EDIT: is there any way I can disable the passcode manually in |
|
@bik0t There's no good passcode workaround but I sent you a private message on Github (no it's not a thing, but it kinda is, you'll see) |
V-Gira
changed the title
|
Has anyone tried Kalium from the commandline? I would like to know if Kalium is also affected by this problem. It would be very interesting to ditch the very fat Electron bloat in favor of a simple TUI. I tried Kalium a year (or 3) ago but could not get it going likely due to lack of documentation. I reported bugs but the whole bug tracker was later deleted so there are no longer records of what I tried and what failed. The Android app app no longer gets notifications. My version was spontaneously hit with unannounced forced obsolescence a couple years ago with no upgrade possibility, so up until this bug notifications were the only thing that worked. But now the notifications are apparently broken too. I’m a bit shocked that there are on the order of ~5 people affected. After a week of being unable to communicate with people I would think a crowd of thousands would be in here looking to crucify someone. I must have overestimated the popularity of Linux. |
Please do not release your app on flatpak. We prefer |
You're counting the number of people who have issues and have GitHub and bothered to search for this issue on GitHub. Generally I estimate that the number of folks who go through the extra effort to signup for GitHub and report the issue is ~1% of those affected. So, yes, this probably is impacting hundreds or thousands of people. |
|
I'm one of the other 99% watching and waiting. I have the web version running in a browser window as a stopgap. However it only displays a tiny few past messages. I dread losing my chat history on this machine. M. |
End of week update:
@bruceleerabbit , @maltfield , @mdevour you should be able to fix the issue by following the steps here , if your issue is not covered, please tell us more. @bruceleerabbit kalium (or any other client) is not affected, the issue concerns only the Electron wrapper (the browser version is not affected as far as we know, let us know otherwise) |
|
Hi, created an account to comment here. On an up to date debian bookworm and wire-desktop, I'm still having this issue after installing I get the following error: I'm guessing because of this I lost all my chat history and will never receive the messages for the last week... |
I have exactly the same issue, I am using the appimage version of the app and since I had a passcode I am unable to get out of the login loop described. |
|
For completeness: There is an upstream bug report for this as well, see electron/electron#39789 However, there seems to be more to it since using the suggested flag I still get the same error using the latest linux version even though other applications work just fine. |
|
@naeya42 @GRBurst what package are you using, are you using the snap by any chance? If you're still facing ssues you can use the app in browser in the meantime. You can backup/restore conversation history between browser and Electron app without issue. |
Great, glad to hear it! It would be really nice to have Kalium working. A simple commandline, no bloat and no big downloads upon every login. It should really be the end game rather than Electron. It would enable people to build more Wire apps. But there are barriers due to bugs in the low-level support packages that Kalium depends on:
I don’t suppose anyone got Kalium working? |
Yep. I've installed wire on people's linux machines. These people happily use wire, but they don't know what github is. |
To confirm, with an updated version of Arch Linux, at the time of this writing (with wire-desktop version |
|
I get the following error output on Fedora 40, running it using Flatpak [2:1103/083936.411224:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
LaunchProcess: failed to execvp:
xdg-settings
[2:1103/083936.766341:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:1103/083936.766404:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:1103/083936.787093:ERROR:object_proxy.cc(576)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6: org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown
[2:1103/083936.787119:ERROR:kwallet_dbus.cc(112)] Error contacting kwalletd6 (isEnabled)
[2:1103/083936.787305:ERROR:object_proxy.cc(576)] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown
[2:1103/083936.787311:ERROR:kwallet_dbus.cc(81)] Error contacting klauncher to start kwalletd6
[2:1103/083936.787421:ERROR:object_proxy.cc(576)] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd6: org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown
[2:1103/083936.787426:ERROR:kwallet_dbus.cc(503)] Error contacting kwalletd6 (close)
src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000
src/gbm_drv_common.c:131: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000I have actually enabled kwalletd6 as a service, but Wire is unable to find it. Likewise, I tried with the option |
|
@V-Gira I see that your PR that should fix the snap was approved in July last year, though the snap version from edge channel still shows "Wire can’t access your system's safe storage." for me on Kubuntu 24.04. I don't know how the release process for snaps works but do you know when a version containing your fix will become available? |
Wire version: 3.35.3348
Wire for web version: 2024.04.11.07.16.27
Operating system: Arch Linux
Which antivirus software do you have installed: none
What steps will reproduce the problem?
What is the expected result?
Login should work
What is the actual result?
Login failes with the error message:
Unexpected errorwhen started froma terminal, this additional error is printed:
Please provide any additional information below. Attach a screenshot if possible.
The error has been reproduced by both version 3.34.3307 from the official arch repository as well as with the current version 3.35.3348 rebuild today.
...
The text was updated successfully, but these errors were encountered: