lanefu

There's a service called lightdm that you'll need to look at. It launches X and the GUI login. Hope that helps

I'm not familiar with that. What causes and issue with the wifi and USB 3?

You're probably going to need to be a little more hands on with the tool you choose. I like borg and borgmatic.

Hi great question. Def can be confusing. We're working to be more clear. GitHub issues (NOT PRs) are meant to be specific to the Armbian build engine and not specific to devices. Raise device issues on forum for conversation and hopefully find the attention of a maintainer. (Part of reason we do it on forum is it creates too much noise on GitHub for such a small team of devs) If it's an issue a maintainer or armbian developer thinks it needs to be prioritized, they will add to our Jira For those that don't like posting on forum anybody can open a draft PR with a proposed solution and explanation of what's being solved in GitHub

Yeah that was my experience with libgpiod a year or 2 ago. No pull-ups etc. It's not ready for prime use. Sysfs gpio access is the most consistent method to deal with gpio accross different devices. And I'll gladly take it over 20 forks of wiring pi (which truly is deprecated in a much more literal sense) for background Even Adafruit jumped on the bandwagon libgpiod when it was announced but they quickly backed off quietly once the reality hit that it wasn't ready for their core customer base. Deprecated in Kernel land doesn't meant stop using immediately, it means don't extend and start preparing/be aware for the (long-term) future

This functionality existed in our pervious stable kernel 5.10.y and should absolutely continue to be supported. It was a breaking change that should not have happened. lane

Ha yeah it was extremely deprecated lol. I was in a "there has to be a markdown plugin" mode scouring the interweb and saw that. On that note I think I did toggle the plain text paste flag off. So copying rendered markdown into the editor may work. Anyway the editor seems to be a whole seperate body of work independent from Invision other than it'd what they use. Sounds like Invision actually has their own upgrading to do from "v4" to "v5"

is this post meant to be in this thread?

That's beyond the feature-scope of Armbian. And yes a great feature on diet-pi, which makes a very nice appliance experience for the user..... part of it's appliciance-ification approach to config management is also what lets it back up so nicely.

oh lord, really? you use it?

All great points. Oneshot seems appropriate. I don't think there's an outstanding technical reason that would prevent us from changing it. Feel free to open a draft pull request as your developing. would ask that this piece be a separate PR from one shot service changes discussed.

Oh! Thanks for clarifying. Will try to get to it but running out of time. Feel free to make changes and comment on the open PR.

yep OMG i keep on fixing it for-myself on my boxes and forgetting to upstream so sorry.... https://github.com/armbian/build/pull/3603

What ELSE do you have for sale @NicoD?!

Thanks @NicoD

I wonder if it was the Armbian RPI images that caused them to add us!

We have community member in France who needed an RPI3 for $dayjob. They found one and dont need one. But it turns out @NicoDhas some RPIs for sale and more. Help support Nicod and channel by purchasing all the crap in his office so he can clean up his camera angles ! 😂😂😂

TLDR; If you would like to help us test desktop pul requests, please let us know what device would work, and any additional preferences. Desktop improvements really are another unique create. As you know we don't provide supported desktops, but we do make a like of nightlies, and there are contributors like @Rich Neese that really do a ton of work to make this stuff better. Another part of our improvement process is stronger peer review on pull requests before merging. This means we really need to start testing desktop images at the pull requests level.... Which we can gladly build images for PRs, just need community members will to download image, install, test and provide feedback. Idea is... get list of willing testers and their preferred devices. We can then produce images and link inside Pull Requests Like This. Then we can just @mention user to try and review within the github issue and comment.. Easy peasy. no git checkouts, building, etc. if Interested please reply here with what you're willing to test, and github user id if you're comfortable. if not we can DM. thank you!

It was probably not considered.

Legacy functionality -- bbcode support has been disabled. The current editor version has richer formatting support natively.. Disabling the bbcode formatting should improve editor performance.

Let's keep the conversation going.. Code for related components here: https://github.com/armbian/build/tree/master/packages/bsp/common/usr/lib/armbian The truncatelogs script does address journald, but to your point it might not be enough. Take a look at the history and blame log to see if there's some useful context https://github.com/armbian/build/blame/master/packages/bsp/common/usr/lib/armbian/armbian-ramlog

New rules have been applied. Will wait 1 week before requiring code signing... so get your code signing working folks @lanefuI'm talking to you, buddy

Ran ran job looks approved. (Link PR next time on post please)

It was often the case but not always. Didn't happen 100% of the time. We're in a spot where we really need to be more thorough.

@IgorI support this 1000% This is common practice is large projects in open source and enterprise. I definitely think we're ready to add this process. It's a great sign that our project is growing more mature. Lets strongly encourage that _anybody_ can click to suggest a reviewer so that the PR and discussion can get attention quickly. Great chance for all the devs to learn more about each other.