package awesome tiling manager for easy install from dom0

[mfc]

for tech-savvy users who like tiling managers, would be nice to have the existing awesome desktop environment @woju uses packaged for easy installation from dom0:

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

This should not be an option on first install / firstboot (ISO is already too big and tech-savvy folks can have an extra hurdle), just from qubes repos from dom0. If it is a bunch of effort or not maintained anymore then we can scrap the idea.

[bnvk]

👍 to this suggestion- the number of tech-savvy people who have cited "no tiling window manager" as a reason to NOT try Qubes is quite high by my count. While not our largest target user base, pleasing these users seems a smart strategy!

[bnvk]

👍 to this suggestion- the number of tech-savvy people who have cited "no tiling window manager" as a reason to NOT try Qubes is quite high by my count. While not our largest target user base, pleasing these users seems a smart strategy!

[petertodd]

+1

I personally held off getting Qubes for ages because of this reason, and not having a tiling WM is still a big downside for me. I tried installing awesome myself from that package but haven't yet figured it out - I've never dealt with the RPM package system before using Qubes.

[petertodd]

+1

I personally held off getting Qubes for ages because of this reason, and not having a tiling WM is still a big downside for me. I tried installing awesome myself from that package but haven't yet figured it out - I've never dealt with the RPM package system before using Qubes.

[minad]

I just installed qubes with i3. @SietsevanderMolen made some patches, see https://github.com/SietsevanderMolen/i3-qubes. The patches are simple and it works really well.

What are the requirements to get an additional wm into qubes?

[minad]

I just installed qubes with i3. @SietsevanderMolen made some patches, see https://github.com/SietsevanderMolen/i3-qubes. The patches are simple and it works really well.

What are the requirements to get an additional wm into qubes?

[marmarek]

If that really works, I think that's all. Next steps (on our side):

• review and test it out
• include in official repository

Thanks @SietsevanderMolen!

[marmarek]

If that really works, I think that's all. Next steps (on our side):

• review and test it out
• include in official repository

Thanks @SietsevanderMolen!

[minad]

Hi,

Sounds good! There was one thing I was wondering about - the qubes dom0 login/logout procedure and session management in KDE.

Is it documented somewhere which qubes specific tasks have to be executed at startup and logout in dom0?

Currently when I logout and login again with i3 the VMs are still running but marked as transient. Then I have to execute 'qvm-rum --all true' to get them to the running state again. So what would be the right way to avoid this hack?

Am 13. Mai 2016 12:19:59 MESZ, schrieb "Marek Marczykowski-Górecki" notifications@github.com:

If that really works, I think that's all. Next steps (on our side):

• review and test it out
• include in official repository

Thanks @SietsevanderMolen!

---

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#1756 (comment)

[minad]

Hi,

Sounds good! There was one thing I was wondering about - the qubes dom0 login/logout procedure and session management in KDE.

Is it documented somewhere which qubes specific tasks have to be executed at startup and logout in dom0?

Currently when I logout and login again with i3 the VMs are still running but marked as transient. Then I have to execute 'qvm-rum --all true' to get them to the running state again. So what would be the right way to avoid this hack?

Am 13. Mai 2016 12:19:59 MESZ, schrieb "Marek Marczykowski-Górecki" notifications@github.com:

If that really works, I think that's all. Next steps (on our side):

• review and test it out
• include in official repository

Thanks @SietsevanderMolen!

---

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#1756 (comment)

[marmarek]

Handle freedesktop standard of autostart applications
(/etc/xdg/autostart etc) - that's all. There should be no DE-specific in
that matter.

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?

[marmarek]

Handle freedesktop standard of autostart applications
(/etc/xdg/autostart etc) - that's all. There should be no DE-specific in
that matter.

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?

[minad]

Perfect. Thx. I will try that.

Am 13. Mai 2016 17:15:45 MESZ, schrieb "Marek Marczykowski-Górecki" notifications@github.com:

Handle freedesktop standard of autostart applications
(/etc/xdg/autostart etc) - that's all. There should be no DE-specific
in
that matter.

[minad]

Perfect. Thx. I will try that.

Am 13. Mai 2016 17:15:45 MESZ, schrieb "Marek Marczykowski-Górecki" notifications@github.com:

Handle freedesktop standard of autostart applications
(/etc/xdg/autostart etc) - that's all. There should be no DE-specific
in
that matter.

[marmarek]

awesome fails with:

/usr/share/awesome/lib/qubes.lua:100: bad argument #2 to 'format' (number has no integer representation)

@woju

[marmarek]

awesome fails with:

/usr/share/awesome/lib/qubes.lua:100: bad argument #2 to 'format' (number has no integer representation)

@woju

[marmarek]

@woju it still doesn't support xdg autostart, which is mandatory - for example to start gui daemons.

[marmarek]

@woju it still doesn't support xdg autostart, which is mandatory - for example to start gui daemons.

[adrelanos]

Marek Marczykowski-Górecki:

@woju it still doesn't support xdg autostart, which is mandatory - for example to start gui daemons.

With newer systemd (from stretch) you might be able to port from xdg
autostart to systemd --user services.

[adrelanos]

Marek Marczykowski-Górecki:

@woju it still doesn't support xdg autostart, which is mandatory - for example to start gui daemons.

With newer systemd (from stretch) you might be able to port from xdg
autostart to systemd --user services.

[marmarek]

With newer systemd (from stretch) you might be able to port from xdg autostart to systemd --user services.

It's about dom0, so stretch doesn't apply (at least for now). But systemd --user does.
I've been reluctant to use it anywhere, to not introduce another requirement (making it even harder to migrate to some other distribution in the future for example). But if we consider systemd --user widespread enough, this may indeed solve the problem. @woju what do you think?

[marmarek]

With newer systemd (from stretch) you might be able to port from xdg autostart to systemd --user services.

It's about dom0, so stretch doesn't apply (at least for now). But systemd --user does.
I've been reluctant to use it anywhere, to not introduce another requirement (making it even harder to migrate to some other distribution in the future for example). But if we consider systemd --user widespread enough, this may indeed solve the problem. @woju what do you think?

[marmarek]

unrelated: @woju build fails on travis: https://travis-ci.org/QubesOS/qubes-desktop-linux-awesome/builds/141500900 any idea why? it works on my system...

[marmarek]

unrelated: @woju build fails on travis: https://travis-ci.org/QubesOS/qubes-desktop-linux-awesome/builds/141500900 any idea why? it works on my system...

[kulinacs]

What are the current roadblocks on getting this packaged? Just the travis build? Or is the xdg autostart problem still a problem?

[kulinacs]

What are the current roadblocks on getting this packaged? Just the travis build? Or is the xdg autostart problem still a problem?

[andrewdavidwong]

Update from Mark Walters on qubes-devel

[andrewdavidwong]

Update from Mark Walters on qubes-devel

[marmarek]

It's done.

[marmarek]

It's done.