Hello TUXEDO Fans and Open-Source Enthusiasts!
Linus Torvalds currently has mixed feelings about AI tools. They are proving useful in kernel development. Even Greg Kroah-Hartman, second-in-command of kernel development, admitted in an interview that he was surprised by how much more useful the tools have become over the past few months. However, that only holds true when they are used responsibly.
Following the release of Linux 7.1-rc4, Torvalds complained that the private kernel bug mailing list is currently being flooded with duplicate bug reports submitted with the help of AI tools. This week, without relying on AI, we take a look on the remote-desktop-application KRDC and provide tips on how to tame stubborn windows on the Plasma desktop.
Enjoy reading,The TUXEDO OS Team
Note: We would like to keep you updated on the latest developments in TUXEDO OS with the TWIX series and introduce you to exciting applications as well as practical tips related to the KDE desktop and TUXEDO OS. However, this section should not be a one-way street: your feedback, ideas, and suggestions for improvement are very welcome! For this purpose, we have created a thread on Reddit, where you can reach us directly.
Security Updates
Chromium 148.0.7778.178
Closes multiple security vulnerabilities
Changelog
KDE App of the Week: Connect local and remote machines with KRDC
As a KDE Plasma user, you can easily remote-control desktops using the VNC client KRDC and the VNC server Krfb — both within a local network and over the internet.
To do so, the computer from which you want to connect to another machine needs the VNC client KRDC installed. On the remote machine, a VNC server is required. On a Linux system running Plasma, Krfb is the natural choice. However, other VNC servers, such as TigerVNC or x11vnc (X11 only) work as well.
KRDC supports both VNC and RDP protocols. RDP is particularly suitable for controlling Windows machines. KRDC transfers the screen Framebuffer (VNC) or graphics and control data (RDP) over the network and renders it locally either in a window or fullscreen.
Hostname, IP Address, and Port in KRDC
For local and remote VNC connections with KRDC, you always require an address or hostname for the target machine: either a hostname or an IP address. Enter this information in the KRDC main window under Connect to… .
The port only needs to be specified if it differs from the default, if multiple VNC instances are running simultaneously, or if you are connecting through port forwarding or an SSH tunnel. In that case, the entry in KRDC could look like 123.45.67.89:5901 (external address with port) or localhost:4500 (when using an SSH tunnel).
After entering the hostname or IP address and selecting the protocol (vnc or rdp), choose the connection type and click OK.
The VNC server Krfb on the remote machine provides both attended and unattended connections.
Attended access: There is no preconfigured password; the local user must approve the connection request.
Unattended access: The displayed password is then used for future connections.
A fixed password for unattended access can be configured using a toggle switch.
When a connection request is initiated in KRDC by clicking OK, a notification appears on the remote machine in attended mode, which must be confirmed by the remote user.
The connection must be confirmed on the remote side.
The password for unattended access does not always replace the confirmation dialog; Krfb distinguishes between connections that require local approval and those that are allowed directly via password authentication without prompting.
Once the connection is approved by the remote side or started through unattended access, the remote desktop opens either in a window or fullscreen, depending on the configuration.
KRDC provides several toolbar buttons for adjusting the display.
Installation
The VNC client KRDC and the server component Krfb are not preinstalled on TUXEDO OS. KRDC can be installed through the Discover software center either as a native package or as a Flatpak, while Krfb is only available as a native package. Both can also be installed via APT from the terminal.
Info: Are you interested in Plasma development and want to know what new features are planned and which programs have been recently updated? You can find a detailed overview in the weekly column This week in Plasma by KDE developer Nate Graham.
TUXEDO OS Tips & Tricks: KDE Plasma: Taming Stubborn Windows
Some programs are quite stubborn when it comes to window placement. No matter where you move the window, the next launch places it back in the wrong spot or even on a different display than intended. In KDE Plasma, this behavior can be fixed once and for all with a built-in tool. No configuration files or terminal commands are required.
The problem
Applications such as DOSBox, GIMP, or LibreOffice sometimes ignore Plasma’s session settings and stubbornly reopen at the same location, regardless of where they were previously placed. Plasma provides an elegant solution for this in the form of Special Window Settings .
Opening the special window settings
First, launch the affected application and move its window to the position where it should appear from now on. Then right-click the window’s title bar and select Configure Special Window Settings… from the context menu.
Under More Actions you will find, among other things, the settings for window behavior.
Defining rules
A dialog with several options will open. First, specify which windows the rule should apply to. You can choose whether the rule only applies to this specific window or to all windows of the application. In most cases, matching by application name is sufficient.
In the Window Rules dialog, the window class can be used to define which application a rule applies to - here with Exact Match for LibreOffice.
Adding the position
In the Size & Position section, you will find the crucial setting. Plasma conveniently inserts the current window coordinates, so there is no need to calculate anything manually. Simply move the window to the correct location before opening the dialog.
If the Position entry is not yet visible, it can be added through Add Property → Position .
Through Add Property , the Position entry can be added under Size & Position . Plasma automatically inserts the current window coordinates.
Choosing the application mode
There are two important modes for positioning:
Apply Initially: The window opens at the defined position but can still be moved freely afterward.Force: The window remains permanently fixed at that position and cannot be moved.
For everyday use, Apply Initially is usually the better choice, since it still allows manual repositioning when needed.
If you still want to move the window later, Apply Initially is the correct choice.
Additional options
The special window settings can do more than simply fix window positions. Among other things, you can configure:
Open windows on a specific virtual desktop or activity
Force windows onto a specific monitor (useful in multi-monitor setups)
Fix the window size (geometry)
Prevent a window from being closed
Prevent focus stealing by mouse or keyboard activity
Under Add Property , many more additional window properties can be configured.
X11 vs. Wayland
Window positioning through special window settings currently works reliably only under X11. Under Wayland, support for session restoration and manual window positioning is still somewhat limited. Users who rely on consistent results should therefore select an X11 session at KDE login.
Conclusion
With its special window settings, KDE Plasma offers one of the most powerful window management systems available in the Linux desktop ecosystem. Tasks that require complex scripts or external tools in other desktop environments can be solved in Plasma with just a few clicks. The combination of session restoration and fixed window positions ensures that the desktop always looks exactly the way you left it after startup.
Ubuntu Security Updates
The Ubuntu security updates listed here are generally incorporated directly into TUXEDO OS. Some updates are only available from Ubuntu for a fee and are therefore not made available to the community until a later date. Unfortunately, we have no control over this:
USN-8204–1: Linux kernel (Raspberry Pi Real-time) vulnerabilities
USN-8203–1: Linux kernel (Oracle) vulnerabilities
USN-8179–3: Linux kernel vulnerabilities
USN-8183–2: Linux kernel vulnerabilities
USN-8202–1: jq vulnerabilities
USN-8198–1: Tornado vulnerabilities
USN-8194–1: league/commonmark vulnerabilities
USN-8191–1: Apache Commons IO vulnerability
USN-8189–1: RapidJSON vulnerability
USN-8185–1: Linux kernel (NVIDIA) vulnerabilities
USN-8277–1: Linux kernel vulnerabilities
USN-8254–3: Linux kernel (NVIDIA Tegra) vulnerabilities
Current BIOS/EC Versions
An EC/BIOS update affects key system components. Please ensure that you follow the instructions carefully and take your time. The process is usually completed quickly. If you have any doubts, our support team is happy to assist you. The following devices have BIOS/EC updates available:
Model
CPU
GPU
BIOS
EC
Stellaris 16 Gen7
Intel
GeForce RTX 5070 Ti
N.1.32A22
2.06.00
Stellaris 16 Gen7
Intel
GeForce RTX 5080
N.1.32A22
2.06.00
Stellaris 16 Gen7
Intel
GeForce RTX 5090
N.1.32A22
2.06.00
Stellaris 16 Gen7
AMD
GeForce RTX 5070 Ti
N.1.40A31
1.50.10
Stellaris 16 Gen7
AMD
GeForce RTX 5080
N.1.40A31
1.50.10
Stellaris 16 Gen7
AMD
GeForce RTX 5090
N.1.40A31
1.50.10
InfinityBook Max 16 Gen10
Intel
Intel Core Ultra 9 275HX/RTX 5060
N.1.32A22
2.06.00
InfinityBook Max 16 Gen10
Intel
Intel Core Ultra 9 275HX/RTX 5060 (OLED)
N.1.32A22
2.06.00
InfinityBook Max 16 Gen10
Intel
Intel Core Ultra 9 275HX/RTX 5070
N.1.32A22
2.06.00
InfinityBook Max 16 Gen10
Intel
Intel Core Ultra 9 275HX/RTX 5070 (OLED)
N.1.32A22
2.06.00
