Just a wild guess, what GPU and drivers are you using. That could explain why newest Proton doesn't work, maybe try beta or stable instead if you are on Nvidia?

There might be some problems with Snap after updating Pulseaudio, but I'm really not sure.
I just installed snap teams-insiders and no sound devices are visible in it. I also got an error during installation INFO snap "teams-insiders" has bad plugs or slots: audio-playback (unknown interface "audio-playback"); audio-record (unknown interface "audio-record").
But I have not used it before, so it is quite likely the snap is broken or my snap config is wrong. Could somebody else check if audio still works in your snaps?

Also both of my issues are now resolved, task list now works as expected and icon now will the entire screen in both orientations, and look really nice. You did a stellar job, thank you so much!

Is the way Arch or Fedora does it good enough? I don't feel experienced enough to do it myself from scratch. Maybe there is somebody more skilled than me that could do it or at least help me.

After updating my main machine I noticed another 2 weird behaviours, which I don't know if they are expected:

In T9379#178277, @JoshStrobl wrote:

Icon spacing is much bigger than before and I think it is too big

You can change the icon sizes in Budgie Desktop settings. They're reflective of expected supported icon sizes (32x32, 48x48, 64x64, 96x96), I don't want to be loading in larger versions of Pixbufs than needed and scaling them down in the name of customization, or use Pixbuf to load (which would also need to handle the SVGs). It's similar behavior to the IconTasklist and even to Nautilus' old desktop view behavior (zoom swaps between supported sizes).

Updated Budgie on my main PC and everything seems to work fine.
But as a heavy user of desktop icons the new implementation leaves a bit to be desired. It works as described, but it lacks useful features:

Could you look at improving the manpage? Right now most of it is installation instructions for different OSes, which are useless as you already have installed it. I don't know if you could trim most of it during the packaging or maybe report that to the original author?

To cite the author:

What is wrong with OBS?
A lot of people online suggest using OBS's replay buffer feature. However this requires opening OBS and start recording. I do not know when something will happen that I want to share. Might not even happen while playing a game. I just want something in the background (like a systemd service) so that whenever something happens I can record it.

Sure OBS can do that, but on Windows after I enable it in a controll panel I can forget about it and days later I'm one shortcut away from starting a recording or saving a replay. This is exactly what ReplaySorcery offers, while with OBS you have to remember to launch it every time before you play. Also this solution is much lighter on the resources.

And if we want a wine version that has best possible game compatibility, why not Proton-GE T9232? Although in its default configuration it does not replace system-wide wine, so it is not quite what you are asking for, but game compatibility is miles better than wine-staging.

The author can't reproduce our errors, but I found an fix to make it work on my machine.
Delete the /home/jacek/.config/vkBasalt/vkBasalt.conf just to be sure, then configure it through GOverlay.
Go to that file and edit:
reshadeTexturePath = /home/jacek/.local/share/reshade
to
reshadeTexturePath = /home/jacek/.local/share/reshade/Textures (So just add "/Textures" to the end).
This fixed it for me and now it works with CAS and SMAA. If it will also work for you then we could pass that on to the creator as a fix.

Error for CAS only says vkBasalt err: Does the filepath exist and does it not include spaces?, so doesn't tell me what exactly is wrong. But the error for SMAA tells me exactly what is wrong so it can be fixed.
Both suggest vkBasalt conf is configured for wrong directory by GOverlay, but where SMAA I can go around it, I don't know what the path to CAS is.
I hope they are both the same issue and can be fixed by the author, because I'm out of ideas.

I figured it out for my machine, the problem isn't with the vkBasalt, but with GOverlay. And not even my packaging, but probably the creator's fault.
On my machine it was searching for file at /home/jacek/.local/share/reshade/AreaTex.dds, but it really was at /home/jacek/.local/share/reshade/Textures/AreaTex.dds so when I copied all files from Textures to main reshade folder, it stopped crashing.
I will report it to the creator, and hopefully he will fix it.
Edit: reported here: https://github.com/benjamimgois/goverlay/issues/62

You are right, it doesn't work for me either. I could have sworn it worked when I last updated GOverlay, but maybe it slipped past my testing, or recent update broke it.
Sorry, I will try to figure out what is wrong.

As this is under active development, can it now be accepted for inclusion? Last diff by @eyecreate had to be abandoned because of lack of development, but that is no longer the case

This was already talked about in T4194, even @eyecreate provided working diffs. So there is some demand.

Reorder builddeps and move .rules file to correct location.

Reorder builddeps and turn off static.

Add patterns.

Solus team can't do much if there isn't driver for it. So the best thing you can do is to monitor support for it on any linux distribution, and if there are things that need to be changed to make it work, you could report them here.
For example it could happen that necessary drivers make their way into the kernel, but they need to be enabled in Solus's kernel config.

You can't use AUR on Solus because they are completely different systems, and many instructions are different. You can sometimes use them as a guide for creating a package for Solus, but that is not necessary here.
So unfortunately there it seems they won't package Chromium for Solus because Google needs api key, so you have 3 options:

This is proton i made to be used from withing Steam and tutorials and guides mention only that. I just wanted to add that it also can be used from within Lutris, but that's just a bonus.
And I just said this is not system wide to clarify this is not replacement for Wine, and that it is gaming-focused and Steam-only

So the desktop would need use V-Sync when no full screen app is running, so that the screen is refreshing at it maximum rate?

Also the current driver doesn't work with some devices using exFAT (like PS VIta), while the Samsung driver and Windows work just fine.

Could you please consider accepting it? It is under active development, stable and I've working package.yml for it.
Only reason against including it is how easy it is to install it using pip.

They found a few fixes for similar issues here, including forcing a language or running through Lutris https://forum.manjaro.org/t/rise-of-the-tomb-raider-does-not-launch/136930/18
Hope it helps

I don't have any other idea, but do you have 32bit driver installed? Depending on your driver version this is nvidia-glx-driver-32bit or nvidia-beta-driver-32bit

Is this the only Steam game that causes problems?
Has this game worked before for you?
Could you try launching whole Steam from the command line and launch the game from there?

You could uninstall the current drivers and try with nvidia beta current or nvidia developer current.

Changed the description to please IDoS

Description and cosmetic changes to package.yml

Switch pkgconfig of gtk-2-devel

Removed leftover comment

Fix the MAINTAINERS.md

I built using this package.yml and verified it works with Steam games, so this is ready to be accepted into the repos

1. This is distributed as a Debian package and not as a source code, which is not ideal and rarely accepted to the repos.
2. Does the license permit redistribution and repackaging? If not this would need to be added to the 3rd party section, and Core Team usually doesn't want to do that.

So this could be hard to accept into the repos, maybe you could give more explanation of what it does?

What I meant that by default we will have 2 different mouse hover behaviours - active screens will switch, but active windows will not. Still it is up to others to decide

Remember that there also is "Activate window on mouse hover" or something like that, which is disabled by default. So one thing would be changed by hovering the mouse, and one not. This might lead to some confusion.
But I personally agree with what you suggest.

Maybe you are looking in the wrong place? I sometimes loose middle click when pressing both buttons. So I enable it with xinput at every boot.
So you could try typing xinput, then finding name of your touchpad and doing something like xinput list-props "AlpsPS/2 ALPS DualPoint TouchPad".
Then you set a property like xinput set-prop "AlpsPS/2 ALPS DualPoint TouchPad" "libinput Middle Emulation Enabled" 1
Your problem still might be Plasma specific, but it is worth a try.

It has been 3 years since the initial release, it is actively developed and is a re-implementation of author's previous version from 10 years ago. Also the only feature missing is terminal apperance configuration.
And I haven't had any problems for last few months. But obviously the choice is up to you.

Thank you so much for your answer! What I was lacking was /etc/modules-load.d/kvmgt.conffile, which I didn't found in any documentation, maybe I missed it. Now it does work just fine.
Only peculiar thing is I still get i915 0000:00:02.0: Direct firmware load for i915/gvt/vid_0x8086_did_0x161e_rid_0x09.golden_hw_state failed with error -2 in dmesg.

To remove redundant dependencies you need to go through each one and look at reverse dependencies. Here is the process:

Are you saying that compiz-plugins-extra package still doesn't include all the plugins you need?

You should be more specific, what errors? One easy thing you could try to check if Legacy Boot is set to on or off. If you disable it you will force the system to boot in EFI mode (instead of BIOS), which should be the default for all modern hardware.

I'm on Budgie and I haven't encountered a single problem, and even noticed an improvement. Automatic screen rotation used to be wery smooth on Gnome, and on Budgie the screen went black for a second and then the entire interface spasmed out. Now it is really smooth

I think this package can stay as it is, but if next time I would need newer versions of some dependencies, then what steps should I take:

1. Create a package update requests for each dependency, one for all or can I straight up post the updated diffs?
2. If other packages depending on it (like Ardour and Audacity on suil) need a bump to be rebuilt, should I also post a diff for all them, or you will take care for that?

Rebase properly and up the version number

But this will create a new diff on phabricator, won't it?

@kyrios123 Do I need to make a new diff? Any tips would be helpful

Rebased and incremented the build number
I hope I did it correctly

• Update Cinelerra-GG to 2020.02.29

I'm working on it

Oh, phabricator didn't submit my comment from 5 days ago...
So what should I do? Can we proceed like it is, or should I update those 3 dependencies so Cinelerra is less static? Will I need to create a local repo for that?

Light sensor is now working correctly, thank you so much!

Fixed the email