Banshee freezes on mtp device connect (Sony NWZ-E 436F)

On Tue, 08 Jun 2010 09:03:24 -0000
Alvaro Aleman <email address hidden> wrote:

> Public bug reported:
>
> Binary package hint: banshee
>
> If my Sony NWE-E436F is connected and I start Banshee afterwards, it
> freezes. Same situation if Banshee is already started and I plug in
> the device.

Could you post the output of "LANG=C banshee --debug" and "lsusb
-tv" with the device plugged in for debugging purposes, please?

  status incomplete

--
Kind regards,
Chow Loong Jin

I had to kill Banshee because of the freeze, so please don't wonder about the end in the "LANG=C banshee --debug" file

On Fri, 11 Jun 2010 16:57:21 -0000
Alvaro Aleman <email address hidden> wrote:

> I had to kill Banshee because of the freeze, so please don't wonder
> about the end in the "LANG=C banshee --debug" file
>

Instead of killing banshee when it freezes, try "killall -SIGQUIT
banshee-1", which causes Banshee to dump out a stack trace when --debug
is used. That'll yield more information.

--
Kind regards,
Chow Loong Jin

I think I have the same problem but with a different sony walkman (Sony Walkman NWZ-S615F/NWZ-S616F/NWZ-S618F)
it only crashes if I plugin the player while banshee is running.
I could provide additional information if needed. (please advise)

Could you check if this issue is present in Banshee 1.7.5? It is available in the Banshee Unstable PPA at https://launchpad.net/~banshee-team/+archive/banshee-unstable.

With manshee 1.7.5 the freeze does not accur anymore but the device is also not working.
I attached the banshee-debug output.
after that, the player is visible to banshee, but nothing can be transferred.
also, the player says it is not connected anymore.

Nearly the same over here

No freezes anymore, the device appears in Banshee, but does not work (file transfering, showing the content).

Why was this bug marked as incomplete and now as expired? The device still doesn't work with Banshee!

On Friday 29,October,2010 06:47 AM, Alvaro Aleman wrote:
> Why was this bug marked as incomplete and now as expired? The device
> still doesn't work with Banshee!
>

The bug status was updated over at
https://bugzilla.gnome.org/show_bug.cgi?id=621352, due to a lack of response.
This link was obtained from the gnome-bugs link on the Banshee row.

If you wish to amend/revert this status, please test with 1.8.0 and post your
findings over at the upstream GNOME bug tracker. Banshee 1.8.0 is available in
maverick-proposed, natty, and the Banshee PPA (ppa:banshee-team/ppa) for Karmic,
Lucid and Maverick.

--
Kind regards,
Chow Loong Jin

Upstream comments said:
> No package 'boo' found
> Nevertheless, the package "boo" (v. 0.9.2.3383+dfsg-1) is installed. Any
> advices how to fix this?

Install the debug package for it. However that's stuff for a forum and
unrelated to this report. :)

Alvaro any news about this issue? Could be possible if you can try to reproduce this issue using latest release of banshee from PPA?

Since there is another guy who has reported this issue is still there and he has provided additional information I have marked this problem as triaged for now.

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Generally for MTP devices this might be of use:
http://mail.gnome.org/archives/banshee-list/2011-November/msg00036.html

Closing this bug report due to lack of information. If you are affected by this bug, please submit the information requested in the GNOME bugtracker (see the gnome-bugs link).