Tidal-hifi client does not appear on wayland

[aljustiet]

Tidal version: Flatpak OS: Arch/Hyprland

Log:

❯ flatpak --verbose run com.mastermindzh.tidal-hifi
F: No installations directory in /etc/flatpak/installations.d. Skipping
F: Opening system flatpak installation at path /var/lib/flatpak
F: Opening user flatpak installation at path /home/aljustiet/.local/share/flatpak
F: Opening user flatpak installation at path /home/aljustiet/.local/share/flatpak
F: Opening system flatpak installation at path /var/lib/flatpak
F: Skipping parental controls check for app/com.mastermindzh.tidal-hifi/x86_64/stable since parental controls are disabled globally
F: Opening user flatpak installation at path /home/aljustiet/.local/share/flatpak
F: Opening system flatpak installation at path /var/lib/flatpak
F: /var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/24.08/6ad4305d3f60009c2a75a59f99c652ab271ea89347e10201e74730cb1a6c0ecd/files/lib32 does not exist
F: Cleaning up unused container id 3045588628
F: Cleaning up per-app-ID state for com.mastermindzh.tidal-hifi
F: Cleaning up unused container id 2051785141
F: Cleaning up per-app-ID state for com.mastermindzh.tidal-hifi
F: Allocated instance id 2889695990
F: Add defaults in dir /com/mastermindzh/tidal-hifi/
F: Add locks in dir /com/mastermindzh/tidal-hifi/
F: Allowing dri access
F: Allowing host-fs access
F: Allowing homedir access
F: Allowing wayland access
F: Allowing x11 access
F: Allowing pulseaudio access
F: Pulseaudio user configuration file '/home/aljustiet/.config/pulse/client.conf': Error opening file /home/aljustiet/.config/pulse/client.conf: No such file or directory
F: Running 'bwrap --args 43 -- xdg-dbus-proxy --args=42'
F: Running 'bwrap --args 41 -- com.mastermindzh.tidal-hifi'
Wayland socket is available, running natively on Wayland.
To disable, remove the --socket=wayland permission.
[2:0225/064816.014746: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
^C

[Mastermindzh]

You don't seem to have dbus, that is required :)

[aljustiet]

You don't seem to have dbus, that is required :)

I have it installed

[aljustiet]

I gave

You don't seem to have dbus, that is required :)

Maybe, it can't access dbus, how can I give access to dbus for tidal-hifi, then?

[aljustiet]

I added this lines to the permissions of the flatpak:

[System Bus Policy]
org.freedesktop.DBus=talk

and now have this output:

❯ flatpak --verbose run com.mastermindzh.tidal-hifi
F: No installations directory in /etc/flatpak/installations.d. Skipping
F: Opening system flatpak installation at path /var/lib/flatpak
F: Opening user flatpak installation at path /home/aljustiet/.local/share/flatpak
F: Opening user flatpak installation at path /home/aljustiet/.local/share/flatpak
F: Opening system flatpak installation at path /var/lib/flatpak
F: Skipping parental controls check for app/com.mastermindzh.tidal-hifi/x86_64/stable since parental controls are disabled globally
F: Opening user flatpak installation at path /home/aljustiet/.local/share/flatpak
F: Opening system flatpak installation at path /var/lib/flatpak
F: /var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/24.08/7843a03291593f58bfd4583eaa48b65198be8a84ecd1a5885d0d65920d3a22a6/files/lib32 does not exist
F: Cleaning up unused container id 2344768719
F: Cleaning up per-app-ID state for com.mastermindzh.tidal-hifi
F: Cleaning up unused container id 3966753113
F: Cleaning up per-app-ID state for com.mastermindzh.tidal-hifi
F: Allocated instance id 1193441040
F: Add defaults in dir /com/mastermindzh/tidal-hifi/
F: Add locks in dir /com/mastermindzh/tidal-hifi/
F: Allowing dri access
F: Allowing host-fs access
F: Allowing homedir access
F: Allowing wayland access
F: Allowing x11 access
F: Allowing pulseaudio access
F: Pulseaudio user configuration file '/home/aljustiet/.config/pulse/client.conf': Error opening file /home/aljustiet/.config/pulse/client.conf: No such file or directory
F: Running 'bwrap --args 42 -- xdg-dbus-proxy --args=43'
F: Running 'bwrap --args 41 -- com.mastermindzh.tidal-hifi'
Wayland socket is available, running natively on Wayland.
To disable, remove the --socket=wayland permission.
^C

Wayland client doesn't appear.

[aljustiet]

You don't seem to have dbus, that is required :)

dbus is running How can I run in debug mode? In xorg window manager, it launches fine so.

[aljustiet]

Will this issue be somehow fixed? What other info can I give to solve this issue?

[Mastermindzh]

Unless we can reproduce it there is no way we can start looking into the issue. In a recent topic we've had several people (including myself) try the flatpak (and aur version) on hyprland and it worked without issue.

How can I run in debug mode?

If you actually want to debug you'd have to download & run the sourcecode. Then you can attach a debugger to the electron process. Alternatively launching it in a terminal like you've been doing gives you most error/warning messages.

[aljustiet]

Unless we can reproduce it there is no way we can start looking into the issue. In a recent topic we've had several people (including myself) try the flatpak (and aur version) on hyprland and it worked without issue.

How can I run in debug mode?

If you actually want to debug you'd have to download & run the sourcecode. Then you can attach a debugger to the electron process. Alternatively launching it in a terminal like you've been doing gives you most error/warning messages.

Which flags should I use to run it with debugging enabled?

[Mastermindzh]

You can use npm run watch to start the compilation etc... and then use npm start to start the actual thing. You'll have to repeat npm start everytime you've made changes as the app doesn't auto reload. (but compilation does)

[aljustiet]

You can use npm run watch to start the compilation etc... and then use npm start to start the actual thing. You'll have to repeat npm start everytime you've made changes as the app doesn't auto reload. (but compilation does)

What should I do with this, I searched for the tsc-watch in the repos, but it didn't found the required binary?:

❯ npm run watch

> [email protected] watch
> tsc-watch --onSuccess "npm run compile-all"

sh: line 1: tsc-watch: command not found
❯ echo $?
127
``` ? 

[Mastermindzh]

Oh, you have to install the dependencies first with npm install 😄

Sorry, I forgot about that as it's "normal" in node projects.

[aljustiet]

9:36:21 AM - Starting compilation in watch mode...


9:36:26 AM - Found 0 errors. Watching for file changes.

> [email protected] compile-all
> npm run sass-and-copy && ts-node scripts/generate-swagger.ts


> [email protected] sass-and-copy
> npm run sass && npm run copy-files && npm run copy-themes-dev


> [email protected] sass
> sass ./src/pages/settings/settings.scss ./src/pages/settings/settings.css && sass --no-source-map src/themes:themes


> [email protected] copy-files
> copyfiles -u 1 --exclude './src/**/*.ts' --exclude './src/**/*.scss' "./src/**/*" ts-dist


> [email protected] copy-themes-dev
> copyfiles -u 1 "./themes/*" node_modules/electron/dist/resources

Written swagger.json
^C
❯ npm start

> [email protected] start
> electron --inspect=0.0.0.0:5858 .

Debugger listening on ws://0.0.0.0:5858/f1570a71-f048-4350-a653-3ddeca26884c
For help, see: https://nodejs.org/en/docs/inspector
^C/home/aljustiet/Documents/git/tidal-hifi/node_modules/electron/dist/electron exited with signal SIGINT

Where am I supposed to look for the debug messages?

[aljustiet]

I launched Hyprland with a clean config from TTY. An XWayland window appears, but native Wayland window does not.

[aljustiet]

XWayland couldn't launch because of ELECTRON_OZONE_PLATFORM_HINT=auto. I think it was trying to use Wayland mode with 'auto', but no Wayland window appeared.

[b1ggi]

i have the same issue

[DrEdwards]

Had the same issue, removing socket=wayland permission allowed the app to run through XWayland and now it works properly

[aljustiet]

Issue is gone somehow on my side.

[MarkoCindric-xyz]

Having the same issue here on Fedora 42 / GNOME 48.1. Only works with socket=wayland removed in Flatseal, forcing an XWayland window. I had it working on Fedora 41, so maybe that contributed to the breakage somehow? (The client's Settings pane has never rendered for me unless I applied the XWayland workaround, even on 41, but I digress.)

[aljustiet]

Having the same issue here on Fedora 42 / GNOME 48.1. Only works with socket=wayland removed in Flatseal, forcing an XWayland window. I had it working on Fedora 41, so maybe that contributed to the breakage somehow? (The client's Settings pane has never rendered for me unless I applied the XWayland workaround, even on 41, but I digress.)

For me, it now works under wayland; probably, it started working after some update. I use arch btw.

[Mastermindzh]

Closing as completed since the issue seems fixed :)