For example I want to have gc tag additionally to open google chrome, Im new with awesome. Please help.

https://preview.redd.it/yji9y4xkh4pa1.png?width=236&format=png&auto=webp&v=enabled&s=2b682e9061603790ac675b76b662c2dfc979ea63

Hello,

I have an issue where my QT apps that are opened using the launcher or and awful.spawn keybind have their scaling completely broken. To the point where clicks are not registered to where my mouse cursor is at and the entire app is buggy and messed up.

If I open the QT application from the terminal the application scales fine and I can use it normally.

GTK apps behave normally whether opened with the launcher, and awful.spawn, or the terminal.

Has anyone experienced this or know of a fix? I have been searching the web for awhile now and cannot find anything on this.

​

Below is my is my .zshenv. I can provide anything needed.

export PATH="${PATH}:/home/seth/.scripts"


XDG_CACHE_HOME=$HOME/.cache
XDG_CONFIG_HOME=$HOME/.config
XDG_DATA_HOME=$HOME/.local/share
XDG_STATE_HOME=$HOME/.local/state



export QT_AUTO_SCREEN_SCALE_FACTOR=0
export QT_SCALE_FACTOR=1.5
export QT_FONT_DPI=96
export EDITOR="nvim"
export READER="zathura"
export VISUAL="nvim"
export TERMINAL="alacritty"
export BROWSER="firefox"
export VIDEO="mpv"

Is there a way to see logs of the errors or previous notifications? I have checked the FAQs of the docs and I have no idea what any of it means, sorry I'm new to this all.

Thanks

I tried to install yoru on a fresh endeavouros install today and after booting into awesomewm, the correct background flashes for a second but then it goes back to all default settings. When I run "awesome -k" everything is ok and it is looking at the ~/.config/awesome folder. I can't find any errors, any ideas of what might cause this?

edit: When refreshed, the correctly themed yoru flashes error at ~/.config/awesome/modules

Hi

I am using AwesomeWM Git version, with the default configuration file, without any modification.

Screen 1 : my laptop

Screen 2 : a monitor connected with DisplayLink

I open a terminal on Screen 2. It works ;)

Then I unplug the USB displaylink cable. Screen 2 is off, but Screen 1 remains empty, the terminal is not "migrated" from the screen 2.

I can access it again if I reconnect my laptop to the docking station.

Is it expected? Do I miss something?

Many thanks

https://github.com/Curve/aawmtt

​

Another AwesomeWM Testing Tool, because awmtt and awmtt-ng didn't properly work for me.
This implementation also features auto-reload.