Package Details: awesome-gnome 2.3-1

Git Clone URL: https://aur.archlinux.org/awesome-gnome.git (read-only, click to copy)
Package Base: awesome-gnome
Description: Setup awesome as window manager of GNOME 3
Upstream URL: http://awesome.naquadah.org/wiki/Quickly_Setting_up_Awesome_with_Gnome
Keywords: awesome gnome
Licenses: CCPL
Submitter: dynamo
Maintainer: stas-t
Last Packager: stas-t
Votes: 10
Popularity: 0.060316
First Submitted: 2016-06-19 05:14 (UTC)
Last Updated: 2024-03-24 19:29 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

dynamo commented on 2020-02-25 15:47 (UTC)

Cool @stas-t. I updated to you can maintain this package.

marcinn commented on 2020-01-13 22:12 (UTC)

--builtin

Bless you, stas-t. Works again.

BTW: I have patch ready to commit.

stas-t commented on 2020-01-12 20:17 (UTC) (edited on 2020-01-12 20:17 (UTC) by stas-t)

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: https://github.com/i3-gnome/i3-gnome/

dynamo commented on 2020-01-10 17:37 (UTC)

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 (UTC)

You can read more about this approach here: https://wiki.archlinux.org/index.php/Xinit#xinitrc

stas-t commented on 2019-10-27 08:27 (UTC) (edited on 2019-10-27 08:48 (UTC) by stas-t)

@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 SSH_AUTH_SOCK
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 (UTC) (edited on 2019-10-26 11:57 (UTC) by frydac)

Hi,

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

org.gnome.SettingsDaemon.Clipboard
org.gnome.SettingsDaemon.Mouse

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

I have checked:

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

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

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 (UTC) (edited on 2019-10-23 12:35 (UTC) by stas-t)

@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: https://aur.archlinux.org/cgit/aur.git/tree/awesome-gnome.install?h=awesome-gnome

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
17
% grep -ri Awesome /etc/xdg/autostart/org.gnome.SettingsDaemon.*.desktop|wc -l
17

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 (UTC)

Hi.

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 https://github.com/SirJson/awesomewm-gnome/blob/master/session/awesome-gnome, but there is no integration with gnome stack (no ssh agent, strange fonts, core dump on gnome-control-center).