Processed: merge 846950 and 849608

2016-12-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 846950 849608 Bug #846950 [nfs-common] nfs-common: RPCGSSDOPTS not replicated to /run/sysconfig/nfs-utils Bug #846950 [nfs-common] nfs-common: RPCGSSDOPTS not replicated to /run/sysconfig/nfs-utils Marked as found in versions nfs-utils/1:1

Bug#846950: Merging with #849608

2016-12-28 Thread Felix Lechner
Hi, Sebastian's point is also addressed in #849608 ('keytab location is hardcoded to /etc/krb5.keytab'). Pursuant to the maintainer's request from December 15, I will try to merge both reports. Best regards, Felix

Bug#849608: nfs-common: For rpc.gssd, keytab location is hardcoded to /etc/krb5.keytab

2016-12-28 Thread Felix Lechner
Package: nfs-common Version: 1:1.3.4-2 Severity: normal Tags: patch Hi, Someone using a keytab other than /etc/krb5.keytab must pass the location with "-k" to rpc.gssd. Currently, those arguments are not collected from /etc/defaults/nfs-common. (A similar point is addressed in report #846950.) As

Bug#849572: vsyscall == none breaks wheezy chroots

2016-12-28 Thread Guido Günther
Package: src:linux Version: 4.9~rc8-1~exp1 Severity: normal Hi, I'm seeing [ 105.205620] dpkg[7064] vsyscall attempted with vsyscall=none ip:ff600400 cs:33 sp:7ffc52a8bc08 ax:ff600400 si:428720 di:7ffc52a8bc20 [ 105.205622] dpkg[7064]: segfault at ff600400 ip

Bug#849474: consolation and kernel issue

2016-12-28 Thread Adam Borowski
On Wed, Dec 28, 2016 at 09:29:11AM +0100, Adam Borowski wrote: > However, all my testing so far was on vgacon (because nvidia). When on > nouveau, it locks up immediately, after 6 iterations. Tried on 4.10-rc1+ > (current linus/master). > > Same on a crap armhf laptop using 3.0 vendor kernel, pr

Bug#849474: consolation and kernel issue

2016-12-28 Thread Adam Borowski
On Wed, Dec 28, 2016 at 12:50:20AM +0100, Bill Allombert wrote: > On Wed, Dec 28, 2016 at 12:42:33AM +0100, Adam Borowski wrote: > > On Tue, Dec 27, 2016 at 10:22:34PM +0100, Bill Allombert wrote: > > > This can be automated using the attached program > > > (warning, this is slightly dangerous sinc