Hi, yes almost everyday, so looking at updates for day 2009-12-22 (there is always a full poweroff each night), I found:
Log started: 2009-12-22 23:37:54
Preparing to replace netbase 4.37 (using .../archives/netbase_4.40_all.deb) ...
Unpacking replacement netbase ...
Setting up netbase (4.40) ...
Installing new version of config file /etc/services ...
Installing new version of config file /etc/init.d/networking ...
Setting up libhal1 (0.5.14-1) ...
Setting up libhal-storage1 (0.5.14-1) ...
Setting up hal (0.5.14-1) ...
Reloading system message bus config...done.
Starting Hardware abstraction layer: hald.
Did not include the mono update logs.
DOH, reading the windows timestamp on /etc/services not the accessed time.
No entry in there for 5900, but don't know if it ever was.
Had a look at changelog for netbase, no help:
netbase (4.40) unstable; urgency=low
* Fixed removal of /etc/sysctl.d/ on purge. (Closes: #560164)
* etc-services: added zabbix-agent (10050), zabbix-trapper (10051).
On the 23rd though wireshark got an update but Vino-server and azareus (Vuse) had stopped working with tcp and chosen to use tcp6.
Preparing to replace wireshark 1.2.4-3 (using .../wireshark_1.2.5-1_i386.deb) ...
Setting up wireshark-common (1.2.5-1) ...
Setting up wireshark (1.2.5-1) ...
I did add to /etc/modprobe.d/blacklist.conf
but that made no difference so removed it.
So its definately after the update on 22/12/2009 update.
Log ended: 2009-12-22 23:41:42
I think I was able to access on the am via vino, but may have done the wireshark update
Log started: 2009-12-23 12:47:03
and after this and a reboot (as I was testing some Main switch on/off software) that it stopped allowing access.
Can't see how wireshark would effect??
So apt-get remove wireshark and a reboot later, still no difference.
Then did a apt-get autoremove but still Vuze and Vino won't work. Vuze insist that something else is using port 127.0.0.1:6886.