triage VS os

There is a known issue on Elementary, system not cleaning automatically old kernel, completely filled the /boot partition.

You can open up an issue here of you’re not sure about the correct repo: https://github.com/elementary/triage

https://github.com/elementary/triage, submit a issue here :))

As described here, sometimes one of my displays sets itself to a lower resolution (on boot) and there's no option to change it. The only "fix" is to reboot my PC. Does anyone has any ideas?

Thank you for the links / your time. I was able to boot 20.04 and 21 ubuntu so am wondering if its something other than this bug on my dell, as i am not getting that error message. I read somewhere that https://github.com/ventoy/Ventoy wrote an iso raw and rufus (which i used) did not, so going to create a new boot disk with ventoy when home tonight and try that. Only have UEFI as its a new laptop and think i cant boot from legacy but hopefully the workarounds here https://github.com/elementary/triage/issues/74 will help some people! Thanks.

I am talking about this issue for example, and the management of it. Of course the eOS developers didn't do anything wrong, Ubuntu devs messed up everything and lets wait for them to fix it. Meanwhile we are going to mix repos to our liking, and blame other devs if some apps wont install or work. The problem is not having bugs or issues with a software, they should be acknowledged and fixed, not blamed on other devs. I am very happy to hack around my system, but please dont try selling a frankensystem that has a 3 yr old ubuntu base as a "capable replacement for macos" because for example it wont even boot for me, although on the front page you can only "purchase" it (I know that if I type in 0usd i can just dl it, not my point)

Looks like it’s an issue facing more than just Neon - this is for Elementary OS, workaround works https://github.com/elementary/triage/issues/74

Cool. My goal in asking is to find out if there's anything I should know before trying to update the build script myself.. This is my first time trying to build an OS, so if I'm getting in way over my head, I'd definitely like to know that in advance.

From what I understand, OSTree-based images[0] are in progress and will remediate this.

[0] https://github.com/elementary/os/pull/582

elementaryOS is licensed under GPLv3. You may absolutely sell hardware that comes with it pre-installed, so long as any modifications you have made to the software are also released under GPLv3. There are non-commercial licenses, but they are not free and open source.

Problem still occurs, here’s a bug report: https://github.com/elementary/os/issues/634

Go to https://github.com/elementary/os

Sounds like it's probably a bug that you'll wanna report to the eOS developers. They prefer getting those on their GitHub Issues page if you have a GitHub account

I really hope it does. I have a discussion open here: https://github.com/elementary/os/discussions/552

with elementary OS working on an OSTREE image what is the possibility of linux mint also joining in and also working on an OSTREE image for their distro?

I’m not sure tbh. I generally stay away from Nvidia because of issues like this. It’s probably worth opening a new issue report and maybe someone else has access to this hardware https://github.com/elementary/os

Surprising enough (expectations set by decades of Debian/Ubuntu) that I had to look it up, but it's true https://github.com/elementary/os/wiki/Release-Upgrades#perfo...