Thanks for the info.
On Sunday, September 11, 2016 at 9:00:46 PM UTC+2, Marek
Marczykowski-Górecki wrote:
>
> Take a look at discussion here:
> https://github.com/QubesOS/qubes-issues/issues/1784
>
I went through the discussion. Is there anything specific I should note?
In short: no,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
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
> >>
I've done some improvement by configuring foreground colors of yellow,
green and orange VMs to black. Borders of inactive windows are not fixed
(that is, they still have the same color as in inactive windows), but I am
not sure if there is a way to fix them.
Tested with Breeze and it works
>> 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
-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
>>> 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
>>>
As explained here, https://github.com/netblue30/firejail/issues/770 adding
'-nolisten local' allows for easily isolating x11 or sandboxing an app from
it. i cant see any advantage to having both the unix domain socket and the
abstract socket.
this should be upstream. but, that change would
