Awesome WM

[andrea...@gmail.com]

Hi,

I've heard that there is a port of Awesome, usable as window manager in Dom0, available. Could you share this? I'd really like to get rid of KDE. :)

Thanks,

Andreas

[Wojciech Zygmunt Porczyk]

On Thu, Oct 23, 2014 at 03:02:47AM -0700, andrea...@gmail.com wrote:
> I've heard that there is a port of Awesome, usable as window manager in
> Dom0, available. Could you share this? I'd really like to get rid of KDE. :)

Here you are: git://git.qubes-os.org/woju/desktop-linux-awesome.git

This is barely tested. There are currently following known issues:
- xscreensaver startup and dependency is missing;
- ConfigureWindow X event is sometimes delayed to after focus switch
(I don't know why, still investigating); that means resizing AppVM
windows is barely working;
- because of above, is not (yet) included in official repos, you have
to compile it yourself

To remedy some of those issues, I will post my rc.lua somewhere on the
wiki. Default config in package is almost generic.

--
regards, _.-._
Wojciech Porczyk .-^' '^-.
Qubes OS Developer |'-.-^-.-'|
| | | |
I do not fear computers, | '-.-' |
I fear lack of them. '-._ : ,-'
-- Isaac Asimov `^-^-_>

[Wojtek Porczyk]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Mar 10, 2015 at 08:08:49PM -0700, fowl...@riseup.net wrote:
> > Here you are: git://git.qubes-os.org/woju/desktop-linux-awesome.git
> >
>

> This link redirects to the github now where I can find this repo.

Uploaded to github: https://github.com/woju/qubes-desktop-linux-awesome.git

> > To remedy some of those issues, I will post my rc.lua somewhere on the
> > wiki. Default config in package is almost generic.
> >
>

> Have you worked out these issue and posted your rc.lua anywhere yet?

I'm afraid no, I had more pressing things to do. Sorry for that.


- --
regards, _.-._
Wojtek Porczyk .-^' '^-.
Invisible Things Lab |'-.-^-.-'|

| | | |
I do not fear computers, | '-.-' |
I fear lack of them. '-._ : ,-'
-- Isaac Asimov `^-^-_>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJVAB8NAAoJEL9r2TIQOiNR2QkP/1pgdB+HmRpK7GTbWv9fpSsB
nf1rYLtHOor6RDiZYhHbgDjbUObtvJZW7plyBrCFioAEZewPFjwffgsgld8+bXDI
dNEg2/1L2jBoc1fJm8Sk3zuaeseigvvH7SgQBAj2/Xno0Fx6fDE9pxKHAf2Fsvsn
Bf5dWkz3neXRunSWxErGjZk4btPU/kpSUq6tgBA9BNoB2fkUcCFCSNQbafqkQjo6
QcBGl/QxI0Vp1w8UPyXeUGEHFeKxmDB609O/EkW29NAoD9Am/u+wJptURx6lc4h6
U+MN14Jie7voSXArIdu2URUu4hml0Dku95t04RJk0pt0fM37pKtI+7dR6/uHllno
sOCV1Fw+U7tFD7T594nwYp68e3S+mKQoTcVyI3kMXJLWAHdqX8xfKpuRLbDepkn1
+jXPjbrVWw5GPvMJ9yhOkLWgmJS1Ffsb92HNssbmaG3aU0unMDEXrTMQYA8jD8Az
dvzs1kX0z7I3w8Di0t9Trsc40Z377zFSgXQhpWqd3PW25crNbQtOiy0gJIspQB4e
eyXBQbKfq5m0aE+J2VwT1bRDEc8+63bnWuduZUyrRZfEoQSF34MD76roNcSmTFMI
m9WasQ4xFcr/zlheXV9Fqj5PW5nioOEO3CqCNGmOTVfPVPTRxev9D7PX3M9NeOT5
Y4T27gopezayJi2CBLfw
=dCzp
-----END PGP SIGNATURE-----

[fowl...@riseup.net]

Here you are: git://git.qubes-os.org/woju/desktop-linux-awesome.git

 

This link redirects to the github now where I can find this repo.

This is barely tested. There are currently following known issues:
 - xscreensaver startup and dependency is missing;
 - ConfigureWindow X event is sometimes delayed to after focus switch
   (I don't know why, still investigating); that means resizing AppVM
   windows is barely working;
 - because of above, is not (yet) included in official repos, you have
   to compile it yourself

To remedy some of those issues, I will post my rc.lua somewhere on the
wiki. Default config in package is almost generic.

[ro...@mullvad.net]

First of all, thank you for your great work on qubes! I know you have a busy schedule so I hope this reply isn't too long and that I'm not requesting too much assistance!

Now, I recently started using qubes and as you probably know yourself (since you are the one who has patched awesome to work with qubes) not using a tiling window manager kind of drives you mad when you're accustomed to using one! :)

I'd just like some clarifications before I try to experiment with your patched awesome version:
- Does the resizing of AppVM windows affect moving tiles around as well? Do the windows get borked when a bigger tile is moved to a smaller one?
- Since the xfce repo has not been updated in the past months I'm guessing you haven't changed anything that should break awesome from working when using qubes 3?
- Is the rc.lua you're describing required for awesome to work with qubes?
- Is there anything else I should be aware of that you haven't described?

I understand that this is not production ready and am willing to live with some quirks/bugs here and there, it would just be nice to be able to use (proper) tiling again!

Regards,
Robin

As you have said

[Wojtek Porczyk]

On Thu, Jun 04, 2015 at 04:09:37AM -0700, ro...@mullvad.net wrote:
> First of all, thank you for your great work on qubes! I know you have a
> busy schedule so I hope this reply isn't too long and that I'm not
> requesting too much assistance!

Sorry for the delay, but last weekend was the so called "long weekend"
which spanned 4 days because of the holiday on Thursday in Poland and
I used it for AFK vacation.

> Now, I recently started using qubes and as you probably know yourself
> (since you are the one who has patched awesome to work with qubes) not
> using a tiling window manager kind of drives you mad when you're accustomed
> to using one! :)

Oh, yes. Since I got accustomed to it, everything else feels so sloppy.
Nice to meet a friendly soul. :)

> I'd just like some clarifications before I try to experiment with your
> patched awesome version:
> - Does the resizing of AppVM windows affect moving tiles around as well? Do
> the windows get borked when a bigger tile is moved to a smaller one?

Yes, the windows do get borked. Resizing tile does not always results in
resizing of the window content. The workaround is to move the window
(for example swap tiles or, with 1 tile, maximise it shortly to cover
top wibox).

Long story short, X protocol is complicated and sometimes ambiguous and
there are different expectations and points of view. Currently there is
a clash of expectations between awesome and Qubes GUI daemon. The blame
lies squarely between them and there is no-one who does it "wrong".

> - Since the xfce repo has not been updated in the past months I'm guessing
> you haven't changed anything that should break awesome from working when
> using qubes 3?

AFAIK there shouldn't be a problem, however I didn't test awesome on R3 yet.

> - Is the rc.lua you're describing required for awesome to work with qubes?

In principle, no. Awesome works just fine with default config as well as
any found on the Internet. However to get Qubes-specific GUI features
(most importantly the Trusted GUI, which is required for meaningful
security), you have to patch your favourite config. The patch for the
default config is included, it should be easy to port to another setup.

> - Is there anything else I should be aware of that you haven't described?

Floating/dock and similar hints somehow get lost, but I didn't found the
exact place. Most annoying is the split-gpg dialog, which occupies whole
tile, which is half the screen as designed. I close it fast enough not
to get annoyed by it.

> I understand that this is not production ready and am willing to live with
> some quirks/bugs here and there, it would just be nice to be able to use
> (proper) tiling again!

I'd be interested in your config once you polish it enough to get
merged. :)

> As you have said
> On Wednesday, March 11, 2015 at 11:55:19 AM UTC+1, Wojtek Porczyk wrote:

> > On Tue, Mar 10, 2015 at 08:08:49PM -0700, fowl...@riseup.net <javascript:>

> > wrote:
> > > > Here you are: git://git.qubes-os.org/woju/desktop-linux-awesome.git
> > > >
> > >
> > > This link redirects to the github now where I can find this repo.
> >
> > Uploaded to github:
> > https://github.com/woju/qubes-desktop-linux-awesome.git
> >
> > > > To remedy some of those issues, I will post my rc.lua somewhere on the
> > > > wiki. Default config in package is almost generic.
> > > >
> > >
> > > Have you worked out these issue and posted your rc.lua anywhere yet?
> >
> > I'm afraid no, I had more pressing things to do. Sorry for that.

[42t...@gmail.com]

any news on the tiling-qubes front? i'd really <3 to use i3wm (my fav tiling wm)
in qubes, but i'm not sure what would have to be patched in order to get it up and running
(e.g. with the right colors for the window borders and vm-name in the title)

this is currently the biggest reason for me not to use qubes as daily driver on my x220.

[David Hobach]

On 08/13/2015 12:22 PM, 42t...@gmail.com wrote:
> any news on the tiling-qubes front? i'd really <3 to use i3wm

> <https://i3wm.org/> (my fav tiling wm)

> in qubes, but i'm not sure what would have to be patched in order to get
> it up and running
> (e.g. with the right colors for the window borders and vm-name in the title)

Awesome works as discussed. i3wm would have to be patched in order to
make important Qubes features work (colors), yes.

It would also work by itself, if you can live without these features. I
wouldn't want to miss them though especially since they provide a big
security benefit.

[g.v.]

Hi all,

What is the current state of the patch? 

the repository
https://github.com/woju/qubes-desktop-linux-awesome
seems a bit dated, does it work currently? Do I have to merge it with up-to-date version of i3wm?

Btw, if something is not working is there anything I can do to make i3wm work? No promises though.

-- G.V.

четверг, 23 октября 2014 г., 14:02:47 UTC+4 пользователь andrea...@gmail.com написал:

[Outback Dingo]

On Sun, Dec 20, 2015 at 10:02 PM, g.v. <ovch....@gmail.com> wrote:

Hi all,

What is the current state of the patch? 

the repository
https://github.com/woju/qubes-desktop-linux-awesome
seems a bit dated, does it work currently? Do I have to merge it with up-to-date version of i3wm?

Btw, if something is not working is there anything I can do to make i3wm work? No promises though.

-- G.V.

you can literally replace plasma with xmonad..... and get full tiling without loosing the default kde config settings, i dont see a full need to replace the whole wm

 

четверг, 23 октября 2014 г., 14:02:47 UTC+4 пользователь andrea...@gmail.com написал:

Hi,

I've heard that there is a port of Awesome, usable as window manager in Dom0, available. Could you share this? I'd really like to get rid of KDE. :)

Thanks,

Andreas

--
You received this message because you are subscribed to the Google Groups "qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/c36de692-0218-4527-a30f-8aec009178f2%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Radoslaw Szkodzinski]

On Mon, Dec 21, 2015 at 1:02 AM, Outback Dingo <outbac...@gmail.com> wrote:
>
> On Sun, Dec 20, 2015 at 10:02 PM, g.v. <ovch....@gmail.com> wrote:
>>
>> Hi all,
>>
>> What is the current state of the patch?
>>
>> the repository
>> https://github.com/woju/qubes-desktop-linux-awesome
>> seems a bit dated, does it work currently? Do I have to merge it with
>> up-to-date version of i3wm?

This is a patch against Awesome WM not i3wm, should be fine against
Awesome 3.5.6.
Those are different WMs with different scripting.

The rc.lua parts should apply fine still and if not, should be trivial
to port. There were no API changes in the point release.
What it does is:
- add a prefix property and display it along application title
- add vm colors for the window borders
- replace menu with qubes-generated one

It's not quite a high performance implementation, calling python twice
to grab colors and vms and parsing desktop files. Could use some
caching and more direct Lua interface to Qubes libs.

The Lua 5.2 patch should be fine too, though you could instead use
Cmake 3.x and FindLua instead of versioned one - if 3.5.6 doesn't do
so already.

>>
>> Btw, if something is not working is there anything I can do to make i3wm
>> work? No promises though.
>>
>> -- G.V.
>
>
> you can literally replace plasma with xmonad..... and get full tiling
> without loosing the default kde config settings, i dont see a full need to
> replace the whole wm

Xmonad is a terrible by default, hard to extend WM.
Using very dense Haskell (with "interesting" data structure to
represent the WM) to implement anything nontrivial is painful.
You also pull GHC and extra libraries into the TCB. Good luck auditing it!

Plasma takes quite a bit of RAM still, even as slimmed down as in Qubes.
I can see a few reasons to replace it, including mediocre keyboard
support, higher memory use and ease of scripting.
Not to mention smaller TCB still. Lua is tiny and well audited, so is
Awesome and the default scripts.

--
Radosław Szkodziński

[Cyril LEVIS]

Hi,

Could you please explain me how build and install cleanly this awesome config?

Regards,

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Not sure about the current state of awesome support, but there was a
thread on this a while back:

https://groups.google.com/d/topic/qubes-users/BTajmuXSy_g/discussion

And woju has this repo:

https://github.com/woju/qubes-desktop-linux-awesome

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJXK5RpAAoJENtN07w5UDAwB/4QALB3TN0oqvKhd4JeG5DMBpjb
hCWiYeMPP5brdNGvZtlppoWSzncVDZf2GcP36PZKhUWO7GBO1kSjU6KJxVIprbl2
S/3ZNvslJnS2JFeU1CuU7EED+IHX5oMPgCIIZ/vhWtAk9cXcsXBGhCigikaDE+oq
ag9aC61Og5de9yBo1ebA6dbzj1I5DHZ1o9JWdMo8ZTV3fKt00hCT3QvJUT3CpB6y
cmpH//G6YaVuhpLhfkQ3S5uhswDcU2o/onxTXqiX/P0LO2ZVghZWyp3/atTMKeLj
5TP4yDj1u2QyxU9k8rhVLM3tlPeHINiDNyiWBLK4cyM2WeyvAW1Bf8zKt2bC0rX0
OvShPK2jI0tDelTm+OjB02/7/G0g1HQIGU1deFWTLCIJw92cwexXERyXr9JUZ0X8
NrssPJfbSyOzg7NIwKSYZvyml3b8HZ5OPRr1673LTMsaT8qZrPz73SmoEfVFIwqC
q/nJjD31REBNF3r35irl79bOKCIJgHq0G5hLVHAXwT/TTuwK84tYiMpnW8XBp0v2
EDN9hgIUaYc/ci+kUvoeE4tChXbBcyD9ud/AbrfPzWnkVhOQS3Fj3pCxCumYmolJ
/bM0EY7eV1VJqy+6vAgYzcIKpjJwqu6ZUAKQm/0WLD+Sk+PLK894+qVZcpaMH1w7
4xm6VJNh2U0NIxtBOU4+
=ivt+
-----END PGP SIGNATURE-----

[Cyril LEVIS]

Thx I will re-check that

[Peter Todd]

On Thu, May 05, 2016 at 02:27:50PM -0700, Cyril LEVIS wrote:
> Thx I will re-check that

Please let us know how that works out for you!

My only real issue with Qubes OS is I miss having a tiling window manager.

--
https://petertodd.org 'peter'[:-1]@petertodd.org

[Cyril LEVIS]

It works very well !

But, I have handly apply patch to the few files after install normal awesome rpm.
I have not a pretty build env for dom0 and can't build rpm from a fedora 23 because lua version is more recent than required.

-From patch file, awesomerc.lua is /etc/xdg/awesome/rc.lua, I have patch it but next, I have copy all dir /etc/xdg/awesome in ~/.config/; cleaner I think.

-I have 1px colored border and prefix in titlebar like [work], [dom0] etc...
-I will now try to tweak awesome config to autostart qubes-manager and do some keybinding.
- The autogenerated menu isn't enought large, i will try to tweak this.

Say me if I can help you to install it yet, next I think we can tweak config and share our tips.

Cyril

[Cyril LEVIS]

- I can't find how to enlarge size menu, and also, I search how to re-add "Add application entry" to the autogen menu.
- I have be able to change wallpaper
- I would like to be able to switch between app from same VM, i think we must do something with prefix and awesome tags?
- I search a way to start qubes-manager in systray only, do you have an idea?

[Mark Walters]

On Sat, 07 May 2016, Cyril LEVIS <levis...@gmail.com> wrote:
> - I can't find how to enlarge size menu, and also, I search how to re-add
> "Add application entry" to the autogen menu.
> - I have be able to change wallpaper
> - I would like to be able to switch between app from same VM, i think we
> must do something with prefix and awesome tags?
> - I search a way to start qubes-manager in systray only, do you have an
> idea?

I can't help with any of these, but this thread has prompted me to put
the minor bugfixes/tweaks I have made to

https://github.com/woju/qubes-desktop-linux-awesome

somewhere public. They are at

https://gitlab.com/markwalters1009/qubes-awesome-git

Since I have never actually built the rpm (I just patch/replace the
small number of lua files that are modified) my repository is just in
"installed filesystem layout".

But it might help with any tweaks you are doing.

(One thing I hadn't realised was how well mod4-p works for starting new
programs)

I have been using it for a few months and am basically happy with it.

Best wishes

Mark

> --
> You received this message because you are subscribed to the Google Groups "qubes-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel...@googlegroups.com.
> To post to this group, send email to qubes...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/a7456169-c883-48ec-a557-1dd9b6e3111e%40googlegroups.com.

[Cyril LEVIS]

Thanks :)
I have fetch your modification.
I have just a problem with the rc.lua and "if string.match '^disp[0-9]*$' part, i get an error on awesome restart : bad argument #1 to 'match' (string expected, got nil)

[Mark Walters]

Hi

> I have just a problem with the rc.lua and "if string.match '^disp[0-9]*$'
> part, i get an error on awesome restart : bad argument #1 to 'match'
> (string expected, got nil)

I think this must mean that awful.client.property.get(c, 'qubes_vmname')
is returning nil, which shouldn't happen (and doesn't on the fresh
install of the whole series I tried just before posting the link). Did
you apply the whole series, or just some of the patches? Did you have to
do any manual merging/patching? In particular, did you include the
qubes.manage(c) line earlier in that patch?

Best wishes

Mark

>

> Le samedi 7 mai 2016 19:35:18 UTC+2, Mark Walters a écrit :
>>
>>

>> On Sat, 07 May 2016, Cyril LEVIS <levis...@gmail.com <javascript:>>

>> an email to qubes-devel...@googlegroups.com <javascript:>.

>> > To post to this group, send email to qubes...@googlegroups.com

>> <javascript:>.

>> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/qubes-devel/a7456169-c883-48ec-a557-1dd9b6e3111e%40googlegroups.com.
>>
>> > For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups "qubes-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel...@googlegroups.com.
> To post to this group, send email to qubes...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/f0b56cf7-f0fa-4167-9de9-8cc5d0f42c7b%40googlegroups.com.

[Cyril LEVIS]

I missed ligne 375 in your rc.lua :)
I patched it manually ...

Thanks for your help!

Le jeudi 23 octobre 2014 12:02:47 UTC+2, andrea...@gmail.com a écrit :

[LEVIS Cyril]

Hi discover another problem.
It seems to be dbus problem.
I can't start awesome only at boot.
I must login to kde the logout and start awesome session to have all working properly.
If I start awesome only, for example vms with autostart stay with yellow status, and I can't then start app.
Also, I would like to my wlan networks applet in systray at start, but I must shutdown net cm, and restart it to get it. Maybe I must delai start of it?

[Mark Walters]

> It seems to be dbus problem.
> I can't start awesome only at boot.
> I must login to kde the logout and start awesome session to have all
> working properly.
> If I start awesome only, for example vms with autostart stay with yellow
> status, and I can't then start app.

This does work for me without any problems (I am on Qubes 3.0 if it
makes a difference)

> Also, I would like to my wlan networks applet in systray at start, but I
> must shutdown net cm, and restart it to get it. Maybe I must delai start of
> it?

I do know how to fix this: just run xterm (or any "non-systray" graphical
program) and then the network applet systray icon appears. Indeed, if
you run

qvm-run sys-net "xterm -e true"

It probably makes sense to add this to rc.lua file, until we know how to
fix it properly.

I think something similar happens if you log in to kde, open several
vm windows, and then logout and back into awesome. The windows don't
appear until you start open a new window from that vm, and then all the
windows for that vm appear.

Finally, for the net problem you can fix some problems by opening a
terminal in the sys-net vm, killing nm-applet and restarting it.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, May 09, 2016 at 07:48:39AM +0100, Mark Walters wrote:
>
> > It seems to be dbus problem.
> > I can't start awesome only at boot.
> > I must login to kde the logout and start awesome session to have all
> > working properly.
> > If I start awesome only, for example vms with autostart stay with yellow
> > status, and I can't then start app.
>
> This does work for me without any problems (I am on Qubes 3.0 if it
> makes a difference)
>
> > Also, I would like to my wlan networks applet in systray at start, but I
> > must shutdown net cm, and restart it to get it. Maybe I must delai start of
> > it?
>
> I do know how to fix this: just run xterm (or any "non-systray" graphical
> program) and then the network applet systray icon appears. Indeed, if
> you run
>
> qvm-run sys-net "xterm -e true"
>
> It probably makes sense to add this to rc.lua file, until we know how to
> fix it properly.
>
> I think something similar happens if you log in to kde, open several
> vm windows, and then logout and back into awesome. The windows don't
> appear until you start open a new window from that vm, and then all the
> windows for that vm appear.
>
> Finally, for the net problem you can fix some problems by opening a
> terminal in the sys-net vm, killing nm-applet and restarting it.

Does awesome support XDG standard for autostart applications
(/etc/xdg/autostart)? There is already qvm-run call to solve exactly
this problem.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXMEBsAAoJENuP0xzK19csFqwH/jniG6tkyBLpG4oKucDUFTZM
duTCM/qQ/Yu4HNTyDOEfwbJLHqq4Yqwrek2ZGXCqg2mXgQ16RHNra/Du6oY+mM1N
s4T4BdWTSB+ui+/IWXIrpzCpcDzWW7vgC3h3lWGqMjrKaJOF6AE9RuVFge5ntFF2
H83L8MFmDwspE6DG47+mCnc06ryWEoav4w6L3fpqtg1MKD99NWe7yKbrxbR66XKJ
cdKTM+3TZISDNomjseQ8A5ZNqJX6qCRS9vOIzmjtIngSXplKiR509WJtLOJxCqvs
cID02WRO+JuCYlq+Hv6Hm1omEw18phydeVEKRlz4+m4iiV1NmesRatqwQAAoZDc=
=h1oG
-----END PGP SIGNATURE-----

[LEVIS Cyril]

Hi, thanks for reply, 

@mark @marek I havn't my qubes laptop now, could you just say me which package provides this xdg autostart file?

My goal is to remove the maximun of kde dependencies and i had remove qubes-kde-*

Awesome seems to doesn't support xdg autostart (https://awesomewm.org/wiki/Autostart); I must so migrate those xdg autostart to lua?

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, May 09, 2016 at 08:04:42AM +0000, LEVIS Cyril wrote:
> Hi, thanks for reply,
> @mark @marek I havn't my qubes laptop now, could you just say me which
> package provides this xdg autostart file?

qubes-core-dom0. I guess you have this package installed ;)

> My goal is to remove the maximun of kde dependencies and i had remove
> qubes-kde-*
> Awesome seems to doesn't support xdg autostart (
> https://awesomewm.org/wiki/Autostart); I must so migrate those xdg
> autostart to lua?

According to that page, you can use dex.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXMGf5AAoJENuP0xzK19css7EH/3uvJlhgc3G0w/vF8gy8MtiE
TWL81s3jm04B0jlKrYLeobiDDWK4VG2jXpoP01xJ9yzYiH0V0ogruAHZYB8qloTH
cs+nIRDYDIWrhSIv06bdR7Xhx+nmLE0fY5+/SIC/WZwufWkCyK4Erv7fa1susVvl
zr1bDL/gbiWjDacaalerrJw0tiuESjrfYdu5Znia6GgngnTzGb3DctOeQJjOcqdB
bJ5wor8zcqERMLuJAtjB6ufshQ/Acaq2jbPzFAcK1PJo6WoS9OP7kuhku7JcGqjT
GCUCPq/omQ1VvLRllxKKEw+MNd7nJ0dgldCYwqlIbPnl8Z4+CagePDavYwqvZFk=
=2F6P
-----END PGP SIGNATURE-----

[LEVIS Cyril]

Le lun. 9 mai 2016 à 12:35, Marek Marczykowski-Górecki <marm...@invisiblethingslab.com> a écrit :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, May 09, 2016 at 08:04:42AM +0000, LEVIS Cyril wrote:
> Hi, thanks for reply,
> @mark @marek I havn't my qubes laptop now, could you just say me which
> package provides this xdg autostart file?

qubes-core-dom0. I guess you have this package installed ;)

Yes I think ^^  

> My goal is to remove the maximun of kde dependencies and i had remove
> qubes-kde-*
> Awesome seems to doesn't support xdg autostart (
> https://awesomewm.org/wiki/Autostart); I must so migrate those xdg
> autostart to lua?

According to that page, you can use dex.

Oh geat I miss-reading, searching for xdg in page, I will try to install dex-autostart and put this in rc.lua os.execute"dex-autostart -a -e Awesome" 

[Iestyn Best]

Sorry, just a side note.

Has anyone added this as an issue so that it can be tracked and developed potentially as an official Qubes option just like XFCE is?

[Mark Walters]

Hi

>> Awesome seems to doesn't support xdg autostart (
>> https://awesomewm.org/wiki/Autostart); I must so migrate those xdg
>> autostart to lua?
>
> According to that page, you can use dex.

This definitely seems the way to go. (I think using the autostart
packages will also solve a different hiccup I hide with awesome under
qubes -- resolution changes not being propogated to vms.)

There are couple of difficulties:

dex-autostart does not appear to be in fc20, only in fc21.

It has python3 as a dependency. I don't know whether installing python3
in dom0 is possible or desirable. (Alternatively patching dex to use
python2 might be possible).

Finally, how good does awesome support need to be before it could go
into qubes in some semi-official form (eg in the unstable repository)? I
have been running it for a few months now with the patches I posted
above (https://gitlab.com/markwalters1009/qubes-awesome-git) and am
essentially happy with it.

Best wishes

Mark

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Tue, May 10, 2016 at 08:36:06AM +0100, Mark Walters wrote:
>
> Hi
>
> >> Awesome seems to doesn't support xdg autostart (
> >> https://awesomewm.org/wiki/Autostart); I must so migrate those xdg
> >> autostart to lua?
> >
> > According to that page, you can use dex.
>
> This definitely seems the way to go. (I think using the autostart
> packages will also solve a different hiccup I hide with awesome under
> qubes -- resolution changes not being propogated to vms.)
>
> There are couple of difficulties:
>
> dex-autostart does not appear to be in fc20, only in fc21.
>
> It has python3 as a dependency. I don't know whether installing python3
> in dom0 is possible or desirable. (Alternatively patching dex to use
> python2 might be possible).

Not sure how to proceed for Qubes 3.1, but Qubes 3.2 (with dom0 based
on fc23) will be really soon. I hope to prepare first testable image
this week.

> Finally, how good does awesome support need to be before it could go
> into qubes in some semi-official form (eg in the unstable repository)? I
> have been running it for a few months now with the patches I posted
> above (https://gitlab.com/markwalters1009/qubes-awesome-git) and am
> essentially happy with it.

I think the only missing part is packaging it as rpms, to actually have
something to upload to the repository.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXMZq5AAoJENuP0xzK19csdJQH/0o3NFJ8WewE1BSfQ+ACLI3D
LdyGA4sCIfqcHaUyyHHWAP3wC+ElFOie0KFzZ8PnLl+FBN3euHzi8QgCbr5QGJ7I
UUkFqz7190FtRWhJTqU3c1hjUfemX0/OnXyHSRZA3HmnVlzekqd24KYFdOsRnUG6
+vsc1LEzvnMQs+wyq2eE+cNtHC5NjZKEC3JjXKRuL0RiKZi1PKu8j6toROchjArB
KaYsCzmm0+B8+J10537EAQTJTMCAMO+CheapLrEJXd4ONSNkjXKzhIzC6/KGdtlc
YGZZGNsDy8EBPuSiWAJGtFt+0bW4LW6XyXg/1YHsKqQTExUWFqLG2kYs0xe/iug=
=gMnT
-----END PGP SIGNATURE-----

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Yes, it's being tracked here:

https://github.com/QubesOS/qubes-issues/issues/1949

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXMkSkAAoJENtN07w5UDAwKFYP/jWkrRDQPaYtFfwwiMSAV6qK
hVpgL1QKYe4/arprVllVANCjZb7EeMmKHrUPflB/FJOpot05kI1wnnPDgcQ//kPC
dFUuWHiKA8wFdDrKNx89hjfmMvw+HmySPpvKoFPc0V1esnobeUIAqUL6XntMAXNy
0qqTAlEeNoIXetRM7XjkAOrbzcy19C+CzlzuKRMct9ZgkblONEIz1b1iCwjpNuP0
WsaUZxbJlKBUOD5AkEc0sHJSJCsl3c7p0zs3nRhMz5Y3huz4A6B26aX2iahEkOYq
9W1YOQRbJIbkD/T/btrfo5MQFfUllKfsYPEBpectAqw1N2aVAUz0C/6dm9Q6oaYz
Dy5zBPe9HhBssvHmKpWyN3Z53zxdCLdtgXRQie1kRfyNBSKurusm/Wmyzd7j951I
YWGdEN+QEqNHmocyH54qTvnIMgxjFgNIS0Kf8gaeM91TN7nHi204cNw1WcGkjYnO
QY4d0vZSfZBpCw5TirMQJRBY/dpl+f+k3++ZTfTidVNTUjUh88Sydpv08yynZDbt
ike02sYLRCrRc+9tP4v65Hx88ujdsBOBzUJsC2zNEvS0LXOBV1GnmRgGBxFi3drj
2ED2lBBUE4h0YQRUmqdvpDdg/bfOA24DEdV/ZSVhtCOOPqTEZh18UlRH7CyGMrrI
cslQSeOPESvmEPqVPqJD
=0ahn
-----END PGP SIGNATURE-----

[Mark Walters]

> Not sure how to proceed for Qubes 3.1, but Qubes 3.2 (with dom0 based
> on fc23) will be really soon. I hope to prepare first testable image
> this week.

That sounds great: I will test a dex/awesome mix when it comes out.

>> Finally, how good does awesome support need to be before it could go
>> into qubes in some semi-official form (eg in the unstable repository)? I
>> have been running it for a few months now with the patches I posted
>> above (https://gitlab.com/markwalters1009/qubes-awesome-git) and am
>> essentially happy with it.
>
> I think the only missing part is packaging it as rpms, to actually have
> something to upload to the repository.

Once I have got the above working I will try and package it (as in
branch the existing rpm with the extra patches etc)

Many thanks

Mark

[Cyril LEVIS]

Hi,

Another bug, when I plug a secondary screen, then apply a xrandr profile for work on both, I must restart awesome for get a clean display.

After the restart I get a qubes-manager error, saying error appear while wmctrl -R Qubes Manager

Do you have the same issue?

[Mark Walters]

On Thu, 12 May 2016, Cyril LEVIS <levis...@gmail.com> wrote:
> Hi,
>
> Another bug, when I plug a secondary screen, then apply a xrandr profile
> for work on both, I must restart awesome for get a clean display.
> After the restart I get a qubes-manager error, saying error appear while
> wmctrl -R Qubes Manager
>
> Do you have the same issue?

Hi

What are you doing about autostart stuff? I think this might be caused
by awesome not running
/etc/xdg/autostart/qubes-screen-layout-watches.desktop

We can run that manually for now, but in the longer term dex (or
similar) is probably the way to go.

Best wishes

Mark

[LEVIS Cyril]

I think this is another problem. 

I'm in the thread dex/awesome related, dex is installed and qubes layout notifier running.

[Mark Walters]

>>> Finally, how good does awesome support need to be before it could go
>>> into qubes in some semi-official form (eg in the unstable repository)? I
>>> have been running it for a few months now with the patches I posted
>>> above (https://gitlab.com/markwalters1009/qubes-awesome-git) and am
>>> essentially happy with it.
>>
>> I think the only missing part is packaging it as rpms, to actually have
>> something to upload to the repository.

I have now updated my tweaks to work with Qubes 3.2 rc3/ Fedora 23. I
have also made it use dex (called dex-autostart in fedora) to run the
xdg autostart desktop files, which fixes on key blocker in
https://github.com/QubesOS/qubes-issues/issues/1756

Finally I have packaged it all as rpms (or at least source which builds
the rpms).

The main rpm package repository is at
https://gitlab.com/markwalters1009/qubes-desktop-linux-awesome

However, rather than have the rpm apply lots of patches to upstream
awesome I have squashed most of them together. To see the separated out
changes I have a separate awesome-for-qubes source repository at

https://gitlab.com/markwalters1009/awesome-source-for-qubes

All the changes there are small so it would be easy to cherry-pick those
that are wanted.

NOTES

1) The last two commits in the rpm repository are not relevant: they are
there for users who want to build the rpm.

2) Broadly things seem to work as expected -- monitor layout changes,
screensaver etc, colours of windows etc

3) At the moment I have set it so dex autostarts all the things XFCE
does. This is probably close but not quite right, but I didn't want to
get into modifying the .desktop files.

Best wishes

Mark

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, Sep 11, 2016 at 10:12:47AM +0100, Mark Walters wrote:
>
> >>> Finally, how good does awesome support need to be before it could go
> >>> into qubes in some semi-official form (eg in the unstable repository)? I
> >>> have been running it for a few months now with the patches I posted
> >>> above (https://gitlab.com/markwalters1009/qubes-awesome-git) and am
> >>> essentially happy with it.
> >>
> >> I think the only missing part is packaging it as rpms, to actually have
> >> something to upload to the repository.
>
> I have now updated my tweaks to work with Qubes 3.2 rc3/ Fedora 23. I
> have also made it use dex (called dex-autostart in fedora) to run the
> xdg autostart desktop files, which fixes on key blocker in
> https://github.com/QubesOS/qubes-issues/issues/1756

Thanks!

> Finally I have packaged it all as rpms (or at least source which builds
> the rpms).
>
> The main rpm package repository is at
> https://gitlab.com/markwalters1009/qubes-desktop-linux-awesome
>
> However, rather than have the rpm apply lots of patches to upstream
> awesome I have squashed most of them together. To see the separated out
> changes I have a separate awesome-for-qubes source repository at
>
> https://gitlab.com/markwalters1009/awesome-source-for-qubes

That's ok if the patch is still short. But in such a case it's better to
include git log --oneline in the commit message.

> All the changes there are small so it would be easy to cherry-pick those
> that are wanted.
>
> NOTES
>
> 1) The last two commits in the rpm repository are not relevant: they are
> there for users who want to build the rpm.
>
> 2) Broadly things seem to work as expected -- monitor layout changes,
> screensaver etc, colours of windows etc
>
> 3) At the moment I have set it so dex autostarts all the things XFCE
> does. This is probably close but not quite right, but I didn't want to
> get into modifying the .desktop files.

That would start things designed to work specifically on XFCE. I think
it should be safe to place "Awesome" or sth like this. So only entries
designed to start in any environment (or specifically for Awesome) would
be started.

"Awesome" currently isn't registered menu specification:
https://specifications.freedesktop.org/menu-spec/latest/apb.html

Don't know if it worth to register it.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJX1UrRAAoJENuP0xzK19css0YIAJhi4vhBPLka268GxXSzIe7Y
Xb2NWEnsOA8wQAiXwuKkX6020fQ1ywsndQSa1ImQPtRzBSyVJNjRsRcq7gjWnAV7
9pfoLOG1FuLmCcw6DLCv5pZN7BuavH2B0Smoy1wREVH6gZ2t4ZAXZwI5bHLfNgt2
ecYYNgTQAfRzwygpecJdPGl7Xn7HF3CDOGlM8SSQp46hrJGXAMZFLRZLVP3GLOgj
QbVw8skoLadIckUm8xfZDHn+Vn4AQyeHBCntAzBkeYU/RlWvJ5JuowSjvhClXvnh
zeODMkMzcJo1cyhlyRPwhYZl/cRPr80T0Y3gofxdT5Y0tAdjVJGmE1vErO6OMNw=
=yBnj
-----END PGP SIGNATURE-----

[Mark Walters]

>> Finally I have packaged it all as rpms (or at least source which builds
>> the rpms).
>>
>> The main rpm package repository is at
>> https://gitlab.com/markwalters1009/qubes-desktop-linux-awesome
>>
>> However, rather than have the rpm apply lots of patches to upstream
>> awesome I have squashed most of them together. To see the separated out
>> changes I have a separate awesome-for-qubes source repository at
>>
>> https://gitlab.com/markwalters1009/awesome-source-for-qubes
>
> That's ok if the patch is still short. But in such a case it's better to
> include git log --oneline in the commit message.

Yes I will do that.

>> 3) At the moment I have set it so dex autostarts all the things XFCE
>> does. This is probably close but not quite right, but I didn't want to
>> get into modifying the .desktop files.
>
> That would start things designed to work specifically on XFCE. I think
> it should be safe to place "Awesome" or sth like this. So only entries
> designed to start in any environment (or specifically for Awesome) would
> be started.

At the moment there are some things that are XFCE only, that I would
like to start; in particular xscreensaver.

I think the following is a full list of things that the .desktop files
start for XFCE but not an unknown window manager

/usr/libexec/polkit-gnome-authentication-agent-1
xfce4-volumed
xss-lock xflock4
xfsettingsd
xscreensaver -no-splash

I am not sure which of these awesome should be calling -- I think
xscreensaver is clear, and only xfsettingsd looks obviously wrong. But
this is much deeper into Qubes/Fedora than I know about.


Best wishes

Mark

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Ok, lets keep it this way for now.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJX1a8PAAoJENuP0xzK19csAfgH/1w9zQkTcOSASRj5kxevptDx
cTBzuFd1IQN49EiZxaFAzGyK2Om5L+rYUFhq9sVeCOq8xvA3jwAapEXkdH85gJVc
49T5b6n69MrRv28MdazUNEN6UsbdkG+WkqytYzI2ny9GE+2lLVNuV2xH8hFukbPJ
kCcj/W0sNZbr4sf4U8rwj3JmAUc+RxnKZw5OsDeN7+x8B+KNBWX1ivbg+fK/o6+X
ifZmHZjF3jLwXPN5H3CzVkCcz7G++jo8hV8fNd/fhfG/4UawJk04F1vhRxcKjJte
uIClvgWK2GBi0Tu6OAo3BqfYMPou5AJv1/At+hlfLmUINweSJQNup2X18lAZdsg=
=E2kf
-----END PGP SIGNATURE-----

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, Sep 11, 2016 at 09:22:54PM +0200, Marek Marczykowski-Górecki wrote:
> On Sun, Sep 11, 2016 at 02:13:50PM +0100, Mark Walters wrote:
> >
> > >> Finally I have packaged it all as rpms (or at least source which builds
> > >> the rpms).
> > >>
> > >> The main rpm package repository is at
> > >> https://gitlab.com/markwalters1009/qubes-desktop-linux-awesome
> > >>
> > >> However, rather than have the rpm apply lots of patches to upstream
> > >> awesome I have squashed most of them together. To see the separated out
> > >> changes I have a separate awesome-for-qubes source repository at
> > >>
> > >> https://gitlab.com/markwalters1009/awesome-source-for-qubes
> > >
> > > That's ok if the patch is still short. But in such a case it's better to
> > > include git log --oneline in the commit message.
> >
> > Yes I will do that.

Are you going to change that commit, or only do that next time?
I'm asking because I want to build & upload the package to repository
and this is the last thing I'm waiting for.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJX2HjaAAoJENuP0xzK19csOnAH/ilHXP8q9w5f588+U1Bdhq9S
lr+5dSG53GkeAJElIuxpmNVnWgC1p8xBdGPPi4yKX0BGHmXWPtvrIEq4iik9cBr9
vcAl1nxiDflh1l4hsOPZWvo0g1307sqiDixb+PZfSDQxPPRZI7PMQySTASbZ4/Af
R2ivl0De3rFzAeasngVsY3MycKpsyy+wlRuaNNLHwOpDFtJPrKtHfnkblNhFKQXJ
L1JSTavo4X69fk18bn8Bd+CCCj1u8LmVfYOvVFxgu5ywPb2GVuUH4uygHzfnb9Cj
MCEgQDp/mJK+fa5ybbNn71UGawf+ApcfSouiHM8ktwwNp/5GV4bsGGUebdhZhcM=
=C2Vs
-----END PGP SIGNATURE-----

[Mark Walters]

> Are you going to change that commit, or only do that next time?
> I'm asking because I want to build & upload the package to repository
> and this is the last thing I'm waiting for.

Hi

Sorry I hadn't realised you were waiting on this. I have updated it
now. There were a couple of other minor (typo level) fixes that I did at
the same time. Note both repositories were rebased -- I hope that is OK.

Note you probably don't want the last two commits from the rpm
repository -- they are just so that I, and other users without signing
keys, can build the rpm.

Finally, as I think my git repository layout may be confusing I detail
what I have done below -- if it is not relevant then please ignore.

Best wishes

Mark

There is an awesome repository

https://gitlab.com/markwalters1009/awesome-source-for-qubes

with two branches: "master" which has all the split out patches, and
"for-rpm" which has the split out patches squashed into commits which will
form the individual patches in the rpm file. Following your suggestion
the squashed patch contains the git log --oneline output for the
squashed commits.

And there is the awesome-rpm repository at

https://gitlab.com/markwalters1009/awesome-source-for-qubes

This is basically a source rpm directory structure, and contains as
individual files the patches generated from the for-rpm repository
described above.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, Sep 14, 2016 at 10:04:21AM +0100, Mark Walters wrote:
>
> > Are you going to change that commit, or only do that next time?
> > I'm asking because I want to build & upload the package to repository
> > and this is the last thing I'm waiting for.
>
> Hi
>
> Sorry I hadn't realised you were waiting on this. I have updated it
> now. There were a couple of other minor (typo level) fixes that I did at
> the same time. Note both repositories were rebased -- I hope that is OK.
>
> Note you probably don't want the last two commits from the rpm
> repository -- they are just so that I, and other users without signing
> keys, can build the rpm.

That signing code in rpms-* targets is obsolete for a long time, so it's
ok to drop it from there.

Also I've included source verification step, please merge it back (it's
in my repo on github). I can't issue pull requests from github to
gitlab :(

Anyway, I've just uploaded it to current-testing repository for R3.2.
Thanks!

> Finally, as I think my git repository layout may be confusing I detail
> what I have done below -- if it is not relevant then please ignore.
>
> Best wishes
>
> Mark
>
> There is an awesome repository
>
> https://gitlab.com/markwalters1009/awesome-source-for-qubes
>
> with two branches: "master" which has all the split out patches, and
> "for-rpm" which has the split out patches squashed into commits which will
> form the individual patches in the rpm file. Following your suggestion
> the squashed patch contains the git log --oneline output for the
> squashed commits.
>
> And there is the awesome-rpm repository at
>
> https://gitlab.com/markwalters1009/awesome-source-for-qubes

https://gitlab.com/markwalters1009/qubes-desktop-linux-awesome

> This is basically a source rpm directory structure, and contains as
> individual files the patches generated from the for-rpm repository
> described above.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJX2TLhAAoJENuP0xzK19cs5LMIAJlmuuJ92wKzAVh7oy0zt+iB
QH3OoMUsDH21ewKC253CjbclZejBrLuNlGcE0QNTNajKFKLTAtqAaCVuyuwr5xYn
OkQ1+5O0QkzJCJzg0J8IOxpqgW5CE5aoOPwGElTS3uoRY68afHMcWioIRjXLqbMX
O9BnCggztp76RXwQK4iqHdE6ahigkBqnkeFGHphsZml7n1SAglSz73rSeemyXPov
Yl2B2rJ10BJbZBZAT7/IbZdDlcMZYleaEnfrErYq9IECCV2+foIOb4rBVRDPKZYC
M/6l72moKTYuiO8AvhUvjZtzwSp+TDPgNF8hqKab62vA7A9O8gFHuNWdi7mTrwU=
=x0jg
-----END PGP SIGNATURE-----

[Mark Walters]

> Also I've included source verification step, please merge it back (it's
> in my repo on github). I can't issue pull requests from github to
> gitlab :(
>
> Anyway, I've just uploaded it to current-testing repository for R3.2.
> Thanks!

That's great, many thanks.

I have pulled your changes back to the gitlab repository, and I have
added a note there recommending the main qubes one.

Best wishes

Mark