Arch Linux User Repository

Hello,

I would like to request gnome-keyring as a dependency for this package as I installed on KDE, it doesn't work out of the box.

@alessandroberna Yeah I'm sticking with X11 for the time being. If you are on Gnome 47 fractional scaling should work fine with X11 windows. You need to turn on xwayland native scaling.

I have two monitors with different DPIs and different scaling factors, and it worked great.

@jianglai Ok well, it seems that I was wrong: the fix on v4.2.8 is allegedly unrelated to the issue you linked, even if it fixed the segfaults for me, when forging the incorrect config. The comments say that it had already been fixed with v4.2.7(?). That doesn’t seem to be the case since it’s still crashing for you.

One final thing you could try is setting those window size values to something small, like 500. it seems that once those values are set, they don't get updated anymore.

Overall, the recent builds seem quite unstable and have lots of issues. The new debian builds don't start on Debian since they get built with a too recent GLIBC version. the new rpm and appimage builds have another (different?) segfault issue and the flatpak appears to have other issues too.

There's not much I can do here. I only repackage the Debian build, I'm not a flutter dev and I'm not involved with the project.

All things considered, it might be best to just use the X11 workaround and avoid looking too much into the issue. That wouldn't work too well for me, XWayland makes all text blurry on my setup (likely due to fractional scaling being used with mixed-dpi displays), but it should work for most users. my setup is quite uncommon.

@alessandroberna I tried to delete the json file and indeed I was able to launch the app in wayland. Of course I had to log in again. However, the next time I started the app it crashed again for the same reason.

So it seems like it was still saving the wrong value after a successful log in.

@jianglai I actually used fractional scaling in my tests, altough only on KDE.

version 4.2.8 fixed a segfault issue that may be related.

It seems that, at times, incorrect values for flutter.windowWidth or flutter.windowHeight are saved in .local/share/io.ente.auth/shared_preferences.json

Even though i've never managed to get any segfault while regularly using the app, i tried manually entering bogus values into that config file. I noticed that enteauth does crash consistently this way, but only when started with the wayland backend. Using the X11 backend effectively acts as a workaround, for whatever reason.

If your segfaults were caused by ente saving an incorrect config (which seems likely at this point), you may now safely restore the .desktop entry to its original configuration.

@alessandroberna I had thought that this is happening to everyone on Wayland. I'm on Gnome with amdgpu FWIW. Maybe because I'm using fractional scaling? By any chance your test cases did not include fractional scaling?

I indeed wrote a pacman hook myself once I found out about the fix, very similar to what you have below. I encourage other people who are facing the same issue to try it.

One can also simply run

GDK_BACKEND=X11 enteauth

in the command line to verify that switching to X11 as the graphical backend will fix the issue.

@jianglai thank you very much for the additional insight

I attempted to reproduce the issue, as this package has always worked fine for me under Wayland. I tested the app with different Wayland compositors and GPU vendors, using all the systems I had available, thinking the issue might arise only with specific setups.

I tested it on the following:

• KWin 6.2.5 (KDE 6.2.5), amdgpu, mesa 24.3.3-arch1.2
• Mutter 47.4 (GNOME 47), amdgpu, mesa 24.3.3-arch1.2
• aquamarine 0.7.1 (Hyprland 0.46.2), amdgpu, mesa 24.3.3-arch1.2
• KWin 6.2.5, Nvidia 565.77-11
• Mutter 47.4, Nvidia 565.77-11
• Kwin 6.2.4, i915, mesa 24.3.1-arch1.3

I was unable to reproduce the issue in any environment, whether running the app with Wayland or forcing XWayland using the GDK_BACKEND=x11 flag.

To ensure Wayland was being used, I verified this with KWin’s debug console, launched via qdbus org.kde.KWin /KWin org.kde.KWin.showDebugConsole when using KWin, and with the xeyes trick on the other platforms. In any case, as noted in the ArchWiki GTK apps will always use wayland by default in wayland sessions.

Since the issue seems to be inconsistent, i don't think that forcing the X11 backend for every user of the package is a good idea, unless more people report the same issue.

However, I have written this pacman hook for you and anyone else facing the same issue:

[Trigger]
Type = Package
Operation = Install
Operation = Upgrade
Target = ente-auth-bin

[Action]
Description = Updating the ente auth desktop entry to use X11 backend
When = PostTransaction
Exec = /usr/bin/sed -i 's|^Exec=|Exec=env GDK_BACKEND=X11 |' /usr/share/applications/enteauth.desktop

Place it in /etc/pacman.d/hooks/ente-auth-x11.hook.

This will ensure the X11 backend is automatically used when launching the app via its desktop entry. If the app is already installed, simply reinstall it to apply the changes.

@alessandroberna setting GDK_BACKEND=x11 works.

https://github.com/ente-io/ente/issues/4100#issuecomment-2588021813

@alessandroberna There was a bug upstream about this (still unfixed as of 2025-01-12). It seems like wayland can be turn off for flatpak (via flatseal, not configurable by the app itself). It is unclear if the same option exists for deb.

@jianglai I apologize for the late reply. I believe that your issue is not related to packaging. If the issue is still there on the latest version, could you please report it upstream on Github?