Lite Control Center - Suggestions welcomed

[shaggytwodope]

Code:

cat /etc/apt/apt.conf.d/15update-stamp

Outout:

Code:

APT::Update::Post-Invoke-Success {"touch /var/lib/apt/periodic/update-success-stamp 2>/dev/null || true";};

After running

Code:

sudo rm /var/lib/apt/periodic/update-success-stamp

and

Code:

sudo apt-get update && sudo apt-get upgrade

the control center says "Updates not been done, Please update soon"

Code:

stat /var/lib/apt/periodic/update-success-stamp

Output:

Code:

stat: cannot stat ‘/var/lib/apt/periodic/update-success-stamp’: No such file or directory

So it looks like SOMETHING is acting up here.

run this, and then upload the file aptdump.txt here or pastebin etc.

Code:

apt-config dump > aptdump.txt

And if you would be so kind, create a system report (either in control center or located in the menu MENU>SYSTEM> CREATE SYSTEM REPORT)

This will let me see some of the things installed on your setup and figure what's causing this conflict.

[UltraCookie]

Apt dump
http://pastebin.com/bi5giQsJ

System Report
http://pastebin.com/qFUNmrBr

[avj]

Everything looks ok on my old netbook.  The amount of memory in the image is an issue with my hardware not the program.

http://i.imgur.com/6FxPssm.png

[shaggytwodope]

Apt dump
http://pastebin.com/bi5giQsJ

System Report
http://pastebin.com/qFUNmrBr

Figuring this out is always a headache lol. But have you added any repos since your initial install?

If you have can you run

Code:

apt-cache policy > aptpolicy.txt

and upload aptpolicy.txt for me.

When you run update, do you see ANY errors? Can you copy/paste all the output from running

Code:

sudo apt-get update

Lastly, can you run

Code:

ls -l /var/lib/apt/periodic

And share that output.

My first thought was use of a 3rd party apt tool at one stage, but that seems fine. All the post install config stuff is still fairly default. But atm I'am thinking something is failing when update is run, if not all the db stuff is fetched it may cause the update trigger to not execute. Thanks for the time spent trying to solve this.

[UltraCookie]

I only added the Spotify and Inkscape repos as far es I can remember.
The Spotify repo causes some errors when updating. They come and go and since Spotify doesn't get many updates I tend to ignore it.

Code:

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used.
GPG error: http://repository.spotify.com stable InRelease:
The following signatures couldn't be verified because the public key is not available:
NO_PUBKEY 13B00F1FD2C19886

W: Failed to fetch http://repository.spotify.com/dists/stable/InRelease 

W: Some index files failed to download. They have been ignored, or old ones used instead.

APT Policy:
http://pastebin.com/W0nNycBR

Code:

ls -l /var/lib/apt/periodic

Output:

Code:

total 0
-rw-r--r-- 1 root root 0 Jun 17 06:38 update-stamp

[shaggytwodope]

I only added the Spotify and Inkscape repos as far es I can remember.
The Spotify repo causes some errors when updating. They come and go and since Spotify doesn't get many updates I tend to ignore it.

Code:

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used.
GPG error: http://repository.spotify.com stable InRelease:
The following signatures couldn't be verified because the public key is not available:
NO_PUBKEY 13B00F1FD2C19886

W: Failed to fetch http://repository.spotify.com/dists/stable/InRelease 

W: Some index files failed to download. They have been ignored, or old ones used instead.

APT Policy:
http://pastebin.com/W0nNycBR

Code:

ls -l /var/lib/apt/periodic

Output:

Code:

total 0
-rw-r--r-- 1 root root 0 Jun 17 06:38 update-stamp

When you installed did you run

Code:

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys D2C19886

They have been known to change their key time to time, a bad practice lol. Give that command a run, and repeat the update command as before. And lemme know if the same error occurs.

For the record this is the issue, when a failure occurs the file wont be run. Basicly if successful do > update file. So the repo isn't being updated proper. Causing this odd bug. It's been reported to apt upstream, hopefully gets fixed lol.

[UltraCookie]

Looks like

Code:

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys D2C19886

did the job ^.^

[shaggytwodope]

Looks like

Code:

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys D2C19886

did the job ^.^

Wonderful, just some advice.. when you have an issue with a repo and it mentions the key/signature like that. Please tell us, or look at the upstream vendor for that repo. It's extremely unsafe for you the user.

Lets say spotify's website was hijacked or "hacked", they could inject some nasty code under the guise of the spotify client. (sounds crazy, but thats why we got signatures for the repo/deb files and stuff)

Bottomline, be safe and don't be afraid to point out errors. And thank you for the time figuring this problem out, we know what the problem is likely to be in the future.

[valtam]

Update: 1.0-0080

- link to updates directly on date next to 'Software Updates' main tab
- Screenshot tool on main tab is greyed out if person clicks Show/Hide IP, prevents accidental upload of sensitive info

[valtam]

Update: 1.0-0090

- Check if application exists, eg. if Light Locker was uninstalled, it would no longer show in Lite CC (Thank you to Misko!)
- Minor changes, if computer is up to date, display last update in green and remove link
- some re-wording