>
> > Any recommendations for a better panel?
>
> If you weren't on the list about 6 months ago, there was some
> wonderfully enlightening discussion about de's and wm's that long ago
> or more. I can find the exact dates if you want so you can find it in
> the archives.
Ah now you say that, i
On Sat, 23 May 2020, Hendrik Boom wrote:
> Where does LXQt keep ist panel config?
>
~/.config/lxqt/panel.conf
Jim
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
On Sat, 2020-05-23 at 19:54 +0100, Jim Jackson wrote:
> Generally, why does apparmor get installed on a dist-upgrade, when
> it
> wasn't there initially? It isn't as if it's a new "thing".
That's a good question.
> I got it
> on my ascii -> beowulf upgrade, and removed it.
That was the first
On Sat, 2020-05-23 at 21:08 +0300, Dimitris via Dng wrote:
> bug report link, was about /var/cache, not /var/log (?).. anyway, the
>
> default apparmor profile has this :
>
>
>
> # some people like to put logs in /var/log/named/ instead of having
>
> # syslog do the heavy lifting.
>
> /
On Sat, May 23, 2020 at 07:54:55PM +0100, Jim Jackson wrote:
>
> Generally, why does apparmor get installed on a dist-upgrade, when it
> wasn't there initially? It isn't as if it's a new "thing". I got it
> on my ascii -> beowulf upgrade, and removed it.
>
> My desktop was LXQt and the upgrade i
On 5/23/20 9:54 PM, Jim Jackson wrote:
> Generally, why does apparmor get installed on a dist-upgrade, when it
> wasn't there initially? It isn't as if it's a new "thing".
in repos since wheezy.. from beowulf/buster on, it is enabled by default:
https://wiki.debian.org/AppArmor/HowToUse#Enable_A
Anno domini 19:54:55 Sat, 23 May 2020 +0100 (BST)
Jim Jackson scripsit:
>
> Generally, why does apparmor get installed on a dist-upgrade, when it
> wasn't there initially? It isn't as if it's a new "thing". I got it
> on my ascii -> beowulf upgrade, and removed it.
>
> My desktop was LXQt and t
Generally, why does apparmor get installed on a dist-upgrade, when it
wasn't there initially? It isn't as if it's a new "thing". I got it
on my ascii -> beowulf upgrade, and removed it.
My desktop was LXQt and the upgrade ignored some customisations. Among
other minor iritants the LXQt-panel de
On 5/23/20 8:42 PM, 'smee via Dng wrote:
>
> The workaround mentioned in the bug report for is to add explicit
> permissions in /etc/apparmor.d/local/usr.sbin.named by adding a line to
> that file with the path to the problem file and the permissions. In
> this case rwk for read/write/lock. In my
Hello list,
This issue has a workaround that works fine but I want to throw this
info out there in case it's useful to anyone else or to the devs.
I've got a couple dns servers that I installed initially with ascii.
After upgrading to Beowulf, bind9 wouldn't start any more. Turned out
to be a p
10 matches
Mail list logo