[ubuntu-mono] [Bug 768092] Re: error when try to start several banshee instances at the same time

[Chow Loong Jin]

*** This bug is a duplicate of bug 766303 ***
    https://bugs.launchpad.net/bugs/766303

On 26/04/2011 02:29, Kamus wrote:
> Which version of banshee do you use? by the way, I tried to reproduce
> ths issue here with banshee 2.0 included in Ubuntu Natty but it works
> fine for me (tried to run three instances of banshee in a terminal)
> 
> ** Changed in: banshee (Ubuntu)
>    Importance: Undecided => Low
> 

I reckon this is a duplicate of Bug #766303, where multiple Banshee instances
launched at the same time did not detect each other and all tried to lock the
sqlite database at the same time.

  duplicate 766303

To reliably reproduce this issue, you can do "banshee & banshee & banshee &"
which will launch three instance at once (timing is important). It may be that
only multiprocessor machines can reproduce this bug -- I haven't actually tried
on any other machine apart from my laptop running a Core 2 Duo.

-- 
Kind regards,
Loong Jin


** This bug has been marked a duplicate of bug 766303
   Fatal error after start of Banshee 2.0
 * You can subscribe to bug 766303 by following this link: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/766303/+subscribe

** This bug has been marked a duplicate of bug 766303
   Fatal error after start of Banshee 2.0
 * You can subscribe to bug 766303 by following this link: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/766303/+subscribe

-- 
You received this bug notification because you are a member of Ubuntu
CLI/Mono Uploaders, which is subscribed to banshee in Ubuntu.
https://bugs.launchpad.net/bugs/768092

Title:
  error when try to start several banshee instances at the same time

Status in “banshee” package in Ubuntu:
  New

Bug description:
  Binary package hint: banshee

  With three open terminals I entered in each  a banshee command and got
  this error in the first tab.

  $ banshee

  Unhandled Exception: System.Exception: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
    at Halie.Client+IClientWindowProxy.Present () [0x00000] in <filename unknown>:0 
    at Halie.Client.HandleWindowCommands (Boolean present) [0x00000] in <filename unknown>:0 
    at Halie.Client.Main () [0x00000] in <filename unknown>:0 
    at (wrapper managed-to-native) System.AppDomain:ExecuteAssembly (System.Reflection.Assembly,string[])
    at System.AppDomain.ExecuteAssemblyInternal (System.Reflection.Assembly a, System.String[] args) [0x00000] in <filename unknown>:0 
    at System.AppDomain.ExecuteAssembly (System.String assemblyFile, System.Security.Policy.Evidence assemblySecurity, System.String[] args) [0x00000] in <filename unknown>:0 
    at (wrapper remoting-invoke-with-check) System.AppDomain:ExecuteAssembly (string,System.Security.Policy.Evidence,string[])
    at System.AppDomain.ExecuteAssembly (System.String assemblyFile) [0x00000] in <filename unknown>:0 
    at (wrapper remoting-invoke-with-check) System.AppDomain:ExecuteAssembly (string)
    at Booter.Booter.BootClient (System.String clientName) [0x00000] in <filename unknown>:0 
    at Booter.Booter.Main () [0x00000] in <filename unknown>:0 

  In the second tab I enabled --redirect-log and got no error at all,
  but nothing happened.

  In the third tab I enabled --redirect-log, but I got an error though.
  Unhandled Exception: System.Exception: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

  Server stack trace:

  
  Exception rethrown at [0]: 

    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke
  (System.Runtime.Remoting.Proxies.RealProxy rp, IMessage msg,
  System.Exception& exc, System.Object[]& out_args) [0x00000] in
  <filename unknown>:0