Mastermindzh
Tidal-HiFi freezes in arch
System: Arch, TIDAL-HiFi version 5.20.0 Application installed from file: tidal-hifi-5.20.0.pacman
Tidal-HiFi freezes my entire computer after listening to music for a long time, and I have to restart it. I have enough RAM, as I have 32GB. While playing music, the app uses a maximum of 6GB of RAM.
Any additional info? Ive had it play since 10:00 this morning so little over 12 hours now and all is fine for me.
Any additional info? Ive had it play since 10:00 this morning so little over 12 hours now and all is fine for me.
And it might have broken the theme for KDE Plasma 6?
So what do you consider long? Was it longer than 12 hours?
Did this happen once or consistently? Is this similar?: https://github.com/Mastermindzh/tidal-hifi/issues/643
So what do you consider long? Was it longer than 12 hours?
Did this happen once or consistently? Is this similar?: #643
I reinstalled the system because I think I messed something up and I'll test it.
So what do you consider long? Was it longer than 12 hours?
Did this happen once or consistently? Is this similar?: #643
I find myself under the exact same circumstances than issue #643, both in the issue and context. But, it also happens randomly after a while of reproducing music (specifically when a new song starts, I don't consider the issue is activating when skipping, but it may be the fastest route to it), It has happened to me from about 3 hours reproducing music, and it's exactly the same problem, plasmashell crashes and I have to reboot everything. This last part may be just me going crazy, but I feel like it has become increasingly more usual, almost feels unusable at this point, hope my additional context helps
And are you all using KDE? I am using i3wm and can't reproduce it whatsoever.
And are you all using KDE? I am using i3wm and can't reproduce it whatsoever.
Indeed. I'm using Fedora KDE 42
If the Error occurs Plasmashell outputs the following: IFFChunk::innerFromDevice: unkwnown chunk "\x89PNG" IFFChunk::innerFromDevice: unkwnown chunk "\x89PNG" IFFChunk::innerFromDevice: unkwnown chunk "\x89PNG" However, this also occurs when I restart Plasmashell while Tidal is open in the background.
I don't have any more useful information but I can confirm I'm having the same issue in KDE. On Nobara 42 (Fedora).
This seems like it's probably the same as #532?
It seems like it also is an issue when using swaync as the notification daemon, though, not just KDE.
happens to me too but it worked for several weeks. I do have libnotify installed though, which throws warnings
libnotify-WARNING **: 14:51:50.592: Failed to connect to proxy. Running export DBUS_SESSION_BUS_ADDRESS=unix:path=/dev/null, then running tidal-hifi worked though, but of course there's no more playback notifications
Hello I also have this issue when using KDE. The entire DE freezes, I can ALT+TAB to switch windows but the Panel is frozen. When I terminate the application the icon on the panel stays there, no matter how many times I choose Quit on the menu that pops up when I click on it. Also after clicking it, it again freezes or something because the menu shows up after like 10+ seconds.
This sounds like this plasma bug, should be fixed in the next update. Also i found that it is the same issue as #643, the frequency at which you skip tracks doesn't matter for this bug.
Please forgive my persistence. But if it's a Plasma issue, that means I have to wait for Plasma to release a new version that fixes it, right? How long would that take? Because in the Plasma list you attached, the issue has been there since 2022, and there are people who have had this issue since Fedora KDE 39. We're already at 42 and still dealing with the same thing. Is there nothing I can do as a user? Or just wait? Or who is this up to?
Or at least someone who would be kind enough to give me a temporary alternative that would allow me to listen to my music at maximum quality in the meantime because the difference is frustrating.
Hello I have Arch and updated KDE to version 6.4.4 and so far everything works fine with Tidal Hi-Fi
@Pagsnan9,
Please make sure you're running on the latest versions of KDE etc. If it is a problem just with KDE (which many users have now confirmed) then it's unfortunately out of our hands.
We can't exactly force the KDE maintainers to merge the fixes faster.
Of course, if this is crucial to you, you can always boot into another DE and use all the apps without issues 😄
I'm experiencing the same issue, but I'm on Niri, not Plasma. I was able to get some logs when the issue happened. Here is the entire log of the session:
Wayland socket is available, running natively on Wayland.
To disable, remove the --socket=wayland permission.
[2:1114/131848.617883:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:1114/131848.903093:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:1114/131848.903130:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
components ready: {
"oimompecagnajdejgnnjijobebaeigek": {
"status": "new",
"title": "Widevine Content Decryption Module",
"version": "4.10.2891.0"
}
}
LaunchProcess: failed to execvp:
xdg-settings
[2:1114/131849.851014:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:1114/131849.851047:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:1114/131849.851097:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:1114/131849.851121:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:1114/131849.851137:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Started preventing app suspension with id: 0
Released inhibitor with id: 0
Started preventing app suspension with id: 1
[2:1114/145132.905346:ERROR:electron/shell/browser/notifications/linux/libnotify_notification.cc:50] notify_notification_show: domain=194 code=24 message="Timeout was reached"
[2:1114/145133.048992:ERROR:ui/events/platform/wayland/wayland_event_watcher.cc:78] Fatal Wayland communication error: Connection reset by peer.
[2:1114/145133.049105:FATAL:electron/shell/browser/electron_browser_main_parts.cc:501] Failed to shutdown.
The issue so far has only happened when a notification is shown due to a new song being played and the logs seem to also point in that direction.
Yes, you will need a dunst compatible notification system or disable them(notifications) alltogether.
Yes, you will need a dunst compatible notification system or disable them(notifications) alltogether.
I'm using libnotify (together with swaync), which should be supported according to the README. Notifications work in general, they just sometimes cause the application to freeze.
To me it looks like the same Bug as in Plasma, maybe look into the source of your notification service and see if they save the image data and post it to dbus every time the notification is triggered.
Maybe it would be better for Tidal-Hifi to not stream the image data directly over dbus and instead cache it somewhere. It seems like this feature causes some issues with some notification servers, because the image data is not handled properly. I have found that plasma-workspace for example, kept the image data twice internally and always included it in requests to dbus, thus eventually crashing it, because the notification request is a few megabytes in size.
To test this i would suggest you try out the python script from this post and see if that triggers the issue. If it does, post a bug report to swaync or libnotify.
I'm experiencing the same issue, but I'm on Niri, not Plasma. I was able to get some logs when the issue happened. Here is the entire log of the session:
Wayland socket is available, running natively on Wayland. To disable, remove the --socket=wayland permission. [2:1114/131848.617883:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory [2:1114/131848.903093:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory [2:1114/131848.903130:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory components ready: { "oimompecagnajdejgnnjijobebaeigek": { "status": "new", "title": "Widevine Content Decryption Module", "version": "4.10.2891.0" } } LaunchProcess: failed to execvp: xdg-settings [2:1114/131849.851014:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory [2:1114/131849.851047:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory [2:1114/131849.851097:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory [2:1114/131849.851121:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory [2:1114/131849.851137:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory Started preventing app suspension with id: 0 Released inhibitor with id: 0 Started preventing app suspension with id: 1 [2:1114/145132.905346:ERROR:electron/shell/browser/notifications/linux/libnotify_notification.cc:50] notify_notification_show: domain=194 code=24 message="Timeout was reached" [2:1114/145133.048992:ERROR:ui/events/platform/wayland/wayland_event_watcher.cc:78] Fatal Wayland communication error: Connection reset by peer. [2:1114/145133.049105:FATAL:electron/shell/browser/electron_browser_main_parts.cc:501] Failed to shutdown.The issue so far has only happened when a notification is shown due to a new song being played and the logs seem to also point in that direction.