siempre muestra que esta actualizado aunque existan actualizaciones, hasta que no haces click y se abre en modo root no te muestra las actualizaciones ...Pues bien, la única manera para solucionar este pequeño inconveniente es crear una tarea repetitiva (crontab) o mediante un script, pues bien he probado diversos métodos y no parecen funcionar bien ... A continuación hago una extensa explicación de las posibles soluciones:
OPCIÓN A
El primero es un script cuyo contenido es el siguiente:
Code: Select all
#! /bin/bash
sleep 30
(
while : ; do
aptitude update
sleep 2h
done
) &Para que se ejecute el script en el inicio tienes que añadir al final del fichero /etc/init.d/rc.local el lugar donde se aloja el script por ejemplo /home/hector/updatescript.
Pues bien he probado el script y no funciona correctamente.......si vais a la terminal y escribes ps -aux véis todos los procesos en marcha y se observa como efectivamente se ejecuta el script pero el escudo sigue mostrando que todo esta Ok, para asegurarme bien de que no funciona lo probé durante 4 o 5 días y realmente no funciona.
Link: http://forums.linuxmint.com/viewtopic.php?f=34&t=115128
OPCIÓN B
Otra opción se trata también de un script:
Para ello abrimos la terminal y ejecutamos la siguiente orden:
Code: Select all
gksudo pluma /etc/cron.daily/apt_updateCode: Select all
#!/bin/sh
# /etc/cron.daily/apt_update (MagicMint) M0518
# Taken from apt-xapian-index
CMD=/usr/local/bin/apt
# ionice should not be called in a virtual environment
# (similar to man-db cronjobs)
egrep -q '(envID|VxID):.*[1-9]' /proc/self/status || IONICE=/usr/bin/ionice
# Check if we're on battery
if which on_ac_power >/dev/null 2>&1; then
on_ac_power >/dev/null 2>&1
ON_BATTERY=$?
# Here we use "-eq 1" instead of "-ne 0" because
# on_ac_power could also return 255, which means
# it can't tell whether we are on AC or not. In
# that case, run update-a-x-i nevertheless.
[ "$ON_BATTERY" -eq 1 ] && exit 0
fi
# Download lists of new/upgradable packages
if [ -x "$CMD" ]
then
if [ -x "$IONICE" ]
then
nice -n 19 $IONICE -c 3 $CMD update
else
nice -n 19 $CMD update
fi
fiCode: Select all
sudo chmod +x /etc/cron.daily/apt_updateCode: Select all
# m h dom mon dow user command
17 * * * * root cd / && run-parts --report /etc/cron.hourly
25 6 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6 * * 7 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6 1 * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
#La pega que tiene es que sólo se ejecuta una vez al día.
Link: http://community.linuxmint.com/tutorial/view/1347
OPCIÓN C
Otra opción sería la que propone el usuario karlchen:
Lo he intentado probar pero si abro cat /etc/apt/apt.conf.d/10periodic me muestra lo siguiente:Hi, folks.
I know that the initial complaint "mintUpdate icon says "up to date" - even if updates available" was posted two months ago.
Yet, if I have not missed it, no-one has posted a solution, yet.
OK. So here is the solution which works fine for me:
Problem:
mintUpdate icon says "up to date" - even if updates available, as reported.
Cause:
There is a daily anacron job /etc/cron.daily/apt which is meant to update the local software list once per day. (apt-get update).
This job reads the configuration file /etc/apt/apt.conf.d/10periodic and checks the value of the setting named "APT::Periodic::Update-Package-Lists"
This setting defaults to "0", unless explicitly set to "1".
I do not know since when. But it is a fact that this setting is missing on all of my Mint 13 installations from the file /etc/apt/apt.conf.d/10periodic.
As a consequence the daily job assumes it does not have to perform any
As a consequence MintUpdate is always happily telling me there are no updates, unless I open MintUpdate by clicking on the icon in the notification area nevertheless.Code: Select all
apt-get update
Solution:
As user root edit the file /etc/apt/apt.conf.d/10periodic and make sure it holds the line
Code: Select all
APT::Periodic::Update-Package-Lists "1";
Effect:
Next time the daily job /etc/cron.daily/apt gets executed, it will performthus updating the local software list.Code: Select all
apt-get update
Provided updated software packages are available a few minutes later the MintUpdate icon in the notification area will let you know.
Problem solved.
Code: Select all
APT::Periodic::Download-Upgradeable-Packages "0";
APT::Periodic::Unattended-Upgrade "0";No existe la línea:
APT::Periodic::Update-Package-Lists "0"; por lo tanto no podemos poner lo que propone el compañero APT::Periodic::Update-Package-Lists "1";
Link: http://forums.linuxmint.com/viewtopic.php?f=34&t=115128
Bueno eso es lo que he encontrado aquí en el propio foro (inglés), mucha gente opina que es un "bug" de Mint que aún a día de hoy continúa y no se ha solucionado pero el propio Clem (fundador de linux Mint se pronunció contrariado de la siguiente manera):
OK, I subscribed to this topic so I'll be keeping an eye on your feedback.
When you login first, mintupdate is launched with your own permissions... i.e. in user mode. When in that mode it runs only in the system tray, and it does not have sufficient permissions to perform an "apt update". In other words, it does check every X minutes whether things are available, but it cannot refresh the APT cache. So if you use some other APT program in the meantime and thus refresh the APT cache yourself, mintupdate is then able to find new available updates.... if that makes sense...
When you click on mintupdate to see its main window, it basically kills itself and re-launches in root mode. That's why it asks for a password. So, once you've seen the mintupdate main window, from that moment on, it's running in root mode. Before it shows the window, and before it checks for updates it refreshes the APT cache.
You can check the log and you'll see in there whether the update manager is running in user or root mode.
In terms of reliability and rationale, it's not important that an available update appear "immediately". What's important though, is that mintupdate list all available updates in a consistent manner... so for instance, if there's a particular update listed by Synaptic that doesn't appear in MintUpdate that should be considered a bug and we should find the cause for it. If that's the case, please give me as much info as you can, logs, apt policy for the package, versions, etc..
Link: http://forums.linuxmint.com/viewtopic.php?f=34&t=69859Well, it all comes down to one thing and one thing only: You need to refresh your APT cache to see if there are "new" updates. For this, you need to elevate yourself to root.
When you click on mintupdate, it launches itself in root mode, and that's why it asks for a password. When you type "apt update" (which is the same as "sudo apt-get update"), you're asked for a password too.. as you're elevating yourself as root to refresh the cache. Either way, you're refreshing your cache when you do that.
What's important to realise here, is that mintUpdate isn't designed to "alert" you in "real time". It's not a server admin tool to keep your box up to date "the minute" something is released in the repositories. Its primary function is to make it easy for people to upgrade and to prevent novice users from upgrading sensitive parts of their system (via the level system).
Note however, that if you wanted mintUpdate to find updates and alert you in real time, all you'd have to do is to create a cron job that regularly calls "apt update". This would refresh the cache for you in the background and mintUpdate would then be able to find new updates, whether it's in root mode or user mode.
Repito que toda esta información la encontré en el foro de Linux mint en su versión inglesa, pero si alguien esta interesado en profundizar sobre el tema puede acudir aquí:
http://hatteras.wordpress.com/2010/12/02/crontab-programarautomatizar-tareas/
http://hatteras.wordpress.com/2010/12/15/programarautomatizar-tareas-repetitivas-con-gnome-schedule/
http://hatteras.wordpress.com/2010/12/21/programarautomatizar-tareas-no-repetitivas-con-el-comando-at/
http://hatteras.wordpress.com/2010/12/27/programarautomatizar-tareas-no-repetitivas-con-gnome-schedule/
Bueno pues aquí esta la información que he encontrado, haber si alguien se le ocurre cómo mostrar en tiempo real que el gestor de actualizaciones muestre las actualizaciones disponibles ....
