** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970264
Title:
autofs fails to mount nfs4 shares with "error 0x3
Thanks you for the detailed response.
I have to say that this was the first time that I was confronted with
the 'proposed'-repository. I followed the instructions at
https://wiki.ubuntu.com/Testing/EnableProposed without too much
investigation of the precise effect of the single steps.
Thereby,
I can confirm that the package autofs-5.1.8-1ubuntu1.1 solves the
original problem, as long as it is a "pure" automount without LDAP
involved.
It is clear that a LDAP-based automount cannot work as the autofs-ldap
package has been uninstalled.
--
You received this bug notification because you
@Brian Murray
In the process, I see the following:
apt-get install autofs/jammy-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '5.1.8-1ubuntu1.1' (Ubuntu:22.04/jammy-proposed [amd64]) for
'autofs'
The following packages
These are good news, thank you so much!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970264
Title:
autofs fails to mount nfs4 shares with "error 0x3 getting portmap
client"
To manage
Here is some more info:
The server runs with an enabled UFW firewall. It was set up via
ufw allow from to any port nfs proto tcp
Here is the server output of 'ufw status'
Status: active
To Action From
-- --
OpenSSH
Many thanks for looking into this.
I guess a "quick reproducer" means that I have to set up 2 fresh 22.04
installs, and then do a minimal configuration of one as a server
(provide NFSv4 share) and on the other install as a client (pull in
NFSv4 share via autofs mount). This would take some time.
** Description changed:
I'm running a server which provides user home directories as NFSv4
shares. The clients mount these shares via automount + LDAP.
- Now I've updated one client from 20.04 to 22.04 (new installation from
scratch). Setting up things as before, I cannot get the
** Description changed:
I'm running a server which provides user home directories as NFSv4
shares. The clients mount these shares via automount + LDAP.
Now I've updated one client from 20.04 to 22.04 (new installation from
scratch). Setting up things as before, I cannot get the
** Description changed:
I'm running a server which provides user home directories as NFSv4
shares. The clients mount these shares via automount + LDAP.
Now I've updated one client from 20.04 to 22.04 (new installation from
scratch). Setting up things as before, I cannot get the
** Summary changed:
- autofs fails to mount nfs4 shares
+ autofs fails to mount nfs4 shares with "error 0x3 getting portmap client"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970264
Title:
Maybe this one
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1965643
is the same bug. It is hard to tell as not much info is given.
** Description changed:
- I'm running a server which provides NFSv4 shares. The clients mount
- these shares via automount + LDAP.
+ I'm running a server
Public bug reported:
I'm running a server which provides user home directories as NFSv4
shares. The clients mount these shares via automount + LDAP.
Now I've updated one client from 20.04 to 22.04 (new installation from
scratch). Setting up things as before, I cannot get the automount mechanism
Christopher M. Penalver,
on 2)
The problem does not occur after
sudo iw dev X set power_save off
What's the best way to make this permament?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628061
Christopher M. Penalver,
thank you.
1) will need some time as I don't remember when exactly the problem has started.
I see that you added the tag "kernel-bug-exists-upstream-4.9". To make sure: I
didn't experience the reported problem on 4.9. Simply because I cannot boot
into it due to a kernel
Christopher M. Penalver, as written, I've tested 4.9-rc5 a few weeks ago
**and 4.9 today**.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628061
Title:
iwl4965 crashes randomly
To manage
Christopher M. Penalver, I continued testing:
4.8.15-040815-generic gives a kernel panic at boot, too.
4.7.10-040710-generic boots just fine, but the original Problem is still there
(WLAN not working after some while).
--
You received this bug notification because you are a member of Ubuntu
Christopher M. Penalver, I had tested 4.9-r5, which gives a kernel panic at
boot. Now I've tested the latest mainline kernel 4.9. Kernel panic at boot, too.
How should I proceed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Christopher M. Penalver:
The newest kernel 4.9-rc5-generic gives a kernel panic at boot.
"stack guard page was hit at ..."
What to do now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628061
Christopher M. Penalver (penalvch): ok, see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628061
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1461738
Title:
iwl3945 on X61T crashes with
Public bug reported:
On my Lenovo X61s, WLAN randomly stops working, typically after a few hours of
running time. I don't know any remedy but to reboot.
This behavior started maybe 2 or 3 months ago. My maching is usually kept up to
date, so the problem might be caused by some kernel update at
same problem here (Lenovo X61s, Ubuntu Server 16.04, Kernel
4.4.0-38-generic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1461738
Title:
iwl3945 on X61T crashes with Error sending C_POWER_TBL:
@andrikos: Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565842
Title:
biber removes texlive-bibtex-extra
To manage notifications about this bug go to:
@Robert Bredereck:
I completely agree. The problem affects many people, and the fix is almost
trivial. But sadly we don't even know if anyone in the position of applying it
is listening at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Yes, the fix would simply be to provide the biber package in version 2.4
in Xenial. Hope that this will be done soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565842
Title:
biber removes
** Description changed:
It seems you can either install texlive-bibtex-extra or biber.
I expected to be able to install both.
sudo apt-get install texlive-bibtex-extra biber
Reading package lists... Done
- Building dependency tree
+ Building dependency tree
Reading state
26 matches
Mail list logo
