Picard daily builds

MusicBrainz Picard
22

The Picard master branch now got the changes for switching to PyQt6 merged. This is a first step towards Picard 3. Currently this means things might be more broken then usual and plugins won’t work (updating the plugin system will come soon).

For now the daily builds I provide have switched over to the 2.10.x branch, in which we will provide future version of Picard 2.10 as we want to maintain this for a while. The same is true for the latest “edge” release on Snapcraft, which can installed with snap install --edge picard.

Updated daily builds for the latest master will come later again. I need to update the build itself to provide necessary dependencies. But also I want to have stabilized the master branch a bit more. So for now the builds track the progress towards the upcoming 2.10.x releases.

6 Likes
23

Version 2.10.1.dev2 (59-a6f816c7.20231223004418) works on Windows 11 Pro. :wink:

At the moment it still returns “standalone recordings” when it shouldn’t.

24

I found this:

$ grep QT ~/.profile
export QT_STYLE_OVERRIDE=Adwaita-Dark

I haven’t tested it, but on the machine with a dark picard, it was in the ~/.profile and on the machine with light picard it was not.

So insert export QT_STYLE_OVERRIDE=<theme> in ~/.profile with whatever your preferred light/dark theme is. Presumably you could script it to match the theme you pull from dconf.

25

No, this is not the solution. This was happening on the machine with the picard dark mode active as well as on the desktop where it was not:

QApplication: invalid style override ‘Adwaita-Dark’ passed, ignoring it.
Available styles: kvantum-dark, kvantum, Windows, Fusion

So exporting
export=QT_STYLE_OVERRIDE=’kvantum-dark’

did work on the desktop to get a dark picard…so that goes in ~/.profile?

Installing additional qt5-plugins with
apt install qt5-style-plugins
yielded more theme options but none of them dark apparetly:

Application: invalid style override ‘Adwaita-Dark’ passed, ignoring it.
Available styles: kvantum-dark, kvantum, cleanlooks, gtk2, cde, motif, plastique, Windows, Fusion
Warning: config file 3.0.0.dev2 was created by a more recent version of Picard (current is 2.13.3.final0)

also, you can see what version of picard there.

As I’m doing this, I recalled that quassel irc has .qss files for themeing quassel. perhaps that could be an answer for Picard as well?

26

Related thread:

27

No, this is not the solution. This was happening on the machine with the picard dark mode active as well as on the desktop where it was not:

QApplication: invalid style override ‘Adwaita-Dark’ passed, ignoring it.
Available styles: kvantum-dark, kvantum, Windows, Fusion

So exporting
export=QT_STYLE_OVERRIDE=’kvantum-dark’

did work on the desktop to get a dark picard…so that goes in ~/.profile?

Installing additional qt5-plugins with
apt install qt5-style-plugins
yielded more theme options but none of them dark apparetly:

Application: invalid style override ‘Adwaita-Dark’ passed, ignoring it.
Available styles: kvantum-dark, kvantum, cleanlooks, gtk2, cde, motif, plastique, Windows, Fusion
Warning: config file 3.0.0.dev2 was created by a more recent version of Picard (current is 2.13.3.final0)

also, you can see what version of picard there.

As I’m doing this, I recalled that quassel irc has .qss files for themeing quassel. perhaps that could be an answer for Picard as well?

It’s also possible that this has something to do with why it was working in dark mode on my one machine:

pwd: /etc/skel/.config/Kvantum !568 # cat kvantum.kvconfig
theme=KvRhinoDark

I can only guess that this gets created in all the user directories created after the Rhino Linux Unicorn (XFCE) desktop (or related component) adds this to /etc/skel/.config.