Thanks! I’ll add that, and then it should work! ( Famous last words… )
Now version is 1.5.24-1. Soon at mirrors. Yay!
It’s there!
Works perfectly! Thank you!
@Pudge @Shjim @joekamprad @BONK
If everyone is ok with it, and (If we are allowed) I quite like wallaper this for ARM (up to regualtion!)
And for x64_86 - Same thing without without the logo
I think we should all a moment to thank @Shjim! These are brilliant!
we will go to update ISO soon, after this is done we start implementing community contributed setups
In looking at alacritty further, I tried to launch alacritty from termite to look for error codes.
I got this:
[don@RPi4-Sway ~]$ alacritty
Created log file at "/tmp/Alacritty-747.log"
[2021-02-02 17:03:47.309452056] [ERROR] [alacritty] Alacritty encountered an unecoverable error:
There was an error initializing the shaders: Failed compiling shader: 0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.00 ES, and 3.00 ES
The log contents at “tmp/Alacritty-747.log” listed the same as above.
alacritty.yml
colors:
primary:
background: ‘#282c34’
foreground: ‘#d8dee9’
dim_foreground: ‘#282c34’
cursor:
text: ‘#2e3440’
cursor: ‘#d8dee9’
vi_mode_cursor:
text: ‘#2e3440’
cursor: ‘#d8dee9’
selection:
text: CellForeground
background: ‘#4c566a’
search:
matches:
foreground: CellBackground
background: ‘#88c0d0’
bar:
background: ‘#434c5e’
foreground: ‘#d8dee9’
normal:
black: ‘#434c5e’
red: ‘#f9929b’
green: ‘#98c379’
yellow: ‘#ebcb8b’
blue: ‘#81a1c1’
magenta: ‘#b48ead’
cyan: ‘#88c0d0’
white: ‘#d8dee9’
bright:
black: ‘#4c566a’
red: ‘#bf616a’
green: ‘#8fbcbb’
yellow: ‘#fbdf90’
blue: ‘#81a1c1’
magenta: ‘#d2b8ed’
cyan: ‘#8fbcbb’
white: ‘#d8dee9’
dim:
black: ‘#373e4d’
red: ‘#94545d’
green: ‘#809575’
yellow: ‘#b29e75’
blue: ‘#68809a’
magenta: ‘#8c738c’
cyan: ‘#6d96a5’
white: ‘#aeb3bb’
key_bindings:
- { key: Return, mods: Control|Shift, action: SpawnNewInstance }
background_opacity: 1.00
window:
padding:
x: 20
y: 20
font:
normal:
family: UbuntuMono
style: Regular
size: 12
live_config_reload: true
dynamic_padding: true
Termite worked as expected. Kitty did not.
Kitty
[don@RPi4-Sway alacritty]$ kitty
[033 17:17:45.695282] [glfw error 65543]: EGL: Failed to create context: Arguments are inconsistent
[033 17:17:45.707943] Traceback (most recent call last):
File “/usr/bin/…/lib/kitty/kitty/main.py”, line 344, in main
_main()
File “/usr/bin/…/lib/kitty/kitty/main.py”, line 337, in _main
run_app(opts, cli_opts, bad_lines)
File “/usr/bin/…/lib/kitty/kitty/main.py”, line 160, in call
_run_app(opts, args, bad_lines)
File “/usr/bin/…/lib/kitty/kitty/main.py”, line 133, in _run_app
window_id = create_os_window(
ValueError: Failed to create GLFWwindow
Off to work on getting ownership and permissions fixed in the installer.
Thanks for everyone’s patience with this Sway newbie. With help from above posts, I am starting to get more comfortable with the short cuts on Sway. I have one more question on short cuts. Is there a keyboard short cut to open the exit menu, besides clicking on the power symbol in the extreme right side of the panel?
Pudge
New window for choosing DE / WM on arm installer.
Pudge
@Pudge
That the default. No sure if it removed.
# Exit sway (logs you out of your Wayland session)
bindsym $mod+Shift+e exec swaynag -t warning -m 'You pressed the exit shortcut. Do you really want to exit sway? This will end your Wayland session.' -b 'Yes, exit sway' 'swaymsg exit'
@Shjim [mod]+Shift+e worked and brought up the power drop down menu.
I just finished a successful install of Sway on the Raspberry Pi 4b. All ownership and permissions were OK. By the way, @OdiousImp, the problem was mine, not yours.
The only thing left on the to do list is fix alacritty, or use termite instead for arm.
I also do not have Welcome coming up at the first boot up yet.
Very close.
Pudge
The alacritty devs don’t seem to be wanting to solve it anytime soon unfortunately.
Kitty’s facing a similar problem so I think we’re just better off using termite at least for ARM. Or termite for both?
Is this Sway edition only for ARM or for both ARM and x86_64?
It for both
termite work good . it need configure by user =" cp /ect/xdg/termite.config ~/.config/termite/config "
user need to make .config/termite/config No sure new users will like or known how to … in Arm it maybe good for xfce-terminal set as easy to set up … just thought
alacritty + termite great for x86
I added a termite config…XFCE4 terminal…never tried it i will do now
@OdiousImp maybe you interested ?
"network#vpn": {
"interface": "tun0",
"format": "",
"format-disconnected": "",
"tooltip-format": "{ifname}: {ipaddr}/{cidr}",
"on-click": "nm-connection-editor"
it work
I’ll add!
I’m stuck now between using XFCE4 or Termite for ARM. I’ve already made a termite config for the colorscheme…but @joekamprad and @Shjim seem to love XFCE4 Terminal… Ahhh. It will run wayland native. (Thought termite was made for wayland in the first place)
As you see it is so that users have a beloved terminal, but if you put the one you like with a nice setup, you give the opportunity to try something new
When the new iso drops later I will do an install and try termite never used it.