banshee doesn't save new last.fm stations

Does it return if you click on the Last.fm icon (i.e. the parent icon of the available stations)?

no

On Thu, 2009-01-29 at 16:29 +0000, Jonne wrote:
> no
>
Hi could you try removing ~/.config/banshee-1 and ~/.config/banshee, and
see if this problem persists? Your settings and library will be
clobbered, so if you want to retain them, you should backup
~/.config/banshee-1.
--
Chow Loong Jin

http://bugzilla.gnome.org/show_bug.cgi?id=548524 seems to indicate this was fixed more recently than I expected. You could try using the Banshee PPA (https://launchpad.net/~banshee-team/+archive/ppa), but I expect this was fixed after 1.4.2.

If your issue appears to be different than what is mentioned upstream, let me know.

I removed ~/.config/banshee-1 (I don't have a ~/.config/banshee )
still the same thing (btw, removing the folder didn't seem to remove my prefs and stuff, where are the banshee settings stored?)

it seems to be the same issue as the one in the gnome bugtracker, so i guess people should just wait for when the new version shows up in backports?

I'll try using the ppa in the meantime.

Tried the ppa version, same issue.

On Thu, Jan 29, 2009 at 5:29 PM, Jonne <email address hidden> wrote:

> Tried the ppa version, same issue.

Yes, I'm pretty sure the PPA version isn't new enough. If you would like to
try the development version, instructions are here:
http://banshee-project.org/download/development. Help with installing that
is outside the scope of this bug or Launchpad in general, but you can feel
free to direct any questions to the mailing list (where Chow Loong Jin and I
join others in helping with Banshee):
http://banshee-project.org/about/contact. :)

i didn't notice the timestamps of the latest posts in the gnome bugreport, apparently it was fixed only 2 days ago or so. I'll just wait for the new version to appear in the ppa or through the backports and listen to my recommendations in the meantime.

This is fixed upstream. Thanks for reporting.

Still not fixed in 1.4.3. I'm not sure what the version number of the trunk was, but whatever fixed it didn't make it into Ubuntu yet.

Jonne,
I just sought clarification upstream, and apparently this was fixed after 1.4.3 also. It will be available in the first 1.5 release.

Also, "Fix Committed" does not imply any release in Ubuntu. (That status is confusing to me since we're tracking the bug upstream already, but there it is.)

In the meantime, it can be requested for a backport once it's released (9.10?) or specifically patched to fix this bug, though I'm not sure how the latter process works.

The thing that confuses me about Launchpad is that it's not clear what we're tracking here. If we're talking in terms of the Banshee that ships with Ubuntu, it's not fixed. If we're talking about Banshee upstream, it seems like it is. It's probably frustrating for upstream too to see bug reports still open while they did their job with fixing them.

So if I want to have this thing fixed for me personally I'll just have to get it from cvs and try to compile? (I tried this before, but I seem to have failed miserably, I'll probably need to get help on IRC for this).

On Mon, 2009-03-09 at 19:04 +0000, Jonne wrote:
> The thing that confuses me about Launchpad is that it's not clear what
> we're tracking here. If we're talking in terms of the Banshee that ships
> with Ubuntu, it's not fixed. If we're talking about Banshee upstream, it
> seems like it is. It's probably frustrating for upstream too to see bug
> reports still open while they did their job with fixing them.
>
> So if I want to have this thing fixed for me personally I'll just have
> to get it from cvs and try to compile? (I tried this before, but I seem
> to have failed miserably, I'll probably need to get help on IRC for
> this).
>
Actually it is pretty clear. Notice that there are two tasks, "Banshee"
and "Banshee (Ubuntu)". If you wish to see this bug fixed, you have two
choices:
      * Wait until someone fixes it in Ubuntu (backport the patch)
      * Compile from SVN yourself.

I'd tackle this myself, but I don't have enough time to handle this at
the moment. I'll be free in another 48 hours or so, so if the bug isn't
fixed by then I'll work on it.
--
Chow Loong Jin

On Mon, Mar 9, 2009 at 15:04, Jonne <email address hidden> wrote:

> The thing that confuses me about Launchpad is that it's not clear what
> we're tracking here. If we're talking in terms of the Banshee that ships
> with Ubuntu, it's not fixed.
>

Right, which is why Banshee in Ubuntu is marked as Fix Committed (meaning
the fix has been committed to the source tree of the project—Banshee
itself.)

If we're talking about Banshee upstream, it
> seems like it is. It's probably frustrating for upstream too to see bug
> reports still open while they did their job with fixing them.
>

Launchpad tracks everything. So you'll see the Banshee line at the top,
which is coming from the upstream bug, marked Fix Released. The developers
use an external bugtracker, Bugzilla, and only see their bug as being fixed.
No frustration for them.

So if I want to have this thing fixed for me personally I'll just have
> to get it from cvs and try to compile? (I tried this before, but I seem
> to have failed miserably, I'll probably need to get help on IRC for
> this).
>

Yes, only if you want the fix in the immediate short-term. My guess is that
it will be fixed pretty quickly since it's been committed (the Banshee
maintainers do a great job packaging fixes and new versions).

If you're inclined to install the development version, you can find
instructions here: http://banshee-project.org/download/development. If you
run into trouble, please don't post here, but feel free to seek help
directly: http://banshee-project.org/about/contact.

On Mon, Mar 9, 2009 at 15:23, hyperair <email address hidden> wrote:

> I'd tackle this myself, but I don't have enough time to handle this at
> the moment. I'll be free in another 48 hours or so, so if the bug isn't
> fixed by then I'll work on it.

See Jonne? Like I said. ;)

On Mon, 2009-03-09 at 19:40 +0000, Andrew Conkling wrote:
> On Mon, Mar 9, 2009 at 15:23, hyperair <email address hidden> wrote:
>
> > I'd tackle this myself, but I don't have enough time to handle this at
> > the moment. I'll be free in another 48 hours or so, so if the bug isn't
> > fixed by then I'll work on it.
>
>
> See Jonne? Like I said. ;)
>
I've uploaded a fix (patch from SVN) to the PPA (1.4.3-1~intrepid2).
Please test. If that fix works, I'll try and see if I can get it into
Debian, then request a merge.

--
Chow Loong Jin

I can confirm this is fixed, although now i have a huge list of my personal radio station repeated for every time i ever added it, but that's no big deal, imho.

thanks for this,
hyperair :-)

On Thu, 2009-03-12 at 12:10 +0000, Jonne wrote:
> I can confirm this is fixed, although now i have a huge list of my
> personal radio station repeated for every time i ever added it, but
> that's no big deal, imho.
>
> thanks for this,
> hyperair :-)
>
Awesome. =)
--
Chow Loong Jin

This bug was fixed in the package banshee - 1.4.3-3ubuntu1

---------------
banshee (1.4.3-3ubuntu1) jaunty; urgency=low

  * Merge from debian unstable (LP: #343059), remaining changes:
    + debian/control: GNOME# 2.24 transition
  * Also fixes issue where Last.fm personal stations are not loaded
    (LP: #322781)

banshee (1.4.3-3) unstable; urgency=low

  * debian/control:
    + Add me to Uploaders
  * debian/patches/03_fix-lastfm.patch:
    + Fix issue where Last.fm personal stations are not loaded
  * debian/patches/debian/patches/20_check_notification_support.patch:
    + Check whether notification daemon supports actions

banshee (1.4.3-2) unstable; urgency=low

  * debian/control:
    + Build depend on libtaglib2.0-cil >= 2.0.3.2 (Closes: #518755).

 -- Chow Loong Jin <email address hidden> Sun, 15 Mar 2009 14:21:02 +0800