Package Details: element-desktop-blur-me-not 0.1.8-1

Git Clone URL: https://aur.archlinux.org/electron-blur-me-not.git (read-only, click to copy)
Package Base: electron-blur-me-not
Description: Auto-enable Wayland (ozone) for element-desktop
Upstream URL: https://aur.archlinux.org/pkgbase/electron-blur-me-not
Licenses: Apache-2.0
Submitter: Auerhuhn
Maintainer: Auerhuhn
Last Packager: Auerhuhn
Votes: 2
Popularity: 0.004836
First Submitted: 2023-03-04 00:17 (UTC)
Last Updated: 2025-10-02 12:41 (UTC)

Latest Comments

1 2 Next › Last »

rightaditya commented on 2025-10-03 20:41 (UTC)

@Auerhuhn Thanks for adding that so quickly!

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

Auerhuhn commented on 2025-10-02 12:42 (UTC) (edited on 2025-10-02 12:51 (UTC) by Auerhuhn)

@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.

rightaditya commented on 2025-10-02 08:02 (UTC)

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 :)

Auerhuhn commented on 2025-04-19 12:40 (UTC)

@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.

OctopusET commented on 2025-04-19 12:32 (UTC)

Can we also add

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

for IME?

Auerhuhn commented on 2024-03-03 13:37 (UTC) (edited on 2024-03-03 13:37 (UTC) by Auerhuhn)

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

Auerhuhn commented on 2024-01-21 12:22 (UTC) (edited on 2024-01-21 12:27 (UTC) by Auerhuhn)

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.)

andrej commented on 2024-01-20 21:54 (UTC)

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.

Auerhuhn commented on 2023-11-11 11:26 (UTC)

Note: as of electron-fiddle v0.34.5, the app is now crashing for me when I have electron-fiddle-blur-me-not installed, or when I use some other way to configure the app to use Wayland.

If the app crashes for you, try one of the following:

  • uninstall electron-fiddle-blur-me-not;

  • alternatively, create a symlink under /usr/bin/electron that points to Electron 26 (caution: unsupported! May break other packages that depend on that executable. You may want to look at the output of pacman -Qi electron | grep 'Required By' and then check for regressions in the apps listed there);

  • or, try the symlink trick but alternate between Electron 26 and 25 back and forth until you find it’s working with one of them (caution: unsupported!)

Additionally, consider leaving a comment at issue #39449 on Electron’s GitHub repository.

See also:

danherbert commented on 2023-08-04 21:48 (UTC)

For reproducing the icon problem, I was able to replicate the problem on a fresh VM install of Arch with Gnome's Wayland defaults. To replicate, I installed the VM using the following archinstall config with the defaults for disk layout:

archinstall --config https://dan.herbert.io/wayland-vm.json

The config above includes signal-desktop as one of the bundled packages. I manually installed signal-desktop-blur-me-not, then opened Signal. When searching for apps or checking the installed applications from the default Gnome launcher, the icon looks fine. But once the app is started, every place that shows the app icon (opened windows, running apps, etc) shows the Adwaita application-x-executable icon

I should probably also mention that I only notice this problem with Signal and not other apps that also have a blur-me-not package. I also have the 1Password blur-me-not package and the icon for that app is fine.

1 2 Next › Last »