in systemd package in Ubuntu:
New
Bug description:
What I expected to happen?
I want an NFS share to be mounted on startup using
192.168.178.66:/media/captainplanet/7EF8B26FF8B22575/
/media/captainplanet/banane/ nfs rw 0 0
What happened instead?
It does not mount on startup. Systemd
Public bug reported:
What I expected to happen?
I want an NFS share to be mounted on startup using
192.168.178.66:/media/captainplanet/7EF8B26FF8B22575/
/media/captainplanet/banane/ nfs rw 0 0
What happened instead?
It does not mount on startup. Systemd waits 91sec instead and finally
I experience a similar isses as Tommy. I mounted the NFS manually and
the computer will just not shutdown. Additionally I also failed mounting
the device via fstab but I used different options.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Ahh, understand. Good idea!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1476192
Title:
No error message when certificate for a configured WLAN is missing
Hi Matthew,
thank you for your response. Here’s my configuration:
Xubuntu 14.04 LTS
Lenovo Thinkpad T61
The certificate was in the home directory and I moved into
/home/documents.
I already fixed the problem as you described. I just did not remember this may
be the problem at first. So this
Public bug reported:
Hi,
this is rather an enhancement suggestion than a bug.
I just figured out that if you move a certificate file which is needed
for a certain WLAN it just won’t work anymore without a specific
message. Would be much easier with a little error message like CA-
Certificate
6 matches
Mail list logo
