touch-packages team mailing list archive

[HuangZhiquan <ZhiquanHuang@xxxxxxxxxxxxxxx>]

Public bug reported:

every time you click home button it will show you clickscope, when you swipe to another scope,for example video,  you click home button, you should be shown clickscope as code want (in shell.qml, there is a function showHome() and a line code dash.setCurrentScope(),you can change arguments you want), but only focused unity8-dash, in an interesting condition ,when you runs unity8 and unity8-dash with qtcreator, everything works fine, maybe it means the function of setCurrentScope() has some trouble;
what i can see in unity8.log may be about to this condition is below:
"UbuntuClipboard - Failed to get system clipboard contents via D-Bus. org.freedesktop.DBug.Error.NoReply, 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 xepired, or the network connections was broken"

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1452098

Title:
  [Launcher]home button can not setcurrentscope as you want

Status in unity8 package in Ubuntu:
  New

Bug description:
  every time you click home button it will show you clickscope, when you swipe to another scope,for example video,  you click home button, you should be shown clickscope as code want (in shell.qml, there is a function showHome() and a line code dash.setCurrentScope(),you can change arguments you want), but only focused unity8-dash, in an interesting condition ,when you runs unity8 and unity8-dash with qtcreator, everything works fine, maybe it means the function of setCurrentScope() has some trouble;
  what i can see in unity8.log may be about to this condition is below:
  "UbuntuClipboard - Failed to get system clipboard contents via D-Bus. org.freedesktop.DBug.Error.NoReply, 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 xepired, or the network connections was broken"

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