[Touch-packages] [Bug 1644727] [NEW] package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 failed to install/upgrade: спроба перезаписати «/etc/signon-ui/webkit-options.d/www.facebook.com.conf»

[dexel]

Public bug reported:

On Kubuntu 16.04 install ubuntu-desktop.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Nov 20 09:03:12 2016
ErrorMessage: спроба перезаписати 
«/etc/signon-ui/webkit-options.d/www.facebook.com.conf», який вже є у пакунку 
kaccounts-providers 4:15.12.3-0ubuntu1
InstallationDate: Installed on 2016-11-04 (20 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: account-plugins
Title: package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 failed to 
install/upgrade: спроба перезаписати 
«/etc/signon-ui/webkit-options.d/www.facebook.com.conf», який вже є у пакунку 
kaccounts-providers 4:15.12.3-0ubuntu1
UpgradeStatus: Upgraded to xenial on 2016-11-04 (20 days ago)

** Affects: account-plugins (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 failed to
  install/upgrade: спроба перезаписати «/etc/signon-ui/webkit-
  options.d/www.facebook.com.conf», який вже є у пакунку kaccounts-
  providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  On Kubuntu 16.04 install ubuntu-desktop.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 20 09:03:12 2016
  ErrorMessage: спроба перезаписати 
«/etc/signon-ui/webkit-options.d/www.facebook.com.conf», який вже є у пакунку 
kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2016-11-04 (20 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: account-plugins
  Title: package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 failed to 
install/upgrade: спроба перезаписати 
«/etc/signon-ui/webkit-options.d/www.facebook.com.conf», який вже є у пакунку 
kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: Upgraded to xenial on 2016-11-04 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1644727/+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 1644718] [NEW] subprocess installed post-installation script returned error exit status 1

[Nihar Das]

Public bug reported:

This happened for dbus 1.10.6 & pulse audio contol(pavucontrol) while
updating

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: udev 229-4ubuntu12
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CustomUdevRuleFiles: 50-Huawei-Datacard.rules
Date: Fri Nov 25 11:46:47 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-10-29 (26 days ago)
InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720)
MachineType: Acer Aspire ES1-521
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=086ac968-8f80-4757-9fbd-4161d240ea3c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: systemd
Title: package udev 229-4ubuntu12 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: BELLEMERE_BE
dmi.board.vendor: Acer
dmi.board.version: V1.06
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2015:svnAcer:pnAspireES1-521:pvrV1.06:rvnAcer:rnBELLEMERE_BE:rvrV1.06:cvnAcer:ct9:cvrChassisVersion:
dmi.product.name: Aspire ES1-521
dmi.product.version: V1.06
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  subprocess installed post-installation script returned error exit
  status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  This happened for dbus 1.10.6 & pulse audio contol(pavucontrol) while
  updating

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu12
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CustomUdevRuleFiles: 50-Huawei-Datacard.rules
  Date: Fri Nov 25 11:46:47 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-29 (26 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: Acer Aspire ES1-521
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=086ac968-8f80-4757-9fbd-4161d240ea3c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: systemd
  Title: package udev 229-4ubuntu12 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: BELLEMERE_BE
  dmi.board.vendor: Acer
  dmi.board.version: V1.06
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2015:svnAcer:pnAspireES1-521:pvrV1.06:rvnAcer:rnBELLEMERE_BE:rvrV1.06:cvnAcer:ct9:cvrChassisVersion:
  dmi.product.name: Aspire ES1-521
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1644718/+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 1644695] [NEW] won't boot

[Sammy]

Public bug reported:

won't boot past purple screen

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CasperVersion: 1.376
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Nov 25 04:19:00 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:22cd]
LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Hewlett-Packard HP 15 Notebook PC
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- oem-config/enable=true
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/04/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.42
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 22CD
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 93.32
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd11/04/2015:svnHewlett-Packard:pnHP15NotebookPC:pvr097710205F1620180:rvnHewlett-Packard:rn22CD:rvr93.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 15 Notebook PC
dmi.product.version: 097710205F1620180
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Nov 25 04:02:54 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.2
xserver.video_driver: radeon

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


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

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

Title:
  won't boot

Status in xorg package in Ubuntu:
  New

Bug description:
  won't boot past purple screen

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CasperVersion: 1.376
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Nov 25 04:19:00 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:22cd]
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- oem-config/enable=true
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 22CD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 93.32
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Touch-packages] [Bug 1561759] Re: Not able to "Filing a general bug against no particular package"

[Launchpad Bug Tracker]

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

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

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

Title:
  Not able to "Filing a general bug against no particular package"

Status in apport package in Ubuntu:
  Expired

Bug description:
  Unlike described in 
  
https://help.ubuntu.com/community/ReportingBugs#Filing_a_general_bug_against_no_particular_package
  ubuntu-bug fails  if not given a package name or using the -w option to 
retrieve package from executeable contrary to the descibed procedure to file a 
/general/ bug against /no particular/ package

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport-gtk 2.20-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportLog:
   
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  CrashReports: 640:1000:117:1220382:2016-03-23 10:25:40.878120899 
+0100:2016-03-23 10:27:02.488061850 
+0100:/var/crash/_usr_bin_xfce4-power-manager.1000.crash
  CurrentDesktop: LXDE
  Date: Thu Mar 24 23:32:22 2016
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2016-02-19 (34 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160217)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1561759/+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 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

[Launchpad Bug Tracker]

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

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

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Expired

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+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 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[Daniel van Vugt]

Good question. Alan seems to be on top of this problem. Maybe he can try
to upstream the fix...?

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  Fix Released

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

  ~

  The reason this matters:

  The principle downstream from Mir (Unity8) loads Mir as one of a
  number of plugins, several of which use protobuf. That means that
  we're prone to being loaded, unloaded and reloaded and don't have
  control of this.

  We've encountered problems in this scenario before that have been
  traced to protobuf so we have a specific test. But other Unity8
  plugins may encounter the same issue.

  As seen in comment #25 the problem here is entirely down to a change
  in the behavior of libmirprotobuf-lite - it no longer unloads on
  dlclose().

  This is only a problem because there is code (see patch in comment
  #20) that assumes that the library will not be used after a call to
  google::protobuf::ShutdownProtobufLibrary() unless it is reloaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1644237] Re: unity8 fails to start as guest user

[Daniel van Vugt]

Probably not related directly to bug 1593407. Because duplicate bug
1307618 shows we've had this problem since 2014, before snaps existed.

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

Title:
  unity8 fails to start as guest user

Status in Canonical System Image:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  This is shown in unity8.log:

  [2016-11-23 15:59:25.820868] mirserver: Starting
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132):
 Throw in function 
mir::DefaultServerConfiguration::the_graphics_platform()::
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Exception while creating graphics platform
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245):
 Throw in function 
mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const 
string&, const string&, const 
std::shared_ptr&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Nested Mir Platform Connection Error: Failed to connect 
to server socket: Permission denied


  [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start
  initctl: No such variable: UNITY_MIR_SOCKET

  running current zesty, but I had the same problem on yakkety too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644237/+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 1644664] Re: poltergeist

[Paul White]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.

We'd be grateful if you would then provide a more complete description
of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).

Please also change the title of the bug to something more meaningful.

Sometimes it is better to raise problems you are having in the support
tracker at https://answers.launchpad.net/ubuntu if you are uncertain if
they are bugs. You can also find help with your problem in the support
forum of your local Ubuntu community http://loco.ubuntu.com/ or asking
at http://askubuntu.com or https://ubuntuforums.org.

Thanks!

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

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

Title:
  poltergeist

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I don't know much about computers, all I know I feel someone else is
  controlling my computer


  what is Xorg anyway?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Nov 24 22:55:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2163]
  InstallationDate: Installed on 2016-11-23 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=1bf97efe-efc4-48d6-b2ba-62340b386b39 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2163
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd12/04/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2163:rvr29.40:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 098B1140410620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Nov 24 18:17:34 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1463023] Re: systemd Timed out waiting for device swap and file system check

[Alexander Adam]

Okay, sorry I was wrong again. The other issue just handles the
cryptswap-stuff which seems to be an issue for years in Ubuntu (and gets
closed most of the times).

However, I was finally able to boot my system and wanted to share for
others who might be run into this issue with systemd timeouts:

I added "selinux=1 enforcing=0" to kernel boot parameters.
I have no idea why this helps but I found it here:

http://unix.stackexchange.com/questions/279987/fedora-24-wont-boot-
after-dnf-upgrade#answer-280298

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

Title:
  systemd Timed out waiting for device swap and file system check

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  
  My Ubuntu 15.04 did not start --or took so long that I switched back to 
upstart!

  ISSUE: (systemd during the boot)

  Timed out waitingfor device dev-disk-by\x2duuid-... (swap)
  Dependency failed for /dev/disk/by-uuid/... (swap)
  Dependency failed for Swap.
  Timed out waiting for device dev-sdaX.device(swap)
  Dependency failed for Swap Partition.
  Failed to start udev Wait for Complete Device Initialization.
  See "systemctl status systemd-udev-settle.service" for details.
  Starting File System Check on Root Device...
  Starting Copy rules generated while the root was ro...
  (1 of 2) A start job is running for File System Check on Root Device (3min 
28s / no limit)
  ...
   No tainted 3.19.0-18-generic #18-Ubuntu
  "echo 0> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  INFO: task systemd-udevd:336 blocked for more than 120 seconds.
  ...
  INFO: task systemd-udevd:338 blocked for more than 120 seconds.
  ...
  INFO: task systemd-udevd:346 blocked for more than 120 seconds.
  ...
  (1 of 2) A start job is running for File System Check on Root Device (4min 3s 
/ no limit)

  WORKAROUND:

  apt-get -qq -y install upstart-sysv # switch back to upstart
  
http://linux.softpedia.com/blog/Ubuntu-15-04-Users-Can-Switch-Off-Systemd-and-Use-Upstart-479373.shtml
  P.S. don't ask me to go back to systemd-sysv... I am fine with upstart

  TECHNICAL DETAILS:

  $ lsb_release -r
  Release:  15.04

  $ uname -r
  3.19.0-18-generic

  $ sudo dmidecode -s system-product-name
  MacBookPro8,2

  $ grep "^GRUB_CMDLINE_LINUX_DEFAULT" /etc/default/grub
  GRUB_CMDLINE_LINUX_DEFAULT="transparent_hugepage=always intel_iommu=on 
acpi_irq_nobalance cgroup_enable=memory swapaccount=1 libata.force=noncq 
modeset=1 hybridopts=ON,IGD,OFF i915.modeset=0 radeon.modeset=1 radeon.dpm=1 
radeon.audio=1 i915.lvds_channels=2 quirks.mbp_force_ahci=1 
acpi_backlight=vendor reboot=pci"

  $ cat /etc/fstab
  #
  # / was on /dev/sda5 during installation
  UUID=6619a7e9-4b94-4e9b-8dbe-4110f89dde74 /   ext4
errors=remount-ro 0   1
  # swap was on /dev/sda6 during installation
  UUID=813e9dc2-c678-4959-ac89-e6660f886942 noneswapsw  
0   0

  # lsblk -f
  NAME   FSTYPE  LABELUUID MOUNTPOINT
  sda  
  ├─sda1 vfatEFI  67E3-17ED
  ├─sda2 hfsplus Macintosh HD 2ba5bbc1-fff0-36ea-ade4-140386274279 
  ├─sda3 hfsplus Recovery HD  9e776f16-ceb4-37e6-b4ce-4e75c1db5444 
  ├─sda4   
  ├─sda5 ext4 6619a7e9-4b94-4e9b-8dbe-4110f89dde74 /
  └─sda6 swap 813e9dc2-c678-4959-ac89-e6660f886942 [SWAP]
  sr0   

  # blkid 
  /dev/sda1: LABEL="EFI" UUID="67E3-17ED" TYPE="vfat" PARTLABEL="EFI System 
Partition" PARTUUID="5d71ff71-9843-473d-90e7-4c780c8a494d"
  /dev/sda2: UUID="2ba5bbc1-fff0-36ea-ade4-140386274279" LABEL="Macintosh HD" 
TYPE="hfsplus" PARTLABEL="Macintosh HD" 
PARTUUID="4e4c2249-24f8-4229-9325-d4aafd7ac093"
  /dev/sda3: UUID="9e776f16-ceb4-37e6-b4ce-4e75c1db5444" LABEL="Recovery HD" 
TYPE="hfsplus" PARTLABEL="Recovery HD" 
PARTUUID="a986e3e1-ed3b-44bb-a75b-87b54434380d"
  /dev/sda5: UUID="6619a7e9-4b94-4e9b-8dbe-4110f89dde74" TYPE="ext4" 
PARTUUID="9d860cb1-1334-4f79-a07a-01b8818c4aab"
  /dev/sda6: UUID="813e9dc2-c678-4959-ac89-e6660f886942" TYPE="swap" 
PARTUUID="bf1271f6-8d51-4510-8979-666c9546f1f3"
  /dev/sda4: PARTUUID="2b731a42-bd29-4548-8f0e-a9889ee9486b"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1463023/+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 1644653] Re: tracker broken for KDE/X/lightdm

[Richard]

This is probably the race conditions mentioned paired with broken re-curse of 
bug 1644651
- possibly cause by dbus problems

Once that one is fixed, and someone is still on kde, it should be tested
again

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

Title:
  tracker broken for KDE/X/lightdm

Status in tracker package in Ubuntu:
  New

Bug description:
  tracker 1.6.2-0ubuntu1.1 on 16.04 could be made to work for KDE/X/lightdm
  - https://bugzilla.gnome.org/show_bug.cgi?id=769715#c12
  - DBUS_SESSION_BUS_ADDRESS has an incorrect value

  on 16.10 it’s beyond repair:

  dpkg --status tracker | egrep ^V
  Version: 1.10.0-1ubuntu1

  tracker reset hard && tracker daemon --start && tracker daemon 
--list-processes
  Found process ID 23118 for 'tracker-extract'
  Found process ID 23135 for 'tracker-store'
  Found process ID 23145 for 'tracker-miner-user-guides'
  Found process ID 23150 for 'tracker-miner-fs'
  Found process ID 23155 for 'tracker-miner-apps'
  - produces unhealthy tracker

  A healthy tracker has one or two tracker entries
  tracker daemon --start && tracker daemon --list-processes
  Starting miners…
✓ Userguides
✓ File System
✓ Applications
✓ Extractor
  Found 6 PIDs…
  Found process ID 4185 for 'tracker-store'
  Found process ID 4196 for 'tracker-miner-fs'
  Found process ID 4201 for 'tracker-miner-apps'
  Found process ID 4207 for 'tracker-extract'
  Found process ID 4229 for 'tracker'
  Found process ID 4921 for 'tracker-miner-user-guides'

  16/10/Unity 8 and 16.10/GNOME/Wayland are healthy, kde is not

  On login tracker kind of works, but after a while the 'tracker' entry
  dies and tracker is no longer with us.

  There are some new fancy race conditions, too:

  on reset occasionally
  (tracker daemon:13618): Tracker-CRITICAL **: Could not create proxy on the 
D-Bus session bus, Error calling StartServiceByName for 
org.freedesktop.Tracker1.Miner.Extract: Timeout was reached

  on list processes occasionally:
  Could not stat() file '/proc/21722', Error when getting information for file 
'/proc/21722': No such file or directoryFound 5 PIDs…

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: tracker 1.6.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 24 13:57:04 2016
  InstallationDate: Installed on 2016-08-26 (89 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: tracker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1644653/+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 1644666] Re: Xorg crash

[Piraten-Kris Pseudonym]

Boot with Linux 4.4.0-47-generic (upstart) instead of (systemd) now led to tty1.
The Login-Screen did not show-up at all. CTRL+ALT+F7 did not react.

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:

  Ubuntu 16.04.1 (Automatic Upgrade from 14.04)
  My Onboard-Graphics (AMD-System, ASRock N68C-S UCC): 
Nvidia C61 [GeForce 7025 / nForce 630a]
  ---
  In the Past: 
  => System and Apps worked well with Auto-Login enabled.
  To eliminate Hardware-Errors:
  > Memtest
  > Boot with Windows-XP
  => No Problems

  
  Problems in short: Linux 4.4.0-47-generic (systemd) and (upstart)
  -- 
  1. nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop
  2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen
  ---
  I don't know in which Category to sort the Bugs
  So this one is for the (Nr.1) Login-Loop (from tty-Terminal)
  (I already filed another Bug-Report for the (Nr.2) System-(Freeze)-Crash with 
Stripes-Screen)


  First Problem startet on 2016-Nov-05: => Login-Loop
  ---
  I later found out, that one Day before, the following Auto-Updates had been 
installed:
  ---
  libcurl3-gnutls(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  nvidia304(304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  nvidia-opencl-icd-304 (304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
  libcurl3(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
  ---
  After Shutdown, the next Computer-Start was stuck in a 
  => Login-Loop: After entering the correct Password, the Screen turns black 
for a Second, then the Login-Form shows up again.
  ---
  I tried a few things, that did not help, like: 
  > CTRL+F2 => Terminal > sudo ..
  > apt autoclean
  > apt clean
  > apt autoremove
  > apt update
  > apt upgrade
  > apt dist-upgrade
  > shutdown -r now
  > mv .Xauthority .Xauthority.alt
  > shutdown -r now
  > service lightdm restart
  > shutdown -r now
  > apt purge lightdm
  > apt install lightdm
  > shutdown -r now
  > .. Boot into different Linux-Kernel, .. (upstart), 
  > .. Boot into Recovery-Mode > .. > Repair > ..
  > .. I also tried to install other nvidia-drivers, which, sadly, i did not 
document. 
  => Did NOT work
  ---
  Only Thing that helped was:
  ---
  > sudo apt purge nvidia-*
  > sudo shutdown -r now
  => (nouveau-Driver was automatically installed)
  => Auto-Login to Desktop

  
  But then there was a second Problem:
  
  When > starting Thunderbird, mostly at once, sometimes after > opening some 
E-Mail-Windows, another Error occurred:
  => System freeze for 3 Seconds, then Screen turned to Stripes-Wallpaper => 
Total (Freeze-)Crash
  --
  Later, even with DISabled Hardware-Acceleration, starting both, Firefox and 
Thunderbird led to the System-Crash.
  (Sometimes, the System with nouveau booted and auto-logined into a Black 
Screen with a Mouse-Pointer. Nevertheless the System seemed to work and could 
be rebooted normally.)
  ---
  > CTRL+ALT+F2 => did NOT work
  > Magic Sys-Request (SysRQ): (ALT+PRINT)+ REISUB => did NOT work
  > ping to IP => unreachable
  ---
  After cold Reboot, i tried again to switch back from nouveau- to 
nvidia-Drivers
  > Additional Drivers > Nvidia-304.132
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-nouveau
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  ---
  > .. removed and tried to install the old driver (I probably did wrong):
  > sudo apt purge nvidia-*
  > sudo add-apt-repository ppa:graphics-drivers/ppa
  > sudo apt update
  > sudo apt install nvidia-current=304.131-0ubuntu3
  => Login-Loop
  ---
  > sudo apt purge nvidia-*
  > Additional Drivers > nouveau
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic" (NO Option=SYSTEMD?)
  => Auto-Login
  >  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
  
  What seemed to help was:
  
  > Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
4.4.0-47-generic (upstart)" (UPSTART!)
  => Auto-Login
  >  Firefox / Thunderbird => seem to work stable!
  => After half an Hour of testing:
  >  open Firefox (Hardware-Acceleration disabled) 
  => System-(Freeze)-Crash with Stripes-Screen
  -
  Because this is far more stable: 
  Changed Standard-Boot in Grub-2 to UpStart instead of SystemD
  ---
  > Terminal >
  sudo apt install upstart-sysv
  su
  sudo shutdown -r now
  ---
  For Roll-Back:
  > Terminal >
  sudo apt install systemd-sysv
  sudo update-initramfs -u
  sudo shutdown -r now
  --
  Sorry, 

[Touch-packages] [Bug 1644651] Re: tracker file system miner misses most files on Ubuntu 16.10

[Richard]

by using dconf org.freedesktop.Tracker.Miner.Files verbosity 'debug'
and running it
in syslog tracker-miner-f finds all top level entries in Documents
None of those directories are stored or traversed, however
tracker-miner-f[11630]:   Found 1 directories, ignored 0 directories

One can check:
grep --text tracker-miner-f /var/log/syslog | grep Processing | 
less
- lists entries looked at
grep --text tracker-miner-f /var/log/syslog | grep Found | less
- lists everything found for those entries

broken broken broken

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

Title:
  tracker file system miner misses most files on Ubuntu 16.10

Status in tracker package in Ubuntu:
  New

Bug description:
  This still works for Ubuntu 16.04 tracker 1.6.2-0ubuntu1.1

  On Ubuntu 16.10 tracker mining of the file system stops mid-way, most folders 
are not re-cursed into.
  - for a test system with 1 or 2 folders, it looks to be working

  REPRO
  Log in and start a terminal window
  1. Configure
  gsettings get org.freedesktop.Tracker.Miner.Files index-recursive-directories
  ['']
  - ensure that 300 or more folders are to be indexed
  - to make changes launch the app Search and Indexing, tab Locations
  2. Run
  tracker reset --hard <

[Touch-packages] [Bug 1644666] [NEW] Xorg crash

[Piraten-Kris Pseudonym]

Public bug reported:


Ubuntu 16.04.1 (Automatic Upgrade from 14.04)
My Onboard-Graphics (AMD-System, ASRock N68C-S UCC): 
  Nvidia C61 [GeForce 7025 / nForce 630a]
---
In the Past: 
=> System and Apps worked well with Auto-Login enabled.
To eliminate Hardware-Errors:
> Memtest
> Boot with Windows-XP
=> No Problems


Problems in short: Linux 4.4.0-47-generic (systemd) and (upstart)
-- 
1. nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop
2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen
---
I don't know in which Category to sort the Bugs
So this one is for the (Nr.1) Login-Loop (from tty-Terminal)
(I already filed another Bug-Report for the (Nr.2) System-(Freeze)-Crash with 
Stripes-Screen)


First Problem startet on 2016-Nov-05: => Login-Loop
---
I later found out, that one Day before, the following Auto-Updates had been 
installed:
---
libcurl3-gnutls(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
nvidia304(304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
nvidia-opencl-icd-304 (304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
libcurl3(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
---
After Shutdown, the next Computer-Start was stuck in a 
=> Login-Loop: After entering the correct Password, the Screen turns black for 
a Second, then the Login-Form shows up again.
---
I tried a few things, that did not help, like: 
> CTRL+F2 => Terminal > sudo ..
> apt autoclean
> apt clean
> apt autoremove
> apt update
> apt upgrade
> apt dist-upgrade
> shutdown -r now
> mv .Xauthority .Xauthority.alt
> shutdown -r now
> service lightdm restart
> shutdown -r now
> apt purge lightdm
> apt install lightdm
> shutdown -r now
> .. Boot into different Linux-Kernel, .. (upstart), 
> .. Boot into Recovery-Mode > .. > Repair > ..
> .. I also tried to install other nvidia-drivers, which, sadly, i did not 
> document. 
=> Did NOT work
---
Only Thing that helped was:
---
> sudo apt purge nvidia-*
> sudo shutdown -r now
=> (nouveau-Driver was automatically installed)
=> Auto-Login to Desktop


But then there was a second Problem:

When > starting Thunderbird, mostly at once, sometimes after > opening some 
E-Mail-Windows, another Error occurred:
=> System freeze for 3 Seconds, then Screen turned to Stripes-Wallpaper => 
Total (Freeze-)Crash
--
Later, even with DISabled Hardware-Acceleration, starting both, Firefox and 
Thunderbird led to the System-Crash.
(Sometimes, the System with nouveau booted and auto-logined into a Black Screen 
with a Mouse-Pointer. Nevertheless the System seemed to work and could be 
rebooted normally.)
---
> CTRL+ALT+F2 => did NOT work
> Magic Sys-Request (SysRQ): (ALT+PRINT)+ REISUB => did NOT work
> ping to IP => unreachable
---
After cold Reboot, i tried again to switch back from nouveau- to nvidia-Drivers
> Additional Drivers > Nvidia-304.132
=> Login-Loop
---
> sudo apt purge nvidia-*
> sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-nouveau
=> Auto-Login
>  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
---
> .. removed and tried to install the old driver (I probably did wrong):
> sudo apt purge nvidia-*
> sudo add-apt-repository ppa:graphics-drivers/ppa
> sudo apt update
> sudo apt install nvidia-current=304.131-0ubuntu3
=> Login-Loop
---
> sudo apt purge nvidia-*
> Additional Drivers > nouveau
> Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
> 4.4.0-47-generic" (NO Option=SYSTEMD?)
=> Auto-Login
>  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen

What seemed to help was:

> Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
> 4.4.0-47-generic (upstart)" (UPSTART!)
=> Auto-Login
>  Firefox / Thunderbird => seem to work stable!
=> After half an Hour of testing:
>  open Firefox (Hardware-Acceleration disabled) 
=> System-(Freeze)-Crash with Stripes-Screen
-
Because this is far more stable: 
Changed Standard-Boot in Grub-2 to UpStart instead of SystemD
---
> Terminal >
sudo apt install upstart-sysv
su
sudo shutdown -r now
---
For Roll-Back:
> Terminal >
sudo apt install systemd-sysv
sudo update-initramfs -u
sudo shutdown -r now
--
Sorry, don't know, what to try next ..

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.132  Fri Sep 16 11:02:09 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64

[Touch-packages] [Bug 1644664] [NEW] poltergeist

[giuseppe rosa]

Public bug reported:

I don't know much about computers, all I know I feel someone else is
controlling my computer


what is Xorg anyway?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Nov 24 22:55:17 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2163]
InstallationDate: Installed on 2016-11-23 (1 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=1bf97efe-efc4-48d6-b2ba-62340b386b39 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/04/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.42
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2163
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 29.40
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd12/04/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2163:rvr29.40:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion 15 Notebook PC
dmi.product.version: 098B1140410620180
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Nov 24 18:17:34 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   17900 
 vendor AUO
xserver.version: 2:1.18.4-0ubuntu0.2

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


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

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

Title:
  poltergeist

Status in xorg package in Ubuntu:
  New

Bug description:
  I don't know much about computers, all I know I feel someone else is
  controlling my computer


  what is Xorg anyway?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Nov 24 22:55:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2163]
  InstallationDate: Installed on 2016-11-23 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=1bf97efe-efc4-48d6-b2ba-62340b386b39 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1644657] Re: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Paul White]

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

** This bug has been marked a duplicate of bug 1642966
   package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1

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

Title:
  package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  I'm not sure where the issue is, system attempts to create a bug
  report on its own.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov 23 22:17:38 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2014-07-26 (852 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 045e:07b2 Microsoft Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=4715bf15-fd0e-426c-a9c3-06a6693e1294 ro
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (111 days ago)
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-07-26T18:51:07.729488

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1644657/+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 1644653] Re: tracker broken for KDE/X/lightdm

[Richard]

so the 'tracker' entries are created by follow or watch commands, so
that’s not a problem

crawling, however, is broken

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

Title:
  tracker broken for KDE/X/lightdm

Status in tracker package in Ubuntu:
  New

Bug description:
  tracker 1.6.2-0ubuntu1.1 on 16.04 could be made to work for KDE/X/lightdm
  - https://bugzilla.gnome.org/show_bug.cgi?id=769715#c12
  - DBUS_SESSION_BUS_ADDRESS has an incorrect value

  on 16.10 it’s beyond repair:

  dpkg --status tracker | egrep ^V
  Version: 1.10.0-1ubuntu1

  tracker reset hard && tracker daemon --start && tracker daemon 
--list-processes
  Found process ID 23118 for 'tracker-extract'
  Found process ID 23135 for 'tracker-store'
  Found process ID 23145 for 'tracker-miner-user-guides'
  Found process ID 23150 for 'tracker-miner-fs'
  Found process ID 23155 for 'tracker-miner-apps'
  - produces unhealthy tracker

  A healthy tracker has one or two tracker entries
  tracker daemon --start && tracker daemon --list-processes
  Starting miners…
✓ Userguides
✓ File System
✓ Applications
✓ Extractor
  Found 6 PIDs…
  Found process ID 4185 for 'tracker-store'
  Found process ID 4196 for 'tracker-miner-fs'
  Found process ID 4201 for 'tracker-miner-apps'
  Found process ID 4207 for 'tracker-extract'
  Found process ID 4229 for 'tracker'
  Found process ID 4921 for 'tracker-miner-user-guides'

  16/10/Unity 8 and 16.10/GNOME/Wayland are healthy, kde is not

  On login tracker kind of works, but after a while the 'tracker' entry
  dies and tracker is no longer with us.

  There are some new fancy race conditions, too:

  on reset occasionally
  (tracker daemon:13618): Tracker-CRITICAL **: Could not create proxy on the 
D-Bus session bus, Error calling StartServiceByName for 
org.freedesktop.Tracker1.Miner.Extract: Timeout was reached

  on list processes occasionally:
  Could not stat() file '/proc/21722', Error when getting information for file 
'/proc/21722': No such file or directoryFound 5 PIDs…

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: tracker 1.6.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 24 13:57:04 2016
  InstallationDate: Installed on 2016-08-26 (89 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: tracker
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1644653/+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 1644661] [NEW] Xorg crash

[Piraten-Kris Pseudonym]

Public bug reported:


Ubuntu 16.04.1 (Automatic Upgrade from 14.04)
My Onboard-Graphics (AMD-System, ASRock N68C-S UCC): 
  Nvidia C61 [GeForce 7025 / nForce 630a]
---
In the Past: 
=> System and Apps worked well with Auto-Login enabled.
To eliminate Hardware-Errors:
> Memtest
> Boot with Windows-XP
=> No Problems


Problems in short: Linux 4.4.0-47-generic (systemd) and (upstart)
-- 
1. nvidia-304.132-0ubuntu0.16.04.2 => Login-Loop
2. nouveau, Thunderbird, Firefox => System-(Freeze)-Crash with Stripes-Screen
---
I don't know in which Category to sort the Bugs
So this one ist for the (Nr.2) System-(Freeze)-Crash with Stripes-Screen
I will try to file another Bug-Report for the (Nr.1) Login-Loop (If it works 
from tty-Terminal)


First Problem startet on 2016-Nov-05: => Login-Loop
---
I later found out, that one Day before, the following Auto-Updates had been 
installed:
---
libcurl3-gnutls(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
nvidia304(304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
nvidia-opencl-icd-304 (304.131-0ubuntu3, 304.132-0ubuntu0.16.04.2)
libcurl3(7.47.0-1ubuntu2.1, 7.47.0-1ubuntu2.2)
---
After Shutdown, the next Computer-Start was stuck in a 
=> Login-Loop: After entering the correct Password, the Screen turns black for 
a Second, then the Login-Form shows up again.
---
I tried a few things, that did not help, like: 
> CTRL+F2 => Terminal > sudo ..
> apt autoclean
> apt clean
> apt autoremove
> apt update
> apt upgrade
> apt dist-upgrade
> shutdown -r now
> mv .Xauthority .Xauthority.alt
> shutdown -r now
> service lightdm restart
> shutdown -r now
> apt purge lightdm
> apt install lightdm
> shutdown -r now
> .. Boot into different Linux-Kernel, .. (upstart), 
> .. Boot into Recovery-Mode > .. > Repair > ..
> .. I also tried to install other nvidia-drivers, which, sadly, i did not 
> document. 
=> Did NOT work
---
Only Thing that helped was:
---
> sudo apt purge nvidia-*
> sudo shutdown -r now
=> (nouveau-Driver was automatically installed)
=> Auto-Login to Desktop


But then there was a second Problem:

When > starting Thunderbird, mostly at once, sometimes after > opening some 
E-Mail-Windows, another Error occurred:
=> System freeze for 3 Seconds, then Screen turned to Stripes-Wallpaper => 
Total (Freeze-)Crash
--
Later, even with DISabled Hardware-Acceleration, starting both, Firefox and 
Thunderbird led to the System-Crash.
(Sometimes, the System with nouveau booted and auto-logined into a Black Screen 
with a Mouse-Pointer. Nevertheless the System seemed to work and could be 
rebooted normally.)
---
> CTRL+ALT+F2 => did NOT work
> Magic Sys-Request (SysRQ): (ALT+PRINT)+ REISUB => did NOT work
> ping to IP => unreachable
---
After cold Reboot, i tried again to switch back from nouveau- to nvidia-Drivers
> Additional Drivers > Nvidia-304.132
=> Login-Loop
---
> sudo apt purge nvidia-*
> sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-nouveau
=> Auto-Login
>  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen
---
> .. removed and tried to install the old driver (I probably did wrong):
> sudo apt purge nvidia-*
> sudo add-apt-repository ppa:graphics-drivers/ppa
> sudo apt update
> sudo apt install nvidia-current=304.131-0ubuntu3
=> Login-Loop
---
> sudo apt purge nvidia-*
> Additional Drivers > nouveau
> Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
> 4.4.0-47-generic" (NO Option=SYSTEMD?)
=> Auto-Login
>  Firefox / Thunderbird => System-(Freeze)-Crash with Stripes-Screen

What seemed to help was:

> Boot > Grub-2 > "Erweiterte Optionen für Ubuntu" > "Ubuntu, mit Linux 
> 4.4.0-47-generic (upstart)" (UPSTART!)
=> Auto-Login
>  Firefox / Thunderbird => seem to work stable!
=> After half an Hour of testing:
>  open Firefox (Hardware-Acceleration disabled) 
=> System-(Freeze)-Crash with Stripes-Screen
-
Because this is far more stable: 
Changed Standard-Boot in Grub-2 to UpStart instead of SystemD
---
> Terminal >
sudo apt install upstart-sysv
su
sudo shutdown -r now
---
For Roll-Back:
> Terminal >
sudo apt install systemd-sysv
sudo update-initramfs -u
sudo shutdown -r now
--
Sorry, don't know, what to try next ..

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Nov 24 23:32:54 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu

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

[zacktu]

I have the same symptoms as described here after upgrading from 14.04 to
16.04.  I have always been a vi user.  On this system vi links
eventually to /usr/bin/vim.tiny, and I get the same error messages as
described here.

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

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

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

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

Status in vim package in Ubuntu:
  Expired

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

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

  Now I get the following error:

  [[[ BEGIN PASTE ]]]

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

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

  [[[ END PASTE ]]]

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

  
  [[[ BEGIN PASTE ]]]

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

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

  [[[ END PASTE ]]]

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

[Touch-packages] [Bug 1644657] [NEW] package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Marc Lalonde]

Public bug reported:

I'm not sure where the issue is, system attempts to create a bug report
on its own.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
Uname: Linux 4.4.0-49-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Nov 23 22:17:38 2016
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2014-07-26 (852 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:07dc Intel Corp. 
 Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
 Bus 001 Device 002: ID 045e:07b2 Microsoft Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=4715bf15-fd0e-426c-a9c3-06a6693e1294 ro
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: cups
Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-08-04 (111 days ago)
modified.conffile..etc.default.cups:
 # Cups configure options
 
 # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
 # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
 # LOAD_LP_MODULE=yes
mtime.conffile..etc.default.cups: 2014-07-26T18:51:07.729488

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


** Tags: amd64 apport-package need-duplicate-check package-from-proposed xenial

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

Title:
  package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  I'm not sure where the issue is, system attempts to create a bug
  report on its own.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Nov 23 22:17:38 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2014-07-26 (852 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 045e:07b2 Microsoft Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=4715bf15-fd0e-426c-a9c3-06a6693e1294 ro
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (111 days ago)
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-07-26T18:51:07.729488

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1644657/+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 1463023] Re: systemd Timed out waiting for device swap and file system check

[Alexander Adam]

Ah, I'm sorry. I just realized this is rather this issue:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/953875

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

Title:
  systemd Timed out waiting for device swap and file system check

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  
  My Ubuntu 15.04 did not start --or took so long that I switched back to 
upstart!

  ISSUE: (systemd during the boot)

  Timed out waitingfor device dev-disk-by\x2duuid-... (swap)
  Dependency failed for /dev/disk/by-uuid/... (swap)
  Dependency failed for Swap.
  Timed out waiting for device dev-sdaX.device(swap)
  Dependency failed for Swap Partition.
  Failed to start udev Wait for Complete Device Initialization.
  See "systemctl status systemd-udev-settle.service" for details.
  Starting File System Check on Root Device...
  Starting Copy rules generated while the root was ro...
  (1 of 2) A start job is running for File System Check on Root Device (3min 
28s / no limit)
  ...
   No tainted 3.19.0-18-generic #18-Ubuntu
  "echo 0> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  INFO: task systemd-udevd:336 blocked for more than 120 seconds.
  ...
  INFO: task systemd-udevd:338 blocked for more than 120 seconds.
  ...
  INFO: task systemd-udevd:346 blocked for more than 120 seconds.
  ...
  (1 of 2) A start job is running for File System Check on Root Device (4min 3s 
/ no limit)

  WORKAROUND:

  apt-get -qq -y install upstart-sysv # switch back to upstart
  
http://linux.softpedia.com/blog/Ubuntu-15-04-Users-Can-Switch-Off-Systemd-and-Use-Upstart-479373.shtml
  P.S. don't ask me to go back to systemd-sysv... I am fine with upstart

  TECHNICAL DETAILS:

  $ lsb_release -r
  Release:  15.04

  $ uname -r
  3.19.0-18-generic

  $ sudo dmidecode -s system-product-name
  MacBookPro8,2

  $ grep "^GRUB_CMDLINE_LINUX_DEFAULT" /etc/default/grub
  GRUB_CMDLINE_LINUX_DEFAULT="transparent_hugepage=always intel_iommu=on 
acpi_irq_nobalance cgroup_enable=memory swapaccount=1 libata.force=noncq 
modeset=1 hybridopts=ON,IGD,OFF i915.modeset=0 radeon.modeset=1 radeon.dpm=1 
radeon.audio=1 i915.lvds_channels=2 quirks.mbp_force_ahci=1 
acpi_backlight=vendor reboot=pci"

  $ cat /etc/fstab
  #
  # / was on /dev/sda5 during installation
  UUID=6619a7e9-4b94-4e9b-8dbe-4110f89dde74 /   ext4
errors=remount-ro 0   1
  # swap was on /dev/sda6 during installation
  UUID=813e9dc2-c678-4959-ac89-e6660f886942 noneswapsw  
0   0

  # lsblk -f
  NAME   FSTYPE  LABELUUID MOUNTPOINT
  sda  
  ├─sda1 vfatEFI  67E3-17ED
  ├─sda2 hfsplus Macintosh HD 2ba5bbc1-fff0-36ea-ade4-140386274279 
  ├─sda3 hfsplus Recovery HD  9e776f16-ceb4-37e6-b4ce-4e75c1db5444 
  ├─sda4   
  ├─sda5 ext4 6619a7e9-4b94-4e9b-8dbe-4110f89dde74 /
  └─sda6 swap 813e9dc2-c678-4959-ac89-e6660f886942 [SWAP]
  sr0   

  # blkid 
  /dev/sda1: LABEL="EFI" UUID="67E3-17ED" TYPE="vfat" PARTLABEL="EFI System 
Partition" PARTUUID="5d71ff71-9843-473d-90e7-4c780c8a494d"
  /dev/sda2: UUID="2ba5bbc1-fff0-36ea-ade4-140386274279" LABEL="Macintosh HD" 
TYPE="hfsplus" PARTLABEL="Macintosh HD" 
PARTUUID="4e4c2249-24f8-4229-9325-d4aafd7ac093"
  /dev/sda3: UUID="9e776f16-ceb4-37e6-b4ce-4e75c1db5444" LABEL="Recovery HD" 
TYPE="hfsplus" PARTLABEL="Recovery HD" 
PARTUUID="a986e3e1-ed3b-44bb-a75b-87b54434380d"
  /dev/sda5: UUID="6619a7e9-4b94-4e9b-8dbe-4110f89dde74" TYPE="ext4" 
PARTUUID="9d860cb1-1334-4f79-a07a-01b8818c4aab"
  /dev/sda6: UUID="813e9dc2-c678-4959-ac89-e6660f886942" TYPE="swap" 
PARTUUID="bf1271f6-8d51-4510-8979-666c9546f1f3"
  /dev/sda4: PARTUUID="2b731a42-bd29-4548-8f0e-a9889ee9486b"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1463023/+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 1644653] [NEW] tracker broken for KDE/X/lightdm

[Richard]

Public bug reported:

tracker 1.6.2-0ubuntu1.1 on 16.04 could be made to work for KDE/X/lightdm
- https://bugzilla.gnome.org/show_bug.cgi?id=769715#c12
- DBUS_SESSION_BUS_ADDRESS has an incorrect value

on 16.10 it’s beyond repair:

dpkg --status tracker | egrep ^V
Version: 1.10.0-1ubuntu1

tracker reset hard && tracker daemon --start && tracker daemon --list-processes
Found process ID 23118 for 'tracker-extract'
Found process ID 23135 for 'tracker-store'
Found process ID 23145 for 'tracker-miner-user-guides'
Found process ID 23150 for 'tracker-miner-fs'
Found process ID 23155 for 'tracker-miner-apps'
- produces unhealthy tracker

A healthy tracker has one or two tracker entries
tracker daemon --start && tracker daemon --list-processes
Starting miners…
  ✓ Userguides
  ✓ File System
  ✓ Applications
  ✓ Extractor
Found 6 PIDs…
Found process ID 4185 for 'tracker-store'
Found process ID 4196 for 'tracker-miner-fs'
Found process ID 4201 for 'tracker-miner-apps'
Found process ID 4207 for 'tracker-extract'
Found process ID 4229 for 'tracker'
Found process ID 4921 for 'tracker-miner-user-guides'

16/10/Unity 8 and 16.10/GNOME/Wayland are healthy, kde is not

On login tracker kind of works, but after a while the 'tracker' entry
dies and tracker is no longer with us.

There are some new fancy race conditions, too:

on reset occasionally
(tracker daemon:13618): Tracker-CRITICAL **: Could not create proxy on the 
D-Bus session bus, Error calling StartServiceByName for 
org.freedesktop.Tracker1.Miner.Extract: Timeout was reached

on list processes occasionally:
Could not stat() file '/proc/21722', Error when getting information for file 
'/proc/21722': No such file or directoryFound 5 PIDs…

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: tracker 1.6.2-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Nov 24 13:57:04 2016
InstallationDate: Installed on 2016-08-26 (89 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: tracker
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  tracker broken for KDE/X/lightdm

Status in tracker package in Ubuntu:
  New

Bug description:
  tracker 1.6.2-0ubuntu1.1 on 16.04 could be made to work for KDE/X/lightdm
  - https://bugzilla.gnome.org/show_bug.cgi?id=769715#c12
  - DBUS_SESSION_BUS_ADDRESS has an incorrect value

  on 16.10 it’s beyond repair:

  dpkg --status tracker | egrep ^V
  Version: 1.10.0-1ubuntu1

  tracker reset hard && tracker daemon --start && tracker daemon 
--list-processes
  Found process ID 23118 for 'tracker-extract'
  Found process ID 23135 for 'tracker-store'
  Found process ID 23145 for 'tracker-miner-user-guides'
  Found process ID 23150 for 'tracker-miner-fs'
  Found process ID 23155 for 'tracker-miner-apps'
  - produces unhealthy tracker

  A healthy tracker has one or two tracker entries
  tracker daemon --start && tracker daemon --list-processes
  Starting miners…
✓ Userguides
✓ File System
✓ Applications
✓ Extractor
  Found 6 PIDs…
  Found process ID 4185 for 'tracker-store'
  Found process ID 4196 for 'tracker-miner-fs'
  Found process ID 4201 for 'tracker-miner-apps'
  Found process ID 4207 for 'tracker-extract'
  Found process ID 4229 for 'tracker'
  Found process ID 4921 for 'tracker-miner-user-guides'

  16/10/Unity 8 and 16.10/GNOME/Wayland are healthy, kde is not

  On login tracker kind of works, but after a while the 'tracker' entry
  dies and tracker is no longer with us.

  There are some new fancy race conditions, too:

  on reset occasionally
  (tracker daemon:13618): Tracker-CRITICAL **: Could not create proxy on the 
D-Bus session bus, Error calling StartServiceByName for 
org.freedesktop.Tracker1.Miner.Extract: Timeout was reached

  on list processes occasionally:
  Could not stat() file '/proc/21722', Error when getting information for file 
'/proc/21722': No such file or directoryFound 5 PIDs…

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: tracker 1.6.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 24 13:57:04 2016
  InstallationDate: Installed on 2016-08-26 (89 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  

[Touch-packages] [Bug 1644651] [NEW] tracker file system miner misses most files on Ubuntu 16.10

[Richard]

Public bug reported:

This still works for Ubuntu 16.04 tracker 1.6.2-0ubuntu1.1

On Ubuntu 16.10 tracker mining of the file system stops mid-way, most folders 
are not re-cursed into.
- for a test system with 1 or 2 folders, it looks to be working

REPRO
Log in and start a terminal window
1. Configure
gsettings get org.freedesktop.Tracker.Miner.Files index-recursive-directories
['']
- ensure that 300 or more folders are to be indexed
- to make changes launch the app Search and Indexing, tab Locations
2. Run
tracker reset --hard <

[Touch-packages] [Bug 1643239] Re: Xorg crash on compiz login, with Intel 945

[Henry Wertz]

>I haven't verified this yet, but it looks from the XOrg log like these
systems are booting into dual head (with the SVideo out on head 2),
2128x800 total.

Suspicion confirmed, the "phantom" second head was causing causing
compiz to fail due to the 2128 pixel width exceeding the 2048 pixel
texture width limit of this chip.  I booted up a D620, and verified
Flashback (Compiz) failed.  I logged in with Flashback (Metacity), went
to Display control panel, hit Apply, and logged back out.  I could then
log into Flashback (Compiz) fine, it loaded quickly and everything
worked fine.  The display setting "stuck" fine so everything worked
after a reboot as well.

I guess you can close this bug!  Maybe the info will remain useful for
someone who runs into a similar issue.  Thanks for the good work!

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

Title:
  Xorg crash on compiz login, with Intel 945

Status in xorg package in Ubuntu:
  New

Bug description:
  I went to install Ubuntu (via systemback) onto some Dell D620s, and found 
"Gnome Flashback (compiz)" crashes back to login prompt, while "Gnome Flashback 
(Metacity)" does not.  The attached logs reflect booting up, (attempting to) 
log in with Flashback (compiz) then logging in with Flashback (Metacity) to 
file a bug report.  This may be chipset-specific, as I have several other 
rather antiquated systems:
  Intel 865-based (Compaq DC5000): Works. (Using LLVMPipe -- this chip is 
missing a few OpenGL features compiz requires.)

  Intel 915-based (Dell Inspiron 2200): Works.
  Intel 945-based (Dell Latitude D620): Crashes to login prompt (this is the 
machine in this bug report.)
  Intel 965-based (Dell Latitude 755?): Works.
  Intel G35-based (slightly newer Dell Latitude 755): Works.

  I can rule out software differences; since I knew Compiz worked on a
  915, I assumed I'd screwed up my systemback LiveUSB somehow, and test-
  ran it on the D620, 2200, and one of the 755s, and it worked on the
  2200 and 755.

  Left up to me, I'd categorize this as severity "low", I'm just setting
  these to Flashback Metacity and then stability seems fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  BootLog: SB@: clean, 208182/2244608 files, 1302234/8973568 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Nov 19 10:12:40 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [1028:01c2]
 Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated 
Graphics Controller [1028:01c2]
  InstallationDate: Installed on 2016-04-29 (203 days ago)
  InstallationMedia:
   
  MachineType: Dell Inc. Latitude D620
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=702f73f8-ca72-4102-9c59-48f182329bfa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0TD761
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd05/16/2008:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0TD761:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Nov 19 10:12:01 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: 

[Touch-packages] [Bug 1463023] Re: systemd Timed out waiting for device swap and file system check

[Alexander Adam]

I just found out that running "cryptdisks_start cryptswap1" allows me to 
activate the swap with swapon.
So I guess the UUID references are fine and there is some systemd-crypto-issue 
going on.

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

Title:
  systemd Timed out waiting for device swap and file system check

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  
  My Ubuntu 15.04 did not start --or took so long that I switched back to 
upstart!

  ISSUE: (systemd during the boot)

  Timed out waitingfor device dev-disk-by\x2duuid-... (swap)
  Dependency failed for /dev/disk/by-uuid/... (swap)
  Dependency failed for Swap.
  Timed out waiting for device dev-sdaX.device(swap)
  Dependency failed for Swap Partition.
  Failed to start udev Wait for Complete Device Initialization.
  See "systemctl status systemd-udev-settle.service" for details.
  Starting File System Check on Root Device...
  Starting Copy rules generated while the root was ro...
  (1 of 2) A start job is running for File System Check on Root Device (3min 
28s / no limit)
  ...
   No tainted 3.19.0-18-generic #18-Ubuntu
  "echo 0> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  INFO: task systemd-udevd:336 blocked for more than 120 seconds.
  ...
  INFO: task systemd-udevd:338 blocked for more than 120 seconds.
  ...
  INFO: task systemd-udevd:346 blocked for more than 120 seconds.
  ...
  (1 of 2) A start job is running for File System Check on Root Device (4min 3s 
/ no limit)

  WORKAROUND:

  apt-get -qq -y install upstart-sysv # switch back to upstart
  
http://linux.softpedia.com/blog/Ubuntu-15-04-Users-Can-Switch-Off-Systemd-and-Use-Upstart-479373.shtml
  P.S. don't ask me to go back to systemd-sysv... I am fine with upstart

  TECHNICAL DETAILS:

  $ lsb_release -r
  Release:  15.04

  $ uname -r
  3.19.0-18-generic

  $ sudo dmidecode -s system-product-name
  MacBookPro8,2

  $ grep "^GRUB_CMDLINE_LINUX_DEFAULT" /etc/default/grub
  GRUB_CMDLINE_LINUX_DEFAULT="transparent_hugepage=always intel_iommu=on 
acpi_irq_nobalance cgroup_enable=memory swapaccount=1 libata.force=noncq 
modeset=1 hybridopts=ON,IGD,OFF i915.modeset=0 radeon.modeset=1 radeon.dpm=1 
radeon.audio=1 i915.lvds_channels=2 quirks.mbp_force_ahci=1 
acpi_backlight=vendor reboot=pci"

  $ cat /etc/fstab
  #
  # / was on /dev/sda5 during installation
  UUID=6619a7e9-4b94-4e9b-8dbe-4110f89dde74 /   ext4
errors=remount-ro 0   1
  # swap was on /dev/sda6 during installation
  UUID=813e9dc2-c678-4959-ac89-e6660f886942 noneswapsw  
0   0

  # lsblk -f
  NAME   FSTYPE  LABELUUID MOUNTPOINT
  sda  
  ├─sda1 vfatEFI  67E3-17ED
  ├─sda2 hfsplus Macintosh HD 2ba5bbc1-fff0-36ea-ade4-140386274279 
  ├─sda3 hfsplus Recovery HD  9e776f16-ceb4-37e6-b4ce-4e75c1db5444 
  ├─sda4   
  ├─sda5 ext4 6619a7e9-4b94-4e9b-8dbe-4110f89dde74 /
  └─sda6 swap 813e9dc2-c678-4959-ac89-e6660f886942 [SWAP]
  sr0   

  # blkid 
  /dev/sda1: LABEL="EFI" UUID="67E3-17ED" TYPE="vfat" PARTLABEL="EFI System 
Partition" PARTUUID="5d71ff71-9843-473d-90e7-4c780c8a494d"
  /dev/sda2: UUID="2ba5bbc1-fff0-36ea-ade4-140386274279" LABEL="Macintosh HD" 
TYPE="hfsplus" PARTLABEL="Macintosh HD" 
PARTUUID="4e4c2249-24f8-4229-9325-d4aafd7ac093"
  /dev/sda3: UUID="9e776f16-ceb4-37e6-b4ce-4e75c1db5444" LABEL="Recovery HD" 
TYPE="hfsplus" PARTLABEL="Recovery HD" 
PARTUUID="a986e3e1-ed3b-44bb-a75b-87b54434380d"
  /dev/sda5: UUID="6619a7e9-4b94-4e9b-8dbe-4110f89dde74" TYPE="ext4" 
PARTUUID="9d860cb1-1334-4f79-a07a-01b8818c4aab"
  /dev/sda6: UUID="813e9dc2-c678-4959-ac89-e6660f886942" TYPE="swap" 
PARTUUID="bf1271f6-8d51-4510-8979-666c9546f1f3"
  /dev/sda4: PARTUUID="2b731a42-bd29-4548-8f0e-a9889ee9486b"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1463023/+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 1463243] Re: 20KB write to ~/.config/dconf/user on caps lock or num lock

[Launchpad Bug Tracker]

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

** Changed in: d-conf (Ubuntu)
   Status: New => Confirmed

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

Title:
  20KB write to ~/.config/dconf/user on caps lock or num lock

Status in d-conf package in Ubuntu:
  Confirmed

Bug description:
  Whenever I press Caps Lock or Num Lock, a 20KB ~/.config/dconf/user
  file is written.

  Someone else already reported this in a question with more details::
  https://answers.launchpad.net/ubuntu/+source/d-conf/+question/178204

  Ubuntu MATE 15.04 64-bit
  Linux 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 
x86_64 x86_64 GNU/Linux

  dconf 0.22.0-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1463243/+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 1463243] Re: 20KB write to ~/.config/dconf/user on caps lock or num lock

[johnny lee]

This bug still continues/exists on xubuntu 16.04 with dconf-service. It
happens on my machine when I open more than one instance of mousepad,
the I/O disk write increments and the HDD led doesn't stop blinking,
until I close one of the instances of mousepad.

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

Title:
  20KB write to ~/.config/dconf/user on caps lock or num lock

Status in d-conf package in Ubuntu:
  Confirmed

Bug description:
  Whenever I press Caps Lock or Num Lock, a 20KB ~/.config/dconf/user
  file is written.

  Someone else already reported this in a question with more details::
  https://answers.launchpad.net/ubuntu/+source/d-conf/+question/178204

  Ubuntu MATE 15.04 64-bit
  Linux 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 
x86_64 x86_64 GNU/Linux

  dconf 0.22.0-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1463243/+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 1619616] Re: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

[LocutusOfBorg]

why this patch is not upstream? I don't see it in the google protobuf github 
repo
https://github.com/google/protobuf/blob/master/src/google/protobuf/stubs/common.cc

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

Title:
  Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT)

Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  Fix Released

Bug description:
  builds with 3.0.0-7, then has one failing test:

  test 19
Start 19: Protobuf-can-be-reloaded

  19: Test command: 
/<>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf
  19: Test timeout computed to be: 9.99988e+06
  19/19 Test #19: Protobuf-can-be-reloaded 
..***Exception: SegFault 0.17 sec

  95% tests passed, 1 tests failed out of 19

  Total Test time (real) = 125.73 sec

  The following tests FAILED:
19 - Protobuf-can-be-reloaded (SEGFAULT)
  Errors while running CTest
  Makefile:85: recipe for target 'test' failed
  make[2]: *** [test] Error 8

  ~

  The reason this matters:

  The principle downstream from Mir (Unity8) loads Mir as one of a
  number of plugins, several of which use protobuf. That means that
  we're prone to being loaded, unloaded and reloaded and don't have
  control of this.

  We've encountered problems in this scenario before that have been
  traced to protobuf so we have a specific test. But other Unity8
  plugins may encounter the same issue.

  As seen in comment #25 the problem here is entirely down to a change
  in the behavior of libmirprotobuf-lite - it no longer unloads on
  dlclose().

  This is only a problem because there is code (see patch in comment
  #20) that assumes that the library will not be used after a call to
  google::protobuf::ShutdownProtobufLibrary() unless it is reloaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1619616/+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 1644624] Re: lightdm does not start after upgrade from 14.04.5 to 16.04.1

[Robert Ancell]

This isn't a LightDM problem, it's either your script is not valid or X
/ your video drivers have changed.

I'd suggest you make your script not abort when xrandr fails.

** Package changed: lightdm (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  lightdm does not start after upgrade from 14.04.5 to 16.04.1

Status in xorg-server package in Ubuntu:
  New

Bug description:
  After upgrading from 14.04.5 to 16.04.1 lightdm does not start. Only
  error I could find reported was:

  [+0.19s] DEBUG: Launching process 1927: /usr/share/lightdm_xrandr
  [+0.21s] DEBUG: Process 1927 exited with return value 1
  [+0.21s] DEBUG: Seat seat0: Exit status of /usr/share/lightdm_xrandr: 1
  [+0.21s] DEBUG: Seat seat0: Stopping display server due to failed setup script
  [+0.21s] DEBUG: Sending signal 15 to process 1922
  [+0.59s] DEBUG: Process 1922 exited with return value 0

  Looking at /usr/share/lightdm_xrandr output:
  #!/bin/sh
  xrandr --output Virtual1 --primary --mode 1920x1200

  # /usr/share/lightdm_xrandr
  xrandr: Failed to get size of gamma for output default
  warning: output Virtual1 not found; ignoring

  # xrandr --listproviders
  Providers: number : 0

  # xrandr --listmonitors
  xrandr: Failed to get size of gamma for output default
  Monitors: 1
   0: +*default 1920/508x1200/317+0+0  default

  Changing
   xrandr --output Virtual1 --primary --mode 1920x1200

  to
   xrandr --output default --primary --mode 1920x1200

  
  leads to display of 1024x768 on a monitor capable of 1920x1200. Doesn't look 
nice!
  It worked with 14.04.5 seamless. I'd never had to think of it until upgrading!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 24 19:19:53 2016
  InstallationDate: Installed on 2014-02-10 (1017 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  LightdmConfig:
   [Seat:*]
   display-setup-script=/usr/share/lightdm_xrandr
   greeter-session=lightdm-gtk-greeter
   user-session=xubuntu
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-11-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1644624/+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 1644643] [NEW] apt failed to run due to link time reference error

[zhiting zhu]

Public bug reported:

After update apt and its related library to 1.2.15 from 1.2.10ubuntu1, I
get following message when I try to invoke apt:

apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt-
private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0 not
defined in file libapt-pkg.so.5.0 with link time reference

1.2.10 do not have this problem. Now I manually downgrade from 1.2.15 to
1.2.10 to solve this problem.

Ubuntu release: 
Description:Ubuntu 16.04.1 LTS
Release:16.04

what I expect to happen: apt would show the helper message
what happened instead: apt shows me the line on above

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

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

Title:
  apt failed to run due to link time reference error

Status in apt package in Ubuntu:
  New

Bug description:
  After update apt and its related library to 1.2.15 from 1.2.10ubuntu1,
  I get following message when I try to invoke apt:

  apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt-
  private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0
  not defined in file libapt-pkg.so.5.0 with link time reference

  1.2.10 do not have this problem. Now I manually downgrade from 1.2.15
  to 1.2.10 to solve this problem.

  Ubuntu release: 
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  what I expect to happen: apt would show the helper message
  what happened instead: apt shows me the line on above

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1644643/+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 1176046] Re: isc-dhcp dhclient listens on extra random ports

[Eric Desrochers]

The following debian[1] forum indicate that failover and tracing need to
be disabled in order to disable NSUPDATE as well and I confirmed the
steps, otherwise the build fails.

I'm not too sure if this is the right way to fix this problem as I don't
want to introduce new issues that will impact other users.

Additionally, Debian had to re-enable NSUPDATE after disabling it due to
some issues

* Reenable NSUPDATE (closes: #798237)

Will need to look at it more carefully, and talk with the foundation
team maybe.

[1] - http://forums.debian.net/viewtopic.php?f=10=95273

Eric

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  
  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient   
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+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 1638338] Re: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options)

[Colin Watson]

** Also affects: openssh via
   https://bugzilla.mindrot.org/show_bug.cgi?id=2643
   Importance: Unknown
   Status: Unknown

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

Title:
  Can not ssh with tr_TR.UTF-8 locales (Bad configuration options)

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Triaged

Bug description:
  I can not ssh to any host with Turkish locales.

  What I expected to happen:

  I expected that 'ssh some_host' command would successfully run.

  What actually happened

  'ssh some_host' command failed with an error.

  Steps to produce:

  1. Open a terminal
  2. Run LANG=tr_TR.UTF-8 ssh some_host

  If I run ssh with tr_TR.UTF-8 locale, the first error I get is:

  $HOME/.ssh/config: line 7: Bad configuration option: Identityfile
  $HOME/.ssh/config: terminating, 1 bad configuration options

  If I commend IdentityFile option from $HOME/.ssh/config file and re-
  run the command, I get this:

  debug1: Reading configuration data ~/.ssh/config
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  /etc/ssh/ssh_config: line 55: Bad configuration option: 
gssapIauthentication
  /etc/ssh/ssh_config: line 56: Bad configuration option: 
gssapIdelegatecredentials
  /etc/ssh/ssh_config: terminating, 2 bad configuration options

  If I commend GSSAPIAuthentication and GSSAPIDelegateCredentials
  option, I can ssh to a host.

  So to ssh to a host with tr_TR.UTF-8 locale, one must commend out
  IdentityFile, if it is used, GSSAPIAuthentication and
  GSSAPIDelegateCredentials optons.

  Workaround:

  LC_ALL=C ssh some_host

  
  LC_ALL=C apt-cache policy openssh-client
  openssh-client:
Installed: 1:7.3p1-1
Candidate: 1:7.3p1-1
Version table:
   *** 1:7.3p1-1 500
  500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  LC_ALL=C lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: openssh-client 1:7.3p1-1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 19:37:35 2016
  InstallationDate: Installed on 2016-10-23 (9 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.3p1 Ubuntu-1, OpenSSL 1.0.2g  1 Mar 2016
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1638338/+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 1643931] Re: Security problem with Super User Authorization

[Steve Beattie]

Thanks for taking the time to report your issue. In this case, the tools
you're highlighting do not use sudo, but instead use policykit-1 to
verify privileges. In order to require the root password instead of your
user's password to operate those utilities, you'll need to modify your
policykit configuration to do so. Specifically, you'll need to override
the configuration in /etc/polkit-1/localauthority.conf.d/51-ubuntu-
admin.conf ; you can do this by creating a conf file that begins with a
higher number in /etc/polkit-1/localauthority.conf.d/ (e.g. 60-local-
admin.conf). Copying the contents of
/etc/polkit-1/localauthority.conf.d/50-localauthority.conf into it
(specifically setting 'AdminIdentities=unix-user:0') will cause
policykit to require the root password when authenticating for
administrative privileges.

You can verify this by using pkexec as well as the other tools you
listed above; e.g. "pkexec date" should require the root password after
changing your configuration.

And of course, you'll want to be careful making changes to your
policykit configuration, as you could be creating a security exposure
for yourself.

** Package changed: sudo (Ubuntu) => policykit-1 (Ubuntu)

** Changed in: policykit-1 (Ubuntu)
   Status: New => Invalid

** Information type changed from Private Security to Public

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

Title:
  Security problem with Super User Authorization

Status in policykit-1 package in Ubuntu:
  Invalid

Bug description:
  luca@pc-sala:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  luca@pc-sala:~$ 

  luca@pc-sala:~$ apt-cache policy sudo
  sudo:
Instalados: 1.8.16-0ubuntu1.2
Candidato:  1.8.16-0ubuntu1.2
Tabla de versión:
   *** 1.8.16-0ubuntu1.2 500
  500 http://pe.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.8.16-0ubuntu1 500
  500 http://pe.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  luca@pc-sala:~$ 

  On my system I have 3 accounts (me, my wife and my son), My account is the 
only that can use SUDO, the others are desktop users.
  I need to limit the access to my son (5 years old), so I had to put the 
password to my login, but my password was very strong: large and complicate. 
Otherwise I need to use sometimes SUDO (truecrypt, rsync with other devices, 
etc.).
  In order to simplify my login and keep the ability to use SUDO I activated 
the "targetpw" flag in sudoers, so now my login password is quite easy and ROOT 
account has the strong password.
  It works, programs like synaptic, sudo, gksu and others accept the root 
password, but I found a very very strange behaviours in some programs, for 
example:

  a) users-admin
  b) gnome-language-selector
  c) lightdm-gtk-greeter-settings-pkexec

  Those programs perform admin tasks and I suppose that when they ask for the 
password authorization they need the root password.
  No! They want my personal account password, the root password is not accepted.

  I think that this is not right, because my system now has a security
  weakness, and I don't know how many other programs have the same
  behaviour. This could be a serious security breach.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1643931/+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 1176046] Re: isc-dhcp dhclient listens on extra random ports

[Eric Desrochers]

Applying the Xenial "disable-nsupdate.patch" result in a failling build
in Trusty.

/<>/server/dhcpd.c:498: undefined reference to `trace_ddns_init'
dhcpd-failover.o: In function `dhcp_failover_process_bind_update':
/<>/server/failover.c:5225: undefined reference to `ddns_removals'

Seems like failover rely on this to work properly.

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  
  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient   
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+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 1439687] Re: Can not report bug: SSL Certificate Verify Failure

[Numan Demirdöğen]

If I am not rude, may I ask what the status of this bug is? I think the
severity of this bug is high because when reporting a bug, I can not
fill a bug report with enough relevant information that is collected by
apport. If we want good bug reports from anyone, this bug is an
hindrance to this.

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

Title:
  Can not report bug: SSL Certificate Verify Failure

Status in apport package in Ubuntu:
  Confirmed
Status in whoopsie package in Ubuntu:
  Invalid

Bug description:
  I called apport with apport-bug linux, because I wanted to report a
  kernel bug.

  However I could not send the logs to launchpad because of the
  following error message:

  

  Distribution: Kubuntu 15.04 64 Bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1439687/+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 1644626] [NEW] Login does not work with krb5 after upgrade to 16.04.1 from 14.04.5

[Thomas Schweikle]

Public bug reported:

After having managed to have a 1024x768 lightdm screen displayed begging
to login, I've tried and being prompted with "You where logged in with
cached credentials".

Not really: I am logged in, but immediately thrown out again. It is
impossible to work!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.2-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Nov 24 19:32:58 2016
InstallationDate: Installed on 2014-02-10 (1017 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
IpRoute:
 default via 10.160.0.1 dev eth1 
 10.160.0.0/16 dev eth1  proto kernel  scope link  src 10.160.2.45 
 169.254.0.0/16 dev eth0  scope link  metric 1000 
 172.18.8.0/24 dev eth0  proto kernel  scope link  src 172.18.8.141
IwConfig:
 lono wireless extensions.
 
 eth1  no wireless extensions.
 
 eth0  no wireless extensions.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: Upgraded to xenial on 2016-11-24 (0 days ago)
ftp_proxy: http://proxy01-muc.bfs.de:8080/
http_proxy: http://proxy01-muc.bfs.de:8080/
nmcli-con:
 NAME   UUID  TYPE  
  TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH 
 Kabelnetzwerkverbindung 1  c6be5d5a-c232-41e9-ae61-28f7974f30a9  
802-3-ethernet  1397215392  Fr 11 Apr 2014 13:23:12 CEST  yes  0
 no/org/freedesktop/NetworkManager/Settings/0  no  --   
   -- --
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
 eth0ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
 eth1ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----   
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.2connected  started  none  enabled enabled  
enabled  enabled  enabled
no_proxy: 127.0.0.1, localhost

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Login does not work with krb5 after upgrade to 16.04.1 from 14.04.5

Status in network-manager package in Ubuntu:
  New

Bug description:
  After having managed to have a 1024x768 lightdm screen displayed
  begging to login, I've tried and being prompted with "You where logged
  in with cached credentials".

  Not really: I am logged in, but immediately thrown out again. It is
  impossible to work!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 24 19:32:58 2016
  InstallationDate: Installed on 2014-02-10 (1017 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  IpRoute:
   default via 10.160.0.1 dev eth1 
   10.160.0.0/16 dev eth1  proto kernel  scope link  src 10.160.2.45 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   172.18.8.0/24 dev eth0  proto kernel  scope link  src 172.18.8.141
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-11-24 (0 days ago)
  ftp_proxy: http://proxy01-muc.bfs.de:8080/
  http_proxy: http://proxy01-muc.bfs.de:8080/
  nmcli-con:
   NAME   UUID  TYPE
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH 
   Kabelnetzwerkverbindung 1  c6be5d5a-c232-41e9-ae61-28f7974f30a9  
802-3-ethernet  1397215392  Fr 11 Apr 2014 13:23:12 CEST  yes  0
  

[Touch-packages] [Bug 1644624] [NEW] lightdm does not start after upgrade from 14.04.5 to 16.04.1

[Thomas Schweikle]

Public bug reported:

After upgrading from 14.04.5 to 16.04.1 lightdm does not start. Only
error I could find reported was:

[+0.19s] DEBUG: Launching process 1927: /usr/share/lightdm_xrandr
[+0.21s] DEBUG: Process 1927 exited with return value 1
[+0.21s] DEBUG: Seat seat0: Exit status of /usr/share/lightdm_xrandr: 1
[+0.21s] DEBUG: Seat seat0: Stopping display server due to failed setup script
[+0.21s] DEBUG: Sending signal 15 to process 1922
[+0.59s] DEBUG: Process 1922 exited with return value 0

Looking at /usr/share/lightdm_xrandr output:
#!/bin/sh
xrandr --output Virtual1 --primary --mode 1920x1200

# /usr/share/lightdm_xrandr
xrandr: Failed to get size of gamma for output default
warning: output Virtual1 not found; ignoring

# xrandr --listproviders
Providers: number : 0

# xrandr --listmonitors
xrandr: Failed to get size of gamma for output default
Monitors: 1
 0: +*default 1920/508x1200/317+0+0  default

Changing
 xrandr --output Virtual1 --primary --mode 1920x1200

to
 xrandr --output default --primary --mode 1920x1200


leads to display of 1024x768 on a monitor capable of 1920x1200. Doesn't look 
nice!
It worked with 14.04.5 seamless. I'd never had to think of it until upgrading!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Nov 24 19:19:53 2016
InstallationDate: Installed on 2014-02-10 (1017 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
LightdmConfig:
 [Seat:*]
 display-setup-script=/usr/share/lightdm_xrandr
 greeter-session=lightdm-gtk-greeter
 user-session=xubuntu
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: Upgraded to xenial on 2016-11-24 (0 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  lightdm does not start after upgrade from 14.04.5 to 16.04.1

Status in lightdm package in Ubuntu:
  New

Bug description:
  After upgrading from 14.04.5 to 16.04.1 lightdm does not start. Only
  error I could find reported was:

  [+0.19s] DEBUG: Launching process 1927: /usr/share/lightdm_xrandr
  [+0.21s] DEBUG: Process 1927 exited with return value 1
  [+0.21s] DEBUG: Seat seat0: Exit status of /usr/share/lightdm_xrandr: 1
  [+0.21s] DEBUG: Seat seat0: Stopping display server due to failed setup script
  [+0.21s] DEBUG: Sending signal 15 to process 1922
  [+0.59s] DEBUG: Process 1922 exited with return value 0

  Looking at /usr/share/lightdm_xrandr output:
  #!/bin/sh
  xrandr --output Virtual1 --primary --mode 1920x1200

  # /usr/share/lightdm_xrandr
  xrandr: Failed to get size of gamma for output default
  warning: output Virtual1 not found; ignoring

  # xrandr --listproviders
  Providers: number : 0

  # xrandr --listmonitors
  xrandr: Failed to get size of gamma for output default
  Monitors: 1
   0: +*default 1920/508x1200/317+0+0  default

  Changing
   xrandr --output Virtual1 --primary --mode 1920x1200

  to
   xrandr --output default --primary --mode 1920x1200

  
  leads to display of 1024x768 on a monitor capable of 1920x1200. Doesn't look 
nice!
  It worked with 14.04.5 seamless. I'd never had to think of it until upgrading!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 24 19:19:53 2016
  InstallationDate: Installed on 2014-02-10 (1017 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  LightdmConfig:
   [Seat:*]
   display-setup-script=/usr/share/lightdm_xrandr
   greeter-session=lightdm-gtk-greeter
   user-session=xubuntu
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-11-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1644624/+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: [SRU] Re-read the link type if the name changed

[Peter Amaral]

Hi everybody, I realize that this fix I found may not help everybody.
However, the symptoms I was seeing are the same as described in this bug
report so maybe it will work for some other folks as well. The solution
was to do the following:

$ sudo vim /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf

Change the value of wifi.powersave to 0

:wq

After rebooting I have not experienced the problems with disconnect,
even after resuming from suspend.

As I understand it, this setting will disable power management for wifi
adapters if its not supported in the driver/kernel by default.

-- 
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:
  [SRU] Re-read the link type if the name changed

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:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  [Testcase]
  1. Boot the system. It should include a wireless device.
  2. In a terminal, run 'nmcli dev'.
  3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

  ---

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

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 1176046] Re: isc-dhcp dhclient listens on extra random ports

[Eric Desrochers]

NSUPDATE is disabled in Xenial, will keep the same approach for Trusty
and then test.

More details can be found here :

xenial/isc-dhcp-4.3.3/debian/patches/disable-nsupdate.patch 
description: undefine NSUPDATE
author: cchip
origin: http://forums.debian.net/viewtopic.php?f=10=95273
bug-debian: https://bugs.debian.org/712503

--- a/includes/site.h
+++ b/includes/site.h
@@ -121,7 +121,7 @@
 
 /* Define this if you want DNS update functionality to be available. */
 
-#define NSUPDATE
+/* #define NSUPDATE */
 
 /* Define this if you want to enable the DHCP server attempting to
find a nameserver to use for DDNS updates. */

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  
  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient   
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+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 1176046] Re: isc-dhcp dhclient listens on extra random ports

[Eric Desrochers]

** Changed in: isc-dhcp (Ubuntu)
   Status: Triaged => In Progress

** Changed in: isc-dhcp (Ubuntu)
 Assignee: (unassigned) => Eric Desrochers (slashd)

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  
  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient   
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+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 1619600] Re: [SRU] New stable release 1.8.3

[Iain Lane]

Reuploaded -good

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

Title:
  [SRU] New stable release 1.8.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Committed
Status in gstreamer-vaapi source package in Xenial:
  In Progress
Status in gstreamer1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Yakkety:
  Invalid

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+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 1638338] Re: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options)

[Numan Demirdöğen]

Thank you @Colin Watson. I reported this to the upstream. Here is the
link to the bug: https://bugzilla.mindrot.org/show_bug.cgi?id=2643

** Bug watch added: OpenSSH Portable Bugzilla #2643
   https://bugzilla.mindrot.org/show_bug.cgi?id=2643

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

Title:
  Can not ssh with tr_TR.UTF-8 locales (Bad configuration options)

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  I can not ssh to any host with Turkish locales.

  What I expected to happen:

  I expected that 'ssh some_host' command would successfully run.

  What actually happened

  'ssh some_host' command failed with an error.

  Steps to produce:

  1. Open a terminal
  2. Run LANG=tr_TR.UTF-8 ssh some_host

  If I run ssh with tr_TR.UTF-8 locale, the first error I get is:

  $HOME/.ssh/config: line 7: Bad configuration option: Identityfile
  $HOME/.ssh/config: terminating, 1 bad configuration options

  If I commend IdentityFile option from $HOME/.ssh/config file and re-
  run the command, I get this:

  debug1: Reading configuration data ~/.ssh/config
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  /etc/ssh/ssh_config: line 55: Bad configuration option: 
gssapIauthentication
  /etc/ssh/ssh_config: line 56: Bad configuration option: 
gssapIdelegatecredentials
  /etc/ssh/ssh_config: terminating, 2 bad configuration options

  If I commend GSSAPIAuthentication and GSSAPIDelegateCredentials
  option, I can ssh to a host.

  So to ssh to a host with tr_TR.UTF-8 locale, one must commend out
  IdentityFile, if it is used, GSSAPIAuthentication and
  GSSAPIDelegateCredentials optons.

  Workaround:

  LC_ALL=C ssh some_host

  
  LC_ALL=C apt-cache policy openssh-client
  openssh-client:
Installed: 1:7.3p1-1
Candidate: 1:7.3p1-1
Version table:
   *** 1:7.3p1-1 500
  500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  LC_ALL=C lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: openssh-client 1:7.3p1-1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 19:37:35 2016
  InstallationDate: Installed on 2016-10-23 (9 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.3p1 Ubuntu-1, OpenSSL 1.0.2g  1 Mar 2016
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1638338/+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 1176046] Re: isc-dhcp dhclient listens on extra random ports

[Eric Desrochers]

Then NSUPDATE has been re-enable with debian bug :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798237

# changelog
isc-dhcp (4.3.3-4) unstable; urgency=medium

  * Reenable NSUPDATE (closes: #798237)

I will look at both changes, but most likely the one in #798237 seems
more suitable for a wider audience, since the change in #712503 cause
some unwanted situation for certain debian users.

Eric

** Bug watch added: Debian Bug tracker #798237
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798237

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  
  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient   
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+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 1176046] Re: isc-dhcp dhclient listens on extra random ports

[Eric Desrochers]

Sound similar to debian bug : https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=712503

The situation doesn't occur on Xenial (16.04 LTS), but present in Trusty
(14.04) as a fix has been first introduce in Ubuntu with version : isc-
dhcp (4.3.3-2)

Trusty : 
#netstat -tulp | grep -i dhclient
udp0  0 *:bootpc*:* 
23402/dhclient  
udp0  0 *:bootpc*:* 
1589/dhclient   
udp0  0 *:33749 *:* 
1589/dhclient   
udp0  0 *:11662 *:* 
23402/dhclient  
udp6   0  0 [::]:7082   [::]:*  
1589/dhclient   
udp6   0  0 [::]:12668  [::]:*  
23402/dhclient  


Xenial:
# netstat -tulp | grep -i dhclient
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address   Foreign Address State   
PID/Program name
udp0  0 *:bootpc*:* 
142/dhclient


# changelog
isc-dhcp (4.3.3-2) unstable; urgency=medium
...
 ===> * Disable NSUPDATE (closes: #712503). <==
...

** Bug watch added: Debian Bug tracker #712503
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712503

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  
  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient   
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+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 1637731] Re: [SRU] Update to 2.48.2 in Xenial

[Iain Lane]

Thx for filing

** Changed in: glib2.0 (Ubuntu)
   Status: New => In Progress

** Also affects: glib2.0 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: glib2.0 (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: glib2.0 (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: glib2.0 (Ubuntu Xenial)
   Status: New => In Progress

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

Title:
  [SRU] Update to 2.48.2 in Xenial

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  In Progress

Bug description:
  [Description]
  Upstream have released a new bugfix release 2.48.2.

  [Changes]
  https://git.gnome.org/browse/glib/tree/NEWS?h=glib-2-48

  Bugs fixed:
   547200 g_utf8_find_next_char() issues
   673101 resource compiler dependency generation not working for generated 
files
   700756 GFile.new_for_path arguments misses (type filename) annotation
   725902 build: simplify dtrace configuration
   728207 gsocketservice: Documentation does not mention that is already 
active...
   730187 glocalfileoutputstream: Fix an FD leak in an error path
   746685 Doc: clarify that g_variant_get_data() can be used instead of 
g_varia...
   750257 GSettings changed signal should clearly state the order required
   753231 Memory is potentially used after free
   755439 Memory leak in gdbusproxy.c
   760115 gtestutils: add missing dash in seed argument's --help documentation
   760423 gio-querymodules prints error messages as question marks on some 
locales
   761810 gio: Support using GDBusObjectManagerServer at path ‘/’
   766211 Fix the upper bound in g_unichar_iswide_bsearch
   766899 Superflous HTML/XML comments in GDBusProxyTypeFunc documentation 
string
   766933 GSocketAddress leaks in 
gnetworkmonitornetlink.c:read_netlink_messages()
   767172 docs: Move GIO_USE_VFS to "okay for production" section
   767218 Remove a UTF-8 ellipsis from gsignal.h
   767824 Some UTC timezones incorrectly recognized on Windows 7
   767949 Typos in glib docs
   768453 Gdbus test: compilation fails due to -Werror=format-y2k errors
   768504 keyfile: g_key_file_get_double behavior doesn't follow documentation
   768551 Test failure: test_socket_address_to_string
   768560 gio/tests/gsettings: fix GSettings reference leaks in some tests
   768806 gdbus tool must swallow -- argument
   769027 Docs misleadingly imply G_CHECKSUM_SHA512 is available since 2.16

  Translations updated:
   Indonesian
   Portuguese
   Turkish

  [QA, testing, regression potential]
  Under the GNOME MRE, you can believe all bugs upstream says are fixed are 
really fixed. Just test the system and make sure there are no regressions (e.g. 
look at errors.ubuntu.com).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1637731/+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 1643333] Re: Ubuntu Touch web browser does not display Openstack Dashboard

[Olivier Tilloy]

According to upstream, jujucharms.com is not expected to be fully usable
on mobile browsers, that’s not specific to webbrowser-app on ubuntu
touch.

Waiting for more input from Nephilim1973 about the openstack dashboard
issue.

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

Title:
  Ubuntu Touch web browser does not display Openstack Dashboard

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu Touch 15.04 (OTA-13) armhf Build 20160913-023544
  2) Ubuntu Touch web Browser
  3) Navigating without problems on OpenStack Dashboard and Juju Dashboard
  4) Websites are displayed malformated

  
  Hi folks,

  while trying to navigate to an OpenStack Dashboard (Horizon), the web
  browser does not display the web site correctly.

  Also navigating to a Juju-Dashboard has the same effect.

  Examples:
  Horizon Dashboard
  https://x86.trystack.org/dashboard/auth/login/?next=/dashboard/

  Juju:
  https://demo.jujucharms.com

  
  Its a little bit funny, that a Canonical product does not work with other 
Canonical products.

  Regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/164/+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 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame

[Alan Griffiths]

Again:

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

12:05:28 9: Actual function call count doesn't match EXPECT_CALL(first_client, 
handle_input(_))...
12:05:28 9: Expected: to be called between 20 and 180 times
12:05:28 9: Actual: called 18 times - unsatisfied and active
12:05:28 9: [2016-11-24 12:05:28.455825] mirserver: Stopping
12:05:28 9: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame 
(124506 ms)

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

Title:
  CI failure in TestClientInput.receives_one_touch_event_per_frame

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

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull

  02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
  02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting
  02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy 
(version 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor
  02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display 
configuration:
  02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm
  02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0
  02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: 
mir:stub-input (version: 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 
(133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:44 11: Stack trace:
  02:44:44 11: 
/��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639:
 Failure
  02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 
0.2400953674316, which exceeds 0.2f, where
  02:44:44 11: 1.0f evaluates to 1,
  02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, 
and
  02:44:44 11: 0.2f evaluates to 0.2000298023224.
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 
(10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: 
  02:44:45 11: GMOCK WARNING:
  02:44:45 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128 
(14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping
  02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame 
(4083 ms)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1570698/+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 1176046] Re: isc-dhcp dhclient listens on extra random ports

[David Coronel]

I confirm I have the same behavior in Ubuntu 14.04.5 LTS with isc-dhcp-
client version 4.2.4-7ubuntu12.7

I recompiled the isc-dhcp-client with the fix from
http://forums.debian.net/viewtopic.php?f=10=95273 and I no longer have
the issue:

BEFORE:

root@trustydhclient:~# lsof -i udp 
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME 
dhclient 521 root 5u IPv4 7553 0t0 UDP *:bootpc 
dhclient 521 root 20u IPv4 7479 0t0 UDP *:50522 
dhclient 521 root 21u IPv6 7480 0t0 UDP *:17754 

AFTER:

root@trustydhclient:~# lsof -i udp 
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME 
dhclient 524 root 5u IPv4 7613 0t0 UDP *:bootpc

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  
  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient   
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  2659/dhclient   
  udp6   0  0 :::45664:::*  
  2659/dhclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+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 1643333] Re: Ubuntu Touch web browser does not display Openstack Dashboard

[Bill Filler]

Looks like upstream bug request got closed, please take a look to see
what next steps should be

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

Title:
  Ubuntu Touch web browser does not display Openstack Dashboard

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu Touch 15.04 (OTA-13) armhf Build 20160913-023544
  2) Ubuntu Touch web Browser
  3) Navigating without problems on OpenStack Dashboard and Juju Dashboard
  4) Websites are displayed malformated

  
  Hi folks,

  while trying to navigate to an OpenStack Dashboard (Horizon), the web
  browser does not display the web site correctly.

  Also navigating to a Juju-Dashboard has the same effect.

  Examples:
  Horizon Dashboard
  https://x86.trystack.org/dashboard/auth/login/?next=/dashboard/

  Juju:
  https://demo.jujucharms.com

  
  Its a little bit funny, that a Canonical product does not work with other 
Canonical products.

  Regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/164/+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 1644595] [NEW] krb5-1.13.2+dfsg-5 source contains source subject to the aladdin license

[David Simons]

Public bug reported:

The krb5-1.13.2+dfsg-5 package source contains a file autolock.hxx  in
the directory
krb5-1.13.2+dfsg-5\krb5_1.13.2+dfsg.orig\krb5-1.13.2+dfsg\src\ccapi\common\win\OldCC.
Although not declared in any other licensing file for this package the
file contains comments indicating its subject to the Aladdin license
which has implications for any commercial distribution of the software,
specifically:

“2(a) Distribution of the Program or any work based on the Program by a
commercial organization to any third party is prohibited if any payment
is made in connection with such distribution, whether directly (as in
payment for a copy fo the Program) or indirectly (as in payment for some
service related to the Program, or payment for some product or service
that includes a copy of the Program ‘without charge’ . . .”

This file clearly is not needed or used for any Linux build as it
appears specific to windows.

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

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

Title:
  krb5-1.13.2+dfsg-5 source contains source subject to the aladdin
  license

Status in krb5 package in Ubuntu:
  New

Bug description:
  The krb5-1.13.2+dfsg-5 package source contains a file autolock.hxx  in
  the directory
  
krb5-1.13.2+dfsg-5\krb5_1.13.2+dfsg.orig\krb5-1.13.2+dfsg\src\ccapi\common\win\OldCC.
  Although not declared in any other licensing file for this package the
  file contains comments indicating its subject to the Aladdin license
  which has implications for any commercial distribution of the
  software, specifically:

  “2(a) Distribution of the Program or any work based on the Program by
  a commercial organization to any third party is prohibited if any
  payment is made in connection with such distribution, whether directly
  (as in payment for a copy fo the Program) or indirectly (as in payment
  for some service related to the Program, or payment for some product
  or service that includes a copy of the Program ‘without charge’ . . .”

  This file clearly is not needed or used for any Linux build as it
  appears specific to windows.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1644595/+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 1616422] Re: [trusty SRU/FFE] Add systemd binary package for snapd

[Po-Hsu Lin]

Hello Martin,

hello world does not work as well, but core snap can be installed
without any problem.

ubuntu@ubuntu:~$ snap list
Name  Version  Rev  Developer  Notes
core  16.04.1  394  canonical  -
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 3.13.0-102-generic #149-Ubuntu SMP Wed Nov 9 21:52:08 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@ubuntu:~$ dpkg -l | grep systemd
ii  libpam-systemd:amd64  204-5ubuntu20.20  
 amd64system and service manager - PAM module
ii  libsystemd-daemon0:amd64  204-5ubuntu20.20  
 amd64systemd utility library
ii  libsystemd-journal0:amd64 204-5ubuntu20.20  
 amd64systemd journal utility library
ii  libsystemd-login0:amd64   204-5ubuntu20.20  
 amd64systemd login utility library
ii  systemd   204-5ubuntu20.20  
 amd64system and service manager
ii  systemd-services  204-5ubuntu20.20  
 amd64systemd runtime services
rc  systemd-shim  6-2bzr1   
 amd64shim for systemd


ubuntu@ubuntu:~$ sudo snap install hello-world
[sudo] password for ubuntu: 
error: cannot perform the following tasks:
- Setup snap "hello-world" (27) security profiles (cannot setup apparmor for 
snap "hello-world": cannot load apparmor profile "snap.hello-world.env": cannot 
load apparmor profile: exit status 1
apparmor_parser output:
AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.hello-world.env 
in /var/lib/snapd/apparmor/profiles/snap.hello-world.env at line 305: syntax 
error, unexpected TOK_CONDLISTID, expecting TOK_MODE
)
- Setup snap "hello-world" (27) security profiles (cannot load apparmor profile 
"snap.hello-world.env": cannot load apparmor profile: exit status 1
apparmor_parser output:
AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.hello-world.env 
in /var/lib/snapd/apparmor/profiles/snap.hello-world.env at line 305: syntax 
error, unexpected TOK_CONDLISTID, expecting TOK_MODE
)

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

Title:
  [trusty SRU/FFE] Add systemd binary package for snapd

Status in init-system-helpers package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in init-system-helpers source package in Trusty:
  Fix Committed
Status in systemd source package in Trusty:
  Fix Committed

Bug description:
  Rationale: For backporting snapd to 14.04 LTS, we need to provide
  systemd's service manager (not just logind and auxiliary services like
  logind or timesyncd). upstart will continue to do the actual booting,
  and systemd will act as a "deputy init" which by default does not ship
  with/start any services by itself. We will only support this on server
  (at the first iteration at least), not on desktops.

  Regression potential: This is a new binary package in universe, so
  existing systems are unaffected (provided that we ensure that the
  other binary packages do not change and there are no code changes that
  affect processes other than the "deputy pid 1" service manager). So
  for plain upgrades the regression potential is very low. However,
  there is a medium potential for breakage when actually installing the
  new systemd package, as it might interfere with upstart jobs or other
  running processes, cause boot/shutdown hangs, etc.

  For init-system-helpers, the regression potential is near-zero: We
  never had (and never will) systemd as pid 1 in trusty, so deb-systemd-
  invoke was previously never called. It does get called now if you
  install Ubuntu packages that ship a systemd unit, so we need to make
  that a no-op to retain the current behaviour.

  Test plan:
   1. Dist-upgrade a trusty installation to the proposed versions. Ensure this 
does not pull in "systemd", and that booting, shutdown, desktop startup, 
suspend on lid close, resume, logout, and user switching all still work.

   2. Install the "systemd" binary package (this will replace/remove
  systemd-shim). Verify that you can talk to the service manager with
  "sudo systemctl status". Check that booting and shutdown continues to
  work without (significant) delays.

   3. Ensure that "sudo journalctl" works and that "sudo systemctl
  status systemd-journald" is running and has a few lines of log at the
  end (unlike what you get when you run systemctl as user).

   4. Install a package that ships a systemd .service file, such as
  "haveged". Ensure that the service file is ignored, "pgrep -af
  haveged" should only have *one* process and "systemctl status haveged"
  should not be running (it should not exist, or not be enabled and be
  

[Touch-packages] [Bug 1644585] [NEW] Google+ does not work for some accounts

[Alberto Mardegan]

Public bug reported:

After logging in to plus.google.com in the browser with my
@canonical.com account, I get an error message which says that my
browser is not supported. Please see the attached screenshot.

This does not happen with my personal account, which works just fine.

This happens on rc-proposed.

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "screenshot20161118_114746743.png"
   
https://bugs.launchpad.net/bugs/1644585/+attachment/4782499/+files/screenshot20161118_114746743.png

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

Title:
  Google+ does not work for some accounts

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  After logging in to plus.google.com in the browser with my
  @canonical.com account, I get an error message which says that my
  browser is not supported. Please see the attached screenshot.

  This does not happen with my personal account, which works just fine.

  This happens on rc-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1644585/+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 1644572] [NEW] package init 1.29ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Dhairav Mehta]

Public bug reported:

Cannot install any new packages, broke init

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: init 1.29ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Thu Nov 24 19:57:35 2016
DpkgTerminalLog:
 dpkg: error processing package init (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-11-24 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.10ubuntu1
SourcePackage: init-system-helpers
Title: package init 1.29ubuntu3 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: init-system-helpers (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package init 1.29ubuntu3 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in init-system-helpers package in Ubuntu:
  New

Bug description:
  Cannot install any new packages, broke init

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: init 1.29ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Nov 24 19:57:35 2016
  DpkgTerminalLog:
   dpkg: error processing package init (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-11-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: init-system-helpers
  Title: package init 1.29ubuntu3 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/init-system-helpers/+bug/1644572/+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 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

[Bug Watch Updater]

** Changed in: systemd
   Status: New => Fix Released

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  Fix Released
Status in cloud-init package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  In Progress
Status in cloud-init source package in Yakkety:
  New
Status in systemd source package in Yakkety:
  In Progress

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
    └─basic.target @11.403s
  └─sockets.target @11.401s
    └─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
    └─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
    └─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
    └─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
    └─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
    └─system.slice @783ms
  └─-.slice @721ms

  cloud-init would need networkd to run at or before
  'networking.service' so it can raise networking to then find and use
  network-based datasources.

  # grep systemd /usr/share/snappy/dpkg.list
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  systemd   229-4ubuntu11   
 amd64system and service manager
  ii  systemd-sysv  229-4ubuntu11   
 amd64system and service manager - SysV links

  # grep cloud-init /usr/share/snappy/dpkg.list
  ii  cloud-init
0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all  Init 
scripts for cloud instances

  SRU INFORMATION FOR systemd
  ===
  Fix: For xenial it is sufficient to drop systemd-networkd's 
After=dbus.service (https://github.com/systemd/systemd/commit/5f004d1e32) and 
(for xenial only) drop the useless org.freedesktop.network1.busname unit (which 
is always "condition failed" as there is no kdbus, but it moves 
systemd-network.service after sockets.target which is too late for cloud-init).

  Regression 

[Touch-packages] [Bug 1522675] Re: Can't drop privileges for downloading : _apt user not allowed

[Rochvellon]

Same here. Installing the paket from Debian is only a workaround.

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

Title:
  Can't drop privileges for downloading : _apt user not allowed

Status in apt package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Confirmed
Status in apt package in Debian:
  New
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1644541] Re: Update stuck at “configuring unattended-upgrades”

[Paul White]

** Package changed: ubuntu => unattended-upgrades (Ubuntu)

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

Title:
  Update stuck at “configuring unattended-upgrades”

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  On basically fresh install from ubuntu-16.04.1-desktop-amd64.iso; no
  updates or installs had been applied since installing the OS from the
  media.

  During execution of "Software Updater", it freezes indefinitely while
  "Installing updates..." at the step marked "Configuring unattended-
  upgrades."

  It appears that this happens if System Settings->Software &
  Updates->Updates, "Automatically check for updates" has been set to
  "Never."

  If that is instead set to "Daily" and the following are then set in
  /etc/apt/apt.conf.d/10periodic then the update succeeds:

  APT::Periodic::Update-Package-Lists "1";
  APT::Periodic::Download-Upgradeable-Packages "1";
  APT::Periodic::AutocleanInterval "7";
  APT::Periodic::Unattended-Upgrade "1";

  Someone else had asked about this issue at AskUbuntu.  Their question
  along with my answer (from Kevin) provide some further details:

  http://askubuntu.com/questions/851371/update-stuck-at-configuring-
  unattended-upgrades-software-updater-turned-black/852110#852110

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1644541/+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 1620636] Re: Fails to pair with Bose QC35 headphones

[Robin Sheat]

Following the instructions here: http://askubuntu.com/questions/833322
/pair-bose-quietcomfort-35-with-ubuntu-16-04-over-bluetooth I managed to
make it pair and appear as an audio device.

While playback technically worked, it wasn't useable as it came across
as though there wasn't enough bandwidth - the audio was choppy and got
delayed. It seemed that pulse gave up sending to it after a point, and
nothing would play back then.

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

Title:
  Fails to pair with Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+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 1644541] [NEW] Update stuck at “configuring unattended-upgrades”

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

On basically fresh install from ubuntu-16.04.1-desktop-amd64.iso; no
updates or installs had been applied since installing the OS from the
media.

During execution of "Software Updater", it freezes indefinitely while
"Installing updates..." at the step marked "Configuring unattended-
upgrades."

It appears that this happens if System Settings->Software &
Updates->Updates, "Automatically check for updates" has been set to
"Never."

If that is instead set to "Daily" and the following are then set in
/etc/apt/apt.conf.d/10periodic then the update succeeds:

APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "1";
APT::Periodic::AutocleanInterval "7";
APT::Periodic::Unattended-Upgrade "1";

Someone else had asked about this issue at AskUbuntu.  Their question
along with my answer (from Kevin) provide some further details:

http://askubuntu.com/questions/851371/update-stuck-at-configuring-
unattended-upgrades-software-updater-turned-black/852110#852110

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Update stuck at “configuring unattended-upgrades”
https://bugs.launchpad.net/bugs/1644541
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to unattended-upgrades in Ubuntu.

-- 
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 1642240] Re: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salid

[Launchpad Bug Tracker]

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

** Changed in: url-dispatcher (Ubuntu)
   Status: New => Confirmed

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

Title:
  package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to
  install/upgrade: el subproceso instalado el script post-installation
  devolvió el código de salida de error 1

Status in url-dispatcher package in Ubuntu:
  Confirmed

Bug description:
  package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to
  install/upgrade: el subproceso instalado el script post-installation
  devolvió el código de salida de error 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Tue Nov 15 20:02:19 2016
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2014-09-26 (781 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: url-dispatcher
  Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to 
install/upgrade: el subproceso instalado el script post-installation devolvió 
el código de salida de error 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-18 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1642240/+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 1643789] Re: Backport packages for 16.04.2 lts-hwe stack

[Timo Aaltonen]

sorry, freedreno is the FOSS driver for adreno devices (some phones,
tablets), RasPI has vc4

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

Title:
  Backport packages for 16.04.2 lts-hwe stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Incomplete
Status in libdrm source package in Xenial:
  Incomplete

Bug description:
  [Impact]
  We need a few packages backported to xenial for lts-hwe X stack.

  [Test case]

  libdrm: run a desktop session, see that things still work
  libclc: TBD

  [Regression potential]

  slim to none, changes from 2.4.67..2.4.70:
  - amdgpu: spelling fixes
  - ati: typo-/make check fixes
  - intel: pci-id changes, already SRU'd
  - nouveau: only some android makefile diff
  - core: drmGetDevice fixes for multi-gpu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1643789/+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 1492783] Re: GPS does not work on my Bq E5

[flohack]

GPS works for me now if WiFi is turned on with 9/10 success. Can be
closed IMHO

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

Title:
  GPS does not work on my Bq E5

Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  I have a Bq E5 (not an E4.5) and the GPS does not seem to work. The
  SensorsStatus app shows GPS as returning no results for location
  (every reading ("Latitude", "Longitude", etc) is shown as a dash,
  except "Method" which is "Satellite" and "Speed" which is "nan") . I
  have attached various logfiles in the hope that they will help. I have
  tried turning off location detection and GPS and turning them back on
  again, to no avail. I have also tried turning off wifi, to no avail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1492783/+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 1608234] Re: [Nexus 5] Camera pictures rotated by 90° clockwise

[flohack]

Hello,

can be closed, this one is filed in a wrong package. Moved it to ubports
issues :)

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

Title:
  [Nexus 5] Camera pictures rotated by 90° clockwise

Status in camera-app package in Ubuntu:
  New

Bug description:
  Hello,

  using either the front or the back camera I get pictures which are
  rotated by 90° clockwise. No idea what this could come from acutally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1608234/+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 1643789] Re: Backport packages for 16.04.2 lts-hwe stack

[Timo Aaltonen]

Proprietary drivers (nvidia versions, there is no fglrx anymore) don't
use these.

The libdrm diff apart from freedreno (free driver for RasPi) is minimal,
and actually reverting one commit which makes vc4 use headers from
libdrm would make the backport unnecessary. It would be more useful to
backport 2.4.73 from zesty instead.. (adds hw support for some amd
polaris etc)

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

Title:
  Backport packages for 16.04.2 lts-hwe stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Incomplete
Status in libdrm source package in Xenial:
  Incomplete

Bug description:
  [Impact]
  We need a few packages backported to xenial for lts-hwe X stack.

  [Test case]

  libdrm: run a desktop session, see that things still work
  libclc: TBD

  [Regression potential]

  slim to none, changes from 2.4.67..2.4.70:
  - amdgpu: spelling fixes
  - ati: typo-/make check fixes
  - intel: pci-id changes, already SRU'd
  - nouveau: only some android makefile diff
  - core: drmGetDevice fixes for multi-gpu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1643789/+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 1635812] Re: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

[madbiologist]

Has this patch been submitted upstream?

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

Title:
  atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

Status in Poppler:
  Unknown
Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: atril 1.12.2-1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: MATE
  Date: Sat Oct 22 09:43:08 2016
  ExecutablePath: /usr/bin/atril-thumbnailer
  InstallationDate: Installed on 2016-05-14 (160 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: atril-thumbnailer -s 128 
file:///home/username/Documents/jedi_complaint.pdf 
/tmp/.mate_desktop_thumbnail.8JDPPY
  SegvAnalysis:
   Segfault happened at: 0x7fdcb0258990 : mov
0x50(%rdi),%eax
   PC (0x7fdcb0258990) ok
   source "0x50(%rdi)" (0x0050) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: atril
  StacktraceTop:
   cmsGetColorSpace () from /usr/lib/x86_64-linux-gnu/liblcms2.so.2
   GfxICCBasedColorSpace::parse(Array*, OutputDev*, GfxState*, int) () from 
/usr/lib/x86_64-linux-gnu/libpoppler.so.58
   GfxColorSpace::parse(GfxResources*, Object*, OutputDev*, GfxState*, int) () 
from /usr/lib/x86_64-linux-gnu/libpoppler.so.58
   Page::loadThumb(unsigned char**, int*, int*, int*) () from 
/usr/lib/x86_64-linux-gnu/libpoppler.so.58
   poppler_page_get_thumbnail () from 
/usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
  Title: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1635812/+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 1635812] Re: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

[madbiologist]

I just read the upstream bug report.  The patch has been taken from that
report, but has not yet been accepted by upstream.  Perhaps we should
revert and wait?

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

Title:
  atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

Status in Poppler:
  Unknown
Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: atril 1.12.2-1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: MATE
  Date: Sat Oct 22 09:43:08 2016
  ExecutablePath: /usr/bin/atril-thumbnailer
  InstallationDate: Installed on 2016-05-14 (160 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: atril-thumbnailer -s 128 
file:///home/username/Documents/jedi_complaint.pdf 
/tmp/.mate_desktop_thumbnail.8JDPPY
  SegvAnalysis:
   Segfault happened at: 0x7fdcb0258990 : mov
0x50(%rdi),%eax
   PC (0x7fdcb0258990) ok
   source "0x50(%rdi)" (0x0050) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: atril
  StacktraceTop:
   cmsGetColorSpace () from /usr/lib/x86_64-linux-gnu/liblcms2.so.2
   GfxICCBasedColorSpace::parse(Array*, OutputDev*, GfxState*, int) () from 
/usr/lib/x86_64-linux-gnu/libpoppler.so.58
   GfxColorSpace::parse(GfxResources*, Object*, OutputDev*, GfxState*, int) () 
from /usr/lib/x86_64-linux-gnu/libpoppler.so.58
   Page::loadThumb(unsigned char**, int*, int*, int*) () from 
/usr/lib/x86_64-linux-gnu/libpoppler.so.58
   poppler_page_get_thumbnail () from 
/usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
  Title: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1635812/+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 1643789] Re: Backport packages for 16.04.2 lts-hwe stack

[Timo Aaltonen]

** Description changed:

  [Impact]
  We need a few packages backported to xenial for lts-hwe X stack.
  
  [Test case]
  
  libdrm: run a desktop session, see that things still work
  libclc: TBD
  
  [Regression potential]
  
- slim to none
+ slim to none, changes from 2.4.67..2.4.70:
+ - amdgpu: spelling fixes
+ - ati: typo-/make check fixes
+ - intel: pci-id changes, already SRU'd
+ - nouveau: only some android makefile diff
+ - core: drmGetDevice fixes for multi-gpu

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

Title:
  Backport packages for 16.04.2 lts-hwe stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Incomplete
Status in libdrm source package in Xenial:
  Incomplete

Bug description:
  [Impact]
  We need a few packages backported to xenial for lts-hwe X stack.

  [Test case]

  libdrm: run a desktop session, see that things still work
  libclc: TBD

  [Regression potential]

  slim to none, changes from 2.4.67..2.4.70:
  - amdgpu: spelling fixes
  - ati: typo-/make check fixes
  - intel: pci-id changes, already SRU'd
  - nouveau: only some android makefile diff
  - core: drmGetDevice fixes for multi-gpu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1643789/+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 1644526] Re: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Paul White]

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

** This bug has been marked a duplicate of bug 1642966
   package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1

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

Title:
  package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  il problema  mi appare quando aggiorno il sistema

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Nov 19 20:52:54 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2015-04-02 (601 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat:
   device for Canon-MX390: parallel:/dev/lp0
   device for Canon-MX390-series: 
usb://Canon/MX390%20series?serial=21EC4A=1
   device for Canon-MX390-series-FAX: 
usb://Canon/MX390%20series%20FAX?serial=21EC4A=2
   device for MX390-series: usb://Canon/MX390%20series?serial=21EC4A=1
  MachineType: MICRO-STAR INTERANTIONAL CO.,LTD MS-7327
  Papersize: a4
  PpdFiles:
   Canon-MX390-series: Canon MX390 series - CUPS+Gutenprint v5.2.11
   Canon-MX390-series-FAX: Canon MX390 series - CUPS+Gutenprint v5.2.11
   Canon-MX390: Canon MX390 series Ver.3.90
   MX390-series: Canon MX390 series - CUPS+Gutenprint v5.2.11
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=32693442-960b-4ad5-8ef3-8d544168a443 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=32693442-960b-4ad5-8ef3-8d544168a443 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-09-13 (72 days ago)
  dmi.bios.date: 05/04/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.3
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7327
  dmi.board.vendor: MICRO-STAR INTERANTIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERANTIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.3:bd05/04/2007:svnMICRO-STARINTERANTIONALCO.,LTD:pnMS-7327:pvr1.0:rvnMICRO-STARINTERANTIONALCO.,LTD:rnMS-7327:rvr1.0:cvnMICRO-STARINTERANTIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7327
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERANTIONAL CO.,LTD
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-04-17T03:25:57

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1644526/+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 1628635] Re: browser crashes saving image

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-download-manager -
1.3+17.04.20161115-0ubuntu1

---
ubuntu-download-manager (1.3+17.04.20161115-0ubuntu1) zesty; urgency=medium

  * Reorder dbus object and service registration to be compatible with
Qt 5.6 (LP: #1628635)

 -- Michael Sheldon   Tue, 15 Nov 2016
12:10:25 +

** Changed in: ubuntu-download-manager (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  browser crashes saving image

Status in ubuntu-download-manager package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  testing on unity8 desktop on xenial + overlay + silo 2010

  Right click on image and press "Save Image"
  will sometimes work, but crashes quite frequently 1/4 times roughly

  Here is thread trace, full core attached

  sing host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `webbrowser-app 
--desktop_file_hint=/usr/share/applications/webbrowser-app.deskt'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f35552730a1 in 
QDBusAbstractInterface::asyncCallWithArgumentList(QString const&, 
QList const&)
  () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  [Current thread is 1 (Thread 0x7f356042e780 (LWP 10477))]
  (gdb) bt
  #0  0x7f35552730a1 in 
QDBusAbstractInterface::asyncCallWithArgumentList(QString const&, 
QList const&)
  () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #1  0x7f3553cc0858 in ?? () from 
/usr/lib/x86_64-linux-gnu/libubuntu-download-manager-client.so.1
  #2  0x7f34bdfdf997 in 
Ubuntu::DownloadManager::SingleDownload::setAllowMobileDownload(bool) ()
 from 
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/DownloadManager/libUbuntuDownloadManager.so
  #3  0x7f34bdfe18fc in 
Ubuntu::DownloadManager::SingleDownload::bindDownload(Ubuntu::DownloadManager::Download*)
  () from 
/usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/DownloadManager/libUbuntuDownloadManager.so
  #4  0x7f355e955c24 in QMetaObject::activate(QObject*, int, int, void**) ()
 from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #5  0x7f3553ceacaf in 
Ubuntu::DownloadManager::Manager::downloadCreated(Ubuntu::DownloadManager::Download*)
 ()
 from /usr/lib/x86_64-linux-gnu/libubuntu-download-manager-client.so.1
  #6  0x7f3553ce6770 in ?? () from 
/usr/lib/x86_64-linux-gnu/libubuntu-download-manager-client.so.1
  #7  0x7f355e955c24 in QMetaObject::activate(QObject*, int, int, void**) ()
 from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #8  0x7f35552adb9f in 
QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) ()
 from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #9  0x7f35552adc98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #10 0x7f355e956719 in QObject::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #11 0x7f355feb1b1c in QApplicationPrivate::notify_helper(QObject*, 
QEvent*) ()
 from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #12 0x7f355feb7056 in QApplication::notify(QObject*, QEvent*) ()
 from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #13 0x7f355e9292a8 in QCoreApplication::notifyInternal2(QObject*, 
QEvent*) ()
 from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #14 0x7f355e92b16a in QCoreApplicationPrivate::sendPostedEvents(QObject*, 
int, QThreadData*) ()
 from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #15 0x7f355e97df53 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #16 0x7f355d60f1a7 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #17 0x7f355d60f400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #18 0x7f355d60f4ac in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #19 0x7f355e97e35f in 
QEventDispatcherGlib::processEvents(QFlags) ()
 from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #20 0x7f355e926ffa in 
QEventLoop::exec(QFlags) ()
 from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #21 0x7f355e92f6bc in QCoreApplication::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #22 0x0042bf55 in main ()
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1628635/+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 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

[Martin Pitt]

I suppose you want this for yakkety too, so backported:
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h
=ubuntu-yakkety=648c659e9

** Description changed:

  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not yet
  available when cloud-init.service runs.
  
  cloud-init service unit deps look like this:
  
  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target
  
  Here's networkd unit deps:
  
  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target
  
  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname
  
  And a critical-chain output:
  
  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.
  
  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.
  
  systemd-networkd.service +440ms
  └─dbus.service @11.461s
    └─basic.target @11.403s
  └─sockets.target @11.401s
    └─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
    └─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
    └─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
    └─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
    └─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
    └─system.slice @783ms
  └─-.slice @721ms
  
  cloud-init would need networkd to run at or before 'networking.service'
  so it can raise networking to then find and use network-based
  datasources.
  
  # grep systemd /usr/share/snappy/dpkg.list
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  systemd   229-4ubuntu11   
 amd64system and service manager
  ii  systemd-sysv  229-4ubuntu11   
 amd64system and service manager - SysV links
  
  # grep cloud-init /usr/share/snappy/dpkg.list
  ii  cloud-init
0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all  Init 
scripts for cloud instances
  
  SRU INFORMATION FOR systemd
  ===
- Fix: For xenial it is sufficient to drop systemd-networkd's 
After=dbus.service (https://github.com/systemd/systemd/commit/5f004d1e32) and 
drop the useless org.freedesktop.network1.busname unit (which is always 
"condition failed" as there is no kdbus, but it moves systemd-network.service 
after sockets.target which is too late for cloud-init).
+ Fix: For xenial it is sufficient to drop systemd-networkd's 
After=dbus.service (https://github.com/systemd/systemd/commit/5f004d1e32) and 
(for xenial only) drop the useless org.freedesktop.network1.busname unit (which 
is always "condition failed" as there is no kdbus, but it moves 
systemd-network.service after sockets.target which is too late for cloud-init).
  
  Regression potential: Low. networkd is not widely being used outside of 
netplan/snappy in xenial. Running it before dbus.service is running has two 

[Touch-packages] [Bug 1644526] [NEW] package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Pierluigi70]

Public bug reported:

il problema  mi appare quando aggiorno il sistema

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
Uname: Linux 4.4.0-49-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CupsErrorLog:
 
Date: Sat Nov 19 20:52:54 2016
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2015-04-02 (601 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Lpstat:
 device for Canon-MX390: parallel:/dev/lp0
 device for Canon-MX390-series: 
usb://Canon/MX390%20series?serial=21EC4A=1
 device for Canon-MX390-series-FAX: 
usb://Canon/MX390%20series%20FAX?serial=21EC4A=2
 device for MX390-series: usb://Canon/MX390%20series?serial=21EC4A=1
MachineType: MICRO-STAR INTERANTIONAL CO.,LTD MS-7327
Papersize: a4
PpdFiles:
 Canon-MX390-series: Canon MX390 series - CUPS+Gutenprint v5.2.11
 Canon-MX390-series-FAX: Canon MX390 series - CUPS+Gutenprint v5.2.11
 Canon-MX390: Canon MX390 series Ver.3.90
 MX390-series: Canon MX390 series - CUPS+Gutenprint v5.2.11
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=32693442-960b-4ad5-8ef3-8d544168a443 ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=32693442-960b-4ad5-8ef3-8d544168a443 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: cups
Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-09-13 (72 days ago)
dmi.bios.date: 05/04/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.3
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7327
dmi.board.vendor: MICRO-STAR INTERANTIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERANTIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.3:bd05/04/2007:svnMICRO-STARINTERANTIONALCO.,LTD:pnMS-7327:pvr1.0:rvnMICRO-STARINTERANTIONALCO.,LTD:rnMS-7327:rvr1.0:cvnMICRO-STARINTERANTIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7327
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERANTIONAL CO.,LTD
modified.conffile..etc.default.cups:
 # Cups configure options
 
 # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
 # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
 # LOAD_LP_MODULE=yes
mtime.conffile..etc.default.cups: 2014-04-17T03:25:57

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


** Tags: amd64 apport-package need-duplicate-check package-from-proposed xenial

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

Title:
  package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  il problema  mi appare quando aggiorno il sistema

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Nov 19 20:52:54 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2015-04-02 (601 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat:
   device for Canon-MX390: parallel:/dev/lp0
   device for Canon-MX390-series: 
usb://Canon/MX390%20series?serial=21EC4A=1
   device for Canon-MX390-series-FAX: 
usb://Canon/MX390%20series%20FAX?serial=21EC4A=2
   device for MX390-series: usb://Canon/MX390%20series?serial=21EC4A=1
  MachineType: MICRO-STAR INTERANTIONAL CO.,LTD MS-7327
  Papersize: a4
  PpdFiles:
   Canon-MX390-series: Canon MX390 series - CUPS+Gutenprint v5.2.11
   Canon-MX390-series-FAX: Canon MX390 series - CUPS+Gutenprint v5.2.11
   Canon-MX390: Canon MX390 series Ver.3.90
   MX390-series: Canon MX390 series - CUPS+Gutenprint v5.2.11
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=32693442-960b-4ad5-8ef3-8d544168a443 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=32693442-960b-4ad5-8ef3-8d544168a443 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4ubuntu0.1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-09-13 (72 days ago)
  dmi.bios.date: 

[Touch-packages] [Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

[Martin Pitt]

Xenial fixes:

  
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=aeff48d716
  
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=310753a6

** Changed in: systemd (Ubuntu Xenial)
   Status: Triaged => In Progress

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  New
Status in cloud-init package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  In Progress

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
    └─basic.target @11.403s
  └─sockets.target @11.401s
    └─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
    └─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
    └─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
    └─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
    └─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
    └─system.slice @783ms
  └─-.slice @721ms

  cloud-init would need networkd to run at or before
  'networking.service' so it can raise networking to then find and use
  network-based datasources.

  # grep systemd /usr/share/snappy/dpkg.list
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  systemd   229-4ubuntu11   
 amd64system and service manager
  ii  systemd-sysv  229-4ubuntu11   
 amd64system and service manager - SysV links

  # grep cloud-init /usr/share/snappy/dpkg.list
  ii  cloud-init
0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all  Init 
scripts for cloud instances

  SRU INFORMATION FOR systemd
  ===
  Fix: For xenial it is sufficient to drop systemd-networkd's 
After=dbus.service (https://github.com/systemd/systemd/commit/5f004d1e32) and 
drop the useless org.freedesktop.network1.busname unit (which is always 
"condition failed" as there is no kdbus, but it moves systemd-network.service 

[Touch-packages] [Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

[Martin Pitt]

** Description changed:

  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not yet
  available when cloud-init.service runs.
  
  cloud-init service unit deps look like this:
  
  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target
  
  Here's networkd unit deps:
  
  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target
  
  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname
  
  And a critical-chain output:
  
  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.
  
  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.
  
  systemd-networkd.service +440ms
  └─dbus.service @11.461s
    └─basic.target @11.403s
  └─sockets.target @11.401s
    └─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
    └─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
    └─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
    └─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
    └─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
    └─system.slice @783ms
  └─-.slice @721ms
  
  cloud-init would need networkd to run at or before 'networking.service'
  so it can raise networking to then find and use network-based
  datasources.
  
  # grep systemd /usr/share/snappy/dpkg.list
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  systemd   229-4ubuntu11   
 amd64system and service manager
  ii  systemd-sysv  229-4ubuntu11   
 amd64system and service manager - SysV links
  
  # grep cloud-init /usr/share/snappy/dpkg.list
  ii  cloud-init
0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all  Init 
scripts for cloud instances
  
- 
  SRU INFORMATION FOR systemd
  ===
- Fix: For xenial it is sufficient to drop systemd-networkd's 
After=dbus.service (https://github.com/systemd/systemd/commit/5f004d1e32)
+ Fix: For xenial it is sufficient to drop systemd-networkd's 
After=dbus.service (https://github.com/systemd/systemd/commit/5f004d1e32) and 
drop the useless org.freedesktop.network1.busname unit (which is always 
"condition failed" as there is no kdbus, but it moves systemd-network.service 
after sockets.target which is too late for cloud-init).
  
  Regression potential: Low. networkd is not widely being used outside of 
netplan/snappy in xenial. Running it before dbus.service is running has two 
consequences:
-  - It cannot immediately expose its D-Bus status interface. But it will retry 
every 5 s until that succeeds, so the D-Bus status interface will continue to 
work. (see test case)
-  - If a DHCP response with a hostname or timezone is received before 
dbus.service is running, it cannot talk to systemd-hostnamed/systemd-timedated 
to set these properties (if enabled). 

[Touch-packages] [Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

[Martin Pitt]

** Description changed:

  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not yet
  available when cloud-init.service runs.
  
  cloud-init service unit deps look like this:
  
  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target
  
  Here's networkd unit deps:
  
  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target
  
  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname
  
- 
  And a critical-chain output:
  
  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.
  
  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.
  
  systemd-networkd.service +440ms
  └─dbus.service @11.461s
-   └─basic.target @11.403s
- └─sockets.target @11.401s
-   └─dbus.socket @11.398s
- └─cloud-init.service @10.127s +1.266s
-   └─networking.service @9.305s +799ms
- └─network-pre.target @9.295s
-   └─cloud-init-local.service @3.822s +5.469s
- └─local-fs.target @3.813s
-   └─run-cgmanager-fs.mount @12.687s
- └─local-fs-pre.target @1.393s
-   └─systemd-tmpfiles-setup-dev.service @1.116s +195ms
- └─kmod-static-nodes.service @887ms +193ms
-   └─system.slice @783ms
- └─-.slice @721ms
+   └─basic.target @11.403s
+ └─sockets.target @11.401s
+   └─dbus.socket @11.398s
+ └─cloud-init.service @10.127s +1.266s
+   └─networking.service @9.305s +799ms
+ └─network-pre.target @9.295s
+   └─cloud-init-local.service @3.822s +5.469s
+ └─local-fs.target @3.813s
+   └─run-cgmanager-fs.mount @12.687s
+ └─local-fs-pre.target @1.393s
+   └─systemd-tmpfiles-setup-dev.service @1.116s +195ms
+ └─kmod-static-nodes.service @887ms +193ms
+   └─system.slice @783ms
+ └─-.slice @721ms
  
+ cloud-init would need networkd to run at or before 'networking.service'
+ so it can raise networking to then find and use network-based
+ datasources.
  
- cloud-init would need networkd to run at or before 'networking.service' so it 
can raise networking to then find and use network-based datasources.
- 
- # grep systemd /usr/share/snappy/dpkg.list 
+ # grep systemd /usr/share/snappy/dpkg.list
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  systemd   229-4ubuntu11   
 amd64system and service manager
  ii  systemd-sysv  229-4ubuntu11   
 amd64system and service manager - SysV links
  
- # grep cloud-init /usr/share/snappy/dpkg.list 
+ # grep cloud-init /usr/share/snappy/dpkg.list
  ii  cloud-init
0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all  Init 
scripts for cloud instances
+ 
+ 
+ SRU INFORMATION FOR systemd
+ ===
+ Fix: For xenial it is sufficient to drop systemd-networkd's 
After=dbus.service 

[Touch-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

[Roberto Mier Escandón ]

** Branch linked: lp:~phablet-team/telephony-service/fix-hardcoded-paths

** Changed in: telephony-service (Ubuntu)
   Status: New => In Progress

** Changed in: telephony-service (Ubuntu)
 Assignee: (unassigned) => Roberto Mier Escandón  (rmescandon)

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Released
Status in address-book-app package in Ubuntu:
  In Progress
Status in address-book-service package in Ubuntu:
  In Progress
Status in dialer-app package in Ubuntu:
  In Progress
Status in history-service package in Ubuntu:
  New
Status in indicator-bluetooth package in Ubuntu:
  In Progress
Status in indicator-display package in Ubuntu:
  New
Status in indicator-keyboard package in Ubuntu:
  In Progress
Status in indicator-location package in Ubuntu:
  In Progress
Status in indicator-messages package in Ubuntu:
  In Progress
Status in indicator-network package in Ubuntu:
  In Progress
Status in indicator-power package in Ubuntu:
  In Progress
Status in indicator-session package in Ubuntu:
  In Progress
Status in indicator-sound package in Ubuntu:
  In Progress
Status in indicator-transfer package in Ubuntu:
  In Progress
Status in mediascanner2 package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress
Status in pay-service package in Ubuntu:
  New
Status in policykit-unity8 package in Ubuntu:
  Fix Released
Status in sync-monitor package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  In Progress
Status in ubuntu-keyboard package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  In Progress
Status in unity-scope-scopes package in Ubuntu:
  Won't Fix
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+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 1616422] Re: [trusty SRU/FFE] Add systemd binary package for snapd

[Martin Pitt]

Thanks Po-Hsu. This is clearly a bug within test-snapd-tools, possibly
fixed by bug 1641243. Is there a simpler "hello world" type snap that
has a service that can be used to verify this without running into the
apparmor profile issue?

Steps 7 to 9 can be done independently.

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

Title:
  [trusty SRU/FFE] Add systemd binary package for snapd

Status in init-system-helpers package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in init-system-helpers source package in Trusty:
  Fix Committed
Status in systemd source package in Trusty:
  Fix Committed

Bug description:
  Rationale: For backporting snapd to 14.04 LTS, we need to provide
  systemd's service manager (not just logind and auxiliary services like
  logind or timesyncd). upstart will continue to do the actual booting,
  and systemd will act as a "deputy init" which by default does not ship
  with/start any services by itself. We will only support this on server
  (at the first iteration at least), not on desktops.

  Regression potential: This is a new binary package in universe, so
  existing systems are unaffected (provided that we ensure that the
  other binary packages do not change and there are no code changes that
  affect processes other than the "deputy pid 1" service manager). So
  for plain upgrades the regression potential is very low. However,
  there is a medium potential for breakage when actually installing the
  new systemd package, as it might interfere with upstart jobs or other
  running processes, cause boot/shutdown hangs, etc.

  For init-system-helpers, the regression potential is near-zero: We
  never had (and never will) systemd as pid 1 in trusty, so deb-systemd-
  invoke was previously never called. It does get called now if you
  install Ubuntu packages that ship a systemd unit, so we need to make
  that a no-op to retain the current behaviour.

  Test plan:
   1. Dist-upgrade a trusty installation to the proposed versions. Ensure this 
does not pull in "systemd", and that booting, shutdown, desktop startup, 
suspend on lid close, resume, logout, and user switching all still work.

   2. Install the "systemd" binary package (this will replace/remove
  systemd-shim). Verify that you can talk to the service manager with
  "sudo systemctl status". Check that booting and shutdown continues to
  work without (significant) delays.

   3. Ensure that "sudo journalctl" works and that "sudo systemctl
  status systemd-journald" is running and has a few lines of log at the
  end (unlike what you get when you run systemctl as user).

   4. Install a package that ships a systemd .service file, such as
  "haveged". Ensure that the service file is ignored, "pgrep -af
  haveged" should only have *one* process and "systemctl status haveged"
  should not be running (it should not exist, or not be enabled and be
  inactive). [This part also needs the updated init-system-helpers].

     The only services that are running are expected to be systemd-
  journald.service and systemd-journald.socket.

   5. Ensure that the standard targets are active, as that is where
  third-party/snap services hook into:

  systemctl status sysinit.target multi-user.target default.target

   6. Install snapd (not in trusty yet, e. g. from Thomas' PPA) and
  ensure you can install a snap, and its services start after installing
  the snap and after rebooting.

   7. Run "sudo apt-get install --reinstall systemd" to ensure that
  upgrades to newer systemd trusty versions work. The running systemd
  should *not* be restarted as that would disrupt snapd and its services
  (verify that the pid in "initctl status systemd" is the same before
  and after the upgrade).

   8. Run "sudo apt install -y colord && sudo apt purge -y colord". This
  should succeed.

   9. Dist-upgrade to 16.04 to ensure that there are no file conflicts,
  dependency issues, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1616422/+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 1643789] Re: Backport packages for 16.04.2 lts-hwe stack

[Timo Aaltonen]

** Description changed:

+ [Impact]
  We need a few packages backported to xenial for lts-hwe X stack.
+ 
+ [Test case]
+ 
+ libdrm: run a desktop session, see that things still work
+ libclc: TBD
+ 
+ [Regression potential]
+ 
+ slim to none

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

Title:
  Backport packages for 16.04.2 lts-hwe stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Incomplete
Status in libdrm source package in Xenial:
  Incomplete

Bug description:
  [Impact]
  We need a few packages backported to xenial for lts-hwe X stack.

  [Test case]

  libdrm: run a desktop session, see that things still work
  libclc: TBD

  [Regression potential]

  slim to none

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1643789/+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 1644287] Re: apt-get throwing ValueError: Invalid header value 'AWS ASIAJ5KTV3ZQHPUKWSAQ:W9GzdJOuZYKf+qYITznWGgYXx9E=\n'

[Dimitri John Ledkov]

On 23 November 2016 at 16:21, David Makin <1644...@bugs.launchpad.net> wrote:
> Public bug reported:
>
> Description:Ubuntu 14.04.5 LTS
> Release:14.04
> Package:libpython2.7-minimal 2.7.6-8ubuntu0.3
>
> After updated to libpython2.7:amd64 2.7.6-8ubuntu0.3 apt-get update
> throws the following error
>
> W: Failed to fetch 
> s3://XXX.s3.amazonaws.com/repo/dists/stable/main/binary-amd64/Packages: 
> ValueError: Invalid header value 'AWS 
> ASIAJ5KTV3ZQHPUKWSAQ:W9GzdJOuZYKf+qYITznWGgYXx9E=\n'
> E: Some index files failed to download. They have been ignored, or old ones 
> used instead.
> E: Couldn't rebuild package cache
>

s3:// protocol is not supported by ubuntu. Do you have some kind of
apt-transport-s3 protocol helper installed? In that case the bug is
probably there. Please contact the support of whoever provided that to
you. As s3 protocol handler is not shipped in Ubuntu.

> Downgrading to the previous installed versions,
> libpython2.7-stdlib_2.7.6-8ubuntu0.2_amd64.deb and
> libpython2.7-minimal_2.7.6-8ubuntu0.2_amd64.deb, fixes this. apt-get
> update runs once again
>

Apt is a C++ application and does not use python at all.

> ** Affects: python2.7 (Ubuntu)
>  Importance: Undecided
>  Status: New
>
> --
> You received this bug notification because you are a member of Ubuntu
> Pythoneers, which is subscribed to python2.7 in Ubuntu.
> https://bugs.launchpad.net/bugs/1644287
>
> Title:
>   apt-get throwing ValueError: Invalid header value 'AWS
>   ASIAJ5KTV3ZQHPUKWSAQ:W9GzdJOuZYKf+qYITznWGgYXx9E=\n'
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1644287/+subscriptions


-- 
Regards,

Dimitri.


** Changed in: python2.7 (Ubuntu)
   Status: New => Invalid

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

Title:
  apt-get throwing ValueError: Invalid header value 'AWS
  ASIAJ5KTV3ZQHPUKWSAQ:W9GzdJOuZYKf+qYITznWGgYXx9E=\n'

Status in python2.7 package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04
  Package:libpython2.7-minimal 2.7.6-8ubuntu0.3 

  After updated to libpython2.7:amd64 2.7.6-8ubuntu0.3 apt-get update
  throws the following error

  W: Failed to fetch 
s3://XXX.s3.amazonaws.com/repo/dists/stable/main/binary-amd64/Packages: 
ValueError: Invalid header value 'AWS 
ASIAJ5KTV3ZQHPUKWSAQ:W9GzdJOuZYKf+qYITznWGgYXx9E=\n'
  E: Some index files failed to download. They have been ignored, or old ones 
used instead.
  E: Couldn't rebuild package cache

  Downgrading to the previous installed versions,
  libpython2.7-stdlib_2.7.6-8ubuntu0.2_amd64.deb and
  libpython2.7-minimal_2.7.6-8ubuntu0.2_amd64.deb, fixes this. apt-get
  update runs once again

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1644287/+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 1644237] Re: unity8 fails to start as guest user

[Timo Aaltonen]

looks like it

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

Title:
  unity8 fails to start as guest user

Status in Canonical System Image:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  This is shown in unity8.log:

  [2016-11-23 15:59:25.820868] mirserver: Starting
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132):
 Throw in function 
mir::DefaultServerConfiguration::the_graphics_platform()::
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Exception while creating graphics platform
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245):
 Throw in function 
mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const 
string&, const string&, const 
std::shared_ptr&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Nested Mir Platform Connection Error: Failed to connect 
to server socket: Permission denied


  [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start
  initctl: No such variable: UNITY_MIR_SOCKET

  running current zesty, but I had the same problem on yakkety too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644237/+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 1639202] Re: Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

[Richard Lovell]

more info, as requested:

ls -la /sys/class/net/*

lrwxrwxrwx  1   0   /sys/class/net/lo ->
../../devices/virtual/net/lo

lrwxrwxrwx  1   0   /sys/class/net/enx847beb55c195 ->
../../devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb3/3-1/3-1:1.0/net/enx847beb55c195


cat /sys/class/net/*/address

84:7b:eb:55:c1:95
00:00:00:00:00:00


so there's no reference to 9c-eb-e8-3c-52-cc, which is the mac displayed via 
BOOTIF =

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

Title:
  Cannot enlist/commission machines in MAAS 2.1 with usb network adapter

Status in MAAS:
  Invalid
Status in maas-images:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrade from MAAS 2.0 to MAAS 2.1:

  Cannot enlist/commission client machines via network boot (or pre-
  staging machine) when using usb-c network adapter D59GG (e.g.
  Precision 5510). This was working ok with MAAS 2.0.

  Using the Xenial 16.04 base image for enlist/commission (no minimum
  kernel set).

  Enlist/Commission/Deploy works fine with other laptop and desktop
  models which have a built in NIC.

  From an already deployed Precision 5510 system (16.04.1) I can see the
  following module is loaded when the usb-c adapter is connected (and
  working):

  $ lsmod
  usbnet45056 1 cdc_ether

  
  Errors received on client during enlisting with MAAS:

  no /run/net-bootif.conf
  lvmetad is not activated
  ...invalid path for logical volume.
  gave up waiting for root device
  common problems: boot args (cat /proc/cmdline)
  check rootdelay = (did system wait long enough)
  check root = (did the system wait for the right device?)
  missing modules (cat /proc/modules)
  ALERT!  
/dev/disk/by-path/ip-:3260-iscsi-iqn,2004.05.com.ubuntu:maas:ephemeral-ubuntu-amd64-generic-xenial-daily-lun-1
 does not exist. Dropping to shell!
  usbcore: registered new interface driver usbhid
  usbhid: USB HID core driver

  - cat /proc/cmdline shows mac address that of usb-c network adapter.
  - cat /proc/modules includes “usbnet 45056 cdc_ether, Live 0xc009c000”
  - cat /proc/modules | grep usb … includes “ usbnet 45056 and usbhid 49152”

  
  I've tried enlisting with older boot image and different kernel versions 
(14.04 and 16.04 with ga-16.04, hwe-16.04 set) but get the same problem.

  It seems like the usb-c network adapter isn't loading properly or
  maybe just not quickly enough?

  Please let me know if you require any more info. I can provide info
  from /var/log/maas/* and dpkg -l '*maas*'|cat if need be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1639202/+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 1643847] Re: Ubuntu 16.04 no sound after change volume

[clement.analogue]

If I simply downgrade the package, it doesn't work.

I just manage to have the sound back with the following procedure:
#1 purge the package
sudo apt purge libpulsedsp pulseaudio libpulse0 libpulse-mainloop-glib0 
pulseaudio-module-x11 pulseaudio-module-bluetooth pulseaudio-utils
#2 keep track of the additional removed packages, in my case
checkbox-converged checkbox-gui gdm3 gnome-control-center gnome-orca 
gnome-session gnome-settings-daemon gnome-shell gstreamer1.0-plugins-bad 
gstreamer1.0-pulseaudio indicator-bluetooth indicator-sound libasound2-plugins 
libcanberra-pulse libespeak1 libfluidsynth1 libfreerdp-plugins-standard 
liboxideqt-qmlplugin liboxideqtcore0 liboxideqtquick0 libqt5feedback5 
libqt5multimedia5 libsdl-image1.2 libsdl1.2debian libunity-webapps0 
qml-module-qtfeedback qml-module-ubuntu-components qml-module-ubuntu-test 
qml-module-ubuntu-web qtdeclarative5-ubuntu-ui-toolkit-plugin speech-dispatcher 
speech-dispatcher-audio-plugins ubuntu-desktop ubuntu-session 
unity-control-center unity-control-center-signon unity-settings-daemon 
unity-webapps-common unity-webapps-qml unity-webapps-service vlc 
webapp-container webbrowser-app
#3 reinstall the packages, with the pulseaudio one to the previous version
sudo apt install libpulsedsp=1:8.0-0ubuntu3 pulseaudio=1:8.0-0ubuntu3 
libpulse0=1:8.0-0ubuntu3 libpulse-mainloop-glib0=1:8.0-0ubuntu3 
pulseaudio-module-x11=1:8.0-0ubuntu3 pulseaudio-module-bluetooth=1:8.0-0ubuntu3 
pulseaudio-utils=1:8.0-0ubuntu3 checkbox-converged checkbox-gui gdm3 
gnome-control-center gnome-orca gnome-session gnome-settings-daemon gnome-shell 
gstreamer1.0-plugins-bad gstreamer1.0-pulseaudio indicator-bluetooth 
indicator-sound libasound2-plugins libcanberra-pulse libespeak1 libfluidsynth1 
libfreerdp-plugins-standard liboxideqt-qmlplugin liboxideqtcore0 
liboxideqtquick0 libqt5feedback5 libqt5multimedia5 libsdl-image1.2 
libsdl1.2debian libunity-webapps0 qml-module-qtfeedback 
qml-module-ubuntu-components qml-module-ubuntu-test qml-module-ubuntu-web 
qtdeclarative5-ubuntu-ui-toolkit-plugin speech-dispatcher 
speech-dispatcher-audio-plugins ubuntu-desktop ubuntu-session 
unity-control-center unity-control-center-signon unity-settings-daemon 
unity-webapps-common unity-webapps-qml unity-webapps-service vlc 
webapp-container webbrowser-app
#4 Remove the user config file
rm -r ~/.config/pulse/*
#5 Shutdown the computer then turn it on again (don't reboot).
#6 Enjoy sound again :)

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

Title:
  Ubuntu 16.04 no sound after change volume

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I did a new ubuntu 16.04 installation. All worked great until i tried
  to test the speaker sound. When I did it the analog stereo option
  dissappeared and only had digital and hdmi option. The sound card is
  onboard (A Realtek ALC888 Audio). With ubuntu 14.04 i havent any
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luna   1790 F pulseaudio
   /dev/snd/controlC1:  luna   1790 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Nov 22 08:36:07 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.3
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7374
  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.:bvrV3.3:bd12/23/2008:svnMSI:pnMS-7374:pvr1.0:rvnMSI:rnMS-7374:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7374
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643847/+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 1644287] Re: apt-get throwing ValueError: Invalid header value 'AWS ASIAJ5KTV3ZQHPUKWSAQ:W9GzdJOuZYKf+qYITznWGgYXx9E=\n'

[David Makin]

s3://XXX.s3.amazonaws.com/repo/dists/stable/main/binary-amd64/Packages
is our own list of packages stored on s3 and we only have stable.

ls -lh /etc/apt/*
-rw-r--r-- 1 root root 3.4K May 10  2016 /etc/apt/sources.list
-rw-r--r-- 1 root root 3.3K Apr  1  2016 /etc/apt/sources.list.save
-rw-r--r-- 1 root root  14K Dec  9  2015 /etc/apt/trusted.gpg
-rw-r--r-- 1 root root  13K Jun  7  2014 /etc/apt/trusted.gpg~

/etc/apt/apt.conf.d:
total 40K
-rw-r--r-- 1 root root  643 Apr 10  2014 01autoremove
-rw-r--r-- 1 root root 1.1K Jun 13 09:16 01autoremove-kernels
-rw-r--r-- 1 root root  129 Aug 22  2011 10periodic
-rw-r--r-- 1 root root  155 Dec  9  2015 15update-stamp
-rw-r--r-- 1 root root   85 Aug 22  2011 20archive
-rw-r--r-- 1 root root  123 Apr 10  2014 20changelog
-rw-r--r-- 1 root root 2.3K Apr  2  2014 50unattended-upgrades
-rw-r--r-- 1 root root  182 Feb 23  2014 70debconf
-rw-r--r-- 1 root root   80 May 10  2016 90cloud-init-pipelining
-rw-r--r-- 1 root root  231 Aug 22  2011 99update-notifier

/etc/apt/preferences.d:
total 108K
-rw-r--r-- 1 root root 143 Nov 23 13:32 hold_skylab-aiba.pref
-rw-r--r-- 1 root root 168 Aug 17 09:26 hold_skylab-badminton-england.pref
-rw-r--r-- 1 root root 157 Dec  9  2015 hold_skylab-badminton-gp.pref
-rw-r--r-- 1 root root 165 Oct 26 12:26 hold_skylab-battle-badminton.pref
-rw-r--r-- 1 root root 165 Nov 23 13:32 hold_skylab-creative-kitchen.pref
-rw-r--r-- 1 root root 171 Nov 23 13:32 hold_skylab-englacrosse-portals.pref
-rw-r--r-- 1 root root 155 Oct 26 12:26 hold_skylab-englacrosse.pref
-rw-r--r-- 1 root root 169 May 12  2016 hold_skylab-frontend-framework.pref
-rw-r--r-- 1 root root 171 Sep 28 14:27 hold_skylab-holt-lloyd-identity.pref
-rw-r--r-- 1 root root 161 Oct  3 14:52 hold_skylab-holt-lloyd-ims.pref
-rw-r--r-- 1 root root 161 Nov 16 11:27 hold_skylab-holt-lloyd-pmp.pref
-rw-r--r-- 1 root root 155 Nov 24 10:06 hold_skylab-holt-lloyd.pref
-rw-r--r-- 1 root root 151 May 12  2016 hold_skylab-ideaspace.pref
-rw-r--r-- 1 root root 149 Nov 23 13:32 hold_skylab-ittf-api.pref
-rw-r--r-- 1 root root 142 Nov 23 13:32 hold_skylab-ittf.pref
-rw-r--r-- 1 root root 161 Apr 27  2016 hold_skylab-ittf-prototype.pref
-rw-r--r-- 1 root root 189 Oct 26 12:28 
hold_skylab-leigh-sports-village-website.pref
-rw-r--r-- 1 root root 162 Oct  5 10:00 hold_skylab-mcparland-finn.pref
-rw-r--r-- 1 root root 145 Jan  5  2016 hold_skylab-morson.pref
-rw-r--r-- 1 root root 161 Apr  6  2016 hold_skylab-nfts-wordpress.pref
-rw-r--r-- 1 root root 166 Nov 24 10:06 hold_skylab-rounders-england.pref
-rw-r--r-- 1 root root 153 Jun 13 08:49 hold_skylab-secontrols.pref
-rw-r--r-- 1 root root 139 Nov 23 13:32 hold_skylab-smd.pref
-rw-r--r-- 1 root root 157 Jun 13 08:49 hold_skylab-sportnetwork.pref
-rw-r--r-- 1 root root 171 Nov 24 10:06 hold_skylab-sports-publications.pref
-rw-r--r-- 1 root root 157 Nov  9 13:08 hold_skylab-studioskylab.pref
-rw-r--r-- 1 root root 164 Nov 23 13:32 hold_skylab-video-wordpress.pref

/etc/apt/sources.list.d:
total 40K
-rw-r--r-- 1 root root 138 Apr  1  2016 chris-lea-node_js-trusty.list
-rw-r--r-- 1 root root 138 Apr  1  2016 chris-lea-node_js-trusty.list.save
-rw-r--r-- 1 root root 131 Apr  1  2016 deployer.list
-rw-r--r-- 1 root root 131 Apr  1  2016 deployer.list.save
-rw-r--r-- 1 root root 112 Apr  1  2016 newrelic.list
-rw-r--r-- 1 root root 112 Apr  1  2016 newrelic.list.save
-rw-r--r-- 1 root root 174 Apr  1  2016 puppetlabs.list
-rw-r--r-- 1 root root 379 Apr 12  2016 puppetlabs.list.dpkg-dist
-rw-r--r-- 1 root root 174 Apr  1  2016 puppetlabs.list.save
-rw-r--r-- 1 root root 136 Apr  1  2016 twemproxy-stable-trusty.list

/etc/apt/trusted.gpg.d:
total 40K
-rw-r--r-- 1 root root  351 Dec  9  2015 chris-lea-node_js.gpg
-rw-r--r-- 1 root root0 Dec  9  2015 chris-lea-node_js.gpg~
-rw-r--r-- 1 root root  15K Sep 14 09:29 puppetlabs-keyring.gpg
-rw-r--r-- 1 root root  12K Aug 29 23:28 puppetlabs-keyring.gpg~
-rw-r--r-- 1 root root 4.0K Aug 22  2014 puppetlabs-nightly-keyring.gpg
-rw-r--r-- 1 root root 1.2K Apr  1  2016 twemproxy-stable.gpg
-rw-r--r-- 1 root root0 Apr  1  2016 twemproxy-stable.gpg~

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

Title:
  apt-get throwing ValueError: Invalid header value 'AWS
  ASIAJ5KTV3ZQHPUKWSAQ:W9GzdJOuZYKf+qYITznWGgYXx9E=\n'

Status in python2.7 package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04
  Package:libpython2.7-minimal 2.7.6-8ubuntu0.3 

  After updated to libpython2.7:amd64 2.7.6-8ubuntu0.3 apt-get update
  throws the following error

  W: Failed to fetch 
s3://XXX.s3.amazonaws.com/repo/dists/stable/main/binary-amd64/Packages: 
ValueError: Invalid header value 'AWS 
ASIAJ5KTV3ZQHPUKWSAQ:W9GzdJOuZYKf+qYITznWGgYXx9E=\n'
  E: Some index files failed to download. They have been ignored, or old ones 
used instead.
  E: Couldn't rebuild 

[Touch-packages] [Bug 1636381] Re: Details views in dialogs are too small

[Wolf Rogner]

This issue occurs in:
- deja-dup
- software updater

In applications that provide grid views (PgAdminIII) the grid is
illegible (fonts larger than row height).

My screen scaling factor is 1,62

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

Title:
  Details views in dialogs are too small

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Details views in dialogs are too small, the viewing height is approx. 15px.
  My machine has a screen resolution of 2880x1800 on 15". I have to adjust the 
scaling to 1,62 to be able to read text. This leads to just half a line 
displayed in the viewing slot.

  Initially I reported this issue with deja-dup
  (https://bugs.launchpad.net/bugs/1635197) but this issue also shows up
  on several other dialog boxes (e.g. system updates - download of
  repos, ...).

  Thus I presume it either to be related with Unity or xorg.

  If you need additional information to identity the source, let me
  know.

  This behaviour is new to 16.10 and can be reproduced on any machine
  that I have access to.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Oct 25 07:59:44 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-26-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.8.0-26-generic, x86_64: installed
   nvidia-367, 367.57, 4.8.0-26-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00f7]
   NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2]
  InstallationDate: Installed on 2016-10-22 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Apple Inc. MacBookPro10,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic.efi.signed 
root=UUID=9a60a19c-458f-4dca-8617-f7c6cacf9658 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  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-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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: Mon Oct 24 16:16:55 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 

[Touch-packages] [Bug 1616422] Re: [trusty SRU/FFE] Add systemd binary package for snapd

[Po-Hsu Lin]

Hello,

I tried to verify this with trusty server image on a laptop, everything
act as expected before step 6 (except that stuff like desktop startup,
suspend on lid close can't be tested with server image). After that it
failed with:

ubuntu@ubuntu:~$ sudo snap install test-snapd-tools
error: cannot perform the following tasks:
- Setup snap "test-snapd-tools" (3) security profiles (cannot setup apparmor 
for snap "test-snapd-tools": cannot load apparmor profile 
"snap.test-snapd-tools.block": cannot load apparmor profile: exit status 1
apparmor_parser output:
AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.test-snapd-tools.block in 
/var/lib/snapd/apparmor/profiles/snap.test-snapd-tools.block at line 305: 
syntax error, unexpected TOK_CONDLISTID, expecting TOK_MODE
)
- Setup snap "test-snapd-tools" (3) security profiles (cannot load apparmor 
profile "snap.test-snapd-tools.block": cannot load apparmor profile: exit 
status 1
apparmor_parser output:
AppArmor parser error for 
/var/lib/snapd/apparmor/profiles/snap.test-snapd-tools.block in 
/var/lib/snapd/apparmor/profiles/snap.test-snapd-tools.block at line 305: 
syntax error, unexpected TOK_CONDLISTID, expecting TOK_MODE
)

snapd came from Thomas' ppa

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

Title:
  [trusty SRU/FFE] Add systemd binary package for snapd

Status in init-system-helpers package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in init-system-helpers source package in Trusty:
  Fix Committed
Status in systemd source package in Trusty:
  Fix Committed

Bug description:
  Rationale: For backporting snapd to 14.04 LTS, we need to provide
  systemd's service manager (not just logind and auxiliary services like
  logind or timesyncd). upstart will continue to do the actual booting,
  and systemd will act as a "deputy init" which by default does not ship
  with/start any services by itself. We will only support this on server
  (at the first iteration at least), not on desktops.

  Regression potential: This is a new binary package in universe, so
  existing systems are unaffected (provided that we ensure that the
  other binary packages do not change and there are no code changes that
  affect processes other than the "deputy pid 1" service manager). So
  for plain upgrades the regression potential is very low. However,
  there is a medium potential for breakage when actually installing the
  new systemd package, as it might interfere with upstart jobs or other
  running processes, cause boot/shutdown hangs, etc.

  For init-system-helpers, the regression potential is near-zero: We
  never had (and never will) systemd as pid 1 in trusty, so deb-systemd-
  invoke was previously never called. It does get called now if you
  install Ubuntu packages that ship a systemd unit, so we need to make
  that a no-op to retain the current behaviour.

  Test plan:
   1. Dist-upgrade a trusty installation to the proposed versions. Ensure this 
does not pull in "systemd", and that booting, shutdown, desktop startup, 
suspend on lid close, resume, logout, and user switching all still work.

   2. Install the "systemd" binary package (this will replace/remove
  systemd-shim). Verify that you can talk to the service manager with
  "sudo systemctl status". Check that booting and shutdown continues to
  work without (significant) delays.

   3. Ensure that "sudo journalctl" works and that "sudo systemctl
  status systemd-journald" is running and has a few lines of log at the
  end (unlike what you get when you run systemctl as user).

   4. Install a package that ships a systemd .service file, such as
  "haveged". Ensure that the service file is ignored, "pgrep -af
  haveged" should only have *one* process and "systemctl status haveged"
  should not be running (it should not exist, or not be enabled and be
  inactive). [This part also needs the updated init-system-helpers].

     The only services that are running are expected to be systemd-
  journald.service and systemd-journald.socket.

   5. Ensure that the standard targets are active, as that is where
  third-party/snap services hook into:

  systemctl status sysinit.target multi-user.target default.target

   6. Install snapd (not in trusty yet, e. g. from Thomas' PPA) and
  ensure you can install a snap, and its services start after installing
  the snap and after rebooting.

   7. Run "sudo apt-get install --reinstall systemd" to ensure that
  upgrades to newer systemd trusty versions work. The running systemd
  should *not* be restarted as that would disrupt snapd and its services
  (verify that the pid in "initctl status systemd" is the same before
  and after the upgrade).

   8. Run "sudo apt install -y colord && sudo apt purge -y colord". This
  should succeed.

   9. Dist-upgrade to 16.04 to ensure that there are no file 

[Touch-packages] [Bug 1643843] Re: Distorted colours after suspend / resume cycle

[Jan-Marek Glogowski]

I can't bisect the problem, because for the two kernels I build, suspend was 
broken and the PC didn't wake up from 2nd suspend :-(
I also tried 4.9-rc6 (albeit on an Arch Linux), which shows the same bug.

** Package changed: xorg (Ubuntu) => linux-lts-xenial (Ubuntu)

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

Title:
  Distorted colours after suspend / resume cycle

Status in X.Org X server:
  Unknown
Status in linux-lts-xenial package in Ubuntu:
  New

Bug description:
  When waking up the system from a suspend-resume cycle, the display most times 
shows distorted colours.
  As a workaround one can switch to the linux console (VT) and back to fix the 
display.
  Alternatively triggering DPMS also fixes the problem (xset dpms force off ; 
sleep 0.1; xset dpms force on)

  Hardware:
   01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
   Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]
   PCIID: 1002:6779

  I've tested Ubuntu Xenial (16.04) with the latest updates:

  mesa 11.2.0-1ubuntu2.2
  xserver-xorg-video-radeon 1:7.7.0-1
  linux-image-4.4.0-47-generic 4.4.0-47.68
  xserver-xorg-core 2:1.18.3-1ubuntu2.3

  I've tried older kernels, xorg, linux-firmware, as a colleague claimed
  it started for him after some of the latest Ubuntu updates, but
  couldn't find a working configuration.

  I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with
  XFCE, but instantly with the Unity session, but probably XFCE was just
  lucky, as sometimes I also had series of working (~5) cycles. Current
  versions:

  mesa 12.0.3-1ubuntu2
  xserver-xorg-video-radeon 1:7.7.1-1
  linux-image-4.8.0-27-generic 4.8.0-27.29
  xserver-xorg-core 2:1.18.4-1ubuntu6.1

  I'm also going to test Trusty (14.04) to check if it's really a
  regression. At least I have never seen this problem while running it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Nov 22 12:21:24 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 
6450 [1642:3a75]
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 4524BL8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic 
root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9HKT54AUS
  dmi.board.vendor: LENOVO
  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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 4524BL8
  dmi.product.version: ThinkCentre M91p
  dmi.sys.vendor: LENOVO
  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-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  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.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: Tue Nov 22 11:56:40 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1643843/+subscriptions

-- 

Re: [Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Roger Joness]

Should I as just a user ignore this problem? Don't understand what is going
on really.

On Thu, 24 Nov 2016 at 04:45, Isiramen Akeeminemen <
1642...@bugs.launchpad.net> wrote:

> so is there any thing i can do to make things better, or should i think
> it is not a threat
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1643196).
> https://bugs.launchpad.net/bugs/1642966
>
> Title:
>   package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
>   pre-removal script returned error exit status 1
>
> Status in cups package in Ubuntu:
>   Confirmed
>
> Bug description:
>   This is in xenial-proposed, please block release to -updates
>   accordingly :)
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: cups-daemon 2.1.3-4
>   ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
>   Uname: Linux 4.4.0-46-generic x86_64
>   NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
>   ApportVersion: 2.20.1-0ubuntu2.1
>   Architecture: amd64
>   CupsErrorLog:
>
>   Date: Fri Nov 18 11:13:15 2016
>   ErrorMessage: subprocess new pre-removal script returned error exit
> status 1
>   InstallationDate: Installed on 2016-05-02 (200 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   Lpstat: device for mallards-officejet-pro-8600:
> dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
>   MachineType: Dell Inc. XPS 15 9550
>   Papersize: a4
>   PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups
> 3.16.3
>   ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed
> root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed
> root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.1
>apt  1.2.15
>   SourcePackage: cups
>   Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess
> new pre-removal script returned error exit status 1
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/07/2016
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 01.02.00
>   dmi.board.name: 0N7TVV
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: XPS 15 9550
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+subscriptions
>
-- 
Sent from my IPad

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 1463023] Re: systemd Timed out waiting for device swap and file system check

[Alexander Adam]

I'm having the same issue now. I upgraded from Ubuntu 16.04 to 16.10.
I was able to boot twice into a running system, but I had no luck the other 
times besides from these two times.

However, this gives you the chance to, hopefully, solve this issue.
And as I'm landing in the recovery console with decrypted and mounted root 
partition I guess it may be solvable.

I can't really remember how the cryptsetup stuff worked so it may really
be related to some changed / referenced uuids?

I found posts from other people with the same issue but none of them
seem to got it solved.

** Attachment added: "logs"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1463023/+attachment/4782351/+files/logs.tar.gz

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

Title:
  systemd Timed out waiting for device swap and file system check

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  
  My Ubuntu 15.04 did not start --or took so long that I switched back to 
upstart!

  ISSUE: (systemd during the boot)

  Timed out waitingfor device dev-disk-by\x2duuid-... (swap)
  Dependency failed for /dev/disk/by-uuid/... (swap)
  Dependency failed for Swap.
  Timed out waiting for device dev-sdaX.device(swap)
  Dependency failed for Swap Partition.
  Failed to start udev Wait for Complete Device Initialization.
  See "systemctl status systemd-udev-settle.service" for details.
  Starting File System Check on Root Device...
  Starting Copy rules generated while the root was ro...
  (1 of 2) A start job is running for File System Check on Root Device (3min 
28s / no limit)
  ...
   No tainted 3.19.0-18-generic #18-Ubuntu
  "echo 0> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  INFO: task systemd-udevd:336 blocked for more than 120 seconds.
  ...
  INFO: task systemd-udevd:338 blocked for more than 120 seconds.
  ...
  INFO: task systemd-udevd:346 blocked for more than 120 seconds.
  ...
  (1 of 2) A start job is running for File System Check on Root Device (4min 3s 
/ no limit)

  WORKAROUND:

  apt-get -qq -y install upstart-sysv # switch back to upstart
  
http://linux.softpedia.com/blog/Ubuntu-15-04-Users-Can-Switch-Off-Systemd-and-Use-Upstart-479373.shtml
  P.S. don't ask me to go back to systemd-sysv... I am fine with upstart

  TECHNICAL DETAILS:

  $ lsb_release -r
  Release:  15.04

  $ uname -r
  3.19.0-18-generic

  $ sudo dmidecode -s system-product-name
  MacBookPro8,2

  $ grep "^GRUB_CMDLINE_LINUX_DEFAULT" /etc/default/grub
  GRUB_CMDLINE_LINUX_DEFAULT="transparent_hugepage=always intel_iommu=on 
acpi_irq_nobalance cgroup_enable=memory swapaccount=1 libata.force=noncq 
modeset=1 hybridopts=ON,IGD,OFF i915.modeset=0 radeon.modeset=1 radeon.dpm=1 
radeon.audio=1 i915.lvds_channels=2 quirks.mbp_force_ahci=1 
acpi_backlight=vendor reboot=pci"

  $ cat /etc/fstab
  #
  # / was on /dev/sda5 during installation
  UUID=6619a7e9-4b94-4e9b-8dbe-4110f89dde74 /   ext4
errors=remount-ro 0   1
  # swap was on /dev/sda6 during installation
  UUID=813e9dc2-c678-4959-ac89-e6660f886942 noneswapsw  
0   0

  # lsblk -f
  NAME   FSTYPE  LABELUUID MOUNTPOINT
  sda  
  ├─sda1 vfatEFI  67E3-17ED
  ├─sda2 hfsplus Macintosh HD 2ba5bbc1-fff0-36ea-ade4-140386274279 
  ├─sda3 hfsplus Recovery HD  9e776f16-ceb4-37e6-b4ce-4e75c1db5444 
  ├─sda4   
  ├─sda5 ext4 6619a7e9-4b94-4e9b-8dbe-4110f89dde74 /
  └─sda6 swap 813e9dc2-c678-4959-ac89-e6660f886942 [SWAP]
  sr0   

  # blkid 
  /dev/sda1: LABEL="EFI" UUID="67E3-17ED" TYPE="vfat" PARTLABEL="EFI System 
Partition" PARTUUID="5d71ff71-9843-473d-90e7-4c780c8a494d"
  /dev/sda2: UUID="2ba5bbc1-fff0-36ea-ade4-140386274279" LABEL="Macintosh HD" 
TYPE="hfsplus" PARTLABEL="Macintosh HD" 
PARTUUID="4e4c2249-24f8-4229-9325-d4aafd7ac093"
  /dev/sda3: UUID="9e776f16-ceb4-37e6-b4ce-4e75c1db5444" LABEL="Recovery HD" 
TYPE="hfsplus" PARTLABEL="Recovery HD" 
PARTUUID="a986e3e1-ed3b-44bb-a75b-87b54434380d"
  /dev/sda5: UUID="6619a7e9-4b94-4e9b-8dbe-4110f89dde74" TYPE="ext4" 
PARTUUID="9d860cb1-1334-4f79-a07a-01b8818c4aab"
  /dev/sda6: UUID="813e9dc2-c678-4959-ac89-e6660f886942" TYPE="swap" 
PARTUUID="bf1271f6-8d51-4510-8979-666c9546f1f3"
  /dev/sda4: PARTUUID="2b731a42-bd29-4548-8f0e-a9889ee9486b"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1463023/+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 1641954] [NEW] Output switches from HDMI speakers to internal speakers on DPMS off

[Cristian Klein]

Could you tell me exactly which pulseaudio package you used? I could try to
re-reproduce the bug on my end.

2016-11-24 2:51 GMT+01:00 Luke Yelavich :

> On Wed, Nov 16, 2016 at 12:58:14AM AEDT, Cristian Klein wrote:
> > (1) Alice listens to music on her speakers, which are connected to the
> > screen, which is connected through HDMI to the computer.
> >
> > (2) Alice leaves the computer, the screen gets suspended (DPMS off).
> >
> > (3) PulseAudio sees that the HDMI output got disconnected (although only
> > for a short interval) and switches to internal speaker.
>
> Ok, with a fresh Xenial install, I don't seem to get this behavior. I
> have tested with 2 different monitors, both different brands from each
> other. I set the HDMI audio out as the output, start playing audio, and
> let the screen turn off and/or run xset dpms force off. In either case,
> audio stops playing, but does not switch to another device. When I press
> a key and the screen turns back on, the music resumes playback on the
> monitor's speakers.
>
> I should note that I've also tested this on 3 different machines, 2 that
> were also connected to speakers via 3.5mm analog jack, and another via
> S/PDIF.
>
> Am I missing something?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1641954
>
> Title:
>   Output switches from HDMI speakers to internal speakers on DPMS off
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+
> bug/1641954/+subscriptions
>

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

Title:
  Output switches from HDMI speakers to internal speakers on DPMS off

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio 8.0 includes a well-known user-experience regression: Its
  new auto-routing algorithm tries to switch to another output, as soon
  as the active output gets disconnected. This leads to the following
  bad user experience:

  (1) Alice listens to music on her speakers, which are connected to the
  screen, which is connected through HDMI to the computer.

  (2) Alice leaves the computer, the screen gets suspended (DPMS off).

  (3) PulseAudio sees that the HDMI output got disconnected (although
  only for a short interval) and switches to internal speaker.

  (4) Alice returns to the computer but finds that the music is now
  playing through the internal speakers.

  (5) Alice can switch the output to the HDMI speakers manually, but the
  above user experience bug will reoccur when she leaves the computer
  again.

  This is a well-known upstream bug that was fixed in PulseAudio 9.0.
  Due to the fact that Ubuntu 16.04.1 LTS uses PulseAudio 8.0, it is
  desirable to backport this fix to PulseAudio 8.0, so that all LTS
  users have better experience. Upstream said they would not do this and
  that I should report this to Ubuntu directly.

  Other information:
  * Upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=93946
  * Fix 1: 
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=04040c522f5f62dda50ac927e92453381d419f09
  * Fix 2: 
https://github.com/pulseaudio/pulseaudio/commit/23c15c3b52a958887c1f8cad3c94879a8770ef0e

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1641954/+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 1644237] Re: unity8 fails to start as guest user

[Oliver Grawert]

related to bug 1593407 ?

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

Title:
  unity8 fails to start as guest user

Status in Canonical System Image:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  This is shown in unity8.log:

  [2016-11-23 15:59:25.820868] mirserver: Starting
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132):
 Throw in function 
mir::DefaultServerConfiguration::the_graphics_platform()::
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Exception while creating graphics platform
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245):
 Throw in function 
mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const 
string&, const string&, const 
std::shared_ptr&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Nested Mir Platform Connection Error: Failed to connect 
to server socket: Permission denied


  [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start
  initctl: No such variable: UNITY_MIR_SOCKET

  running current zesty, but I had the same problem on yakkety too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644237/+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 1643459] Re: additional writable paths for other system services

[Ubuntu Foundations Team Bug Bot]

The attachment "0001-misc-create-var-lib-udisks2-in-post-install.patch"
seems to be a patch.  If it isn't, please remove the "patch" flag from
the attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  additional writable paths for other system services

Status in Canonical System Image:
  New
Status in lxc-android-config package in Ubuntu:
  In Progress
Status in udisks2 package in Ubuntu:
  New

Bug description:
  /var/tmp: rtkit systemd service uses PrivateTmp
  /var/lib/udisks2: udisks2
  /var/lib/dhcp: isc-dhcp-server leases files

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1643459/+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 1644445] Re: avila xenial+systemd port takes too long to boot to GUI

[Vicamo Yang]

** Merge proposal linked:
   https://code.launchpad.net/~vicamo/repowerd/+git/repowerd/+merge/311694

** Changed in: repowerd (Ubuntu)
 Assignee: (unassigned) => Vicamo Yang (vicamo)

** Changed in: lxc-android-config (Ubuntu)
   Status: New => In Progress

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

** Changed in: ubuntu-touch-session (Ubuntu)
   Status: New => In Progress

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

Title:
  avila xenial+systemd port takes too long to boot to GUI

Status in Canonical System Image:
  New
Status in lxc-android-config package in Ubuntu:
  In Progress
Status in repowerd package in Ubuntu:
  In Progress
Status in ubuntu-touch-session package in Ubuntu:
  In Progress

Bug description:
  We found devices will take about 80 seconds to show the ubuntu flash UI, and 
after about 60 seconds to show the login UI.
  So it will take more than 2 minutes to boot up the system.

  [[1. on xenial+systemd/arm64]]:
  Second boot time:
  Without flight mode: 25s to ubuntu splash, 93s to login dialog
  With flight mode: 46s to ubuntu splash, 120s to login dialog
  Without flight mode, but disable ofono completely: 84s to ubuntu splash, 143s 
to login dialog. Worse cases are also observed.

  $ adb shell system-image-cli -i
  current build number: 84
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-11-17 03:23:16
  version version: 84
  version ubuntu: 20161117
  version device: 20161014.0
  version custom: 20161117

  [[2. on vivid+upstart/armhf]]:
  Second boot time:
  Without flight mode: The worse case I got is 78s to ubuntu splash, 92s to 
login dialog. However I have this only once and am never able to reproduce the 
same. The usual cases have almost no difference from the following two cases. 
All boot to splash in 10s and login dialog in around 22s.

  With flight mode: 9s to ubuntu splash, 19s to login dialog
  Without flight mode, but disable ofono completely: 9s to ubuntu splash, 21s 
to login dialog

  $ adb shell system-image-cli -i
  current build number: 235
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
  last update: 2016-11-19 11:56:02
  version version: 235
  version ubuntu: 20161119
  version device: 20160809.0
  version custom: 20160831--42-26-vivid

  [[Debug Tips]]

  1. Flash xenial user build:

$ ubuntu-device-flash touch --bootstrap --wipe \
  --channel=ubuntu-touch/staging/ubuntu \
  --device=frieza_arm64 [--recovery-image=recovery.img]

  2. Flash vivid user build:

$ ubuntu-device-flash touch --bootstrap --wipe \
  --channel=ubuntu-touch/rc-proposed/bq-aquaris-pd.en \
  --device=frieza [--recovery-image=recovery.img]

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/165/+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