Hi everyone,

the installation guide recommends to install from http://deb.tuxedocomputers.com/ubuntu/pool/main/t/tuxedo-tomte/, but I wonder if there is any signature we could verify. If there is no signature, please at least change the link to a secure connection.

Cheers,
Klaus

I followed the procedure described here to deactivate tomte but it keeps changing /etc/apt/sources.list with not reponding urls.

https://www.tuxedocomputers.com/en/Infos/Help-Support/Frequently-asked-questions/What-is-TUXEDO-Tomte-.tuxedo

the only thing I could do is :

ps -ef | grep tuxedo and kill the process.

If found a better way missing on doc :

1. fix /etc/apt/sources.list

sudo vi /etc/apt/sources.list

from

#### commented out by TUXEDO Tomte
# deb http://us.archive.ubuntu.com/ubuntu/ focal main restricted universe multiverse

# Added by TUXEDO Tomte
deb https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu focal main restricted universe multiverse

# Added by TUXEDO Tomte
deb https://mirrors.tuxedocomputers.com/ubuntu/mirror/security.ubuntu.com/ubuntu focal-security main restricted universe multiverse

# Added by TUXEDO Tomte
deb https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse

to

deb http://us.archive.ubuntu.com/ubuntu/ focal main restricted universe multiverse

then

sudo systemctl stop tccd
sudo systemctl disable tccd

in my case this command fixed the broken packages

sudo aptitude upgrade --full-resolve

Hi.

The latest update, with tuxedo-tomte, gave me problems on my TUXEDO InfinityBook Pro 14 Gen6 Standard This is causes my screen to flicker, and make my laptop useless.

-tuxedo-tomte 2.5.21 all
+tuxedo-tomte 2.5.25 all

I have located it to here:

The Tuxedo Website, suggests the change that this script is overriding. So I'm a little confused.
https://www.tuxedocomputers.com/en/Infos/Help-Support/Help-for-my-device/TUXEDO-InfinityBook-Series/TUXEDO-InfinityBook-Pro-14/Fix-flickering-display-after-manualy-installing-an-OS.tuxedo

If I set my grub config back, the screen stops flickering, at least as long as there is an external monitor connection. The second I reboot my laptop, the grub setting is set back to what suggestion in the tuxedo-tomte.

I really hope for a fast fix, as this makes my laptop useless.

The apt-package manager only allows me to install the latest version, doesn't find other version available, so hard to do a rollback

$ apt search tuxedo-tomte
Sorting... Done
Full Text Search... Done
tuxedo-tomte/unknown,unknown,now 2.5.25 all [installed]
  little helper that provides services, updates and fixes for TUXEDO devices

Logging this here, but feel free to move if better placed in a different project.

Installed Tuxedo OS 2 (22.04) via webFAI on an InfinityBook Pro 15v5 (based on the Clevo N15xCU).

Post-install, when setting up the touchpad for my needs, none of the tapping settings in System Settings -> Input Devices -> Touchpad were able to be ticked, all greyed out.

Installing the Synaptics touchpad driver (xserver-xorg-input-synaptics) and a reboot fixed that and it's all working now as intended, but this driver should probably be preinstalled via webFAI or tomte for this machine.

On a Notebook TUXEDO InfinityBook S 17 - Gen6 running Ubuntu 20.04 LTS

Since the last kernel update tomte yields the following error message when called e.g.:
tompte list
tomte: error: no packages found matching plasma-workspace
is not a valid version

uname -a
Linux korcslayer-LINUX 5.15.0-10072-tuxedo #79~20.04.1tux1 SMP Fri May 5 15:33:35 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Since 8e084d6 all other kernel versions are automatically removed from the system.

My problem is this: I have some hardware (USB audio device) that the tuxedo default kernel v5.13.0 doesn't support completely. So I installed a self-compiled v5.16.10 which made that device work a lot better. But two days ago, after having been updated, tomte told me not to shut down the system, because it was updating. It never finished however, and after a forced reboot, the system didn't work anymore. Unfortunately it took me quite some time to realize what had happened: tomte had silently removed the kernel image and modules of the running(!) kernel.

So for now, I had to temporarily deactivate it. Is there a way, to prevent tomte from automatically removing more recent (or manually installed) kernel versions?

OS: Ubuntu 20.04 LTS
Kernel: 5.13.0-22-generic

Screen Brightness stopped working after updating the kernel to 5.13 from 5.11.

xrandr --output eDP-1 --brightness 0.8 command works but it gives wired brightness

Attached are the logs when changing the brightness, looks like BIOS BUG and the kernel developer will not fix it

I using KUBUNTU:

in /var/log there is a tomte log file. This logfile contains no useful information.

Sometimes, tomte starts installing and shows me a popup. But in this situations, I don't know what modules were installed.

I would recommend a better, more detailed install log.

Tomte is showing a Gnome Notification:

TUXEDO Tomte is installing fixes
Please do not restart or shutdown the system

The notification cannot be closed. It just stays there forever on top of everything. As it suggests that the laptop should not be restarted or shutdown there is NO way to get rid of that annoying message.
That is really bad UX. Did nobody think about that?
No indication whatsoever what is going on. Should I wait for months or years until that gnome notification disappears? I would really like to fix it by restarting the system, but oops, I shouldn't?

Hello,

I opened #30 to introduce support of Linux Mint 21.3 and would love to get it reviewed and merged so that I can rely on the main tuxedo-tomte package instead of having to keep a fork installed. This would most likely benefit other people too.

Thanks!

Tomte appends the sources.list with

# Added by TUXEDO Tomte
deb https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu jammy main restricted universe multiverse

# Added by TUXEDO Tomte
deb https://mirrors.tuxedocomputers.com/ubuntu/mirror/security.ubuntu.com/ubuntu jammy-security main restricted universe multiverse

# Added by TUXEDO Tomte
deb https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse

on every update. I had 4 entries and this makes apt upgrade package list loading very slow plus it spams

W: Ziel CNF (multiverse/cnf/Commands-all) ist mehrfach konfiguriert in /etc/apt/sources.list:8 und /etc/apt/sources.list:17

[...]

It also adds with and without trailing slash for the URL and trailing spaces:

• deb https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
• deb https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu/ jammy main restricted universe multiverse

Maybe that helps narrow down the problem.

Hello, would it be possible to add support for Ubuntu 23.04?
Just got my InfinityBook Pro 14 Gen 8 and moved my drive from my old laptop!

Hi,

would it be possible to also support Linux Mint?

/etc$ cat os-release
NAME="Linux Mint"
VERSION="21 (Vanessa)"
ID=linuxmint
ID_LIKE="ubuntu debian"
PRETTY_NAME="Linux Mint 21"
VERSION_ID="21"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.linuxmint.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=vanessa
UBUNTU_CODENAME=jammy

You can check UBUNTU_CODENAME to get the regular ubuntu codename.

Thanks,
Christian

Hi, could you please add support to KDE Neon 22.04? It is currently only supporting 20.04.

One workaround for me was to replace KDE Neon string with TUXEDO OS or Ubuntu in the /etc/os-release file, but not very happy to lose the KDE Neon identity in my system, and I am also concerned about consistency. Any thoughts?

Thanks!

I'm considering purchasing a tuxedo laptop and testing non-debian distros on it (fedora, opensuse, nixos, deepin). Is there a chance of this working on them?

I try it on a TUXEDO N650DU (Debian 11) and get the following error message:

~$ sudo tuxedo-tomte list
It seems that this is not a TUXEDO device. Please contact us if this is a mistake

I have a Tuxedo laptop with Ubuntu 20.04. It worked fine until yesterday. Today, after switching it on, I see the small pop-up at the top of the screen which says: "TUXEDO Tomte is installing fixed. Please do not restart or shutdown the system". The pop-up never disappears (and if I click on the cross in its upper right-hand corner, it disappears for a few seconds but then comes back). Also, the fan of the laptop is running at high speed all the time.

After letting the system alone for about 20 minutes with no changes, I shut it and re-started it. The same behaviour appeared again.

Conclusion: the laptop is virtually unusable (owing to the noise of the fan). What should I do?

The screenshot below provides information about the system configuration.

It is possible to add an option for blocking new modules being installed automatically:
$ sudo tuxedo-tomte block --new-modules
$ sudo tuxedo-tomte unblock --new-modules

Also, while installing the tuxedo-tomte, is it possible to prevent everything being installed with something like an environment variable:
$ TOMTE_DONT_INSTALL=1 sudo apt install tuxedo-tomte
or,
$ touch $HOME/.tuxedo_no_automatic_install; sudo apt install tuxedo-tomte
Afterwards tuxedo-tomte may delete the file and block new modules being installed.

These kind of features is needed I think, because there is no option for removing the modules. Some people may like things done automatically in the background but I always become afraid of what modifications will occur in my system. But I also would like to keep updated some modules and let tuxedo-tomte handle it.

Hey Tuxedo team,

I'm currently rocking an awesome Infinitybook 16 Pro, Gen-7 running Pop OS 22.04. I've realized after the installation, and especially now after using it for a couple of weeks, that there might be some drivers missing, which affects the performance in some cases. I discovered after some research that that's what tuxedo-tomte is for. However, it seems that tuxedo-tomte does not support Pop OS at this time.

And as I was thinking of potential workaround I was thinking that both Ubuntu and Pop OS are debian derivatives, which makes it highly unlikely that there will be any software and or driver imcompatibilities (just an assumption). With that in mind, I was wondering if it would be possible to add the following line to the perl script:

`###############################################################################

find OS name and version and put them into $distribution and

$distributionVersion

sub readOSData {
my $osReleaseFile = '/etc/os-release';
my @osReleaseLines;

@osReleaseLines = readFileReturnLines($osReleaseFile);

if (!@osReleaseLines) {
    print "Can't determine the operating system\n";
    exit(0);
}

foreach (@osReleaseLines) {
    if ($_ =~ /^NAME=/) {
        $_ =~ /NAME=\"(.*)\"/;
        $distribution = $1;
        $distribution =~ s/Pop/Ubuntu/g;  # Replace "Pop" with "Ubuntu"                            # NEW LINE
    }
    if ($_ =~ /^VERSION_ID=/) {
        $_ =~ /VERSION_ID=\"(.*)\"/;
        $distributionVersion = $1;
    }
}

$completeDistVersion = $distribution . ' ' . $distributionVersion;

# Check if the distribution is supported
if (!grep { $_ eq $distribution } @supportedDistros) {
    print "Distribution '$distribution' not supported\n";
    exit(0);
}

}`

Which essentially makes it so, that "Pop" distro name will be changed to "Ubuntu" and thus act accordingly. I'm curious on any thoughts and potential risks this approach could come with, as I'm very keen on making use of such a tool. But I'm also very interested in which steps I could do manually or via different types of software, to find and install the correct (Pop OS optimized and verified) drivers that I'm lacking, without having to jeopardise my OS.

after installation of tomte I noticed that installing the tuxedo-repos does not work properly. running sudo apt update refuses to read deb.tuxedocomputers.com with a deprecation warning.

It seems that the script is using apt-key for installing the GPG key which is deprecated, see also https://askubuntu.com/questions/1328806/how-to-solve-apt-key-deprecated

Workaround:

1. delete /etc/apt/trusted.gpg
2. download the public key from tuxedo and put it into the /etc/apt/trusted.gpg.d directory.

wget -O - https://deb.tuxedocomputers.com/0x54840598.pub.asc | sudo tee /etc/apt/trusted.gpg.d/tuxedo-computers.asc

Note: I am unable to find any info how to import the public key by hand on tuxedo's website. I got the download link to the pub key from google cache.

At the moment OS like Linux Mint are not supported.
By running tuxedo-tomte you get the message:
Argument "" isn't numeric in numeric le (<=) at /usr/bin/tuxedo-tomte line 4107. This OS is not supported

For this the ID_LIKE and UBUNTU_CODENAME in /etc/os-release could be used:

At the moment my workaround is setting the versions manually:

I have here a TUXEDO Gemini 17 - Gen2 laptop and some problems related to tomte.

If I open the Tuxedo control center and go to Settings Tomte I just get a error message.

so i checked the service:

> service tuxedo-tomte status
●  tuxedo-tomte.service - Tomte-daemon, finishes tasks that could not be accomplished before
     Loaded: loaded (/lib/systemd/system/tuxedo-tomte.service; static)
     Active: activating (start) since Fri 2023-08-04 09:43:07 CEST; 1min 57s ago
TriggeredBy: ● tuxedo-tomte.timer
   Main PID: 1261 (tuxedo-tomte)
      Tasks: 16 (limit: 76534)
     Memory: 109.6M
        CPU: 1.544s
     CGroup: /system.slice/tuxedo-tomte.service
             ├─1261 /usr/bin/perl -w /usr/bin/tuxedo-tomte configure all
             ├─1794 apt-get update
             ├─1798 /usr/lib/apt/methods/https
             ├─1799 /usr/lib/apt/methods/https
             ├─1800 /usr/lib/apt/methods/https
             ├─1801 /usr/lib/apt/methods/https
             ├─1802 /usr/lib/apt/methods/https
             ├─1803 /usr/lib/apt/methods/https
             ├─1804 /usr/lib/apt/methods/https
             ├─1805 /usr/lib/apt/methods/https
             ├─1806 /usr/lib/apt/methods/https
             ├─1807 /usr/lib/apt/methods/mirror+file
             ├─1808 /usr/lib/apt/methods/https
             ├─1809 /usr/lib/apt/methods/https
             ├─1811 /usr/lib/apt/methods/file
             └─2653 /usr/lib/apt/methods/gpgv

Aug 04 09:43:07 tux-158764 systemd[1]: Starting Tomte-daemon, finishes tasks that could not be accomplished before...
Aug 04 09:43:18 tux-158764 tuxedo-tomte[1261]: no network found!! some fixes might not be applied correctly
Aug 04 09:43:18 tux-158764 tuxedo-tomte[1261]: systemctlCmd: systemd-run --on-active="30sec" tuxedo-tomte configure all >/dev/null 2>&1

when i stop the service (sudo service tuxedo-tomte stop) and start it myself (sudo service tuxedo-tomte start) everything runs fine:

> service tuxedo-tomte status
○ tuxedo-tomte.service - Tomte-daemon, finishes tasks that could not be accomplished before
     Loaded: loaded (/lib/systemd/system/tuxedo-tomte.service; static)
     Active: inactive (dead) since Fri 2023-08-04 09:47:33 CEST; 4s ago
TriggeredBy: ● tuxedo-tomte.timer
    Process: 5164 ExecStart=/usr/bin/tuxedo-tomte configure all (code=exited, status=0/SUCCESS)
   Main PID: 5164 (code=exited, status=0/SUCCESS)
        CPU: 5.951s

Aug 04 09:47:33 tux-158764 tuxedo-tomte[5164]: - tuxedo-repos: Prerequisite! Adds the TUXEDO repositories
Aug 04 09:47:33 tux-158764 tuxedo-tomte[5164]: - tuxedo-mirrors: Adds TUXEDO maintained Ubuntu repositories
Aug 04 09:47:33 tux-158764 tuxedo-tomte[5164]: - cracklib-runtime: Builds password dictionary databases
Aug 04 09:47:33 tux-158764 tuxedo-tomte[5164]: - tuxedo-keyboard: Keyboard & keyboard backlight driver for TUXEDO notebooks
Aug 04 09:47:33 tux-158764 tuxedo-tomte[5164]: - linux-tuxedo-22.04: Required kernel version linux-tuxedo-22.04
Aug 04 09:47:33 tux-158764 tuxedo-tomte[5164]: - tuxedo-dgpu-run: commandline tool and KDE context menu entries to run programms on dGPU while>
Aug 04 09:47:33 tux-158764 tuxedo-tomte[5164]: Nothing to do in post configuration
Aug 04 09:47:33 tux-158764 systemd[1]: tuxedo-tomte.service: Deactivated successfully.
Aug 04 09:47:33 tux-158764 systemd[1]: Finished Tomte-daemon, finishes tasks that could not be accomplished before.
Aug 04 09:47:33 tux-158764 systemd[1]: tuxedo-tomte.service: Consumed 5.951s CPU time.

Finished in a few seconds.
While the first auto started one was stuck with "no network found"? My Wi-Fi network was probably not up so early.

Now i can access Tomte via the control center (until the next system restart).

Edit: forgot to mention I am using Tuxedo OS (up to date) tuxedo-tomte 2.11.0
Edit2: Added image of the error messages, system at that point already running with a working internet connection for more than 10 Minutes. Manually restarting the service resolved the issue, until i shutdown my Laptop and start it again.

Edit3 Today, 3 days later, I discovered that even KDE discover (what a Pun) throws an error while that tomte service is stuck:
E: Sperre /var/lib/apt/lists/lock konnte nicht erlangt werden. Sie wird von Prozess 1870 (apt-get) gehalten.
W: Beachten Sie, dass das Entfernen der Sperrdatei keine Lösung ist und Ihr System beschädigen kann.
E: Das Verzeichnis /var/lib/apt/lists/ kann nicht gesperrt werden.
And the system can probably not even search for Updates that way(?).
That is really bad.