[Bug 248965] Re: u-n does not process a file dropped in /var/lib/update-notifier/user.d until dpkg-run-stamp was written
Thanks for this additional information. There is nothing that prevents third parties from using it, its just that the current main use-case is stuff that is happening during package installation. The dpkg-run-stamp file is automatcially updated when apt is finished so in practise this should not be a real limitation. ** Changed in: update-notifier (Ubuntu) Assignee: Michael Vogt (mvo) => (unassigned) -- u-n does not process a file dropped in /var/lib/update-notifier/user.d until dpkg-run-stamp was written https://bugs.launchpad.net/bugs/248965 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 248965] Re: u-n does not process a file dropped in /var/lib/update-notifier/user.d until dpkg-run-stamp was written
We thought that /var/lib/update-notifier/user.d was the place where applications that wanted to use the update-notifier infrastructure should drop a file. Our application required an specific action to be run by the user upon upgrade, thus we dropped a file mimicking how the firefox package does it. The weird part starts here, we found no virtual difference between the way firefox dropped that file there and our way, yet our popup never appeared. Once we started debugging it, we found out that it wouldn't be shown until "touch /var/lib/update-notifier/dpkg- run-stamp". If u-n shouldn't be used by third-party apps, it should be stated somewhere. If it can be used by third party apps, what are we missing here that the touch command is needed? -- u-n does not process a file dropped in /var/lib/update-notifier/user.d until dpkg-run-stamp was written https://bugs.launchpad.net/bugs/248965 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 248965] Re: u-n does not process a file dropped in /var/lib/update-notifier/user.d until dpkg-run-stamp was written
Thanks for your bugreport. Given that the files installed there are from packages (or the system is designed for that) having the touch requirement sounds not too bad to me. This ensures that e.g. firefox-restart notifciation are not shown until he install is actually finished. Or what is your use-case? ** Changed in: update-notifier (Ubuntu) Status: Triaged => Incomplete -- u-n does not process a file dropped in /var/lib/update-notifier/user.d until dpkg-run-stamp was written https://bugs.launchpad.net/bugs/248965 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 248965] Re: u-n does not process a file dropped in /var/lib/update-notifier/user.d until dpkg-run-stamp was written
** Changed in: update-notifier Importance: Undecided => Medium Status: New => Triaged -- u-n does not process a file dropped in /var/lib/update-notifier/user.d until dpkg-run-stamp was written https://bugs.launchpad.net/bugs/248965 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
