03-01-2016, 11:50 PM
03-02-2016, 06:59 AM
Open Synaptic Package Manager.
Look at the left, see if you have anything in "Installed(upgradable) .??,,
I think they are included in the count also.
Look at the left, see if you have anything in "Installed(upgradable) .??,,
I think they are included in the count also.
03-02-2016, 01:01 PM
(03-01-2016, 11:50 PM)firenice03 link Wrote:Just for FYI... Checked tonight ..This has been fixed, once I contact Jerry a update will be made.
Updater showed 22 only 2 updates thou...
03-02-2016, 01:10 PM
(02-29-2016, 05:16 PM)n1ksn link Wrote:I tried the lite-updater in LL 2.8 on my 64-bit Dell Latitude E6410. It correctly notified me of 67 available updates and did the updating.
However, after the update the checkmark icon was still visible (maybe lighter?) and the tooltip showed that the same 67 updates were available. I quit the program and re-ran from the menu. The tooltip then correctly showed no updates available.
Also, I opened the configuration menu for it and found it a bit confusing. There were two enties for update checking interval, one minutes and one for hours. Do these add together? It was not clear.
Hope this helps.
Andy N1KSN
Added a bit later:
I installed the updater in my 32-bit Gateway LT40 notebook. When I first ran it the behaviour was the same as above, with the tooltip and icon still indicating updates available after an update.
However, on the second run (after a reboot) it now showed 7 updates available. When I ran it this time the update process completed and said there had actually been no updates available, not seven. And the tooltip and icon still said 7 updates available.
Andy
There was bug in updating the count, this as been fixed.
The config option is added up, I'll see if I can make it any clearer. If you have any ideas as to improve this please let me know.
03-02-2016, 01:11 PM
(02-29-2016, 12:58 PM)avj link Wrote:I don't know if this will be an issue with new users, but I suspect it might. If you have held packages they still show up as available updates this is also true with the control center, and will likely have new users confused as to why they can't install their updates, just my opinion. On a side note it might be useful to be able to set a specific time for checking for updates like once a day at 7:00 am. This will work better for people with limited bandwidth at certain hours. Again just my opinion, everything seems to work fine have not noticed any issues. Good work.
I'll look into specific timed events, this may be a fair bit of work before it's added. No promises ofc.
03-02-2016, 03:23 PM
I think you could leave the minutes and hours boxes as-is (although they could be horizontally smaller) but just put "Minutes" and "Hours" in front of them (to their left). Then put a text line above the two saying "Time between checks" (or your favorite wording).
Or maybe better, under the description line put the two boxes on the same line, (smaller, of course), with the simple hour and minute labels beneath or above them and a big "+" sign or ":" colon between them.
Andy
Or maybe better, under the description line put the two boxes on the same line, (smaller, of course), with the simple hour and minute labels beneath or above them and a big "+" sign or ":" colon between them.
Andy
03-02-2016, 10:59 PM
New update now available.
03-03-2016, 12:19 AM
Cool - I'll run updates and watch 
Well done gentlemen!!!
**UPDATE**
Ran updates from LLCC = Error: couldn't fetch the package cache information lists.
From terminal using sudo apt-get update
I removed google from source, for the time being (this is a 64-bit system) Now just the no PUBKEY
** FYI; Occurring on multiple systems..

Well done gentlemen!!!
**UPDATE**
Ran updates from LLCC = Error: couldn't fetch the package cache information lists.
From terminal using sudo apt-get update
Code:
W: GPG error: http://extras.ubuntu.com trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 16126D3A3E5C1192
W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release Unable to find expected entry 'main/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file)
E: Some index files failed to download. They have been ignored, or old ones used instead.
I removed google from source, for the time being (this is a 64-bit system) Now just the no PUBKEY
Code:
W: GPG error: http://extras.ubuntu.com trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 16126D3A3E5C1192
** FYI; Occurring on multiple systems..
03-03-2016, 12:40 AM
(03-03-2016, 12:19 AM)firenice03 link Wrote:Cool - I'll run updates and watch
Well done gentlemen!!!
**UPDATE**
Ran updates from LLCC = Error: couldn't fetch the package cache information lists.
From terminal using sudo apt-get update
Code:W: GPG error: http://extras.ubuntu.com trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 16126D3A3E5C1192
W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release Unable to find expected entry 'main/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file)
E: Some index files failed to download. They have been ignored, or old ones used instead.
I removed google from source, for the time being (this is a 64-bit system) Now just the no PUBKEY
Code:W: GPG error: http://extras.ubuntu.com trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 16126D3A3E5C1192
** FYI; Occurring on multiple systems..
Recently google removed 32bit chrome from repo. However not updated repo data yet.
If you are on 64bit, simply edit
Code:
/etc/apt/sources.list.d/google-chrome.list
Change from:
Code:
deb http://dl.google.com/linux/chrome/deb/ stable main
To:
Code:
deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
03-03-2016, 01:04 AM
Shaggy - That fixed the google prompt (yes 64-bit)
Still getting the NOKEY message..
*Reminder for the folks running Chrome on 32-bit systems; Google ended 32-bit Linux support (for more info please search the forums)
Chromium or another will need to be installed/utilized.
**Update*
Shaggy.. if it helps
I found the following info.. http://askubuntu.com/questions/520828/gp...henticated
Which suggests running the following command;
Replacing "ABCDEFGH12345678" with key error when running updates
It did resolve the NOKEY message on a system I tested...
Still getting the NOKEY message..
*Reminder for the folks running Chrome on 32-bit systems; Google ended 32-bit Linux support (for more info please search the forums)
Chromium or another will need to be installed/utilized.
**Update*
Shaggy.. if it helps
I found the following info.. http://askubuntu.com/questions/520828/gp...henticated
Which suggests running the following command;
Replacing "ABCDEFGH12345678" with key error when running updates
Code:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys ABCDEFGH12345678
It did resolve the NOKEY message on a system I tested...