hannah-eee/arch-wiki-docs huggingface dataset:
Telnet

Related articles
Secure Shell
From
Wikipedia
:
Telnet (short for "teletype network") is a client/server application protocol that provides access to virtual terminals of remote systems on local area networks or the Internet.
Today, telnet is rarely used due to security concerns and is often only used for legacy software and hardware, for information on how to mitigate the security issues see
#Security concerns
.
Installation
Install
the
inetutils
package which includes a telnet client, a telnet server with
systemd
service and sockets.
To configure a telnet server with xinetd,
install
xinetd
AUR
as well.
Configuration
To enable telnet server connections in systemd,
enable
telnet.socket
(if the telnet server should be started on every boot), and
start
telnet.socket
to test connectivity.
To enable telnet server connections in xinetd, edit
/etc/xinetd.d/telnet
, change
disable = yes
to
disable = no
and restart the xinetd service.
Enable
systemd xinetd service if you wish to start it at boot time.
Testing the setup
Try opening a telnet connection to your server:
$ telnet localhost
Try a root login to see if your configuration permits it and the security implications that implies.
Tip
If you receive junk codes from a remote telnet server sending non-ascii chars with a non-unicode encoding, you might want to try
luit
to solve this problem.
Tips and tricks
Security concerns
Telnet is a plain text protocol which does not support
TLS encryption
. Data can be easily intercepted and modified therefore should not be used on production servers, or to transmit sensitive data.
There are attempts to mitigate said security concerns, see
#Netkit
and
#Tunneling
for mitigations.
Netkit
You can use
netkit-telnet-ssl
AUR
which modifies the protocol to support
TLS encryption
.
Tunneling
You can use a
VPN
or
SSH
to create an encrypted tunnel for the telnet traffic between two devices, or networks.
Note
The telnet traffic will only be encrypted while it is within the encrypted tunnel, ensure the network or device it is tunneled to is secure.
Teltonika RUTxxx

Teltonika Modems enable internet connection using GSM, 3G or LTE networks. They run
OpenWrt
based, feature rich, open source firmware.
Command Line Interface (CLI)
Modem can be accessed via command line interface (
CLI
)
Communicate with the modem via gsmctl
From
CLI
communication with the modem is possible with
gsmctl
. The programm can be used to gather network information.
$ gsmctl -h
To see options.
Tip
gsmctl also enables sending Hayes AT commands to the modem.
SMS
SMS can be sent with
gsmctl
Tip
As mobile data often is limited, to monitor data usage
VnStat
is a good option.
See also
There is a very good
wiki
by Teltonika.
The manufacturer provides a
sofware development kit
Modems can be configured to be controlled with SMS
Configuration is possible with
UCI commands
Terminator

Terminator
is a
terminal emulator
which supports tabs and multiple resizable terminal panels in one window. It is based on
GNOME Terminal
.
Installation
Install
the
terminator
package.
Configuration
See
terminator_config(5)
or right click Terminator then click
Preferences
.
User-specific configurations can be found in
~/.config/terminator/config
.
GTK customization
Terminator supports tabs. If their size is considered too big, GTK styling can be used in
~/.config/gtk-3.0/gtk.css
on 'notebook tab' and 'notebook tab button' to achieve the desired height and/or width.
Note
This affects all GTK applications.
Key commands
F11
Toggle fullscreen
Ctrl+Shift+o
Split terminals h
o
rizontally
Ctrl+Shift+e
Split terminals v
e
rtically
Ctrl+Shift+w
Close current Panel
Ctrl+Shift+t
Open new tab
Alt+Up
Move to the terminal above the current one
Alt+Down
Move to the terminal below the current one
Alt+Left
Move to the terminal left of the current one
Alt+Right
Move to the terminal right of the current one
Managing profiles
It is possible to start terminator with a random profile every time. To avoid unexpected behavior, you should start with a clean
[profiles]
section. You can copy the one from
this file
. It contains many well-known color schemes. Copy its contents to your
config
file, which is located in
~/.config/terminator/
. Then,
sed
your list of profiles to a destination of your choice.
$ sed -n -e '/background_color/{x;1!s/.*\[\[\(.*\)\]\]/\1/p;g;D;}' -e h $HOME/.config/terminator/config > $HOME/.config/terminator/profiles
When you add more profiles in the future and would like to have them included in the startup pool, you will have to reissue the command above. You can create an
alias
.
You must now modify Terminator's desktop file so that it selects a random profile from this list at startup.
$ cp /usr/share/applications/terminator.desktop ~/.local/share/applications
Find the
Exec
line and comment it out with
#
. Add your own
Exec
line as follows.
~/.local/share/applications/terminator.desktop
# Exec=terminator
Exec=sh -c "terminator -p $( shuf -n 1 $HOME/.config/terminator/profiles )"
Save the file and restart your
desktop environment
.
Tip
Go to the terminator preferences and under the "keybindings" tab, take note of how to switch to the next profile. This way, if the profile Terminator has not started with your liking, you can quickly change it.
See also
Terminator
- Official site
https://github.com/gnome-terminator/terminator
- GitHub
TerraTec Aureon 7.1

The Terratec Aureon 7.1 USB is an affordable external sound card which supports optical and digital output through S/PDIF with full 5.1/7.1 surround sound.
Installation
ALSA
drivers are part of the kernel and have support for this sound card.
Configuration
Set the card as the default device
If you have multiple sound cards, you need to set the Terratec card as a default. Create the following file:
/etc/modprobe.d/alsa.conf
options snd slots=snd_usb_audio
Rebooting may be required for the changes to take effect.
Enable volume control
This card does not have hardware volume control, so you need to create software Master control.
Create the following file in your home folder:
.asoundrc
pcm.softvol {
        type softvol
        slave {
                pcm "dmix"
        }
        control {
                name "Master"
                card 0
        }
}

pcm.!default {
        type plug
        slave.pcm "softvol"
}
Run
alsamixer
and check as you should have a
Master volume
control.
Hotkeys
The sound card has external hotkeys for volume change and mute. You can capture the button presses by installing
Xbindkeys
and using the following config:
.xbindkeysrc
#Volume up
"amixer set 'Master' 5+"
    m:0x0 + c:123
    XF86AudioRaiseVolume

#Volume down
"amixer set 'Master' 5-"
    m:0x0 + c:122
    XF86AudioLowerVolume

#Mute
"/media/disk/programs/mute.sh"
    m:0x0 + c:121
    XF86AudioMute
As you can see,
alsamixer(1)
does not handle mute for this mixer, which is why you can use a simple
mute.sh
script, which stores the volume level in
volume.txt
. Be sure to change the file path to
mute.sh
accordingly.
#!/bin/bash
var=$(amixer get Master | grep "Front Left:")
var=$(echo "$var" | sed -ne 's/^[^[]*\[\([^]]*\)\].*/\1/p')
if [ $var == "0%" ]
then
        volume=$(cat volume.txt)
        amixer set 'Master' $volume
else
        rm volume.txt
        echo $var > volume.txt
        amixer set 'Master' 0%
fi
Configure mplayer for surround sound (optional)
Add the following codec settings for
mplayer
:
.mplayer/config
ac=hwac3,hwdts,a52,dts,
ao=alsa
Kodi
can be used for media playback too, as most receivers do no support the AAC codec.
Kodi
will re-encode AAC to a common codec (AC3 probably) in realtime, so you can watch most surround sound media files. It also has a self-explanatory configuration system using a GUI.
TerraTec Cinergy T RC MKII USB Stick

TerraTec Cinergy T RC MKII
is a USB DVB-T receiver manufactured by TerraTec Electronic GmbH. This page describes the installation of the TerraTec Cinergy T RC MKII USB Stick.
Verify device ID
Make sure you have the 'correct' device. The USB ID is
0ccd:0097
:
$ lsusb
Bus 001 Device 004: ID 0ccd:0097 TerraTec Electronic GmbH Cinergy T RC MKII
Installation
If you plug-in the device you will see the following kernel message:
# dmesg
[ 4403.369654] usb 1-1: new high-speed USB device number 5 using ehci_hcd
[ 4403.862797] dvb-usb: found a 'TerraTec Cinergy T Stick RC' in cold state, will try to load a firmware
[ 4403.864076] dvb-usb: did not find the firmware file. (dvb-usb-af9015.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. (-2)
[ 4403.864103] dvb_usb_af9015: probe of 1-1:1.0 failed with error -2
You need to
install
the firmware—
af9015-firmware
AUR
.
Reconnect the device and you should see the following output. The device is now ready to use :)
# dmesg
[ 4867.138959] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected.
[ 4870.056313] usb 1-1: new high-speed USB device number 6 using ehci_hcd
[ 4870.549447] dvb-usb: found a 'TerraTec Cinergy T Stick RC' in cold state, will try to load a firmware
[ 4870.551676] dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw'
[ 4870.618834] dvb-usb: found a 'TerraTec Cinergy T Stick RC' in warm state.
[ 4870.618971] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 4870.619381] DVB: registering new adapter (TerraTec Cinergy T Stick RC)
[ 4870.622186] af9013: firmware version:4.95.0.0
[ 4870.627936] DVB: registering adapter 0 frontend 0 (Afatech AF9013 DVB-T)...
[ 4870.630198] tda18218: NXP TDA18218HN successfully identified.
[ 4870.631940] Registered IR keymap rc-terratec-slim-2
[ 4870.632197] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.7/usb1/1-1/rc/rc2/input11
[ 4870.632437] rc2: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.7/usb1/1-1/rc/rc2
[ 4870.632446] dvb-usb: schedule remote query interval to 500 msecs.
[ 4870.632454] dvb-usb: TerraTec Cinergy T Stick RC successfully initialized and connected.
See also
TerraTec Cinergy T RC MKII at Linux TV
TerraTec T6 DVB-T (Afatech AF9035)

The TerraTec T6 is a dual
DVB-T
USB-device. The device is supported by the kernel, but requires additional proprietary firmware to be loaded to function.
This tutorial was tested for a Terratec T6 with the
Afatech AF9035
chipset.
Identify chipset
Filter
dmesg
to find out the exact chipset with the following command:
# dmesg | grep dvb
usb 3-1: dvb_usb_af9035: prechip_version_00 chip_version_03 chip_type_3802 
usb 3-1: dvb_usb_af9035: prechip_version=00 chip_version=03 chip_type=3802 
usb 3-1: dvb_usb_v2: found a 'Afatech AF9035 reference design' in
cold state
The
cold state
indicates it is not active, due to the missing firmware file.
Install firmware
The firmware was made available at
dvb-usb-af9035-fw
AUR
After installing the package and re-plugging the device,
dmesg
should show the firmware loaded and the device is now in
warm state
:
# dmesg | grep -e dvb -e af9033
usb 3-1: dvb_usb_af9035: prechip_version=00 chip_version=03 chip_type=3802
usb 3-1: dvb_usb_v2: found a 'Afatech AF9035 reference design' in cold state
usb 3-1: dvb_usb_v2: downloading firmware from file 'dvb-usb-af9035-02.fw'
usb 3-1: dvb_usb_af9035: firmware version=12.13.15.0
usb 3-1: dvb_usb_v2: found a 'Afatech AF9035 reference design' in
warm state
usb 3-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
DVB: registering new adapter (Afatech AF9035 reference design)
calling  af9033_driver_init+0x0/0x1000 [af9033] @ 5364
initcall af9033_driver_init+0x0/0x1000 [af9033] returned 0 after 47 usecs
af9033 7-0038:
firmware version: LINK 12.13.15.0 - OFDM 6.20.15.0
af9033 7-0038: Afatech AF9033 successfully attached
usb 3-1: DVB: registering adapter 0 frontend 0 (Afatech AF9033 (DVB-T))...
TeXstudio

TeXstudio
is a free
LaTeX
editor
. It offers multiple features to easily input special characters, edit tables, preview math mode snippets and language checking.
Installation
Install
the
texstudio
package.
Language checking
If you want to enable the language checking functions, install
hunspell
and at least
one of the corresponding dictionaries
. The selection of languages available in TeXstudio will match the hunspell dictionaries installed. If no dictionaries are installed, it is impossible to select a language in the application.
You can also install
languagetool
for a more advanced language check, or connect to a remote
LanguageTool
server. In any case, you need to install the hunspell dictionary for your desired language, otherwise TeXstudio will not let you select it, even if your LanguageTool installation or server supports it.
Textadept

Textadept
describes itself as "a fast, minimalist, and remarkably extensible cross-platform text editor".
With a very lightweight code base written in C, it relies on Lua for its extensibility. The editor works both in a graphical (GTK) and in a CLI environment (Curses).
Installation
Install
the
textadept
AUR
package. It features 2 executables:
textadept
textadept-curses
The
curses
version runs in a CLI environment.
Configuration
On first start, Textadept will create a
~/.textadept
folder. You can edit
~/.textadept/init.lua
to start customizing the editor. From there you can define new functions, key bindings, themes, and even modules, as explained in the
manual
and the
API
.
Textadept sample configuration
Modules
By default, Textadept features modules for its core only, that is ANSI C, Lua and itself, however the AUR package also embeds some of the
official modules
.
More contributed modules and functions are listed in the
wiki
.
A convenient way to install modules is by cloning the repository in
~/.textadept/modules
. For instance you can fetch
textadept-vi
from there:
$ cd ~/.textadept/modules
$ git clone
https://github.com/jugglerchris/textadept-vi.git
You can easily keep up to date all your modules with version control tools.
See also
Manual
Default key bindings
API
Wiki
TFTP

The
Trivial File Transfer Protocol
(TFTP) provides a minimalistic means for transferring files. It is generally used as a part of
PXE
booting or for updating configuration and firmware on devices which have limited memory such as routers, IP phones and printers.
Server
There are several TFTP server implementations, some of which are listed below.
Note
Make sure not to start different TFTP implementations at the same time. They will  fail with an error
got more than one socket
, because only one may listen to the default TFTP port
69
.
tftp-hpa
Install
tftp-hpa
and then
start
tftpd.service
.
To modify service parameters edit
/etc/conf.d/tftpd
.
URL rewriting
This server includes a useful URL rewriting feature via the
--map-file
option (
--mapfile
in some versions). It allows requests to be altered via regular expressions so the files on the server do not have to match the view the client sees, and different files can be returned to different clients even if they request the same file.
Configure a map by adding
--map-file /etc/tftpd.map
to
/etc/conf.d/tftpd
and creating a file such as this:
/etc/tftpd.map
# Add the remote IP address as a folder on the front of all requests.
r ^ \i/
This example file will result in each TFTP request being prefixed with the remote IP address. For example if the machine at 192.168.0.1 requests "boot.bin" and the TFTP server root is
/srv/tftp
then the file
/srv/tftp/192.168.0.1/boot.bin
will be returned (or
/srv/tftp/::ffff:192.168.0.1/boot.bin
if the server is listening on an IPv6 port).
The available map file options are documented in
in.tftpd(8) § FILENAME REMAPPING
.
Debugging
The
--verbosity 5
option can be used to turn on all debugging messages.  This is very useful for diagnosing why a machine will not successfully boot from the network, as the debug messages list all requests for files, whether rewrite rules were used, where the files were read from on the filesystem and whether the request was successful or not.
It is not possible to log messages to stdout/stderr, as only syslog is supported.  This means the messages can be viewed with
journalctl
or similar.
atftp
Install
atftp
and then
start
atftpd.service
.
To modify service parameters edit
/etc/conf.d/atftpd
.
uftpd
uftpd
AUR
is a
simple
(T)FTP server that can be run from the command line:
# uftpd -n -o ftp=0,tftp=69 /tmp/tftp
The option
-o ftp=0
disables the FTP server and only runs TFTP. The server runs in read-only mode by default and passing
-o writable
allows clients to put files on the server. The
-o tftp=69
is redundant in the case of default port, but shows a way to select a different one.
dnsmasq
Note
dnsmasq does not support file uploads.
See
dnsmasq#TFTP server
.
Client
tftp-hpa
Install
tftp-hpa
and then tftp your day away!
$ tftp
atftp
The package
atftp
contains both a server and a client with interactive and batch mode. The client binary is
atftp
and supports both getting and putting files.
curl
Standard
curl
has an ability to connect to a TFTP server and upload a file via:
$ curl -T FILE tftp://HOST
Download a file:
$ curl -o DESTINATION tftp://HOST/file
Where
file
is relative to the TFTP root directory.
TICK stack

Related articles
Prometheus
Grafana
The TICK stack is a collection of associated technologies that consists of
T
elegraf,
I
nfluxDB,
C
hronograf and
K
apacitor. They combine to deliver a platform for storing, capturing, monitoring and visualizing data that is in time series.
The TICK stack consists of the following technologies:
#Telegraf
– collection of time sequential data from a range of sources including IoT devices.
#InfluxDB
– high performance and efficient database store for handling high volumes of time-series data.
#Chronograf
– real-time visualization of InfluxDB data.
#Kapacitor
– monitoring and alerting based on views of InfluxDB data and anomalies contained within those views.
Note
These components do not have to be used altogether. Also they can be replaced with other preferred tools (e.g.
Grafana
instead of Chronograf) or not used at all (e.g. Kapacitor).
Telegraf
Installation
Install
the
telegraf
AUR
or the
telegraf-bin
AUR
package.
Configuration
Main configuration file is stored at
/etc/telegraf/telegraf.conf
. For available plugins, configuration and customization, see
upstream documentation
.
Also
start/enable
telegraf.service
.
InfluxDB
Installation
Install
the
influxdb
package.
Configuration
For configuration, see
upstream documentation
.
Also
start/enable
influxdb.service
.
Chronograf
Installation
Install the
chronograf-bin
AUR
package.
Configuration
Main configuration file is stored at
/etc/chronograf/chronograf.conf
. For configuration, see
upstream documentation
.
Also
start/enable
chronograf.service
.
Kapacitor
Installation
Install the
kapacitor
AUR
or the
kapacitor-bin
AUR
package.
Configuration
Main configuration file is stored at
/etc/kapacitor/kapacitor.conf
. For configuration, see
upstream documentation
. Many examples can also be found in
official github repository
.
Also
start/enable
kapacitor.service
.
See also
Flux
InfluxDB 2.*
tmuxp

Related articles
tmux
tmuxp
is a session manager for the
tmux
terminal multiplexer. Compare to
tmuxinator
or
teamocil
.
Installation
Install the
tmuxp
package.
Configurations
tmuxp
accepts both JSON and YAML configurations. The YAML markup is similar to
tmuxinator'
s.
You can put configurations in any directory to access them via 3 ways:
Via absolute or relative file path
tmuxp load
file
,
tmuxp load ../
myconfig
tmuxp checks for files in
$XDG_CONFIG_HOME/tmuxp
(usually
$HOME/.config/tmuxp
), and
$TMUXP_CONFIGDIR
path (default
$HOME/.tmuxp
). Files inside can be loaded via filename, e.g.
tmuxp load
basename
. So
$HOME/.tmuxp/
myconfig
.yaml
would be loadable via
tmuxp load myconfig
.
Via
.tmuxp.yaml
in a project or directory (so you can store configs in a VCS per-project / folder. And then
tmuxp load
path/to/dir
A sample YAML configuration with 4 panes:
session_name: 4-pane-split
windows:
- window_name: dev window
  layout: tiled
  shell_command_before:
    - cd ~/                    # run as a first command in all panes
  panes:
    - shell_command:           # pane no. 1
        - cd /var/log          # run multiple commands in this pane
        - ls -al | grep \.log
    - echo second pane         # pane no. 2
    - echo third pane          # pane no. 3
    - echo forth pane          # pane no. 4
tmuxp
is also capable of running arbitrary scripts before building
tmux
sessions via
before_script
. In this example,
from the tmuxp project itself
, a
bootstrap script
runs which creates a
virtualenv
(python package environment) for the project and installs dependency packages. In addition, the session configures all panes to source the project's
virtualenv
:
session_name: tmuxp
start_directory: ./ # load session relative to config location (project root).
before_script: ./bootstrap_env.py # ./ to load relative to project root.
windows:
- window_name: tmuxp
  focus: True
  layout: main-horizontal
  options:
    main-pane-height: 35
  shell_command_before:
    - '[ -d .venv -a -f .venv/bin/activate ] && source .venv/bin/activate'
  panes:
  - focus: true
  - pane 
  - make watch_test
- window_name: docs
  layout: main-horizontal
  options:
    main-pane-height: 35
  start_directory: doc/
  shell_command_before: 
    - '[ -d ../.venv -a -f ../.venv/bin/activate ] && source ../.venv/bin/activate'
  panes:
  - focus: true
  - pane
  - make serve
  - make watch
More examples
are available in the documentation showcasing YAML, as well as JSON configurations.
See also
Official Homepage
, including documentation and examples
GitHub
PyPI package
Tomb

Related articles
Data-at-rest encryption
dm-crypt
TrueCrypt
Tcplay
From
the official website
:
Tomb is 100% free and open source software to make strong encryption easy to use.
A tomb is like a locked folder that can be safely transported and hidden in a filesystem.
Keys can be kept separate: for instance the tomb on your computer and the key on a USB stick.
Tomb aims to be a really simple to use software to manage "encrypted directories", called tombs. A tomb can only be opened if you both have a keyfile and you know the password.
Installation
Install
tomb
AUR
or
tomb-git
AUR
.
Usage
Tomb is meant to be used from the console as a single, non-interactive script. it also provides
tomb-open
, which is a simple interactive script to help you create a tomb, open it, retrieve keys from USB.
Tombs are operated from a terminal command line and require root access to the machine (or just
sudo
access to the script).
To create a 100 MiB tomb called "secret" do:
# tomb dig -s 100 secret.tomb
# tomb forge secret.tomb.key
# tomb lock secret.tomb -k secret.tomb.key
To open it, do:
# tomb open secret.tomb -k secret.tomb.key
And after you are done:
# tomb close
For more information see
tomb -h
and
man tomb
.
This article or section needs expansion.
Reason:
Tomb added support for
FIDO2 passkeys
[1]
[2]
(Discuss in
Talk:Tomb
)
Advanced features
The
advanced features
are:
steganography
to hide the key inside a jpeg/wav file.
This feature can be used on its own using
steghide
AUR
.
If an attacker assumes you are using this feature (i.e.,
searching
for
steghide
AUR
) they can scan your system using
stegseek
AUR
.
bind hooks: can automatically apply a
mount
to a subdirectory inside a tomb with the
--bind
operation to one outside. Suppose, for example, you would like to encrypt your
Documents
directory. Then you can create a tomb which contains it (and others too, if you want) and create a simple configuration file inside the tomb itself. When you run
tomb open
it will automatically bind the directories into the right places. This way you will easily get an encrypted documents folder, browser profile, or maildir.
post hooks: commands that are run when the tomb is opened, or closed. You can imagine lot of things for this: open files inside the tomb, put your computer in a "paranoid" status (for example, disabling swap), etc.
See also
manpage (available as pdf also)
home page
quickstart
Toolbox

Related articles
Linux Containers
Podman
Buildah
Distrobox
Toolbox is a tool that allows you to create and run containers that seamlessly integrate with the rest of the operating system by providing access to the user's home directory, the Wayland and X11 sockets, networking (including Avahi), removable devices (like USB sticks), systemd journal, SSH agent, D-Bus, ulimits, /dev and the udev database, etc.
Installation
Install
the
toolbox
package.
Note that
podman
is installed as a dependency of Toolbox. By default it is only possible to run Podman containers as root. See
Podman#Rootless Podman
to set up running containers as a non-root user. In general, if you are having issues with Toolbox, make sure your issues are not with Podman first.
If you want to build your own toolbox-compatible images, install
buildah
as well.
Fedora Containers
You can create a Fedora 35 toolbox with the following:
$ toolbox create -d fedora -r 35
Once that's done, you can enter the toolbox with:
$ toolbox enter fedora-toolbox-35
Arch Containers
You can create an Arch Linux toolbox with the following:
$ toolbox create
This will create a container named
arch-linux-latest
.
Once that's done, you should be able to enter the toolbox with:
$ toolbox enter
Troubleshooting
Error: failed to start container (rootless containers)
You may not be able to enter rootless containers if
virtualbox
is installed due to strict permissions in
/dev/vboxusb
and toolbox trying to stat vboxusb.
To fix this, change
/dev/vboxusb
permissions from 750 to 755:
# chmod -R 755 /dev/vboxusb
X11 applications not starting
When attempting to run an X11 application from within the toolbox, you may get the following error:
Authorization required, but no authorization protocol specified
Error: Can't open display: :0
To fix this, you can use
xorg-xauth
(on your host machine) to give your container permission to communicate with X11. Run the following, or add it to
Xinit#xinitrc
:
$ xauth add "toolbox/unix$DISPLAY" . "$(xauth list | grep "^$(hostnamectl hostname)/unix$DISPLAY\s*MIT-MAGIC-COOKIE-1\s*" | awk '{print $3}')"
Alternatively, run:
$ xauth nlist | sed -e 's/^..../ffff/' | xauth nmerge -
See also
Official website
Github repo
Fedora Silverblue documentation
toolbx-images
- Community maintained container images to use with Toolbox, with pre-built images available via quay.io
duhdugg's custom toolboxes
- a set of custom scripts to build toolbox containers using a directory structure that makes them simple to modify
Toshiba Portege Z30-A

This article or section does not follow the
Laptop page guidelines
.
Reason:
Needs an accessibility and a function keys section (Discuss in
Talk:Toshiba Portege Z30-A
)
Hardware
PCI/USB ID
Working?
GPU
8086:0a16
Yes
Audio
8086:9c20
Yes
Wi-Fi
8086:08b1
Yes
8086:08b3
Ethernet
8086:155a
Yes
8086:1559
Card reader
10ec:5227
Untested
Bluetooth
8087:07dc
Yes
Webcam
04f2:b3b2
Untested
Smartcart reader
0b97:7772
Yes
Fingerprint sensor
138a:0010
Yes
High-performance ultrabook laptop of Toshiba made for professionals and business. Portégé Z30-A has a long-lasting battery, full-size ports in a laptop of 13.3" and 1.2Kg.
Bluetooth
The
toshiba_bluetooth
kernel module is auto-loaded but is not necessary and, in fact, is counter-productive since as soon as you disable Bluetooth (e.g. with
rfkill
), it seems to attempt to re-load the Intel Bluetooth firmware every few seconds. Just blacklist the module, to make it permanent
create
:
/etc/modprobe.d/toshiba-blacklist.conf
blacklist toshiba_bluetooth
Wi-Fi
linux-firmware
is needed for the correct working of Wi-Fi, see
Network configuration/Wireless
.
Smartcard reader
Works perfectly with
ccid
&
opensc
, see
Smartcards
.
Display backlight control
See
Backlight
.
Keyboard backlight control
The backlight works correctly if it is configured on BIOS.
toshiba_acpi
kernel module add support for configuring the backlit of the keyboard. However,
Fn+Z
does not work. The modules can be changed in
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS6208:00/kbd_backlight_mode
with the modes: 2,8,16.
# echo 2 > /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS6208:00/kbd_backlight_mode
Fingerprint reader
Fprint
has support for it. However, the image usually is wrong (lengthened) and needs two, three or more tries to obtain verifications.
See also
Microcode
- for the CPU
Intel
- For the GPU
Touchegg

Touchegg
is a multitouch gesture program that runs as a user in the background,
recognizes gestures, translates them to more conventional types of events and/or performs custom actions in response to them.
Touchegg is not compatible with Wayland.
Installation
Install
the
touchegg
package. Install
touche
AUR
if you want a desktop application to configure touchegg.
For X11 GNOME, one can also install the extension
X11 Gestures
in addition to touchegg.
Configuration
The default configuration can be found in
/usr/share/touchegg/touchegg.conf
.
To customize it, copy the default configuration to
~/.config/touchegg/touchegg.conf
and make your changes.
It is a basic XML file that defines various gestures. Please note that at this time,
TAP_AND_HOLD
,
PINCH
, and
ROTATE
do not appear to work.
See the
list of triggers
and the
list of actions
.
The two-fingers scrolling emulation
has been dropped
, due to bad user experience, in the recent 2.0 rewrite of touchegg.
To restore it, install
xdotool
and add the following to the configuration file:
<gesture type="SWIPE" fingers="2" direction="DOWN">
      <action type="RUN_COMMAND">
        <repeat>true</repeat>
        <command>xdotool click 4</command>
        <decreaseCommand>xdotool click 5</decreaseCommand>
      </action>
    </gesture>
    <gesture type="SWIPE" fingers="2" direction="UP">
      <action type="RUN_COMMAND">
        <repeat>true</repeat>
        <command>xdotool click 5</command>
        <decreaseCommand>xdotool click 4</decreaseCommand>
      </action>
    </gesture>
Note that on KDE, text gets selected while scrolling (see upstream
issue 401
).
Start on login
Enable
touchegg.service
, the client can then be
autostarted
.
Tox

From the project
home page
: "Tox is a distributed, secure messenger with audio and video chat capabilities."
Installation
In order to use Tox, you should
install
a
Tox client
. See
List of applications/Internet#Tox clients
.
Proxy
To connect via
Tor
, first start it with:
[tor]$ /usr/bin/tor
Then configure your Tox client. For example:
$ toxic -t -p 127.0.0.1 9050
Run a node
To be able to connect to others, Tox needs to connect to a
DHT node
first. All DHT nodes are connected to each other, and since everyone is connected to at least one DHT node, you can connect to others one way or the other.
The package
toxcore
creates user
tox-bootstrapd
and includes
tox-bootstrapd.service
and a configuration file in
/etc/tox-bootstrapd.conf
.
Edit the configuration file and add appropriate nodes from
Tox wiki
or
Node status page
.
Enable
and start
tox-bootstrapd.service
and check if it is running fine and port has been bound:
# ss --listening --numeric --processes | grep
node_port
udp        0      0 *:
node_port
*:*                                 576/DHT_bootstrap
Tp-battery-mode

This article or section is a candidate for merging with
tp_smapi
.
Notes:
Duplicates
tp_smapi
, and the script itself arguably offers little over following the instructions in that article. Perhaps it is best to redirect this to
tp_smapi
. (Discuss in
Talk:Tp-battery-mode
)
tp-battery-mode is a module to easily switch your Thinkpad's battery charging mode to prolong battery lifetime using
tpacpi-bat
AUR
.
Installation
Install the
tp-battery-mode
AUR
package.
Features
Your Thinkpad's default behavior is to start charging its battery as soon as it drops below 100% capacity and stop charging once it is at 100% capacity. Switching your battery charging mode changes these start & stop threshold. tp-battery-mode's default values can be found in
/etc/tp-battery-mode.conf
START_THRESHOLD=85
STOP_THRESHOLD=90
These values mean that your battery will start charging once the capacity drops below 85% and stop charging once it has reached 90% capacity. This should prolong your battery's lifespan while still giving you ample charge for portable needs.
Prolong Battery Lifetime
Switching to these new charging thresholds is as simple as
enabling
and
starting
tp-battery-mode.service
You can tailor the start/stop thresholds to fit your needs by modifying
/etc/tp-battery-mode.conf
. If you modify these values, you will need to restart the tp-battery-mode service otherwise the changes will not be reflected until you reboot.
Note
tp-battery-mode supports the T440's dual batteries however their charging thresholds cannot be changed independently.
Reverting to default charging behavior
Sometimes you might want to charge your battery all the way to 100% If you wish to revert to the default Thinkpad charging behavior, you just need to
stop
tp-battery-mode.service
If you wish to revert to the default Thinkpad charging behavior completely, you will also need to
disable
tp-battery-mode.service
Trac

From the
project web page
:
Trac is an enhanced wiki and issue tracking system for software development projects. Trac uses a minimalistic approach to web-based software project management. Our mission is to help developers write great software while staying out of the way. Trac should impose as little as possible on a team's established development process and policies.
Installation
Install
the
trac
AUR
package. Configuration is done on a per-environment basis. See below on how to create an environment. Detailed instructions can be found at
https://trac.edgewall.org/wiki/TracGuide
.
Configuration
Create and initialize an environment
Initialize an environment
# cd /srv/
# mkdir tracenv
# trac-admin /srv/tracenv initenv
The environment configuration can be found at
/srv/tracenv/conf/trac.ini
.
Configure the systemd unit
Edit
tracd.service
using a
drop-in file
point to your new environment. The
ExecStart
entry should look something like this:
ExecStart=/usr/bin/tracd -b localhost -p 8080 /srv/tracenv
Webinterface
Start/enable
the service and you can view the web interface at
http://localhost:8080
using a web browser.
Trac user
It is a good idea to create a dedicated
user
for the trac service. Once that user is created, you can create the environment using that user:
# cd /srv/
# mkdir tracenv
# chown trac:trac tracenv
[trac]$ trac-admin /srv/tracenv initenv
Extend the unit
file to make sure it is started as the
trac
user:
[Service]
User=trac
Group=trac
Users and permissions within trac
(This section refers to creating users within the trac environment rather than GNU/Linux users.)
Next, you will want to add users and give permissions to those users. To add users, see
https://trac.edgewall.org/wiki/TracStandalone#UsingAuthentication
(you will have to change your
.service
file to refer to the authentication mechanism you choose). To grant permissions to users, run the following on the trac server:
# trac-admin /srv/tracenv permission add <username> TRAC_ADMIN
Trickle

trickle
is a portable lightweight userspace bandwidth shaper, that either runs in collaborative mode (together with trickled) or in stand alone mode.
It works by preloading its own socket library wrappers, that limit traffic by delaying data.
Trickle runs entirely in userspace.
[1]
Installation
Install
the
trickle
AUR
package.
Usage
Warning
Programs that generate heavy traffic, but get controlled via a web interfaces (with very light traffic), will also have the web interface traffic shaped. This means that they will barely be accessible.
Trickle can only limit traffic of programs that do not fork, so shaping a FTP server's traffic will not work that way.
If you are running the daemon (see below), just start any program with "trickle" in front of it:
# trickle pacman -Syu
Otherwise also specify upload and download limit as well as other configuration options (see
trickle(1)
for more information):
# trickle -s -d200 -u50 pacman -Syu
Modifying other systemd services
Modify
ExecStart
for a desired systemd service,  appending
/usr/bin/trickle
. For example:
ExecStart=/usr/bin/
daemon
changes to
ExecStart=/usr/bin/trickle /usr/bin/
daemon
When using the standalone mode, also add the configuration options as described in
#Usage
.
Restart
the daemon, which should now have shaped bandwith.
Use with rsync
Instead of putting trickle in front of the rsync command (which will not work, since rsync presumably forks the ssh process), you call rsync like this:
rsync --rsh="trickle -d 10 -u 10 ssh" SRC DEST
Daemon configuration
If you want to have application specific settings with trickled, create the optional
/etc/trickled.conf
file as described in the
trickled.conf(5)
man page. For example:
[ssh]
Priority = 1
Time-Smoothing = 0.1
Length-Smoothing = 2
[ftp]
Priority = 8
Time-Smoothing = 5
Length-Smoothing = 20
Trinity

Related articles
Desktop environment
From the Trinity Desktop Environment (TDE)
project page
:
TDE is a complete software desktop environment designed for Unix-like operating systems, intended for computer users preferring a traditional desktop model, and is free/libre software. Born as a fork of
KDE
3.5 back in 2010, TDE is now a fully independent project with its own personality and development team, available for various Linux distributions, BSD and DilOS.
TDE depends on End of Life libraries like Qt 3, which they maintain themselves.
The Trinity applications and applets should also work with other desktop environments.
Installation
Binary packages
Install either the
tde-tdebase
package from the
trinity
repository for a base Trinity environment, or
tde-meta
for a more complete one.
If you have any errors during an
upgrade
, add the
0x8685AD8B
key by following
pacman/Package signing#Adding unofficial keys
.
Build from source
Trinity Packaging repository
contains
PKGBUILD
files for most Trinity packages in the
arch
folder.
The sources are in a git repository. More info on cloning it is at their
GIT information
page.
The suggested build order is specified in the
How to Build TDE
page.
See also
DeveloperWiki:Building in a clean chroot
.
Starting
Manually
To start Trinity from the Linux console:
$ startx /opt/trinity/bin/starttde
See
xinit
for more.
Graphically
tde-tdebase
comes with TDE Display Manager. To start it at boot,
enable
the
tdm.service
.
Tips and tricks
Trinity "Kicker" panel with other desktop environments
To use the Trinity "kicker" Desktop Panel and Applets with another desktop environment, create this script and make it
executable
. For Plasma5, use
System Settings > Startup and Shutdown > Autostart > Add Script
.
#!/bin/bash
/opt/trinity/bin/tdeinit
/opt/trinity/bin/kicker
/opt/trinity/bin/tdebuildsycoca --noincremental
Troubleshooting
TDE Display Manager
If you encounter any issues, the
default.target
may have to be manually configured. See
Display manager#Loading the display manager
for resolution.
See also
TDE Git repositories
TDE Bugzilla
Mailing Lists
Developers Web
QT and TQT Tutorials and Documentation
How To Build
Trojan

Related articles
Shadowsocks
V2Ray
WireGuard
Trojan
is a proxy server, client and protocol, designed to bypass the
Great Firewall of China
by imitating HTTPS. Trojan claims to be unidentifiable.
Warning
Trojan has not undergone proper degrees of security auditing. Use it with caution!
Installation
Install
one of the following options:
trojan
− the official Trojan implementation in C++, for which development has long been stalled.
trojan-go-git
AUR
− Go implementation with features such as multiplexing, AEAD and routing based on destination IP.
trojan-r-git
AUR
− Rust implementation with an emphasis on high performance and low memory usage.
Configuration
Trojan cannot run without proper configuration. It uses
JSON
as its configuration format. All configuration work is done in
/etc/trojan/
. Detailed explanations of each field of the configuration file can be found
on the GitHub repository
.
Examples of configuration files are at
/usr/share/doc/trojan/examples/
.
TLS certificate
You will need to provide a
TLS
certificate and private key for Trojan servers to work. You can either apply for a free certificate with some automation tools like
Acme.sh
from
Let's Encrypt
or generate a self-signed one as shown in
OpenSSL#Generate a self-signed certificate
. Then, set the
cert
,
key
, and
key_password
(not necessarily) fields in the configuration file accordingly. Note that you should pin the certificate by setting
cert
on the client if you generate a self-signed certificate. Also, make sure that trojan on a server has enough permission to access the certificate and key file.
TCP Fast Open
For
TCP Fast Open
on servers to work, you will need to turn it on in your OS:
# echo 3 > /proc/sys/net/ipv4/tcp_fastopen
Disguise
Trojan servers can be disguised as other services over TLS to prevent active probing. This can be done by, for example, running a
web server
with
nginx
and pointing
remote_addr
and
remote_port
fields to the server address and port.
Running
systemd services
Trojan can be controlled with
trojan.service
and
trojan@.service
. For example,
start/enable
the
trojan@
conf
.service
instance to run Trojan with the
/etc/trojan/
conf
.json
configuration file. Trojan can be similarly ran with
/etc/trojan/config.json
by
starting/enabling
trojan.service
.
Manually
Trojan can also start in a shell, by running:
$ trojan /etc/trojan/config.json
You can replace
/etc/trojan/config.json
with any other configuration files. Note that Trojan outputs its log to
stderr
, so you will have to redirect it to a file if you want to keep the log.
See also
GitHub Project
TurboVNC

Related articles
x11vnc
TigerVNC
TurboVNC
is a high-performance VNC implementation derived from TightVNC. It provides both VNC server and VNC viewer functionalities. According to the official site, it is better than TigerVNC in multiple aspects
[1]
.
Installation
Install
the
turbovnc
AUR
package.
Running vncserver
Simply runing
vncserver
as the normal user that will later use VNC, and you will be prompted to set a password. Then configure which desktop environment to use in
/usr/bin/xstartup.turbovnc
. For example, edit the file below as root to use KDE plasma:
/usr/bin/xstartup.turbovnc
exec startplasma-x11
You can also use any different file than
/usr/bin/xstartup.turbovnc
with the
-xstartup
FILE
option of
vncserver
to avoid modifying the script provided by the package.
Then run
vncserver
again to start it, you should see it binds to the port 5901. You should always wrap it in a SSH tunnel as what is done with any other VNC software(see
TigerVNC#Accessing vncserver via SSH tunnels
).
TUXEDO Aura 15

This article or section is a candidate for merging with
Clevo NL51RU
.
Notes:
This should be the same hardware so we might no need two pages. (Discuss in
Talk:TUXEDO Aura 15#TUXEDO Aura 15#Please don't merge into Clevo page
)
This article or section does not follow the
Laptop page guidelines
.
Reason:
Hardware table needs some PCI/USB IDs, page is missing a proper accessibility, firmware and function keys table. (Discuss in
Talk:TUXEDO Aura 15
)
Hardware
PCI/USB ID
Working?
Video
1002:1636
Yes
Ethernet
10ec:8168
Yes
Card Reader
1217:8621
Yes
Wi-Fi
8086:2723
Yes
Mobile broadband
Untested
Bluetooth
8087:0029
Yes
Audio
1002:1637
Yes
Touchpad
Yes
Webcam
5986:9102
Yes
Function keys
Yes
Fingerprint sensor
04f3:0c63
Yes
Keyboard
To control the RGB keyboard and improve function keys functionality, install
tuxedo-drivers-dkms
AUR
.
Power management
See
TUXEDO InfinityBook Pro 15v4#TUXEDO Control Center
.
Video
The Aura 15 uses an AMD Radeon RX Vega graphics chip with GCN5 GPU architecture, hence
xf86-video-amdgpu
should be the correct video driver.
Fingerprint scanner
Warning
The following is probably insecure, even if in practice the false positive rate is extremely low.
Using a
modified libfprint
, it is possible to use
fprintd
as authentication agent alongside PAM just like with regular
libfprint
. The patch brings changes that improve the (previously catastrophic) false negative rate, making the fingerprint scanner actually usable and convenient.
TUXEDO InfinityBook 14 Gen10

Hardware
PCI/USB ID
Working?
Touchpad
Yes
Keyboard
Yes
GPU
1002:150e
Yes
Ethernet
1f0a:6801
Yes
Bluetooth
Yes
SD card reader
Yes
Audio
1022:15e3
Yes
Wi-Fi
8086:2725
Yes
Tuxedo lists a few troubleshooting issues on their device-specific
FAQ
See also the official
advice
from Tuxedo regarding recommended packages for Arch Linux
Keyboard
The internal keyboard may not function on resume from suspend, as noted in the FAQ linked above. Below you can find the
kernel parameters
required:
i8042.reset i8042.nomux i8042.nopnp i8042.noloop
Keyboard backlight
TUXEDO provides a driver for this. It can be installed with
tuxedo-drivers-dkms
AUR
.
Ethernet
The laptop has a built in Motorcomm YT6801 LAN chipset. The package
tuxedo-yt6801-dkms-git
AUR
provides a
kernel module
for ethernet functionality. It is built from the official
Tuxedo GitLab Repo
.
Function keys
The function keys should be recognised automatically once
tuxedo-drivers-dkms
AUR
is installed, with an exception for F3. This key could be programmed to run the Tuxedo Control Centre binary or for other purposes
Key
Visible?
1
Marked?
2
Effect
Fn+Esc
No
Yes
Toggles Fn lock
Fn+F1
No
Yes
XF86MonBrightnessDown
Fn+F2
No
Yes
XF86MonBrightnessUp
Fn+F3
Yes
Yes
Open Tuxedo Control Centre
Fn+F4
Yes
No
Fn+F5
Yes
No
Fn+F6
No
Yes
XF86AudioMute
Fn+F7
No
Yes
XF86LowerVolume
Fn+F8
No
Yes
XF86RaiseVolume
Fn+F9
No
Yes
Toggles display on/off
Fn+F10
No
Yes
XF86WebCam
Fn+F11
Yes
Yes
XF86TouchpadToggle
Fn+F12
Yes
Yes
XF86RFKill
The key is visible to
xev
and similar tools
The physical key has a symbol on it, which describes its function
Power management
As advised above by Tuxedo you can
install
the official
tuxedo-control-center-bin
AUR
to let it control the fan speed and CPU frequency. The package will create and enable the systemd service
tccd.service
, which is all that is needed for the laptop to activate the power management options chosen.
To change the power management options, and select different profiles according to the battery status (running on battery power or plugged in), a GUI binary
tuxedo-control-center
is provided.
TUXEDO InfinityBook 14 v6

This article or section does not follow the
Laptop page guidelines
.
Reason:
Needs a proper function key table, an accessibility and firmware section. (Discuss in
Talk:TUXEDO InfinityBook 14 v6
)
Hardware
PCI/USB ID
Working?
GPU
8086:9a49
Yes
Wi-Fi
8086:a0f0
Yes
Bluetooth
8087:0026
Yes
Audio
8086:a0c8
Yes
Touchpad
093a:0255
Yes
Card Reader
0bda:0316
Yes
Webcam
04f2:b71a
Yes
IR Camera
04f2:b71a
Yes
GPU
Add
i915.enable_psr=0
to the
kernel command line
to the kernel command line if you are experiencing
flickering, artifacts or low GPU performance
.
Function keys
The most
Fn
function keys work out of the box. For the
Fn
function keys
F10
,
F11
and
F12
the following must be set as
kernel parameter
(unless
tuxedo-drivers-dkms
AUR
is installed):
acpi_os_name=Linux acpi_osi=
TUXEDO Control Center
See
TUXEDO InfinityBook Pro 15v4#TUXEDO Control Center
.
Power Management
Suspend
See
Power management/Suspend and hibernate#Changing suspend method
.
Read more at the help page from TUXEDO
[1]
.