Package Details: awesome-gnome 2.3-1

Git Clone URL: (read-only, click to copy)
Package Base: awesome-gnome
Description: Setup awesome as window manager of GNOME 3
Upstream URL:
Keywords: awesome gnome
Licenses: CCPL
Submitter: dynamo
Maintainer: dynamo (stas-t)
Last Packager: stas-t
Votes: 9
Popularity: 0.001193
First Submitted: 2016-06-19 05:14
Last Updated: 2020-02-27 20:25

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

marcinn commented on 2020-01-13 22:12


Bless you, stas-t. Works again.

BTW: I have patch ready to commit.

stas-t commented on 2020-01-12 20:17

Hi dynamo,

I think I can do this for some time. Two things have to be fixed a.t.m.:

  • remove two items from awesome.session which I mentioned before

  • in awesome-gnome.desktop use gnome-session --builtin --session=awesome: this will prevent gnome-shell from starting when starting from XDM/GDM

I will have to follow GNOME blogs and use e.g. this Git repo as a reference:

dynamo commented on 2020-01-10 17:37

I no longer use Archlinux and switch to use Awesome only, so we need other maintainer(s). Please notice me if anyone can do that.

stas-t commented on 2019-10-27 08:51

You can read more about this approach here:

stas-t commented on 2019-10-27 08:27

@frydac: Sorry for providing you incomplete information. I've just made some checks and:

It seems that gdm now alway starts gnome-shell for gnome-session indeed.

Because of this the option to start awesome-gnome I know of is via startx from console. For that you need ~/.xinitrc file. Mine looks like

eval $(/usr/bin/gnome-keyring-daemon --start --components=pkcs11,secrets,ssh)
export GDK_BACKEND=x11
env GDK_DPI_SCALE=0.72 GTK_THEME=Materia-dark-compact systemd-cat \
  /usr/lib/notification-daemon-1.0/notification-daemon &
exec gnome-session --session=awesome

If this works for you and you like the result - you may stop and disable gdm.service and use normal console login. Note: for security reasons you may want to run your session with exec startx so that if Xorg dies for any reason - the user will have to re-authenticate again.

UPD: The main point is that exec gnome-session ... call should appear in .xinitrc and then it will be called when Xorg process is running.

frydac commented on 2019-10-26 11:17


Thanks for the info, although I haven't been able to get it to work thus far.

After updating my system, I've removed and reinstalled awesome-gnome.
I've removed


from /usr/share/gnome-session/sessions/awesome.session

I have checked:

▶ ls /etc/xdg/autostart/org.gnome.SettingsDaemon.*.desktop|wc -l

▶ grep -ri Awesome /etc/xdg/autostart/org.gnome.SettingsDaemon.*.desktop|wc -l

I have executed gnome-control-center keyboard

Also I have tried to change Exec=awesome to gnome-session-awesome taken from the github repository in /usr/share/applications/awesome.desktop (not sure this .desktop file was where this should be changed)

I do use gdm, not sure how to circumvent this and use exec gnome-session --session=awesome, tried this after starting into gnome, but it seemed to hang. But when I choose Awesome-gnome in gdm, it takes some time and it starts normal gnome. At first there was an error message, which after the above actions isn't there anymore though.

I guess I'll have to read more about gnome sessions and how awesome-gnome integrates into this, any suggestions on how to troubleshoot this would be nice.

stas-t commented on 2019-10-23 12:34

@marcinn: As I said - I've got mine running after removal (sudo pacman -R awesome-gnome) and installing it again, then after removal of Clipboard/Mouse from the session file.

Note: I needed removal of the package because otherwise it wouldn't run its post-install script (awesome-gnome.install) which prepares what you lacking exactly, i.e. GNOME integration:

gnome-control-center will crash if you have selected there e.g. Display - and it's known problem because mutter is not running. But most components would work once you fix gnome integration, e.g.:

gnome-control-center keyboard

Run these checks to verify that you allow all gnome components in your awesomewm session:

% ls /etc/xdg/autostart/org.gnome.SettingsDaemon.*.desktop|wc -l
% grep -ri Awesome /etc/xdg/autostart/org.gnome.SettingsDaemon.*.desktop|wc -l

Both commands should give you the same output - that's the number of gnome components present your gnome setup.

marcinn commented on 2019-10-21 07:14


It's not working after reinstallation and removal of Clipboard/Mouse.

I've got Awesome running after changing Exec to /usr/bin/gnome-session-awesome taken from, but there is no integration with gnome stack (no ssh agent, strange fonts, core dump on gnome-control-center).

marcinn commented on 2019-10-15 13:40

Many thanks, I'll try this.

stas-t commented on 2019-10-15 13:15

Yes, I'm using one. However there are few tricks to make it work:

  • after upgrading either gnome-settings-daemon or gnome-disk-utility you have to uninstall awesome-gnome package and install it again so it runs its script to update all /etc/xdg/autostart/org.gnome.SettingsDaemon.*.desktop files

  • as I said before - afterwards you also need to remove org.gnome.SettingsDaemon.Clipboard and org.gnome.SettingsDaemon.Mouse from awesome.session because these are no longer available in GNOME 3.24

Then you can start awesome session. I'm not using gdm recently, just have my ~/.xinitrc and starting the session directly with "exec startx".

UPD: The easiest way to try to start it from the console:

exec gnome-session --session=awesome