desktop-packages team mailing list archive

[Iain Lane <iain@xxxxxxxxxxxxxxxxxxx>]

On Fri, Sep 09, 2011 at 08:05:55PM -0000, Rodney Dawes wrote:
> You can test that by opening banshee, and immediately start music
> playing before the 10s timeout. If it's going to hang, the music should
> pause/stutter/something while it's rescanning, but it didn't seem to do
> this for me when I tested.

The music does not hang, but the UI does. I'm sure it's the U1
extension, because I started banshee without it, began to play a song
and then enabled the extension. Exactly 10 seconds after I enabled the
extension, the UI hung for 25 seconds (presumably while it was waiting
for the DBUS timeout).

-- 
Iain Lane                                  [ iain@xxxxxxxxxxxxxxxxxxx ]
Debian Developer                                   [ laney@xxxxxxxxxx ]
Ubuntu Developer                                   [ laney@xxxxxxxxxx ]
PhD student                                       [ ial@xxxxxxxxxxxxx ]

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to banshee in Ubuntu.
https://bugs.launchpad.net/bugs/788532

Title:
  U1 music store plugin severely delays banshee startup

Status in Ubuntu One widget library:
  Fix Committed
Status in “banshee” package in Ubuntu:
  Invalid
Status in “libubuntuone” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: banshee

  Everytime Banshee starts a blank window appears, then after a few
  seconds it turns grey and stays grey for about 20 seconds, then
  finally the UI populates.  I ran Banshee with --debug and piped the
  output to a log file using tee.  I watched the log file while Banshee
  starts and as soon as all the plugins are loaded the U1 music store
  plugin start iterating over every music file I have purchased checking
  whether it has been copied to ~/Music.  If the file already exists
  then the log says something like "not copying because this file
  already exists in  ${HOME}/Music/.  During this exhaustive check is
  when Banshee's window goes grey (which is I think Compiz telling me
  the window is not sending updates and inactive).  As soon as those
  checks end, Banshee paints the window and I can use Banshee.

  I thought maybe the problem was that the files didn't need to be in
  ~/Music, so I deleted any files in ~/Music that were already in
  ~/.ubuntuone/Purchased from Ubuntu One/.  On next startup the log file
  showed the check w/o the "not copying messages" and Banshee started
  somewhat faster (but by no means fast).  I noticed I missed one file
  so I deleted that file in ~/Music and reran Banshee and watched the
  log file.  This time again all the files were back in ~/Music and
  Banshee took forever to start.

  This may have one other side effect.  I noticed that many of my
  purchased songs show up multiple times in my Library.  For instance, I
  purchased a song call "Hello" by Martin Solvig and that appears in my
  library five times.  Looking in ~/Music I see the file has been copied
  multiple times so I have the same file name with (n) appended to it.
  If I delete the dups they just reappear over time.

  This all seems very broken and wrong.

  1.  Why does the U1MS plugin need to check every time for purchases it has already recognised?
  2.  Why do the files need to be copied to ~/Music when it could just watch ~/.ubuntuone/Purchased from Ubuntu One/
  3.  Why do I keep getting multiple copies of purchased songs even after I delete the duplicates?

  Will attach my latest log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: banshee-extension-ubuntuonemusicstore 2.0.0-2ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Thu May 26 09:57:33 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110120)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: banshee
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libubuntuone/+bug/788532/+subscriptions