[BUG] plymouth splash screen freezed on dual gpu computers (works well on qemu)
i need to see how pear os or others implement the plymouth splash to solve this
We don't want to be a one-person distro. Do you want to collaborate? Welcome! It doesn't matter your level or if you are a programmer or not. What's more, it's even good for us to have professional people and beginners because that way we can have both ways of seeing things.
Chat with the community (most active). There is always someone to assist you and collaborate instantly. English and Spanish languages.
Are you more of a geek? Well we have Matrix channel! Another great place to talk, with fewer integrations than Discord, but just as functional.
Every repository, every build and every line of code is public and auditable.
See what is pending, in progress or done — and pick a task.
Known issues are tracked openly. Found one we don't know about? Report it.
i need to see how pear os or others implement the plymouth splash to solve this
Ideas that occur to us or that you propose.
Crear algo mejor que zimaos: Un debian o arch linux, con plasma bigscreen, control remoto de casaos (tuneado con nuestr logo), configurador inicial remoto (tipo umbrel). suite arr* configurada, jellyfin, vacuumtube, android emulator…
Make a Siri with a very lightweight local model and openclaw, interface using SiriWave and audio detection and put it in the form of a GNOME extension
We don't stop having ideas and we need you to decide and give your opinion.
A distro focused on TV and NAS. Save your videos or movies and enjoy them on your television, everything that Android TV or Apple doesn’t do.
It would include CasaOS and PLasma Bigscreen
A Windows-inspired edition of Pulsar OS for people coming from Windows.
What we are thinking about:
Open decision — we need your input: should Wintux be built on KDE Plasma or GNOME? We are leaning towards KDE Plasma for a closer Windows feel, but we want the community to weigh in on Discord and Matrix.
You can help with any error or proposal, but here we list what matters most to us.
If there is nothing here, it may be a good sign or that the page is crashing (most likely).
Pulsar OS grows because people recommend it and help it. We want to thank the people who make that happen — publicly.
Recommend Pulsar OS and bring people into Discord or Matrix. When new members arrive, tell us who invited them — or write your name in the hall-of-fame file of the repo.
Write about Pulsar OS, run an audit, review code, translate, design, test on real hardware, document, or collaborate on anything.
Pulsar OS is open source, built by and for the community. Whether you're a developer, designer, translator, documentation writer or simply want to help out, there is a place for you.
All of Pulsar OS source code is available on GitHub. Explore the repositories, open issues, send pull requests and follow development in real time. The project board shows which tasks are pending, in progress or completed.
We welcome pull requests developed with the help of AI assistants, as long as they meet the following requirements:
AI is a powerful productivity tool, not a replacement for responsibility. If your PR is well tested and properly documented, it will be reviewed like any other.
You don't need to be a programmer to help. You can contribute with documentation, translations, graphic design, bug reports, or simply by sharing Pulsar OS with others. Every bit helps.
No Linux elitism and zero gatekeeping — we have no time for loonixtards. We are a friendly bunch of geeks who love talking about Pulsar OS, and several of us are around the chats every day, so there is always someone to answer your questions.
Beginners are more than welcome: every bit of help counts, no matter how small. Ask without fear — the only stupid question is the one you don't ask.
Whether you audit, test, translate, code or simply spread the word — your name belongs on the wall.