[Dx-packages] [Bug 1554878] Re: fix up usage of XDG_CURRENT_DESKTOP

2016-10-02 Thread Launchpad Bug Tracker 
** Branch linked: lp:~robert-ancell/unity-control-center/xdg-current-
desktop

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

Title:
  fix up usage of XDG_CURRENT_DESKTOP

Status in GLib:
  Confirmed
Status in Python XDG App:
  Confirmed
Status in empathy package in Ubuntu:
  Fix Released
Status in eog package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in indicator-bluetooth package in Ubuntu:
  Fix Committed
Status in nautilus package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Committed
Status in unity-settings-daemon package in Ubuntu:
  Fix Committed
Status in yelp package in Ubuntu:
  Fix Released

Bug description:
  Since being standardised XDG_CURRENT_DESKTOP supports specifying
  multiple Desktop Names seperated by a colon, however many of the
  patches in Ubuntu pre-date this change so don't correctly support the
  current format in some cases.

  These days XDG_CURRENT_DESKTOP will look something like
  Unity
  GNOME (gnome-shell)
  GNOME-Classic:GNOME (gnome-shell classic mode)
  GNOME-Flashback:Unity (Flashback sesison, although upstream and debian use 
GNOME-Flashack:GNOME for this)

  Many of the patches only check for == "Unity" or == "GNOME", so
  misbehave for the latter cases in the list above.

  I suspect this will be more widespread than just nautilus, but fixing
  that would be a good start. Since most of this code is still Ubuntu
  specific (upstream mainly use XDG_CURRENT_DESKTOP for onlyShowIn etc),
  probably taking the last value in the string would get the desired
  result of Unity vs GNOME3 behaviour

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Mar  9 15:04:36 2016
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to xenial on 2015-11-28 (102 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1554878/+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 1554878] Re: fix up usage of XDG_CURRENT_DESKTOP

2016-10-02 Thread Robert Ancell 
This is affecting Ubuntu 16.10 now as XDG_CURRENT_DESKTOP is now set to
"Unity:Unity7" (e.g. bug 1629668)

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

Title:
  fix up usage of XDG_CURRENT_DESKTOP

Status in GLib:
  Confirmed
Status in Python XDG App:
  Confirmed
Status in empathy package in Ubuntu:
  Fix Released
Status in eog package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in indicator-bluetooth package in Ubuntu:
  Fix Committed
Status in nautilus package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Committed
Status in unity-settings-daemon package in Ubuntu:
  Fix Committed
Status in yelp package in Ubuntu:
  Fix Released

Bug description:
  Since being standardised XDG_CURRENT_DESKTOP supports specifying
  multiple Desktop Names seperated by a colon, however many of the
  patches in Ubuntu pre-date this change so don't correctly support the
  current format in some cases.

  These days XDG_CURRENT_DESKTOP will look something like
  Unity
  GNOME (gnome-shell)
  GNOME-Classic:GNOME (gnome-shell classic mode)
  GNOME-Flashback:Unity (Flashback sesison, although upstream and debian use 
GNOME-Flashack:GNOME for this)

  Many of the patches only check for == "Unity" or == "GNOME", so
  misbehave for the latter cases in the list above.

  I suspect this will be more widespread than just nautilus, but fixing
  that would be a good start. Since most of this code is still Ubuntu
  specific (upstream mainly use XDG_CURRENT_DESKTOP for onlyShowIn etc),
  probably taking the last value in the string would get the desired
  result of Unity vs GNOME3 behaviour

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Mar  9 15:04:36 2016
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to xenial on 2015-11-28 (102 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1554878/+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 1629288] Re: package python-appindicator 12.10.1+13.10.20130920-0ubuntu4.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-10-02 Thread Apport retracing service 
*** This bug is a duplicate of bug 1629297 ***
https://bugs.launchpad.net/bugs/1629297

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1629297
   package python-appindicator 12.10.1+13.10.20130920-0ubuntu4.1 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1

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

Title:
  package python-appindicator 12.10.1+13.10.20130920-0ubuntu4.1 failed
  to install/upgrade: subprocess new pre-removal script returned error
  exit status 1

Status in libappindicator package in Ubuntu:
  New

Bug description:
  python failed upgrade 14 to 16.  I am an end user and appreciate all
  help.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-appindicator 12.10.1+13.10.20130920-0ubuntu4.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 29 17:49:08 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2010-11-28 (2133 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libappindicator
  Title: package python-appindicator 12.10.1+13.10.20130920-0ubuntu4.1 failed 
to install/upgrade: subprocess new pre-removal script returned error exit 
status 1
  UpgradeStatus: Upgraded to xenial on 2016-09-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1629288/+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 1629288] Re: package python-appindicator 12.10.1+13.10.20130920-0ubuntu4.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-10-02 Thread Emily Ratliff 
*** This bug is a duplicate of bug 1629297 ***
https://bugs.launchpad.net/bugs/1629297

** Information type changed from Private Security to Public

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

Title:
  package python-appindicator 12.10.1+13.10.20130920-0ubuntu4.1 failed
  to install/upgrade: subprocess new pre-removal script returned error
  exit status 1

Status in libappindicator package in Ubuntu:
  New

Bug description:
  python failed upgrade 14 to 16.  I am an end user and appreciate all
  help.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-appindicator 12.10.1+13.10.20130920-0ubuntu4.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 29 17:49:08 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2010-11-28 (2133 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libappindicator
  Title: package python-appindicator 12.10.1+13.10.20130920-0ubuntu4.1 failed 
to install/upgrade: subprocess new pre-removal script returned error exit 
status 1
  UpgradeStatus: Upgraded to xenial on 2016-09-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1629288/+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 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates

2016-10-02 Thread Iain Lane 
On Sun, Oct 02, 2016 at 10:27:43AM -, Martin Pitt wrote:
> Iain Lane [2016-10-01 19:26 -]:
> > Hmm. Maybe this is saying that we should bind ubuntu-session.target to
> > something else - like unity7? You can't log in again with an active
> > unity7, so in theory (if stop is propagated down to graphical-session
> > and graphical-session-pre) there wouldn't be a need to stop/restart in
> > the script since everything would be stopped by definition if you're
> > trying to start unity7 again.
> 
> I like that idea in principle -- picking a session leader which
> automatically dies when X goes away would be a lot simpler indeed (and
> gnome-session does not do that). I picked gnome-session as the session
> leader because it traditionally has had that role, and it still has
> the API for logging out.
> 
> Another point is that we want to make unity/compiz robust against
> crashes and provide auto-restart -- if it becomes the session leader,
> then the whole session will go down on any crash. So picking
> unity7.service in particular is a bad choice.

It would be good if it were possible to say that the BindsTo shouldn't
trigger the target to stop until after systemd gives up restarting the
unit.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  unity-gtk-module.service is racy; session services don't stop if
  session terminates

Status in gnome-session package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released

Bug description:
  Sometimes on session start unity-gtk-module.service runs too late or
  something, and $GTK_MODULES does not include "unity". It is in
  "systemctl --user show-environment" but not in a terminal bash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+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 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates

2016-10-02 Thread Iain Lane 
On Sun, Oct 02, 2016 at 08:39:01AM -, Martin Pitt wrote:
> > If you ever end up stopping gnome-keyring from within a new session
> then its ExecStopPost kills the upstart session of this new one that we
> are starting up, *not* the previous one that it was started up under.
> 
> I assume you meant to say "gnome-session.service" here, not keyring (as
> its ExecStopPost is harmless). gnome-session is the session leader, so
> stopping it by definition means to end the current session.

Yes I did. But the problem is that it is *not* always stopped when the
session dies, so it is a bad choice of leader while that is true.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  unity-gtk-module.service is racy; session services don't stop if
  session terminates

Status in gnome-session package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released

Bug description:
  Sometimes on session start unity-gtk-module.service runs too late or
  something, and $GTK_MODULES does not include "unity". It is in
  "systemctl --user show-environment" but not in a terminal bash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+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 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates

2016-10-02 Thread Martin Pitt 
Iain Lane [2016-10-01 19:26 -]:
> Hmm. Maybe this is saying that we should bind ubuntu-session.target to
> something else - like unity7? You can't log in again with an active
> unity7, so in theory (if stop is propagated down to graphical-session
> and graphical-session-pre) there wouldn't be a need to stop/restart in
> the script since everything would be stopped by definition if you're
> trying to start unity7 again.

I like that idea in principle -- picking a session leader which
automatically dies when X goes away would be a lot simpler indeed (and
gnome-session does not do that). I picked gnome-session as the session
leader because it traditionally has had that role, and it still has
the API for logging out.

Another point is that we want to make unity/compiz robust against
crashes and provide auto-restart -- if it becomes the session leader,
then the whole session will go down on any crash. So picking
unity7.service in particular is a bad choice.

Of course over time we want to get rid of gnome-session -- we don't
need its service management any more, thus the only thing it provides
is that D-Bus API for logout/user switching etc. This can/should be
replaced with calls to stop units or calls to the DM, and then we
should actually be able to completely drop that concept of a "session
leader" (or rather, foo-session.target then *is* the leader, as we
really intend). But we aren't there yet, so until then I think
BindsTo=gnome-session.service is still conceptually correct IMHO.

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

Title:
  unity-gtk-module.service is racy; session services don't stop if
  session terminates

Status in gnome-session package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released

Bug description:
  Sometimes on session start unity-gtk-module.service runs too late or
  something, and $GTK_MODULES does not include "unity". It is in
  "systemctl --user show-environment" but not in a terminal bash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+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 1629580] Re: firefox keyboard not showing up (gmail, ...)

2016-10-02 Thread Man usashi 
sorry, this bug has nothing to do here, but don't know how to remove it
now...

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

Title:
  firefox keyboard not showing up (gmail,...)

Status in indicator-power package in Ubuntu:
  New

Bug description:
  Hello,

  I'm using Ubuntu 15.04 (OTA13) on my Aquarius M10.
  Now the keyboard shows up at least in google and other websites, but I can't 
connect to my gmail account, because the keyboard doesn't show up when the 
password of the gmail account is asked. I was able to write my email account 
with the kb, but not the password (because no kb).
  This might also appear at other text box input, but I don't have any other 
proof. Firefox 44 is installed.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1629580/+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 1629637] Re: package libaccountsservice0:i386 0.6.40-2ubuntu11.2 failed to install/upgrade: Pakiet jest w złym stanie - powinien zostać zainstalowany ponownie przed próbą jego skon

2016-10-02 Thread Jakub Jankiewicz 
I've solve the issue by removing the package using:

sudo dpkg -r --force-all libaccountsservice0 accountsservice indicator-
messages indicator-sound

and then running

sudo apt-get -f install

** Changed in: accountsservice (Ubuntu)
   Status: New => Invalid

** Summary changed:

- package libaccountsservice0:i386 0.6.40-2ubuntu11.2 failed to 
install/upgrade: Pakiet jest w złym stanie - powinien zostać zainstalowany 
ponownie  przed próbą jego skonfigurowania.
+ package libaccountsservice0:i386 0.6.40-2ubuntu11.2 failed to 
install/upgrade: The package is in poor condition - it should be installed 
again before attempting to set up.

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

Title:
  package libaccountsservice0:i386 0.6.40-2ubuntu11.2 failed to
  install/upgrade: The package is in poor condition - it should be
  installed again before attempting to set up.

Status in accountsservice package in Ubuntu:
  Invalid

Bug description:
  I've got error when installing claws-mail plugins I got this message
  from synaptic (translated from Polish using google translate):

  Errors were encountered while processing:
    libaccountsservice0 i386
    accountsservice
  E: Sub-process /usr/bin/dpkg  returned an error code (1)
  Failed to install package. An attempt to return to the previous state:
  dpkg: error processing package libaccountsservice0: i386 (--configure):
    The package is in poor condition - it should be reinstalled
    before attempting to set up.
  dpkg: dependency problems prevent configuration package accountsservice:
    accountsservice depends libaccountsservice0 (= 0.6.40-2ubuntu11.2); however:
     Package libaccountsservice0 i386 is not configured yet.

  dpkg: error processing package accountsservice (--configure):
    dependency problems - leaving unconfigured

  I've try to execute `sudo dpkg --configure -a` also again `sudo apt
  install accountsservice` after installation but that didn't work.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libaccountsservice0:i386 0.6.40-2ubuntu11.2
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Sun Oct  2 10:11:45 2016
  ErrorMessage: Pakiet jest w złym stanie - powinien zostać zainstalowany 
ponownie  przed próbą jego skonfigurowania.
  InstallationDate: Installed on 2016-10-01 (0 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: accountsservice
  Title: package libaccountsservice0:i386 0.6.40-2ubuntu11.2 failed to 
install/upgrade: Pakiet jest w złym stanie - powinien zostać zainstalowany 
ponownie  przed próbą jego skonfigurowania.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1629637/+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 1629637] [NEW] package libaccountsservice0:i386 0.6.40-2ubuntu11.2 failed to install/upgrade: Pakiet jest w złym stanie - powinien zostać zainstalowany ponownie przed próbą jego sk

2016-10-02 Thread Jakub Jankiewicz 
Public bug reported:

I've got error when installing claws-mail plugins I got this message
from synaptic (translated from Polish using google translate):

Errors were encountered while processing:
  libaccountsservice0 i386
  accountsservice
E: Sub-process /usr/bin/dpkg  returned an error code (1)
Failed to install package. An attempt to return to the previous state:
dpkg: error processing package libaccountsservice0: i386 (--configure):
  The package is in poor condition - it should be reinstalled
  before attempting to set up.
dpkg: dependency problems prevent configuration package accountsservice:
  accountsservice depends libaccountsservice0 (= 0.6.40-2ubuntu11.2); however:
   Package libaccountsservice0 i386 is not configured yet.

dpkg: error processing package accountsservice (--configure):
  dependency problems - leaving unconfigured

I've try to execute `sudo dpkg --configure -a` also again `sudo apt
install accountsservice` after installation but that didn't work.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libaccountsservice0:i386 0.6.40-2ubuntu11.2
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic i686
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
Date: Sun Oct  2 10:11:45 2016
ErrorMessage: Pakiet jest w złym stanie - powinien zostać zainstalowany 
ponownie  przed próbą jego skonfigurowania.
InstallationDate: Installed on 2016-10-01 (0 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: accountsservice
Title: package libaccountsservice0:i386 0.6.40-2ubuntu11.2 failed to 
install/upgrade: Pakiet jest w złym stanie - powinien zostać zainstalowany 
ponownie  przed próbą jego skonfigurowania.
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package libaccountsservice0:i386 0.6.40-2ubuntu11.2 failed to
  install/upgrade: Pakiet jest w złym stanie - powinien zostać
  zainstalowany ponownie  przed próbą jego skonfigurowania.

Status in accountsservice package in Ubuntu:
  New

Bug description:
  I've got error when installing claws-mail plugins I got this message
  from synaptic (translated from Polish using google translate):

  Errors were encountered while processing:
    libaccountsservice0 i386
    accountsservice
  E: Sub-process /usr/bin/dpkg  returned an error code (1)
  Failed to install package. An attempt to return to the previous state:
  dpkg: error processing package libaccountsservice0: i386 (--configure):
    The package is in poor condition - it should be reinstalled
    before attempting to set up.
  dpkg: dependency problems prevent configuration package accountsservice:
    accountsservice depends libaccountsservice0 (= 0.6.40-2ubuntu11.2); however:
     Package libaccountsservice0 i386 is not configured yet.

  dpkg: error processing package accountsservice (--configure):
    dependency problems - leaving unconfigured

  I've try to execute `sudo dpkg --configure -a` also again `sudo apt
  install accountsservice` after installation but that didn't work.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libaccountsservice0:i386 0.6.40-2ubuntu11.2
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Sun Oct  2 10:11:45 2016
  ErrorMessage: Pakiet jest w złym stanie - powinien zostać zainstalowany 
ponownie  przed próbą jego skonfigurowania.
  InstallationDate: Installed on 2016-10-01 (0 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: accountsservice
  Title: package libaccountsservice0:i386 0.6.40-2ubuntu11.2 failed to 
install/upgrade: Pakiet jest w złym stanie - powinien zostać zainstalowany 
ponownie  przed próbą jego skonfigurowania.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1629637/+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 1328309] Re: Power indicator is hidden when only a secondary battery (such as mouse and keyboard) are discharging

2016-10-02 Thread David Gámiz Jiménez 
For same. In Ubuntu 16.04 64bits. Not show indicator-power icon but show
in unity-control-panel section.

** Tags added: 16.04

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

Title:
  Power indicator is hidden when only a secondary battery (such as mouse
  and keyboard) are discharging

Status in indicator-power:
  New
Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  I've wireless keyboard and mouse and I've set the "Show battery status
  on the menu bar" to "When battery is charging/in use".

  In this case, when my mouse and keyboard batteries are discharging the
  indicator should show, but without listing the not-charging devices
  (such as my notebook battery).

  For the same reason, when using a desktop computer or a notebook
  without battery, the indicator won't ever show the state of the other
  battery powered devices available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-power/+bug/1328309/+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 1328309] Re: Power indicator is hidden when only a secondary battery (such as mouse and keyboard) are discharging

2016-10-02 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Power indicator is hidden when only a secondary battery (such as mouse
  and keyboard) are discharging

Status in indicator-power:
  New
Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  I've wireless keyboard and mouse and I've set the "Show battery status
  on the menu bar" to "When battery is charging/in use".

  In this case, when my mouse and keyboard batteries are discharging the
  indicator should show, but without listing the not-charging devices
  (such as my notebook battery).

  For the same reason, when using a desktop computer or a notebook
  without battery, the indicator won't ever show the state of the other
  battery powered devices available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-power/+bug/1328309/+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 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates

2016-10-02 Thread Martin Pitt 
> If you ever end up stopping gnome-keyring from within a new session
then its ExecStopPost kills the upstart session of this new one that we
are starting up, *not* the previous one that it was started up under.

I assume you meant to say "gnome-session.service" here, not keyring (as
its ExecStopPost is harmless). gnome-session is the session leader, so
stopping it by definition means to end the current session.

I now cleaned up the transaction handling to avoid having to wait for
"deactivating" units after *-session.target ends (both at the top of the
script to clean up lingering sessions and the end to cleanly exit
without prematurely stopping X).

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

Title:
  unity-gtk-module.service is racy; session services don't stop if
  session terminates

Status in gnome-session package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released

Bug description:
  Sometimes on session start unity-gtk-module.service runs too late or
  something, and $GTK_MODULES does not include "unity". It is in
  "systemctl --user show-environment" but not in a terminal bash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+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 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service

2016-10-02 Thread funkoolow 
solution from geek.de.nz worked perfectly for me, i'm on ubuntu 16.04
upgraded from 14.04

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

Title:
  [7.287663] systemd-logind[1057]: Failed to start unit
  user@126.service: Unknown unit: user@126.service

Status in NULL Project:
  Invalid
Status in systemd package in Ubuntu:
  Won't Fix
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Utopic:
  Won't Fix
Status in systemd-shim source package in Utopic:
  Won't Fix
Status in systemd-shim package in Debian:
  New

Bug description:
  [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: 
Unknown unit: user@126.service
  [7.287677] systemd-logind[1057]: Failed to start user service: Unknown 
unit: user@126.service
  [7.293871] systemd-logind[1057]: New session c1 of user lightdm.
  [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to 
/run/user/126/X11-display.
  [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team
  [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
  [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready
  [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec
  [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3)
  [9.920181] wlan0: authenticated
  [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3)
  [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 
status=0 aid=2)
  [9.927753] wlan0: associated
  [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [   12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope
  [   12.677122] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc1_2escope
  [   12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: 
Unknown unit: user@1000.service
  [   12.683912] systemd-logind[1057]: Failed to start user service: Unknown 
unit: user@1000.service
  [   12.685157] systemd-logind[1057]: New session c2 of user caravena.
  [   12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to 
/run/user/1000/X11-display.
  [  234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope
  [  234.494478] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc2_2escope
  [  235.514349] systemd-logind[1057]: New session c3 of user lightdm.
  [  244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope
  [  244.245923] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc3_2escope

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-7ubuntu4 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Aug 20 18:26:06 2014
  InstallationDate: Installed on 2014-04-27 (115 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1359439/+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 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates

2016-10-02 Thread Launchpad Bug Tracker 
This bug was fixed in the package upstart - 1.13.2-0ubuntu32

---
upstart (1.13.2-0ubuntu32) yakkety; urgency=medium

  * debian/systemd-graphical-session.conf: Stop any lingering active units
when logging in. (LP: #1618886)
  * debian/control: Break old versions of gnome-session, which take the
session down when stopped in the above way.

 -- Iain Lane   Tue, 27 Sep 2016 17:47:27 +0100

** Changed in: upstart (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  unity-gtk-module.service is racy; session services don't stop if
  session terminates

Status in gnome-session package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released

Bug description:
  Sometimes on session start unity-gtk-module.service runs too late or
  something, and $GTK_MODULES does not include "unity". It is in
  "systemctl --user show-environment" but not in a terminal bash.

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