date:20160911

** Changed in: dbus (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1622401

Title:
  Merge dbus 1.10.10-1 (main) from Debian unstable (main)

Status in dbus package in Ubuntu:
  Fix Committed

Bug description:
  Please merge dbus 1.10.10-1 (main) from Debian unstable (main)

  1.10.10 is a bugfix release in the stable 1.10 series.

  https://sources.debian.net/src/dbus/1.10.10-1/NEWS/

  https://cgit.freedesktop.org/dbus/dbus/log/?h=dbus-1.10

  I am personally interested in Debian's virtual default-dbus-session-
  bus package since Debian is increasingly depending on it instead of
  directly depending on dbus-x11.

  https://lists.debian.org/debian-devel/2016/08/msg00554.html

  Explanation of the Ubuntu delta and why it can be dropped:
    - debian/dbus.preinst: divert the dbus-daemon-launch-helper if upgrading
  from < 1.9.4-2~. This will make sure we keep the setuid bit during 
upgrade.
     (LP: #1555237)
   Not needed after Ubuntu 16.04 LTS

  Explanation of the remaining Ubuntu delta
  - Add upstart jobs
    + debian/dbus.upstart and debian/dbus.user-session.upstart
  - debian/dbus.postinst: remove diversion.
  - debian/rules: Don't start D-Bus on package installation, as that doesn't
    work any more. Instead, start dbus.socket in postinst, which will then
    start D-Bus on demand after package installation.
  - Add debian/patches/dont-stop-dbus.patch: Don't stop D-Bus in the service
    unit (see patch header and upstream bug for details). Fixes various
    causes of shutdown hangs, particularly with remote file systems. (LP:
    #1438612) (LP: #1540282)
  - aa-get-connection-apparmor-security-context.patch: This is not
    intended for upstream inclusion. It implements a bus method
    (GetConnectionAppArmorSecurityContext) to get a connection's AppArmor
    security context but upstream D-Bus has recently added a generic way of
    getting a connection's security credentials (GetConnectionCredentials).
    Ubuntu should carry this patch until packages in the archive are moved
    over to the new, generic method of getting a connection's credentials.

  Changelog entries since current yakkety version 1.10.6-1ubuntu4:

  dbus (1.10.10-1) unstable; urgency=medium

    * New upstream stable release 1.10.10
    * Provide new virtual packages for other packages to depend on:
  - dbus-session-bus: any implementation of the D-Bus well-known session bus
    (provided by: dbus-user-session, dbus-x11)
  - default-dbus-session-bus: the recommended implementation of
    dbus-session-bus (currently provided by: dbus-user-session)
    * Add arm64, mips64el, ppc64el to the list of architectures that
  have valgrind
    * debian/gbp.conf: use DEP-14 branch names
    * Standards-Version: 3.9.8 (no changes needed)
    * debian/rules: fail the build if "make install" installs anything we
  don't package or delete. Only do this for final releases (suite
  in debian/changelog is not UNRELEASED) to facilitate future
  autobuilding of new upstream releases.
    * debian/rules: do not require symbols file to be complete if the
  suite in debian/changelog is UNRELEASED, again to facilitate
  autobuilding new upstream releases.
    * debian/source/options: don't fail dpkg-source on changes to
  build-aux/{compile,depcomp,missing}. We regenerate that directory anyway,
  and during a snapshot build they might become symlinks.
    * debian/rules: do the build in debian/build-* so it's easier to .gitignore
    * debian/.gitignore: update
    * Use the correct systemctl for Debian even if not installed on the build
  system. (Regression in 1.10.2)

   -- Simon McVittie   Mon, 15 Aug 2016 22:05:45 +0100

  dbus (1.10.8-1) unstable; urgency=medium

    * New upstream release
    * dbus.prerm: ensure that dbus.socket is stopped before removal,
  so that a new connection to the bus won't cause dbus.service to be
  restarted (Closes: #813970)
    * debian/75dbus_dbus-launch: when not using systemd --user or the
  dbus-user-session package is not installed, start dbus-daemon early,
  then upload the full environment from Xsession.d later on
  (in 95dbus_update-activation-env). This more closely matches the
  behaviour with dbus-user-session. (Closes: #815503; thanks to Samuel
  Thibault)
    * Switch Vcs-Git to https (see #810378)
    * debian/upstream/signing-key.asc: add upstream signing keys
  (just my keys for now, in practice I do almost all dbus releases)
    * debian/watch: use https and describe how to download signatures
    * Standards-Version: 3.9.7 (no changes needed)
    * Sort .install files and remove unnecessary debian/tmp prefix
    * Normalize lists of packages and

[Touch-packages] [Bug 1622089] Re: timezone parser in qt-5.5 breaks KDE clock

2016-09-11 Thread Timo Jyrinki

Sounds like a good candidate for stable release upgrade to 16.04 LTS.
Thank you for the bug report!

It will take some time as it will first need to be landed to 16.10 (the
patch is in Qt 5.6.2, 16.10 has 5.6.1), and then the SRU process
(https://wiki.ubuntu.com/StableReleaseUpdates) also takes some time.

https://codereview.qt-project.org/#/c/157499/

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Confirmed

** Also affects: qtbase-opensource-src (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: qtbase-opensource-src (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

** Changed in: qtbase-opensource-src (Ubuntu Xenial)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1622089

Title:
  timezone parser in qt-5.5 breaks KDE clock

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src source package in Xenial:
  Confirmed

Bug description:
  For a set of timezones in tzdata-2016*
  Qt parser produces wrong result in
  Qt versions earlier than 5.6.

  In kubuntu-16.04 xenial xerus the most annoying
  issue is broken digital clock plasmoid on the default KDE panel
  if system timezone is set to e.g. Asia/Novosibirsk.
  All Qt programs that attempts to convert time to non-default
  timezone are affected as well in xenial and earlier ubuntu released
  including ubuntu-14.04 LTS trusty.

  I consider the bug is nasty enough for updating Qt in LTS ubuntu
  releases.

  The upstream bug is https://bugreports.qt.io/browse/QTBUG-53071
  "QTimeZone mishandles tzdata 2016b and later in Russia, Kazakhstan".
  The direct link to the patch that fixes the problem is
  
https://codereview.qt-project.org/gitweb?p=qt/qtbase.git;a=patch;h=e9041c7fc1052167f1ec2df0ea9623059e55d00f

  I have rebuilt qtbase-opensource-src-5.5.1+dfsg (-16ubuntu7.1)
  from sources with the patch applied and the bug has gone away.

  A bit more details.

  I faced the problem with Kubuntu 16.04.1, x86_64.
  Asia/Novosibirsk has UTC+07:00 offset last a couple of months
  but KDE clock shows a time that has offset of 14 hours from the actual wall 
time,
  so it is rather unusable.
  Command line tool "date" reports correct local time.
  KDE digital clock works correctly in e.g. Asia/Krasnoyarsk timezone.
  It as a workaround if time transition history does not matter.

  Some other timezones affected by the bug (tzdata-2106f)
  file europe:
  Europe/Astrakhan
  Europe/Kirov
  Europe/Ulyanovsk
  Asia/Barnaul
  Asia/Novosibirsk
  Asia/Tomsk
  Asia/Novokuznetsk
  file asia:
  Asia/Almaty
  Asia/Qyzylorda
  Asia/Aqtobe
  Asia/Aqtau
  Asia/Oral

  A simple program to demonstrate the problem:

  #include 
  #include 
  #include 

  int main() {
  QTimeZone tz = QTimeZone(QTimeZone::systemTimeZoneId());
  QDateTime current = QDateTime::currentDateTime();
  qDebug() << "current offset" << tz.offsetFromUtc(current);
  return 0;
  }

  It reports 0 for incorrectly parsed timezones.

  The only thing that bothers me is that I had to disable tests
  when was rebuilding libqt5core5a_5.5.1+dfsg-16ubuntu7.1_amd64.deb
  using dpg-buildpackage. Otherwise I got error with cmake
  in tests/auto/cmake/. Cmake was unable to find qt libraries
  in the build tree.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1622089/+subscriptions

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

[Touch-packages] [Bug 1622401] Re: Merge dbus 1.10.10-1 (main) from Debian unstable (main)

LGTM, thanks! I'll take the liberty to add the cleanup of
/etc/init/dbus.conf.

** Changed in: dbus (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1622401

Title:
  Merge dbus 1.10.10-1 (main) from Debian unstable (main)

Status in dbus package in Ubuntu:
  In Progress

Bug description:
  Please merge dbus 1.10.10-1 (main) from Debian unstable (main)

  1.10.10 is a bugfix release in the stable 1.10 series.

  https://sources.debian.net/src/dbus/1.10.10-1/NEWS/

  https://cgit.freedesktop.org/dbus/dbus/log/?h=dbus-1.10

  I am personally interested in Debian's virtual default-dbus-session-
  bus package since Debian is increasingly depending on it instead of
  directly depending on dbus-x11.

  https://lists.debian.org/debian-devel/2016/08/msg00554.html

  Explanation of the Ubuntu delta and why it can be dropped:
    - debian/dbus.preinst: divert the dbus-daemon-launch-helper if upgrading
  from < 1.9.4-2~. This will make sure we keep the setuid bit during 
upgrade.
     (LP: #1555237)
   Not needed after Ubuntu 16.04 LTS

  Explanation of the remaining Ubuntu delta
  - Add upstart jobs
    + debian/dbus.upstart and debian/dbus.user-session.upstart
  - debian/dbus.postinst: remove diversion.
  - debian/rules: Don't start D-Bus on package installation, as that doesn't
    work any more. Instead, start dbus.socket in postinst, which will then
    start D-Bus on demand after package installation.
  - Add debian/patches/dont-stop-dbus.patch: Don't stop D-Bus in the service
    unit (see patch header and upstream bug for details). Fixes various
    causes of shutdown hangs, particularly with remote file systems. (LP:
    #1438612) (LP: #1540282)
  - aa-get-connection-apparmor-security-context.patch: This is not
    intended for upstream inclusion. It implements a bus method
    (GetConnectionAppArmorSecurityContext) to get a connection's AppArmor
    security context but upstream D-Bus has recently added a generic way of
    getting a connection's security credentials (GetConnectionCredentials).
    Ubuntu should carry this patch until packages in the archive are moved
    over to the new, generic method of getting a connection's credentials.

  Changelog entries since current yakkety version 1.10.6-1ubuntu4:

  dbus (1.10.10-1) unstable; urgency=medium

    * New upstream stable release 1.10.10
    * Provide new virtual packages for other packages to depend on:
  - dbus-session-bus: any implementation of the D-Bus well-known session bus
    (provided by: dbus-user-session, dbus-x11)
  - default-dbus-session-bus: the recommended implementation of
    dbus-session-bus (currently provided by: dbus-user-session)
    * Add arm64, mips64el, ppc64el to the list of architectures that
  have valgrind
    * debian/gbp.conf: use DEP-14 branch names
    * Standards-Version: 3.9.8 (no changes needed)
    * debian/rules: fail the build if "make install" installs anything we
  don't package or delete. Only do this for final releases (suite
  in debian/changelog is not UNRELEASED) to facilitate future
  autobuilding of new upstream releases.
    * debian/rules: do not require symbols file to be complete if the
  suite in debian/changelog is UNRELEASED, again to facilitate
  autobuilding new upstream releases.
    * debian/source/options: don't fail dpkg-source on changes to
  build-aux/{compile,depcomp,missing}. We regenerate that directory anyway,
  and during a snapshot build they might become symlinks.
    * debian/rules: do the build in debian/build-* so it's easier to .gitignore
    * debian/.gitignore: update
    * Use the correct systemctl for Debian even if not installed on the build
  system. (Regression in 1.10.2)

   -- Simon McVittie   Mon, 15 Aug 2016 22:05:45 +0100

  dbus (1.10.8-1) unstable; urgency=medium

    * New upstream release
    * dbus.prerm: ensure that dbus.socket is stopped before removal,
  so that a new connection to the bus won't cause dbus.service to be
  restarted (Closes: #813970)
    * debian/75dbus_dbus-launch: when not using systemd --user or the
  dbus-user-session package is not installed, start dbus-daemon early,
  then upload the full environment from Xsession.d later on
  (in 95dbus_update-activation-env). This more closely matches the
  behaviour with dbus-user-session. (Closes: #815503; thanks to Samuel
  Thibault)
    * Switch Vcs-Git to https (see #810378)
    * debian/upstream/signing-key.asc: add upstream signing keys
  (just my keys for now, in practice I do almost all dbus releases)
    * debian/watch: use https and describe how to download signatures
    * Standards-Version: 3.9.7 (no changes needed)
    * Sort .install files and remove

[Touch-packages] [Bug 1617063] Re: from alternate lubuntu installs network manager does not manage devices or give network info

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

** This bug has been marked a duplicate of bug 1616400
   Lubuntu's alternate i386 installer cannot connect to a network

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1617063

Title:
  from alternate lubuntu installs network manager does not manage
  devices or give network info

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  To reproduce on an alternate install complete the install with
  ethernet plugged in  and boot into the new install and log into to the
  lubuntu desktop and move over to the nm-applet and notice it says that
  your ethernet device is not managed and showing connectoin information
  fails

   Description: Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  network-manager:
Installed: 1.2.2-0ubuntu8
Candidate: 1.2.2-0ubuntu8
Version table:
   *** 1.2.2-0ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status
  I expected to be able to show connection info in network manager and connect 
disconnet to ethernet with this network manager with software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.2-0ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15
  Uname: Linux 4.4.0-9134-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Aug 25 14:11:11 2016
  InstallationDate: Installed on 2016-08-25 (0 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160825.1)
  IpRoute:
   default via 192.168.122.1 dev ens3 
   192.168.122.0/24 dev ens3  proto kernel  scope link  src 192.168.122.84
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile,ofono
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  ACTIVE-PATH 
   Wired connection 1  f8fb3e0c-4ddc-4d20-9585-954d34538369  802-3-ethernet  0  
never   yes  0 no
/org/freedesktop/NetworkManager/Settings/0  no  --  -- --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   ens3ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ----   
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  none  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1617063/+subscriptions

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

[Touch-packages] [Bug 1622403] Re: Sync pygobject 3.21.92-1 (main) from Debian unstable (main)

This bug was fixed in the package pygobject - 3.21.92-1
Sponsored for Jeremy Bicha (jbicha)

---
pygobject (3.21.92-1) unstable; urgency=medium

  * New upstream development release.
  * Drop patches which have been merged upstream.

 -- Michael Biebl   Sun, 11 Sep 2016 15:02:27 +0200

pygobject (3.21.91-2) unstable; urgency=medium

  [ Aurelien Jarno ]
  * Fix wrong enum to hash conversion on 64-bit big endian. (Closes: #835413)

  [ Michael Biebl ]
  * Use dbus-run-session instead of dbus-launch to run the tests.
(Closes: #836049)
  * Handle nullable filename parameters. This fixes a test suite error in
test_spawn_async_with_pipes triggered by an annotation change in glib.
  * Drop override for dh_python2, no longer needed.

 -- Michael Biebl   Sun, 04 Sep 2016 00:02:14 +0200

pygobject (3.21.91-1) experimental; urgency=medium

  * New upstream beta release.
  * Set Maintainer to Debian GNOME Maintainers
  * Add python{,3}-setuptools to build-dependencies
- as needed in debian/rules clean by the new setup.py

 -- Andreas Henriksson   Fri, 26 Aug 2016 10:57:27
+0200

pygobject (3.21.0-1) experimental; urgency=medium

  [ Michael Biebl ]
  * Drop --disable-silent-rules from debian/rules. This is now handled by dh
directly depending on whether the DH_QUIET environment variable is set.

  [ Andreas Henriksson ]
  * New upstream development release.

 -- Andreas Henriksson   Tue, 23 Aug 2016 13:31:24
+0200

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1622403

Title:
  Sync pygobject 3.21.92-1 (main) from Debian unstable (main)

Status in pygobject package in Ubuntu:
  Fix Released

Bug description:
  Please sync pygobject 3.21.92-1 (main) from Debian unstable (main)

  https://git.gnome.org/browse/pygobject/tree/NEWS
  https://git.gnome.org/browse/pygobject/log/

  Mattia Rizzolo ~mapreri recommended we sync pygobject 3.21
  to fix libsecret's tests hanging on s390x

  Changelog entries since current yakkety version 3.20.1-1:

  pygobject (3.21.92-1) unstable; urgency=medium

* New upstream development release.
* Drop patches which have been merged upstream.

   -- Michael Biebl   Sun, 11 Sep 2016 15:02:27 +0200

  pygobject (3.21.91-2) unstable; urgency=medium

[ Aurelien Jarno ]
* Fix wrong enum to hash conversion on 64-bit big endian. (Closes: #835413)

[ Michael Biebl ]
* Use dbus-run-session instead of dbus-launch to run the tests.
  (Closes: #836049)
* Handle nullable filename parameters. This fixes a test suite error in
  test_spawn_async_with_pipes triggered by an annotation change in glib.
* Drop override for dh_python2, no longer needed.

   -- Michael Biebl   Sun, 04 Sep 2016 00:02:14 +0200

  pygobject (3.21.91-1) experimental; urgency=medium

* New upstream beta release.
* Set Maintainer to Debian GNOME Maintainers
* Add python{,3}-setuptools to build-dependencies
  - as needed in debian/rules clean by the new setup.py

   -- Andreas Henriksson   Fri, 26 Aug 2016 10:57:27
  +0200

  pygobject (3.21.0-1) experimental; urgency=medium

[ Michael Biebl ]
* Drop --disable-silent-rules from debian/rules. This is now handled by dh
  directly depending on whether the DH_QUIET environment variable is set.

[ Andreas Henriksson ]
* New upstream development release.

   -- Andreas Henriksson   Tue, 23 Aug 2016 13:31:24
  +0200

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

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

[Touch-packages] [Bug 1622403] Re: Sync pygobject 3.21.92-1 (main) from Debian unstable (main)

Mostly just bug fixes and good test coverage, so fine for yakkety at
this point.

** Changed in: pygobject (Ubuntu)
   Status: New => Confirmed

** Changed in: pygobject (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1622403

Title:
  Sync pygobject 3.21.92-1 (main) from Debian unstable (main)

Status in pygobject package in Ubuntu:
  Fix Released

Bug description:
  Please sync pygobject 3.21.92-1 (main) from Debian unstable (main)

  https://git.gnome.org/browse/pygobject/tree/NEWS
  https://git.gnome.org/browse/pygobject/log/

  Mattia Rizzolo ~mapreri recommended we sync pygobject 3.21
  to fix libsecret's tests hanging on s390x

  Changelog entries since current yakkety version 3.20.1-1:

  pygobject (3.21.92-1) unstable; urgency=medium

* New upstream development release.
* Drop patches which have been merged upstream.

   -- Michael Biebl   Sun, 11 Sep 2016 15:02:27 +0200

  pygobject (3.21.91-2) unstable; urgency=medium

[ Aurelien Jarno ]
* Fix wrong enum to hash conversion on 64-bit big endian. (Closes: #835413)

[ Michael Biebl ]
* Use dbus-run-session instead of dbus-launch to run the tests.
  (Closes: #836049)
* Handle nullable filename parameters. This fixes a test suite error in
  test_spawn_async_with_pipes triggered by an annotation change in glib.
* Drop override for dh_python2, no longer needed.

   -- Michael Biebl   Sun, 04 Sep 2016 00:02:14 +0200

  pygobject (3.21.91-1) experimental; urgency=medium

* New upstream beta release.
* Set Maintainer to Debian GNOME Maintainers
* Add python{,3}-setuptools to build-dependencies
  - as needed in debian/rules clean by the new setup.py

   -- Andreas Henriksson   Fri, 26 Aug 2016 10:57:27
  +0200

  pygobject (3.21.0-1) experimental; urgency=medium

[ Michael Biebl ]
* Drop --disable-silent-rules from debian/rules. This is now handled by dh
  directly depending on whether the DH_QUIET environment variable is set.

[ Andreas Henriksson ]
* New upstream development release.

   -- Andreas Henriksson   Tue, 23 Aug 2016 13:31:24
  +0200

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

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

[Touch-packages] [Bug 1543921] Re: Make sure color fonts work

[Expired for fontconfig (Ubuntu) because there has been no activity for
60 days.]

** Changed in: fontconfig (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1543921

Title:
  Make sure color fonts work

Status in fontconfig package in Ubuntu:
  Expired

Bug description:
  Can someone please confirm that color fonts work in latest Ubuntu?

  Please install a sample font from:

https://github.com/behdad/color-
  emoji/blob/master/specification/examples/PhantomOpenEmoji.ttf

  then, at least in Chrome, you should be able to see color glyphs
  correctly.  In other apps, you probably will see them grayscale, but
  they should be there and of the correct size.

  This requires a recent fontconfig, and hopefully with default config
  that doesn't mess up with bitmap color fonts.  All reports I've
  received say that it doesn't work, hence this bug.

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

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

[Touch-packages] [Bug 1576747] Re: Network manager applet unable to control wifi after suspend in 16.04

2016-09-11 Thread Rob Frohne

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

I find that I can:

$ killall nm-applet && nm-applet&

and it is back working.  I haven't been successful getting that to work
in a script upon resume yet though.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1576747

Title:
  Network manager applet unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)

Re: [Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

2016-09-11 Thread Ian Weisser

Jarno Suni,

This bug report ran it's course, and 'Fix Released' is another way of
saying 'Closed.' You can discuss it, but no developer is likely to read
it...to them, it's a closed issue. It's fixed, and won't be unfixed.
The patch is released, and won't be reverted. The normal workflow is to
file a new bug, not to reopen or discuss a closed bug.

Bug 1357093 is 'Fix Released' because I duplicated the original
reporter's problems, triaged the bug, and forwarded enough information
to a developer who agreed with my triage and decided to fix it. Upon
testing the fix (repeatedly), my duplication of the original reporter's
problem is really fixed.

If you have a triage-able problem with the unattended-upgrades package,
please open a new bug report and provide enough information so I can
triage it. I cannot generally triage a problem that I cannot duplicate.

If all you know is 'it should work but does not work', then please jump
into a support forum (like Ubuntuforums) and let the experts there help
you figure out how to duplicate or triage it. Similar symptoms may come
from very different causes. Having an unresolved problem is really,
really frustrating. Been there.

I'm quite happy to discuss kernel header dependencies and go into much
greater detail...but doing so in this bug report would be rather
counterproductive. The issue is closed, and most of the questions seem
unrelated to the original bug.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions

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

[Touch-packages] [Bug 1613949] Re: vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu 16.04.1 Xenial

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: vim (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1613949

Title:
  vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu
  16.04.1 Xenial

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  I have a fresh install of Ubuntu v16.04.1, then I did an `apt-get
  upgrade` and it only had a few seemingly-minor packages to upgrade
  (don't remember the list, sorry).

  Apparently all the core vim packages have been upgraded to
  2:7.4.1689-3ubuntu1.1 but vim-gtk3 (and all the other gvim-providing
  packages I tested) are still held back to 2:7.4.1689-3ubuntu1 so there
  is a version mis-match.

  Now I get the following error:

  [[[ BEGIN PASTE ]]]

  root@machine:/# apt-get install vim-gtk3
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   vim-gtk3 : Depends: vim-common (= 2:7.4.1689-3ubuntu1) but 
2:7.4.1689-3ubuntu1.1 is to be installed
  Depends: vim-runtime (= 2:7.4.1689-3ubuntu1) but 
2:7.4.1689-3ubuntu1.1 is to be installed
  E: Unable to correct problems, you have held broken packages.

  [[[ END PASTE ]]]

  
  However I can still get gvim working if I force the installation of the 
vim-gtk3 package using dpkg.  Of course this is not a good solution, because it 
leaves my system in a state of seemingly-broken packages!

  
  [[[ BEGIN PASTE ]]]

  root@machine:/# dpkg -i --force-depends ./vim-gtk3_7.4.1689-3ubuntu1_amd64.deb
  Selecting previously unselected package vim-gtk3.
  (Reading database ... 251539 files and directories currently installed.)
  Preparing to unpack .../vim-gtk3_7.4.1689-3ubuntu1_amd64.deb ...
  Unpacking vim-gtk3 (2:7.4.1689-3ubuntu1) ...
  dpkg: vim-gtk3: dependency problems, but configuring anyway as you requested:
   vim-gtk3 depends on vim-common (= 2:7.4.1689-3ubuntu1); however:
Version of vim-common on system is 2:7.4.1689-3ubuntu1.1.
   vim-gtk3 depends on vim-runtime (= 2:7.4.1689-3ubuntu1); however:
Version of vim-runtime on system is 2:7.4.1689-3ubuntu1.1.

  Setting up vim-gtk3 (2:7.4.1689-3ubuntu1) ...
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vim (vim) in 
auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vimdiff 
(vimdiff) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rvim (rvim) 
in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rview 
(rview) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vi (vi) in 
auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/view (view) 
in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/ex (ex) in 
auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/editor 
(editor) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gvim (gvim) 
in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gview 
(gview) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rgview 
(rgview) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rgvim 
(rgvim) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/evim (evim) 
in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/eview 
(eview) in auto mode
  update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gvimdiff 
(gvimdiff) in auto mode

  [[[ END PASTE ]]]

  
  And yes, I can confirm that gvim actually works using this method.  We just 
need to upgrade the package versioning so that we don't have a problem with the 
apt-get packaging dependency system.

  Thanks for all your hard work.  Ubuntu is #1!!!  :-)

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

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

[Touch-packages] [Bug 1516443] Re: Wishlist: (RedShift) Night mode for Ubuntu Phones

** Changed in: mir
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1516443

Title:
  Wishlist: (RedShift) Night mode for Ubuntu Phones

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Triaged
Status in Ubuntu UX:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  I would love to see a feature to make the backlight less agressive for
  the late hours of the day. For desktor there is the possibility to
  turn the screen 'red' and it feels really good compared to normal.

  This is a wish, I don't know where to put it else.

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

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

[Touch-packages] [Bug 1527137] Re: libmirprotobuf.so.3: undefined symbol: _ZNK6google8protobuf11MessageLite25InitializationErrorStringB5cxx11Ev

>From what I can see and recall this bug only exists on systems that were
initially installed/upgraded to an unstable Ubuntu development release.
The problem should not exist in stable installations.

Try something like the commands in comment #3.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1527137

Title:
  libmirprotobuf.so.3: undefined symbol:
  _ZNK6google8protobuf11MessageLite25InitializationErrorStringB5cxx11Ev

Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid

Bug description:
  
  After probably updating Ubuntu 15.10 packages, I unable to launch
  software like evolution and virt-manager

  $ evolution 
  evolution: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/libmirprotobuf.so.3: undefined symbol: 
_ZNK6google8protobuf11MessageLite25InitializationErrorStringB5cxx11Ev

  $ virt-manager 
  ** (process:3051): WARNING **: Failed to load shared library 'libgtk-3.so.0' 
referenced by the typelib: /usr/lib/x86_64-linux-gnu/libmirprotobuf.so.3: 
undefined symbol: 
_ZNK6google8protobuf11MessageLite25InitializationErrorStringB5cxx11Ev

  ** (process:3051): WARNING **: Failed to load shared library
  'libgdk-3.so.0' referenced by the typelib: /usr/lib/x86_64-linux-
  gnu/libmirprotobuf.so.3: undefined symbol:
  _ZNK6google8protobuf11MessageLite25InitializationErrorStringB5cxx11Ev

  $ dpkg -l | grep libmirprotobuf3
  ii  libmirprotobuf3:amd64   
0.17.0+15.10.20151008.2-0ubuntu1   amd64Display server for 
Ubuntu - RPC definitions

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 15.10
  Release:  15.10
  Codename: wily

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1527137/+subscriptions

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

[Touch-packages] [Bug 1599649] Re: High CPU usage on arale when running simple clients with animations

This is possibly not a bug at all, unless someone can prove arale can or
has performed better than this in the past.

See comment #4 and #6, but also keep in mind arale has around 8 cores
and still underperforms compared to other phones. So it stands to reason
that even 100% of one core possibly isn't much to worry about if this is
one of those platforms where the GPU load affects the CPU load.

I completely agree that anything above 1% I would recommend
investigating, /if this was not a graphics problem/. However since it is
a graphics problem it is reasonably likely that the high relative CPU
load is due to graphics drivers and poor CPU scaling that is specific to
arale (a known problem).

Since there is so much reasonable doubt as to whether this problem is in
userspace at all, I recommend keeping it Incomplete unless we can get
profile data showing high CPU in places where it shouldn't be.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1599649

Title:
  High CPU usage on arale when running simple clients with animations

Status in Mir:
  Confirmed
Status in QtMir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  It seems that independently from which Mir server I use
  (mir_demo_server, qtmir-demo-shell, unity8) the CPU usage on Arale
  when running any simple client seems to be quite high.

  My investigation started with a designer contacting me about
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1431957
  and
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1513450

  Since the activity indicator visual has to be updated anyway, we were
  looking at the options we had to also make it less CPU consuming at
  the same time.

  It turned out it's not a matter of how you render it, anything that
  causes redraw at 60fps will cause high cpu usage, here are the results
  I got:

  Tools:
  phablet-shell to run the commands
  top to see cpu usage

  Device:
  Arale, rc-proposed r370

  Setup:
  clean flash + apt-get install qtmir-tests mir-demos
  (qtmir-tests will remove qtmir-android, you'll have to reinstall it until 
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1599614 is fixed)

  echo 806000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  echo 806000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
  and the same for cpu1 and cpu2 (after bringing them online by scrolling 
scopes)

  Results:
  === Minimal Mir server + egltriangle demo ===
  sudo su
  stop lightdm
  echo 2047 > /sys/class/backlight/lm3630_bled/brightness
  sudo mir_demo_server_minimal --arw-file

  (separate shell, phablet user)
  mir_demo_client_egltriangle -m /tmp/mir_socket

  1 CORE ONLINE
  mir_demo_server: 12.5%
  mir_demo_client: 11%

  === Mir demo server + egltriangle demo ===
  sudo su
  stop lightdm
  echo 2047 > /sys/class/backlight/lm3630_bled/brightness
  LD_PRELOAD=/lib/arm-linux-gnueabihf/libpthread.so.0 mir_demo_server 
--test-client /usr/bin/mir_demo_client_egltriangle

  1 CORE ONLINE
  mir demo server: 20%
  mir_demo_client: 9%

  === Qt Mir demo shell + egltriangle demo ===
  sudo su
  stop lightdm
  echo 2047 > /sys/class/backlight/lm3630_bled/brightness
  cd /usr/share/qtmir/qtmir-demo-shell
  MIR_SERVER_FILE=/tmp/mir_socket QT_QPA_PLATFORM=mirserver qmlscene 
./qml-demo-shell.qml

  (on a separate shell, phablet user)
  MIR_SOCKET=/tmp/mir_socket QT_QPA_PLATFORM=ubuntumirclient sudo 
mir_demo_client_egltriangle -- --desktop_file_hint=dialer-app

  1 to 2 CORES ONLINE (varying)
  qmlscene (Mir server): 27.5% CPU
  mir_demo_client: 10% CPU

  === Unity8 + test qml app ===
  qmlscene test.qml --desktop_file_hint=dialer-app

  2 CORES ONLINE
  Unity8: 30%
  qmlscene: 15%
  USC: 10%

   QML TEST FILE 
  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Item {
  anchors.fill: parent

  /*AnimatedSprite {
  id: sprite
  width: 69
  height: 69
  source: "spinner-spritesheet.png"
  frameCount: 74
  frameSync: true
  frameWidth: 81
  frameHeight: 81
  loops: 100
  }*/

  /*ActivityIndicator {
  id: indicator
  running: true
  }*/

  Rectangle {
  id: rect
  width: 69
  height: 69
  color: "orange"

  /*RotationAnimation on rotation {
  loops: Animation.Infinite
  from: 0
  to: 360
  }*/

  /*NumberAnimation on x {
  loops: Animation.Infinite
  from: 0
  to: 360
  }*/

  XAnimator {
  target: rect;
  from: 0;
  to: 360;
  duration: 15000
  running: true
  }
  }

  Timer {

[Touch-packages] [Bug 1622406] Re: Libertine (X11 App) page disappeared (OTA12) on BQ M10

** Also affects: libertine
   Importance: Undecided
   Status: New

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

** Package changed: mir (Ubuntu) => libertine (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1622406

Title:
  Libertine (X11 App)  page disappeared (OTA12) on BQ M10

Status in Libertine:
  New
Status in libertine package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Under OTA12 of BQ M10 (Cooler), I opened Libreoffice and tried to add
  an additional language layout for external keyboard (Thai).  I was
  able to add US and Thai Pattachote keyboards (for external keyboard),
  but did not know how to switch the keyboard layout.  I tried ALT-Shift
  and CTR-Shift without a success.

  There was no Internet connection during the keyboard layout adding.

  It turned out that the X11 App or Libertine page disappeared.  I tried
  to restart and even turned of the M10.  However, the X11 App page did
  not come back.  Could it be I did type in unkonw hot keys?

  Is there a way to bring back the missing Libertine (X11 App) page?  Or
  can I bring up the missing programmes under terminal (e.g.
  Libreoffice, Firefox, Gimp)?

  
  PS I used K380 Logitech Bluetooth external keyboard.  And I use this M10 
around once a week.

  Thanks.

  Namsommut

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1622406/+subscriptions

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

[Touch-packages] [Bug 1622411] Re: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()

2016-09-11 Thread Apport retracing service

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1622411/+attachment/4738943/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1622411/+attachment/4738946/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1622411/+attachment/4738952/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1622411/+attachment/4738954/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1622411/+attachment/4738955/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1622411/+attachment/4738957/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1622411/+attachment/4738959/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1621396

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1622411

Title:
  systemd-resolved crashed with SIGSEGV in sd_event_dispatch()

Status in systemd package in Ubuntu:
  New

Bug description:
  Unsure what the cause is, but this error occurred after I clicked on a
  hyperlink on YouTube.com to access one of my subscribed channels.

  Running Ubuntu GNOME 16.10 x64 beta 1, GNOME 3.20 desktop environment,
  kernel 4.4.0-9136-generic.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-5
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Sun Sep 11 17:43:41 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2016-08-30 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160824)
  MachineType: LENOVO 80SA
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic 
root=UUID=0ac2b91e-398e-44c3-93be-fdde19739c68 ro quiet splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-231.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/17/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0VCN18WW(V1.03)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo ideapad F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 4-1470
  dmi.modalias: 
dmi:bvnLENOVO:bvr0VCN18WW(V1.03):bd05/17/2016:svnLENOVO:pn80SA:pvrLenovoideapadFLEX4-1470:rvnLENOVO:rnLenovoideapadF:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1470:
  dmi.product.name: 80SA
  dmi.product.version: Lenovo ideapad FLEX 4-1470
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1622406] [NEW] Libertine (X11 App) page disappeared (OTA12) on BQ M10

2016-09-11 Thread Namsommut Tinueng

Public bug reported:

Under OTA12 of BQ M10 (Cooler), I opened Libreoffice and tried to add an
additional language layout for external keyboard (Thai).  I was able to
add US and Thai Pattachote keyboards (for external keyboard), but did
not know how to switch the keyboard layout.  I tried ALT-Shift and CTR-
Shift without a success.

There was no Internet connection during the keyboard layout adding.

It turned out that the X11 App or Libertine page disappeared.  I tried
to restart and even turned of the M10.  However, the X11 App page did
not come back.  Could it be I did type in unkonw hot keys?

Is there a way to bring back the missing Libertine (X11 App) page?  Or
can I bring up the missing programmes under terminal (e.g. Libreoffice,
Firefox, Gimp)?


PS I used K380 Logitech Bluetooth external keyboard.  And I use this M10 around 
once a week.

Thanks.

Namsommut

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1622406

Title:
  Libertine (X11 App)  page disappeared (OTA12) on BQ M10

Status in unity8 package in Ubuntu:
  New

Bug description:
  Under OTA12 of BQ M10 (Cooler), I opened Libreoffice and tried to add
  an additional language layout for external keyboard (Thai).  I was
  able to add US and Thai Pattachote keyboards (for external keyboard),
  but did not know how to switch the keyboard layout.  I tried ALT-Shift
  and CTR-Shift without a success.

  There was no Internet connection during the keyboard layout adding.

  It turned out that the X11 App or Libertine page disappeared.  I tried
  to restart and even turned of the M10.  However, the X11 App page did
  not come back.  Could it be I did type in unkonw hot keys?

  Is there a way to bring back the missing Libertine (X11 App) page?  Or
  can I bring up the missing programmes under terminal (e.g.
  Libreoffice, Firefox, Gimp)?

  
  PS I used K380 Logitech Bluetooth external keyboard.  And I use this M10 
around once a week.

  Thanks.

  Namsommut

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

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

[Touch-packages] [Bug 1271955] Re: unity-scope-loader crashed with SIGSEGV

2016-09-11 Thread jahtemg

Some evidence about this: happens if you install nvidia-340.52 driver on
ubuntu 16.04 and try to modify time settings (for example) without
rebooting.

uname -a:

Linux pc 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launchpad.net/bugs/1271955

Title:
  unity-scope-loader crashed with SIGSEGV

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

Bug description:
  This crash was seen during
  https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job
  /trusty-touch-mako-smoke-ubuntu-weather-app-
  autopilot/127/artifact/clientlogs/

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libunity9 7.1.3+14.04.20131106-0ubuntu1
  Uname: Linux 3.4.0-3-mako armv7l
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Thu Jan 23 07:35:13 2014
  Disassembly: => 0x40027f08:   Cannot access memory at address 0x40027f08
  ExecutablePath: /usr/bin/unity-scope-loader
  ExecutableTimestamp: 1383715346
  MarkForUpload: True
  ProcCmdline: /usr/bin/unity-scope-loader music/onlinemusic.scope
  ProcCwd: /
  Signal: 11
  SourcePackage: libunity
  Stacktrace:
   #0  0x40027f08 in ?? ()
   No symbol table info available.
   Backtrace stopped: previous frame identical to this frame (corrupt stack?)
  StacktraceSource: #0  0x40027f08 in ?? ()
  StacktraceTop: ?? ()
  UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty 
video
  _LogindSession: /user/32011.user/c1.session

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/1271955/+subscriptions

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

[Touch-packages] [Bug 1622339] Re: System freezes after opening LibreOffice with AMD GPU and OpenGL rendering turned on

2016-09-11 Thread Christopher M. Penalver

Aron Budea, thank you for reporting this and helping make Ubuntu better.
However, your crash report is manually attached.

Please follow these instructions to have apport report a new bug about your
crash that can be dealt with by the automatic retracer. First, execute at a
terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y
dist-upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in
/etc/default/apport and restart. Now reproduce the crash, then open a terminal,
navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By
default, this sends the crash to the Ubuntu Error Tracker
infrastructure, which is different than Launchpad. For more on this,
please see https://wiki.ubuntu.com/ErrorTracker .

However, if after doing this you would still like to have a crash report posted
to Launchpad, for example to ease triage and add others to your report, one
would need to open the following file via a terminal:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and file the crash report via:
sudo ubuntu-bug /var/crash/FILENAME.crash

Where FILENAME is the actual name of the file found in the folder.

However, this report is being closed since the process outlined above
will deal with this issue more efficiently.

Also, please do not attach your crash report manually to this report and
reopen it.

Thank you for your help.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** No longer affects: xorg (Ubuntu)

** Project changed: df-libreoffice => xorg (Ubuntu)

** Changed in: xorg (Ubuntu)
Importance: Unknown => Undecided

** Changed in: xorg (Ubuntu)
Status: Unknown => New

** Changed in: xorg (Ubuntu)
Remote watch: Document Foundation Bugzilla #101836 => None

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

** Attachment removed: "_usr_bin_compiz.1000.crash"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1622339/+attachment/4738825/+files/_usr_bin_compiz.1000.crash

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1622339

Title:
System freezes after opening LibreOffice with AMD GPU and OpenGL
rendering turned on

Status in xorg package in Ubuntu:
Invalid

Bug description:
I'm using an AMD A10-7800 APU (Kaveri with R7-category integrated GPU
(GCN)), OS is Ubuntu 16.04 with default drivers.

Steps to reproduce:
1. Start LibreOffice.
2. Enable OpenGL rendering via menu Tools -> Options..., then View -> Use
OpenGL for all rendering (on restart).
3. Restart LibreOffice.
4. Open menu Help -> About LibreOffice.

=> Driver will crash, attempt to restart (after screen going dark 1-2
times) and potentially freeze the whole system.

This happens with:
-LibreOffice 5.1.4.2 bundled with Ubuntu 16.04,
-also with 5.2.1.2 distributed by The Document Foundation.

This bug should probably be raised against the driver, but I'm not familiar
with where they are tracked, so raising the issue here, since it seems to
affect a wide range of systems with the default Ubuntu 16.04 installation
(fortunately OpenGL rendering is turned off by default in LibreOffice).
The issue is also tracked in LibreOffice Bugzilla.

Note that the bug was reported in normal state, as it wouldn't have
been possible to do so after the crash.

Let me know if I should supply further details.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libreoffice-core 1:5.1.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Sep 11 15:35:54 2016
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2016-07-04 (68 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
---
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:

CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
DistUpgraded: Fresh install
DistroCodename: xenial
DistroRelease: Ubuntu 16.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics]
[1002:130f] (prog-if 00 [VGA controller])

[Touch-packages] [Bug 1622339] [NEW] System freezes after opening LibreOffice with AMD GPU and OpenGL rendering turned on

You have been subscribed to a public bug:

I'm using an AMD A10-7800 APU (Kaveri with R7-category integrated GPU
(GCN)), OS is Ubuntu 16.04 with default drivers.

Steps to reproduce:
1. Start LibreOffice.
2. Enable OpenGL rendering via menu Tools -> Options..., then View -> Use 
OpenGL for all rendering (on restart).
3. Restart LibreOffice.
4. Open menu Help -> About LibreOffice.

=> Driver will crash, attempt to restart (after screen going dark 1-2
times) and potentially freeze the whole system.

This happens with:
 -LibreOffice 5.1.4.2 bundled with Ubuntu 16.04,
 -also with 5.2.1.2 distributed by The Document Foundation.

This bug should probably be raised against the driver, but I'm not familiar 
with where they are tracked, so raising the issue here, since it seems to 
affect a wide range of systems with the default Ubuntu 16.04 installation 
(fortunately OpenGL rendering is turned off by default in LibreOffice).
The issue is also tracked in LibreOffice Bugzilla.

Note that the bug was reported in normal state, as it wouldn't have been
possible to do so after the crash.

Let me know if I should supply further details.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libreoffice-core 1:5.1.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Sep 11 15:35:54 2016
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2016-07-04 (68 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
--- 
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
DistUpgraded: Fresh install
DistroCodename: xenial
DistroRelease: Ubuntu 16.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:130f] 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Kaveri [Radeon R7 Graphics] [1043:85cb]
InstallationDate: Installed on 2016-07-04 (68 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: System manufacturer System Product Name
Package: xorg 1:7.7+13ubuntu3
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ff1c7218-9477-4528-bf93-8e5ff09cbc1b ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Tags:  xenial ubuntu compiz-0.9
Uname: Linux 4.4.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/10/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2903
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A88XM-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2903:bd03/10/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2

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


** Tags: amd64 apport-bug apport-collected compiz-0.9 latest-bios-2903 ubuntu 
xenial
-- 
System freezes after opening LibreOffice with AMD GPU and OpenGL rendering 
turned on
https://bugs.launchpad.net/bugs/1622339
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1622401] Re: Merge dbus 1.10.10-1 (main) from Debian unstable (main)

** Description changed:

  Please merge dbus 1.10.10-1 (main) from Debian unstable (main)
  
  1.10.10 is a bugfix release in the stable 1.10 series.
  
  https://sources.debian.net/src/dbus/1.10.10-1/NEWS/
  
  https://cgit.freedesktop.org/dbus/dbus/log/?h=dbus-1.10
  
  I am personally interested in Debian's virtual default-dbus-session-bus
  package since Debian is increasingly depending on it instead of directly
  depending on dbus-x11.
  
+ https://lists.debian.org/debian-devel/2016/08/msg00554.html
+ 
  Explanation of the Ubuntu delta and why it can be dropped:
    - debian/dbus.preinst: divert the dbus-daemon-launch-helper if upgrading
  from < 1.9.4-2~. This will make sure we keep the setuid bit during 
upgrade.
     (LP: #1555237)
   Not needed after Ubuntu 16.04 LTS
  
  Explanation of the remaining Ubuntu delta
- - Add upstart jobs
-   + debian/dbus.upstart and debian/dbus.user-session.upstart
- - debian/dbus.postinst: remove diversion.
- - debian/rules: Don't start D-Bus on package installation, as that doesn't
-   work any more. Instead, start dbus.socket in postinst, which will then 
-   start D-Bus on demand after package installation.
- - Add debian/patches/dont-stop-dbus.patch: Don't stop D-Bus in the service
-   unit (see patch header and upstream bug for details). Fixes various
-   causes of shutdown hangs, particularly with remote file systems. (LP:
-   #1438612) (LP: #1540282)
- - aa-get-connection-apparmor-security-context.patch: This is not
-   intended for upstream inclusion. It implements a bus method
-   (GetConnectionAppArmorSecurityContext) to get a connection's AppArmor
-   security context but upstream D-Bus has recently added a generic way of
-   getting a connection's security credentials (GetConnectionCredentials).
-   Ubuntu should carry this patch until packages in the archive are moved
-   over to the new, generic method of getting a connection's credentials.
+ - Add upstart jobs
+   + debian/dbus.upstart and debian/dbus.user-session.upstart
+ - debian/dbus.postinst: remove diversion.
+ - debian/rules: Don't start D-Bus on package installation, as that doesn't
+   work any more. Instead, start dbus.socket in postinst, which will then
+   start D-Bus on demand after package installation.
+ - Add debian/patches/dont-stop-dbus.patch: Don't stop D-Bus in the service
+   unit (see patch header and upstream bug for details). Fixes various
+   causes of shutdown hangs, particularly with remote file systems. (LP:
+   #1438612) (LP: #1540282)
+ - aa-get-connection-apparmor-security-context.patch: This is not
+   intended for upstream inclusion. It implements a bus method
+   (GetConnectionAppArmorSecurityContext) to get a connection's AppArmor
+   security context but upstream D-Bus has recently added a generic way of
+   getting a connection's security credentials (GetConnectionCredentials).
+   Ubuntu should carry this patch until packages in the archive are moved
+   over to the new, generic method of getting a connection's credentials.
  
  Changelog entries since current yakkety version 1.10.6-1ubuntu4:
  
  dbus (1.10.10-1) unstable; urgency=medium
  
    * New upstream stable release 1.10.10
    * Provide new virtual packages for other packages to depend on:
  - dbus-session-bus: any implementation of the D-Bus well-known session bus
    (provided by: dbus-user-session, dbus-x11)
  - default-dbus-session-bus: the recommended implementation of
    dbus-session-bus (currently provided by: dbus-user-session)
    * Add arm64, mips64el, ppc64el to the list of architectures that
  have valgrind
    * debian/gbp.conf: use DEP-14 branch names
    * Standards-Version: 3.9.8 (no changes needed)
    * debian/rules: fail the build if "make install" installs anything we
  don't package or delete. Only do this for final releases (suite
  in debian/changelog is not UNRELEASED) to facilitate future
  autobuilding of new upstream releases.
    * debian/rules: do not require symbols file to be complete if the
  suite in debian/changelog is UNRELEASED, again to facilitate
  autobuilding new upstream releases.
    * debian/source/options: don't fail dpkg-source on changes to
  build-aux/{compile,depcomp,missing}. We regenerate that directory anyway,
  and during a snapshot build they might become symlinks.
    * debian/rules: do the build in debian/build-* so it's easier to .gitignore
    * debian/.gitignore: update
    * Use the correct systemctl for Debian even if not installed on the build
  system. (Regression in 1.10.2)
  
   -- Simon McVittie   Mon, 15 Aug 2016 22:05:45 +0100
  
  dbus (1.10.8-1) unstable; urgency=medium
  
    * New upstream release
    * dbus.prerm: ensure that dbus.socket is stopped before removal,
  so that a new connection to the bus won't cause

[Touch-packages] [Bug 1622402] Re: unity8-dash crashed with SIGSEGV in eglDestroyContext()

2016-09-11 Thread Apport retracing service

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1622402/+attachment/4738906/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1622402/+attachment/4738908/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1622402/+attachment/4738911/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1622402/+attachment/4738912/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1622402/+attachment/4738913/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1622402/+attachment/4738914/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1622402/+attachment/4738915/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1620994

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1622402

Title:
  unity8-dash crashed with SIGSEGV in eglDestroyContext()

Status in unity8 package in Ubuntu:
  New

Bug description:
  *

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160831.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Sep 12 01:04:00 2016
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2016-09-10 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160909)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  SegvAnalysis:
   Segfault happened at: 0x7f15410afa3e:mov0x30(%rbp),%rax
   PC (0x7f15410afa3e) ok
   source "0x30(%rbp)" (0x0030) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   eglDestroyContext () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   QOpenGLContext::destroy() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: unity8-dash crashed with SIGSEGV in eglDestroyContext()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  upstart.unity8-dash.log: [2016-09-12:01:04:00.306] QEGLPlatformContext: 
eglMakeCurrent failed: 3001

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

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

[Touch-packages] [Bug 1622403] [NEW] Sync pygobject 3.21.92-1 (main) from Debian unstable (main)

Public bug reported:

Please sync pygobject 3.21.92-1 (main) from Debian unstable (main)

https://git.gnome.org/browse/pygobject/tree/NEWS
https://git.gnome.org/browse/pygobject/log/

Mattia Rizzolo ~mapreri recommended we sync pygobject 3.21
to fix libsecret's tests hanging on s390x

Changelog entries since current yakkety version 3.20.1-1:

pygobject (3.21.92-1) unstable; urgency=medium

  * New upstream development release.
  * Drop patches which have been merged upstream.

 -- Michael Biebl   Sun, 11 Sep 2016 15:02:27 +0200

pygobject (3.21.91-2) unstable; urgency=medium

  [ Aurelien Jarno ]
  * Fix wrong enum to hash conversion on 64-bit big endian. (Closes: #835413)

  [ Michael Biebl ]
  * Use dbus-run-session instead of dbus-launch to run the tests.
(Closes: #836049)
  * Handle nullable filename parameters. This fixes a test suite error in
test_spawn_async_with_pipes triggered by an annotation change in glib.
  * Drop override for dh_python2, no longer needed.

 -- Michael Biebl   Sun, 04 Sep 2016 00:02:14 +0200

pygobject (3.21.91-1) experimental; urgency=medium

  * New upstream beta release.
  * Set Maintainer to Debian GNOME Maintainers
  * Add python{,3}-setuptools to build-dependencies
- as needed in debian/rules clean by the new setup.py

 -- Andreas Henriksson   Fri, 26 Aug 2016 10:57:27
+0200

pygobject (3.21.0-1) experimental; urgency=medium

  [ Michael Biebl ]
  * Drop --disable-silent-rules from debian/rules. This is now handled by dh
directly depending on whether the DH_QUIET environment variable is set.

  [ Andreas Henriksson ]
  * New upstream development release.

 -- Andreas Henriksson   Tue, 23 Aug 2016 13:31:24
+0200

** Affects: pygobject (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: upgrade-software-version

** Changed in: pygobject (Ubuntu)
   Importance: Undecided => Wishlist

** Tags added: upgrade-software-version

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1622403

Title:
  Sync pygobject 3.21.92-1 (main) from Debian unstable (main)

Status in pygobject package in Ubuntu:
  New

Bug description:
  Please sync pygobject 3.21.92-1 (main) from Debian unstable (main)

  https://git.gnome.org/browse/pygobject/tree/NEWS
  https://git.gnome.org/browse/pygobject/log/

  Mattia Rizzolo ~mapreri recommended we sync pygobject 3.21
  to fix libsecret's tests hanging on s390x

  Changelog entries since current yakkety version 3.20.1-1:

  pygobject (3.21.92-1) unstable; urgency=medium

* New upstream development release.
* Drop patches which have been merged upstream.

   -- Michael Biebl   Sun, 11 Sep 2016 15:02:27 +0200

  pygobject (3.21.91-2) unstable; urgency=medium

[ Aurelien Jarno ]
* Fix wrong enum to hash conversion on 64-bit big endian. (Closes: #835413)

[ Michael Biebl ]
* Use dbus-run-session instead of dbus-launch to run the tests.
  (Closes: #836049)
* Handle nullable filename parameters. This fixes a test suite error in
  test_spawn_async_with_pipes triggered by an annotation change in glib.
* Drop override for dh_python2, no longer needed.

   -- Michael Biebl   Sun, 04 Sep 2016 00:02:14 +0200

  pygobject (3.21.91-1) experimental; urgency=medium

* New upstream beta release.
* Set Maintainer to Debian GNOME Maintainers
* Add python{,3}-setuptools to build-dependencies
  - as needed in debian/rules clean by the new setup.py

   -- Andreas Henriksson   Fri, 26 Aug 2016 10:57:27
  +0200

  pygobject (3.21.0-1) experimental; urgency=medium

[ Michael Biebl ]
* Drop --disable-silent-rules from debian/rules. This is now handled by dh
  directly depending on whether the DH_QUIET environment variable is set.

[ Andreas Henriksson ]
* New upstream development release.

   -- Andreas Henriksson   Tue, 23 Aug 2016 13:31:24
  +0200

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

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

[Touch-packages] [Bug 1622401] Re: Merge dbus 1.10.10-1 (main) from Debian unstable (main)

debdiff from current Debian packaging to proposed Ubuntu packaging

** Patch added: "dbus-diff-from-current-debian.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1622401/+attachment/4738918/+files/dbus-diff-from-current-debian.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1622401

Title:
  Merge dbus 1.10.10-1 (main) from Debian unstable (main)

Status in dbus package in Ubuntu:
  New

Bug description:
  Please merge dbus 1.10.10-1 (main) from Debian unstable (main)

  1.10.10 is a bugfix release in the stable 1.10 series.

  https://sources.debian.net/src/dbus/1.10.10-1/NEWS/

  https://cgit.freedesktop.org/dbus/dbus/log/?h=dbus-1.10

  I am personally interested in Debian's virtual default-dbus-session-
  bus package since Debian is increasingly depending on it instead of
  directly depending on dbus-x11.

  Explanation of the Ubuntu delta and why it can be dropped:
    - debian/dbus.preinst: divert the dbus-daemon-launch-helper if upgrading
  from < 1.9.4-2~. This will make sure we keep the setuid bit during 
upgrade.
     (LP: #1555237)
   Not needed after Ubuntu 16.04 LTS

  Explanation of the remaining Ubuntu delta
  - Add upstart jobs
+ debian/dbus.upstart and debian/dbus.user-session.upstart
  - debian/dbus.postinst: remove diversion.
  - debian/rules: Don't start D-Bus on package installation, as that doesn't
work any more. Instead, start dbus.socket in postinst, which will then 
start D-Bus on demand after package installation.
  - Add debian/patches/dont-stop-dbus.patch: Don't stop D-Bus in the service
unit (see patch header and upstream bug for details). Fixes various
causes of shutdown hangs, particularly with remote file systems. (LP:
#1438612) (LP: #1540282)
  - aa-get-connection-apparmor-security-context.patch: This is not
intended for upstream inclusion. It implements a bus method
(GetConnectionAppArmorSecurityContext) to get a connection's AppArmor
security context but upstream D-Bus has recently added a generic way of
getting a connection's security credentials (GetConnectionCredentials).
Ubuntu should carry this patch until packages in the archive are moved
over to the new, generic method of getting a connection's credentials.

  Changelog entries since current yakkety version 1.10.6-1ubuntu4:

  dbus (1.10.10-1) unstable; urgency=medium

    * New upstream stable release 1.10.10
    * Provide new virtual packages for other packages to depend on:
  - dbus-session-bus: any implementation of the D-Bus well-known session bus
    (provided by: dbus-user-session, dbus-x11)
  - default-dbus-session-bus: the recommended implementation of
    dbus-session-bus (currently provided by: dbus-user-session)
    * Add arm64, mips64el, ppc64el to the list of architectures that
  have valgrind
    * debian/gbp.conf: use DEP-14 branch names
    * Standards-Version: 3.9.8 (no changes needed)
    * debian/rules: fail the build if "make install" installs anything we
  don't package or delete. Only do this for final releases (suite
  in debian/changelog is not UNRELEASED) to facilitate future
  autobuilding of new upstream releases.
    * debian/rules: do not require symbols file to be complete if the
  suite in debian/changelog is UNRELEASED, again to facilitate
  autobuilding new upstream releases.
    * debian/source/options: don't fail dpkg-source on changes to
  build-aux/{compile,depcomp,missing}. We regenerate that directory anyway,
  and during a snapshot build they might become symlinks.
    * debian/rules: do the build in debian/build-* so it's easier to .gitignore
    * debian/.gitignore: update
    * Use the correct systemctl for Debian even if not installed on the build
  system. (Regression in 1.10.2)

   -- Simon McVittie   Mon, 15 Aug 2016 22:05:45 +0100

  dbus (1.10.8-1) unstable; urgency=medium

    * New upstream release
    * dbus.prerm: ensure that dbus.socket is stopped before removal,
  so that a new connection to the bus won't cause dbus.service to be
  restarted (Closes: #813970)
    * debian/75dbus_dbus-launch: when not using systemd --user or the
  dbus-user-session package is not installed, start dbus-daemon early,
  then upload the full environment from Xsession.d later on
  (in 95dbus_update-activation-env). This more closely matches the
  behaviour with dbus-user-session. (Closes: #815503; thanks to Samuel
  Thibault)
    * Switch Vcs-Git to https (see #810378)
    * debian/upstream/signing-key.asc: add upstream signing keys
  (just my keys for now, in practice I do almost all dbus releases)
    * debian/watch: use https and describe how to download signatures
    * Standards-Version: 3.9.7 (no changes needed)

[Touch-packages] [Bug 1622401] Re: Merge dbus 1.10.10-1 (main) from Debian unstable (main)

debdiff from current Ubuntu packaging to proposed

** Description changed:

  Please merge dbus 1.10.10-1 (main) from Debian unstable (main)
  
+ 1.10.10 is a bugfix release in the stable 1.10 series.
+ 
+ https://sources.debian.net/src/dbus/1.10.10-1/NEWS/
+ 
+ https://cgit.freedesktop.org/dbus/dbus/log/?h=dbus-1.10
+ 
+ I am personally interested in Debian's virtual default-dbus-session-bus
+ package since Debian is increasingly depending on it instead of directly
+ depending on dbus-x11.
+ 
  Explanation of the Ubuntu delta and why it can be dropped:
-   - debian/dbus.preinst: divert the dbus-daemon-launch-helper if upgrading
- from < 1.9.4-2~. This will make sure we keep the setuid bit during 
upgrade.
-(LP: #1555237)
-  Not needed after Ubuntu 16.04 LTS
+   - debian/dbus.preinst: divert the dbus-daemon-launch-helper if upgrading
+ from < 1.9.4-2~. This will make sure we keep the setuid bit during 
upgrade.
+    (LP: #1555237)
+  Not needed after Ubuntu 16.04 LTS
  
  Explanation of the remaining Ubuntu delta
-   * debian/dbus.user-session.upstart:
- - Don't start a new session bus if there already is one (e. g. via
-   dbus-user-session), as this would lead to different services talking to
-   different buses and thus not seeing each other. As we still need the
-   actual job itself running, run "sleep infinity" instead in this case.
- - Drop "expect fork" and "--fork" argument. There is little point in the
-   daemon forking, upstart already manages it. This makes debugging easier
-   and also avoids having to fork "sleep" in the case that dbus-daemon is
-   already running.
- - Drop "mkdir ~/.cache/upstart". This doesn't belong into a job, isn't
-   necessary (upstart already creates it on start) and would be too late
-   anyway.
-   * debian/dbus.preinst: divert the dbus-daemon-launch-helper if upgrading
- from < 1.9.4-2~. This will make sure we keep the setuid bit during 
upgrade.
- (LP: #1555237)
-   * debian/dbus.postinst: remove diversion.
-   * debian/dbus.preinst: divert the dbus-daemon-launch-helper if upgrading
- from < 1.9.4-2~. This will make sure we keep the setuid bit during 
upgrade.
- (LP: #1555237)
-   * debian/dbus.postinst: remove diversion.
-   * dont-stop-dbus.patch: Disallow manual (re)starts, as we don't (want to)
- stop D-Bus on shutdown. (LP: #1540282)
-   * debian/rules: Don't start D-Bus on package installation, as that doesn't
- work any more with the above. Instead, start dbus.socket in postinst,
- which will then start D-Bus on demand after package installation.
-   * Merge with Debian, remaining changes:
- - Add upstart jobs; Upstart is still supported for the system init.
-   + Add debian/dbus.upstart and dbus.user-session.upstart
+ - Add upstart jobs
+   + debian/dbus.upstart and debian/dbus.user-session.upstart
+ - debian/dbus.postinst: remove diversion.
+ - debian/rules: Don't start D-Bus on package installation, as that doesn't
+   work any more. Instead, start dbus.socket in postinst, which will then 
+   start D-Bus on demand after package installation.
  - Add debian/patches/dont-stop-dbus.patch: Don't stop D-Bus in the service
unit (see patch header and upstream bug for details). Fixes various
causes of shutdown hangs, particularly with remote file systems. (LP:
-   #1438612)
+   #1438612) (LP: #1540282)
  - aa-get-connection-apparmor-security-context.patch: This is not
intended for upstream inclusion. It implements a bus method
(GetConnectionAppArmorSecurityContext) to get a connection's AppArmor
security context but upstream D-Bus has recently added a generic way of
getting a connection's security credentials (GetConnectionCredentials).
Ubuntu should carry this patch until packages in the archive are moved
over to the new, generic method of getting a connection's credentials.
  
  Changelog entries since current yakkety version 1.10.6-1ubuntu4:
  
  dbus (1.10.10-1) unstable; urgency=medium
  
-   * New upstream stable release 1.10.10
-   * Provide new virtual packages for other packages to depend on:
- - dbus-session-bus: any implementation of the D-Bus well-known session bus
-   (provided by: dbus-user-session, dbus-x11)
- - default-dbus-session-bus: the recommended implementation of
-   dbus-session-bus (currently provided by: dbus-user-session)
-   * Add arm64, mips64el, ppc64el to the list of architectures that
- have valgrind
-   * debian/gbp.conf: use DEP-14 branch names
-   * Standards-Version: 3.9.8 (no changes needed)
-   * debian/rules: fail the build if "make install" installs anything we
- don't package or delete. Only do this for final releases (suite
- in debian/changelog is not UNRELEASED) to facilitate future
- autobuilding of new upstream releases.
-   * debian/rules: do not require symbols file to be complete if the

[Touch-packages] [Bug 1622401] Re: Merge dbus 1.10.10-1 (main) from Debian unstable (main)

old debdiff (from Debian's 1.10.6-1 to Ubuntu's 1.10.6-1ubuntu4)

** Patch added: "dbus_1.10.6-1ubuntu4.patch"
   
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1622401/+attachment/4738919/+files/dbus_1.10.6-1ubuntu4.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1622401

Title:
  Merge dbus 1.10.10-1 (main) from Debian unstable (main)

Status in dbus package in Ubuntu:
  New

Bug description:
  Please merge dbus 1.10.10-1 (main) from Debian unstable (main)

  1.10.10 is a bugfix release in the stable 1.10 series.

  https://sources.debian.net/src/dbus/1.10.10-1/NEWS/

  https://cgit.freedesktop.org/dbus/dbus/log/?h=dbus-1.10

  I am personally interested in Debian's virtual default-dbus-session-
  bus package since Debian is increasingly depending on it instead of
  directly depending on dbus-x11.

  Explanation of the Ubuntu delta and why it can be dropped:
    - debian/dbus.preinst: divert the dbus-daemon-launch-helper if upgrading
  from < 1.9.4-2~. This will make sure we keep the setuid bit during 
upgrade.
     (LP: #1555237)
   Not needed after Ubuntu 16.04 LTS

  Explanation of the remaining Ubuntu delta
  - Add upstart jobs
+ debian/dbus.upstart and debian/dbus.user-session.upstart
  - debian/dbus.postinst: remove diversion.
  - debian/rules: Don't start D-Bus on package installation, as that doesn't
work any more. Instead, start dbus.socket in postinst, which will then 
start D-Bus on demand after package installation.
  - Add debian/patches/dont-stop-dbus.patch: Don't stop D-Bus in the service
unit (see patch header and upstream bug for details). Fixes various
causes of shutdown hangs, particularly with remote file systems. (LP:
#1438612) (LP: #1540282)
  - aa-get-connection-apparmor-security-context.patch: This is not
intended for upstream inclusion. It implements a bus method
(GetConnectionAppArmorSecurityContext) to get a connection's AppArmor
security context but upstream D-Bus has recently added a generic way of
getting a connection's security credentials (GetConnectionCredentials).
Ubuntu should carry this patch until packages in the archive are moved
over to the new, generic method of getting a connection's credentials.

  Changelog entries since current yakkety version 1.10.6-1ubuntu4:

  dbus (1.10.10-1) unstable; urgency=medium

    * New upstream stable release 1.10.10
    * Provide new virtual packages for other packages to depend on:
  - dbus-session-bus: any implementation of the D-Bus well-known session bus
    (provided by: dbus-user-session, dbus-x11)
  - default-dbus-session-bus: the recommended implementation of
    dbus-session-bus (currently provided by: dbus-user-session)
    * Add arm64, mips64el, ppc64el to the list of architectures that
  have valgrind
    * debian/gbp.conf: use DEP-14 branch names
    * Standards-Version: 3.9.8 (no changes needed)
    * debian/rules: fail the build if "make install" installs anything we
  don't package or delete. Only do this for final releases (suite
  in debian/changelog is not UNRELEASED) to facilitate future
  autobuilding of new upstream releases.
    * debian/rules: do not require symbols file to be complete if the
  suite in debian/changelog is UNRELEASED, again to facilitate
  autobuilding new upstream releases.
    * debian/source/options: don't fail dpkg-source on changes to
  build-aux/{compile,depcomp,missing}. We regenerate that directory anyway,
  and during a snapshot build they might become symlinks.
    * debian/rules: do the build in debian/build-* so it's easier to .gitignore
    * debian/.gitignore: update
    * Use the correct systemctl for Debian even if not installed on the build
  system. (Regression in 1.10.2)

   -- Simon McVittie   Mon, 15 Aug 2016 22:05:45 +0100

  dbus (1.10.8-1) unstable; urgency=medium

    * New upstream release
    * dbus.prerm: ensure that dbus.socket is stopped before removal,
  so that a new connection to the bus won't cause dbus.service to be
  restarted (Closes: #813970)
    * debian/75dbus_dbus-launch: when not using systemd --user or the
  dbus-user-session package is not installed, start dbus-daemon early,
  then upload the full environment from Xsession.d later on
  (in 95dbus_update-activation-env). This more closely matches the
  behaviour with dbus-user-session. (Closes: #815503; thanks to Samuel
  Thibault)
    * Switch Vcs-Git to https (see #810378)
    * debian/upstream/signing-key.asc: add upstream signing keys
  (just my keys for now, in practice I do almost all dbus releases)
    * debian/watch: use https and describe how to download signatures
    * Standards-Version: 3.9.7 (no changes needed)
    * Sort .install files

[Touch-packages] [Bug 1622401] [NEW] Merge dbus 1.10.10-1 (main) from Debian unstable (main)

Public bug reported:

Please merge dbus 1.10.10-1 (main) from Debian unstable (main)

1.10.10 is a bugfix release in the stable 1.10 series.

https://sources.debian.net/src/dbus/1.10.10-1/NEWS/

https://cgit.freedesktop.org/dbus/dbus/log/?h=dbus-1.10

I am personally interested in Debian's virtual default-dbus-session-bus
package since Debian is increasingly depending on it instead of directly
depending on dbus-x11.

Explanation of the Ubuntu delta and why it can be dropped:
  - debian/dbus.preinst: divert the dbus-daemon-launch-helper if upgrading
from < 1.9.4-2~. This will make sure we keep the setuid bit during upgrade.
   (LP: #1555237)
 Not needed after Ubuntu 16.04 LTS

Explanation of the remaining Ubuntu delta
- Add upstart jobs
  + debian/dbus.upstart and debian/dbus.user-session.upstart
- debian/dbus.postinst: remove diversion.
- debian/rules: Don't start D-Bus on package installation, as that doesn't
  work any more. Instead, start dbus.socket in postinst, which will then 
  start D-Bus on demand after package installation.
- Add debian/patches/dont-stop-dbus.patch: Don't stop D-Bus in the service
  unit (see patch header and upstream bug for details). Fixes various
  causes of shutdown hangs, particularly with remote file systems. (LP:
  #1438612) (LP: #1540282)
- aa-get-connection-apparmor-security-context.patch: This is not
  intended for upstream inclusion. It implements a bus method
  (GetConnectionAppArmorSecurityContext) to get a connection's AppArmor
  security context but upstream D-Bus has recently added a generic way of
  getting a connection's security credentials (GetConnectionCredentials).
  Ubuntu should carry this patch until packages in the archive are moved
  over to the new, generic method of getting a connection's credentials.

Changelog entries since current yakkety version 1.10.6-1ubuntu4:

dbus (1.10.10-1) unstable; urgency=medium

  * New upstream stable release 1.10.10
  * Provide new virtual packages for other packages to depend on:
- dbus-session-bus: any implementation of the D-Bus well-known session bus
  (provided by: dbus-user-session, dbus-x11)
- default-dbus-session-bus: the recommended implementation of
  dbus-session-bus (currently provided by: dbus-user-session)
  * Add arm64, mips64el, ppc64el to the list of architectures that
have valgrind
  * debian/gbp.conf: use DEP-14 branch names
  * Standards-Version: 3.9.8 (no changes needed)
  * debian/rules: fail the build if "make install" installs anything we
don't package or delete. Only do this for final releases (suite
in debian/changelog is not UNRELEASED) to facilitate future
autobuilding of new upstream releases.
  * debian/rules: do not require symbols file to be complete if the
suite in debian/changelog is UNRELEASED, again to facilitate
autobuilding new upstream releases.
  * debian/source/options: don't fail dpkg-source on changes to
build-aux/{compile,depcomp,missing}. We regenerate that directory anyway,
and during a snapshot build they might become symlinks.
  * debian/rules: do the build in debian/build-* so it's easier to .gitignore
  * debian/.gitignore: update
  * Use the correct systemctl for Debian even if not installed on the build
system. (Regression in 1.10.2)

 -- Simon McVittie   Mon, 15 Aug 2016 22:05:45 +0100

dbus (1.10.8-1) unstable; urgency=medium

  * New upstream release
  * dbus.prerm: ensure that dbus.socket is stopped before removal,
so that a new connection to the bus won't cause dbus.service to be
restarted (Closes: #813970)
  * debian/75dbus_dbus-launch: when not using systemd --user or the
dbus-user-session package is not installed, start dbus-daemon early,
then upload the full environment from Xsession.d later on
(in 95dbus_update-activation-env). This more closely matches the
behaviour with dbus-user-session. (Closes: #815503; thanks to Samuel
Thibault)
  * Switch Vcs-Git to https (see #810378)
  * debian/upstream/signing-key.asc: add upstream signing keys
(just my keys for now, in practice I do almost all dbus releases)
  * debian/watch: use https and describe how to download signatures
  * Standards-Version: 3.9.7 (no changes needed)
  * Sort .install files and remove unnecessary debian/tmp prefix
  * Normalize lists of packages and uploaders via wrap-and-sort -ast
  * Normalize order of packages via wrap-and-sort -b

 -- Simon McVittie   Mon, 07 Mar 2016 19:15:47 +

** Affects: dbus (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: upgrade-software-version

** Changed in: dbus (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1622401

Title:
  Merge dbus 1.10.10-1 (main) from Debian unstable (main)

[Touch-packages] [Bug 1599649] Re: High CPU usage on arale when running simple clients with animations

2016-09-11 Thread Andrea Bernabei

** Changed in: mir
   Status: Expired => Confirmed

** Changed in: qtmir
   Status: Expired => Confirmed

** Changed in: unity8 (Ubuntu)
   Status: Expired => Confirmed

** Changed in: mir (Ubuntu)
   Status: Expired => Confirmed

** Changed in: qtmir (Ubuntu)
   Status: Expired => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1599649

Title:
  High CPU usage on arale when running simple clients with animations

Status in Mir:
  Confirmed
Status in QtMir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  It seems that independently from which Mir server I use
  (mir_demo_server, qtmir-demo-shell, unity8) the CPU usage on Arale
  when running any simple client seems to be quite high.

  My investigation started with a designer contacting me about
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1431957
  and
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1513450

  Since the activity indicator visual has to be updated anyway, we were
  looking at the options we had to also make it less CPU consuming at
  the same time.

  It turned out it's not a matter of how you render it, anything that
  causes redraw at 60fps will cause high cpu usage, here are the results
  I got:

  Tools:
  phablet-shell to run the commands
  top to see cpu usage

  Device:
  Arale, rc-proposed r370

  Setup:
  clean flash + apt-get install qtmir-tests mir-demos
  (qtmir-tests will remove qtmir-android, you'll have to reinstall it until 
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1599614 is fixed)

  echo 806000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  echo 806000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
  and the same for cpu1 and cpu2 (after bringing them online by scrolling 
scopes)

  Results:
  === Minimal Mir server + egltriangle demo ===
  sudo su
  stop lightdm
  echo 2047 > /sys/class/backlight/lm3630_bled/brightness
  sudo mir_demo_server_minimal --arw-file

  (separate shell, phablet user)
  mir_demo_client_egltriangle -m /tmp/mir_socket

  1 CORE ONLINE
  mir_demo_server: 12.5%
  mir_demo_client: 11%

  === Mir demo server + egltriangle demo ===
  sudo su
  stop lightdm
  echo 2047 > /sys/class/backlight/lm3630_bled/brightness
  LD_PRELOAD=/lib/arm-linux-gnueabihf/libpthread.so.0 mir_demo_server 
--test-client /usr/bin/mir_demo_client_egltriangle

  1 CORE ONLINE
  mir demo server: 20%
  mir_demo_client: 9%

  === Qt Mir demo shell + egltriangle demo ===
  sudo su
  stop lightdm
  echo 2047 > /sys/class/backlight/lm3630_bled/brightness
  cd /usr/share/qtmir/qtmir-demo-shell
  MIR_SERVER_FILE=/tmp/mir_socket QT_QPA_PLATFORM=mirserver qmlscene 
./qml-demo-shell.qml

  (on a separate shell, phablet user)
  MIR_SOCKET=/tmp/mir_socket QT_QPA_PLATFORM=ubuntumirclient sudo 
mir_demo_client_egltriangle -- --desktop_file_hint=dialer-app

  1 to 2 CORES ONLINE (varying)
  qmlscene (Mir server): 27.5% CPU
  mir_demo_client: 10% CPU

  === Unity8 + test qml app ===
  qmlscene test.qml --desktop_file_hint=dialer-app

  2 CORES ONLINE
  Unity8: 30%
  qmlscene: 15%
  USC: 10%

   QML TEST FILE 
  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Item {
  anchors.fill: parent

  /*AnimatedSprite {
  id: sprite
  width: 69
  height: 69
  source: "spinner-spritesheet.png"
  frameCount: 74
  frameSync: true
  frameWidth: 81
  frameHeight: 81
  loops: 100
  }*/

  /*ActivityIndicator {
  id: indicator
  running: true
  }*/

  Rectangle {
  id: rect
  width: 69
  height: 69
  color: "orange"

  /*RotationAnimation on rotation {
  loops: Animation.Infinite
  from: 0
  to: 360
  }*/

  /*NumberAnimation on x {
  loops: Animation.Infinite
  from: 0
  to: 360
  }*/

  XAnimator {
  target: rect;
  from: 0;
  to: 360;
  duration: 15000
  running: true
  }
  }

  Timer {
  interval: 1
  running: true
  onTriggered: Qt.quit()
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1599649/+subscriptions

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

[Touch-packages] [Bug 1271955] Re: unity-scope-loader crashed with SIGSEGV

2016-09-11 Thread jahtemg

Still isn't fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launchpad.net/bugs/1271955

Title:
  unity-scope-loader crashed with SIGSEGV

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

Bug description:
  This crash was seen during
  https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job
  /trusty-touch-mako-smoke-ubuntu-weather-app-
  autopilot/127/artifact/clientlogs/

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libunity9 7.1.3+14.04.20131106-0ubuntu1
  Uname: Linux 3.4.0-3-mako armv7l
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Thu Jan 23 07:35:13 2014
  Disassembly: => 0x40027f08:   Cannot access memory at address 0x40027f08
  ExecutablePath: /usr/bin/unity-scope-loader
  ExecutableTimestamp: 1383715346
  MarkForUpload: True
  ProcCmdline: /usr/bin/unity-scope-loader music/onlinemusic.scope
  ProcCwd: /
  Signal: 11
  SourcePackage: libunity
  Stacktrace:
   #0  0x40027f08 in ?? ()
   No symbol table info available.
   Backtrace stopped: previous frame identical to this frame (corrupt stack?)
  StacktraceSource: #0  0x40027f08 in ?? ()
  StacktraceTop: ?? ()
  UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty 
video
  _LogindSession: /user/32011.user/c1.session

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/1271955/+subscriptions

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

[Touch-packages] [Bug 1622394] [NEW] vlc playback flicker and has delays

2016-09-11 Thread Leo Kalovyrnas

Public bug reported:

Your system is providing 3D via software rendering rather than hardware
rendering.  This is a compatibility mode which should display 3D
graphics properly but the performance may be very poor.  If the problem
you're reporting is related to graphics performance, your real question
may be why X didn't use hardware acceleration for your system.

ubuntu 16.04 LTS 
Intel® Core™2 CPU 6420 @ 2.13GHz × 2 
Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Sep 11 22:19:56 2016
DistUpgraded: 2016-09-11 12:24:34,299 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Cedar [Radeon HD 
5000/6000/7350/8350 Series] [174b:e164]
InstallationDate: Installed on 2012-12-11 (1370 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=150153c9-a663-4cf4-b335-3e170c2f4845 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-09-11 (0 days ago)
dmi.bios.date: 07/03/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0901
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5B-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd07/03/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Sep 11 21:01:07 2016
xserver.configfile: /etc/X11/xorg.conf
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputMicrosoft Microsoft Wireless Optical Desktop® 2.10 KEYBOARD, id 8
 inputMicrosoft Microsoft Wireless Optical Desktop® 2.10 KEYBOARD, id 9
 input2.4G wireless Mouse  MOUSE, id 10
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1622394

Title:
  vlc playback flicker and has delays

Status in xorg package in Ubuntu:
  New

Bug description:
  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  ubuntu 16.04 LTS 
  Intel® Core™2 CPU 6420 @ 2.13GHz × 2 
  Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04

[Touch-packages] [Bug 1013881] Re: Right-Ctrl key broken on French OSS keyboard

2016-09-11 Thread Coeur Noir

I also noticed actual versions of xkb-data & xkb-data-i18n in Ubuntu
14.04.4/5 broke again right-ctrl-key with french ( alternative )
keyboard.

I've fixed it installing versions from xenial, using dpkg command.

http://packages.ubuntu.com/xenial/xkb-data
http://packages.ubuntu.com/xenial/xkb-data-i18n

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1013881

Title:
  Right-Ctrl key broken on French OSS keyboard

Status in xkeyboard-config:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xkeyboard-config source package in Precise:
  Fix Released

Bug description:
  Since the version 2.5-1ubuntu1.2 of the package xkb-data, the right CTRL key 
of the keyboard has ceased to work.
  The problem started when APT has updated the xkd-data from 2.5-1ubuntu1 to 
2.5-1ubuntu1.2.

  If I switch back to 2.5.-1ubuntu1 using Synaptic, it works back.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xkb-data 2.5-1ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  ApportVersion: 2.0.1-0ubuntu9
  Architecture: amd64
  Date: Sat Jun 16 00:16:09 2012
  Dependencies:
   
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  MachineType: LENOVO 4243E69
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic 
root=UUID=f6981326-31fd-4eaf-b039-3a1e5f33dbc0 ro quiet splash vt.handoff=7
  SourcePackage: xkeyboard-config
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET56WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4243E69
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4243E69:pvrThinkPadT520:rvnLENOVO:rn4243E69:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4243E69
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.7.8-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.19.0-0ubuntu1~xup1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+subscriptions

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

[Touch-packages] [Bug 1595947] Re: brightness not changing from either u-s-s or hardkey on unity8-desktop

2016-09-11 Thread Lukáš Tinkl

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Lukáš Tinkl (lukas-kde)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1595947

Title:
  brightness not changing from either  u-s-s or hardkey on
  unity8-desktop

Status in Canonical System Image:
  New
Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Running unity8-desktop session on my macbookpro which has a hard display 
brightness key, currently it makes no effect. Also, opened 
ubuntu-sytstem-settings and changing the brightness slider also makes no effect.
  sorry for spamming projects, not sure which to log against.

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

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

[Touch-packages] [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] ERROR si startup failed on resume

2016-09-11 Thread George Velimachitis

Minor correction...

Both Scenarios allow the discreet/radeon card to render as expected
however there is a different problem which is visible when you run for
example..

DRI_PRIME=1 chromium_browser &

The window doesn't render unless you resize it couple of times and then the 
application becomes visible and user responsive. Also right clicking within the 
browser window gives empty rectangular.
The chrome://flags have both H/W acceleration and rasterisation to true

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1581270

Title:
  Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on
  resume

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  dmesg shows issues with being able to use the discrete graphics card
  (relevant dmesg lines attached).

  Grub does pass "radeon.modeset=1" but it doesn't seem to make a
  difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to
  the kernel, then it does not error (except for the VCE error -110,
  which is probably harmless).

  Running `DRI_PRIME=1 glxgears`:
  - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a black 
window with a visible top bar.
  - with just "radeon.modeset=1", error (attached as 'glxgears').

  Results are similar on Ubuntu GNOME 16.04, except with
  "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of
  screen tearing.

  Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
  attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:

  [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
  [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
  [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
  [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
  [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
  [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
  [   23.092276] [drm] UVD initialized successfully.
  [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
  [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
  [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
  [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
  [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
  [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
  [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).

  lsb_release -rd:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 12 20:43:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
     Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADH.017.140421.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP680Z5E-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 870Z5E/880Z5E/680Z5E
  dmi.product.version: P05ADH
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A

[Touch-packages] [Bug 1622378] Re: package libqtcore4 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of packag

2016-09-11 Thread Apport retracing service

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/1622378

Title:
  package libqtcore4 (not installed) failed to install/upgrade: trying
  to overwrite shared '/etc/xdg/Trolltech.conf', which is different from
  other instances of package libqtcore4:amd64

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  THis came up after I tried to install UNetbootin. I don't really know
  what's going on

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqtcore4 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Sep 11 13:42:23 2016
  DuplicateSignature:
   package:libqtcore4:(not installed)
   Unpacking libqtcore4:amd64 (4:4.8.7+dfsg-5ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libqtcore4_4%3a4.8.7+dfsg-5ubuntu2_amd64.deb (--unpack):
trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different 
from other instances of package libqtcore4:amd64
  ErrorMessage: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is 
different from other instances of package libqtcore4:amd64
  InstallationDate: Installed on 2014-08-31 (742 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qt4-x11
  Title: package libqtcore4 (not installed) failed to install/upgrade: trying 
to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other 
instances of package libqtcore4:amd64
  UpgradeStatus: Upgraded to xenial on 2016-08-06 (36 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1622378/+subscriptions

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

[Touch-packages] [Bug 1581801] Re: UUID base RESUME always wait 5 seconds for activating LVM swap