[Dx-packages] [Bug 1262022] Re: incorrect multi-arch related meta information.

2017-01-12 Thread Launchpad Bug Tracker 
This bug was fixed in the package overlay-scrollbar -
0.2.17.1+16.04.20151117-0ubuntu1.16.04.1

---
overlay-scrollbar (0.2.17.1+16.04.20151117-0ubuntu1.16.04.1) xenial; 
urgency=medium

  * Mark overlay-scrollbar Multi-Arch: foreign. (LP: #1262022)

 -- Stefano Rivera   Sat, 24 Dec 2016 15:43:12
-0500

** Changed in: overlay-scrollbar (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to overlay-scrollbar in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1262022

Title:
  incorrect multi-arch related meta information.

Status in overlay-scrollbar package in Ubuntu:
  Fix Released
Status in overlay-scrollbar source package in Xenial:
  Fix Released
Status in overlay-scrollbar source package in Yakkety:
  Fix Released

Bug description:
  == SRU Impact ==
  overlay-scrollbar-gtk2:i386 is uninstallable on amd64, which blocks the 
installation of some packages.

  == Test Case ==

  On amd64:
  dpkg --add-architecture i386
  apt update
  apt install overlay-scrollbar-gtk2:i386

  Either this succeeds, or fails (this bug)

  == Regression potential ==

  Nil (or close enough)

  == Original Bug ==

  I'm on a 64-bit system trying to install "overlay-scrollbar-gtk2:i386"
  which depends on the "overlay-scrollbar:i386" package. "overlay-
  scrollbar:i386" doesn't have an install candidate because it's a
  "multi-arch" package. This should (or so I've been told) be reflected
  in the meta information of the "overlay-scrollbar" package but isn't,
  which is why the former package fails to install.

  As a more competent person than I put it:

  "The overlay-scrollbar package does not come in i386 or amd64 flavors;
  it comes as an "all" flavor, which installs on all archs.

  It appears to be missing the Multi-Arch: allowed header so it won't
  satisfy an i386 package depending on it. You should file a bug report
  asking that the missing header be added."

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: overlay-scrollbar 0.2.16+r359+13.10.20130826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Dec 18 02:14:35 2013
  InstallationDate: Installed on 2013-12-14 (3 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: overlay-scrollbar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1262022/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1262022] Re: incorrect multi-arch related meta information.

2017-01-12 Thread Launchpad Bug Tracker 
This bug was fixed in the package overlay-scrollbar -
0.2.17.1+16.04.20151117-0ubuntu1.16.10.1

---
overlay-scrollbar (0.2.17.1+16.04.20151117-0ubuntu1.16.10.1) yakkety; 
urgency=medium

  * Mark overlay-scrollbar Multi-Arch: foreign. (LP: #1262022)

 -- Stefano Rivera   Sat, 24 Dec 2016 15:43:12
-0500

** Changed in: overlay-scrollbar (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to overlay-scrollbar in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1262022

Title:
  incorrect multi-arch related meta information.

Status in overlay-scrollbar package in Ubuntu:
  Fix Released
Status in overlay-scrollbar source package in Xenial:
  Fix Released
Status in overlay-scrollbar source package in Yakkety:
  Fix Released

Bug description:
  == SRU Impact ==
  overlay-scrollbar-gtk2:i386 is uninstallable on amd64, which blocks the 
installation of some packages.

  == Test Case ==

  On amd64:
  dpkg --add-architecture i386
  apt update
  apt install overlay-scrollbar-gtk2:i386

  Either this succeeds, or fails (this bug)

  == Regression potential ==

  Nil (or close enough)

  == Original Bug ==

  I'm on a 64-bit system trying to install "overlay-scrollbar-gtk2:i386"
  which depends on the "overlay-scrollbar:i386" package. "overlay-
  scrollbar:i386" doesn't have an install candidate because it's a
  "multi-arch" package. This should (or so I've been told) be reflected
  in the meta information of the "overlay-scrollbar" package but isn't,
  which is why the former package fails to install.

  As a more competent person than I put it:

  "The overlay-scrollbar package does not come in i386 or amd64 flavors;
  it comes as an "all" flavor, which installs on all archs.

  It appears to be missing the Multi-Arch: allowed header so it won't
  satisfy an i386 package depending on it. You should file a bug report
  asking that the missing header be added."

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: overlay-scrollbar 0.2.16+r359+13.10.20130826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Dec 18 02:14:35 2013
  InstallationDate: Installed on 2013-12-14 (3 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: overlay-scrollbar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1262022/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1262022] Update Released

2017-01-12 Thread Brian Murray 
The verification of the Stable Release Update for overlay-scrollbar has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to overlay-scrollbar in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1262022

Title:
  incorrect multi-arch related meta information.

Status in overlay-scrollbar package in Ubuntu:
  Fix Released
Status in overlay-scrollbar source package in Xenial:
  Fix Released
Status in overlay-scrollbar source package in Yakkety:
  Fix Released

Bug description:
  == SRU Impact ==
  overlay-scrollbar-gtk2:i386 is uninstallable on amd64, which blocks the 
installation of some packages.

  == Test Case ==

  On amd64:
  dpkg --add-architecture i386
  apt update
  apt install overlay-scrollbar-gtk2:i386

  Either this succeeds, or fails (this bug)

  == Regression potential ==

  Nil (or close enough)

  == Original Bug ==

  I'm on a 64-bit system trying to install "overlay-scrollbar-gtk2:i386"
  which depends on the "overlay-scrollbar:i386" package. "overlay-
  scrollbar:i386" doesn't have an install candidate because it's a
  "multi-arch" package. This should (or so I've been told) be reflected
  in the meta information of the "overlay-scrollbar" package but isn't,
  which is why the former package fails to install.

  As a more competent person than I put it:

  "The overlay-scrollbar package does not come in i386 or amd64 flavors;
  it comes as an "all" flavor, which installs on all archs.

  It appears to be missing the Multi-Arch: allowed header so it won't
  satisfy an i386 package depending on it. You should file a bug report
  asking that the missing header be added."

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: overlay-scrollbar 0.2.16+r359+13.10.20130826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Wed Dec 18 02:14:35 2013
  InstallationDate: Installed on 2013-12-14 (3 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: overlay-scrollbar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1262022/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 779782] [NEW] Mouse release does not activate playback control buttons

2017-01-12 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

indicator-sound 0.6.6.1-0ubuntu3, Ubuntu 11.04
indicator-sound 12.10.2+14.04.20140401-0ubuntu1, Ubuntu 14.04

In maverick's sound menu, it was possible to activate the banshee or
rhythmbox play/pause, back, and forward controls by pressing the mouse
on the indicator applet sound icon, dragging to the chosen control with
the mouse button held down, and releasing the mouse button. It looks
like the sound menu spec at https://wiki.ubuntu.com/SoundMenu is
ambiguous as to whether this should activate the controls, but all other
menu items in the indicator applet can be activated in this way (as an
example, the mute option in the sound menu). The fact that this no
longer works for the playback control buttons seems like a bug.

To be clear, click/release on the sound menu icon followed by
click/release on the playback buttons works perfectly well. The
inconsistency is in the playback buttons being more picky than other
menu items, in that they can't be triggered by just a mouse release.

: "Conversely, clicking on
a different menu item (or any menu title), moving to a button, and
releasing, should activate that button."

** Affects: ido (Ubuntu)
 Importance: Low
 Status: Triaged


** Tags: apport-bug i386 natty
-- 
Mouse release does not activate playback control buttons
https://bugs.launchpad.net/bugs/779782
You received this bug notification because you are a member of DX Packages, 
which is subscribed to ido in Ubuntu.

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1370884] Re: bluetooth icon in indicators keep showing connected

2017-01-12 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: indicator-bluetooth (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1370884

Title:
  bluetooth icon in indicators keep showing connected

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  bluetooth icon in indicators keep showing connected afer even
  forgetting/disconnecting the bt headset.

  Steps to reproduce:
  1. Pair/Connect the bluetooth headtset with krillin
  2. Note that bluetooth icon in indicators is changed, showing device is 
connected over bluetooth.
  3. Now go to bluetooth settings and then further to connected headset's 
setting page.
  4. Tap on Forget this device'

  Observe that despite device is no longer paired and disconnected the
  bluetooth icon in indicators won't change to unpaired state. (see
  attached png)

  Device/Build Info:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 1
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09
  last update: 2014-09-16 17:43:20
  version version: 1
  version ubuntu: 20140916
  version device: 20140912-238

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1370884/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1655712] Re: Broken Qt application indicator icons due to indicator-application-service

2017-01-12 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: indicator-application (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-application in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1655712

Title:
  Broken Qt application indicator icons due to indicator-application-
  service

Status in indicator-application package in Ubuntu:
  Confirmed

Bug description:
  Dear all,

  The tray icon indicator of Qt applications breaks on resume from
  suspend, meaning it has a missing icon.

  It doesn't happen to GTK applications.

  I can work around it by running `killall indicator-application-
  service` and then restart the service with `/usr/lib/x86_64-linux-gnu
  /indicator-application/indicator-application-service4-linux-gnu
  /indicator-application/indicator-applic`.

  Other resources suggest to installing sni-qt:i386 should fix the
  problem but it doesn't.

  I would really appreciate any help on this problem.

  Please also see my attached screenshot.

  Yours,

  -Robert

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1655712/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1656058] Re: package url-dispatcher:i386 0.1+16.10.20160816.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-01-12 Thread Apport retracing service 
*** This bug is a duplicate of bug 1656059 ***
https://bugs.launchpad.net/bugs/1656059

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1656059, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1656059
   package url-dispatcher:i386 0.1+16.10.20160816.1-0ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to url-dispatcher in Ubuntu.
https://bugs.launchpad.net/bugs/1656058

Title:
  package url-dispatcher:i386 0.1+16.10.20160816.1-0ubuntu1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  It occured when upgrading Ubuntu 16.04 to 16.10.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: url-dispatcher:i386 0.1+16.10.20160816.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic i686
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: i386
  Date: Thu Jan 12 19:26:04 2017
  DuplicateSignature:
   package:url-dispatcher:i386:0.1+16.10.20160816.1-0ubuntu1
   Setting up libunity-scopes1.0:i386 (1.0.7+16.10.20160921-0ubuntu2) ...
   Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
   dpkg: error processing package libunity-scopes1.0:i386 (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-09-20 (114 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.3
  SourcePackage: url-dispatcher
  Title: package url-dispatcher:i386 0.1+16.10.20160816.1-0ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to yakkety on 2017-01-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1656058/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1656058] [NEW] package url-dispatcher:i386 0.1+16.10.20160816.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-01-12 Thread ivan 
*** This bug is a duplicate of bug 1656059 ***
https://bugs.launchpad.net/bugs/1656059

Public bug reported:

It occured when upgrading Ubuntu 16.04 to 16.10.

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: url-dispatcher:i386 0.1+16.10.20160816.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic i686
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: i386
Date: Thu Jan 12 19:26:04 2017
DuplicateSignature:
 package:url-dispatcher:i386:0.1+16.10.20160816.1-0ubuntu1
 Setting up libunity-scopes1.0:i386 (1.0.7+16.10.20160921-0ubuntu2) ...
 Cannot start click due to a conflict with a different locally-installed Python 
'click' package.  Remove it using Python packaging tools and try again.
 dpkg: error processing package libunity-scopes1.0:i386 (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-09-20 (114 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.3
SourcePackage: url-dispatcher
Title: package url-dispatcher:i386 0.1+16.10.20160816.1-0ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: Upgraded to yakkety on 2017-01-12 (0 days ago)

** Affects: url-dispatcher (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 yakkety

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to url-dispatcher in Ubuntu.
https://bugs.launchpad.net/bugs/1656058

Title:
  package url-dispatcher:i386 0.1+16.10.20160816.1-0ubuntu1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  It occured when upgrading Ubuntu 16.04 to 16.10.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: url-dispatcher:i386 0.1+16.10.20160816.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic i686
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: i386
  Date: Thu Jan 12 19:26:04 2017
  DuplicateSignature:
   package:url-dispatcher:i386:0.1+16.10.20160816.1-0ubuntu1
   Setting up libunity-scopes1.0:i386 (1.0.7+16.10.20160921-0ubuntu2) ...
   Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
   dpkg: error processing package libunity-scopes1.0:i386 (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-09-20 (114 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.3
  SourcePackage: url-dispatcher
  Title: package url-dispatcher:i386 0.1+16.10.20160816.1-0ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to yakkety on 2017-01-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1656058/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 652978] Re: Notifications should be suppressed when indicators open

2017-01-12 Thread Treviño 
It's not up to unity to request the notification, but to indicator-
sound.

However, it can have an idea about what has changed by monitoring 
unity-panel-service status.
Probably this can be done in notify-osd, though... By always delaying pop-ups 
when an indicator menu is open.

** Changed in: unity (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: notify-osd (Ubuntu)
   Status: Invalid => Triaged

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/652978

Title:
  Notifications should be suppressed when indicators open

Status in notify-osd package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Invalid

Bug description:
  When using the sound menu, the user is immediately visually notified
  about switching of tracks by the menu itself.

  +

  When notifying using Notify-OSD, it covers some parts of sound menu
  itself. I think Notify-OSD should not be shown when switching tracks
  using the sound-menu and MAY BE whenever switching manually.

  Example video:
  http://dl.dropbox.com/u/275756/out.ogv

  PS:
  U1 was not working, so dropbox. :)
  and yes, I did spend like 10 minutes thinking which songs I should show in 
the video. :P

  The equivalent for the volume slider is bug 1389761.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/652978/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1573639] Re: ownCloud Client system tray icon integration broken

2017-01-12 Thread Dominique Meeùs 
Memory 3,8 Gb. Ubuntu 16.10 up to date as of today. Desktop is Flashback with 
Nemo. Appmenu-qt5 is not installed. Indicator-applet-complete 
12.10.2+15.20141127.2-0ubuntu1, indicator-application 
12.10.1+15.20150128.2-0ubuntu1.
Indicator-applet gets mad after some time. At the beginning of the session, the 
indicator appears, with ownCloud client (2.2.2+dfsg-1). It is possible to work 
while ownCloud is synchronizing. After two or three hours work, everything 
slows down to nearly freezing. Is seems impossible to get the ownCloud menu 
from the indicator to quit ownCloud. It takes a long time to even get a 
terminal and start top to see indicator-applet at 100 % CPU. Killing the 
owncloud process takes a very long time after the kill command. Then the 
indicator gradually calms down and it is possible to go on working.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to appmenu-qt5 in Ubuntu.
https://bugs.launchpad.net/bugs/1573639

Title:
  ownCloud Client system tray icon integration broken

Status in appmenu-qt5 package in Ubuntu:
  Fix Released
Status in owncloud-client package in Ubuntu:
  Fix Released
Status in appmenu-qt5 source package in Xenial:
  Invalid
Status in owncloud-client source package in Xenial:
  Fix Released
Status in appmenu-qt5 source package in Yakkety:
  Fix Released
Status in owncloud-client source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  The ownCloud client in Xenial is compiled against Qt 5.5.1. when
  starting the client, the system tray icon does not show up, making the
  application essentially useless.

  See also: https://github.com/owncloud/client/issues/4693.

  [Test case]

  install owncloud-client, run owncloud. It'll open a connection helper
  and should show an icon in the systray but doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1573639/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 903819] Re: use symbolic icons

2017-01-12 Thread Rodney Dawes 
** No longer affects: indicator-application

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-session in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/903819

Title:
  use symbolic icons

Status in Ayatana Design:
  Invalid
Status in indicator-messages package in Ubuntu:
  Triaged
Status in indicator-network package in Ubuntu:
  Triaged
Status in indicator-session package in Ubuntu:
  Triaged
Status in indicator-sound package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  Indicators should use symbolic icons.

  That has various benefits, counting the two more important:
  1. Only need to supply one theme between Ambiance/Radiance whatever.
  2. It's way easier to deal with situations like when the unity dash is 
opened, and icons should turn white: you just need to set the white color and 
it'll be recolored.

  This may depend on bug 599448.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/903819/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1578121] Re: UT does not discover bluetooth smart (BLE) devices

2017-01-12 Thread Rodney Dawes 
*** This bug is a duplicate of bug 1576986 ***
https://bugs.launchpad.net/bugs/1576986

** This bug has been marked a duplicate of bug 1576986
   UT does not discover bluetooth smart (BLE) devices

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1578121

Title:
  UT does not discover bluetooth smart (BLE) devices

Status in indicator-bluetooth package in Ubuntu:
  New

Bug description:
  Same as https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-
  settings/+bug/1576986 but I thought I'd also post it here.

  I am actually typing this on a Microsoft Universal Foldable Keyboard
  connected to my M10 tablet.

  Device: Bq Aquaris M10
  OS: OTA-10.1

  Generally bluetooth devices that are not version 4 or bluetooth smart
  (BLE) seem to work and pair fine with the Aquaris E4.5 and the M10.
  However, when it comes to BLE/version 4, things obviously get too
  complicated for the system bluetooth settings because it doesn't even
  manage to discover these devices.

  OTA-10.1 uses Bluez version 5.37, which is perfectly capable of
  discovering and pairing with BLE devices, but in Ubuntu Touch it
  requires the use of "bluetoothctl" in the terminal. I will describe
  the steps needed below:

  phablet@ubuntu-phablet:-$ bluetoothctl
  [bluetooth]# scan on

  wait for device to show up in list, typically:
  [NEW] Device 01:02:FF:A8:BB:00 DeviceName

  [bluetooth]# discoverable on
  Changing discoverable on succeeded
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# pairable on
  Changing pairable on succeeded

  Now tell bluetoothctl to pair the device
  [bluetooth]# pair 01:02:FF:A8:BB:00
  Attempting to pair with 01:02:FF:A8:BB:00

  If pairing with MS Universal Foldable Keyboard, you will probably see
  a 6-digit code, punch that code on the keyboard and hit return.

  [CHG] Device 01:02:FF:A8:BB:00 Connected: yes
  [agent] Passkey: 123456

  You should be good to go.

  However, the MS Foldable Keyboard does not show up in system bluetooth
  settings (see attached screenshot) and getting the M10 to recognize
  that the Keyboard is turned off seems to require a reboot (and
  possibly also bluetooth turned off). Otherwise, the onscreen keyboard
  doesn't show up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1578121/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1498594] Re: Rejected send message auth.log warnings

2017-01-12 Thread Sebastien Bacher 
that's still an issue in xenial at least, did you look in your log
should be easy enough to confirm if you still see those or not...

** Changed in: indicator-bluetooth (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1498594

Title:
  Rejected send message auth.log warnings

Status in indicator-bluetooth package in Ubuntu:
  New

Bug description:
  Using wily desktop, those errors are in the auth.log

  dbus[903]: [system] Rejected send message, 2 matched rules;
  type="method_call", sender=":1.576" (uid=123 pid=3965
  comm="/usr/lib/i386-linux-gnu/indicator-bluetooth/indica")
  interface="org.freedesktop.DBus.Properties" member="GetAll" error
  name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=833
  comm="/usr/lib/bluetooth/bluetoothd ")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1498594/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp

[Dx-packages] [Bug 1644323] Re: Installing unity8-session-snap adversely effects unity7

2017-01-12 Thread Jean-Baptiste Lallement 
I reopened bug 1654241

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-gtk-module in Ubuntu.
https://bugs.launchpad.net/bugs/1644323

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Fix Released
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Committed
Status in unity-gtk-module source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
  before unity-gtk-module.conf is started - so dbus activated services
  miss the GTK_MODULES environment variable. Update unity-gtk-
  module.conf to set it in the dbus activation environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  Test that gnome-terminal has global menus in both situations.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help   : https://help.launchpad.net/ListHelp