date:20190822

This bug was fixed in the package util-linux - 2.34-0.1ubuntu2

---
util-linux (2.34-0.1ubuntu2) eoan; urgency=medium

  * d/p/prevent-fstrim-inside-container.patch:
- Prevent fstrim to run inside a container environment.
(LP: #1589289)

 -- Eric Desrochers   Wed, 21 Aug 2019
13:19:03 +

** Changed in: util-linux (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  fstrim: cannot open /dev/.lxd-mounts: Permission denied

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  In Progress
Status in util-linux source package in Bionic:
  In Progress
Status in util-linux source package in Disco:
  In Progress
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]
  fstrim weekly cronjob output in an unprivileged LXD container:

  /etc/cron.weekly/fstrim:
  fstrim: cannot open /dev/.lxd-mounts: Permission denied
  fstrim: /dev/fuse: not a directory
  fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted

  There is a github issue:

  https://github.com/lxc/lxd/issues/2030

  The outcome is that it's purely an fstrim misbehaviour, it could be
  smarter.

  Stephane Graber comment:

  As all of this is handled by the kernel, there isn't anything we can
  do about it in LXD.

  I think fstrim should be made slightly more clever:

  * Don't run on bind-mounts (you can detect bind-mounts by parsing 
/proc/self/mountinfo instead of /proc/mounts)
  * Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, 
only log actual failures which would likely be EINVAL or memory related errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jun  5 19:49:04 2016
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Test Case]
  * Ubuntu lxd container
  * Wait for the scheduled fstrim run (X: cronjob, B and late: systemd timer)
  * fstrim will run and report errors "Operation not permitted" "Permission 
denied", ...

  Container shouldn't run fstrim, it should only be run at host level.

  [Potential Regression]

  None, the change will only block fstrim to be automatically run at
  scheduled time. One can still run fstrim on a container manually, even
  if there is no purpose of doing that.

  Xenial uses the cronjob approach /etc/cron.weekly/fstrim
  Bionic and late switched to a systemd timer.

  2 differents fixes (one for X, and one for B and late) will be needed,
  but they'll do same thing, which prevent fstrim to automatically run
  if inside a container both fixes using systemd-virt-detect.

  [Other Informations]

  * The systemd timer change upstream PR:
  https://github.com/karelzak/util-linux/pull/841

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1589289/+subscriptions

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

[Touch-packages] [Bug 1840946] Re: [FFe] include cloud-id in user-agent string

This bug was fixed in the package base-files - 10.2ubuntu5

---
base-files (10.2ubuntu5) eoan; urgency=medium

  * motd/50-motd-news: add cloud_id to user-agent string (LP: #1840946)

 -- Andreas Hasenack   Thu, 15 Aug 2019 14:57:39
-0300

** Changed in: base-files (Ubuntu)
   Status: New => Fix Released

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

Title:
  [FFe] include cloud-id in user-agent string

Status in base-files package in Ubuntu:
  Fix Released

Bug description:
  I'm preemptively filing this bug in case this isn't uploaded before
  the feature freeze.

  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one
  is available.

  There is an MP for this already at
  https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git
  /base-files/+merge/371370

  That MP is also fixing a bug where curl would not return a failure if
  the server status is not 200.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+subscriptions

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

[Touch-packages] [Bug 1841113] [NEW] Don't update to 2.13.92 this cycle

2019-08-22 Thread Sebastien Bacher

Public bug reported:

The new version has non trivial changes and needs proper testing, also
it's not clear there is going to be a stable version before eoan is out,
that update is for next cycle

** Affects: fontconfig (Ubuntu)
 Importance: Wishlist
 Status: Triaged


** Tags: upgrade-software-version version-blocked-ff

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

Title:
  Don't update to 2.13.92 this cycle

Status in fontconfig package in Ubuntu:
  Triaged

Bug description:
  The new version has non trivial changes and needs proper testing, also
  it's not clear there is going to be a stable version before eoan is
  out, that update is for next cycle

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

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

[Touch-packages] [Bug 1676587] Re: Radeon HD 6630M/6650M/6750M/7670M/7690M

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

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

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

Title:
  Radeon HD 6630M/6650M/6750M/7670M/7690M

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Trajeta Radeon no funciona ayuda...

  Radeon HD 6630M/6650M/6750M/7670M/7690M

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-44.47~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-44-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.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: Mon Mar 27 21:50:52 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04cd]
   Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 
6630M/6650M/6750M/7670M/7690M] [1002:6741] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2017-03-15 (12 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. Vostro 3550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-44-generic 
root=UUID=eb468df6-658a-45a9-8e3e-a67751221a14 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0PD77K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd02/18/2014:svnDellInc.:pnVostro3550:pvrNotSpecified:rvnDellInc.:rn0PD77K:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3550
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell 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.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

2019-08-22 Thread Nick Adams

@Ioanna

~25 second delay when connecting via SSH

Happens most often during ansible playbook runs, wherein a single ssh
connection is established, but multiple new sessions are created within
that connection. Usually only happens on the 3rd or 4th run after a
reboot. There are hundreds of leftover scopes after an ansible playbook
run and subsequent disconnection:

# ls -ld /run/systemd/transient/session-*.scope* | wc -l
344

# systemd --version
systemd 237
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Fix Released
Status in systemd:
  Fix Released
Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  Won't Fix
Status in systemd source package in Yakkety:
  Invalid

Bug description:
  [Impact]

  The bug affects multiple users and introduces an user visible delay
  (~25 seconds) on SSH connections after a large number of sessions have
  been processed. This has a serious impact on big systems and servers
  running our software.

  The currently proposed fix is actually a safe workaround for the bug
  as proposed by the dbus upstream. The workaround makes uid 0 immune to
  the pending_fd_timeout limit that kicks in and causes the original
  issue.

  [Test Case]

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  Then checking the log file if there are any ssh sessions that are
  taking 25+ seconds to complete.

  Multiple instances of the same script can be used at the same time.

  [Regression Potential]

  The fix has a rather low regression potential as the workaround is a
  very small change only affecting one particular case - handling of uid
  0. The fix has been tested by multiple users and has been around in
  zesty for a while, with multiple people involved in reviewing the
  change. It's also a change that has been proposed by upstream.

  [Original Description]

  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable

[Touch-packages] [Bug 1838208] Re: Wifi stops responding sporadically on lenovo-yoga-720-15ikb

2019-08-22 Thread Asif Youssuff

I will note that sometimes, restarting network-manager doesn't work,
especially if I have put the machine to sleep prior to trying to access
the network. Here's a dmesg where it did come back after network-manager
restart.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1838208/+attachment/5284074/+files/dmesg.txt

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

Title:
  Wifi stops responding sporadically on lenovo-yoga-720-15ikb

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

Bug description:
  I can make this happen by trying to upload a large file using Firefox
  Nightly to https://send.firefox.com/ Within a few seconds (like 10-15)
  my wifi stops responding.

  Restarting network manager via service network-manager restart
  temporarily resolves the issue.

  This issue began appearing a week or so ago -- almost definitely not a
  month ago; my wifi used to be fine previously.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.18.0-1ubuntu5
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 28 14:59:13 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-10-31 (270 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IpRoute:
   default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp1s0 scope link metric 1000 
   192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE IP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION   CON-UUID
  CON-PATH   
   wlp1s0  wifi  connected full  limited   
/org/freedesktop/NetworkManager/Devices/2  dd-wrt-vap-5g 1  
21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   p2p-dev-wlp1s0  wifi-p2p  disconnected  none  none  
/org/freedesktop/NetworkManager/Devices/3  --   --  
  -- 
   lo  loopback  unmanaged unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --   --  
  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.18.0   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asif   1938 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2018-10-31 (276 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80X7
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic 
root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan wayland-session
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN33WW(V2.05)
  dmi.board.asset.tag: NO

[Touch-packages] [Bug 1841079] Re: Speech Dispatcher user should not be shown on LightdDM login screen

LightDM is affected -> Ubuntu Unity, Ubuntu MATE and any other if user
set LightDM as login screen are affected.

Kylin Greeter for Ubuntu Kylin is also affected.

** Attachment added: "kylin-greeter"
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1841079/+attachment/5284073/+files/kylin-greeter.png

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

Title:
  Speech Dispatcher user should not be shown on LightdDM login screen

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download Ubuntu MATE 19.10 alpha ISO - 20190822
  2. Install it using Entire-disk erase scenario with default settings
  3. Reboot system

  Expected results:
  * LightDM shows only just created username

  Actual results:
  * LightDM shows two user names, Speech Dispatcher is selected by default

  Note:
  problem occurs on VM and on real hardware; Minimal desktop installation is 
affected too; OEM installation is affected by bug 1840971 .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: speech-dispatcher 0.9.1-2
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Aug 22 19:02:42 2019
  InstallationDate: Installed on 2019-08-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
  SourcePackage: speech-dispatcher
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

2019-08-22 Thread Dan Watkins

So, to reset on status: I believe that we've narrowed this down to a
systemd/udev problem, as it goes away when a different udevadm binary is
used.  I don't have a good sense of how to go about digging into that
issue, so I don't think I can take it much further.

(Also, as it appears to be a systemd issue, I'm going to mark the cloud-
init task Invalid.  Feel free to move it back to New if you believe this
is a mistake!)

** Changed in: cloud-init
   Status: In Progress => Invalid

** Changed in: cloud-init
 Assignee: Dan Watkins (daniel-thewatkins) => (unassigned)

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

Title:
  cloud-init growpart race with udev

Status in cloud-init:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  On Azure, it happens regularly (20-30%), that cloud-init's growpart
  module fails to extend the partition to full size.

  Such as in this example:

  

  2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', 
'--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, 
capture=True)
  2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', 
'/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True)
  2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds
  2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: 
init-network/config-growpart: FAIL: running config-growpart with frequency 
always
  2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed
  2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
351, in handle
  func=resize_devices, args=(resizer, devices))
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in 
log_time
  ret = func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
298, in resize_devices
  (old, new) = resizer.resize(disk, ptnum, blockdev)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
159, in resize
  return (before, get_size(partdev))
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
198, in get_size
  fd = os.open(filename, os.O_RDONLY)
  FileNotFoundError: [Errno 2] No such file or directory: 
'/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3'

  

  @rcj suggested this is a race with udev. This seems to only happen on
  Cosmic and later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions

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

[Touch-packages] [Bug 1841079] Re: Speech Dispatcher user should not be shown on LightdDM login screen

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

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

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

Title:
  Speech Dispatcher user should not be shown on LightdDM login screen

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download Ubuntu MATE 19.10 alpha ISO - 20190822
  2. Install it using Entire-disk erase scenario with default settings
  3. Reboot system

  Expected results:
  * LightDM shows only just created username

  Actual results:
  * LightDM shows two user names, Speech Dispatcher is selected by default

  Note:
  problem occurs on VM and on real hardware; Minimal desktop installation is 
affected too; OEM installation is affected by bug 1840971 .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: speech-dispatcher 0.9.1-2
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Aug 22 19:02:42 2019
  InstallationDate: Installed on 2019-08-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
  SourcePackage: speech-dispatcher
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1841079] Re: Speech Dispatcher user should not be shown on LightdDM login screen

The problem is really caused by `accountsservice` packages.
Downgrading them to 0.6.50-0ubuntu1 version (as it was in 20190821 iso) fixes 
the issue:

accountsservice_0.6.50-0ubuntu1_amd64.deb
gir1.2-accountsservice-1.0_0.6.50-0ubuntu1_amd64.deb
libaccountsservice0_0.6.50-0ubuntu1_amd64.deb

I determined the list of these packages by comparing the lists of
installed packages from clean install of 20190821 and fully updated
system (or 20190822 daily iso).

---

Steps to confirm:

```
cd ~/Downloads
wget 
https://mirrors.edge.kernel.org/ubuntu/pool/main/a/accountsservice/accountsservice_0.6.50-0ubuntu1_amd64.deb
wget 
https://mirrors.edge.kernel.org/ubuntu/pool/main/a/accountsservice/gir1.2-accountsservice-1.0_0.6.50-0ubuntu1_amd64.deb
wget 
https://mirrors.edge.kernel.org/ubuntu/pool/main/a/accountsservice/libaccountsservice0_0.6.50-0ubuntu1_amd64.deb
sudo apt install ./*accountsservice*.deb
```

and then reboot.

---

So it is a serious regression.

** Tags added: regression-release

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

Title:
  Speech Dispatcher user should not be shown on LightdDM login screen

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download Ubuntu MATE 19.10 alpha ISO - 20190822
  2. Install it using Entire-disk erase scenario with default settings
  3. Reboot system

  Expected results:
  * LightDM shows only just created username

  Actual results:
  * LightDM shows two user names, Speech Dispatcher is selected by default

  Note:
  problem occurs on VM and on real hardware; Minimal desktop installation is 
affected too; OEM installation is affected by bug 1840971 .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: speech-dispatcher 0.9.1-2
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Aug 22 19:02:42 2019
  InstallationDate: Installed on 2019-08-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
  SourcePackage: speech-dispatcher
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

2019-08-22 Thread Mike Clark

Posted alsa-info.sh to http://alsa-
project.org/db/?f=aea8019642712707b206b1ebf30ceada504b58c2

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

Title:
  [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+subscriptions

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

[Touch-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

2019-08-22 Thread Mike Clark

OK, stopped working again today.  I think I undid everything I've been
testing with hdajackretask (i.e. removed boot override) yesterday while
it was still working and double-checked it today.

Here are the results from hdajacksensetest:

 mclark  ~  sudo hdajacksensetest -a //no headphones
Pin 0x12 (Internal Mic, Mobile-In): present = No
Pin 0x13 (Not connected): present = No
Pin 0x14 (Internal Speaker): present = No
Pin 0x18 (Not connected): present = No
Pin 0x19 (Black Mic, Right side): present = No
Pin 0x1a (Not connected): present = No
Pin 0x1b (Not connected): present = Yes
Pin 0x1d (Not connected): present = No
Pin 0x1e (Not connected): present = No
Pin 0x21 (Black Headphone, Right side): present = No
 mclark  ~  sudo hdajacksensetest -a //headphones
Pin 0x12 (Internal Mic, Mobile-In): present = No
Pin 0x13 (Not connected): present = No
Pin 0x14 (Internal Speaker): present = No
Pin 0x18 (Not connected): present = No
Pin 0x19 (Black Mic, Right side): present = No
Pin 0x1a (Not connected): present = No
Pin 0x1b (Not connected): present = Yes
Pin 0x1d (Not connected): present = No
Pin 0x1e (Not connected): present = No
Pin 0x21 (Black Headphone, Right side): present = No

If I'm interpreting this correctly, I only have a pin active on 0x1b.
Wonder if I need to specify that in some config file.

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

Title:
  [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+subscriptions

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

[Touch-packages] [Bug 1841079] Re: Speech Dispatcher user should not be shown on LightdDM login screen

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

** Changed in: speech-dispatcher (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: ubuntu-mate-settings (Ubuntu)
   Status: Confirmed => Invalid

** No longer affects: ubuntu-mate-settings (Ubuntu)

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

** No longer affects: lightdm (Ubuntu)

** No longer affects: speech-dispatcher (Ubuntu)

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

Title:
  Speech Dispatcher user should not be shown on LightdDM login screen

Status in accountsservice package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Download Ubuntu MATE 19.10 alpha ISO - 20190822
  2. Install it using Entire-disk erase scenario with default settings
  3. Reboot system

  Expected results:
  * LightDM shows only just created username

  Actual results:
  * LightDM shows two user names, Speech Dispatcher is selected by default

  Note:
  problem occurs on VM and on real hardware; Minimal desktop installation is 
affected too; OEM installation is affected by bug 1840971 .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: speech-dispatcher 0.9.1-2
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Aug 22 19:02:42 2019
  InstallationDate: Installed on 2019-08-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
  SourcePackage: speech-dispatcher
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1841093] [NEW] [Inspiron 14-3467, Realtek ALC3246, Black Headphone Out, Front] No sound at all

2019-08-22 Thread Ayush Oberoi

Public bug reported:

No sound in headphones. I checked headphones are not damaged

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
Uname: Linux 4.4.0-134-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ayush  2542 F pulseaudio
CurrentDesktop: Unity
Date: Thu Aug 22 22:49:23 2019
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
InstallationDate: Installed on 2017-08-07 (745 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ayush  2542 F pulseaudio
Symptom_Jack: Black Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [Inspiron 14-3467, Realtek ALC3246, Black Headphone Out, Front] No sound 
at all
UpgradeStatus: Upgraded to xenial on 2019-03-05 (170 days ago)
dmi.bios.date: 04/07/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.07.00
dmi.board.name: 0WPN9K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr01.07.00:bd04/07/2017:svnDellInc.:pnInspiron14-3467:pvr:rvnDellInc.:rn0WPN9K:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 14-3467
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  [Inspiron 14-3467, Realtek ALC3246, Black Headphone Out, Front] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound in headphones. I checked headphones are not damaged

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ayush  2542 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Aug 22 22:49:23 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2017-08-07 (745 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ayush  2542 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Inspiron 14-3467, Realtek ALC3246, Black Headphone Out, Front] No 
sound at all
  UpgradeStatus: Upgraded to xenial on 2019-03-05 (170 days ago)
  dmi.bios.date: 04/07/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.07.00
  dmi.board.name: 0WPN9K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.07.00:bd04/07/2017:svnDellInc.:pnInspiron14-3467:pvr:rvnDellInc.:rn0WPN9K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 14-3467
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1841093/+subscriptions

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

[Touch-packages] [Bug 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)

2019-08-22 Thread Dan Streetman

$ reverse-depends -b -r xenial libseccomp-dev
Reverse-Build-Depends
=
* golang-github-seccomp-libseccomp-golang
* lxc
* ocserv
* qemu
* systemd
* tor
* ubuntu-core-launcher

none of these appear to reference pkey_mprotect, so none should need a
rebuild with the xenial-hwe kernel; marking verification-xenial-done
based on that.

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
  seccomp)

Status in libseccomp package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in libseccomp source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Invalid

Bug description:
  Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
  failing on Bionic on ppc64el with the error messages:

  Operating on architecture: ppc
  Failed to add n/a() rule for architecture ppc, skipping: Bad address
  Operating on architecture: ppc64
  Failed to add n/a() rule for architecture ppc64, skipping: Bad address
  Operating on architecture: ppc64-le
  Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical 
argument out of domain
  Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413, 
function test_memory_deny_write_execute_mmap(). Aborting.
  memoryseccomp-mmap terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG) 
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function 
test_memory_deny_write_execute_mmap(). Aborting.
  Aborted (core dumped)
  FAIL: test-seccomp (code: 134)

  Full logs at:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz

  The testcase passed with systemd version 237-3ubuntu10.13 running on the same 
4.15.0-45 kernel on ppc64el:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz

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

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

[Touch-packages] [Bug 1841079] Re: Speech Dispatcher user should not be shown on LightdDM login screen

2019-08-22 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1841079

** Tags added: iso-testing

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

Title:
  Speech Dispatcher user should not be shown on LightdDM login screen

Status in lightdm package in Ubuntu:
  Confirmed
Status in speech-dispatcher package in Ubuntu:
  Confirmed
Status in ubuntu-mate-settings package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download Ubuntu MATE 19.10 alpha ISO - 20190822
  2. Install it using Entire-disk erase scenario with default settings
  3. Reboot system

  Expected results:
  * LightDM shows only just created username

  Actual results:
  * LightDM shows two user names, Speech Dispatcher is selected by default

  Note:
  problem occurs on VM and on real hardware; Minimal desktop installation is 
affected too; OEM installation is affected by bug 1840971 .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: speech-dispatcher 0.9.1-2
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Aug 22 19:02:42 2019
  InstallationDate: Installed on 2019-08-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
  SourcePackage: speech-dispatcher
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1841079] Re: Speech Dispatcher user should not be shown on LightdDM login screen

2019-08-22 Thread FranksMCB

Confirmed.

09212019 installs worked correctly with the exception of the OEM install
(Bug#1804971)

On 09222019 this has expanded to all installs.

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

Title:
  Speech Dispatcher user should not be shown on LightdDM login screen

Status in lightdm package in Ubuntu:
  Confirmed
Status in speech-dispatcher package in Ubuntu:
  Confirmed
Status in ubuntu-mate-settings package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download Ubuntu MATE 19.10 alpha ISO - 20190822
  2. Install it using Entire-disk erase scenario with default settings
  3. Reboot system

  Expected results:
  * LightDM shows only just created username

  Actual results:
  * LightDM shows two user names, Speech Dispatcher is selected by default

  Note:
  problem occurs on VM and on real hardware; Minimal desktop installation is 
affected too; OEM installation is affected by bug 1840971 .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: speech-dispatcher 0.9.1-2
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Aug 22 19:02:42 2019
  InstallationDate: Installed on 2019-08-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
  SourcePackage: speech-dispatcher
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1841079] Re: Speech Dispatcher user should not be shown on LightdDM login screen

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

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

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

Title:
  Speech Dispatcher user should not be shown on LightdDM login screen

Status in lightdm package in Ubuntu:
  Confirmed
Status in speech-dispatcher package in Ubuntu:
  Confirmed
Status in ubuntu-mate-settings package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download Ubuntu MATE 19.10 alpha ISO - 20190822
  2. Install it using Entire-disk erase scenario with default settings
  3. Reboot system

  Expected results:
  * LightDM shows only just created username

  Actual results:
  * LightDM shows two user names, Speech Dispatcher is selected by default

  Note:
  problem occurs on VM and on real hardware; Minimal desktop installation is 
affected too; OEM installation is affected by bug 1840971 .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: speech-dispatcher 0.9.1-2
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Aug 22 19:02:42 2019
  InstallationDate: Installed on 2019-08-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
  SourcePackage: speech-dispatcher
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1841079] Re: Speech Dispatcher user should not be shown on LightdDM login screen

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

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

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

Title:
  Speech Dispatcher user should not be shown on LightdDM login screen

Status in lightdm package in Ubuntu:
  Confirmed
Status in speech-dispatcher package in Ubuntu:
  Confirmed
Status in ubuntu-mate-settings package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download Ubuntu MATE 19.10 alpha ISO - 20190822
  2. Install it using Entire-disk erase scenario with default settings
  3. Reboot system

  Expected results:
  * LightDM shows only just created username

  Actual results:
  * LightDM shows two user names, Speech Dispatcher is selected by default

  Note:
  problem occurs on VM and on real hardware; Minimal desktop installation is 
affected too; OEM installation is affected by bug 1840971 .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: speech-dispatcher 0.9.1-2
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Aug 22 19:02:42 2019
  InstallationDate: Installed on 2019-08-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
  SourcePackage: speech-dispatcher
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1841079] Re: Speech Dispatcher user should not be shown on LightdDM login screen

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

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

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

Title:
  Speech Dispatcher user should not be shown on LightdDM login screen

Status in lightdm package in Ubuntu:
  Confirmed
Status in speech-dispatcher package in Ubuntu:
  Confirmed
Status in ubuntu-mate-settings package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Download Ubuntu MATE 19.10 alpha ISO - 20190822
  2. Install it using Entire-disk erase scenario with default settings
  3. Reboot system

  Expected results:
  * LightDM shows only just created username

  Actual results:
  * LightDM shows two user names, Speech Dispatcher is selected by default

  Note:
  problem occurs on VM and on real hardware; Minimal desktop installation is 
affected too; OEM installation is affected by bug 1840971 .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: speech-dispatcher 0.9.1-2
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Aug 22 19:02:42 2019
  InstallationDate: Installed on 2019-08-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
  SourcePackage: speech-dispatcher
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1841079] Re: Speech Dispatcher user should not be shown on LightdDM login screen

** Attachment added: "speech-dispatcher-1910.png"
   
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1841079/+attachment/5284044/+files/speech-dispatcher-1910.png

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

Title:
  Speech Dispatcher user should not be shown on LightdDM login screen

Status in lightdm package in Ubuntu:
  New
Status in speech-dispatcher package in Ubuntu:
  New
Status in ubuntu-mate-settings package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Download Ubuntu MATE 19.10 alpha ISO - 20190822
  2. Install it using Entire-disk erase scenario with default settings
  3. Reboot system

  Expected results:
  * LightDM shows only just created username

  Actual results:
  * LightDM shows two user names, Speech Dispatcher is selected by default

  Note:
  problem occurs on VM and on real hardware; Minimal desktop installation is 
affected too; OEM installation is affected by bug 1840971 .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: speech-dispatcher 0.9.1-2
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Aug 22 19:02:42 2019
  InstallationDate: Installed on 2019-08-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
  SourcePackage: speech-dispatcher
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

2019-08-22 Thread Ubuntu Kernel Bot

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Won't Fix
Status in mesa source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Several schools reported black screens after normally updating their Ubuntu 
boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

  This is caused by mesa assuming that soft-pinning on GEN8+ is working
  since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So
  a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT
  sizes/pin flags, but that's left for future.

  [Test case]
  install fixed mesa or kernel, check that the regression is fixed

  [Regression potential]
  mesa: shouldn't be any, it just reverts the change to always soft-pin
  (TODO kernel: adds commits from upstream stable, which have been well tested 
upstream by now)

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

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

[Touch-packages] [Bug 1841088] [NEW] curl with -v parameter writes many 'Expire in 200 ms for 1 (transfer 0x55e0729015c0)'

2019-08-22 Thread Beowulf

Public bug reported:

This is a known issue
https://www.linuxquestions.org/questions/slackware-14/curl-expire-in-1-ms-for-1-transfer-0xa5a060-4175649204/

The fix has already been released, just include the new version of curl
into the distribution.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: curl 7.64.0-2ubuntu1.1
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Aug 22 19:22:39 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-01-06 (592 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: curl
UpgradeStatus: Upgraded to disco on 2019-07-25 (27 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  curl with -v parameter  writes many 'Expire in 200 ms for 1 (transfer
  0x55e0729015c0)'

Status in curl package in Ubuntu:
  New

Bug description:
  This is a known issue
  
https://www.linuxquestions.org/questions/slackware-14/curl-expire-in-1-ms-for-1-transfer-0xa5a060-4175649204/

  The fix has already been released, just include the new version of
  curl into the distribution.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: curl 7.64.0-2ubuntu1.1
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Aug 22 19:22:39 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-01-06 (592 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: curl
  UpgradeStatus: Upgraded to disco on 2019-07-25 (27 days ago)

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

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

[Touch-packages] [Bug 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)

2019-08-22 Thread Ubuntu Kernel Bot

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
  seccomp)

Status in libseccomp package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in libseccomp source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Invalid

Bug description:
  Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
  failing on Bionic on ppc64el with the error messages:

  Operating on architecture: ppc
  Failed to add n/a() rule for architecture ppc, skipping: Bad address
  Operating on architecture: ppc64
  Failed to add n/a() rule for architecture ppc64, skipping: Bad address
  Operating on architecture: ppc64-le
  Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical 
argument out of domain
  Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413, 
function test_memory_deny_write_execute_mmap(). Aborting.
  memoryseccomp-mmap terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG) 
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function 
test_memory_deny_write_execute_mmap(). Aborting.
  Aborted (core dumped)
  FAIL: test-seccomp (code: 134)

  Full logs at:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz

  The testcase passed with systemd version 237-3ubuntu10.13 running on the same 
4.15.0-45 kernel on ppc64el:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz

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

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

[Touch-packages] [Bug 1841079] [NEW] Speech Dispatcher user should not be shown on LightdDM login screen

Public bug reported:

Steps to reproduce:
1. Download Ubuntu MATE 19.10 alpha ISO - 20190822
2. Install it using Entire-disk erase scenario with default settings
3. Reboot system

Expected results:
* LightDM shows only just created username

Actual results:
* LightDM shows two user names, Speech Dispatcher is selected by default

Note:
problem occurs on VM and on real hardware; Minimal desktop installation is 
affected too; OEM installation is affected by bug 1840971 .

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: speech-dispatcher 0.9.1-2
ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
Uname: Linux 5.2.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Aug 22 19:02:42 2019
InstallationDate: Installed on 2019-08-22 (0 days ago)
InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
SourcePackage: speech-dispatcher
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: speech-dispatcher (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug eoan

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

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

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

Title:
  Speech Dispatcher user should not be shown on LightdDM login screen

Status in lightdm package in Ubuntu:
  New
Status in speech-dispatcher package in Ubuntu:
  New
Status in ubuntu-mate-settings package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Download Ubuntu MATE 19.10 alpha ISO - 20190822
  2. Install it using Entire-disk erase scenario with default settings
  3. Reboot system

  Expected results:
  * LightDM shows only just created username

  Actual results:
  * LightDM shows two user names, Speech Dispatcher is selected by default

  Note:
  problem occurs on VM and on real hardware; Minimal desktop installation is 
affected too; OEM installation is affected by bug 1840971 .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: speech-dispatcher 0.9.1-2
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Aug 22 19:02:42 2019
  InstallationDate: Installed on 2019-08-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
  SourcePackage: speech-dispatcher
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1837700] Re: Dell system takes a long time to connect network with external dock

** Also affects: systemd (Ubuntu Eoan)
Importance: Medium
Assignee: Shih-Yuan Lee (fourdollars)
Status: New

** Changed in: systemd (Ubuntu Eoan)
Status: New => Fix Committed

** Changed in: systemd (Ubuntu Eoan)
Assignee: Shih-Yuan Lee (fourdollars) => Dimitri John Ledkov (xnox)

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

Title:
Dell system takes a long time to connect network with external dock

Status in HWE Next:
New
Status in OEM Priority Project:
In Progress
Status in systemd package in Ubuntu:
Fix Committed
Status in systemd source package in Bionic:
In Progress
Status in systemd source package in Disco:
In Progress
Status in systemd source package in Eoan:
Fix Committed

Bug description:
update for SRU process:

---

[1]:

[Touch-packages] [Bug 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time

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

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

Title:
  [SRU] systemd-resolved negative caching for extended period of time

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache
  the result for very long (infinity?). I have to restart systemd-
  resolved to have the negative caching purged.

  * After SERVFAIL DNS server issue has been resolved, chromium/firefox
  still returns DNS error despite host can correctly resolve the name.

  [Test Case]

  * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s 
(See 201d995),
  however, there are several use cases on which this condition is not 
acceptable (See #5552 comments)
  and the only workaround would be to disable cache entirely or flush it , 
which isn't optimal.

  * Configure /etc/systemd/resolved.conf as follows:

  Cache=yes (default)

  * Restart systemd-resolved (systemctl restart systemd-
  resolved.service)

  * Run a host/getent command against a entry that will return SERVFAIL
  and check the journalctl output to see that the reply gets served from
  cache.

  root@systemd-disco:/home/ubuntu# host www.no-record.cl
  Host www.montemar.cl not found: 2(SERVFAIL)
  root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n
  -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 
UTC. --
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for 
 on scope dns on ens3/* now complete with 
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet 
with id 61042 on interface 1/AF_INET.
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 
6222.
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query 
packet for id 53580
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for  
www.no-record.cl IN A.
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache 
hit for  www.no-record.cl IN A
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < 
www.no-record.cl IN A> on scope dns on ens3/* now complete with  scope dns on ens3/.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP 
for transaction 22382.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet 
with id 22382.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming 
packet on transaction 22382 (rcode=SERVFAIL).
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: 
SERVFAIL
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative 
entry for: www.metaklass.org IN A, cache mode set to no-negative
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for 
 on scope dns on ens3/ now complete with from network 
(unsigned).
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet 
with id 31060 on interface 1/AF_INET.

  The following patch https://github.com/systemd/systemd/pull/13047
  implements the required changes.

  [Other Info]

  Note that systemd in Eoan is being upgraded to upstream 242, so I am
  not adding this to Eoan now, as I don't want to disturb the merge. If
  needed after the merge, I'll add to Eoan.

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

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

[Touch-packages] [Bug 1835809] Re: AMD Ryzen 3000 series fails to boot

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

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

Title:
  AMD Ryzen 3000 series fails to boot

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * Systems with AMD Ryzen 3000 series CPUs don't boot.

  [Test Case]

   * Boot with fixed systemd on an AMD Ryzen 3000 series system.

  [Regression Potential]

   * The fix itself is very small, it ignores known to be faulty random
  values returned by the rdrand instruction and use a different random
  source. Those values can still be returned by a properly working
  rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in
  2^64 cases on 64 bit arches, but the fallback to the other random
  source ensures that in those rare occasions a random number can be
  generated.

  [Original Bug Text]

  On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd
  preventing the boot process from completing. This issue does not
  affect the older systemd version in 18.04, but affects the 19.04
  version.

  Here is a screenshot showing what happens:
  
https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux=amd_zen2_14_show

  I am currently testing a patch to systemd, derived from this pull request:
  https://github.com/systemd/systemd/pull/12536

  This is a high severity issue, as I do not believe there is no
  potential workaround without either a firmware update or an ISO
  respin.

  I have attached a rebase of the potential patch on the current 19.04
  version of systemd for reference. I will provide more details after
  testing.

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

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

[Touch-packages] [Bug 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes

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

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

Title:
  networkd-dhcp4 does not set prefsrc for dhcp-provided classless or
  static routes

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  Fix Committed

Bug description:
  [impact]

  the systemd networkd dhcp4 client sets the prefsrc for the default
  route added when a dhcp server provides only the gateway; but if the
  dhcp server provides classless route(s), those are configured instead,
  and the prefsrc is not set for those.

  Normally this is ok, but if the dhcp client system has other
  address(es) configured on the interface using dhcp, then the src for
  packets sent through a classless/static route might not be the same as
  the address provided by the dhcp server.

  If the gateway/router provided in the dhcp classless/static route(s)
  only allows traffic from the address provided to the dhcp client, then
  traffic from the dhcp client may be dropped by the gateway/router.

  [test case]

  set up a dhcp server system (e.g. ubuntu with dnsmasq installed and
  configured) and a dhcp client system.  For example on the dhcp server,
  use this dnsmasq config:

  interface=ens8
  bind-interfaces
  domain=test,10.10.0.0/24
  dhcp-option=42,10.10.0.1
  dhcp-range=test,10.10.0.10,10.10.0.100,1h

  On the dhcp client system, use networkd config such as:

  $ cat /etc/systemd/network/80-ens8.network
  [Match]
  Name=ens8

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  Address=10.10.0.5/24

  Reboot the client, or restart networkd, and it should result in:

  $ ip -4 a show ens8
  3: ens8:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8
     valid_lft forever preferred_lft forever
  inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8
     valid_lft 3580sec preferred_lft 3580sec

  $ ip r
  default via 10.10.0.1 dev ens8 proto dhcp src 10.10.0.75 metric 1024
  10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5
  10.10.0.1 dev ens8 proto dhcp scope link src 10.10.0.75 metric 1024

  Note that, because networkd completes the static ip configuration
  before the dhcp reply is returned and processed, the static address is
  used for the subnet-local routing.  But for global routing through the
  gateway, the dhcp-provided address is used:

  $ ip r get 1.1.1.1
  1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.75 uid 1000

  Now on the server, add a classless route:

  dhcp-option=121,0.0.0.0/0,10.10.0.1

  and restart dnsmasq on the server.  Then on the client, reboot.  It
  should now have:

  $ ip -4 a show ens8
  3: ens8:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8
     valid_lft forever preferred_lft forever
  inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8
     valid_lft 3585sec preferred_lft 3585sec

  $ ip r
  default via 10.10.0.1 dev ens8 proto dhcp metric 1024
  10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5

  Now, the global route will use the static address, not the dhcp-
  provided address:

  $ ip r get 1.1.1.1
  1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.5 uid 1000

  If the router, 10.10.0.1, only will forward traffic sent from the dhcp
  address it provided, 10.10.0.75, then this configuration will result
  in the client being unable to reach anything through the router,
  because all its packets will have a source address of 10.10.0.5, which
  the router would drop/reject.

  [regression potential]

  this only affects dhcp routes provided by a dhcp server using the
  'static' or 'classless' route dhcp options.  Since this behavior is
  currently the default when a system doesn't add static address(es) to
  interfaces that also get dhcp addresses, this is likely not a change
  in behavior for the vast majority of systems.  And any systems that do
  add static address(es) would usually be able to route through a
  gateway from either the dhcp-provided, or static, address.  So the
  regression potential for this change should be low.

  [other info]

  Note that systemd in Eoan is being upgraded to upstream 242, so I am
  not adding this to Eoan now, as I don't want to disturb the merge.  If
  needed after the merge, I'll add to Eoan.

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

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

[Touch-packages] [Bug 1839589] Re: pulseaudio FTBFS on eoan 12.2-2ubuntu4 [FAIL: cpu-volume-test]

2019-08-22 Thread Dave Chiluk

Hey thanks for the fix, I've been on vacation, and didn't have a chance
to look at this further.

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

Title:
  pulseaudio FTBFS on eoan 12.2-2ubuntu4 [FAIL: cpu-volume-test]

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  pulseaudio fails to build from source on Eoan

  I was attempting to put together a patchset for LP#1839580, but it
  appears as if the packages are currently failing to build from source.
  Not sure how they built the first time around.

  Here's my ppa's buildlog, for a source package with my patch commented out of 
the series file.
  
https://launchpadlibrarian.net/436626918/buildlog_ubuntu-eoan-amd64.pulseaudio_1%3A12.2-2ubuntu4+lp1839580b2_BUILDING.txt.gz

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

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

[Touch-packages] [Bug 1840375] Re: groupdel doesn't support extrausers

This bug was fixed in the package shadow - 1:4.5-1.1ubuntu3

---
shadow (1:4.5-1.1ubuntu3) eoan; urgency=medium

  * debian/patches/1014_extrausers_delgroup.patch
- add --extrausers option to "groupdel" (LP: #1840375)

 -- Michael Vogt   Wed, 21 Aug 2019 11:40:17
+0200

** Changed in: shadow (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  groupdel doesn't support extrausers

Status in snapd:
  New
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Xenial:
  New
Status in shadow source package in Bionic:
  New
Status in shadow source package in Disco:
  New

Bug description:
  snapd needs the ability to call 'groupdel --extrausers foo' to clean
  up after itself, but --extrausers is currently unsupported.

  [Impact] 
  On ubuntu-core systems we want to be able to manage "extrausers" in the same
  way as regular users. This requires updates to the various 
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.

  This is an important feature for Ubuntu Core

  [Test Case]
  1. install the libnss-extrausers and configure it
  2. run "groupadd --extrausers foo"
  3  check /var/lib/extrausers/group for the new "foo" group
  4. run "groupdel --extrausers foo"
  5. check /var/lib/extrausers/group and ensure the "foo" group is removed

  [Regression Potential]

   * low: this adds a new (optional) option which is off by default

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

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

[Touch-packages] [Bug 1832019] Re: Error when going to 'Tools -> Preferences -> Keyboard shortcuts' in Spyder3 in Bionic

2019-08-22 Thread Dmitry Shachnev

Thanks for the additional information. Still it is a bug in Spyder, not
in Qt:

1) Cleanlooks and Plastique styles are inheriting from QProxyStyle.
2) So in Spyder’s HTMLDelegate.paint method, options.widget.style() returns a 
QProxyStyle.
3) In QProxyStyle.subElementRect method, the third argument is not optional, so 
should be specified: https://doc.qt.io/qt-5/qproxystyle.html#subElementRect

In C++, if the two-argument call is used, the compiler would ignore
QProxyStyle::subElementRect and fall back to
QCommonStyle::subElementRect. However, in Python there is no concept of
overloading methods so this is not possible.

So Qt and PyQt behave according to their documentation.

Replacing style.subElementRect(QStyle.SE_ItemViewItemText, options) with
style.subElementRect(QStyle.SE_ItemViewItemText, options, None) in
Spyder code seems to help.

With regards to crash when using GTK2, it is a different and known
issue. Qt uses GTK3 platformtheme (i.e. dialogs) by default, and it is
incompatible with GTK2. If you want to use GTK2 then you should export
QT_QPA_PLATFORMTHEME=gtk2. But I recommend against using GTK2 as it is
deprecated.

** Changed in: qtstyleplugins-src (Ubuntu)
   Status: New => Invalid

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

Title:
  Error when going to 'Tools -> Preferences -> Keyboard shortcuts' in
  Spyder3 in Bionic

Status in pyqt5 package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in qtstyleplugins-src package in Ubuntu:
  Invalid
Status in spyder package in Ubuntu:
  New

Bug description:
  In Ubuntu 18.04 LTS
  Steps:

  1. Install spyder3 and qt5-style-plugins (sudo apt install spyder3 
qt5-style-plugins)
  2. Run spyder3
  3. Go to Tools → Preferences → General → Appearance
  4. Change the Qt window style to cleanlooks, gtk2 or plastique
  5. Go to Tools → Preferences → Keyboard shortcuts
  6. Error (or crash in case of gtk2)

  Keyboard shortcuts are not accessible.

  Here is the error:

    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint
  textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options)
  TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): 
not enough arguments
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 
127, in paint

[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

2019-08-22 Thread Adrianvg

Thanks Petr. I'll snoop around and see if I can find the future roadmap
for Shibboleth wrt libcurl3/4. I have this gut-feeling not everything is
a-okay over there. We can't be the only ones getting hit ny this...

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop
  mongodb

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

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

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

[Touch-packages] [Bug 1837937] Re: CRASH

2019-08-22 Thread Po-Hsu Lin

Marked as Incomplete for request in comment #44,
please feel free to switch it back to confirmed when you have it tested.
Thanks.

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

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

Title:
  CRASH

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  The screen froze but the mouse was still moving then it all froze and
  said systemd-journal not able to write entry. I had to press the power
  button.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-9-generic 5.2.0-9.10
  ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1
  Uname: Linux 5.2.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  administrator   2068 F pulseaudio
   /dev/snd/controlC0:  administrator   2068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 25 15:11:47 2019
  InstallationDate: Installed on 2019-06-05 (50 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605)
  MachineType: HP HP Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-9-generic N/A
   linux-backports-modules-5.2.0-9-generic  N/A
   linux-firmware   1.181
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82F6
  dmi.board.vendor: HP
  dmi.board.version: 40.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: X7T78UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  administrator   2852 F pulseaudio
   /dev/snd/controlC0:  administrator   2852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-05 (51 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605)
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=512M-:192M 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-9-generic N/A
   linux-backports-modules-5.2.0-9-generic  N/A
   linux-firmware   1.181
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  eoan
  Uname: Linux 5.2.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/15/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 82F6
  dmi.board.vendor: HP
  dmi.board.version: 40.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: X7T78UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  administrator   2852 F pulseaudio
   /dev/snd/controlC0:  administrator   2852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-05 (51 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605)
  MachineType: HP HP Notebook
  Package: linux (not installed)
  ProcEnviron:

[Touch-packages] [Bug 1840902] Re: ejabberd fails incoming connections with "Failed to secure c2s connection: TLS failed: client renegotiations forbidden"

2019-08-22 Thread Robie Basak

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

This seems fixed in the security pocket now. Thanks!

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

Title:
  ejabberd fails incoming connections with "Failed to secure c2s
  connection: TLS failed: client renegotiations forbidden"

Status in ejabberd package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  Invalid
Status in ejabberd source package in Bionic:
  New
Status in openssl source package in Bionic:
  Invalid

Bug description:
  ejabberd 18.01-2 on Bionic.
  Bad: openssl/libssl1.1 1.1.1-1ubuntu2.1~18.04.4
  Good: openssl/libssl1.1 1.1.0g-2ubuntu4.3

  This hit the Bionic security pocket yesterday, so everyone who uses
  unattended-upgrades for security only (which is the default) will have
  received this overnight.

  Workaround: downgrade openssl/libssl1.1 to 1.1.0g-2ubuntu4.3 using old
  builds that are available from
  https://launchpad.net/ubuntu/+source/openssl/1.1.0g-2ubuntu4.3 (follow
  the architecture link eg. "amd64")

  The error logged by ejabberd is:

  2019-08-21 06:52:28.402 [warning]
  <0.539.0>@ejabberd_c2s:process_terminated:290 (tls|<0.539.0>) Failed
  to secure c2s connection: TLS failed: client renegotiations forbidden

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

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

[Touch-packages] [Bug 218637] Re: Non-breaking space is easy to write accidentally and impossible or hard to distinguish from regular space.

2019-08-22 Thread Jarno Suni

** Description changed:

  OS: from Hardy to at least Bionic.
  
  When you use Finnish keyboard, you have to hold Alt Gr down to type | or
  \ or certain other characters. When typing a shell command, you may
  often want to enter a space character after such characters. But it
  easily happens that Alt Gr is still down when you press space, and
  consequently you type non-breaking space character U+00A0 (at least, if
  you use UTF-8 keyboard layout, which is default in Ubuntu).
  
  $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar"
  ls: cannot access foo bar: No such file or directory
  $cat foo bar | grep 0
  No command ' grep' found, but there are 16 similar ones
   grep: command not found
  
  Besides it may be hard to see the typing error, as non-breaking space
  character looks exactly same as regular space character.
  
  A way to avoid such typos would be to use another keyboard shortcut for
  non-breaking space. Besides non-breaking space should look different
  than regular space in terminal emulators and in editors.
  
  WORKAROUNDS:
  
  Run
  setxkbmap -option "nbsp:none"
  to make  type regular space character.
  
  Even better option is to use "classic", "mac" or "nodeadkeys" keyboard
  variant instead of "". This could be set up in /etc/default/keyboard and
  maybe in configuration dialog in your desktop environment.
  
  Non-breaking space can still be typed (in GTK apps) by u
  00a0, if needed. Another option is to use compose key: 
   .
  
  In Bash scripts you could also use `printf '\u00a0'` or `printf
  '\xc2\xa0'` to print a non-breaking space. (You could use `echo -en`
  instead of `printf`.) Or you could set up a variable `readonly
  nbsp=$'\u00a0'`.
+ 
+ Yet another workaround would be to use a font that displays regular
+ space and non-breaking space differently, but is there one?

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

Title:
  Non-breaking space is easy to write accidentally and impossible or
  hard to distinguish from regular space.

Status in Geany:
  New
Status in gedit:
  New
Status in GNOME Terminal:
  New
Status in nano:
  New
Status in xfce4-terminal:
  New
Status in xkeyboard-config package in Ubuntu:
  Opinion

Bug description:
  OS: from Hardy to at least Bionic.

  When you use Finnish keyboard, you have to hold Alt Gr down to type |
  or \ or certain other characters. When typing a shell command, you may
  often want to enter a space character after such characters. But it
  easily happens that Alt Gr is still down when you press space, and
  consequently you type non-breaking space character U+00A0 (at least,
  if you use UTF-8 keyboard layout, which is default in Ubuntu).

  $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar"
  ls: cannot access foo bar: No such file or directory
  $cat foo bar | grep 0
  No command ' grep' found, but there are 16 similar ones
   grep: command not found

  Besides it may be hard to see the typing error, as non-breaking space
  character looks exactly same as regular space character.

  A way to avoid such typos would be to use another keyboard shortcut
  for non-breaking space. Besides non-breaking space should look
  different than regular space in terminal emulators and in editors.

  WORKAROUNDS:

  Run
  setxkbmap -option "nbsp:none"
  to make  type regular space character.

  Even better option is to use "classic", "mac" or "nodeadkeys" keyboard
  variant instead of "". This could be set up in /etc/default/keyboard
  and maybe in configuration dialog in your desktop environment.

  Non-breaking space can still be typed (in GTK apps) by u
  00a0, if needed. Another option is to use compose key:
.

  In Bash scripts you could also use `printf '\u00a0'` or `printf
  '\xc2\xa0'` to print a non-breaking space. (You could use `echo -en`
  instead of `printf`.) Or you could set up a variable `readonly
  nbsp=$'\u00a0'`.

  Yet another workaround would be to use a font that displays regular
  space and non-breaking space differently, but is there one?

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

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

[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

2019-08-22 Thread Petr Sedlacek

@adrianvg Despite the very poor planning and execution of the
libcurl3/libcurl4 transition, the best solution is to get all the
relevant packages updated to use libcurl4. I very much doubt the next
LTS release will resolve this.

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop
  mongodb

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

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

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

[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

2019-08-22 Thread Adrianvg

Dev issued me a ticket as he needed php7.0-curl on a server (using Shibd for 
user authentication) running Ubuntu 18.04 LTS, so I obliged. 
Dependency libcurl4 was needed too, but had to stop there as the package 
shibboleth-sp2-common was to be removed. The shibboleth-sp2-common contains the 
shib daemon.
Some googling got me to 
https://depts.washington.edu/bitblog/2018/06/libcurl3-libcurl4-shibboleth-php-curl-ubuntu-18-04/
 and of course here.

My understanding is that Shibboleth is pretty widely used worldwide in
university authentication solutions (we're a major Swedish Uni BTW) -
how could this have slipped through?

Is this a lost cause, do we wait for the next LTS release and hope for
the best or what?

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop
  mongodb

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

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

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

[Touch-packages] [Bug 1841006] Re: gdb reports a segfault in ld-linux.so.3 on armhf

And the VM in question has an arm64 kernel right? Have you tried an
armhf kernel?

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

Title:
  gdb reports a segfault in ld-linux.so.3 on armhf

Status in binutils package in Ubuntu:
  New

Bug description:
  In an eoan armhf container on a disco arm64 vm:

  root@helped-oyster:~# gdb /bin/true
  GNU gdb (Ubuntu 8.3-0ubuntu1) 8.3
  ...
  (gdb) r
  Starting program: /usr/bin/true 

  Program received signal SIGSEGV, Segmentation fault.
  0xf7fc8ee0 in ?? () from /lib/ld-linux-armhf.so.3

  It happens in a disco container too.

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

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

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

2019-08-22 Thread bugproxy

--- Comment From heinz-werner_se...@de.ibm.com 2019-08-22 03:57 EDT---
IBM bugzilla status-> closed, Fix Release with Eoan

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

Title:
  [19.10 FEAT] zlib compression improvements

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in zlib package in Ubuntu:
  Fix Released

Bug description:
  Compression improvements for Linux on z using zlib in support of
  better performance.

  Upstream post 2019-03-15: https://github.com/madler/zlib/pull/410

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1823157/+subscriptions

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

[Touch-packages] [Bug 1782719] Re: Duplex not working upon update to 2.2.7-1ubuntu2.1

2019-08-22 Thread MichaelB

I have not exactly the same problem but it is probably related.

On Ubuntu 18.04.3, i choose Duplex "Long Edge" but it print a single-
sided PDF document.. It was working on Ubuntu 16.04.x.. I tried Ubuntu
19.04 and it works too.

I use Evince for my PDF. If i choose another pdf reader like qpdfview
it's works like expected.

I tried lp command for testing and it's work:
lp -d MP-2352 -o Duplex=DuplexNoTumble testfile.pdf

I also tried to print a text document from gedit with Duplex "Long Edge"
and it's not working. I got one side page.

A document printed with LibreOffice works like expected.


We use Ubuntu 18.04 on our company and is important to fix it because we are 
now unable to print PDF documents with two-side..


Thanks.



Below some log:

...

Filetype: PDF
Neither PDF renderer command line nor Ghostscript-based renderer command line 
found
Driver does not understand PDF input, converting to PostScript
Storing temporary files in /var/spool/cups/tmp
Starting process \"pdf-to-ps\" (generation 1)
Printer make and model: NRG MP 2352 PS3

Running command line for pstops: pstops 44555 john testfile.pdf 1 \'
cups-browsed cups-browsed-dest-printer=\1137\
xxx.xxx.xxx.xxx:631/MP-2352\ Duplex=DuplexNoTumble finishings=0
InputSlot=Auto job-uuid=urn:uuid:8023a1dd-8f1f-3e58-58b2-eb77f271e0d5
JobType=Normal MediaType=Auto OutputBin=Default PageSize=A4
Password=None print-quality=0 StapleLocation=None UserCode=None pdftops-
max-image-resolution=300 pdftops-renderer=pdftops job-originating-host-
name=xxx.xxx.xxx.xxx date-time-at-creation= date-time-at-processing=
time-at-creation=1566373945 time-at-processing=1566373945\'

...

Found: %%BeginFeature: *Duplex None
Option: Duplex=None
Setting option
Found: %% FoomaticRIPOptionSetting: Duplex=None
Option: Duplex=None
Setting option

...

@PJL SET DUPLEX=OFF ...


I also ask question here but not answer until now:
https://askubuntu.com/questions/1167331/ubuntu-18-04-duplex-long-edge-printing-mode-selected-but-not-working

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

Title:
  Duplex not working upon update to 2.2.7-1ubuntu2.1

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  I am using ubuntu 18.04 LTS. After an automatic update of libcups (and
  related) from 2.2.7-1ubuntu2 to 2.2.7-1ubuntu2.1 I have been unable to
  print double-sided, e.g., printing a pdf from evince using the
  standard printer dialog. I have not changed the printer or printer
  drivers during this and before everything was working fine.

  I suspect that the option that is used for duplex printing is has changed and 
is wrong now. It seems to be "DuplexNoTumble", see
  $ lpoptions -l  | grep -i duplex
  Duplex/Duplex: *None DuplexNoTumble DuplexTumble

  After using evince and the standard printer dialog to issue a print job where 
I selected "Long Edge (standard)" for the "Two Sided" option, I see the 
following in the cups error log:
  $ cat /var/log/cups/error_log | grep -i duplex
  D [20/Jul/2018:09:30:36 +0200] [Job 39] 
argv[5]="RPSBitsPerPixel=1BitsPerPixel InputSlot=Auto 
RPSRGBcorrect=DetailBright RPSDitherType=Auto RIwmSize=36 
RIBannerPageMediaType=Auto LockedPrintPassword=None RIWMText=Confidential 
Rcmyksimulation=Off RIwmAngle=45Deg Booklet=None RPSColorRendDict=Auto 
RIPaperPolicy=PromptUser RPSBlackMode=gray noRPSColorUniversalDesign 
PageSize=A4.FullBleed JobType=Normal noRIBannerPagePrint RIPrintMode=0rhit 
MediaType=Auto RIRotateBy180=Off RIwmTextStyle=Gray RIPunch=None 
RIBannerPageInputSlot=Auto ColorModel=Gray Rimagesm=Off number-up=1 
noRPSBlackOverPrint RIOrientOvr=Off StapleLocation=None Resolution=600dpi 
DocServerPassword=None RPSColorSep=None RIFoldType=None UserCode=None noCollate 
Duplex=DuplexNoTumble RIwmFont=HelveticaB RIWatermark=Off OutputBin=Default 
job-uuid=urn:uuid:10bf31c1-fbcf-31fd-4093-04b4cc248849 finishings=53 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1532071836 
time-at-processing=1532071836"
  D [20/Jul/2018:09:30:36 +0200] [Job 39] Added option Duplex
  D [20/Jul/2018:09:30:36 +0200] [Job 39] Pondering option 
\'Duplex=DuplexNoTumble\'
  D [20/Jul/2018:09:30:36 +0200] [Job 39] Running command line for pstops: 
pstops 39 username \'filename\' 1 \'RPSBitsPerPixel=1BitsPerPixel 
InputSlot=Auto RPSRGBcorrect=DetailBright RPSDitherType=Auto RIwmSize=36 
RIBannerPageMediaType=Auto LockedPrintPassword=None RIWMText=Confidential 
Rcmyksimulation=Off RIwmAngle=45Deg Booklet=None RPSColorRendDict=Auto 
RIPaperPolicy=PromptUser RPSBlackMode=gray noRPSColorUniversalDesign 
PageSize=A4.FullBleed JobType=Normal noRIBannerPagePrint RIPrintMode=0rhit 
MediaType=Auto RIRotateBy180=Off RIwmTextStyle=Gray RIPunch=None 
RIBannerPageInputSlot=Auto ColorModel=Gray Rimagesm=Off noRPSBlackOverPrint 
RIOrientOvr=Off StapleLocation=None Resolution=600dpi

[Touch-packages] [Bug 1840995] Re: check_stamp() function of apt.systemd.daily should not assume interval is a number

2019-08-22 Thread Julian Andres Klode

Oh, yes, but that's incomplete, there's a ton of other places that need
adjusting too. In practice, the only non-number value supported is
always.

Fixed in https://salsa.debian.org/apt-
team/apt/commit/489da40d56075efaa28bfdcfb7b02b3bcc222323

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

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

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

Title:
  check_stamp() function of apt.systemd.daily should not assume interval
  is a number

Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  In the second half of the function there is

  # Calculate the interval in seconds depending on the unit specified
  if [ "${interval%s}" != "$interval" ] ; then
  interval="${interval%s}"
  elif [ "${interval%m}" != "$interval" ] ; then
  interval="${interval%m}"
  interval=$((interval*60))
  elif [ "${interval%h}" != "$interval" ] ; then
  interval="${interval%h}"
  interval=$((interval*60*60))
  else
  interval="${interval%d}"
  interval=$((interval*60*60*24))
  fi

  so, a variable might hold something like "1d", "100m", etc.

  Yet in the first there is a condition

  if [ "$interval" -eq 0 ]; then
  debug_echo "check_stamp: interval=0"
  # treat as no time has passed
  return 1
  fi

  which treats the value as a number and leads to

  /usr/lib/apt/apt.systemd.daily: 87: [: Illegal number: 20h

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

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

[Touch-packages] [Bug 1782719] Re: Duplex not working upon update to 2.2.7-1ubuntu2.1