[Bug 1558196] Re: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind

2017-12-15 Thread Tjd
@paelzer: Is this being considered for SRU? Could it still make it into 16.04.4? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: ypbind not able to socket activate rpcbind under

[Bug 160999] Re: Apport doesn't overwrite existing core files

2017-01-10 Thread Tjd
** Changed in: apport (Ubuntu) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/160999 Title: Apport doesn't overwrite existing core files To manage notifications

[Bug 160999] Re: Apport doesn't overwrite existing core files

2017-01-09 Thread Tjd
@k04jg02, as noted in comment #7, this bug has no effect on the Ubuntu Error Reporting process for software that is distributed through normal channels. Instead, for software that comes from any other source, apport seems to make a 'best-efforts' approach to dump a core file, roughly following

[Bug 1254804] Re: [wishlist] Apport doesn't log when a core dump is ignored because of the limit

2017-01-09 Thread Tjd
I got burned by this, too. It is compounded by the fact that "Segmentation fault (core dumped)" is written to stderr, which actually just means that the dump has been collected and passed on to apport. Since it is apport that is parsing the ulimit value and deciding whether or not to write out

[Bug 1384502] Re: fstab entry for nfs /home fails to mount on boot

2016-05-06 Thread Tjd
Workaround: add the 'bootwait' option to the /home fstab entry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384502 Title: fstab entry for nfs /home fails to mount on boot To manage