AudioScrobbler plugin only reports tracks which were manually played

I can't confirm this here... all tracks are submitted.
Is this with 0.11.0-0ubuntu1? Is there any output on the terminal? Please paste it here...

This is with 0.11.0-0ubuntu1.

Upon further testing, this seems to happen only when the plugin has just been enabled. After closing banshee then opening it again it works as expected. I'm still testing this to make sure.

Will try to get some output from the terminal shortly.

This definitely only happens when the plugin has just been enabled. To reproduce, open the plugins window and deactivate the audioscrobber plugin. Then reactivate it and play some tracks, only the one you double click will be submitted.

Doesn't appear to be anything useful in the terminal output. The last two lines are when I deactivated then reactivated the plugin, there was no output while it was playing:

adam@phoenix:~$ banshee
Warning: [27/09/2006 20:10:11] (Cannot connect to NetworkManager) - An available, working network connection will be assumed
Debug: [27/09/2006 20:10:14] (Default player engine) - GStreamer 0.10
Debug: [27/09/2006 20:10:14] (Audio CD Core Initialised) -
Audioscrobbler starting protocol engine
Warning: [27/09/2006 20:10:15] (Could not initialize plugin `Daap') - Daemon not running
Setting MusicBrainz proxy to www.musicbrainz.org:80

(Banshee:26948): Gtk-CRITICAL **: gtk_tree_view_get_cell_area: assertion `GTK_WIDGET_REALIZED (tree_view)' failed

(Banshee:26948): Gtk-CRITICAL **: gtk_tree_view_get_cell_area: assertion `GTK_WIDGET_REALIZED (tree_view)' failed
Audioscrobbler stopping protocol engine
Audioscrobbler starting protocol engine

I can confirm this.

Then let's set this to confirmed ;)

Posted upstream also:
Tentatively, I figured this out. It looks like the problem is that if NetworkManager is not running or is not able to connect (e.g. because of a static IP configuration), then Banshee will assume there is no network connection. This is a problem IMO.

Can anyone else confirm this?
(For what it's worth, I tested this in Banshee SVN.)

I can confirm this behaviour, but it's not just when you enable scrobbling in Banshee during the current session. It was happening to me even though scrobbling had already been enabled (i.e., it was already enabled when I ran Banshee).

The problem does appear to be with Network Manager. I was using a manual network configuration with a static IP address (needed to forward a port to this laptop). Switching back to roaming mode corrected the issue.

The oddest thing is that when using the manual configuration, Banshee scrobbles all the activity that hasn't been scrobbled, then it just stops scrobbling after that.

Banshee 0.13.1
Ubuntu Gutsy 7.10
2.6.22-14-generic

Just attached the (corrected) upstream bug on this. It's been fixed. There have been other reports of problems (http://bugzilla.gnome.org/show_bug.cgi?id=469490) not related to NetworkManager, but that's a different bug.

So, as mentioned upstream, this should've been in Banshee 0.12 and NetworkManager 0.6.4-6ubuntu7.