Hi, this comes from Debian Bug#344429 (http://bugs.debian.org/344429)
submitted by Christian Perrier <firstname.lastname@example.org>.
Current amaroK behavior with respect to submit.xml seems to be the following:
after start, when the time for the first submission comes, if there are items
in submit.xml, it sends the first 9 or so, and stores the present one for
later submission. Repeat with next song, etc.
What Christian would like is that, if when amaroK starts and there are items
in submit.xml, that they are tried to be sent immediately, so that the queue
can be cleared even if no music is played.
This sounds a fair wishlist to me, hence I'm forwarding; I do realize, though,
that the implementation for this may add unneeded complexity, and that tieing
clearing the queue with the normal submission process does really simplify the
*** Bug 101547 has been marked as a duplicate of this bug. ***
This is fixed in the latest svn.