[Bug 2044657] Re: Multiple data corruption issues in zfs
Actually, it may not be an issue even for Jammy HWE. My copy shows block cloning as an option that's off. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: Multiple data corruption issues in zfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044657] Re: Multiple data corruption issues in zfs
This issue is different. It's another problem with block copy. But that's known to still be an issue. It's why block copy is disabled in 2.2.1. This is only an issue for the Jammy HWE, which has 2.2.0. No one should be shipping 2.2.0 with anything. It should be replaced with 2.2.1 at least. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: Multiple data corruption issues in zfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056335] [NEW] /etc/nfsmount.conf doesn't work for servers
Public bug reported: 24.04 nightly from March 5. This is a regression from 20.04. The same problem is present in 22.04 /etc/nfsmount.conf allows specifications of per-server options. with the following: [ NFSMount_Global_Options ] vers=3 rsize=65536 wsize=393216 [ Server "communis.lcsr.rutgers.edu" ] vers=4.2 [ Server "eternal.lcsr.rutgers.edu" ] vers=4.2 communis.lcsr.rutgers.edu uses version 3. eternal.lcsr.rutgers.edu uses 4.2. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nfs-common 1:2.6.3-3ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 .etc.nfs.conf.d.contexttime.conf: [gssd] context-timeout=600 .etc.request-key.d.id_resolver.conf: create id_resolver * * /usr/sbin/nfsidmap -t 600 %k %d ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 6 10:11:48 2024 InstallationDate: Installed on 2024-03-05 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240305) NFSMounts: NFSv4Mounts: /common/home communis.lcsr.rutgers.edu:/common/home nfs4 rw,nosuid,nodev,relatime,vers=4.2,rsize=65536,wsize=393216,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=krb5,clientaddr=128.6.60.252,local_lock=none,addr=172.17.11.218 SourcePackage: nfs-utils SyslogNFS: Mar 05 13:28:08 basel.cs.rutgers.edu rpc.gssd[11676]: event_dispatch() returned 0! Mar 06 09:51:57 basel.cs.rutgers.edu rpc.statd[37785]: Version 2.6.3 starting Mar 06 09:51:57 basel.cs.rutgers.edu rpc.statd[37785]: Flags: TI-RPC Mar 06 09:51:57 basel.cs.rutgers.edu rpc.statd[37785]: Failed to read /var/lib/nfs/state: Success Mar 06 09:51:57 basel.cs.rutgers.edu rpc.statd[37785]: Initializing NSM state UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.nfs-common: 2024-03-05T13:25:47.124322 ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble regression-release ** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056335 Title: /etc/nfsmount.conf doesn't work for servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2056335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056217] Re: nmcli regression: can't set IPV6 token
** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056217 Title: nmcli regression: can't set IPV6 token To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2056217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056217] [NEW] nmcli regression: can't set IPV6 token
Public bug reported: 24.04 nightly, downloaded Mar 5. network-manager 1.45.90-1ubuntu1 In network manager, if you try to set ipv6.token, when you save it says Error: connection verification failed: ipv6.token: only makes sense with EUI64 address generation mode This is the same as under 22.04. However under 22.04 the solution is setipv6.addr-gen-mode eui64 along with the token. In 24.04 when you save you get Error: Failed to save 'netplan-enp3s0' (6effa1b1-280b-3785-9b52-c723b445fb3e) connection: failed to update connection: netplan: YAML translation failed: Error in network definition: enp3s0: ipv6-address-generation and ipv6-address-token are mutually exclusive There doesn't seem to be any combination involving the token that works. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Tue Mar 5 14:14:01 2024 InstallationDate: Installed on 2024-03-05 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240305) IpRoute: default via 128.6.60.1 dev enp3s0 proto dhcp src 128.6.60.252 metric 100 128.6.60.0/24 dev enp3s0 proto kernel scope link src 128.6.60.252 metric 100 IwConfig: lono wireless extensions. enp3s0no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected full limited /org/freedesktop/NetworkManager/Devices/2 netplan-enp3s0 6effa1b1-280b-3785-9b52-c723b445fb3e /org/freedesktop/NetworkManager/ActiveConnection/2 lo loopback connected (externally) unknown unknown /org/freedesktop/NetworkManager/Devices/1 lo b04a6583-06fa-4685-bbd9-05171997cf93 /org/freedesktop/NetworkManager/ActiveConnection/1 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled missing enabled missing enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056217 Title: nmcli regression: can't set IPV6 token To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2056217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044657] Re: Multiple data corruption issues in zfs
Since I was just referenced, note that I wouldn't favor putting 2.2 into Jammy. I would, however, prefer to see the latest 2.1.x. 2.2 is still seeing a substantial number of bug fixes. It will probably be ok by the release date of 24.04, but I still wouldn't change major versions for Jammy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: Multiple data corruption issues in zfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - rpc-statd not started after minor upgrade
Also, can I interest you in 1918312 for 22.04? Everyone agrees it's a security issue. It has a well-known 2-line fix (our version is 4 lines), which we've been using in production for over a year. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails - rpc-statd not started after minor upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - rpc-statd not started after minor upgrade
That's a sensible approach, but there are loads of web pages telling people how to set up NFS, and they all claim that on current distributions you no longer need to enable individual services. That's not true for Ubuntu 20. Please do make sure it's fix in 22.04. The original reasoning had a hole in it: with the scripts, there were three states: on, off, and default. Default was on. With the patch the default is off. I see no way in systemd to duplicate the way the scripts worked purely within systemd. This problem is particularly insidious. First, the symptoms aren't obvious. It took us a couple of days to figure out what was going on. Second, the problem doesn't occur if you mount anything by NFS3. So things worked in testing, but failed the first time we rebooting in production. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails - rpc-statd not started after minor upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - rpc-statd not started after minor upgrade
I conjecture that the problem occurred when moving from init scripts to systemd. It's pretty clear that the default in the nfs-common init script was to start statd. I conjecture that when converting to systemd, someone forgot to put a Wants in nfs-server. It's got an after but not a Wants. Writing the unit file with an [Install] section implies an explicit enable, but you probably don't want that. You probably want nfs-server to start it. It wouldn't be easy to start it the first time a client mounts via NFS 3, without a kernel upcall, so I think nfs-common was right to default to using it. But it looks like nfs-common is a vestige of the init script days and isn't used except in single user. For what it's worth, centos 7 has a nearly identical unit file for rpc- statd, except it's missing the [Install] section (presumably because it's intended to be invoked by other things and not explicitly enabled). There are Wants for autofs and nfs-server. I think adding Wants to at least nfs-server makes sense. rpc-statd.service doesn't have an install section -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails - rpc-statd not started after minor upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - rpc-statd not started after minor upgrade
Statd is used by both client and server. I think that note is for the client usage. Our servers don't necessariy do any NFS3 client mounts, so the client start would't happen. Is it possible that at some point I mounted something via NFS3 and that's the only reason statd was running? I can't prove that that isn't true. I tried enabling nfs-server and that didn't help. My solution has been to enable rpc-statd explicitly. That works. The reason I reported the problem is that it had previously worked automatically, and it took me quite a while to figure out why after the upgrade NFS 3 wasn't working on the server. I might not be alone in this. It looks like it's supposed to be started by /etc/init.d/nfs-common, but I'm pretty sure that isn't started except in /etc/rcS.d/, which wouldn't normally happen. I put a statement in nfs-common to create a file in /var/log, and it didn't happen, so I don't believe nfs-common ran. I suspect statd should be started as part of nfs-server, but it doesn't seem to be happening. Unless you assume that people are just using nfs 4 and want to require manual intervention to support 3. I wouldn't expect that. Particularly since the symptoms are subtle. If you try an NFS 3 mount it works. Things don't start failing until someone tries locking. The most common case is probably firefox, thunderbird, etc, which lock their profiles. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails - rpc-statd not started after minor upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - rpc-statd not started after minor upgrade
right. It's not failing. It's not running at all.
systemctl status rpc-statd
● rpc-statd.service - NFS status monitor for NFSv2/3 locking.
Loaded: loaded (/lib/systemd/system/rpc-statd.service; disabled; vendor
preset: enabled)
Active: inactive (dead)
Journalctl doesn't show that nfs-utils ran. As far as I can tell, that's
the only thing that would activate it.
I note that there's an [Install] section in rpc-statd.service. That
implies that it's intended to be enabled. It's not. If you enable it,
everything works. I suspected maybe the upgrade was supposed to enable
it but didn't.
rpc.statd version 1.3.3
ls -l /sbin/rpc.statd
-rwxr-xr-x 1 root root 89016 May 24 2021 /sbin/rpc.statd
ls -lc /sbin/rpc.statd
-rwxr-xr-x 1 root root 89016 Jan 10 15:09 /sbin/rpc.statd
It looks like it changed in the last update. It was "apt upgrade"
/etc/default/nfs-common
STATDOPTS=
NEED_GSSD=yes
/etc/default/nfs-kernel-server
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids"
NEED_SVCGSSD="yes"
RPCSVCGSSDOPTS=""
/etc/default/rpcbind
OPTIONS=""
OPTIONS="-w"
/etc/systemd/system/rpc-gssd.service.d
gss-krb.conf
[Service]
Environment=KRB5_CONFIG=/etc/krb5.conf:/etc/krb5.conf.gssd
time.conf
[Service]
Environment=GSSDARGS=-t600
The KRB5_CONFIG is to configure
[plugins]
ccselect = {
module = nfs:/usr/lib/ccselect_nfs.so
}
ccselect_nfs.so selects the user's primary principal, so that if they've done
kinit as user.admin to do privileged stuff, NFS still uses their default
principal.
Note that this was all working before the upgrade. The upgrade was
2022-01-10 15:09:15
Looks like the system was installed July 31, 2020, and no upgrades other
than unattended upgrade since then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956787
Title:
nfs v3 locking fails - rpc-statd not started after minor upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1956787/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - rpc-statd not started after minor upgrade
** Summary changed: - nfs v3 locking fails - 5.4.0-92 regression + nfs v3 locking fails - rpc-statd not started after minor upgrade ** Package changed: kernel-package (Ubuntu) => nfs-utils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails - rpc-statd not started after minor upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - 5.4.0-92 regression
It has nothing to do with the kernel. For some reasons rpc.statd isn't getting started. The systemd declaration looks fine, but it isn't there. Doing "systemctl start rpc-statd" and "enable" fixes it. The other parts of nfs-utils seem fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails - 5.4.0-92 regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - 5.4.0-92 regression
The problem occurs on 4 different servers. It does not occur on a server running Centos7 updated to kernel 5.4.170. This implies that the problem is most likely an Ubuntu patch (or it was fixed upstream between 5.4.157 and 5.4.170). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails - 5.4.0-92 regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails - 5.4.0-92 regression
** Summary changed: - nfs v3 locking fails + nfs v3 locking fails - 5.4.0-92 regression -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails - 5.4.0-92 regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] Re: nfs v3 locking fails
Also, "lslocks" on the server shows no locks associated with lockd, though there are locks associated with nfsd. (nfsd would be locks from NFS 4 I believe.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956787] [NEW] nfs v3 locking fails
Public bug reported: We just upgraded our nfs servers from 5.4.0-72 to 5.4.0-92. We are using NFS v3 in a large computer science department, with several hundred clients. Lots of applications are now failing because locks don't work. /var/log/syslog on the client reports lockd not responding. tcpdump shows that the client tries to connect to lockd but there is no response to the TCP SYN. netstat on the server shows some connections open, with lots of bytes in the receive queue. The problem probably occurs only with lots of clients. I believe any typical test would work fine. The problem is new. That is, it didn't happen in 5.4.0-72. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kernel-common (not installed) ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 Uname: Linux 5.4.0-92-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jan 7 13:07:34 2022 InstallationDate: Installed on 2020-10-14 (450 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: kernel-package UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-10-14T13:53:33.474467 ** Affects: kernel-package (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956787 Title: nfs v3 locking fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1956787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
I've also seen this. I wondered if the problem is that the libraries and utilities haven't been updated. I doubt that it's intended for a version 0.8.3 ZFS send and receive to run on a ZFS 2.0.2. kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938703] [NEW] 5.11 HWE on 20.04 needs new ZFS utils
Public bug reported: The 5.11 HWE for 20.04 has version 2.02 of ZFS, but it doesn't update zfsutils. I found that a zfs send | receive pipe gives an error message, though it seems to work. I don't know for sure that this is due to the version mismatch, but it seems dangerous to use 0.8.3 utilities with 2.0.2 kernel module. I recommend making the 2.0.2 zfsutils available, and possibly installing them by default when the kernel is upgraded. ** Affects: zfsutils (Ubuntu) Importance: Undecided Status: New ** Also affects: zfsutils (Ubuntu) Importance: Undecided Status: New ** No longer affects: nfs-utils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938703 Title: 5.11 HWE on 20.04 needs new ZFS utils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfsutils/+bug/1938703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918312] Re: group changes don't show up in kerberizedd mounts
Id be happy to help make changes to the relevant tools so I don't need the hacks in that repository if any maintainers would be interested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918312 Title: group changes don't show up in kerberizedd mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918312] Re: group changes don't show up in kerberizedd mounts
I'm well aware of the problem. I see lots of reports that produce discussions that wander off with nothing done, even though there's an actual fix in the thread. I run a moderately large site that uses Kerberos extensively, and kerberoized NFS. I have a whole github repository full of workarounds for problems I can't get fixed. Perhaps this one could be different. https://github.com/clhedrick/kerberos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918312 Title: group changes don't show up in kerberizedd mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918313] [NEW] code in rpc.svcgssd treats date as signed 32-bit
Public bug reported: Upstream patch eb3a145789b9eedd39b56e1d76f412435abaa747 adds code to rpc.svcgssd to set an expiration date for nfs contexts. (It doesn't work, but that's the subject of a different bug.) That code treats the date is int32. It is sent into the kernel using code that ends up as a printf %d. In 2038 the date will go negative. Because the kernel uses 64-bit dates I believe that will produce the wrong result. The code should use data_t, not int32_t. This is complicated by the fact that it gets the date from a Kerberos ticket. Kerberos declares date as int32. For historical reaosns, they have decided to retain it as int32, but whenever there's a comparison or arithemtic that would break, they cast it (date_t)(u_int32_t). I believe the code in svcgssdd should do the same. All variables should be date_t. Anything retrieved from a Kerberos ticket should be cast (date_t)(u_int32_t). THis is actually a problem upstream. But it's not clear that upstream has any reason to fix it. Redhat is no longer using rpc.svcgssd. They're using gssproxy to handle the upcall from the kernel. So it's not clear that there's any significant use of svcgssd other than Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nfs-common 1:1.3.4-2.5ubuntu3.3 [modified: usr/sbin/rpc.svcgssd] ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 9 12:46:12 2021 InstallationDate: Installed on 2020-03-25 (348 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=vt100 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/tcsh SourcePackage: nfs-utils UpgradeStatus: Upgraded to focal on 2020-12-21 (78 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-08-10T17:26:17.512725 mtime.conffile..etc.default.nfs-common: 2020-04-16T16:03:31.356462 ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918313 Title: code in rpc.svcgssd treats date as signed 32-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 350083] Re: [Hewlett-Packard Presario V5000 (EP422UA#ABA)] suspend/resume failure
same thing with HP L2000. blank screen on resume. Had to power off. -- [Hewlett-Packard Presario V5000 (EP422UA#ABA)] suspend/resume failure https://bugs.launchpad.net/bugs/350083 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355383] Re: key bindings fail in firefox and thunderbird
A workaround: append /usr/share/themes/Emacs/gtk-2.0-key/gtkrc to ~/.gtkrc-2.0 That fixes both thunderbird and firefox. Seems to confirm it as a problem in gnome/gtk. -- key bindings fail in firefox and thunderbird https://bugs.launchpad.net/bugs/355383 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355383] [NEW] key bindings fail in firefox and thunderbird
Public bug reported: Binary package hint: thunderbird You're supposed to be able to get emacs keybindings, which are primarily control keys, e.g. control-A moves to the beginning of the line. In gconf-edit you set the key theme to emacs, then in thunderbird and firefox, change the accelerator key from control to alt (so that the builtin commands don't interfere with the emacs commands). See http://forums.mozillazine.org/viewtopic.php?t=382766 for details. This works in Opensolaris 2008.11, which is a Gnome/GTK environment with packages similar to the normal Linux ones. It works in the most recent Debian for Thunderbird but not Firefox. (However on my machine Debian hangs, so I can't use it for real.) In Ubuntu, the default key bindings, e.g. control-A for selectall, remain even after changing the configuration. After the change the edit menu claims select all is Alt-A, and Alt-A works, but Control-A still does it as well. There are other ways to change the key bindings in Thunderbird, none of which work. Something at a lower level in the system seems to taking the control keys. I also tried sylpheed, which lets you rebind keys. Again, sylpheed understood the new bindings and showed them in the menus, but something is still trapping control A, control C, and control V at least and maybe a few others. I'm currently using unbuntu 9.04 beta i86 with xubuntu installed, but I've also tried it in 8.10. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- key bindings fail in firefox and thunderbird https://bugs.launchpad.net/bugs/355383 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 353786] [NEW] closing lid no longer causes suspend
Public bug reported: HP special edition L2000. Suspend to RAM works. I have set power management to trigger it when I close the lid. It works the first time, but eventually stop working. Instead of suspend I get blank screen. If I do a suspend from the menu it works fine. The problem exists in 8.10 with current patches (as of 1 Apr 2009) and in 9.04 beta (as of midnight 1 Apr). Description:Ubuntu jaunty (development branch) Release:9.04 I've attached dmesg output that should give you the hardware I apologize for the erroneous module name, but the web form wouldn't take "i don't know" ** Affects: affix-kernel (Ubuntu) Importance: Undecided Status: New -- closing lid no longer causes suspend https://bugs.launchpad.net/bugs/353786 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 353786] Re: closing lid no longer causes suspend
** Attachment added: "dmesg" http://launchpadlibrarian.net/24695568/dmesg -- closing lid no longer causes suspend https://bugs.launchpad.net/bugs/353786 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
