Ubuntu
banshee package

select songs to burn enters brasero reversed

Bug #238431 reported by cyberdwarf
6
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

When either a playlist of songs or a group or songs are selected (shift-click), they are sent from banshee to brasero in reversed order. A workaround is the soft by track number in reverse order before selecting "edit, burn cd". This saves having to re-sort the songs before burning them onto cd.

Revision history for this message
cyberdwarf (cyberdwarf) wrote :

"the soft" *to sort

Revision history for this message
cyberdwarf (cyberdwarf) wrote :

https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/221710

Same bug. Probably brasero's, integration ferreted it out.

Revision history for this message
Andrew Conkling (andrewski) wrote :

Which version of Banshee?

Changed in banshee:
status: New → Incomplete
Revision history for this message
cyberdwarf (cyberdwarf) wrote : Re: [Bug 238431] Re: select songs to burn enters brasero reversed

it says 1.0.0 but I think it may have more to do with brasero, as I
found another very similar bug for brasero, and it may be re-sorting the
tracks as it receives them from banshee.

Andrew Conkling wrote:
> Which version of Banshee?
>
> ** Changed in: banshee (Ubuntu)
> Status: New => Incomplete
>
>

Revision history for this message
Andrew Conkling (andrewski) wrote :

Bugs from 1.0 aren't valid in Ubuntu yet... unless you're on Intrepid?

Revision history for this message
cyberdwarf (cyberdwarf) wrote :

No, hardy. How do I upgrade using repos? I thought I was using proposed
and backports. Well, just thought I would pass it along. -b

Andrew Conkling wrote:
> Bugs from 1.0 aren't valid in Ubuntu yet... unless you're on Intrepid?
>
>

Revision history for this message
Jayson Rowe (jayson.rowe) wrote :

Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and find out what additional work should be done on this bug.

Revision history for this message
cyberdwarf (cyberdwarf) wrote :

I've personally not dealt with it for a long time since filing it. Sorry
I can't be more help. -b

JaysonRowe wrote:
> Since it's been a very long time since any additional info was added to
> this bug, I'm just checking to see if this is still an issue, and find
> out what additional work should be done on this bug.
>
>

Revision history for this message
Jayson Rowe (jayson.rowe) wrote :

Closing for now due to original reporters comment.

Changed in banshee:
status: Incomplete → Invalid
Revision history for this message
Andrew Conkling (andrewski) wrote :

Not to be nitpicky, but I'm assuming there were some upstream fixes in Brasero or one of many fixes in Banshee that make this work, so I'm changing the status from Invalid to Fix Released. I just tested and the order is indeed correct, but I cannot recall if I could reproduce it before.

Changed in banshee:
status: Invalid → Fix Released
Revision history for this message
cyberdwarf (cyberdwarf) wrote :

I guess it has been fixed, though I have not tested it since. Thanks. It
is so great to use an OS where there are people interested in making it
better! -Bill H.

Andrew Conkling wrote:
> Not to be nitpicky, but I'm assuming there were some upstream fixes in
> Brasero or one of many fixes in Banshee that make this work, so I'm
> changing the status from Invalid to Fix Released. I just tested and the
> order is indeed correct, but I cannot recall if I could reproduce it
> before.
>
> ** Changed in: banshee (Ubuntu)
> Status: Invalid => Fix Released
>
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.