[Dx-packages] [Bug 2057710] Re: Accountsservice FTBFS on noble

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Accountsservice FTBFS on noble

Status in accountsservice package in Ubuntu:
  New

Bug description:
   package version 23.13.9-2ubuntu FTBFS on all architectures.

  This is because of an invalid test

  This has been resolved upstream - see the attached debdiff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2057710/+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 2024182] Re: GHSL-2023-139: use-after-free in user.c

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  GHSL-2023-139: use-after-free in user.c

Status in accountsservice package in Ubuntu:
  In Progress
Status in accountsservice source package in Focal:
  Fix Released
Status in accountsservice source package in Jammy:
  Fix Released
Status in accountsservice source package in Kinetic:
  Fix Released
Status in accountsservice source package in Lunar:
  Fix Released
Status in accountsservice source package in Mantic:
  In Progress

Bug description:
  # GitHub Security Lab (GHSL) Vulnerability Report, accountsservice:
  `GHSL-2023-139`

  The [GitHub Security Lab](https://securitylab.github.com) team has
  identified a potential security vulnerability in
  [accountsservice](https://code.launchpad.net/ubuntu/+source/accountsservice).

  We are committed to working with you to help resolve this issue. In
  this report you will find everything you need to effectively
  coordinate a resolution of this issue with the GHSL team.

  If at any point you have concerns or questions about this process,
  please do not hesitate to reach out to us at `security...@github.com`
  (please include `GHSL-2023-139` as a reference).

  If you are _NOT_ the correct point of contact for this report, please
  let us know!

  ## Summary

  An unprivileged local attacker can trigger a use-after-free
  vulnerability in accountsservice by sending a D-Bus message to the
  accounts-daemon process.

  ## Product

  accountsservice

  ## Tested Version

  
[22.08.8-1ubuntu7](https://launchpad.net/ubuntu/+source/accountsservice/22.08.8-1ubuntu7)

  The bug is easier to observe on Ubuntu 23.04 than on Ubuntu 22.04 LTS,
  but it is present on both.

  ## Details

  ### Use-after-free when `throw_error` is called (`GHSL-2023-139`)

  After receiving a D-Bus [method
  call](https://dbus.freedesktop.org/doc/dbus-
  specification.html#message-protocol-types), a D-Bus server is expected
  to send either a `METHOD_RETURN` or a `ERROR` message back to the
  client, _but not both_. This is done incorrectly in several places in
  accountsservice. For example, in
  
[`user_change_language_authorized_cb`](https://git.launchpad.net/ubuntu/+source/accountsservice/tree/debian/patches/0010-set-
  language.patch?h=import/22.08.8-1ubuntu7#n427):

  ```c
  static void
  user_change_language_authorized_cb (Daemon*daemon,
  User  *user,
  GDBusMethodInvocation *context,
  gpointer   data)

  {
  const gchar *language = data;

  if (!user_HOME_available (user)) {

  /* SetLanguage was probably called from a login greeter,
 and HOME not mounted and/or not decrypted.
 Hence don't save anything, or else accountsservice
 and ~/.pam_environment would become out of sync. */
  throw_error (context, ERROR_FAILED, "not access to HOME yet 
so language not saved");  <= 1
  goto out;
  }

  

  out:
  accounts_user_complete_set_language (ACCOUNTS_USER (user), context);  
<= 2
  }
  ```

  If `user_HOME_available` returns an error, then `throw_error` is
  called at 1 to send an `ERROR` message, but a regular `METHOD_RETURN`
  is also sent at 2. This is incorrect D-Bus protocol, but the more
  serious problem is that it causes a use-after-free because both
  `throw_error` and `accounts_user_complete_set_language` decrease the
  reference count on `context`. In other words, `context` is freed by
  `throw_error` and a UAF occurs in
  `accounts_user_complete_set_language`.

  An attacker can trigger the bug above by causing `user_HOME_available`
  to fail, which they can do by deleting all the files from their home
  directory. But there are other incorrect uses of `throw_error` in
  `user.c` which are less inconvenient to trigger. For example, this
  command triggers a call to `throw_error` in `user_update_environment`
  due to the invalid characters in the string.

  ```bash
  dbus-send --system --print-reply --dest=org.freedesktop.Accounts 
/org/freedesktop/Accounts/User`id -u` org.freedesktop.Accounts.User.SetLanguage 
string:'**'
  ```

  On Ubuntu 23.04, the above command causes `accounts-daemon` to crash
  with a `SIGSEGV`. But on Ubuntu 22.04 LTS it doesn't cause any visible
  harm. The difference is due to a recent [change in
  
GLib's](https://gitlab.gnome.org/GNOME/glib/-/commit/69e9ba80e2f4d2061a1a68d72bae1c32c1e4f8fa)
  memory allocation: older versions of GLib used the "slice" allocator,
  but newer version uses the system allocator. The system allocator
  trashes the memory when it's freed in a way that causes the use-after-
  

[Dx-packages] [Bug 1910521] Re: libappindicator breaks left-mouse actions for most applications

[Ubuntu Foundations Team Bug Bot]

The attachment "Add support for Activate method to AppIndicator" seems
to be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  libappindicator breaks left-mouse actions for most applications

Status in libappindicator package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  because GTK will drop tray icon support in version 4, many projects
  switch to libappindicator instead. Some are network-manager-applet,
  blueman-tray and electron (affecting all electron apps). The latter 2
  automatically use libappindicator if it's available in the system.

  For most applications, with libappindicator the tray icon behavior is
  broken (at least on archlinux with xfce4 and libappindicator-gtk3):

  * left mouse button triggers the context menu rather than the 
left-mouse-button action
  * the context menu is located beneath the mouse button, so when the mouse is 
released, the action is performed (in most cases "exit application").

  Since the web is full of issue reports about this, I'm, pretty sure
  it's an issue in libappindicator itself than in every single
  application that uses it.

  IMO this is a critical issue, especially for a library that provides
  tray support to applications.

  Kind regards,
  Michael.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1910521/+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 1974250] Re: ~/.pam_environment gets created as owned by root

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  ~/.pam_environment gets created as owned by root

Status in accountsservice package in Ubuntu:
  Confirmed
Status in accountsservice source package in Jammy:
  Fix Released
Status in accountsservice source package in Kinetic:
  Confirmed

Bug description:
  Something has happened lately with accountsservice, which makes it act
  as root instead of the current user when creating ~/.pam_environment.
  The very old bug #904395 comes to mind, and this smells a security
  issue.

  The function which is supposed to prevent this behavior is here:

  https://salsa.debian.org/freedesktop-
  team/accountsservice/-/blob/ubuntu/debian/patches/0010-set-
  language.patch#L75

  Haven't investigated further yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1974250/+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 1575655] Re: the network indicator shows the wrong status

[Ubuntu Foundations Team Bug Bot]

The attachment "Ubuntu Network Manger issue Showing "?"" seems to be a
patch.  If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  the network indicator shows the wrong status

Status in indicator-applet package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  indicator-applet:
Installed: (none)
Candidate: 12.10.2+15.04.20141127.2-0ubuntu1
Version table:
   12.10.2+15.04.20141127.2-0ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  The network indicator sometimes shows the icon for wired connections
  and sometimes claims wifi without connection even though I'm
  consistently connected over wifi. I don't mean to say that it switches
  between these two or that always is wrong. But sometimes my connected
  to wifi symbol changes to wired. Other times it will change to the no
  connection wifi. The info is correct on boot, but switches over time,
  possibly after suspension.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: indicator-applet (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 27 14:54:42 2016
  InstallationDate: Installed on 2016-04-08 (18 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  SourcePackage: indicator-applet
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1575655/+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 1867996] Re: Segfault in app_indicator_set_icon_full [patch attached]

[Ubuntu Foundations Team Bug Bot]

The attachment "Stop passing in undeclared boolean vararg" seems to be a
patch.  If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Segfault in app_indicator_set_icon_full [patch attached]

Status in libappindicator package in Ubuntu:
  New
Status in libappindicator package in Arch Linux:
  New

Bug description:
  Discord and several other applications using libappindicator are
  widely reported to have been crashing for several years. See:
  https://github.com/flathub/com.discordapp.Discord/issues/30 (and
  others)

  This is the backtrace:
  (gdb) bt full
  #0  0x7fe1d5d2e00e in  () at /app/lib/libappindicator.so
  #1  0x7fe1f5a6f3c5 in g_closure_invoke () at /lib/libgobject-2.0.so.0
  #2  0x7fe1f5a813d2 in  () at /lib/libgobject-2.0.so.0
  #3  0x7fe1f5a8a02c in g_signal_emit_valist () at /lib/libgobject-2.0.so.0
  #4  0x7fe1f5a8a40f in g_signal_emit () at /lib/libgobject-2.0.so.0
  #5  0x7fe1d5d2ed4f in app_indicator_set_icon_full () at 
/app/lib/libappindicator.so
  #6  0x0077851a in  ()
  #7  0x01de7123 in  ()
  #8  0x01e4bd4e in  ()
  #9  0x01e6e34c in  ()
  #10 0x01e6e668 in  ()
  #11 0x01e6e9cb in  ()
  #12 0x01df971a in  ()
  #13 0x7fe1f354b1c7 in g_main_context_dispatch () at /lib/libglib-2.0.so.0
  #14 0x7fe1f354b430 in  () at /lib/libglib-2.0.so.0
  #15 0x7fe1f354b4dc in g_main_context_iteration () at /lib/libglib-2.0.so.0
  #16 0x01df9606 in  ()
  #17 0x01e6e0e7 in  ()
  #18 0x01e29570 in  ()
  #19 0x00c37ec8 in  ()
  #20 0x00c37d15 in  ()
  #21 0x00c1da7d in  ()
  #22 0x00a9282e in  ()
  #23 0x007892d4 in  ()
  #24 0x007896e0 in  ()
  #25 0x03b830a3 in main ()

  Happens in all versions of libappindicator built from latest sources
  available on launchpad.

  I ran into the issue yesterday when installing Discord for the first
  time. I have tracked the problem down to libappindicator passing in an
  extra vararg item to g_signal_emit that the signal's definition in
  libappindicator was not declaring, causing the crash you see above in
  gobject's g_signal dispatch machinery.

  Patch is attached.

  I am presuming this is 'upstream' for libappindicator, whatever that
  may mean for what appears to be an unmaintained project. If it is not,
  and since it is an Ubuntu/Canonical-sourced project originally, I
  respectfully request that you assist in upstreaming it since this bug
  is causing severe breakage for users across all distros.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1867996/+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 1844158] Re: FTBFS using vala-0.46.1

[Ubuntu Foundations Team Bug Bot]

The attachment "Fix for FTB" seems to be a patch.  If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  FTBFS using vala-0.46.1

Status in libunity package in Ubuntu:
  Confirmed
Status in libunity package in Fedora:
  Confirmed

Bug description:
  Trying to build on/for fedora 31+ fails with the following errors:

  make[2]: Entering directory '/builddir/build/BUILD/libunity-7.1.4/src'
  /usr/bin/valac -C -H unity.h -d . --gir=Unity-7.0.gir --library unity 
--internal-vapi=unity-internal.vapi --internal-header=unity-internal.h 
--target-glib=2.32 --thread --use-header --vapidir ../vapi --vapidir 
../protocol --vapidir . --pkg unity-protocol --pkg config --pkg unity-trace 
--pkg glib-2.0 --pkg gmodule-2.0 --pkg gobject-2.0 --pkg gio-2.0 --pkg 
gio-unix-2.0 --pkg dee-1.0 --pkg Dbusmenu-0.4  unity-appinfo-manager.vala 
unity-icon.vala unity-inspector.vala unity-io.vala unity-launcher.vala 
unity-category.vala unity-filters.vala unity-preferences-manager.vala 
unity-merge-strategy.vala unity-models.vala unity-search.vala 
unity-synchronizer.vala unity-previews.vala unity-result-activation.vala 
unity-scope-interface.vala unity-scope-dbus-connector.vala 
unity-scope-dbus-impl.vala unity-scope-channel.vala unity-deprecated-scope.vala 
unity-deprecated-scope-impl.vala unity-aggregator-scope.vala 
unity-aggregator-scope-private.vala unity-master-scope.vala 
unity-simple-scope.vala unity-scope-loader.vala unity-scope-tracker.vala 
unity-sound-menu.vala unity-sound-menu-mpris.vala unity-utils.vala
  Command-line option `--thread` is deprecated and will be ignored
  Compilation failed: 2 error(s), 0 warning(s)
  BUILDSTDERR: unity-deprecated-scope.vala:64.3-64.28: error: Creation method 
of abstract class cannot be public.
  BUILDSTDERR:   public DeprecatedScopeBase (string dbus_path_, string id_)
  BUILDSTDERR:   ^^
  BUILDSTDERR: unity-aggregator-scope.vala:54.3-54.24: error: Creation method 
of abstract class cannot be public.
  BUILDSTDERR:   public AggregatorScope (string dbus_path_, string id_, 
MergeMode merge_mode = AggregatorScope.MergeMode.OWNER_SCOPE, bool 
proxy_filter_hints = false)
  BUILDSTDERR:   ^^
  BUILDSTDERR: make[2]: *** [Makefile:1389: libunity_la_vala.stamp] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1844158/+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 1820510] Re: Build errors against recent valac

[Ubuntu Foundations Team Bug Bot]

The attachment "0001-Fix-build-errors-but-not-warnings-with-
vala-044.patch" seems to be a patch.  If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Build errors against recent valac

Status in libunity:
  New
Status in libunity package in Ubuntu:
  New

Bug description:
  I'd like to build Geary with support for Unity indicators in the Geary
  Flatpak package, but it's failing to build against recent valac:

  mjog@blanchefort:~/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig$ vala 
--version
  Vala 0.44.0
  mjog@blanchefort:~/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig$ make
  make  all-recursive
  make[1]: Entering directory 
'/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig'
  Making all in data
  make[2]: Entering directory 
'/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/data'
ITMRG  com.canonical.Unity.Lenses.gschema.xml
GEN  com.canonical.Unity.Lenses.gschema.valid
  make[2]: Leaving directory 
'/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/data'
  Making all in protocol
  make[2]: Entering directory 
'/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/protocol'
GEN  libunity_protocol_private_la_vala.stamp
  Command-line option `--thread` is deprecated and will be ignored
  protocol-scope-discovery.vala:24.3-24.40: warning: the modifier `static' is 
not applicable to constants
private static const string SCOPES_DIR = "unity/scopes";
^^
  protocol-scope-discovery.vala:190.5-190.43: warning: the modifier `static' is 
not applicable to constants
  private static const string SCOPE_GROUP = "Scope";
  ^^^
  protocol-scope-discovery.vala:191.5-191.45: warning: the modifier `static' is 
not applicable to constants
  private static const string DESKTOP_GROUP = "Desktop Entry";
  ^
  protocol-scope-discovery.vala:902.5-902.49: warning: the modifier `static' is 
not applicable to constants
  private static const string SCOPE_GROUP_GROUP = "Scope Group";
  ^
  protocol-preview-player.vala:41.3-41.46: warning: the modifier `static' is 
not applicable to constants
static const string PREVIEW_PLAYER_DBUS_NAME = 
"com.canonical.Unity.Lens.Music.PreviewPlayer";

  protocol-preview-player.vala:42.3-42.46: warning: the modifier `static' is 
not applicable to constants
static const string PREVIEW_PLAYER_DBUS_PATH = 
"/com/canonical/Unity/Lens/Music/PreviewPlayer";

  protocol-scope-interface.vala:117.3-117.51: warning: DBus methods are 
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async ActivationReplyRaw activate (
^
  protocol-scope-interface.vala:124.3-124.57: warning: DBus methods are 
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async HashTable search (
^^^
  protocol-scope-interface.vala:134.7-134.46: error: Synchronous out-parameters 
are not supported in async methods
out HashTable out_hints,

  protocol-scope-interface.vala:130.3-130.43: warning: DBus methods are 
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async string open_channel (
^
  protocol-scope-interface.vala:137.3-137.42: warning: DBus methods are 
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void close_channel (

  protocol-scope-interface.vala:142.3-142.63: warning: DBus methods are 
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async HashTable push_results (
^
  protocol-scope-interface.vala:151.3-151.42: warning: DBus methods are 
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void set_view_type (uint view_type) throws IOError;

  unity-scope-proxy-remote.vala:379.12-379.21: error: The name `channel_id' 
does not exist in the context of 

[Dx-packages] [Bug 1815348] Re: package libappindicator0.1-cil 12.10.1+16.04.20170215-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: libappindicator (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  package libappindicator0.1-cil 12.10.1+16.04.20170215-0ubuntu1 failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 134

Status in libappindicator package in Ubuntu:
  Invalid

Bug description:
  l'errore compare all'avvio di ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libappindicator0.1-cil 12.10.1+16.04.20170215-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sun Jan 20 19:33:19 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 134
  InstallationDate: Installed on 2013-11-03 (1925 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.29
  SourcePackage: libappindicator
  Title: package libappindicator0.1-cil 12.10.1+16.04.20170215-0ubuntu1 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 134
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1815348/+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 1805418] Re: Update pre-populator patch with correct desktop names

[Ubuntu Foundations Team Bug Bot]

The attachment "A small patch to fix pre-populator patch" seems to be a
patch.  If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Update pre-populator patch with correct desktop names

Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  Use correct desktop names for totem, gedit and gnome-calculator.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1805418/+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 725435] Re: notify-osd a memory hog (memory leak?)

[Ubuntu Foundations Team Bug Bot]

The attachment "Patch fixing the shutdown limit being exceeded" seems to
be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: 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/725435

Title:
  notify-osd a memory hog (memory leak?)

Status in notify-osd package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: notify-osd

  Noticed this today on my lucid box in top:
  2647 myaccount  20   0 1196m 595m 3528 S0 29.7   1:09.68 notify-osd

  I don't think a simple notifcation daemon should suck up more than a
  Gig of memory of which half is real memory.  It's the first time I
  noticed this.  I don't have too much information at this point.

  $ dpkg -l notify-osd*
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name  Version 
  Description
  
+++-=-=-==
  ii  notify-osd0.9.29-0ubuntu2 
  daemon that displays passive pop-up notifications
  ii  notify-osd-icons  0.6 
  Notify-OSD icons

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/725435/+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 1789502] Re: Update to 0.6.50

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Update to 0.6.50

Status in accountsservice package in Ubuntu:
  In Progress

Bug description:
  The upstream changes are non trivial and there is work to update the
  patches but that would be useful to do

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1792786] Re: package humanity-icon-theme 0.6.15 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: corrupted-package

** Changed in: humanity-icon-theme (Ubuntu)
   Status: New => Invalid

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

Title:
  package humanity-icon-theme 0.6.15 failed to install/upgrade:
  corrupted filesystem tarfile - corrupted package archive

Status in humanity-icon-theme package in Ubuntu:
  Invalid

Bug description:
  During the updating Ubuntu 1- to 18 beaver,
  bests regards

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: humanity-icon-theme 0.6.15
  ProcVersionSignature: Ubuntu 4.15.0-35.38-generic 4.15.18
  Uname: Linux 4.15.0-35-generic i686
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: i386
  Date: Sun Sep 16 10:12:10 2018
  ErrorMessage: corrupted filesystem tarfile - corrupted package archive
  InstallationDate: Installed on 2013-07-10 (1894 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary 
20120426-12:41
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: humanity-icon-theme
  Title: package humanity-icon-theme 0.6.15 failed to install/upgrade: 
corrupted filesystem tarfile - corrupted package archive
  UpgradeStatus: Upgraded to bionic on 2018-09-16 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1792786/+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 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)

[Ubuntu Foundations Team Bug Bot]

The attachment "IMG_20170914_192319.jpg" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  System users appears in Ligthdm and user switcher (Accountsservice has
  no filter for shell types)

Status in accountsservice package in Ubuntu:
  Confirmed
Status in base-passwd package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Confirmed
Status in ifmail package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in netqmail package in Ubuntu:
  Confirmed
Status in sddm package in Ubuntu:
  Fix Released

Bug description:
  "Technical" user libvirt Qemu appears in the list of user in Ligthdm,
  among the real regular users. It probably shouldn't

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libvirt-bin 2.5.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 22:09:24 2017
  InstallationDate: Installed on 2017-02-01 (21 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  KernLog:
   
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1667113/+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 1699216] Re: Encrypted home support

[Ubuntu Foundations Team Bug Bot]

The attachment "encrypted_home.patch (accountsservice)" seems to be a
patch.  If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Encrypted home support

Status in accountsservice package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-initial-setup package in Ubuntu:
  Confirmed

Bug description:
  In the CreateUser D-bus call, allow the home directory of the new user
  to be encrypted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+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 1666495] Re: [Zesty] No default apps shown on first start in kvm oem end user

[Ubuntu Foundations Team Bug Bot]

The attachment "zeitgeist-service-optional-prestart.patch" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  [Zesty] No default apps shown on first start in kvm oem end user

Status in unity-lens-applications:
  Invalid
Status in zeitgeist package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  1. Install the latest iso in kvm
  2. Click on Ubuntu button

  EXPECTED:
  I expect to see Thunderbird, rhythmbox, totem, etc.  There are normally 5 
default apps shown.

  ACTUAL:
  I get what you see in the attached screenshot.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-02-21 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170221)
  Package: unity-lens-applications 7.1.0+16.10.20160927-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Tags:  zesty
  Uname: Linux 4.10.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-lens-applications/+bug/1666495/+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 1665902] Re: Update zeitgeist to 1.0

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Update zeitgeist to 1.0

Status in zeitgeist package in Ubuntu:
  Triaged

Bug description:
  Zeitgeist 1.0 has been released!

  https://launchpad.net/zeitgeist/1.0/1.0

   - Drop dependency on gnome-common and intltool
   - Use GNU gettext only
   - Fix some valac warnings
   - Use $PYTHON to check for rdflib
   - Install zeitgeist-fts to pkglibexecdir rather than
 libexecdir
   - Use correct names for D-Bus service files
   - Add systemd user service for each D-Bus session service
   - Fix bash auto-completions script
   - Add --vacuum option to Daemon to perform VACUUM SQLite
 database

  Libzeitgeist:
   - Ensure the log mainloop uses the current thread's context
 when waiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1665902/+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 1318321] Re: "the cache has no package" error when wine update is available

[Ubuntu Foundations Team Bug Bot]

The attachment "fix_multiarch_check.patch" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  "the cache has no package" error when wine update is available

Status in Pipelight:
  New
Status in update notifier:
  Confirmed
Status in Wine "Compholio" Edition:
  Triaged
Status in indicator-applet package in Ubuntu:
  Confirmed
Status in wine1.6 package in Ubuntu:
  Confirmed

Bug description:
  (Note: This also affects the regular Wine package, see below)

  Hello,

  On Ubuntu 14.04 x64, each time there is an update for wine-compholio
  available, but not installed yet, update-manager has the following
  error in system indicator :

  class 'KeyError' The cache has no package named wine-compholio-i386

  Installing the updates removes the error message.

  I attach a screenshot of the whole message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pipelight/+bug/1318321/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons

[Ubuntu Foundations Team Bug Bot]

The attachment "qdbustrayicon-try-to-save-temp-icons-in-readable-
location.debdiff" seems to be a debdiff.  The ubuntu-sponsors team has
been subscribed to the bug report so that they can review and hopefully
sponsor the debdiff.  If the attachment isn't a patch, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  App indicator does not show icon for Qt apps or with custom icons

Status in Qt:
  In Progress
Status in Snappy:
  New
Status in appmenu-qt5 package in Ubuntu:
  Fix Released
Status in libappindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  In Progress
Status in sni-qt package in Ubuntu:
  Fix Released

Bug description:
  Snaps that use the app indicator area via Qt can't display their icon
  there.

  Steps to reproduce and screenshot:
  https://github.com/nuttyartist/notes/pull/77

  Some research:

  - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html
  - The indicator icon is created under /tmp under a randomly generated 
directory name

  didrocks mentions also:

  1. The application says "this is my menu, and here is my icon at that 
address", the address being /tmp/blablabla
  2. appindicator receives the bus messages
  3. and says "let's have a look at this icon at that address"
  4. BUT! /tmp in the snap is different form system /tmp

To manage notifications about this bug go to:
https://bugs.launchpad.net/qt/+bug/1600136/+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 1100546] Re: Power indicator favours 'not present' mouse over laptop battery level

[Ubuntu Foundations Team Bug Bot]

The attachment "indicator-power_12.10.6+16.04.20160105-0ubuntu1.debdiff"
seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to
the bug report so that they can review and hopefully sponsor the
debdiff.  If the attachment isn't a patch, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are member
of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Power indicator favours 'not present' mouse over laptop battery level

Status in indicator-power:
  Triaged
Status in indicator-power package in Ubuntu:
  Triaged

Bug description:
  The power indicator shows the battery level for cordless mice and
  keyboards, even when it cannot identify the battery level. This is a
  problem as it seems to favour showing a "not present" mouse status
  over the laptop battery level in the top bar.

  I haven't done a good job of explaining it, so check out the
  screenshot - it will explain all :)

  Basically, the laptop battery should be shown in the top bar if the 
mouse/keyboard is "not present".
  Also hiding the mouse and keyboard when the battery level is unknown would 
also be useful too :)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-power 12.10.6daily12.11.21.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3
  Uname: Linux 3.8.0-0-generic x86_64
  ApportVersion: 2.8-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 17 10:11:16 2013
  InstallationDate: Installed on 2012-12-14 (33 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121214)
  MarkForUpload: True
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-power/+bug/1100546/+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 147312] Re: ccsm crashed with KeyError in UpdateEnabledPluginsList()

[Ubuntu Foundations Team Bug Bot]

** Tags added: compiz-0.5

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

Title:
  ccsm crashed with KeyError in UpdateEnabledPluginsList()

Status in compiz package in Ubuntu:
  New
Status in compizconfig-settings-manager package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: compizconfig-settings-manager

  Installed compizconfig-settings-manager, along with xserver-glx, using
  apt-get, and it came up with this error.

  ProblemType: Crash
  Architecture: i386
  Date: Sun Sep 30 18:28:10 2007
  DistroRelease: Ubuntu 7.10
  ExecutablePath: /usr/bin/ccsm
  InterpreterPath: /usr/bin/python2.5
  NonfreeKernelModules: ath_hal
  Package: compizconfig-settings-manager 0.5.2+git20070912-0ubuntu1
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/ccsm
  ProcCwd: /home/hraefn
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/ccsm']
  SourcePackage: compizconfig-settings-manager
  Title: ccsm crashed with KeyError in UpdateEnabledPluginsList()
  Uname: Linux worker-ant 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 
i686 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/147312/+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 1609793] Re: Unity tests crashes when compiling google-mocks with gcc-6

[Ubuntu Foundations Team Bug Bot]

The attachment "google-mock-gcc6-action-result-holder-crash-fix.patch"
seems to be a patch.  If it isn't, please remove the "patch" flag from
the attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Unity tests crashes when compiling google-mocks with gcc-6

Status in google-mock package in Ubuntu:
  In Progress
Status in google-mock package in Debian:
  Unknown

Bug description:
  Ubuntu Unity tests fails when using gcc-6, because test-gtest causes a
  crash.

  Starting program: 
/tmp/unity-7.5.0+16.10.20160804/obj-x86_64-linux-gnu/tests/test-gtest 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffe0f1d700 (LWP 22778)]
  [New Thread 0x7fffdbfff700 (LWP 22779)]
  [New Thread 0x7fffdb7fe700 (LWP 22780)]
  [==] Running 1637 tests from 105 test cases.
  [--] Global test environment set-up.
  [--] 14 tests from TestActionLink
  [ RUN  ] TestActionLink.AligmentCorrectlySetDifferent

  Thread 1 "test-gtest" received signal SIGSEGV, Segmentation fault.
  testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> 
const&) (args=empty std::tuple, this=0x7fffdb08)
  at /usr/include/gmock/gmock-spec-builders.h:1530
  1530  this->UntypedInvokeWith())->GetValueAndDelete();


  #0  testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> 
const&) (args=empty std::tuple, this=0x7fffdb08)
  at /usr/include/gmock/gmock-spec-builders.h:1530
  No locals.
  #1  testing::internal::FunctionMocker::Invoke() 
(this=0x7fffdb08) at 
/usr/include/gmock/gmock-generated-function-mockers.h:76
  No locals.
  #2  unity::dash::ActionLinkMock::QueueDraw (this=0x7fffd3c0) at 
/tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:43
  No locals.
  #3  0x559ce574 in unity::dash::ActionLink::set_underline 
(this=0x7fffd3c0, underline=unity::StaticCairoText::NUX_UNDERLINE_NONE)
  at 
/tmp/unity-7.5.0+16.10.20160804/tests/../dash/previews/ActionLink.cpp:218
  No locals.
  #4  0x559d53bf in std::function::operator()(unity::StaticCairoText::UnderlineState const&) const 
(__args#0=, this=0x7fffda00) at 
/usr/include/c++/6/functional:2136
  No locals.
  #5  nux::RWProperty::Set 
(this=0x7fffd9c8, value=)
  at /usr/include/Nux-4.0/NuxCore/Property-inl.h:218
  No locals.
  #6  0x559d0c31 in 
unity::dash::TestActionLink_UnderlineCorrectlySetDifferent_Test::TestBody 
(this=)
  at /tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:116

  
  A fix is available at 
https://github.com/google/googletest/issues/705#issuecomment-235067917

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-mock/+bug/1609793/+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 1608148] Re: package humanity-icon-theme 0.6.5 failed to install/upgrade: unable to stat './usr/share/icons/Humanity/apps/22/nm-stage03-connecting02.svg' (which I was about to insta

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: humanity-icon-theme (Ubuntu)
   Importance: Undecided => Low

** Changed in: humanity-icon-theme (Ubuntu)
   Status: New => Invalid

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

Title:
  package humanity-icon-theme 0.6.5 failed to install/upgrade: unable to
  stat './usr/share/icons/Humanity/apps/22/nm-stage03-connecting02.svg'
  (which I was about to install): Input/output error

Status in humanity-icon-theme package in Ubuntu:
  Invalid

Bug description:
  hi

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: humanity-icon-theme 0.6.5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Jul 30 18:40:47 2016
  DuplicateSignature:
   package:humanity-icon-theme:0.6.5
   Unpacking humanity-icon-theme (0.6.10) over (0.6.5) ...
   dpkg: error processing archive 
/var/cache/apt/archives/humanity-icon-theme_0.6.10_all.deb (--unpack):
unable to stat 
'./usr/share/icons/Humanity/apps/22/nm-stage03-connecting02.svg' (which I was 
about to install): Input/output error
  ErrorMessage: unable to stat 
'./usr/share/icons/Humanity/apps/22/nm-stage03-connecting02.svg' (which I was 
about to install): Input/output error
  InstallationDate: Installed on 2016-07-10 (20 days ago)
  InstallationMedia: It
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: humanity-icon-theme
  Title: package humanity-icon-theme 0.6.5 failed to install/upgrade: unable to 
stat './usr/share/icons/Humanity/apps/22/nm-stage03-connecting02.svg' (which I 
was about to install): Input/output error
  UpgradeStatus: Upgraded to xenial on 2016-07-10 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1608148/+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 1597598] Re: a11y-profile-manager-indicator has wrong scale in Ubiquity with HiDPI display.

[Ubuntu Foundations Team Bug Bot]

The attachment "hidpi.patch" seems to be a patch.  If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  a11y-profile-manager-indicator has wrong scale in Ubiquity with HiDPI
  display.

Status in libindicator package in Ubuntu:
  New

Bug description:
  When using a laptop with HiDPI display, the a11y-profile-manager-
  indicator scaled too large in Ubiquity.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/1597598/+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 363108] Re: The first IM message from a buddy does not launch a notification bubble

[Ubuntu Foundations Team Bug Bot]

The attachment "first-message-regression.diff" seems to be a patch.  If
it isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: 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/363108

Title:
  The first IM message from a buddy does not launch a notification
  bubble

Status in notify-osd package in Ubuntu:
  Invalid
Status in pidgin-libnotify package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pidgin

  The first IM message from a buddy (i.e. the message which starts a new
  conversation) does not launch a notify-OSD notification bubble.
  However, the subsequent messages correctly triggers notifications.
  This is annoying, illogical and incoherent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/363108/+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 1584849] Re: Creating a log on a non-default thread causes it to hang

[Ubuntu Foundations Team Bug Bot]

The attachment "thread-default-context.patch" seems to be a patch.  If
it isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Creating a log on a non-default thread causes it to hang

Status in Zeitgeist Framework:
  Unknown
Status in zeitgeist package in Ubuntu:
  New

Bug description:
  When creating a Log object it creates a mainloop to wait on the proxy
  object. It unfortunately does this with NULL has its context which
  means it uses the main thread's context instead of the thread it is
  running on. This causes a hang as no one gets events then.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zeitgeist/+bug/1584849/+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 1506744] Re: Newly installed applications do not show in the dash

[Ubuntu Foundations Team Bug Bot]

The attachment "80_file_monitor_delayed.patch" seems to be a patch.  If
it isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Newly installed applications do not show in the dash

Status in GLib:
  Confirmed
Status in gnome-menus package in Ubuntu:
  In Progress
Status in libunity package in Ubuntu:
  In Progress
Status in unity package in Ubuntu:
  Invalid

Bug description:
  I am running 15.10 development version fully up to date, I installed
  it a few days ago and I have an issue with newly installed
  applications not appearing in the dash when I search for them, they
  can be started via console but the icons/launchers of newly installed
  applications will only appear in the dash after session is restarted.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20151002.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Oct 16 08:41:39 2015
  InstallationDate: Installed on 2015-10-11 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1506744/+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 1570894] Re: s390x build failure

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  s390x build failure

Status in nux package in Ubuntu:
  New

Bug description:
  poking s390x build failure:

  Executing gtest-nuxgraphics under dummy xserver results in illigel
  instructions:

  # .libs/gtest-nuxgraphics 
  [==] Running 9 tests from 2 test cases.
  [--] Global test environment set-up.
  [--] 8 tests from TestTextures
  [ RUN  ] TestTextures.TestTextureSizes
  Illegal instruction (core dumped)

  Program received signal SIGILL, Illegal instruction.
  0x03fffdf2e53a in nux::NThreadSafeCounter::Increment (this=0x3fffdf53f2e 
) at ThreadGNU.cpp:31
  31return __sync_add_and_fetch (_Counter, 1);
  (gdb) backtrace full
  #0  0x03fffdf2e53a in nux::NThreadSafeCounter::Increment 
(this=0x3fffdf53f2e ) at ThreadGNU.cpp:31
  No locals.

  
  But there is nothing special in ThreadGNU.cpp:31 it simply does:

int NThreadSafeCounter::Increment()
{
  return __sync_add_and_fetch (_Counter, 1);
}

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1570894/+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 1570812] Re: [UIFe] Window actions such as Minimize, Maximize, Restore, Move, Resize... Aren't accessible from HUD

[Ubuntu Foundations Team Bug Bot]

The attachment "libwnck3-fix-mnemonics.patch" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff.  If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  [UIFe] Window actions such as Minimize, Maximize, Restore, Move,
  Resize... Aren't accessible from HUD

Status in bamf package in Ubuntu:
  In Progress
Status in hud package in Ubuntu:
  In Progress
Status in libwnck3 package in Ubuntu:
  In Progress

Bug description:
  The Window menu actions (those currently accessible by right-clicking
  the decorations, or by Alt+space) aren't listed in HUD.

  Moving the UIFe side of things from bug #1551986.
  ACKed: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1551986/comments/9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1570812/+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 1512002] Re: Annoying dialog "Authentication is required to change your own user data"

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Annoying dialog "Authentication is required to change your own user
  data"

Status in accountsservice:
  Unknown
Status in accountsservice package in Ubuntu:
  Confirmed
Status in indicator-messages package in Ubuntu:
  Confirmed
Status in policykit-1-gnome package in Ubuntu:
  Confirmed

Bug description:
  Every few days a dialog pops up saying "Authentication is required to change 
your own user data" with an entry field for a password. If I type my user's 
password the dialog will reappear with an empty entry field. If I click on the 
cross to close the window many times it will be gone, but reappear a few days 
later. I don't know what this window is for and it makes no difference whether 
I close it or leave it. I don't use the gnome keyring.
  This started with Ubuntu 15.04 or maybe with an earlier release, and is still 
there in Ubuntu 15.10, also on machines I did a fresh install.

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

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

-- 
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:
  Fix Committed
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 1427866] Re: Eclipse crashes in g_str_hash when using menu proxy and "New Window"

[Ubuntu Foundations Team Bug Bot]

The attachment "Back-port of fix from 14.10" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Eclipse crashes in g_str_hash when using menu proxy and "New Window"

Status in unity-gtk-module package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04.2 LTS
  unity-gtk2-module:
Installed: 0.0.0+14.04.20141212-0ubuntu1

  1. Download Eclipse 4.4.2 available here:
  
https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/luna/SR2/eclipse-java-luna-SR2-linux-gtk-x86_64.tar.gz
  2.  Start Eclipse. Close the Welcome screen.
  3.  Mouse over to "Window" menu on top bar, click, move mouse down to "New 
Window", click to open a new, empty window.
  4.  Mouse over to "Window" menu on top bar, click. Crash occurs.

  If Eclipse is started with UBUNTU_MENUPROXY=0, it doesn't crash.

  #  SIGSEGV (0xb) at pc=0x7fa88c654fe0, pid=3787, tid=140362505688832
  #
  # JRE version: OpenJDK Runtime Environment (7.0_75-b13) (build 1.7.0_75-b13)
  # Java VM: OpenJDK 64-Bit Server VM (24.75-b04 mixed mode linux-amd64 
compressed oops)
  # Derivative: IcedTea 2.5.4
  # Distribution: Ubuntu 14.04 LTS, package 7u75-2.5.4-1~trusty1
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x38fe0]  g_str_hash+0x0

  ...

  Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
  j  org.eclipse.swt.internal.gtk.OS._gtk_widget_show(J)V+0
  j  org.eclipse.swt.internal.gtk.OS.gtk_widget_show(J)V+8
  j  org.eclipse.swt.widgets.MenuItem.createHandle(I)V+248
  j  org.eclipse.swt.widgets.Widget.createWidget(I)V+2
  j  
org.eclipse.swt.widgets.MenuItem.(Lorg/eclipse/swt/widgets/Menu;II)V+38
  j  
org.eclipse.ui.internal.SwitchToWindowMenu.fill(Lorg/eclipse/swt/widgets/Menu;I)V+97
  j  
org.eclipse.jface.action.MenuManager.doItemFill(Lorg/eclipse/jface/action/IContributionItem;I)V+6
  j  org.eclipse.jface.action.MenuManager.update(ZZ)V+371
  j  org.eclipse.jface.action.MenuManager.handleAboutToShow()V+33

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1427866/+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 1502094] Re: libgee-0.8-dev should be used, libgee-dev will be removed from the archive

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  libgee-0.8-dev should be used, libgee-dev will be removed from the
  archive

Status in indicator-keyboard package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  In Progress
Status in indicator-sound-gtk2 package in Ubuntu:
  Fix Released
Status in libfriends package in Ubuntu:
  Fix Released
Status in libgee package in Ubuntu:
  New
Status in unity-china-music-scope package in Ubuntu:
  Fix Released
Status in unity-china-video-scope package in Ubuntu:
  Fix Released
Status in unity-lens-applications package in Ubuntu:
  In Progress
Status in unity-lens-files package in Ubuntu:
  Fix Released
Status in unity-lens-friends package in Ubuntu:
  Fix Released
Status in unity-lens-music package in Ubuntu:
  Fix Released
Status in unity-lens-video package in Ubuntu:
  In Progress
Status in unity-scope-home package in Ubuntu:
  In Progress
Status in indicator-keyboard source package in Xenial:
  Fix Released
Status in indicator-sound source package in Xenial:
  In Progress
Status in indicator-sound-gtk2 source package in Xenial:
  Fix Released
Status in libfriends source package in Xenial:
  Fix Released
Status in libgee source package in Xenial:
  New
Status in unity-china-music-scope source package in Xenial:
  Fix Released
Status in unity-china-video-scope source package in Xenial:
  Fix Released
Status in unity-lens-applications source package in Xenial:
  In Progress
Status in unity-lens-files source package in Xenial:
  Fix Released
Status in unity-lens-friends source package in Xenial:
  Fix Released
Status in unity-lens-music source package in Xenial:
  Fix Released
Status in unity-lens-video source package in Xenial:
  In Progress
Status in unity-scope-home source package in Xenial:
  In Progress

Bug description:
  The libgee source is obsolete, replaced by the libgee-0.8 source.
  Packages should change their build dependency to libgee-0.8-dev
  instead.

  The libgee source was already removed in Debian; it will be removed in
  Ubuntu as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1502094/+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 919801] Re: Unity dash file search is extremely slow

[Ubuntu Foundations Team Bug Bot]

The attachment "zeitgeist_0.9.16-upstart-and-vacuum-support.debdiff"
seems to be a debdiff.  The ubuntu-sponsors team has been subscribed to
the bug report so that they can review and hopefully sponsor the
debdiff.  If the attachment isn't a patch, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are member
of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Unity dash file search is extremely slow

Status in unity-lens-files:
  Incomplete
Status in Zeitgeist Framework:
  Incomplete
Status in unity-lens-files package in Ubuntu:
  Confirmed
Status in zeitgeist package in Ubuntu:
  In Progress

Bug description:
  When I try to use the Unity dash search feature to navigate to files
  and folders, it is extremely slow. For example, if I hit the super
  button to launch the search and then type "Pictures" to get my
  pictures directory, it takes almost 5 seconds for the folder icon to
  show. In comparison, if I use Gnome-Do to navigate to my Pictures
  folder, it's basically instant.

  I have attached a video screencast so that you can see the problem for 
yourself.
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,move,vpswitch,place,session,imgpng,mousepoll,resize,gnomecompat,regex,snap,grid,wall,unitymtgrabhandles,animation,expo,ezoom,workarounds,fade,scale,unityshell]
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
  NonfreeKernelModules: nvidia
  Package: unity 5.0.0~+bzr1825ubuntu0+611
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-14-generic i686
  UnreportableReason: This is not a genuine Ubuntu package
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (99 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-lens-files/+bug/919801/+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 1539202] Re: please multiarchify the library packages

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  please multiarchify the library packages

Status in libunity-webapps package in Ubuntu:
  New

Bug description:
  please multiarchify the library packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1539202/+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 1197569] Re: Move from zeitgeist-1.0 to zeitgeist-2.0

[Ubuntu Foundations Team Bug Bot]

The attachment "nautilus_3.18.2-1ubuntu2.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff.  If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Move from zeitgeist-1.0 to zeitgeist-2.0

Status in Bijiben:
  Fix Released
Status in Cairo-Dock Plug-ins:
  Fix Released
Status in Diodon:
  Fix Released
Status in Scratch:
  Fix Released
Status in Totem:
  Fix Released
Status in Ubuntu Application Launcher:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-lens-applications:
  In Progress
Status in unity-lens-files:
  Fix Committed
Status in Unity Videos Lens:
  In Progress
Status in activity-log-manager package in Ubuntu:
  Fix Released
Status in bijiben package in Ubuntu:
  Fix Released
Status in cairo-dock-plug-ins package in Ubuntu:
  Fix Released
Status in diodon package in Ubuntu:
  Fix Released
Status in folks package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in synapse package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  New
Status in unity package in Ubuntu:
  Fix Released
Status in unity-lens-applications package in Ubuntu:
  In Progress
Status in unity-lens-files package in Ubuntu:
  Fix Released
Status in unity-lens-video package in Ubuntu:
  In Progress
Status in upstart-app-launch package in Ubuntu:
  Fix Released

Bug description:
  The older libzeitgeist (http://launchpad.net/libzeitgeist) served its
  days and will be deprecated soon.

  All the apps should slowly move to libzeitgeist 2 (zeitgeist-2.0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/bijiben/+bug/1197569/+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 617816] Re: Critically Low Battery Notification not showing in Ubuntu 14.04 lts

[Ubuntu Foundations Team Bug Bot]

The attachment "It will give notification when the battery is low and
you should run this .sh file in terminal." seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: 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/617816

Title:
  Critically Low Battery Notification not showing in Ubuntu 14.04 lts

Status in notify-osd package in Ubuntu:
  Fix Committed

Bug description:
  I have installed Ubuntu 14.04 lts and when the battery is low, I am
  unable to get notifications such as battery critically low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/617816/+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 1436405] Re: Duplicate menu (both unity and in-app) for Qt apps

[Ubuntu Foundations Team Bug Bot]

The attachment "smime.p7s" seems to be a patch.  If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Duplicate menu (both unity and in-app) for Qt apps

Status in One Hundred Papercuts:
  Confirmed
Status in appmenu-qt5 package in Ubuntu:
  Confirmed
Status in libdbusmenu-qt package in Ubuntu:
  Confirmed

Bug description:
  At least konsole and khelpcenter suffers from this bug:

  Start the app inside the default Unity environment (not under KDE).
  Notice that the app's menubar appears twice.  Once in the upper row of
  the whole desktop, as expected and as it is for every Gnome app.  And
  also inside the application's window, wasting precious screen real
  estate.

  In Utopic, at least for konsole, I'm quite sure that the menu wasn't
  duplicated inside the app, it only appeared on the desktop's top Unity
  bar.

  (I'm not sure I guessed the component right; please reassign as
  appropriate.)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libdbusmenu-qt5 0.9.3+14.10.20140619-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 25 16:33:14 2015
  InstallationDate: Installed on 2012-05-30 (1028 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: libdbusmenu-qt
  UpgradeStatus: Upgraded to vivid on 2015-03-17 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1436405/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout

[Ubuntu Foundations Team Bug Bot]

The attachment "non-latin-shortcuts.patch" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Hotkeys not functional in non-latin keyboard layout

Status in aptana-studio-installer:
  New
Status in Default settings and artwork for Baltix OS:
  New
Status in LibreOffice Productivity Suite:
  Fix Released
Status in ibus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape:
  New
Status in monodevelop:
  New
Status in mutter:
  Fix Released
Status in okular:
  New
Status in OpenOffice:
  New
Status in sigram:
  New
Status in Unity:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-terminal package in Ubuntu:
  Triaged
Status in openjdk-7 package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in Fedora:
  Unknown
Status in gnome-shell package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters->keyboard->hotkeys->windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1491913] Re: Force high gfx mode with UNITY_LOW_GFX_MODE == 0

[Ubuntu Foundations Team Bug Bot]

The attachment "low-gfx-override.patch" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Force high gfx mode with UNITY_LOW_GFX_MODE == 0

Status in Unity:
  In Progress
Status in unity package in Ubuntu:
  In Progress

Bug description:
  While discussing bug #1491555,  my colleague Brian Paul suggested that
  in addition to forcing low gfx mode with UNITY_LOW_GFX_MODE = 1, it
  would also be helpful to force it out of low gfx mode with
  UNITY_LOW_GFX_MODE = 0.

  This way if Unity ends up in low gfx mode unnecessarily due to a wrong
  renderer string match, e.g. LLVM in the current case, there is a quick
  workaround to get out of it while a fix works its way through the
  release process.

  The patch (signed-off-by: Sinclair Yeh ) attached
  adds this capability.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1491913/+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 1491542] Re: libunity ftbfs in wily

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  libunity ftbfs in wily

Status in libunity package in Ubuntu:
  New

Bug description:
  libunity seems to no longer be buildable in wily.  This is a problem
  because it must be rebuilt for Python 3.5, but it is failing for
  unrelated reasons.  Here's an excerpt of the build log from a local
  build using the current wily source package:

  /usr/bin/glib-compile-resources --sourcedir . --target=unity-tool-res.c 
--generate-source unity-tool-res.gresource.xml
  /usr/bin/valac -C --vapidir ../vapi --vapidir=../protocol --vapidir=../src 
--pkg config --pkg gtk+-3.0 --pkg gmodule-2.0 --pkg unity-internal --pkg 
unity-protocol --pkg glib-2.0 --pkg gmodule-2.0 --pkg gobject-2.0 --pkg gio-2.0 
--pkg gio-unix-2.0 --pkg dee-1.0 --pkg Dbusmenu-0.4  unity-tool.vala 
unity-tool-dbus-util.vala unity-tool-ui.vala preview-renderer.vala 
music-track-model-renderer.vala
  unity-tool-ui.vala:846.13-846.21: error: `ListStore' is an ambiguous 
reference between `GLib.ListStore' and `Gtk.ListStore'
  private ListStore uimodel = null;
  ^
  unity-tool-ui.vala:847.13-847.21: error: `ListStore' is an ambiguous 
reference between `GLib.ListStore' and `Gtk.ListStore'
  private ListStore ui_filter_model = null;
  ^
  unity-tool-ui.vala:848.13-848.21: error: `ListStore' is an ambiguous 
reference between `GLib.ListStore' and `Gtk.ListStore'
  private ListStore scope_list_model = null;
  ^
  unity-tool-ui.vala:849.13-849.21: error: `ListStore' is an ambiguous 
reference between `GLib.ListStore' and `Gtk.ListStore'
  private ListStore ui_cat_model = null;
  ^
  unity-tool-ui.vala:43.62-43.70: error: `ListStore' is an ambiguous reference 
between `GLib.ListStore' and `Gtk.ListStore'
  uimodel = builder.get_object("results_model") as ListStore;
   ^
  unity-tool-ui.vala:44.70-44.78: error: `ListStore' is an ambiguous reference 
between `GLib.ListStore' and `Gtk.ListStore'
  ui_filter_model = builder.get_object("filters_model") as 
ListStore;
   ^
  unity-tool-ui.vala:45.70-45.78: error: `ListStore' is an ambiguous reference 
between `GLib.ListStore' and `Gtk.ListStore'
  ui_cat_model = builder.get_object("categories_model") as 
ListStore;
   ^
  unity-tool-ui.vala:158.74-158.82: error: `ListStore' is an ambiguous 
reference between `GLib.ListStore' and `Gtk.ListStore'
  scope_list_model = builder.get_object("scope_list_model") as 
ListStore;
   
^
  music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an 
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
  public ListStore track_view_model { get; construct; }
 ^
  music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an 
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
  public ListStore track_view_model { get; construct; }
 ^
  music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an 
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
  public ListStore track_view_model { get; construct; }
 ^
  music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an 
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
  public ListStore track_view_model { get; construct; }
 ^
  Compilation failed: 12 error(s), 0 warning(s)

  Seems like the same problem in all cases, and I'm not sure which
  ListStore is intended.  Full buildlog is available in the Python 3.5
  -as-default PPA:

  https://launchpadlibrarian.net/216183170/buildlog_ubuntu-wily-
  amd64.libunity_7.1.4%2B14.10.20140808-0ubuntu1_BUILDING.txt.gz

  This is blocking several other critical packages which need updating
  for Python 3.5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1491542/+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 1446081] Re: Incorrect scaling of launcher icons

[Ubuntu Foundations Team Bug Bot]

The attachment launchpad-1446081.patch seems to be a patch.  If it
isn't, please remove the patch flag from the attachment, remove the
patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Incorrect scaling of launcher icons

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

Bug description:
  Launcher icons shown w/o issues only on this sizes of launcher: 16,
  24, 32, 48, 64.

  Screenshot attached. Look at Sublime, Chrome and Skype icons. There
  was no such issue before vivid.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150410.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Apr 20 00:26:44 2015
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-03-27 (23 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1446081/+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 1465340] Re: Unity Radiance Menu Bar Should Stop Radiating

[Ubuntu Foundations Team Bug Bot]

The attachment Patch (created with diff -u): set RGBA to false in
gtkrc seems to be a patch.  If it isn't, please remove the patch flag
from the attachment, remove the patch tag, and if you are a member of
the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Unity Radiance Menu Bar Should Stop Radiating

Status in unity package in Ubuntu:
  New

Bug description:
  This bug has been there for at least three years.

  The font anti aliasing in the menu bar is completely off when the user
  chooses the Radiance theme. The attached screen shot shows a Firefox
  menu on top of an Emacs session. You see the unity menu bar at the top
  with the distorted anti aliasing. Under it in the pop-up menu you see
  a font rendered normally which looks much better.

  In addition to the distorted anti aliasing the menu bar does not seem
  to respect the user settings in ~/.fonts.conf.

  Please fix this and alter the name of Radiance to Bright. Stop the
  menu bar from radiating with Radiance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1465340/+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 1447224] Re: Regression: Unable to select audio or subtitle tracks

[Ubuntu Foundations Team Bug Bot]

The attachment 0001-Add-a-traditional-menubar.patch seems to be a
patch.  If it isn't, please remove the patch flag from the attachment,
remove the patch tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Regression: Unable to select audio or subtitle tracks

Status in indicator-appmenu package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in indicator-appmenu source package in Vivid:
  Confirmed
Status in totem source package in Vivid:
  Confirmed
Status in vlc source package in Vivid:
  Invalid

Bug description:
  After upgrading to Ubuntu 15.04 neither Totem nor VLC are able to
  select different audio tracks or subtitles when playing videos with
  multiple tracks. This is a regression from Ubuntu 14.10 where playback
  of such files was working as expected. I tried this on multiple
  machines running 15.04 and with various media, mostly MKV videos but
  also AVI videos or simply DVDs.

  On Totem the expected functionality in the application menu is missing
  or the menu item is just empty.

  On VLC the menu items are present but always disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: totem 3.14.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 22 16:53:57 2015
  InstallationDate: Installed on 2014-07-15 (280 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1447224/+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 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime)

[Ubuntu Foundations Team Bug Bot]

The attachment Patch for nux-4.0.7+14.10.20141007 seems to be a patch.
If it isn't, please remove the patch flag from the attachment, remove
the patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Menu interaction in fully maximised window causes the next click on
  the title bar to restore the window (after 2^31ms of uptime)

Status in Compiz:
  New
Status in Nux:
  Confirmed
Status in Unity:
  New
Status in nux package in Ubuntu:
  Confirmed

Bug description:
  (Using the Terminal window as an example)
  1. Open a Terminal window
  2. Maximise a window fully so that its title bar and menu share the top Unity 
panel
  3. Click the View menu (the menu opens)
  4. Click the Search menu (the View menu closes)
  5. Click anywhere on the title bar
  6. The window restores to non-maximised size

  It shouldn't do this, only a double-click should restore the window.

  Alternative ways to trigger it:
  3. Click the Terminal menu
  4. Click the Reset option
  5. Click  anywhere on the title bar

  3. Click the Terminal menu
  4. Click inside the main area of the application
  5. Click anywhere on the title bar

  It looks like something is going wrong with the double-click detection
  when a menu is opened and then closed.

  Version: Ubuntu 14.04.1
  unity 7.2.2+14.04.20140714-0ubuntu1.1
  xorg 1:7.7+1ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1379960/+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 1302004] Re: Indicator-datetime still doesn't list all events for today's date (Trusty/Utopic/Vivid)

[Ubuntu Foundations Team Bug Bot]

The attachment upcoming-after-end.patch seems to be a patch.  If it
isn't, please remove the patch flag from the attachment, remove the
patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Indicator-datetime still doesn't list all events for today's date
  (Trusty/Utopic/Vivid)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  This bug is related to this bug: Bug #1293646 (Which is marked as fix
  released)

  With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it
  lists all events for all past selected dates properly (which was fixed
  in bug Bug #1293646) except today's date. When I click on any past
  date in calendar it shows:

  1. all all-day events for the day.
  2. all events with time for the day
  3. upcoming (future) all-day events
  4. upcoming (future) events with time

  But when I click on today's date it only shows:

  1. future all day events
  2. future events with time

  I still have to click on previous day's date to find out all all-day
  events for today.

  The behavior (showing all events for a day) should be same for any
  date, including today's date.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1302004/+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 1440825] Re: dnd_is_screensaver_inhibited no longer works

[Ubuntu Foundations Team Bug Bot]

The attachment notify-osd_dnd.patch seems to be a patch.  If it isn't,
please remove the patch flag from the attachment, remove the patch
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: 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/1440825

Title:
  dnd_is_screensaver_inhibited no longer works

Status in notify-osd package in Ubuntu:
  New

Bug description:
  Notifications are still shown even if the system inhibits
  screensaver(expecting dnd_is_screensaver_inhibited state).

  The code seems to expect GetInhibitors method is in
  org.gnome.ScreenSaver, but the method is no longer there. The
  equivalent is IsInhibited method in org.gnome.SessionManager.

  
https://people.gnome.org/~mccann/gnome-session/docs/gnome-session.html#org.gnome.SessionManager.IsInhibited
  ## unit32:8 = (Inhibit the session being marked as idle)
  $ dbus-send --print-reply --dest=org.gnome.SessionManager 
/org/gnome/SessionManager org.gnome.SessionManager.IsInhibited uint32:8
  method return sender=:1.24 - dest=:1.284 reply_serial=2
 boolean true

  [src/dnd.c]
  100 static DBusGProxy*
  101 get_screensaver_proxy (void)
  102 {
  103 if (gsmgr == NULL)
  104 {
  105 DBusGConnection *connection = dbus_get_connection ();
  106 gsmgr = dbus_g_proxy_new_for_name (connection,
  107
org.gnome.ScreenSaver,
  108
/org/gnome/ScreenSaver,
  109
org.gnome.ScreenSaver);
  110 }
  111 
  112 return gsmgr;
  113 }   
  114 
  115 gboolean
  116 dnd_is_screensaver_inhibited ()
  117 {
  118 GError  *error = NULL;
  119 gboolean inhibited = FALSE;
  120 char **list;
  121 
  122 if (! get_screensaver_proxy ())
  123 return FALSE;
  124 
  125 if (dbus_g_proxy_call_with_timeout (
  126 gsmgr, GetInhibitors, 2000, error,
  127 G_TYPE_INVALID,
  128 G_TYPE_STRV, list,
  129 G_TYPE_INVALID))

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: notify-osd 0.9.35+15.04.20150126-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  7 01:49:02 2015
  DesktopSession: 'ubuntu'
  EcryptfsInUse: Yes
  GtkTheme: 'Ambiance'
  IconTheme: 'ubuntu-mono-dark'
  InstallationDate: Installed on 2015-02-28 (37 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150228)
  MachineType: FUJITSU FMVS54KR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+7ubuntu4
   libgl1-mesa-glx  10.5.2-0ubuntu1
   libdrm2  2.4.59-0ubuntu1
   xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
   xserver-xorg-video-ati   1:7.5.0-1ubuntu2
  SourcePackage: notify-osd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2013
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.06
  dmi.board.name: FJNB24F
  dmi.board.vendor: FUJITSU
  dmi.board.version: D2
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd01/07/2013:svnFUJITSU:pnFMVS54KR:pvr:rvnFUJITSU:rnFJNB24F:rvrD2:cvnFUJITSU:ct10:cvr:
  dmi.product.name: FMVS54KR
  dmi.sys.vendor: FUJITSU
  glxinfo: Error: [Errno 2] No such file or directory: 'glxinfo'

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

[Ubuntu Foundations Team Bug Bot]

The attachment logind-check-booted-with-systemd.patch seems to be a
patch.  If it isn't, please remove the patch flag from the attachment,
remove the patch tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
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 systemd package in Ubuntu:
  New
Status in systemd-shim package in Ubuntu:
  Triaged
Status in systemd-shim package in Debian:
  New

Bug description:
  ATTENTION: This bug is fully understood, there is *no need* to add
  even more comments about me too here.

  [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/ubuntu/+source/systemd/+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 1423463] Re: package unity 7.2.2+14.04.20140714-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/compiz/libunityshell.so' to '/usr/lib/compiz/libunitysh

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: corrupted-package

** Changed in: unity (Ubuntu)
   Status: New = 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/1423463

Title:
  package unity 7.2.2+14.04.20140714-0ubuntu1 failed to install/upgrade:
  cannot copy extracted data for './usr/lib/compiz/libunityshell.so' to
  '/usr/lib/compiz/libunityshell.so.dpkg-new': unexpected end of file or
  stream

Status in unity package in Ubuntu:
  Invalid

Bug description:
  Brand new install of ubuntu 14.04.1 amd64 on a Dell Inspiron N5110 and
  was just doing an update and the software updater gave me this error
  for a package

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  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: Thu Feb 19 07:11:54 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: package:unity:7.2.2+14.04.20140714-0ubuntu1:cannot copy 
extracted data for './usr/lib/compiz/libunityshell.so' to 
'/usr/lib/compiz/libunityshell.so.dpkg-new': unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/compiz/libunityshell.so' to 
'/usr/lib/compiz/libunityshell.so.dpkg-new': unexpected end of file or stream
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04b0]
  InstallationDate: Installed on 2015-02-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=cd239b5b-1946-412e-b58d-290c1970af38 ro quiet splash vt.handoff=7
  SourcePackage: unity
  Title: package unity 7.2.2+14.04.20140714-0ubuntu1 failed to install/upgrade: 
cannot copy extracted data for './usr/lib/compiz/libunityshell.so' to 
'/usr/lib/compiz/libunityshell.so.dpkg-new': unexpected end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 034W60
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn034W60:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  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.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Feb 19 04:23:36 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   21569 
   vendor SEC
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Dx-packages] [Bug 1357257] Re: package accountsservice 0.6.35-0ubuntu7 failed to install/upgrade: cannot copy extracted data for './usr/lib/accountsservice/accounts-daemon' to '/usr/lib/accountsservi

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: corrupted-package

** Changed in: accountsservice (Ubuntu)
   Status: New = 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/1357257

Title:
  package accountsservice 0.6.35-0ubuntu7 failed to install/upgrade:
  cannot copy extracted data for './usr/lib/accountsservice/accounts-
  daemon' to '/usr/lib/accountsservice/accounts-daemon.dpkg-new':
  unexpected end of file or stream

Status in accountsservice package in Ubuntu:
  Invalid

Bug description:
  i was doing a fresh install of 14.04 on a compaq presario cq50, after the 
instilation i did an apt-get update then upgrade and i recived this error
  I have no idea why this happened,  i have been running 14.04 after updating 
from 13 and have never had a problem before.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: accountsservice 0.6.35-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Fri Aug 15 16:56:17 2014
  DuplicateSignature: package:accountsservice:0.6.35-0ubuntu7:cannot copy 
extracted data for './usr/lib/accountsservice/accounts-daemon' to 
'/usr/lib/accountsservice/accounts-daemon.dpkg-new': unexpected end of file or 
stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/accountsservice/accounts-daemon' to 
'/usr/lib/accountsservice/accounts-daemon.dpkg-new': unexpected end of file or 
stream
  InstallationDate: Installed on 2014-08-15 (0 days ago)
  InstallationMedia: It
  SourcePackage: accountsservice
  Title: package accountsservice 0.6.35-0ubuntu7 failed to install/upgrade: 
cannot copy extracted data for './usr/lib/accountsservice/accounts-daemon' to 
'/usr/lib/accountsservice/accounts-daemon.dpkg-new': unexpected end of file or 
stream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

-- 
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 1308098] Re: 'E:Encountered a section with no Package: header, E:Problem with MergeList /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_precise-security_universe_binary-i386_Pac

[Ubuntu Foundations Team Bug Bot]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your bug report it seems that you are
experiencing bug 346386.  This issue happens when you have tried to
update your package information when you are a network that didn't
return the right files.  This issue can be cleaned up by using the
following commands in a terminal:

1.) sudo rm /var/lib/apt/lists/*
2.) sudo apt-get update

Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please reopen the bug task if it was incorrect.]

** This bug has been marked a duplicate of bug 346386
   [MASTER] Update fails with invalid package files with Encountered a section 
with no Package: header

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

Title:
   'E:Encountered a section with no Package: header, E:Problem with
  MergeList /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_precise-
  security_universe_binary-i386_Packages, E:The package lists or status
  file could not be parsed or opened.'

Status in Indicator Applet:
  New
Status in “indicator-applet” package in Ubuntu:
  New

Bug description:
  
  'E:Encountered a section with no Package: header, E:Problem with MergeList 
/var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_precise-security_universe_binary-i386_Packages,
 E:The package lists or status file could not be parsed or opened.'

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-applet/+bug/1308098/+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 978687] Re: Vala bindings use GIR name instead of pkg-config name

[Ubuntu Foundations Team Bug Bot]

The attachment dbusmenu.patch seems to be a patch.  If it isn't,
please remove the patch flag from the attachment, remove the patch
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Vala bindings use GIR name instead of pkg-config name

Status in DBus Menu:
  Triaged
Status in “libdbusmenu” package in Ubuntu:
  Triaged

Bug description:
  The Vala bindings should use pkg-config names, not GIR names, so valac
  can automatically pick up the relevant libraries and cflags.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libdbusmenu/+bug/978687/+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 1041600] Re: Patch to configure visible indicators

[Ubuntu Foundations Team Bug Bot]

The attachment Patch against 12.10.0 that adds indicator filtering
functionality seems to be a patch.  If it isn't, please remove the
patch flag from the attachment, remove the patch tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Patch to configure visible indicators

Status in Indicator Applet:
  Confirmed
Status in “indicator-applet” package in Ubuntu:
  Confirmed

Bug description:
  Using gnome-classic, I didn't want some of the new indicators (e.g.
  messaging, keyboard layout switcher) that I could not deactivate.

  Attached is a simple patch that allows indicators to be hidden through
  a dialog on the panel applet as well as through dconf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-applet/+bug/1041600/+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 1342731] Re: Horizontal Scrolling over Indicator-ng (and sound) does not work as expected

[Ubuntu Foundations Team Bug Bot]

The attachment unity_7.2.3+14.04.20140826-0ubuntu1.debdiff seems to be
a debdiff.  The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff.  If
the attachment isn't a patch, please remove the patch flag from the
attachment, remove the patch tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Horizontal Scrolling over Indicator-ng (and sound) does not work as
  expected

Status in Libindicator:
  In Progress
Status in Nux:
  Fix Committed
Status in Nux trusty series:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “libindicator” package in Ubuntu:
  In Progress
Status in “nux” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released
Status in “libindicator” source package in Trusty:
  New
Status in “nux” source package in Trusty:
  New
Status in “unity” source package in Trusty:
  New

Bug description:
  [Impact]
  When scrolling on indicator-sound using the horizontal scrolling the result 
is the opposite to what we expect in unity (left scrolling increases the volume 
and right scrolling decreases it), while in general is not handled at all for 
indicator-ng indicators as both left and right scrolling always ends up in a 
+1 delta scroll.

  [Test case]
  1. Hover Indicator-sound in unity
  2. Scroll left: the volume should be reduced
  3. Scroll right: the volume should be increased

  [Regression potential]
  The horizontal scroll direction might be inverted with some touchpads

To manage notifications about this bug go to:
https://bugs.launchpad.net/libindicator/+bug/1342731/+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 1320071] Re: Power buttons do not work when the screen is locked

[Ubuntu Foundations Team Bug Bot]

The attachment unity_7.2.3+14.04.20140826-0ubuntu1.debdiff seems to be
a debdiff.  The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff.  If
the attachment isn't a patch, please remove the patch flag from the
attachment, remove the patch tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Power buttons do not work when the screen is locked

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Keyboard power buttons do not work in the lockscreen

  [Test case]
  1. Lock the screen (using Super+L or menus)
  2. Pressing keyboard Sleep, Suspend, Hibernate and Power buttons should 
trigger the
 action defined by unity settings daemon power plugin;
 so by default:
 - Pressing power button should open the shutdown dialog
 - Pressing suspend button should suspend the computer
 - Pressing hibernate button should hibernate the computer
 - Pressing the screensaver button should blank the display

  [Regression Potential]
  Nothing known

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1320071/+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 1001621] Re: appmenu-qt doesn't work with 32-bit apps on 64-bit system

[Ubuntu Foundations Team Bug Bot]

The attachment Multiarch support for appmenu-qt seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff.  If the attachment
isn't a patch, please remove the patch flag from the attachment,
remove the patch tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  appmenu-qt doesn't work with 32-bit apps on 64-bit system

Status in Application menu for Qt4:
  Triaged
Status in Unity:
  Confirmed
Status in “appmenu-qt” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  When I run a software which it write with and build in 32bit system in a 
64bit system.
  It can't work a global meun and the HUD.

  I test this in Ubuntu 12.04 64bit,and the version of unity is 5.12.0.
  And we can reproduce it run the little program (attachment) in 64bit sysytem 
which I write it with Qt and build in 32 bit system.
  (You may should install ia32-libs to support 32bit software in 64bit system)

  And this is the output information:

  Unable to load library icui18n Cannot load library icui18n: 
(libicui18n.so.48: wrong ELF class: ELFCLASS64)
  /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class: ELFCLASS64

  (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module:
  /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so

  /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class:
  ELFCLASS64

  (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module:
  /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so

  /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class:
  ELFCLASS64

  (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module:
  /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so

  /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class:
  ELFCLASS64

  (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module:
  /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so

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

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

-- 
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 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()

[Ubuntu Foundations Team Bug Bot]

The attachment nux-remove-area-from-layout-queue.patch seems to be a
patch.  If it isn't, please remove the patch flag from the attachment,
remove the patch tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  compiz crashed with SIGSEGV in
  nux::WindowThread::ComputeQueuedLayout()

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

Bug description:
  Hi, this is basically the same bug as
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that
  bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing
  this bug on trusty, with the latest Unity version (unity
  7.2.1+14.04.20140513-0ubuntu2).  I already mentioned in that bug that
  I was still seeing it quite a while ago, but got no reply to that.

  Crashes are being experienced in multiple machines, while unlocking
  the screen.  The stacktraces vary, but they always fail in the same
  function and same line.

  First stacktrace:
  #0  0x0410 in ?? ()
  #1  0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout 
(this=this@entry=0x22c1990) at ./WindowThread.cpp:318
  #2  0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd 
(this=0x22c1990, clip=...) at ./WindowThread.cpp:1627
  #3  0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from 
/usr/lib/compiz/libunityshell.so
  #4  0x7fd4c0c20748 in 
unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, 
CompRegion const, CompOutput*, unsigned int)
 () from /usr/lib/compiz/libunityshell.so
  #5  0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, 
GLMatrix const, CompRegion const, CompOutput*, unsigned int) ()
from /usr/lib/compiz/libopengl.so
  #6  0x7fd4d4f2eed4 in 
PrivateGLScreen::paintOutputs(std::listCompOutput*, 
std::allocatorCompOutput* , unsigned int, CompRegion const) ()
from /usr/lib/compiz/libopengl.so
  #7  0x7fd4d556944f in CompositeScreen::paint(std::listCompOutput*, 
std::allocatorCompOutput* , unsigned int) ()
from /usr/lib/compiz/libcomposite.so
  #8  0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from 
/usr/lib/compiz/libcomposite.so
  #9  0x7fd4e12c053d in CompTimer::triggerCallback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () 
from /usr/lib/libcompiz_core.so.ABI-20140123
  #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int 
(*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  #13 0x7fd4df29ece5 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #15 0x7fd4df29f30a in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #16 0x7fd4e127b0eb in 
compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #17 0x00401971 in main ()

  Second stacktrace (different machine):
  #0  0x7f0058407ed0 in nux_area_accessible_check_pending_notification () 
from /usr/lib/compiz/libunityshell.so
  #1  0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout 
(this=this@entry=0x1d530e0) at ./WindowThread.cpp:318
  #2  0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd 
(this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627
  #3  0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from 
/usr/lib/compiz/libunityshell.so
  #4  0x7f00583e6748 in 
unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, 
CompRegion const, CompOutput*, unsigned int) () from 
/usr/lib/compiz/libunityshell.so
  #5  0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, 
GLMatrix const, CompRegion const, CompOutput*, unsigned int) ()
from /usr/lib/compiz/libopengl.so
  #6  0x7f00705e2ed4 in 
PrivateGLScreen::paintOutputs(std::listCompOutput*, 
std::allocatorCompOutput* , unsigned int, CompRegion const) ()
from /usr/lib/compiz/libopengl.so
  #7  0x7f0070c1d44f in CompositeScreen::paint(std::listCompOutput*, 
std::allocatorCompOutput* , unsigned int) ()
from /usr/lib/compiz/libcomposite.so
  #8  0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from 
/usr/lib/compiz/libcomposite.so
  #9  0x7f007879b53d in CompTimer::triggerCallback() () from 
/usr/lib/libcompiz_core.so.ABI-20140123
  #10 0x7f007879b5ef in CompTimeoutSource::callback() () from 

[Dx-packages] [Bug 1348575] Re: package libmessaging-menu0 13.10.1+14.04.20140410-0ubuntu1 failed to install/upgrade: ErrorMessage: no package named `libmessaging-menu0' is installed, cannot configure

[Ubuntu Foundations Team Bug Bot]

** Attachment removed: VarLogDistupgradeTermlog.gz
   
https://bugs.launchpad.net/bugs/1348575/+attachment/4162649/+files/VarLogDistupgradeTermlog.gz

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

Title:
  package libmessaging-menu0 13.10.1+14.04.20140410-0ubuntu1 failed to
  install/upgrade: ErrorMessage: no package named `libmessaging-menu0'
  is installed, cannot configure

Status in “indicator-messages” package in Ubuntu:
  New

Bug description:
  sucedio en el primer reinicio y tras actualizar ubuntu 12.04 a 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libmessaging-menu0
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Thu Jul 24 22:35:04 2014
  DuplicateSignature: 
package:libmessaging-menu0:13.10.1+14.04.20140410-0ubuntu1:ErrorMessage: no 
package named `libmessaging-menu0' is installed, cannot configure
  ErrorMessage: ErrorMessage: no package named `libmessaging-menu0' is 
installed, cannot configure
  InstallationDate: Installed on 2014-05-04 (81 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
  SourcePackage: indicator-messages
  Title: package libmessaging-menu0 13.10.1+14.04.20140410-0ubuntu1 failed to 
install/upgrade: ErrorMessage: no package named `libmessaging-menu0' is 
installed, cannot configure
  UpgradeStatus: Upgraded to trusty on 2014-07-25 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1348575/+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 1208019] Re: Eclipse menus doesn't show up in Saucy

[Ubuntu Foundations Team Bug Bot]

The attachment gtk+3.0_3.10.8-0ubuntu1.2.debdiff seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the patch flag from the
attachment, remove the patch tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Eclipse menus doesn't show up in Saucy

Status in Eclipse:
  Unknown
Status in GTK+ GUI Toolkit:
  Fix Released
Status in Unity GTK+ module:
  In Progress
Status in “gtk+3.0” package in Ubuntu:
  New
Status in “oracle-jdk7-installer” package in Ubuntu:
  Invalid
Status in “unity-gtk-module” package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  Switching tabs between open source files with different file types in
  Eclipse causes the Source and Refactor menus to be empty in the global
  menu bar under Unity.

  This is a severe usability problem for many Eclipse users. The fix
  proposed has been available in a PPA and is well-tested.

  [Test Case]

  1. Open a new project in Eclipse.
  2. Open two files: one with a .java extension, another with a .txt extension.
  3. Switch between the .java file and the .txt file and back again.
  4. Open the Source or Refactor menu in the Unity global menu bar.

  Expected result: menus with menu items
  Actual result: empty menus for both

  [Regression Potential]

  The fix involves changes to both gtk and unity-gtk-module.

  The changes to gtk are minimal and only involve the reversal of a pair
  of signal emissions, in a part of the code (GtkMenuTracker) which is
  normally used by desktop environments, not typical user applications.
  Therefore regression potential for the gtk update is unlikely.

  The changes to unity-gtk-module involve emitting show and hide signals
  where they were none before has some regression potential for
  applications that are explicitly watching for when their menus are
  opening and closing. But this is rare for applications to do, and we
  likely would have already received bug reports for those that do.
  Being completely sure would require extensive testing across all gtk
  apps though.

  Both changes together have been available as a PPA, thoroughly tested
  for quite some time now.

  [Other Info]

  The changes to unity-gtk-module depend on the changes to gtk, so both
  must be tested in simultaneity. Suggested to upload both to trusty-
  proposed at the same time.

  Original bug report follows:

  === % ===

  
  HOW TO REPRODUCE
  

  1. Run Eclipse, Gimp or Inkscape.
  2. Move the cursor to the top of the screen.
  3. Click on any of the menu items (File, Edit, Navigate, ...)

  **
  EXPECTED BEHAVIOUR
  **

  - The content of the submenus show up.

  **
  REAL BEHAVIOUR
  **

  - Only the top-level headers are available.
  - Nothing happens when clicking on them
  - They don't show up in the HUD either.

  ***
  WORK-AROUND
  ***

  To modify /usr/share/applications/eclipse.desktop to look like this:

  [Desktop Entry]
  Type=Application
  Name=Eclipse
  Comment=Eclipse Integrated Development Environment
  Icon=eclipse
  Exec=env UBUNTU_MENUPROXY= eclipse
  Terminal=false
  Categories=Development;IDE;Java;

  
  RELEVANT DETAILS
  

  - Doesn't affect Ubuntu releases prior to 13.10.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: eclipse 3.8.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic i686
  ApportVersion: 2.11-0ubuntu1
  Architecture: i386
  Date: Sat Aug  3 17:03:55 2013
  InstallationDate: Installed on 2013-07-08 (25 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130708)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: eclipse
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1208019/+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 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations

[Ubuntu Foundations Team Bug Bot]

The attachment diff seems to be a patch.  If it isn't, please remove
the patch flag from the attachment, remove the patch tag, and if you
are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Clicking on Nautilus’ launcher icon opens new window instead of
  restoring the minimized one when browsing external drives/locations

Status in “bamf” package in Ubuntu:
  Triaged
Status in “nautilus” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Sometimes left clicking the nautilus launcher icon doesn't bring up a
  minimized nautilus window. Instead of restoring the window a new
  instance of nautilus is showing up.

  Steps to reproduce:

  1. Open a nautilus window by clicking on the launcher icon.
  2. Navigate to a symlinked directory whose target is located on a different 
harddrive (for example: a symlink to a folder on a sd-card).
  3. Minimize the nautilus window.
  4. Try to bring up that window again by clicking the launcher icon.

  What happens:

  1. A new instance (window) of nautilus is opened.
  2. There's no obvious way to access the first window again. The only way is 
ALT+TAB.

  What schould happen:

  If a nautilus window is already open and minimized clicking the
  launcher icon should bring up that window. This was the behavior of
  nautilus windows in Ubuntu 12.10 (quantal).

  Ubuntu 13.04 Raring Ringtail (development branch)
  nautilus 3.6.3-0ubuntu16
  unity 7.0.0daily13.04.18~13.04-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Fri Apr 19 11:33:13 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'182'
  InstallationDate: Installed on 2011-07-23 (635 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1170647/+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 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session

[Ubuntu Foundations Team Bug Bot]

The attachment unity.kill.patch.txt seems to be a patch.  If it isn't,
please remove the patch flag from the attachment, remove the patch
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Unity kills running compiz, even if it belongs to a different Unity
  session

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

Bug description:
  Hi!

  I'm trying to get a setup with two different Unity desktop sessions
  running at the same time.  One for the local desktop, one for a remote
  desktop.  This almost works, except that when starting the second
  Unity session, the compiz process that belongs to the first one is
  killed because of this code in /usr/bin/unity:

  # kill a previous compiz if was there (this is a hack as compiz can
  # sometimes get stuck and not exit on --replace)
  subprocess.call ([pkill, -9, compiz])

  Commenting this line makes both desktop sessions work fine.

  This kill is far too harsh.  If you want to kill compiz, you should
  make sure that you are killing it in the same DISPLAY as the session
  that you are about to start, and not just every possible compiz
  process that is running.

  Please consider either removing the kill or making it apply only to
  processes in the same DISPLAY.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1324114/+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 1326788] Re: debian/rules clean does not clean adequately

[Ubuntu Foundations Team Bug Bot]

The attachment Crude fix for the problem seems to be a patch.  If it
isn't, please remove the patch flag from the attachment, remove the
patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  debian/rules clean does not clean adequately

Status in “unity-lens-applications” package in Ubuntu:
  New

Bug description:
  This is a problem in the unity-lens-applications source package.

  According to Ubuntu policy, the clean rule in debian/rules  must
  undo any effects that the build and binary targets may have had,
  except that it should leave alone any output files created in the
  parent directory by a run of a binary target.  That target in unity-
  lens-applications does not do this:

  root@chickatrice:/tmp# apt-get source 
unity-lens-applications=7.1.0+13.10.20131011-0ubuntu2 /dev/null 21
  root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 | wc 
-l92
  root@chickatrice:/tmp# ( cd unity-lens-applications-7.1.0+13.10.20131011  
debian/rules build  debian/rules clean ) /dev/null 21
  root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011 | wc 
-l103
  root@chickatrice:/tmp# rm -r unity*
  root@chickatrice:/tmp# apt-get source 
unity-lens-applications=7.1.0+13.10.20131011-0ubuntu2 /dev/null 21
  root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011  
files.before
  root@chickatrice:/tmp# ( cd unity-lens-applications-7.1.0+13.10.20131011  
debian/rules build  debian/rules clean ) /dev/null 21
  root@chickatrice:/tmp# find unity-lens-applications-7.1.0+13.10.20131011  
files.after
  root@chickatrice:/tmp# diff files.before files.after | grep '^'
   unity-lens-applications-7.1.0+13.10.20131011/tests/unit/aptd-client.c
   
unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-data-cache.c
   unity-lens-applications-7.1.0+13.10.20131011/tests/unit/xapian-utils.c
   unity-lens-applications-7.1.0+13.10.20131011/tests/unit/schemas.c
   
unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-utils.c
   
unity-lens-applications-7.1.0+13.10.20131011/tests/unit/software-center-app-details.c
   unity-lens-applications-7.1.0+13.10.20131011/tests/unit/utils.c
   
unity-lens-applications-7.1.0+13.10.20131011/tests/unit/purchase-info-helper.c
   unity-lens-applications-7.1.0+13.10.20131011/tests/unit/app-watcher.c
   unity-lens-applications-7.1.0+13.10.20131011/data/applications.scope
   unity-lens-applications-7.1.0+13.10.20131011/data/scopes.scope

  It looks like some of the files generating while building are not
  correctly removed while cleaning.  This is a problem if (as I do) you
  want to convert the package to use the 3.0 (quilt) source format.

  The attached patch fixes the problem, but probably more crudely than
  is acceptable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1326788/+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 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged

[Ubuntu Foundations Team Bug Bot]

The attachment Patch to give laptop battery always highest precedence
seems to be a patch.  If it isn't, please remove the patch flag from
the attachment, remove the patch tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Mouse with no time remaining estimate showing in preference to battery
  being charged

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

Bug description:
  When my laptop battery is in a charging state, but is not fully
  charged, I expect it to be displayed in preference to my mouse, which
  has no time remaining estimate.

  The spec here:

  https://wiki.ubuntu.com/Power

  says:

  If anything is discharging, the menu title should represent the
  component (not battery, but component) that is estimated to lose power
  first. For example, if your notebook battery is estimated to discharge
  in 1 hour 47 minutes, and your wireless mouse battery is estimated to
  discharge in 27 minutes, the menu title should represent the mouse. 

  but there doesn't seem to be any guideline to what happens when a
  battery is being charged.

  I suggest the time remaining to charge a battery should be displayed
  in preference to the power level in a wireless mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 11:50:36 2014
  InstallationDate: Installed on 2013-11-26 (156 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1315434/+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 1312749] Re: German translation: password wrong text is too long and destroys layout

[Ubuntu Foundations Team Bug Bot]

The attachment diff seems to be a patch.  If it isn't, please remove
the patch flag from the attachment, remove the patch tag, and if you
are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  German translation: password wrong text is too long and destroys
  layout

Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  When I try to log in with a wrong password, the string which informs
  me about the wrong password is too long (I will attach a screenshot)
  it makes the password box enlarge, which makes the right end of it
  (with the circle, that is spinning while logging in) disappear.

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

[Ubuntu Foundations Team Bug Bot]

** Attachment removed: VarLogDistupgradeTermlog.gz
   
https://bugs.launchpad.net/bugs/1309522/+attachment/4087422/+files/VarLogDistupgradeTermlog.gz

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

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

Status in “libappindicator” package in Ubuntu:
  New

Bug description:
  updated to 14.04 from 12.04 and multiple problems occured.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-appindicator
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Fri Apr 18 17:19:15 2014
  DuplicateSignature: 
package:python-appindicator:12.10.1+13.10.20130920-0ubuntu4:ErrorMessage: 
subprocess new pre-removal script returned error exit status 1
  ErrorMessage: ErrorMessage: subprocess new pre-removal script returned error 
exit status 1
  InstallationDate: Installed on 2011-08-06 (986 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  SourcePackage: libappindicator
  Title: package python-appindicator 12.10.1+13.10.20130920-0ubuntu4 failed to 
install/upgrade: ErrorMessage: subprocess new pre-removal script returned error 
exit status 1
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1309522/+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 1283849] Re: LIM breaks middle click title bar

[Ubuntu Foundations Team Bug Bot]

The attachment Quick fix - Lower action is hardcoded in. seems to be a
patch.  If it isn't, please remove the patch flag from the attachment,
remove the patch tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  LIM breaks middle click title bar

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

Bug description:
  On previous versions of Ubuntu without LIM, middle clicking the titlebar 
would send a window to the back of the stack.
  With LIM on Ubuntu 14.04 that no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,grid,imgpng,gnomecompat,scale,workarounds,mousepoll,regex,wall,move,place,vpswitch,resize,unitymtgrabhandles,snap,session,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Sun Feb 23 22:58:06 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-06-29 (604 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-01-20 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1283849/+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 733349] Re: Minimize Application's Windows upon clicking its Launcher Icon

[Ubuntu Foundations Team Bug Bot]

The attachment Allows for minimizing windows from the launcher on Unity
2D seems to be a patch.  If it isn't, please remove the patch flag
from the attachment, remove the patch tag, and if you are a member of
the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Minimize Application's Windows upon clicking its Launcher Icon

Status in Ayatana Design:
  Won't Fix
Status in Obsolete project please ignore:
  Invalid
Status in Unity:
  In Progress
Status in Unity Tweak Tool:
  Won't Fix
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  What I do miss in Unity is the possibility to click on the app. icon on the 
Unity launcher bar to minimize all windows of that application, not only to 
launch/restore it.
  mlaverdiere's futher addition: 
https://bugs.launchpad.net/ayatana-design/+bug/733349/comments/2

  My suggestion would be to modify the interaction-design/process like
  this (*=my modification proposal/2 cents!):

  1) start it, if it hasn't been started yet;
  *2) restore it, if it is minimized;
  *3) focus the app, if it's started, not minimized and has not the focus yet;
  4) spread windows (of app), if app is focused and has multiple windows open;
  *5) minimize it if it is in spread-mode (see 4).

  Note that this bug has over 300 comments and several working but
  rejected patches. This means that this feature probably will never
  land in official Unity! So if you want it, you have to use a patched
  version of Unity.

  There is a working patch for 13.04 ( from comment #322,
  https://bugs.launchpad.net/ayatana-
  design/+bug/733349/+attachment/3573380/+files/minimize.patch ).
  Somebody should set up a PPA (and note it here) to make it easy to
  install the patched version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/733349/+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 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager

[Ubuntu Foundations Team Bug Bot]

The attachment Patch for powerbtn.sh which checks for qdbus
availabilities. seems to be a patch.  If it isn't, please remove the
patch flag from the attachment, remove the patch tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Pressing power button turns off the PC ignoring the presence of
  another session manager

Status in “gnome-session” package in Ubuntu:
  Fix Released
Status in “kde-workspace” package in Ubuntu:
  Triaged
Status in “systemd” package in Ubuntu:
  Fix Released
Status in “systemd-shim” package in Ubuntu:
  Invalid

Bug description:
  In saucy the PC powers down as soon as I press the power button, it
  seems that systemd is calling poweroff, but I'm not sure if it's
  doing that in response of some other event (i.e. as callback of a dbus
  call):

  root  4998  0.0  0.0 177932  2104 ?Sl   20:41   0:00 
/usr/lib/x86_64-linux-gnu/systemd-shim
  root  5012  0.0  0.0   4440   624 ?S20:41   0:00  \_ sh -c 
/sbin/poweroff
  root  5013  0.0  0.0   4440   628 ?S20:41   0:00  \_ 
/bin/sh /sbin/shutdown -h -P now

  In any case the caller or systemd itself should be aware that there's
  a session-manager running and that it shouldn't actually directly
  power off the system then.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+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 1291370] Re: in virtual-manager, the global-menu or local integrated menus stopped working in the vm-display

[Ubuntu Foundations Team Bug Bot]

The attachment virt-manager_0.9.5-1ubuntu3.debdiff seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the patch flag from the
attachment, remove the patch tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  in virtual-manager, the global-menu or local integrated menus stopped
  working in the vm-display

Status in “unity-gtk-module” package in Ubuntu:
  Confirmed
Status in “virt-manager” package in Ubuntu:
  Invalid

Bug description:
  1) open virtual manager
  2) create / open a virtual machine
  3) start it
  4) try to open menu Send keys - Ctrl Alt F2

  the menu titles File, Virtual Machine, ... are visible but it's not
  possible to expand them, see any options under them, or click on them.

  I believe virtual manager is using python-gtk2.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-gtk2-module 0.0.0+14.04.20140311-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 12 13:24:29 2014
  InstallationDate: Installed on 2012-01-12 (789 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318)
  SourcePackage: unity-gtk-module
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1291370/+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 1288957] Re: Add option to restore behavior of using mouse scrollwheel to focus app windows

[Ubuntu Foundations Team Bug Bot]

The attachment lp1288957.patch seems to be a patch.  If it isn't,
please remove the patch flag from the attachment, remove the patch
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Add option to restore behavior of using mouse scrollwheel to focus app
  windows

Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  The fixes for bug #1263786 and bug #1267888 has caused headaches for
  users who were used to focusing inactive windows using the scrollwheel
  on the Launcher icon of opened apps.

  We should have an option in the CCSM Unity plugin that will allow
  users to restore this behavior if they want that behavior back.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1288957/+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 1286784] Re: Inconsistent scrollwheel launcher behavior for window switching.

[Ubuntu Foundations Team Bug Bot]

The attachment Non-invasive minimal fix. seems to be a patch.  If it
isn't, please remove the patch flag from the attachment, remove the
patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Inconsistent scrollwheel launcher behavior for window switching.

Status in Ayatana Design:
  New
Status in Unity:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  Background:
  I believe it first landed in 13.04 that scrolling the mouse wheel over 
launcher icons would flip through multiple windows of that app or do nothing if 
that app was not open. IMO, this is exactly what Unity was missing that I 
couldn't put a finger on for myself and I love it!! This worked exactly as 
described there for all lauchers regardless of what app was focused. 
Apparently, working on unfocused apps was unintentional but at this point it 
has been in use in the wild for a while. This unintended feature has recently 
been removed in the fix for #1263786 and #1267888.

  Current Sitution:
  The recurring theory in this scrollwheel discussion has been that whatever 
scrolling in one direction does, scrolling in the opposite direction should 
undo. The primary focus of this bug is just to define where such opposite 
scrolling needs fixing. But it must also be pointed out that fixing these 
behaviors resolves some complaints against the aforementioned unintended 
feature making its removal unnecessary. And a consistent approach to this could 
also solve some other hotly requested use cases.

  1. Single App Use Case

  1.1. Steps to Reproduce

  1.1.1. Open 4 Terminals. They should naturally position into the 4 corners so 
let's refer to them as NorthWest, NorthEast, SouthWest, SouthEast (NW, NE, SW, 
SE).
  1.1.2. Click through them all to force a Z order. Of course the Z order will 
be the opposite of the click order so I click through them intentionally 
backwards bottom to top and right to left: SE, SW, NE, NW. My Z order is now 
NW, NE, SW, SE; NW is the focused window.
  1.1.3. Mouseover Terminal Launcher and Scrollwheel Down Repeatedly, 
eventually coming to rest on NW again as the focused window. This proceeds 
through and loops the Z order as expected: NW, NE, SW, SE, ... NW
  1.1.4. Mouseover Terminal Launcher and Scrollwheel Up Repeatedly, eventually 
coming to rest again on NW. This reverses through and loops the Z order as 
expected: SE, SW, NE, NW ... NW
  1.1.5 Mouseover Terminal Launcher and Scrollwheel Down 1 notch and then Up 1 
notch.

  1.2. Expected Results: Down Goes from NW to NE and Up goes back from NE to 
NW. Z order should remain unchanged: NW, NE, SW, SE.
  1.3. Actual Results: Down Goes from NW to NE and Up goes from NE to SE.
  1.4. Reasoning: The Up abrubtly terminates the Down process causing NE to 
gain focus and leaving the new Z order NE, NW, SW, SE. Now the new Up process 
immediately processes from the bottom of the Z order to SE. Presumably if this 
Up process is completed here and SE gains focus the Z order ends at SE, NE, NW, 
SW. This can be confirmed by swicthing direction again and scrolling down 
repeatedly.
  1.5. Preferred Fix: Scrollwheel Up and Down should proceed through the Z 
order but should not be independent. In other words, an App Launcher Scrolling 
Event on the focused should grab and freeze the Z order of all App windows and 
scroll through the them, up or down, until all scrolling is done.
  1.6. Alternative Fix: If Scrolling were changed to proceed through some sort 
of spacial relationship instead of Z order it would not matter if they were 
independent. However, behavior for windows of identical geometry would then be 
undefined.
  1.7. Alternative Fix: If Scrolling were changed to always proceed through the 
order shown in the Launcher context menu it would not matter. This would also 
most closely resemble previous mouse wheel behavior on the old Gnome 2 window 
list panel. Presumably this ordering is defined by window creation order or 
age.

  
  2. Multitasking Use Case

  2.1 Steps to Reproduce

  2.1.1. Same as 1.1.1. Open 4 Terminals.
  2.1.2. Same as 1.1.2. Force Z Order NW, NE, SW, SE.
  2.1.3. Click Other Launcher. Other App (Firefox in my case) is 
opened/focused. The effects of later steps are easiest to noticed when this 
other App is maximized.
  2.1.4. Click Terminal Launcher. As expected NW Terminal is focused; all other 
terminals remain below Other App (OA). Z Order is NW, OA.
  2.1.5. Scrollweel Down Repeatedly. This is a part of the genius of the whole 
Scrollwheel feature!! As expected, this cycles through the terminals in Z order 
but always keeps 

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

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

-- 
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 331949] Re: Bubble colors and translucency are not customizable (by user or gtkrc)

[Ubuntu Foundations Team Bug Bot]

The attachment Frugalware patch seems to be a patch.  If it isn't,
please remove the patch flag from the attachment, remove the patch
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

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

Title:
  Bubble colors and translucency are not customizable (by user or gtkrc)

Status in Aachen:
  Confirmed
Status in “notify-osd” package in Ubuntu:
  In Progress

Bug description:
  The foreground and background colors composing the bubble's appearance
  need to be user customizable. Ideally, they should respect the GTK+
  theme, so when the user is using a high-contrast theme the bubbles
  would be adequately visible.

  I think a usable way of going about this is to have some custom themes
  like Jaunty, Happy, Disco, and have another option called
  System Theme which when used will simply respect the current GTK+
  theme.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aachen/+bug/331949/+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 724326] Re: rename dbus service file to avoid conflicts

[Ubuntu Foundations Team Bug Bot]

The attachment rename_dbus_service_file.bundle seems to be a patch.
If it isn't, please remove the patch flag from the attachment, remove
the patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: 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/724326

Title:
  rename dbus service file to avoid conflicts

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

Bug description:
  rename dbus service file to avoid conflicts.
  attached is a bundle that renames it to 
net.launchpad.notify-osd.Notifications.service
  This allows to have more then one implementation installed (how stupid that 
may be though).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/724326/+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 496129] Re: Notification bubble is sometimes misplaced

[Ubuntu Foundations Team Bug Bot]

The attachment slot_allocation.diff seems to be a patch.  If it isn't,
please remove the patch flag from the attachment, remove the patch
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: 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/496129

Title:
  Notification bubble is sometimes misplaced

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

Bug description:
  Notification bubbles often appear lower than expected - in the second
  notification slot - as if there is an already existing notification.

  Note that this does not affect all notifications - roughly half the
  time, all notifications stack up correctly, however in some cases they
  do not.

  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/496129/+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 1257505] Re: Create Unity Control Center so can remain on old GNOME Control Center version

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

-- 
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 Eye of GNOME:
  New
Status in GNOME Color Manager:
  Incomplete
Status in GNOME Media Utilities:
  New
Status in The Gnome Thumbnail Image Viewer:
  Fix Released
Status in Nautilus:
  Fix Released
Status in “activity-log-manager” package in Ubuntu:
  Fix Released
Status in “chromium-browser” package in Ubuntu:
  In Progress
Status in “deja-dup” package in Ubuntu:
  Fix Released
Status in “empathy” package in Ubuntu:
  Confirmed
Status in “eog” package in Ubuntu:
  Fix Released
Status in “gnome-color-manager” package in Ubuntu:
  Fix Released
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:
  Fix Released
Status in “gthumb” package in Ubuntu:
  Fix Released
Status in “indicator-bluetooth” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Fix Released
Status in “indicator-power” package in Ubuntu:
  Fix Released
Status in “indicator-session” package in Ubuntu:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “landscape-client” package in Ubuntu:
  Fix Released
Status in “language-selector” package in Ubuntu:
  Fix Released
Status in “nautilus” package in Ubuntu:
  Fix Released
Status in “software-properties” package in Ubuntu:
  Fix Released
Status in “system-config-printer” package in Ubuntu:
  Fix Released
Status in “ubuntuone-control-panel” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Triaged
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 unity-control-center (see bug tasks).

  A PPA for testing is https://launchpad.net/~ubuntu-desktop/+archive
  /unity-control-center

To manage notifications about this bug go to:
https://bugs.launchpad.net/eog/+bug/1257505/+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 907640] Re: alt-backtick doesn't work properly

[Ubuntu Foundations Team Bug Bot]

The attachment Proposed debdiff for trusty seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the patch flag from the attachment, remove the
patch tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  alt-backtick doesn't work properly

Status in Ayatana Design:
  New
Status in The Metacity Window Manager:
  New
Status in “metacity” package in Ubuntu:
  New
Status in “unity-2d” package in Ubuntu:
  Confirmed

Bug description:
  In Unity (and I presume unity-2d) alt-backtick (alt-grave, alt-key-
  above-tab) is meant to flip between the active windows of the current
  application.  In precise unity-2d for me it shows a switcher window
  with 4 icons for the four windows of my current app (chrome), but
  repeated presses of backtick while holding alt just flip between the
  focussed window and the next window, not around all four.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity-2d 4.12.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-5.11-generic 3.2.0-rc5
  Uname: Linux 3.2.0-5-generic x86_64
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  Date: Thu Dec 22 16:23:53 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  PackageArchitecture: all
  SourcePackage: unity-2d
  UpgradeStatus: Upgraded to precise on 2011-12-15 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/907640/+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 976100] Re: Time and Date Settings don't load in Ubuntu Precise and newer with Gnome Classic

[Ubuntu Foundations Team Bug Bot]

The attachment indicator-datetime_0.3.94-0ubuntu2.1.debdiff seems to
be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff.  If
the attachment isn't a patch, please remove the patch flag from the
attachment, remove the patch tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Time and Date Settings don't load in Ubuntu Precise and newer with
  Gnome Classic

Status in The Date and Time Indicator:
  In Progress
Status in “indicator-datetime” package in Ubuntu:
  Triaged
Status in “indicator-datetime” source package in Precise:
  Triaged

Bug description:
  STEPS TO REPRODUCE:

  1) Install gnome-panel to have Ubuntu Classic

  2) Login to Ubuntu Gnome Classic with Effects

  3) Click on the Time Indicator

  4) Select Time and Date Settings

  5) System Settings is opened. We have to find date and time
  manually.

  
  DESIRED OUTPUT:

  4) Select Time and Date Settings

  5) System Settings-  Date and Time should be opened.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: indicator-datetime 0.3.94-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sat Apr  7 10:49:05 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120325)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/976100/+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 1242633] [unity/precise] possible regression found

[Ubuntu Foundations Team Bug Bot]

As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of unity from precise-proposed
was performed and bug 1263392 was found.  Please investigate this bug
report to ensure that a regression will not be created by this SRU. In
the event that this is not a regression remove the verification-failed
tag from this bug report and tag 1263392 bot-stop-nagging. Thanks!

** Tags added: verification-failed

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

Title:
  unity pointer barriers sru bug

Status in “libxfixes” package in Ubuntu:
  In Progress
Status in “libxi” package in Ubuntu:
  In Progress
Status in “qt4-x11” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress
Status in “unity-2d” package in Ubuntu:
  In Progress
Status in “x11proto-input” package in Ubuntu:
  In Progress
Status in “libxfixes” source package in Precise:
  Fix Committed
Status in “libxi” source package in Precise:
  Fix Committed
Status in “qt4-x11” source package in Precise:
  Fix Committed
Status in “unity” source package in Precise:
  Fix Committed
Status in “unity-2d” source package in Precise:
  Fix Committed
Status in “x11proto-input” source package in Precise:
  Fix Committed

Bug description:
  x11proto-input, libxfixes, libxi, unity and unity-2d in precise needs
  updates to work with the new pointer barrier api from x1.14.

  [Impact]
   * Pointer barrier api has changed between 1.13 and 1.14. 
(xorg-server-lts-saucy)
   * Modifications in unity and unity-2d are required to support both api's.

  [Test Case]
   * Update all packages.
   * Test pointer barriers on an old xorg-server, they should continue to work.
   * Test pointer barriers on the new xorg-server, they should work.

  [Regression Potential]
    * Low, it enables a separate code path for pointer barriers. The code in 
unity is a bit different due to copying the rework from upstream unity and 
keeping the old paths for legacy pointer barriers. Upstream dropped the old 
paths.

  [Other Info]
    * It's a bit of a hack. The old pointer barrier symbols live in libxfixes, 
the new ones in libxi. Because of the overlap some modifications had to be made 
to allow both pointer barriers to be included. This works as well as it can.
   * Depending on the queried libxi2/libxfixes versions, old pointer barriers 
or new ones are used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxfixes/+bug/1242633/+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 1195481] [gnome-control-center/saucy] possible regression found

[Ubuntu Foundations Team Bug Bot]

As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of gnome-control-center from
saucy-proposed was performed and bug 1245199 was found.  Please
investigate this bug report to ensure that a regression will not be
created by this SRU. In the event that this is not a regression remove
the verification-failed tag from this bug report and tag 1245199 bot-
stop-nagging. Thanks!

** Tags added: verification-failed

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

Title:
  [power]: gnome-control-center crashes if indicator-power is not
  installed in Unity

Status in One Hundred Papercuts:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  [ Description ]

  gnome-control-center's power panel crashes when indicator-power isn't
  installed.

  [ Test case ]

  1. Uninstall indicator-power
  2. Open System Settings and click Power
  3. System Settings crashes

  At 3 it shouldn't crash. If you have indicator-power installed, you
  should see the option to configure whether it shows.

  [ Regression potential ]

  This adds some new code to check if the GSettings schema is installed, since
  that's a reliable way to check for indicator-power's presence, and is what the
  code modifies. It also makes the option appear in DEs other than Unity.

  There's a chance that the GSettings schema-detection work could be wrong. It
  also wouldn't hurt to check non-Unity environments such as a gnome-panel
  session.

  [ Original report ]

  I see that unity recommends indicator-power; let's make it a depends
  instead.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu29
  ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
  Uname: Linux 3.9.0-7-generic x86_64
  NonfreeKernelModules: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs 
ext2 overlayfs nls_utf8 isofs pci_stub vboxpci vboxnetadp vboxnetflt vboxdrv 
parport_pc ppdev rfcomm bnep dm_crypt intel_powerclamp coretemp kvm_intel kvm 
joydev crc32_pclmul ghash_clmulni_intel arc4 cryptd ath9k dm_multipath scsi_dh 
ath9k_common ath9k_hw uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_core ath snd_hda_codec_hdmi snd_hda_codec_conexant mac80211 
snd_hda_intel videodev ath3k btusb snd_hda_codec bluetooth cfg80211 snd_hwdep 
snd_pcm psmouse microcode toshiba_acpi toshiba_bluetooth serio_raw 
sparse_keymap snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer snd mei soundcore lpc_ich mac_hid lp parport 
btrfs xor zlib_deflate raid6_pq libcrc32c dm_mirror dm_region_hash dm_log 
ums_realtek usb_storage i915 i2c_algo_bit drm_kms_helper drm atl1c ahci libahci 
wmi video
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  Date: Thu Jun 27 17:42:04 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-06-14 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 
(20130613)
  MarkForUpload: True
  ProcCmdline: gnome-control-center
  Signal: 5
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/control-center-1/panels/libpower.so
  Title: [power]: gnome-control-center crashed with signal 5 in 
g_object_new_valist()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.5-0ubuntu1
   deja-dup27.3.1-0ubuntu1
   gnome-control-center-signon 0.1.7~+13.10.20130625-0ubuntu1
   gnome-control-center-unity  1.3daily13.06.14.1-0ubuntu1
   indicator-datetime  12.10.3daily13.06.19-0ubuntu1

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

[Ubuntu Foundations Team Bug Bot]

The attachment notify-osd-lp404658.patch seems to be a patch.  If it
isn't, please remove the patch flag from the attachment, remove the
patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: 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 1227920] Re: after suspend/resume, the Unity HUD is always open when I unlock the screen

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  after suspend/resume, the Unity HUD is always open when I unlock the
  screen

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

Bug description:
  Traveling at a conference, so I'm doing a lot of suspending and
  resuming of my laptop.  Every time I open my laptop back up after
  resume and unlock the desktop, the Unity dash is open.  This does not
  happen if I lock my screen using the lock screen hotkey, and does
  not happen if my screen is locked by a lid close event; only when the
  system suspends and resumes.  But it is 100% reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,imgpng,snap,place,grid,resize,regex,mousepoll,gnomecompat,unitymtgrabhandles,vpswitch,move,animation,expo,session,wall,ezoom,staticswitcher,workarounds,fade,scale,unityshell]
  Date: Thu Sep 19 17:51:29 2013
  InstallationDate: Installed on 2010-09-24 (1091 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 
(20100816.1)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (136 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1227920/+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 1228570] Re: Login often fails

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Login often fails

Status in “lightdm” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Invalid
Status in “xorg” package in Ubuntu:
  Invalid

Bug description:
  I am using the Lenovo Thinkpad Twist with Saucy and the standard Unity
  desktop. Often when I log in, after entering the password the screen
  gets black and within one second I am back in LightDM. I have to enter
  my password three or four times until getting a successful login.
  Logging in right after reboot works more often. Logging into the guest
  account always works.

  There are no messages in .xsession-errors. /var/log/syslog adds the
  following lines after pressing Enter after entering the password until
  LightDM re-appearing:

  First failed attempt:

  Sep 21 13:28:05 till-twist colord: device removed: xrandr-LVDS1
  Sep 21 13:28:05 till-twist colord: Profile removed: 
icc-212ca362d5002958378e8fefb0ad7943
  Sep 21 13:28:05 till-twist colord: Profile removed: 
icc-f5a7781aa544aba4d0654c67690ec8d4
  Sep 21 13:28:05 till-twist colord: Profile removed: 
icc-42cf0f25cbd914f2177438317b72f222
  Sep 21 13:28:05 till-twist NetworkManager[1705]: warn error requesting auth 
for org.freedesktop.NetworkManager.wifi.share.open: (3) 
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: 
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of 
name ':1.139': no such name
  Sep 21 13:28:05 till-twist acpid: client 7242[0:0] has disconnected
  Sep 21 13:28:05 till-twist acpid: client connected from 7493[0:0]
  Sep 21 13:28:05 till-twist acpid: 1 client rule loaded
  Sep 21 13:28:05 till-twist dbus[574]: [system] Activating service 
name='org.freedesktop.systemd1' (using servicehelper)
  Sep 21 13:28:05 till-twist dbus[574]: [system] Successfully activated service 
'org.freedesktop.systemd1'
  Sep 21 13:28:06 till-twist colord: Device added: xrandr-LVDS1
  Sep 21 13:28:06 till-twist colord: Profile added: 
icc-212ca362d5002958378e8fefb0ad7943
  Sep 21 13:28:06 till-twist colord: Automatic metadata add 
icc-f5a7781aa544aba4d0654c67690ec8d4 to xrandr-LVDS1
  Sep 21 13:28:06 till-twist colord: Profile added: 
icc-f5a7781aa544aba4d0654c67690ec8d4
  Sep 21 13:28:06 till-twist colord: Profile added: 
icc-42cf0f25cbd914f2177438317b72f222

  Second failed attempt:

  Sep 21 13:34:42 till-twist colord: device removed: xrandr-LVDS1
  Sep 21 13:34:42 till-twist colord: Profile removed: 
icc-212ca362d5002958378e8fefb0ad7943
  Sep 21 13:34:42 till-twist colord: Profile removed: 
icc-f5a7781aa544aba4d0654c67690ec8d4
  Sep 21 13:34:42 till-twist colord: Profile removed: 
icc-42cf0f25cbd914f2177438317b72f222
  Sep 21 13:34:42 till-twist NetworkManager[1705]: warn error requesting auth 
for org.freedesktop.NetworkManager.wifi.share.protected: (3) 
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: 
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of 
name ':1.160': no such name
  Sep 21 13:34:42 till-twist NetworkManager[1705]: warn error requesting auth 
for org.freedesktop.NetworkManager.wifi.share.open: (3) 
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: 
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of 
name ':1.160': no such name
  Sep 21 13:34:43 till-twist acpid: client 7493[0:0] has disconnected
  Sep 21 13:34:43 till-twist acpid: client connected from 7737[0:0]
  Sep 21 13:34:43 till-twist acpid: 1 client rule loaded
  Sep 21 13:34:43 till-twist dbus[574]: [system] Activating service 
name='org.freedesktop.systemd1' (using servicehelper)
  Sep 21 13:34:43 till-twist dbus[574]: [system] Successfully activated service 
'org.freedesktop.systemd1'
  Sep 21 13:34:43 till-twist colord: Device added: xrandr-LVDS1
  Sep 21 13:34:43 till-twist colord: Profile added: 
icc-212ca362d5002958378e8fefb0ad7943
  Sep 21 13:34:43 till-twist colord: Automatic metadata add 
icc-f5a7781aa544aba4d0654c67690ec8d4 to xrandr-LVDS1
  Sep 21 13:34:43 till-twist colord: Profile added: 
icc-f5a7781aa544aba4d0654c67690ec8d4
  Sep 21 13:34:43 till-twist colord: Profile added: 
icc-42cf0f25cbd914f2177438317b72f222

  Third failed attempt:

  Sep 21 13:34:53 till-twist whoopsie[1969]: online
  Sep 21 13:35:43 till-twist colord: device removed: xrandr-LVDS1
  Sep 21 13:35:43 till-twist colord: Profile removed: 
icc-212ca362d5002958378e8fefb0ad7943
  Sep 21 13:35:43 till-twist colord: Profile removed: 
icc-f5a7781aa544aba4d0654c67690ec8d4
  Sep 21 13:35:43 till-twist colord: Profile removed: 
icc-42cf0f25cbd914f2177438317b72f222
  Sep 21 13:35:43 till-twist NetworkManager[1705]: warn error requesting auth 
for org.freedesktop.NetworkManager.wifi.share.protected: (3) 
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: