Regarding my issue I could try to install the player using the zorin os app store (blue icon software) since that way the theme is respected.
However I would need help to rescale strawberry's UI since the app doesn't obey to the "Bigger Text" option I have enabled in accessibility settings and there's no way for me to rescale the UI in the app itself since it follows the default in the OS.
I tried to disable the "bigger text" option and configure the system font manually but the font in the taskbar becomes too small compared to the rest of the OS.
The Gnome Software store offers several package formats. Stating that you use the Store does not narrow down which format is used.
The formats can include:
APT (labeled as "Zorin OS"): This is the standard Advanced Package Tool, used by Debian and Debian based systems for disseminating packages.
APT supplies tested, vetted and stable packages.
Flatpak: This is a newer alternative format by the Gnome Development group that supplies a self contained version of an application. It may supply a higher version, including Beta's, unstable and experimental packages. Due to its containerization, it is isolated and cannot communicate with the System, including themes, supplying its own appearance theming. Permissions can be allowed using an additional piece of software: Flatseal.
Snap: This is a newer alternative format supplied by the Canonical development Group. Snap packages are self-contained, like flatpaks. However, there is no tool to allow permissions. Snaps are rather locked down and due to their many cons, are usually deceptively snuck onto a system with misleading wording or underhanded tactics by Canonical ( I call it like it is and I make zero excuses for this behavior).
I use Exhaile Music Player due to how stable it is, how it meets every need and never fails. I will ask of the elephant in the room: Are you open to using a less troublesome music player? Or does strawberry meet a very specific need?
This is the version available in the software center app.
I think an alternative would be to keep using the mismatched theme on the strawberry app, I use it because of the high bitrate/bit depth audio capabilities and ALSA integration. The theme limitation is not but the app is still usable.
I uninstall SnapD and Flatpak first thing. This means I am often caught by surprise by the vast number of users that have a different experience than I do by being forced into package formats.
And seeing things like this on Zorin OS - where the defaults apply Force upon users in the same style as Microsoft - makes me question my presence here.
With a combination of Wayland and a Flatpak with such Limited system access... I am unsure of how to make this app match your system theme.
It conforms to Microsoft and many different companies shoving us into Subscriptions: They firmly believe we should not have permission to unify Our Own Desktops and we are not allowed to own the products we buy.
I'm using the default 1080p 14 inch T480s monitor and scaling is set to 100%. I am using the "Bigger Text" setting in accessibility because only this way the display looks normal and readable to me.
So testing the Strawberry Flatpak, if you switch to Xorg desktop, and you enable "Large Text" in accessability, it will follow that setting in Strawberry. It will not work in Wayland.
To switch over, you could logout, then when you go to type in your password, select the cog in the bottom right, then click "Zorin on X".
I just tested this on a clean laptop, so it seems like it should work.
There's a PPA that you can install this from, by the same author of this project so it's seems safe to use. To use, add it to your system by running this in a terminal window:
This is interesting to me, as other packages I have run, do work. I might test them again - I wonder if there is something the developer can (Or in those cases, does) that allows theming to work properly.
This is the output of the commands present in the section "Strawberry does not integrate natively with Wayland." so I believe everything should be right.
Is there any other fix?
I thought of one possibility I don't know if is plausible. Is it possible that only the strawberry app opens in xorg instead of wayland? If it opened in Wayland the font would be very small, wouldn't it?
No, you can only use one or the other. Wayland already implements a compatibility layer through XWayland, as way to preserve functionality as best as possible for programs that haven't been explicitly designed to work with Wayland. But, as far I know, that's the closest you can get to having "the best of both worlds".
It may very well be due to the package format after all, as I mentioned in this other thread (we might want to keep it down to this one though just for cleanliness' sake).
I want to thank everyone for the time invested in this problem and all the insights you gave me, even though the problem isn't solved i learned a lot about Linux which is valuable information since I'm quite new to this.
It was a great first experience to post in this forum too.
To switch to Xorg, go to the Login Screen (not the Lock Screen). simply reboot for that. On the Login Screen click on Your Profile so that the Password Field appears. It has to be appeared. When it is appeared, You should see in the bottom right corner a Gear Icon. Click on it and choose the Option ''Zorin Desktop on Xorg'' and then log in and test it.
One interesting thing I saw from their project's development site:
We do not maintain the Flatpak package. Do not report issues related to Flatpak unless the issue can be reproduced with a native package, use Flatpak support instead Flatpakâthe future of application distribution
To answer your questions from the other thread:
Not that I know of, though I suspect most likely not since that would require a re-write on the source code.
The instructions from my earlier post would install the correct version for your operating system. Those — Bookworm, Trixie and Sid — are codenames for Debian branches; do not use those.
I would suggest trying the native package format from that PPA, or use Xorg, or both. It may just be the case that the Flatpak package is unmaintained or has something wrong with it?
The problem is that when i install the right package using apt, the app doesn't follow the system dark theme.
And when I install it using flathub even though the theme is right the font becomes too small.
Using Xorg doesn't fix this theme issue on the apt version, but the font size becomes normal in the flathub app (even though there are some minor theme issues).
I can use the app with no scaling issues (only on white mode) using wayland.
Is there any disadvantage about using xorg vs wayland? I did some research and Xorg is more legacy compatible but wayland is more recent and smooth.
What would you do? Would you use the app with a mismatched theme or switch to xorg and use the flathub version instead of the apt?
Just to clarify, was any of you guys able to change the theme on this app, in any way? I don't think it is possible.
Could it be that the app is designed to be used in Ubuntu 24.04?
Wayland was initially released sixteen years ago, actually.
Xorg is the current standard, not Legacy.
I would and do use Xorg. I do not need all the problems Wayland brings, especially given that the only reason most of it is working is because it is using Xorg and XServer on its backend to patch what Wayland cannot do.
What's the point of using Half Wayland?
It does look like the developer has set it as qt6 only.
This seems to be causing you a lot of headache given that
Exhaile
Cantata
VLC
Quod Libet
are all plenty capable of high bitrate and depth with ALSA configuration.
Many of us get rid of Pulseaudio entirely, sticking purley with ALSA.
you are right, I don't see any visible difference with using wayland vs xorg.
I have pipewire since I need LDAC for my bluetooth headphones, outside of my wired audio setup. Does ALSA have that compatibility? Is there any more efficient way to install this setup I need? Switching to Xorg sounds good and my problem is solved.
I do need the ability to make playlists, import them as folders would be nice too but that isn't a big problem since this command find "$(pwd)" -type f \( -iname "*.mp3" -o -iname "*.flac" -o -iname "*.wav" \) \ | awk 'BEGIN {print "<?xml version=\"1.0\" encoding=\"UTF-8\"?>"; print "<playlist version=\"1\" xmlns=\"http://xspf.org/ns/0/\">"; print "<trackList>"} {print "<track><location>file://"$0"</location></track>"} END {print "</trackList>"; print "</playlist>"}' > playlist.xspf creates me a .xspf file that I can use to import the playlist.
