Package: nfs-kernel-server
Version: 1:1.3.4-2.1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I have recently upgraded my NFS server from Jessie to Stretch. It was
the last system on my network that needed to be upgraded. After the
upgrade, I found that NFSv4 was nearly un
On Wed, 2017-11-01 at 15:38 +0100, Evgeni Golov wrote:
> Ohai,
>
> On Wed, Nov 01, 2017 at 12:00:12PM -0200, Antonio Terceiro wrote:
> > > lxc-start 20171101123914.655 ERRORlxc_apparmor -
> > > lsm/apparmor.c:apparmor_process_label_set:220 - If you really want to
> > > start this conta
Relevant upstream commit merge:
https://github.com/torvalds/linux/commit/89db69d670a11274c323af48479841d3d765bd49
Not tested it yet, but I'll try to report back.
--
Andrew Chadwick
Processing commands for cont...@bugs.debian.org:
> severity 880441 serious
Bug #880441 [src:linux] linux-image-4.13.0-1-amd64: silently enabled AppArmor
breaks other programs
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
-
Ohai,
On Wed, Nov 01, 2017 at 12:00:12PM -0200, Antonio Terceiro wrote:
> > lxc-start 20171101123914.655 ERRORlxc_apparmor -
> > lsm/apparmor.c:apparmor_process_label_set:220 - If you really want to start
> > this container, set
> > lxc-start 20171101123914.655 ERRORlxc_appar
Control: retitle -1 lxc: cannot start container with kernel 4.13.10
On Wed, Nov 01, 2017 at 11:32:31AM -0200, Antonio Terceiro wrote:
> Package: lxc
> Version: 1:2.0.9-3
> Severity: serious
>
> I'm filing this in lxc initially as I don't know exactly where the issue
> is yet. We will probably wan
Control: tag -1 serious
On Tue, 2017-10-31 at 17:21 +, Ben Hutchings wrote:
> On Tue, 2017-10-31 at 17:10 +0100, Christoph Anton Mitterer wrote:
> > The severity would have shown people which haven't upgraded, that there
> > are issues... :-(
> >
> >
> > On Tue, 2017-10-31 at 16:01 +, Be
Source: linux
Version: 4.14~rc7-1~exp1
Severity: important
Control: affects -1 cifs-utils
Control: affects -1 linux-image-amd64
Control: found -1 4.13.4-2
Control: notfound -1 4.12.6-1
When using multiuser cifs on domain members with Kerberos
authorization, user accesses to mounted file systems fa
Processing control commands:
> affects -1 cifs-utils
Bug #880504 [src:linux] multiuser cifs: spurious ETOOLONG, file writes & dir
reads broken since 4.12.6 [message: "File name too long"]
Added indication that 880504 affects cifs-utils
> affects -1 linux-image-amd64
Bug #880504 [src:linux] multiu
Package: src:linux
Version: 3.16.43-2+deb8u5
Severity: important
Tags: upstream patch
Dear Maintainer,
What led up to the situation?
- Use of docker containers, causes the system to become non-responsive or
crash with kernel panic.
What exactly did you do (or not do) that was effective (or ine
On Wed, Oct 25, 2017 at 11:45:52AM +0200, Sedat Dilek wrote:
> [ Please CC me - I am not subscribed to lxc-users and debian-kernel MLs ]
>
> Hi,
>
> I am playing with LXC and OverlayFS.
>
> The Debian-kernel shipped with stretch64 fails when using lxc-copy for
> a snapshot.
> Later I tried the l
Package: lxc
Version: 1:2.0.9-3
Severity: serious
I'm filing this in lxc initially as I don't know exactly where the issue
is yet. We will probably want to reassign it.
Something other than lxc itself changed recently in unstable which makes
lxc not able to start a Debian container:
# lxc-start
One can also sidestep writing to /tmp in the script in
/lib/systemd/system-sleep/:
#!/bin/bash
### Ensure that the frequency is restored upon resuming from suspend
# The array to store frequencies:
declare -a frequencies
# Number of processors minus 1:
N=$((`nproc --all`-1))
case "${1}" in
pos
On 01.11.2017 13:38, Ben Hutchings wrote:
On Tue, 31 Oct 2017 13:25:11 +0100 Leon Meier wrote:
On 31.10.2017 11:39, Debian Bug Tracking System wrote:
Yes, but that doesn't mean we can do anything about it.
Why not simply re-issue the request setting the performance-level after
resume?
The
On Tue, 31 Oct 2017 13:25:11 +0100 Leon Meier wrote:
> On 31.10.2017 11:39, Debian Bug Tracking System wrote:
> > Yes, but that doesn't mean we can do anything about it.
>
> Why not simply re-issue the request setting the performance-level after
> resume?
The driver does that.
Ben.
--
Ben Hu
On Wed, 2017-11-01 at 13:02 +0100, Leon Meier wrote:
> On 31.10.2017 13:25, Leon Meier wrote:
> > On 31.10.2017 11:39, Debian Bug Tracking System wrote:
> > > Yes, but that doesn't mean we can do anything about it.
> >
> > Why not simply re-issue the request setting the performance-level after
>
On 31.10.2017 13:25, Leon Meier wrote:
On 31.10.2017 11:39, Debian Bug Tracking System wrote:
Yes, but that doesn't mean we can do anything about it.
Why not simply re-issue the request setting the performance-level after
resume?
You could at least suggest a script similar to the following
Hi,
I'm not sure if the preferred direction is many small firmware packages
(e.g. see the microcode firmware packages for intel, amd, ...), or if
firmware-nonfree maintained by kernel team is a good place to have all of
it in one place.
Is firmware-nonfree the right place for arm cpu/boot loader
Your message dated Wed, 01 Nov 2017 11:41:00 +0100
with message-id <87k1zab7sz@turtle.gmx.de>
and subject line Re: Bug#836411: linux-image-4.7.0-1-amd64: hibernation fails,
regression from 4.6
has caused the Debian Bug report #836411,
regarding linux-image-4.7.0-1-amd64: hibernation fails, reg
19 matches
Mail list logo
