[Bug 1729910] Re: lp ignores ~/.cups/lpoptions in 17.10
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729910 Title: lp ignores ~/.cups/lpoptions in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1729910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729910] Re: lp ignores ~/.cups/lpoptions in 17.10
I confirm that the problem is fixed in version 2.2.4-7ubuntu3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729910 Title: lp ignores ~/.cups/lpoptions in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1729910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515446] Re: network file systems in FSTAB no longer mount at boot with NetworkManager
I can confirm that the bug is fixed in network-manager 1.0.4-0ubuntu5.3. Thanks! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515446 Title: network file systems in FSTAB no longer mount at boot with NetworkManager To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1515446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217835] [NEW] Kernel Oops while mounting via NFSv4
Public bug reported: The Kernel Oops occurred during system startup, apparently while mounting an NFSv4 share. The entry in /etc/fstab is: fqdn_of_nfs_server:/ /cfs nfs4 sec=krb5p 0 0 'mountall --daemon', which was started via /etc/init/mountall.conf, is still running (since several hours). Usually the mount succeeds, however sometimes with a delay of roughly 60 seconds. In order to investigate the cause of the delay, the machine was rebooted a few hundred times, up to now without any Oops. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 Date: Wed Aug 28 11:13:08 2013 MarkForUpload: True ProcEnviron: LC_CTYPE=de_DE.ISO-8859-1 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-raring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kernel-oops precise ** Attachment added: "kern.log" https://bugs.launchpad.net/bugs/1217835/+attachment/3791497/+files/kern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217835 Title: Kernel Oops while mounting via NFSv4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1217835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1101292] Re: NFSv4 regression in 3.4-rc1 causes Invalid Argument on chown/grp
On Fri, Mar 08, 2013 at 05:30:17PM -, Dave Chiluk wrote: > I have verified this null-termination occurs in quantal even with a > precise nfsv4 server with no security set. I have also verified that > this is still the same in raring, and appears to be be maintained in > upstream. I read through the RFC, and it does not appear to be > incorrect in reference to the protocol *(as far as I read it). I didn't find a definitive answer for that in the RFC, but to me it makes no sense to null-terminate a string if the length is given, especially when the length includes the null-byte. But let's see what the experts say. > Just in case Rolf Anders, can you please attach a tcpdump of a single > run of chown or chgrp? Attached. Thank you ** Attachment added: "chgrp.cap" https://bugs.launchpad.net/bugs/1101292/+attachment/3564138/+files/chgrp.cap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101292 Title: NFSv4 regression in 3.4-rc1 causes Invalid Argument on chown/grp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1101292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1101292] Re: NFSv4 regression in 3.4-rc1 causes Invalid Argument on chown/grp
The problem with mounting was my fault: I only installed 'linux-image' and not 'linux-image-extra' which contains rpcsec_gss_krb5.ko. That module is needed for mounting with 'sec=krb5'. So I was able to test 3.8.0-030800rc5-generic from http://kernel.ubuntu.com/~kernel-ppa/mainline. Unfortunately the bug is still there: $ uname -r 3.8.0-030800rc5-generic $ chgrp -v groupname newfile chgrp: changing group of `newfile': Invalid argument failed to change group of `newfile' from groupname to groupname $ chown -v username newfile chown: changing ownership of `newfile': Invalid argument failed to change ownership of `newfile' from username to username -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101292 Title: NFSv4 regression in 3.4-rc1 causes Invalid Argument on chown/grp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1101292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1101292] Re: NFSv4 regression in 3.4-rc1 causes Invalid Argument on chown/grp
I'm the original reporter of this problem and would like to add a possibly helpful detail. I did wireshark traces and found that in the failing case the length of the group name in the SETATTR call is given wrongly: Opcode: SETATTR (34) stateid [StateID Hash: 0xafa9] seqid: 0x Data: obj_attributes attrmask recc_attr: FATTR4_OWNER_GROUP (37) fattr4_owner_group: groupn...@domainname.com length: 25 In the working case the length is given correctly as 24 (the actual group name has the same length as "groupn...@domainname.com"). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101292 Title: NFSv4 regression in 3.4-rc1 causes Invalid Argument on chown/grp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1101292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041377] Re: mountall ignores NFS mount option "timeo"
mountall 2.36.3 solves the problem (tested on Ubuntu 12.04). Thanks! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041377 Title: mountall ignores NFS mount option "timeo" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1041377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041377] Re: mountall ignores NFS mount option "timeo"
** Attachment added: "rz-t-apport.mountall.txt" https://bugs.launchpad.net/bugs/1041377/+attachment/3275880/+files/rz-t-apport.mountall.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041377 Title: mountall ignores NFS mount option "timeo" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1041377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041377] [NEW] mountall ignores NFS mount option "timeo"
Public bug reported:
If the mount option "timeo" is specified for an NFS mount in /etc/fstab,
mountall does not pass it to mount.nfs. The bug is in the function
cut_options() in mountall.c. It is called with the following arguments:
opts = cut_options (NULL, mnt, "showthrough", "optional",
"bootwait", "nobootwait", "timeout",
NULL);
Although it should only remove the specified options, it also removes
any option that is a prefix of one of those, e.g. "timeo".
The call to strncmp() in line 661 compares only up to the length of the
option from the fstab, without comparing the length of both strings.
Hence I propose the following patch:
--- mountall-2.36/src/mountall.c.orig 2012-08-24 20:25:07.445892095 +0200
+++ mountall-2.36/src/mountall.c2012-08-24 21:29:10.098595843 +0200
@@ -658,7 +658,8 @@
va_copy (options, args);
while ((option = va_arg (options, const char *)) != NULL)
{
- if (j && ! strncmp (opts + i, option, j))
+ if (j && option[j] == '\0'
+ && ! strncmp (opts + i, option, j))
break;
}
va_end (options);
** Affects: mountall (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041377
Title:
mountall ignores NFS mount option "timeo"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1041377/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
