Arch Linux User Repository

IMPORTANT: Please uninstall the signal-desktop-blur-me-not package. It’s not compatible with signal-desktop >= 8.0.0, nor is it needed anymore.

Instead, create a ~/.config/signal-desktop-flags.conf file (if you even need one).

This package may not be needed anymore for element-desktop and 1password. Apps that use Electron v38+ should use Wayland automatically without additional configuration. The current version of element-desktop in extra uses depends on electron39. I don't know how to check which Electron version 1password ships with but I just verified that it's running in Wayland automatically without 1password-blur-me-not.

I don't use electron-fiddle but it looks like the most recent version (v0.38) uses Electron v39 and so this package shouldn't be needed for that either.

IMPORTANT: Please uninstall the signal-desktop-blur-me-not package. It’s not compatible with signal-desktop >= 8.0.0, nor is it needed anymore.

Instead, create a ~/.config/signal-desktop-flags.conf file (if you even need one).

@Auerhuhn Thanks for adding that so quickly!

I eventually realized the autostart was added by me and not 1password... my mistake! 😅

@rightaditya Thanks for the report. I pushed a new version that patches 1Password’s desktop file, too. Should work now.

Update: Files in ~/.config/autostart are user-managed and thus generally off limits for Pacman and alpm hooks. I suggest that you modify and manage those on your own.

Works great for me with Signal and Element, but for 1password, the 1password.desktop file in /usr/share/applications (and also the one set up to autostart in ~/.config/autostart) points to /opt/1Password/1password instead of /usr/bin/1password as set up by this package. Would it be possible to also patch the .desktop files to alter the path, or else replace /opt/1Password/1password? I think I can get around this by, e.g., adding extra libalpm hooks, so it's not too big a deal; but it'd be nice to have the 1password-blur-me-not package handle the situation properly :)

@OctopusET Sure! You can manually edit the /etc/*-flags.conf file and add anything you like. Your changes will be preserved across updates.

If you prefer not to modify /etc/*-flags.conf, you can alternatively place a copy of the file (named identically) into your ${XDG_CONFIG_HOME}/ or ~/.config/, and then edit it there. If that file exists, then the launcher will ignore the file in /etc and pick up your copy from ~/.config/ instead.

Can we also add

--enable-wayland-ime
--wayland-text-input-version=3

for IME?

PSA: Please uninstall the spotify-blur-me-not package.

The AUR package spotify now supports a native flags file, so spotify-blur-me-not is no longer necessary.

All users should uninstall spotify-blur-me-not and create a spotify-flags.conf file in the ~/.config directory with the following contents:

--enable-features=WaylandWindowDecorations
# Spotify still requires the `--ozone-platform` legacy switch
--ozone-platform=wayland

Hi @andrej, thanks for the report.

I’d like to know whether that issue is specific to electron-fiddle.

1. Would you mind trying one of the other *-blur-me-not packages and then reporting back whether HiDPI works for you there?

2. Additionally, can you post the output of pgrep -afl electron-fiddle while the app is running? (Don’t forget to anonymize the --enable-crash-reporter and --field-trial-handle IDs contained in the command line before you post the output.)

For me electron-fiddle-blur-me-not has no effect whatsoever, neither a crash nor a solution to the blurred disaster on Wayland. Everything stays the same.