odex-tos / tools Goto Github PK

Describe the bug
When launching an application with swaybar we can't kill it using mod+q.
This means that part of the screen is occupied until it is manually killed from the terminal.

To Reproduce

1. Launch sway
2. Click on a swaybar app (eg wifi)
3. See the settings menu
4. mod+q the menu when having focus

Expected behavior
The application should be killed

Additional context
This mostly is a problem with sway. So it might be interesting to watch that project and see if they have a solution or if it is a config issue.

Is your feature request related to a problem? Please describe.
The installer should also include an option without encryption. For the users how use a desktop that can't really be compromised

Is your feature request related to a problem? Please describe.
When installing tos the installer should detect the processor and install the correct microcode.
Currently no microcode is provided eg intel-ucode or amd-ucode

Describe the solution you'd like
A section in the installer to include intel-ucode/amd-ucode

Is your feature request related to a problem? Please describe.
You can only install the OS on a full disk. But for people who want to dual boot it would be useful to simply install the OS on a single partition.

A packagebuild should be provided that installs all tools present in this tools repository. This way we don't need to add $HOME/bin manually for each user but we can use all tools system wide

Is your feature request related to a problem? Please describe.
You can generate ssh keys and sync them with remote servers. However you should also include a way to make gpg keys and setup git/remote keyservers with it

When using sway. A person should be able to do screen opperations. Much like the operations that exist now. They just need to be sway compatible

Describe the bug
When using the tos tool there is an error with the bluetooth interactive command

$ tos bluetooth full

This command should put you into a full blown interactive shell. However it exits quietly.

To Reproduce

1. Download the latest version of the tos tool
2. Run the command tos bluetooth full
3. Observe that nothing happens

Expected behavior
Put into a interactive shell. Much like bluetoothctl

Additional context
The bug probably involves wrong redirects of stdin and stdout. This however is a guess and could totally be wrong. More investigation is needed to determine how to fix it

Tos shell would be a new suboption of the tos command. It would install a given package in a closed environment, where it can be tested and when you stop executing the shell it would disappear completely from your system.

Usage could look something like this:

# show the output in the terminal but the app runs in a closed env
tos shell asciicinema

# mount the app to the current x session (--gui flag)
tos shell --gui firefox

# expose a dir to the env
tos shell --expose /home/$USER ls

# expose the entire filesystem
tos shell --filesystem --gui firefox

# run an application that is named differently that the package
tos shell --gui awesome-tos awesome

This can be done in multiple ways: using docker as the backbone or using chroot (we might have a flag to do both) but that can be done in a later stage

Is your feature request related to a problem? Please describe.
When hooking up a second monitor (eg a tv) the output of your sound is still going through the laptop/desktop. There should be a feature that makes it possible to duplicate or stream your audio to said monitor

Describe the solution you'd like
A simple display and voice duplicator using the tos tool. You can already duplicate screen output but sound is not duplicated yet.

Is your feature request related to a problem? Please describe.
When a system is broken you often need a rescue cd. TOS proides this in the form of there iso's. However to chroot into your installation you need to crypsetup open your devices and mount all partitions manually before chrooting.

Describe the solution you'd like
A option to tos to automatically mount the encrypted filesystem and chroot into its environment.

During the last step of the installation process we should detect if a graphics card is present and install the correct driver for it (might need to happen in calamares though)

Describe the bug
When suspending the bluetooth value is reset to on.
The tos tools should always keep bluetooth off

It seems that the user picture is different from the display manager vs the desktop environment.

This can be either a bug in tde-greeter or in here

Command to set the user-profile picture:

tos -p user-picture.jpg

current issue

When using tos screen resolution you can only set resolutions supported by xrandr. However sometimes the correct resolution can't be found (due to cheap or badly implemented monitors) if this resolution is not found it should be created instead using a new command

solution

Instead of soly relying on xrandr detected resolutions you should implement a add resolution feature. Here is a short explanation.

$ cvt <horizontal> <vertical> # get screen timing info based on resolution

$ cvt 1280 1024
# 1280x1024 59.89 Hz (CVT 1.31M4) hsync: 63.67 kHz; pclk: 109.00 MHz Modeline "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync

Based on the output of cvt you can generate the apropriat xrandr command

$ xrandr --newmode "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync

Now you have added a new resolution to your screen. Be carefull when using this xrandr command because if the resolution is not supported by your screen you can get very unexpected results. Luckily a reboot wil bring you back to the old screen resolution

I propose that the tos syntax is the following
tos screen add resolution 1920x1080 or in short tos s a r 1920x1080

Describe the current issue
The tos -u option is no longer revelant as it depends on an old implementation of the architecture.

Describe the current issue
tos help is still displaying the old interface with tos. This is however outdated since a big refactor took place recently.

Where is the problem
tos-helper/help.sh contains nothing but old code.

How should it change
The printf statement need to be updated to support the new syntax used by tos.

What are the benefits?
People rely heavily on help functions. This means they need to work properly.

When booting up and starting i3 we should detect all touchpads and enable the soft touch setting

Describe the bug
When installing tos with the dialog installer the oh-my-zsh framework doesn't get installed. This
If you login the first time you are put into a tty (instead of sway/i3) and have a bare bone bash prompt.

To Reproduce

1. Follow the dialog installer and use the recommended settings
2. Boot your device without the installer iso
3. Observe that zsh is not the default shell and that .oh-my-zsh is not installed
4. tos tool is not in bash path

Expected behavior
zsh should be the default shell and oh-my-zsh should be installed. Also tos should be in the bash path.

Additional context

Zsh related

It seems that zsh failed to install during the installer process. it think due to beeing root user or something hower this should be checked in more detail.

Bash related

The following lines from zshrc should be added to the bashrc

export ZSH=$HOME"/.oh-my-zsh"
export ZSH_LOAD=$ZSH/load
export ZSH_PRELOAD=$ZSH_LOAD/preload
PATH="$HOME/bin:$HOME/.local/bin:$PATH:/usr/lib/dart/bin:$HOME/.pub-cache/bin"
export PATH=/home/zeus/dev/flutter/bin:$PATH
export PATH=$HOME/bin:$HOME/opt/cross/bin:$PATH

These will help with launching the custom scripts and having the correct path variable

Is your feature request related to a problem? Please describe.
The current tools provided rely heavily on X11. Here are a few examples

• open (uses xdg-open)
• tos screen (uses xrandr)
• sway config (uses xbacklight?!?)
• rofi (it works with xwayland but still)
  These tools are allowed but wayland compatible tools need to be present also.

Describe the solution you'd like
A check in each script to respond to wayland as well.

Describe the bug
The keepalive script restarts polybar if it is broken (a crash or something) and simply restarts is.
However when using sway with wayland polybar isn't supported (it is threated like a normal application) This means we have to use a different piece of software (tos recommends swaybar) but keepalive doesn't support swaybar yet.

To Reproduce

1. Launch tos
2. start the graphical environment with sway
3. Start keepalive (if not started)
4. Kill swaybar

Expected behavior
After killing swaybar it should automatically restart

Additional context
Simply verify if sway is the current window manager and check for waybar instead of polybar.