date:20170605

Sorry. Confirmed on artful. You just have to log in using the GNOME
session (not GNOME on Wayland). So this is a Xorg-specific bug, which
still exists.

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: lightdm (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Confirmed

** Tags added: artful

** Summary changed:

- cursor not following the theme while hovering the desktop and the windows 
decorations
+ Gnome (on Xorg) randomly ignores customized cursor theme

** Summary changed:

- Gnome (on Xorg) randomly ignores customized cursor theme
+ Gnome (on Xorg) dishonours customized cursor theme while hovering the desktop 
and the windows decorations

** Tags added: cursor

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

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

Title:
  Gnome (on Xorg) dishonours customized cursor theme while hovering the
  desktop and the windows decorations

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  If I use lightdm to load GNOME Shell, I encounter a very weird bug: if
  I move the cursor to hover the desktop, the cursor theme becomes DMZ
  White, but if I move the cursor over the GNOME panel or over any open
  window, it returns back to the custom theme set by me.

  I can experience this bug only when using lightdm, if I use gdm3 I
  always have the same cursor.

  Note that I'm not on Wayland and that I have nautilus folders on my
  desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun  6 02:14:12 2017
  InstallationDate: Installed on 2016-09-09 (269 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696019/+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 1696019] Re: cursor not following the theme while hovering the desktop and the windows decorations

It appears the bug does not exist in 17.10. So this is either Fix
Released post-16.04, or some problem specific to your custom theme.
Please help us to figure out which by:

1. Testing Ubuntu 17.10 or 17.04; and
2. Testing the standard Ambiance/Radiance themes.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

** Changed in: lightdm (Ubuntu)
   Status: New => Incomplete

** Changed in: nautilus (Ubuntu)
   Status: New => Incomplete

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

Title:
  Gnome (on Xorg) dishonours customized cursor theme while hovering the
  desktop and the windows decorations

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  If I use lightdm to load GNOME Shell, I encounter a very weird bug: if
  I move the cursor to hover the desktop, the cursor theme becomes DMZ
  White, but if I move the cursor over the GNOME panel or over any open
  window, it returns back to the custom theme set by me.

  I can experience this bug only when using lightdm, if I use gdm3 I
  always have the same cursor.

  Note that I'm not on Wayland and that I have nautilus folders on my
  desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun  6 02:14:12 2017
  InstallationDate: Installed on 2016-09-09 (269 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696019/+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 1693693] Re: Stuck on a black screen after logging out of Gnome Shell

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

** Changed in: lightdm (Ubuntu)
   Status: Incomplete => New

** Changed in: unity-greeter (Ubuntu)
   Status: Incomplete => New

** Description changed:

  Stuck on a black screen after logging out of Gnome Shell.
  
  Logging in via ssh shows gnome-shell is no longer running. But if I
- press Ctrl+Alt+F7 then the login screen (unity-greeter) comes up (and
- the login sound plays).
+ press Alt+F7 then the login screen (unity-greeter) comes up (and the
+ login sound plays).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri May 26 14:34:05 2017
  DisplayManager: lightdm
  GsettingsChanges:
-  b'org.gnome.shell' b'app-picker-view' b'uint32 1'
-  b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'chromium-browser.desktop', 'gnome-control-center.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']"
-  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
-  b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
+  b'org.gnome.shell' b'app-picker-view' b'uint32 1'
+  b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'chromium-browser.desktop', 'gnome-control-center.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']"
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+  b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (23 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- Stuck on a black screen after logging out of Gnome Shell
+ Stuck on a black screen (wrong VT) after logging out of Gnome Shell

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

Title:
  Stuck on a black screen (wrong VT) after logging out of Gnome Shell

Status in gnome-shell package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in unity-greeter package in Ubuntu:
  New

Bug description:
  Stuck on a black screen after logging out of Gnome Shell.

  Logging in via ssh shows gnome-shell is no longer running. But if I
  press Alt+F7 then the login screen (unity-greeter) comes up (and the
  login sound plays).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri May 26 14:34:05 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'chromium-browser.desktop', 'gnome-control-center.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (23 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693693/+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 1627311] Re: Xmir crashed with SIGABRT in send_message() from mir_buffer_stream_release()

** Changed in: canonical-devices-system-image
   Status: Incomplete => Invalid

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

Title:
  Xmir crashed with SIGABRT in send_message() from
  mir_buffer_stream_release()

Status in Canonical System Image:
  Invalid
Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

  ubuntu 16.10 + proposed unity8 session / x86 / nvidia

  this crash was triggered by closing Firefox window (firefox installed through 
libertine)
  result -> black screen, unity8 crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: xmir 2:1.18.4-1ubuntu6
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Sep 24 16:40:18 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xmir
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: LeadTek Research Inc. G84 [GeForce 8600 GT] [107d:2a8a]
  InstallationDate: Installed on 2016-06-05 (110 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 10c4:8103 Cygnal Integrated Products, Inc. 
   Bus 002 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MSI MS-7369
  ProcCmdline: Xmir -title @ -displayfd 3 -mir yakkety_firefox_0.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-16-generic 
root=UUID=5df9f676-aa66-4983-a2d8-fd6dbf07719a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  Title: Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/11/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.6
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7369
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.6:bd03/11/2008:svnMSI:pnMS-7369:pvr1.0:rvnMSI:rnMS-7369:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7369
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sat Sep 24 16:44:28 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB USB Keykoard KEYBOARD, id 8
   inputUSB USB Keykoard KEYBOARD, id 9
   inputYSPRINGTECH USB OPTICAL MOUSE MOUSE, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: nouveau

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

-- 
Mailing list:

[Touch-packages] [Bug 1695872] Re: GNOME on Wayland session could not be started from lightdm

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

** Changed in: lightdm (Ubuntu)
   Status: Incomplete => New

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

Title:
  GNOME on Wayland session could not be started from lightdm

Status in gnome-shell package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695872/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-05 Thread Ubuntu Foundations Team Bug Bot

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

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

** Tags added: patch

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1696042] Re: package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

** Tags removed: need-duplicate-check

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

Title:
  package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  Ubantu version : 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CrashReports: 600:0:122:68434:2017-06-06 09:39:28.350133180 +0530:2017-06-06 
09:39:29.350133180 +0530:/var/crash/python3-apport.0.crash
  Date: Tue Jun  6 09:39:29 2017
  DuplicateSignature:
   package:python3-apport:2.20.4-0ubuntu4
   Setting up libldap-common (2.4.44+dfsg-3ubuntu2.1) ...
   dpkg: error processing package python3-apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-17 (19 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1696042/+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 1696042] [NEW] package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura

2017-06-05 Thread Sajan Beetu

Public bug reported:

Ubantu version : 17.04

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: python3-apport 2.20.4-0ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportLog:
 
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CrashReports: 600:0:122:68434:2017-06-06 09:39:28.350133180 +0530:2017-06-06 
09:39:29.350133180 +0530:/var/crash/python3-apport.0.crash
Date: Tue Jun  6 09:39:29 2017
DuplicateSignature:
 package:python3-apport:2.20.4-0ubuntu4
 Setting up libldap-common (2.4.44+dfsg-3ubuntu2.1) ...
 dpkg: error processing package python3-apport (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-05-17 (19 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: apport
Title: package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  Ubantu version : 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CrashReports: 600:0:122:68434:2017-06-06 09:39:28.350133180 +0530:2017-06-06 
09:39:29.350133180 +0530:/var/crash/python3-apport.0.crash
  Date: Tue Jun  6 09:39:29 2017
  DuplicateSignature:
   package:python3-apport:2.20.4-0ubuntu4
   Setting up libldap-common (2.4.44+dfsg-3ubuntu2.1) ...
   dpkg: error processing package python3-apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-17 (19 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package python3-apport 2.20.4-0ubuntu4 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1696042/+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 1627311] Re: Xmir crashed with SIGABRT in send_message() from mir_buffer_stream_release()

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

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Xmir crashed with SIGABRT in send_message() from
  mir_buffer_stream_release()

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

  ubuntu 16.10 + proposed unity8 session / x86 / nvidia

  this crash was triggered by closing Firefox window (firefox installed through 
libertine)
  result -> black screen, unity8 crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: xmir 2:1.18.4-1ubuntu6
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Sep 24 16:40:18 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xmir
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: LeadTek Research Inc. G84 [GeForce 8600 GT] [107d:2a8a]
  InstallationDate: Installed on 2016-06-05 (110 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 10c4:8103 Cygnal Integrated Products, Inc. 
   Bus 002 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MSI MS-7369
  ProcCmdline: Xmir -title @ -displayfd 3 -mir yakkety_firefox_0.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-16-generic 
root=UUID=5df9f676-aa66-4983-a2d8-fd6dbf07719a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  Title: Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/11/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.6
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7369
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.6:bd03/11/2008:svnMSI:pnMS-7369:pvr1.0:rvnMSI:rnMS-7369:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7369
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sat Sep 24 16:44:28 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB USB Keykoard KEYBOARD, id 8
   inputUSB USB Keykoard KEYBOARD, id 9
   inputYSPRINGTECH USB OPTICAL MOUSE MOUSE, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: nouveau

To manage notifications about this bug go to:

[Touch-packages] [Bug 1627311] Re: Xmir crashed with SIGABRT in send_message() from mir_buffer_stream_release()

[Expired for Mir because there has been no activity for 60 days.]

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

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

Title:
  Xmir crashed with SIGABRT in send_message() from
  mir_buffer_stream_release()

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

  ubuntu 16.10 + proposed unity8 session / x86 / nvidia

  this crash was triggered by closing Firefox window (firefox installed through 
libertine)
  result -> black screen, unity8 crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: xmir 2:1.18.4-1ubuntu6
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Sep 24 16:40:18 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xmir
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: LeadTek Research Inc. G84 [GeForce 8600 GT] [107d:2a8a]
  InstallationDate: Installed on 2016-06-05 (110 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 10c4:8103 Cygnal Integrated Products, Inc. 
   Bus 002 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MSI MS-7369
  ProcCmdline: Xmir -title @ -displayfd 3 -mir yakkety_firefox_0.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-16-generic 
root=UUID=5df9f676-aa66-4983-a2d8-fd6dbf07719a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  Title: Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/11/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.6
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7369
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.6:bd03/11/2008:svnMSI:pnMS-7369:pvr1.0:rvnMSI:rnMS-7369:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7369
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sat Sep 24 16:44:28 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB USB Keykoard KEYBOARD, id 8
   inputUSB USB Keykoard KEYBOARD, id 9
   inputYSPRINGTECH USB OPTICAL MOUSE MOUSE, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: nouveau

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

--

[Touch-packages] [Bug 1627311] Re: Xmir crashed with SIGABRT in send_message() from mir_buffer_stream_release()

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

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

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

Title:
  Xmir crashed with SIGABRT in send_message() from
  mir_buffer_stream_release()

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

  ubuntu 16.10 + proposed unity8 session / x86 / nvidia

  this crash was triggered by closing Firefox window (firefox installed through 
libertine)
  result -> black screen, unity8 crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: xmir 2:1.18.4-1ubuntu6
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Sep 24 16:40:18 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xmir
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: LeadTek Research Inc. G84 [GeForce 8600 GT] [107d:2a8a]
  InstallationDate: Installed on 2016-06-05 (110 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 10c4:8103 Cygnal Integrated Products, Inc. 
   Bus 002 Device 002: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MSI MS-7369
  ProcCmdline: Xmir -title @ -displayfd 3 -mir yakkety_firefox_0.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-16-generic 
root=UUID=5df9f676-aa66-4983-a2d8-fd6dbf07719a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  Title: Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/11/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.6
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7369
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.6:bd03/11/2008:svnMSI:pnMS-7369:pvr1.0:rvnMSI:rnMS-7369:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7369
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sat Sep 24 16:44:28 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB USB Keykoard KEYBOARD, id 8
   inputUSB USB Keykoard KEYBOARD, id 9
   inputYSPRINGTECH USB OPTICAL MOUSE MOUSE, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: nouveau

To manage notifications about this bug go to:

[Touch-packages] [Bug 1696019] Re: cursor not following the theme while hovering the desktop and the windows decorations

After making the screencast something fixed this behaviour, at least for
this session..

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

Title:
  cursor not following the theme while hovering the desktop and the
  windows decorations

Status in gnome-shell package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  If I use lightdm to load GNOME Shell, I encounter a very weird bug: if
  I move the cursor to hover the desktop, the cursor theme becomes DMZ
  White, but if I move the cursor over the GNOME panel or over any open
  window, it returns back to the custom theme set by me.

  I can experience this bug only when using lightdm, if I use gdm3 I
  always have the same cursor.

  Note that I'm not on Wayland and that I have nautilus folders on my
  desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun  6 02:14:12 2017
  InstallationDate: Installed on 2016-09-09 (269 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696019/+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 1696019] Re: cursor not following the theme while hovering the desktop and the windows decorations

I made a screencast of this behaviour. I rescaled it to keep it in a
limited size

** Attachment added: "untitled.mpg"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1696019/+attachment/4889756/+files/untitled.mpg

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

Title:
  cursor not following the theme while hovering the desktop and the
  windows decorations

Status in gnome-shell package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  If I use lightdm to load GNOME Shell, I encounter a very weird bug: if
  I move the cursor to hover the desktop, the cursor theme becomes DMZ
  White, but if I move the cursor over the GNOME panel or over any open
  window, it returns back to the custom theme set by me.

  I can experience this bug only when using lightdm, if I use gdm3 I
  always have the same cursor.

  Note that I'm not on Wayland and that I have nautilus folders on my
  desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun  6 02:14:12 2017
  InstallationDate: Installed on 2016-09-09 (269 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696019/+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 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

Done.

Also note we are working to release at least one significant update soon
for Ubuntu 16.04 Bluetooth audio support. So the PPA fixes will go
mainstream...

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

Title:
[xenial] Bluetooth device doesn't play any sound in A2DP mode unless
set to HSP/HFP first

Status in bluez package in Ubuntu:
Invalid
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Xenial:
In Progress

Bug description:
[Impact]
Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP
first. A2DP is the high quality profile used for Bluetooth speakers and music
in general.

[Test Case]
1. Pair a Bluetooth audio device with Ubuntu.
2. Verify in Sound settings you have it set to A2DP mode.
3. Turn off and then on the Bluetooth device.
4. Verify the device has reconnected and if not, force it to in the Bluetooth
indicator menu.
5. Open Sound settings again, select the device and verify it's reappeared in
A2DP mode.
6. Click 'Test Sound'.
Expected: Sound can be heard from the Bluetooth device.

[Regression Potential]
Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main
area affected. A combination of related A2DP bugs in pulseaudio in xenial means
it is difficult to get working at all without this patch. So highly unlikely
Bluetooth audio support could get worse. Since pulseaudio itself is being
modified there is always a regression potential in support for other audio
devices, but several audio devices have been tested and all continue to work
well with the patch.

[Other notes]
Related to bug 1283003 and bug 1438510. Possibly others too.

Please note that Bluetooth and Bluetooth audio support in xenial is
still not perfect. This SRU only aims to address a few of the most
troublesome issues. Please consider the fact that this is an
incremental improvement and some people are still likely to experience
some bugs related to pulseaudio and Bluetooth, even after this SRU.

The patch was authored by Luke Yelavich with help from Konrad
Zapałowicz. And it has received further testing over the past two
months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
here only changes the changelog wording from Luke's original PPA.

[Original Description]
I have a Sennheiser MM 450-X headset.

In 15.10, connection & playback was straightforward.

In 16.04, the headset connects, and shows up as default playback
device on `pavucontrol`, but there is no sound.

A functional workaround is to, after having connected it, to go the
`Configuration` tab, and in the `Profile` dropdown, to choose `...
HSP/HFP`, which will make them play as expected (but in low quality),
then switch to `... A2DP Sink` (they will play in high quality).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm
nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: myuser2936 F pulseaudio
/dev/snd/controlC2: myuser2936 F pulseaudio
/dev/snd/controlC0: myuser2936 F pulseaudio
Date: Mon May 16 14:18:58 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-03-11 (66 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/22/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A88XN-WIFI
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

--
Mailing list:

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-05 Thread Nicholas Stommel

The actual patch is attached above and can be applied to the source code
which you can build yourself. But for your convenience, I have attached
the .deb file below:

** Attachment added: "patched network manager .deb for easy fix installation on 
Ubuntu 17.04"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317/+attachment/4889755/+files/network-manager_1.4.4-1ubuntu3_amd64.deb

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-05 Thread Nicholas Stommel

Please note that this patch and fix only works for Ubuntu 17.04 which relies on
systemd-resolved as a DNS/DNSSEC stub resolver, as well as an LLMNR resolver.

You also need to be using a network-manager plugin like 
network-manager-openvpn-gnome.
Install and configure an openvpn connection after going 'sudo apt-get install 
network-manager-
openvpn-gnome', importing a config file, connecting (if possible), and 
observing the fact that
there are DNS leaks (queries WILL be routed to your ISP) with online tools like 
those at
https://dnsleaktest.com. Otherwise, just know that systemd-resolved naturally 
leaks DNS queries
over all configured domains on all interfaces by design unless a specific 
system bus call is made.
In this case, the SetLinkDomains(in  i ifindex, in  a(sb) domains) method, if 
passed
the interface index followed by an array containing the "routing-only" domain 
"~." 
(see https://manpages.debian.org/testing/systemd/systemd.network.5.en.html) and 
the boolean true.
But enough with the technical details, lets move on to the fix!

First, make sure you have all necessary packages to build the network
manager, install with:

sudo apt update
sudo apt-get build-dep network-manager

cd ~/Documents
mkdir nm && cd nm
apt-get source network-manager
cd network-manager-1.4.4/

Copy the patch file into the network-manager-1.4.4 directory:

cp ~/Downloads/resolved-vpn-dns-leak-fix.patch .

Apply the patch with:

patch -p1 < resolved-vpn-dns-leak-fix.patch

Remove patch from source directory before compilation:

rm resolved-vpn-dns-leak-fix.patch

Compile and build .deb package for installation (this will take a
while):

dpkg-buildpackage -us -uc -b

The compiled .debs should be in the parent directory you created nm:

cd ../

First, stop all network services:

sudo service network-manager stop
sudo service networking stop

Install just the patched network manager (the other .debs are not
necessary):

sudo dpkg -i network-manager_1.4.4-1ubuntu3_amd64.deb

Bring network services back up:

sudo service networking start
sudo service network-manager start

Connect to standard openvpn via network-manager-openvpn GUI (or other plugin)
Search the syslog for something like:

NetworkManager[876]:   [1496716774.9849] 
systemd-resolved[0x55b0132ec2b0]: Link type is VPN
TUN or TAP, fixing DNS leak...

and verify that the VPN link (for example tun0) includes the descriptor:
DNS Domain: ~.

using the command:

systemd-resolve --status

When compiling network manager, several bogus links are created and will show 
up when
you type 'systemd-resolve --status', don't worry they will disappear once you 
reboot.

Then open your browser, navigate to https://dnsleaktest.com and select Extended 
test
You should only see your VPN provider's DNS servers. For example, with PIA you 
should see
something like:

Test complete

Query round Progress... Servers found
  1  ..  1
  2  ..  1
  3  ..  1
  4  ..  1
  5  ..  1
  6  ..  1

IP  HostnameISP Country
173.239.220.5   ip-5-220-239-173.east.us.northamericancoax.com  GoLightSpeed
United States

Now, to prevent Ubuntu apt from replacing your patched, VPN-DNS-leak-
free version of network manager that relies on systemd-resolved, use the
command:

sudo apt-mark hold network-manager

Thats all, you're done. Congrats, no DNS leaks on Ubuntu 17.04!
I hope that I was able to make your life easier and more secure using openvpn 
or other
vpn services through the built-in GUI for the Gnome NetworkManager on Ubuntu 
17.04 :)

(Side note: I am a college student and C/C++ dev who loves Ubuntu <3 Also, this 
took quite a bit
of research on the GLib API, systemd-resolved API, and much much tracing using 
our good friend
'grep -r' for built in functions and enums of the Gnome network manager itself. 
No additional
compiler warnings are generated, the patch conforms to the C90 standard, and 
the syntax style 
used throughout the network manager source code was maintained.)

I will attach the small text patch generated using 'diff -u' along with the 
patched generated 
.deb file for your convenience. Cheers, and I hope this helps you all!

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-06-05 Thread Nicholas Stommel

** Patch added: "patch for network-manager source"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317/+attachment/4889747/+files/resolved-vpn-dns-leak-fix.patch

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1696019] Re: cursor not following the theme while hovering the desktop and the windows decorations

** Summary changed:

- cursor not following the theme while hovering the desktop
+ cursor not following the theme while hovering the desktop and the windows 
decorations

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

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

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

Title:
  cursor not following the theme while hovering the desktop and the
  windows decorations

Status in gnome-shell package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  If I use lightdm to load GNOME Shell, I encounter a very weird bug: if
  I move the cursor to hover the desktop, the cursor theme becomes DMZ
  White, but if I move the cursor over the GNOME panel or over any open
  window, it returns back to the custom theme set by me.

  I can experience this bug only when using lightdm, if I use gdm3 I
  always have the same cursor.

  Note that I'm not on Wayland and that I have nautilus folders on my
  desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun  6 02:14:12 2017
  InstallationDate: Installed on 2016-09-09 (269 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696019/+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 1695872] Re: GNOME on Wayland session could not be started from lightdm

I receive the following warning:
Hint: You are currently not seeing messages from other users and the system.
  Users in the 'systemd-journal' group can see all messages. Pass -q to
  turn off this notice.
No journal files were opened due to insufficient permissions.

Retrying as superuser I didn't receive the warning but the log was
empty..

** Attachment added: "gnome-shell.log"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1695872/+attachment/4889746/+files/gnome-shell.log

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

Title:
  GNOME on Wayland session could not be started from lightdm

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695872/+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 1691556] Re: Can't send audio to Amazon Echo via Bluetooth

** This bug is no longer a duplicate of bug 1582213
   [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to 
HSP/HFP first

** Tags added: a2dp

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

Title:
  Can't send audio to Amazon Echo via Bluetooth

Status in bluez package in Ubuntu:
  New

Bug description:
  Pairing and coupling to Amazon Echo works, but no sound is heard.

  I believe the issue is related to the fact that Amazon Echo is paired
  as a handset (i.e., speaker + microphone) rather than just as a
  speaker.  I believe the critical error is found in a dmesg line such
  as:

  Feb 28 10:59:05 n1 bluetoothd[1025]: a2dp-source profile connect
  failed for 50:F5:DA:A6:3F:EA: Device or resource busy

  as I describe in the askubuntu.com discussion at:

  https://askubuntu.com/questions/871630/cant-send-audio-to-amazon-echo-
  via-bluetooth

  I have clarified there my thinking and the steps I've taken thus far
  on this issue, which includes trying debug bluetooth per the Ubuntu
  wiki page which describes how to do so.

  This is probably an upstream issue, as Mike H-R has commented there
  that the problem also occurs on ArchLinux.

  I and a few others would like to get this resolved, and I am happy to
  help (I'm a software developer).  However, at this point, I'm not sure
  how to proceed without some assistance.  I suppose I could report it
  to Debain, but I've only ever used Debain vis a vis Ubuntu, so I
  thought it best to start here.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 17 22:27:59 2017
  InstallationDate: Installed on 2015-12-26 (507 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2017-02-28 (78 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: DC:53:60:97:55:17  ACL MTU: 1021:5  SCO MTU: 96:6
    UP RUNNING PSCAN
    RX bytes:13547334 acl:58 sco:0 events:1935087 errors:0
    TX bytes:1652407651 acl:1934967 sco:0 commands:76 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1691556/+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 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

2017-06-05 Thread Doug Morse

@Daniel van Vugt (vanvugt):  Thanks for your assistance!

I am not Mary Sherman, and I'm continuing to experience this problem,
even with the PPA and after rebooting.

I didn't subscribe to this bug, I didn't even know about it.  I report
bug 1691556 and you marked it a duplicate of this one.

As I have already requested, kindly re-open my bug 1691556, as I don't
believe I can re-open it myself.

Finally, I'd like to see this fixed in 16.04.  It's LTS, and that's
important to me (and a lot of users).  If that means I have to help with
backport, I'm happy to do so.  In addition, if I can be helpful with
debugging, I'd be happy to do so, and have tried.  It's just not clear
to me at this point how to get better / more detailed debugging info.
What I did try per https://wiki.ubuntu.com/DebuggingBluetooth didn't
reveal anything helpful.  For me, I believe the key issue is figuring
out the "Device or resource busy" error (as I've mentioned here and in
my original bug report).

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

Title:
  [xenial] Bluetooth device doesn't play any sound in A2DP mode unless
  set to HSP/HFP first

Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress

Bug description:
  [Impact]
  Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP 
first. A2DP is the high quality profile used for Bluetooth speakers and music 
in general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Verify in Sound settings you have it set to A2DP mode.
  3. Turn off and then on the Bluetooth device.
  4. Verify the device has reconnected and if not, force it to in the Bluetooth 
indicator menu.
  5. Open Sound settings again, select the device and verify it's reappeared in 
A2DP mode.
  6. Click 'Test Sound'.
  Expected: Sound can be heard from the Bluetooth device.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1438510. Possibly others too.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  I have a Sennheiser MM 450-X headset.

  In 15.10, connection & playback was straightforward.

  In 16.04, the headset connects, and shows up as default playback
  device on `pavucontrol`, but there is no sound.

  A functional workaround is to, after having connected it, to go the
  `Configuration` tab, and in the `Profile` dropdown, to choose `...
  HSP/HFP`, which will make them play as expected (but in low quality),
  then switch to `... A2DP Sink` (they will play in high quality).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  myuser2936 F pulseaudio
   /dev/snd/controlC2:  myuser2936 F pulseaudio
   /dev/snd/controlC0:  myuser2936 F pulseaudio
  Date: Mon May 16 14:18:58 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-11 (66 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.

[Touch-packages] [Bug 1695567] Re: /usr/bin/gnome-shell:* Error in `/usr/bin/gnome-shell': double free or corruption (out): ADDR * in g_free() from gweather_location_unref()

** Description changed:

  [Impact]
  Backport git patch that fixes memory corruption in libgweather that is 
causing gnome-shell to crash. This is particularly bad on wayland as it causes 
the user to lose their sessions
  
  I believe this should also fix bug 1688208 and potentially a couple of
  other high ranking crashes on errors.ubuntu.com. I have not however
  found reliable reproducers for those other bugs.
+ 
+ This error has been reported over 700 times on errors.ubuntu.com for
+ Ubuntu GNOME 17.04.
  
  [Test Case]
  After update of libgweather
  1. Ensure org.gnome.Weather.Application locations is not set (as per default 
setting)
  2. Disable Location Services
  3. gnome-shell should not crash
  
  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.
  
   Original bug report 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.2-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/06422e05faafe183b4cb70daa7306dcb4c08c97e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

** Description changed:

  [Impact]
  Backport git patch that fixes memory corruption in libgweather that is 
causing gnome-shell to crash. This is particularly bad on wayland as it causes 
the user to lose their sessions
  
  I believe this should also fix bug 1688208 and potentially a couple of
  other high ranking crashes on errors.ubuntu.com. I have not however
  found reliable reproducers for those other bugs.
  
  This error has been reported over 700 times on errors.ubuntu.com for
  Ubuntu GNOME 17.04.
  
  [Test Case]
  After update of libgweather
  1. Ensure org.gnome.Weather.Application locations is not set (as per default 
setting)
  2. Disable Location Services
  3. gnome-shell should not crash
  
  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.
  
+ [Other Info]
+ This updates libgweather from 3.24.0 to 3.24.1
+ https://git.gnome.org/browse/libgweather/log
+ 
+ The guard_against_segfault commit was already present in Ubuntu 17.04.
+ 
   Original bug report 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.2-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/06422e05faafe183b4cb70daa7306dcb4c08c97e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

** Changed in: libgweather (Ubuntu Zesty)
   Importance: Undecided => High

** Changed in: libgweather (Ubuntu)
   Importance: Undecided => High

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

Title:
  /usr/bin/gnome-shell:*** Error in `/usr/bin/gnome-shell': double free
  or corruption (out): ADDR *** in g_free() from
  gweather_location_unref()

Status in gnome-shell package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Zesty:
  In Progress

Bug description:
  [Impact]
  Backport git patch that fixes memory corruption in libgweather that is 
causing gnome-shell to crash. This is particularly bad on wayland as it causes 
the user to lose their sessions

  I believe this should also fix bug 1688208 and potentially a couple of
  other high ranking crashes on errors.ubuntu.com. I have not however
  found reliable reproducers for those other bugs.

  This error has been reported over 700 times on errors.ubuntu.com for
  Ubuntu GNOME 17.04.

  [Test Case]
  After update of libgweather
  1. Ensure org.gnome.Weather.Application locations is not set (as per default 
setting)
  2. Disable Location Services
  3. gnome-shell should not crash

  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.

  [Other Info]
  This updates libgweather from 3.24.0 to 3.24.1
  https://git.gnome.org/browse/libgweather/log

  The guard_against_segfault commit was already present in Ubuntu 17.04.

   Original bug report 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.2-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/06422e05faafe183b4cb70daa7306dcb4c08c97e 
contains more details, including

[Touch-packages] [Bug 1695872] Re: GNOME on Wayland session could not be started from lightdm

OK, could you please:

1. Start a separate VT login: Ctrl+Alt+F4, and log in.
2. Return to lightdm (Ctrl+Alt+F7) and attempt a Gnome login.
3. After it fails return to Ctrl+Alt+F4 and take a copy of the log using this 
command:
   journalctl /usr/bin/gnome-shell > gnome-shell.log
4. Attach gnome-shell.log to this bug.

I hope in future bug reports will do this automatically for users, but
they don't yet.

** Changed in: lightdm (Ubuntu)
   Status: New => Incomplete

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  GNOME on Wayland session could not be started from lightdm

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695872/+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 1688208] Re: gnome-shell crashed with SIGSEGV in foreach_city() from foreach_city() from foreach_city() from foreach_city() from foreach_city()

** Description changed:

+ Impact
+ ==
+ Memory corruption in libgweather caused gnome-shell to crash. This is 
particularly bad for GNOME on Wayland as a gnome-shell crash will causes the 
user to lose their sessions.
+ 
+ (GNOME Shell 3.24 introduced a new weather feature in the clock menu.)
+ 
+ This particular error has been reported over 1000 times to
+ errors.ubuntu.com from Ubuntu GNOME 17.04 and was also a Fedora 26
+ blocker bug.
+ 
+ Test Case
+ =
+ The number of crashes reported on errors.ubuntu.com for gnome-shell should be 
significantly lower once this new version of libgweather rolls out.
+ 
+ Because e.u.com links this issue with gnome-shell, this is difficult to
+ verify except that if you run gnome-shell, it shouldn't crash so often
+ especially when first logging in.
+ 
+ Regression Potential
+ 
+ The main new commit here had already been cherry-picked by Fedora and in 
Ubuntu 17.10 Alpha. Considering the previous 
+ 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.1-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/39b6625ed47999dab38b064b2d91bde1e11dec62 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

Title:
  gnome-shell crashed with SIGSEGV in foreach_city() from foreach_city()
  from foreach_city() from foreach_city() from foreach_city()

Status in libgweather:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Zesty:
  In Progress

Bug description:
  Impact
  ==
  Memory corruption in libgweather caused gnome-shell to crash. This is 
particularly bad for GNOME on Wayland as a gnome-shell crash will causes the 
user to lose their sessions.

  (GNOME Shell 3.24 introduced a new weather feature in the clock menu.)

  This particular error has been reported over 1000 times to
  errors.ubuntu.com from Ubuntu GNOME 17.04 and was also a Fedora 26
  blocker bug.

  Test Case
  =
  The number of crashes reported on errors.ubuntu.com for gnome-shell should be 
significantly lower once this new version of libgweather rolls out.

  Because e.u.com links this issue with gnome-shell, this is difficult
  to verify except that if you run gnome-shell, it shouldn't crash so
  often especially when first logging in.

  Regression Potential
  
  The main new commit here had already been cherry-picked by Fedora and in 
Ubuntu 17.10 Alpha. Considering the previous 

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1688208/+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 1695872] Re: GNOME on Wayland session could not be started from lightdm

I have an nvidia/intel hybrid GPU (GTX-850M), with nvidia proprietary
drivers (nvidia-375) from the supported drivers PPA. The attempt failed
when using the intel GPU, so the nvidia part is not involved. Using GDM
I could load a fully functional Wayland session.

I'm using also the most updated Linux/X/Mesa HWE stack from main
repository (I think it's based on the 16.10 stack).

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

Title:
  GNOME on Wayland session could not be started from lightdm

Status in gnome-shell package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695872/+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 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

All,

I have spent some time looking at the major Bluetooth/audio pain points
recently. And a common problem is simply that some bugs are
oversubscribed. Everyone experiences bugs slightly differently and it
clouds the issue to the point of us not being able to ever close it.

But the answer is simple: If your name is not Mary Sherman and you
continue to experience problems even with the PPA (and after rebooting)
then please log a separate bug of your own.

P.S. Also generally speaking Bluetooth audio support is still maturing
so my advice is if you rely on Bluetooth audio then you should be using
the latest (17.04+) Ubuntu release. It certainly was not ready for
general usage in 16.04.

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

Title:
  [xenial] Bluetooth device doesn't play any sound in A2DP mode unless
  set to HSP/HFP first

Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress

Bug description:
  [Impact]
  Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP 
first. A2DP is the high quality profile used for Bluetooth speakers and music 
in general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Verify in Sound settings you have it set to A2DP mode.
  3. Turn off and then on the Bluetooth device.
  4. Verify the device has reconnected and if not, force it to in the Bluetooth 
indicator menu.
  5. Open Sound settings again, select the device and verify it's reappeared in 
A2DP mode.
  6. Click 'Test Sound'.
  Expected: Sound can be heard from the Bluetooth device.

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1283003 and bug 1438510. Possibly others too.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  I have a Sennheiser MM 450-X headset.

  In 15.10, connection & playback was straightforward.

  In 16.04, the headset connects, and shows up as default playback
  device on `pavucontrol`, but there is no sound.

  A functional workaround is to, after having connected it, to go the
  `Configuration` tab, and in the `Profile` dropdown, to choose `...
  HSP/HFP`, which will make them play as expected (but in low quality),
  then switch to `... A2DP Sink` (they will play in high quality).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  myuser2936 F pulseaudio
   /dev/snd/controlC2:  myuser2936 F pulseaudio
   /dev/snd/controlC0:  myuser2936 F pulseaudio
  Date: Mon May 16 14:18:58 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-11 (66 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias:

[Touch-packages] [Bug 1695567] Re: /usr/bin/gnome-shell:* Error in `/usr/bin/gnome-shell': double free or corruption (out): ADDR * in g_free() from gweather_location_unref()

** Summary changed:

- /usr/bin/gnome-shell:*** Error in `/usr/bin/gnome-shell': double free or 
corruption (out): ADDR ***
+ /usr/bin/gnome-shell:*** Error in `/usr/bin/gnome-shell': double free or 
corruption (out): ADDR *** in g_free() from gweather_location_unref()

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

Title:
  /usr/bin/gnome-shell:*** Error in `/usr/bin/gnome-shell': double free
  or corruption (out): ADDR *** in g_free() from
  gweather_location_unref()

Status in gnome-shell package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Zesty:
  In Progress

Bug description:
  [Impact]
  Backport git patch that fixes memory corruption in libgweather that is 
causing gnome-shell to crash. This is particularly bad on wayland as it causes 
the user to lose their sessions

  I believe this should also fix bug 1688208 and potentially a couple of
  other high ranking crashes on errors.ubuntu.com. I have not however
  found reliable reproducers for those other bugs.

  [Test Case]
  After update of libgweather
  1. Ensure org.gnome.Weather.Application locations is not set (as per default 
setting)
  2. Disable Location Services
  3. gnome-shell should not crash

  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695567/+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 1695292] Re: I can see through the title bar when the window is maximized

This bug appears to be fixed in 17.10. Maybe just wait for the themes
backport.

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

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

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

Title:
  I can see through the title bar when the window is maximized

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  I'm using gnome-shell in Ubuntu 17.04
  When I maximize a window in the following programs: Firefox, Terminal, 
Rhythmbox, LibreOffice. I can see the background colors in top and bottom 
margins of the title bar.

  The bug is present in Ambiance and Radiance themes.
  The bug is not present in Nautilus, Google Chrome and Gnome Tweak Tool.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: light-themes 16.10+17.04.20170406-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jun  2 16:13:15 2017
  InstallationDate: Installed on 2017-02-18 (103 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to zesty on 2017-05-22 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1695292/+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 1693724] Re: Context menus have no animation/fade-in under Gnome Shell

Both. A regression in visual quality when compared to Unity7 is a bug.
Even if it sounds like an enhancement :)

** Tags added: visual-quality

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

Title:
  Context menus have no animation/fade-in under Gnome Shell

Status in gnome-shell package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Context menus have no animation/fade-in under Gnome Shell. The
  transitions under Unity7 for context menus look nicer, less abrupt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693724/+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 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Ralph, as this bug is closed you should open a new one if you have any
continuing issues.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1681870

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Fix Released
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  Fix Released
Status in pay-service package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  Won't Fix
Status in unity8 package in Ubuntu:
  Fix Released
Status in url-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  Added other packages that could have been affected as the crash is due
  to some ABI break in ubuntu-app-launch.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1681870/+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 1574347] Re: WiFi networks list disappears (device type not reloaded)

All: Commenting on a closed bug will generally be ignored (even if it
was closed erroneously).

If you have continuing issues then please log a new bug.

** Changed in: network-manager (Ubuntu)
 Assignee: Marzenco Alexandru Ionuț (thors-hand) => (unassigned)

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

Title:
  WiFi networks list disappears (device type not reloaded)

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  
   WARNING 
  
  If you are still experiencing this bug please don't comment here, but look at 
these: (https://goo.gl/LdPpYG)

  **
   HOW TO REPRODUCE
  **
  Boot the system.

  
   RESULT
  
  From time to time, some of these happen:
  - The applet doesn't list any wireless network.
  - The applet doesn't show the name of the current network.
  - The icon shows the wired connection symbol, instead of the wifi one.

  *
   WORK AROUND
  *
  (http://askubuntu.com/questions/762198/16-04-lts-wifi-connection-issues)

  *
   FIX
  *
  The applet needs to re-read the DEVTYPE after the device name changed.

  ***
   HOW TO TEST A FIX
  ***
  In the Terminal application enter:
  nmcli dev

  If it works, in the line for the wireless device, the TYPE column
  should be "wifi". If it doesn't it will be "ethernet".

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1695872] Re: GNOME on Wayland session could not be started from lightdm

That might be true, but NVIDIA isn't mentioned anywhere in this bug.

fcole90: What GPU/drivers are you using?

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

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

Title:
  GNOME on Wayland session could not be started from lightdm

Status in gnome-shell package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  GNOME on Wayland session could not be started from lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  5 11:23:22 2017
  InstallationDate: Installed on 2016-09-09 (268 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695872/+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 1696022] Re: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

** Tags removed: need-duplicate-check

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

Title:
  package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  something not right

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-96-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Mon Jun  5 18:50:23 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2016-04-11 (420 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: Upgraded to xenial on 2016-09-21 (257 days ago)

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

Re: [Touch-packages] [Bug 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

2017-06-05 Thread Ralph Gilbert

Antonio,
Thank you for your report saying the bug was fixed...
I must report I've had a few problems that I have reported.Like "system 
setting" wont open from the "gear" in the corner,and I lost the Ubuntu Software 
center from the launch pad andothers... However in searching for possible 
answers I found these 2 commands in one answer:
Sudo apt-get update && apt-get dist-upgrade, andSudo do-release upgrade -d
Running these 2 solved all my known problems. What they didI'm still not sure - 
maybe a total re-install I'm not sure. I'm trying to learn...
Again thanks.


 

On Monday, June 5, 2017 4:41 PM, Launchpad Bug Tracker 
<1681...@bugs.launchpad.net> wrote:
 

 ** Branch linked: lp:~ci-train-bot/indicator-datetime/indicator-
datetime-ubuntu-artful-2797

-- 
You received this bug notification because you are subscribed to a
duplicate bug report (1681127).
https://bugs.launchpad.net/bugs/1681870

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Fix Released
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  Fix Released
Status in pay-service package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  Won't Fix
Status in unity8 package in Ubuntu:
  Fix Released
Status in url-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  Added other packages that could have been affected as the crash is due
  to some ABI break in ubuntu-app-launch.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1681870/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1681870

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Fix Released
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  Fix Released
Status in pay-service package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  Won't Fix
Status in unity8 package in Ubuntu:
  Fix Released
Status in url-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  Added other packages that could have been

[Touch-packages] [Bug 1696022] [NEW] package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

2017-06-05 Thread Alex Telnyi

Public bug reported:

something not right

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shared-mime-info 1.5-2ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39
Uname: Linux 3.13.0-96-generic i686
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: i386
Date: Mon Jun  5 18:50:23 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 139
InstallationDate: Installed on 2016-04-11 (420 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
UpgradeStatus: Upgraded to xenial on 2016-09-21 (257 days ago)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  something not right

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-96-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Mon Jun  5 18:50:23 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2016-04-11 (420 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: Upgraded to xenial on 2016-09-21 (257 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1696022/+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 1695876] Re: German Documentation file displays incorrect CUPS version

2017-06-05 Thread Bug Watch Updater

** Changed in: cups
   Status: Unknown => New

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

Title:
  German Documentation file displays incorrect CUPS version

Status in CUPS:
  New
Status in cups package in Ubuntu:
  New

Bug description:
  The /doc/de/index.html.in file in the package source has an incorrect
  version number written into a header instead of using '@CUPS_VERSION@'
  to populate this file as in the other languages' version of the same
  file, seemingly resulting in /usr/share/cups/doc-root/de/index.html
  having the wrong version once CUPS is installed:

  ...
  

  CUPS 2.0.2
  ...

  instead of:

  ...
  

  CUPS @CUPS_VERSION@
  ...

  resulting in 'CUPS 2.0.2' instead of 2.1.3 being shown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1695876/+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 1696019] [NEW] cursor not following the theme while hovering the desktop

Public bug reported:

If I use lightdm to load GNOME Shell, I encounter a very weird bug: if I
move the cursor to hover the desktop, the cursor theme becomes DMZ
White, but if I move the cursor over the GNOME panel or over any open
window, it returns back to the custom theme set by me.

I can experience this bug only when using lightdm, if I use gdm3 I
always have the same cursor.

Note that I'm not on Wayland and that I have nautilus folders on my
desktop.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-53-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jun  6 02:14:12 2017
InstallationDate: Installed on 2016-09-09 (269 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages xenial

** Summary changed:

- cursor does not following the theme while hovering the desktop
+ cursor not following the theme while hovering the desktop

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

Title:
  cursor not following the theme while hovering the desktop

Status in lightdm package in Ubuntu:
  New

Bug description:
  If I use lightdm to load GNOME Shell, I encounter a very weird bug: if
  I move the cursor to hover the desktop, the cursor theme becomes DMZ
  White, but if I move the cursor over the GNOME panel or over any open
  window, it returns back to the custom theme set by me.

  I can experience this bug only when using lightdm, if I use gdm3 I
  always have the same cursor.

  Note that I'm not on Wayland and that I have nautilus folders on my
  desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jun  6 02:14:12 2017
  InstallationDate: Installed on 2016-09-09 (269 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1696019/+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 1695876] Re: German Documentation file displays incorrect CUPS version

2017-06-05 Thread Till Kamppeter

Reported upstream as

https://github.com/apple/cups/issues/5019

** Bug watch added: github.com/apple/cups/issues #5019
   https://github.com/apple/cups/issues/5019

** Also affects: cups via
   https://github.com/apple/cups/issues/5019
   Importance: Unknown
   Status: Unknown

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

Title:
  German Documentation file displays incorrect CUPS version

Status in CUPS:
  Unknown
Status in cups package in Ubuntu:
  New

Bug description:
  The /doc/de/index.html.in file in the package source has an incorrect
  version number written into a header instead of using '@CUPS_VERSION@'
  to populate this file as in the other languages' version of the same
  file, seemingly resulting in /usr/share/cups/doc-root/de/index.html
  having the wrong version once CUPS is installed:

  ...
  

  CUPS 2.0.2
  ...

  instead of:

  ...
  

  CUPS @CUPS_VERSION@
  ...

  resulting in 'CUPS 2.0.2' instead of 2.1.3 being shown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1695876/+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 1681870] Re: indicator-datetime-service crashed with SIGABRT in __malloc_assert()

** Branch linked: lp:~ci-train-bot/indicator-datetime/indicator-
datetime-ubuntu-artful-2797

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1681870

Title:
  indicator-datetime-service crashed with SIGABRT in __malloc_assert()

Status in content-hub package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Fix Released
Status in keeper package in Ubuntu:
  Confirmed
Status in libertine-scope package in Ubuntu:
  Fix Released
Status in pay-service package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in ubuntu-app-launch package in Ubuntu:
  Fix Released
Status in ubuntu-push package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in unity-scope-click package in Ubuntu:
  Won't Fix
Status in unity8 package in Ubuntu:
  Fix Released
Status in url-dispatcher package in Ubuntu:
  Fix Released

Bug description:
  Install I386 version of desktop or run live desktop and the indicator
  is crashed.

  Added other packages that could have been affected as the crash is due
  to some ABI break in ubuntu-app-launch.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 11 15:41:03 2017
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-04-11 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170411)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/davmor2
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0xb6d27f38 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0xb6d24696 "malloc.c", line=line@entry=2403, 
function=) at malloc.c:301
   sysmalloc (nb=nb@entry=264, av=av@entry=0xb6d7a780 ) at 
malloc.c:2400
   _int_malloc (av=av@entry=0xb6d7a780 , bytes=bytes@entry=260) at 
malloc.c:3862
   __GI___libc_malloc (bytes=260) at malloc.c:2925
   operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
  Title: indicator-datetime-service crashed with SIGABRT in __malloc_assert()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1681870/+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 1681597] Re: DNS broken after >50m of uptime

2017-06-05 Thread pbhj

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

This issue just came up for me on Kubuntu 17.04, using systemd
232-21ubuntu3.

I had upgraded some packages with apt, but none are related to systemd:
there's samba, Firefox, apport, kio ... nothing that should really be
touching system resolver settings AFAICT.

Re-modprobing the ath9k_htc module, restarting systemd-resolved.service,
reconnecting network through the system tray icon ... all bring back the
network very briefly.

It looks from tail-ing syslog to almost be a race condition between two
DNS systems??

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

Title:
  DNS broken after >50m of uptime

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After about 50m of uptime news.ycombinator.com stops working in Chromium: 
news.ycombinator.com’s server's DNS address could not be found. 
DNS_PROBE_FINISHED_NXDOMAIN
  $ host news.ycombinator.com
  Host news.ycombinator.com not found: 2(SERVFAIL)

  This is a *regression* from Ubuntu 16.10, where DNS worked flawlessly.

  Workarounds:
   * 'systemctl restart systemd-resolved' solves the problem for another 50m
   * disable systemd-resolved and use the DNS server directly. This involves 
removing 'resolve [!UNAVAIL=return]' from nsswitch.conf, and disabling the 
systemd-resolved unit

  Logs show DNSSEC related errors, and DNSSEC getting disabled and reenabled:
  -- Logs begin at Mon 2017-04-10 23:10:59 BST, end at Tue 2017-04-11 00:11:14 
BST. --
  Apr 10 23:11:01 bolt systemd[1]: Starting Network Name Resolution...
  Apr 10 23:11:01 bolt systemd-resolved[1351]: Positive Trust Anchors:
  Apr 10 23:11:01 bolt systemd-resolved[1351]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
  Apr 10 23:11:01 bolt systemd-resolved[1351]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Apr 10 23:11:01 bolt systemd-resolved[1351]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 
19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 
23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 
27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 
31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal 
intranet lan local private test
  Apr 10 23:11:01 bolt systemd-resolved[1351]: Using system hostname 'bolt'.
  Apr 10 23:11:01 bolt systemd[1]: Started Network Name Resolution.
  Apr 10 23:11:05 bolt systemd-resolved[1351]: Switching to DNS server 
194.168.4.100 for interface wlp3s0.
  Apr 10 23:11:06 bolt systemd-resolved[1351]: Using degraded feature set 
(UDP+EDNS0) for DNS server 194.168.4.100.
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question com IN SOA: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question ubuntu.com IN DS: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question ubuntu.com IN SOA: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question daisy.ubuntu.com IN DS: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question daisy.ubuntu.com IN SOA: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question daisy.ubuntu.com IN A: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: Server 194.168.4.100 does not 
support DNSSEC, downgrading to non-DNSSEC mode.
  Apr 10 23:11:06 bolt systemd-resolved[1351]: Switching to DNS server 
194.168.8.100 for interface wlp3s0.
  Apr 10 23:11:07 bolt systemd-resolved[1351]: Using degraded feature set 
(UDP+EDNS0) for DNS server 194.168.8.100.
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question net IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question clamav.net IN DS: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question clamav.net IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question cvd.clamav.net IN DS: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question cvd.clamav.net IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question current.cvd.clamav.net IN DS: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question current.cvd.clamav.net IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question

[Touch-packages] [Bug 1681597] Re: DNS broken after >50m of uptime

2017-06-05 Thread pbhj

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

Should have said DNSSEC is already off, have made the change in the
systemd/resolved.conf file anyway, but no help for me.

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

Title:
  DNS broken after >50m of uptime

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After about 50m of uptime news.ycombinator.com stops working in Chromium: 
news.ycombinator.com’s server's DNS address could not be found. 
DNS_PROBE_FINISHED_NXDOMAIN
  $ host news.ycombinator.com
  Host news.ycombinator.com not found: 2(SERVFAIL)

  This is a *regression* from Ubuntu 16.10, where DNS worked flawlessly.

  Workarounds:
   * 'systemctl restart systemd-resolved' solves the problem for another 50m
   * disable systemd-resolved and use the DNS server directly. This involves 
removing 'resolve [!UNAVAIL=return]' from nsswitch.conf, and disabling the 
systemd-resolved unit

  Logs show DNSSEC related errors, and DNSSEC getting disabled and reenabled:
  -- Logs begin at Mon 2017-04-10 23:10:59 BST, end at Tue 2017-04-11 00:11:14 
BST. --
  Apr 10 23:11:01 bolt systemd[1]: Starting Network Name Resolution...
  Apr 10 23:11:01 bolt systemd-resolved[1351]: Positive Trust Anchors:
  Apr 10 23:11:01 bolt systemd-resolved[1351]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
  Apr 10 23:11:01 bolt systemd-resolved[1351]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Apr 10 23:11:01 bolt systemd-resolved[1351]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 
19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 
23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 
27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 
31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal 
intranet lan local private test
  Apr 10 23:11:01 bolt systemd-resolved[1351]: Using system hostname 'bolt'.
  Apr 10 23:11:01 bolt systemd[1]: Started Network Name Resolution.
  Apr 10 23:11:05 bolt systemd-resolved[1351]: Switching to DNS server 
194.168.4.100 for interface wlp3s0.
  Apr 10 23:11:06 bolt systemd-resolved[1351]: Using degraded feature set 
(UDP+EDNS0) for DNS server 194.168.4.100.
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question com IN SOA: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question ubuntu.com IN DS: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question ubuntu.com IN SOA: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question daisy.ubuntu.com IN DS: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question daisy.ubuntu.com IN SOA: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question daisy.ubuntu.com IN A: failed-auxiliary
  Apr 10 23:11:06 bolt systemd-resolved[1351]: Server 194.168.4.100 does not 
support DNSSEC, downgrading to non-DNSSEC mode.
  Apr 10 23:11:06 bolt systemd-resolved[1351]: Switching to DNS server 
194.168.8.100 for interface wlp3s0.
  Apr 10 23:11:07 bolt systemd-resolved[1351]: Using degraded feature set 
(UDP+EDNS0) for DNS server 194.168.8.100.
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question net IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question clamav.net IN DS: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question clamav.net IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question cvd.clamav.net IN DS: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question cvd.clamav.net IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question current.cvd.clamav.net IN DS: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question current.cvd.clamav.net IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question current.cvd.clamav.net IN TXT: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: Server 194.168.8.100 does not 
support DNSSEC, downgrading to non-DNSSEC mode.
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question daisy.ubuntu.com IN SOA: failed-auxiliary
  Apr 10 23:11:07 bolt systemd-resolved[1351]: DNSSEC validation failed for 
question daisy.ubuntu.com IN

[Touch-packages] [Bug 1645636] Re: deadlock during lvm snapshot

2017-06-05 Thread Wolfgang Hennerbichler

Same here. Snapshot of "a random VM" that ran on the machine.

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

Title:
  deadlock during lvm snapshot

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I'm doing backup of a running mongodb using LVM snapshot. Sometimes I
  run into a deadlock situation and kernel reports blocked tasks for jbd2,
  mongod, dmeventd and my tar doing backup.

  This happens very rarely (one in a thousand) but the effect is rather
  severe as mongodb stops working. I also can't remove and unmount the
  snapshot.

  I have Ubuntu 16.04.1 (lvm2 2.02.133-1ubuntu10) with mongod 3.2.9 on a
  64bit system.

  According to the link below its a kernel race with considerably
  decreased chance in latest lvm2 package.

  https://www.redhat.com/archives/linux-lvm/2016-November/msg00037.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1645636/+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 1687354] Re: package python-crypto 2.6.1-6ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

** Changed in: python-crypto (Ubuntu)
   Status: New => Confirmed

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

Title:
  package python-crypto 2.6.1-6ubuntu0.16.04.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in python-crypto package in Ubuntu:
  Confirmed

Bug description:
  Please fix this issue as soon as possible...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-crypto 2.6.1-6ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon May  1 00:07:48 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-04-18 (13 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: python-crypto
  Title: package python-crypto 2.6.1-6ubuntu0.16.04.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1687354/+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 1695987] [NEW] "Unknown option: proto udp6" error on openvpn import in KDE network manager

2017-06-05 Thread linex83

Public bug reported:

I created an openvpn config file, which I could successfully run on
command line. However, as I tried importing the file with the KDE
network manager, I got the following error message:

"Unknown option: proto udp6"

Since the openvpn command could process the config file without
problems, I think the network manager should be able to do that, too.

Here's my openvpn client config file:
client
dev tun
proto udp6
remote ::...:ccc 7002
resolv-retry infinite
nobind
persist-key
persist-tun
ca ca.crt
cert my.crt
key my.key
remote-cert-tls server
tls-auth ta.key 1
cipher AES-256-CBC
auth SHA512
comp-lzo
verb 3
key-direction 1

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Jun  5 22:08:08 2017
InstallationDate: Installed on 2017-06-04 (0 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu zesty

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

Title:
  "Unknown option: proto udp6" error on openvpn import in KDE network
  manager

Status in xorg package in Ubuntu:
  New

Bug description:
  I created an openvpn config file, which I could successfully run on
  command line. However, as I tried importing the file with the KDE
  network manager, I got the following error message:

  "Unknown option: proto udp6"

  Since the openvpn command could process the config file without
  problems, I think the network manager should be able to do that, too.

  Here's my openvpn client config file:
  client
  dev tun
  proto udp6
  remote ::...:ccc 7002
  resolv-retry infinite
  nobind
  persist-key
  persist-tun
  ca ca.crt
  cert my.crt
  key my.key
  remote-cert-tls server
  tls-auth ta.key 1
  cipher AES-256-CBC
  auth SHA512
  comp-lzo
  verb 3
  key-direction 1

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jun  5 22:08:08 2017
  InstallationDate: Installed on 2017-06-04 (0 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1695987/+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 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)

2017-06-05 Thread Chris

I found the bug described and confirmed on redhat, where I also found the 
solution. (although they have the goa-demon in the /usr/libexec/ folder)
https://bugzilla.redhat.com/show_bug.cgi?id=1340203

As a work-around, for each user account I created a new file in
~/.config/autostart/ called goa-replace.desktop, and in a text-editor
entered the following:

[Desktop Entry]
Name=GOA Replace
Exec=/usr/lib/gnome-online-accounts/goa-daemon --replace
NoDisplay=true
Terminal=false
Type=Application

The problem seems to be that dbus is spawning goa-daemon, but then not
killing the process when the user logs out. gnome-keyring IS killed, and
this breaks the link between the two.

Not sure what the *real* solution is, seems to be a big debate about how
systemd leaves 'lingering' processes from users after log out. I see 28
processes left running after a user logs out. Surely this needs to be
cleaned up??? Is there a better way to force systemd to properly close a
users session?

** Bug watch added: Red Hat Bugzilla #1340203
   https://bugzilla.redhat.com/show_bug.cgi?id=1340203

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

Title:
  GNOME Online Accounts breaks if you log out (until you reboot)

Status in gnome-online-accounts:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Can't add any online accounts in after opened Online accounts + mark is 
faded, can't click.
  After reinstalled gnome-online-accounts still has same problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-online-accounts 3.20.3-1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Mon Aug  8 15:33:45 2016
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+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 1695983] [NEW] Removing an imported openvpn connection doesn't clean up copied certificates

2017-06-05 Thread linex83

Public bug reported:

I imported an openvpn connection with the KDE network manager, which
worked fine. On import I was asked whether I want my certificates to be
copied to .local/share/networkmanagement, which I confirmed. Them I
removed my connection and reimported it again, this time receiving the
following error message:

"Error copying certificate to
/home/user/.local/share/networkmanagement/certificates/myopenvpn.key:
Destination file exists"

Seems like copied certificates aren't cleaned up when an openvpn
connection is removed.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Jun  5 21:56:31 2017
InstallationDate: Installed on 2017-06-04 (0 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kubuntu zesty

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

Title:
  Removing an imported openvpn connection doesn't clean up copied
  certificates

Status in xorg package in Ubuntu:
  New

Bug description:
  I imported an openvpn connection with the KDE network manager, which
  worked fine. On import I was asked whether I want my certificates to
  be copied to .local/share/networkmanagement, which I confirmed. Them I
  removed my connection and reimported it again, this time receiving the
  following error message:

  "Error copying certificate to
  /home/user/.local/share/networkmanagement/certificates/myopenvpn.key:
  Destination file exists"

  Seems like copied certificates aren't cleaned up when an openvpn
  connection is removed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jun  5 21:56:31 2017
  InstallationDate: Installed on 2017-06-04 (0 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1695983/+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 1695980] Re: package python-problem-report 2.20.1-0ubuntu2.6 failed to install/upgrade: subprocess new pre-removal script returned error exit status 139

** Tags removed: need-duplicate-check

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

Title:
  package python-problem-report 2.20.1-0ubuntu2.6 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 139

Status in apport package in Ubuntu:
  New

Bug description:
  # Hi !

  # After an update + upgrade, compiz reported segmentation fault at X session 
starting.
  # By the way ! I had to clean my memory because it was very dirty. this event 
followed a DIII game session that has crashed. I was playing in an other 
computer link to this one. I wanted to update my system.

  
  sudo lspci -nn | grep VGA
  -- STDOUT
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806]
  -- !STDOUT

  less /var/log/syslog
  -- FILE
  [...]
  un  5 20:27:44 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
Error loading theme icon 'image-missing' for stock: Unrecognized image file 
format
  Jun  5 20:27:44 prd gnome-session[18141]: (nautilus:18410): 
GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
  Jun  5 20:27:44 prd gnome-session[18141]: (nautilus:18410): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed
  Jun  5 20:27:45 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
Error loading image 
'file:///usr/share/themes/Ambiance/gtk-3.0/assets/backdrop-entry.png': 
Unrecognized image file format
  Jun  5 20:27:45 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
Error loading image 
'file:///usr/share/themes/Ambiance/gtk-3.0/assets/backdrop-button-active.png': 
Unrecognized image file forma
  t
  Jun  5 20:27:45 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
Error loading image 
'file:///usr/share/themes/Ambiance/gtk-3.0/assets/backdrop-button.png': 
Unrecognized image file format
  Jun  5 20:27:45 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
Error loading image 
'file:///usr/share/themes/Ambiance/gtk-3.0/assets/backdrop-button-toolbar.png': 
Unrecognized image file form
  at
  Jun  5 20:27:45 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
Error loading image 
'file:///usr/share/themes/Ambiance/gtk-3.0/assets/backdrop-button-toolbar-active.png':
 Unrecognized image file format
  Jun  5 20:27:48 prd kernel: [30935.779767] compiz[18540]: segfault at e0 ip 
7f09307dd263 sp 7ffebf670ef0 error 4 in 
libnux-graphics-4.0.so.0.8.0[7f093079+cf000]
  Jun  5 20:27:49 prd bluetoothd[797]: Endpoint unregistered: sender=:1.728 
path=/MediaEndpoint/A2DPSource
  Jun  5 20:27:49 prd bluetoothd[797]: Endpoint unregistered: sender=:1.728 
path=/MediaEndpoint/A2DPSink
  Jun  5 20:27:51 prd kernel: [30938.927532] compiz[18586]: segfault at e0 ip 
7f3c109f5263 sp 7ffea6f6ab50 error 4 in 
libnux-graphics-4.0.so.0.8.0[7f3c109a8000+cf000]
  Jun  5 20:27:54 prd kernel: [30942.070271] compiz[18605]: segfault at e0 ip 
7f603cc09263 sp 7ffe88d14780 error 4 in 
libnux-graphics-4.0.so.0.8.0[7f603cbbc000+cf000]
  Jun  5 20:27:57 prd kernel: [30945.302393] compiz[18624]: segfault at e0 ip 
7fc66aed1263 sp 7ffdde618c40 error 4 in 
libnux-graphics-4.0.so.0.8.0[7fc66ae84000+cf000]
  Jun  5 20:27:57 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
Error loading image 
'file:///usr/share/themes/Ambiance/gtk-3.0/assets/check-menuitem.png': 
Unrecognized image file format
  Jun  5 20:27:57 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
drawing failure for widget 'GtkCheckMenuItem': invalid matrix (not invertible)
  Jun  5 20:27:57 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
drawing failure for widget 'GtkMenu': invalid matrix (not invertible)
  [...]
  -- !FILE

  # I made rezet of compiz (not sure it was efficient but my screen has stoped 
to blink) :
  sudo dconf reset -f /org/compiz/; setsid unity

  # I had to reinstall shared-mime-info package
  sudo apt-get install --reinstall shared-mime-info

  # I reinstalled compiz too, but I am not sure it was necessary.
  sudo apt-get install --reinstall compiz

  # Now I will try to restart and pray that I will recorver my X
  session.

  # Wish you a good day :-)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-problem-report 2.20.1-0ubuntu2.6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sun Jun  4 17:49:36 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 139
  InstallationDate: Installed on 2012-07-28 (1772

[Touch-packages] [Bug 1695980] [NEW] package python-problem-report 2.20.1-0ubuntu2.6 failed to install/upgrade: subprocess new pre-removal script returned error exit status 139

2017-06-05 Thread NICAISE

Public bug reported:

# Hi !

# After an update + upgrade, compiz reported segmentation fault at X session 
starting.
# By the way ! I had to clean my memory because it was very dirty. this event 
followed a DIII game session that has crashed. I was playing in an other 
computer link to this one. I wanted to update my system.


sudo lspci -nn | grep VGA
-- STDOUT
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806]
-- !STDOUT

less /var/log/syslog
-- FILE
[...]
un  5 20:27:44 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
Error loading theme icon 'image-missing' for stock: Unrecognized image file 
format
Jun  5 20:27:44 prd gnome-session[18141]: (nautilus:18410): 
GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
Jun  5 20:27:44 prd gnome-session[18141]: (nautilus:18410): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed
Jun  5 20:27:45 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
Error loading image 
'file:///usr/share/themes/Ambiance/gtk-3.0/assets/backdrop-entry.png': 
Unrecognized image file format
Jun  5 20:27:45 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
Error loading image 
'file:///usr/share/themes/Ambiance/gtk-3.0/assets/backdrop-button-active.png': 
Unrecognized image file forma
t
Jun  5 20:27:45 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
Error loading image 
'file:///usr/share/themes/Ambiance/gtk-3.0/assets/backdrop-button.png': 
Unrecognized image file format
Jun  5 20:27:45 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
Error loading image 
'file:///usr/share/themes/Ambiance/gtk-3.0/assets/backdrop-button-toolbar.png': 
Unrecognized image file form
at
Jun  5 20:27:45 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
Error loading image 
'file:///usr/share/themes/Ambiance/gtk-3.0/assets/backdrop-button-toolbar-active.png':
 Unrecognized image file format
Jun  5 20:27:48 prd kernel: [30935.779767] compiz[18540]: segfault at e0 ip 
7f09307dd263 sp 7ffebf670ef0 error 4 in 
libnux-graphics-4.0.so.0.8.0[7f093079+cf000]
Jun  5 20:27:49 prd bluetoothd[797]: Endpoint unregistered: sender=:1.728 
path=/MediaEndpoint/A2DPSource
Jun  5 20:27:49 prd bluetoothd[797]: Endpoint unregistered: sender=:1.728 
path=/MediaEndpoint/A2DPSink
Jun  5 20:27:51 prd kernel: [30938.927532] compiz[18586]: segfault at e0 ip 
7f3c109f5263 sp 7ffea6f6ab50 error 4 in 
libnux-graphics-4.0.so.0.8.0[7f3c109a8000+cf000]
Jun  5 20:27:54 prd kernel: [30942.070271] compiz[18605]: segfault at e0 ip 
7f603cc09263 sp 7ffe88d14780 error 4 in 
libnux-graphics-4.0.so.0.8.0[7f603cbbc000+cf000]
Jun  5 20:27:57 prd kernel: [30945.302393] compiz[18624]: segfault at e0 ip 
7fc66aed1263 sp 7ffdde618c40 error 4 in 
libnux-graphics-4.0.so.0.8.0[7fc66ae84000+cf000]
Jun  5 20:27:57 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
Error loading image 
'file:///usr/share/themes/Ambiance/gtk-3.0/assets/check-menuitem.png': 
Unrecognized image file format
Jun  5 20:27:57 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
drawing failure for widget 'GtkCheckMenuItem': invalid matrix (not invertible)
Jun  5 20:27:57 prd gnome-session[18141]: (nautilus:18410): Gtk-WARNING **: 
drawing failure for widget 'GtkMenu': invalid matrix (not invertible)
[...]
-- !FILE

# I made rezet of compiz (not sure it was efficient but my screen has stoped to 
blink) :
sudo dconf reset -f /org/compiz/; setsid unity

# I had to reinstall shared-mime-info package
sudo apt-get install --reinstall shared-mime-info

# I reinstalled compiz too, but I am not sure it was necessary.
sudo apt-get install --reinstall compiz

# Now I will try to restart and pray that I will recorver my X session.

# Wish you a good day :-)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-problem-report 2.20.1-0ubuntu2.6
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Sun Jun  4 17:49:36 2017
ErrorMessage: subprocess new pre-removal script returned error exit status 139
InstallationDate: Installed on 2012-07-28 (1772 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: apport
Title: package python-problem-report 2.20.1-0ubuntu2.6 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 
139
UpgradeStatus: Upgraded to xenial on 2017-05-11 (25 days ago)

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


** Tags: amd64

[Touch-packages] [Bug 1695971] Re: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 failed to install/upgrade: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 cannot be configured because l

** Tags removed: need-duplicate-check

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

Title:
  package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 failed to
  install/upgrade: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1
  cannot be configured because libgl1-mesa-glx:i386 is at a different
  version (13.1~git1701031930.c4b87f~gd~x)

Status in mesa package in Ubuntu:
  New

Bug description:
  I tried to install Qt5 by
  ```
  $ sudo apt-get install qt5-default
  ```
  what gave me a `you have held broken packages' error`-message so I tried
  ```
  $ sudo aptitude install qt5-default
  ```
  what proposed some solutions. I think, the chosen solution downgraded the 
given package in the summary.

  Additional information:
  ```
  $ lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  
  $ apt-cache policy libgl1-mesa-glx:amd64
  libgl1-mesa-glx:
Installed: 12.0.6-0ubuntu0.16.10.1
Candidate: 12.0.6-0ubuntu0.16.10.1
Version table:
   *** 12.0.6-0ubuntu0.16.10.1 500
  500 http://de.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   12.0.3-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages

  
  $ apt-cache policy libgl1-mesa-glx:i386
  libgl1-mesa-glx:i386:
Installed: (none)
Candidate: 12.0.6-0ubuntu0.16.10.1
Version table:
   12.0.6-0ubuntu0.16.10.1 500
  500 http://de.archive.ubuntu.com/ubuntu yakkety-updates/main i386 
Packages
   12.0.3-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu yakkety/main i386 Packages
  ```

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jun  5 20:33:05 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   vhba, 20161009, 4.8.0-49-generic, x86_64: installed
   vhba, 20161009, 4.8.0-52-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-49-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-52-generic, x86_64: installed
  DuplicateSignature:
   package:libgl1-mesa-glx:amd64:12.0.6-0ubuntu0.16.10.1
   Processing triggers for desktop-file-utils (0.23-1ubuntu1.1) ...
   dpkg: error processing package libglapi-mesa:amd64 (--configure):
package libglapi-mesa:amd64 12.0.6-0ubuntu0.16.10.1 cannot be configured 
because libglapi-mesa:i386 is at a different version 
(13.1~git1701031930.c4b87f~gd~x)
  ErrorMessage: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 cannot be 
configured because libgl1-mesa-glx:i386 is at a different version 
(13.1~git1701031930.c4b87f~gd~x)
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:7007]
  InstallationDate: Installed on 2016-06-04 (366 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 2740p
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic 
root=UUID=45931ea1-c5bd-4b7e-ae5d-28d50c0d8e97 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: mesa
  Title: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 failed to 
install/upgrade: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 cannot 
be configured because libgl1-mesa-glx:i386 is at a different version 
(13.1~git1701031930.c4b87f~gd~x)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68COU Ver. F.04
  dmi.board.name: 7007
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 39.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68COUVer.F.04:bd03/08/2011:svnHewlett-Packard:pnHPEliteBook2740p:pvr:rvnHewlett-Packard:rn7007:rvrKBCVersion39.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 2740p
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2

[Touch-packages] [Bug 1695971] [NEW] package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 failed to install/upgrade: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 cannot be configured because

2017-06-05 Thread Michael Banucu

Public bug reported:

I tried to install Qt5 by
```
$ sudo apt-get install qt5-default
```
what gave me a `you have held broken packages' error`-message so I tried
```
$ sudo aptitude install qt5-default
```
what proposed some solutions. I think, the chosen solution downgraded the given 
package in the summary.

Additional information:
```
$ lsb_release -rd
Description:Ubuntu 16.10
Release:16.10


$ apt-cache policy libgl1-mesa-glx:amd64
libgl1-mesa-glx:
  Installed: 12.0.6-0ubuntu0.16.10.1
  Candidate: 12.0.6-0ubuntu0.16.10.1
  Version table:
 *** 12.0.6-0ubuntu0.16.10.1 500
500 http://de.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 12.0.3-1ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages


$ apt-cache policy libgl1-mesa-glx:i386
libgl1-mesa-glx:i386:
  Installed: (none)
  Candidate: 12.0.6-0ubuntu0.16.10.1
  Version table:
 12.0.6-0ubuntu0.16.10.1 500
500 http://de.archive.ubuntu.com/ubuntu yakkety-updates/main i386 
Packages
 12.0.3-1ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu yakkety/main i386 Packages
```

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Jun  5 20:33:05 2017
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 vhba, 20161009, 4.8.0-49-generic, x86_64: installed
 vhba, 20161009, 4.8.0-52-generic, x86_64: installed
 virtualbox, 5.1.6, 4.8.0-49-generic, x86_64: installed
 virtualbox, 5.1.6, 4.8.0-52-generic, x86_64: installed
DuplicateSignature:
 package:libgl1-mesa-glx:amd64:12.0.6-0ubuntu0.16.10.1
 Processing triggers for desktop-file-utils (0.23-1ubuntu1.1) ...
 dpkg: error processing package libglapi-mesa:amd64 (--configure):
  package libglapi-mesa:amd64 12.0.6-0ubuntu0.16.10.1 cannot be configured 
because libglapi-mesa:i386 is at a different version 
(13.1~git1701031930.c4b87f~gd~x)
ErrorMessage: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 cannot be 
configured because libgl1-mesa-glx:i386 is at a different version 
(13.1~git1701031930.c4b87f~gd~x)
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:7007]
InstallationDate: Installed on 2016-06-04 (366 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard HP EliteBook 2740p
PccardctlStatus:
 Socket 0:
   3.3V
  16-bit
  PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic 
root=UUID=45931ea1-c5bd-4b7e-ae5d-28d50c0d8e97 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.4
SourcePackage: mesa
Title: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 failed to 
install/upgrade: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 cannot 
be configured because libgl1-mesa-glx:i386 is at a different version 
(13.1~git1701031930.c4b87f~gd~x)
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/08/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68COU Ver. F.04
dmi.board.name: 7007
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 39.36
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68COUVer.F.04:bd03/08/2011:svnHewlett-Packard:pnHPEliteBook2740p:pvr:rvnHewlett-Packard:rn7007:rvrKBCVersion39.36:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 2740p
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.74+git1612241830.eebefa~gd~x
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.8.99+git1612191933.720dd0~gd~x
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1701040733.028c94~gd~x
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.13+git1610280732.1516d3~gd~x
xserver.bootTime: Mon Jun  5 20:51:28 2017
xserver.configfile:

[Touch-packages] [Bug 1695948] [NEW] Nothing

2017-06-05 Thread Severin Scheuerer

Public bug reported:

Nothing

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Jun  5 20:05:15 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:81d2]
InstallationDate: Installed on 2017-06-04 (1 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ENVY Notebook
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-54-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81D2
dmi.board.vendor: HP
dmi.board.version: KBC Version 87.13
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd07/08/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.13:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug 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/1695948

Title:
  Nothing

Status in xorg package in Ubuntu:
  New

Bug description:
  Nothing

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jun  5 20:05:15 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:81d2]
  InstallationDate: Installed on 2017-06-04 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-54-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81D2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 87.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd07/08/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core:

[Touch-packages] [Bug 1695928] Re: Please remove obsolete UOA packages

** Description changed:

  Ubuntu Online Accounts is no longer maintained. There is an alternative,
  GNOME Online Accounts for the GNOME desktop.
  
  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.
  
  Please remove these source packages and their binaries:
  -
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qt-purchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-scope-gdrive
  
+ 
+ ubuntu-system-settings-online-accounts
+ online-accounts-api
+ storage-framework
+ keeper
+ mcloud
+ Note: ubuntu-system-settings recommends u-s-s-online-accounts. My 
understanding is that we'll be dropping unity8 from Ubuntu 17.10 so I'm not 
sure it's worthwhile to drop that recommends.
+ 
  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802
  
  Kubuntu still uses signon-ui

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

Title:
  Please remove obsolete UOA packages

Status in gnome-control-center-signon package in Ubuntu:
  New

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  -
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qt-purchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-scope-gdrive

  
  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper
  mcloud
  Note: ubuntu-system-settings recommends u-s-s-online-accounts. My 
understanding is that we'll be dropping unity8 from Ubuntu 17.10 so I'm not 
sure it's worthwhile to drop that recommends.

  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

  Kubuntu still uses signon-ui

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1695928/+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 1695884] Re: usb probing malforms Epson TM-T70 label printer output

2017-06-05 Thread Till Kamppeter

As the backends do not filter data but simply pass the data through it
is not clear whether the "usb" CUPS backend really causes the problem.
Especially in this case the CUPS backend still lets go data to the
printer and the printer prints something.

So before modifying the backend behavior I would like to know what kind
of data you feed to the printer and what does CUPS exactly do.

Did you create a CUPS queue with a driver/PPD file? Which driver or PPD
file (please attach your print queue's PPD file from /etc/cups/ppd/)? Or
did you create a raw (unfiltered) queue? How do you send jobs to CUPS?
Do you simply send them or do you use the "-o raw" option (unfiltered
by-job)? Are you sending jobs as plain text or as PDF, PostScript, ...?

If you add the quirk rule to blacklist your printer the "usb" CUPS
backend would ignore the printer preventing the backend to discover the
printer. How are you using the printer then? Another CUPS backend? Which
one? No use of CUPS at all (like "cat file > /dev/usb/lp0")? Are you
using a driver/filter then?

Please also follow the instructions of the sections "CUPS error_log",
"USB printer", "Capturing print job data", and "Getting the data which
would go to the printer" for the case when you are using the "usb" CUPS
backend without changes in the quirk rules and also when using CUPS with
the change. also run

sudo lsusb -vvv > lsusb-out.txt

and attach the resulting file.

Please do not compress any of the files you get and do not package them
together. Attach them to this bug report one by one.

** Changed in: cups (Ubuntu)
   Status: New => Incomplete

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

Title:
  usb probing malforms Epson TM-T70 label printer output

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  CUPS USB probing malforms Epson TM-T70 (vendorid: 0x04b8 productid:
  0x0202) which is used outside CUPS (via usblp driver).

  No matter whether the printer is set up as a CUPS raw printer or it's
  not used via CUPS (but rather via a device node under usblp control)
  the formatting is broken on the printed out labels: the orientation is
  different from what had been set, the fonts differ.

  After blacklisting the printer in the quirks file all the problems
  were gone.

  My assumption is that this printer should be blacklisted by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1695884/+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 1695884] Re: usb probing malforms Epson TM-T70 label printer output

2017-06-05 Thread Ubuntu Foundations Team Bug Bot

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

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

** Tags added: patch

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

Title:
  usb probing malforms Epson TM-T70 label printer output

Status in cups package in Ubuntu:
  New

Bug description:
  CUPS USB probing malforms Epson TM-T70 (vendorid: 0x04b8 productid:
  0x0202) which is used outside CUPS (via usblp driver).

  No matter whether the printer is set up as a CUPS raw printer or it's
  not used via CUPS (but rather via a device node under usblp control)
  the formatting is broken on the printed out labels: the orientation is
  different from what had been set, the fonts differ.

  After blacklisting the printer in the quirks file all the problems
  were gone.

  My assumption is that this printer should be blacklisted by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1695884/+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 1695928] [NEW] Please remove obsolete UOA packages

Public bug reported:

Ubuntu Online Accounts is no longer maintained. There is an alternative,
GNOME Online Accounts for the GNOME desktop.

Also, Unity's Online Accounts settings panel does not currently work
without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

Please remove these source packages and their binaries:
-
gnome-control-center-signon
account-plugins
account-plugin-fitbit
account-polld
pay-service
qt-purchasing-opensource-src
storage-provider-webdav
sync-monitor
ubuntuone-credentials
ubuntu-push
unity-scope-gdrive

Other Notes
---
The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

Kubuntu still uses signon-ui

** Affects: gnome-control-center-signon (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Please remove obsolete UOA packages

Status in gnome-control-center-signon package in Ubuntu:
  New

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  -
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qt-purchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-scope-gdrive

  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

  Kubuntu still uses signon-ui

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1695928/+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 1155307] Re: zconf.h header file is missing for 32 bits arch

2017-06-05 Thread Luca Weiss

This issue is more than 4 years old... Thanks Ubuntu...

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

Title:
  zconf.h header file is missing for 32 bits arch

Status in zlib package in Ubuntu:
  Confirmed

Bug description:
  zconf.h  was moved to multiarch directory (zlib1g-dev package) because it 
contains an arch dependant declaration.
  Problem is programs using zlib doesn't compile anymore using 32bits  target 
arch. (zconf.h is not found)

  I suppose a 32 bits version of zconf.h should be added into
  lib32z1-dev package ?

  Description:  Ubuntu Raring Ringtail (development branch)
  Release:  13.04
  x86_64
  lib32z1-dev 1:1.2.7.dfsg-13ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: lib32z1-dev 1:1.2.7.dfsg-13ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
  Uname: Linux 3.8.0-12-generic x86_64
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  Date: Thu Mar 14 20:54:10 2013
  InstallationDate: Installed on 2013-02-21 (21 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130221)
  MarkForUpload: True
  ProcEnviron:
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: zlib
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1155307/+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 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-06-05 Thread Eric Desrochers

@Brian Murray,
@sil2100

To summarize :
- wgrant did his verifications which are all successful
- I did mine that are all still successful
- I also reviewed all the regression failures reported on the pending sru page 
and have provided an explanation for all of them above in the SRU justification 
template.

IMHO, Now I don't see any blockers for the SRU to complete, but I'll let
you guys (SRU) take the final decision.

Let us know if we can be of any help.

- Eric

** Description changed:

  [Impact]
  
  * Context:
  
  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit
  only (Confirmed with AMD representative). Current OpenSSL version in
  Ryzens still calls SHA for SSSE3 routine as result a number of
  extensions were effectively masked on Ryzen and shows no improvement.
  
  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family : 23
  model : 1
  model name : AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 
constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni 
pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
  
  [2] - sha_ni: SHA1/SHA256 Instruction Extensions
  
  [3] - https://en.wikipedia.org/wiki/Ryzen
  ...
  All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
  ...
  
  * Program to performs the CPUID check:
  
  Reference :
  https://software.intel.com/en-us/articles/intel-sha-extensions
  
  ... Availability of the Intel® SHA Extensions on a particular processor
  can be determined by checking the SHA CPUID bit in CPUID.(EAX=07H,
  ECX=0):EBX.SHA [bit 29]. The following C function, using inline
  assembly, performs the CPUID check:
  
  --
  int CheckForIntelShaExtensions() {
     int a, b, c, d;
  
     // Look for CPUID.7.0.EBX[29]
     // EAX = 7, ECX = 0
     a = 7;
     c = 0;
  
     asm volatile ("cpuid"
  :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
  :"a"(a), "c"(c)
     );
  
     // Intel® SHA Extensions feature bit is EBX[29]
     return ((b >> 29) & 1);
  }
  --
  
  On CPU with sha_ni the program return "1". Otherwise it return "0".
  
  [Test Case]
  
   * Reproducible with Xenial/Zesty/Artful release.
  
   * Generated a checksum of a big file (e.g. 5GB file) with openssl
   $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
  SHA256(/var/tmp/5Gfile)= 
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8
  
  real  0m12.835s
  user  0m12.344s
  sys   0m0.484s
  
  * Openssl speed
  $ openssl speed sha1
  Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
  Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
  Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
  Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s
  Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s
  OpenSSL 1.0.2g 1 Mar 2016
  built on: reproducible build, date unspecified
  options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) 
blowfish(idx)
  compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT 
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall 
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM 
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
  The 'numbers' are in 1000s of bytes per second processed.
  type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
  sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55
  
  The performance are clearly better when using the patch which take
  benefit of the sha extension. (See Regression Potential section for
  result with patch)
  
  [Regression Potential]
  
   * Note : IRC discussion with infinity :
  
https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/comments/8
  
   * Note from irc discussion with apw and rbasak :
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/comments/2
  
   * It basically allow openssl to take benefit of sha extension potential
  (mostly performance-wise) now that new AMD cpu starting  to have the
  capability.
  
  * The code check the CPUID bit to determine if the sha instructions are
  available are not.
  
  * Maintainer comment proves that he did the successfully tested on Intel

[Touch-packages] [Bug 1693226] Re: Break the conflicts with click the optparser

2017-06-05 Thread Sergio Schvezov

I did some preemptive testing with ppa:ci-train-ppa-service/ubuntu/2790
(https://bileto.ubuntu.com/#/ticket/2790) which should land in artful:

root@artful:/# dpkg -l snapcraft
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  snapcraft  2.30.1+17.10 all  easily craft snaps
root@artful:/# dpkg -l click
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  click  0.4.46+17.10 amd64Click packages
root@artful:/# snapcraft --help
Usage: snapcraft [OPTIONS] COMMAND [ARGS]...

  Snapcraft is a delightful packaging tool.

Options:
  -d, --debug
  --help   Show this message and exit.

Commands:
  buildBuild artifacts defined for a part.
  cleanRemove content - cleans downloads, builds or...
  cleanbuild   Create a snap using a clean environment...
  closeClose  for .
  create-key   Create a key to sign assertions.
  define   Shows the definition for the cloud part.
  enable-ciEnable continuous-integration systems to...
  gatedGet the list of snaps and revisions gating a...
  help Obtain help for a certain plugin or topic.
  init Initialize a snapcraft project.
  list-keysList the keys available to sign assertions.
  list-plugins List the available plugins that handle...
  list-registered  List snap names registered or shared with...
  list-revisions   Get the history on the store for .
  loginAuthenticate session against Ubuntu One SSO.
  logout   Clear session credentials.
  primeFinal copy and preparation for the snap.
  pull Download or retrieve artifacts defined for a...
  push Push  to the store.
  register Register  with the store.
  register-key Register a key with the store to sign...
  release  Release  on  to the...
  search   Searches the remote parts cache for matching...
  sign-build   Sign a built snap file and assert it using...
  snap Create a snap.
  stageStage the part's built artifacts into the...
  status   Get the status on the store for .
  tour Setup the snapcraft examples used in the...
  update   Updates the parts listing from the cloud.
  validate Validate a gated snap.
root@artful:/# click --help
Usage: click COMMAND [options]

Commands are as follows ('click COMMAND --help' for more):

  build Build a Click package.
  buildsource   Build a Click source package.
  chrootUse and manage a Click chroot.
  contents  Show the file-list contents of a Click package file.
  framework List available frameworks.
  hook  Install or remove a Click system hook.
  info  Show manifest information for a Click package.
  install   Install a Click package (low-level; consider pkcon 
instead).
  list  List installed Click packages.
  pkgdirPrint the directory where a Click package is unpacked.
  register  Register an installed Click package for a user.
  unregisterUnregister an installed Click package for a user.
  verifyVerify a Click package.

Options:
  -h, --help  show this help message and exit


** Description changed:

- click the optparser cannot be installed in parallel with this package.
- Please break the conflict so they can be co-installable.
+ [Impact]
+ 
+  * python-click and python-click-package conflict as they use the same
+python package for its implementation.
+ 
+  * Since python-click-package is an implementation detail for the click 
+package and python3-click is a package meant to be used in other
+implementations it makes sense to break the conflict by moving the
+package name for python-click-package to a different name
+ 
+  * snapcraft has moved from docopt to python3-click, users that have click
+installed don't have an upgrade path.his bug.
+ 
+ [Test Case]
+ 
+  * Where snapcraft 2.30 is present:
+
+- apt install click
+- Install snapcraft << 2.30
+- update to snapcraft >= 2.30
+- the upgrade should not be held on any package.
+- click and snapcraft commands should work.
+ 
+ * Install python3-click and click should be possible. The click command
+   should keep working and python3 -c 'from click import group' shall work.
+ 
+ 
+ [Regression

[Touch-packages] [Bug 1655431] Re: apt-helper / update-notifier / ttf-mscorefonts-installer download failure (regression)

2017-06-05 Thread Jonathan Kamens

The bug of which this one was previously marked a duplicate (I unmarked
it) was fixed months ago, and yet I'm still getting this email from
cron.daily every single day:

>/etc/cron.daily/update-notifier-common:
>ttf-mscorefonts-installer: processing...

The problem at this point seems to have nothing whatsoever to do with
spaces in URLs or anything like that. Rather, the problem is that when
the package ttf-mscorefonts-installer is installed non-interactively,
the license is not accepted, and the downloader for the package silently
fails to download any fonts if the license hasn't been accepted.

Note this stanza at the end of /usr/share/package-data-downloads/ttf-
mscorefonts-installer:

>Script: /usr/lib/msttcorefonts/update-ms-fonts
>Should-Download: msttcorefonts/accepted-mscorefonts-eula

On my system, msttcorefonts/accepted-mscorefonts-eula is false, because
the package was installed non-interactively.

The code which silently refuses to download fonts if that setting is
false is in /usr/lib/update-notifier/package-data-downloader:

>if 'Should-Download' in para:
>db = debconf.DebconfCommunicator('update-notifier')
>try:
>should = db.get(para['Should-Download'])
>if should == "false":
># Do nothing with this file.   
>  
>break
>except:
>pass
>finally:
>db.shutdown()

Furthermore, maybe I'm missing something, but I can't find any supported
way of accepting this license once the package has been installed,
because the code that prompts the user to accept the license is in
/var/lib/dpkg/info/ttf-mscorefonts-installer.preinst, and as far as I
can tell, dpkg-reconfigure doesn't rerun preinst files.

** This bug is no longer a duplicate of bug 1651923
   apt https method decodes redirect locations and sends them to the 
destination undecoded.

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

Title:
  apt-helper / update-notifier / ttf-mscorefonts-installer download
  failure (regression)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  * OS release: Ubuntu 16.04.1 LTS
  * Package version: 3.168.3

  For the past few days (maybe even weeks for other users), update-
  notifier has been very repeatedly failing to handle the downloads for
  ttf-mscorefonts-installer. Previously it was working fine on the same
  system.

  This seems to affect a lot of desktop users, but the issue is usually
  misdiagnosed on forums because it is attributed to ttf-mscorefonts-
  installer and not to update-notifier-common.

  The issue is made particularly irritating because the update-notifier
  cron job tries and fails and notifies users daily of this failure.

  The issue can be reproduced by having ttf-mscorefonts-installer
  installed, and running:

  sudo dpkg-reconfigure update-notifier-common

  The error messages seem to be random but actually appear to be
  consistent for a given download source:

  * freefr.dl.sourceforge.net: 404  Not Found
  * kent.dl.sourceforge.net: Protocol "http" not supported or disabled in 
libcurl
  * netassist.dl.sourceforge.net: The HTTP server sent an invalid Content-Range 
header Bad header data [IP: 62.205.134.42 80]
  * netcologne.dl.sourceforge.net: The HTTP server sent an invalid 
Content-Range header
  * netix.dl.sourceforge.net: 404  Not Found
  * vorboss.dl.sourceforge.net: 404  Not Found

  In all above cases, the reported failing URL can be downloaded just
  fine using wget.

  Some other mirrors appear to work (unfortunately, mirror names are
  only printed in case of errors). However, since ttf-mscorefonts-
  installer triggers 11 downloads in a row, chances of randomly getting
  11 working mirrors are very low.

  I am tagging this as regression-update because the issue started
  happening when upgrading from 3.168.2 to 3.168.3 last Friday. It is of
  course entirely possible the root cause is in another package, but
  this would also likely be a regression-update, since I am very careful
  about system-wide changes on this machine.

  The previous update from 3.168.1 to 3.168.2 on November 4th went just
  fine. ttf-mscorefonts-installer has been installed (just fine) on
  September 26th, and not upgraded since then.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1655431/+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 1695905] [NEW] package sudo 1.8.19p1-1ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2017-06-05 Thread Tola Liv

Public bug reported:

Unable to install any application such as Google Chrome.  The
installation process stopped at 33% progress. Additionally, I cannot
view CNN video on either Firefox browser or Opera.  Noted that Adobe
Flash was installed.

Version of Ubuntu 17.04

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: sudo 1.8.19p1-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
AptOrdering:
 opera-stable:amd64: Install
 libindicator7:amd64: Install
 libappindicator1:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sun Jun  4 18:43:58 2017
DuplicateSignature:
 package:sudo:1.8.19p1-1ubuntu1.1
 Processing triggers for desktop-file-utils (0.23-1ubuntu2) ...
 dpkg: error processing package sudo (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-05-07 (29 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: sudo
Title: package sudo 1.8.19p1-1ubuntu1.1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package sudo 1.8.19p1-1ubuntu1.1 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in sudo package in Ubuntu:
  New

Bug description:
  Unable to install any application such as Google Chrome.  The
  installation process stopped at 33% progress. Additionally, I cannot
  view CNN video on either Firefox browser or Opera.  Noted that Adobe
  Flash was installed.

  Version of Ubuntu 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: sudo 1.8.19p1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   opera-stable:amd64: Install
   libindicator7:amd64: Install
   libappindicator1:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jun  4 18:43:58 2017
  DuplicateSignature:
   package:sudo:1.8.19p1-1ubuntu1.1
   Processing triggers for desktop-file-utils (0.23-1ubuntu2) ...
   dpkg: error processing package sudo (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-07 (29 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: sudo
  Title: package sudo 1.8.19p1-1ubuntu1.1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1695905/+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 1695905] Re: package sudo 1.8.19p1-1ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

** Tags removed: need-duplicate-check

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

Title:
  package sudo 1.8.19p1-1ubuntu1.1 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in sudo package in Ubuntu:
  New

Bug description:
  Unable to install any application such as Google Chrome.  The
  installation process stopped at 33% progress. Additionally, I cannot
  view CNN video on either Firefox browser or Opera.  Noted that Adobe
  Flash was installed.

  Version of Ubuntu 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: sudo 1.8.19p1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   opera-stable:amd64: Install
   libindicator7:amd64: Install
   libappindicator1:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jun  4 18:43:58 2017
  DuplicateSignature:
   package:sudo:1.8.19p1-1ubuntu1.1
   Processing triggers for desktop-file-utils (0.23-1ubuntu2) ...
   dpkg: error processing package sudo (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-07 (29 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: sudo
  Title: package sudo 1.8.19p1-1ubuntu1.1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1695905/+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 1692247] Re: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half-installed')

2017-06-05 Thread ChristianEhrhardt

Hi Nicholas,
at the moment this is non reproducible for us.
If you are really running into the same issue, could you

a) test the workaround to fix the install that Seth posted before
b) provide further into about the actual error - at least the full console 
content of when you try a would be nice (DpkgTerminalLog was not attached in 
the initial bug report)

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

Title:
  package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade:
  package iproute2 is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  I dont know anything. I just try to instal some programs on my comp,
  and when i try to start virtualbox it cant.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: iproute2 4.3.0-1ubuntu3.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   iproute2: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May 20 16:22:19 2017
  DpkgTerminalLog:
   dpkg: error processing package iproute2 (--configure):
package iproute2 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package iproute2 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-02-20 (88 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: iproute2
  Title: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: 
package iproute2 is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1692247/+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 1393578] Re: Subpixel order not included in Mir display information

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Subpixel order not included in Mir display information

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Triaged
Status in qtubuntu package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  Just capturing something mentioned by Trevinho on IRC this morning.
  MirDisplayOutput does not include subpixel ordering, it could and
  should though. The information is exposed on the drm side
  (drmModeSubPixel). Marking as wishlist in absence of other
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1393578/+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 1661704] Re: mir_window_request_persistent_id_sync seg faults when called twice

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  mir_window_request_persistent_id_sync seg faults when called twice

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Thread 1 "gtk3-widget-fac" received signal SIGSEGV, Segmentation fault.
  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67
  67  ../nptl/pthread_mutex_lock.c: No such file or directory.
  (gdb) bt
  #0  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67
  #1  0x737c1003 in __gthread_mutex_lock () at 
/usr/include/x86_64-linux-gnu/c++/6/bits/gthr-default.h:748
  #2  std::mutex::lock() (this=0x0) at /usr/include/c++/6/bits/std_mutex.h:103
  #3  std::unique_lock::lock() (this=0x7fffbad0) at 
/usr/include/c++/6/bits/std_mutex.h:267
  #4  std::unique_lock::unique_lock(std::mutex&) () at 
/usr/include/c++/6/bits/std_mutex.h:197
  #5  MirWaitHandle::wait_for_all() (this=0x0) at 
./src/client/mir_wait_handle.cpp:51
  #6  0x737d0623 in mir_surface_request_persistent_id_sync 
(surface=) at ./src/client/mir_surface_api.cpp:1266
  #7  0x77b7137a in gdk_mir_display_convert_selection 
(display=0x557ad010, requestor=0x56235af0, selection=0x45, target=0x52, 
time=34494073)
  at /home/william/Code/jhbuild/checkout/gtk+-3/gdk/mir/gdkmirdisplay.c:845
  #8  0x77aee577 in gdk_selection_convert (requestor=0x56235af0, 
selection=0x45, target=0x52, time=34494073) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gdk/gdkselection.c:273
  #9  0x773f675e in gtk_selection_convert (widget=0x55fcaf80, 
selection=0x45, target=0x52, time_=34494073) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkselection.c:1162
  #10 0x77537a04 in gtk_clipboard_real_request_contents 
(clipboard=0x55fb7690, target=0x52, callback=0x774469cc 
, user_data=0x7fffc00037b0)
  at /home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkclipboard.c:1023
  #11 0x7753793f in gtk_clipboard_request_contents 
(clipboard=0x55fb7690, target=0x52, callback=0x774469cc 
, user_data=0x7fffc00037b0)
  at /home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkclipboard.c:994
  #12 0x774471be in gtk_text_buffer_paste_clipboard 
(buffer=0x5594b2f0, clipboard=0x55fb7690, override_location=0x0, 
default_editable=1)
  at /home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtktextbuffer.c:3871
  #13 0x7747f7e6 in gtk_text_view_paste_clipboard 
(text_view=0x55ad28b0) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtktextview.c:7156
  #14 0x762b4fe7 in g_cclosure_marshal_VOID__VOID 
(closure=0x55cac020, return_value=0x0, n_param_values=1, 
param_values=0x5616a050, invocation_hint=0x7fffc0e0,
  marshal_data=0x7747f78d ) at 
/home/william/Code/jhbuild/checkout/glib/gobject/gmarshal.c:875
  #15 0x762b24a4 in g_type_class_meta_marshal (closure=0x55cac020, 
return_value=0x0, n_param_values=1, param_values=0x5616a050, 
invocation_hint=0x7fffc0e0, marshal_data=0x410)
  at /home/william/Code/jhbuild/checkout/glib/gobject/gclosure.c:997
  #16 0x762b1dc0 in g_closure_invoke (closure=0x55cac020, 
return_value=0x0, n_param_values=1, param_values=0x5616a050, 
invocation_hint=0x7fffc0e0)
  at /home/william/Code/jhbuild/checkout/glib/gobject/gclosure.c:804
  #17 0x762d0532 in signal_emit_unlocked_R (node=0x55cac050, 
detail=0, instance=0x55ad28b0, emission_return=0x0, 
instance_and_params=0x5616a050)
  at /home/william/Code/jhbuild/checkout/glib/gobject/gsignal.c:3673
  #18 0x762ce32d in g_signal_emitv (instance_and_params=0x5616a050, 
signal_id=450, detail=0, return_value=0x0) at 
/home/william/Code/jhbuild/checkout/glib/gobject/gsignal.c:3129
  #19 0x771a598c in gtk_binding_entry_activate (entry=0x55cc7c80, 
object=0x55ad28b0) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkbindings.c:646
  #20 0x771a7193 in binding_activate (binding_set=0x55cac760, 
entries=0x562609c0, object=0x55ad28b0, is_release=0, 
unbound=0x7fffc2ec)
  at /home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkbindings.c:1446
  #21 0x771a7320 in gtk_bindings_activate_list (object=0x55ad28b0, 
entries=0x562609c0, is_release=0) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkbindings.c:1505
  #22 0x771a7594 in gtk_bindings_activate_event (object=0x55ad28b0, 
event=0x7fffdc002810) at 
/home/william/Code/jhbuild/checkout/gtk+-3/gtk/gtkbindings.c:1592
  #23 0x77505621 in gtk_widget_real_key_press_event 
(widget=0x55ad28b0, event=0x7fffdc002810) at

[Touch-packages] [Bug 1644189] Re: Shell doesn't know when base display config has changed

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Shell doesn't know when base display config has changed

Status in Mir:
  Fix Released
Status in MirAL:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  In Progress

Bug description:
  Privileged clients can change the server base display configuration.
  Shell wants to know when the  base config is committed to a valid
  config (as opposed to a preview), in order to save that config to
  disk, to be applied again on restart.

  I cannot see any API for shell to learn when base config is changed.

  Closest is the AuthorizingDisplayChanger, but that is private. Really, all we 
want is a callback on
  - base config set to new config (applied, not previewed)

  Would also be nice to know:
  - base config has changed to preview a new config
  - base config preview cancelled

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644189/+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 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] Nested server segfaults or rapidly logs exceptions when a
  fullscreen client starts [in mir_presentation_chain_set_dropping_mode
  ... std::exception::what: Operation not permitted]

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Nested server segfaults when a fullscreen client starts

  Using Mir 0.26.0 (zesty release):

  The client dies:

  [2017-02-03 15:05:44.315444]  Mesa/NativeSurface: Caught exception at 
Mir/EGL driver boundary (in advance_buffer): 
/build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76):
 Throw in function void mir::client::PromiseStateBase::break_promise() [with 
T = std::shared_ptr]
  Dynamic exception type: 
boost::exception_detail::error_info_injector
  std::exception::what: broken_promise

  Because the server died:

  Segmentation fault (core dumped)
  (gdb) bt
  #0  __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67
  #1  0x7fcceb7b4003 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #2  0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode ()
     from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #3  0x7fccec0e3a7a in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #4  0x7fccec09fd2d in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #5  0x7fccec09f018 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #6  0x7fccec0e2c79 in ?? ()
     from /usr/lib/x86_64-linux-gnu/libmirserver.so.43
  #7  0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #8  0x7fcce95326ca in start_thread (arg=0x7fccde2b4700)
  at pthread_create.c:333
  #9  0x7fccec4710ff in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

  However in development builds the server does not die and just floods
  the log instead:

  [2017-02-03 16:52:44.382460]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.399142]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.415823]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  [2017-02-03 16:52:44.432504]  mirclient: Caught exception at client 
library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic 
exception type: std::system_error
  std::exception::what: Operation not permitted

  *** WORKAROUND ***
  Start your nested server with --nested-passthrough=OFF
  Which works on the 0.26.0 release, but not on anything newer because you'll 
then hit the more recent regression bug 1661521.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1661508/+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 1661521] Re: [regression] Windowed clients of nested servers are all black

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] Windowed clients of nested servers are all black

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  [regression] Windowed clients of nested servers are all black

  FAILING:
  lp:mir r4008
  lp:mir/0.26 r4005

  WORKING:
  Mir 0.26.0 zesty binaries (lp:mir/0.26 r3994)
  lp:mir/0.25 r3822

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1661521/+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 1661498] Re: [regression] Segfault on detect_fd_leaks during acceptance tests (in DisplayConfiguration/{DisplayFormatSetting, DisplaySubpixelSetting})

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] Segfault on detect_fd_leaks during acceptance tests (in
  DisplayConfiguration/{DisplayFormatSetting,DisplaySubpixelSetting})

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  I've seen this quite often in a silo... Not so often in CI.

  8: [ RUN ] 
DisplayConfiguration/DisplayFormatSetting.can_get_all_output_format/3
  8: [2017-02-03 01:05:22.479325] mirserver: Starting
  8: [2017-02-03 01:05:22.479397] mirserver: Selected driver: mir:stub-graphics 
(version 0.26.1)
  8: [2017-02-03 01:05:22.489793] mirserver: Using software cursor
  8: [2017-02-03 01:05:22.492185] mirserver: Selected input driver: 
mir:stub-input (version: 0.26.1)
  8: [2017-02-03 01:05:22.492233] mirserver: Mir version 0.26.1
  8: [2017-02-03 01:05:22.492401] mirserver: Initial display configuration:
  8: [2017-02-03 01:05:22.492420] mirserver: Output 1: VGA connected, used
  8: [2017-02-03 01:05:22.492430] mirserver: Physical size 0.0" 0x0mm
  8: [2017-02-03 01:05:22.492436] mirserver: Power is on
  8: [2017-02-03 01:05:22.492444] mirserver: Current mode 4x3 10.00Hz
  8: [2017-02-03 01:05:22.492451] mirserver: Preferred mode 4x3 10.00Hz
  8: [2017-02-03 01:05:22.492457] mirserver: Orientation normal
  8: [2017-02-03 01:05:22.492463] mirserver: Logical size 4x3
  8: [2017-02-03 01:05:22.492468] mirserver: Logical position +0+0
  8: [2017-02-03 01:05:22.492474] mirserver: Output 2: VGA disconnected
  8: [2017-02-03 01:05:22.492480] mirserver: Output 3: VGA connected, unused
  8: [2017-02-03 01:05:22.492486] mirserver: Physical size 0.0" 0x0mm
  8: [2017-02-03 01:05:22.492491] mirserver: Power is off
  8: [2017-02-03 01:05:22.511553] mirserver: New display configuration:
  8: [2017-02-03 01:05:22.511586] mirserver: Output 1: VGA connected, used
  8: [2017-02-03 01:05:22.511597] mirserver: Physical size 0.0" 0x0mm
  8: [2017-02-03 01:05:22.511603] mirserver: Power is on
  8: [2017-02-03 01:05:22.511611] mirserver: Current mode 4x3 10.00Hz
  8: [2017-02-03 01:05:22.511618] mirserver: Preferred mode 4x3 10.00Hz
  8: [2017-02-03 01:05:22.511624] mirserver: Orientation normal
  8: [2017-02-03 01:05:22.511629] mirserver: Logical size 4x3
  8: [2017-02-03 01:05:22.511635] mirserver: Logical position +0+0
  8: [2017-02-03 01:05:22.511661] mirserver: New base display configuration:
  8: [2017-02-03 01:05:22.526758] mirserver: Stopping
  8: /<>/mir-0.26.1+17.04.20170203/tools/detect_fd_leaks.bash: line 
84: 27470 Segmentation fault  (core dumped) $@ 2>&1
  8:  27471 Done| detect_fd_leaks
   8/20 Test  #8: mir_acceptance_tests ..***Failed  
 81.66 sec
  Running main() from main.cpp
  Note: Google Test filter = -:
  [==] Running 517 tests from 86 test cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1661498/+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 1626866] Re: [regression] 'make abi-check' fails to build

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] 'make abi-check' fails to build

Status in Mir:
  Fix Released
Status in Mir 0.24 series:
  Triaged
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  make abi-check fails to build:

  The GCC parameters:
/usr/bin/c++ -fdump-translation-unit -fkeep-inline-functions -c -x 
c++-header -fpermissive -w  -pthread -g -std=c++14 -Werror -Wall 
-fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC 
"/tmp/rTU25VRtKM/dump1.h"  -I/home/dan/bzr/mir/unbreak/include/common 
-I/home/dan/bzr/mir/unbreak/include/cookie -I/usr/include 
-I/home/dan/bzr/mir/unbreak/src/include/common 
-I/home/dan/bzr/mir/unbreak/build/src/protobuf 
-I/home/dan/bzr/mir/unbreak/include/platform 
-I/home/dan/bzr/mir/unbreak/src/include/platform

  In file included from /tmp/rTU25VRtKM/dump1.h:22:0:
  /home/dan/bzr/mir/unbreak/include/platform/mir/graphics/gamma_curves.h:27:7: 
error: redefinition of ‘class mir::graphics::GammaCurves’
   class GammaCurves
 ^~~
  In file included from 
/home/dan/bzr/mir/unbreak/include/platform/mir/graphics/display_configuration.h:26:0,
   from /tmp/rTU25VRtKM/dump1.h:4:
  /home/dan/bzr/mir/unbreak/include/platform/mir/graphics/gamma_curves.h:27:7: 
error: previous definition of ‘class mir::graphics::GammaCurves’
   class GammaCurves
 ^~~

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1626866/+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 1612012] Re: Valgrind errors in NesterServer.* cause subsequent tests (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Valgrind errors in NesterServer.* cause subsequent tests
  (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail

Status in Mir:
  Confirmed
Status in Mir 0.24 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Tests always fail together: ServerDisconnect, ServerStartup,
  UnresponsiveClient

  17:27:52 9: [ FAILED ] 5 tests, listed below:
  17:27:52 9: [ FAILED ] ServerDisconnect.is_detected_by_client
  17:27:52 9: [ FAILED ] 
ServerDisconnect.doesnt_stop_client_calling_API_functions
  17:27:52 9: [ FAILED ] ServerStartup.creates_endpoint_on_filesystem
  17:27:52 9: [ FAILED ] 
ServerStartup.after_server_sigkilled_can_start_new_instance
  17:27:52 9: [ FAILED ] UnresponsiveClient.does_not_hang_server

  [https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/1772/consoleFull]

  This is happening regularly in CI. These failures occur together.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1612012/+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 1638774] Re: Mir FTBFS on zesty: invalid use of ‘struct native_handle’ with a zero-size array

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Mir FTBFS on zesty: invalid use of ‘struct native_handle’ with a zero-
  size array

Status in Mir:
  Fix Released
Status in Mir 0.24 series:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Mir FTBFS on zesty:

  In file included from 
/home/dan/bzr/mir/trunk/tests/unit-tests/platforms/android/server/test_buffer.cpp:27:0:
  
/home/dan/bzr/mir/trunk/tests/include/mir/test/doubles/mock_android_native_buffer.h:65:21:
 error: invalid use of ‘struct native_handle’ with a zero-size array in ‘struct 
mir::test::doubles::MockAndroidNativeBuffer’ [-Werror=pedantic]
   native_handle_t native_handle;
   ^
  In file included from /usr/include/android-23/system/window.h:20:0,
   from /usr/include/android-23/hardware/gralloc.h:21,
   from 
/home/dan/bzr/mir/trunk/src/platforms/android/server/buffer.h:27,
   from 
/home/dan/bzr/mir/trunk/tests/unit-tests/platforms/android/server/test_buffer.cpp:20:
  /usr/include/android-23/cutils/native_handle.h:29:15: note: array member ‘int 
native_handle::data [0]’ declared here
   int data[0];/* numFds + numInts ints */
 ^

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1638774/+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 1661072] Re: [regression] Mir 0.26.0 - spinner loading animation, minimize, maximize too fast

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] Mir 0.26.0 - spinner loading animation, minimize,
  maximize too fast

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in miral package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  mir 0.26 landed in overlay and now the loading animation is too fast and also 
i think all the animations are too fast (minimize, maximize etc) o_O
  aren't the animation fps independent? should be time based right?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661072/+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 1661163] Re: [regression] mirout crashes when connecting to unity8 or any nested server: [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:1408] CHECK failed: (ind

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] mirout crashes when connecting to unity8 or any nested
  server: [libprotobuf FATAL
  /usr/include/google/protobuf/repeated_field.h:1408] CHECK failed:
  (index) < (current_size_):

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  mirout crashes when connecting to unity8 or any nested server.

  $ mirout -- --desktop_file_hint=unity8
  Connected to server: 
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:1408] CHECK 
failed: (index) < (current_size_):
  terminate called after throwing an instance of 
'google::protobuf::FatalException'
    what():  CHECK failed: (index) < (current_size_):
  Aborted (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1661163/+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 1640366] Re: [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (AKA dropping_latency_is_closer_to_zero_than_one)

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one (AKA
  dropping_latency_is_closer_to_zero_than_one)

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  20:35:16 10: [ RUN  ] ClientLatency.dropping_latency_is_limited_to_one
  20:35:16 10: [2016-11-08 20:35:16.713374] mirserver: Starting
  20:35:16 10: [2016-11-08 20:35:16.713544] mirserver: Selected driver: 
mir:stub-graphics (version 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.714686] mirserver: Using software cursor
  20:35:16 10: [2016-11-08 20:35:16.733467] mirserver: Initial display 
configuration:
  20:35:16 10: [2016-11-08 20:35:16.734637] mirserver: Selected input driver: 
mir:stub-input (version: 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.734766] mirserver: Mir version 0.25.0
  20:35:18 10: 
/<>/mir-0.25.0+yakkety2807bzr3804/tests/acceptance-tests/test_latency.cpp:341:
 Failure
  20:35:18 10: Value of: max_latency
  20:35:18 10: Expected: is <= 1
  20:35:18 10:   Actual: 2 (of type unsigned int)
  20:35:18 10: [  debug   ] 98 frames sampled, averaging 1.0 frames latency
  20:35:18 10: [  debug   ]  0:  1  1  1  1  1  1  1  2  1  1
  20:35:18 10: [  debug   ] 10:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 20:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 30:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 40:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 50:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 60:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 70:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 80:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 90:  1  1  1  1  1  1  1  1
  20:35:18 10: [2016-11-08 20:35:18.575646] mirserver: Stopping
  20:35:18 10: [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one 
(1879 ms)

  [https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2781/consoleFull]

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1640366/+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 1662942] Re: libmirclient-dev missing build depndency on libmircore-dev

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  libmirclient-dev missing build depndency on libmircore-dev

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  There is a broken build-dep in the Mir 0.26 packaging.

  Dialogue taken from IRC revealing the details:

   alan_g, when I include mir_toolkit header files in chromium I get 
this error:
   In file included from 
/usr/include/mirclient/mir_toolkit/events/event.h:90:
   #include "mir_toolkit/mir_input_device_types.h"
   and apt-file search doesn't return anything
   I wonder what I am missing
   is this a bug or there's a lib I should have installed?
   locate also cant find this file
   that's in libmircore-dev.  What do you get from $ pkg-config 
--cflags mirclient
   $ pkg-config --cflags mirclient
   -pthread -I/usr/include/mirclient -I/usr/include/mircookie 
-I/usr/include/mircore
   that lib was missing :)
   Then /usr/include/mircore/mir_toolkit/mir_input_device_types.h ought 
to be there
   :s
   ok installing mircore-dev fixed that
   apt-file should return it though :/
   Hmm. $ apt depends libmirclient-dev doesn't list libmircore-dev - 
sounds like a bug
   yes, when I ran apt-get build-dep libmirclient-dev mircore-dev was 
not installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1662942/+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 1651638] Re: [regression] Latency for fullscreen interval 0 clients (e.g. games and benchmarks) increased with the introduction of nested passthrough

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] Latency for fullscreen interval 0 clients (e.g. games and
  benchmarks) increased with the introduction of nested passthrough

Status in Mir:
  Fix Released
Status in Mir 0.25 series:
  Triaged
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Nested fullscreen interval 0 clients in Mir 0.25.0 had higher latency
  than interval 1 nested fullscreen clients.

  I've reproduced this a couple of times and it is concerning:

  Mir 0.25:
     Interval 0: 81ms  <-- regression
     Interval 1: 64ms  <-- improvement

  Mir 0.24:
 Interval 0: 70ms
 Interval 1: 96ms

  It's the obvious green spike in this chart:
  
https://docs.google.com/spreadsheets/d/1RbTVDbx04ohkF4-md3wAlgmxbSI1DttstnT6xdcXhZQ/pubchart?oid=1566479835=interactive

  Although this regression appears to be resolved in the 0.26 series
  (lp:mir) it's serious enough that we should look into finding what the
  cause was so that Mir 0.25.1 can get the same fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1651638/+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 1634508] Re: Clients cannot connect when MIR_SOCKET=""

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Clients cannot connect when MIR_SOCKET=""

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Launch a Unity 8 desktop session, log out, then log into a Unity 7
  session. Launch a Mir-on-X shell like MirAL and then try to launch a
  Mir client like mir_demo_client_egltriangle. The client will refuse to
  connect.

  Unity 8's upstart script always sets MIR_SOCKET to its old value when
  the session ends. If MIR_SOCKET wasn't set, then the post-stop script
  will still set MIR_SOCKET, setting it to "". Mir should interpret this
  as if MIR_SOCKET were unset.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1634508/+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 1591328] Re: Pointer/cursor input lag in unity8 session

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Pointer/cursor input lag in unity8 session

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Mouse pointer suffers of heavy input lag on my laptop, might also
  affect tablet

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591328/+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 1662455] Re: Mir graphics platform ABI broke in series 0.26 but sonames never changed

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Mir graphics platform ABI broke in series 0.26 but sonames never
  changed

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  An ABI break in series 0.26 arose from changes to:
  include/platform/mir/graphics/display_configuration.h
  include/platform/mir/graphics/graphic_buffer_allocator.h

  However the applicable ABI(s) never changed from series 0.25:
  MIR_SERVER_GRAPHICS_PLATFORM_ABI
  MIRPLATFORM_ABI

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1662455/+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 1644075] Re: [regression] Those mir_demo_client_* which default to fullscreen now ignore the size parameter (-s WIDTHxHEIGHT)

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] Those mir_demo_client_* which default to fullscreen now
  ignore the size parameter (-s WIDTHxHEIGHT)

Status in Mir:
  Fix Released
Status in Mir 0.25 series:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Those mir_demo_client_* which default to fullscreen now ignore the
  size parameter (-s WIDTHxHEIGHT), instead choosing to stay in
  fullscreen mode.

  This applies to mirvanity too, making testing of windowed client
  latency difficult.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1644075/+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 1626435] Re: Keyboard layout not applied on the shell

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Keyboard layout not applied on the shell

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Released
Status in Mir 0.24 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Split out from bug #1611859:

  Steps:
  * connect a BT or a physical keyboard
  * wipe or remove ~/.config/ubuntu-system-settings/wizard-has-run* and reboot
  * go through the wizard

  Expected:
  * I can use the selected layout in the wizard
  * and in snap decisions

  Current:
  * you can only use us layout in the shell

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.14+16.04.20160914-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-landing-078]
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 22 10:07:47 2016
  InstallationDate: Installed on 2016-05-06 (138 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626435/+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 1661128] Re: [regression] Unity8 stutters constantly (like half frame rate) using Mir 0.26.0

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] Unity8 stutters constantly (like half frame rate) using
  Mir 0.26.0

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Unity8 stutters constantly (like half frame rate) on a high-end
  desktop.

  This regression only happened recently, perhaps due to the
  introduction of Mir 0.26.0.

  Surprisingly though, using the same Mir release I can start a demo
  server on another VT and everything is silky-smooth. The problem only
  seems to occur with Unity8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661128/+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 1660017] Re: EDID does not change when hotplugging a monitor

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  EDID does not change when hotplugging a monitor

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  EDID does not change when hotplugging a monitor

  It appears Mir only gets the EDID right if the monitor was plugged in
  before the server started.

  If you change monitors, then Mir continues to report the old monitor's
  EDID. And similarly if the server started before the monitor was
  plugged in, Mir always reports no EDID for it.

  Other attributes like physical size appear to change correctly when
  hotplugging. Only the EDID is wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1660017/+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 1645372] Re: support display scaling slider in unity8

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  support display scaling slider in unity8

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  We need to be able to scale the display in unity8, via ubuntu-system-
  settings Display->Scaling slider. This will need backend support in
  Mir and unity8, filing this bug to track.

  Also see related bug https://bugs.launchpad.net/mir/+bug/1196239/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1645372/+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 1628507] Re: Mir fails to cross-build with newer sbuild versions

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Mir fails to cross-build with newer sbuild versions

Status in Mir:
  Fix Released
Status in abi-compliance-checker package in Ubuntu:
  New
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  When trying to cross-build Mir with sbuild version >= 0.68.0, the
  build fails with:

  sbuild-build-depends-mir-dummy:armhf : Depends: cmake-data:armhf but it is 
not installable
     Depends: abi-compliance-checker:armhf 
but it is not installable

  This is caused by a change ([1]) in the way sbuild installs build-deps
  for the package under build. Previously sbuild used the 'apt-get
  build-dep' command, but recent versions calculate the build-deps
  manually (using the Dpkg perl module) and install the -dummy package
  instead.

  This change isn't a problem in and of itself, but unfortunately
  uncovers a problem in the cmake-data and abi-compliance-checker
  packages. In particular, the two packages are not multi-arch ready and
  sbuild can't know that it needs to install their native/build (amd64)
  version, so it uses the host (armhf) version instead.

  The previous 'apt-get build-dep' way worked because APT is patched in
  ubuntu (but not in debian) to consider packages with architecture
  'all' as 'Multi-Arch: foreign' ([1],[2]). The Dpkg perl modules don't
  contain such a patch.

  [1] 
https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/commit/?id=e227c8f3e10edd78bc71350380f559c481634b79
  [2] https://wiki.debian.org/Multiarch/CrossDependencies
  [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666772

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1628507/+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 1662997] Re: [regression] mirscreencast hangs during screencast creation

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] mirscreencast hangs during screencast creation

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  hmm, sometime between 3980 and tip, mirscreencast started hanging
  during screencast creation. Bound to generate some complaints.

  Thread 1 "mirscreencast.b" received signal SIGTSTP, Stopped (user).
  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  185   ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S: No such file or 
directory.
  (gdb) bt
  #0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  #1  0x77449afc in 
std::condition_variable::wait(std::unique_lock&) ()
 from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  #2  0x77ea131a in 
std::condition_variable::wait 
>(std::unique_lock &, MirWaitHandle::) 
(this=0x555da6d0, __lock=..., __p=...)
  at /usr/include/c++/6/condition_variable:99
  #3  0x77ea1061 in MirWaitHandle::wait_for_all (this=0x555da6a8)
  at /home/kdub/source/mir/mir/src/client/mir_wait_handle.cpp:53
  #4  0x77ee5420 in (anonymous namespace)::create_screencast 
(spec=0x555d9bf0)
  at /home/kdub/source/mir/mir/src/client/mir_screencast_api.cpp:38
  #5  0x77ee5631 in mir_screencast_create_sync (spec=0x555d9bf0)
  at /home/kdub/source/mir/mir/src/client/mir_screencast_api.cpp:90
  #6  0x55591430 in main (argc=3, argv=0x7fffe478)
  at /home/kdub/source/mir/mir/src/utils/screencast.cpp:568

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1662997/+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 1666372] Re: Nested servers (Unity8) periodically stutter (half frame rate) with Mir 0.26.1

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Nested servers (Unity8) periodically stutter (half frame rate) with
  Mir 0.26.1

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Nested servers periodically stutter (half frame rate) with Mir 0.26.1

  On an old laptop, it's about half the time stuttering and half the
  time smooth.

  On a fast desktop, it only stutters occasionally like when a large
  blur is active.

  It seems the problem is Mir's predictive bypass optimization
  conflicting with the new client-side vsync optimization. Both are
  correct and desirable when used alone, but when used together they
  conflict, presumably because the former requires perfect vsync phase
  and the latter lacks correct vsync phase (which is still an exercise
  for later).

  A workaround to get more reliably smooth frame rates is to create a file:
/etc/lightdm/lightdm.conf.d/foo.conf
  with contents:

  [Seat:*]
  unity-compositor-command=/usr/sbin/unity-system-compositor --composite-delay=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666372/+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 1673533] Re: Presentation chains should support various Vulkan presentation modes

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Presentation chains should support various Vulkan presentation modes

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Specifically, Vulkan modes:

  mir_present_mode_immediate, //same as VK_PRESENT_MODE_IMMEDIATE_KHR
  mir_present_mode_mailbox, //same as VK_PRESENT_MODE_MAILBOX_KHR
  mir_present_mode_fifo, //same as VK_PRESENT_MODE_FIFO_KHR
  mir_present_mode_fifo_relaxed, //same as VK_PRESENT_MODE_FIFO_RELAXED_KHR

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1673533/+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 1672955] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::Lib

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  unity-system-compositor crashed with SIGSEGV in
  libinput_device_config_accel_is_available() from
  libinput_device_config_accel_set_speed() from
  mir::input::evdev::LibInputDevice::apply_settings()

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in mir source package in Xenial:
  Fix Committed
Status in unity-system-compositor source package in Xenial:
  Invalid

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

  It seems that the configuration change is requested just a moment
  before the device gets removed. The change actions are serialized,
  depending on where there memory of mir::input::DefaultDevice is
  allocated the segfault either occurs inside the lambda or inside
  underlying mir::input::LibInputDevice in the platform. The activities
  on input dispatch device removal and reconfiguration are serialized
  inside the input thread, so we just need to clean the action queue (or
  have multiple queues) before removing the devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+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 1673534] Re: Need an extension for GBM buffers to replace mir_buffer_get_buffer_package()

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Need an extension for GBM buffers to replace
  mir_buffer_get_buffer_package()

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  We need for Mesa EGL

  typedef struct MirExtensionGbmBufferV2
  {
  MirConnectionAllocateBufferGbm allocate_buffer_gbm;
  MirConnectionAllocateBufferGbmSync allocate_buffer_gbm_sync;
  MirBufferIsGbmImportable is_gbm_importable;
  MirBufferGbmFd fd;
  MirBufferGbmStride stride;
  MirBufferGbmFormat format;
  MirBufferGbmFlags flags;
  MirBufferGbmAge age;
  } MirExtensionGbmBufferV2;

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1673534/+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 1675138] Re: Please transition to Boost 1.62

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Please transition to Boost 1.62

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in mir source package in Xenial:
  Fix Committed

Bug description:
  There is an ongoing transition to Boost 1.62 and mir is one of the last 
affected packages:
  http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.62.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1675138/+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 1670876] Re: Setting MirWindowSpec parameters always causes window's input_region to be reset

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

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Setting MirWindowSpec parameters always causes window's input_region
  to be reset

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Triaged
Status in MirAL:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  I've made a quick demo to reproduce this:

  https://code.launchpad.net/~gerboland/+git/basic_mir_client/+ref
  /cursor-mask-demo

  
  1. launch any mir demo server
  2. launch the above demo
  3. press 'c' to set the cursor of the window, cursor should become a cross 
over the window.
  4. press 'm' to set the input region as a subset of the window. You can 
observe the input region by moving the cursor over the window, cursor will be a 
cross inside the specified region. You can click too, will cause client to 
print "click"
  5. press 'c' again.

  Expected result
  no change

  Actual result
  Input region of surface appears to be reset - cursor is a cross over the 
entire window.

  
  I've noticed this behaviour only after this update to QtUbuntu:
  
https://code.launchpad.net/~albaguirre/qtubuntu/more-new-mir-apis/+merge/316646
  so suspect a bug with the new api only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670876/+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 1667645] Re: If the only surface in a session cannot take focus the server crashes

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  If the only surface in a session cannot take focus the server crashes

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in MirAL:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in miral package in Ubuntu:
  Fix Released

Bug description:
  The problem is in ms::ApplicationSession::surface_after() it can
  dereference the surfaces.end() iterator.

  Original description:

  $ bin/miral-desktop
  ...
  terminate called after throwing an instance of 
'boost::exception_detail::clone_impl'
    what():  surface_after: surface is not a member of this session
  Aborted (core dumped)

  Using tiling WM doesn't exhibit this problem:

  $ bin/miral-desktop --window-manager tiling

  I would guess this is something to do with the recent addition of
  wallpaper. And possibly due to this test box being slow (14 years
  old), not due to Xenial/Mir 21.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1667645/+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 1663062] Re: [regression] Software clients of nested servers with size >=480x480 are all black in Mir 0.25.0 and later (or stretched and distorted under Unity8)

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] Software clients of nested servers with size >=480x480
  are all black in Mir 0.25.0 and later (or stretched and distorted
  under Unity8)

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in Mir 0.25 series:
  Won't Fix
Status in Mir 0.26 series:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  GPU apps seem to work.

  CPU apps all get black screen.

  To repro :
  Under unity7 using mir-on-x:

  1- In a terminal, run :
  mir_demo_server -f /tmp/mysock

  2- In another terminal, run :
  mir_demo_server --host-socket /tmp/mysock

  3- In another terminal, run :
  mir_demo_client_progressbar

  Under Unity8 :
  In another terminal, run :
  mir_demo_client_progressbar

  Observe that, the window is black.

  Whereas, egl clients run fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663062/+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 1677239] Re: mir_demo_standalone_render_overlays fails to link

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  mir_demo_standalone_render_overlays fails to link

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in mir source package in Xenial:
  Fix Committed

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/4453/console

  11:41:20 [ 52%] Linking CXX executable 
../../../../bin/mir_demo_standalone_render_overlays.bin
  11:41:20 cd 
/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124/obj-x86_64-linux-gnu/src/platforms/android/utils
 && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/mir_demo_standalone_render_overlays.dir/link.txt --verbose=1
  11:41:20 /usr/lib/ccache/c++ -g -O2 
-fdebug-prefix-map=/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing 
-pedantic -Wnon-virtual-dtor -Wextra -fPIC -flto -ffat-lto-objects 
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
CMakeFiles/mir_demo_standalone_render_overlays.dir/render_overlays.cpp.o -o 
../../../../bin/mir_demo_standalone_render_overlays.bin -rdynamic 
../../../../lib/libmirplatform.so.16 ../../../../lib/libmircommon.so.7 
../../../capnproto/libmircapnproto.a -lkj -lcapnp 
../../../../lib/libmircore.so.1 -lboost_date_time -lboost_system 
-lboost_program_options -lboost_filesystem -ldl -lEGL -lGLESv2 -lGLESv2 
-L/lib/x86_64-linux-gnu -ludev -ludev
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirInputDeviceStateEvent::device_pressed_keys_for_index(unsigned long, 
unsigned long) const@MIR_COMMON_0.25_PRIVATE'
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirPointerEvent::set_x(float)@MIR_COMMON_0.25_PRIVATE'
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirTouchEvent::pressure(unsigned long) const@MIR_COMMON_0.25_PRIVATE'

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1677239/+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 1669444] Re: [regression] OSK input shaping no longer works correctly

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  [regression] OSK input shaping no longer works correctly

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-keyboard package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

  1) Run the keyboard under Unity8 (silo 2481 can be helpful in making this 
more usable at present)
  2) Click in an input field
  3) Move the mouse over the keyboard
  4) Attempt to click on the app again

  Expected result:

  The mouse click should be passed through to the app

  Actual result:

  The click is swallowed by the keyboard surface instead. However, it is
  still possible to click on the app if this is done prior to the mouse
  entering the visible keyboard area.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669444/+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 1663197] Re: mir_window_spec_set_cursor_name() doesn't trigger mir::scene::SurfaceObserver::cursor_image_set_to

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  mir_window_spec_set_cursor_name() doesn't trigger
  mir::scene::SurfaceObserver::cursor_image_set_to

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in MirAL:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  qtmir relies on mir::scene::SurfaceObserver::cursor_image_set_to being
  called whenever the surface cursor name changes.

  qtubuntu still uses the deprecated API
  "mir_cursor_configuration_from_name() && mir_window_configure_cursor".
  With that, mir::scene::SurfaceObserver::cursor_image_set_to does get
  called in qtmir.

  But once qtubuntu uses the new Mir API for that[1],
  "mir_window_spec_set_cursor_name() && mir_window_apply_spec()", the
  SurfaceObserver in qtmir no longer gets notified

  
  [1] - 
https://code.launchpad.net/~albaguirre/qtubuntu/more-new-mir-apis/+merge/316646

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1663197/+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 1675357] Re: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while)

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Mir sending key repeat events continually to nested shell after VT
  switch (causes Unity8 lockup for a while)

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid
Status in mir source package in Xenial:
  Fix Committed
Status in qtmir source package in Xenial:
  Invalid
Status in unity8 source package in Xenial:
  Invalid

Bug description:
  Steps:
  * log in to unity8
  * Ctrl+Alt+F* to a different vt, or log in to a different user session
  * go back to the unity8 vt

  Expected:
  * session is locked, but working

  Current:
  * unity8 starts spinning for a time proportional to the period it was inactive
  * if it was inactive long enough, it doesn't seem to recover at all

  It seems it's "catching up" in some way, maybe with input, maybe
  frames.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2555]
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 23 11:36:39 2017
  InstallationDate: Installed on 2016-05-06 (320 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)

  Causes:
  The mir::input::KeyRepeatDispatcher is running inside the nested mirserver 
even though there is another instance running inside the host server. A few 
months ago qtmir used to replace the key repeater by replacing mirs  
dispatcher. And key repeat is not disabled within the nested server. So both 
the host and the nested server are producing repeat events.
    Now due to a logic error inside mirserver the key repeat dispatcher is not 
hooked up to the input device hub when running inside the nested server. The 
input device hub would tell the key repeater when devices get removed - i.e. 
due to vt switching. So it never notices that the devices go away continues to 
produce those events indefinitely.

  This applies to all currently pressed buttons. I.e. you can open an
  edit field and press 'w' while simultaneously pressing Ctrl+Alt+FX to
  switch to another VT. On return 'w' will be repeated indefinitely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675357/+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 1664760] Re: Mir server crashed with SIGSEGV in mir::compositor::TemporaryBuffer::size() called from mir::gl::tessellate_renderable_into_rectangle()

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783

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

Title:
  Mir server crashed with SIGSEGV in
  mir::compositor::TemporaryBuffer::size() called from
  mir::gl::tessellate_renderable_into_rectangle()

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  I run mir exempla:
  ./bin/mir_demo_server --launch-client ./bin/mir_demo_client_multistrea
  mir_demo_server crash when I move central animated object to right border and 
back.

  Cause of crash is to call size() function from invalid pointer in
  temporaty_buffers.cpp mc::TemporaryBuffer::size() - line: return
  buffer->size();

  I have checked why pointer is invalid:

  In function: 
  std::shared_ptr 
mc::MultiMonitorArbiter::compositor_acquire(compositor::CompositorID id) from 
multi_monitor_arbiter.cpp 

  auto& last_entry = onscreen_buffers.front();
  last_entry.use_count++;
  if (mode == mc::MultiMonitorMode::multi_monitor_sync)
  clean_onscreen_buffers(lk);

  last_entry reference pointing not existing object (object is not longer in 
onscreen_buffers) after calling clean_onscreen_buffers() function.
  clean_onscreen_buffers() function looks correct for me - but after calling 
it, data remains inconsistent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1664760/+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 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS