[Touch-packages] [Bug 1696147] Re: apport failing to collect logs on armhf

[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/1696147

Title:
  apport failing to collect logs on armhf

Status in apport package in Ubuntu:
  Expired

Bug description:
  I simply created the user and proceeded to install, and on the
  "creating user" portion of setup it crashed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubiquity 2.21.63.3
  Uname: Linux 4.4.38-v7+ armv7l
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: armhf
  Date: Tue Jun  6 11:04:46 2017
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1696147/+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 1647393] Re: broken upgrade or whitespace diff?

[Launchpad Bug Tracker]

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

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

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

Title:
  broken upgrade or whitespace diff?

Status in resolvconf package in Ubuntu:
  Expired

Bug description:
  I got a conffile prompt off:

  $ diff -u head head.dpkg-old 
  --- head  2016-11-28 23:37:41.0 +
  +++ head.dpkg-old 2016-01-27 06:04:06.414599155 +
  @@ -1,5 +1,3 @@
   # Dynamic resolv.conf(5) file for glibc resolver(3) generated by 
resolvconf(8)
   # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  -# 127.0.0.53 is the systemd-resolved stub resolver.
  -# run "systemd-resolve --status" to see details about the actual nameservers.
   

  
  Is this just a whitespace difference? Or is there a broken conf upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1647393/+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 1710441] Re: package linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  package linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  How to solve

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Aug 12 09:17:52 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2017-08-07 (5 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1710441/+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 1710441] Re: package linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  How to solve

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Aug 12 09:17:52 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2017-08-07 (5 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1710441/+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 1710441] [NEW] package linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Hemant Kumar]

Public bug reported:

How to solve

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Sat Aug 12 09:17:52 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2017-08-07 (5 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: initramfs-tools
Title: package linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1710441

Title:
  package linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  How to solve

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Aug 12 09:17:52 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2017-08-07 (5 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1710441/+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 1704533] Re: French language locale missing : Gnome-Weather

[Claude Champagne]

Is there some way to fix it or a workaround ?

Something I could try to help ?

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

Title:
  French language locale missing : Gnome-Weather

Status in Ubuntu Translations:
  New
Status in gnome-weather package in Ubuntu:
  In Progress
Status in libgweather package in Ubuntu:
  Confirmed

Bug description:
  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1704533/+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 1710427] Re: tracker-extract crashed with signal 31 in __GI___openat()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  tracker-extract crashed with signal 31 in __GI___openat()

Status in tracker package in Ubuntu:
  New

Bug description:
  Upgraded to Artful dev and logged into ubuntu GNOME and this crash
  popped up.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: tracker-extract 1.12.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug 13 07:56:59 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/tracker/tracker-extract
  InstallationDate: Installed on 2015-09-28 (684 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  Signal: 31
  SourcePackage: tracker
  StacktraceTop:
   __GI___openat (fd=22, file=0x7f88cc1d3e01 "sys", oflag=2752512) at 
../sysdeps/unix/sysv/linux/wordsize-64/../openat.c:58
   () at /lib/x86_64-linux-gnu/libudev.so.1
   () at /lib/x86_64-linux-gnu/libudev.so.1
   () at /lib/x86_64-linux-gnu/libudev.so.1
   () at /lib/x86_64-linux-gnu/libudev.so.1
  Title: tracker-extract crashed with signal 31 in __GI___openat()
  UpgradeStatus: Upgraded to artful on 2017-08-12 (0 days ago)
  UserGroups: adm cdrom dip docker fuse kismet libvirt libvirtd lp lpadmin lxd 
mail mythtv netdev plugdev sambashare sbuild scanner sudo video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1710427/+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 1502978] Re: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build against kernel 4.3 [firegl_public.c:... error: void value not ignored as it ought to be ... se

[Yu]

I got this bug while plugging in my HDMI cable, screen was hanging
(super lag, it seems like the GPU rendering error). It works fine with
VGA interface.

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

Title:
  fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
  against kernel 4.3 [firegl_public.c:... error: void value not ignored
  as it ought to be ... seq_printf]

Status in fglrx-installer package in Ubuntu:
  Invalid
Status in fglrx-installer-updates package in Ubuntu:
  Invalid
Status in software-properties package in Ubuntu:
  Invalid
Status in fglrx-installer source package in Trusty:
  New
Status in fglrx-installer-updates source package in Trusty:
  New
Status in software-properties source package in Trusty:
  Triaged

Bug description:
  Probably fglrx-installer. 
  However I am not using fglrx , I am using xserver-xorg-video-ati and 
xserver-xorg-video-amdgpu.
  This happened when I installed kernel 4.3.0-040300rc4 in Ubuntu Wily Werewolf.
  Graphic card Radeon R9 380

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: fglrx-core 2:15.201-0ubuntu1
  Uname: Linux 4.3.0-040300rc4-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19-0ubuntu1
  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
  DKMSKernelVersion: 4.3.0-040300rc4-generic
  Date: Mon Oct  5 18:33:50 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.201, 4.2.0-14-generic, x86_64: installed
  DuplicateSignature: 
dkms:fglrx-core:2:15.201-0ubuntu1:/var/lib/dkms/fglrx-core/15.201/build/2.6.x/firegl_public.c:639:9:
 error: void value not ignored as it ought to be
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2015]
  InstallationDate: Installed on 2015-02-01 (246 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150130)
  MachineType: Gigabyte Technology Co., Ltd. GA-MA770-UD3
  PackageVersion: 2:15.201-0ubuntu1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-040300rc4-generic 
root=UUID=494a814f-1825-4bfc-941f-1d7ee79111d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu4
   apt  1.0.9.10ubuntu7
  SourcePackage: fglrx-installer
  Title: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-MA770-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/09/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA770-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+15.10.20151002-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Mon Oct  5 18:37:05 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9
  xserver.video_driver: amdgpu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1502978/+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 1567107] Re: [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs

[can avar]

** Also affects: initramfs-tools
   Importance: Undecided
   Status: New

** No longer affects: initramfs-tools

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

Title:
  [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released

Bug description:
  Because Generation 2 virtual machines in Hyper-V are presented with a
  minimal set of EFI hardware, the kernel module "hyperv_keyboard" must
  be present to interact with the console keyboard. On systems with disk
  encryption, the user will be prompted for the key to decrypt the disk,
  but cannot enter the password because no keyboard driver is present.

  This issue appears to exist in all Ubuntu releases that support EFI
  and are therefore eligible to be used as Generation 2 VMs, most
  recently tried with the April 5 ISO of the day for 16.04 (pre-
  release).

  This module *is* present when the grub menu is presented and later when the 
kernel is fully loaded.
  FYI, if some mechanism requires a mouse or touch, the hid_hyperv module will 
also be needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1567107/+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 1567107] Re: [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs

[can avar]

https://bugs.launchpad.net/bugs/1567107

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

Title:
  [Hyper-V] hyperv_keyboard module needed for Generation 2 VMs

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released

Bug description:
  Because Generation 2 virtual machines in Hyper-V are presented with a
  minimal set of EFI hardware, the kernel module "hyperv_keyboard" must
  be present to interact with the console keyboard. On systems with disk
  encryption, the user will be prompted for the key to decrypt the disk,
  but cannot enter the password because no keyboard driver is present.

  This issue appears to exist in all Ubuntu releases that support EFI
  and are therefore eligible to be used as Generation 2 VMs, most
  recently tried with the April 5 ISO of the day for 16.04 (pre-
  release).

  This module *is* present when the grub menu is presented and later when the 
kernel is fully loaded.
  FYI, if some mechanism requires a mouse or touch, the hid_hyperv module will 
also be needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1567107/+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 1690671] Re: Pointer clicks and hovering fail to have effect at the very left and top borders of screen

[Douglas H. Silva]

** Description changed:

  THE ISSUE:
  The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.
  
  This affects any desktop environment made with gtk+3, such as MATE,
- Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
- affected. Any DE still using gtk2 works fine. I tested 3 different
+ Pantheon, parts of Xfce, Budgie and probably others. GNOME and Unity are
+ not affected. Any DE still using gtk2 works fine. I tested 3 different
  computers with Intel Graphics and they were all displaying the same
  glitch.
  
  It can always be reproduced. I can record a video of the issue if
  needed.

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

Title:
  Pointer clicks and hovering fail to have effect at the very left and
  top borders of screen

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  THE ISSUE:
  The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.

  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME and Unity
  are not affected. Any DE still using gtk2 works fine. I tested 3
  different computers with Intel Graphics and they were all displaying
  the same glitch.

  It can always be reproduced. I can record a video of the issue if
  needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1690671/+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 1706936] Re: Wrong version of libgles1-mesa in Xenial-updates

[Dibo]

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

I had same problem few months ago with Linux Mint 18.1 KDE and VLC daily
ppa. Solved it by removing ppa xorg-edgers but few weeks ago it came
back on Mint 18.2 (IIRC not immediately after update to 18.2). Again
related to VLC:

astępujące pakiety zostaną zaktualizowane:  
  libgl1-mesa-glx libglapi-mesa libgles2-mesa 
3 pakietów aktualizowanych, 0 instalowanych, 0 do usunięcia i 0 
nieaktualizowanych.
Do pobrania 165 kB archiwów. Zwolnione po rozpakowaniu: 1024 B.
Następujące pakiety mają niespełnione zależności:
 libgles1-mesa : Wymaga: libglapi-mesa (= 12.0.6-0ubuntu0.16.04.1) ale 
zaplanowana jest instalacja wersji 17.0.7-0ubuntu0.16.04.1.
Następujące działania rozwiążą problemy z zależnościami:

 Usunięcie następujących pakietów:
1) libgles1-mesa  
2) vlc

It is always (same as previous time) proposing uninstall VLC and mesa. I'm 
pressing "n" so it propose to keep old version and this is how I keep my distro 
updated, always keeping old version.
And this is my rdepends output:

apt-cache rdepends libgles1-mesa
libgles1-mesa
Reverse Depends:
  libgles1-mesa-dev
 |vlc
  libgles1-mesa-lts-xenial
  libgles1-mesa-lts-wily-dbg
  libgles1-mesa-lts-wily
  libgles1-mesa-lts-vivid-dbg
  libgles1-mesa-lts-vivid
  libgles1-mesa-lts-utopic-dbg
  libgles1-mesa-lts-utopic
  libgles1-mesa-dev
 |vlc
  libopentk1.1-cil
  libgles1-mesa-lts-wily-dbg
  libgles1-mesa-lts-wily
  libgles1-mesa-lts-vivid-dbg
  libgles1-mesa-lts-vivid
  libgles1-mesa-lts-utopic-dbg
  libgles1-mesa-lts-utopic


Also attached repo's screenshots

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

Title:
  Wrong version of libgles1-mesa in Xenial-updates

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Xenial-updates has the following packages:

  - libgles1-mesa (12.0.6-0ubuntu0.16.04.1)
  - libglapi-mesa (17.0.7-0ubuntu0.16.04.1)

  The first one depends on libglapi-mesa (= 12.0.6-0ubuntu0.16.04.1),
  but libglapi-mesa has a higher version and so there's a conflict.

  I've had to remove libgles1-mesa for now, to avoid the conflict.

  I have Linux Mint 18.1 but I believe it affects anyone using xenial-
  updates.

  Source links I used to verify it's a xenial-updates problem:

  https://packages.ubuntu.com/xenial-updates/libs/libgles1-mesa
  https://packages.ubuntu.com/xenial-updates/libglapi-mesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1706936/+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 1709193] Re: Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer

[Launchpad Bug Tracker]

This bug was fixed in the package gnutls28 - 3.5.8-6ubuntu2

---
gnutls28 (3.5.8-6ubuntu2) artful; urgency=medium

  * use_normal_priority_for_openssl_sslv23.diff by Andreas Metzler:
OpenSSL wrapper: SSLv23_*_method translates to NORMAL GnuTLS priority,
which includes TLS1.2 support. (LP: #1709193)

 -- Simon Deziel   Thu, 10 Aug 2017 00:34:06
+

** Changed in: gnutls28 (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  Unable to use TLSv1.1 or 1.2 with OpenSSL compat layer

Status in gnutls26 package in Ubuntu:
  Invalid
Status in gnutls28 package in Ubuntu:
  Fix Released
Status in gnutls26 source package in Trusty:
  In Progress
Status in gnutls28 source package in Trusty:
  Won't Fix
Status in ssmtp source package in Trusty:
  Invalid
Status in gnutls26 source package in Xenial:
  Invalid
Status in gnutls28 source package in Xenial:
  In Progress
Status in ssmtp source package in Xenial:
  Invalid
Status in gnutls26 source package in Zesty:
  Invalid
Status in gnutls28 source package in Zesty:
  In Progress
Status in ssmtp source package in Zesty:
  Invalid
Status in gnutls26 source package in Artful:
  Invalid
Status in gnutls28 source package in Artful:
  Fix Released
Status in ssmtp source package in Artful:
  Invalid
Status in gnutls28 package in Debian:
  Fix Released

Bug description:
  [Impact]

  Applications using GnuTLS OpenSSL compat layer [1] are be unable to
  use modern TLS versions (1.1 and 1.2) when relying on the
  SSLv23_{client,server}_method functions.

  There is an industry-wide push to use modern TLS versions, see [2] and
  [3] for example.

  The proposed fix changes the compat layer to use GnuTLS' "NORMAL"
  priority [4] instead of hard-coding which protocol versions and
  ciphers to enable.

  [Test Case]

  1) Setup a mail submission server that uses StartTLS
  2) Setup sSMTP (uses GnuTLS OpenSSL compat layer) to relay
 through the mail relay using StartTLS
  3) Send an email while capturing with tcpdump/tshark
  4) Inspect the submission connection (TCP/587) and look for the protocol
 version negotiated by the client.

  Without the fix, you should see TLSv1.0. With the fix, it should be
  TLSv1.2.

  Please see the original issue description for more details.

  [Regression Potential]

  Regression risk should be low since it's a backport of a simple fix
  that landed in Debian in April 2017.

  [References]

  1: $ apt-cache rdepends libgnutls-openssl27
  libgnutls-openssl27
  Reverse Depends:
libgnutls-dev
libgnutls-dev
zoneminder
yaskkserv
tf5
ssmtp
snowdrop
sngrep
slrnpull
slrn
sipsak
macopix-gtk2
gnss-sdr
gkrellm
freewheeling
boinctui
iputils-ping

  2: https://lists.debian.org/debian-devel-announce/2017/08/msg4.html
  3: https://blog.pcisecuritystandards.org/migrating-from-ssl-and-early-tls
  4: https://gnutls.org/manual/html_node/Priority-Strings.html

  
  [Original issue description]

  sSMTP is limited to using TLSv1.0 and the "old" ciphers that come with
  it. Here's a packet capture when ssmtp connects to
  smtp.sdeziel.info:587 that offers TLSv1.0 and higher:

  $ tshark -ta -Vr submission.pcap | sed -n '/^Frame 14:/,/^Frame 15:/ p' | 
grep -E '^[[:space:]]+(Version|Cipher|Handshake Protocol)'
  Version: TLS 1.0 (0x0301)
  Handshake Protocol: Client Hello
  Version: TLS 1.0 (0x0301)
  Cipher Suites Length: 30
  Cipher Suites (15 suites)
  Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
  Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0041)
  Cipher Suite: TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0084)
  Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)
  Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
  Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
  Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA (0x0045)
  Cipher Suite: TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x0088)
  Cipher Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x0016)
  Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032)
  Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038)
  Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_128_CBC_SHA (0x0044)
  Cipher Suite: TLS_DHE_DSS_WITH_CAMELLIA_256_CBC_SHA (0x0087)
  Cipher Suite: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013)

  I would expect ssmtp to use TLSv1.2 and a recent cipher like the
  openssl s_client is able to do:

  $ echo | openssl s_client -connect 

[Touch-packages] [Bug 1710410] [NEW] Must run systemd-resolve --status before DNS resolving is operative

[WoJ]

Public bug reported:

Context: fresh install of zesty via

debootstrap --include=nano,dbus,iputils-ping,iproute2 zesty zesty1
http://fr.archive.ubuntu.com/ubuntu

ran via asystemd-nspawn with a static IP

1. Upon first connexion, a ping fails:

root@zesty1:~# ping google.com
ping: google.com: Temporary failure in name resolution

2. The content of /etc/resolv.conf:

root@zesty1:~# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

3. When running systemd-resolve --status:

root@zesty1:~# systemd-resolve --status
Global
 DNS Servers: 8.8.8.8
  8.8.4.4
  2001:4860:4860::
  2001:4860:4860::8844
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
(...)

4. After running this command the resolution is miraculously restored:

root@zesty1:~# ping google.com
PING google.com (172.217.22.142) 56(84) bytes of data.
64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=1 ttl=53 time=2.62 ms
64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=2 ttl=53 time=1.93 ms

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

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

Title:
  Must run systemd-resolve --status before DNS resolving is operative

Status in systemd package in Ubuntu:
  New

Bug description:
  Context: fresh install of zesty via

  debootstrap --include=nano,dbus,iputils-ping,iproute2 zesty zesty1
  http://fr.archive.ubuntu.com/ubuntu

  ran via asystemd-nspawn with a static IP

  1. Upon first connexion, a ping fails:

  root@zesty1:~# ping google.com
  ping: google.com: Temporary failure in name resolution

  2. The content of /etc/resolv.conf:

  root@zesty1:~# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  3. When running systemd-resolve --status:

  root@zesty1:~# systemd-resolve --status
  Global
   DNS Servers: 8.8.8.8
8.8.4.4
2001:4860:4860::
2001:4860:4860::8844
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
  (...)

  4. After running this command the resolution is miraculously restored:

  root@zesty1:~# ping google.com
  PING google.com (172.217.22.142) 56(84) bytes of data.
  64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=1 ttl=53 time=2.62 ms
  64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=2 ttl=53 time=1.93 ms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710410/+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 1710408] [NEW] dbus warning when open texmakdbus warning when open texmakerer

[Mahmoud Gadalla]

Public bug reported:

** (apport-gtk:5779): WARNING **: Couldn't connect to accessibility bus:
Failed to connect to socket /tmp/dbus-3kdh2k4Pws: Connection refused

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: dbus 1.10.6-1ubuntu3.3
ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
Uname: Linux 4.4.0-89-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Aug 12 21:06:03 2017
InstallationDate: Installed on 2016-12-28 (226 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)
upstart.dbus.log:
 Activating service name='org.gnome.GConf'
 Successfully activated service 'org.gnome.GConf'
 Activating service name='org.freedesktop.thumbnails.Cache1'
 Successfully activated service 'org.freedesktop.thumbnails.Cache1'

** Affects: dbus (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 dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1710408

Title:
  dbus warning when open texmakdbus warning when open texmakerer

Status in dbus package in Ubuntu:
  New

Bug description:
  ** (apport-gtk:5779): WARNING **: Couldn't connect to accessibility
  bus: Failed to connect to socket /tmp/dbus-3kdh2k4Pws: Connection
  refused

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dbus 1.10.6-1ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Aug 12 21:06:03 2017
  InstallationDate: Installed on 2016-12-28 (226 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.dbus.log:
   Activating service name='org.gnome.GConf'
   Successfully activated service 'org.gnome.GConf'
   Activating service name='org.freedesktop.thumbnails.Cache1'
   Successfully activated service 'org.freedesktop.thumbnails.Cache1'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1710408/+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 1710402] [NEW] package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: pacote libssl1.0.0:amd64 não está pronto para configuração não posso configurar (estado atu

[Virgínia]

Public bug reported:

o sistema ubuntu, tá informando falha de erro, toda vez que o sitema
operacional é inicializado.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Aug 11 14:49:29 2017
ErrorMessage: pacote libssl1.0.0:amd64 não está pronto para configuração  não 
posso configurar (estado atual 'half-installed')
InstallationDate: Installed on 2017-04-17 (117 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssl
Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
pacote libssl1.0.0:amd64 não está pronto para configuração  não posso 
configurar (estado atual 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openssl (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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1710402

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  pacote libssl1.0.0:amd64 não está pronto para configuração  não posso
  configurar (estado atual 'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  o sistema ubuntu, tá informando falha de erro, toda vez que o sitema
  operacional é inicializado.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Aug 11 14:49:29 2017
  ErrorMessage: pacote libssl1.0.0:amd64 não está pronto para configuração  não 
posso configurar (estado atual 'half-installed')
  InstallationDate: Installed on 2017-04-17 (117 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
pacote libssl1.0.0:amd64 não está pronto para configuração  não posso 
configurar (estado atual 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1710402/+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 1522675] Re: Warning messages about unsandboxed downloads

[Ads20000]

Martin, if you want to get this bug fixed please click on the link
Julian gave in #89 and rewrite the bug so it can be fixed in Ubuntu
16.04 and 17.04. It won't be fixed until that happens (and, ideally,
would be good if you could check it's working in 17.10, where it's
already been patched, as well). We know it's a problem but someone needs
to do the work to get it fixed (I don't feel able to sorry).

-- 
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:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in aptitude package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  Fix Released
Status in apt package in Debian:
  Fix Released
Status in aptitude package in Debian:
  Fix Released
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 1710399] [NEW] Unable to install packages

[Andrew Vagin]

Public bug reported:

We use docker and qemu-static to build our project for all supported
arch-es in travis. But a few days ago a ppc job started to fail with
this error:

Status: Downloaded newer image for ppc64le/ubuntu:trusty
 ---> 52071895775c
Step 2 : ENV QEMU_CPU POWER8
 ---> Running in 4d3df022afff
 ---> 755937024d05
Removing intermediate container 4d3df022afff
Step 3 : COPY scripts/build/qemu-user-static/usr/bin/qemu-ppc64le-static 
/usr/bin/qemu-ppc64le-static
 ---> 188daa3f7494
Removing intermediate container 472eb3b49e8e
Step 4 : ARG CC=gcc
 ---> Running in 8f626dc61623
 ---> 20139f6cb27c
Removing intermediate container 8f626dc61623
Step 5 : ARG ENV1=FOOBAR
 ---> Running in 2767f0ce96a6
 ---> 8a7ea42bae39
Removing intermediate container 2767f0ce96a6
Step 6 : RUN apt-get update && apt-get install -y 
build-essential protobuf-c-compiler 
libprotobuf-c0-dev libprotobuf-dev bsdmainutils 
protobuf-compiler python-minimal
 libaio-dev libcap-dev iptables 
libnl-3-dev libselinux-dev pkg-config   
  git-corelibnet-dev  ccache $CC
 ---> Running in ae68ad78ec81
Ign http://ports.ubuntu.com trusty InRelease
Get:1 http://security.ubuntu.com trusty-security InRelease [65.9 kB]
Get:2 http://ports.ubuntu.com trusty-updates InRelease [65.9 kB]
Get:3 http://ports.ubuntu.com trusty-backports InRelease [65.9 kB]
Get:4 http://ports.ubuntu.com trusty Release.gpg [933 B]
Get:5 http://ports.ubuntu.com trusty Release [58.5 kB]
Get:6 http://security.ubuntu.com trusty-security/universe Sources [73.1 kB]
Get:7 http://ports.ubuntu.com trusty-updates/universe Sources [236 kB]
Get:8 http://ports.ubuntu.com trusty-updates/main ppc64el Packages [993 kB]
Err http://security.ubuntu.com trusty-security/main ppc64el Packages
  404  Not Found [IP: 91.189.88.149 80]
Get:9 http://ports.ubuntu.com trusty-updates/restricted ppc64el Packages [40 B]
Err http://security.ubuntu.com trusty-security/restricted ppc64el Packages
  404  Not Found [IP: 91.189.88.149 80]
Get:10 http://ports.ubuntu.com trusty-updates/universe ppc64el Packages [499 kB]
Err http://security.ubuntu.com trusty-security/universe ppc64el Packages
  404  Not Found [IP: 91.189.88.149 80]
Get:11 http://ports.ubuntu.com trusty-updates/multiverse ppc64el Packages [6925 
B]
Err http://security.ubuntu.com trusty-security/multiverse ppc64el Packages
  404  Not Found [IP: 91.189.88.149 80]
Get:12 http://ports.ubuntu.com trusty-backports/main ppc64el Packages [14.0 kB]
Get:13 http://ports.ubuntu.com trusty-backports/restricted ppc64el Packages [40 
B]
Get:14 http://ports.ubuntu.com trusty-backports/universe ppc64el Packages [48.0 
kB]
Get:15 http://ports.ubuntu.com trusty-backports/multiverse ppc64el Packages 
[573 B]
Get:16 http://ports.ubuntu.com trusty/universe Sources [7926 kB]
Get:17 http://ports.ubuntu.com trusty/main ppc64el Packages [1615 kB]
Get:18 http://ports.ubuntu.com trusty/restricted ppc64el Packages [40 B]
Get:19 http://ports.ubuntu.com trusty/universe ppc64el Packages [7014 kB]
Get:20 http://ports.ubuntu.com trusty/multiverse ppc64el Packages [135 kB]
Fetched 18.8 MB in 10s (1771 kB/s)
W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/trusty-security/main/binary-ppc64el/Packages
  404  Not Found [IP: 91.189.88.149 80]
W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/trusty-security/restricted/binary-ppc64el/Packages
  404  Not Found [IP: 91.189.88.149 80]
W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/trusty-security/universe/binary-ppc64el/Packages
  404  Not Found [IP: 91.189.88.149 80]
W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/trusty-security/multiverse/binary-ppc64el/Packages
  404  Not Found [IP: 91.189.88.149 80]
E: Some index files failed to download. They have been ignored, or old ones 
used instead.

Here is a full log:
https://travis-ci.org/xemul/criu/jobs/263720066

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

** Package changed: apport (Ubuntu) => apt (Ubuntu)

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

Title:
  Unable to install packages

Status in apt package in Ubuntu:
  New

Bug description:
  We use docker and qemu-static to build our project for all supported
  arch-es in travis. But a few days ago a ppc job started to fail with
  this error:

  Status: Downloaded newer image for ppc64le/ubuntu:trusty
   ---> 52071895775c
  Step 2 : ENV QEMU_CPU POWER8
   ---> Running in 4d3df022afff
   ---> 755937024d05
  Removing intermediate container 4d3df022afff
  Step 3 : COPY scripts/build/qemu-user-static/usr/bin/qemu-ppc64le-static 
/usr/bin/qemu-ppc64le-static
   ---> 188daa3f7494
  

[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Bill Duetschler]

Looks like I misspoke, adding "HandleLidSwitchDocked=suspend" didn't
work.  I took the laptop offsite after closing the lid and when I
arrived at my destination the laptop was still warm and there had been
significant battery drain, as if it had been running full-blast all
along.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1710397] [NEW] Unable to identify package based on windows for some applications

[Donald Pellegrino]

Public bug reported:

When running ubuntu-bug -w the following message is output to terminal:

Gtk-Message: GtkDialog mapped without a transient parent. This is
discouraged.

Clicking on windows from GNOME Terminal or Backups has not effect.
Clicking on a Firefox window however, will trigger the expected
behavior. It seems ubuntu-bug -w is only recognizing some windows.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: apport 2.20.4-0ubuntu4.5
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CrashReports: 640:1000:122:995835:2017-08-12 12:30:28.203223748 
-0400:2017-08-12 12:30:27.252524580 
-0400:/var/crash/_usr_bin_update-notifier.1000.crash
CurrentDesktop: GNOME
Date: Sat Aug 12 13:40:46 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-08-12 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wayland-session zesty

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

Title:
  Unable to identify package based on windows for some applications

Status in apport package in Ubuntu:
  New

Bug description:
  When running ubuntu-bug -w the following message is output to
  terminal:

  Gtk-Message: GtkDialog mapped without a transient parent. This is
  discouraged.

  Clicking on windows from GNOME Terminal or Backups has not effect.
  Clicking on a Firefox window however, will trigger the expected
  behavior. It seems ubuntu-bug -w is only recognizing some windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4.5
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CrashReports: 640:1000:122:995835:2017-08-12 12:30:28.203223748 
-0400:2017-08-12 12:30:27.252524580 
-0400:/var/crash/_usr_bin_update-notifier.1000.crash
  CurrentDesktop: GNOME
  Date: Sat Aug 12 13:40:46 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-08-12 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1710397/+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 1710395] [NEW] package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 10

[Ekanath Chougale]

Public bug reported:

Login Loop is happening.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptOrdering:
 lightdm: Purge
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Aug 12 22:49:35 2017
ErrorMessage: subprocess installed pre-removal script returned error exit 
status 10
InstallationDate: Installed on 2017-08-12 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
LightdmConfig:
 [SeatDefaults]
 greeter-session=unity-greeter
 user-session=gnome
 greeter-show-manual-login=true
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: lightdm
Title: package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lightdm (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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1710395

Title:
  package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade:
  subprocess installed pre-removal script returned error exit status 10

Status in lightdm package in Ubuntu:
  New

Bug description:
  Login Loop is happening.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   lightdm: Purge
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Aug 12 22:49:35 2017
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 10
  InstallationDate: Installed on 2017-08-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=unity-greeter
   user-session=gnome
   greeter-show-manual-login=true
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: lightdm
  Title: package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade: 
subprocess installed pre-removal script returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1710395/+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 1710389] Re: Sound plays out of the speakers and no longer the headphones. No volume control for headphones anymore.

[Vash The Stampede]

** Summary changed:

- Sound plays out of the speakers and headphones at the same time. No volume 
control for headphones anymore.
+ Sound plays out of the speakers and no longer the headphones. No volume 
control for headphones anymore.

** Description changed:

  Plugging in headphones used to generate a pop up to select which audio
  device to play. This no longer occurs. Only get one output (speakers) in
  the sound controls when their used to be multiple. When plugging in
- headphones sound comes out of both the speakers and headphones at the
- same time.
+ headphones sound comes out of the speakers and no longer the headphones.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  dpepe  1788 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dpepe  1788 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Aug 12 12:32:10 2017
  InstallationDate: Installed on 2017-07-25 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.25
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.25:bd05/07/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

Title:
  Sound plays out of the speakers and no longer the headphones. No
  volume control for headphones anymore.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Plugging in headphones used to generate a pop up to select which audio
  device to play. This no longer occurs. Only get one output (speakers)
  in the sound controls when their used to be multiple. When plugging in
  headphones sound comes out of the speakers and no longer the
  headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dpepe  1788 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Aug 12 12:32:10 2017
  InstallationDate: Installed on 2017-07-25 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.25
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.25:bd05/07/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01: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/alsa-driver/+bug/1710389/+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 1710389] [NEW] Sound plays out of the speakers and headphones at the same time. No volume control for headphones anymore.

[Vash The Stampede]

Public bug reported:

Plugging in headphones used to generate a pop up to select which audio
device to play. This no longer occurs. Only get one output (speakers) in
the sound controls when their used to be multiple. When plugging in
headphones sound comes out of both the speakers and headphones at the
same time.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
Uname: Linux 4.11.0-13-generic x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dpepe  1788 F pulseaudio
CurrentDesktop: GNOME
Date: Sat Aug 12 12:32:10 2017
InstallationDate: Installed on 2017-07-25 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Only some of outputs are working
Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] Playback 
problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/07/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.25
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.25:bd05/07/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

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

Title:
  Sound plays out of the speakers and headphones at the same time. No
  volume control for headphones anymore.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Plugging in headphones used to generate a pop up to select which audio
  device to play. This no longer occurs. Only get one output (speakers)
  in the sound controls when their used to be multiple. When plugging in
  headphones sound comes out of both the speakers and headphones at the
  same time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dpepe  1788 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Aug 12 12:32:10 2017
  InstallationDate: Installed on 2017-07-25 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.25
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.25:bd05/07/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01: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/alsa-driver/+bug/1710389/+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 1457054] Re: journal is broken in unprivileged LXC and nspawn containers

[Mathew Hodson]

** Changed in: systemd (Ubuntu Vivid)
   Importance: Undecided => Medium

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

Title:
  journal is broken in unprivileged LXC and nspawn containers

Status in lxc package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Vivid:
  Fix Released
Status in systemd source package in Wily:
  Fix Released

Bug description:
  Test case
  -
  - Under Ubuntu 15.04 (or 15.10), set up an unprivileged container as in 
https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/
  - Boot it. You'll get a lot of errors like

    [FAILED] Failed to start Journal Service.
    systemd-journald-audit.socket failed to listen on sockets: Operation not 
permitted
    [FAILED] Failed to listen on Journal Audit Socket.

  - The same happens with systemd-nspawn -b.

  As a result, the journal isn't working at all, and you have a bunch of
  failed journal related units.

  With a fixed systemd package, systemd in the container should realize
  that it cannot listen to the audit socket (as the kernel doesn't allow
  that -- the audit subsystem isn't fit for namespaces right now), and
  "sudo journalctl" should show the journal and systemd-journald.service
  should be running. These systemd fixes are sufficient for nspawn, but
  not completely for unprivileged LXC containers -- there the journal
  will start working, but systemd-journald-audit.socket will still keep
  failing (this is less important)

  REGRESSION POTENTIAL: Very low. This only affects the fallback error
  code path if binding to the audit socket failed. In that case the
  journal is currently not working at all. This usually doesn't happen
  on real iron/VMs (they also always CAP_AUDIT_READ), so there is no
  practical change there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1457054/+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 1576341] Re: systemd in degraded state on startup in LXD containers

[Mathew Hodson]

** No longer affects: snapd (Ubuntu)

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

Title:
  systemd in degraded state on startup in LXD containers

Status in lvm2 package in Ubuntu:
  Fix Released
Status in nfs-utils package in Ubuntu:
  New
Status in open-iscsi package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass --all to see loaded but inactive units, too.
  To show all installed unit files use 'systemctl list-unit-files'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 17:28:04 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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 1710384] [NEW] Error Login Google-chrome Ubuntu On Wayland

[FranciscoLima]

Public bug reported:

google-chrome
Gkr-Message: secret service operation failed: Did not receive a reply. Possible 
causes include: the remote application did not send a reply, the message bus 
security policy blocked the reply, the reply timeout expired, or the network 
connection was broken.
Gkr-Message: secret service operation failed: Did not receive a reply. Possible 
causes include: the remote application did not send a reply, the message bus 
security policy blocked the reply, the reply timeout expired, or the network 
connection was broken.
[4927:4955:0812/115828.953055:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-109403329677698997745
[4927:5006:0812/115828.953063:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token

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

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

Title:
  Error Login Google-chrome Ubuntu On Wayland

Status in perl package in Ubuntu:
  New

Bug description:
  google-chrome
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4927:4955:0812/115828.953055:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-109403329677698997745
  [4927:5006:0812/115828.953063:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1710384/+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 1710382] [NEW] Wireless network frequently drops in 17.10

[Alan Pope  濾]

Public bug reported:

On a fairly clean 17.10 install, on a Thinkpad T450, the wireless
connection keeps dropping. Other devices nearby do not suffer the same
way.

I can turn the wifi off and on again to get reconnected. It happens
multiple times over a short period of an hour or so. So quite
irritating.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.2-1ubuntu2
ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
Uname: Linux 4.11.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Aug 12 15:52:20 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-08-02 (9 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
IpRoute:
 default via 192.168.1.1 dev wlp3s0 proto static metric 600 
 10.124.121.0/24 dev lxdbr0 proto kernel scope link src 10.124.121.1 
 169.254.0.0/16 dev wlp3s0 scope link metric 1000 
 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.95 metric 600
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile
 
 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE   TYPE  STATEDBUS-PATH   
CONNECTION  CON-UUID  CON-PATH  
  
 lxdbr0   bridgeconnected/org/freedesktop/NetworkManager/Devices/27  
lxdbr0  9e57f30a-21b5-4f87-aa76-06a328c24462  
/org/freedesktop/NetworkManager/ActiveConnection/10 
 wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/3   
popey   b83cf629-38b9-47dc-8916-3aaa2868e90a  
/org/freedesktop/NetworkManager/ActiveConnection/6  
 enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2   -- 
 ----   
   
 lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1   -- 
 ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  Wireless network frequently drops in 17.10

Status in network-manager package in Ubuntu:
  New

Bug description:
  On a fairly clean 17.10 install, on a Thinkpad T450, the wireless
  connection keeps dropping. Other devices nearby do not suffer the same
  way.

  I can turn the wifi off and on again to get reconnected. It happens
  multiple times over a short period of an hour or so. So quite
  irritating.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 12 15:52:20 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-08-02 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto static metric 600 
   10.124.121.0/24 dev lxdbr0 proto kernel scope link src 10.124.121.1 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.95 metric 600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH   
CONNECTION  CON-UUID  CON-PATH  
  
   lxdbr0   bridgeconnected/org/freedesktop/NetworkManager/Devices/27  
lxdbr0  9e57f30a-21b5-4f87-aa76-06a328c24462  
/org/freedesktop/NetworkManager/ActiveConnection/10 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/3   
popey   b83cf629-38b9-47dc-8916-3aaa2868e90a  
/org/freedesktop/NetworkManager/ActiveConnection/6  
 

[Touch-packages] [Bug 1710359] Re: package libperl5.26 5.26.0-5 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libperl5.26/changelog.Debian.gz' partilhado, que é diferente de outras

[Hans Joachim Desserud]

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

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

** This bug has been marked a duplicate of bug 1574351
   package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite 
shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different 
from other instances of package libperl5.22:i386

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

Title:
  package libperl5.26 5.26.0-5 failed to install/upgrade: a tentar
  sobreescrever '/usr/share/doc/libperl5.26/changelog.Debian.gz'
  partilhado, que é diferente de outras instâncias do pacote
  libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  Libperl5 install error

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libperl5.26 5.26.0-5
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  Date: Sat Aug 12 09:23:20 2017
  ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libperl5.26/changelog.Debian.gz' partilhado, que é diferente de 
outras instâncias do pacote libperl5.26:i386
  InstallationDate: Installed on 2017-07-30 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~beta1
  SourcePackage: perl
  Title: package libperl5.26 5.26.0-5 failed to install/upgrade: a tentar 
sobreescrever '/usr/share/doc/libperl5.26/changelog.Debian.gz' partilhado, que 
é diferente de outras instâncias do pacote libperl5.26:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1710359/+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 1710381] [NEW] all

[Severin Scheuerer]

Public bug reported:

nothing

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Aug 12 16:43:30 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:81d2]
InstallationDate: Installed on 2017-08-07 (5 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 04f2:b56d Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ENVY Notebook
ProcEnviron:
 LANGUAGE=de_CH:de
 PATH=(custom, no user)
 LANG=de_CH.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81D2
dmi.board.vendor: HP
dmi.board.version: KBC Version 87.13
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd07/08/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81D2:rvrKBCVersion87.13:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sat Aug 12 16:42:59 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.2
xserver.video_driver: modeset

** 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/1710381

Title:
  all

Status in xorg package in Ubuntu:
  New

Bug description:
  nothing

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Aug 12 16:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:81d2]
  InstallationDate: Installed on 2017-08-07 (5 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b56d Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Notebook
  ProcEnviron:
   LANGUAGE=de_CH:de
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81D2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 87.13
  dmi.chassis.type: 10
  

[Touch-packages] [Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full

[Jarno Suni]

This patch is better, because it takes into account the size of possible
existing initramfs file  when calculating the needed available free
space.

** Patch added: "version 2 of patch concerning generate_initramfs function in 
update_initramfs"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+attachment/4931280/+files/update-initramfs.patch

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

Title:
  Removing a linux-image-extra package fails, if /boot is about full

Status in initramfs-tools:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  System calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space
  in /boot temporarily. But there is no space left, if /boot is full.

  Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u".

  The fix could be to create the new initrg.img file in different partition 
before replacing the old one by it in update-initramfs. So the update-initramfs 
script should be fixed. But there may not be such a partition..
  Anyway the likely case when space runs out is when there is a separate /boot 
partition.

  Alternatively the init scripts should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 
  That may be worse way, as then initrd.img file is missing for longer period 
of time and system integrity may suffer in case of e.g. power cut.

  Related question: http://askubuntu.com/q/898499/21005
  The output of 'dpkg --purge' presented there shows that corresponding 
linux-image package may get successfully removed while the linux-image-extra is 
left broken. If the linux-image-extra package will be removed later, the 
post-installation script will create an initrd.img file for a non-installed 
kernel! Same would happen, if removing would be done by apt-get purge.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1678187/+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 1697900] Re: Small graphical glitch in Nautilus "Delete" button border

[AsciiWolf]

Still present in the latest Ubuntu 17.10 build.

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

Title:
  Small graphical glitch in Nautilus "Delete" button border

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Glitch in the "Delete" button (see the attached screenshots).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1697900/+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 1710377] [NEW] "Additional Drivers" desktop shortcut missing in Ubuntu 17.10

[AsciiWolf]

Public bug reported:

There used to be an "Additional Drivers" shortcut in the applications
list in Unity. This shortcut is missing in the GNOME Shell Overview in
Ubuntu 17.10.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful

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

Title:
  "Additional Drivers" desktop shortcut missing in Ubuntu 17.10

Status in software-properties package in Ubuntu:
  New

Bug description:
  There used to be an "Additional Drivers" shortcut in the applications
  list in Unity. This shortcut is missing in the GNOME Shell Overview in
  Ubuntu 17.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1710377/+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 1710359] [NEW] package libperl5.26 5.26.0-5 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libperl5.26/changelog.Debian.gz' partilhado, que é diferente de outr

[FranciscoLima]

Public bug reported:

Libperl5 install error

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libperl5.26 5.26.0-5
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
Date: Sat Aug 12 09:23:20 2017
ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libperl5.26/changelog.Debian.gz' partilhado, que é diferente de 
outras instâncias do pacote libperl5.26:i386
InstallationDate: Installed on 2017-07-30 (12 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5~beta1
SourcePackage: perl
Title: package libperl5.26 5.26.0-5 failed to install/upgrade: a tentar 
sobreescrever '/usr/share/doc/libperl5.26/changelog.Debian.gz' partilhado, que 
é diferente de outras instâncias do pacote libperl5.26:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful

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

Title:
  package libperl5.26 5.26.0-5 failed to install/upgrade: a tentar
  sobreescrever '/usr/share/doc/libperl5.26/changelog.Debian.gz'
  partilhado, que é diferente de outras instâncias do pacote
  libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  Libperl5 install error

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libperl5.26 5.26.0-5
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  Date: Sat Aug 12 09:23:20 2017
  ErrorMessage: a tentar sobreescrever 
'/usr/share/doc/libperl5.26/changelog.Debian.gz' partilhado, que é diferente de 
outras instâncias do pacote libperl5.26:i386
  InstallationDate: Installed on 2017-07-30 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~beta1
  SourcePackage: perl
  Title: package libperl5.26 5.26.0-5 failed to install/upgrade: a tentar 
sobreescrever '/usr/share/doc/libperl5.26/changelog.Debian.gz' partilhado, que 
é diferente de outras instâncias do pacote libperl5.26:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1710359/+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 1689825] Re: gnome-keyring not unlocked on boot

[Tom Reynolds]

This is not fixed. What we have is a reliable workaround to a bug which
apparently affects all Ubuntu 16.04 LTS users with the dbus-user-session
package installed.

Flatpak packages provided by the PPA at
https://launchpad.net/~alexlarsson/+archive/ubuntu/flatpak (and possibly
others) indirectly depend on this package and cause it to be installed
(but this issue which seems to be a bug in Ubuntu 16.04 is not this
PPA's fault).

$ apt-rdepends --reverse dbus-user-session
Reading package lists... Done
Building dependency tree   
Reading state information... Done
dbus-user-session
  Reverse Depends: xdg-desktop-portal (0.8-0alexlarsson2~xenial)
  Reverse Depends: xdg-desktop-portal-gtk (0.7-0alexlarsson2~xenial)
xdg-desktop-portal
  Reverse Depends: xdg-desktop-portal-gtk (0.7-0alexlarsson2~xenial)
xdg-desktop-portal-gtk


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

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

Title:
  gnome-keyring not unlocked on boot

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  New
Status in flatpak package in Ubuntu:
  Confirmed
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1689825/+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 1522675] Re: Warning messages about unsandboxed downloads

[Martin Dünkelmann]

W: Download is performed unsandboxed as root as file
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. -
pkgAcquire::Run (13: Keine Berechtigung)

Ubuntu Mate x64 17.04
Synaptic 0.84.2

I only want to install the updates and autoremove unessecary
packages.

-- 
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:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in aptitude package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  Fix Released
Status in apt package in Debian:
  Fix Released
Status in aptitude package in Debian:
  Fix Released
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 1705040] Re: can't get source package

[Hans Joachim Desserud]

Could you please run `sudo apt update` and see if that resolves the
issue?

Update needs to be run after changing repositories, otherwise apt won't
know about the contents of the new ones.

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

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

Title:
  can't get source package

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  $ apt-get --version
  apt 1.5~beta1 (amd64)
  Supported modules:
  *Ver: Standard .deb
  *Pkg:  Debian dpkg interface (Priority 30)
   Pkg:  Debian APT solver interface (Priority -1000)
   Pkg:  Debian APT planner interface (Priority -1000)
   S.L: 'deb' Debian binary tree
   S.L: 'deb-src' Debian source tree
   Idx: Debian Source Index
   Idx: Debian Package Index
   Idx: Debian Translation Index
   Idx: Debian dpkg status file
   Idx: Debian deb file
   Idx: Debian dsc file
   Idx: Debian control file
   Idx: EDSP scenario file
   Idx: EIPP scenario file

  Ubuntu 17.10

  
  $ apt-get source mutterReading package lists... Done
  E: You must put some 'source' URIs in your sources.list

  But all deb-src are enabled.

  $ cat /etc/apt/sources.list
  #deb cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Alpha amd64 (20170714)]/ artful 
main restricted

  # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
  # newer versions of the distribution.
  deb http://ru.archive.ubuntu.com/ubuntu/ artful main restricted
  deb-src http://ru.archive.ubuntu.com/ubuntu/ artful main restricted

  ## Major bug fix updates produced after the final release of the
  ## distribution.
  deb http://ru.archive.ubuntu.com/ubuntu/ artful-updates main restricted
  deb-src http://ru.archive.ubuntu.com/ubuntu/ artful-updates main restricted

  ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
  ## team. Also, please note that software in universe WILL NOT receive any
  ## review or updates from the Ubuntu security team.
  deb http://ru.archive.ubuntu.com/ubuntu/ artful universe
  deb-src http://ru.archive.ubuntu.com/ubuntu/ artful universe
  deb http://ru.archive.ubuntu.com/ubuntu/ artful-updates universe
  deb-src http://ru.archive.ubuntu.com/ubuntu/ artful-updates universe

  ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu 
  ## team, and may not be under a free licence. Please satisfy yourself as to 
  ## your rights to use the software. Also, please note that software in 
  ## multiverse WILL NOT receive any review or updates from the Ubuntu
  ## security team.
  deb http://ru.archive.ubuntu.com/ubuntu/ artful multiverse
  deb-src http://ru.archive.ubuntu.com/ubuntu/ artful multiverse
  deb http://ru.archive.ubuntu.com/ubuntu/ artful-updates multiverse
  deb-src http://ru.archive.ubuntu.com/ubuntu/ artful-updates multiverse

  ## N.B. software from this repository may not have been tested as
  ## extensively as that contained in the main release, although it includes
  ## newer versions of some applications which may provide useful features.
  ## Also, please note that software in backports WILL NOT receive any review
  ## or updates from the Ubuntu security team.
  deb http://ru.archive.ubuntu.com/ubuntu/ artful-backports main restricted 
universe multiverse
  deb-src http://ru.archive.ubuntu.com/ubuntu/ artful-backports main restricted 
universe multiverse

  ## Uncomment the following two lines to add software from Canonical's
  ## 'partner' repository.
  ## This software is not part of Ubuntu, but is offered by Canonical and the
  ## respective vendors as a service to Ubuntu users.
  # deb http://archive.canonical.com/ubuntu artful partner
  # deb-src http://archive.canonical.com/ubuntu artful partner

  deb http://security.ubuntu.com/ubuntu artful-security main restricted
  deb-src http://security.ubuntu.com/ubuntu artful-security main restricted
  deb http://security.ubuntu.com/ubuntu artful-security universe
  deb-src http://security.ubuntu.com/ubuntu artful-security universe
  deb http://security.ubuntu.com/ubuntu artful-security multiverse
  deb-src http://security.ubuntu.com/ubuntu artful-security multiverse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1705040/+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 1710353] [NEW] unable to maximize windows (doubled title bars?) in Ubuntu 17.10 alpha

[TomaszChmielewski]

Public bug reported:

In Ubuntu 17.10 alpha (with Gnome being the default environment) - when
compared to Unity on Ubuntu 17.04 and earlier - it is not possible to
fully maximize a window.

There are two title bars in Ubuntu 17.10 alpha and Gnome after a window
is maximized, while we had only one title bar in Unity and earlier
Ubuntu versions.

Two title bars instead of one waste screen real estate and don't contain
any extra information.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubuntu-desktop 1.379
Uname: Linux 4.12.2-041202-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Sat Aug 12 19:40:16 2017
InstallationDate: Installed on 2017-04-14 (120 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


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

** Attachment added: "two title bars instead of one?"
   
https://bugs.launchpad.net/bugs/1710353/+attachment/4931151/+files/double-title-bar.png

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1710353/+attachment/4931155/+files/ProcEnviron.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1710353/+attachment/4931154/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1710353/+attachment/4931153/+files/JournalErrors.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1710353/+attachment/4931152/+files/Dependencies.txt

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

Title:
  unable to maximize windows (doubled title bars?) in Ubuntu 17.10 alpha

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  In Ubuntu 17.10 alpha (with Gnome being the default environment) -
  when compared to Unity on Ubuntu 17.04 and earlier - it is not
  possible to fully maximize a window.

  There are two title bars in Ubuntu 17.10 alpha and Gnome after a
  window is maximized, while we had only one title bar in Unity and
  earlier Ubuntu versions.

  Two title bars instead of one waste screen real estate and don't
  contain any extra information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-desktop 1.379
  Uname: Linux 4.12.2-041202-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Aug 12 19:40:16 2017
  InstallationDate: Installed on 2017-04-14 (120 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1710353/+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 1281617] Re: Missing padding above menu's first item and below last item

[Bug Watch Updater]

** Changed in: gtk
   Status: Fix Released => Confirmed

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

Title:
  Missing padding above menu's first item and below last item

Status in GTK+:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  Problem occurs with: light-themes 13.04+13.10.20131014-0ubuntu1, Ubuntu 13.10
  Does not occur with: light-themes 0.1.8.11, Ubuntu 11.04

  1. Position the pointer on an empty area of the desktop, or of a Nautilus 
window's main pane.
  2. Without moving the pointer at all, either hold down the right mouse 
button, or click once.
  3. Release the button, or click again.

  What happens:
  2. A shortcut menu opens with "New Folder" highlighted.
  3. A new folder is created.

  What should happen:
  2. A shortcut menu opens with nothing highlighted.
  3. Nothing.

  This is a regression of bug 626462. I noticed the problem during a
  usability test in 2009 or 2010, when someone tapped absent-mindedly on
  the right mouse button and created a folder without realizing it.

  The fix is to add as much padding above every menu's first item, and
  below its last item, as there is above or below a menu separator (as
  illustrated in bug 659866).

  Fixing this would also help avoid accidentally closing a menu in the
  menu bar, when its first item is a submenu or other control that is
  dangerously close to other items in the menu bar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1281617/+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 1710345] Re: package kmod 22-1ubuntu4 failed to install/upgrade: package kmod is not ready for configuration cannot configure (current status 'half-installed')

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package kmod 22-1ubuntu4 failed to install/upgrade: package kmod is
  not ready for configuration  cannot configure (current status 'half-
  installed')

Status in kmod package in Ubuntu:
  New

Bug description:
  while uninstalling node js

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kmod 22-1ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Aug 12 14:03:40 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   libkmod2 22-1ubuntu4
   lsb-base 9.20160110ubuntu0.2
  DuplicateSignature:
   package:kmod:22-1ubuntu4
   Processing triggers for libc-bin (2.23-0ubuntu9) ...
   dpkg: error processing package kmod (--configure):
package kmod is not ready for configuration
  ErrorMessage: package kmod is not ready for configuration  cannot configure 
(current status 'half-installed')
  InstallationDate: Installed on 2017-08-02 (9 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: kmod
  Title: package kmod 22-1ubuntu4 failed to install/upgrade: package kmod is 
not ready for configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1710345/+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 1710345] [NEW] package kmod 22-1ubuntu4 failed to install/upgrade: package kmod is not ready for configuration cannot configure (current status 'half-installed')

[Sharan A]

Public bug reported:

while uninstalling node js

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: kmod 22-1ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Sat Aug 12 14:03:40 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
 libkmod2 22-1ubuntu4
 lsb-base 9.20160110ubuntu0.2
DuplicateSignature:
 package:kmod:22-1ubuntu4
 Processing triggers for libc-bin (2.23-0ubuntu9) ...
 dpkg: error processing package kmod (--configure):
  package kmod is not ready for configuration
ErrorMessage: package kmod is not ready for configuration  cannot configure 
(current status 'half-installed')
InstallationDate: Installed on 2017-08-02 (9 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: kmod
Title: package kmod 22-1ubuntu4 failed to install/upgrade: package kmod is not 
ready for configuration  cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: kmod (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 kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1710345

Title:
  package kmod 22-1ubuntu4 failed to install/upgrade: package kmod is
  not ready for configuration  cannot configure (current status 'half-
  installed')

Status in kmod package in Ubuntu:
  New

Bug description:
  while uninstalling node js

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kmod 22-1ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Aug 12 14:03:40 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   libkmod2 22-1ubuntu4
   lsb-base 9.20160110ubuntu0.2
  DuplicateSignature:
   package:kmod:22-1ubuntu4
   Processing triggers for libc-bin (2.23-0ubuntu9) ...
   dpkg: error processing package kmod (--configure):
package kmod is not ready for configuration
  ErrorMessage: package kmod is not ready for configuration  cannot configure 
(current status 'half-installed')
  InstallationDate: Installed on 2017-08-02 (9 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: kmod
  Title: package kmod 22-1ubuntu4 failed to install/upgrade: package kmod is 
not ready for configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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