[SOLVED]Cant open terminal or other apps using tty1.

boris9921 · 2024-08-21 11:00:32

I recently switched from kde to i3 on x11. Used sddm to login but decided to remove it. I managed to automate login using getty. Im on zsh and with zprofile im executing startx and im entering i3 and everything even feh is loading my background but when i try to use modkeys and nothing happens.
When i switch to tty2 login manually and startx modkeys work normally.
I have tried switching over to bash, trying different scripts for zprofile, redoing the xinitrc but without success.

my .xinitrc

feh --bg-scale ~/Downloads/wallpaper/WEVfbB.jpg
  exec i3

my .zprofile

  if [[ -z ${DISPLAY} && ${XDG_VTNR} -eq 1 ]]; then
    exec startx -- -keeptty -nolisten tcp > ~/.xorg.log 2>&1
  fi

This is my getty drop in

  
[Service]
  ExecStart=
  ExecStart=-/usr/bin/agetty --autologin boris --noclear %I $TERM

Does someone have any tips on why this could be happening.

Last edited by boris9921 (2024-08-21 16:53:05)

Lone_Wolf · 2024-08-21 11:06:52

Please use code tags for command output & content of text files, see https://bbs.archlinux.org/help.php#bbcode

Your ~/.xinitrc is broken, read https://wiki.archlinux.org/title/Xinit#xinitrc an correct it.

boris9921 · 2024-08-21 11:12:06

I am sorry i edited the post with tags.
Thank you i will read and fix.

boris9921 · 2024-08-21 12:12:06

okay so i saw what was the problem with ~/.xinitrc
i added

#!/bin/sh

and i added a missing & after feh
so it looks like this

#!/bin/sh
feh --bg-scale ~/Downloads/wallpaper/WEVfbB.jpg &
exec i3

i also tested with firefox it starts if i add it to the shell script but i still cant use my modkeys

Last edited by boris9921 (2024-08-21 13:29:07)

Trilby · 2024-08-21 13:18:41

~~You didn't fix your post to use code tags - you apparently used ins tags.~~ Also I'm pretty sure that's not your full ~/.zprofile, is it?

Also please actually describe the problem / symptoms. All we have is "when i try to use modkeys and nothing happens." What does this mean? How do you try to use it? And what is it? There is no "modkeys" binary in the main repos, and I didn't quickly find any "modkeys" matches in the AUR. Is this about modmap? Or bindkeys? Or do you mean i3 is not responding to keybindings from it's config file??

Last edited by Trilby (2024-08-21 14:28:21)

boris9921 · 2024-08-21 13:46:04

So to start this is actually my full ~/.zprofile.

Its my mistake i should have said bindkeys in i3 from the config file not modkeys

Like my original post i will say that i installed i3wm and i made it so in tty1 i would autologin without a login manager and i setup automatically to startx. But after boot up i try to use my bindkeys but they are not executing programs like firefox dmenu or terminal. I only see the cursor changes to a circle which means it sees an input. I do not know from where this could be happening i believe it could be something with my zprofile if you are saying that is not full then for sure im missing something. I dont think its something with i3

I checked the config file for i3wm but its its not form there.

I would say though before i removed the login manager everything was working fine.

I hope im giving you a better picture. Im still new into this only 5 months with arch.

Last edited by boris9921 (2024-08-21 13:48:09)

Trilby · 2024-08-21 14:28:00

In that case it sounds like an i3 issue, so any relevant error output would be in ~/.xorg.log

Your ~/.zprofile is fine. I was just skeptical that there was nothing else in it. Frequently shell profiles would have additional content.

The most notable difference between when you report it working and not working is that in the working condition your ~/.zshrc is sourced before i3 is started. Typically this shouldn't matter, but if you've put something in your i3 config that depends on settings from your ~/.zshrc then this may be the source of the problem.

Please post these two files as well (so in total, please post ~/.xorg.log ~/.config/i3/config and ~/.zshrc in code tags).

boris9921 · 2024-08-21 14:55:03

So this is my ~/.config/i3/config

# This file has been auto-generated by i3-config-wizard(1).
# It will not be overwritten, so edit it as you like.
#
# Should you change your keyboard layout some time, delete
# this file and re-run i3-config-wizard(1).
#

# i3 config file (v4)
#
# Please see https://i3wm.org/docs/userguide.html for a complete reference!

set $mod Mod1

# Font for window titles. Will also be used by the bar unless a different font
# is used in the bar {} block below.
font pango:monospace 8

# This font is widely installed, provides lots of unicode glyphs, right-to-left
# text rendering and scalability on retina/hidpi displays (thanks to pango).
#font pango:DejaVu Sans Mono 8

# Start XDG autostart .desktop files using dex. See also
# https://wiki.archlinux.org/index.php/XDG_Autostart
exec --no-startup-id dex --autostart --environment i3

# The combination of xss-lock, nm-applet and pactl is a popular choice, so
# they are included here as an example. Modify as you see fit.

# xss-lock grabs a logind suspend inhibit lock and will use i3lock to lock the
# screen before suspend. Use loginctl lock-session to lock your screen.
exec --no-startup-id xss-lock --transfer-sleep-lock -- i3lock --nofork

# NetworkManager is the most popular way to manage wireless networks on Linux,
# and nm-applet is a desktop environment-independent system tray GUI for it.
exec --no-startup-id nm-applet

# Use pactl to adjust volume in PulseAudio.
set $refresh_i3status killall -SIGUSR1 i3status
bindsym XF86AudioRaiseVolume exec --no-startup-id pactl set-sink-volume @DEFAULT_SINK@ +10% && $refresh_i3status
bindsym XF86AudioLowerVolume exec --no-startup-id pactl set-sink-volume @DEFAULT_SINK@ -10% && $refresh_i3status
bindsym XF86AudioMute exec --no-startup-id pactl set-sink-mute @DEFAULT_SINK@ toggle && $refresh_i3status
bindsym XF86AudioMicMute exec --no-startup-id pactl set-source-mute @DEFAULT_SOURCE@ toggle && $refresh_i3status


# Use Mouse+$mod to drag floating windows to their wanted position
floating_modifier $mod

# move tiling windows via drag & drop by left-clicking into the title bar,
# or left-clicking anywhere into the window while holding the floating modifier.
tiling_drag modifier titlebar

# start a terminal
bindsym $mod+Return exec terminator

# kill focused window
bindsym $mod+Shift+q kill

# start dmenu (a program launcher)
bindsym $mod+d exec /usr/bin/nautilus
# A more modern dmenu replacement is rofi:
# bindcode $mod+40 exec "rofi -modi drun,run -show drun"
# There also is i3-dmenu-desktop which only displays applications shipping a
# .desktop file. It is a wrapper around dmenu, so you need that installed.
# bindcode $mod+40 exec --no-startup-id i3-dmenu-desktop

# change focus
bindsym $mod+j focus left
bindsym $mod+k focus down
bindsym $mod+l focus up
bindsym $mod+semicolon focus right

# alternatively, you can use the cursor keys:
bindsym $mod+Left focus left
bindsym $mod+Down focus down
bindsym $mod+Up focus up
bindsym $mod+Right focus right

# move focused window
bindsym $mod+Shift+j move left
bindsym $mod+Shift+k move down
bindsym $mod+Shift+l move up
bindsym $mod+Shift+semicolon move right

# alternatively, you can use the cursor keys:
bindsym $mod+Shift+Left move left
bindsym $mod+Shift+Down move down
bindsym $mod+Shift+Up move up
bindsym $mod+Shift+Right move right

# split in horizontal orientation
bindsym $mod+h split h

# split in vertical orientation
bindsym $mod+v split v

# enter fullscreen mode for the focused container
bindsym $mod+f fullscreen toggle

# change container layout (stacked, tabbed, toggle split)
bindsym $mod+s layout stacking
bindsym $mod+w layout tabbed
bindsym $mod+e layout toggle split

# toggle tiling / floating
bindsym $mod+Shift+space floating toggle

# change focus between tiling / floating windows
bindsym $mod+space focus mode_toggle

# focus the parent container
bindsym $mod+a focus parent

# focus the child container
#bindsym $mod+d focus child

# start steam
bindsym $mod+g exec /usr/bin/steam

# start firefox
bindsym $mod+b exec /usr/bin/firefox

# Define names for default workspaces for which we configure key bindings later on.
# We use variables to avoid repeating the names in multiple places.
set $ws1 "1"
set $ws2 "2"
set $ws3 "3"
set $ws4 "4"
set $ws5 "5"
set $ws6 "6"
set $ws7 "7"
set $ws8 "8"
set $ws9 "9"
set $ws10 "10"

# switch to workspace
bindsym $mod+1 workspace number $ws1
bindsym $mod+2 workspace number $ws2
bindsym $mod+3 workspace number $ws3
bindsym $mod+4 workspace number $ws4
bindsym $mod+5 workspace number $ws5
bindsym $mod+6 workspace number $ws6
bindsym $mod+7 workspace number $ws7
bindsym $mod+8 workspace number $ws8
bindsym $mod+9 workspace number $ws9
bindsym $mod+0 workspace number $ws10


# move focused container to workspace
bindsym $mod+Shift+1 move container to workspace number $ws1
bindsym $mod+Shift+2 move container to workspace number $ws2
bindsym $mod+Shift+3 move container to workspace number $ws3
bindsym $mod+Shift+4 move container to workspace number $ws4
bindsym $mod+Shift+5 move container to workspace number $ws5
bindsym $mod+Shift+6 move container to workspace number $ws6
bindsym $mod+Shift+7 move container to workspace number $ws7
bindsym $mod+Shift+8 move container to workspace number $ws8
bindsym $mod+Shift+9 move container to workspace number $ws9
bindsym $mod+Shift+0 move container to workspace number $ws10

# reload the configuration file
bindsym $mod+Shift+c reload
# restart i3 inplace (preserves your layout/session, can be used to upgrade i3)
bindsym $mod+Shift+r restart
# exit i3 (logs you out of your X session)
bindsym $mod+Shift+e exec "i3-nagbar -t warning -m 'You pressed the exit shortcut. Do you really want to exit i3? Th>

# resize window (you can also use the mouse for that)
mode "resize" {
        # These bindings trigger as soon as you enter the resize mode

        # Pressing left will shrink the window’s width.
        # Pressing right will grow the window’s width.
        # Pressing up will shrink the window’s height.
        # Pressing down will grow the window’s height.
        bindsym j resize shrink width 10 px or 10 ppt
        bindsym k resize grow height 10 px or 10 ppt
        bindsym l resize shrink height 10 px or 10 ppt
        bindsym semicolon resize grow width 10 px or 10 ppt

        # same bindings, but for the arrow keys
        bindsym Left resize shrink width 10 px or 10 ppt
        bindsym Down resize grow height 10 px or 10 ppt
        bindsym Up resize shrink height 10 px or 10 ppt
        bindsym Right resize grow width 10 px or 10 ppt

        # back to normal: Enter or Escape or $mod+r
        bindsym Return mode "default"
        bindsym Escape mode "default"
        bindsym $mod+r mode "default"
}

bindsym $mod+r mode "resize"

# Start i3bar to display a workspace bar (plus the system information i3status
# finds out, if available)
bar {
        status_command i3status
}

Yeah there is some issues with setting up i3 apparently from the ~/.xorg.log

X.Org X Server 1.21.1.13
X Protocol Version 11, Revision 0
Current Operating System: Linux archlinux 6.10.6-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 19 Aug 2024 17:02:39 +0000 x86_>
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=37eef753-e7b6-4312-a11a-802a570195f7 rw loglevel=3 qui>

Current version of pixman: 0.43.4
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Aug 21 15:11:53 2024
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
dbus-run-session: ignoring unknown child process 760
/bin/sh: line 1: nm-applet: command not found
/bin/sh: line 1: xss-lock: command not found
/bin/sh: line 1: dex: command not found
i3status: trying to auto-detect output_format setting
i3status: auto-detected "i3bar"
Authorization required, but no authorization protocol specified

Authorization required, but no authorization protocol specified

You need to run terminator in an X environment. Make sure $DISPLAY is properly set

And here is my ~/.zshrc

# If you come from bash you might have to change your $PATH.
# export PATH=$HOME/bin:$HOME/.local/bin:/usr/local/bin:$PATH

# Path to your oh-my-zsh installation.
export ZSH="$HOME/.oh-my-zsh"

# Set name of the theme to load --- if set to "random", it will
# load a random theme each time oh-my-zsh is loaded, in which case,
# to know which specific one was loaded, run: echo $RANDOM_THEME
# See https://github.com/ohmyzsh/ohmyzsh/wiki/Themes
ZSH_THEME="robbyrussell"

# Set list of themes to pick from when loading at random
# Setting this variable when ZSH_THEME=random will cause zsh to load
# a theme from this variable instead of looking in $ZSH/themes/
# If set to an empty array, this variable will have no effect.
# ZSH_THEME_RANDOM_CANDIDATES=( "robbyrussell" "agnoster" )

# Uncomment the following line to use case-sensitive completion.
# CASE_SENSITIVE="true"

# Uncomment the following line to use hyphen-insensitive completion.
# Case-sensitive completion must be off. _ and - will be interchangeable.
# HYPHEN_INSENSITIVE="true"

# Uncomment one of the following lines to change the auto-update behavior
# zstyle ':omz:update' mode disabled  # disable automatic updates
# zstyle ':omz:update' mode auto      # update automatically without asking
# zstyle ':omz:update' mode reminder  # just remind me to update when it's time

# Uncomment the following line to change how often to auto-update (in days).
# zstyle ':omz:update' frequency 13

# Uncomment the following line if pasting URLs and other text is messed up.
# DISABLE_MAGIC_FUNCTIONS="true"

# Uncomment the following line to disable colors in ls.
# DISABLE_LS_COLORS="true"

# Uncomment the following line to disable auto-setting terminal title.
# DISABLE_AUTO_TITLE="true"

# Uncomment the following line to enable command auto-correction.
# ENABLE_CORRECTION="true"

# Uncomment the following line to display red dots whilst waiting for completion.
# You can also set it to another string to have that shown instead of the default red dots.
# e.g. COMPLETION_WAITING_DOTS="%F{yellow}waiting...%f"
# Caution: this setting can cause issues with multiline prompts in zsh < 5.7.1 (see #5765)
# COMPLETION_WAITING_DOTS="true"

# Uncomment the following line if you want to disable marking untracked files
# under VCS as dirty. This makes repository status check for large repositories
# much, much faster.
# DISABLE_UNTRACKED_FILES_DIRTY="true"

# Uncomment the following line if you want to change the command execution time
# stamp shown in the history command output.
# You can set one of the optional three formats:
# "mm/dd/yyyy"|"dd.mm.yyyy"|"yyyy-mm-dd"
# or set a custom format using the strftime function format specifications,
# see 'man strftime' for details.
# HIST_STAMPS="mm/dd/yyyy"

# Would you like to use another custom folder than $ZSH/custom?
# ZSH_CUSTOM=/path/to/new-custom-folder

# Which plugins would you like to load?
# Standard plugins can be found in $ZSH/plugins/
# Custom plugins may be added to $ZSH_CUSTOM/plugins/
# Example format: plugins=(rails git textmate ruby lighthouse)
# Add wisely, as too many plugins slow down shell startup.
plugins=(git)

source $ZSH/oh-my-zsh.sh

# User configuration

# export MANPATH="/usr/local/man:$MANPATH"

# You may need to manually set your language environment
# export LANG=en_US.UTF-8

# Preferred editor for local and remote sessions
# if [[ -n $SSH_CONNECTION ]]; then
#   export EDITOR='vim'
# else
#   export EDITOR='mvim'
# fi

# Compilation flags
# export ARCHFLAGS="-arch x86_64"

# Set personal aliases, overriding those provided by oh-my-zsh libs,
# plugins, and themes. Aliases can be placed here, though oh-my-zsh
# users are encouraged to define aliases within the ZSH_CUSTOM folder.
# For a full list of active aliases, run `alias`.
#
# Example aliases
# alias zshconfig="mate ~/.zshrc"
# alias ohmyzsh="mate ~/.oh-my-zsh"

Last edited by boris9921 (2024-08-21 14:55:50)

seth · 2024-08-21 15:09:16

Your xnitrc is still broken, see the link Lone_Wolf provided (also last link below) again and pay attention to the second blue note about what to include at least.

boris9921 · 2024-08-21 15:26:06

seth wrote:

Your xnitrc is still broken, see the link Lone_Wolf provided (also last link below) again and pay attention to the second blue note about what to include at least.

So i added the if to ~/.xinitrc i believe know both should be sourced.
According to the other links i did read about drop in files from the second link you attached. The one about dualbooting is irrelevent i dont use windows. And the first i will try to upload files like this .

Last edited by boris9921 (2024-08-21 15:26:47)

seth · 2024-08-21 15:29:37

Those are my signature - please post the actual xinitrc you've right now, make sure you've xterm installed, run that ("xterm &") before "exec i3" and see whether you get an xterm - and can interact with it.

boris9921 · 2024-08-21 15:36:05

seth wrote:

Those are my signature - please post the actual xinitrc you've right now, make sure you've xterm installed, run that ("xterm &") before "exec i3" and see whether you get an xterm - and can interact with it.

#!/bin/sh
if [ -d /etc/X11/xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi

feh --bg-scale ~/Downloads/wallpaper/WEVfbB.jpg &
xterm &
exec i3

Yeah i can interact with xterm

Last edited by boris9921 (2024-08-21 15:36:49)

seth · 2024-08-21 16:07:26

Can you start a second xterm from that xterm?
What's the output of

echo $DISPLAY
xauth info

Trilby · 2024-08-21 16:14:16

The ~/.xorg.log is interesting and suggests several possible issues - but the first is the reference to dbus-run-session.

dbus-run-session should not be used. And allegedly it is not used as it is not in any of the files you posted to the forums. Yet the log shows an attempt to run it. This leads me to suspect that the file contents that you've posted are not the actual verbatim content.

EDIT: Oh Wait ... you're using OMZ?! *throws hands up* Then forget everything else. I'd bet my left **** that OMZ is somehow causing this problem. Try removing that (and then preferably burning it with fire, nuking it from space, and then covering it in concrete and giving it a burial at sea.)

Last edited by Trilby (2024-08-21 16:18:20)

boris9921 · 2024-08-21 16:18:55

No i cant start another xterm i get Authorization required, but no authorization protocol specified.
Aswell as Error: cannot open display :0
I export to to 1 and 2 but it it was giving error cannot open. Though it was not returning the Authorization error
As for xauth info

Authority file:  /home/boris/.Xauthority
File new: no
File locked: no
Number of entries: 1
CHanges honored: yes
Changes made: no
Current input: (argv):1

Also i should mention that a couple of times i got an error about some colorreload-gtk-module.
I found it in some settings.ini file from kde and i uncomented it so its not returning anymore.

seth · 2024-08-21 16:24:06

xauth list
hostnamectl

boris9921 · 2024-08-21 16:28:13

Trilby wrote:

The ~/.xorg.log is interesting and suggests several possible issues - but the first is the reference to dbus-run-session.
dbus-run-session should not be used. And allegedly it is not used as it is not in any of the files you posted to the forums. Yet the log shows an attempt to run it. This leads me to suspect that the file contents that you've posted are not the actual verbatim content.
EDIT: Oh Wait ... you're using OMZ?! *throws hands up* Then forget everything else. I'd bet my left **** that OMZ is somehow causing this problem. Try removing that (and then preferably burning it with fire, nuking it from space, and then covering it in concrete and giving it a burial at sea.)

:D:D:D I uninstalled OMZ. I saw earlier some posts about people hating on it. A friend of mine suggested that is good for ricing up terminal. Ill research a bit why its bad later. On the topic no its was not from OMZ. Looks like its some display export problem because after i rebooted it returned to display 0 on its own. It continues with the Authorization requirement

Last edited by boris9921 (2024-08-21 16:30:08)

boris9921 · 2024-08-21 16:41:22

seth wrote:

xauth list
hostnamectl

xauth list

archlinux/unix:0  MIT-MAGIC-COOKIE-1  97629f1aceee55d332bbe1783ac2a8c3
Borkata/unix:1  MIT-MAGIC-COOKIE-1  46339502980db722673147414222b7c0

hostnamectl

Transient hostname: Borkata
         Icon name: computer-desktop
           Chassis: desktop ?️
        Machine ID: 99defb8ba12b45b4b521d40ee7de33ad
           Boot ID: b5f0d901011e49a398866bc0abc0d884
  Operating System: Arch Linux                      
            Kernel: Linux 6.10.6-arch1-1
      Architecture: x86-64
   Hardware Vendor: ASRock
    Hardware Model: B760M PG Lightning
  Firmware Version: 1.04
     Firmware Date: Wed 2023-04-26
      Firmware Age: 1y 3month 3w 6d

seth · 2024-08-21 16:46:36

https://wiki.archlinux.org/title/Networ … e_hostname

X11 is a network protocol that colors pixels by accident, when the hostname changes, you're loosing access to the server.

Does dbus-run-session still show up anywhere after fixing your xinitrc?

Edit: OMZ is One Messy Zsh-stuff-collection, most people confuse it for https://wiki.archlinux.org/title/Powerline but it's not.
If you want some QND solution for more fancy zsh stuff, have a look (literally) at https://archlinux.org/packages/extra/an … sh-config/

Last edited by seth (2024-08-21 16:49:25)

boris9921 · 2024-08-21 16:49:57

seth wrote:

https://wiki.archlinux.org/title/Networ … e_hostname
X11 is a network protocol that colors pixels by accident, when the hostname changes, you're loosing access to the server.
Does dbus-run-session still show up anywhere after fixing your xinitrc?
Edit: OMZ is One Messy Zsh-stuff-collection, most people confuse it for https://wiki.archlinux.org/title/Powerline but it's not.
If you want some QND solution for more fancy zsh stuff, have a look (literally) at https://archlinux.org/packages/extra/an … sh-config/

No dbus-run-session doesnt show up anymore.
I will read into your link.

boris9921 · 2024-08-21 16:52:44

boris9921 wrote:

seth wrote:
https://wiki.archlinux.org/title/Networ … e_hostname
X11 is a network protocol that colors pixels by accident, when the hostname changes, you're loosing access to the server.
Does dbus-run-session still show up anywhere after fixing your xinitrc?
Edit: OMZ is One Messy Zsh-stuff-collection, most people confuse it for https://wiki.archlinux.org/title/Powerline but it's not.
If you want some QND solution for more fancy zsh stuff, have a look (literally) at https://archlinux.org/packages/extra/an … sh-config/
No dbus-run-session doesnt show up anymore.
I will read into your link.

That fixed it. THANK YOU. You are legends guys.
I will mark as solved now.

Arch Linux

#1 2024-08-21 11:00:32

[SOLVED]Cant open terminal or other apps using tty1.

#2 2024-08-21 11:06:52

Re: [SOLVED]Cant open terminal or other apps using tty1.

#3 2024-08-21 11:12:06

Re: [SOLVED]Cant open terminal or other apps using tty1.

#4 2024-08-21 12:12:06

Re: [SOLVED]Cant open terminal or other apps using tty1.

#5 2024-08-21 13:18:41

Re: [SOLVED]Cant open terminal or other apps using tty1.

#6 2024-08-21 13:46:04

Re: [SOLVED]Cant open terminal or other apps using tty1.

#7 2024-08-21 14:28:00

Re: [SOLVED]Cant open terminal or other apps using tty1.

#8 2024-08-21 14:55:03

Re: [SOLVED]Cant open terminal or other apps using tty1.

#9 2024-08-21 15:09:16

Re: [SOLVED]Cant open terminal or other apps using tty1.

#10 2024-08-21 15:26:06

Re: [SOLVED]Cant open terminal or other apps using tty1.

#11 2024-08-21 15:29:37

Re: [SOLVED]Cant open terminal or other apps using tty1.

#12 2024-08-21 15:36:05

Re: [SOLVED]Cant open terminal or other apps using tty1.

#13 2024-08-21 16:07:26

Re: [SOLVED]Cant open terminal or other apps using tty1.

#14 2024-08-21 16:14:16

Re: [SOLVED]Cant open terminal or other apps using tty1.

#15 2024-08-21 16:18:55

Re: [SOLVED]Cant open terminal or other apps using tty1.

#16 2024-08-21 16:24:06

Re: [SOLVED]Cant open terminal or other apps using tty1.

#17 2024-08-21 16:28:13

Re: [SOLVED]Cant open terminal or other apps using tty1.

#18 2024-08-21 16:41:22

Re: [SOLVED]Cant open terminal or other apps using tty1.

#19 2024-08-21 16:46:36

Re: [SOLVED]Cant open terminal or other apps using tty1.

#20 2024-08-21 16:49:57

Re: [SOLVED]Cant open terminal or other apps using tty1.

#21 2024-08-21 16:52:44

Re: [SOLVED]Cant open terminal or other apps using tty1.

Board footer