← Back to team overview

desktop-packages team mailing list archive

[Bug 845031] [NEW] U1MS extension severely delays startup if syncdaemon cannot be started

 

Public bug reported:

I have a session in which you can't start the sync daemon for whatever
reason.  Probably because it's not a Unity or GNOME session
(gnome-panel/g-s-d with xmonad as WM). In this situation, the U1MS
extension tries to start syncdaemon and cannot:

  ** (Banshee:13609): DEBUG: Syncdaemon not running, waiting for it to
start in NameOwnerChanged

  (Banshee:13609): libsoup-WARNING **: No feature manager for feature of
type 'U1RequestChrome'

  [ here is a delay of maybe 20 seconds ]

  ** (Banshee:13609): WARNING **: Error calling get_info: Did not
receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the
reply timeout expired, or the network connection was broken.

  ** (Banshee:13609): CRITICAL **: syncdaemon_folder_info_get_subscribed: assertion `SYNCDAEMON_IS_FOLDER_INFO (finfo)' failed
  [1 Debug 19:04:22.256] Extension source loaded: Ubuntu One Music Store

And when the source is "loaded", it just displays a message of "Cannot
resolve proxy hostname ()" when invoked.

The source should not block like this when waiting to initialise the
syncdaemon. Certainly not when loading Banshee. Further, if the source
is not going to work correctly due to syncdaemon not being loadable, it
should disable itself rather than present something which doesn't work.

** Affects: banshee (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

- I have a session in which you can't start the sync daemon for whatever reason.
- Probably because it's not a Unity or GNOME session (gnome-panel/g-s-d with
- xmonad as WM). In this situation, the U1MS extension tries to start syncdaemon
- and cannot:
+ I have a session in which you can't start the sync daemon for whatever
+ reason.  Probably because it's not a Unity or GNOME session
+ (gnome-panel/g-s-d with xmonad as WM). In this situation, the U1MS
+ extension tries to start syncdaemon and cannot:
  
-   ** (Banshee:13609): DEBUG: Syncdaemon not running, waiting for it to start in NameOwnerChanged
-  
-   (Banshee:13609): libsoup-WARNING **: No feature manager for feature of type 'U1RequestChrome'
+   ** (Banshee:13609): DEBUG: Syncdaemon not running, waiting for it to
+ start in NameOwnerChanged
  
-   [ here is a delay of maybe 20 seconds ]
+   (Banshee:13609): libsoup-WARNING **: No feature manager for feature of
+ type 'U1RequestChrome'
  
-   ** (Banshee:13609): WARNING **: Error calling get_info: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
-  
-   ** (Banshee:13609): CRITICAL **: syncdaemon_folder_info_get_subscribed: assertion `SYNCDAEMON_IS_FOLDER_INFO (finfo)' failed
-   [1 Debug 19:04:22.256] Extension source loaded: Ubuntu One Music Store
+   [ here is a delay of maybe 20 seconds ]
  
- And when the source is "loaded", it just displays a message of "Cannot resolve
- proxy hostname ()" when invoked.
+   ** (Banshee:13609): WARNING **: Error calling get_info: Did not
+ receive a reply. Possible causes include: the remote application did not
+ send a reply, the message bus security policy blocked the reply, the
+ reply timeout expired, or the network connection was broken.
+ 
+   ** (Banshee:13609): CRITICAL **: syncdaemon_folder_info_get_subscribed: assertion `SYNCDAEMON_IS_FOLDER_INFO (finfo)' failed
+   [1 Debug 19:04:22.256] Extension source loaded: Ubuntu One Music Store
+ 
+ And when the source is "loaded", it just displays a message of "Cannot
+ resolve proxy hostname ()" when invoked.
  
  The source should not block like this when waiting to initialise the
- syncdaemon. Certainly not when loading Banshee. Further, if the source is not
- going to work correctly due to syncdaemon not being loadable, it should disable
- itself rather than present something which doesn't work.
+ syncdaemon. Certainly not when loading Banshee. Further, if the source
+ is not going to work correctly due to syncdaemon not being loadable, it
+ should disable itself rather than present something which doesn't work.

-- 
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/845031

Title:
  U1MS extension severely delays startup if syncdaemon cannot be started

Status in “banshee” package in Ubuntu:
  New

Bug description:
  I have a session in which you can't start the sync daemon for whatever
  reason.  Probably because it's not a Unity or GNOME session
  (gnome-panel/g-s-d with xmonad as WM). In this situation, the U1MS
  extension tries to start syncdaemon and cannot:

    ** (Banshee:13609): DEBUG: Syncdaemon not running, waiting for it to
  start in NameOwnerChanged

    (Banshee:13609): libsoup-WARNING **: No feature manager for feature
  of type 'U1RequestChrome'

    [ here is a delay of maybe 20 seconds ]

    ** (Banshee:13609): WARNING **: Error calling get_info: Did not
  receive a reply. Possible causes include: the remote application did
  not send a reply, the message bus security policy blocked the reply,
  the reply timeout expired, or the network connection was broken.

    ** (Banshee:13609): CRITICAL **: syncdaemon_folder_info_get_subscribed: assertion `SYNCDAEMON_IS_FOLDER_INFO (finfo)' failed
    [1 Debug 19:04:22.256] Extension source loaded: Ubuntu One Music Store

  And when the source is "loaded", it just displays a message of "Cannot
  resolve proxy hostname ()" when invoked.

  The source should not block like this when waiting to initialise the
  syncdaemon. Certainly not when loading Banshee. Further, if the source
  is not going to work correctly due to syncdaemon not being loadable, it
  should disable itself rather than present something which doesn't work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/845031/+subscriptions


Follow ups

References