2012/1/10 Julien Valroff <jul...@debian.org>: >> So, on Jan 08 it appeared on two jobs (00logwatch and apt). I'm >> undecided to which package to reassign: cron or gnome-keyring? What do >> you think? > > What happens if you run such a cron job by hand when not in an X session?
Today I watched the Cron run without X/gnome/gdm running at all. The result was the same: # Date: Wed, 11 Jan 2012 07:34:27 +0200 /etc/cron.daily/00logwatch: WARNING: gnome-keyring:: no socket to connect to > I have never seen this behaviour, maybe you have any specific configuration? I don't think so. On all systems (desktops, servers) I have 'ssmtp' to provide the 'sendmail' interface, thus no SMTP daemon. One think I've noticed a few days ago is that something was changing the hostname from the FQDN (frost.DOMAIN -- set from /etc/hostname) to just 'frost' but I didn't investigate further. Also, today I obtained this message while doing packages upgrades: | Processing triggers for man-db ... | Processing triggers for menu ... | Processing triggers for desktop-file-utils ... | Processing triggers for gnome-menus ... | Processing triggers for hicolor-icon-theme ... | Processing triggers for cups ... | Starting Common Unix Printing System: cupsd. | WARNING: gnome-keyring:: no socket to connect to | WARNING: gnome-keyring:: no socket to connect to | Updating PPD files for postscript-hp ... | Updating PPD files for splix ... | Processing triggers for gconf2 ... Usually this warning appears on the email from Cron. Other ideas? Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org