[Touch-packages] [Bug 1743797] Re: Xorg not recognizing AMD graphics card

[Timo Aaltonen]

putting 'radeon.modeset=0' to kernel options is what disables all hw
acceleration

if it doesn't boot properly without that, you need to test a newer
kernel, so try installing 'linux-generic-hwe-16.04'

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

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

Title:
  Xorg not recognizing AMD graphics card

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  A few months after upgrading to Ubuntu 16.04, my graphics card stopped
  working. I got a black screen after booting. I was able to work around
  that problem, and then around the problem of losing my external
  display when I closed my laptop lid, so I can now boot normally and
  have only one problem - I still only have software rendering, which
  isn't up to the job.

  I checked my graphics card and it was on the list of fully supported
  versions. I found work-arounds online for my other problems, but no
  way to fix this one, which results in choppy video with audio out of
  sync.

  I trust the apport report which should be attached will give you the
  specs you need.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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: Wed Jan 17 10:15:32 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV515/M52 [Mobility Radeon X1300] 
[1002:714a] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RV515/M52 [Mobility Radeon X1300] 
[103c:30ac]
  InstallationDate: Installed on 2014-04-10 (1378 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: Hewlett-Packard HP Compaq nc6400 (RB523UA#ABA)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=123f436f-0331-4097-8a8e-54cc927298c4 ro radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YCD Ver. F.08
  dmi.board.name: 30AC
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 56.34
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YCDVer.F.08:bd12/18/2006:svnHewlett-Packard:pnHPCompaqnc6400(RB523UA#ABA):pvrF.08:rvnHewlett-Packard:rn30AC:rvrKBCVersion56.34:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nc6400 (RB523UA#ABA)
  dmi.product.version: F.08
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jan 17 08:23:08 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1743797/+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 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial

[TJ]

Attached is a patch (generated on 16.04) that activates volume groups
when root=UUID=... is on the kernel command-line.

** Patch added: "activate VGs  when root=UUID="
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1573982/+attachment/5038702/+files/lvm2_local_top.patch

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

Title:
  LVM boot problem - volumes not activated after upgrade to Xenial

Status in curtin:
  Incomplete
Status in MAAS:
  Incomplete
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Soon after upgrade to Xenial (from 15.10) the boot process got broken.
  I'm using LVM for /root swap and other partitions.

  ===
  The current behaviour is:

  When I boot short after the Grub login screen I'm getting log messages
  like:

  ---
  Scanning for Btrfs filesystems
  resume: Could not state the resume device file: '/dev/mapper/VolGroup'
  Please type in the full path...
  ---

  Then I press ENTER, for a few minutes some errors about floppy device
  access are raised (for some reason it tries to scan fd0 when floppy
  drive is empty). And then:

  ---
  Gave up waiting for root device. Common problems: ...
  ...
  ALERT! UUID=xxx-xxx does not exist.
  Dropping to a shell.
  ---

  From the BusyBox shell I managed to recover the boot by issuing "lvm
  vgchange -ay", then exit and then boot continues fine (all LVM file
  systems are successfully mounted).

  ===
  One workaround so far is creating 
/etc/initramfs-tools/scripts/local-top/lvm2-manual script doing "lvm vgchange 
-ay". But I'm looking for cleaner solution.

  Boot used to work fine with 15.10. Actually the first boot after
  upgrading to Xenial actually worked OK too, I'm not sure what might
  changed meanwhile (I've been fixing some packages installation since
  mysql server upgrade has failed).

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1573982/+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 1737662] Re: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system

[Steve Langasek]

The log in the last comment shows an error from the kernel driver for
the disk, which is either a hardware or kernel bug.  It is unrelated to
the issue reported in this launchpad bug.

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

Title:
  Unable to install ubuntu1804 build with Debootstrap warning on
  witherspoon system

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in busybox package in Ubuntu:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released

Bug description:
  Problem Description:
  ===
  Ubuntu1804 installer shows Debootstrap warning  messages and not able to 
proceed with installation

  Steps to re-create:
  ==
  > on Witherspoon test system, tried to install ubuntu1804 using netboot 
install.

  > Selected mirror path:http://10.xx.11.31:3128

  
 [!] Choose a mirror of the Ubuntu archive 
? ?
? Please select an Ubuntu archive mirror. You should use a mirror in  ?
? your country or region if you do not know which mirror has the best ?
? Internet connection to you. ?
? ?
? Usually, .archive.ubuntu.com is a good choice.   ?
? ?
? Ubuntu archive mirror:  ?
? ?
? us.ports.ubuntu.com ?
? ?
??
? ?
???

  
  > Able to select the disks

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?/dev/nvme0n1 - 409.6 GB Unknown  ?
?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB   ?
?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB   ?
? ?
??
? ?
???

  
  > Started installing base system

??? Installing the base system 
? ?
?6%   ?
? ?
? Retrieving libc6... ?
? ?
???

  > Then seen Debootstrap warning messages as below

  
??? [!!] Install the base system ???
?  ? ??
?   ?   Debootstrap warning?  ?
?   ? Warning: Failure trying to run: chroot /target dpkg-deb -f   ?  ?
?   ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ?  ?
? Ex?  ?  ?
?   ?   ?  ?
?  ? ??



??? [!!] Install the base system ??
?   ?  ?  ?
?   ?   Debootstrap warning?  ?
?   ? Warning: See the log for details ?  ?
? Extracting zlib1g.?

[Touch-packages] [Bug 1737662] syslog

[bugproxy]

--- Comment (attachment only) From sthou...@in.ibm.com 2018-01-18 02:00 
EDT---


** Attachment added: "syslog"
   
https://bugs.launchpad.net/bugs/1737662/+attachment/5038672/+files/boslcp4g5-25-2

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

Title:
  Unable to install ubuntu1804 build with Debootstrap warning on
  witherspoon system

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in busybox package in Ubuntu:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released

Bug description:
  Problem Description:
  ===
  Ubuntu1804 installer shows Debootstrap warning  messages and not able to 
proceed with installation

  Steps to re-create:
  ==
  > on Witherspoon test system, tried to install ubuntu1804 using netboot 
install.

  > Selected mirror path:http://10.xx.11.31:3128

  
 [!] Choose a mirror of the Ubuntu archive 
? ?
? Please select an Ubuntu archive mirror. You should use a mirror in  ?
? your country or region if you do not know which mirror has the best ?
? Internet connection to you. ?
? ?
? Usually, .archive.ubuntu.com is a good choice.   ?
? ?
? Ubuntu archive mirror:  ?
? ?
? us.ports.ubuntu.com ?
? ?
??
? ?
???

  
  > Able to select the disks

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?/dev/nvme0n1 - 409.6 GB Unknown  ?
?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB   ?
?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB   ?
? ?
??
? ?
???

  
  > Started installing base system

??? Installing the base system 
? ?
?6%   ?
? ?
? Retrieving libc6... ?
? ?
???

  > Then seen Debootstrap warning messages as below

  
??? [!!] Install the base system ???
?  ? ??
?   ?   Debootstrap warning?  ?
?   ? Warning: Failure trying to run: chroot /target dpkg-deb -f   ?  ?
?   ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ?  ?
? Ex?  ?  ?
?   ?   ?  ?
?  ? ??



??? [!!] Install the base system ??
?   ?  ?  ?
?   ?   Debootstrap warning?  ?
?   ? Warning: See the log for details ?  ?
? E

[Touch-packages] [Bug 1737662] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From sthou...@in.ibm.com 2018-01-18 01:58 EDT---
*** Bug 163644 has been marked as a duplicate of this bug. ***

--- Comment From sthou...@in.ibm.com 2018-01-18 01:59 EDT---
Jan 17 15:22:47 main-menu[384]: INFO: Menu item 'bootstrap-base' selected
Jan 17 15:22:48 debootstrap: gpgv: Signature made Wed Jan 17 21:09:59 2018 UTC
Jan 17 15:22:48 debootstrap: gpgv:using RSA key
Jan 17 15:22:48 debootstrap: gpgv: Good signature from "Ubuntu Archive 
Automatic Signing Key (2012) "
Jan 17 15:23:01 kernel: [ 1733.162901] sd 0:0:5:0: [sdf] tag#1 FAILED Result: 
hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 17 15:23:01 kernel: [ 1733.162924] sd 0:0:5:0: [sdf] tag#1 Sense Key : 
Illegal Request [current]
Jan 17 15:23:01 kernel: [ 1733.162929] sd 0:0:5:0: [sdf] tag#1 Add. Sense: 
Invalid field in cdb
Jan 17 15:23:01 kernel: [ 1733.162934] sd 0:0:5:0: [sdf] tag#1 CDB: Write(10) 
2a 00 06 04 4a 48 00 03 f0 00
Jan 17 15:23:01 kernel: [ 1733.162947] print_req_error: critical target error, 
dev sdf, sector 100944456
Jan 17 15:23:01 kernel: [ 1733.172558] Aborting journal on device sdf2-8.
Jan 17 15:23:01 kernel: [ 1733.173420] EXT4-fs error (device sdf2): 
ext4_journal_check_start:60: Detected aborted journal
Jan 17 15:23:01 kernel: [ 1733.173424] EXT4-fs (sdf2): Remounting filesystem 
read-only
Jan 17 15:23:01 debootstrap: tar: write error: Read-only file system
Jan 17 15:23:05 main-menu[384]: (process:13638): mv: can't rename 
'/target/etc/fstab.orig': Read-only file system
Jan 17 15:23:05 main-menu[384]: WARNING **: Configuring 'bootstrap-base' failed 
with error code 1
Jan 17 15:23:05 main-menu[384]: WARNING **: Menu item 'bootstrap-base' failed.
Jan 17 15:23:06 main-menu[384]: INFO: Modifying debconf priority limit from 
'high' to 'medium'
Jan 17 15:23:06 debconf: Setting debconf/priority to medium
Jan 17 15:23:11 main-menu[384]: INFO: Menu item 'di-utils-shell' selected

Continue to see the issue with latest iso available.
kernel 4.13.0-25-generic

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

Title:
  Unable to install ubuntu1804 build with Debootstrap warning on
  witherspoon system

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in busybox package in Ubuntu:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released

Bug description:
  Problem Description:
  ===
  Ubuntu1804 installer shows Debootstrap warning  messages and not able to 
proceed with installation

  Steps to re-create:
  ==
  > on Witherspoon test system, tried to install ubuntu1804 using netboot 
install.

  > Selected mirror path:http://10.xx.11.31:3128

  
 [!] Choose a mirror of the Ubuntu archive 
? ?
? Please select an Ubuntu archive mirror. You should use a mirror in  ?
? your country or region if you do not know which mirror has the best ?
? Internet connection to you. ?
? ?
? Usually, .archive.ubuntu.com is a good choice.   ?
? ?
? Ubuntu archive mirror:  ?
? ?
? us.ports.ubuntu.com ?
? ?
??
? ?
???

  
  > Able to select the disks

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?/dev/nvme0n1 - 409.6 GB Unknown  ?
?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB   ?
?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB   ?
? ?
??
?   

[Touch-packages] [Bug 1575779] Re: hostnamectl fails under lxd unpriv container

[tonyk]

Comment on post #12 above (as one cannot edit):

Step 4 can be omitted as I don't think the service needs to be
restarted.

I think the hostnamectl command starts this service on demand when
changing the hostname.

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

Title:
  hostnamectl fails under lxd unpriv container

Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  1.  % lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  2.  % apt-cache policy apparmor
  apparmor:
Installed: 2.10.95-0ubuntu2
Candidate: 2.10.95-0ubuntu2
Version table:
   *** 2.10.95-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  % apt-cache policy lxd
  lxd:
Installed: 2.0.0-0ubuntu4
Candidate: 2.0.0-0ubuntu4
Version table:
   *** 2.0.0-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3. lxc launch ubuntu-daily:xenial x1
  lxc exec x1 /bin/bash

  root@x1:~# hostnamectl status 
 Static hostname: x1
   Icon name: computer-container
 Chassis: container
  Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d
 Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca
  Virtualization: lxc
Operating System: Ubuntu 16.04 LTS
  Kernel: Linux 4.4.0-18-generic
Architecture: x86-64

  
  4. hostnamectl status hangs indefinitely

  On the host, there are some audit messages for each invocation of
  hostnamectl

  [411617.032274] audit: type=1400 audit(1461695563.731:100):
  apparmor="DENIED" operation="file_lock" profile="lxd-
  x1_" pid=17100 comm="(ostnamed)" family="unix"
  sock_type="dgram" protocol=0 addr=none

  It's related to socket activation.  One can workaround this by running
  systemd-hostnamed in the background first

  root@x1:~# /lib/systemd/systemd-hostnamed & 
  [1] 2462
  root@x1:~# hostnamectl status 
 Static hostname: x1
   Icon name: computer-container
 Chassis: container
  Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d
 Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca
  Virtualization: lxc
Operating System: Ubuntu 16.04 LTS
  Kernel: Linux 4.4.0-18-generic
Architecture: x86-64

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed Apr 27 11:19:27 2016
  InstallationDate: Installed on 2016-01-01 (117 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e0b8b294-f364-4ef5-aa70-1916cdd37192 ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779/+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 1575779] Re: hostnamectl fails under lxd unpriv container

[tonyk]

Thanks for that PrivateNetwork=no hint - works like a charm!

For those that need this, follow the steps below:

1. systemctl edit systemd-hostnamed

   Add the 2 lines below then exit the editor (don't forget to save when
prompted):

   [Service]
   PrivateNetwork=no

2. This will create an override.conf file with the above 2 lines in the
directory:

   /etc/systemd/system/systemd-hostnamed.service.d/

3. The update systemd:

   systemctl daemon-reload

4. Then restart the service:

   systemctl restart systemd-hostnamed


You should now be able to run hostnamectl without it hanging.

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

Title:
  hostnamectl fails under lxd unpriv container

Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  1.  % lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  2.  % apt-cache policy apparmor
  apparmor:
Installed: 2.10.95-0ubuntu2
Candidate: 2.10.95-0ubuntu2
Version table:
   *** 2.10.95-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  % apt-cache policy lxd
  lxd:
Installed: 2.0.0-0ubuntu4
Candidate: 2.0.0-0ubuntu4
Version table:
   *** 2.0.0-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3. lxc launch ubuntu-daily:xenial x1
  lxc exec x1 /bin/bash

  root@x1:~# hostnamectl status 
 Static hostname: x1
   Icon name: computer-container
 Chassis: container
  Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d
 Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca
  Virtualization: lxc
Operating System: Ubuntu 16.04 LTS
  Kernel: Linux 4.4.0-18-generic
Architecture: x86-64

  
  4. hostnamectl status hangs indefinitely

  On the host, there are some audit messages for each invocation of
  hostnamectl

  [411617.032274] audit: type=1400 audit(1461695563.731:100):
  apparmor="DENIED" operation="file_lock" profile="lxd-
  x1_" pid=17100 comm="(ostnamed)" family="unix"
  sock_type="dgram" protocol=0 addr=none

  It's related to socket activation.  One can workaround this by running
  systemd-hostnamed in the background first

  root@x1:~# /lib/systemd/systemd-hostnamed & 
  [1] 2462
  root@x1:~# hostnamectl status 
 Static hostname: x1
   Icon name: computer-container
 Chassis: container
  Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d
 Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca
  Virtualization: lxc
Operating System: Ubuntu 16.04 LTS
  Kernel: Linux 4.4.0-18-generic
Architecture: x86-64

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed Apr 27 11:19:27 2016
  InstallationDate: Installed on 2016-01-01 (117 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e0b8b294-f364-4ef5-aa70-1916cdd37192 ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779/+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 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

[Steve Langasek]

Ubuntu 17.04 has reached end of life.  No further bugfixes will be
applied to this version.

** Changed in: apt (Ubuntu Zesty)
   Status: Fix Committed => Won't Fix

** Changed in: unattended-upgrades (Ubuntu Zesty)
   Status: New => Won't Fix

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

Title:
  unattended-upgrades does not block shutdown of system, as it is
  designed to

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  Triaged
Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Xenial:
  New
Status in apt source package in Zesty:
  Won't Fix
Status in unattended-upgrades source package in Zesty:
  Won't Fix

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
    Installed: 0.90
    Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

  
  * APT SRU *
  [Impact]
  Stopping apt-daily-upgrade.service terminates dpkg and friends by sending the 
signals to all processes in the cgroup, and will send KILL quickly after.

  [Test case]
  Start apt-daily-upgrade.service and stop it while unattended-upgrades is 
running.

  The upgrade should run to completion or a safe exit point as long as
  it takes less than about 900s (which is the timeout for sending kill).

  [Regression potential]
  Leftover processes might remain in the apt-daily-upgrade cgroup if the 
postinst scripts or some apt hooks do something funny.

  Shutdown might take longer due to the 900 second timeout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+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 1743939] Re: Canon MF8380 Wireless Network Not Printing

[Scott Stehno]

Please edit or delete any data that is not important.  I just posted the
whole log file from several different commands.

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

Title:
  Canon MF8380 Wireless Network Not Printing

Status in cups package in Ubuntu:
  New

Bug description:
  A Canon MF8380CDW printer will not print any thing after upgrading to
  17.10.  I ran all  the steps from this
  https://wiki.ubuntu.com/DebuggingPrintingProblems web site.

  I have attached a lot of log files.  Not sure which one is needed. The
  printer did work back under 15.10 or 16.04 but took a lot to get it
  fixed to work then.  I have tried to print from 18.04 and it has the
  same problem with this printer.





  
  myuseraccount@myuseraccount-System-Product-Name:~$ /usr/lib/cups/backend/snmp
  network socket://192.168.1.100 "Canon MF8300C Series" "Canon MF8300C Series" 
"MFG:Canon;MDL:MF8300C Series;CLS:PRINTER;DES:Canon MF8300
  C Series;CID:;CMD:LIPSLX,CPCA;" ""
  myuseraccount@myuseraccount-System-Product-Name:~$ sudo 
/usr/lib/cups/backend/dnssd
  [sudo] password for myuseraccount:
  DEBUG: sent=0, count=0
  DEBUG: Querying "Canon\032MF8300C\032Series._printer._tcp.local"...
  DEBUG: Querying "Canon\032MF8300C\032Series._pdl-datastream._tcp.local"...
  DEBUG: sent=0, count=2
  DEBUG2: query_callback(browser=0x556cd4f96420, interfaceIndex=2, protocol=0, 
event=0, fullName="Canon\032MF8300C\032Series._printer._tcp.local", rrclass=1, 
rrtype=16, rdata=0x
  556cd4f97854, rdlen=338, flags=5, context=0x556cd4f95900)
  DEBUG2: query_callback: "txtvers=1".
  DEBUG2: query_callback: "note=".
  DEBUG2: query_callback: "qtotal=1".
  DEBUG2: query_callback: "priority=20".
  DEBUG2: query_callback: "ty=Canon MF8300C Series".
  DEBUG2: query_callback: "product=(CNMF8300C Series)".
  DEBUG2: query_callback: "pdl=application/octet-stream".
  DEBUG2: query_callback: 
"adminurl=http://Canon0f2ec4.local/m_network_tcpip.html";.
  DEBUG2: query_callback: "usb_MFG=Canon".
  DEBUG2: query_callback: "usb_MDL=MF8300C Series".
  DEBUG2: query_callback: "Transparent=F".
  DEBUG2: query_callback: "Binary=F".
  DEBUG2: query_callback: "TBCP=F".
  DEBUG2: query_callback: "Color=T".
  DEBUG2: query_callback: "Copies=T".
  DEBUG2: query_callback: "Duplex=T".
  DEBUG2: query_callback: "PaperCustom=T".
  DEBUG2: query_callback: "Bind=F".
  DEBUG2: query_callback: "Collate=T".
  DEBUG2: query_callback: "Sort=T".
  DEBUG2: query_callback: "Staple=F".
  DEBUG2: query_callback: "Punch=0".
  DEBUG2: query_callback: "PaperMax=legal-A4".
  DEBUG2: query_callback(browser=0x556cd4f96420, interfaceIndex=-1, 
protocol=-1, event=2, 
fullName="Canon\032MF8300C\032Series._printer._tcp.local", rrclass=1, 
rrtype=16, rdata=
  (nil), rdlen=0, flags=0, context=0x556cd4f95900)
  DEBUG2: query_callback(browser=0x556cd4f95aa0, interfaceIndex=2, protocol=0, 
event=0, fullName="Canon\032MF8300C\032Series._pdl-datastream._tcp.local", 
rrclass=1, rrtype=16, r
  data=0x556cd4f97a0c, rdlen=338, flags=5, context=0x556cd4f95780)
  DEBUG2: query_callback: "txtvers=1".
  DEBUG2: query_callback: "note=".
  DEBUG2: query_callback: "qtotal=1".
  DEBUG2: query_callback: "priority=10".
  DEBUG2: query_callback: "ty=Canon MF8300C Series".
  DEBUG2: query_callback: "product=(CNMF8300C Series)".
  DEBUG2: query_callback: "pdl=application/octet-stream".
  DEBUG2: query_callback: 
"adminurl=http://Canon0f2ec4.local/m_network_tcpip.html";.
  DEBUG2: query_callback: "usb_MFG=Canon".
  DEBUG2: query_callback: "usb_MDL=MF8300C Series".
  DEBUG2: query_callback: "Transparent=F".
  DEBUG2: query_callback: "Binary=F".
  DEBUG2: query_callback: "TBCP=F".
  DEBUG2: query_callback: "Color=T".
  DEBUG2: query_callback: "Copies=T".
  DEBUG2: query_callback: "Duplex=T".
  DEBUG2: query_callback: "PaperCustom=T".
  DEBUG2: query_callback: "Bind=F".
  DEBUG2: query_callback: "Collate=T".
  DEBUG2: query_callback: "Sort=T".
  DEBUG2: query_callback: "Staple=F".
  DEBUG2: query_callback: "Punch=0".
  DEBUG2: query_callback: "PaperMax=legal-A4".
  network dnssd://Canon%20MF8300C%20Series._pdl-datastream._tcp.local/ "Canon 
MF8300C Series" "Canon MF8300C Series" "MFG:Canon;MDL:MF8300C Series;" ""
  DEBUG: sent=2, count=2
  myuseraccount@myuseraccount-System-Product-Name:~$ /usr/lib/cups/backend/snmp 
192.168.1.100
  network socket://192.168.1.100 "Canon MF8300C Series" "Canon MF8300C Series" 
"MFG:Canon;MDL:MF8300C Series;CLS:PRINTER;DES:Canon MF8300C 
Series;CID:;CMD:LIPSLX,CPCA;" ""
  myuseraccount@myuseraccount-System-Product-Name:~$ lpinfo -v
  network ipp
  network https
  network ipps
  network http
  file cups-brf:/
  network beh
  direct hp
  serial serial:/dev/ttyS0?baud=115200
  network socket
  network lpd
  direct parallel:/dev/lp0
  file cups-pdf:/
  network bjnp
  direct hpfax
  network dnssd://Canon%20MF8300C%20Series._pdl-datastream._tcp.local/
  network socket:

[Touch-packages] [Bug 1743939] [NEW] Canon MF8380 Wireless Network Not Printing

[Scott Stehno]

Public bug reported:

A Canon MF8380CDW printer will not print any thing after upgrading to
17.10.  I ran all  the steps from this
https://wiki.ubuntu.com/DebuggingPrintingProblems web site.

I have attached a lot of log files.  Not sure which one is needed. The
printer did work back under 15.10 or 16.04 but took a lot to get it
fixed to work then.  I have tried to print from 18.04 and it has the
same problem with this printer.




myuseraccount@myuseraccount-System-Product-Name:~$ /usr/lib/cups/backend/snmp
network socket://192.168.1.100 "Canon MF8300C Series" "Canon MF8300C Series" 
"MFG:Canon;MDL:MF8300C Series;CLS:PRINTER;DES:Canon MF8300
C Series;CID:;CMD:LIPSLX,CPCA;" ""
myuseraccount@myuseraccount-System-Product-Name:~$ sudo 
/usr/lib/cups/backend/dnssd
[sudo] password for myuseraccount:
DEBUG: sent=0, count=0
DEBUG: Querying "Canon\032MF8300C\032Series._printer._tcp.local"...
DEBUG: Querying "Canon\032MF8300C\032Series._pdl-datastream._tcp.local"...
DEBUG: sent=0, count=2
DEBUG2: query_callback(browser=0x556cd4f96420, interfaceIndex=2, protocol=0, 
event=0, fullName="Canon\032MF8300C\032Series._printer._tcp.local", rrclass=1, 
rrtype=16, rdata=0x
556cd4f97854, rdlen=338, flags=5, context=0x556cd4f95900)
DEBUG2: query_callback: "txtvers=1".
DEBUG2: query_callback: "note=".
DEBUG2: query_callback: "qtotal=1".
DEBUG2: query_callback: "priority=20".
DEBUG2: query_callback: "ty=Canon MF8300C Series".
DEBUG2: query_callback: "product=(CNMF8300C Series)".
DEBUG2: query_callback: "pdl=application/octet-stream".
DEBUG2: query_callback: 
"adminurl=http://Canon0f2ec4.local/m_network_tcpip.html";.
DEBUG2: query_callback: "usb_MFG=Canon".
DEBUG2: query_callback: "usb_MDL=MF8300C Series".
DEBUG2: query_callback: "Transparent=F".
DEBUG2: query_callback: "Binary=F".
DEBUG2: query_callback: "TBCP=F".
DEBUG2: query_callback: "Color=T".
DEBUG2: query_callback: "Copies=T".
DEBUG2: query_callback: "Duplex=T".
DEBUG2: query_callback: "PaperCustom=T".
DEBUG2: query_callback: "Bind=F".
DEBUG2: query_callback: "Collate=T".
DEBUG2: query_callback: "Sort=T".
DEBUG2: query_callback: "Staple=F".
DEBUG2: query_callback: "Punch=0".
DEBUG2: query_callback: "PaperMax=legal-A4".
DEBUG2: query_callback(browser=0x556cd4f96420, interfaceIndex=-1, protocol=-1, 
event=2, fullName="Canon\032MF8300C\032Series._printer._tcp.local", rrclass=1, 
rrtype=16, rdata=
(nil), rdlen=0, flags=0, context=0x556cd4f95900)
DEBUG2: query_callback(browser=0x556cd4f95aa0, interfaceIndex=2, protocol=0, 
event=0, fullName="Canon\032MF8300C\032Series._pdl-datastream._tcp.local", 
rrclass=1, rrtype=16, r
data=0x556cd4f97a0c, rdlen=338, flags=5, context=0x556cd4f95780)
DEBUG2: query_callback: "txtvers=1".
DEBUG2: query_callback: "note=".
DEBUG2: query_callback: "qtotal=1".
DEBUG2: query_callback: "priority=10".
DEBUG2: query_callback: "ty=Canon MF8300C Series".
DEBUG2: query_callback: "product=(CNMF8300C Series)".
DEBUG2: query_callback: "pdl=application/octet-stream".
DEBUG2: query_callback: 
"adminurl=http://Canon0f2ec4.local/m_network_tcpip.html";.
DEBUG2: query_callback: "usb_MFG=Canon".
DEBUG2: query_callback: "usb_MDL=MF8300C Series".
DEBUG2: query_callback: "Transparent=F".
DEBUG2: query_callback: "Binary=F".
DEBUG2: query_callback: "TBCP=F".
DEBUG2: query_callback: "Color=T".
DEBUG2: query_callback: "Copies=T".
DEBUG2: query_callback: "Duplex=T".
DEBUG2: query_callback: "PaperCustom=T".
DEBUG2: query_callback: "Bind=F".
DEBUG2: query_callback: "Collate=T".
DEBUG2: query_callback: "Sort=T".
DEBUG2: query_callback: "Staple=F".
DEBUG2: query_callback: "Punch=0".
DEBUG2: query_callback: "PaperMax=legal-A4".
network dnssd://Canon%20MF8300C%20Series._pdl-datastream._tcp.local/ "Canon 
MF8300C Series" "Canon MF8300C Series" "MFG:Canon;MDL:MF8300C Series;" ""
DEBUG: sent=2, count=2
myuseraccount@myuseraccount-System-Product-Name:~$ /usr/lib/cups/backend/snmp 
192.168.1.100
network socket://192.168.1.100 "Canon MF8300C Series" "Canon MF8300C Series" 
"MFG:Canon;MDL:MF8300C Series;CLS:PRINTER;DES:Canon MF8300C 
Series;CID:;CMD:LIPSLX,CPCA;" ""
myuseraccount@myuseraccount-System-Product-Name:~$ lpinfo -v
network ipp
network https
network ipps
network http
file cups-brf:/
network beh
direct hp
serial serial:/dev/ttyS0?baud=115200
network socket
network lpd
direct parallel:/dev/lp0
file cups-pdf:/
network bjnp
direct hpfax
network dnssd://Canon%20MF8300C%20Series._pdl-datastream._tcp.local/
network socket://192.168.1.100
myuseraccount@myuseraccount-System-Product-Name:~$ avahi-browse -a -v -t -r
Server version: avahi 0.6.32; Host name: myuseraccount-System-Product-Name.local
E Ifce Prot Name  Type 
Domain
: Cache exhausted
: All for now
myuseraccount@myuseraccount-System-Product-Name:~$ avahi-browse -a -v -c -r
Server version: avahi 0.6.32; Host name: myuseraccount-System-Product-Name.local
E Ifce Prot Name  Type 
Domain
: Cache exhausted

ProblemType: Bug

[Touch-packages] [Bug 1743939] Re: Canon MF8380 Wireless Network Not Printing

[Scott Stehno]

myuseraccount@myuseraccount-System-Product-Name:~$ ifconfig 
enp3s0: flags=4163  mtu 1500 
   inet 192.168.1.66  netmask 255.255.255.0  broadcast 192.168.1.255 
   inet6 2600:1700:5270:9c00:180c:2f00:4a3d:95e0  prefixlen 64  scopeid 
0x0 
   inet6 2600:1700:5270:9c00:87a4:1cae:bf0:552f  prefixlen 64  scopeid 
0x0 
   inet6 fe80::776:f004:4e65:db1d  prefixlen 64  scopeid 0x20 
   ether 10:bf:48:b6:dd:3f  txqueuelen 1000  (Ethernet) 
   RX packets 49910  bytes 10437067 (10.4 MB) 
   RX errors 0  dropped 0  overruns 0  frame 0 
   TX packets 11245  bytes 1359731 (1.3 MB) 
   TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 

lo: flags=73  mtu 65536 
   inet 127.0.0.1  netmask 255.0.0.0 
   inet6 ::1  prefixlen 128  scopeid 0x10 
   loop  txqueuelen 1000  (Local Loopback) 
   RX packets 912  bytes 87131 (87.1 KB) 
   RX errors 0  dropped 0  overruns 0  frame 0 
   TX packets 912  bytes 87131 (87.1 KB) 
   TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 

myuseraccount@myuseraccount-System-Product-Name:~$ route 
Kernel IP routing table 
Destination Gateway Genmask Flags Metric RefUse Iface 
default homeportal  0.0.0.0 UG10000 enp3s0 
link-local  0.0.0.0 255.255.0.0 U 1000   00 enp3s0 
192.168.1.0 0.0.0.0 255.255.255.0   U 10000 enp3s0 
myuseraccount@myuseraccount-System-Product-Name:~$ 


Unknown Withheld1k  Unknown canceled at
Wed 17 Jan 2018 04:43:41 PM CST 
"src = bidiCommon.c, line = 1200, err = 0¥nDEBUG2: prtMarkerSuppliesLevel.1.1 = 
100" 
Canon_MF8300C_Series-77 Unknown Withheld1k  Unknown 
canceled at
Wed 17 Jan 2018 04:46:03 PM CST 
 
Canon_MF8300C_Series-78 Unknown Withheld1k  1   
completed at
Wed 17 Jan 2018 05:16:46 PM CST 
 
Canon_MF8300C_Series-79 Unknown Withheld1k  1   
completed at
Wed 17 Jan 2018 05:16:47 PM CST 
 
Canon_MF8300C_Series-80 Unknown Withheld1k  1   
completed at
Wed 17 Jan 2018 05:20:46 PM CST 
 
Canon_MF8300C_Series-81 Unknown Withheld1k  1   
completed at
Wed 17 Jan 2018 05:22:12 PM CST 
 
Canon_MF8300C_Series-82 Unknown Withheld1k  1   
completed at
Wed 17 Jan 2018 05:23:54 PM CST 
 
Canon_MF8300C_Series-83 Unknown Withheld1k  1   
completed at
Wed 17 Jan 2018 05:26:05 PM CST 
 
Canon_MF8300C_Series-84 Unknown Withheld1k  1   
completed at
Wed 17 Jan 2018 05:28:14 PM CST 


I have installed both drivers from canon 34-2 and 340 and still will not
print.

E [17/Jan/2018:00:10:34 -0600] Canon_MF8300C_Series: File 
\"/usr/lib/cups/filter/pstoufr2cpca\" not available: No such file or directory  

 
E [17/Jan/2018:00:10:34 -0600] Canon_MF8300C_Series: File 
\"/usr/lib/cups/filter/pstoufr2cpca\" not available: No such file or directory  

 
E [17/Jan/2018:00:10:34 -0600] Unknown: File 
\"/usr/lib/cups/filter/pstoufr2cpca\" not available: No such file or directory  

  
E [17/Jan/2018:04:21:56 -0600] Canon_MF8300C_Series: File 
\"/usr/lib/cups/filter/pstoufr2cpca\" not available: No such file or directory  

 
E [17/Jan/2018:04:21:56 -0600] Canon_MF8300C_Series: File 
\"/usr/lib/cups/filter/pstoufr2cpca\" not available: No such file or directory  

 
E [17/Jan/2018:04:21:56 -0600] Unknown: File 
\"/usr/lib/cups/filter/pstoufr2cpca\" not available: No such file or directory  

  
E [17/Jan/2018:04:42:40 -0600] Canon_MF8300C_Series: File 
\"/usr/lib/cups/filter/pstoufr2cpca\" not available: No such file or directory  

 
E [17/Jan/2018:04:42:40 -0600] [Job 69] Unable to start filter "pstoufr2cpca" - 
Success.
  

[Touch-packages] [Bug 97722] Re: Windows dual-boot can corrupt system clock even if time servers are enabled

[Dan Bryant]

I am not sure if my issue would have the same bug report number or not
but I did a search and this bug is very close to the same issue I am
having. I am using dual boot with grub2, windows 7 and Ubuntu Mate 17. I
mainly use windows and the clock works fine reboot after reboot no
issues, and when I boot into Mate the clock works fine and has the
correct time, but then when I boot back to windows the time displayed is
6 hours ahead, and if it goes unnoticed it will stay that way until I
change it. This is getting very annoying, as all my previuos installs of
Ubuntu and Linux on the same machine and same version of windows I did
not have this problem, even after the latest updates to 17.10 I continue
to have this issue. This should be a simple fix?

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

Title:
  Windows dual-boot can corrupt system clock even if time servers are
  enabled

Status in ntp package in Ubuntu:
  Invalid

Bug description:
  I use a dual boot setup: Windows XP and Kubuntu Edgy. First of all,
  Kubuntu did not detect the switch to summer time, and I didn't want to
  do it manually, so I ticked the box "Set date and time manually". I
  applied, and the time was set to the correct value.

  I have not logged into Windows for quite some time, but I had to check
  something. It detected the switch, and changed the clock to summer
  time. When I went back to Kubuntu I found that the clock now is off by
  1 hour.

  That leads to the question: why didn't it realize that the clock was
  off? Doesn't it check the time servers on startup / logon? I think it
  should realize that the difference between the time on the local clock
  and the time server has changed. Otherwise how will it know when to
  switch to winter time? I think it should be able to handle this, and
  that the clock value has been modified, and change it back.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/97722/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: patch

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1742941] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From danie...@au1.ibm.com 2018-01-17 22:56 EDT---
code submitted upstream: https://github.com/madler/zlib/pull/335

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

Title:
  zlib: improve  crc32 performance on P8

Status in The Ubuntu-power-systems project:
  Triaged
Status in zlib package in Ubuntu:
  New

Bug description:
  Calculate the checksum of data that is 16 byte aligned and a multiple
  of  16 bytes.

  The first step is to reduce it to 1024 bits. We do this in 8 parallel
   chunks in order to mask the latency of the vpmsum instructions. If we
   have more than 32 kB of data to checksum we repeat this step multiple
   times, passing in the previous 1024 bits.

   The next step is to reduce the 1024 bits to 64 bits. This step adds
   32 bits of 0s to the end - this matches what a CRC does. We just
   calculate constants that land the data in this 32 bits.

   We then use fixed point Barrett reduction to compute a mod n over GF(2)
   for n = CRC using POWER8 instructions. We use x = 32.

   http://en.wikipedia.org/wiki/Barrett_reduction

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1742941/+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 1743931] Re: package linux-image-extra-3.13.0-139-generic 3.13.0-139.188 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/1743931

Title:
  package linux-image-extra-3.13.0-139-generic 3.13.0-139.188 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:
  Running hooks in /etc/ca-certificates/update.ddone.
  Processing triggers for tex-common (4.04) ...
  Running mktexlsr. This may take some time... done.
  Processing triggers for ureadahead (0.100.0-16) ...
  Errors were encountered while processing:
   linux-firmware
   linux-image-extra-3.13.0-139-generic
   linux-image-generic
   linux-generic
   linux-server
   linux-image-server
   squid3
   squid
   initramfs-tools
  Error in function:

  
  A fatal error occurred

  Please report this as a bug and include the files
  /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in
  your report. The upgrade has aborted.
  Your original sources.list was saved in
  /etc/apt/sources.list.distUpgrade.

  SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)


  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (797.9 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): S

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  99%

  *** To continue, you must visit the following URL:

https://bugs.launchpad.net/ubuntu/+source/initramfs-
  tools/+filebug/e0ae7b26-fc02-11e7-9115-68b5996a96c8?field.title=package
  +linux-image-
  extra-3.13.0-139-generic+3.13.0-139.188+failed+to+install%2Fupgrade%3A
  +run-parts%3A+%2Fetc%2Fkernel%2Fpostinst.d%2Finitramfs-
  tools+exited+with+return+code+1

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  
  Choices:
1: Launch a browser now
C: Cancel
  Please choose (1/C): C

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (797.2 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-139-generic 3.13.0-139.188
  ProcVersionSignature: Ubuntu 3.2.0-126.169-generic 3.2.79
  Uname: Linux 3.2.0-126-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', 
'/dev/dsp1', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer', 
'/dev/sequencer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Wed Jan 17 19:45:03 2018
  DuplicateSignature: 
package:linux-image-extra-3.13.0-139-generic:3.13.0-139.188:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=33e3f4b9-fd73-41ff-ab23-0c8a9408c7a2
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: BIOSTAR Group G31-M7 TE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-126-generic 
root=/dev/mapper/hostname-root ro quiet
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.14
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'

[Touch-packages] [Bug 1743931] [NEW] package linux-image-extra-3.13.0-139-generic 3.13.0-139.188 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Eric Pardee]

Public bug reported:

Running hooks in /etc/ca-certificates/update.ddone.
Processing triggers for tex-common (4.04) ...
Running mktexlsr. This may take some time... done.
Processing triggers for ureadahead (0.100.0-16) ...
Errors were encountered while processing:
 linux-firmware
 linux-image-extra-3.13.0-139-generic
 linux-image-generic
 linux-generic
 linux-server
 linux-image-server
 squid3
 squid
 initramfs-tools
Error in function:


A fatal error occurred

Please report this as a bug and include the files
/var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in
your report. The upgrade has aborted.
Your original sources.list was saved in
/etc/apt/sources.list.distUpgrade.

SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)


*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (797.9 KB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): S

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.

*** Uploading problem information

The collected information is being sent to the bug tracking system.
This might take a few minutes.
99%

*** To continue, you must visit the following URL:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+filebug/e0ae7b26-fc02-11e7-9115-68b5996a96c8?field.title=package
+linux-image-
extra-3.13.0-139-generic+3.13.0-139.188+failed+to+install%2Fupgrade%3A
+run-parts%3A+%2Fetc%2Fkernel%2Fpostinst.d%2Finitramfs-
tools+exited+with+return+code+1

You can launch a browser now, or copy this URL into a browser on another
computer.


Choices:
  1: Launch a browser now
  C: Cancel
Please choose (1/C): C

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (797.2 KB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-139-generic 3.13.0-139.188
ProcVersionSignature: Ubuntu 3.2.0-126.169-generic 3.2.79
Uname: Linux 3.2.0-126-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', 
'/dev/dsp1', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer', 
'/dev/sequencer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Date: Wed Jan 17 19:45:03 2018
DuplicateSignature: 
package:linux-image-extra-3.13.0-139-generic:3.13.0-139.188:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=33e3f4b9-fd73-41ff-ab23-0c8a9408c7a2
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: BIOSTAR Group G31-M7 TE
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-126-generic 
root=/dev/mapper/hostname-root ro quiet
RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.14
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: initramfs-tools
Title: package linux-image-extra-3.13.0-139-generic 3.13.0-139.188 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to trusty on 2018-01-18 (0 days ago)
WifiSyslog:
 
dmi.bios.date: 09/25/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080014
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: G31-M7 TE
dmi.board.vendor: BIOSTAR Group
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080014:bd09/25/2009:svnBIOSTARGrou

[Touch-packages] [Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Forest]

A systemd build with my patch applied is available here:

https://launchpad.net/~foresto/+archive/ubuntu/ubuntutweaks/

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Forest]

The ecryptfs-manager workaround helps the mount to succeed, but (at
least in my case) the system refuses to unmount it afterward. This is a
problem for those of us who open our ecryptfs volumes only for as long
as they're needed.

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Forest]

This is a systemd bug, created by this commit:

https://github.com/systemd/systemd/commit/74dd6b5

It looks like poettering has attempted to address it in more recent
versions of systemd (though that doesn't help us in ubuntu 17.10):

https://github.com/systemd/systemd/pull/6832

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Forest]

Here's a simple patch to disable the broken systemd feature, and restore
ecryptfs functionality.

** Patch added: "disable_system_service_session_keyrings.patch"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718658/+attachment/5038578/+files/disable_system_service_session_keyrings.patch

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Launchpad Bug Tracker]

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

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

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1726873] Re: mount.ecryptfs_private can't mount in 17.10

[Forest]

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

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

** This bug has been marked a duplicate of bug 1718658
   ecryptfs-mount-private fails to initialize ecryptfs keys

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

Title:
  mount.ecryptfs_private can't mount in 17.10

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  I am using several ecryptfs mounts with ecryptfs-add-passphrase and
  mount.ecryptfs_private, configured in ~/.ecryptfs/xxx.conf and
  ~/.ecryptfs/xxx.sig, which was working well for years up to 17.04.

  With 17.10 I can't mount these file systems anymore.

  ecryptfs-add-passphrase says

  Inserted auth tok with sig [] into the user session keyring
   
  with the correct sig (!). 

  
  Trying to mount with mount.ecryptfs_private then says 
  mount: No such file or directory

  although all directories present and correct.

  the Kernel then says (dmesg):

  
  [10149.247972] Could not find key with description: [...]
  [10149.247994] process_request_key_err: No key
  [10149.248000] Could not find valid key in user session keyring for sig 
specified in mount option: [...]
  [10149.248012] One or more global auth toks could not properly register; rc = 
[-2]
  [10149.248019] Error parsing options; rc = [-2]

  
  with exactly the same sig! 

  
  So although ecryptfs-add-passphrase claimed to have added the key to the 
keyring, the kernel complains that it could not find such a key.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ecryptfs-utils 111-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue Oct 24 15:31:45 2017
  InstallationDate: Installed on 2017-10-24 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  SourcePackage: ecryptfs-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1726873/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Forest]

** Also 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/1718658

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1743773] Re: Audio problems after updating

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1743773

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

Title:
  Audio problems after updating

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I'm running Ubuntu 17.10 and installed today a bunch of updates from
  the software updater. After that, there's no sound from headphones
  anymore, even if they are detected when plugged in and show up in
  sound settings and alsamixer.

  The headphones work on other devices, and the computer speakers work
  too, so the problem seems limited to the headphones output.

  Attached the alsa-info output.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1743773/+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 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Daniel van Vugt]

Indeed we need to get this fix released in bionic first.

Possibly confusing is that "LP: #1718824" is only mentioned in the
changelog entry for "1:11.1-1ubuntu3" and not "1:11.1-1ubuntu4". But the
fix is still there in both.

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  New
Status in pulseaudio source package in Artful:
  New

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1736371] Re: Feature Request: Syncthing integration

[Denis Donici]

Second you here. In most cases, a user has his mobile phone on him.
There are also cases when one user has more than one computer and it's
quite a hustle to keep all these devices in sync. One of the Apple's
advantages is everything is in sync. I can see Ubuntu team bringing
Syncthing as a default server/client for syncing its files across
multiple devices. Even user-specific config files could be stored for
back-up on the mobile phone. And next time, on a fresh install, config
files are retrieved from the phone, everything is back the way it was.
Really neat and convenient. Syncthing has an android client. I think it
is an opportunity Ubuntu should take advantage of.

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

Title:
  Feature Request: Syncthing integration

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  since the removal of Ubuntu One filehosting, a nice, well-integrated
  filesync in Ubuntu desktop is missing. It would be a welcome addition
  to have filesync back as an out-of-the box feature.

  Syncthing is a proven open-source p2p filesync software. The software
  has a track record of many years under active development, the
  developer community is alive and well. It seems to be stable and the
  architecture seems sound. (I cannot comment on its security
  implications, though.)

  Syncthing is server-less, it doesn't require a central/cloud server.
  The usability leaves a lot to be desired and the current installation
  and end-user experience is poor for a novice user.

  The most successful part of Ubuntu desktop's mission has always been
  making complicated Linux software easier to use for novice end-users.

  Therefore my request is that Ubuntu considers spending development
  resources on improving the user experience of Syncthing.

  - Make Syncthing a part of a default Ubuntu desktop installation.
  - Design a better end-user interface for remote sync device management.
  - Design a better end-user interface for seamless filemanager integration.
  - Add a possible, optional encrypted cloud storage sync service.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1736371/+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 1736371] Re: Feature Request: Syncthing integration

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  Feature Request: Syncthing integration

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  since the removal of Ubuntu One filehosting, a nice, well-integrated
  filesync in Ubuntu desktop is missing. It would be a welcome addition
  to have filesync back as an out-of-the box feature.

  Syncthing is a proven open-source p2p filesync software. The software
  has a track record of many years under active development, the
  developer community is alive and well. It seems to be stable and the
  architecture seems sound. (I cannot comment on its security
  implications, though.)

  Syncthing is server-less, it doesn't require a central/cloud server.
  The usability leaves a lot to be desired and the current installation
  and end-user experience is poor for a novice user.

  The most successful part of Ubuntu desktop's mission has always been
  making complicated Linux software easier to use for novice end-users.

  Therefore my request is that Ubuntu considers spending development
  resources on improving the user experience of Syncthing.

  - Make Syncthing a part of a default Ubuntu desktop installation.
  - Design a better end-user interface for remote sync device management.
  - Design a better end-user interface for seamless filemanager integration.
  - Add a possible, optional encrypted cloud storage sync service.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1736371/+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 1743905] Re: SM: Add an option to generate INV file only for Provision CMD with SM

[Prabhu Seshachellam]

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

** No longer affects: procps (Ubuntu)

** Changed in: juniperopenstack
 Assignee: (unassigned) => Prabhu Seshachellam (sprabhu72)

** Changed in: juniperopenstack
   Importance: Undecided => High

** Also affects: juniperopenstack/trunk
   Importance: High
 Assignee: Prabhu Seshachellam (sprabhu72)
   Status: New

** Changed in: juniperopenstack/trunk
Milestone: None => r5.0.0

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

Title:
  SM: Add an option to generate INV file only for Provision CMD with SM

Status in Juniper Openstack:
  New
Status in Juniper Openstack trunk series:
  New

Bug description:
  
  Syntax for the new option - "no_run" :

  server-manager provision --cluster_id five-node ga_8 --no_run
  >> Main Entry  <<
  Namespace(cluster_id='five-node', contrail_image_id=None, interactive=False, 
no_confirm=False, no_run=True, package_image_id='ga_8', 
provision_params_file=None, server_id=None, tag=None, tasks=None, where=None)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/1743905/+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 1743905] [NEW] SM: Add an option to generate INV file only for Provision CMD with SM

[Prabhu Seshachellam]

Public bug reported:


Syntax for the new option - "no_run" :

server-manager provision --cluster_id five-node ga_8 --no_run
>> Main Entry  <<
Namespace(cluster_id='five-node', contrail_image_id=None, interactive=False, 
no_confirm=False, no_run=True, package_image_id='ga_8', 
provision_params_file=None, server_id=None, tag=None, tasks=None, where=None)

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

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

Title:
  SM: Add an option to generate INV file only for Provision CMD with SM

Status in procps package in Ubuntu:
  New

Bug description:
  
  Syntax for the new option - "no_run" :

  server-manager provision --cluster_id five-node ga_8 --no_run
  >> Main Entry  <<
  Namespace(cluster_id='five-node', contrail_image_id=None, interactive=False, 
no_confirm=False, no_run=True, package_image_id='ga_8', 
provision_params_file=None, server_id=None, tag=None, tasks=None, where=None)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1743905/+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 686000] Re: top shows unknown argument when -U is set

[Balint Reczey]

This seems to be fixed for some time.

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

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

Title:
  top shows unknown argument when -U is set

Status in procps package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: procps

  With version 1:3.2.8-9ubuntu3 of procps, it appears to have a bug in
  top which it doesn't send a null pointer after the username, so its
  parsing in enviromental information from memory

  This is taken from here: http://us.generation-nt.com/answer/bug-571790
  -patch-bug-571790-top-unknown-argument-k-help-169599851.html (with a
  patch)

  This doesn't happen in 10.04 which has procps version:
  1:3.2.8-1ubuntu4

  1) Version:
  root@chgbld03:~# lsb_release -rd
  Description:Ubuntu 10.10
  Release:10.10
  root@chgbld03:~#

  2) Package version:

  root@chgbld03:~# apt-cache policy procps
  procps:
Installed: 1:3.2.8-9ubuntu3
Candidate: 1:3.2.8-9ubuntu3
Version table:
   *** 1:3.2.8-9ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
  100 /var/lib/dpkg/status
  root@chgbld03:~#

  3) What you expected to happen:

  Top running but only showing processes from 'mpukgame'

  4) What happened instead:
  root@chgbld03:~# top -U mpukgame
  top: unknown argument 'T'
  usage:  top -hv | -bcisSH -d delay -n iterations [-u user | -U user] -p pid 
[,pid ...]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/686000/+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 1073543] Re: [patch] Adding support for thread

[Balint Reczey]

This seems to be fixed for some time.

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

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

Title:
  [patch] Adding support for thread

Status in procps package in Ubuntu:
  Fix Released

Bug description:
  As many tools require thread ids (not only processes) I added thread support 
  to pgrep.

  to show all mysql threads, simply use:
   # pgrep -fw mysql

  I posted it on the procps mailing list, but it seems dead...

  Patch is attached. Feedback welcome.

  Thx++ & Peace,
  R.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1073543/+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 1721839] Re: [REGRESSION] Services asked for by UDEV do not get triggered

[Till Kamppeter]

Now in Bionic the only systemd problem known to me is the
quoting/unquoting turnaround problem mentioned here.

In system-config-printer this problem got worked around upstream by
calling the systemd service with the simpler bus and device IDs and not
with the device path. This works reliably in Bionic and probably also in
Artful.

Another, more severe severe systemd problem in Artful was that systemd
did not unregister (at least some) USB devices when they got unplugged.
This problem went away in Bionic.

So in Bionic I do not have any problems with USB printer auto-setup any
more.

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

Title:
  [REGRESSION] Services asked for by UDEV do not get triggered

Status in systemd:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The packages system-config-printer-udev and ippusbxd are installed,
  having the following UDEV rule files:

  /lib/udev/rules.d/70-printers.rules

  --
  # Low-level USB device add trigger
  ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="udev-configure-printer", 
TAG+="systemd", PROGRAM="/bin/systemd-escape 
--template=udev-configure-printer@.service %p", ENV{SYSTEMD_WANTS}+="%c"
  # Low-level USB device remove trigger
  ACTION=="remove", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701*:*", RUN+="udev-configure-printer remove %p"
  --

  /lib/udev/rules.d/55-ippusbxd.rules

  --
  # ippusbxd udev rules file

  ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device" 
ENV{ID_USB_INTERFACES}=="*:070104:*", OWNER="root", GROUP="lp", MODE="0664", 
PROGRAM="/bin/systemd-escape --template=ippusbxd@.service 
$env{BUSNUM}:$env{DEVNUM}", ENV{SYSTEMD_WANTS}+="%c"
  --

  If I turn on an appropriate printer (USB, supporting IPP-over-USB,
  here the HP DeskJet 2540) I get in the output of "udevadm monitor
  --environment"

  --
  UDEV  [17527.514150] add  /devices/pci:00/:00:14.0/usb2/2-2 (usb)
  ACTION=add
  BUSNUM=002
  DEVNAME=/dev/bus/usb/002/033
  DEVNUM=033
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2
  DEVTYPE=usb_device
  DRIVER=usb
  ID_BUS=usb
  ID_MODEL=Deskjet_2540_series
  ID_MODEL_ENC=Deskjet\x202540\x20series
  ID_MODEL_ID=c211
  ID_REVISION=0100
  ID_SERIAL=HP_Deskjet_2540_series_BR54BFB02C05XK
  ID_SERIAL_SHORT=BR54BFB02C05XK
  ID_USB_INTERFACES=:ffcc00:070104:070102:ff0401:
  ID_VENDOR=HP
  ID_VENDOR_ENC=HP
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  ID_VENDOR_ID=03f0
  MAJOR=189
  MINOR=160
  PRODUCT=3f0/c211/100
  SEQNUM=9891
  SUBSYSTEM=usb
  SYSTEMD_WANTS=ippusbxd@002:033.service 
udev-configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service 
printer.target
  TAGS=:udev-configure-printer:systemd:
  TYPE=0/0/0
  USEC_INITIALIZED=17527513940

  UDEV  [17527.517724] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
  .MM_USBIFNUM=00
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0
  DEVTYPE=usb_interface
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  INTERFACE=255/204/0
  MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFiscCCip00in00
  PRODUCT=3f0/c211/100
  SEQNUM=9892
  SUBSYSTEM=usb
  TYPE=0/0/0
  USEC_INITIALIZED=17527517478

  UDEV  [17527.522565] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2 (usb)
  .MM_USBIFNUM=02
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2
  DEVTYPE=usb_interface
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  INTERFACE=255/4/1
  MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFisc04ip01in02
  PRODUCT=3f0/c211/100
  SEQNUM=9895
  SUBSYSTEM=usb
  TYPE=0/0/0
  USEC_INITIALIZED=17527522332

  UDEV  [17527.523761] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1 (usb)
  .MM_USBIFNUM=01
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1
  DEVTYPE=usb_interface
  DRIVER=usblp
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  INTERFACE=7/1/2
  MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00ic07isc01ip02in01
  PRODUCT=3f0/c211/100
  SEQNUM=9893
  SUBSYSTEM=usb
  TYPE=0/0/0
  USEC_INITIALIZED=17527523500

  UDEV  [17527.527275] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1 (usbmisc)
  .MM_USBIFNUM=01
  ACTION=add
  DEVNAME=/dev/usb/lp1
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1
  MAJOR=180
  MINOR=1
  SEQNUM=9894
  SUBSYSTEM=usbmisc
  USEC_INITIALIZED=17527527175
  --

  Here one can see that the UDEV rules files are correct, leading to the
  correct systemd services being requested

  SYSTEMD_WANTS=ippusbxd@002:033.service udev-configure-printer
  @-devices-pci:00-:00:14.0-usb2-2\x2d2.service printer.target

  but neither the service ippusbxd@002:033.service nor the service udev-
  configure-pr

[Touch-packages] [Bug 1719746] Re: gdebi 0.9.5.7+nmu1ubuntu3 broke being able to open .debs on default Ubuntu desktop

[Jeremy Bicha]

** Changed in: gdebi (Ubuntu Artful)
   Status: Confirmed => Triaged

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

Title:
  gdebi 0.9.5.7+nmu1ubuntu3 broke being able to open .debs on default
  Ubuntu desktop

Status in gdebi package in Ubuntu:
  Fix Released
Status in gdebi source package in Artful:
  Triaged

Bug description:
  I don't use gdebi but this commit looks wrong:

  https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu1ubuntu3

  See
  https://lintian.debian.org/tags/desktop-mime-but-no-exec-code.html

  https://standards.freedesktop.org/desktop-entry-spec/desktop-entry-
  spec-latest.html#mime-types

  (Do not be confused by the Type=MimeType deprecation. This file is
  Type=Application.)

  Here's a user video report:
  https://youtu.be/yDrAbBAp-1A?t=16m19s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1719746/+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 1743182] Re: free -s N didn't work well

[Balint Reczey]

This is fixed in Zesty and later versions.

** Changed in: procps (Ubuntu)
   Status: New => Fix Released

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

Title:
  free -s N didn't work well

Status in procps package in Ubuntu:
  Fix Released

Bug description:
  sample:
  in ubuntu 16.04

  free -s 3

  result shows like this

  free: seconds argument `3' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1743182/+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 1719746] Re: gdebi 0.9.5.7+nmu1ubuntu3 broke being able to open .debs on default Ubuntu desktop

[Launchpad Bug Tracker]

This bug was fixed in the package gdebi - 0.9.5.7+nmu2

---
gdebi (0.9.5.7+nmu2) unstable; urgency=medium

  [ Julien Lavergne ]
  * Add a gdebi-gtk-pkexec executable to launch without gksu (LP: #189617).
  * debian/control:
   - Make gdebi depends on policykit-1 | gksu.

  [ Simon Quigley ]
  * Finish the policykit port:
- gdebi-gtk-pkexec isn't needed, root access is only needed for the
  package installation and removal.
- Install the policykit file (create debian/gdebi-gtk.install).
- Modify the gksu commands in GDebi/GDebiGtk.py to call pksu instead.
- Drop the dependency on gksu and only depend on policykit-1.
- Thanks for the initial work, Julien!

  [ Jeremy Bicha ]
  * Upload to unstable (LP: #1719746)
  * Stop building gdebi-kde since gdebi-kde is the last package in Testing
depending on the unmaintained pykde4 (Closes: #864963)

 -- Jeremy Bicha   Sun, 31 Dec 2017 11:00:13 -0500

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

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

Title:
  gdebi 0.9.5.7+nmu1ubuntu3 broke being able to open .debs on default
  Ubuntu desktop

Status in gdebi package in Ubuntu:
  Fix Released
Status in gdebi source package in Artful:
  Confirmed

Bug description:
  I don't use gdebi but this commit looks wrong:

  https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu1ubuntu3

  See
  https://lintian.debian.org/tags/desktop-mime-but-no-exec-code.html

  https://standards.freedesktop.org/desktop-entry-spec/desktop-entry-
  spec-latest.html#mime-types

  (Do not be confused by the Type=MimeType deprecation. This file is
  Type=Application.)

  Here's a user video report:
  https://youtu.be/yDrAbBAp-1A?t=16m19s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1719746/+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 1743897] [NEW] boot loader not repairing

[Shamim Akram]

Public bug reported:

boot loader not repairing

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
BootLog:
 [  OK  ] Started LSB: Speech Dispatcher.
 [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Jan 18 04:18:37 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3035]
   Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3035]
InstallationDate: Installed on 2017-02-26 (325 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2)
MachineType: Hewlett-Packard HP Compaq dc7900 Convertible Minitower
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=175070e4-764b-4085-93e7-45c288aeae89 ro plymouth:debug drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/05/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786G1 v01.16
dmi.board.name: 3032h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G1v01.16:bd03/05/2009:svnHewlett-Packard:pnHPCompaqdc7900ConvertibleMinitower:pvr:rvnHewlett-Packard:rn3032h:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP Compaq dc7900 Convertible Minitower
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
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: Thu Jan 18 04:17:21 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


** Tags: apport-bug compiz-0.9 i386 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/1743897

Title:
  boot loader not repairing

Status in xorg package in Ubuntu:
  New

Bug description:
  boot loader not repairing

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  BootLog:
   [  OK  ] Started LSB: Speech Dispatcher.
   [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jan 18 04:18:37 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3035]
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3035]
  InstallationDate: Installed on 2017-02-26 (325 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  MachineType: Hewlett-Packard HP Compaq dc7900 Convertible Minitower
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=175070e4-764b-4085-93e7-45c288aeae89 ro plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G1 v01.16
  dmi.board.name: 3032h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Pack

[Touch-packages] [Bug 1743899] [NEW] PCI/internal sound card not detected

[Sebastian]

Public bug reported:

My mic not working, so i decide to reainstal alsa and pulseaudio, after
this i dont have sound

Description:Ubuntu 17.10
Release:17.10

alsa-base:
  Zainstalowana: 1.0.25+dfsg-0ubuntu5
  Kandydująca:   1.0.25+dfsg-0ubuntu5
  Tabela wersji:
 *** 1.0.25+dfsg-0ubuntu5 500
500 http://pl.archive.ubuntu.com/ubuntu artful/main amd64 Packages
500 http://pl.archive.ubuntu.com/ubuntu artful/main i386 Packages
100 /var/lib/dpkg/status

pulseaudio:
  Zainstalowana: 1:10.0-2ubuntu3
  Kandydująca:   1:10.0-2ubuntu3
  Tabela wersji:
 *** 1:10.0-2ubuntu3 500
500 http://pl.archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 18 00:15:08 2018
InstallationDate: Installed on 2017-09-03 (136 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: Upgraded to artful on 2017-10-26 (83 days ago)
dmi.bios.date: 06/28/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.40
dmi.board.asset.tag: Default string
dmi.board.name: Z270 GAMING M7 (MS-7A57)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd06/28/2017:svnMSI:pnMS-7A57:pvr1.0:rvnMSI:rnZ270GAMINGM7(MS-7A57):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: Default string
dmi.product.name: MS-7A57
dmi.product.version: 1.0
dmi.sys.vendor: MSI

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My mic not working, so i decide to reainstal alsa and pulseaudio,
  after this i dont have sound

  Description:  Ubuntu 17.10
  Release:  17.10

  alsa-base:
Zainstalowana: 1.0.25+dfsg-0ubuntu5
Kandydująca:   1.0.25+dfsg-0ubuntu5
Tabela wersji:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://pl.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://pl.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  pulseaudio:
Zainstalowana: 1:10.0-2ubuntu3
Kandydująca:   1:10.0-2ubuntu3
Tabela wersji:
   *** 1:10.0-2ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 18 00:15:08 2018
  InstallationDate: Installed on 2017-09-03 (136 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to artful on 2017-10-26 (83 days ago)
  dmi.bios.date: 06/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270 GAMING M7 (MS-7A57)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd06/28/2017:svnMSI:pnMS-7A57:pvr1.0:rvnMSI:rnZ270GAMINGM7(MS-7A57):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A57
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1743899/+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 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu

[Scott Moser]

Marked as fix-released.
I tested today with 20180115.1 image from bionic.

wget http://cloud-images.ubuntu.com/bionic/20180115.1/bionic-server-
cloudimg-amd64.img -O bionic-server-cloudimg-amd64.img

url="https://smoser.brickies.net/ubuntu/nocloud/";
qemu-system-x86_64 -enable-kvm -m 768 \
   -net nic -net user \
   -drive file=disk.img,if=virtio \
   -smbios "type=1,serial=ds=nocloud-net;s=$url"


Just for info, showing:
$ curl https://smoser.brickies.net/ubuntu/nocloud/user-data
#cloud-config
password: passw0rd
chpasswd: { expire: False }
ssh_pwauth: True

$ curl https://smoser.brickies.net/ubuntu/nocloud/meta-data
instance-id: iid-brickies-nocloud


** No longer affects: cloud-init (Ubuntu Bionic)

** Changed in: cloud-init (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  DNS doesn't work in no-cloud as launched by ubuntu

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  In Progress
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  I use no-cloud to test the kernel in CI (I am maintainer of the bcache
  subsystem), and have been running it successfully under 16.04 cloud
  images from qemu, using a qemu command that includes:

  -smbios "type=1,serial=ds=nocloud-
  net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-
  metadata/linuxtst/"

  As documented here:

  http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html

  Under the new 17.10 cloud images, this doesn't work: the network comes
  up, but name resolution doesn't work-- /etc/resolv.conf is a symlink
  to a nonexistent file at this point of the boot and systemd-resolved
  is not running.  When I manually hack /etc/resolv.conf in the cloud
  image to point to 4.2.2.1 it works fine.

  I don't know if nameservice not working is by design, but it seems
  like it should work.  The documentation states:

  "With ds=nocloud-net, the seedfrom value must start with http://,
  https:// or ftp://";

  And https is not going to work for a raw IP address.

  Related bugs:
   * bug 1734939: #include fails silently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1734167/+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 1553137] Re: Change in OpenSSL triggers bug in XMLTooling

[Simon Déziel]

Xenial ships 1.5.6-2 so marking as fix released.

** Changed in: xmltooling (Ubuntu)
   Status: New => Fix Released

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

Title:
  Change in OpenSSL triggers bug in XMLTooling

Status in openssl package in Ubuntu:
  New
Status in xmltooling package in Ubuntu:
  Fix Released

Bug description:
  A recent change in the openssl package provided by Ubuntu triggers a
  bug in xmltooling. The change was introduced in openssl 1.0.1f-
  1ubuntu2.17 (14.04) and 1.0.1-4ubuntu5.34 (12.04) when releasing for
  USN-2913-3 [1]. Patch alt-cert-chains-7.patch (found in [2,3]) changes
  the intended use of the OpenSSL API and xmltooling was using it
  wrongly. This is fixed in upstream xmltooling version 1.5.6 [4].
  Please backport the fix from 1.5.6 or upgrade the xmltooling package
  to 1.5.6.

  [1] http://www.ubuntu.com/usn/usn-2913-3/
  [2] 
https://launchpadlibrarian.net/236983031/openssl_1.0.1-4ubuntu5.33_1.0.1-4ubuntu5.34.diff.gz
  [3] 
https://launchpadlibrarian.net/236982637/openssl_1.0.1f-1ubuntu2.16_1.0.1f-1ubuntu2.17.diff.gz
  [4] https://issues.shibboleth.net/jira/browse/CPPXT-105

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libxmltooling6 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Mar  4 11:43:47 2016
  InstallationDate: Installed on 2015-02-04 (394 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xmltooling
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1553137/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[laurel]

My Unity Launcher now works after installing the January 17, 2018 update
from the Software Updater(gnome-software).

I'm a newbie so I wasn't able to use the fixes noted in the other
comments but after the install, I clicked on the side panel and the
Dash, File Manager, Chromium browser and the suite of Libre Office tools
all worked.  The Launcher seems stable and doesn't flicker off and then
on.  Also I can go to the wheel at the top right and shutdown the
computer now.

I have a Toshiba Satellite M645 (2011)
Intel Core i5 CPU, 64 bit OS
Ubuntu 16.04.3 LTS

THANK YOU, Timo and all who tested this fix.  I appreciate all the work.
The good outcome of this, for me, was that I learned to use terminal
commands rather quickly! I now really appreciate the GUI interface.

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1739532] Re: apport-collect SHOULD prune out /home/%USER/ from JournalErrors

[Brian Murray]

To be clear I understand your issue here to be that only your username
(the logged in user) was replaced in the file JournalErrors.txt and that
you'd like to see every username replaced in JournalErrors.txt. Is that
a correct statement?

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

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

** Tags added: beaver

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

Title:
  apport-collect SHOULD prune out /home/%USER/ from JournalErrors

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  During https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1739525, I ran apport-collect.

  I was happy to see that my hostname from the system logs was pruned to
  "hostname". Great!

  However, there are some logs that complain about /home/FOO user ... we
  SHOULD NOT leak a user's $HOME directory contents (a potential list of
  local user accounts) into these reports. This MAY be considered as
  sensitive information.

  The JournalErrors.txt should prune it.

  Example of CULPRITS:
  {{{
  Dec 20 21:39:20 hostname com.ubuntu.OneConf[3069]: 
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file 
or directory: 
'/home/FOO/.cache/oneconf/1dfe6d2e52223c637c7bddd90002/other_hosts'
  Dec 20 21:39:33 hostname com.ubuntu.OneConf[18688]: 
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file 
or directory: 
'/home/BAR/.cache/oneconf/1dfe6d2e52223c637c7bddd90002/other_hosts'
  }}}

  The suggestion here, is simply to also prune out usernames from ANY
  "/home/%USER" or "~%USER" type regexes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1739532/+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 1637239] Re: Please merge ncurses 6.0+20161126-1 (main) from Debian unstable (main)

[Julian Andres Klode]

Uploaded the latest and greatest last week:

ncurses (6.0+20171125-1ubuntu1) bionic; urgency=low

  * Merge from Debian unstable (LP: #1637239).  Remaining changes:
- Add a simple autopkgtest to the package.
- Build x32 packages.
- Build lib32 packages on s390x.
  * Fix typo in libx32 package descriptions

 -- Julian Andres Klode   Thu, 11 Jan 2018 20:51:25
+0100


** Changed in: ncurses (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Please merge ncurses 6.0+20161126-1 (main) from Debian unstable (main)

Status in ncurses package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu version: 6.0+20160625-1ubuntu1
  Debian verison: 6.0+20161126-1

  Details: https://merges.ubuntu.com/n/ncurses/REPORT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1637239/+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 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

[Dimitri John Ledkov]

yes, but I'm not uploading systemd until after the build-farm is open.

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1743873] [NEW] rsync version for xenial

[Jeff Norden]

Public bug reported:

Any chance that rsync could be updated to 3.1.2 for xenial?

The --backup-dir option in 3.1.1 doesn't work properly - it creates
empty directories even when no files need to be put in them.

Thanks,
-Jeff

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

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

Title:
  rsync version for xenial

Status in rsync package in Ubuntu:
  New

Bug description:
  Any chance that rsync could be updated to 3.1.2 for xenial?

  The --backup-dir option in 3.1.1 doesn't work properly - it creates
  empty directories even when no files need to be put in them.

  Thanks,
  -Jeff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1743873/+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 1089389] Re: juju bootstrap fail behind a proxy when a gpg key must be imported

[Scott Moser]

@Nate,
there is some suggestions about that in bug 1433761.

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

Title:
  juju bootstrap fail behind a proxy when a gpg key must be imported

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  This is related to a Maas environment hosted behind a proxy.

  I'm trying to use 
  juju 0.6.0.1+bzr603-0juju1~precise1

  ubuntu@maas:~$ cat .juju/environments.yaml 
  environments:
mymaas:
  type: maas
  maas-server: 'http://192.168.124.2:80/MAAS'
  maas-oauth: 
'UP5Qay8Nsku8K98fqn:LjhnStY2HjfCeKfvmg:BxA586DWVNPKrT9ASNj9QasMvSPdgavt'
  admin-secret: 'nothing'
  default-series: precise
  juju-origin: ppa

  When juju boostrap, things do not behave as expected on the zookeeper
  node.

  Excerpt from the cloud-init-output.log:

  W: GPG error: http://ppa.launchpad.net precise Release: The following
  signatures couldn't be verified because the public key is not
  available: NO_PUBKEY 376A290EC8068B11

  On the zookeeper node, if i try to apt-add-repository , the needed gpg
  key is not injected, but the scrpit does not return any error code:

  ubuntu@zookeeper:/var/log$ sudo mv 
/etc/apt/sources.list.d/juju-pkgs-precise.list /tmp/
  ubuntu@zookeeper:/var/log$ sudo ls /etc/apt/sources.list.d/
  ubuntu@zookeeper:/var/log$ sudo apt-add-repository ppa:juju/pkgs --yes
  gpg: keyring `/tmp/tmpmlP7VA/secring.gpg' created
  gpg: keyring `/tmp/tmpmlP7VA/pubring.gpg' created
  gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com
  gpgkeys: key A2EB2DEC0BD7519B7B38BE38376A290EC8068B11 not found on keyserver
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  recv failed
  ubuntu@zookeeper:/var/log$ echo $?
  0

  Trying to inject key while setting the http_proxy environment variable works 
better:
  ubuntu@zookeeper:/var/log$ sudo http_proxy=http://91.189.90.174:3128/ 
apt-add-repository ppa:juju/pkgs --yes
  gpg: keyring `/tmp/tmp1pAd6X/secring.gpg' created
  gpg: keyring `/tmp/tmp1pAd6X/pubring.gpg' created
  gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp1pAd6X/trustdb.gpg: trustdb created
  gpg: key C8068B11: public key "Launchpad Ensemble PPA" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  OK
  ubuntu@zookeeper:/var/log$ echo $?
  0

  
  On the zookeeper node,  python-software-properties  is version   0.82.7.3

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: python-software-properties 0.82.7.3
  ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33
  Uname: Linux 3.2.0-34-generic x86_64
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: amd64
  Date: Wed Dec 12 14:40:21 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to precise on 2012-05-14 (212 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1089389/+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 934291] Re: Deleting or stopping print jobs does not work

[Didier Raboud]

@ken-vandine: I'd not name the system user 'lpadmin' but rather 'cups-
pk-helper', which is more precise, especially as its creation/deletion
is handled by the cups-pk-helper maintainer scripts.

Other than that, it looks like a good solution.

That said, only the cups-pk-helper maintainer in Debian (Guido Günther,
see https://tracker.debian.org/pkg/cups-pk-helper) can have a definitive
opinion there.

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Unknown
Status in cups package in Ubuntu:
  Invalid
Status in cups-pk-helper package in Ubuntu:
  In Progress
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+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 1743582] Re: Cannot install libxcomposite-dev:i386 on 64-Bit Ubuntu

[Timo Aaltonen]

again fixed since 17.04

** Changed in: libxcomposite (Ubuntu)
   Status: New => Fix Released

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

Title:
  Cannot install libxcomposite-dev:i386 on 64-Bit Ubuntu

Status in libxcomposite package in Ubuntu:
  Fix Released

Bug description:
  When trying to install libxcomposite-dev:i386 this gives a conflict
  with the installed 64-Bit package:

  The following NEW packages will be installed:
libxcomposite-dev:i386{b}
  0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 9.864 B of archives. After unpacking 76,8 kB will be used.
  The following packages have unmet dependencies:
   libxcomposite-dev : Conflicts: libxcomposite-dev:i386 but 1:0.4.4-1 is to be 
installed.
   libxcomposite-dev:i386 : Conflicts: libxcomposite-dev but 1:0.4.4-1 is 
installed.
   
  This is Ubuntu 16.04
  I expect that the 32-Bit dev-lib can be installed in parallel with their 
64-Bit versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxcomposite/+bug/1743582/+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 1743584] Re: Cannot install libxi-dev:i386 on 64-Bit Ubuntu

[Timo Aaltonen]

this has been fixed since 17.04

** Changed in: libxi (Ubuntu)
   Status: New => Fix Released

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

Title:
  Cannot install libxi-dev:i386 on 64-Bit Ubuntu

Status in libxi package in Ubuntu:
  Fix Released

Bug description:
  When trying to install libxi-dev:i386 this gives a conflict with the
  installed 64-Bit package:

  The following NEW packages will be installed:
libxi-dev:i386{b}
  0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 185 kB of archives. After unpacking 666 kB will be used.
  The following packages have unmet dependencies:
   libxi-dev : Conflicts: libxi-dev:i386 but 2:1.7.6-1 is to be installed.
   libxi-dev:i386 : Conflicts: libxi-dev but 2:1.7.6-1 is installed.

  This is Ubuntu 16.04
  I expect that the 32-Bit dev-lib can be installed in parallel with their 
64-Bit versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxi/+bug/1743584/+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 1421075] Re: Typo with dynamically removing port forward in ssh

[Hans Joachim Desserud]

As mentioned in the upstream bug report, this issue has been fixed in
OpenSSH, and the fix is included in the openssh package (1:7.5p1-10) in
Ubuntu 17.10 and later.

** Changed in: openssh (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Typo with dynamically removing port forward in ssh

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  When using ssh and managing ssh port forwards with ~C to remove a
  forward that doesn't exist, the following occurs:

user@host:~$ 
ssh> -KD12345
Unkown port forwarding.

  ie, the mispelling of the work Unknown as 'Unkown'.

  This occurs at least on a server running on trusty:

  $ dpkg --list | grep openssh
  ii  openssh-client  1:6.6p1-2ubuntu2   
amd64secure shell (SSH) client, for secure access to remote machines
  ii  openssh-server  1:6.6p1-2ubuntu2   
amd64secure shell (SSH) server, for secure access from remote machines
  ii  openssh-sftp-server 1:6.6p1-2ubuntu2   
amd64secure shell (SSH) sftp server module, for SFTP access from remote 
machines

  Please let me know if you need any more information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1421075/+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 1713457] Re: DNS search domain not removed from resolv.conf on disconnect

[BertWesarg]

Thanks. That works.

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

Title:
  DNS search domain not removed from resolv.conf on disconnect

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  When I connect to a wireless network that sets a DNS search domain
  name via DHCP, the line 'search ' is added to /etc/resolv.conf
  as expected.  But if I then disconnect and connect to a different
  network, it is not removed from resolv.conf.  If the second network
  also sets a search domain name, that one gets appended to resolv.conf
  along with the first one, and so on.  Depending on the network, this
  can cause DNS leaks, name resolution failures, or other misbehavior.

  To be sure this wasn't some kind of user configuration issue, I
  reproduced this on the artful daily live image (artful-desktop-
  amd64.iso, 2017-08-27), from which I'm writing this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 10:34:22 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 172.20.20.1 dev wlp3s0 proto static metric 600
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
   172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConnection/2
   enp0s31f6  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1713457/+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 1743773] Re: No sound through headphones

[Sergio Bossa]

I managed make headphones work by reinstalling pulseaudio and alsa, and
shutting down the computer (for any reason just rebooting didn't work).

Now, everything works except I don't hear the "popping" sound when
changing the volume anymore, and "Test Speakers" from Sound Settings
doesn't produce any sound.

Any ideas? Do you want me to change the bug title?

** Summary changed:

- No sound through headphones
+ Audio problems after updating

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

Title:
  Audio problems after updating

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 17.10 and installed today a bunch of updates from
  the software updater. After that, there's no sound from headphones
  anymore, even if they are detected when plugged in and show up in
  sound settings and alsamixer.

  The headphones work on other devices, and the computer speakers work
  too, so the problem seems limited to the headphones output.

  Attached the alsa-info output.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1743773/+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 1734503] Re: In Xfce, Gnome3, Ubuntu Studio, and Mate Desktop the pulse audio gui application is corrupted, I can't switch outputs.

[c_smooth]

I've been Running default flavor of Ubuntu since 12/22 without issue;
still version 16.04.3. I didn't switch to 17 or 18 because I use my
machine for my work, and I do like to run the most stable version. I've
realized that Ubuntu doesn't run simulated 7.1 surround sound well. I
got it working a few years ago with another headset so I thought I could
replicate the same solution with my Astro A40's. It just didn't work.

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

Title:
  In Xfce, Gnome3, Ubuntu Studio, and Mate Desktop the pulse audio gui
  application is corrupted, I can't switch outputs.

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04.3 LTS
  1.8.0
  I expected to be able to switch to different outputs of my sound hardware. 
That list is gone and all I have is a volume circle knob. This doesn't effect 
the cinnamon DE but it does effect Gnome3, Mate, Xfce, and Xfce ubuntu studio 
edition.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.4
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Sat Nov 25 22:12:43 2017
  InstallationDate: Installed on 2017-09-29 (57 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: Z87-M8
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd11/07/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87-M8:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-10-18T18:43:48.348315

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

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

Re: [Touch-packages] [Bug 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Iain Lane]

On Wed, Jan 17, 2018 at 05:05:07PM -, Robie Basak wrote:
> > The problem is that if you upgrade from Xenial to Zesty or (soon)
> Artful and we haven't SRUed the fixes then users could either become
> unfixed or in some cases (didn't check / don't remember for this bug)
> package versions might go backwards.
> 
> Worse, a user may not receive future security updates for the package in
> Artful.

No need to argue, since we SRUed to Artful.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  Fix Released
Status in protobuf package in Ubuntu:
  Fix Released
Status in py-macaroon-bakery package in Ubuntu:
  Fix Released
Status in pymacaroons package in Ubuntu:
  Fix Released
Status in httmock source package in Xenial:
  In Progress
Status in protobuf source package in Xenial:
  In Progress
Status in py-macaroon-bakery source package in Xenial:
  In Progress
Status in pymacaroons source package in Xenial:
  In Progress
Status in httmock source package in Artful:
  Invalid
Status in protobuf source package in Artful:
  Invalid
Status in py-macaroon-bakery source package in Artful:
  In Progress
Status in pymacaroons source package in Artful:
  In Progress

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:

  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.

  [Test case]
  - for protobuf: $ python3 -c "import google.protobuf"
  - for protobuf: $ python2 -c "import google.protobuf"
  - for python3-macaroonbakery: make sure all the tests pass
  - make sure "snapcraft login" works properly

  [Regression Potential]
  - httmock, none has it's not in xenial
  - protobuf, reduced considering that the code has been backported from master 
(small changes to make it compatabile py3 compatabile)
  - pymacaroons, none has 0.12 is backward compatible with 0.9.2
  - py-macaroon-bakery, none has it's not in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/1735160/+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 1743828] [NEW] network-manager-gnome: Consistent segfault when

[Ramin Farajpour Cami]

Public bug reported:

Hi,

nm-applet segfaults every time I attempt to click "connection
information",

root@raminfp:~$ gdb nm-applet
GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from nm-applet...(no debugging symbols found)...done.
(gdb)
(gdb) run
Starting program: /usr/bin/nm-applet
warning: the debug information found in "/lib64/ld-2.26.so" does not match 
"/lib64/ld-linux-x86-64.so.2" (CRC mismatch).

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe878d700 (LWP 13515)]
[New Thread 0x7fffe7f8c700 (LWP 13516)]
[New Thread 0x7fffe734a700 (LWP 13517)]
[New Thread 0x7fffe6b49700 (LWP 13518)]
[New Thread 0x7fffe6348700 (LWP 13519)]

(nm-applet:13510): Gtk-WARNING **: Can't set a parent on widget which has a 
parent
[Thread 0x7fffe6348700 (LWP 13519) exited]
[Thread 0x7fffe6b49700 (LWP 13518) exited]

Thread 1 "nm-applet" received signal SIGSEGV, Segmentation fault.
0x in ?? ()
(gdb) bt
#0  0x in ?? ()
#1  0x74ee5644 in g_hash_table_lookup () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x763d88d0 in gdk_x11_atom_to_xatom_for_display () from 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#3  0x763e7aed in gdk_x11_get_server_time () from 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#4  0x55570cb6 in ?? ()
#5  0x751cff9d in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6  0x751e2cde in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x751eb4b5 in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x751ebecf in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x72ef33dd in ?? () from 
/usr/lib/x86_64-linux-gnu/libdbusmenu-gtk3.so.4
#10 0x751cff9d in g_closure_invoke () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x751e2cde in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x751eb4b5 in g_signal_emit_valist () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x751ebecf in g_signal_emit () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x72cd43ea in dbusmenu_menuitem_handle_event () from 
/usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4
#15 0x72cd5817 in ?? () from 
/usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4
#16 0x74ef78a3 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x74ef6e25 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x74ef71f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x74ef727c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x754b4c4d in g_application_run () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#21 0x55564231 in ?? ()
#22 0x748ce1c1 in __libc_start_main (main=0x55564100, argc=1, 
argv=0x7fffe108, init=, fini=, 
rtld_fini=, stack_end=0x7fffe0f8)
at ../csu/libc-start.c:308
#23 0x5556434a in ?? ()

** Affects: network-manager-applet
 Importance: Undecided
 Status: New

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

** Also affects: network-manager-applet
   Importance: Undecided
   Status: New

** No longer affects: busybox (Ubuntu)

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

Title:
  network-manager-gnome: Consistent segfault when

Status in Network Manager Applet:
  New

Bug description:
  Hi,

  nm-applet segfaults every time I attempt to click "connection
  information",

  root@raminfp:~$ gdb nm-applet
  GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1
  Copyright (C) 2017 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  

[Touch-packages] [Bug 474646] ✈The world's travel search engine Skyscanner compares millions of flights to find you the cheapest deal, fast.

[shanta]

Whether you  want to go to Tenerife or Tokyo,  we'll find  low cost flights  to 
get you there.
We also  find the cheapest  hotels  and car  hire deals.
Just dial: +1 (888) 369-2751.
Skyscanner  is free! When you find your flights and dial  (888) 369-2751, we 
redirect  your call through directly to the airline or  travel agent.We 
never charge you commission. Nor do we add hidden fees. See more ways we put 
you first.
Acclaimed flight comparison Skyscanner  is  an award winning site recommended  
by: The Independent, The Guardian, Which? Travel, BBC Radio 1 and 
more!Skyscanner has  been consistently found to be comprehensive, fast, and 
the best  way to find  cheap flights.
Just dial: +1 (888) 369-2751.
Let’s  get social! Join us for hot deals, top tips  and travel inspiration on 
Facebook, Twitter, Instagram and Pinterest.
Find  the perfect place to stay
The  Trip by Skyscanner community has reviewed tens of thousands of  hotels  
around the world so you can always find the perfect place to stay, based on  
your tribe and your price  range.
Simply select  your destination, dial +1 (888) 369-2751, and you  
are off!
And now Trip by Skyscanner  searches all the top  booking sites to  make sure 
to always find you the lowest price.
Check out some of our most popular destinations:
Chicago-New York$175.12Los Angeles-San Francisco$103.67Los Angeles-New  York$175.24Chicago-Los Angeles$325.45Miami-New York$96.29Atlanta-Chicago$100.64Newark-Toronto$299.39Boston-Miami$189.96San Francisco-New  York City$293.59New York City-Kingston$461.16New York City-Casablanca$825.40Chicago-Minneapolis$95.85Atlanta-New York$225.64Atlanta-Orlando$90.20Chicago-Washington DC$195.45New York City-Paris$545.97New York  City-London$399.46Top Deal 55%  Off:  
Skyscanner's Flight Deals.
Primary: +1 (888) 369-2751.  24/7 Support.
Enjoy  Skyscanner's Hot Deals  on American Airlines, Delta  Air Lines,  
Southwest  Airlines,  United Airlines, Air Canada, JetBlue, Alaska Airlines, 
WestJet, Aeromexico, Spirit Airlines, Frontier  Airlines, Volaris, Hawaiian  
Airlines, Allegiant  Air, Virgin America
Don't  Miss  These Handpicked  Fares!

Primary +1 (888) 369-2751. 24/7 Support

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

Title:
  sound dos not work crackaling noise only

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  This as not worked for some time I have added utills but they don't help.
  New upgrade to the latest version did not help
  If run a game call railroad tycoon the sound dose work. so the card in the 
laptap is ok
  I am running a msi mega book s430x
  AMD Athlon-x2 64

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: ALC883 Analog [ALC883 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shanta 2558 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfebd8000 irq 23'
 Mixer name : 'Realtek ALC883'
 Components : 'HDA:10ec0883,1462373d,0012 
HDA:11c11040,11c10001,00100200'
 Controls  : 23
 Simple ctrls  : 14
  CheckboxCommand: alsa_record_playback
  CheckboxDescription:
   Connect a microphone to your microphone port. Click the Test button, then 
speak into the microphone. After a few seconds, your speech will be played back 
to you.
   
   Did you hear your speech played back?
  CheckboxTest: alsa_record_playback_external
  Date: Wed Nov  4 11:46:10 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: alsa-base 1.0.20+dfsg-1ubuntu5
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_CA.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: alsa-driver
  Tags: checkbox-bug
  Uname: Linux 2.6.31-14-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/474646/+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 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Robie Basak]

> The problem is that if you upgrade from Xenial to Zesty or (soon)
Artful and we haven't SRUed the fixes then users could either become
unfixed or in some cases (didn't check / don't remember for this bug)
package versions might go backwards.

Worse, a user may not receive future security updates for the package in
Artful.

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

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  Fix Released
Status in protobuf package in Ubuntu:
  Fix Released
Status in py-macaroon-bakery package in Ubuntu:
  Fix Released
Status in pymacaroons package in Ubuntu:
  Fix Released
Status in httmock source package in Xenial:
  In Progress
Status in protobuf source package in Xenial:
  In Progress
Status in py-macaroon-bakery source package in Xenial:
  In Progress
Status in pymacaroons source package in Xenial:
  In Progress
Status in httmock source package in Artful:
  Invalid
Status in protobuf source package in Artful:
  Invalid
Status in py-macaroon-bakery source package in Artful:
  In Progress
Status in pymacaroons source package in Artful:
  In Progress

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:

  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.

  [Test case]
  - for protobuf: $ python3 -c "import google.protobuf"
  - for protobuf: $ python2 -c "import google.protobuf"
  - for python3-macaroonbakery: make sure all the tests pass
  - make sure "snapcraft login" works properly

  [Regression Potential]
  - httmock, none has it's not in xenial
  - protobuf, reduced considering that the code has been backported from master 
(small changes to make it compatabile py3 compatabile)
  - pymacaroons, none has 0.12 is backward compatible with 0.9.2
  - py-macaroon-bakery, none has it's not in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/1735160/+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 934291] Re: Deleting or stopping print jobs does not work

[Ken VanDine]

@odyx do you think the patch in comment #53 is suitable for debian?  I'd
like to avoid a delta with debian if possible, so i'll defer sponsoring
this until we have some agreement on the fix.

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Unknown
Status in cups package in Ubuntu:
  Invalid
Status in cups-pk-helper package in Ubuntu:
  In Progress
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+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 1737592] Re: no zfs module in initramfs

[Scott Moser]

closer.
still need artful to be updated. but seems like next build would do that.

$ for f in *-initrd; do echo == $f ==; lsinitramfs $f | grep zfs; done
== artful-20180109-initrd ==
== bionic-20180115.1-initrd ==
lib/modules/4.13.0-25-generic/kernel/zfs
lib/modules/4.13.0-25-generic/kernel/zfs/spl
lib/modules/4.13.0-25-generic/kernel/zfs/spl/spl.ko
lib/modules/4.13.0-25-generic/kernel/zfs/unicode
lib/modules/4.13.0-25-generic/kernel/zfs/unicode/zunicode.ko
lib/modules/4.13.0-25-generic/kernel/zfs/nvpair
lib/modules/4.13.0-25-generic/kernel/zfs/nvpair/znvpair.ko
lib/modules/4.13.0-25-generic/kernel/zfs/zcommon
lib/modules/4.13.0-25-generic/kernel/zfs/zcommon/zcommon.ko
lib/modules/4.13.0-25-generic/kernel/zfs/zfs
lib/modules/4.13.0-25-generic/kernel/zfs/zfs/zfs.ko
lib/modules/4.13.0-25-generic/kernel/zfs/avl
lib/modules/4.13.0-25-generic/kernel/zfs/avl/zavl.ko
== xenial-20180112-initrd ==
lib/modules/4.4.0-109-generic/kernel/zfs
lib/modules/4.4.0-109-generic/kernel/zfs/spl
lib/modules/4.4.0-109-generic/kernel/zfs/spl/spl.ko
lib/modules/4.4.0-109-generic/kernel/zfs/unicode
lib/modules/4.4.0-109-generic/kernel/zfs/unicode/zunicode.ko
lib/modules/4.4.0-109-generic/kernel/zfs/nvpair
lib/modules/4.4.0-109-generic/kernel/zfs/nvpair/znvpair.ko
lib/modules/4.4.0-109-generic/kernel/zfs/zcommon
lib/modules/4.4.0-109-generic/kernel/zfs/zcommon/zcommon.ko
lib/modules/4.4.0-109-generic/kernel/zfs/zfs
lib/modules/4.4.0-109-generic/kernel/zfs/zfs/zfs.ko
lib/modules/4.4.0-109-generic/kernel/zfs/avl
lib/modules/4.4.0-109-generic/kernel/zfs/avl/zavl.ko
== yakkety-20170719.1-initrd ==
== zesty-20171219-initrd ==

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

Title:
  no zfs module in initramfs

Status in maas-images:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  zfs support exists in Ubuntu kernels for 16.04 and later, but the
  default initramfs build does not include this module.

  Other common filesystems are included.

  As a small piece of information:
  $ du -hs /lib/modules/4.13.0-17-generic/kernel/zfs/
  3.2M  /lib/modules/4.13.0-17-generic/kernel/zfs/


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools-core 0.125ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 11 13:05:15 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (872 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1737592/+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 1742301] Re: /usr/bin/software-properties-gtk:UnboundLocalError:show_drivers:gather_device_data

[Brian Murray]

** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  /usr/bin/software-properties-
  gtk:UnboundLocalError:show_drivers:gather_device_data

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
1.92.36bodhi1, the problem page at 
https://errors.ubuntu.com/problem/dbe7741e95ffda0ea64d12522c8f664897773564 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1742301/+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 1516564] Re: Remove 'Ç' key from Portuguese (PT-PT) layout

[Ivo Xavier]

** No longer affects: ubuntu-keyboard

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

Title:
  Remove 'Ç' key from Portuguese (PT-PT) layout

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  Hi,

  The current ubuntu keyboard layout for Portuguese from Portugal
  displays the 'ç' key, which is unnecessary because with a long-press
  in the 'c' key we can get 'ç'.

  Triage: http://bazaar.launchpad.net/~phablet-team/ubuntu-
  keyboard/trunk/view/head:/plugins/pt/qml/Keyboard_pt.qml

  Row {
  anchors.horizontalCenter: parent.horizontalCenter;
  spacing: 0

  CharKey { label: "a"; shifted: "A"; extended: 
["ã","á","à","â","ª","ä","å","æ"]; extendedShifted: 
["Ã","Á","À","Â","ª","Ä","Å","Æ"]; leftSide: true; }
  CharKey { label: "s"; shifted: "S"; extended: ["ß","$"]; 
extendedShifted: ["$"] }
  CharKey { label: "d"; shifted: "D"; extended: ["ð"]; 
extendedShifted: ["Ð"] }
  CharKey { label: "f"; shifted: "F"; }
  CharKey { label: "g"; shifted: "G"; }
  CharKey { label: "h"; shifted: "H"; }
  CharKey { label: "j"; shifted: "J"; }
  CharKey { label: "k"; shifted: "K"; }
  CharKey { label: "l"; shifted: "L"; }
  CharKey { label: "ç"; shifted: "Ç"; rightSide: true; }  <--'ç'
  }

  Row {
  anchors.horizontalCenter: parent.horizontalCenter;
  spacing: 0

  ShiftKey {}
  CharKey { label: "z"; shifted: "Z"; }
  CharKey { label: "x"; shifted: "X"; }
  CharKey { label: "c"; shifted: "C"; extended: ["ç"]; 
extendedShifted: ["Ç"] } <--'ç'
  CharKey { label: "v"; shifted: "V"; }
  CharKey { label: "b"; shifted: "B"; }
  CharKey { label: "n"; shifted: "N"; extended: ["ñ"]; 
extendedShifted: ["Ñ"] }
  CharKey { label: "m"; shifted: "M"; }
  BackspaceKey {}
  }

  
  Even the android/ios doesn't have the 'ç' key, see the attachment.

  It's a bit difficult to handle the current layout with the 'Ç' key.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1516564/+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 1331057] Re: Can't be used to verify current trusty images

[Dimitri John Ledkov]

** Also affects: ubuntu-keyring (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-keyring (Ubuntu)
   Status: New => In Progress

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

Title:
  Can't be used to verify current trusty images

Status in ubuntu-cloudimage-keyring package in Ubuntu:
  Confirmed
Status in ubuntu-keyring package in Ubuntu:
  In Progress

Bug description:
  The description of this package says "This package contains the keys
  used for files on cloud-images.ubuntu.com." However, the checksum
  files are signed with keyid 7DB87C81, which I can't find in this
  package.

  ubuntu@server-46af3152-8a83-4995-8dfb-e3b2d07e0841:~$ wget 
http://cloud-images.ubuntu.com/trusty/current/SHA256SUMS 
http://cloud-images.ubuntu.com/trusty/current/SHA256SUMS.gpg
  ubuntu@server-46af3152-8a83-4995-8dfb-e3b2d07e0841:~$ gpg --verify 
SHA256SUMS.gpg SHA256SUMS
  gpg: Signature made Sat 14 Jun 2014 01:03:39 PM UTC using RSA key ID 7DB87C81
  gpg: Can't check signature: public key not found
  ubuntu@server-46af3152-8a83-4995-8dfb-e3b2d07e0841:~$ gpg --keyring 
/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg 
--list-keys/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg
  -
  pub   4096R/476CF100 2012-10-27
  uid  Ubuntu Cloud Image Builder (Canonical Internal Cloud 
Image Builder) 
  sub   4096R/9D817405 2012-10-27

  ubuntu@server-46af3152-8a83-4995-8dfb-e3b2d07e0841:~$ dpkg -l 
ubuntu-cloudimage-keyring
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-p 
end
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   VersionArchitecture   
Description
  
+++-==-==-==-=
  ii  ubuntu-cloudimage-keyring  2013.11.11 allGnuPG 
keys of the Ubuntu Cloud Image builder

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-cloudimage-keyring/+bug/1331057/+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 1465266] Re: [xorg-edgers] lowering brightness with hotkeys causes it to drop to the minimum and stay minimal

[Karl-Philipp Richter]

This can be fixed by adding `acpi_backlight=vendor` to the `linux`
stanza  in `grub.cfg` which is effectively done by adding it to
`GRUB_CMDLINE_LINUX_DEFAULT` in `/etc/default/grub` in Ubuntu 17.10 or
possibly earlier.

I'm leaving this open in order to suggest improvement of automatic
handling of this issue.

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

Title:
  [xorg-edgers] lowering brightness with hotkeys causes it to drop to
  the minimum and stay minimal

Status in xorg package in Ubuntu:
  New

Bug description:
  The setting persists over reboot and the brightness needs to be set in
  the bootloader (e.g. `grub`).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  Uname: Linux 4.1.0-040100rc7-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: »/apps/compiz-1/general/screen0/options/active_plugins« wurde 
kein Wert zugewiesen
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Jun 15 14:16:20 2015
  DistUpgraded: 2015-06-09 11:26:48,626 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3904]
  InstallationDate: Installed on 2015-06-08 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20221
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-040100rc7-generic 
root=UUID=b7cf2463-f723-4ad2-bcc0-ebecb1842908 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to vivid on 2015-06-09 (6 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.61+git20150614.97be70b4-0ubuntu0ricotz~vivid
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.6.0~git20150614+10.6.9dc43dc3-0ubuntu0ricotz~vivid
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.6.0~git20150614+10.6.9dc43dc3-0ubuntu0ricotz~vivid
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.99+git20150521.d64a13eb-0ubuntu0ricotz~vivid
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150528.fb1643f0-0ubuntu0sarvatt~vivid
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Jun 15 14:14:01 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5557 
   vendor CMN
  xserver.version: 2:1.17.1-0ubuntu3
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: »/apps/compiz-1/general/screen0/options/active_plugins« wurde 
kein Wert zugewiesen
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3904]
  InstallationDate: Installed on 2015-12-12 (57 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20221
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-040400-generic 
root=UUID=791b47e7-

[Touch-packages] [Bug 1743401] Re: AddressSanitizer: heap-buffer-overflow in libxkbcommon-x11.so

[Oliver Stöneberg]

Sorry I didn't think about this before, but I gave the non-ASAN version
of the application a spin with valgrind 3.13 and it doesn't report any
memory errors with it - so it's possible this is either something
valgrind won't catch or a false positive by ASAN.

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

Title:
  AddressSanitizer: heap-buffer-overflow in libxkbcommon-x11.so

Status in libxkbcommon package in Ubuntu:
  New

Bug description:
  I am running an application which has a feature which utilizes Qt5. For 
testing purposes this application was built with the AddressSanitizer of the 
official clang 5.0.1 binariesfor ubuntu 16.04. This was working fine until a 
few days ago. It started out with another user reporting issues with Qt and the 
pt_BR.UTF-8 locale which I was able to confirm after I installed it. Shorty 
after that I was no longer able to run anything that used the Qt code. I tried 
removing the additional locale or setting a different one via the environment, 
but that didn't help. I also did some changes in the "Text Input" settings like 
removing removing the "English" keyboard layout before I encountered this.
  Unfortunately I didn't have the time yet to set the system back up from 
scratch and try to reproduce what exact change caused this.

  Below I added the traces of ASAN and the debugger.

  The code in question is found in xkbcommon/src/x11/util.c

  length = xcb_get_atom_name_name_length(reply);
  name = xcb_get_atom_name_name(reply);

  *out = strndup(name, length);

  Unfortunately I was not able to see what "name" is, but length was 8.

  lsb_release -rd
  Description:Ubuntu 16.04.3 LTS
  Release:16.04

  libxkbcommon0:
Installed: 0.5.0-1ubuntu2
Candidate: 0.5.0-1ubuntu2
Version table:
   *** 0.5.0-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  qt5-default:
Installed: 5.5.1+dfsg-16ubuntu7.5
Candidate: 5.5.1+dfsg-16ubuntu7.5
Version table:
   *** 5.5.1+dfsg-16ubuntu7.5 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   5.5.1+dfsg-16ubuntu7 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  locale
  LANG=en_US.UTF-8
  LANGUAGE=
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC=de_DE.UTF-8
  LC_TIME=de_DE.UTF-8
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY=de_DE.UTF-8
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER=de_DE.UTF-8
  LC_NAME=de_DE.UTF-8
  LC_ADDRESS=de_DE.UTF-8
  LC_TELEPHONE=de_DE.UTF-8
  LC_MEASUREMENT=de_DE.UTF-8
  LC_IDENTIFICATION=de_DE.UTF-8
  LC_ALL=

  ==3008==ERROR: AddressSanitizer: heap-buffer-overflow on address 
0x60400015c4b8 at pc 0x01445853 bp 0x7ffd07632920 sp 0x7ffd076320b8
  READ of size 9 at 0x60400015c4b8 thread T0
  #0 0x1445852 in __interceptor___strndup 
/opt/media/clang_nightly/llvm/utils/release/final/llvm.src/projects/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:337:3
  #1 0x7fc1481fd70e  
(/usr/lib/x86_64-linux-gnu/libxkbcommon-x11.so.0+0x470e)
  #2 0x7fc1481fcd79 in xkb_x11_keymap_new_from_device 
(/usr/lib/x86_64-linux-gnu/libxkbcommon-x11.so.0+0x3d79)
  #3 0x7fc149cb9c8f  (/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5+0x42c8f)
  #4 0x7fc149cba0ec  (/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5+0x430ec)
  #5 0x7fc149cb4931 in QXcbConnection::QXcbConnection(QXcbNativeInterface*, 
bool, unsigned int, char const*) 
(/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5+0x3d931)
  #6 0x7fc149cb7bac in QXcbIntegration::QXcbIntegration(QStringList const&, 
int&, char**) (/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5+0x40bac)
  #7 0x7fc149d773ac in _init 
(/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so+0x13ac)
  #8 0x7fc179728d91 in QPlatformIntegrationFactory::create(QString const&, 
QStringList const&, int&, char**, QString const&) 
(/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5+0xdfd91)
  #9 0x7fc179734fc3 in QGuiApplicationPrivate::createPlatformIntegration() 
(/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5+0xebfc3)
  #10 0x7fc179735ecc in QGuiApplicationPrivate::createEventDispatcher() 
(/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5+0xececc)
  #11 0x7fc1793fd7e5 in QCoreApplication::init() 
(/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x28a7e5)
  #12 0x7fc1793fd855 in 
QCoreApplication::QCoreApplication(QCoreApplicationPrivate&) 
(/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x28a855)
  #13 0x7fc179737cc8 in 
QGuiApplication::QGuiApplication(QGuiApplicationPrivate&) 
(/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5+0xeecc8)
  #14 0x7fc179ceebcc in QApplication::QApplication(int&, char**, int) 
(/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x15dbcc)
  #15 0x8c7f4e5 in debug_qt::init_debugger(running_machine&) 
/mnt/mame/

[Touch-packages] [Bug 1739948] Re: Missing French-Belgian keyboard layout

[Baudouin]

I could find the missing keyboard layout by typing this in the terminal:
gsettings set org.gnome.desktop.input-sources show-all-sources true

I think it would be a good idea to add a button to show more layout...
or at least to document how to proceed to get those additional layout

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

Title:
  Missing French-Belgian keyboard layout

Status in ibus package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 17.10
  Release:  17.10

  ibus:
Installed: 1.5.14-2ubuntu1
Candidate: 1.5.14-2ubuntu1
Version table:
   *** 1.5.14-2ubuntu1 500
  500 http://be.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  After my update on 17.10 I couldn't get a french Belgian keyboard in the 
input sources.
  During install time I have tried to find my keyboard layout by using the 
"Type this key process" without success.
  I have also tried all the French keyboard but none of them allow me to type 
"@" or "-"... sut to mention main missing keys.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1739948/+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 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 17.2.4-0ubuntu1~17.10.2

---
mesa (17.2.4-0ubuntu1~17.10.2) artful; urgency=medium

  * i965-disable-l3-cache-alloc-for-ext-buffers.diff:
- Replaced with five backported commits from upstream
  (LP: #1727401, #1735594)

mesa (17.2.4-0ubuntu1~17.10.1) artful; urgency=medium

  * Backport to artful.
  * vulkan-mir.patch: Dropped, breaks radeon vulkan driver. (LP:
#1720890)

mesa (17.2.4-0ubuntu1) bionic; urgency=medium

  * New upstream bugfix release. (LP: #1727390)
  * i965-disable-l3-cache-alloc-for-ext-buffers.diff: Fix corruption
running windowed 3D apps on dGPU. (LP: #1727401)

 -- Timo Aaltonen   Tue, 09 Jan 2018 15:28:48 +0200

** Changed in: mesa (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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1720890

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1720890/+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 1727401] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for mesa has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 17.2.4-0ubuntu1~16.04.4

---
mesa (17.2.4-0ubuntu1~16.04.4) xenial; urgency=medium

  * control: Relax mesa-opencl-icd dependency on libclc. (LP: #1743018)

mesa (17.2.4-0ubuntu1~16.04.3) xenial; urgency=medium

  * i965-disable-l3-cache-alloc-for-ext-buffers.diff:
- Replaced with five backported commits from upstream
  (LP: #1727401, #1735594)

 -- Timo Aaltonen   Sat, 13 Jan 2018 09:06:08 +0200

** Changed in: mesa (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 17.2.4-0ubuntu1~17.10.2

---
mesa (17.2.4-0ubuntu1~17.10.2) artful; urgency=medium

  * i965-disable-l3-cache-alloc-for-ext-buffers.diff:
- Replaced with five backported commits from upstream
  (LP: #1727401, #1735594)

mesa (17.2.4-0ubuntu1~17.10.1) artful; urgency=medium

  * Backport to artful.
  * vulkan-mir.patch: Dropped, breaks radeon vulkan driver. (LP:
#1720890)

mesa (17.2.4-0ubuntu1) bionic; urgency=medium

  * New upstream bugfix release. (LP: #1727390)
  * i965-disable-l3-cache-alloc-for-ext-buffers.diff: Fix corruption
running windowed 3D apps on dGPU. (LP: #1727401)

 -- Timo Aaltonen   Tue, 09 Jan 2018 15:28:48 +0200

** Changed in: mesa (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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1727401

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+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 1727390] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for mesa has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  New bugfix release 17.2.4

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]

  A new upstream bugfix release is available. Release note diff compared
  to 17.2.2:

  "Mesa 17.2.3 is now available.

  In this release we have:

  The Vulkan drivers ANV and RADV have multiple small fixes.

  The EGL code has improved handling of the new wl_dmabuf codepath.

  SWR no longer crashes when checking environment variables.

  Other gallium drivers have also seen updates - freedreno, nouveau and
  radeonsi. The gallivm module, used by llvmpipe et al. has gained little
  endian PPC64 fixes.

  The VA and VDPAU state-trackers have seems improvements handling
  interlaced videos.

  We're using python3 compatible constructs which gives us SCons 3.0
  support."

  "Mesa 17.2.4 is now available.

  In this release we have:

  In Mesa Core we have included a change to prevent KOTOR from breaking
  when in combination with the ATI fragment shader extension. 
  Additionally, NIR has also received a correction.

  Mesa's state tracker has gotten a patch to avoid leaks in certain
  situations like when resizing a window.

  Intel drivers have received several fixes.  The compiler has gotten a
  couple, while anv also received one.  i965 got a patch to avoid VA-
  API, Beignet and other contexts in the system to break when in
  combination with previous versions of Mesa 17.2.x.

  AMD's compiler has received a couple of fixes while radv has also
  received another couple, including one to avoid a hang due to an
  overflow on huge textures.

  Broadcom's vc4 has corrected a problem when compiling with Android's
  clang.

  clover has also seen fixed a problem compiling after a specific clang
  revision.

  Vulkan's WSI has gotten plugged a memory leak for X11."

  
  [Test case]

  Test typical use cases on the most common hw/driver combinations:
  intel/i965
  nvidia/nouveau
  radeon/radeonsi

  [Regression potential]

  These releases are tested against compliance, bugfix releases in
  particular have minimal risk of regressing anything major at least.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+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 1727390] Re: New bugfix release 17.2.4

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 17.2.4-0ubuntu1~17.10.2

---
mesa (17.2.4-0ubuntu1~17.10.2) artful; urgency=medium

  * i965-disable-l3-cache-alloc-for-ext-buffers.diff:
- Replaced with five backported commits from upstream
  (LP: #1727401, #1735594)

mesa (17.2.4-0ubuntu1~17.10.1) artful; urgency=medium

  * Backport to artful.
  * vulkan-mir.patch: Dropped, breaks radeon vulkan driver. (LP:
#1720890)

mesa (17.2.4-0ubuntu1) bionic; urgency=medium

  * New upstream bugfix release. (LP: #1727390)
  * i965-disable-l3-cache-alloc-for-ext-buffers.diff: Fix corruption
running windowed 3D apps on dGPU. (LP: #1727401)

 -- Timo Aaltonen   Tue, 09 Jan 2018 15:28:48 +0200

** Changed in: mesa (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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1727390

Title:
  New bugfix release 17.2.4

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]

  A new upstream bugfix release is available. Release note diff compared
  to 17.2.2:

  "Mesa 17.2.3 is now available.

  In this release we have:

  The Vulkan drivers ANV and RADV have multiple small fixes.

  The EGL code has improved handling of the new wl_dmabuf codepath.

  SWR no longer crashes when checking environment variables.

  Other gallium drivers have also seen updates - freedreno, nouveau and
  radeonsi. The gallivm module, used by llvmpipe et al. has gained little
  endian PPC64 fixes.

  The VA and VDPAU state-trackers have seems improvements handling
  interlaced videos.

  We're using python3 compatible constructs which gives us SCons 3.0
  support."

  "Mesa 17.2.4 is now available.

  In this release we have:

  In Mesa Core we have included a change to prevent KOTOR from breaking
  when in combination with the ATI fragment shader extension. 
  Additionally, NIR has also received a correction.

  Mesa's state tracker has gotten a patch to avoid leaks in certain
  situations like when resizing a window.

  Intel drivers have received several fixes.  The compiler has gotten a
  couple, while anv also received one.  i965 got a patch to avoid VA-
  API, Beignet and other contexts in the system to break when in
  combination with previous versions of Mesa 17.2.x.

  AMD's compiler has received a couple of fixes while radv has also
  received another couple, including one to avoid a hang due to an
  overflow on huge textures.

  Broadcom's vc4 has corrected a problem when compiling with Android's
  clang.

  clover has also seen fixed a problem compiling after a specific clang
  revision.

  Vulkan's WSI has gotten plugged a memory leak for X11."

  
  [Test case]

  Test typical use cases on the most common hw/driver combinations:
  intel/i965
  nvidia/nouveau
  radeon/radeonsi

  [Regression potential]

  These releases are tested against compliance, bugfix releases in
  particular have minimal risk of regressing anything major at least.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+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 1720890] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for mesa has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1720890/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 17.2.4-0ubuntu1~16.04.4

---
mesa (17.2.4-0ubuntu1~16.04.4) xenial; urgency=medium

  * control: Relax mesa-opencl-icd dependency on libclc. (LP: #1743018)

mesa (17.2.4-0ubuntu1~16.04.3) xenial; urgency=medium

  * i965-disable-l3-cache-alloc-for-ext-buffers.diff:
- Replaced with five backported commits from upstream
  (LP: #1727401, #1735594)

 -- Timo Aaltonen   Sat, 13 Jan 2018 09:06:08 +0200

** Changed in: mesa (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1735594] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for mesa has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 17.2.4-0ubuntu1~17.10.2

---
mesa (17.2.4-0ubuntu1~17.10.2) artful; urgency=medium

  * i965-disable-l3-cache-alloc-for-ext-buffers.diff:
- Replaced with five backported commits from upstream
  (LP: #1727401, #1735594)

mesa (17.2.4-0ubuntu1~17.10.1) artful; urgency=medium

  * Backport to artful.
  * vulkan-mir.patch: Dropped, breaks radeon vulkan driver. (LP:
#1720890)

mesa (17.2.4-0ubuntu1) bionic; urgency=medium

  * New upstream bugfix release. (LP: #1727390)
  * i965-disable-l3-cache-alloc-for-ext-buffers.diff: Fix corruption
running windowed 3D apps on dGPU. (LP: #1727401)

 -- Timo Aaltonen   Tue, 09 Jan 2018 15:28:48 +0200

** Changed in: mesa (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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1735594

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1743018] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for mesa has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Unable to install mesa-opencl-icd because of unmet dependencies on
  Xenial

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Xenial:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 16.04 LTS
  2. Try to install `mesa-opencl-icd` with

  $ sudo apt-get install mesa-opencl-icd
  [sudo] password for user: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done

  
  Expected results:
  * mesa-opencl-icd is installed successfully

  Actual results:
  * got errors as follow

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

  The following packages have unmet dependencies:
   mesa-opencl-icd : Depends: libclc-r600 (>= 0.2.0+git20170330-3) but it is 
not going to be installed
 Depends: libclc-amdgcn (>= 0.2.0+git20170330-3) but it is 
not going to be installed
  E: Unable to correct problems, you have held broken packages.

  
  Note: inspired by this AskUbuntu question - 
https://askubuntu.com/q/995274/66509 .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mesa-opencl-icd (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,mousepoll,move,gnomecompat,wall,regex,place,resize,snap,session,imgpng,vpswitch,grid,unitymtgrabhandles,animation,expo,workarounds,ezoom,staticswitcher,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Jan 12 21:22:22 2018
  DistUpgraded: 2017-04-16 02:19:02,541 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:2135]
  InstallationDate: Installed on 2014-02-07 (1434 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=1e3c78e2-1a6e-4afe-8249-40fe7fa81a86 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to xenial on 2017-04-15 (271 days ago)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Jan 12 20:32:41 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: intel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1743

[Touch-packages] [Bug 1743018] Re: Unable to install mesa-opencl-icd because of unmet dependencies on Xenial

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 17.2.4-0ubuntu1~16.04.4

---
mesa (17.2.4-0ubuntu1~16.04.4) xenial; urgency=medium

  * control: Relax mesa-opencl-icd dependency on libclc. (LP: #1743018)

mesa (17.2.4-0ubuntu1~16.04.3) xenial; urgency=medium

  * i965-disable-l3-cache-alloc-for-ext-buffers.diff:
- Replaced with five backported commits from upstream
  (LP: #1727401, #1735594)

 -- Timo Aaltonen   Sat, 13 Jan 2018 09:06:08 +0200

** Changed in: mesa (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Unable to install mesa-opencl-icd because of unmet dependencies on
  Xenial

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Xenial:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 16.04 LTS
  2. Try to install `mesa-opencl-icd` with

  $ sudo apt-get install mesa-opencl-icd
  [sudo] password for user: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done

  
  Expected results:
  * mesa-opencl-icd is installed successfully

  Actual results:
  * got errors as follow

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

  The following packages have unmet dependencies:
   mesa-opencl-icd : Depends: libclc-r600 (>= 0.2.0+git20170330-3) but it is 
not going to be installed
 Depends: libclc-amdgcn (>= 0.2.0+git20170330-3) but it is 
not going to be installed
  E: Unable to correct problems, you have held broken packages.

  
  Note: inspired by this AskUbuntu question - 
https://askubuntu.com/q/995274/66509 .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mesa-opencl-icd (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,mousepoll,move,gnomecompat,wall,regex,place,resize,snap,session,imgpng,vpswitch,grid,unitymtgrabhandles,animation,expo,workarounds,ezoom,staticswitcher,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Jan 12 21:22:22 2018
  DistUpgraded: 2017-04-16 02:19:02,541 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:2135]
  InstallationDate: Installed on 2014-02-07 (1434 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=1e3c78e2-1a6e-4afe-8249-40fe7fa81a86 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to xenial on 2017-04-15 (271 days ago)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Jan 12 20:32:41 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: intel

To manage notificat

[Touch-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

[Timo Aaltonen]

i've tested artful too, marking verified

** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1720890/+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 1727390] Re: New bugfix release 17.2.4

[Timo Aaltonen]

artful works fine still

** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful

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

Title:
  New bugfix release 17.2.4

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  A new upstream bugfix release is available. Release note diff compared
  to 17.2.2:

  "Mesa 17.2.3 is now available.

  In this release we have:

  The Vulkan drivers ANV and RADV have multiple small fixes.

  The EGL code has improved handling of the new wl_dmabuf codepath.

  SWR no longer crashes when checking environment variables.

  Other gallium drivers have also seen updates - freedreno, nouveau and
  radeonsi. The gallivm module, used by llvmpipe et al. has gained little
  endian PPC64 fixes.

  The VA and VDPAU state-trackers have seems improvements handling
  interlaced videos.

  We're using python3 compatible constructs which gives us SCons 3.0
  support."

  "Mesa 17.2.4 is now available.

  In this release we have:

  In Mesa Core we have included a change to prevent KOTOR from breaking
  when in combination with the ATI fragment shader extension. 
  Additionally, NIR has also received a correction.

  Mesa's state tracker has gotten a patch to avoid leaks in certain
  situations like when resizing a window.

  Intel drivers have received several fixes.  The compiler has gotten a
  couple, while anv also received one.  i965 got a patch to avoid VA-
  API, Beignet and other contexts in the system to break when in
  combination with previous versions of Mesa 17.2.x.

  AMD's compiler has received a couple of fixes while radv has also
  received another couple, including one to avoid a hang due to an
  overflow on huge textures.

  Broadcom's vc4 has corrected a problem when compiling with Android's
  clang.

  clover has also seen fixed a problem compiling after a specific clang
  revision.

  Vulkan's WSI has gotten plugged a memory leak for X11."

  
  [Test case]

  Test typical use cases on the most common hw/driver combinations:
  intel/i965
  nvidia/nouveau
  radeon/radeonsi

  [Regression potential]

  These releases are tested against compliance, bugfix releases in
  particular have minimal risk of regressing anything major at least.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+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 1743797] [NEW] Xorg not recognizing AMD graphics card

[Greta Regan]

Public bug reported:

A few months after upgrading to Ubuntu 16.04, my graphics card stopped
working. I got a black screen after booting. I was able to work around
that problem, and then around the problem of losing my external display
when I closed my laptop lid, so I can now boot normally and have only
one problem - I still only have software rendering, which isn't up to
the job.

I checked my graphics card and it was on the list of fully supported
versions. I found work-arounds online for my other problems, but no way
to fix this one, which results in choppy video with audio out of sync.

I trust the apport report which should be attached will give you the
specs you need.

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.15
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: Wed Jan 17 10:15:32 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV515/M52 [Mobility Radeon X1300] 
[1002:714a] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company RV515/M52 [Mobility Radeon X1300] 
[103c:30ac]
InstallationDate: Installed on 2014-04-10 (1378 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
MachineType: Hewlett-Packard HP Compaq nc6400 (RB523UA#ABA)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=123f436f-0331-4097-8a8e-54cc927298c4 ro radeon.modeset=0
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2006
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68YCD Ver. F.08
dmi.board.name: 30AC
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 56.34
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YCDVer.F.08:bd12/18/2006:svnHewlett-Packard:pnHPCompaqnc6400(RB523UA#ABA):pvrF.08:rvnHewlett-Packard:rn30AC:rvrKBCVersion56.34:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq nc6400 (RB523UA#ABA)
dmi.product.version: F.08
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Jan 17 08:23:08 2018
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.7

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

Title:
  Xorg not recognizing AMD graphics card

Status in xorg package in Ubuntu:
  New

Bug description:
  A few months after upgrading to Ubuntu 16.04, my graphics card stopped
  working. I got a black screen after booting. I was able to work around
  that problem, and then around the problem of losing my external
  display when I closed my laptop lid, so I can now boot normally and
  have only one problem - I still only have software rendering, which
  isn't up to the job.

  I checked my graphics card and it was on the list of fully supported
  versions. I found work-arounds online for my other problems, but no
  way to fix this one, which results in choppy video with audio out of
  sync.

  I trust the apport report which should be attached will give you the
  specs you need.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.

[Touch-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Robie Basak]

I see pulseaudio in the SRU queue for stable releases. But this bug
doesn't appear to be fixed in Bionic yet, and AFAICT you have tried
multiple times to fix it in Bionic so it isn't clear to me that the
uploads for the stable releases are still current.

Please confirm what you want doing with the existing stable uploads in
their queues, and please make sure the bug is Fix Released (and
confirmed fixed) in Bionic before uploading anything more to the stables
to avoid confusion.

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  New
Status in pulseaudio source package in Artful:
  New

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

[Scott Moser]

Hi,

I'm coming here from bug 1730744.
Is this bug expected to be fixed for 18.04?

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1686618] Re: ssh connection attempts fail if hw crypto support on s390x is enabled on 17.04

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2018-01-17 08:56 EDT---
IBM Bugzilla status -> closed, Fix Released by Canonical.

** Tags removed: verification-failed

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

Title:
  ssh connection attempts fail if hw crypto support on s390x is enabled
  on 17.04

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Zesty:
  Invalid
Status in openssh source package in Artful:
  Fix Released

Bug description:
  [ Impact ]

  * Unable to ssh into Ubuntu, using default sshd configuration, when hw
  acceleration is enabled in openssl.

  [ Proposed solution ]

  * Cherrypick upstream fixes for:
- sandboxing code on big endian
- allowing hw accel iocls in the sandbox

  short:
  after investigations the following commits are needed by openssh-server 
version 7.4p1 that is part of 17.04:
  - 5f1596e11d55539678c41f68aed358628d33d86f
  - 9e96b41682aed793fadbea5ccd472f862179fb02
  on master branch in https://github.com/openssh/openssh-portable
  that belong to openssh 7.5 release notes statement: "sshd(8): Avoid sandbox 
errors for Linux S390 systems using an ICA crypto coprocessor."
  __

  [Test case]

  long:

  enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  sudo apt-get install openssl-ibmca libica-utils libica2
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' /etc/ssl/openssl.cnf
  sudo sed -i '10i openssl_cnf = openssl_def' /etc/ssl/openssl.cnf

  afterwards ssh login attempts fail:
  $ ssh ubuntu@zlin42
  ubuntu@zlin42's password:
  Connection to zlin42 closed by remote host.
  Connection to zlin42 closed.

  the normal logs don't provide any interesting details:

  mit log:
    Apr 24 12:37:52 zlin42 kernel: [933567.994312] audit: type=1326 
audit(1493051872.112:29): auid=4294967295 uid=107 gid=65534 ses=4294967295 
pid=25105 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=8016 syscall=201 
compat=0 ip=0x3ffb8a3fb32 code=0x0

  Verbose:
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /home/fheimes/.ssh/config
  debug1: /home/fheimes/.ssh/config line 6: Deprecated option "useroaming"
  debug1: /home/fheimes/.ssh/config line 7: Applying options for *
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to 10.245.208.7 [10.245.208.7] port 22.
  debug1: Connection established.
  debug1: identity file /home/fheimes/.ssh/id_rsa type 1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 
Ubuntu-10
  debug1: match: OpenSSH_7.4p1 Ubuntu-10 pat OpenSSH* compat 0x0400
  debug1: Authenticating to 10.245.208.7:22 as 'ubuntu'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:ss9j12+jMMKL9u2vxNeb3XjOeH0E9lw24IG5LxUeJXk
  debug1: Host '10.245.208.7' is known and matches the ECDSA host key.
  debug1: Found key in /home/fheimes/.ssh/known_hosts:87
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS received
  debug1: SSH2_MSG_EXT_INFO received
  debug1: kex_input_ext_info: 
server-sig-algs=
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: publickey,password

[Touch-packages] [Bug 1731417] Re: Installed network printer removed automatically when turned off

[Alberto Donato]

Updated the bug title, as it's not really related to suspend/resume

** Summary changed:

- Installed printer removed after suspend/resume
+ Installed network printer removed automatically when turned off

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

Title:
  Installed network printer removed automatically when turned off

Status in cups package in Ubuntu:
  Confirmed
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  After installing artful, I configured my HP LaserJet M1212nf via network as 
usual via hp-setup.
  Installation worked and I could print/scan via network, but next time I 
needed to print, the printer was gone from the system.
  Basically, every time I need to print, I have to install the printer again.
  I'm not sure when the printer disappears, but I can reproduce consistently.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hplip-gui 3.17.7+repack0-3
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: GNOME
  Date: Fri Nov 10 09:33:12 2017
  InstallationDate: Installed on 2017-07-30 (102 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170730)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed 
root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F15
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+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 1686618] Re: ssh connection attempts fail if hw crypto support on s390x is enabled on 17.04

[Frank Heimes]

closing this ticket - since Zesty ran out of support on Jan the 13th:
https://www.google.de/url?https://lists.ubuntu.com/archives/ubuntu-announce/2018-January/000227.html
and kernel 4.10 is no longer supported.
Even on Xenial we moved the HWE kernel already from 4.10 to 4.13 

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

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Released

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

Title:
  ssh connection attempts fail if hw crypto support on s390x is enabled
  on 17.04

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Zesty:
  Invalid
Status in openssh source package in Artful:
  Fix Released

Bug description:
  [ Impact ]

  * Unable to ssh into Ubuntu, using default sshd configuration, when hw
  acceleration is enabled in openssl.

  [ Proposed solution ]

  * Cherrypick upstream fixes for:
- sandboxing code on big endian
- allowing hw accel iocls in the sandbox

  short:
  after investigations the following commits are needed by openssh-server 
version 7.4p1 that is part of 17.04:
  - 5f1596e11d55539678c41f68aed358628d33d86f
  - 9e96b41682aed793fadbea5ccd472f862179fb02
  on master branch in https://github.com/openssh/openssh-portable
  that belong to openssh 7.5 release notes statement: "sshd(8): Avoid sandbox 
errors for Linux S390 systems using an ICA crypto coprocessor."
  __

  [Test case]

  long:

  enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  sudo apt-get install openssl-ibmca libica-utils libica2
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' /etc/ssl/openssl.cnf
  sudo sed -i '10i openssl_cnf = openssl_def' /etc/ssl/openssl.cnf

  afterwards ssh login attempts fail:
  $ ssh ubuntu@zlin42
  ubuntu@zlin42's password:
  Connection to zlin42 closed by remote host.
  Connection to zlin42 closed.

  the normal logs don't provide any interesting details:

  mit log:
    Apr 24 12:37:52 zlin42 kernel: [933567.994312] audit: type=1326 
audit(1493051872.112:29): auid=4294967295 uid=107 gid=65534 ses=4294967295 
pid=25105 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=8016 syscall=201 
compat=0 ip=0x3ffb8a3fb32 code=0x0

  Verbose:
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /home/fheimes/.ssh/config
  debug1: /home/fheimes/.ssh/config line 6: Deprecated option "useroaming"
  debug1: /home/fheimes/.ssh/config line 7: Applying options for *
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to 10.245.208.7 [10.245.208.7] port 22.
  debug1: Connection established.
  debug1: identity file /home/fheimes/.ssh/id_rsa type 1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 
Ubuntu-10
  debug1: match: OpenSSH_7.4p1 Ubuntu-10 pat OpenSSH* compat 0x0400
  debug1: Authenticating to 10.245.208.7:22 as 'ubuntu'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:ss9j12+jMMKL9u2vxNeb3XjOeH0E9lw24IG5LxUeJXk
  debug1: Host '10.245.208.7' is known and matches the ECDSA host key.
  debug1: Found key in /home/fheimes/.ssh/known_hosts:87
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: reke

[Touch-packages] [Bug 1743773] [NEW] No sound through headphones

[Sergio Bossa]

Public bug reported:

I'm running Ubuntu 17.10 and installed today a bunch of updates from the
software updater. After that, there's no sound from headphones anymore,
even if they are detected when plugged in and show up in sound settings
and alsamixer.

The headphones work on other devices, and the computer speakers work
too, so the problem seems limited to the headphones output.

Attached the alsa-info output.

Thanks.

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

** Attachment added: "alsa-info.txt.QStkGNvyGE"
   
https://bugs.launchpad.net/bugs/1743773/+attachment/5038209/+files/alsa-info.txt.QStkGNvyGE

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

Title:
  No sound through headphones

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 17.10 and installed today a bunch of updates from
  the software updater. After that, there's no sound from headphones
  anymore, even if they are detected when plugged in and show up in
  sound settings and alsamixer.

  The headphones work on other devices, and the computer speakers work
  too, so the problem seems limited to the headphones output.

  Attached the alsa-info output.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1743773/+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 1727237] Re: systemd-resolved is not finding a domain

[Axel]

I would like to test it here with our public company-network that uses
securelogin.arubanetworks.com.

However, I run 17.10 on my laptop and installing the whole new systemd
235 from Bionic is not so straightforward I experienced. I gave up with
too many unfulfilled dependencies.

So could you give me instructions how to load this patch into Artful?

Thank you in advance.

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Zesty:
  Confirmed
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  
  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$ 

  
  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  
  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+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 1743767] Re: Mouse click does not work

[Leo Treasure]

** Description changed:

  moving mouse is fine, clicking does nothing. Just upgraded some packages
  in 17.10
+ 
+ in the /var/log/Xorg.0.log:
+ 
+ config/udev: Adding input device Logitech G Pro Gaming Mouse 
(/dev/input/mouse0)
+ no input driver specified , ignoring this device
+ 
+ I wrote that out as I can't copy paste without clicking.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.15.0-041500rc3-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 20:35:20 2018
  DistUpgraded: 2017-12-18 13:27:58,717 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] [1002:687f] 
(rev c0) (prog-if 00 [VGA controller])
-Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] 
[1002:6b76]
+  Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] [1002:687f] 
(rev c0) (prog-if 00 [VGA controller])
+    Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] 
[1002:6b76]
  InstallationDate: Installed on 2017-10-17 (92 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. X399 AORUS Gaming 7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-041500rc3-generic 
root=UUID=ffe04907-dda5-48e8-b717-b9a5fb224907 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2017-12-18 (30 days ago)
  dmi.bios.date: 09/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3d
  dmi.board.asset.tag: Default string
  dmi.board.name: X399 AORUS Gaming 7
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3d:bd09/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSGaming7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSGaming7:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X399 AORUS Gaming 7
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.89+git1801121720.fd9bcb7~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 
1:17.4~git180112172800.0eb30d8~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 
1:17.4~git180112172800.0eb30d8~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.10.99+git1801121842.1fe8ca7~a~padoka0
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1801121840.26f5406~a~padoka0
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Title:
  Mouse click does not work

Status in xorg package in Ubuntu:
  New

Bug description:
  moving mouse is fine, clicking does nothing. Just upgraded some
  packages in 17.10

  in the /var/log/Xorg.0.log:

  config/udev: Adding input device Logitech G Pro Gaming Mouse 
(/dev/input/mouse0)
  no input driver specified , ignoring this device

  I wrote that out as I can't copy paste without clicking.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.15.0-041500rc3-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 20:35:20 2018
  DistUpgraded: 2017-12-18 13:27:58,717 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] [1002:687f] 
(rev c0) (prog-if 00 [VGA controller])
     Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] 
[1002:6b76]
  InstallationDate: Installed on 2017-10-17 (92 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. X399 AORUS Gaming 7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-041500rc3-generic 
root=UUID=ffe04907-dda5-48e8-b717-b9a5fb224907 ro quiet s

[Touch-packages] [Bug 1743767] [NEW] Mouse click does not work

[Leo Treasure]

Public bug reported:

moving mouse is fine, clicking does nothing. Just upgraded some packages
in 17.10

in the /var/log/Xorg.0.log:

config/udev: Adding input device Logitech G Pro Gaming Mouse (/dev/input/mouse0)
no input driver specified , ignoring this device

I wrote that out as I can't copy paste without clicking.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
Uname: Linux 4.15.0-041500rc3-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 17 20:35:20 2018
DistUpgraded: 2017-12-18 13:27:58,717 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] [1002:687f] (rev 
c0) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] 
[1002:6b76]
InstallationDate: Installed on 2017-10-17 (92 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Gigabyte Technology Co., Ltd. X399 AORUS Gaming 7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-041500rc3-generic 
root=UUID=ffe04907-dda5-48e8-b717-b9a5fb224907 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to artful on 2017-12-18 (30 days ago)
dmi.bios.date: 09/06/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3d
dmi.board.asset.tag: Default string
dmi.board.name: X399 AORUS Gaming 7
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3d:bd09/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSGaming7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSGaming7:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: X399 AORUS Gaming 7
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.89+git1801121720.fd9bcb7~a~padoka0
version.libgl1-mesa-dri: libgl1-mesa-dri 
1:17.4~git180112172800.0eb30d8~a~padoka0
version.libgl1-mesa-glx: libgl1-mesa-glx 
1:17.4~git180112172800.0eb30d8~a~padoka0
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.10.99+git1801121842.1fe8ca7~a~padoka0
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1801121840.26f5406~a~padoka0
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful third-party-packages ubuntu wayland-session

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

Title:
  Mouse click does not work

Status in xorg package in Ubuntu:
  New

Bug description:
  moving mouse is fine, clicking does nothing. Just upgraded some
  packages in 17.10

  in the /var/log/Xorg.0.log:

  config/udev: Adding input device Logitech G Pro Gaming Mouse 
(/dev/input/mouse0)
  no input driver specified , ignoring this device

  I wrote that out as I can't copy paste without clicking.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.15.0-041500rc3-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 20:35:20 2018
  DistUpgraded: 2017-12-18 13:27:58,717 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] [1002:687f] 
(rev c0) (prog-if 00 [VGA controller])
     Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] 
[1002:6b76]
  InstallationDate: Installed on 2017-10-17 (92 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. X399 AORUS Gaming 7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-041500rc3-generic 
root=UUID=ffe04907-dda5-48e8-b717-b9a5fb224907 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2017-12-18 (30 days ago)
  dmi.bios.date: 09/06/2017
  dmi.bios.vendor: American 

[Touch-packages] [Bug 1524000] Re: PyGIWarning: UbuntuAppLaunch was imported without specifying a version first

[Christoph Reiter]

PyGObject warns that gi.require_version() wasn't used. That's something
that needs to be fixed by the library user.

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

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

Title:
  PyGIWarning: UbuntuAppLaunch was imported without specifying a version
  first

Status in Autopilot:
  Fix Released
Status in Ubuntu Music App:
  Invalid
Status in pygobject package in Ubuntu:
  Invalid

Bug description:
  When launching Autopilot tests for Music App you get an error indicating that 
UbuntuAppLaunch was imported without specifying a version first.
  This is the error:

  autopilot run music_app
  /usr/lib/python2.7/dist-packages/autopilot/application/_launcher.py:23: 
PyGIWarning: UbuntuAppLaunch was imported without specifying a version first. 
Use gi.require_version('UbuntuAppLaunch', '2') before import to ensure that the 
right version gets loaded.
from gi.repository import GLib, UbuntuAppLaunch
  Loading tests from: /home/victor/Development/music-app/tests/autopilot

  Failed to import test module: music_app.tests.test_music
  Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
  module = self._get_module_from_name(name)
File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
  __import__(name)
File 
"/home/victor/Development/music-app/tests/autopilot/music_app/__init__.py", 
line 9, in 
  from ubuntuuitoolkit import (
  ImportError: No module named ubuntuuitoolkit

  Tests running...
  ==
  ERROR: unittest.loader.ModuleImportFailure.music_app.tests.test_music
  --
  Traceback (most recent call last):
  ImportError: Failed to import test module: music_app.tests.test_music
  Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
  module = self._get_module_from_name(name)
File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
  __import__(name)
File 
"/home/victor/Development/music-app/tests/autopilot/music_app/__init__.py", 
line 9, in 
  from ubuntuuitoolkit import (
  ImportError: No module named ubuntuuitoolkit

To manage notifications about this bug go to:
https://bugs.launchpad.net/autopilot/+bug/1524000/+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 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

[Launchpad Bug Tracker]

This bug was fixed in the package iproute2 - 4.3.0-1ubuntu3.16.04.3

---
iproute2 (4.3.0-1ubuntu3.16.04.3) xenial; urgency=medium

  * Fix ip maddr show (LP: #1732032):
- d/p/1005-ip-maddr-fix-igmp-parsing.patch: fix igmp parsing when iface is
  long
- d/p/1006-ip-maddr-avoid-uninitialized-data.patch: avoid accessing
  uninitialized data
- d/p/1007-ip-maddr-fix-filtering-by-device.patch: fix filtering
  by device

 -- Andreas Hasenack   Wed, 29 Nov 2017 15:04:40
-0200

** Changed in: iproute2 (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: iproute2 (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 iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1732032

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Released
Status in iproute2 source package in Xenial:
  Fix Released
Status in iproute2 source package in Zesty:
  Won't Fix
Status in iproute2 source package in Artful:
  Fix Released

Bug description:
  [Impact]
  When a nic has a long enough name such that there is no space between the 
name and the ":" in /proc/net/igmp, ip maddr show dev  will miss the IPV4 
addresses which is otherwise shown with "ip maddr show".

  This is inconsistent behavior and can break scripts and tests, as
  shown in this bug's original description.

  Three patches from upstream were taken to fix this bug, and they were used 
individually instead of being merged into one single patch so it's easier to 
track and recognize authorship:
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=530903dd9003492edb0714e937ad4a5d1219e376
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=b48a1161f5f9b6a0cda399a224bbbf72eba4a5c6
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=21503ed2af233ffe795926f6641ac84ec1b15bf9

  [Test Case]
  * deploy the ubuntu release under test. Please use bare metal or a VM instead 
of containers, because the ip tool parses a file in /proc. Make sure iproute2 
is installed:
  sudo apt install iproute2

  * Run these commands to setup a dummy interface with a long name and
  an IPv4 address. Please change the address if it conflicts with a real
  network you might have available on that machine:

  sudo ip link add dummylongnic0 type dummy
  sudo ip addr add 192.168.199.10/24 dev dummylongnic0
  sudo ip link set dev dummylongnic0 up

  * Compare the output of these two commands with regards to the dummylongnic0 
interface:
  sudo ip maddr show
  sudo ip maddr show dev dummylongnic0

  * With the buggy iproute2 package installed, the more specific output "ip 
maddr show dev dummylongnic0" should lack the "inet 224.0.0.1" line:
  ip maddr show dev dummylongnic0
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet6 ff02::1
inet6 ff01::1

  
  Whereas the less specific command, which lists all interfaces, will have it 
listed for dummylongnic0:
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet  224.0.0.1
inet6 ff02::1
inet6 ff01::1

  
  * With the fixed iproute2 package, all dummylongnic0 addresses will be 
present in both outputs.

  
  [Regression Potential]
  In the end, the ip tool is parsing a text file produced by the kernel. As 
most parsing done in C, it's pretty low level and sensitive to changes in the 
file it's reading.

  [Other Info]
  I suggest to conduct the tests in VMs instead of containers (LXD) because the 
ip maddr command parses /proc/net/igmp, which is produced by the kernel. If you 
use a container, then it's the host's kernel that will be providing that file 
and it might not be the same as with the native kernel of that particular 
ubuntu release.

  --- Original description ---
  Attn. Canonical:  Please make sure that the existing iproute2 package gets 
updated with the two referenced patches as the missing information is impacting 
our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data

  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8286-42A

  ---Steps to Reproduce---
   run these at command line:
  root@roselp1:~# ip maddr show
  ...
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet  224.

[Touch-packages] [Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

[Launchpad Bug Tracker]

This bug was fixed in the package iproute2 - 3.12.0-2ubuntu1.2

---
iproute2 (3.12.0-2ubuntu1.2) trusty; urgency=medium

  * Fix ip maddr show (LP: #1732032):
- d/p/1003-ip-maddr-fix-igmp-parsing.patch: fix igmp parsing when iface is
  long
- d/p/1004-ip-maddr-avoid-uninitialized-data.patch: avoid accessing
  uninitialized data
- d/p/1005-ip-maddr-fix-filtering-by-device.patch: fix filtering
  by device

 -- Andreas Hasenack   Wed, 29 Nov 2017 17:15:25
-0200

** Changed in: iproute2 (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Released
Status in iproute2 source package in Xenial:
  Fix Released
Status in iproute2 source package in Zesty:
  Won't Fix
Status in iproute2 source package in Artful:
  Fix Released

Bug description:
  [Impact]
  When a nic has a long enough name such that there is no space between the 
name and the ":" in /proc/net/igmp, ip maddr show dev  will miss the IPV4 
addresses which is otherwise shown with "ip maddr show".

  This is inconsistent behavior and can break scripts and tests, as
  shown in this bug's original description.

  Three patches from upstream were taken to fix this bug, and they were used 
individually instead of being merged into one single patch so it's easier to 
track and recognize authorship:
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=530903dd9003492edb0714e937ad4a5d1219e376
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=b48a1161f5f9b6a0cda399a224bbbf72eba4a5c6
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=21503ed2af233ffe795926f6641ac84ec1b15bf9

  [Test Case]
  * deploy the ubuntu release under test. Please use bare metal or a VM instead 
of containers, because the ip tool parses a file in /proc. Make sure iproute2 
is installed:
  sudo apt install iproute2

  * Run these commands to setup a dummy interface with a long name and
  an IPv4 address. Please change the address if it conflicts with a real
  network you might have available on that machine:

  sudo ip link add dummylongnic0 type dummy
  sudo ip addr add 192.168.199.10/24 dev dummylongnic0
  sudo ip link set dev dummylongnic0 up

  * Compare the output of these two commands with regards to the dummylongnic0 
interface:
  sudo ip maddr show
  sudo ip maddr show dev dummylongnic0

  * With the buggy iproute2 package installed, the more specific output "ip 
maddr show dev dummylongnic0" should lack the "inet 224.0.0.1" line:
  ip maddr show dev dummylongnic0
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet6 ff02::1
inet6 ff01::1

  
  Whereas the less specific command, which lists all interfaces, will have it 
listed for dummylongnic0:
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet  224.0.0.1
inet6 ff02::1
inet6 ff01::1

  
  * With the fixed iproute2 package, all dummylongnic0 addresses will be 
present in both outputs.

  
  [Regression Potential]
  In the end, the ip tool is parsing a text file produced by the kernel. As 
most parsing done in C, it's pretty low level and sensitive to changes in the 
file it's reading.

  [Other Info]
  I suggest to conduct the tests in VMs instead of containers (LXD) because the 
ip maddr command parses /proc/net/igmp, which is produced by the kernel. If you 
use a container, then it's the host's kernel that will be providing that file 
and it might not be the same as with the native kernel of that particular 
ubuntu release.

  --- Original description ---
  Attn. Canonical:  Please make sure that the existing iproute2 package gets 
updated with the two referenced patches as the missing information is impacting 
our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data

  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8286-42A

  ---Steps to Reproduce---
   run these at command line:
  root@roselp1:~# ip maddr show
  ...
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet  224.0.0.252
  inet  224.0.0.1
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 us

[Touch-packages] [Bug 1705534] Re: "lvs" exits with status 0 after failing

[Jonathan Kamens]

I'm sorry, but I still don't understand what you're saying or what
you're doing.

It's reported fixed in earlier releases OF LVM2, not of Ubuntu. It has
not been fixed in Ubuntu, because Ubuntu hasn't upgraded the LVM2 it
ships to the newer release.

Furthermore, the project you keep marking invalid isn't, as far as I
know, Zesty. It's just "Ubuntu", not a specific Ubuntu version. Am I
missing something?

As I said above, this is still a problem in Artful. I checked and
confirmed that before saying that. And Artful is still supported. So
this is still a bug in the current release of Ubuntu. Therefore, this
bug should remain open as a bug in the current release of Ubuntu.

What exactly needs to change in the bug statuses to accomplish that?

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

Title:
  "lvs" exits with status 0 after failing

Status in lvm2 package in Ubuntu:
  Invalid

Bug description:
  $ sudo lvs --noheadings -o vg_name /tmp
  [sudo] password for jik: 
"/tmp": Invalid path for Logical Volume.
  $ echo $?
  0
  $

  The exit status there after I've provided an invalid logical volume
  path and the program has printed an error message clearly should not
  be 0.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lvm2 2.02.167-1ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Jul 20 12:42:39 2017
  InstallationDate: Installed on 2017-05-19 (62 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1705534/+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 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

[Launchpad Bug Tracker]

This bug was fixed in the package iproute2 - 4.9.0-1ubuntu2.1

---
iproute2 (4.9.0-1ubuntu2.1) artful; urgency=medium

  * Fix ip maddr show (LP: #1732032):
- d/p/1003-ip-maddr-fix-igmp-parsing.patch: fix igmp parsing when iface is
  long
- d/p/1004-ip-maddr-avoid-uninitialized-data.patch: avoid accessing
  uninitialized data
- d/p/1005-ip-maddr-fix-filtering-by-device.patch: fix filtering
  by device
  * d/p/1006-fix-undeclared-UINT16_MAX.patch: FTBFS: tc: include stdint.h
explicitly for UINT16_MAX (LP: #1735158)

 -- Andreas Hasenack   Wed, 29 Nov 2017 11:02:27
-0200

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

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Released
Status in iproute2 source package in Xenial:
  Fix Released
Status in iproute2 source package in Zesty:
  Won't Fix
Status in iproute2 source package in Artful:
  Fix Released

Bug description:
  [Impact]
  When a nic has a long enough name such that there is no space between the 
name and the ":" in /proc/net/igmp, ip maddr show dev  will miss the IPV4 
addresses which is otherwise shown with "ip maddr show".

  This is inconsistent behavior and can break scripts and tests, as
  shown in this bug's original description.

  Three patches from upstream were taken to fix this bug, and they were used 
individually instead of being merged into one single patch so it's easier to 
track and recognize authorship:
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=530903dd9003492edb0714e937ad4a5d1219e376
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=b48a1161f5f9b6a0cda399a224bbbf72eba4a5c6
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=21503ed2af233ffe795926f6641ac84ec1b15bf9

  [Test Case]
  * deploy the ubuntu release under test. Please use bare metal or a VM instead 
of containers, because the ip tool parses a file in /proc. Make sure iproute2 
is installed:
  sudo apt install iproute2

  * Run these commands to setup a dummy interface with a long name and
  an IPv4 address. Please change the address if it conflicts with a real
  network you might have available on that machine:

  sudo ip link add dummylongnic0 type dummy
  sudo ip addr add 192.168.199.10/24 dev dummylongnic0
  sudo ip link set dev dummylongnic0 up

  * Compare the output of these two commands with regards to the dummylongnic0 
interface:
  sudo ip maddr show
  sudo ip maddr show dev dummylongnic0

  * With the buggy iproute2 package installed, the more specific output "ip 
maddr show dev dummylongnic0" should lack the "inet 224.0.0.1" line:
  ip maddr show dev dummylongnic0
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet6 ff02::1
inet6 ff01::1

  
  Whereas the less specific command, which lists all interfaces, will have it 
listed for dummylongnic0:
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet  224.0.0.1
inet6 ff02::1
inet6 ff01::1

  
  * With the fixed iproute2 package, all dummylongnic0 addresses will be 
present in both outputs.

  
  [Regression Potential]
  In the end, the ip tool is parsing a text file produced by the kernel. As 
most parsing done in C, it's pretty low level and sensitive to changes in the 
file it's reading.

  [Other Info]
  I suggest to conduct the tests in VMs instead of containers (LXD) because the 
ip maddr command parses /proc/net/igmp, which is produced by the kernel. If you 
use a container, then it's the host's kernel that will be providing that file 
and it might not be the same as with the native kernel of that particular 
ubuntu release.

  --- Original description ---
  Attn. Canonical:  Please make sure that the existing iproute2 package gets 
updated with the two referenced patches as the missing information is impacting 
our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data

  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8286-42A

  ---Steps to Reproduce---
   run these at command line:
  root@roselp1:~# ip maddr show
  ...
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet  224.0.0.252
  inet  224.0.0.1
  inet6 ff02::1:3
     

[Touch-packages] [Bug 1732032] Update Released

[Robie Basak]

The verification of the Stable Release Update for iproute2 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

** Changed in: iproute2 (Ubuntu Zesty)
   Status: Fix Committed => Won't Fix

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

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Released
Status in iproute2 source package in Xenial:
  Fix Released
Status in iproute2 source package in Zesty:
  Won't Fix
Status in iproute2 source package in Artful:
  Fix Released

Bug description:
  [Impact]
  When a nic has a long enough name such that there is no space between the 
name and the ":" in /proc/net/igmp, ip maddr show dev  will miss the IPV4 
addresses which is otherwise shown with "ip maddr show".

  This is inconsistent behavior and can break scripts and tests, as
  shown in this bug's original description.

  Three patches from upstream were taken to fix this bug, and they were used 
individually instead of being merged into one single patch so it's easier to 
track and recognize authorship:
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=530903dd9003492edb0714e937ad4a5d1219e376
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=b48a1161f5f9b6a0cda399a224bbbf72eba4a5c6
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=21503ed2af233ffe795926f6641ac84ec1b15bf9

  [Test Case]
  * deploy the ubuntu release under test. Please use bare metal or a VM instead 
of containers, because the ip tool parses a file in /proc. Make sure iproute2 
is installed:
  sudo apt install iproute2

  * Run these commands to setup a dummy interface with a long name and
  an IPv4 address. Please change the address if it conflicts with a real
  network you might have available on that machine:

  sudo ip link add dummylongnic0 type dummy
  sudo ip addr add 192.168.199.10/24 dev dummylongnic0
  sudo ip link set dev dummylongnic0 up

  * Compare the output of these two commands with regards to the dummylongnic0 
interface:
  sudo ip maddr show
  sudo ip maddr show dev dummylongnic0

  * With the buggy iproute2 package installed, the more specific output "ip 
maddr show dev dummylongnic0" should lack the "inet 224.0.0.1" line:
  ip maddr show dev dummylongnic0
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet6 ff02::1
inet6 ff01::1

  
  Whereas the less specific command, which lists all interfaces, will have it 
listed for dummylongnic0:
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet  224.0.0.1
inet6 ff02::1
inet6 ff01::1

  
  * With the fixed iproute2 package, all dummylongnic0 addresses will be 
present in both outputs.

  
  [Regression Potential]
  In the end, the ip tool is parsing a text file produced by the kernel. As 
most parsing done in C, it's pretty low level and sensitive to changes in the 
file it's reading.

  [Other Info]
  I suggest to conduct the tests in VMs instead of containers (LXD) because the 
ip maddr command parses /proc/net/igmp, which is produced by the kernel. If you 
use a container, then it's the host's kernel that will be providing that file 
and it might not be the same as with the native kernel of that particular 
ubuntu release.

  --- Original description ---
  Attn. Canonical:  Please make sure that the existing iproute2 package gets 
updated with the two referenced patches as the missing information is impacting 
our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data

  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8286-42A

  ---Steps to Reproduce---
   run these at command line:
  root@roselp1:~# ip maddr show
  ...
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet  224.0.0.252
  inet  224.0.0.1
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
     

[Touch-packages] [Bug 1735158] Re: FTBFS with gcc7

[Launchpad Bug Tracker]

This bug was fixed in the package iproute2 - 4.9.0-1ubuntu2.1

---
iproute2 (4.9.0-1ubuntu2.1) artful; urgency=medium

  * Fix ip maddr show (LP: #1732032):
- d/p/1003-ip-maddr-fix-igmp-parsing.patch: fix igmp parsing when iface is
  long
- d/p/1004-ip-maddr-avoid-uninitialized-data.patch: avoid accessing
  uninitialized data
- d/p/1005-ip-maddr-fix-filtering-by-device.patch: fix filtering
  by device
  * d/p/1006-fix-undeclared-UINT16_MAX.patch: FTBFS: tc: include stdint.h
explicitly for UINT16_MAX (LP: #1735158)

 -- Andreas Hasenack   Wed, 29 Nov 2017 11:02:27
-0200

** Changed in: iproute2 (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 iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1735158

Title:
  FTBFS with gcc7

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Artful:
  Fix Released

Bug description:
  tc
  CC   tc_core.o
  tc_core.c: In function ‘tc_calc_size_table’:
  tc_core.c:190:29: error: ‘UINT16_MAX’ undeclared (first use in this 
function); did you mean ‘__INT16_MAX__’?
 if ((sz >> s->size_log) > UINT16_MAX) {
   ^~
   __INT16_MAX__
  tc_core.c:190:29: note: each undeclared identifier is reported only once for 
each function it appears in
  ../Config:40: recipe for target 'tc_core.o' failed
  make[3]: *** [tc_core.o] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1735158/+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 1735158] Update Released

[Robie Basak]

The verification of the Stable Release Update for iproute2 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  FTBFS with gcc7

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Artful:
  Fix Released

Bug description:
  tc
  CC   tc_core.o
  tc_core.c: In function ‘tc_calc_size_table’:
  tc_core.c:190:29: error: ‘UINT16_MAX’ undeclared (first use in this 
function); did you mean ‘__INT16_MAX__’?
 if ((sz >> s->size_log) > UINT16_MAX) {
   ^~
   __INT16_MAX__
  tc_core.c:190:29: note: each undeclared identifier is reported only once for 
each function it appears in
  ../Config:40: recipe for target 'tc_core.o' failed
  make[3]: *** [tc_core.o] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1735158/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Daniel Eckl]

This workaround is not bad indeed and saves me, too. But it has
drawbacks that people need to know

1) In newer Ubuntu versions, "dnsmasq" is the default DNS option, so the
config does not have this option to comment out. Instead you have to set
"dns=default" there.

2) With this workaround, some applications need a restart to recognize
the new DNS servers after you started VPN. Browsers are a prominent
example of reading resolv.conf setup at start and then caching this
until restart.

3) The VPN DNS servers are used then, but they are on top of the
underlying DNS servers coming from your local DHCP. They are just added
to the top of the list. As long as the VPN DNS servers are working, data
security is intact. As soon as these stop working, your system might
send DNS queries (that maybe should be confidential) to the underlying
DNS server.

Issues 2 and 3 are the most dangerous as they can compromise VPN
confidentiality.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1742433] Re: printer isnt working

[Paul White]

Take a look at https://wiki.ubuntu.com/DebuggingPrintingProblems

** Package changed: xorg (Ubuntu) => cups (Ubuntu)

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

Title:
  printer isnt working

Status in cups package in Ubuntu:
  New

Bug description:
  Hello, i cant connect the printer,installation not possible.Maybe you
  can help me, that would be great!! Greetings Andreas

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  Date: Wed Jan 10 13:28:14 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-25-generic, x86_64: installed
   nvidia-384, 384.111, 4.13.0-25-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP108 [10de:1d01] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:1476]
  InstallationDate: Installed on 2018-01-10 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  MachineType: ECS A780GM-A
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=46d485e9-dea9-402d-9223-fb90a866a61b ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080014
  dmi.board.name: A780GM-A
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080014:bd02/02/2009:svnECS:pnA780GM-A:pvr1.0:rvnECS:rnA780GM-A:rvr1.0:cvnECS:ct3:cvr:
  dmi.product.name: A780GM-A
  dmi.product.version: 1.0
  dmi.sys.vendor: ECS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Jan 10 13:16:19 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputPS/2 Logitech Mouse  MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.5-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1742433/+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 1742902] Re: package libxml2:amd64 2.9.3+dfsg1-1ubuntu0.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi

[Mattia Rizzolo]

tl;dr: your system is in a mess.
Please contact user support if you don't know how to handle it, but it's most 
likely due to some odd thing you did rather than a bug.

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

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

Title:
  package libxml2:amd64 2.9.3+dfsg1-1ubuntu0.5 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libxml2 package in Ubuntu:
  Invalid

Bug description:
  anggifw@anggi-TMA:~$ sudo apt-get -f install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 163 not upgraded.
  5 not fully installed or removed.
  Need to get 0 B/697 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  dpkg: error processing package libxml2:amd64 (--configure):
   package is in a very bad inconsistent state; you should
   reinstall it before attempting configuration
  dpkg: dependency problems prevent configuration of libwebkit2gtk-4.0-37:amd64:
   libwebkit2gtk-4.0-37:amd64 depends on libxml2 (>= 2.7.4); however:
Package libxml2:amd64 is not configured yet.

  dpkg: error processing package libwebkit2gtk-4.0-37:amd64 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of gir1.2-webkit2-4.0:amd64:
   gir1.2-webkit2-4.0:amd64 depends on libwebkit2gtk-4.0-37 (>= 2.17.90); 
however:
Package libwebkit2gtk-4.0-37:amd64 is not configured yet.

  dpkg: error processing package gir1.2-webkit2-4.0:amd64 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of 
libwebkit2gtk-4.0-37-gtk2:amd64:
   libwebkit2gtk-4.0-37-gtk2:amd64 depends on libwebkit2gtk-4.0-37 (= 
2.18.5-0ubuntu0.16.04.1); however:
Package libwebkit2gtk-4.0-37:amd64 is not configured yet.
   libwebkit2gtk-4.0-37-gtk2:amd64 depends on libxml2 (>= 2.7.4); however:
Package libxml2:amd64 is not configured No apport report written because 
the error message indicates its a followup error from a previous failure.
  No apport 
report written because the error message indicates its a followup error from a 
previous failure.
No apport report written because MaxReports is reached already
  
No apport report written because MaxReports is reached already
yet.

  dpkg: error processing package libwebkit2gtk-4.0-37-gtk2:amd64 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of 
ubuntu-release-upgrader-gtk:
   ubuntu-release-upgrader-gtk depends on gir1.2-webkit2-4.0 | 
gir1.2-webkit-3.0; however:
Package gir1.2-webkit2-4.0:amd64 is not configured yet.
Package gir1.2-webkit-3.0 is not installed.

  dpkg: error processing package ubuntu-release-upgrader-gtk (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   libxml2:amd64
   libwebkit2gtk-4.0-37:amd64
   gir1.2-webkit2-4.0:amd64
   libwebkit2gtk-4.0-37-gtk2:amd64
   ubuntu-release-upgrader-gtk
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libxml2:amd64 2.9.3+dfsg1-1ubuntu0.5
  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: Fri Jan 12 16:57:19 2018
  DuplicateSignature:
   package:libxml2:amd64:2.9.3+dfsg1-1ubuntu0.5
   Processing triggers for libc-bin (2.23-0ubuntu9) ...
   dpkg: error processing package libxml2:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-01-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: libxml2
  Title: package libxml2:amd64 2.9.3+dfsg1-1ubuntu0.5 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 1718476] Re: dont know

[adage n]

how can fix this bug.


On Mon, Jan 15, 2018 at 11:57 PM, dino99 <1718...@bugs.launchpad.net> wrote:

> That version is now dead
> http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-
> has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1718476
>
> Title:
>   dont know
>
> Status in xorg package in Ubuntu:
>   Invalid
>
> Bug description:
>   I don't know
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.04
>   Package: xorg 1:7.7+16ubuntu3
>   ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
>   Uname: Linux 4.10.0-35-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.4-0ubuntu4.5
>   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: Wed Sep 20 21:20:59 2017
>   DistUpgraded: Fresh install
>   DistroCodename: zesty
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: No
>   GraphicsCard:
>Intel Corporation 3rd Gen Core processor Graphics Controller
> [8086:0156] (rev 09) (prog-if 00 [VGA controller])
>  Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597]
>   InstallationDate: Installed on 2017-08-25 (26 days ago)
>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
>   MachineType: Dell Inc. Inspiron 3521
>   ProcEnviron:
>LANGUAGE=en_IN:en
>PATH=(custom, no user)
>LANG=en_IN
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic
> root=UUID=92f99876-c22f-40f0-849b-7afdc26f ro quiet splash
> vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 08/19/2013
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A10
>   dmi.board.name: 0FXP6Y
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 8
>   dmi.chassis.vendor: Dell Inc.
>   dmi.chassis.version: A10
>   dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/19/2013:svnDellInc.:
> pnInspiron3521:pvrA10:rvnDellInc.:rn0FXP6Y:rvrA00:cvnDellInc.:ct8:cvrA10:
>   dmi.product.name: Inspiron 3521
>   dmi.product.version: A10
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.76-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20170309-0ubuntu1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.14-0ubuntu1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1718476/+subscriptions
>

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

Title:
  dont know

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I don't know

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  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: Wed Sep 20 21:20:59 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597]
  InstallationDate: Installed on 2017-08-25 (26 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Inspiron 3521
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=92f99876-c22f-40f0-849b-7afdc26f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2013
  dmi.bios.vendor: Dell