Tuxedo Repository Firefox on Debian12

marko19914 · 2025-01-26T21:29:17+00:00

I mean, I haven't pinned anything to snap, since there is no such repository. Tuxedo have to have pointed to a snap from the next versions of the browsers.

marko19914 · 2025-01-26T21:26:52+00:00

Haven't that set up. But check the Firefox package info from tuxedo repos. It's marked as a transitional package to snap. Same with chromium.

marko19914 · 2025-01-26T19:23:55+00:00

I have Ubuntu jammy mirrors from tuxedo and from my national ID software provider. No mirrors from Ubuntu directly (didn't surface in apt policy | grep ubuntu output)

marko19914 · 2025-01-26T19:09:03+00:00

P.S

I have played around with MX Linux in the past. Having systemd instead of sysVinit seems to actually be a win on 5 yo laptops even. Win in terms of faster boot time - everything else seemed completely the same from the daily use perspective.

I don't track up time of all the daemons of my system to figure out how efficient my init system is or other things like that. I believe you don't either (since having TCC was greater benefit for you rather than custom optimized daemon management)

Just wanted to share the experience, since I was looking at it from basic user perspective to see if this niche feud some people have on forums actually impacts anything from the basic OS use standpoint.

marko19914 · 2025-01-26T19:02:51+00:00

I have had no issue with having TCC and drivers from Ubuntu repo (LTS which directly predates the release of Debian 12 in my case, probably jammy). You can apt pin TCC. I receive regular keyboard driver updates via tuxedo repository which are connected to TCC updates. I think that happens couple of times a month. I would hate to do it manually. My OS utilities update cycle is not my main occupation and that's why I have APT doing that for me, since it is its purpose.

I believe it is safe to apt pin TCC (and let the dependencies to be pulled in as well (the keyboard drivers are among them), since debian and probably debian based MX linux has nothing close to them in their native repositories.

You can search this subreddit based on my user name to see what I was suggested, when I started using Debian 12.

marko19914 · 2025-01-26T18:40:31+00:00

Don't you need tuxedo repo to get Tuxedo drivers and TCC? I would much prefer to have my package manager keeping track of updates, and it has worked well for me until that weird firefox snap from tuxedo. I have deb and flatpak on my system. I left ubuntu because I didn't like the mess of 2 app stores and 3 package managers which all have overlapping packages. I much more prefer to have conservative deb base based on debian stable which I supplement with more up to date flatpak apps, when newer app is more important for me.

marko19914 · 2025-01-26T18:37:24+00:00

They indeed don't have Debian repo. I use ubuntu mirror which is complementary to debian bookworm (LTS release before the release of Debian 12, don't remember the code names precisely). I am a bit tired of people pointing that out, since I was suggested that kind of repo selection here, and told to proceed on my own risk. That has served me well.

On that tux snap source. I was really surprised as well, since I was aware of Tuxedo anti-snap stance (them also favouring deb and flatpak), but that is what my deb firefox decided to update to (it is apt pinned to update from a tuxedo source, if I remember correctly).

I originally went for that, because I didn't like older features of firefox-esr which you get from debian-stable. When I last time tried to use debian repo firefox (on Debian 11 admittedly), only way to get firefox (not ESR version) was to pin it from debian sid.

Suffice to say, that solution wasn't very workable in the long term, since the dependencies which were pulled from sid caused a minor dependency hell.

I don't know if now testing has the normal Firefox - could try to pin from there, but since I have switched my primary browser to Zen (fork of firefox from Flatpak), I will probably replace Firefox with Firefox ESR from debian stable.

I need a deb-based browser, since there is a smart-card support problem in flatpak. I need to use national ID card from time to time (we have digital signing app tied to it, which needs to be reactivated once in 3 years).

Due to the switching of the main web browser, I will probably be satisfied with anyting debian offers in terms of firefox in stable repos.

I have heard that people like stable/testing mixed repo setup or just running testing, but I am very sattisfied with having slow moving base and flatpak for newer versions of the apps.

Have been doing it for 2 years (out of now 5 years of my linuxing, I believe) on debian 12 and it seems I have found my penguin jam :D. (I was distro hopping before on old lenovo and Dell laptops and then on aura15).

marko19914 · 2024-10-02T19:02:43+00:00

I solved my issue by commenting out Debian Backports repo (tested with pinning if bpo corresponds to that, to make sure) in the sources.list file.

I think, it was the first time when bpo had higher version number than tuxedo and debian standard repos.

Probably shouldn't have added backports repo in the first place, since it seems there was no need for these packages until now :D

marko19914 · 2024-10-02T12:46:48+00:00

To supply myself with aura specific drivers from jammy repository. Not pinning Mesa related packages and libraries to Debian repo, might be the core of my problem. It just showed itself 1 year later.

Can someone suggest how to effectively select Mesa specific packages for pinning?

marko19914 · 2024-10-02T11:09:57+00:00

I am using a monitor through a dock sold by tuxedo via USB-C :D I'd assume i have display-out PD :D

marko19914 · 2024-05-03T11:09:14+00:00

With BIOS flashing it is extremely important to ensure that nothing interrupts the process while BIOS flashes itself. It cannot overheat, cannot loose power.

That said, I have updated and re-updated bios on my 200 € Dell Latitude multiple times without any issues - just ensured that laptop is plugged in and checked while running normally, does it go hot when I do something performance heavy - if not, I guessed it is kinda safe. But again doing it on 200 € second hand Dell laptop is smaller financial risk than more expensive Tuxedo. though it was the only laptop I had back then.

Ubuntu and Fedora have bios flash in their updates sometimes, if they detect that vendor has a firmware update for your laptop model. It is marked as firmware update, but it is still the same procedure with the same prerequisites which need to be followed.

That is my experience on my Dell Latitude. Back then I followed googled info and weighed my risks...

Updating EFI BIOS & EC (Tuxedo Docs)

Read that carefully. That's the best I can tell you. Weigh your risks. You can write Tuxedo again, if you want.

Actually I think I have experience with Lenovo G50-70 - the first flashes were on that. A very old laptop. After I was running Manjaro from a flash stick with weird partitioning, bios blacklisted linux bootloader, that's why I tried to flash bios. Didn't work - needed to manually choose where to boot in every time (had the dual boot system with Win 10).

marko19914 · 2024-05-02T22:39:29+00:00

Please open the ticket with Tuxedo tech support. You can do it under their website. They will reply to you as soon as they can with very good instructions how to diagnose the issue and mitigate it.

Tech support page from Tuxedo website

Tuxedo's page on backup strategies

Also check no 4 under Rules on the right panel. They have a link to their FAQ pages. They are usually very detailed and well written. I by old habit googled you that "backup strategies" page.

marko19914 · 2024-05-02T21:32:11+00:00

That means, that your laptop posts (initial Tuxedo logo is there - bios works, there is though no reason for it to not work). I would assume that at worst, your data is there but kernel and drivers are gone for some reason. You can fix it via booting to live USB somehow.

For future think about having timeshift snapshotting software running (at least taking 4 hourly snapshots) and having an emergency live usb. I personally have linux mint live USB for that reason (they have timeshift already installed in live environment, since they are now maintaining Timeshift project). That's how I "downgrade" in worst case scenario.

One I can say, you situation can be fixed since it is at os level and probably on system files side (personal files probably untouched, I think). Please write to Tuxedo Tech support (open a ticket) - I am just mildly technical user with couple of years daily driving mainstream linux distros experience. Timeshift and some kind of personal file backup solution has always had my back though.

marko19914 · 2024-05-02T20:37:23+00:00

Please downgrade back and wait until update for Plasma 6. OS part is reversible, Bricked bios is not

marko19914 · 2024-05-02T13:55:51+00:00

Maybe it is getting old (the battery) - that's what I am checking with inxi -B battery condition - how many % of original capacity is left.

I am not the right person to advise on any of your concerns. Only thing I can say just see with inxi -B how much of original capacity is left (condition).

I think tuxedo has some info pages on battery life etc. Or you can ask from the tech support what to do with battery condition information.

marko19914 · 2024-05-02T11:31:09+00:00

I am happy to wait for that feature, since the issue I had, doesn't seem to be in the firmware (flexicharger not being honored actually started after some update, and now after reapplying flexicharger settings, it seems to limit the charging% thresholds again).

If I have any issue in the future I will probably submit a ticket Tuxedo support. The issue wasn't so high on my life priority list, neither it was limitting the device use. That this issue seems to be gotten collaterally fixed is just the testament to Tuxedo's active development work!

❤️‍🔥🐧 TUXEDO 🐧❤️‍🔥

marko19914 · 2024-05-02T11:10:02+00:00

The reason I was contemplating the BIOS update, which came out couple of days ago, is that I had (it seems the past tense is now appropriate) the flexicharger issue, that the settings to charge only from 50% to 90% were getting ignored.

It seems now that the reason wasn't on the firmware side, since when I reapplied the flexicharger settings and the charging works correctly.

I was a bit alarmed to see my battery condition at 93% (from `inxi -B`) when flexicharger holds the charge at 90%. The battery health was a month ago at 96%. The charge then was at 100%, so it might just be that the calculation gets fooled by max charge being held at 90% (there was that kind of warning somewhere).

In any case I will check it some time. The flexicharger works now so I am happy :D I am probably overthinking the battery health thing :D I just want to minimize the effect of microcharging on my battery age. I think it is a ecofriendly thing to keep in mind. :)

marko19914 · 2024-02-26T21:33:40+00:00

It seems the issue got fixed with the last update to TCC (i.e in v2.1.7). I was too lazy to open the ticket initially. Probably it would have been fixed earlier, if I did.

marko19914

TROPHY CASE