Arch Linux User Repository

Amazing! I solved the problem myself by some google searching. I'll share it here...

As it turns out, Chromium has an undocumented command line option:

--disable-gpu

I just tried this with the Deezer app and it works: deezer --disable-gpu

(For app like this, which is just for playing music, I really don't care about it to run hardware accelerated, but just that it works. :P)

So now we know this works, the next step is to edit the .desktop shortcut, put this command line option into it, and storing the shortcut in ~/.local/share/applications/ (I just do that by rightclick and editing the icon in my Plasma desktop, so that this is done automatically).

Anyone else having graphical troubles with NVIDIA and running this app on a Wayland desktop? I am seeing black contents inside the app window.

For a very long time I been using Xfce running Xorg and the Deezer app always worked.

But I am now using KDE Plasma running on Wayland, and I see a pitch black pitch black screen with dedicated NVIDIA graphics enabled on my laptop.

Note that pressing spacebar inside the window pressing the play/pause/forward/backward buttons on my keyboard still work. And the mouse as well, as the cursor still gets a hand shape where hyperlinks should be visible.

When I use dynamic graphics, effectively using my AMD CPU graphics card by default, the app works normally. (This hybrid mode for my laptop reduces energy, but reduces graphics performance and quality, so being able to switch between both options is what I want, and using Deezer in both ways would be great)

It's probably and old Electron13 Chromium engine problem, but maybe someone knows a fix.

Yurii, I hadn't realized that electronXX-flags.conf was not supported as standard by electron. But it makes sense...

Anyway, now I tested passing in the flags manually (which I somehow failed to consider trying earlier), and it does something different. Unfortunately, it's to crash with a SIGILL just after trying to create the first/main window.

I'll look into it later, but if someone has already seen and fixed this, please let me know!

Jonas,

If you mean my package electron13-bin and setting flags in ~/.config/electron13-flags.conf and ~/.config/electron-flags.conf, then it would work now. I hope to implement this feature in my electronXX-bin packages, just like in official electron30's electron-launcher.sh. I didn't know about this feature until seeing your comment.

Have you managed to run it natively on Wayland? I tried to set the recommended (in the Wayland page of the wiki) electron13 flags, but it's still running on XWayland. And stracing it shows that no electron*-flags.conf file is even opened.

@eltongermano, Arch User Repository (Français) — ArchWiki:

Assurez-vous que le méta-paquet base-devel est installé dans son intégralité (pacman -S --need base-devel).

Pra quem estiver com erro na linha 54 na hora de montar o pacote, verifique se possui o pacote 'patch' (https://archlinux.org/packages/core/x86_64/patch/) instalado. Resolvendo essa dependência o app foi instalado com sucesso. Obrigado Sibren Vasse, uso seu app a mais de 1 ano e sempre roda fluído <3

@jonasmalacofilho: thank you for notifying me about the missing part of the patch. The patch is from https://github.com/aunetx/deezer-linux/pull/11. But as you've already mentioned, it doesn't seem to be working.

I have removed the systray fix. I have been unable to differentiate in function between the two events (typing in search bar vs clicking in systray). On our platform, triggeredByAccelerator is always true and the action is never handled. If you have an idea how to fix both use-cases, please let me know.

I also noticed that in e0195f61d2dd ("Fix build with prettier 3.2.1") one of patched usages of fix-isDev-usage.patch was lost: the one in getSentryTags() (patch).

However, that apparently isn't enough to save the system log from being spammed.

Typing in a space in the search box pauses/unpauses music. Tracked down the issue to systray-buttons-fix.patch, but I'm not familiar with electron apps to immediately see a solution that fixes the systray menu actions without causing this search box issue. Do you have any ideas?