[Bug 619052] Re: file update-motd-updates-available is empty

2010-12-08 Thread Christopher J. Shaker
After my upgrade to Ubuntu 10.04.1 LTS, my /usr/lib/update-notifier /update-motd-updates-available was bad, too. It actually exec'd itself, hanging logins infinitely! Reinstalling update-notifier-common using apt-get fixed it. Chris Shaker -- You received this bug notification because you are

[Bug 619052] Re: file update-motd-updates-available is empty

2010-08-18 Thread MikeR
Sorry, I did not realize that the issue affected only me. And I still don't know where it came from -- seemed to appear after upgrade to Lucid. -- file update-motd-updates-available is empty https://bugs.launchpad.net/bugs/619052 You received this bug notification because you are a member of

[Bug 619052] Re: file update-motd-updates-available is empty

2010-08-17 Thread MikeR
** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/619052/+attachment/1494697/+files/Dependencies.txt -- file update-motd-updates-available is empty https://bugs.launchpad.net/bugs/619052 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 619052] Re: file update-motd-updates-available is empty

2010-08-17 Thread Ilya Zakreuski
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, it is not clear which steps or actions you took that caused you to encounter the problem. We would be grateful if you would then provide a more complete description of the problem. In the meantime,

[Bug 619052] Re: file update-motd-updates-available is empty

2010-08-17 Thread MikeR
Re-installation of update-notifier-common fixed it!! $ sudo /usr/lib/update-notifier/update-motd-updates-available --force 0 packages can be updated. 0 updates are security updates. Many thanks, Mike P.S. I wonder where the correct file got lost... -- file update-motd-updates-available is

[Bug 619052] Re: file update-motd-updates-available is empty

2010-08-17 Thread Ilya Zakreuski
We are glad that your problem has been resolved. Examining the information you have given us, this does not appear to be a bug in update-notifier so we are closing it. We appreciate the difficulties you were facing, but it would make more sense to raise problems you are having in the support