[Touch-packages] [Bug 1859754] [NEW] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

[Hui Wang]

Public bug reported:

This ucm is only for Eoan and Bionic, for focal and future versions, we
plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on
the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by
the community, is not ready yet.

** Affects: alsa-lib (Ubuntu)
 Importance: High
 Assignee: Hui Wang (hui.wang)
 Status: New


** Tags: originate-from-1856130 somerville

** Changed in: alsa-lib (Ubuntu)
   Importance: Undecided => High

** Tags added: originate-from-1856130 somerville

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

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

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

[Touch-packages] [Bug 1855402] Re: [TGL] mesa support

[quanxian]

** Attachment added: "this is commit list for TGL mesa support, just as a 
reference."
   
https://bugs.launchpad.net/intel/+bug/1855402/+attachment/5320322/+files/tgl_commit_20200110.list

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

Title:
  [TGL] mesa support

Status in intel:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Description:

  this feature tracks the updates of mesa 3d for TGL support.

  We will update the commitid list as necessary

  Target Release: 20.04
  Target version: TBD

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

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

[Touch-packages] [Bug 1855402] Re: [TGL] mesa support

[quanxian]

** Attachment removed: "this is commit list for TGL mesa support, just as a 
reference."
   
https://bugs.launchpad.net/intel/+bug/1855402/+attachment/5320320/+files/tgl_commit_20200110.list_kernv_mesa

** Attachment added: "tgl_commit_20200110.list"
   
https://bugs.launchpad.net/intel/+bug/1855402/+attachment/5320321/+files/tgl_commit_20200110.list

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

Title:
  [TGL] mesa support

Status in intel:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Description:

  this feature tracks the updates of mesa 3d for TGL support.

  We will update the commitid list as necessary

  Target Release: 20.04
  Target version: TBD

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

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

[Touch-packages] [Bug 1855402] Re: [TGL] mesa support

[quanxian]

** Attachment added: "this is commit list for TGL mesa support, just as a 
reference."
   
https://bugs.launchpad.net/intel/+bug/1855402/+attachment/5320320/+files/tgl_commit_20200110.list_kernv_mesa

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

Title:
  [TGL] mesa support

Status in intel:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Description:

  this feature tracks the updates of mesa 3d for TGL support.

  We will update the commitid list as necessary

  Target Release: 20.04
  Target version: TBD

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

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

[Touch-packages] [Bug 1859390] Re: Blurred texts, icons and character typed on login screen after logout or switching user

[Sidney Lins]

I cant reproduce this bug anymore since last updates.

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

Title:
  Blurred texts, icons and character typed on login screen after logout
  or switching user

Status in lightdm package in Ubuntu:
  New

Bug description:
  I login to my account normally. But, when I click on "switch user"
  from app indicator, the clock in login screen will be completely
  blurred, impossible even to perceive it is a clock/time, except if I
  wait one minute so that the last number will update and it will show
  correctly (only the last number).

  If I press enter or click-up, I see the login form with the same
  problem: I can see that there are two users but they are completely
  indistinguishable and blurred. If I click on it, I can type my
  password but still blurred, even the chars I type are blurred.

  The app indicator icons are blurred too, but when I put the cursor
  over them, instantly they are fixed.

  PS: I have two enabled monitors and two users, but the second user is
  not logged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 13 00:13:45 2020
  InstallationDate: Installed on 2019-12-31 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried

[Eric Desrochers]

I reproduced the behaviour using 5.5 upstream kernel by:

1) Mounting a loop device
2) Setup frace for all loop function for capture purposes
3) Then umount the loop device

trace_pipe reveal the following:
"umount-1850 [000]  471.727511: loop_release_xfer <-__loop_clr_fd"

As cascardo mentioned earlier it might be in the way that loop device
are detached, now that I know what function to look at, I'll investigate
further.

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

Title:
  i/o error if next unused loop device is queried

Status in linux package in Ubuntu:
  Incomplete
Status in parted package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  This is reproducible in Bionic and late.

  Here's an example running 'focal':

  $ lsb_release -cs
  focal

  $ uname -r
  5.3.0-24-generic

  The error is:
  blk_update_request: I/O error, dev loop2, sector 0

  and on more recent kernel:

  kernel: [18135.185709] blk_update_request: I/O error, dev loop18,
  sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0

  
  How to trigger it:
  $ sosreport -o block

  or more precisely the cmd causing the situation inside the block plugin:
  $ parted -s $(losetup -f) unit s print

  https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52

  but if I run it on the next next unused loop device, in this case
  /dev/loop3 (which is also unused), no errors.

  While I agree that sosreport shouldn't query unused loop devices,
  there is definitely something going on with the next unused loop
  device.

  What is differentiate loop2 and loop3 and any other unused ones ?

  3 things so far I have noticed:
  * loop2 is the next unused loop device (losetup -f)
  * A reboot is needed (if some loop modification (snap install, mount loop, 
...) has been made at runtime
  * I have also noticed that loop2 (or whatever the next unused one is) have 
some stat as oppose to other unused loop devices. The stat exist already right 
after the system boot for the next unused loop device.

  /sys/block/loop2/stat
  ::
  2 0 10 0 1 0 0 0 0 0 0

  2  = number of read I/Os processed
  10 = number of sectors read
  1  = number of write I/Os processed

  Explanation of each column:
  https://www.kernel.org/doc/html/latest/block/stat.html

  while /dev/loop3 doesn't

  /sys/block/loop3/stat
  ::
  0 0 0 0 0 0 0 0 0 0 0

  Which tells me that something during the boot process most likely
  acquired (on purpose or not) the next unused loop and possibly didn't
  released it well enough.

  If loop2 is generating errors, and I install a snap, the snap squashfs
  will take loop2, making loop3 the next unused loop device.

  If I query loop3 with 'parted' right after, no errors.

  If I reboot, and query loop3 again, then no I'll have an error.

  To triggers the errors it need to be after a reboot and it only impact
  the first unused loop device available (losetup -f).

  This was tested with focal/systemd whic his very close to latest
  upstream code.

  This has been test with latest v5.5 mainline kernel as well.

  For now, I don't think it's a kernel problem, I'm more thinking of a
  userspace misbehaviour dealing with loop device (or block device) at
  boot.

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

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

[Touch-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried

[Eric Desrochers]

I reproduced the behaviour using 5.5 upstream kernel by:

1) Mounting a loop device
2) Setup frace for all loop function for capture purposes
3) Then umount the loop device

trace_pipe reveal the following:
"umount-1850  [000]    471.727511: loop_release_xfer <-__loop_clr_fd"

As cascardo mentioned earlier it might be in the way that loop device
are clear, now that I know what function to look at, I'll investigate
further.

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

Title:
  i/o error if next unused loop device is queried

Status in linux package in Ubuntu:
  Incomplete
Status in parted package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  This is reproducible in Bionic and late.

  Here's an example running 'focal':

  $ lsb_release -cs
  focal

  $ uname -r
  5.3.0-24-generic

  The error is:
  blk_update_request: I/O error, dev loop2, sector 0

  and on more recent kernel:

  kernel: [18135.185709] blk_update_request: I/O error, dev loop18,
  sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0

  
  How to trigger it:
  $ sosreport -o block

  or more precisely the cmd causing the situation inside the block plugin:
  $ parted -s $(losetup -f) unit s print

  https://github.com/sosreport/sos/blob/master/sos/plugins/block.py#L52

  but if I run it on the next next unused loop device, in this case
  /dev/loop3 (which is also unused), no errors.

  While I agree that sosreport shouldn't query unused loop devices,
  there is definitely something going on with the next unused loop
  device.

  What is differentiate loop2 and loop3 and any other unused ones ?

  3 things so far I have noticed:
  * loop2 is the next unused loop device (losetup -f)
  * A reboot is needed (if some loop modification (snap install, mount loop, 
...) has been made at runtime
  * I have also noticed that loop2 (or whatever the next unused one is) have 
some stat as oppose to other unused loop devices. The stat exist already right 
after the system boot for the next unused loop device.

  /sys/block/loop2/stat
  ::
  2 0 10 0 1 0 0 0 0 0 0

  2  = number of read I/Os processed
  10 = number of sectors read
  1  = number of write I/Os processed

  Explanation of each column:
  https://www.kernel.org/doc/html/latest/block/stat.html

  while /dev/loop3 doesn't

  /sys/block/loop3/stat
  ::
  0 0 0 0 0 0 0 0 0 0 0

  Which tells me that something during the boot process most likely
  acquired (on purpose or not) the next unused loop and possibly didn't
  released it well enough.

  If loop2 is generating errors, and I install a snap, the snap squashfs
  will take loop2, making loop3 the next unused loop device.

  If I query loop3 with 'parted' right after, no errors.

  If I reboot, and query loop3 again, then no I'll have an error.

  To triggers the errors it need to be after a reboot and it only impact
  the first unused loop device available (losetup -f).

  This was tested with focal/systemd whic his very close to latest
  upstream code.

  This has been test with latest v5.5 mainline kernel as well.

  For now, I don't think it's a kernel problem, I'm more thinking of a
  userspace misbehaviour dealing with loop device (or block device) at
  boot.

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

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

[Touch-packages] [Bug 1859739] [NEW] package ubuntu-minimal 1.361.4 failed to install/upgrade: 依赖关系问题 - 仍未被配置

[zhang]

Public bug reported:

when I open the system,it would tell me this question

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ubuntu-minimal 1.361.4
ProcVersionSignature: Ubuntu 4.15.0-74.83~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-74-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
Date: Wed Jan 15 10:12:17 2020
ErrorMessage: 依赖关系问题 - 仍未被配置
InstallationDate: Installed on 2019-12-17 (28 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32
SourcePackage: ubuntu-meta
Title: package ubuntu-minimal 1.361.4 failed to install/upgrade: 依赖关系问题 - 仍未被配置
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package ubuntu-minimal 1.361.4 failed to install/upgrade: 依赖关系问题 -
  仍未被配置

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  when I open the system,it would tell me this question

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-minimal 1.361.4
  ProcVersionSignature: Ubuntu 4.15.0-74.83~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Wed Jan 15 10:12:17 2020
  ErrorMessage: 依赖关系问题 - 仍未被配置
  InstallationDate: Installed on 2019-12-17 (28 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: ubuntu-meta
  Title: package ubuntu-minimal 1.361.4 failed to install/upgrade: 依赖关系问题 - 
仍未被配置
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1859740] [NEW] package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 10

[zhang]

Public bug reported:

when I open the system,it would tell me this question

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: rsyslog 8.16.0-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-74.83~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-74-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
Date: Wed Jan 15 10:12:17 2020
ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 10
InstallationDate: Installed on 2019-12-17 (28 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32
SourcePackage: rsyslog
Title: package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 10
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.logrotate.d.rsyslog: 2016-02-03T18:55:28

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


** Tags: amd64 apport-package xenial

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

Title:
  package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade: 子进程 已安装
  post-installation 脚本 返回错误状态 10

Status in rsyslog package in Ubuntu:
  New

Bug description:
  when I open the system,it would tell me this question

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: rsyslog 8.16.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-74.83~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Wed Jan 15 10:12:17 2020
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 10
  InstallationDate: Installed on 2019-12-17 (28 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: rsyslog
  Title: package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 10
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.logrotate.d.rsyslog: 2016-02-03T18:55:28

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

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

[Touch-packages] [Bug 1838838] Re: username is not saved in openconnect connection dialog

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  username is not saved in openconnect connection dialog

Status in GNOME Shell:
  New
Status in NetworkManager:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Same issue as https://bugs.launchpad.net/ubuntu/+source/network-
  manager-openconnect/+bug/1609700

  This was marked resolved. The report of its reappearance in Ubuntu
  19.04 and 19.10 has not been acknowledged.

  This was working for me in 18.10, but a fresh install of 19.04 and
  19.10 show that it is back. The password is saved when the option to
  save passwords is selected, but the username must be entered manually
  upon connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1838838/+subscriptions

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

[Touch-packages] [Bug 1859730] Re: Xorg freeze

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

** Package changed: xorg (Ubuntu) => ubuntu

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

Title:
  Xorg freeze

Status in Ubuntu:
  Incomplete

Bug description:
  ack please..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.4.11-050411-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jan 14 20:17:26 2020
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed
   backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  InstallationDate: Installed on 2020-01-13 (1 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0029 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 7390
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic 
root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0377MH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1859468] Re: dialog windows spanning across dual monitors poorly

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: multimonitor

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

Title:
  dialog windows spanning across dual monitors poorly

Status in gnome-shell package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10


  
  apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu12
Candidate: 1:7.7+19ubuntu12
Version table:
   *** 1:7.7+19ubuntu12 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status


  
  the dialog windows are spanning across my two monitors.

  1 open dialog for saving file
  2 window opens and spans across the two monitors
  3 user buttons open/cancel/save are hidden in the UI. The task bar on the 
left side is covering/hiding the dialog window buttons

  
  desired behavior
  dialog windows fit INSIDE a single monitor UI


  please see the attached screenshots

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 13 15:41:37 2020
  DistUpgraded: 2019-10-23 09:33:56,809 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:84ca]
  InstallationDate: Installed on 2015-08-23 (1603 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (82 days ago)
  dmi.bios.date: 07/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Aug 20 17:24:57 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859468/+subscriptions

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

[Touch-packages] [Bug 1838838] Re: username is not saved in openconnect connection dialog

[Daniel van Vugt]

** Also affects: network-manager via
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/328
   Importance: Unknown
   Status: Unknown

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2105
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/2105

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/2105
   Importance: Unknown
   Status: Unknown

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

Title:
  username is not saved in openconnect connection dialog

Status in GNOME Shell:
  Unknown
Status in NetworkManager:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Same issue as https://bugs.launchpad.net/ubuntu/+source/network-
  manager-openconnect/+bug/1609700

  This was marked resolved. The report of its reappearance in Ubuntu
  19.04 and 19.10 has not been acknowledged.

  This was working for me in 18.10, but a fresh install of 19.04 and
  19.10 show that it is back. The password is saved when the option to
  save passwords is selected, but the username must be entered manually
  upon connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1838838/+subscriptions

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

[Touch-packages] [Bug 1859730] Re: Xorg freeze

[Chris Guiver]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Unfortunately, we cannot work on this bug because your description
didn't include enough information. You may find it helpful to read "How
to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

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

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

Thanks!

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  ack please..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.4.11-050411-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jan 14 20:17:26 2020
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed
   backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  InstallationDate: Installed on 2020-01-13 (1 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0029 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 7390
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic 
root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0377MH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1859730] [NEW] Xorg freeze

[Alonso]

Public bug reported:

ack please..

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 5.4.11-050411-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CompositorRunning: None
Date: Tue Jan 14 20:17:26 2020
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed
 backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Very infrequently
GraphicsCard:
 Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0962]
InstallationDate: Installed on 2020-01-13 (1 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
Lsusb:
 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 8087:0029 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 7390
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic 
root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.0
dmi.board.name: 0377MH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390
dmi.product.sku: 0962
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  ack please..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.4.11-050411-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jan 14 20:17:26 2020
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed
   backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  InstallationDate: Installed on 2020-01-13 (1 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0029 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 7390
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic 
root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell 

[Touch-packages] [Bug 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device

[Mauricio Faria de Oliveira]

The autopkgtest failures for focal are unrelated to this upload.

- piuparts/1.1.0:

There's changes from piuparts 1.1.0 to 1.1.1 (released a few hours ago)
that resolved the issues, as seen in the autopkgtests page for piuparts.
Requested re-runs.

- openjdk:

The failing test timed-out on armhf and is reported as FLAKY in the log; 
requested re-run.
(openjdk probably is not checking for XFS filesystems on bcache devices :)

  autopkgtest [09:28:36]: ERROR: timed out on command "<...>
  autopkgtest [09:28:36]: test jdk: ---]
  autopkgtest [09:28:40]: test jdk:  - - - - - - - - - - results - - - - - - - 
- - -
  jdk  FLAKY timed out

- cmake-extras/1.3+17.04.20170310-5:

There's changes in focal-proposed (cmake-extras 1.3+17.04.20170310-7) that 
address autopkgtest failures, but looking at its test log, it fixed 1 of 2 
failures (fixed 'copyrighttest' but not 'includechecker', and regressed 
'findgmock'. so _not_ requesting re-runs. 
Thus apparently not quite there yet; but anyway, not XFS/bcache either.

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

Title:
  libblkid: no bcache UUID due to ambivalent detection of bcache and
  xfs_external_log for regular xfs in bcache backing device

Status in util-linux package in Ubuntu:
  In Progress
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 source package in Eoan:
  In Progress
Status in util-linux source package in Focal:
  In Progress
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]

   * Users with an XFS filesystem on top of bcache
     (this is seen on some ceph, cloud deployments)
     might fail to reference the bcache device by
     UUID or other udev properties.

   * The journal of the regular XFS filesystem in
     the bcache device is incorrectly detected as
     an XFS external log; so two superblocks are
     detected (bcache and xfs_external_log).

   * Thus blkid fails with ambivalent superblocks
     detected then doesn't provide the usual udev
     properties (UUID, etc.)

   * The fix improves the probe function for XFS
     external log so it detects it's regular XFS
     and bails out.

  [Test Case]

   * See test steps detailed in comment #7 and later.
     - Create an XFS filesystem with the journal/log
   in the beginning of the bcache device (< 256K).
     - Stop the bcache device.
     - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'.

     $ sudo make-bcache -B $BACKING_DEV
     $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV
     $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop
     $ sudo blkid -o udev -p $BACKING_DEV

  [Regression Potential]

   * The patch only changes the detection function
     for XFS external log to be more general about
     the sector where the magic of regular XFS may
     be found (which is shifted inside the bcache.)

   * It still checks at sector zero (the only one
     checked previously), so this behavior didn't
     change.

   * Possible regressions are actual XFS external
     log devices that are not anymore detected as
     such. (Although that would probably indicate
     a different bug in libblkid.)

  [Other Info]
   * upstream commit:
     
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424

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

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

[Touch-packages] [Bug 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device

[Mauricio Faria de Oliveira]

The uploads to stable releases are blocked on LP#1845529 currently in 
eoan-proposed.
It was pending analysis of autopkgtest failures as well, and I provided those 
today.
(cyphermox removed the tag 'verification-needed' from that bug, so maybe it'll 
move.)

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

Title:
  libblkid: no bcache UUID due to ambivalent detection of bcache and
  xfs_external_log for regular xfs in bcache backing device

Status in util-linux package in Ubuntu:
  In Progress
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 source package in Eoan:
  In Progress
Status in util-linux source package in Focal:
  In Progress
Status in util-linux package in Debian:
  Unknown

Bug description:
  [Impact]

   * Users with an XFS filesystem on top of bcache
     (this is seen on some ceph, cloud deployments)
     might fail to reference the bcache device by
     UUID or other udev properties.

   * The journal of the regular XFS filesystem in
     the bcache device is incorrectly detected as
     an XFS external log; so two superblocks are
     detected (bcache and xfs_external_log).

   * Thus blkid fails with ambivalent superblocks
     detected then doesn't provide the usual udev
     properties (UUID, etc.)

   * The fix improves the probe function for XFS
     external log so it detects it's regular XFS
     and bails out.

  [Test Case]

   * See test steps detailed in comment #7 and later.
     - Create an XFS filesystem with the journal/log
   in the beginning of the bcache device (< 256K).
     - Stop the bcache device.
     - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'.

     $ sudo make-bcache -B $BACKING_DEV
     $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV
     $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop
     $ sudo blkid -o udev -p $BACKING_DEV

  [Regression Potential]

   * The patch only changes the detection function
     for XFS external log to be more general about
     the sector where the magic of regular XFS may
     be found (which is shifted inside the bcache.)

   * It still checks at sector zero (the only one
     checked previously), so this behavior didn't
     change.

   * Possible regressions are actual XFS external
     log devices that are not anymore detected as
     such. (Although that would probably indicate
     a different bug in libblkid.)

  [Other Info]
   * upstream commit:
     
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424

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

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

[Touch-packages] [Bug 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering

[rtimai]

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

ADDITIONAL INFORMATION ABOUT WINDOW TITLEBAR BUTTONS AND TOP BAR BUTTONS
(GNOME-TWEAK-TOOL ONLY)

If you have installed Unite (a window decoration multi-function
extension, store in .local/share/gnome-
shell/extensions/un...@hardpixel.eu):

Window titlebar and Top Bar buttons do not "slide" off the titlebars out
of sight if buttons are configured to display in Unite > Appearance >
Top bar window buttons position > RIGHT or LAST or AUTO

In the GNOME-tweak-tool Main Menu, the setting for Window Titlebars >
Placement  may also introduce a conflict in the way window button
animations occur in GNOME-tweak if they don't match the Unite settings
(however, Unite includes an AUTO setting which might be used to avoid
this.)

As is warned in the Ubuntu Software tool, GNOME-shell-extensions can
cause settings conflicts, depending on which extensions one is running.
So your mileage may vary. Notably, the options in some of the extensions
displayed in GNOME-tweak-tool are no longer available by clicking on the
gear icon. -- However, I found that these options can be changed in
Ubuntu Software > Addons > Shell Extensions > Extensions Settings
(button.) GNOME-shell-integration with extensions in web browsers have
been disabled in Ubuntu 19.10, and now GNOME-tweak-tool seems to be
losing functionality as well, all being superceded by the Ubuntu
Software tool.

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

Title:
  gnome-tweak-tool window keeps flickering on cursor hovering

Status in gnome-tweaks package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  the gnome-tweak-tool window keeps flickering abnormally. this might be
  a bug as i have seen somebody else mention the issue somewhere in the
  internet.

  i do have the screencast of the phenomenon i can send it to you for
  the review of the problem i am facing.

  i am on ubuntu 19.10 system installed via bootable usb. before i had
  interrupted network upgrade of the system which was recovered via grub
  recovery mode. since i thought the flickering was due to all this, i
  fresh installed the system via bootable usb.

  still the problem is persistent and its abnormal irrespective of the 
animation button turned on or off.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-26 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Tags:  wayland-session eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+subscriptions

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

[Touch-packages] [Bug 815562] Re: Difficult to know why we can't find signing_key_fingerprint for a PPA

[Graham Leggett]

9 years later and this bug is still unfixed when building from Bionic.

The error

Error: signing key fingerprint does not exist
Failed to add key.

might be a statement of fact, but it doesn't tell me what I must do, or
whether my system is broken or not, or what action I must take.

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

Title:
  Difficult to know why we can't find signing_key_fingerprint for a PPA

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  I've created a PPA, but I haven't uploaded anything yet. On my development 
machine I tried to add the PPA using apt-apt-repository and I got the following 
error message: 
  «Error: can't find signing_key_fingerprint at 
https://launchpad.net/api/1.0/~joerlend.schinstad/+archive/testing»

  I thought I'd done something wrong, so I asked in #Launchpad where it
  was explained to me that keys aren't generated until the first upload.
  That sounds reasonable, but I think it should be easier to know why
  add-apt-repository fails. I also think it should be explained in pages
  like this one:
  https://help.launchpad.net/Packaging/PPA/InstallingSoftware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/815562/+subscriptions

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

[Touch-packages] [Bug 815562] Re: Difficult to know why we can't find signing_key_fingerprint for a PPA

[Launchpad Bug Tracker]

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

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  Difficult to know why we can't find signing_key_fingerprint for a PPA

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  I've created a PPA, but I haven't uploaded anything yet. On my development 
machine I tried to add the PPA using apt-apt-repository and I got the following 
error message: 
  «Error: can't find signing_key_fingerprint at 
https://launchpad.net/api/1.0/~joerlend.schinstad/+archive/testing»

  I thought I'd done something wrong, so I asked in #Launchpad where it
  was explained to me that keys aren't generated until the first upload.
  That sounds reasonable, but I think it should be easier to know why
  add-apt-repository fails. I also think it should be explained in pages
  like this one:
  https://help.launchpad.net/Packaging/PPA/InstallingSoftware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/815562/+subscriptions

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

[Touch-packages] [Bug 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`

[Mathieu Trudel-Lapierre]

** Tags removed: verification-needed

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

Title:
  bash completion shows `awk: line 18: function gensub never defined` on
  `umount /dev/`

Status in bash-completion package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in util-linux package in Ubuntu:
  Fix Released
Status in bash-completion source package in Eoan:
  Invalid
Status in gawk source package in Eoan:
  Invalid
Status in mawk source package in Eoan:
  Invalid
Status in ubuntu-meta source package in Eoan:
  Invalid
Status in util-linux source package in Eoan:
  Fix Committed
Status in bash-completion source package in Focal:
  Invalid
Status in gawk source package in Focal:
  Invalid
Status in mawk source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Invalid
Status in util-linux source package in Focal:
  Fix Released
Status in Debian:
  Confirmed

Bug description:
  [Impact]
  Any user attempting to tab-complete from "umount /dev/" when running the bash 
shell.

  [Test cases]
  Steps to reproduce:
  1. Install Ubuntu MATE 19.10 using minimal desktop option
  2. Open terminal and enter `umount /dev/s` and then hit 

  Expected result:
  * bash completion works as expected

  Actual results:
  * bash completion does not work :

  $ umount /dev/awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined

  $ umount /meawk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined

  
  [Regression potential]
  Since it is limited to a single file 
(/usr/share/bash-completion/completions/umount) and affects only it, as well as 
given that it currently does not work, I estimate this as a low risk change. 
Things to look out for as a regression would be if another previously-working 
completion would fail to work (ie. what if mount stops completing correctly, 
and works again if the fix is backed out?).

  ---

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bash-completion 1:2.9-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Sep 26 18:46:59 2019
  Dependencies:

  InstallationDate: Installed on 2019-09-26 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+subscriptions

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

[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

[Dan Streetman]

as disco reaches EOL next week, marking this as wontfix for disco.

** Changed in: systemd (Ubuntu Disco)
   Status: Confirmed => Won't Fix

** Changed in: keepalived (Ubuntu Disco)
   Status: Confirmed => Won't Fix

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

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in Keepalived Charm:
  New
Status in netplan:
  Confirmed
Status in heartbeat package in Ubuntu:
  Won't Fix
Status in keepalived package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in keepalived source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed
Status in keepalived source package in Disco:
  Won't Fix
Status in systemd source package in Disco:
  Won't Fix
Status in keepalived source package in Eoan:
  In Progress
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  - ALL related HA software has a small problem if interfaces are being
  managed by systemd-networkd: nic restarts/reconfigs are always going
  to wipe all interfaces aliases when HA software is not expecting it to
  (no coordination between them.

  - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
  smarter in this case because it has a service monitor that will
  restart the virtual IP resource, in affected node & nic, before
  considering a real failure, but other HA service might consider a real
  failure when it is not.

  [test case]

  - comment #14 is a full test case: to have 3 node pacemaker, in that
  example, and cause a networkd service restart: it will trigger a
  failure for the virtual IP resource monitor.

  - other example is given in the original description for keepalived.
  both suffer from the same issue (and other HA softwares as well).

  [regression potential]

  - this backports KeepConfiguration parameter, which adds some
  significant complexity to networkd's configuration and behavior, which
  could lead to regressions in correctly configuring the network at
  networkd start, or incorrectly maintaining configuration at networkd
  restart, or losing network state at networkd stop.

  - Any regressions are most likely to occur during networkd start,
  restart, or stop, and most likely to involve missing or incorrect ip
  address(es).

  - the change is based in upstream patches adding the exact feature we
  needed to fix this issue & it will be integrated with a netplan change
  to add the needed stanza to systemd nic configuration file
  (KeepConfiguration=)

  [other info]

  original description:
  ---

  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth2:
  addresses:
    - 12.13.14.18/29
    - 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # IP
  smtp_connect_timeout 30  # integer, seconds
  router_id system3  # string identifying the machine,
   # (doesn't have to be hostname).
  vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
  vrrp_mcast_group6 ff02::12   # optional, default ff02::12
  enable_traps # enable SNMP traps
  }
  

[Touch-packages] [Bug 1859683] [NEW] cannot find network printer the add printer dialog just shows CUPS

[John Howard]

Public bug reported:

the WP4535 printer in the logs is for a printer at home. I am at work
and the printer here is not showing in the find printer dialog. It can
also not be found by ip address however I can ping the printer in
terminal. Other Ubuntu users on the same network can find the printer
but they are using ubuntu 18.04 while I am on 19.10

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cups 2.2.12-2ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CupsErrorLog:
 E [14/Jan/2020:17:56:54 +] File \"/usr/lib/cups/daemon/cups-deviced\" not 
available: No such file or directory
 E [14/Jan/2020:17:56:54 +] [Client 7] Returning IPP 
server-error-internal-error for CUPS-Get-Devices (no URI) from localhost.
 E [14/Jan/2020:18:19:51 +] Unable to remove /run/cups/certs/0!
 E [14/Jan/2020:18:20:37 +] File \"/usr/lib/cups/daemon/cups-deviced\" not 
available: No such file or directory
 E [14/Jan/2020:18:20:37 +] [Client 8] Returning IPP 
server-error-internal-error for CUPS-Get-Devices (no URI) from localhost.
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 14 18:39:35 2020
InstallationDate: Installed on 2019-12-19 (26 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lpstat: device for EPSON_WP_4535_Series: implicitclass://EPSON_WP_4535_Series/
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:671b Microdia Integrated_Webcam_HD
 Bus 001 Device 002: ID 27c6:538c Goodix FingerPrint
 Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 7386
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_WP_4535_Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON_WP_4535_Series.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=f23e8b57-647a-4358-896b-42314520f118 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/29/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.0
dmi.board.name: 0THMD7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd05/29/2019:svnDellInc.:pnInspiron7386:pvr:rvnDellInc.:rn0THMD7:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7386
dmi.product.sku: 0894
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug eoan

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

Title:
  cannot find network printer the add printer dialog just shows CUPS

Status in cups package in Ubuntu:
  New

Bug description:
  the WP4535 printer in the logs is for a printer at home. I am at work
  and the printer here is not showing in the find printer dialog. It can
  also not be found by ip address however I can ping the printer in
  terminal. Other Ubuntu users on the same network can find the printer
  but they are using ubuntu 18.04 while I am on 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CupsErrorLog:
   E [14/Jan/2020:17:56:54 +] File \"/usr/lib/cups/daemon/cups-deviced\" 
not available: No such file or directory
   E [14/Jan/2020:17:56:54 +] [Client 7] Returning IPP 
server-error-internal-error for CUPS-Get-Devices (no URI) from localhost.
   E [14/Jan/2020:18:19:51 +] Unable to remove /run/cups/certs/0!
   E [14/Jan/2020:18:20:37 +] File \"/usr/lib/cups/daemon/cups-deviced\" 
not available: No such file or directory
   E [14/Jan/2020:18:20:37 +] [Client 8] Returning IPP 
server-error-internal-error for CUPS-Get-Devices (no URI) from localhost.
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 14 18:39:35 2020
  InstallationDate: Installed on 2019-12-19 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for EPSON_WP_4535_Series: implicitclass://EPSON_WP_4535_Series/
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671b Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538c Goodix FingerPrint
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7386
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON_WP_4535_Series.ppd'] failed with exit code 2: grep: 

[Touch-packages] [Bug 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target

[Bug Watch Updater]

** Changed in: resolvconf (Debian)
   Status: Fix Committed => Fix Released

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in resolvconf source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in resolvconf source package in Yakkety:
  Fix Released
Status in resolvconf package in Debian:
  Fix Released

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

  [SRU]
  Fix: switch resolvconf.service to run Before=network-pre.target and add 
Wants=network-pre.target.  Add a Before=network-online.target to 
systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf 
with DNS config prior to reaching network-online.target.

  Regression potential: Low. networkd is not widely being used outside
  of netplan/snappy in xenial.

  Test Case:
    lxc launch ubuntu-daily:xenial x1
    lxc exec x1 /bin/bash

    # make sure you're on systemd-229-4ubuntu17
    apt update && apt install -y systemd

    # enable networkd and netplan
    apt install -y nplan
  cat < /etc/netplan/nplan.yaml
  network:
  version: 2
  ethernets:
  all-en:
  match:
  name: "en*"
  dhcp4: true
  all-eth:
  match:
  name: "eth*"
  dhcp4: true
  EOF
    sed -i.orig -e 's/^source/# source/' /etc/network/interfaces

    netplan generate

    # make sure cloud-init.service uses networkd
    sed -i.orig -e '/After=networking.service/a 
After=systemd-networkd-wait-online.service' 
/lib/systemd/system/cloud-init.service

    reboot

    # check that the order of execution with:
    journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd-resolvconf-update.service

    # the order should be:
  1. resolvconf:  systemd[1]: Started Nameserver information manager.
  2. systemd-networkd-wait-online.service:  systemd[1]: Starting Wait for 
Network to be Configured...
  3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update 
resolvconf for networkd DNS.
  4. network-online.target: systemd[1]: Reached target Network is Online.

  === BAD OUTPUT ===
  On a failing system, Reached target Network is Online occurs before (1, 2, or 
3) above, like this output:

  Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
  Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.

  === GOOD OUTPUT ===
  On a passing system, Reached target Network is Online occurs after 1, 2, and 
3.

  Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
  Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be 
Configured...
  Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
  Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be 
Configured.
  Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd 
DNS...
  Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd 
DNS.
  Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online.

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

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

[Touch-packages] [Bug 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`

[Mauricio Faria de Oliveira]

Looked at the remaining autopkgtest failures for util-linux/eoan [1]:

util-linux
Regression in autopkgtest for sbd (i386): test log
Regression in autopkgtest for gfs2-utils (i386): test log
Regression in autopkgtest for network-manager (ppc64el): test log

- sbd/i386:
  passed with retries [2]

- network-manager/ppc64el:
  passed with retries [3]

- gfs2-utils/i386:
  failure is unrelated to this change.

  there's an ioctl() failing w/ ENOTTY from the kernel (see strace below)
  so it's unrelated to this change to bash autocompletion.

  it's reproducible w/ util-linux from eoan-updates,
  thus not a regression from eoan-proposed.

  i'll try to look at this, 
  but this should not block this SRU any longer.

root@autopkgtest:~# strace -e ioctl gfs2_jadd -j 1 /mnt2
ioctl(5, FS_IOC32_GETFLAGS or FS_IOC_GETFLAGS, 0xffb9d568) = -1 ENOTTY 
(Inappropriate ioctl for device)
ioctl(6, TCGETS, {B9600 opost isig icanon echo ...}) = 0
GETFLAGS: Inappropriate ioctl for device
+++ exited with 1 +++

root@autopkgtest:~# dpkg -s util-linux | grep -i version:
Version: 2.34-0.1ubuntu2

cheers,
Mauricio


[1] https://people.canonical.com/~ubuntu-archive/pending-sru.html

[2] https://autopkgtest.ubuntu.com/packages/sbd/eoan/i386
sbd [eoan/i386]
1.4.0-18-g5e3283c-1ubuntu1  util-linux/2.34-0.1ubuntu2.12020-01-14 
13:02:27 UTC 0h 16m 07s  mfo pass

[3] https://autopkgtest.ubuntu.com/packages/network-manager/eoan/ppc64el
network-manager [eoan/ppc64el]
1.20.4-2ubuntu2 util-linux/2.34-0.1ubuntu2.12020-01-14 13:06:12 UTC 
0h 20m 00s  mfo pass

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

Title:
  bash completion shows `awk: line 18: function gensub never defined` on
  `umount /dev/`

Status in bash-completion package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in util-linux package in Ubuntu:
  Fix Released
Status in bash-completion source package in Eoan:
  Invalid
Status in gawk source package in Eoan:
  Invalid
Status in mawk source package in Eoan:
  Invalid
Status in ubuntu-meta source package in Eoan:
  Invalid
Status in util-linux source package in Eoan:
  Fix Committed
Status in bash-completion source package in Focal:
  Invalid
Status in gawk source package in Focal:
  Invalid
Status in mawk source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Invalid
Status in util-linux source package in Focal:
  Fix Released
Status in Debian:
  Confirmed

Bug description:
  [Impact]
  Any user attempting to tab-complete from "umount /dev/" when running the bash 
shell.

  [Test cases]
  Steps to reproduce:
  1. Install Ubuntu MATE 19.10 using minimal desktop option
  2. Open terminal and enter `umount /dev/s` and then hit 

  Expected result:
  * bash completion works as expected

  Actual results:
  * bash completion does not work :

  $ umount /dev/awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined

  $ umount /meawk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined
  awk: line 18: function gensub never defined

  
  [Regression potential]
  Since it is limited to a single file 
(/usr/share/bash-completion/completions/umount) and affects only it, as well as 
given that it currently does not work, I estimate this as a low risk change. 
Things to look out for as a regression would be if another previously-working 
completion would fail to work (ie. what if mount stops completing correctly, 
and works again if the fix is backed out?).

  ---

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bash-completion 1:2.9-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Sep 26 18:46:59 2019
  Dependencies:

  InstallationDate: Installed on 2019-09-26 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+subscriptions

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

[Touch-packages] [Bug 1851695] Re: DEP8 failure/regression in nspr on arm64 and armhf

[Andreas Hasenack]

It's a force-badtest across the board:

ubuntu-release:force-badtest notary/0.6.1~ds1-4


revno: 4077
committer: Steve Langasek 
branch nick: hints-ubuntu
timestamp: Wed 2019-11-13 15:35:28 -0800
message:
  badtest notary

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

Title:
  DEP8 failure/regression in nspr on arm64 and armhf

Status in notary package in Ubuntu:
  New
Status in nspr package in Ubuntu:
  Invalid
Status in notary package in Debian:
  Confirmed

Bug description:
  nspr 0.6.1~ds1-4 is failing DEP8 test in arm64 and armhf:

  
  autopkgtest [09:46:25]: test command1: /usr/bin/dh_golang_autopkgtest
  autopkgtest [09:46:25]: test command1: [---
  [info] Testing github.com/theupdateframework/notary...
  [info] Source code installed by binary package, overriding 
dh_auto_configure...
  [info] Disabling existing override_dh_auto_configure...
  dh build --builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build \
--buildsystem=golang \
--with=golang
 dh_update_autotools_config 
-O--builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build 
-O--buildsystem=golang
 dh_autoreconf 
-O--builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build 
-O--buildsystem=golang
 debian/rules override_dh_auto_configure
  make[1]: Entering directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp'
  mkdir -p "_build"
  cp -a /usr/share/gocode/src "_build"
  make[1]: Leaving directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp'
 debian/rules override_dh_auto_build
  make[1]: Entering directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp'
  dh_auto_build -- -tags "pkcs11"
cd _build && go install 
-gcflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" 
-asmflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" 
-v -p 1 -tags pkcs11 github.com/theupdateframework/notary 
github.com/theupdateframework/notary/client 
github.com/theupdateframework/notary/client/changelist 
github.com/theupdateframework/notary/cmd/escrow 
github.com/theupdateframework/notary/cmd/notary 
github.com/theupdateframework/notary/cmd/notary-server 
github.com/theupdateframework/notary/cmd/notary-signer 
github.com/theupdateframework/notary/cryptoservice 
github.com/theupdateframework/notary/passphrase 
github.com/theupdateframework/notary/proto 
github.com/theupdateframework/notary/server 
github.com/theupdateframework/notary/server/errors 
github.com/theupdateframework/notary/server/handlers 
github.com/theupdateframework/notary/server/snapshot 
github.com/theupdateframework/notary/server/storage 
github.com/theupdateframework/notary/server/timestamp 
github.com/theupdateframework/notary/signer 
github.com/theupdateframework/notary/signer/api 
github.com/theupdateframework/notary/signer/client 
github.com/theupdateframework/notary/signer/keydbstore 
github.com/theupdateframework/notary/storage 
github.com/theupdateframework/notary/storage/rethinkdb 
github.com/theupdateframework/notary/trustmanager 
github.com/theupdateframework/notary/trustmanager/remoteks 
github.com/theupdateframework/notary/trustmanager/yubikey 
github.com/theupdateframework/notary/trustpinning 
github.com/theupdateframework/notary/tuf 
github.com/theupdateframework/notary/tuf/data 
github.com/theupdateframework/notary/tuf/signed 
github.com/theupdateframework/notary/tuf/testutils 
github.com/theupdateframework/notary/tuf/testutils/interfaces 
github.com/theupdateframework/notary/tuf/testutils/keys 
github.com/theupdateframework/notary/tuf/utils 
github.com/theupdateframework/notary/tuf/validation 
github.com/theupdateframework/notary/utils 
github.com/theupdateframework/notary/version
  src/github.com/docker/distribution/digestset/set.go:9:2: cannot find package 
"github.com/opencontainers/go-digest" in any of:

/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/docker/distribution/vendor/github.com/opencontainers/go-digest
 (vendor tree)
/usr/lib/go-1.12/src/github.com/opencontainers/go-digest (from $GOROOT)

/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/opencontainers/go-digest
 (from $GOPATH)
  src/github.com/docker/distribution/blobs.go:13:2: cannot find package 
"github.com/opencontainers/image-spec/specs-go/v1" in any of:

/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/docker/distribution/vendor/github.com/opencontainers/image-spec/specs-go/v1
 (vendor tree)
/usr/lib/go-1.12/src/github.com/opencontainers/image-spec/specs-go/v1 
(from $GOROOT)

/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/opencontainers/image-spec/specs-go/v1
 (from $GOPATH)
  dh_auto_build: cd _build && go install 
-gcflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" 

[Touch-packages] [Bug 1831459] Re: 'storage' test needs to wait for systemd-cryptsetup to be active before stopping it

[Dan Streetman]

** Changed in: systemd (Ubuntu Cosmic)
   Status: In Progress => Won't Fix

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

Title:
  'storage' test needs to wait for systemd-cryptsetup to be active
  before stopping it

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

Bug description:
  [impact]

  test case fails because it does not wait for the service to become
  active before stopping it, resulting in failure to rmmod the
  scsi_debug module because it's still in use.

  [test case]

  check 'storage' test results for systemd in autopkgtest logs, e.g.:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/s/systemd/20190601_160043_a5281@/log.gz

  [regression potential]

  low; test case fix only.

  [other info]

  detected and reported by @cascardo in bug 1814373 comment 4 and 5, but
  separate (non-test) systemd bugfix uploaded for that bug so opening
  this bug to track fixing the test case.

  larger fixes/improvements to 'storage' testcase in bug 1829347, but
  those rejected.

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

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

[Touch-packages] [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal

[Dariusz Gadomski]

** No longer affects: gnome-terminal (Ubuntu)

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

Title:
  pam_group.so is not evaluated by gnome-terminal

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Won't Fix
Status in gnome-terminal source package in Eoan:
  New
Status in systemd source package in Eoan:
  In Progress

Bug description:
  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1757091] Re: systemctl enable lightdm

[Dirk Hagedorn]

It's 2020 now and I can confirm this bug for Ubuntu 18.04.3 LTS, too.

Calling "/lib/systemd/systemd-sysv-install enable lightdm" directly
worked for me.

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

Title:
  systemctl enable lightdm

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Synchronizing state of lightdm.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
  Executing: /lib/systemd/systemd-sysv-install enable lightdm
  The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
  settings in the [Install] section, and DefaultInstance for template units).
  This means they are not meant to be enabled using systemctl.
  Possible reasons for having this kind of units are:
  1) A unit may be statically enabled by being symlinked from another unit's
 .wants/ or .requires/ directory.
  2) A unit's purpose may be to act as a helper for some other unit which has
 a requirement dependency on it.
  3) A unit may be started when needed via activation (socket, path, timer,
 D-Bus, udev, scripted systemctl call, ...).
  4) In case of template units, the unit is meant to be enabled with some
 instance name specified.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: lightdm 1.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Tue Mar 20 11:44:46 2018
  InstallationDate: Installed on 2018-01-22 (57 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1831459] Re: 'storage' test needs to wait for systemd-cryptsetup to be active before stopping it

[Dan Streetman]

as disco is EOL next week, marking this won't fix for disco.

** Changed in: systemd (Ubuntu Disco)
   Status: In Progress => Won't Fix

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

Title:
  'storage' test needs to wait for systemd-cryptsetup to be active
  before stopping it

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

Bug description:
  [impact]

  test case fails because it does not wait for the service to become
  active before stopping it, resulting in failure to rmmod the
  scsi_debug module because it's still in use.

  [test case]

  check 'storage' test results for systemd in autopkgtest logs, e.g.:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/s/systemd/20190601_160043_a5281@/log.gz

  [regression potential]

  low; test case fix only.

  [other info]

  detected and reported by @cascardo in bug 1814373 comment 4 and 5, but
  separate (non-test) systemd bugfix uploaded for that bug so opening
  this bug to track fixing the test case.

  larger fixes/improvements to 'storage' testcase in bug 1829347, but
  those rejected.

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

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

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

[Dan Streetman]

as disco is EOL next week, marking this won't fix for disco.

** Changed in: systemd (Ubuntu Disco)
   Status: In Progress => Won't Fix

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

Title:
  networkd should allow configuring IPV6 MTU

Status in systemd:
  Unknown
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in cloud-init source package in Disco:
  New
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Won't Fix
Status in cloud-init source package in Eoan:
  New
Status in netplan.io source package in Eoan:
  Fix Released
Status in systemd source package in Eoan:
  In Progress
Status in cloud-init source package in Focal:
  Confirmed
Status in netplan.io source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  In Progress

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

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

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its larger header overhead.

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

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

[Touch-packages] [Bug 1831787] Re: Bogus routes after DHCP lease change

[Dan Streetman]

as disco is EOL next week, marking this won't fix for disco.

** Changed in: systemd (Ubuntu Disco)
   Status: In Progress => Won't Fix

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

Title:
  Bogus routes after DHCP lease change

Status in netplan:
  Invalid
Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  networkd does not remove old route(s) after DHCP address change

  [test case]

  on a system using networkd, that is connected to a network where you
  can control the addresses that the DHCP server provides, setup system
  with networkd to get address via DHCP, e.g.

  [Match]
  Name=ens3

  [Network]
  DHCP=ipv4

  
  (re)start networkd or reboot, so the system gets an ipv4 DHCP address, and 
corresponding route to the gateway.

  
  Then on the dhcp server, change the subnet to a different subnet.  On the 
client, once its renews its DHCP address, the server will provide a new address 
in the new subnet, and the client will add a new default route to the new 
gateway address.  However, the old default route to the old gateway address 
isn't removed.

  Note this also happens without changing the entire subnet, but is more
  subtle as shown in the original description.

  [regression potential]

  this affects how networkd handles routes, so has the potential to
  leave a system with partial or incorrect networking, or no networking
  at all.  Any regression would most likely occur during networkd
  (re)start or during renewal of a DHCP lease, or when an interface is
  brought up.

  [other info]

  original description:
  ---

  
  Netplan config:

  network:
    version: 2
    renderer: networkd
    ethernets:
  eno4:
    dhcp4: no
  eno1np0:
    dhcp4: no
    addresses:
  - 172.16.0.2/24
    bridges:
  br0:
    dhcp4: yes
    interfaces:
  - eno4

  On initial boot, machine got 10.0.15.109 IP address:

  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: Configured
  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: DHCPv4 address 
10.0.15.109/23 via 10.0.15.253

  At one point, DHCP server reserver this IP address and client
  eventually picked up new IP address:

  May 03 15:01:12 ceph2 systemd-networkd[1137]: br0: DHCPv4 address
  10.0.15.128/23 via 10.0.15.253

  This resulted in IP addresses:

  # ip -o a
  1: loinet 127.0.0.1/8 scope host lo\   valid_lft forever 
preferred_lft forever
  1: loinet6 ::1/128 scope host \   valid_lft forever preferred_lft 
forever
  2: eno1np0inet 172.16.0.2/24 brd 172.16.0.255 scope global eno1np0\   
valid_lft forever preferred_lft forever
  2: eno1np0inet6 fe80::b226:28ff:fe53:56be/64 scope link \   valid_lft 
forever preferred_lft forever
  6: br0inet 10.0.15.128/23 brd 10.0.15.255 scope global dynamic br0\   
valid_lft 503sec preferred_lft 503sec
  6: br0inet6 fe80::b8d7:5eff:fe6b:62a/64 scope link \   valid_lft 
forever preferred_lft forever

  So far, everything is fine. But, the routes on the machine are bogus:

  # ip r
  default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.109 metric 100
  default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.128 metric 100
  10.0.14.0/23 dev br0 proto kernel scope link src 10.0.15.128
  10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.109 metric 100
  10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.128 metric 100
  172.16.0.0/24 dev eno1np0 proto kernel scope link src 172.16.0.2

  routes with src 10.0.15.109 should have been removed when lease was
  renewed. I'm not sure if this is a bug in netplan or systemd. This is
  18.04, systemd 37-3ubuntu10.21, netplan 0.40.1~18.04.4.

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

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

[Touch-packages] [Bug 1845909] Re: [SRU] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

[Dan Streetman]

as disco is EOL next week, marking this won't fix for disco.

** Changed in: systemd (Ubuntu Disco)
   Status: In Progress => Won't Fix

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

Title:
  [SRU] IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

Status in systemd:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  [impact]

  when a networkd interface is configured with LinkLocalAddressing=no,
  networkd still assigns a link-local address to it

  [test case]

  see comment 3.

  note I was only able to reproduce this at boot time; if the vlan
  interface is removed (i.e. 'sudo ip l del pppoe') and then networkd
  restarted, the pppoe interface is created and does not have a link-
  local address.

  [regression potential]

  this moves the point when ipv6ll is configured; regressions would most
  likely involve failure to correctly configure an ipv6ll address when
  desired.

  [other info]

  this bug was attempted to be fixed by 
'debian/patches/networkd-honour-LinkLocalAddressing.patch' from upstream issue 
9890, using a commit that does not correctly fix the issue and was never 
accepted upstream:
  https://github.com/systemd/systemd/issues/9890#issuecomment-455168751

  this SRU completely reverts that patch, and adds the correct fix which
  was merged upstream:
  
https://github.com/systemd/systemd/commit/0e2fdb83bb5e22047e0c7cc058b415d0e93f02cf

  that commit is already included in Eoan so this sru is needed only for
  Disco.

  original description:

  --

  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

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

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

[Touch-packages] [Bug 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP

[Dan Streetman]

as disco is EOL next week, marking this won't fix for disco.

** Changed in: systemd (Ubuntu Disco)
   Status: In Progress => Won't Fix

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

Title:
  systemd-networkd fails to apply static IPv4 when the static IP is the
  same as previously configured by DHCP

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  Won't Fix

Bug description:
  [impact]

  if networkd is configured with a static address, and the address has
  already been assigned by dhcp (so that it has finite valid_lft),
  networkd will not change the valid_lft to 'forever' during startup,
  which leaves networkd thinking the address is static (meaning,
  networkd will not attempt to renew the dhcp lease) but the address
  valid_lft counting down.

  Once the valid_lft expires, the kernel will remove the address from
  the interface, breaking the system's networking.

  [test case]

  configure a system with networkd similar to:

  [Match]
  Name=ens3

  [Network]
  DHCP=ipv4

  restart systemd-networkd, and ens3 should get a DHCP address, e.g.:

  $ ip -4 a show ens3
  2: ens3:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  inet 192.168.122.147/24 brd 192.168.122.255 scope global dynamic ens3
     valid_lft 2295sec preferred_lft 2295sec

  then, edit the networkd config to use a static address, e.g.:

  [Match]
  Name=ens3

  [Network]
  Address=192.168.122.147/24
  Gateway=192.168.122.1
  DNS=192.168.122.1
  Domains=vm

  make sure to use the exact same address that was provided by dhcp.

  Then, without rebooting, just restart networkd and check the address
  lft:

  $ sudo systemctl restart systemd-networkd

  $ ip -4 a show ens3
  2: ens3:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  inet 192.168.122.147/24 brd 192.168.122.255 scope global dynamic ens3
     valid_lft 2992sec preferred_lft 2992sec

  the address should have 'forever' valid_lft, but it doesn't.

  [regression potential]

  this changes the details of how networkd updates static addresses
  during startup, so any regression would occur at networkd startup when
  using static addresses.

  [scope]

  this is needed only in Bionic and Disco.

  this is fixed by upstream:
  https://github.com/systemd/systemd/pull/11460/commits
  specifically commit a47a6daebe0af26c07d8d423225eb4add110793c
  which is included in Eoan and later.

  In Xenial using networkd, testing shows this problem does not occur,
  because this older version of networkd removes the 'foreign' dhcp
  address before re-assigning it as a static address.

  [other info]

  original description:
  ---

  In bionic, running systemd 237-3ubuntu10.22 and netplan.io
  0.97-0ubuntu1~18.04.1, systemd-networkd fails to configure an
  interface with a static IPv4 address if the statically confiugred
  address is the same as the interface already has gotten from DHCP.

  This will cause the interface to loose its IP address when the DHCP
  lease exires, even though you've told netplan to configure it as
  static.

  I expect systemd-networkd to actually configure an IP address as
  static, regardless of what address the interface has before from DHCP.

  # lsb_release  -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  # apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu10.22

  # apt-cache policy netplan.io
  netplan.io:
    Installed: 0.97-0ubuntu1~18.04.1

  A paste of systemd-networkd's debug log when I run "netplan apply" and
  the interface already has the static IP configured from DHCP.

  It seems like upon a restart, systemd-networkd will allways add
  whatever IP config it had before the service stopped, and then apply
  changes (if any). Since my new config has the same IP as it already
  had, it does nothing even though the new config has static
  configuration.

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

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

[Touch-packages] [Bug 1833025] Re: bcache partition within fstab prevents from booting

[Dan Streetman]

Very sorry that this did not get fixed, but Disco is reaching EOL next
week, so this fix will not make it.  I recommend you upgrade to Eoan,
where this should be fixed.

Marking this won't fix for Disco.

** Changed in: systemd (Ubuntu Disco)
   Status: In Progress => Won't Fix

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

Title:
  bcache partition within fstab prevents from booting

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Disco:
  Won't Fix

Bug description:
  Almost every boot attempt drops to initramfs prompt, requiring me to
  type echo /dev/sdb >/sys/fs/bcache/register. Logs showing that attempt
  to register caching device via udev rules was made, but failed with
  code == 1.

  Looks like an regression were introduced in upstream (systemd 240)
  which breaks the order of udev commands.

  Here is an upstream bug https://github.com/systemd/systemd/issues/11368
  And here is a patch for this issue 
https://github.com/systemd/systemd/pull/11891
  Can you, please merge this patch to disco branch?

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

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

[Touch-packages] [Bug 1836695] Re: systemd fails to setup static routes at boot when using DHCP

[Dan Streetman]

as disco is EOL next week, marking this won't fix for disco.

** Changed in: systemd (Ubuntu Disco)
   Status: In Progress => Won't Fix

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

Title:
  systemd fails to setup static routes at boot when using DHCP

Status in netplan:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  a systemd-networkd configuration that uses ipv4 dhcp but ignores the
  dhcp-provided route, and instead sets up a static route, and also does
  not include a static ipv4 address, fails to actually create the static
  route.

  This is due to networkd attempting to set up the static route before
  the dhcp ipv4 address is assigned, and the kernel does not allow
  creation of the route before setting up corresponding ipv4 address.

  this results in a network that does have the dhcp-provided ipv4
  address, but is missing both its dhcp-provided route (because networkd
  is configured to ignore it) and the static route (because networkd was
  not able to create it).

  [test case]

  (remove or unconfigure netplan, so it will not conflict with this
  manual networkd configuration)

  create a networkd config file, e.g.:

  $ cat /etc/systemd/network/10-eth0.network 
  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4

  [Route]
  Destination=10.0.0.0/8
  Gateway=10.202.51.1

  [DHCP]
  UseRoutes=false

  
  then *reboot* the system, and check that the static route was not applied:

  $ ip r
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.254 

  
  note that because networkd does not remove ipv4 addresses that it manages 
(including dhcpv4 addresses), restarting networkd after the initial boot
  will correctly create the static route, e.g.:

  ubuntu@lp1836695-b:~$ ip r
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.254 
  ubuntu@lp1836695-b:~$ sudo systemctl restart systemd-networkd
  ubuntu@lp1836695-b:~$ ip r
  10.0.0.0/8 via 10.202.51.1 dev eth0 proto static 
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.254 

  [regression potential]

  adjusting how networkd works always carries the risk of breaking
  networking.

  TBD detailed regression potential after analyzing fix.

  [other info]

  original description:

  --

  
  Consider the following setup:

  network:
    version: 2
    renderer: networkd
    ethernets:
  ens4:
    dhcp-identifier: mac
    dhcp4: yes
    dhcp4-overrides:
  use-dns: no
  use-ntp: no
  send-hostname: no
  use-hostname: no
  use-routes: no
    routes:
    - to: 10.0.0.0/8
  via: 10.50.0.1
    optional: true

  Thus I only need to get the IP address by DHCP, then add some static
  routes. This setup doesn't work. Apparently `routes` keyword only
  works when using static addresses.

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

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

[Touch-packages] [Bug 1858412] Re: systemd vacuuming does not work for remote journals

[Balint Reczey]

Fixed in v244, I think hits is a minor issue that does not seem to
warrant a backport.

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

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

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

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

** Changed in: systemd (Ubuntu Bionic)
   Importance: Undecided => Low

** Changed in: systemd (Ubuntu Disco)
   Importance: Undecided => Low

** Changed in: systemd (Ubuntu Eoan)
   Importance: Undecided => Low

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

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

Title:
  systemd vacuuming does not work for remote journals

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

Bug description:
  systemd has an issue in regard to vacuuming remote journals:
  https://github.com/systemd/systemd/issues/2376 - this affects 18.04 as
  this version still has this problem.

  Steps to reproduce on "Description: Ubuntu 18.04.3 LTS":

  root@1:~# du -hs /var/log/journal/remote/
  8.6G  /var/log/journal/remote/
  root@1:~# journalctl -D /var/log/journal/remote --vacuum-size=100M
  root@1:~# du -hs /var/log/journal/remote/
  8.6G  /var/log/journal/remote/

  Would it be possible to backport this trivial patch
  https://github.com/systemd/systemd/pull/13924 into 18.04?

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

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

[Touch-packages] [Bug 1858210] Re: timedatectl doesn't list all timezones

[Balint Reczey]

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

** Tags removed: arm64

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

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

Title:
  timedatectl doesn't list all timezones

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Is there some filter determining which timezones are displayed by
  `timedatectl list-timezones`? My zone, Europe/Bratislava, is missing.
  Even stranger, it can successfully be set by timedatectl.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10
  Uname: Linux 5.3.0-1014-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  Date: Fri Jan  3 15:36:03 2020
  Lspci:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 
elevator=deadline rootwait fixrtc
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.systemd.resolved.conf: 2020-01-03T01:02:47.779343

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

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

[Touch-packages] [Bug 1856428] Re: Disable TLS below 1.2 by default

[Launchpad Bug Tracker]

This bug was fixed in the package nss - 2:3.48-1ubuntu1

---
nss (2:3.48-1ubuntu1) focal; urgency=low

  * Merge from Debian unstable.  Remaining changes:
- d/libnss3.links: make freebl3 available as library (LP #1744328)
- d/control: add dh-exec to Build-Depends
- d/rules: make mkdir tolerate debian/tmp existing (due to dh-exec)
- Disable reading fips_enabled flag in FIPS mode. libnss is
  not a FIPS certified library. (LP #1837734)
  * Set TLSv1.2 as minimum TLS version. LP: #1856428

nss (2:3.48-1) unstable; urgency=medium

  * New upstream release. Closes: #947131.
  * debian/control: Bump nspr build dependency to 4.24.
  * nss/lib/freebl/Makefile: Disable hardware AES on ARM softfloat to fix
FTBFS on armel. Closes: #947246.

nss (2:3.47.1-1) unstable; urgency=medium

  * New upstream release.
- Fixes CVE-2019-11745.

 -- Ubuntu Merge-o-Matic   Sun, 29 Dec 2019 03:43:36
+

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11745

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

Title:
  Disable TLS below 1.2 by default

Status in gnutls28 package in Ubuntu:
  Fix Committed
Status in golang-1.13 package in Ubuntu:
  New
Status in nss package in Ubuntu:
  Fix Released
Status in openssl package in Ubuntu:
  Fix Committed

Bug description:
  Disable TLS 1.0, TLS1.1, DTLS1.0

  As part of focal commitment, we shall disable obsolete protocols by
  default.

  Users can override this behaviour with a config file.

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

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

[Touch-packages] [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal

[Dariusz Gadomski]

Please hold on with uploading until
https://github.com/systemd/systemd/issues/14567 is resolved.

** Bug watch added: github.com/systemd/systemd/issues #14567
   https://github.com/systemd/systemd/issues/14567

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

Title:
  pam_group.so is not evaluated by gnome-terminal

Status in systemd:
  New
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Won't Fix
Status in gnome-terminal source package in Eoan:
  New
Status in systemd source package in Eoan:
  In Progress

Bug description:
  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1856560] Re: ds-identify - stuck in uninterruptible sleep state

[Nicklas]

Affected process
```
root  1166  0.0  0.0  72292  5812 ?Ss2019   0:00 /usr/sbin/sshd 
-D
```

Output of `ls -latr /proc/1166/fd`

total 0
dr-xr-xr-x 9 root root  0 Jan 14 12:00 ..
dr-x-- 2 root root  0 Jan 14 12:31 .
lrwx-- 1 root root 64 Jan 14 12:31 4 -> 'socket:[24485]'
lrwx-- 1 root root 64 Jan 14 12:31 3 -> 'socket:[24483]'
lrwx-- 1 root root 64 Jan 14 12:31 2 -> 'socket:[24455]'
lrwx-- 1 root root 64 Jan 14 12:31 1 -> 'socket:[24455]'
lr-x-- 1 root root 64 Jan 14 12:31 0 -> /dev/null


Should we disable `cloud-init` altogether?

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

Title:
  ds-identify - stuck in uninterruptible sleep state

Status in cloud-init:
  Invalid
Status in util-linux package in Ubuntu:
  New

Bug description:
  We got recurring issues with the cloud-init/ds-identify process. It
  spawns sub-processes "blkid -c /dev/null -o export" which gets stuck
  in the "D" uninterruptible sleep state.

  The processes cannot be killed, so the only solution is to reboot the
  affected server.

  root 3839 0.0 0.0 4760 1840 ? S Dec05 0:00 /bin/sh 
/usr/lib/cloud-init/ds-identify
  root 3844 0.0 0.0 11212 2836 ? D Dec05 0:00 \_ blkid -c /dev/null -o export
  root 6943 0.0 0.0 4760 1880 ? S Dec05 0:00 /bin/sh 
/usr/lib/cloud-init/ds-identify
  root 6948 0.0 0.0 11212 2844 ? D Dec05 0:00 \_ blkid -c /dev/null -o export
  root 6111 0.0 0.0 4760 1916 ? S Dec12 0:00 /bin/sh 
/usr/lib/cloud-init/ds-identify
  root 6149 0.0 0.0 11212 2940 ? D Dec12 0:00 \_ blkid -c /dev/null -o export
  root 8765 0.0 0.3 926528 24968 ? Ssl Dec12 0:12 /usr/lib/snapd/snapd
  root 9179 0.0 0.0 4760 1892 ? S Dec12 0:00 /bin/sh 
/usr/lib/cloud-init/ds-identify
  root 9185 0.0 0.0 11980 3552 ? D Dec12 0:00 \_ blkid -c /dev/null -o export

  Distributor ID: Ubuntu
  Description: Ubuntu 18.04.3 LTS
  Release: 18.04
  Codename: bionic

  5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019
  x86_64 x86_64 x86_64 GNU/Linux

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

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

[Touch-packages] [Bug 1856560] Re: ds-identify - stuck in uninterruptible sleep state

[Nicklas]

Never mind my last message...

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

Title:
  ds-identify - stuck in uninterruptible sleep state

Status in cloud-init:
  Invalid
Status in util-linux package in Ubuntu:
  New

Bug description:
  We got recurring issues with the cloud-init/ds-identify process. It
  spawns sub-processes "blkid -c /dev/null -o export" which gets stuck
  in the "D" uninterruptible sleep state.

  The processes cannot be killed, so the only solution is to reboot the
  affected server.

  root 3839 0.0 0.0 4760 1840 ? S Dec05 0:00 /bin/sh 
/usr/lib/cloud-init/ds-identify
  root 3844 0.0 0.0 11212 2836 ? D Dec05 0:00 \_ blkid -c /dev/null -o export
  root 6943 0.0 0.0 4760 1880 ? S Dec05 0:00 /bin/sh 
/usr/lib/cloud-init/ds-identify
  root 6948 0.0 0.0 11212 2844 ? D Dec05 0:00 \_ blkid -c /dev/null -o export
  root 6111 0.0 0.0 4760 1916 ? S Dec12 0:00 /bin/sh 
/usr/lib/cloud-init/ds-identify
  root 6149 0.0 0.0 11212 2940 ? D Dec12 0:00 \_ blkid -c /dev/null -o export
  root 8765 0.0 0.3 926528 24968 ? Ssl Dec12 0:12 /usr/lib/snapd/snapd
  root 9179 0.0 0.0 4760 1892 ? S Dec12 0:00 /bin/sh 
/usr/lib/cloud-init/ds-identify
  root 9185 0.0 0.0 11980 3552 ? D Dec12 0:00 \_ blkid -c /dev/null -o export

  Distributor ID: Ubuntu
  Description: Ubuntu 18.04.3 LTS
  Release: 18.04
  Codename: bionic

  5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019
  x86_64 x86_64 x86_64 GNU/Linux

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

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

[Touch-packages] [Bug 1859610] [NEW] python-gi/arm64 segfaults with the focal-proposed libffi version

[Sebastien Bacher]

Public bug reported:

Testcase, on focal/arm64

$ sudo apt install python3-goocalendar
$ python3 -c "import goocalendar ; print(goocalendar.__version__)"

-> works fine

install the python3-gi package from focal-proposed it segfaults in
libffi

Program received signal SIGSEGV, Segmentation fault.
0x in ?? ()
(gdb) bt
#0  0x in ?? ()
#1  0xf7390ff8 in ffi_call_SYSV () at ../src/aarch64/sysv.S:114
#2  0xf7390634 in ffi_call_int (cif=0xa12d78, fn=, 
orig_rvalue=, avalue=0x0, closure=)

** Affects: libffi (Ubuntu)
 Importance: High
 Status: New


** Tags: rls-ff-incoming

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

Title:
  python-gi/arm64 segfaults with the focal-proposed libffi version

Status in libffi package in Ubuntu:
  New

Bug description:
  Testcase, on focal/arm64

  $ sudo apt install python3-goocalendar
  $ python3 -c "import goocalendar ; print(goocalendar.__version__)"

  -> works fine

  install the python3-gi package from focal-proposed it segfaults in
  libffi

  Program received signal SIGSEGV, Segmentation fault.
  0x in ?? ()
  (gdb) bt
  #0  0x in ?? ()
  #1  0xf7390ff8 in ffi_call_SYSV () at ../src/aarch64/sysv.S:114
  #2  0xf7390634 in ffi_call_int (cif=0xa12d78, fn=, 
  orig_rvalue=, avalue=0x0, closure=)

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

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

[Touch-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

[BZHipHop]

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

Comment #6 fixed for me, thanks a lot buo-ren-lin

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+subscriptions

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

[Touch-packages] [Bug 1859404] Re: binutils regressed llvm-toolchain-9 and llvm-toolchain-7 bootstrap on arm64

[Bug Watch Updater]

** Changed in: binutils (Debian)
   Status: Unknown => New

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

Title:
  binutils regressed llvm-toolchain-9 and llvm-toolchain-7 bootstrap on
  arm64

Status in binutils package in Ubuntu:
  New
Status in binutils package in Debian:
  New

Bug description:
  Retrying builds on bileto with the release only pocket enabled worked
  correctly.

  
  Still trying to figure out what can have regressed it (Debian doesn't show 
the issue, but probably it is affected on the same way, just his CPUs can 
understand the new instructions?

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

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

[Touch-packages] [Bug 1859404] Re: binutils regressed llvm-toolchain-9 and llvm-toolchain-7 bootstrap on arm64

[Graham Inggs]

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

** Also affects: binutils (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948803
   Importance: Unknown
   Status: Unknown

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

Title:
  binutils regressed llvm-toolchain-9 and llvm-toolchain-7 bootstrap on
  arm64

Status in binutils package in Ubuntu:
  New
Status in binutils package in Debian:
  Unknown

Bug description:
  Retrying builds on bileto with the release only pocket enabled worked
  correctly.

  
  Still trying to figure out what can have regressed it (Debian doesn't show 
the issue, but probably it is affected on the same way, just his CPUs can 
understand the new instructions?

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

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

[Touch-packages] [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal

[Dariusz Gadomski]

SRU proposal for Focal (upstream backport).

** Patch added: "focal_systemd_244-3ubuntu4.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1762391/+attachment/5320077/+files/focal_systemd_244-3ubuntu4.debdiff

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

Title:
  pam_group.so is not evaluated by gnome-terminal

Status in systemd:
  New
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Won't Fix
Status in gnome-terminal source package in Eoan:
  New
Status in systemd source package in Eoan:
  In Progress

Bug description:
  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1452115] Re: Python interpreter binary is not compiled as PIE

[Jarek Zgoda]

3.7 is also affected in bionic:

$ hardening-check /usr/bin/python3.7
/usr/bin/python3.7:
 Position Independent Executable: no, normal executable!
 Stack protected: yes
 Fortify Source functions: yes (some protected functions found)
 Read-only relocations: yes
 Immediate binding: no, not found!

** Also affects: python3.7 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Python interpreter binary is not compiled as PIE

Status in Python:
  New
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3.4 package in Ubuntu:
  Fix Released
Status in python3.6 package in Ubuntu:
  Confirmed
Status in python3.7 package in Ubuntu:
  New
Status in python3.8 package in Ubuntu:
  Confirmed
Status in python3.8 package in Debian:
  New

Bug description:
  The python2.7 binary (installed at /usr/bin/python2.7; package version
  2.7.6-8) is not compiled as a position independent executable (PIE).
  It appears that the python compilation process is somewhat arcane and
  the hardening wrapper probably doesn't do the trick for it.

  This is incredibly dangerous as it means that any vulnerability within
  a native module (e.g. ctypes-based), or within python itself will
  expose an incredibly large amount of known memory contents at known
  addresses (including a large number of dangerous instruction
  groupings). This enables ROP-based (https://en.wikipedia.org/wiki
  /Return-oriented_programming) to abuse the interpreter itself to
  bypass non-executable page protections.

  I have put together an example vulnerable C shared object (with a buffer 
overflow) accessed via python through the ctypes interface as an example. This 
uses a single ROP "gadget" on top of using the known PLT location for system(3) 
(https://en.wikipedia.org/wiki/Return-to-libc_attack) to call "id". The example 
code is accessible at:
  - https://gist.github.com/ChaosData/ae6076cb1c3cc7b0a367

  I'm not exactly familiar enough with the python build process to say
  where exactly an -fPIE needs to be injected into a script/makefile,
  but I feel that given the perceived general preference for ctypes-
  based modules over python written ones, as the native code
  implementations tend to be more performant, this feels like a large
  security hole within the system. Given the nature of this "issue," I'm
  not 100% sure of where it is best reported, but from what I can tell,
  this conflicts with the Ubuntu hardening features and is definitely
  exploitable should a native module contain a sufficiently exploitable
  vulnerability that allows for control of the instruction register.

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

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

[Touch-packages] [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal

[Dariusz Gadomski]

This issue has been fixed upstream, I believe it makes sense to also
have it in Ubuntu.

** Changed in: systemd (Ubuntu Bionic)
   Status: Won't Fix => In Progress

** Changed in: systemd (Ubuntu)
   Status: Won't Fix => In Progress

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

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

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

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

** Changed in: systemd (Ubuntu Eoan)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

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

Title:
  pam_group.so is not evaluated by gnome-terminal

Status in systemd:
  New
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Won't Fix
Status in gnome-terminal source package in Eoan:
  New
Status in systemd source package in Eoan:
  In Progress

Bug description:
  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1841157] Re: have /usr/bin/oem-getlogs in apport to collect all in one logs

[Yuan-Chen Cheng]

for #6, create new bug LP: #1859581

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

Title:
  have /usr/bin/oem-getlogs in apport to collect all in one logs

Status in Apport:
  New
Status in OEM Priority Project:
  In Progress
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  plan to use command like

  $ sudo oem-getlogs

  to collect all logs that oem project could need.

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

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

[Touch-packages] [Bug 1841157] Re: have /usr/bin/oem-getlogs in apport to collect all in one logs

[Yuan-Chen Cheng]

just found that oem-getlog is not included in focal

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

Title:
  have /usr/bin/oem-getlogs in apport to collect all in one logs

Status in Apport:
  New
Status in OEM Priority Project:
  In Progress
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  plan to use command like

  $ sudo oem-getlogs

  to collect all logs that oem project could need.

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

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

[Touch-packages] [Bug 1841157] Re: have /usr/bin/oem-getlogs in apport to collect all in one logs

[Yuan-Chen Cheng]

just found that oem-getlogs is not listed in debian/apport.install in
focal.

Can we include it?

In the mean time, we need the apport-unpack patch so that it can unpack
apport.gz file directly. Please check attached patch.

** Patch added: "apport-unpack.patch"
   
https://bugs.launchpad.net/oem-priority/+bug/1841157/+attachment/5320064/+files/apport-unpack.diff

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

Title:
  have /usr/bin/oem-getlogs in apport to collect all in one logs

Status in Apport:
  New
Status in OEM Priority Project:
  In Progress
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  plan to use command like

  $ sudo oem-getlogs

  to collect all logs that oem project could need.

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

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