I was in a rush when I posted the second addendum, hence, I knew I left out graphics that might have been useful. My intention is to post a few screen shots and to describe my methods and experiences using the update notifier solely as an unprivileged user. In addition, I learned an easier way to activate the update notifier upon startup.
I am going to limit this note to some graphics showing screens with pertinent notifier icon information. In addition, I will elaborate briefly on my experience with manual methods to activate the notifier in an unprivileged account. Finally I will show how I learned to automate the entire process with my son's advice using the built-in GUIs.
In order to keep this brief, please refer to my previous article and the discussion of the issue filed under Bug 288099 in Canonical's Lauchpad site.
I have now run my system, which upon startup the first task was opening a terminal and pasting in a command:
[regular user]@[machine name]:~$ update-notifier --force &
Or more likely, I began by hitting this key combination to bring up the command line above from memory: Ctrl-r [2.], then a dash "-", which if not sufficient followed by a second "-". For me this sufficed, however, should it have failed I would have begun to type in the word force [3.]. As you see in the graphic below, as an unprivileged user I was informed on "Thu Nov. 20,  9:03 AM" a security update was waiting:
Figure 1. Unprivileged User Security Alert
Figure 2. Administrative Account No Security Alert Seen Upon Opening
My standard action was/is to use the menu: System > Administration > Update Manager, which would then check for updates. The icon would appear once I had initiated the actual updates [4.]. I found this routine simple and easy enough to suit my needs. However, my means are not to everyone's tastes.
To accomplish this task, it might be necessary [5.] to do some preliminary configuration in the administrative account. Your first task is making certain under the tab, Startup Programs the Update Notifier exists and is checked to run. Once those conditions are met, the automating steps are easily implemented. First look at the Sessions Preferences to confirm it is ready:
Figure 3. Confirmation Update Notifier Runs Upon Startup
Figure 4. Pasting in Critical Code into Update Command
It is critical that the highlighted code be pasted in after "update-notifier" in the command line as shown, without it an unprivileged user will not receive notice when updates are needed and ready. I can assure you that I have had now run this for a sufficient period to be certain it works as described. However, I must credit my son for the setup [6.]. That is, despite my having previously tried configure it in an unprivileged account to activate the notifier icon, I do not naturally think of using it as a part of the user configuration.
Finally, if you have to setup the update-notifier program, in this graphic you should have sufficient information without the necessity of examining this in the administrative account:
Figure 5. Current Session Startup Program Specifications
I have presented a quick supplement to the previous addendums showing how an unprivileged account could be activated to see update notifications. The missing part was just adding the graphics left out of the second addendum and instructions how to automate the process. I hope this helps those users that use Ubuntu (and variants) that prefer to stay out of the administrative account.
Corrections, suggested extension or comments write: H. Cohen.
© Herschel Cohen, All Rights Reserved
____________________________________________________________________ 1. Abbreviation for: standard operating procedure. Return 2. Usually shown as Ctrl-R, but the case r works. Return 3. If you are a heavy user of the CLI it might be possible you used the --force option, hence, use portions of "update" or "notifier" to recover the command. Return 4. Not completely accurate, reflected the speed at which I started process. The appearance of the icon need not await the operation of the manual update. Return 5. I thought it was necessary to add the notifier to the session preferences using the sudo account. However, I now believe it can all be accomplished in the non sudo account. Return 6. GUIs always leave me with the impression that they are hiding something important from me. Hence, I tend to distrust them. Return ____________________________________________________________________