[Dx-packages] [Bug 1298656] Re: hud-service crashed with g-assert-if-reached in GMenu call from qtgmenu::QtGMenuModel::CreateChild()

2014-06-14 Thread Pete Woods
** Changed in: hud (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  hud-service crashed with g-assert-if-reached in GMenu call from
  qtgmenu::QtGMenuModel::CreateChild()

Status in “hud” package in Ubuntu:
  Fix Committed
Status in “hud” source package in Trusty:
  In Progress

Bug description:
  [Impact]

   * Unknown GTK application causes HUD service to crash by sending
  invalid menu updates via GMenu.

  [Test Case]

   * Not reproducable so far.

  [Regression Potential]

   * Worst case is that somehow HUD doesn't work on the desktop and
  phone.

   * There are, obviously, extensive unit and functional tests to verify
  this doesn't happen.

  [Other Info]

   * The patch will report the offending application to
  errors.ubuntu.com with all available debugging information.

   * The indexes are now range checked before processing. As soon as a
  window sends any invalid message it is blocked.

   * Further hardening around the memory management in QtGMenu has been
  carried out.

  * The change is not as large as it at first appears. The majority of
  the diff is simply replacing Type* with QSharedPointer. The rest
  is the extra code for reporting the recoverable problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1298656/+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 1330037] Re: upower 0.99 transition

2014-06-14 Thread Jackson Doak
** Also affects: razorqt (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  upower 0.99 needs uploading for gnome 3.12. This bug tracks the
  transition.
  
  A transition is required as some features were removed and the SONAME
  was changed
+ 
+ wmbattery and razorqt will probably need removing. When a package is
+ ready, mark it fix committed and link what changes are needed below.

** Bug watch added: Debian Bug tracker #748935
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748935

** Also affects: wmbattery (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748935
   Importance: Unknown
   Status: Unknown

** Description changed:

  upower 0.99 needs uploading for gnome 3.12. This bug tracks the
  transition.
  
  A transition is required as some features were removed and the SONAME
  was changed
  
- wmbattery and razorqt will probably need removing. When a package is
- ready, mark it fix committed and link what changes are needed below.
+ Some packages are staged in
+ https://launchpad.net/~noskcaj/+archive/upower/+packages
+ 
+ wmbattery will probably need removing. When a package is ready, mark it
+ fix committed and link what changes are needed below.

** Also affects: indicator-power (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-control-center (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unity-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: telepathy-mission-control-5 (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  upower 0.99 needs uploading for gnome 3.12. This bug tracks the
  transition.
  
  A transition is required as some features were removed and the SONAME
  was changed
  
  Some packages are staged in
  https://launchpad.net/~noskcaj/+archive/upower/+packages
  
  wmbattery will probably need removing. When a package is ready, mark it
  fix committed and link what changes are needed below.
+ 
+ 
+ telepathy-mission-control-5: Debian has dropped upower support, needs merging
+ wmbattery: needs removal. orphaned upstream/debian and doesn't work with new 
kernals

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

Title:
  upower 0.99 transition

Status in “indicator-power” package in Ubuntu:
  New
Status in “powerd” package in Ubuntu:
  New
Status in “razorqt” package in Ubuntu:
  New
Status in “sugar-0.96” package in Ubuntu:
  New
Status in “sugar-0.98” package in Ubuntu:
  New
Status in “telepathy-mission-control-5” package in Ubuntu:
  New
Status in “tracker” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  New
Status in “unity-control-center” package in Ubuntu:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  New
Status in “upower” package in Ubuntu:
  New
Status in “xfce4-power-manager” package in Ubuntu:
  New
Status in “xfce4-session” package in Ubuntu:
  New
Status in “xfce4-settings” package in Ubuntu:
  New
Status in “xfce4-systemload-plugin” package in Ubuntu:
  New
Status in “wmbattery” package in Debian:
  Unknown

Bug description:
  upower 0.99 needs uploading for gnome 3.12. This bug tracks the
  transition.

  A transition is required as some features were removed and the SONAME
  was changed

  Some packages are staged in
  https://launchpad.net/~noskcaj/+archive/upower/+packages

  wmbattery will probably need removing. When a package is ready, mark
  it fix committed and link what changes are needed below.

  
  telepathy-mission-control-5: Debian has dropped upower support, needs merging
  wmbattery: needs removal. orphaned upstream/debian and doesn't work with new 
kernals

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1330037/+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 1330037] Re: upower 0.99 transition

2014-06-14 Thread Jackson Doak
** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  upower 0.99 transition

Status in “indicator-power” package in Ubuntu:
  New
Status in “mate-power-manager” package in Ubuntu:
  New
Status in “mate-session-manager” package in Ubuntu:
  New
Status in “mutter” package in Ubuntu:
  New
Status in “powerd” package in Ubuntu:
  New
Status in “razorqt” package in Ubuntu:
  New
Status in “sugar-0.96” package in Ubuntu:
  New
Status in “sugar-0.98” package in Ubuntu:
  New
Status in “telepathy-mission-control-5” package in Ubuntu:
  New
Status in “tracker” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  New
Status in “unity-control-center” package in Ubuntu:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  New
Status in “upower” package in Ubuntu:
  New
Status in “xfce4-power-manager” package in Ubuntu:
  New
Status in “xfce4-session” package in Ubuntu:
  New
Status in “xfce4-settings” package in Ubuntu:
  New
Status in “xfce4-systemload-plugin” package in Ubuntu:
  New
Status in “wmbattery” package in Debian:
  Unknown

Bug description:
  upower 0.99 needs uploading for gnome 3.12. This bug tracks the
  transition.

  A transition is required as some features were removed and the SONAME
  was changed

  Some packages are staged in
  https://launchpad.net/~noskcaj/+archive/upower/+packages

  wmbattery will probably need removing. When a package is ready, mark
  it fix committed and link what changes are needed below.

  
  telepathy-mission-control-5: Debian has dropped upower support, needs merging
  wmbattery: needs removal. orphaned upstream/debian and doesn't work with new 
kernals

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1330037/+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 1330037] Re: upower 0.99 transition

2014-06-14 Thread Jackson Doak
** Also affects: mate-session-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: mate-power-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: mate-applets (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-session (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-power-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-packagekit (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  upower 0.99 needs uploading for gnome 3.12. This bug tracks the
  transition.
  
  A transition is required as some features were removed and the SONAME
  was changed
  
  Some packages are staged in
  https://launchpad.net/~noskcaj/+archive/upower/+packages
  
- wmbattery will probably need removing. When a package is ready, mark it
- fix committed and link what changes are needed below.
- 
+ wmbattery will probably need removing. If a package only needs a
+ rebuild, mark it fix commited, if something else is needed, in progress.
  
  telepathy-mission-control-5: Debian has dropped upower support, needs merging
  wmbattery: needs removal. orphaned upstream/debian and doesn't work with new 
kernals

** Also affects: cairo-dock-plug-ins (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: python-dbusmock (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cairo-dock-plug-ins (Ubuntu)
   Status: New => Fix Committed

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

Title:
  upower 0.99 transition

Status in “cairo-dock-plug-ins” package in Ubuntu:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  New
Status in “gnome-packagekit” package in Ubuntu:
  New
Status in “gnome-power-manager” package in Ubuntu:
  New
Status in “gnome-session” package in Ubuntu:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  New
Status in “gnome-shell” package in Ubuntu:
  New
Status in “indicator-power” package in Ubuntu:
  New
Status in “mate-applets” package in Ubuntu:
  New
Status in “mate-power-manager” package in Ubuntu:
  New
Status in “mate-session-manager” package in Ubuntu:
  New
Status in “mutter” package in Ubuntu:
  New
Status in “powerd” package in Ubuntu:
  New
Status in “python-dbusmock” package in Ubuntu:
  New
Status in “razorqt” package in Ubuntu:
  New
Status in “sugar-0.96” package in Ubuntu:
  New
Status in “sugar-0.98” package in Ubuntu:
  New
Status in “telepathy-mission-control-5” package in Ubuntu:
  New
Status in “tracker” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  New
Status in “unity-control-center” package in Ubuntu:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  New
Status in “upower” package in Ubuntu:
  New
Status in “xfce4-power-manager” package in Ubuntu:
  New
Status in “xfce4-session” package in Ubuntu:
  New
Status in “xfce4-settings” package in Ubuntu:
  New
Status in “xfce4-systemload-plugin” package in Ubuntu:
  New
Status in “wmbattery” package in Debian:
  Unknown

Bug description:
  upower 0.99 needs uploading for gnome 3.12. This bug tracks the
  transition.

  A transition is required as some features were removed and the SONAME
  was changed

  Some packages are staged in
  https://launchpad.net/~noskcaj/+archive/upower/+packages

  wmbattery will probably need removing. If a package only needs a
  rebuild, mark it fix commited, if something else is needed, in
  progress.

  telepathy-mission-control-5: Debian has dropped upower support, needs merging
  wmbattery: needs removal. orphaned upstream/debian and doesn't work with new 
kernals

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+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 1330037] Re: upower 0.99 transition

2014-06-14 Thread Jackson Doak
** Description changed:

  upower 0.99 needs uploading for gnome 3.12. This bug tracks the
  transition.
  
  A transition is required as some features were removed and the SONAME
  was changed
  
  Some packages are staged in
  https://launchpad.net/~noskcaj/+archive/upower/+packages
  
  wmbattery will probably need removing. If a package only needs a
  rebuild, mark it fix commited, if something else is needed, in progress.
  
+ cairo-dock-plug-ins: needs rebuilding
+ #gnome-shell - Only a depend (used directly in 3.12)
+ gnome-control-center: WIP
+ gnome-packagekit: Fixed in newest upstream release, needs packaging
+ gnome-power-manager: Fixed in newest upstream release. Merge from debian 
experimental
+ gnome-session: Done in ppa, needs patches from git or new upstream release
+ gnome-settings-daemon
+ kde: no idea (awaiting reply)
+ mate: all mate packages need rebuilding
+ python-dbusmock: lp:1324791
+ sugar: no idea.
  telepathy-mission-control-5: Debian has dropped upower support, needs merging
  wmbattery: needs removal. orphaned upstream/debian and doesn't work with new 
kernals
+ xfce4-power-manager: Fixed in new upstream release. Needs merging from debian 
experimental
+ xfce4-session: patch is upstream, needs testing
+ xfce4-settings: Patch from upstream in ppa
+ xfce4-systemload-plugin: needs rebuild
+ xfce4-weather-plugin: needs rebuild

** Changed in: gnome-control-center (Ubuntu)
 Assignee: (unassigned) => Tim (darkxst)

** Changed in: gnome-settings-daemon (Ubuntu)
 Assignee: (unassigned) => Tim (darkxst)

** Changed in: unity-settings-daemon (Ubuntu)
 Assignee: (unassigned) => Tim (darkxst)

** Changed in: unity-control-center (Ubuntu)
 Assignee: (unassigned) => Tim (darkxst)

** Changed in: xfce4-session (Ubuntu)
 Assignee: (unassigned) => Jackson Doak (noskcaj)

** Changed in: xfce4-systemload-plugin (Ubuntu)
 Assignee: (unassigned) => Jackson Doak (noskcaj)

** Description changed:

  upower 0.99 needs uploading for gnome 3.12. This bug tracks the
  transition.
  
  A transition is required as some features were removed and the SONAME
  was changed
  
  Some packages are staged in
  https://launchpad.net/~noskcaj/+archive/upower/+packages
  
  wmbattery will probably need removing. If a package only needs a
  rebuild, mark it fix commited, if something else is needed, in progress.
  
  cairo-dock-plug-ins: needs rebuilding
  #gnome-shell - Only a depend (used directly in 3.12)
  gnome-control-center: WIP
  gnome-packagekit: Fixed in newest upstream release, needs packaging
  gnome-power-manager: Fixed in newest upstream release. Merge from debian 
experimental
  gnome-session: Done in ppa, needs patches from git or new upstream release
  gnome-settings-daemon
  kde: no idea (awaiting reply)
  mate: all mate packages need rebuilding
  python-dbusmock: lp:1324791
  sugar: no idea.
  telepathy-mission-control-5: Debian has dropped upower support, needs merging
  wmbattery: needs removal. orphaned upstream/debian and doesn't work with new 
kernals
  xfce4-power-manager: Fixed in new upstream release. Needs merging from debian 
experimental
  xfce4-session: patch is upstream, needs testing
  xfce4-settings: Patch from upstream in ppa
  xfce4-systemload-plugin: needs rebuild
- xfce4-weather-plugin: needs rebuild

** Changed in: xfce4-systemload-plugin (Ubuntu)
   Status: New => Fix Committed

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

Title:
  upower 0.99 transition

Status in “cairo-dock-plug-ins” package in Ubuntu:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  New
Status in “gnome-packagekit” package in Ubuntu:
  New
Status in “gnome-power-manager” package in Ubuntu:
  New
Status in “gnome-session” package in Ubuntu:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  New
Status in “gnome-shell” package in Ubuntu:
  New
Status in “indicator-power” package in Ubuntu:
  New
Status in “mate-applets” package in Ubuntu:
  New
Status in “mate-power-manager” package in Ubuntu:
  New
Status in “mate-session-manager” package in Ubuntu:
  New
Status in “mutter” package in Ubuntu:
  New
Status in “powerd” package in Ubuntu:
  New
Status in “python-dbusmock” package in Ubuntu:
  New
Status in “razorqt” package in Ubuntu:
  New
Status in “sugar-0.96” package in Ubuntu:
  New
Status in “sugar-0.98” package in Ubuntu:
  New
Status in “telepathy-mission-control-5” package in Ubuntu:
  New
Status in “tracker” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  New
Status in “unity-control-center” package in Ubuntu:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  New
Status in “upower” package in Ubuntu:
  New
Status in “xfce4-power-manager” package in Ubuntu:
  New
Status in “xfce4-session” package in Ubuntu:
  New
Status in “xfce4-settings” package in Ubuntu:
  New
Status in “

[Dx-packages] [Bug 960537] Re: Dash search box doesn't unhide Onboard on-screen keyboard

2014-06-14 Thread Daniel Holz
The problem is still present in 14.04.

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

Title:
  Dash search box doesn't unhide Onboard on-screen keyboard

Status in Ubuntu on the Nexus 7:
  Confirmed
Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Onboard 0.97 can be configured to auto-show when an editable text
  entry becomes focused. It does this by reacting to AT-SPI focus
  messages. Unity Dash's search box seems like prime candidate to unhide
  Onboard, but currently there are no at-spi messages triggered when
  opening dash. It would be great if dash search could be at-enabled.

  This is the original bug report for Onboard:
  https://bugs.launchpad.net/onboard/+bug/936310

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.6.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,compiztoolbox,regex,imgpng,place,animation,expo,grid,mousepoll,session,snap,vpswitch,wall,workarounds,resize,gnomecompat,move,fade,scale,ezoom,unityshell]
  Date: Tue Mar 20 20:06:12 2012
  ProcEnviron:
   TERM=xterm
   PATH=(custom, User Name)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/960537/+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 1330037] Re: upower 0.99 transition

2014-06-14 Thread Bug Watch Updater
** Changed in: wmbattery (Debian)
   Status: Unknown => New

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

Title:
  upower 0.99 transition

Status in “cairo-dock-plug-ins” package in Ubuntu:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  New
Status in “gnome-packagekit” package in Ubuntu:
  New
Status in “gnome-power-manager” package in Ubuntu:
  New
Status in “gnome-session” package in Ubuntu:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  New
Status in “gnome-shell” package in Ubuntu:
  New
Status in “indicator-power” package in Ubuntu:
  New
Status in “mate-applets” package in Ubuntu:
  New
Status in “mate-power-manager” package in Ubuntu:
  New
Status in “mate-session-manager” package in Ubuntu:
  New
Status in “mutter” package in Ubuntu:
  New
Status in “powerd” package in Ubuntu:
  New
Status in “python-dbusmock” package in Ubuntu:
  New
Status in “razorqt” package in Ubuntu:
  New
Status in “sugar-0.96” package in Ubuntu:
  New
Status in “sugar-0.98” package in Ubuntu:
  New
Status in “telepathy-mission-control-5” package in Ubuntu:
  New
Status in “tracker” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  New
Status in “unity-control-center” package in Ubuntu:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  New
Status in “upower” package in Ubuntu:
  New
Status in “xfce4-power-manager” package in Ubuntu:
  New
Status in “xfce4-session” package in Ubuntu:
  New
Status in “xfce4-settings” package in Ubuntu:
  New
Status in “xfce4-systemload-plugin” package in Ubuntu:
  Fix Committed
Status in “wmbattery” package in Debian:
  New

Bug description:
  upower 0.99 needs uploading for gnome 3.12. This bug tracks the
  transition.

  A transition is required as some features were removed and the SONAME
  was changed

  Some packages are staged in
  https://launchpad.net/~noskcaj/+archive/upower/+packages

  wmbattery will probably need removing. If a package only needs a
  rebuild, mark it fix commited, if something else is needed, in
  progress.

  cairo-dock-plug-ins: needs rebuilding
  #gnome-shell - Only a depend (used directly in 3.12)
  gnome-control-center: WIP
  gnome-packagekit: Fixed in newest upstream release, needs packaging
  gnome-power-manager: Fixed in newest upstream release. Merge from debian 
experimental
  gnome-session: Done in ppa, needs patches from git or new upstream release
  gnome-settings-daemon
  kde: no idea (awaiting reply)
  mate: all mate packages need rebuilding
  python-dbusmock: lp:1324791
  sugar: no idea.
  telepathy-mission-control-5: Debian has dropped upower support, needs merging
  wmbattery: needs removal. orphaned upstream/debian and doesn't work with new 
kernals
  xfce4-power-manager: Fixed in new upstream release. Needs merging from debian 
experimental
  xfce4-session: patch is upstream, needs testing
  xfce4-settings: Patch from upstream in ppa
  xfce4-systemload-plugin: needs rebuild

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+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 1330037] Re: upower 0.99 transition

2014-06-14 Thread Tim
** Description changed:

  upower 0.99 needs uploading for gnome 3.12. This bug tracks the
  transition.
  
  A transition is required as some features were removed and the SONAME
  was changed
  
  Some packages are staged in
  https://launchpad.net/~noskcaj/+archive/upower/+packages
  
  wmbattery will probably need removing. If a package only needs a
  rebuild, mark it fix commited, if something else is needed, in progress.
  
  cairo-dock-plug-ins: needs rebuilding
- #gnome-shell - Only a depend (used directly in 3.12)
+ #gnome-shell - ready, just need to drop upower revert.
  gnome-control-center: WIP
  gnome-packagekit: Fixed in newest upstream release, needs packaging
  gnome-power-manager: Fixed in newest upstream release. Merge from debian 
experimental
  gnome-session: Done in ppa, needs patches from git or new upstream release
  gnome-settings-daemon
  kde: no idea (awaiting reply)
  mate: all mate packages need rebuilding
  python-dbusmock: lp:1324791
  sugar: no idea.
  telepathy-mission-control-5: Debian has dropped upower support, needs merging
  wmbattery: needs removal. orphaned upstream/debian and doesn't work with new 
kernals
  xfce4-power-manager: Fixed in new upstream release. Needs merging from debian 
experimental
  xfce4-session: patch is upstream, needs testing
  xfce4-settings: Patch from upstream in ppa
  xfce4-systemload-plugin: needs rebuild

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

Title:
  upower 0.99 transition

Status in “cairo-dock-plug-ins” package in Ubuntu:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  New
Status in “gnome-packagekit” package in Ubuntu:
  New
Status in “gnome-power-manager” package in Ubuntu:
  New
Status in “gnome-session” package in Ubuntu:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  New
Status in “gnome-shell” package in Ubuntu:
  New
Status in “indicator-power” package in Ubuntu:
  New
Status in “mate-applets” package in Ubuntu:
  New
Status in “mate-power-manager” package in Ubuntu:
  New
Status in “mate-session-manager” package in Ubuntu:
  New
Status in “mutter” package in Ubuntu:
  New
Status in “powerd” package in Ubuntu:
  New
Status in “python-dbusmock” package in Ubuntu:
  New
Status in “razorqt” package in Ubuntu:
  New
Status in “sugar-0.96” package in Ubuntu:
  New
Status in “sugar-0.98” package in Ubuntu:
  New
Status in “telepathy-mission-control-5” package in Ubuntu:
  New
Status in “tracker” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  New
Status in “unity-control-center” package in Ubuntu:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  New
Status in “upower” package in Ubuntu:
  New
Status in “xfce4-power-manager” package in Ubuntu:
  New
Status in “xfce4-session” package in Ubuntu:
  New
Status in “xfce4-settings” package in Ubuntu:
  New
Status in “xfce4-systemload-plugin” package in Ubuntu:
  Fix Committed
Status in “wmbattery” package in Debian:
  New

Bug description:
  upower 0.99 needs uploading for gnome 3.12. This bug tracks the
  transition.

  A transition is required as some features were removed and the SONAME
  was changed

  Some packages are staged in
  https://launchpad.net/~noskcaj/+archive/upower/+packages

  wmbattery will probably need removing. If a package only needs a
  rebuild, mark it fix commited, if something else is needed, in
  progress.

  cairo-dock-plug-ins: needs rebuilding
  #gnome-shell - ready, just need to drop upower revert.
  gnome-control-center: WIP
  gnome-packagekit: Fixed in newest upstream release, needs packaging
  gnome-power-manager: Fixed in newest upstream release. Merge from debian 
experimental
  gnome-session: Done in ppa, needs patches from git or new upstream release
  gnome-settings-daemon
  kde: no idea (awaiting reply)
  mate: all mate packages need rebuilding
  python-dbusmock: lp:1324791
  sugar: no idea.
  telepathy-mission-control-5: Debian has dropped upower support, needs merging
  wmbattery: needs removal. orphaned upstream/debian and doesn't work with new 
kernals
  xfce4-power-manager: Fixed in new upstream release. Needs merging from debian 
experimental
  xfce4-session: patch is upstream, needs testing
  xfce4-settings: Patch from upstream in ppa
  xfce4-systemload-plugin: needs rebuild

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+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


Re: [Dx-packages] [Cairo-dock-team] [Bug 1242112] Re: Shutdown/restart dialogue is not working if Cairo-Dock and its logout applet are running

2014-06-14 Thread Fabounet
Thank you for sharing this post !
This confirms what we thought, since Cairo-Dock also registers as Unity to
get the LauncherEntry events.

I've made a small modification, I hope it will help (revision 3097)
Please let me know if you can test (or if you prefer you can also test the
modification directly, simply edit
/usr/lib/cairo-dock/cairo-dock-launcher-API-daemon and replace
bus_name = dbus.service.BusName (self.bus_name_str, self.bus)
by
bus_name = dbus.service.BusName (self.bus_name_str, self.bus,
allow_replacement=True)
then restart your session as usual


2014-06-12 23:50 GMT+02:00 Lee Hyde <1242...@bugs.launchpad.net>:

> Tom Beckmann's answer to Question #250144
> (https://answers.launchpad.net/gala/+question/250144) as well as his
> workaround for my similar issues with a modified pantheon session (using
> Compiz rather than Gala) could well be enlightening on this matter.
>
> I've haven't deployed the workaround yet, but I thought it best to share
> here regardless.
>
> --
> You received this bug notification because you are a member of Cairo-
> Dock Devs, which is subscribed to Cairo-Dock Core.
> https://bugs.launchpad.net/bugs/1242112
>
> Title:
>   Shutdown/restart dialogue is not working if Cairo-Dock and its logout
>   applet are running
>
> Status in Cairo-Dock : Core:
>   Invalid
> Status in “cairo-dock” package in Ubuntu:
>   Invalid
> Status in “unity” package in Ubuntu:
>   Confirmed
> Status in “cairo-dock” source package in Trusty:
>   Confirmed
> Status in “unity” source package in Trusty:
>   Confirmed
> Status in “cairo-dock” source package in Utopic:
>   Invalid
> Status in “unity” source package in Utopic:
>   Confirmed
>
> Bug description:
>   Using latest stable release (3.3.1). Just upgraded to Saucy Salamander
>   in Ubuntu. When cairo dock is set to automatically run at boot up the
>   options to shutdown/restart do not work from the top menu panel next
>   to the clock. When run manually after boot the shutdown/restart works
>   fine. The shutdown/restart options do work fine from cairo
>   dock/terminal but just mess up the shutdown/restart from the top menu
>   panel
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cairo-dock-core/+bug/1242112/+subscriptions
>
> ___
> Mailing list: https://launchpad.net/~cairo-dock-team
> Post to : cairo-dock-t...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~cairo-dock-team
> More help   : https://help.launchpad.net/ListHelp
>

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

Title:
  Shutdown/restart dialogue is not working if Cairo-Dock and its logout
  applet are running

Status in Cairo-Dock : Core:
  Invalid
Status in “cairo-dock” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Confirmed
Status in “cairo-dock” source package in Trusty:
  Confirmed
Status in “unity” source package in Trusty:
  Confirmed
Status in “cairo-dock” source package in Utopic:
  Invalid
Status in “unity” source package in Utopic:
  Confirmed

Bug description:
  Using latest stable release (3.3.1). Just upgraded to Saucy Salamander
  in Ubuntu. When cairo dock is set to automatically run at boot up the
  options to shutdown/restart do not work from the top menu panel next
  to the clock. When run manually after boot the shutdown/restart works
  fine. The shutdown/restart options do work fine from cairo
  dock/terminal but just mess up the shutdown/restart from the top menu
  panel

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo-dock-core/+bug/1242112/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

2014-06-14 Thread oliver
@Dimitry from #131

Unfortunatly for some reason Gnomebuntu doesn't care about
/etc/pm/sleep/*, pm-utls is involved with /etc/pm* and pm-utils is not
installed under gnomebuntu 14.04 for me. Installing pm-utils makes
suspend/resume work much less reliable, so leaving it off.

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in NetworkManager:
  New
Status in wicd:
  New
Status in “systemd-shim” package in Ubuntu:
  Confirmed
Status in “systemd-shim” source package in Saucy:
  Confirmed
Status in “systemd-shim” source package in Trusty:
  Confirmed

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1252121/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

2014-06-14 Thread Yanpas
@oliver so which utility does provide you power management?

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in NetworkManager:
  New
Status in wicd:
  New
Status in “systemd-shim” package in Ubuntu:
  Confirmed
Status in “systemd-shim” source package in Saucy:
  Confirmed
Status in “systemd-shim” source package in Trusty:
  Confirmed

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1252121/+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 1329963] Re: Normal scrollbars lack up/down buttons

2014-06-14 Thread Adolfo Jayme
This is a preference that can be set by the GTK+ theme. It has nothing
to do with Unity.

** Package changed: unity (Ubuntu) => ubuntu-themes (Ubuntu)

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Low

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Triaged

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1329963/+attachment/4131189/+files/Dependencies.txt

** Attachment removed: "GconfCompiz.txt"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1329963/+attachment/4131190/+files/GconfCompiz.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1329963/+attachment/4131191/+files/ProcEnviron.txt

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

Title:
  Normal scrollbars lack up/down buttons

Status in “ubuntu-themes” package in Ubuntu:
  Triaged

Bug description:
  On 14.04, I have disabled the annoying, and buggy overlay scrollbars that 
I've hated since they appeared, with the method described here:
  
http://ubuntuhandbook.org/index.php/2013/10/disable-overlay-scrollbars-ubuntu13-10/

  So now I have "normal" scrollbars, which is good, except that THEY
  LACK THE UP/DOWN BUTTON that should be present at the top and bottom
  (either an up button at the top and a down button at the bottom, or
  both either at top or bottom).

  Why the developers of Ubuntu keep destroying the usability of such
  basic, obvious things as scrollbars, is beyond me.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Jun 13 23:36:03 2014
  InstallationDate: Installed on 2013-10-11 (245 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1329963/+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 1329399] Re: menu key problem

2014-06-14 Thread Adolfo Jayme
** Package changed: unity (Ubuntu) => nautilus (Ubuntu)

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

Title:
  menu key problem

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  When the Menu Key is pressed (on the keyboard) it opens a context menu/app, 
when i press it again (without closing the first context menu) it generates 
another context menu, and doesnt delete the first one. It does NOT replace the 
first context menu, when creating another one.
  That happens only in the desktop and nautilus
  ---
  diegos@diegos-NCL60:~$ LANG= lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  diegos@diegos-NCL60:~$ LANG= uname -a
  Linux diegos-NCL60 3.15.0-031500-generic #201406081435 SMP Sun Jun 8 18:36:00 
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
  diegos@diegos-NCL60:~$ LANG= apt-cache policy compiz
  compiz:
Installed: 1:0.9.11+14.04.20140423-0ubuntu1
Candidate: 1:0.9.11+14.04.20140423-0ubuntu1
Version table:
   *** 1:0.9.11+14.04.20140423-0ubuntu1 0
  500 http://ar.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:0.9.11+14.04.20140409-0ubuntu1 0
  500 http://ar.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.1+14.04.20140513-0ubuntu2
  Uname: Linux 3.15.0-031500-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jun 12 14:11:05 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: COMPAL Electronics Inc Device [14c0:0051]
  InstallationDate: Installed on 2014-06-08 (3 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Compal NCL60/61
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.0-031500-generic 
root=UUID=843fed2d-20bf-4567-9be7-980658ef4e68 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2011
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NCL60/61
  dmi.board.vendor: Compal
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.11:bd11/10/2011:svnCompal:pnNCL60/61:pvrF01:rvnCompal:rnNCL60/61:rvrBaseBoardVersion:cvnCompal:ct10:cvrChassisVersion:
  dmi.product.name: NCL60/61
  dmi.product.version: F01
  dmi.sys.vendor: Compal
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Jun 12 11:56:34 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1439 
   vendor BOE
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1329399/+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 1308037] Re: No results from application scope

2014-06-14 Thread Mateusz Stachowski
It happened again today. I don't get any results for applications in
Home and Applications lens but this time the commands scope (Alt+F2)
works.

Output of gsettings get:

$ gsettings get com.canonical.Unity.Lenses home-lens-default-view
['music.scope', 'music-audacious.scope', 'music-gmusicbrowser.scope', 
'music-grooveshark.scope', 'music-musicstore.scope', 'music-rhythmbox.scope', 
'music-songsterr.scope', 'music-soundcloud.scope', 'files.scope', 
'files-gdrive.scope', 'files-local.scope', 'applications.scope', 
'applications-applications.scope', 'applications-scopes.scope']

$ gsettings get com.canonical.Unity.Lenses always-search
['applications.scope', 'music.scope', 'videos.scope', 'files.scope']

$ gsettings get com.canonical.Unity.Lenses disabled-scopes
['more_suggestions-skimlinks.scope', 'more_suggestions-ebay.scope', 
'photos-facebook.scope', 'music-audacious.scope', 
'more_suggestions-amazon.scope']

** Attachment added: "dbus.log"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1308037/+attachment/4131490/+files/dbus.log

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

Title:
  No results from application scope

Status in LibUnity:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Unity is in a state where I don't get any results from the
  applications lens. This sometimes happens for one search but either
  re-entering the search or toggling the lens has always fixed it in the
  past for me. This time neither of these steps work.

  I'm attaching a bustle log of the problem in case that's helpful. I
  searched for "spotify", which I've got installed, and got 0 results.

  The only way to fix the issue is to log out and back in.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 15 13:29:40 2014
  InstallationDate: Installed on 2012-10-07 (554 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/1308037/+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 1330103] Re: a launcher icon (Terminal) randomly stops responding to clicks and to Alt+tab switching

2014-06-14 Thread Teo
** Attachment added: "Screenshot from 2014-06-14 18:57:59.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1330103/+attachment/4131513/+files/Screenshot%20from%202014-06-14%2018%3A57%3A59.png

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

Title:
  a launcher icon (Terminal) randomly stops responding to clicks and to
  Alt+tab switching

Status in “unity” package in Ubuntu:
  New

Bug description:
  Not sure whether this is an issue in whatever part of the system manages 
window switching, or in the Terminal itself.
  And this is NOT easily reproducible. I'm observing it for the first time now.

  I have 3 terminal windows open, which I opened several hours ago,
  probably even yesterday prior to suspending and resuming. And I have
  several other windows open. You can see my Launcher in the attached
  screenshot.

  If I click on any of the launcher icons except the Terminal's one,
  they work as expected, bringing the corresponding window to front.

  However, if I click on the Terminal launcher icon nothing happens
  (expected: should bring to front one of the terminal windows). And if
  I click on the very left of it, nothing happens either (expected:
  should show the three existing windows and allow me to choose one of
  them). Nothing.

  If I hit Alt+Tab and try switch to Terminal, it does not work (nothing 
happens).
  However, if I hit Alt+Tab until Terminal is highlighted and then keep holding 
Alt and wait, it does show me the three windows and allow me to switch to any 
of them by further hitting Tab. And once I do that and have finally one 
terminal window focused, it does work and the terminal does respond and work, 
it is not unresponsive or anything.

  Right now this is only affecting Terminal and no other application.

  After closing two of the terminal windows (which were accessible with
  the last method described above), now I have only one, so I can't
  access it in any way because the alt+tab+and-hold method is not
  applicable.

  
  Finally, my workaround was:
  - open a new terminal with Ctrl+Alt+T (the issue remained)
  - ps aux | grep term to figure out the terminal's process id
  - killed it.

  Then the launcher icon (I have it locked to launcher) allowed me to
  open a new terminal window and starting from now everything works as
  expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat Jun 14 18:57:26 2014
  InstallationDate: Installed on 2013-10-11 (245 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1330103/+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 1330103] [NEW] a launcher icon (Terminal) randomly stops responding to clicks and to Alt+tab switching

2014-06-14 Thread Teo
Public bug reported:

Not sure whether this is an issue in whatever part of the system manages window 
switching, or in the Terminal itself.
And this is NOT easily reproducible. I'm observing it for the first time now.

I have 3 terminal windows open, which I opened several hours ago,
probably even yesterday prior to suspending and resuming. And I have
several other windows open. You can see my Launcher in the attached
screenshot.

If I click on any of the launcher icons except the Terminal's one, they
work as expected, bringing the corresponding window to front.

However, if I click on the Terminal launcher icon nothing happens
(expected: should bring to front one of the terminal windows). And if I
click on the very left of it, nothing happens either (expected: should
show the three existing windows and allow me to choose one of them).
Nothing.

If I hit Alt+Tab and try switch to Terminal, it does not work (nothing happens).
However, if I hit Alt+Tab until Terminal is highlighted and then keep holding 
Alt and wait, it does show me the three windows and allow me to switch to any 
of them by further hitting Tab. And once I do that and have finally one 
terminal window focused, it does work and the terminal does respond and work, 
it is not unresponsive or anything.

Right now this is only affecting Terminal and no other application.

After closing two of the terminal windows (which were accessible with
the last method described above), now I have only one, so I can't access
it in any way because the alt+tab+and-hold method is not applicable.


Finally, my workaround was:
- open a new terminal with Ctrl+Alt+T (the issue remained)
- ps aux | grep term to figure out the terminal's process id
- killed it.

Then the launcher icon (I have it locked to launcher) allowed me to open
a new terminal window and starting from now everything works as
expected.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Sat Jun 14 18:57:26 2014
InstallationDate: Installed on 2013-10-11 (245 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-05-24 (20 days ago)

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


** Tags: amd64 apport-bug trusty

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

Title:
  a launcher icon (Terminal) randomly stops responding to clicks and to
  Alt+tab switching

Status in “unity” package in Ubuntu:
  New

Bug description:
  Not sure whether this is an issue in whatever part of the system manages 
window switching, or in the Terminal itself.
  And this is NOT easily reproducible. I'm observing it for the first time now.

  I have 3 terminal windows open, which I opened several hours ago,
  probably even yesterday prior to suspending and resuming. And I have
  several other windows open. You can see my Launcher in the attached
  screenshot.

  If I click on any of the launcher icons except the Terminal's one,
  they work as expected, bringing the corresponding window to front.

  However, if I click on the Terminal launcher icon nothing happens
  (expected: should bring to front one of the terminal windows). And if
  I click on the very left of it, nothing happens either (expected:
  should show the three existing windows and allow me to choose one of
  them). Nothing.

  If I hit Alt+Tab and try switch to Terminal, it does not work (nothing 
happens).
  However, if I hit Alt+Tab until Terminal is highlighted and then keep holding 
Alt and wait, it does show me the three windows and allow me to switch to any 
of them by further hitting Tab. And once I do that and have finally one 
terminal window focused, it does work and the terminal does respond and work, 
it is not unresponsive or anything.

  Right now this is only affecting Terminal and no other application.

  After closing two of the terminal windows (which were accessible with
  the last method described above), now I have only one, so I can't
  access it in any way because the alt+tab+and-hold method is not
  applicable.

  
  Finally, my workaround was:
  - open a new terminal with Ctrl+Alt+T (the issue remained)
  - ps aux | grep term to figure out the terminal's process id
  - killed it.

  Then the launcher icon (I have it locked to launcher) allowed me to
  open a new terminal window and starting from now everything works as
  expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.1

[Dx-packages] [Bug 1330037] Re: upower 0.99 transition

2014-06-14 Thread Charles Kerr
Confirmed, indicator-power will need to be updated for this: src/device-
provider-upower.c is currently using some of the signals that got
removed.

** Changed in: indicator-power (Ubuntu)
   Importance: Undecided => Medium

** Changed in: indicator-power (Ubuntu)
   Status: New => Triaged

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

Title:
  upower 0.99 transition

Status in “cairo-dock-plug-ins” package in Ubuntu:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  New
Status in “gnome-packagekit” package in Ubuntu:
  New
Status in “gnome-power-manager” package in Ubuntu:
  New
Status in “gnome-session” package in Ubuntu:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  New
Status in “gnome-shell” package in Ubuntu:
  New
Status in “indicator-power” package in Ubuntu:
  Triaged
Status in “mate-applets” package in Ubuntu:
  New
Status in “mate-power-manager” package in Ubuntu:
  New
Status in “mate-session-manager” package in Ubuntu:
  New
Status in “mutter” package in Ubuntu:
  New
Status in “powerd” package in Ubuntu:
  New
Status in “python-dbusmock” package in Ubuntu:
  New
Status in “razorqt” package in Ubuntu:
  New
Status in “sugar-0.96” package in Ubuntu:
  New
Status in “sugar-0.98” package in Ubuntu:
  New
Status in “telepathy-mission-control-5” package in Ubuntu:
  New
Status in “tracker” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  New
Status in “unity-control-center” package in Ubuntu:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  New
Status in “upower” package in Ubuntu:
  New
Status in “xfce4-power-manager” package in Ubuntu:
  New
Status in “xfce4-session” package in Ubuntu:
  New
Status in “xfce4-settings” package in Ubuntu:
  New
Status in “xfce4-systemload-plugin” package in Ubuntu:
  Fix Committed
Status in “wmbattery” package in Debian:
  New

Bug description:
  upower 0.99 needs uploading for gnome 3.12. This bug tracks the
  transition.

  A transition is required as some features were removed and the SONAME
  was changed

  Some packages are staged in
  https://launchpad.net/~noskcaj/+archive/upower/+packages

  wmbattery will probably need removing. If a package only needs a
  rebuild, mark it fix commited, if something else is needed, in
  progress.

  cairo-dock-plug-ins: needs rebuilding
  #gnome-shell - ready, just need to drop upower revert.
  gnome-control-center: WIP
  gnome-packagekit: Fixed in newest upstream release, needs packaging
  gnome-power-manager: Fixed in newest upstream release. Merge from debian 
experimental
  gnome-session: Done in ppa, needs patches from git or new upstream release
  gnome-settings-daemon
  kde: no idea (awaiting reply)
  mate: all mate packages need rebuilding
  python-dbusmock: lp:1324791
  sugar: no idea.
  telepathy-mission-control-5: Debian has dropped upower support, needs merging
  wmbattery: needs removal. orphaned upstream/debian and doesn't work with new 
kernals
  xfce4-power-manager: Fixed in new upstream release. Needs merging from debian 
experimental
  xfce4-session: patch is upstream, needs testing
  xfce4-settings: Patch from upstream in ppa
  xfce4-systemload-plugin: needs rebuild

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+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 1283236] Re: Alarms are triggered in UTC tz despite saving in local tz

2014-06-14 Thread Charles Kerr
** Changed in: indicator-datetime
   Status: In Progress => Fix Released

** Changed in: indicator-datetime (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => High

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

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

Title:
  Alarms are triggered in UTC tz despite saving in local tz

Status in The Date and Time Indicator:
  Fix Released
Status in Clock application for Ubuntu devices:
  Fix Released
Status in Ubuntu UI Toolkit:
  Fix Committed
Status in “indicator-datetime” package in Ubuntu:
  Fix Released
Status in “qtorganizer5-eds” package in Ubuntu:
  Confirmed
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Fix Released

Bug description:
  Setting an alarm in the local timezone is not respected by the system
  since the alarms is triggered in the equivalent UTC timezone.

  Mako build 200, 205

  Steps to reproduce: 
  1. Ensure that phone timezone is something other than UTC. For instance 
eastern tz (UTC-5)
  2. Set an alarm for 3:00 PM in the ubuntu clock app.
  3. Indicator shows a pending alarm for 3:00 PM
  4. Check a minute or so later, indicator shows an alarm pending for 8:00 PM

  What happens:
  The alarm does not go off at 3:00 PM. Instead it triggers at 8:00 PM

  What should happen:
  The alarm is triggered at 3:00 PM

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1283236/+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