[Dx-packages] [Bug 1826271] Re: virt-manager does not save preferences

[Tim Crisall]

Thought I was hitting this same issue - turns out it wasn't quite the
same as I did NOT have dconf-editor available.

Ended up figuring this out as follows:

virt-manager --debug

<...go into preferences screen...>

(virt-manager:10411): dconf-WARNING **: 03:20:30.256: failed to commit changes 
to dconf: Failed to execute child process “dbus-launch” (No such file or 
directory)
[Fri, 29 Nov 2019 03:20:30 virt-manager 10411] DEBUG (preferences:97) Showing 
preferences

apt install dbus-x11

all good now.

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

Title:
  virt-manager does not save preferences

Status in d-conf package in Ubuntu:
  Confirmed
Status in virt-manager package in Ubuntu:
  Incomplete

Bug description:
  running Ubuntu 18.04.2 LTS with KDE Plasma 5.12.7 (Qt 5.9.5)
  after a recent discover software update virt-manager no longer saves 
preferences. preferences were correctly saved previously (march 2019 and 
earlier)

  /usr/bin/virt-manager
  edit -> preferences -> polling
  select poll disk i/o
  select memory stats
  close window

  virt-manager displays cpu usage only.
  on restart preferences have not been saved

  also, when starting vm's the virtual machine terminal is too small.
  previously (march 2019 and earlier) the vm terminals would 'remember'
  the window-size that had been made.

  something must be 'broken'. can't find virt-manager preferences in any text
  file to determine if the file is written-to.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1826271/+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 1757009] [NEW] libappindicator3 not multilib aware, amd64 and i386 versions conflict

[Tim Brown]

Public bug reported:

Trying to install the amd64 and i386 versions of libappindicator3 on
trusty, xenial and artful all fail with a message similar to the
following:

tim@ubuntu-artful:~$ sudo apt install libappindicator3-1 libappindicator3-1:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
libappindicator3-1 is already the newest version 
(12.10.1+17.04.20170215-0ubuntu2).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
 libappindicator3-1 : Conflicts: libappindicator3-1:i386 but 
12.10.1+17.04.20170215-0ubuntu2 is to be installed
 libappindicator3-1:i386 : Depends: libindicator3-7:i386 (>= 0.4.90) but it is 
not going to be installed
   Conflicts: libappindicator3-1 but 
12.10.1+17.04.20170215-0ubuntu2 is to be installed
E: Unable to correct problems, you have held broken packages.

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


** Tags: multiarch

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

Title:
  libappindicator3 not multilib aware, amd64 and i386 versions conflict

Status in libappindicator package in Ubuntu:
  New

Bug description:
  Trying to install the amd64 and i386 versions of libappindicator3 on
  trusty, xenial and artful all fail with a message similar to the
  following:

  tim@ubuntu-artful:~$ sudo apt install libappindicator3-1 
libappindicator3-1:i386
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  libappindicator3-1 is already the newest version 
(12.10.1+17.04.20170215-0ubuntu2).
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  The following packages have unmet dependencies:
   libappindicator3-1 : Conflicts: libappindicator3-1:i386 but 
12.10.1+17.04.20170215-0ubuntu2 is to be installed
   libappindicator3-1:i386 : Depends: libindicator3-7:i386 (>= 0.4.90) but it 
is not going to be installed
 Conflicts: libappindicator3-1 but 
12.10.1+17.04.20170215-0ubuntu2 is to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1757009/+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 1728449] Re: Indicator icons do not appear after upgrade to Ubuntu 17.10

[Tim Passingham]

Marco - If you are referring to my comments, I freely admit my linux
knowledge is very limited.

As a client upgrading from 17.04 I do not, and seemingly have no way of
knowing, what a valid configuration is in this respect.  I'm not using
Unity any more, and am using Ubuntu (Xorg) rather than the explicit
GNOME login.

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

Title:
  Indicator icons do not appear after upgrade to Ubuntu 17.10

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in indicator-application package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 17.04 to 17.10 all the indicator icons (Steam,
  InSync, Google Chrome, Hangouts, Slack, etc) are missing.

  A temporary workaround is to kill indicator-application-service, but
  this only works until the next reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: indicator-application 12.10.1+17.04.20161201-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 29 20:45:06 2017
  InstallationDate: Installed on 2015-03-28 (946 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-application
  UpgradeStatus: Upgraded to artful on 2017-10-07 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728449/+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 1728449] Re: Indicator icons do not appear after upgrade to Ubuntu 17.10

[Tim Passingham]

To update my comment above, I then tried deleting the packages as in #4
and #5, disabling "topicons plus" and "Kstatusnotifieritem/appindictor
support" extensions, rebooting, enabling "Ubuntu appindicators", and all
is now well and stable (so far...).

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

Title:
  Indicator icons do not appear after upgrade to Ubuntu 17.10

Status in indicator-application package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 17.04 to 17.10 all the indicator icons (Steam,
  InSync, Google Chrome, Hangouts, Slack, etc) are missing.

  A temporary workaround is to kill indicator-application-service, but
  this only works until the next reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: indicator-application 12.10.1+17.04.20161201-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 29 20:45:06 2017
  InstallationDate: Installed on 2015-03-28 (946 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-application
  UpgradeStatus: Upgraded to artful on 2017-10-07 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1728449/+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 1728449] Re: Indicator icons do not appear after upgrade to Ubuntu 17.10

[Tim Passingham]

I had a similar problem on 17.10, logging on as Ubuntu xorg (not unity).
I tried running with just "ubuntu appindicators", but several indicators
were missing (particularly classicmenu and gnome encfs).

Eventually I got all the icons I need back by installing both "topicons
plus" and "Kstatusnotifieritem/appindictor support" extensions and
disabling "ubuntu appindicators".  On rebooting the latter then shows as
having an error (in gnome tweaks).

That's OK so far, since at least it now does what I need.

However, occasionally on starting up "ubuntu appindicators" becomes
enabled, and "Kstatusnotifieritem/appindictor support" disabled.  I then
lose my indicators, have to reset the extension statuses, reboot, and
cross my fingers.

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

Title:
  Indicator icons do not appear after upgrade to Ubuntu 17.10

Status in indicator-application package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 17.04 to 17.10 all the indicator icons (Steam,
  InSync, Google Chrome, Hangouts, Slack, etc) are missing.

  A temporary workaround is to kill indicator-application-service, but
  this only works until the next reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: indicator-application 12.10.1+17.04.20161201-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 29 20:45:06 2017
  InstallationDate: Installed on 2015-03-28 (946 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-application
  UpgradeStatus: Upgraded to artful on 2017-10-07 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1728449/+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 1693992] Re: /usr/lib/gdm3/gdm-session-worker:6:g_assertion_message:g_assertion_message_expr:load_users:load_idle:g_main_dispatch

[Tim]

** Also affects: accountsservice (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-gnome
   Importance: Undecided
   Status: New

** Changed in: ubuntu-gnome
Milestone: None => artful

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

Title:
  /usr/lib/gdm3/gdm-session-
  
worker:6:g_assertion_message:g_assertion_message_expr:load_users:load_idle:g_main_dispatch

Status in Ubuntu GNOME:
  New
Status in accountsservice package in Ubuntu:
  New
Status in gdm3 package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gdm3.  This problem was most recently seen with package version 
3.24.1-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/c0848264c9da4adaeb5da47a7aa34ce5bdd84909 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1693992/+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 1591342] Re: Complains about bad url on libertine scope urls

[Tim Süberkrüb]

It definitely worked before, but I understand now what you mean.

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

Title:
  Complains about bad url on libertine scope urls

Status in Canonical System Image:
  In Progress
Status in libertine-scope package in Ubuntu:
  Invalid
Status in url-dispatcher package in Ubuntu:
  In Progress

Bug description:
  ** (process:4255): WARNING **: Unable to dispatch url
  
'appid://xenial/org.kde.kate/0.0':GDBus.Error:com.canonical.URLDispatcher.BadURL:
  URL 'appid://xenial/org.kde.kate/0.0' is not handleable by the URL
  Dispatcher

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591342/+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 1591342] Re: Complains about bad url on libertine scope urls

[Tim Süberkrüb]

For the record: Installing Silo 1886 fixed the problem. So was this the
right bug after all?

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

Title:
  Complains about bad url on libertine scope urls

Status in Canonical System Image:
  In Progress
Status in libertine-scope package in Ubuntu:
  Invalid
Status in url-dispatcher package in Ubuntu:
  In Progress

Bug description:
  ** (process:4255): WARNING **: Unable to dispatch url
  
'appid://xenial/org.kde.kate/0.0':GDBus.Error:com.canonical.URLDispatcher.BadURL:
  URL 'appid://xenial/org.kde.kate/0.0' is not handleable by the URL
  Dispatcher

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591342/+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 1591342] Re: Complains about bad url on libertine scope urls

[Tim Süberkrüb]

Apologize for this misunderstanding, apparently this is - even though it
looked like it (at least to me) in the first place - not the cause for
the problem I mentioned. Thanks for clarifying.

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

Title:
  Complains about bad url on libertine scope urls

Status in Canonical System Image:
  In Progress
Status in libertine-scope package in Ubuntu:
  Invalid
Status in url-dispatcher package in Ubuntu:
  In Progress

Bug description:
  ** (process:4255): WARNING **: Unable to dispatch url
  
'appid://xenial/org.kde.kate/0.0':GDBus.Error:com.canonical.URLDispatcher.BadURL:
  URL 'appid://xenial/org.kde.kate/0.0' is not handleable by the URL
  Dispatcher

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591342/+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 1591342] Re: Complains about bad url on libertine scope urls

[Tim Süberkrüb]

> To be clear, URL Dispatcher hasn't changed except for rebuilds since
> November 2015. It's not anything related to OTA13 or any of the last
> several OTAs. If those apps worked in OTA12 but not 13, it wasn't URL
> Dispatcher's fault.
> Not saying this should get fixed and land, but acting like it broke
> apps is disingenuous.
I apologize for the misinformation (if that's the case).
But you pointed me to this bug on IRC 
(https://irclogs.ubuntu.com/2016/08/22/%23ubuntu-app-devel.html) :-)
I'm a bit confused now TBH.

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

Title:
  Complains about bad url on libertine scope urls

Status in Canonical System Image:
  In Progress
Status in libertine-scope package in Ubuntu:
  Invalid
Status in url-dispatcher package in Ubuntu:
  In Progress

Bug description:
  ** (process:4255): WARNING **: Unable to dispatch url
  
'appid://xenial/org.kde.kate/0.0':GDBus.Error:com.canonical.URLDispatcher.BadURL:
  URL 'appid://xenial/org.kde.kate/0.0' is not handleable by the URL
  Dispatcher

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591342/+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 1591342] Re: Complains about bad url on libertine scope urls

[Tim Süberkrüb]

FWIW, this bug results in users not being able to launch certain apps on 
OTA-13. At least Ubuntu Hangups, Liri Browser and YourGUS are affected by this 
problem.
Can you give any information about when the fix will land?

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

Title:
  Complains about bad url on libertine scope urls

Status in Canonical System Image:
  In Progress
Status in libertine-scope package in Ubuntu:
  Invalid
Status in url-dispatcher package in Ubuntu:
  Triaged

Bug description:
  ** (process:4255): WARNING **: Unable to dispatch url
  
'appid://xenial/org.kde.kate/0.0':GDBus.Error:com.canonical.URLDispatcher.BadURL:
  URL 'appid://xenial/org.kde.kate/0.0' is not handleable by the URL
  Dispatcher

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591342/+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 1581744] Re: User profile photo won't change

[Tim]

Hi,
  Thanks for your bug report, there are people on #ubuntu-gnome, you just need 
to ask a question and then be patient!

Anyway I can confirm this issue on 3.20 (w/ gnome3-staging)

(gnome-control-center.real:18529): AccountsService-WARNING **:
SetIconFile call failed:
GDBus.Error:org.freedesktop.Accounts.Error.PermissionDenied: Not
authorized


** Changed in: ubuntu-gnome
Milestone: None => yakkety

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

** Also affects: accountsservice (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  User profile photo won't change

Status in Ubuntu GNOME:
  New
Status in accountsservice package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Hi!

  I was super excited to find out I could use gnome3 however
  disappointed to find a few things were broken.

  In particular, when I tried to change my user profile photo, it won't
  change. Here are the steps to reproduce

  1. Install gnome-ubuntu with 2 hard drives dual booting with windows
  2. Encrypt your home folder
  3. Try to change your profile photo by going to account settings -> Users -> 
Unlock -> and click on the gray icon.
  4. Scream loudly at your computer when it doesn't work over and over again
  5. Manually try to change ~/.face to the photo you want
  6. Screen loudly again at your computer when you find out it doesn't change 
the login screens photo
  7. Desperately try to get help on #ubuntu irc channel and get rejected 
because you use Gnome
  8. Go to #ubuntu-gnome and realize that nobody is there to help support you. 
  9. Post a sassy bug report on launchpad.net

  I hope this helps, it would be nice to figure out how to fix this
  problem. Since I didn't see any errors, I don't know what else to post
  here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1581744/+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 1547297] Re: No auto login in Ubuntu GNOME Xenial

[Tim]

** Changed in: ubuntu-gnome
   Status: Confirmed => Fix Released

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

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

Title:
  No auto login in Ubuntu GNOME Xenial

Status in Ubuntu GNOME:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Invalid
Status in sddm package in Ubuntu:
  Confirmed

Bug description:
  Just installed Ubuntu GNOME Xenial 20160218 amd64 and selected to auto
  login during installation, but once the installation was complete and
  I booted into Ubuntu GNOME I was asked for my password. I looked in
  the user UI and auto login was set to off, so I unlocked it, selected
  auto login = on, clicked on lock again, and rebooted but was once
  again asked for my password and the user UI once again showed auto
  login = off.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdm3 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Feb 18 20:26:14 2016
  InstallationDate: Installed on 2016-02-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1547297/+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 1547297] Re: No auto login in Ubuntu GNOME Xenial

[Tim]

** No longer affects: gdm

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

Title:
  No auto login in Ubuntu GNOME Xenial

Status in Ubuntu GNOME:
  Confirmed
Status in accountsservice package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Confirmed
Status in sddm package in Ubuntu:
  Confirmed

Bug description:
  Just installed Ubuntu GNOME Xenial 20160218 amd64 and selected to auto
  login during installation, but once the installation was complete and
  I booted into Ubuntu GNOME I was asked for my password. I looked in
  the user UI and auto login was set to off, so I unlocked it, selected
  auto login = on, clicked on lock again, and rebooted but was once
  again asked for my password and the user UI once again showed auto
  login = off.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdm3 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Feb 18 20:26:14 2016
  InstallationDate: Installed on 2016-02-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1547297/+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 1487819] Re: Wily user UI shows auto-login off after selecting on during install

[Tim]

oddly the toggle state works fine on xenial + GNOME 3.20, which would
still be using the same accountsservice. However the related code in
gnome-control-center has not changed in years

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

Title:
  Wily user UI shows auto-login off after selecting on during install

Status in accountsservice package in Ubuntu:
  New
Status in gdm package in Ubuntu:
  Confirmed

Bug description:
  Just testing Ubuntu GNOME Wily 20150822 i386 and I've noticed that in
  spite of selecting auto-login = on during installation when the
  installation is complete and after first boot opening Settings > Users
  the UI shows off, but auto-login is working properly and if you toggle
  the UI back and forth from off to on a couple of times it seems to
  start working properly.

  I also installed Ubuntu 20150822 i386 and it's not affected so I
  suspect this is either a bug in gdm or possibly in g-c-c or g-s-d.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gdm 3.16.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic i686
  ApportVersion: 2.18-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sat Aug 22 23:04:29 2015
  InstallationDate: Installed on 2015-08-23 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 (20150822)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm.custom.conf: 2015-08-22T21:20:12.826508

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1487819/+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 1487819] Re: Wily user UI shows auto-login off after selecting on during install

[Tim]

** Also affects: accountsservice (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Wily user UI shows auto-login off after selecting on during install

Status in accountsservice package in Ubuntu:
  New
Status in gdm package in Ubuntu:
  Confirmed

Bug description:
  Just testing Ubuntu GNOME Wily 20150822 i386 and I've noticed that in
  spite of selecting auto-login = on during installation when the
  installation is complete and after first boot opening Settings > Users
  the UI shows off, but auto-login is working properly and if you toggle
  the UI back and forth from off to on a couple of times it seems to
  start working properly.

  I also installed Ubuntu 20150822 i386 and it's not affected so I
  suspect this is either a bug in gdm or possibly in g-c-c or g-s-d.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gdm 3.16.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic i686
  ApportVersion: 2.18-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sat Aug 22 23:04:29 2015
  InstallationDate: Installed on 2015-08-23 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 (20150822)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm.custom.conf: 2015-08-22T21:20:12.826508

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1487819/+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 1547297] Re: No auto login in Ubuntu GNOME Xenial

[Tim]

** Patch added: "gdm3-path.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1547297/+attachment/4625468/+files/gdm3-path.debdiff

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

Title:
  No auto login in Ubuntu GNOME Xenial

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in accountsservice package in Ubuntu:
  New
Status in gdm3 package in Ubuntu:
  Confirmed
Status in sddm package in Ubuntu:
  Confirmed

Bug description:
  Just installed Ubuntu GNOME Xenial 20160218 amd64 and selected to auto
  login during installation, but once the installation was complete and
  I booted into Ubuntu GNOME I was asked for my password. I looked in
  the user UI and auto login was set to off, so I unlocked it, selected
  auto login = on, clicked on lock again, and rebooted but was once
  again asked for my password and the user UI once again showed auto
  login = off.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdm3 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Feb 18 20:26:14 2016
  InstallationDate: Installed on 2016-02-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1547297/+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 1547297] Re: No auto login in Ubuntu GNOME Xenial

[Tim]

Accounts Service is supposed to update custom.conf, but the path is
wrong now

** Also affects: accountsservice (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  No auto login in Ubuntu GNOME Xenial

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in accountsservice package in Ubuntu:
  New
Status in gdm3 package in Ubuntu:
  Confirmed
Status in sddm package in Ubuntu:
  Confirmed

Bug description:
  Just installed Ubuntu GNOME Xenial 20160218 amd64 and selected to auto
  login during installation, but once the installation was complete and
  I booted into Ubuntu GNOME I was asked for my password. I looked in
  the user UI and auto login was set to off, so I unlocked it, selected
  auto login = on, clicked on lock again, and rebooted but was once
  again asked for my password and the user UI once again showed auto
  login = off.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdm3 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Feb 18 20:26:14 2016
  InstallationDate: Installed on 2016-02-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1547297/+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 1547297] Re: No auto login in Ubuntu GNOME Xenial

[Tim]

Note the above comment is specific to gdm.

I do notice however that the Accounts Service "AutomaticLogin" property
is not persistent across reboots, that would be why the settings toggle
is broken.

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

Title:
  No auto login in Ubuntu GNOME Xenial

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in accountsservice package in Ubuntu:
  New
Status in gdm3 package in Ubuntu:
  Confirmed
Status in sddm package in Ubuntu:
  Confirmed

Bug description:
  Just installed Ubuntu GNOME Xenial 20160218 amd64 and selected to auto
  login during installation, but once the installation was complete and
  I booted into Ubuntu GNOME I was asked for my password. I looked in
  the user UI and auto login was set to off, so I unlocked it, selected
  auto login = on, clicked on lock again, and rebooted but was once
  again asked for my password and the user UI once again showed auto
  login = off.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdm3 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Feb 18 20:26:14 2016
  InstallationDate: Installed on 2016-02-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1547297/+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 1556684] Re: gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()

[Tim]

the Ignoring launcher messages are unrelated.

The crash was 32-bit only, uploading a fix now

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

Title:
  gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()

Status in Ubuntu GNOME:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  I wanted to install Japanese through the gnome-control-center, so I
  opened it, went to the "Region & Language" section, clicked
  "Language", searched for "Japanese", when I found it I clicked on it
  (a tick appeared next to it), and finally I clicked "Done". Now what
  then should have happened is it should have asked me if I wanted to
  install the language packs it would then present to me and I would be
  able to continue with the installation... What instead happened was it
  hanged for a while and then finally outputted in Terminal:

  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Language 
ja_JP.UTF-8 not installed, trying to intall it
  Segmentation fault (core dumped)

  The full output in Terminal was:

  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
landscape-client-settings (missing desktop file)
  
  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
language-selector (missing desktop file)
  
  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
ubuntuone-installer (missing desktop file)
  
  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Couldn't 
get LANG locale -- Copying interrupted
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_language_from_locale: assertion '*locale != '\0'' failed
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_country_from_locale: assertion '*locale != '\0'' failed

  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Couldn't 
get LANG locale -- Copying interrupted
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_language_from_locale: assertion '*locale != '\0'' failed
  
  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Language 
ja_JP.UTF-8 not installed, trying to intall it
  Segmentation fault (core dumped)

  I have tested this bug and it is present in Ubuntu GNOME 15.10 with
  GNOME 3.18 and 16.04 with GNOME 3.19 VMs, however I cannot reproduce
  it on the host (15.10 with GNOME 3.18).

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.19.90-0ubuntu1~xenial1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 13 20:45:54 2016
  ExecutablePath: /usr/bin/gnome-control-center.real
  InstallationDate: Installed on 2016-03-04 (9 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha i386 
(20160225.1)
  ProcCmdline: /usr/bin/gnome-control-center.real
  SegvAnalysis:
   Segfault happened at: 0xb5b30c10 :  movzbl 
(%ebx),%eax
   PC (0xb5b30c10) ok
   source "(%ebx)" (0x13e9c381) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_utf8_validate () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_variant_new_string () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_variant_new_strv () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1556684/+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 1556684] Re: gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()

[Tim]

Test on a clean install, you can't install gnome-control-center 3.18
alongside 3.19.

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

Title:
  gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()

Status in Ubuntu GNOME:
  New
Status in accountsservice package in Ubuntu:
  Fix Released

Bug description:
  I wanted to install Japanese through the gnome-control-center, so I
  opened it, went to the "Region & Language" section, clicked
  "Language", searched for "Japanese", when I found it I clicked on it
  (a tick appeared next to it), and finally I clicked "Done". Now what
  then should have happened is it should have asked me if I wanted to
  install the language packs it would then present to me and I would be
  able to continue with the installation... What instead happened was it
  hanged for a while and then finally outputted in Terminal:

  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Language 
ja_JP.UTF-8 not installed, trying to intall it
  Segmentation fault (core dumped)

  The full output in Terminal was:

  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
landscape-client-settings (missing desktop file)
  
  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
language-selector (missing desktop file)
  
  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
ubuntuone-installer (missing desktop file)
  
  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Couldn't 
get LANG locale -- Copying interrupted
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_language_from_locale: assertion '*locale != '\0'' failed
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_country_from_locale: assertion '*locale != '\0'' failed

  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Couldn't 
get LANG locale -- Copying interrupted
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_language_from_locale: assertion '*locale != '\0'' failed
  
  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Language 
ja_JP.UTF-8 not installed, trying to intall it
  Segmentation fault (core dumped)

  I have tested this bug and it is present in Ubuntu GNOME 15.10 with
  GNOME 3.18 and 16.04 with GNOME 3.19 VMs, however I cannot reproduce
  it on the host (15.10 with GNOME 3.18).

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.19.90-0ubuntu1~xenial1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 13 20:45:54 2016
  ExecutablePath: /usr/bin/gnome-control-center.real
  InstallationDate: Installed on 2016-03-04 (9 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha i386 
(20160225.1)
  ProcCmdline: /usr/bin/gnome-control-center.real
  SegvAnalysis:
   Segfault happened at: 0xb5b30c10 :  movzbl 
(%ebx),%eax
   PC (0xb5b30c10) ok
   source "(%ebx)" (0x13e9c381) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_utf8_validate () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_variant_new_string () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_variant_new_strv () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1556684/+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] [Bug 1556684] Re: gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()

[Tim]

On Thu, Mar 17, 2016, at 02:27 AM, Nikita Yerenkov-Scott wrote:
> I have tested your fix and I still get this as the output but no
> Japanese install:
> 
> ** (gnome-control-center.real:3528): WARNING **: Ignoring launcher
> gufw (missing desktop file)
> 
> ** (gnome-control-center.real:3528): WARNING **: Ignoring launcher
> landscape-client-settings (missing desktop file)
> 
> ** (gnome-control-center.real:3528): WARNING **: Ignoring launcher
> language-selector (missing desktop file)
> 
> ** (gnome-control-center.real:3528): WARNING **: Ignoring launcher
> ubuntuone-installer (missing desktop file)
> 
> (gnome-control-center.real:3528): common-cc-panel-WARNING **:
> Language ja_JP.UTF-8 not installed, trying to intall it
> Segmentation fault (core dumped)
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1556684
> 
> Title:
>   gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-gnome/+bug/1556684/+subscriptions

You still have the old gnomes controls center, are you testing on 16.04?
-- 
  Tim Lunn
  dark...@fastmail.fm

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

Title:
  gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()

Status in Ubuntu GNOME:
  New
Status in accountsservice package in Ubuntu:
  Fix Released

Bug description:
  I wanted to install Japanese through the gnome-control-center, so I
  opened it, went to the "Region & Language" section, clicked
  "Language", searched for "Japanese", when I found it I clicked on it
  (a tick appeared next to it), and finally I clicked "Done". Now what
  then should have happened is it should have asked me if I wanted to
  install the language packs it would then present to me and I would be
  able to continue with the installation... What instead happened was it
  hanged for a while and then finally outputted in Terminal:

  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Language 
ja_JP.UTF-8 not installed, trying to intall it
  Segmentation fault (core dumped)

  The full output in Terminal was:

  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
landscape-client-settings (missing desktop file)
  
  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
language-selector (missing desktop file)
  
  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
ubuntuone-installer (missing desktop file)
  
  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Couldn't 
get LANG locale -- Copying interrupted
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_language_from_locale: assertion '*locale != '\0'' failed
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_country_from_locale: assertion '*locale != '\0'' failed

  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Couldn't 
get LANG locale -- Copying interrupted
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_language_from_locale: assertion '*locale != '\0'' failed
  
  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Language 
ja_JP.UTF-8 not installed, trying to intall it
  Segmentation fault (core dumped)

  I have tested this bug and it is present in Ubuntu GNOME 15.10 with
  GNOME 3.18 and 16.04 with GNOME 3.19 VMs, however I cannot reproduce
  it on the host (15.10 with GNOME 3.18).

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.19.90-0ubuntu1~xenial1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 13 20:45:54 2016
  ExecutablePath: /usr/bin/gnome-control-center.real
  InstallationDate: Installed on 2016-03-04 (9 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha i386 
(20160225.1)
  ProcCmdline: /usr/bin/gnome-control-center.real
  SegvAnalysis:
   Segfault happened at: 0xb5b30c10 <g_utf8_validate+256>:  movzbl 
(%ebx),%eax
   PC (0xb5b30c10) ok
   source "(%ebx)" (0x13e9c381) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_utf8_validate () from /lib/i386-linux-gnu/libg

Re: [Dx-packages] [Bug 1556684] Re: gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()

[Tim]

On 17/03/16 17:49, Gunnar Hjalmarsson wrote:
> Tim,
>
> I was wrong in comment #55 at bug #1551283. The problem I had was (first
> time) *switching* of display language; *installing* a new language from
> Region & Language worked fine for me (still does).
Yeh I've not been able to reproduce nikita's crash, however apparently that is 
on 15.10
>
> g-c-c 1:3.18.2-1ubuntu6~xenial2 in your PPA fixes the language switching
> issue for me. The warning messages still appear when you start g-c-c
> from terminal, but apparently they are/were unrelated to my issue.
which warning? about is/not installed, or the LANG locale failed ones?
>

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

Title:
  gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()

Status in Ubuntu GNOME:
  New
Status in accountsservice package in Ubuntu:
  Fix Released

Bug description:
  I wanted to install Japanese through the gnome-control-center, so I
  opened it, went to the "Region & Language" section, clicked
  "Language", searched for "Japanese", when I found it I clicked on it
  (a tick appeared next to it), and finally I clicked "Done". Now what
  then should have happened is it should have asked me if I wanted to
  install the language packs it would then present to me and I would be
  able to continue with the installation... What instead happened was it
  hanged for a while and then finally outputted in Terminal:

  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Language 
ja_JP.UTF-8 not installed, trying to intall it
  Segmentation fault (core dumped)

  The full output in Terminal was:

  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
landscape-client-settings (missing desktop file)
  
  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
language-selector (missing desktop file)
  
  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
ubuntuone-installer (missing desktop file)
  
  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Couldn't 
get LANG locale -- Copying interrupted
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_language_from_locale: assertion '*locale != '\0'' failed
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_country_from_locale: assertion '*locale != '\0'' failed

  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Couldn't 
get LANG locale -- Copying interrupted
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_language_from_locale: assertion '*locale != '\0'' failed
  
  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Language 
ja_JP.UTF-8 not installed, trying to intall it
  Segmentation fault (core dumped)

  I have tested this bug and it is present in Ubuntu GNOME 15.10 with
  GNOME 3.18 and 16.04 with GNOME 3.19 VMs, however I cannot reproduce
  it on the host (15.10 with GNOME 3.18).

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.19.90-0ubuntu1~xenial1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 13 20:45:54 2016
  ExecutablePath: /usr/bin/gnome-control-center.real
  InstallationDate: Installed on 2016-03-04 (9 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha i386 
(20160225.1)
  ProcCmdline: /usr/bin/gnome-control-center.real
  SegvAnalysis:
   Segfault happened at: 0xb5b30c10 <g_utf8_validate+256>:  movzbl 
(%ebx),%eax
   PC (0xb5b30c10) ok
   source "(%ebx)" (0x13e9c381) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_utf8_validate () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_variant_new_string () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_variant_new_strv () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1556684/+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 1556684] Re: gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()

[Tim]

well I fixed the two places that I found causing warnings, but maybe
there are more in the less utilised code paths. Though pretty sure I
squished the one that was causing the issues (when accountservice didnt
yet have a language registered)

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

Title:
  gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()

Status in Ubuntu GNOME:
  New
Status in accountsservice package in Ubuntu:
  New

Bug description:
  I wanted to install Japanese through the gnome-control-center, so I
  opened it, went to the "Region & Language" section, clicked
  "Language", searched for "Japanese", when I found it I clicked on it
  (a tick appeared next to it), and finally I clicked "Done". Now what
  then should have happened is it should have asked me if I wanted to
  install the language packs it would then present to me and I would be
  able to continue with the installation... What instead happened was it
  hanged for a while and then finally outputted in Terminal:

  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Language 
ja_JP.UTF-8 not installed, trying to intall it
  Segmentation fault (core dumped)

  The full output in Terminal was:

  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
landscape-client-settings (missing desktop file)
  
  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
language-selector (missing desktop file)
  
  ** (gnome-control-center.real:1726): WARNING **: Ignoring launcher 
ubuntuone-installer (missing desktop file)
  
  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Couldn't 
get LANG locale -- Copying interrupted
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_language_from_locale: assertion '*locale != '\0'' failed
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_country_from_locale: assertion '*locale != '\0'' failed

  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Couldn't 
get LANG locale -- Copying interrupted
  
  (gnome-control-center.real:1726): GnomeDesktop-CRITICAL **: 
gnome_get_language_from_locale: assertion '*locale != '\0'' failed
  
  (gnome-control-center.real:1726): common-cc-panel-WARNING **: Language 
ja_JP.UTF-8 not installed, trying to intall it
  Segmentation fault (core dumped)

  I have tested this bug and it is present in Ubuntu GNOME 15.10 with
  GNOME 3.18 and 16.04 with GNOME 3.19 VMs, however I cannot reproduce
  it on the host (15.10 with GNOME 3.18).

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.19.90-0ubuntu1~xenial1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 13 20:45:54 2016
  ExecutablePath: /usr/bin/gnome-control-center.real
  InstallationDate: Installed on 2016-03-04 (9 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha i386 
(20160225.1)
  ProcCmdline: /usr/bin/gnome-control-center.real
  SegvAnalysis:
   Segfault happened at: 0xb5b30c10 :  movzbl 
(%ebx),%eax
   PC (0xb5b30c10) ok
   source "(%ebx)" (0x13e9c381) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_utf8_validate () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_variant_new_string () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_variant_new_strv () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center.real crashed with SIGSEGV in g_utf8_validate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1556684/+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 1527015] Re: Dont run zeitgeist on GNOME

[Tim]

** Changed in: ubuntu-gnome
   Importance: Undecided => Medium

** Changed in: ubuntu-gnome
   Status: New => Confirmed

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

Title:
  Dont run zeitgeist on GNOME

Status in Ubuntu GNOME:
  Confirmed
Status in zeitgeist package in Ubuntu:
  New

Bug description:
  Zeitgeist is not really useful under Ubuntu GNOME, and in fact we
  don't ship the binaries by default, since we use tracker. However if a
  user has both Unity and GNOME installed, then zeitgeist will run under
  the GNOME session also. Presumably this is pretty harmless but will
  eat up RAM and I/O cycles so would be good to avoid it.

  Hopefully just requires an AutostartCondition in desktop file(s) to
  fix.

  ProblemType: BugDistroRelease: Ubuntu 16.04
  Package: zeitgeist 0.9.16-0ubuntu3~gcc5.1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 17 12:39:45 2015
  InstallationDate: Installed on 2012-09-23 (1180 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  PackageArchitecture: allSourcePackage: zeitgeist
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1527015/+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 1527015] [NEW] Dont run zeitgeist on GNOME

[Tim]

Public bug reported:

Zeitgeist is not really useful under Ubuntu GNOME, and in fact we don't
ship the binaries by default, since we use tracker. However if a user
has both Unity and GNOME installed, then zeitgeist will run under the
GNOME session also. Presumably this is pretty harmless but will eat up
RAM and I/O cycles so would be good to avoid it.

Hopefully just requires an AutostartCondition in desktop file(s) to fix.

ProblemType: BugDistroRelease: Ubuntu 16.04
Package: zeitgeist 0.9.16-0ubuntu3~gcc5.1
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Dec 17 12:39:45 2015
InstallationDate: Installed on 2012-09-23 (1180 days ago)
InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
PackageArchitecture: allSourcePackage: zeitgeist
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-gnome
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug xenial

** Also affects: ubuntu-gnome
   Importance: Undecided
   Status: New

** Changed in: ubuntu-gnome
Milestone: None => xenial

** Description changed:

- Zeitgeist is really useful under Ubuntu GNOME, and in fact we don't ship
- the binaries by default, since we use tracker. However if a user has
- both Unity and GNOME installed, then zeitgeist will run under the GNOME
- session also. Presumably this is pretty harmless but will eat up RAM and
- I/O cycles so would be good to avoid it.
+ Zeitgeist is not really useful under Ubuntu GNOME, and in fact we don't
+ ship the binaries by default, since we use tracker. However if a user
+ has both Unity and GNOME installed, then zeitgeist will run under the
+ GNOME session also. Presumably this is pretty harmless but will eat up
+ RAM and I/O cycles so would be good to avoid it.
  
  Hopefully just requires an AutostartCondition in desktop file(s) to fix.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 16.04
+ ProblemType: BugDistroRelease: Ubuntu 16.04
  Package: zeitgeist 0.9.16-0ubuntu3~gcc5.1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 17 12:39:45 2015
  InstallationDate: Installed on 2012-09-23 (1180 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
- PackageArchitecture: all
- SourcePackage: zeitgeist
+ PackageArchitecture: allSourcePackage: zeitgeist
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Dont run zeitgeist on GNOME

Status in Ubuntu GNOME:
  New
Status in zeitgeist package in Ubuntu:
  New

Bug description:
  Zeitgeist is not really useful under Ubuntu GNOME, and in fact we
  don't ship the binaries by default, since we use tracker. However if a
  user has both Unity and GNOME installed, then zeitgeist will run under
  the GNOME session also. Presumably this is pretty harmless but will
  eat up RAM and I/O cycles so would be good to avoid it.

  Hopefully just requires an AutostartCondition in desktop file(s) to
  fix.

  ProblemType: BugDistroRelease: Ubuntu 16.04
  Package: zeitgeist 0.9.16-0ubuntu3~gcc5.1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 17 12:39:45 2015
  InstallationDate: Installed on 2012-09-23 (1180 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  PackageArchitecture: allSourcePackage: zeitgeist
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1527015/+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 1470033] Re: Pressing "Enter" on the "Reply to SMS" field of the SMS notification will clear the notification and erase the typed text, but the reply is not sent.

[Tim]

Also happening in MX4 release R4

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

Title:
  Pressing "Enter" on the "Reply to SMS" field of the SMS notification
  will clear the notification and erase the typed text, but the reply is
  not sent.

Status in indicator-messages package in Ubuntu:
  Confirmed

Bug description:
  When recieving an SMS in ubuntu touch, you can reply to this text message in 
the notification area directly.
  However, if you press "enter" to add a newline, the text you have just typed 
gets deleted, the reply closed,  just like as if you had pressed "send", but no 
message gets sent.
  This happens on my BQ Aqauris E4.5 with all the latest updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1470033/+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 999929] Re: Seamless Mode Not Working Correctly in Virtual Box

[Tim Chambers]

I can no longer reproduce this bug in 15.04 in VirtualBox 5.0.2 (Windows
host) on a Dell M4800.

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

Title:
  Seamless Mode Not Working Correctly in Virtual Box

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  I think the bug is in Nautilus, but the search field says there are
  too many matches. I'm making a naïve guess, anyway. Maybe it's in
  VirtualBox, which would be nice to get narrowed down.

  Enclosed is the text at  http://askubuntu.com/questions/136397
  /seamless-mode-not-working-correctly-in-virtual-box – three of us are
  seeing this issue, so I decided it's time to file a bug. Plus, as a
  fan of Ubuntu, I'm concerned that Giovanni said, This problem,
  together with the bad feeling I have with Unity, will probably force
  me to try other distributions, like Mint.

  -- tbc0

  [text updated 2012-05-31 by tbc0]
  I run Ubuntu Desktop in a VirtualBox seamless mode, hosted on Windows 7. I 
recently upgraded from 11.10 to 12.04 and seamless mode no longer works 
correctly. I have re-installed guest extensions.

  The problem is that the Ubuntu desktop wallpaper is shown, effectively
  blocking the Windows desktop. I can bring Windows apps to the
  foreground, but as soon as I bring any Ubuntu window to the
  foreground, all the windows apps will disappear, hidden by the ubuntu
  desktop even if I activated an Ubuntu window in a different monitor.
  So, it is not very much different from full-screen mode at this time.

  I suspect if I could turn off the Ubuntu desktop or wallpaper this
  would be a sufficient workaround (this is basically what Seamless mode
  is) but that does not seem to be possible within Ubuntu itself.

  [Jeremy doesn't specify system config, but I can confirm I'm seeing
  this behavior in Win 7 64-bit with both 32-bit and 64-bit guests.
  Giovanni sees the same thing on his laptop running Vista Ultimate 64
  bit after upgrading his 32-bit guest to 12.04 (forums.virtualbox.org
  p225407, requires logging in with your free Oracle account). I was
  using vbox 4.1.14r77440 and matching Guest Additions. I upgraded to
  4.1.16-78094 vbox+additions. Still a problem. And I filed launchpad
  bug 29 to see if I can get feedback from developers. – tbc0]

  Any other ideas?

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/29/+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 1440275] Re: Ubuntu GNOME only allows regional format setting for US, UK, Canada, Australia, and NZ

[Tim]

Gunnar, can you rebase against my 3.16 branch in bug 1468941?

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

Title:
  Ubuntu GNOME only allows regional format setting for US, UK, Canada,
  Australia, and NZ

Status in accountsservice package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-desktop3 package in Ubuntu:
  In Progress

Bug description:
  I installed Ubuntu GNOME 15.04 Beta 2. I set the system locale to
  Korean language, which worked okay. When I tried to set regional
  format (date, time, currency, number, metric, etc.), however, the
  options are only limited to 5 regions: US, UK, Canada, Australia, New
  Zealand. I do live in the US, but I want to set the regional format in
  Korean because that goes with the system language. I currently set the
  regional format to that of Canada because I am not familiar with US
  system of yards, feet and pounds. As you can see in the attached
  screenshot, the date format shown on the middle of the task bar is a
  mixture of English and Korean (Frankenstein-ish).

  As I browsed through the bug report launchpad site, I found this bug
  has a long history which dates back to Ubuntu version 9.04. I have
  installed Ubuntu GNOME 14.04 LTS on my other computer and it does not
  have the same bug. I guess it has something to do with the newly
  introduced systemd?

  I would very much like to see this bug is fixed ASAP (at least before
  the release of 15.04 proper version). I love GNOME interface, but this
  bug annoys me. Regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1440275/+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 1440275] Re: Ubuntu GNOME only allows regional format setting for US, UK, Canada, Australia, and NZ

[Tim]

@Gunnar, thanks changes look fine to me, however I can't sponsor since I
don't yet have upload rights to ubuntu-desktop packageset.

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

Title:
  Ubuntu GNOME only allows regional format setting for US, UK, Canada,
  Australia, and NZ

Status in accountsservice package in Ubuntu:
  In Progress
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gnome-desktop3 package in Ubuntu:
  In Progress

Bug description:
  I installed Ubuntu GNOME 15.04 Beta 2. I set the system locale to
  Korean language, which worked okay. When I tried to set regional
  format (date, time, currency, number, metric, etc.), however, the
  options are only limited to 5 regions: US, UK, Canada, Australia, New
  Zealand. I do live in the US, but I want to set the regional format in
  Korean because that goes with the system language. I currently set the
  regional format to that of Canada because I am not familiar with US
  system of yards, feet and pounds. As you can see in the attached
  screenshot, the date format shown on the middle of the task bar is a
  mixture of English and Korean (Frankenstein-ish).

  As I browsed through the bug report launchpad site, I found this bug
  has a long history which dates back to Ubuntu version 9.04. I have
  installed Ubuntu GNOME 14.04 LTS on my other computer and it does not
  have the same bug. I guess it has something to do with the newly
  introduced systemd?

  I would very much like to see this bug is fixed ASAP (at least before
  the release of 15.04 proper version). I love GNOME interface, but this
  bug annoys me. Regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1440275/+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 1313446] Re: window disappears on toggle shade

[Tim Hockin]

This is my #1 problem with Unity right now.  I keep a lot of in-
progress state in shaded windows on my 12.x systems, and I can no
longer do this at all on 14.x

Please oh please fix?

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

Title:
  window disappears on toggle shade

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  I used Unity Tweak Tool to enable Toggle Shade using middle click.
  When I click to top of the window, it rolls up and disappears. A
  ghost outline of the window appears and the only way to get the
  window back is by using Alt-tab. Sometimes, when reselecting the
  window using Alt-tab, Ubuntu freezes (crashes) and an internal error
  is generated. It seems to be related to Compiz but I'm not sure. An
  error report was generated and sent.

  Description:  Ubuntu 14.04 LTS (64-bit)
  Release:  14.04
  unity-tweak-tool 0.0.6ubuntu1

  I expected the window would roll up and I'd be left with the
  window's top bar like with previous versions of Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1313446/+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 1414390] [NEW] update to 0.6.40

[Tim]

Public bug reported:

New upstream release

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: accountsservice 0.6.37-1ubuntu10
ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
Uname: Linux 3.18.0-9-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.15.1-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Jan 25 14:29:08 2015
InstallationDate: Installed on 2012-09-23 (854 days ago)
InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha 
amd64(20120922)
SourcePackage: accountsservice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug vivid

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

Title:
  update to 0.6.40

Status in accountsservice package in Ubuntu:
  New

Bug description:
  New upstream release

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: accountsservice 0.6.37-1ubuntu10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jan 25 14:29:08 2015
  InstallationDate: Installed on 2012-09-23 (854 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha 
amd64(20120922)
  SourcePackage: accountsservice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1414390/+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 1414390] Re: update to 0.6.40

[Tim]

** Patch added: accountsservice-0.6.40.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1414390/+attachment/4305167/+files/accountsservice-0.6.40.debdiff

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

Title:
  update to 0.6.40

Status in accountsservice package in Ubuntu:
  New

Bug description:
  New upstream release

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: accountsservice 0.6.37-1ubuntu10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jan 25 14:29:08 2015
  InstallationDate: Installed on 2012-09-23 (854 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha 
amd64(20120922)
  SourcePackage: accountsservice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1414390/+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 1386255] Re: devhelp and many other apps crash with SIGSEGV in g_closure_invoke() due to overlay-scrollbars

[Tim]

** Changed in: ubuntu-gnome
   Status: New = 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/1386255

Title:
  devhelp and many other apps crash with SIGSEGV in g_closure_invoke()
  due to overlay-scrollbars

Status in Overlay Scrollbar:
  New
Status in Ubuntu GNOME:
  Fix Released
Status in overlay-scrollbar package in Ubuntu:
  Fix Released

Bug description:
  With the gnome3-team/gnome3-staging PPA enabled all Gtk+ applications
  segfault when I do stuff like

  - Press the Menu key
  - Press the Save button in gedit's headerbar
  - Press the hamburger menu button in devhelp's headerbar (the stack trace 
attached to this bug)
  - Press the Add button in gtimelog
  - Try to open any of the regular menus in gtimelog

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: devhelp 3.14.0-1~utopic1 [origin: LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 27 17:15:30 2014
  Disassembly: = 0x0:  Cannot access memory at address 0x0
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/devhelp
  InstallationDate: Installed on 2012-07-25 (824 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcCmdline: devhelp
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: devhelp
  StacktraceTop:
   ?? ()
   g_closure_invoke (closure=0x11e4ce0, return_value=0x0, n_param_values=2, 
param_values=0x7fffd6ed0920, invocation_hint=0x7fffd6ed08c0) at 
/build/buildd/glib2.0-2.42.0/./gobject/gclosure.c:768
   signal_emit_unlocked_R (node=node@entry=0x11e50b0, detail=detail@entry=0, 
instance=instance@entry=0x182a510, emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffd6ed0920) at 
/build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3483
   g_signal_emit_valist (instance=optimized out, signal_id=optimized out, 
detail=optimized out, var_args=var_args@entry=0x7fffd6ed0ab0) at 
/build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3309
   g_signal_emit (instance=instance@entry=0x182a510, signal_id=optimized out, 
detail=detail@entry=0) at /build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3365
  Title: devhelp crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (3 days ago)
  UserGroups: adm cdrom dip docker libvirtd lp lpadmin plugdev sambashare 
shared sudo wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/overlay-scrollbar/+bug/1386255/+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 1397517] [NEW] Unity Screen Brightness Settings not Preserved on Reboot

[Tim Edwards]

Public bug reported:

Whenever Unity starts it sets the screen brightness to maximum, even
when the laptop is on battery. Lowering the screen brightness doesn't
persist across reboots.

To reproduce:
1. Start laptop (in this case a Lenovo Yoga 2 Pro) in battery mode (i.e. 
disconnected from the AC adaptor)
2. Unity will start in maximum brightness. Lower brightness using keyboard 
brightness keys.
3. Shutdown laptop and start it back up again (still with the AC adapter 
disconnected)

Expected result:
The screen brightness settings should be preserved across reboots

Actual result:
After each new start Unity sets the screen brightness to maximum, meaning the 
user has to remember to manually reduce it or the battery will be quickly used 
up

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,imgpng,mousepoll,vpswitch,unitymtgrabhandles,gnomecompat,regex,move,grid,place,wall,animation,snap,resize,fade,session,expo,workarounds,scale,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Nov 29 11:59:31 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3978]
InstallationDate: Installed on 2014-09-16 (73 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
MachineType: LENOVO 20266
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic.efi.signed 
root=/dev/mapper/MainVG-root ro video.use_native_backlight=1 quiet splash 
vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 76CN35WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Yoga2
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga 2 Pro
dmi.modalias: 
dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
dmi.product.name: 20266
dmi.product.version: Lenovo Yoga 2 Pro
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11.2+14.04.20140714-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.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
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.3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Nov 28 23:10:38 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16970 
 vendor SDC
xserver.version: 2:1.15.1-0ubuntu2.1

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages trusty 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/1397517

Title:
  Unity Screen Brightness Settings not Preserved on Reboot

Status in unity package in Ubuntu:
  New

Bug description:
  Whenever Unity starts it sets the screen brightness to maximum, even
  when the laptop is on battery. Lowering the screen brightness doesn't
  persist across reboots.

  To reproduce:
  1. Start laptop (in this case a Lenovo Yoga 2 Pro) in battery mode (i.e. 
disconnected from the AC adaptor)
  2. Unity will start in maximum brightness. Lower brightness using keyboard 
brightness keys.
  3. Shutdown laptop and start it back up again (still with the AC adapter 
disconnected)

  Expected result:
  The screen brightness settings should be preserved across reboots

  Actual result:
  After each new start Unity sets the screen brightness to maximum, meaning the 
user has to remember to manually reduce it or the battery will be quickly used 
up

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: 

[Dx-packages] [Bug 1389336] Re: Use geoclue-2.0

[Tim]

Seb, That is correct its no longer possible to provide custom providers,
so it would either require teaching the ubuntu GeoIP server the
Geolocate API or merging ubuntu-geoip directly into geoclue as a
location source.

There was a one point a geoip client in geoclue-2.0 but it got dropped when 
GNOME switched to using Mozilla Location Service. It should be possible to do 
something similar for ubuntu-geoip support
http://cgit.freedesktop.org/geoclue/commit/?id=b6563179f55b44b9b566c11c8c4bc0870d50879f

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

Title:
  Use geoclue-2.0

Status in “empathy” package in Ubuntu:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  New
Status in “libunity-webapps” package in Ubuntu:
  New
Status in “qtlocation-opensource-src” package in Ubuntu:
  New
Status in “ubuntu-geoip” package in Ubuntu:
  New
Status in “webkitgtk” package in Ubuntu:
  New

Bug description:
  Geoclue2 (source package geoclue-2.0) is a separate, parallel-
  installable version of geoclue1 (source package geoclue).  We will
  likely shortly have both in main (see MIR bug 1388294) and it would be
  great to be able to demote geoclue1 to universe and only support one
  version of the service.

  The packages associated with this bug all have a reverse depends on
  geoclue1 in some form or patches to remove support for geoclue-2.0
  because it wasn't in main yet (e.g. gnome-settings-daemon).

  Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial.
  But we have at least six months to do it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+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 1386255] Re: devhelp and many other apps crash with SIGSEGV in g_closure_invoke() due to overlay-scrollbars

[Tim]

This will need to be fixed for gtk+3.14 to land in vivid

** Also affects: overlay-scrollbar (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-gnome
Milestone: None = vivid

** Tags added: ubuntugnome-blocker

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

Title:
  devhelp and many other apps crash with SIGSEGV in g_closure_invoke()
  due to overlay-scrollbars

Status in Ubuntu GNOME:
  New
Status in “overlay-scrollbar” package in Ubuntu:
  New

Bug description:
  With the gnome3-team/gnome3-staging PPA enabled all Gtk+ applications
  segfault when I do stuff like

  - Press the Menu key
  - Press the Save button in gedit's headerbar
  - Press the hamburger menu button in devhelp's headerbar (the stack trace 
attached to this bug)
  - Press the Add button in gtimelog
  - Try to open any of the regular menus in gtimelog

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: devhelp 3.14.0-1~utopic1 [origin: LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 27 17:15:30 2014
  Disassembly: = 0x0:  Cannot access memory at address 0x0
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/devhelp
  InstallationDate: Installed on 2012-07-25 (824 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcCmdline: devhelp
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: devhelp
  StacktraceTop:
   ?? ()
   g_closure_invoke (closure=0x11e4ce0, return_value=0x0, n_param_values=2, 
param_values=0x7fffd6ed0920, invocation_hint=0x7fffd6ed08c0) at 
/build/buildd/glib2.0-2.42.0/./gobject/gclosure.c:768
   signal_emit_unlocked_R (node=node@entry=0x11e50b0, detail=detail@entry=0, 
instance=instance@entry=0x182a510, emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffd6ed0920) at 
/build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3483
   g_signal_emit_valist (instance=optimized out, signal_id=optimized out, 
detail=optimized out, var_args=var_args@entry=0x7fffd6ed0ab0) at 
/build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3309
   g_signal_emit (instance=instance@entry=0x182a510, signal_id=optimized out, 
detail=detail@entry=0) at /build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3365
  Title: devhelp crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (3 days ago)
  UserGroups: adm cdrom dip docker libvirtd lp lpadmin plugdev sambashare 
shared sudo wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1386255/+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 1386255] Re: devhelp and many other apps crash with SIGSEGV in g_closure_invoke() due to overlay-scrollbars

[Tim]

** Branch linked: lp:~darkxst/overlay-scrollbar/lp1386255

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

Title:
  devhelp and many other apps crash with SIGSEGV in g_closure_invoke()
  due to overlay-scrollbars

Status in Overlay Scrollbar:
  New
Status in Ubuntu GNOME:
  New
Status in “overlay-scrollbar” package in Ubuntu:
  New

Bug description:
  With the gnome3-team/gnome3-staging PPA enabled all Gtk+ applications
  segfault when I do stuff like

  - Press the Menu key
  - Press the Save button in gedit's headerbar
  - Press the hamburger menu button in devhelp's headerbar (the stack trace 
attached to this bug)
  - Press the Add button in gtimelog
  - Try to open any of the regular menus in gtimelog

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: devhelp 3.14.0-1~utopic1 [origin: LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 27 17:15:30 2014
  Disassembly: = 0x0:  Cannot access memory at address 0x0
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/devhelp
  InstallationDate: Installed on 2012-07-25 (824 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcCmdline: devhelp
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: devhelp
  StacktraceTop:
   ?? ()
   g_closure_invoke (closure=0x11e4ce0, return_value=0x0, n_param_values=2, 
param_values=0x7fffd6ed0920, invocation_hint=0x7fffd6ed08c0) at 
/build/buildd/glib2.0-2.42.0/./gobject/gclosure.c:768
   signal_emit_unlocked_R (node=node@entry=0x11e50b0, detail=detail@entry=0, 
instance=instance@entry=0x182a510, emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffd6ed0920) at 
/build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3483
   g_signal_emit_valist (instance=optimized out, signal_id=optimized out, 
detail=optimized out, var_args=var_args@entry=0x7fffd6ed0ab0) at 
/build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3309
   g_signal_emit (instance=instance@entry=0x182a510, signal_id=optimized out, 
detail=detail@entry=0) at /build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3365
  Title: devhelp crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (3 days ago)
  UserGroups: adm cdrom dip docker libvirtd lp lpadmin plugdev sambashare 
shared sudo wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/overlay-scrollbar/+bug/1386255/+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 1364949] Re: Editing alarm sounds doesn't actually change them

[Tim Peeters]

** Changed in: ubuntu-ui-toolkit
   Status: Fix Committed = Fix Released

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

Title:
  Editing alarm sounds doesn't actually change them

Status in The Date and Time Indicator:
  Fix Released
Status in Ubuntu UI Toolkit:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Fix Released
Status in “qtorganizer5-eds” package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. Open the clock app
  2. Swipe up from the bottom
  3. Click on the + symbol
  4. Save an alarm for a few minutes time leave everything on default settings
  5. Click on save
  6. Click on the alarm
  7. Change the sound of the alram
  8. Click on save
  9. Let the alarm go off

  EXPECTED:
  I expected the sound I chose to play

  ACTUAL:
  The default harps played instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1364949/+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: [FFe] upower 0.99.1 transition

[Tim]

As Laney mentoned Shipping upower 0.99 only for GNOME would be a lot of
work. I have however managed to untangle the gnome-desktop transition
from upower, so we can now land that without upower 0.99, in which case
landing upower transition as soon a V opens should probably be ok.

-- 
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:
  [FFe] upower 0.99.1 transition

Status in “cairo-dock-plug-ins” package in Ubuntu:
  Fix Committed
Status in “cinnamon-control-center” package in Ubuntu:
  New
Status in “cinnamon-session” package in Ubuntu:
  New
Status in “cinnamon-settings-daemon” package in Ubuntu:
  New
Status in “gnome-applets” package in Ubuntu:
  In Progress
Status in “gnome-control-center” package in Ubuntu:
  In Progress
Status in “gnome-packagekit” package in Ubuntu:
  Fix Released
Status in “gnome-power-manager” package in Ubuntu:
  In Progress
Status in “gnome-session” package in Ubuntu:
  In Progress
Status in “gnome-settings-daemon” package in Ubuntu:
  In Progress
Status in “gnome-shell” package in Ubuntu:
  In Progress
Status in “gnome-shell-pomodoro” package in Ubuntu:
  New
Status in “indicator-power” package in Ubuntu:
  Fix Released
Status in “kde-workspace” package in Ubuntu:
  Fix Released
Status in “mate-applets” package in Ubuntu:
  Fix Released
Status in “mate-power-manager” package in Ubuntu:
  Fix Released
Status in “mate-session-manager” package in Ubuntu:
  Fix Released
Status in “mutter” package in Ubuntu:
  In Progress
Status in “powerd” package in Ubuntu:
  New
Status in “python-dbusmock” package in Ubuntu:
  Fix Released
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:
  Fix Released
Status in “tracker” package in Ubuntu:
  Fix Committed
Status in “ubuntu-system-settings” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  New
Status in “upower” package in Ubuntu:
  In Progress
Status in “xfce4-power-manager” package in Ubuntu:
  Fix Committed
Status in “xfce4-session” package in Ubuntu:
  Fix Released
Status in “xfce4-settings” package in Ubuntu:
  In Progress
Status in “xfce4-systemload-plugin” package in Ubuntu:
  Fix Committed
Status in “xfce4-weather-plugin” package in Ubuntu:
  Invalid
Status in “wmbattery” package in Debian:
  Fix Released

Bug description:
  upower 0.99 needs uploading for gnome 3.12 to enter ubuntu. It drops
  the suspend/hibernate functions, as logind now does that. All major
  DEs have support for this,so nearly everything just needs a rebuild.
  This bug tracks the transition.

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

  All packages (and build logs) are staged in
  https://launchpad.net/~noskcaj/+archive/upower/+packages

  sugar 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: Upower dropped from newest upstream release.
  gnome-power-manager: Fixed in newest upstream release. Merge from debian
  gnome-session: Done in ppa, needs patches from git or new upstream release
  gnome-settings-daemon: 3.12 is ready out of the box, however that also 
requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is 
mostly working, however had to cherry-pick quite a few patches and may just be 
better to backport 3.12 power plugin. (considering g-s-d patches will be 
temporary, but u-s-d not so)
  kde: works fine with systemd, suspend broken with upstart, no rebuilds needed
  cinnamon: Rebuild
  mate: all mate packages need rebuilding
  python-dbusmock: needs rebuild
  sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We 
should remove this from the archive till the next upstream release
  telepathy-mission-control-5: Debian has dropped upower support, so it's done
  wmbattery: needs rebuild
  xfce4-power-manager: Needs rebuilding
  xfce4-session: Fixed already, since we switched to logind
  xfce4-settings: Needs rebuild
  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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10

[Tim]

** Changed in: ubuntu-gnome
   Status: Triaged = Invalid

** Changed in: gnome-desktop3 (Ubuntu)
   Status: Confirmed = Invalid

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Triaged = Invalid

** Changed in: unity-control-center (Ubuntu)
   Status: In Progress = Invalid

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

Title:
  [FFe] Implement DisplayConfig dbus interface and transition to gnome-
  desktop 3.10

Status in Ubuntu GNOME:
  Invalid
Status in Unity:
  Invalid
Status in “gnome-desktop3” package in Ubuntu:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid
Status in “unity-control-center” package in Ubuntu:
  Invalid
Status in “unity-settings-daemon” package in Ubuntu:
  In Progress

Bug description:
  Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome-
  control-center 3.10. This however requires a transition to gnome-
  desktop 3-10. I have been working on this for quite some time however
  this work was essentially blocked waiting on the unity- forks for
  settings daemon and control center. These were only finalised the day
  before feature freeze.

  Right now there are quite a few features that are not available for
  configuration in g-c-c given it is so old. We are also hitting some
  odd bugs with mutter using its own display config separate to what
  gnome-settings-daemon is doing with xrandr.

  For GNOME 3.10, all the display configuration/xrandr code has been
  moved into Mutter as dbus interface. The Main reason for this move was
  to abstract away the display server (x11/wayland). Apart from these
  changes there were no significant changes in the API.

  This affects gnome-desktop3 and gnome-settings-daemon. In particular
  the changes in gnome-desktop would create a gigantic mess if we tried
  to revert these changes for Unity only. As such have forked the
  display config code from mutter and ported *-settings-daemon and
  *-control-center to the new api. The code itself is fairly self
  contained, so apart from the resulting duplication of code, it
  shouldnt really be much of an issue.

  We have tested this via a ppa, however it was hard to get extensive
  testing, due to the amount of archive churn in the affected packages.
  I am pretty confident there are no much regressions and I will commit
  to fixing any issues to do appear.

  Essentially this transition will involve:
  new displayconfig package: This is the relevant code forked from mutter 
3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. 
This gets autostarted when required by g/u-s-d (although dbus activation may be 
broken in flashback session)
  my upstream branch is at https://github.com/darkxst/displayconfig (I had 
trouble working out how to import a git branch into bzr, but I imagine it 
should live in bzr once approved)

  gnome/unity-settings-daemon, have backported patches to adapt to the new API.
  Likewise for gnome/unity-control-center.
  All other rdepends just require a no-change rebuild to adapt to the new 
soname.

  Assuming this gets a approved, subsequent FFe's for gnome-settings-
  daemon and gnome-control-center 3.10 will follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10

[Tim]

This was fixed via Bug: 1372240
gnome-desktop transition and FFe now being tracked in Bug: 1372346

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

Title:
  [FFe] Implement DisplayConfig dbus interface and transition to gnome-
  desktop 3.10

Status in Ubuntu GNOME:
  Invalid
Status in Unity:
  Invalid
Status in “gnome-desktop3” package in Ubuntu:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid
Status in “unity-control-center” package in Ubuntu:
  Invalid
Status in “unity-settings-daemon” package in Ubuntu:
  In Progress

Bug description:
  Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome-
  control-center 3.10. This however requires a transition to gnome-
  desktop 3-10. I have been working on this for quite some time however
  this work was essentially blocked waiting on the unity- forks for
  settings daemon and control center. These were only finalised the day
  before feature freeze.

  Right now there are quite a few features that are not available for
  configuration in g-c-c given it is so old. We are also hitting some
  odd bugs with mutter using its own display config separate to what
  gnome-settings-daemon is doing with xrandr.

  For GNOME 3.10, all the display configuration/xrandr code has been
  moved into Mutter as dbus interface. The Main reason for this move was
  to abstract away the display server (x11/wayland). Apart from these
  changes there were no significant changes in the API.

  This affects gnome-desktop3 and gnome-settings-daemon. In particular
  the changes in gnome-desktop would create a gigantic mess if we tried
  to revert these changes for Unity only. As such have forked the
  display config code from mutter and ported *-settings-daemon and
  *-control-center to the new api. The code itself is fairly self
  contained, so apart from the resulting duplication of code, it
  shouldnt really be much of an issue.

  We have tested this via a ppa, however it was hard to get extensive
  testing, due to the amount of archive churn in the affected packages.
  I am pretty confident there are no much regressions and I will commit
  to fixing any issues to do appear.

  Essentially this transition will involve:
  new displayconfig package: This is the relevant code forked from mutter 
3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. 
This gets autostarted when required by g/u-s-d (although dbus activation may be 
broken in flashback session)
  my upstream branch is at https://github.com/darkxst/displayconfig (I had 
trouble working out how to import a git branch into bzr, but I imagine it 
should live in bzr once approved)

  gnome/unity-settings-daemon, have backported patches to adapt to the new API.
  Likewise for gnome/unity-control-center.
  All other rdepends just require a no-change rebuild to adapt to the new 
soname.

  Assuming this gets a approved, subsequent FFe's for gnome-settings-
  daemon and gnome-control-center 3.10 will follow.

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

[Tim]

gnome-applets does build the battstat applet now that we are in sync
with debian, but is already ready. Just needs a rebuild

** Changed in: gnome-applets (Ubuntu)
   Status: Invalid = In Progress

-- 
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 Released
Status in “cinnamon-control-center” package in Ubuntu:
  New
Status in “cinnamon-session” package in Ubuntu:
  New
Status in “cinnamon-settings-daemon” package in Ubuntu:
  New
Status in “gnome-applets” package in Ubuntu:
  In Progress
Status in “gnome-control-center” package in Ubuntu:
  In Progress
Status in “gnome-packagekit” package in Ubuntu:
  Fix Released
Status in “gnome-power-manager” package in Ubuntu:
  In Progress
Status in “gnome-session” package in Ubuntu:
  In Progress
Status in “gnome-settings-daemon” package in Ubuntu:
  In Progress
Status in “gnome-shell” package in Ubuntu:
  In Progress
Status in “gnome-shell-pomodoro” package in Ubuntu:
  New
Status in “indicator-power” package in Ubuntu:
  Fix Released
Status in “kde-workspace” package in Ubuntu:
  Fix Released
Status in “mate-applets” package in Ubuntu:
  Fix Released
Status in “mate-power-manager” package in Ubuntu:
  Fix Released
Status in “mate-session-manager” package in Ubuntu:
  Fix Released
Status in “mutter” package in Ubuntu:
  In Progress
Status in “powerd” package in Ubuntu:
  New
Status in “python-dbusmock” package in Ubuntu:
  Fix Released
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:
  Fix Released
Status in “tracker” package in Ubuntu:
  Fix Committed
Status in “ubuntu-system-settings” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  New
Status in “upower” package in Ubuntu:
  In Progress
Status in “xfce4-power-manager” package in Ubuntu:
  Fix Committed
Status in “xfce4-session” package in Ubuntu:
  Fix Released
Status in “xfce4-settings” package in Ubuntu:
  In Progress
Status in “xfce4-systemload-plugin” package in Ubuntu:
  Fix Committed
Status in “xfce4-weather-plugin” package in Ubuntu:
  Invalid
Status in “wmbattery” package in Debian:
  Fix Released

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 and sugar 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-applets - patch at bgo:730588
  gnome-shell - ready, just need to drop upower revert.
  gnome-control-center: WIP
  gnome-packagekit: Upower dropped from newest upstream release. Merge from 
debian
  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: 3.12 is ready out of the box, however that also 
requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is 
mostly working, however had to cherry-pick quite a few patches and may just be 
better to backport 3.12 power plugin. (considering g-s-d patches will be 
temporary, but u-s-d not so)
  kde: works fine with systemd, suspend broken with upstart
  mate: all mate packages need rebuilding
  python-dbusmock: lp:1324791
  sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We 
should remove this from the archive till the next upstream release
  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 upstream. Merge at lp:1334185. Will need rebuilding
  xfce4-session: patch is upstream, needs work to apply with our current 
patchset
  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

[Tim]

Charles, are you planning on porting indicator-power? I think this is
really the last thing blocking this transition

-- 
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-applets” package in Ubuntu:
  Invalid
Status in “gnome-control-center” package in Ubuntu:
  In Progress
Status in “gnome-packagekit” package in Ubuntu:
  Fix Released
Status in “gnome-power-manager” package in Ubuntu:
  In Progress
Status in “gnome-session” package in Ubuntu:
  In Progress
Status in “gnome-settings-daemon” package in Ubuntu:
  In Progress
Status in “gnome-shell” package in Ubuntu:
  In Progress
Status in “indicator-power” package in Ubuntu:
  Triaged
Status in “kde-workspace” package in Ubuntu:
  Fix Released
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:
  In Progress
Status in “powerd” package in Ubuntu:
  New
Status in “python-dbusmock” package in Ubuntu:
  Fix Released
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:
  Fix Released
Status in “tracker” package in Ubuntu:
  Fix Committed
Status in “ubuntu-system-settings” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  New
Status in “upower” package in Ubuntu:
  In Progress
Status in “xfce4-power-manager” package in Ubuntu:
  Fix Committed
Status in “xfce4-session” package in Ubuntu:
  Fix Released
Status in “xfce4-settings” package in Ubuntu:
  In Progress
Status in “xfce4-systemload-plugin” package in Ubuntu:
  Fix Committed
Status in “wmbattery” package in Debian:
  Fix Released

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 and sugar 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-applets - patch at bgo:730588
  gnome-shell - ready, just need to drop upower revert.
  gnome-control-center: WIP
  gnome-packagekit: Upower dropped from newest upstream release. Merge from 
debian
  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: 3.12 is ready out of the box, however that also 
requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is 
mostly working, however had to cherry-pick quite a few patches and may just be 
better to backport 3.12 power plugin. (considering g-s-d patches will be 
temporary, but u-s-d not so)
  kde: works fine with systemd, suspend broken with upstart
  mate: all mate packages need rebuilding
  python-dbusmock: lp:1324791
  sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We 
should remove this from the archive till the next upstream release
  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 upstream. Merge at lp:1334185. Will need rebuilding
  xfce4-session: patch is upstream, needs work to apply with our current 
patchset
  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

[Tim]

** Branch linked: lp:~darkxst/ubuntu/utopic/powerd/lp1330037

-- 
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-applets” package in Ubuntu:
  Invalid
Status in “gnome-control-center” package in Ubuntu:
  In Progress
Status in “gnome-packagekit” package in Ubuntu:
  Fix Released
Status in “gnome-power-manager” package in Ubuntu:
  In Progress
Status in “gnome-session” package in Ubuntu:
  In Progress
Status in “gnome-settings-daemon” package in Ubuntu:
  In Progress
Status in “gnome-shell” package in Ubuntu:
  In Progress
Status in “indicator-power” package in Ubuntu:
  Triaged
Status in “kde-workspace” package in Ubuntu:
  Fix Released
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:
  In Progress
Status in “powerd” package in Ubuntu:
  New
Status in “python-dbusmock” package in Ubuntu:
  Fix Released
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:
  Fix Released
Status in “tracker” package in Ubuntu:
  Fix Committed
Status in “ubuntu-system-settings” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  New
Status in “upower” package in Ubuntu:
  In Progress
Status in “xfce4-power-manager” package in Ubuntu:
  Fix Committed
Status in “xfce4-session” package in Ubuntu:
  Fix Released
Status in “xfce4-settings” package in Ubuntu:
  In Progress
Status in “xfce4-systemload-plugin” package in Ubuntu:
  Fix Committed
Status in “wmbattery” package in Debian:
  Fix Released

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 and sugar 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-applets - patch at bgo:730588
  gnome-shell - ready, just need to drop upower revert.
  gnome-control-center: WIP
  gnome-packagekit: Upower dropped from newest upstream release. Merge from 
debian
  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: 3.12 is ready out of the box, however that also 
requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is 
mostly working, however had to cherry-pick quite a few patches and may just be 
better to backport 3.12 power plugin. (considering g-s-d patches will be 
temporary, but u-s-d not so)
  kde: works fine with systemd, suspend broken with upstart
  mate: all mate packages need rebuilding
  python-dbusmock: lp:1324791
  sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We 
should remove this from the archive till the next upstream release
  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 upstream. Merge at lp:1334185. Will need rebuilding
  xfce4-session: patch is upstream, needs work to apply with our current 
patchset
  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 1351815] Re: StartTransientUnit signature has changed in systemd 214

[Tim]

Yes it can wait until 214 is ready to land, not sure its worth
supporting both API's

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

Title:
  StartTransientUnit signature has changed in systemd 214

Status in “systemd-shim” package in Ubuntu:
  Triaged

Bug description:
  This will be required when systemd gets updated to 214

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd-shim 6-4bzr1
  ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
  Uname: Linux 3.16.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.5-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug  3 14:05:50 2014
  InstallationDate: Installed on 2012-09-23 (679 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha 
amd64(20120922)
  SourcePackage: systemd-shim
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1351815/+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 1351815] [NEW] StartTransientUnit signature has changed in systemd 214

[Tim]

Public bug reported:

This will be required when systemd gets updated to 214

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: systemd-shim 6-4bzr1
ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
Uname: Linux 3.16.0-5-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.5-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Aug  3 14:05:50 2014
InstallationDate: Installed on 2012-09-23 (679 days ago)
InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha 
amd64(20120922)
SourcePackage: systemd-shim
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: systemd-shim (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug utopic

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

Title:
  StartTransientUnit signature has changed in systemd 214

Status in “systemd-shim” package in Ubuntu:
  New

Bug description:
  This will be required when systemd gets updated to 214

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd-shim 6-4bzr1
  ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
  Uname: Linux 3.16.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.5-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug  3 14:05:50 2014
  InstallationDate: Installed on 2012-09-23 (679 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha 
amd64(20120922)
  SourcePackage: systemd-shim
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1351815/+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 1351815] Re: StartTransientUnit signature has changed in systemd 214

[Tim]

** Patch added: StartTransientUnit.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1351815/+attachment/4168494/+files/StartTransientUnit.debdiff

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

Title:
  StartTransientUnit signature has changed in systemd 214

Status in “systemd-shim” package in Ubuntu:
  New

Bug description:
  This will be required when systemd gets updated to 214

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd-shim 6-4bzr1
  ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
  Uname: Linux 3.16.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.5-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug  3 14:05:50 2014
  InstallationDate: Installed on 2012-09-23 (679 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha 
amd64(20120922)
  SourcePackage: systemd-shim
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1351815/+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 1348039] Re: shim does not implement 'Subscribe' method called by logind

[Tim]

This error is now fatal in systemd214.

https://bitbucket.org/unit193/systemd/commits/c2310b408fc0cbdccb2253d6e3c2f8bd3f6490e9

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

Title:
  shim does not implement 'Subscribe' method called by logind

Status in “systemd-shim” package in Ubuntu:
  Triaged

Bug description:
  Get that error logged at the end of the dmesg file. That error seems
  to have no sad effect on the system:

  [   30.793181] systemd-logind[1006]: Failed to enable subscription: No
  such method 'Subscribe'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-6ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
  Uname: Linux 3.16.0-4-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Jul 24 07:25:46 2014
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1348039/+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 1243174] Re: updated to Ubuntu 13.10 'Power off warning' does go not turn off

[Tim]

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

** This bug is no longer a duplicate of bug 1232454
   Computer will suspend very soon because of inactivity. dialog when 
resuming from suspend
** This bug has been marked a duplicate of bug 1345116
   Computer fails to autosuspend

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

Title:
  updated to Ubuntu 13.10 'Power off warning' does go not turn off

Status in “indicator-power” package in Ubuntu:
  Incomplete

Bug description:
  The power off warning indicator comes on automatically but does not turn off. 
This is a new something. is there a way to shut it down?
  Thanks Cliff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1243174/+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 1304434] Re: indicator-printers not working on Ubuntu 14.04

[Tim Passingham]

Fixed for me now.

Indicator-printers still 0.1.7+14.04.20140527-0ubuntu1

New Kernel 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  indicator-printers not working on Ubuntu 14.04

Status in Print Indicator:
  In Progress
Status in “indicator-printers” package in Ubuntu:
  Fix Released
Status in “indicator-printers” source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  The panel should have a print indicator as long as there are any print jobs 
queued or processed. Currently, this indicator never appears, even though 
printing works fine.

  This is because the service that listens to CUPS fails to register its
  D-Bus name (as of revision 68), which results in the panel component
  not finding the service. The attached branch fixes this by making the
  service register the name the panel expects.

  [Test Case]
  Print a document from any application and check whether the print indicator 
appears while it is printing.

  [Regression Potential]
  Almost none. The print indicator is not working at all right now, and the fix 
only touches that indicator.

  [Original Description]
  even after lates updates still no printer notifications in the panel . I 
checked and the package indicator-printers is correctly installed and the 
printer prints without problems. But, there is no notification icons on unity 
panel. I had no problems at all with 13.10 instead

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-printers/+bug/1304434/+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 1304434] Re: indicator-printers not working on Ubuntu 14.04

[Tim Passingham]

I still have this problem on 14.04, and have recently wasted quite a bit
of ink  paper as a result.

I am not using a 'proposed' repository.  The installed version is
'0.1.7+14.04.20140527-0ubuntu1'

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

Title:
  indicator-printers not working on Ubuntu 14.04

Status in Print Indicator:
  In Progress
Status in “indicator-printers” package in Ubuntu:
  Fix Released
Status in “indicator-printers” source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  The panel should have a print indicator as long as there are any print jobs 
queued or processed. Currently, this indicator never appears, even though 
printing works fine.

  This is because the service that listens to CUPS fails to register its
  D-Bus name (as of revision 68), which results in the panel component
  not finding the service. The attached branch fixes this by making the
  service register the name the panel expects.

  [Test Case]
  Print a document from any application and check whether the print indicator 
appears while it is printing.

  [Regression Potential]
  Almost none. The print indicator is not working at all right now, and the fix 
only touches that indicator.

  [Original Description]
  even after lates updates still no printer notifications in the panel . I 
checked and the package indicator-printers is correctly installed and the 
printer prints without problems. But, there is no notification icons on unity 
panel. I had no problems at all with 13.10 instead

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-printers/+bug/1304434/+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 773078] Re: Should display the StickyKeys status in some way (a11y)

[Tim Jones]

Original bug report: “Reported by truant on 2011-04-29”
Ubuntu 11.10 Oneiric Ocelot release date: 2011-10-13
Ubuntu 12.04 LTS Precise Pangolin release date: 2012-04-26
Ubuntu 12.10 Quantal Quetzal release date: 2012-10-18
Ubuntu 13.04 Raring Ringtail release date: 2013-04-25
Ubuntu 13.10 Saucy Salamander release date: 2013-10-17
Ubuntu 14.04 LTS Trusty Tahr release date: 2014-04-17
Today's date: 2014-06-28 

I am astonished to discover that this “bug report” has been languishing here 
unaddressed for three years and two months. So despite... 
• the very valid comments about the crippled usability of Sticky Keys without a 
modifier key status indicator, from multiple end users (which I fully endorse – 
there are times when only logging out and logging in again will rectify an 
unknown and non-viable modifier key latched/locked combination);
• “First-class accessibility for those with special interaction needs” being a 
publicly stated aim for Ubuntu 12.04 LTS Precise Pangolin since at least 
2011-10-20; [1]
• SIX missed opportunities to address this critical accessibility problem 
between Ubuntu 11.10 Oneiric Ocelot and Ubuntu 14.04 LTS Trusty Tahr
...it seems that Canonical either have a worse than useless bug-tracking system 
(less likely) or assign the needs of people with disabilities a rock bottom 
priority (more likely, but depressingly disappointing).

I've been using Sticky Keys on Apple Mac OS X for a decade, and
occasionally on Micro$oft Windoze, and on both OS's the modifier key
status indicators are a crucial component in making Sticky Keys work for
unidextrous typing and computer control. The OS X technique of 'sound on
modifier key-press' plus 'user-positionable translucent modifier key
icon overlays' to show the current latched/locked modifier key
combination is far more user friendly than the tiny panel icon in
Windoze. Yet a 'one icon per modifier key' panel applet for Ubuntu,
integrated into the System Settings  Universal Access  Typing 
Sticky Keys, ought to be relatively easy to implement; indeed one end
user has coded a 'one icon per modifier key' panel applet, and although
it doesn't work on the Gnome Flashback environment I'm using, it does
show what's needed:

pic: » http://i.stack.imgur.com/TnURl.png 
caption: Image starting from left: Icon, Shift, Locked Caps, Ctrl, Alt, Super, 
Locked AltGr (Small circle to indicate locked state)
source: » 
http://askubuntu.com/questions/402315/how-to-add-a-keyboard-modifier-state-applet-to-unity-panel
  

As an Ubuntu noob, I'm unfamiliar with how best to get Canonical's
attention drawn to fixing this problem. If more experienced Ubuntu
community members can suggest ways in which to get this long-overdue
error corrected, those of us who need a fully functional Sticky Keys
implementation would be most grateful.


[1] “First-class accessibility for those with special interaction needs” being 
a publicly stated aim for Ubuntu 12.04 LTS Precise Pangolin since at least 
2011-10-20 – see 'Precision Planning; Prepping for 12.04 LTS' by Mark 
Shuttleworth » http://www.markshuttleworth.com/archives/810

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

Title:
  Should display the StickyKeys status in some way (a11y)

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

Bug description:
  Binary package hint: indicator-application

  Following an upgrade to Natty, I can no longer determine what state my
  stickykeys are in.  No special steps are needed to reproduce this
  issue, just being in a Unity session.

  Previously this information was provided by the gnome-panel-applet
  called AccessX Status which displayed a row of icons which would
  show either latched or locked for each modifier key. In GNOME 2.x, I
  would right click a panel, select Add to Panel and choose Keyboard
  Accessibility Status

  This would give me a line of 6 square icons representing Alt, Ctrl,
  Super etc. These icons change state depending on which keys are being
  (temporarily or permanently) locked by stickykeys.

  While stickykeys seems to work - in that keys are latched/locked as
  one would expect - the lack of information about their state renders
  the feature considerably less usable.  For some users, myself
  included, this is a critical a11y failure and requires using the GNOME
  2.x environment instead of Unity.

  This is now the third time I've reported this bug/problem, hopefully
  I've got it in the right place this time!  Apologies if not, and
  please do let me know where I should be reporting this if not here.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: indicator-application 0.3.2-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  Date: Fri Apr 29 10:28:52 2011
  ExecutablePath: 

[Dx-packages] [Bug 1276177] Re: Applications using client-side decorations are not resizable in Unity

[Tim]

** Tags added: ubuntugnome-blocker

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

Title:
  Applications using client-side decorations are not resizable in Unity

Status in Unity:
  New
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  GNOME applications that use client-side decorations can't be resized
  on Unity. I think it's because the frame extents hint is not
  supported.

  gnome-clocks and gnome-tweak-tool are two apps in the archive that
  have this problem.

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

[Tim]

** Tags added: ubuntugnome-blocker

-- 
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-applets” package in Ubuntu:
  New
Status in “gnome-control-center” package in Ubuntu:
  New
Status in “gnome-packagekit” package in Ubuntu:
  Fix Released
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 “kde4libs” 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-applets - patch at bgo:730588
  gnome-shell - ready, just need to drop upower revert.
  gnome-control-center: WIP
  gnome-packagekit: Upower dropped from newest upstream release. Merge from 
debian
  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: 3.12 is ready out of the box, however that also 
requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is 
mostly working, however had to cherry-pick quite a few patches and may just be 
better to backport 3.12 power plugin. (considering g-s-d patches will be 
temporary, but u-s-d not so)
  kde: needs sc 4.13.3 
(http://quickgit.kde.org/?p=kdelibs.gita=commith=44afff90921b8b27d40e810684715d16278b335f)
  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 upstream. Merge at lp:1334185. Will need rebuilding
  xfce4-session: patch is upstream, needs work to apply with our current 
patchset
  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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10

[Tim]

** Tags added: ubuntugnome-blocker

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

Title:
  [FFe] Implement DisplayConfig dbus interface and transition to gnome-
  desktop 3.10

Status in Ubuntu GNOME:
  Triaged
Status in Unity:
  Invalid
Status in Unity Settings Daemon:
  In Progress
Status in “gnome-desktop3” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  In Progress
Status in “unity-settings-daemon” package in Ubuntu:
  New

Bug description:
  Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome-
  control-center 3.10. This however requires a transition to gnome-
  desktop 3-10. I have been working on this for quite some time however
  this work was essentially blocked waiting on the unity- forks for
  settings daemon and control center. These were only finalised the day
  before feature freeze.

  Right now there are quite a few features that are not available for
  configuration in g-c-c given it is so old. We are also hitting some
  odd bugs with mutter using its own display config separate to what
  gnome-settings-daemon is doing with xrandr.

  For GNOME 3.10, all the display configuration/xrandr code has been
  moved into Mutter as dbus interface. The Main reason for this move was
  to abstract away the display server (x11/wayland). Apart from these
  changes there were no significant changes in the API.

  This affects gnome-desktop3 and gnome-settings-daemon. In particular
  the changes in gnome-desktop would create a gigantic mess if we tried
  to revert these changes for Unity only. As such have forked the
  display config code from mutter and ported *-settings-daemon and
  *-control-center to the new api. The code itself is fairly self
  contained, so apart from the resulting duplication of code, it
  shouldnt really be much of an issue.

  We have tested this via a ppa, however it was hard to get extensive
  testing, due to the amount of archive churn in the affected packages.
  I am pretty confident there are no much regressions and I will commit
  to fixing any issues to do appear.

  Essentially this transition will involve:
  new displayconfig package: This is the relevant code forked from mutter 
3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. 
This gets autostarted when required by g/u-s-d (although dbus activation may be 
broken in flashback session)
  my upstream branch is at https://github.com/darkxst/displayconfig (I had 
trouble working out how to import a git branch into bzr, but I imagine it 
should live in bzr once approved)

  gnome/unity-settings-daemon, have backported patches to adapt to the new API.
  Likewise for gnome/unity-control-center.
  All other rdepends just require a no-change rebuild to adapt to the new 
soname.

  Assuming this gets a approved, subsequent FFe's for gnome-settings-
  daemon and gnome-control-center 3.10 will follow.

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

[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-applets - patch at bgo:#276997
+ gnome-applets - patch at bgo:730588
  gnome-shell - ready, just need to drop upower revert.
  gnome-control-center: WIP
  gnome-packagekit: Upower dropped from newest upstream release. Merge from 
debian
  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: 3.12 is ready out of the box, however that also 
requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is 
mostly working, however had to cherry-pick quite a few patches and may just be 
better to backport 3.12 power plugin. (considering g-s-d patches will be 
temporary, but u-s-d not so)
  kde: needs sc 4.13.3 
(http://quickgit.kde.org/?p=kdelibs.gita=commith=44afff90921b8b27d40e810684715d16278b335f)
  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 upstream. Merge at lp:1334185. Will need rebuilding
  xfce4-session: patch is upstream, needs work to apply with our current 
patchset
  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-applets” package in Ubuntu:
  New
Status in “gnome-control-center” package in Ubuntu:
  New
Status in “gnome-packagekit” package in Ubuntu:
  Fix Committed
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 “kde4libs” 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-applets - patch at bgo:730588
  gnome-shell - ready, just need to drop upower revert.
  gnome-control-center: WIP
  gnome-packagekit: Upower dropped from newest upstream release. Merge from 
debian
  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: 3.12 is ready out of the box, however that also 
requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is 
mostly working, however had to cherry-pick quite a few patches and may just be 
better to backport 3.12 power plugin. (considering g-s-d patches will be 
temporary, but u-s-d not so)
  kde: needs sc 4.13.3 
(http://quickgit.kde.org/?p=kdelibs.gita=commith=44afff90921b8b27d40e810684715d16278b335f)
  mate: all mate packages need rebuilding
  

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

[Tim]

** Also affects: gnome-applets (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 “cairo-dock-plug-ins” package in Ubuntu:
  Fix Committed
Status in “gnome-applets” package in Ubuntu:
  New
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 “kde-workspace” 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-applets - patch at bgo:#276997
  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: 3.12 is ready out of the box, however that also 
requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is 
mostly working, however had to cherry-pick quite a few patches and may just be 
better to backport 3.12 power plugin. (considering g-s-d patches will be 
temporary, but u-s-d not so)
  kde: suspend issues, device notifier broken
  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 work to apply with our current 
patchset
  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

[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

[Dx-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen

[Tim Ogilvy]

This appears to be closed, but I'm all up to date, and having this
problem still.  What's the story?

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

Title:
  Lockscreen doesn't turn off the screen

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in Unity:
  Fix Committed
Status in “gnome-screensaver” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  The new Unity lock screen doesn't turn off the monitor screen.

  I can wait as long as 10 minutes after activating the lock screen and
  the monitor still doesn't trun off. Then when I unlock the screen and
  don't use mouse or keyboard monitor will turn off (it's about 5
  seconds after unlocking).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1292041/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10

[Tim]

** Changed in: ubuntu-gnome
Milestone: trusty = utopic

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

Title:
  [FFe] Implement DisplayConfig dbus interface and transition to gnome-
  desktop 3.10

Status in Ubuntu GNOME:
  Triaged
Status in Unity:
  Invalid
Status in Unity Settings Daemon:
  In Progress
Status in “gnome-desktop3” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  In Progress
Status in “unity-settings-daemon” package in Ubuntu:
  New

Bug description:
  Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome-
  control-center 3.10. This however requires a transition to gnome-
  desktop 3-10. I have been working on this for quite some time however
  this work was essentially blocked waiting on the unity- forks for
  settings daemon and control center. These were only finalised the day
  before feature freeze.

  Right now there are quite a few features that are not available for
  configuration in g-c-c given it is so old. We are also hitting some
  odd bugs with mutter using its own display config separate to what
  gnome-settings-daemon is doing with xrandr.

  For GNOME 3.10, all the display configuration/xrandr code has been
  moved into Mutter as dbus interface. The Main reason for this move was
  to abstract away the display server (x11/wayland). Apart from these
  changes there were no significant changes in the API.

  This affects gnome-desktop3 and gnome-settings-daemon. In particular
  the changes in gnome-desktop would create a gigantic mess if we tried
  to revert these changes for Unity only. As such have forked the
  display config code from mutter and ported *-settings-daemon and
  *-control-center to the new api. The code itself is fairly self
  contained, so apart from the resulting duplication of code, it
  shouldnt really be much of an issue.

  We have tested this via a ppa, however it was hard to get extensive
  testing, due to the amount of archive churn in the affected packages.
  I am pretty confident there are no much regressions and I will commit
  to fixing any issues to do appear.

  Essentially this transition will involve:
  new displayconfig package: This is the relevant code forked from mutter 
3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. 
This gets autostarted when required by g/u-s-d (although dbus activation may be 
broken in flashback session)
  my upstream branch is at https://github.com/darkxst/displayconfig (I had 
trouble working out how to import a git branch into bzr, but I imagine it 
should live in bzr once approved)

  gnome/unity-settings-daemon, have backported patches to adapt to the new API.
  Likewise for gnome/unity-control-center.
  All other rdepends just require a no-change rebuild to adapt to the new 
soname.

  Assuming this gets a approved, subsequent FFe's for gnome-settings-
  daemon and gnome-control-center 3.10 will follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1310518] [NEW] Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen

[Tim Chen]

Public bug reported:


Touch screen and touchpad lost click function after quickly tapped dash
home repeatly by touch screen, Installed 14.04, still have same issue.

Quickly tapped dash home more than three times by touch screen.Found
touch screen and touchpad lost click function.

Note:
1.When this issue occured, cursor still can be moved by touch screen/touchpad.
2.When this issue occured ,click/double click by touch screen/touchpad,left 
click/right click by touchpad all were not workable.

Steps to Reproduce:
1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS.
2.Quickly tapped dash home more than three times by touch screen.
3.Found touch screen and touchpad lost click function.

This bug is reported from private OEM project, also check
https://launchpad.net/bugs/1297067

==

using xinput --query-state can actually see the button press event

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ syntp id=6  [slave pointer (2)]
⎜ ↳ ELAN Touchscreen id=11  [slave pointer (2)]

#xinput --query-state 11
2 classes :
ButtonClass
 button[1]=up
 button[2]=up
 button[3]=up
 button[4]=up
 button[5]=up
ValuatorClass Mode=Absolute Proximity=In
 valuator[0]=398
 valuator[1]=1652
 valuator[2]=5
 valuator[3]=3
 valuator[4]=0
 valuator[5]=399
 valuator[6]=1653

#xinput --query-state 6
2 classes :
ButtonClass
 button[1]=down
 button[2]=up
 button[3]=up
 button[4]=up
 button[5]=up
 button[6]=up
 button[7]=up
 button[8]=up
ValuatorClass Mode=Relative Proximity=In
 valuator[0]=1
 valuator[1]=394

touchpad's button and touchpanel's
valuator[2] and valuator[3] will changed after we press the button (or monitor)

Also I found press super on keyboard will recover the
touchscreen/touchpad loss.


ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.20.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
Date: Mon Apr 21 16:50:04 2014
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-stella-daan2-precise-amd64-20140416-1
InstallationMedia: Ubuntu 12.04 Precise - Failed to find casper uuid.conf in 
'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 20140416-06:52
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_US:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug precise running-unity

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

Title:
  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen

Status in “unity” package in Ubuntu:
  New

Bug description:

  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen, Installed 14.04, still have same
  issue.

  Quickly tapped dash home more than three times by touch screen.Found
  touch screen and touchpad lost click function.

  Note:
  1.When this issue occured, cursor still can be moved by touch screen/touchpad.
  2.When this issue occured ,click/double click by touch screen/touchpad,left 
click/right click by touchpad all were not workable.

  Steps to Reproduce:
  1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS.
  2.Quickly tapped dash home more than three times by touch screen.
  3.Found touch screen and touchpad lost click function.

  This bug is reported from private OEM project, also check
  https://launchpad.net/bugs/1297067

  ==

  using xinput --query-state can actually see the button press event

  ⎡ Virtual core pointer id=2   [master pointer (3)]
  ⎜ ↳ Virtual core XTEST pointer id=4   [slave pointer (2)]
  ⎜ ↳ syntp id=6[slave pointer (2)]
  ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)]

  #xinput --query-state 11
  2 classes :
  ButtonClass
   button[1]=up
   button[2]=up
   button[3]=up
   button[4]=up
   button[5]=up
  ValuatorClass Mode=Absolute Proximity=In
   valuator[0]=398
   valuator[1]=1652
   valuator[2]=5
   valuator[3]=3
   valuator[4]=0
   valuator[5]=399
   valuator[6]=1653

  #xinput --query-state 6
  2 classes :
  ButtonClass
   button[1]=down
   button[2]=up
   button[3]=up
   button[4]=up
   button[5]=up
   button[6]=up
   button[7]=up
   button[8]=up
  ValuatorClass Mode=Relative Proximity=In
   valuator[0]=1

[Dx-packages] [Bug 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen

[Tim Chen]

** Description changed:

+ 
  Touch screen and touchpad lost click function after quickly tapped dash
- home repeatly by touch screen
+ home repeatly by touch screen, Installed 14.04, still have same issue.
+ 
+ Quickly tapped dash home more than three times by touch screen.Found
+ touch screen and touchpad lost click function.
+ 
+ Note:
+ 1.When this issue occured, cursor still can be moved by touch screen/touchpad.
+ 2.When this issue occured ,click/double click by touch screen/touchpad,left 
click/right click by touchpad all were not workable.
+ 
+ Steps to Reproduce:
+ 1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS.
+ 2.Quickly tapped dash home more than three times by touch screen.
+ 3.Found touch screen and touchpad lost click function.
+ 
+ This bug is reported from private OEM project, also check
+ https://launchpad.net/bugs/1297067
+ 
+ ==
+ 
+ using xinput --query-state can actually see the button press event
+ 
+ ⎡ Virtual core pointer id=2   [master pointer (3)]
+ ⎜ ↳ Virtual core XTEST pointer id=4   [slave pointer (2)]
+ ⎜ ↳ syntp id=6[slave pointer (2)]
+ ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)]
+ 
+ #xinput --query-state 11
+ 2 classes :
+ ButtonClass
+  button[1]=up
+  button[2]=up
+  button[3]=up
+  button[4]=up
+  button[5]=up
+ ValuatorClass Mode=Absolute Proximity=In
+  valuator[0]=398
+  valuator[1]=1652
+  valuator[2]=5
+  valuator[3]=3
+  valuator[4]=0
+  valuator[5]=399
+  valuator[6]=1653
+ 
+ #xinput --query-state 6
+ 2 classes :
+ ButtonClass
+  button[1]=down
+  button[2]=up
+  button[3]=up
+  button[4]=up
+  button[5]=up
+  button[6]=up
+  button[7]=up
+  button[8]=up
+ ValuatorClass Mode=Relative Proximity=In
+  valuator[0]=1
+  valuator[1]=394
+ 
+ touchpad's button and touchpanel's
+ valuator[2] and valuator[3] will changed after we press the button (or 
monitor)
+ 
+ Also I found press super on keyboard will recover the
+ touchscreen/touchpad loss.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.20.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Apr 21 16:50:04 2014
  DistributionChannelDescriptor:
-  # This is a distribution channel descriptor
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-stella-daan2-precise-amd64-20140416-1
+  # This is a distribution channel descriptor
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-stella-daan2-precise-amd64-20140416-1
  InstallationMedia: Ubuntu 12.04 Precise - Failed to find casper uuid.conf 
in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 
20140416-06:52
  MarkForUpload: True
  ProcEnviron:
-  LANGUAGE=en_US:
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US:
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen

Status in OEM Priority Project:
  New
Status in OEM Priority Project precise series:
  New
Status in OEM Priority Project trusty series:
  New
Status in “unity” package in Ubuntu:
  New

Bug description:

  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen, Installed 14.04, still have same
  issue.

  Quickly tapped dash home more than three times by touch screen.Found
  touch screen and touchpad lost click function.

  Note:
  1.When this issue occured, cursor still can be moved by touch screen/touchpad.
  2.When this issue occured ,click/double click by touch screen/touchpad,left 
click/right click by touchpad all were not workable.

  Steps to Reproduce:
  1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS.
  2.Quickly tapped dash home more than three times by touch screen.
  3.Found touch screen and touchpad lost click function.

  This bug is reported from private OEM project, also check
  https://launchpad.net/bugs/1297067

  ==

  using xinput --query-state can actually see the button press event

  ⎡ Virtual core pointer id=2   [master pointer (3)]
  ⎜ ↳ Virtual core XTEST pointer id=4   [slave pointer (2)]
  ⎜ ↳ syntp id=6[slave pointer (2)]
  ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)]

  #xinput --query-state 11
  2 

[Dx-packages] [Bug 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen

[Tim Chen]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Also affects: oem-priority/precise
   Importance: Undecided
   Status: New

** Also affects: oem-priority/trusty
   Importance: Undecided
   Status: New

** Changed in: oem-priority/precise
   Importance: Undecided = High

** Changed in: oem-priority/trusty
   Importance: Undecided = High

** Changed in: oem-priority
   Importance: Undecided = High

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

Title:
  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen

Status in OEM Priority Project:
  New
Status in OEM Priority Project precise series:
  New
Status in OEM Priority Project trusty series:
  New
Status in “unity” package in Ubuntu:
  New

Bug description:

  Touch screen and touchpad lost click function after quickly tapped
  dash home repeatly by touch screen, Installed 14.04, still have same
  issue.

  Quickly tapped dash home more than three times by touch screen.Found
  touch screen and touchpad lost click function.

  Note:
  1.When this issue occured, cursor still can be moved by touch screen/touchpad.
  2.When this issue occured ,click/double click by touch screen/touchpad,left 
click/right click by touchpad all were not workable.

  Steps to Reproduce:
  1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS.
  2.Quickly tapped dash home more than three times by touch screen.
  3.Found touch screen and touchpad lost click function.

  This bug is reported from private OEM project, also check
  https://launchpad.net/bugs/1297067

  ==

  using xinput --query-state can actually see the button press event

  ⎡ Virtual core pointer id=2   [master pointer (3)]
  ⎜ ↳ Virtual core XTEST pointer id=4   [slave pointer (2)]
  ⎜ ↳ syntp id=6[slave pointer (2)]
  ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)]

  #xinput --query-state 11
  2 classes :
  ButtonClass
   button[1]=up
   button[2]=up
   button[3]=up
   button[4]=up
   button[5]=up
  ValuatorClass Mode=Absolute Proximity=In
   valuator[0]=398
   valuator[1]=1652
   valuator[2]=5
   valuator[3]=3
   valuator[4]=0
   valuator[5]=399
   valuator[6]=1653

  #xinput --query-state 6
  2 classes :
  ButtonClass
   button[1]=down
   button[2]=up
   button[3]=up
   button[4]=up
   button[5]=up
   button[6]=up
   button[7]=up
   button[8]=up
  ValuatorClass Mode=Relative Proximity=In
   valuator[0]=1
   valuator[1]=394

  touchpad's button and touchpanel's
  valuator[2] and valuator[3] will changed after we press the button (or 
monitor)

  Also I found press super on keyboard will recover the
  touchscreen/touchpad loss.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.20.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Apr 21 16:50:04 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-daan2-precise-amd64-20140416-1
  InstallationMedia: Ubuntu 12.04 Precise - Failed to find casper uuid.conf 
in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 
20140416-06:52
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   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/oem-priority/+bug/1310518/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10

[Tim]

Jackson, Thanks, but please attach a debdiff, I can't review that right
now with internet issues

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

Title:
  [FFe] Implement DisplayConfig dbus interface and transition to gnome-
  desktop 3.10

Status in Ubuntu GNOME:
  Triaged
Status in Unity:
  Invalid
Status in Unity Settings Daemon:
  In Progress
Status in “gnome-desktop3” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  In Progress

Bug description:
  Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome-
  control-center 3.10. This however requires a transition to gnome-
  desktop 3-10. I have been working on this for quite some time however
  this work was essentially blocked waiting on the unity- forks for
  settings daemon and control center. These were only finalised the day
  before feature freeze.

  Right now there are quite a few features that are not available for
  configuration in g-c-c given it is so old. We are also hitting some
  odd bugs with mutter using its own display config separate to what
  gnome-settings-daemon is doing with xrandr.

  For GNOME 3.10, all the display configuration/xrandr code has been
  moved into Mutter as dbus interface. The Main reason for this move was
  to abstract away the display server (x11/wayland). Apart from these
  changes there were no significant changes in the API.

  This affects gnome-desktop3 and gnome-settings-daemon. In particular
  the changes in gnome-desktop would create a gigantic mess if we tried
  to revert these changes for Unity only. As such have forked the
  display config code from mutter and ported *-settings-daemon and
  *-control-center to the new api. The code itself is fairly self
  contained, so apart from the resulting duplication of code, it
  shouldnt really be much of an issue.

  We have tested this via a ppa, however it was hard to get extensive
  testing, due to the amount of archive churn in the affected packages.
  I am pretty confident there are no much regressions and I will commit
  to fixing any issues to do appear.

  Essentially this transition will involve:
  new displayconfig package: This is the relevant code forked from mutter 
3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. 
This gets autostarted when required by g/u-s-d (although dbus activation may be 
broken in flashback session)
  my upstream branch is at https://github.com/darkxst/displayconfig (I had 
trouble working out how to import a git branch into bzr, but I imagine it 
should live in bzr once approved)

  gnome/unity-settings-daemon, have backported patches to adapt to the new API.
  Likewise for gnome/unity-control-center.
  All other rdepends just require a no-change rebuild to adapt to the new 
soname.

  Assuming this gets a approved, subsequent FFe's for gnome-settings-
  daemon and gnome-control-center 3.10 will follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1291088] Re: Doesn't unlock when coming back from the greeter

[Tim Penhey]

I have two users on my laptop, in an attempt to have different sessions
for different work.

Switching from one user to another takes me to the greeter to enter my
password, but when the new session starts, it immediately takes me to
the new lockscreen and requests the password again. This is very
annoying.

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

Title:
  Doesn't unlock when coming back from the greeter

Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Using the new unity-lock-screen from the current candidate version:
  - run unity on a system with multiple users
  - click on another user in indicator-session

  - the greeter is displayed with that user selected, so you can type
  the password to log in

  - select back your user and enter the password to unlock the session

  - what happens: the session is unlocked then locked again just after that
  - what should happen: the session should stay unlocked

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1291088/+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 1244084] Re: Ubuntu 13.10 Indicator Applet Complete icon

[Tim]

Marking Ubuntu GNOME task invalid, Edubuntu team maintains gnome-
flashback session

** Changed in: ubuntu-gnome
   Status: New = Invalid

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

Title:
  Ubuntu 13.10 Indicator Applet Complete icon

Status in Ubuntu GNOME:
  Invalid
Status in “indicator-applet” package in Ubuntu:
  Incomplete

Bug description:
  I just upgraded to *Ubuntu 13.10* using *Gnome (classic) Desktop*.

  The system Indicator Applet Complete icon on the far-right is wrong

  Note that if I boot to the *Ubuntu Unity desktop* the same applet has
  the correct icon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1244084/+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 1228765] Re: Need to implement DisplayConfig dbus interface within Unity

[Tim]

** Patch added: gnome-desktop 3.10 update
   
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1228765/+attachment/4006361/+files/gd310.debdiff

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

Title:
  Need to implement DisplayConfig dbus interface within Unity

Status in Ubuntu GNOME:
  Triaged
Status in Unity:
  Triaged
Status in Unity Control Center:
  In Progress
Status in Unity Settings Daemon:
  In Progress
Status in “gnome-desktop3” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  For GNOME 3.10, all the display configuration/xrandr code has been
  moved into Mutter as dbus interface. The Main reason for this move was
  to abstract away the display server (x11/wayland).

  This affects gnome-desktop3 and gnome-settings-daemon. In particular
  the changes in gnome-desktop would create a gigantic mess if we tried
  to revert these changes for Unity only. As such it seems the cleanest
  solution would be to copy the display config interface from Mutter
  into Unity. The code itself is fairly self contained, so apart from
  the resulting duplication of code, it shouldnt really be much of an
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10

[Tim]

** Summary changed:

- Need to implement DisplayConfig dbus interface within Unity
+ [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 
3.10

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

Title:
  [FFe] Implement DisplayConfig dbus interface and transition to gnome-
  desktop 3.10

Status in Ubuntu GNOME:
  Triaged
Status in Unity:
  Triaged
Status in Unity Control Center:
  In Progress
Status in Unity Settings Daemon:
  In Progress
Status in “gnome-desktop3” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  For GNOME 3.10, all the display configuration/xrandr code has been
  moved into Mutter as dbus interface. The Main reason for this move was
  to abstract away the display server (x11/wayland).

  This affects gnome-desktop3 and gnome-settings-daemon. In particular
  the changes in gnome-desktop would create a gigantic mess if we tried
  to revert these changes for Unity only. As such it seems the cleanest
  solution would be to copy the display config interface from Mutter
  into Unity. The code itself is fairly self contained, so apart from
  the resulting duplication of code, it shouldnt really be much of an
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10

[Tim]

** Description changed:

- For GNOME 3.10, all the display configuration/xrandr code has been moved
- into Mutter as dbus interface. The Main reason for this move was to
- abstract away the display server (x11/wayland).
+ Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome-
+ control-center 3.10. This however requires a transition to gnome-desktop
+ 3-10. I have been working on this for quite some time however this work
+ was essentially blocked waiting on the unity- forks for settings daemon
+ and control center. These were only finalised the day before feature
+ freeze.
+ 
+ Right now there are quite a few features that are not available for
+ configuration in g-c-c given it is so old. We are also hitting some odd
+ bugs with mutter using its own display config separate to what gnome-
+ settings-daemon is doing with xrandr.
+ 
+ 
+ For GNOME 3.10, all the display configuration/xrandr code has been moved into 
Mutter as dbus interface. The Main reason for this move was to abstract away 
the display server (x11/wayland). Apart from these changes there were no 
significant changes in the API.
  
  This affects gnome-desktop3 and gnome-settings-daemon. In particular the
  changes in gnome-desktop would create a gigantic mess if we tried to
- revert these changes for Unity only. As such it seems the cleanest
- solution would be to copy the display config interface from Mutter into
- Unity. The code itself is fairly self contained, so apart from the
- resulting duplication of code, it shouldnt really be much of an issue.
+ revert these changes for Unity only. As such have forked the display
+ config code from mutter and ported *-settings-daemon and *-control-
+ center to the new api. The code itself is fairly self contained, so
+ apart from the resulting duplication of code, it shouldnt really be much
+ of an issue.
+ 
+  ultimately it was We did do some testing via a ppa, however it was hard
+ to get extensive testing, due to the amount of archive churn in the
+ affected packages. I am pretty confident there are no much regressions
+ and I will commit to fixing any issues to do appear.
+ 
+ Essentially this transition will involve:
+ new displayconfig package: This is the relevant code forked from mutter 
3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. 
This gets autostarted when required by g/u-s-d (although dbus activation may be 
broken in flashback session)
+ 
+ gnome/unity-settings-daemon, have backported patches to adapt to the new API.
+ Likewise for gnome/unity-control-center.
+ All other rdepends just require a no-change rebuild to adapt to the new 
soname.

** Description changed:

  Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome-
  control-center 3.10. This however requires a transition to gnome-desktop
  3-10. I have been working on this for quite some time however this work
  was essentially blocked waiting on the unity- forks for settings daemon
  and control center. These were only finalised the day before feature
  freeze.
  
  Right now there are quite a few features that are not available for
  configuration in g-c-c given it is so old. We are also hitting some odd
  bugs with mutter using its own display config separate to what gnome-
  settings-daemon is doing with xrandr.
  
- 
- For GNOME 3.10, all the display configuration/xrandr code has been moved into 
Mutter as dbus interface. The Main reason for this move was to abstract away 
the display server (x11/wayland). Apart from these changes there were no 
significant changes in the API.
+ For GNOME 3.10, all the display configuration/xrandr code has been moved
+ into Mutter as dbus interface. The Main reason for this move was to
+ abstract away the display server (x11/wayland). Apart from these changes
+ there were no significant changes in the API.
  
  This affects gnome-desktop3 and gnome-settings-daemon. In particular the
  changes in gnome-desktop would create a gigantic mess if we tried to
  revert these changes for Unity only. As such have forked the display
  config code from mutter and ported *-settings-daemon and *-control-
  center to the new api. The code itself is fairly self contained, so
  apart from the resulting duplication of code, it shouldnt really be much
  of an issue.
  
-  ultimately it was We did do some testing via a ppa, however it was hard
- to get extensive testing, due to the amount of archive churn in the
- affected packages. I am pretty confident there are no much regressions
- and I will commit to fixing any issues to do appear.
+ We have tested this via a ppa, however it was hard to get extensive
+ testing, due to the amount of archive churn in the affected packages. I
+ am pretty confident there are no much regressions and I will commit to
+ fixing any issues to do appear.
  
  Essentially this transition will involve:
  new displayconfig package: This is the relevant code forked from mutter 
3.10.4 (with a couple of fixes from 3.11 

[Dx-packages] [Bug 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10

[Tim]

gnome-desktop buildlog
https://launchpadlibrarian.net/168292752/buildlog_ubuntu-trusty-amd64.gnome-desktop3_3.10.1-0ubuntu1~trusty2_UPLOADING.txt.gz

displayconfig buildlog
https://launchpadlibrarian.net/168120073/buildlog_ubuntu-trusty-amd64.displayconfig_3.10.4-0ubuntu1~trusty1_UPLOADING.txt.gz


logs for the other packages should be at 
https://launchpad.net/~noskcaj/+archive/build


** Changed in: gnome-desktop3 (Ubuntu)
   Status: Triaged = New

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

Title:
  [FFe] Implement DisplayConfig dbus interface and transition to gnome-
  desktop 3.10

Status in Ubuntu GNOME:
  Triaged
Status in Unity:
  Triaged
Status in Unity Control Center:
  In Progress
Status in Unity Settings Daemon:
  In Progress
Status in “gnome-desktop3” package in Ubuntu:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome-
  control-center 3.10. This however requires a transition to gnome-
  desktop 3-10. I have been working on this for quite some time however
  this work was essentially blocked waiting on the unity- forks for
  settings daemon and control center. These were only finalised the day
  before feature freeze.

  Right now there are quite a few features that are not available for
  configuration in g-c-c given it is so old. We are also hitting some
  odd bugs with mutter using its own display config separate to what
  gnome-settings-daemon is doing with xrandr.

  For GNOME 3.10, all the display configuration/xrandr code has been
  moved into Mutter as dbus interface. The Main reason for this move was
  to abstract away the display server (x11/wayland). Apart from these
  changes there were no significant changes in the API.

  This affects gnome-desktop3 and gnome-settings-daemon. In particular
  the changes in gnome-desktop would create a gigantic mess if we tried
  to revert these changes for Unity only. As such have forked the
  display config code from mutter and ported *-settings-daemon and
  *-control-center to the new api. The code itself is fairly self
  contained, so apart from the resulting duplication of code, it
  shouldnt really be much of an issue.

  We have tested this via a ppa, however it was hard to get extensive
  testing, due to the amount of archive churn in the affected packages.
  I am pretty confident there are no much regressions and I will commit
  to fixing any issues to do appear.

  Essentially this transition will involve:
  new displayconfig package: This is the relevant code forked from mutter 
3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. 
This gets autostarted when required by g/u-s-d (although dbus activation may be 
broken in flashback session)
  my upstream branch is at https://github.com/darkxst/displayconfig (I had 
trouble working out how to import a git branch into bzr, but I imagine it 
should live in bzr once approved)

  gnome/unity-settings-daemon, have backported patches to adapt to the new API.
  Likewise for gnome/unity-control-center.
  All other rdepends just require a no-change rebuild to adapt to the new 
soname.

  Assuming this gets a approved, subsequent FFe's for gnome-settings-
  daemon and gnome-control-center 3.10 will follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1223739] Re: Launcher - unable to reveal Launcher under autohide after using the touch screen

[Tim Chen]

I can not reproduce this in trusty daily build today. I think it already
fixed in 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/1223739

Title:
  Launcher - unable to reveal Launcher under autohide after using the
  touch screen

Status in OEM Priority Project:
  Confirmed
Status in Unity 5.0 series:
  Confirmed
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity” source package in Precise:
  Confirmed

Bug description:
  To Reproduce (in a system with a touch screen)

  1. Boot the system and don't touch the screen
  2. Set the Launcher to autohide
  3. Move the cursor to the left (using the touchpad or an external mouse)
  4. The Launcher is revealed successfully
  5. Wait until the launcher hides again
  6. Now, touch the screen for the first time (no matter where you touch the 
screen)
  7. Now, use again the touchpad or external mouse to move the cursor to the 
left to reveal the Launcher

  Expected result: Launcher is revealed
  Actual result: Launcher cannot be revealed.

  Additional information:
  1. When the issue happens, can press window key to show dash and launcher (or 
alt-f1 to reveal the launcher), but moving cursor to the left side still can't 
show launcher
  2. There is no crash is observed so far on X or Compiz
  3. Switch to ttyl1 and restart lightdm can recover

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1223739/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10

[Tim]

** Changed in: unity
   Status: Triaged = Invalid

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

Title:
  [FFe] Implement DisplayConfig dbus interface and transition to gnome-
  desktop 3.10

Status in Ubuntu GNOME:
  Triaged
Status in Unity:
  Invalid
Status in Unity Control Center:
  In Progress
Status in Unity Settings Daemon:
  In Progress
Status in “gnome-desktop3” package in Ubuntu:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome-
  control-center 3.10. This however requires a transition to gnome-
  desktop 3-10. I have been working on this for quite some time however
  this work was essentially blocked waiting on the unity- forks for
  settings daemon and control center. These were only finalised the day
  before feature freeze.

  Right now there are quite a few features that are not available for
  configuration in g-c-c given it is so old. We are also hitting some
  odd bugs with mutter using its own display config separate to what
  gnome-settings-daemon is doing with xrandr.

  For GNOME 3.10, all the display configuration/xrandr code has been
  moved into Mutter as dbus interface. The Main reason for this move was
  to abstract away the display server (x11/wayland). Apart from these
  changes there were no significant changes in the API.

  This affects gnome-desktop3 and gnome-settings-daemon. In particular
  the changes in gnome-desktop would create a gigantic mess if we tried
  to revert these changes for Unity only. As such have forked the
  display config code from mutter and ported *-settings-daemon and
  *-control-center to the new api. The code itself is fairly self
  contained, so apart from the resulting duplication of code, it
  shouldnt really be much of an issue.

  We have tested this via a ppa, however it was hard to get extensive
  testing, due to the amount of archive churn in the affected packages.
  I am pretty confident there are no much regressions and I will commit
  to fixing any issues to do appear.

  Essentially this transition will involve:
  new displayconfig package: This is the relevant code forked from mutter 
3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. 
This gets autostarted when required by g/u-s-d (although dbus activation may be 
broken in flashback session)
  my upstream branch is at https://github.com/darkxst/displayconfig (I had 
trouble working out how to import a git branch into bzr, but I imagine it 
should live in bzr once approved)

  gnome/unity-settings-daemon, have backported patches to adapt to the new API.
  Likewise for gnome/unity-control-center.
  All other rdepends just require a no-change rebuild to adapt to the new 
soname.

  Assuming this gets a approved, subsequent FFe's for gnome-settings-
  daemon and gnome-control-center 3.10 will follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10

[Tim]

- I fixed the issue with configurations not being read from the 
gnome-settings-daemon monitors.xml config file, I',m not entirely sure what 
wrote this file, but Laney suggested it was maybe copied across by one of the 
indicators?
- I couldn't reproduce the pointer barrier issue here on my dual monitor setup. 
I actually don't believe there is any code dealing with pointer barriers 
involved here either.
- Right, Unity no longer requires changes with this solution. marked invalid.
- Our build of g-c-c 3.10 has the bluetooth changes reverted, so no need for 
BlueZ 5 this cycle (will definitely need that for next cycle however).
- I will add a list of the changed API tomorrow, however I don't believe 
gnome-screensaver is affected by this and certainly built fine when I tested 
it. Most of the API changes are pretty internal (i.e. limited to g-s-d and 
g-c-c). The api's that most apps are using (background, thumbnailer, etc) are 
unaffected.

As a side note, I have spoken with upstream about splitting out all app
dependencies from gnome-desktop, at which point it would become feasible
to fork gnome-desktop, however this won't happen until atleast 3.14
anyway.

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

Title:
  [FFe] Implement DisplayConfig dbus interface and transition to gnome-
  desktop 3.10

Status in Ubuntu GNOME:
  Triaged
Status in Unity:
  Invalid
Status in Unity Control Center:
  In Progress
Status in Unity Settings Daemon:
  In Progress
Status in “gnome-desktop3” package in Ubuntu:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome-
  control-center 3.10. This however requires a transition to gnome-
  desktop 3-10. I have been working on this for quite some time however
  this work was essentially blocked waiting on the unity- forks for
  settings daemon and control center. These were only finalised the day
  before feature freeze.

  Right now there are quite a few features that are not available for
  configuration in g-c-c given it is so old. We are also hitting some
  odd bugs with mutter using its own display config separate to what
  gnome-settings-daemon is doing with xrandr.

  For GNOME 3.10, all the display configuration/xrandr code has been
  moved into Mutter as dbus interface. The Main reason for this move was
  to abstract away the display server (x11/wayland). Apart from these
  changes there were no significant changes in the API.

  This affects gnome-desktop3 and gnome-settings-daemon. In particular
  the changes in gnome-desktop would create a gigantic mess if we tried
  to revert these changes for Unity only. As such have forked the
  display config code from mutter and ported *-settings-daemon and
  *-control-center to the new api. The code itself is fairly self
  contained, so apart from the resulting duplication of code, it
  shouldnt really be much of an issue.

  We have tested this via a ppa, however it was hard to get extensive
  testing, due to the amount of archive churn in the affected packages.
  I am pretty confident there are no much regressions and I will commit
  to fixing any issues to do appear.

  Essentially this transition will involve:
  new displayconfig package: This is the relevant code forked from mutter 
3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. 
This gets autostarted when required by g/u-s-d (although dbus activation may be 
broken in flashback session)
  my upstream branch is at https://github.com/darkxst/displayconfig (I had 
trouble working out how to import a git branch into bzr, but I imagine it 
should live in bzr once approved)

  gnome/unity-settings-daemon, have backported patches to adapt to the new API.
  Likewise for gnome/unity-control-center.
  All other rdepends just require a no-change rebuild to adapt to the new 
soname.

  Assuming this gets a approved, subsequent FFe's for gnome-settings-
  daemon and gnome-control-center 3.10 will follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10

[Tim]

This is the full list of API changes for gnome-desktop, keep in mind
that most of these were moved into display-config (and/or made redundant
by those changes). There are no rdepends in the archive that use any of
these (apart from g-s-d/g-c-c and u-s-d/u-c-c which already have patches
prepared on this FFe)

Removed:
gnome_rr_screen_set_size
gnome_rr_screen_get_timestamps
gnome_rr_screen_set_primary_output
gnome_rr_output_is_connected
gnome_rr_output_get_backlight_min
gnome_rr_output_get_backlight_max
gnome_rr_output_get_size_inches
gnome_rr_crtc_set_config_with_time
gnome_rr_output_get_connector_type
gnome_rr_config_save
gnome_rr_config_apply_from_filename_with_time
gnome_rr_config_apply_with_time
gnome_rr_config_get_backup_filename
gnome_rr_config_get_intended_filename
gnome_rr_config_load_filename
gnome_rr_config_new_stored

Changed:
gnome_rr_output_is_laptop - gnome_rr_output_is_builtin_display
gnome_rr_output_get_backlight (remove gerror param)
gnome_rr_output_get_ids_from_edid (type changes for some params)
gnome_rr_output_get_width_mm - gnome_rr_output_get_physical_size
gnome_rr_output_get_height_mm - gnome_rr_output_get_physical_sizels
gnome_idle_monitor_new_for_device (adds gerror)

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

Title:
  [FFe] Implement DisplayConfig dbus interface and transition to gnome-
  desktop 3.10

Status in Ubuntu GNOME:
  Triaged
Status in Unity:
  Invalid
Status in Unity Settings Daemon:
  In Progress
Status in “gnome-desktop3” package in Ubuntu:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  In Progress

Bug description:
  Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome-
  control-center 3.10. This however requires a transition to gnome-
  desktop 3-10. I have been working on this for quite some time however
  this work was essentially blocked waiting on the unity- forks for
  settings daemon and control center. These were only finalised the day
  before feature freeze.

  Right now there are quite a few features that are not available for
  configuration in g-c-c given it is so old. We are also hitting some
  odd bugs with mutter using its own display config separate to what
  gnome-settings-daemon is doing with xrandr.

  For GNOME 3.10, all the display configuration/xrandr code has been
  moved into Mutter as dbus interface. The Main reason for this move was
  to abstract away the display server (x11/wayland). Apart from these
  changes there were no significant changes in the API.

  This affects gnome-desktop3 and gnome-settings-daemon. In particular
  the changes in gnome-desktop would create a gigantic mess if we tried
  to revert these changes for Unity only. As such have forked the
  display config code from mutter and ported *-settings-daemon and
  *-control-center to the new api. The code itself is fairly self
  contained, so apart from the resulting duplication of code, it
  shouldnt really be much of an issue.

  We have tested this via a ppa, however it was hard to get extensive
  testing, due to the amount of archive churn in the affected packages.
  I am pretty confident there are no much regressions and I will commit
  to fixing any issues to do appear.

  Essentially this transition will involve:
  new displayconfig package: This is the relevant code forked from mutter 
3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. 
This gets autostarted when required by g/u-s-d (although dbus activation may be 
broken in flashback session)
  my upstream branch is at https://github.com/darkxst/displayconfig (I had 
trouble working out how to import a git branch into bzr, but I imagine it 
should live in bzr once approved)

  gnome/unity-settings-daemon, have backported patches to adapt to the new API.
  Likewise for gnome/unity-control-center.
  All other rdepends just require a no-change rebuild to adapt to the new 
soname.

  Assuming this gets a approved, subsequent FFe's for gnome-settings-
  daemon and gnome-control-center 3.10 will follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1277888] Re: In most apps all menu items are gray / unclickable

[Tim]

** Also affects: ubuntu-gnome
   Importance: Undecided
   Status: New

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

Title:
  In most apps all menu items are gray / unclickable

Status in Ubuntu GNOME:
  New
Status in Unity:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  In Libreoffice write for example all menu items in the gloal menu are
  gray and unclickable. Even stuff like quit or about libreoffice.
  Using the keyboard shortcuts to access the items works though and it's
  possible to open sub-menus but nothing in them is clickable.

  This happens with several other apps like Gnome Terminal, Sublime Text
  (3 party package) and shotwell.

  The imagage viewer has the first menu working but not the other.
  Firefox  seems to work. The single menu of nautilius works too.

  I found a smiliar bug against Libreoffice but maybe it's a different problem.
  https://bugs.freedesktop.org/show_bug.cgi?id=73794

  See the attatched screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Är en katalog: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.20  Wed Oct 30 17:43:35 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.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
  Date: Sat Feb  8 15:49:47 2014
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: nvidia-331, 331.20, 3.11.0-15-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF100 [GeForce GTX 465] [10de:06c4] (rev a3) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:834c]
  InstallationDate: Installed on 2013-12-20 (49 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: ASUS All Series
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed 
root=UUID=fbdd2a1c-8021-4dff-a5e6-2dd1a4173bfa ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1602
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1602:bd10/29/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.904-0ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Sat Feb  8 14:57:11 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.14.5-1ubuntu2~saucy1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1277888/+subscriptions

-- 
Mailing list: https://launchpad.net/~dx-packages
Post to   

[Dx-packages] [Bug 1263205] Re: unity-menu in gimp and libre office writer greys out active entries

[Tim Passingham]

I found that with Libreoffice if I changed something, opened the menu,
save and undo were greyed out.  If I moved away from the menu and then
went back to it, save and undo were now available.

Further, the shortcut underlines do not appear in the menu.  This is a
source of considerable grief to me, as in 'Good Grief!'.

I have got round this by uninstalling 'indicator-appmenu'.  Menus go
back to the top of each window, and work properly.  I have been trying
to adjust to unity menus, but if the menus don't work properly I can't
possibly do so.

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

Title:
  unity-menu in gimp and libre office writer greys out active entries

Status in “unity-gtk-module” package in Ubuntu:
  New

Bug description:
  There seem to be a problem with interaction between some programs (in
  my case Libre Office and Gimp in the versions that come with Ubtunt
  13.10) and the menu. In libre office it is not possible to save a text
  although it has been altered by the menu, but it is possible to save
  by the shortcut STRG-S.

  In Gimp after some changes on a graphic almost any menu-entries are
  greyed out, but it is possible to get to these menus with the internal
  menu in Gimp One window-mode.

  Checked this on a notebook and on a second fresh install done some
  minutes ago.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1263205/+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 1263205] Re: unity-menu in gimp and libre office writer greys out active entries

[Tim Passingham]

I have the same problem on 13.10, LibreOffice 4.1.4.2.

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

Title:
  unity-menu in gimp and libre office writer greys out active entries

Status in “unity-gtk-module” package in Ubuntu:
  New

Bug description:
  There seem to be a problem with interaction between some programs (in
  my case Libre Office and Gimp in the versions that come with Ubtunt
  13.10) and the menu. In libre office it is not possible to save a text
  although it has been altered by the menu, but it is possible to save
  by the shortcut STRG-S.

  In Gimp after some changes on a graphic almost any menu-entries are
  greyed out, but it is possible to get to these menus with the internal
  menu in Gimp One window-mode.

  Checked this on a notebook and on a second fresh install done some
  minutes ago.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1263205/+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 404658] Re: notification summary doesn't change for synchronous messages

[Tim Chen]

works fine to me with notify-osd/0.9.34-0ubuntu2.1 on Precise.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  notification summary doesn't change for synchronous messages

Status in Notify OSD:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project precise series:
  In Progress
Status in “notify-osd” package in Ubuntu:
  Fix Released
Status in “notify-osd” source package in Precise:
  Fix Committed

Bug description:
  
  Precise SRU info:

  [Impact]

   * The patch provide a fix to provide the x-canonical-private-
  synchronous to work with notifications different with
  LAYOUT_ICON_INDICATOR layout. Currently the x-canonical-private-
  synchronous interface only provide this layout to support brightness
  and volume control.

  [Test Case]

   * This patch make following command behave correctly.

  #notify-send -h string:x-canonical-private-synchronous:1 wireless
  disable -i notification-network-wireless-none ; sleep 1 ; notify-
  send -h string:x-canonical-private-synchronous:1 bluetooth enable
  -i bluetooth

  In current implementation,  both Summary and Body text didn't get
  updated.

  [Regression Potential]

   * The risk should be minimal, the patch should only affect x
  -canonical-private-synchronous interface. This interface is only used
  in brightness and volume hotkey, and layout is different.

   * The patch is already tested in OEM projects.

  [Other Info]

  *** Original bug description:

  When you send a notification in Synchronous with another, the both
  Summary and Body text doesn't get updated.

  As an example:

  while true; do
  notify-send first title first subtitle -i dialog-info -h 
string:x-canonical-private-synchronous:test
  sleep 1
  notify-send second title second subtitle -i dialog-error -h 
string:x-canonical-private-synchronous:test
  sleep 1
  done

  If you run the above, what you should see is the Icon changing, but the 
summary/body text staying the same.
  Is this expected behaviour from the libnotify library? Or is this an 
overlooked feature?

  Regards
  Iain

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=9.04
  DISTRIB_CODENAME=jaunty
  DISTRIB_DESCRIPTION=Ubuntu 9.04

  Package: libnotify-bin
  Priority: optional
  Section: universe/utils
  Installed-Size: 72
  Maintainer: Ubuntu Core Developers ubuntu-devel-disc...@lists.ubuntu.com
  Original-Maintainer: Andre Filipe de Assuncao e Brito de...@noisemakers.org
  Architecture: amd64
  Source: libnotify
  Version: 0.4.5-0ubuntu1
  Depends: libc6 (= 2.3.4), libglib2.0-0 (= 2.12.0), libnotify1 (= 0.4.4), 
libnotify1-gtk2.10
  Filename: pool/universe/libn/libnotify/libnotify-bin_0.4.5-0ubuntu1_amd64.deb
  Size: 7248
  MD5sum: 332bacf4fad51bb2a32d17ed08ae66bc
  SHA1: ecbcfde7197c8934b7883a8d561ba02ba502adf2
  SHA256: 15e1b7d9858a1c89f7bd826b10b16e2c0ee305e4268bd9bd0b1be3469eb9aaf9
  Description: sends desktop notifications to a notification daemon
   A library that sends desktop notifications to a notification daemon, as
   defined in the Desktop Notifications spec. These notifications can be
   used to inform the user about an event or display some form of
   information without getting in the user's way.
   .
   This package contains the binary which sends the notification.
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Origin: Ubuntu
  Task: xubuntu-desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/notify-osd/+bug/404658/+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 1253591] Re: Display switch and Radio enable/disable hotkey icons

[Tim Chen]

good to me test on notify-osd-icons/0.8~precise on Precise.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Display switch and Radio enable/disable hotkey icons

Status in OEM Priority Project:
  In Progress
Status in “notify-osd-icons” package in Ubuntu:
  Fix Released
Status in “notify-osd-icons” source package in Precise:
  Fix Committed

Bug description:
  12.04 Precise SRU info:

  [Impact] 
  The package provide new notify-osd-icons for Radio enable/disable and Display 
switch.

  This is related to https://bugs.launchpad.net/ubuntu/+source/notify-
  osd/+bug/404658 to be used in OEM projects.

  [Test Case]

  The package should be install/upgrade correctly.

  [Regression Potential]

  No known risk right now.

  [Other Info]

  1) Radio enable/disable, for example Fn-F2 on a Dell XPS13.

  2) Display switch, for example Fn-F1 on a Dell XPS13

  attached are icons from John Lea

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1253591/+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] [Bug 1257505] Re: Create Unity Control Center so can remain on old GNOME Control Center version

[Tim]

On 10/01/14 21:23, Alberto Mardegan wrote:
 On 01/10/2014 05:24 AM, Robert Ancell wrote:
 It doesn't look easy to do this for gnome-control-center-signon since
 the package contains a lot of common files. We might have to wait for
 the other components to be ready, and upload the gnome-control-center-
 signon at the same time we add unity-control-center to the seed. We can
 make gnome-control-center signon depend the version of u-c-c that is
 uploaded at that time.
 OK.

 Also, I talked to the Ubuntu GNOME team about what they plan to do with
 unity-control-center. They said that it was desirable to be able to
 access the online accounts in GNOME for the apps that need it. Will
 anything show in g-c-c once we move to u-c-c? Do you care about this
 use-case as an upstream?
 I wonder whether by Online Accounts they meant GNOME Online Accounts
 (GOA) or Ubuntu Online Accounts (UOA). The former should indeed be
 visible in g-c-c without special support from our side; the latter is
 currently visible as well in GNOME, causing two Online Accounts applet
 to appear in the control center (bug 1040193). Do we want to continue
 showing it there as well?
No, we ship GOA by default, however we do have users that use UOA
 as well (its just not installed by default). there are definitely a sub-set of
apps that only work with UOA, sometimes this is due to Ubuntu patches
, in other cases its just lack of upstream support for those apps.

 I would prefer if the Ubuntu GNOME session were as close as possible to
 upstream, meaning that it would be fine for me if UOA was not appearing
 in the GNOME control center. However, this would need at least two
 things to happen first:
Me too, but we can't just rip out the Ubuntu features that have been there
forever, causing regressions and screaming users!

 - If built with UOA support (as it is in Ubuntu), Empathy currently
 opens the UOA panel when asked to configure accounts; we should probably
 change that to a run-time decision, maybe based on the contents of
 XDG_CURRENT_DESKTOP.
I filed a patch upsteam for that, but it was never merged.

 - Ubuntu's Shotwell build is tightly integrated with UOA, and in order
 to publish on Facebook, Flickr or Picasa you need to have a
 corresponding account setup in UOA. We should fix this by submitting our
 patches upstream, and rework them so that the decision to use UOA can
 happen at runtime. Unfortunately this could take several days of work,
 and I'm afraid I don't have this time... :-(


-- 
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, dx-packages, dx-packages, dx-packages
https://bugs.launchpad.net/bugs/1257505

Title:
  Create Unity Control Center so can remain on old GNOME Control Center
  version

Status in “activity-log-manager” package in Ubuntu:
  In Progress
Status in “chromium-browser” package in Ubuntu:
  Confirmed
Status in “deja-dup” package in Ubuntu:
  In Progress
Status in “empathy” package in Ubuntu:
  Confirmed
Status in “eog” package in Ubuntu:
  In Progress
Status in “gnome-color-manager” package in Ubuntu:
  In Progress
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-control-center-signon” package in Ubuntu:
  In Progress
Status in “gnome-media” package in Ubuntu:
  In Progress
Status in “gthumb” package in Ubuntu:
  In Progress
Status in “indicator-bluetooth” package in Ubuntu:
  In Progress
Status in “indicator-datetime” package in Ubuntu:
  In Progress
Status in “indicator-power” package in Ubuntu:
  In Progress
Status in “indicator-session” package in Ubuntu:
  In Progress
Status in “indicator-sound” package in Ubuntu:
  In Progress
Status in “landscape-client” package in Ubuntu:
  In Progress
Status in “language-selector” package in Ubuntu:
  In Progress
Status in “nautilus” package in Ubuntu:
  In Progress
Status in “software-properties” package in Ubuntu:
  In Progress
Status in “ubuntuone-control-panel” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  New
Status in “unity-control-center” package in Ubuntu:
  Fix Released
Status in “webaccounts-browser-extension” package in Ubuntu:
  In Progress

Bug description:
  Ubuntu/Unity uses GNOME Control Center as the application to configure
  the Unity session. We've made a lot of changes appropriate for Ubuntu
  and Unity (61 patches) which makes it hard to maintain and creates a
  conflict for Ubuntu GNOME to use the control center. Unity 7 will be
  replaced by Unity 8 in the future which has a new settings interface.

  So we can continue to remain on the current version of GNOME Control
  Center but allow Ubuntu GNOME to continue to update we will create a
  new project lp:unity-control-center which is a copy of GNOME Control
  Center 3.6 but with appropriate renaming so both can be installed.

  A number of packages that refer to gnome-control-center need to be
  updated to refer to 

[Dx-packages] [Bug 1253591] Re: Display switch and Radio enable/disable hotkey icons

[Tim Chen]

** Description changed:

+ 12.04 Precise SRU info:
+ 
+ [Impact] 
+ The package provide new notify-osd-icons for Radio enable/disable and Display 
switch.
+ 
+ This is related to https://bugs.launchpad.net/ubuntu/+source/notify-
+ osd/+bug/404658 to be used in OEM projects.
+ 
+ [Test Case]
+ 
+ The package should be install/upgrade correctly.
+ 
+ [Regression Potential]
+ 
+ No known risk right now.
+ 
+ [Other Info]
+ 
  1) Radio enable/disable, for example Fn-F2 on a Dell XPS13.
  
  2) Display switch, for example Fn-F1 on a Dell XPS13
  
  attached are icons from John Lea

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

Title:
  Display switch and Radio enable/disable hotkey icons

Status in OEM Priority Project:
  In Progress
Status in “notify-osd-icons” package in Ubuntu:
  Fix Released
Status in “notify-osd-icons” source package in Precise:
  New

Bug description:
  12.04 Precise SRU info:

  [Impact] 
  The package provide new notify-osd-icons for Radio enable/disable and Display 
switch.

  This is related to https://bugs.launchpad.net/ubuntu/+source/notify-
  osd/+bug/404658 to be used in OEM projects.

  [Test Case]

  The package should be install/upgrade correctly.

  [Regression Potential]

  No known risk right now.

  [Other Info]

  1) Radio enable/disable, for example Fn-F2 on a Dell XPS13.

  2) Display switch, for example Fn-F1 on a Dell XPS13

  attached are icons from John Lea

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1253591/+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 1253591] Re: Display switch and Radio enable/disable hotkey icons

[Tim Chen]

https://code.launchpad.net/~timchen119/ubuntu/precise/notify-osd-icons
/notify-osd-icons-precise-1253591/+merge/199619

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

Title:
  Display switch and Radio enable/disable hotkey icons

Status in OEM Priority Project:
  In Progress
Status in “notify-osd-icons” package in Ubuntu:
  Fix Released
Status in “notify-osd-icons” source package in Precise:
  New

Bug description:
  12.04 Precise SRU info:

  [Impact] 
  The package provide new notify-osd-icons for Radio enable/disable and Display 
switch.

  This is related to https://bugs.launchpad.net/ubuntu/+source/notify-
  osd/+bug/404658 to be used in OEM projects.

  [Test Case]

  The package should be install/upgrade correctly.

  [Regression Potential]

  No known risk right now.

  [Other Info]

  1) Radio enable/disable, for example Fn-F2 on a Dell XPS13.

  2) Display switch, for example Fn-F1 on a Dell XPS13

  attached are icons from John Lea

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1253591/+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 1260880] [NEW] typelib file is installed to the incorrect location

[Tim]

Public bug reported:

Accountsservice was converted to multiarch, but now the typelib file is
installed to the multi-arch path which completely breaks gnome-shell.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: accountsservice 0.6.35-0ubuntu5
ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2
Uname: Linux 3.12.0-5-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Dec 14 09:40:42 2013
InstallationDate: Installed on 2012-09-23 (446 days ago)
InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha 
amd64(20120922)
SourcePackage: accountsservice
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: accountsservice (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 accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1260880

Title:
  typelib file is installed to the incorrect location

Status in “accountsservice” package in Ubuntu:
  New

Bug description:
  Accountsservice was converted to multiarch, but now the typelib file
  is installed to the multi-arch path which completely breaks gnome-
  shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: accountsservice 0.6.35-0ubuntu5
  ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2
  Uname: Linux 3.12.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Dec 14 09:40:42 2013
  InstallationDate: Installed on 2012-09-23 (446 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha 
amd64(20120922)
  SourcePackage: accountsservice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1260880/+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 1260880] Re: typelib file is installed to the incorrect location

[Tim]

** Patch added: AccountsService.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1260880/+attachment/3928943/+files/AccountsService.debdiff

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

Title:
  typelib file is installed to the incorrect location

Status in “accountsservice” package in Ubuntu:
  New

Bug description:
  Accountsservice was converted to multiarch, but now the typelib file
  is installed to the multi-arch path which completely breaks gnome-
  shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: accountsservice 0.6.35-0ubuntu5
  ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2
  Uname: Linux 3.12.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Dec 14 09:40:42 2013
  InstallationDate: Installed on 2012-09-23 (446 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha 
amd64(20120922)
  SourcePackage: accountsservice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1260880/+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 1228765] Re: Need to implement DisplayConfig dbus interface within Unity

[Tim]

Tagging as high for Ubuntu GNOME, since this is blocking g-s-d/g-c-c
(once they have been forked for ubuntu)

** Also affects: ubuntu-gnome
   Importance: Undecided
   Status: New

** Changed in: ubuntu-gnome
   Importance: Undecided = High

** Changed in: ubuntu-gnome
   Status: New = Triaged

** Changed in: ubuntu-gnome
Milestone: None = 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/1228765

Title:
  Need to implement DisplayConfig dbus interface within Unity

Status in Ubuntu GNOME:
  Triaged
Status in Unity:
  Triaged
Status in “gnome-desktop3” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  For GNOME 3.10, all the display configuration/xrandr code has been
  moved into Mutter as dbus interface. The Main reason for this move was
  to abstract away the display server (x11/wayland).

  This affects gnome-desktop3 and gnome-settings-daemon. In particular
  the changes in gnome-desktop would create a gigantic mess if we tried
  to revert these changes for Unity only. As such it seems the cleanest
  solution would be to copy the display config interface from Mutter
  into Unity. The code itself is fairly self contained, so apart from
  the resulting duplication of code, it shouldnt really be much of an
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+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 1253591] [NEW] Display switch and Radio enable/disable hotkey icons

[Tim Chen]

Public bug reported:

1) Radio enable/disable, for example Fn-F2 on a Dell XPS13.

2) Display switch, for example Fn-F1 on a Dell XPS13

attached are icons from John Lea

** Affects: oem-priority
 Importance: Undecided
 Status: New

** Affects: notify-osd-icons (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: NotifyOSD-icons.zip
   
https://bugs.launchpad.net/bugs/1253591/+attachment/3913992/+files/NotifyOSD-icons.zip

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

Title:
  Display switch and Radio enable/disable hotkey icons

Status in OEM Priority Project:
  New
Status in “notify-osd-icons” package in Ubuntu:
  New

Bug description:
  1) Radio enable/disable, for example Fn-F2 on a Dell XPS13.

  2) Display switch, for example Fn-F1 on a Dell XPS13

  attached are icons from John Lea

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1253591/+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 404658] Re: notification summary doesn't change for synchronous messages

[Tim Chen]

Patch included, 
the patch provide a fix to provide the x-canonical-private-synchronous to 
work with notifications different with  LAYOUT_ICON_INDICATOR layout. Currently 
the x-canonical-private-synchronous interface only provide this layout to 
support brightness and volume control.

This patch make following command behave correctly.
#notify-send RF-status enabled -h string:x-canonical-private-synchronous:1 
-h string:image_path:/tmp/test.jpg

Canonical OEM projects need this function to

* enable OSD for enable/disable WiFi or bluetooth with a hotkey
* enable OSD for display switching with a hotkey

For more details, see:

https://bugs.launchpad.net/bugs/1213507
https://bugs.launchpad.net/bugs/1213508


** Patch added: notify-osd-lp404658.patch
   
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/404658/+attachment/3889403/+files/notify-osd-lp404658.patch

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

Title:
  notification summary doesn't change for synchronous messages

Status in “notify-osd” package in Ubuntu:
  Confirmed

Bug description:
  When you send a notification in Synchronous with another, the both
  Summary and Body text doesn't get updated.

  
  As an example:

  
  while true; do
  notify-send first title first subtitle -i dialog-info -h 
string:x-canonical-private-synchronous:test
  sleep 1
  notify-send second title second subtitle -i dialog-error -h 
string:x-canonical-private-synchronous:test
  sleep 1
  done

  
  If you run the above, what you should see is the Icon changing, but the 
summary/body text staying the same.
  Is this expected behaviour from the libnotify library? Or is this an 
overlooked feature?

  Regards
  Iain

  
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=9.04
  DISTRIB_CODENAME=jaunty
  DISTRIB_DESCRIPTION=Ubuntu 9.04

  
  Package: libnotify-bin
  Priority: optional
  Section: universe/utils
  Installed-Size: 72
  Maintainer: Ubuntu Core Developers ubuntu-devel-disc...@lists.ubuntu.com
  Original-Maintainer: Andre Filipe de Assuncao e Brito de...@noisemakers.org
  Architecture: amd64
  Source: libnotify
  Version: 0.4.5-0ubuntu1
  Depends: libc6 (= 2.3.4), libglib2.0-0 (= 2.12.0), libnotify1 (= 0.4.4), 
libnotify1-gtk2.10
  Filename: pool/universe/libn/libnotify/libnotify-bin_0.4.5-0ubuntu1_amd64.deb
  Size: 7248
  MD5sum: 332bacf4fad51bb2a32d17ed08ae66bc
  SHA1: ecbcfde7197c8934b7883a8d561ba02ba502adf2
  SHA256: 15e1b7d9858a1c89f7bd826b10b16e2c0ee305e4268bd9bd0b1be3469eb9aaf9
  Description: sends desktop notifications to a notification daemon
   A library that sends desktop notifications to a notification daemon, as
   defined in the Desktop Notifications spec. These notifications can be
   used to inform the user about an event or display some form of
   information without getting in the user's way.
   .
   This package contains the binary which sends the notification.
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Origin: Ubuntu
  Task: xubuntu-desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/404658/+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 404658] Re: notification summary doesn't change for synchronous messages

[Tim Chen]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Also affects: oem-priority/precise
   Importance: Undecided
   Status: New

** Changed in: oem-priority/precise
   Importance: Undecided = Critical

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

Title:
  notification summary doesn't change for synchronous messages

Status in OEM Priority Project:
  New
Status in OEM Priority Project precise series:
  New
Status in “notify-osd” package in Ubuntu:
  Confirmed

Bug description:
  When you send a notification in Synchronous with another, the both
  Summary and Body text doesn't get updated.

  
  As an example:

  
  while true; do
  notify-send first title first subtitle -i dialog-info -h 
string:x-canonical-private-synchronous:test
  sleep 1
  notify-send second title second subtitle -i dialog-error -h 
string:x-canonical-private-synchronous:test
  sleep 1
  done

  
  If you run the above, what you should see is the Icon changing, but the 
summary/body text staying the same.
  Is this expected behaviour from the libnotify library? Or is this an 
overlooked feature?

  Regards
  Iain

  
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=9.04
  DISTRIB_CODENAME=jaunty
  DISTRIB_DESCRIPTION=Ubuntu 9.04

  
  Package: libnotify-bin
  Priority: optional
  Section: universe/utils
  Installed-Size: 72
  Maintainer: Ubuntu Core Developers ubuntu-devel-disc...@lists.ubuntu.com
  Original-Maintainer: Andre Filipe de Assuncao e Brito de...@noisemakers.org
  Architecture: amd64
  Source: libnotify
  Version: 0.4.5-0ubuntu1
  Depends: libc6 (= 2.3.4), libglib2.0-0 (= 2.12.0), libnotify1 (= 0.4.4), 
libnotify1-gtk2.10
  Filename: pool/universe/libn/libnotify/libnotify-bin_0.4.5-0ubuntu1_amd64.deb
  Size: 7248
  MD5sum: 332bacf4fad51bb2a32d17ed08ae66bc
  SHA1: ecbcfde7197c8934b7883a8d561ba02ba502adf2
  SHA256: 15e1b7d9858a1c89f7bd826b10b16e2c0ee305e4268bd9bd0b1be3469eb9aaf9
  Description: sends desktop notifications to a notification daemon
   A library that sends desktop notifications to a notification daemon, as
   defined in the Desktop Notifications spec. These notifications can be
   used to inform the user about an event or display some form of
   information without getting in the user's way.
   .
   This package contains the binary which sends the notification.
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Origin: Ubuntu
  Task: xubuntu-desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/404658/+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 1228765] [NEW] Need to implement DisplayConfig dbus interface within Unity

[Tim]

Public bug reported:

For GNOME 3.10, all the display configuration/xrandr code has been moved
into Mutter as dbus interface. The Main reason for this move was to
abstract away the display server (x11/wayland).

This affects gnome-desktop3 and gnome-settings-daemon. In particular the
changes in gnome-desktop would create a gigantic mess if we tried to
revert these changes for Unity only. As such it seems the cleanest
solution would be to copy the display config interface from Mutter into
Unity. The code itself is fairly self contained, so apart from the
resulting duplication of code, it shouldnt really be much of an issue.

** Affects: gnome-desktop3 (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

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

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

Title:
  Need to implement DisplayConfig dbus interface within Unity

Status in “gnome-desktop3” package in Ubuntu:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  New

Bug description:
  For GNOME 3.10, all the display configuration/xrandr code has been
  moved into Mutter as dbus interface. The Main reason for this move was
  to abstract away the display server (x11/wayland).

  This affects gnome-desktop3 and gnome-settings-daemon. In particular
  the changes in gnome-desktop would create a gigantic mess if we tried
  to revert these changes for Unity only. As such it seems the cleanest
  solution would be to copy the display config interface from Mutter
  into Unity. The code itself is fairly self contained, so apart from
  the resulting duplication of code, it shouldnt really be much of an
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1228765/+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 1103064] Re: power indicator shows Logitech wireless keyboard and mouse batteries with 0%

[Tim]

I have the same issue as Lionel, with my wireless mouse oscillating
between reporting the correct percentage and 1%. I can confirm that the
above git branch resolves this issue.

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

Title:
  power indicator shows Logitech wireless keyboard and mouse batteries
  with 0%

Status in The Power Indicator:
  Invalid
Status in Upower:
  Incomplete
Status in “indicator-power” package in Ubuntu:
  Invalid
Status in “upower” package in Ubuntu:
  Confirmed
Status in “indicator-power” source package in Raring:
  Invalid
Status in “upower” source package in Raring:
  Won't Fix

Bug description:
  I updated by raring installation and found that the power indicator
  now shows my wireless keyboard and mouse as (missing) and with
  extremely low power. Both the keyboard and mouse work (I'm using them
  to type this bug) and the low battery light on the respective devices
  do not show low power. Even switching to brand new batteries don't
  make the indicator change state.

  I've attached a screenshot of the indicator and a screen shot of the
  power setting dialog which seems to be in conflict with the indicator.

  I've reproduced this behavior with the 3.8.0-0-generic 
  vmlinuz-3.8.0-1-generic kernels.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-power 12.10.6daily13.01.18-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3
  Uname: Linux 3.8.0-0-generic x86_64
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  Date: Tue Jan 22 11:39:23 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-05-08 (259 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to raring on 2013-01-18 (3 days ago)
  --- 
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-05-08 (259 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  Package: upower 0.9.19-1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Tags:  raring running-unity
  Uname: Linux 3.8.0-1-generic x86_64
  UpgradeStatus: Upgraded to raring on 2013-01-18 (4 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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