@alecbcs can you you give it a quick test and confirm nothing breaks for you as well?

@Girtablulu I can confirm that using breeze-cursor now no longer breaks flatpak apps. However, I'm still seeing two breeze cursor themes in the budgie desktop settings.

You did use this diff? (Because I dont have anymore two packages) It's not in unstable at the moment

In D6763#106878, @Girtablulu wrote:

You did use this diff? (Because I dont have anymore two packages) It's not in unstable at the moment

Oh crap, no I'm sorry I saw a update for Breeze this morning in unstable and I thought it was this patch. Is there any simple way to clone a diff through arcanist? Or should I just copy these files?

At this stage I wouldn't worry about it. I've been testing it and trying to work out a solution for the duplicate entries (if we do a symlink for "default" theme, which is currently needed for slick-greeter). No success on that front yet.

Stole @Girtablulu's thunder, did R450:7740e26d4e05: Drop our duplicate "default" entry. and R3576:2d67d7f38d32: Added patch to force a specific default cursor icon.

@Girtablulu feel free to abandon should @alecbcs's issues get resolved from the new packages landing in unstable.

After updating to the latest version in the unstable repository I can confirm that I now only have one breeze-cursor option and it works in Flatpak apps. However, after updating breeze my system reverted to Adwaita (after a reboot) and I had to reinstall the breeze-cursor theme through eopkg to get it to show up in budgie desktop settings.

In D6763#107108, @alecbcs wrote:

After updating to the latest version in the unstable repository I can confirm that I now only have one breeze-cursor option and it works in Flatpak apps. However, after updating breeze my system reverted to Adwaita (after a reboot) and I had to reinstall the breeze-cursor theme through eopkg to get it to show up in budgie desktop settings.

This also happened to me.

Why was this abandoned and reverted? Besides the package woes, it seemed like a positive change.

Making actually looking at the breeze package history before commenting would provide some insight?

In D6763#107173, @JoshStrobl wrote:

Making actually looking at the breeze package history before commenting would provide some insight?

No need to be hostile, Josh. I'll take a look.