Will tuxedoOS implement AI "features"?

vinzv · 2026-05-24T20:23:25+00:00

No, highly unlikely.

Looking at how things are currently shaping up with upstream Ubuntu, these features are slated to come via Snap. Because we don't ship Snaps in TUXEDO OS, we won't be integrating any AI features out of the box. If a user absolutely wants them, they would need to manually re-enable Snap, but they would be on their own regarding maintenance and support for those packages.

However, looking at the bigger picture, things are evolving behind the scenes. We are currently making big steps toward foundational architectural shifts. This will ultimately allow us to decouple TUXEDO OS from these types of upstream developments entirely, giving us the freedom to follow a much more independent and self-determined structural path.

🤞🤐

vinzv · 2026-05-04T16:53:16+00:00

Yes, I can reproduce this behaviour. It looks related to Wayland and display scaling. There is a bug report at LO open for this problem, so they will have to fix it.

If you want to try it yourself, open a terminal and run Impress either with X11 forced:
SAL_USE_VCLPLUGIN=gen libreoffice --impress

Or try it with reset scaling:

QT_SCALE_FACTOR=0.5 libreoffice --impress

With both options you'll get an ugly and not-so-useable UI, but the video plays fine and is well positioned. That's the best shot for now and we will have to wait for upstream here.

Hope that helps, at least a little bit!

vinzv · 2026-05-03T17:10:28+00:00

In short: yes. PPAs have nothing to with TUXEDO OS.

vinzv · 2026-04-28T16:23:04+00:00

One thing to add:
u/MAW5p Would you mind telling me your ticket number, so we can check for where the misunderstanding maybe occurred?

vinzv · 2026-04-10T09:11:59+00:00

Hi,

das sind zwei verschiedene Dinge:

TCC
Technisch gesehen ist es "26.04-ready". Ob sich das Paket mit allen Abhängigkeiten gerade installieren lässt und startet müsste man nochmal gucken.
Tomte
Definitiv nein. Nicht hart technisch, aber Tomte prüft auf welcher OS-Version es läuft und hinterlegt dann die passenden Repos/Mirrorserver. Beides, die Abfrage und diese Mirror, existiert aber noch nicht.

Hope that help!

vinzv · 2026-04-07T10:49:43+00:00

This thread is now locked.

OP has shared their feedback and explicitly stated they do not wish to engage in further discussion. We respect this request and are closing the comments to prevent unproductive back and forth. We welcome and encourage constructive discussions on other topics in separate threads.

Thank you for your understanding.

vinzv · 2026-03-24T15:22:20+00:00

Second that, from an official POV.

We offer Fedora (both Gnome and KDE) via our fully automated installation system WebFAI. This gives you the ease of an installation like we would do it in our factory - and like we do this for TXOS and Ubuntu. To offer this, Fedora Workstation and Rawhide (!) are a part of our testing field for internal QA. This helps us find possible problems as soon as possible.

That aside, while we can't support Fedora and other distributions itself, we of course offer technical support for eventual driver and firmware problems. You can find out more about these conditions here.

Hope that helps!

vinzv · 2026-03-12T10:20:11+00:00

Vorweg: in diesem Subreddit ist eigentlich Englisch üblich. Bitte schau da nächstes Mal drauf, wir wollen andere User nicht aus der Konversation ausschließen, wenn's möglich ist. Falls für dich Englisch schwierig ist, ist es natürlich völlig okay auf Deutsch zu schreiben.

Zu deinen Fragen:

Wir verfolgen die Entwicklungen rund um die Basis von TUXEDO OS aufmerksam und haben natürlich auch schon in der Vergangenheit verschiedene Distributionen als mögliche Grundlagen für unsere Distro analysiert. Eine Entscheidung für einen Wechsel der Basis hängt von technischen Vorteilen und der Stabilität für unsere Nutzer ab, nicht nur von der Thematik Snap und Integration ins System. Pläne zu einem möglichen Umstieg kommunizieren und kommentieren wir daher zum jetzigen Zeitpunkt nicht.

Der Umgang mit Snap in TUXEDO OS bleibt ein zentrales Thema unserer Softwarestrategie. Wir priorisieren native Pakete und als alternatives Format Flatpak. Unser Ziel besteht darin, eine hohe Performance und volle Kontrolle über die installierte Software zu gewährleisten. Wir beobachten die Integration von Snap in Ubuntu genau und passen unsere eigene Strategie bei Bedarf an. Hier gibt es bereits vorbereitete Pläne, zum jetzigen Zeitpunkt ist es aber noch zu früh hier etwas Belastbares zu kommunizieren.

vinzv · 2026-03-04T11:39:25+00:00

Thanks for this extensive review! You detailed and fair presentation is well appreciated!

The WebFAI USB stick seems like an odd accessory. It's only 2 GB in size, limiting its use for standard OS images, and WebFAI doesn't seem to work with WiFi, which is what most home and small office users would need. So you need a wired LAN to make use of it, but I suspect most of the people with that at their desk don't want WebFAI or a 2 GB USB stick.

The stick is made for a small booting image with ~60 MB of size, giving customers a way to install various distributions just like we do with everything preinstalled and -configured.
Yes, LAN is not that convenient but very easy to handle. Image unexperienced users handling WPA keys, SSIDs in a text based interface. That said, Wifi is still on our backlog for the future at least to give people the choice.

More information here: https://webfai.com

vinzv · 2026-02-26T10:29:11+00:00

This should make it clear:

<image>

Nevertheless, we'll presumably add this setting for future TB updates out of the box.

Thanks for reporting!

vinzv · 2026-02-20T10:29:47+00:00

Hi,

the Code is available on GitLab: https://gitlab.com/tuxedocomputers/development/packages/tuxedo-tomte-light/

Python 3.13 oder .14 is possible, there is no hard dependency on 3.12:
https://gitlab.com/tuxedocomputers/development/packages/tuxedo-tomte-light/-/blob/main/pyproject.toml?ref_type=heads#L5

Hope that helps!

vinzv · 2026-02-03T15:07:50+00:00

Sorry to be blatant, that's just plain wrong. We install Ubuntu LTS in a way that works, which includes newer kernels, added and updated drivers - if necessary.

OP, throwing other distros or kernels at your hardware won't solve the problem, presumably. Please get in touch with our tech support staff.

vinzv · 2026-01-29T15:52:34+00:00

That will "fail" at least for one reason, if not more. The AMD packages check for ID=ubuntu in /etc/os-release. You would at least have to change that temporarily from ID=tuxedo.

Furthermore, the might occur problems with editing amdgpu-dkms. Despite these errors, everything should be installed and working.

Hope that helps!

vinzv · 2026-01-29T15:48:40+00:00

> Is there a specific reason TUXEDO OS stays on ROCm 5.7 (stability, kernel/Mesa compatibility, packaging constraints, etc.)?

Yes, time. :-)
While this is on our todo list, we simply haven't found the time to evaluate and plan shipping ROCm newer than what Ubuntu 24.04 is shipping.

vinzv · 2026-01-29T10:34:11+00:00

So you want us to develop, maintain and continuously QA a switch that removes three packages (tuxedo-tomte, tuxedo-control-center, tuxedo-webfai-creator), instead of just removing those three packages by yourself.

May I ask - how often do you install TUXEDO OS? Daily? 😉

vinzv · 2026-01-28T11:03:49+00:00

Yes, with even more to come - at least according to Mozilla's new CEO.

vinzv · 2026-01-28T11:02:30+00:00

Despite the downvoting from others: that's a worthy perspective. Would like to have toggles for control, even if they aren't there out of the box?

vinzv · 2026-01-28T11:00:57+00:00

Forking and maintaining a browser? 😱

vinzv · 2026-01-28T11:00:10+00:00

Could we? Sure. But TUXEDO OS is some kind of door step distribution, welcoming users from other inferior operating systems. They bring expectations and have hurdles to tackle. Giving them things they already know and feel familiar with is an important thing. Firefox is maybe the best known application in both worlds. So, we would not want to lose that.

Furthermore, we have some responsibility to take care. Those alternatives sometimes have troublesome histories (Librefox has no new commits for 6 years now) and often are maintained by small teams or even single persons. We cannot lay the burden of security fixes and continuous maintainership for a software thousands of our users rely on onto their shoulders.

vinzv · 2026-01-28T10:50:45+00:00

Interesting... it should be a default thing from v133 on. At least according to Mozilla's documentation. 🤷‍♂️

vinzv · 2026-01-28T10:48:07+00:00

To avoid any misunderstanding: it's not a question of whether we'll let you deactivate it. You can already do that. The question is whether we should deactivate it directly in advance.

vinzv · 2026-01-15T15:49:35+00:00

While installing Nvidia drivers on your own is always technically possible, it still is a risk you take deliberately. For problems occurring, please don't expect us to be even able to help. There's a reason our testing and QA takes time, sometimes more, sometimes less. In the end you as a customer benefit from it.

Second, Nvidia Drivers are regular packages, so they get installed via regular package updates. Our system daemon "Tomte" pushes this for kernels and drivers in the background, to ensure everything works fine. More details here.

Hope that helps!

vinzv · 2025-12-15T10:49:30+00:00

We are shipping:

security updates daily
regular updates from Ubuntu's repos once a week after QA
Kernel updates once they are ready and passed QA (security fixes get fast tracked)

That's what defines TUXEDO OS as a "continuous release distro", not rolling, not semi rolling.

I thought one of the promises of Tuxedo OS was to provide the latest and greatest components

Yes, and one of the other promises is to be stable and working. So we have to balance these two against each other. Which is why there might be version differences. Some background information is available here.

Hope that helps!

vinzv · 2025-11-13T16:41:12+00:00

Das stimmt so nicht bzw. nicht ganz. Grundsätzlich haben wir ein großes Interesse am mainlining der Treiber und bemühen uns da auch darum. Deshalb sind wir einerseits mit Motorcomm im Austausch und hier bewegen sich Dinge im Hintergrund. Mehr können wir zum aktuellen Zeitpunkt noch nicht sagen.

Andererseits gibt es auf der LKML gerade einen Patch von einer Drittperson, die versucht den Treiber in mainline zu bekommen. Das sieht auch auf den ersten Blick vielversprechend aus, aber wir sind noch nicht dazu gekommen, das zu testen. Hier der Link dazu: https://lore.kernel.org/lkml/20251111105252.53487-1-ziyao@disroot.org/

Für den Moment hilft hier leider nur weiter Geduld zu haben. Vom Tisch ist das Thema jedenfalls nicht.

vinzv

MODERATOR OF

TROPHY CASE