@Justin iirc that wasn't an issue with it being a new conky so much as being poorly configured at build time. I think I personally fixed that awhile back.

@cata0309 I appreciate the fact that you are new here and don't yet understand how we do things, but please, don't demand things. We are not other distros. We frequently say no to things because they are technically poor solutions to problems or because better solutions exist. I also recognize that you are still irritated that we refused your request for out-of-tree wireless drivers. You are free to build and compile whatever you want for your system.

@Girtablulu is right @crom5, you need to stop doing this.

LGTM. Thanks!

LGTM. thanks!

This has not been accepted for inclusion with the understanding that all of the recent releases on Github are marked as "Pre-Release" and it is ineligible until that changes.

In T4379#152645, @thespyboss wrote:

Can the ckb-next be updated to the newest ckb-next on the github page?

LGTM. Thanks!

@Solus_BLN This was merged as a duplicate on purpose. Please don't re-open it.

@r3r57 Please file a task. If you comment here I will forget.

They figured it out eventually, just never fixed their patches. This is waiting for a maintainer to step forward.

And our point is that Linux doesn't need a firewall if there aren't any open incoming ports on a base install. Linux rejects incoming requests unless something is actively listening on an incoming port. That's been the case for as long as I can remember.

Don't forget the ISO they used to install in the first place.

It's set up this way so that you have a default menu in i3. You should be able to remove just dmenu with a simple:

sudo eopkg rm --ignore-dependency dmenu