[Bug 1447142] Re: systemd: ntpdate is started too soon (before the network)

2015-10-07 Thread Laurent Bonnaud
> Can you explain why this is actually a problem please? I guess that Ubuntu systems with ntp installed would boot a little faster if ntp was not doing useless work by getting started before the network is fully up. > Won't timesyncd suffice on a desktop that uses NetworkManager now? Perhaps, bu

[Bug 1447142] Re: systemd: ntpdate is started too soon (before the network)

2015-10-02 Thread Laurent Bonnaud
This bug still exists in wily and this package version: Package: ntp Version: 1:4.2.6.p5+dfsg-3ubuntu8 The error even occurs several times: oct. 02 11:05:10 vougeot ntpdate[1464]: Can't find host 0.ubuntu.pool.ntp.org: Name or service not known (-2) oct. 02 11:05:10 vougeot ntpdate[1464]: Can't

[Bug 1447142] Re: systemd: ntpdate is started too soon (before the network)

2015-04-22 Thread Laurent Bonnaud
** This bug is no longer a duplicate of bug 1442044 Ordering processes: networkmanager should wait for kernel'module been activated first before starting -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.la

[Bug 1422125] Re: ntpdate[634]: no servers can be used, exiting

2015-04-22 Thread Laurent Bonnaud
*** This bug is a duplicate of bug 1447142 *** https://bugs.launchpad.net/bugs/1447142 ** This bug has been marked a duplicate of bug 1447142 systemd: ntpdate is started too soon (before the network) -- You received this bug notification because you are a member of Ubuntu Server Team, whi

[Bug 1447142] [NEW] systemd: ntpdate is started too soon (before the network)

2015-04-22 Thread Laurent Bonnaud
Public bug reported: Here is what I see in journalctl: ntpdate cannot do DNS resolution because NetworkManager has not finished configuring the network interface. Apr 21 22:01:13 xeelee ntpdate[1563]: Can't find host 0.ubuntu.pool.ntp.org: Name or service not known (-2) Apr 21 22:01:13 xeelee N

[Bug 214023] Re: checksecurity cron job warning message caused by gvfs

2012-10-23 Thread Laurent Bonnaud
This bug no longer exists in quantal. The gvfs mount point is not in the user's homedir any longer. It is now located in /run : $ grep gvfs /proc/mounts gvfsd-fuse /run/user/bonnaud/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0 ** Changed in: checksecurity (Ubu

[Bug 791101] Re: wrong upstream URL in package description

2011-06-01 Thread Laurent Bonnaud
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cobbler in Ubuntu. https://bugs.launchpad.net/bugs/791101 Title: wrong upstream URL in package description -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify

[Bug 791101] [NEW] wrong upstream URL in package description

2011-06-01 Thread Laurent Bonnaud
Public bug reported: Binary package hint: cobbler Here is the problem: $ apt-cache show cobbler Package: cobbler [...] Homepage: https://fedoraproject.org/cobbler whereas the correct URL is: https://fedorahosted.org/cobbler/ ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cobbler (not

[Bug 214023] Re: checksecurity cron job warning message caused by gvfs

2010-07-01 Thread Laurent Bonnaud
This bug still exists in lucid. To reproduce it: - install both packages checksecurity and gvfs-fuse - log in - wait a week for the cron job to execute or run /etc/cron.weekly/checksecurity as root ** Changed in: checksecurity (Ubuntu) Status: Invalid => Confirmed -- checksecurity