Bug#654583: WARNING: gnome-keyring:: no socket to connect to
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 ___ forensics-devel mailing list forensics-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel
Bug#654583: WARNING: gnome-keyring:: no socket to connect to
Hi, 2012/1/7 Julien Valroff jul...@debian.org: Can you please send the related part of rkhunter.log? This does not appear on any rkhunter log file. If I think more about this, it cannot be in the log file if this goes to stderr and to the output of cron - email. I cannot reproduce this on my system. Does it happen after you have closed your X session (ie. gnome-keyring could still be running) or also after a fresh boot? The strange part is that the message comes from other cron.daily jobs too, not only from rkhunter. For example in the last days: # Date: Thu, 05 Jan 2012 20:26:29 +0200 /etc/cron.daily/apt: WARNING: gnome-keyring:: no socket to connect to # Date: Fri, 06 Jan 2012 07:02:53 +0200 # Date: Sat, 07 Jan 2012 13:09:49 +0200 /etc/cron.daily/00logwatch: WARNING: gnome-keyring:: no socket to connect to # Date: Sun, 08 Jan 2012 13:20:10 +0200 /etc/cron.daily/00logwatch: WARNING: gnome-keyring:: no socket to connect to /etc/cron.daily/apt: WARNING: gnome-keyring:: no socket to connect to # Date: Mon, 09 Jan 2012 10:12:19 +0200 /etc/cron.daily/apt: WARNING: gnome-keyring:: no socket to connect to 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? Thanks ___ forensics-devel mailing list forensics-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/forensics-devel
