Assigning to the maintainer.

epiphany - deprecated
gnome-clocks - deprecated

I think you solved that by yourself: you're using Python 3.9.1 when Solus is officially shipping 3.7.9.

How is pulling in polkit-gnome, scrot and dmenu as required dependencies "simple defaults"? I don't even use dmenu with i3 (I use rofi) and you can very well use the KDE or MATE polkit daemon instead of the GNOME one...

I would argue that music player control, which is included in the default configuration, is more complex and inessential than wallpaper configuration.

This is pretty silly. Of course it doesn't have a wallpaper. Aside from some pretty simple defaults, the whole point is you configure the rest of it.

A question is, which wallpaper should be used? Should there be a special wallpaper for i3 like there is for KDE?

Keyboard disabling started working after latest general system upgrade. Auto rotation started working after installing iio-sensor-proxy.

This appears to be fixed now. I cannot reproduce.

Umm, yes, you're right. Do you know if gst-inspect-1.0 | grep lv2 should give me lv2 plug-ins I have installed? Because it shows nothing.

Isn't the pulseeffects issue rather related to the lisp-plug-ins integration?

Since the 4.5 update Pulseeffects gets its equalizer from calf, so it's grayed out. Right now, only feature available is autogain, so I consider Pulseeffects broken at this point. Should this thread be continued or new one made?

Solid work @so-lo =)

I packaged before but not on Solus so I think I still fall into the required noob category. :)

Confirmed, we do not have pkgconfig(lilv-0) (lilv / lilv-devel, the library responsible for lv2 plugin support) in gstreamer-1.0-plugins-bad package, hence why it is not enabled. Considering this an improvement over a package fix since the gstreamer bad plugins package isn't fundamentally broken.

Approved. If someone (read the IMPORTANT bit after) wants to patch the gimprc file and provide a package update patch for it while I'm "away" on holidays, go for it. Otherwise I can when I'm "back". Here's the steps:

No. Those that want it will already know how to add it into the file or understand that this is something obscure enough and they'd already Google it and as a result find the answer.

@JoshStrobl Can we at least put it in but commented out, so it's easy to enable?

No.

Basically no distribution I have ever used does this. The only gain I could possibly imagine is making sure you didn't type a wrong number of keys while entering your password, then again you could understand you did this with the re-type prompt given 2 seconds later.

Please no! Not displaying asterisks is the standard Unix way of doing it, if a user wants password feedback he can turn it on himself from that file.
Having this enabled is also a security issue, because anyone looking over your shoulder can see how many characters you have typed.

This seems to be the use of xfont

@kyrios123 Can you confirm this please?

See yursan's comment.

I think you should report Budgie's issues to https://github.com/solus-project/budgie-desktop/issues/new

A unbreak system command would be quite useful (I speak from experience of breaking Solus), though we would also probably want a method of making it obvious to users such a method exists. A recovery boot option would probably be the best way to go about it.

@kyrios123 That work perfectly thanks for fixing that most appreciated :)

@kyrios please put it up, I can confirm it fixes the materials crash.

For me cura doesn't crash when I add a printer (note that I don't have a 3D printer so I just randomly select a model and I set a dummy IP address).

In T6555#117894, @kyrios123 wrote:

Is a task request needed for packaging fdm_materials ?

Is a task request needed for packaging fdm_materials ?

Using about in cura it says it built from master and not from a tagged release

From logs

In T5164#101427, @kyrios123 wrote:

Should I also add the replace key in the package.yml of R2689 or is it not necessary if they get deactivated in Phab ?

Should I also add the replace key in the package.yml of R2689 or is it not necessary if they get deactivated in Phab ?

I have created a list of unused git repos for packages (which means they will no longer get globally pulled). Though they likely should be deactivated in Phab as well.

@baimafeima No those are completely different programs.

I also wonder about Gnome Characters (https://github.com/GNOME/gnome-characters/releases) and Character Map/Gucharmap (https://github.com/GNOME/gucharmap/releases)...

Validate your packages

I know a script would be just like a kind of workaround and not an ultimate goal, that's why I tagged this as Low Hanging Fruit and perhaps with your experience of Solus and your deeper knowledge of the system it could be something you'd rather discourage.

I don't think a script is the ultimate goal (a very interim solution at best). Scripts make too many assumptions, and locales really mess it up. There's also the issue of having to find the script much like you have to find the commands to run that would be part of the script