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

2019-09-01 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 237-3ubuntu10.26

---
systemd (237-3ubuntu10.26) bionic; urgency=medium

  [ You-Sheng Yang ]
  * d/p/d/Revert-udev-network-device-renaming-immediately-give.patch:
- udev: drop Revert-udev-network-device-renaming-immediately-give.patch
  The removing patch was for the already deprecated
  "75-persistent-net-generator.rules" based interface renaming mechanism,
  and it's causing unnecessary problem when a system happends to NICs with
  same MAC address, e.g. Dell's MAC address pass-thru. (LP: #1837700)

  [ Shih-Yuan Lee (FourDollars) ]
  * d/p/hwdb-revert-airplane-mode-keys-handling-on-Dell.patch:
- hwdb: revert airplane mode keys handling on Dell
  That reverts some commits those created double key events issues on some
  Dell laptops. (LP: #1740894)

 -- Shih-Yuan Lee (FourDollars)   Wed, 07 Aug 2019
17:56:02 +0800

** Changed in: systemd (Ubuntu Bionic)
   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/1837700

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

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

Bug description:
  update for SRU process:

  [Impact]
  1. On system featured mac passthrough, e.g., Dell/Lenovo laptop, or system 
occasionally install two USB ethernet with same MAC address, the system will 
suffer 90 seconds for network interface renaming mechanism before the last USB 
ethernet interface to activate.

  [Test Case]
  1. Install ubuntu on Dell laptop.
  2. Connect the Dell laptop with two Realtek 8153 USB ethernet dongle. Users 
can observe the last one will take 90 seconds for renaming to rename0.
  3. Users can also find that the two USB ethernet have the same MAC address.

  [Regression Potential] 
  To resolve the issue, drop a debian patch from systemd package. The debian 
patch is to revert an upstream commit to support 
75-persistent-net-generator.rules udev rule. Since the udev rule is deprecated, 
the regression potential should be relatively low.

  ---

  
  Dell has a feature called MAC addrss passthrough[1] that would force usb 
ethernet adapters to be assigned with a predefined MAC address stored in BIOS 
or so. This feature has been landed to mainline kernel in driver r8152[2]. So 
whenever a r8152 managed device is plugged into Dell devices with MAC addrss 
passthrough enabled, this driver will set NIC MAC to a predefined one.

  And some Dell devices have already one built-in r8152 NIC port. On
  these devices, when a second r8152 NIC is plugged in, a Debian
  originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev
  built-in command `net_id` to give a persistent name, and that will be
  based on MAC address. However, since the system has already
  initialized the built-in r8152 NIC with that name, renaming the second
  interface with this name will always fail.

  While Debian still carries a patch called "Revert-udev-network-device-
  renaming-immediately-give.patch"[4] that tries to keep support of
  already deprecated "75-persistent-net-generator.rules" based interface
  renaming mechanism, this patch also propagated into Ubuntu[5]. This
  patch will retry renaming with a 90 seconds timeout when the error
  code is -EEXIST, so the uevent processing will always be blocked in
  the last ifrename step in the victim system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules 
lib/udev/rules.d/50-udev-default.rules 
lib/udev/rules.d/73-special-net-names.rules 
lib/udev/rules.d/73-usb-net-by-mac.rules]
  ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18
  Uname: Linux 4.15.0-1043-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules
  Date: Wed Jul 24 15:30:59 2019
  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-jorah+X90
  InstallationDate: Installed on 2019-07-03 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 7424 Rugged Extreme
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed 
root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet 
splash systemd.log_level=debug 

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

2019-09-01 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 240-6ubuntu5.4

---
systemd (240-6ubuntu5.4) disco; urgency=medium

  [ You-Sheng Yang ]
  * d/p/d/Revert-udev-network-device-renaming-immediately-give.patch:
- udev: drop Revert-udev-network-device-renaming-immediately-give.patch.
  The removing patch was for the already deprecated
  "75-persistent-net-generator.rules" based interface renaming mechanism,
  and it's causing unnecessary problem when a system happends to NICs with
  same MAC address, e.g. Dell's MAC address pass-thru. (LP: #1837700)

 -- Shih-Yuan Lee (FourDollars)   Wed, 21 Aug 2019
16:15:23 +0800

** Changed in: systemd (Ubuntu Disco)
   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/1837700

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

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

Bug description:
  update for SRU process:

  [Impact]
  1. On system featured mac passthrough, e.g., Dell/Lenovo laptop, or system 
occasionally install two USB ethernet with same MAC address, the system will 
suffer 90 seconds for network interface renaming mechanism before the last USB 
ethernet interface to activate.

  [Test Case]
  1. Install ubuntu on Dell laptop.
  2. Connect the Dell laptop with two Realtek 8153 USB ethernet dongle. Users 
can observe the last one will take 90 seconds for renaming to rename0.
  3. Users can also find that the two USB ethernet have the same MAC address.

  [Regression Potential] 
  To resolve the issue, drop a debian patch from systemd package. The debian 
patch is to revert an upstream commit to support 
75-persistent-net-generator.rules udev rule. Since the udev rule is deprecated, 
the regression potential should be relatively low.

  ---

  
  Dell has a feature called MAC addrss passthrough[1] that would force usb 
ethernet adapters to be assigned with a predefined MAC address stored in BIOS 
or so. This feature has been landed to mainline kernel in driver r8152[2]. So 
whenever a r8152 managed device is plugged into Dell devices with MAC addrss 
passthrough enabled, this driver will set NIC MAC to a predefined one.

  And some Dell devices have already one built-in r8152 NIC port. On
  these devices, when a second r8152 NIC is plugged in, a Debian
  originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev
  built-in command `net_id` to give a persistent name, and that will be
  based on MAC address. However, since the system has already
  initialized the built-in r8152 NIC with that name, renaming the second
  interface with this name will always fail.

  While Debian still carries a patch called "Revert-udev-network-device-
  renaming-immediately-give.patch"[4] that tries to keep support of
  already deprecated "75-persistent-net-generator.rules" based interface
  renaming mechanism, this patch also propagated into Ubuntu[5]. This
  patch will retry renaming with a 90 seconds timeout when the error
  code is -EEXIST, so the uevent processing will always be blocked in
  the last ifrename step in the victim system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules 
lib/udev/rules.d/50-udev-default.rules 
lib/udev/rules.d/73-special-net-names.rules 
lib/udev/rules.d/73-usb-net-by-mac.rules]
  ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18
  Uname: Linux 4.15.0-1043-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules
  Date: Wed Jul 24 15:30:59 2019
  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-jorah+X90
  InstallationDate: Installed on 2019-07-03 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 7424 Rugged Extreme
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed 
root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet 
splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0Y7FK3
  dmi.board.vendor: Dell Inc.
  

[Touch-packages] [Bug 1837700] Update Released

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

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

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

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

Bug description:
  update for SRU process:

  [Impact]
  1. On system featured mac passthrough, e.g., Dell/Lenovo laptop, or system 
occasionally install two USB ethernet with same MAC address, the system will 
suffer 90 seconds for network interface renaming mechanism before the last USB 
ethernet interface to activate.

  [Test Case]
  1. Install ubuntu on Dell laptop.
  2. Connect the Dell laptop with two Realtek 8153 USB ethernet dongle. Users 
can observe the last one will take 90 seconds for renaming to rename0.
  3. Users can also find that the two USB ethernet have the same MAC address.

  [Regression Potential] 
  To resolve the issue, drop a debian patch from systemd package. The debian 
patch is to revert an upstream commit to support 
75-persistent-net-generator.rules udev rule. Since the udev rule is deprecated, 
the regression potential should be relatively low.

  ---

  
  Dell has a feature called MAC addrss passthrough[1] that would force usb 
ethernet adapters to be assigned with a predefined MAC address stored in BIOS 
or so. This feature has been landed to mainline kernel in driver r8152[2]. So 
whenever a r8152 managed device is plugged into Dell devices with MAC addrss 
passthrough enabled, this driver will set NIC MAC to a predefined one.

  And some Dell devices have already one built-in r8152 NIC port. On
  these devices, when a second r8152 NIC is plugged in, a Debian
  originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev
  built-in command `net_id` to give a persistent name, and that will be
  based on MAC address. However, since the system has already
  initialized the built-in r8152 NIC with that name, renaming the second
  interface with this name will always fail.

  While Debian still carries a patch called "Revert-udev-network-device-
  renaming-immediately-give.patch"[4] that tries to keep support of
  already deprecated "75-persistent-net-generator.rules" based interface
  renaming mechanism, this patch also propagated into Ubuntu[5]. This
  patch will retry renaming with a 90 seconds timeout when the error
  code is -EEXIST, so the uevent processing will always be blocked in
  the last ifrename step in the victim system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules 
lib/udev/rules.d/50-udev-default.rules 
lib/udev/rules.d/73-special-net-names.rules 
lib/udev/rules.d/73-usb-net-by-mac.rules]
  ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18
  Uname: Linux 4.15.0-1043-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules
  Date: Wed Jul 24 15:30:59 2019
  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-jorah+X90
  InstallationDate: Installed on 2019-07-03 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 7424 Rugged Extreme
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed 
root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet 
splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0Y7FK3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  

[Touch-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace

2019-09-01 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 237-3ubuntu10.26

---
systemd (237-3ubuntu10.26) bionic; urgency=medium

  [ You-Sheng Yang ]
  * d/p/d/Revert-udev-network-device-renaming-immediately-give.patch:
- udev: drop Revert-udev-network-device-renaming-immediately-give.patch
  The removing patch was for the already deprecated
  "75-persistent-net-generator.rules" based interface renaming mechanism,
  and it's causing unnecessary problem when a system happends to NICs with
  same MAC address, e.g. Dell's MAC address pass-thru. (LP: #1837700)

  [ Shih-Yuan Lee (FourDollars) ]
  * d/p/hwdb-revert-airplane-mode-keys-handling-on-Dell.patch:
- hwdb: revert airplane mode keys handling on Dell
  That reverts some commits those created double key events issues on some
  Dell laptops. (LP: #1740894)

 -- Shih-Yuan Lee (FourDollars)   Wed, 07 Aug 2019
17:56:02 +0800

** Changed in: systemd (Ubuntu Bionic)
   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/1740894

Title:
  KEY_RFKILL is not passed to userspace

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project bionic series:
  Fix Committed
Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xorgproto source package in Bionic:
  Fix Released
Status in libxkbcommon source package in Cosmic:
  Fix Released
Status in xkeyboard-config source package in Cosmic:
  Fix Released
Status in xorgproto source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1740894/+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 1830914] Re: software-properties-gtk does not run at all!

2019-09-01 Thread Launchpad Bug Tracker
[Expired for software-properties (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: software-properties (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  software-properties-gtk does not run at all!

Status in software-properties package in Ubuntu:
  Expired

Bug description:
  software-properties-gtk does not even start!

  
  $ software-properties-gtk --debug

  ENABLED COMPS: {'universe', 'main'}
  INTERNET COMPS: {'universe', 'main'}
  MAIN SOURCES
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['main']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu
   BaseURI: http://archive.ubuntu.com/ubuntu

  
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['universe']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu
   BaseURI: http://archive.ubuntu.com/ubuntu

  
  CHILD SOURCES
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['main']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu
   BaseURI: None

  
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['universe']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu
   BaseURI: None

  
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['main']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
   BaseURI: http://security.ubuntu.com/ubuntu/

  
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['universe']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
   BaseURI: http://security.ubuntu.com/ubuntu/

  
   URI: http://archive.ubuntu.com/ubuntu
   Comps: ['universe', 'main']
   Enabled: True
   Valid: True
   MatchURI: archive.ubuntu.com/ubuntu
   BaseURI: None

  
  CDROM SOURCES
  SOURCE CODE SOURCES
  DISABLED SOURCES
  ISV
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 200, in __init__
  self.init_livepatch()
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 1482, in init_livepatch
  self.livepatch_page = LivepatchPage(self)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/LivepatchPage.py", line 
51, in __init__
  self._lps = LivepatchService()
File 
"/usr/lib/python3/dist-packages/softwareproperties/LivepatchService.py", line 
93, in __init__
  self._session = requests_unixsocket.Session()
  NameError: name 'requests_unixsocket' is not defined

  {Exited with code 1.}

  
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 19.04
  Release:  19.04
  Codename: disco

  
  $ dpkg-query -l software-properties-gtk python3-requests-unixsocket

  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ NameVersion  Architecture Description
  
+++-===---===
  ii  python3-requests-unixsocket 0.1.5-3  all  Use requests to 
talk HTTP via a UNIX domain socket - Python 3.x
  ii  software-properties-gtk 0.97.11  all  manage the 
repositories that you install software from (gtk)

  
  $ sudo apt-get update
  {Works.}

  $ sudo apt-get dist-upgrade
  {Works.}

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1830914/+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 1834128] Re: Multiple sshd services cannot be executed

2019-09-01 Thread Launchpad Bug Tracker
[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Multiple sshd services cannot be executed

Status in openssh package in Ubuntu:
  Expired

Bug description:
  OpenSSH 7.6p1
  Ubuntu 18.04.2 (LTS) (Bionic)

  See also Ticket #1831765, #1690485, and #1832110 regarding the path of
  the privilege separation directory (aka: /run/sshd).

  The current Debian installer sets the RuntimeDirectory=sshd (i.e.
  /run/sshd) in sshd.service (i.e. /lib/systemd/system/sshd.service) and
  sshd@.service (i.e. /lib/systemd/system/sshd@.service). This is not
  the best means of implementing this service. The problem is that the
  systemd deletes the RuntimeDirectory resource as soon as the service
  is stopped. When this happens, other sshd services will fault since
  the privileged separation directory is no longer there. We need to
  modify the configuration as follows:

  1) Create /usr/lib/tmpfiles.d/sshd.conf that defines the /run/sshd directory 
with root:root as the owner and the protection of 0755.
  2) Change the assignment of the RuntimeDirectory in sshd.service to something 
other than sshd (i.e. /run/sshd).
  3) Change the assignment of the RuntimeDirectory in sshd@.service to 
something other than sshd (i.e. /run/sshd).

  Both OpenSSH and Ubuntu have declined to provision a means of
  adjusting the Privilege Separation directory. Since both teams do not
  want to address this, we need to have a means of implementing multiple
  instance sshd invocation using  systemd and avoiding using the
  RuntimeDirectory assignment of /run/sshd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1834128/+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 1842133] Re: findutils shows wrong version number

2019-09-01 Thread Keith Thompson
> First off: Ubuntu/Debian do not ship "patched version of the GNU findutils
> package [...] based on release 4.6.0".

OK.  When I do "apt-get source findutils" I get a 
"findutils_4.6.0+git+20170828-2.debian.tar.xz"
file that does include two patches, but neither of them seems to be relevant to 
this issue.

The "findutils_4.6.0+git+20170828.orig.tar.xz" file I get from the same apt-get 
command
unpacks to a "findutils-4.7.0-gitfindutils-4.7.0-git" directory.

I just built findutils revision febde26dd0e66dda5d4060fa29b85443ddc6a865 from 
source, and
the resulting "find" command does print "find (GNU findutils) 4.7.0-git" when 
invoked with
"--version".  So it seems to be an upstream issue.  "info findutils", which 
loads
/usr/share/info/find.info.gz, also reports version 4.7.0-git.

Whatever the cause, I suggest that "4.7.0-git" is misleading, since release 
4.7.0 did not
yet exist.

I could submit a bug report against the upstream findutils component.
Should I do so?

(To be clear, I'm not saying this is a major, or even necessarily
significant, problem.)

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

Title:
  findutils shows wrong version number

Status in findutils package in Ubuntu:
  New

Bug description:
  This problem occurs on Ubuntu 18.04.3 LTS (bionic).
  It does not occur on Ubuntu 19.04 (disco)

  The "find" and "xargs" command are provided by a patched version of the
  GNU findutils package. The current version is based on release 4.6.0, but
  the "--version" option shows a version number of "4.7.0-git".

  As you can see, the "/usr/bin/find" executable is dated Nov 5 2017.
  findutils release 4.7.0 was released just yesterday, Aug 29 2017.

  Ubuntu 19.04 has findutils 4.6.0+git+20190209-2, and "find --version"
  shows "find (GNU findutils) 4.6.0.225-235f".

  Expected: "findutils --version" shows a version number based on 4.6.0
  Actual:   "findutils --version" shows a version number based on 4.7.0,
which had not yet been released

  Demonstration:

  $ lsb_release -rd
  Description:Ubuntu 18.04.3 LTS  
  Release:18.04
  $ apt-cache policy findutils
  findutils:
Installed: 4.6.0+git+20170828-2
Candidate: 4.6.0+git+20170828-2
Version table:
   *** 4.6.0+git+20170828-2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  $ ls -l /usr/bin/find
  -rwxr-xr-x 1 root root 238080 Nov  5  2017 /usr/bin/find
  $ /usr/bin/find --version
  find (GNU findutils) 4.7.0-git
  Copyright (C) 2017 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later .
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  Written by Eric B. Decker, James Youngman, and Kevin Dalley.
  Features enabled: D_TYPE O_NOFOLLOW(enabled) LEAF_OPTIMISATION FTS(FTS_CWDFD) 
CBO(level=2)
  $

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1842133/+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 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled

2019-09-01 Thread Daniel van Vugt
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  System wakes up immediately after suspend if Bluetooth is still
  enabled

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After replacing my USB mouse with a BT mouse, I noticed my machine
  would no longer suspend without immediately waking up. i.e. I suspend
  and see the light go into the slow fade in and out for one cycle and
  then goes solid and the display wakes up again. If I disable BT (via
  blueman applet) suspend works fine.

  I've fixed this by shutting down the BT service before suspend, and
  starting it back up on wake, as indicated here:
  https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately-
  after-suspend

  Perhaps this script should be included in blueZ as suspend issues seem
  very hard to debug and the immediate wake after suspend could be
  caused many any number of things.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1 [modified: 
lib/systemd/system/bluetooth.service]
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Apr  3 13:16:14 2019
  InstallationDate: Installed on 2019-02-09 (53 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0051.2018.1015.1513
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:BB:60:50:92:5D  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1912660 acl:106009 sco:0 events:337 errors:0
TX bytes:12331 acl:74 sco:0 commands:204 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+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 1842161] Re: api hack or virus i think idk

2019-09-01 Thread Daniel van Vugt
The log message at the top of your screenshot is nothing to worry about,
that's just part of gnome-shell. But it might be a bug...

To help us diagnose it further please run this command to collect the
system log:

  journalctl -b0 > journal.txt

Or if you have since rebooted then please run:

  journalctl -b-1 > journal.txt

Make sure the error is in that log file and then please attach it here.

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

** Summary changed:

- api hack or virus i think idk 
+ Some code accessed the property 'discreteGpuAvailable' on the module 
'appDisplay'.

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

Title:
  Some code accessed the property 'discreteGpuAvailable' on the module
  'appDisplay'.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  idk how to show you

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.394
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 30 23:56:28 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Device [196e:0f00]
  LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
  MachineType: Dell Inc. Inspiron 546
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0F896N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/12/2009:svnDellInc.:pnInspiron546:pvr:rvnDellInc.:rn0F896N:rvrA03:cvnDellInc.:ct3:cvr:
  dmi.product.name: Inspiron 546
  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.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842161/+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 1842212] Re: I can't change "Formats" in "Language and Region"

2019-09-01 Thread Gunnar Hjalmarsson
When looking at this, I run into bug #1842256, which is kind of related.
But fixing accountsservice is prio 1.

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

Title:
  I can't change "Formats" in "Language and Region"

Status in accountsservice package in Ubuntu:
  Triaged

Bug description:
  If I try to change format from "Ukraine" to "United Kingdom", system
  offers me to restart to complete the changes, but after this actions I
  don't see any changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.33.90-1ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  1 17:12:15 2019
  InstallationDate: Installed on 2019-09-01 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190830)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1842212/+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 1842212] Re: I can't change "Formats" in "Language and Region"

2019-09-01 Thread Gunnar Hjalmarsson
Thanks for your report!

It's the accountsservice package which is broken somehow. I downgraded
accountsservice to the version used in disco, and then it worked as
usual.

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => High

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Triaged

** Package changed: gnome-control-center (Ubuntu) => accountsservice
(Ubuntu)

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

Title:
  I can't change "Formats" in "Language and Region"

Status in accountsservice package in Ubuntu:
  Triaged

Bug description:
  If I try to change format from "Ukraine" to "United Kingdom", system
  offers me to restart to complete the changes, but after this actions I
  don't see any changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.33.90-1ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  1 17:12:15 2019
  InstallationDate: Installed on 2019-09-01 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190830)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1842212/+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 1842212] [NEW] I can't change "Formats" in "Language and Region"

2019-09-01 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

If I try to change format from "Ukraine" to "United Kingdom", system
offers me to restart to complete the changes, but after this actions I
don't see any changes.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.33.90-1ubuntu2
ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
Uname: Linux 5.2.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep  1 17:12:15 2019
InstallationDate: Installed on 2019-09-01 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190830)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: accountsservice (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: amd64 apport-bug eoan
-- 
I can't change "Formats" in "Language and Region"
https://bugs.launchpad.net/bugs/1842212
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to accountsservice in Ubuntu.

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


[Touch-packages] [Bug 1842255] Re: package libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu] failed to install/upgrade: package libnss3:amd64 is already installed and configured

2019-09-01 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu]
  failed to install/upgrade: package libnss3:amd64 is already installed
  and configured

Status in nss package in Ubuntu:
  New

Bug description:
  No more

  ProblemType: Package
  DistroRelease: elementary 0.4.1
  Package: libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6
  ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14.1
  Architecture: amd64
  Date: Sun Sep  1 13:00:20 2019
  DuplicateSignature:
   package:libnss3:amd64:2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu]
   Removing linux-modules-4.15.0-43-generic (4.15.0-43.46~16.04.1) ...
   dpkg: error processing package libnss3-nssdb (--configure):
package libnss3-nssdb is already installed and configured
  ErrorMessage: package libnss3:amd64 is already installed and configured
  InstallationDate: Installed on 2018-05-26 (463 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: nss
  Title: package libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu] 
failed to install/upgrade: package libnss3:amd64 is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1842255/+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 1842255] [NEW] package libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu] failed to install/upgrade: package libnss3:amd64 is already installed and configured

2019-09-01 Thread Fabio
Public bug reported:

No more

ProblemType: Package
DistroRelease: elementary 0.4.1
Package: libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6
ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-58-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.19
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14.1
Architecture: amd64
Date: Sun Sep  1 13:00:20 2019
DuplicateSignature:
 package:libnss3:amd64:2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu]
 Removing linux-modules-4.15.0-43-generic (4.15.0-43.46~16.04.1) ...
 dpkg: error processing package libnss3-nssdb (--configure):
  package libnss3-nssdb is already installed and configured
ErrorMessage: package libnss3:amd64 is already installed and configured
InstallationDate: Installed on 2018-05-26 (463 days ago)
InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32
SourcePackage: nss
Title: package libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu] failed 
to install/upgrade: package libnss3:amd64 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package loki third-party-packages

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

Title:
  package libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu]
  failed to install/upgrade: package libnss3:amd64 is already installed
  and configured

Status in nss package in Ubuntu:
  New

Bug description:
  No more

  ProblemType: Package
  DistroRelease: elementary 0.4.1
  Package: libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6
  ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14.1
  Architecture: amd64
  Date: Sun Sep  1 13:00:20 2019
  DuplicateSignature:
   package:libnss3:amd64:2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu]
   Removing linux-modules-4.15.0-43-generic (4.15.0-43.46~16.04.1) ...
   dpkg: error processing package libnss3-nssdb (--configure):
package libnss3-nssdb is already installed and configured
  ErrorMessage: package libnss3:amd64 is already installed and configured
  InstallationDate: Installed on 2018-05-26 (463 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: nss
  Title: package libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu] 
failed to install/upgrade: package libnss3:amd64 is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1842255/+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 1841654] Re: Consider replacing mawk with gawk in main

2019-09-01 Thread Thomas Dickey
I updated the webpage last week, to reduce confusion:

https://invisible-island.net/mawk/mawk.html

However, back to the stated issue: if the packager follows the same
guidelines as previously stated (100% compatibility with the existing
scripts, no effort whatsoever required of the packager), it's not likely
that any change will be made.

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

Title:
  Consider replacing mawk with gawk in main

Status in mawk package in Ubuntu:
  New

Bug description:
  For POSIX compatibility reasons Ubuntu ships with mawk ("Mike's awk" =
  mawk) in main. There is an awk-symlink to mawk, thus mawk is the
  official awk implementation in Ubuntu.

  == Reasons against keeping mawk ==

  *The mawk package is synced from debian and it is heavily
  undermaintained: Debian (and thus Ubuntu) still ships version
  1.3.3-17, the same version at least since oldoldstable:
  https://packages.debian.org/search?searchon=names=mawk

  *maintainer Thomas E. Dickey (https://invisible-island.net/mawk/)
  called officially out that Debian "neglected" mawk in 2014 ("As noted,
  mawk has been neglected by some packagers (see for example this
  http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=mawk)". And
  Debian (and Ubuntu) still ship the same version five years later

  *Most other distributions ship mawk at least in its last official
  incarnation 1.3.4 in their repositories. Dickey lists AIX, Fedora,
  FinkPorts (Mac OS X), FreeBSD port, Gentoo, HPUX, MacPorts (Mac OS X),
  NetBSD pkgsrc/lang, OpenCSW (Solaris). That version is from 2014 and
  at first it looked like it wasn't developed anymore:
  https://github.com/ThomasDickey/mawk-20140914/commits/master A recent
  comment by Thomas Dickey below indicates that he is still maintaining
  mawk.

  *A planned rewrite mawk2 was planned by original author Mike Brennan
  in 2016 but obviously came to nothing:
  https://github.com/ploxiln/mawk-2/commits/master

  *Thus mawk sits in Ubuntu main in a version published upstream in 2009
  and celebrates its 10th anniversary of negligence. In a state that
  Debian was called out for 5 years ago.

  *This year it is 10 years unmaintained and largely untouched. At the
  end of the next LTS-support-cycle we can celebrate 15 years of not
  supporting it.

  *awk is included in Linux for POSIX standard compliance. Mawk is known
  to be fast and small but it is the implementation that is farthest
  from being POSIX compliant, missing things like named character
  classes like [[:space:]] within its EREs.

  == Reasons for gawk as a replacement ==

  *It is the official GNU awk implementation and known to work well with
  the rest of the GNU userland.

  *It is actively maintained with the last version 5.01 shipping in
  June, 2019 (even if Ubuntu will obviously still ship 4.2 for Eoan).

  *It is mostly compliant with the POSIX standard.

  *Most other distributions ship it as the standard POSIX
  implementation, with a awk symlink. So it had security reviews already
  by Red Hat and others.

  == Possible problems with switching to gawk in time for Ubuntu 20.4 ==

  - It might need to be MIRed by the Ubuntu security team and a review
  might take some time. So I filed this bug early with Eoan not yet out
  of the door.

  - It is much larger than mawk, the Ubuntu package is 1600 kB in size,
  while mawk is only about 190KB. Thus some might want to split out some
  basic functionality to save size. Like what is vim-tiny to vim. To
  start gawk in --traditional or --posix mode and disable the extensions
  at compile time might be a good start to reduce the size. See:
  https://www.gnu.org/software/gawk/manual/html_node/Additional-
  Configuration-Options.html#Additional-Configuration-Options

  =

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mawk 1.3.3-17ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 27 20:12:11 2019
  Dependencies:
   gcc-9-base 9.1.0-2ubuntu2~19.04
   libc6 2.29-0ubuntu2
   libgcc1 1:9.1.0-2ubuntu2~19.04
   libidn2-0 2.0.5-1
   libunistring2 0.9.10-1ubuntu2
  InstallationDate: Installed on 2018-02-23 (550 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SourcePackage: mawk
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

2019-09-01 Thread Jón Bjarni Bjarnason
Hi

I tried your fix Dan and it seems not to work. I am running on popOs
19.04 (Dell latitude E6530 i7)

kernel vers: Linux 5.0.0-25-generic x86_64

$ sudo apt-cache policy bluez
bluez:
  Installed: 5.50-0ubuntu2+bug1759836v20190827b1~disco

from top: 
488 root  20   0   66264  51564   3208 R 100.0   0.4  18:10.64 systemd-udevd

I previously disabled the bluetooth in the bios.

This is my .rules file (after the update):

# do not edit this file, it will be overwritten on update

ACTION!="add", GOTO="hid2hci_end"
SUBSYSTEM!="usb*", GOTO="hid2hci_end"

# Variety of Dell Bluetooth devices - match on a mouse device that is
# self powered and where a HID report needs to be sent to switch modes
# Known supported devices: 413c:8154, 413c:8158, 413c:8162
ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01", 
ATTR{bInterfaceProtocol}=="02", \
  ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c", 
ATTRS{bmAttributes}=="e0", \
  RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"

# Logitech devices
KERNEL=="hiddev*", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \
  RUN+="hid2hci --method=logitech-hid --devpath=%p"
# Logitech, Inc. diNovo Edge Keyboard
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c7[01]4", \
  RUN+="hid2hci --method=logitech-hid --devpath=%p"

ENV{DEVTYPE}!="usb_device", GOTO="hid2hci_end"

# When a Dell device recovers from S3, the mouse child needs to be repoked
# Unfortunately the only event seen is the BT device disappearing, so the mouse
# device needs to be chased down on the USB bus.
ATTR{bDeviceClass}=="e0", ATTR{bDeviceSubClass}=="01", 
ATTR{bDeviceProtocol}=="01", ATTR{idVendor}=="413c", \
  ENV{REMOVE_CMD}="/sbin/udevadm trigger --action=change --subsystem-match=usb 
--property-match=HID2HCI_SWITCH=1"

# CSR devices
ATTR{idVendor}=="0a12|0458|05ac", ATTR{idProduct}=="1000", RUN+="hid2hci 
--method=csr --devpath=%p"

LABEL="hid2hci_end"

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

Title:
  systemd-udevd consumes 100% of CPU

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in bluez package in Debian:
  Unknown

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2019-09-01 Thread Dmitrii Shcherbakov
On 19.04 I can see the following (correct) behavior.

With VPN (turned on via NetworkManager):

# note: no "global" DNS servers have been configured by hand through
systemd-resolved conf using "DNS=" directive

systemd-resolved --status

# ...

Link 15 (tun0)
  Current Scopes: DNS
DefaultRoute setting: yes
   LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
  DNSSEC setting: no
DNSSEC supported: no
  Current DNS Server: 
 DNS Servers: 
  
  DNS Domain: ~.


Link 2 (wlp59s0)
  Current Scopes: DNS
DefaultRoute setting: yes
   LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
  DNSSEC setting: no
DNSSEC supported: no
  Current DNS Server: 
 DNS Servers: 
  
  DNS Domain: deadbeefcafe


Without VPN:

systemd-resolved --status
# ...

Link 2 (wlp59s0)
  Current Scopes: DNS
DefaultRoute setting: yes
   LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
  DNSSEC setting: no
DNSSEC supported: no
  Current DNS Server: 
 DNS Servers: 
  
  DNS Domain: ~.
  deadbeefcafe


"~." configuration goes to the tun0 interface once VPN is enabled and is 
removed from the physical interface. In this example it means that 
DHCP-advertised local DNS servers will be used for deadbeefcafe domain only and 
everything else will go through the DNS servers of a VPN service.

Clarifications on how "~." affects DNS request routing:

https://github.com/systemd/systemd/blame/v240/src/resolve/resolved-dns-scope.c#L1411-L1418
 * "~."  really trumps everything and clearly indicates that 
this interface shall receive all
 * traffic it can get. */
http://manpages.ubuntu.com/manpages/disco/man5/resolved.conf.5.html#options
https://www.freedesktop.org/software/systemd/man/resolved.conf.html#Domains=

Packages:

ii  network-manager   1.16.0-0ubuntu2   
amd64network management framework (daemon and userspace tools)
ii  network-manager-config-connectivity-ubuntu1.16.0-0ubuntu2   
all  NetworkManager configuration to enable connectivity 
checking
ii  network-manager-gnome 1.8.20-1ubuntu1   
amd64network management framework (GNOME frontend)
ii  network-manager-openvpn   1.8.10-1  
amd64network management framework (OpenVPN plugin core)
ii  network-manager-openvpn-gnome 1.8.10-1  
amd64network management framework (OpenVPN plugin GNOME GUI)
ii  netplan.io0.97-0ubuntu1~19.04.1 
amd64YAML network configuration abstraction for various backends
ii  systemd   240-6ubuntu5.3
amd64system and service manager


I have also captured DNS packets on all interfaces via Wireshark and confirmed 
that DNS requests go to the correct DNS servers on 19.04.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Won't Fix

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN 

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

2019-09-01 Thread Amr Ibrahim
** Also affects: spyderlib via
   https://github.com/spyder-ide/spyder/issues/7008
   Importance: Unknown
   Status: Unknown

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

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

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

Bug description:
  In Ubuntu 18.04 LTS
  Steps:

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

  Keyboard shortcuts are not accessible.

  Here is the error:

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

[Touch-packages] [Bug 1731416] Re: libv4l-0 freezes mouse and keyboard with Logitech QuickCam 4000

2019-09-01 Thread Gregor Jasny
This is a kernel issue and most likely caused by bad hardware or buggy
drivers.

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

Title:
  libv4l-0 freezes mouse and keyboard with Logitech QuickCam 4000

Status in v4l-utils package in Ubuntu:
  New

Bug description:
  I've recently moved from FC25 to KUbuntu 17.10 and the video-
  surveillance program is causing the system to freeze all usb
  peripherals (mouse, keyboard, bluetooth, etc...). As a consequence the
  only solution is to remote login and kill the process using the
  capture device.

  Camera: Logitech QuickCam 4000 Pro USB (old model)
  I've tried with newer webcams and it works.

  Steps:
  - Start any video capturing program e.g. vlc
  - start video Capture with Ctrl-C with the default Video Camera
  - After 1-2 frames the systems freezes
  - Killing the application, unfreezes the system

  The dmesg is full of repeated messages:
  Nov 10 09:02:50 pceet070 kernel: [54333.596539] xhci_hcd :00:14.0: ERROR 
unknown event type 37
  ...
  Nov 10 09:02:50 pceet070 kernel: [54333.599623] xhci_hcd :00:14.0: ERROR 
unknown event type 37
  Nov 10 09:03:17 pceet070 kernel: [54361.410778] usb 3-10: reset high-speed 
USB device number 7 using xhci_hcd
  Nov 10 09:03:17 pceet070 kernel: [54361.534035] pwc: Failed to set LED on/off 
time (-110)
  Nov 10 09:03:23 pceet070 kernel: [54366.654102] pwc: Failed to power off 
camera (-110)
  Nov 10 09:03:23 pceet070 kernel: [54366.882544] usb 3-10: device descriptor 
read/64, error -110
  Nov 10 09:06:10 pceet070 colord[1155]: failed to get session [pid 14132]: No 
data available

  Trying to debug with a simplified grabbing program 
https://github.com/vlachoudis/motion_detect
  The freezing happens at the v4l2_ioctl(.., VIDIOC_DQBUF, ...) 

  Removing the NONBLOCK from the open() of the handle it freezes with other 
messages
  0008047a3000 seg-end 0008047a3ff0
  [55505.385380] xhci_hcd :00:14.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 10 comp_code 13
  [55505.385388] xhci_hcd :00:14.0: Looking for event-dma 0008047a20d0 
trb-start 0008047a3f30 trb-end 0008047a3f30 seg-start 0008047a3000 
seg-end 0008047a3ff0
  [55505.386392] xhci_hcd :00:14.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 10 comp_code 13
  [55505.386400] xhci_hcd :00:14.0: Looking for event-dma 0008047a20e0 
trb-start 0008047a3f30 trb-end 0008047a3f30 seg-start 0008047a3000 
seg-end 0008047a3ff0

  Please let me know what other tests I can perform to further debug the problem
  Thanks in advance
  Vasilis

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1731416/+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 1841269] Re: dvbv5-scan Segmentation fault

2019-09-01 Thread Gregor Jasny
** Changed in: v4l-utils (Ubuntu)
   Status: New => In Progress

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

Title:
  dvbv5-scan Segmentation fault

Status in v4l-utils package in Ubuntu:
  In Progress

Bug description:
  LANG=en_US.UTF-8 gdb -ex=r --args dvbv5-scan -l UNIVERSAL -S0 -v -o 
Turksat.conf ./Turksat-42.0E 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Using LNBf UNIVERSAL
Universal, Europe
Freqs : 10800 to 11800 MHz, LO: 9750 MHz
Freqs : 11600 to 12700 MHz, LO: 10600 MHz
  using demux 'dvb0.demux0'
  Device Montage Technology DS3000/TS2020 (/dev/dvb/adapter0/frontend0) 
capabilities:
   CAN_2G_MODULATION
   CAN_FEC_1_2
   CAN_FEC_2_3
   CAN_FEC_3_4
   CAN_FEC_4_5
   CAN_FEC_5_6
   CAN_FEC_6_7
   CAN_FEC_7_8
   CAN_FEC_AUTO
   CAN_INVERSION_AUTO
   CAN_QPSK
   CAN_RECOVER
  DVB API Version 5.11, Current v5 delivery system: DVBS
  Supported delivery systems: 
  [DVBS]
   DVBS2
  Failed to guess country from the current locale setting.

  ERRORcommand BANDWIDTH_HZ (5) not found during retrieve
  Cannot calc frequency shift. Either bandwidth/symbol-rate is unavailable 
(yet).
  Scanning frequency #1 12346000
  frequency: 12346,00 MHz, high_band: 1
  SEC: set voltage to 18V
  DiSEqC TONE: OFF
  DiSEqC command: e0 10 38 f3 
  DiSEqC BURST: SEC_MINI_A
  DiSEqC TONE: ON
  L-Band frequency: 1746,00 MHz (offset = 10600,00 MHz)
  FREQUENCY = 12346000
  INVERSION = AUTO
  SYMBOL_RATE = 960
  INNER_FEC = 3/4
  POLARIZATION = HORIZONTAL
  DELIVERY_SYSTEM = DVBS
  Got parameters for DVBS:
  FREQUENCY = 12346000
  INVERSION = AUTO
  SYMBOL_RATE = 960
  INNER_FEC = 3/4
  POLARIZATION = HORIZONTAL
  DELIVERY_SYSTEM = DVBS
  Lock   (0x1f) Signal= 37,86% C/N= 47,97% UCB= 31440 postBER= 0
  dvb_read_sections: waiting for table ID 0x00, program ID 0x00
  dvb_parse_section: received table 0x00, extension ID 0xa414, section 0/0
  dvb_parse_section: table 0x00, extension ID 0xa414: done
  PAT
  | table_id 0x00
  | section_length  25
  | one 3
  | zero0
  | syntax  1
  | transport_stream_id 42004
  | current_next1
  | version 14
  | one23
  | section_number  0
  | last_section_number 0
  |\ 4 program pids
  |  pid 0x0010: service 0x
  |  pid 0x0065: service 0x3264
  |  pid 0x012d: service 0x3265
  |  pid 0x0066: service 0x3269
  Program #0 is network PID: 0x0010
  Program #1 ID 0x0065, service ID 0x3264
  dvb_read_sections: waiting for table ID 0x02, program ID 0x65
  dvb_parse_section: received table 0x02, extension ID 0x3264, section 0/0
  dvb_parse_section: table 0x02, extension ID 0x3264: done
  PMT
  | table_id 0x02
  | section_length  112
  | one 3
  | zero0
  | syntax  1
  | transport_stream_id 12900
  | current_next1
  | version 7
  | one23
  | section_number  0
  | last_section_number 0
  |- pcr_pid  0b54
  |  reserved2   7
  |  descriptor length   11
  |  zero3   0
  |  reserved3  15
  |0x0c: multiplex_buffer_utilization_descriptor
  |   80 b4 81 68...h
  |0x0e: maximum_bitrate_descriptor
  |   c0 3e a4   .>.
  |\
  |- stream 0x0b54: Video ISO/IEC 13818-2 (2)
  |descriptor length   16
  |0x52: stream_identifier_descriptor
  |   01 .
  |0x02: video_stream_descriptor
  |   1a 48 5f   .H_
  |0x06: ds_alignment_descriptor
  |   02 .
  |0x0e: maximum_bitrate_descriptor
  |   c0 39 4e   .9N
  |- stream 0x0bb8: Audio ISO/IEC 13818-3 (4)
  |descriptor length   17
  |0x52: stream_identifier_descriptor
  |   02 .
  |0x0a: iso639_language_descriptor
  |   lang: tur (type: 0)
  |0x03: audio_stream_descriptor
  |   67 g
  |0x0e: maximum_bitrate_descriptor
  |   c0 02 90   ...
  |- stream 0x0c1c: Audio ISO/IEC 13818-3 (4)
  |descriptor length   17
  |0x52: stream_identifier_descriptor
  |   03 .
  |0x0a: iso639_language_descriptor
  |   lang: eng (type: 0)
  |0x03: audio_stream_descriptor
  |   67   

[Touch-packages] [Bug 1833536] Re: QuiteRSS crashes intermittently

2019-09-01 Thread Dmitry Shachnev
And now I have verified the fix for Disco using the same steps.

** Attachment added: "VirtualBox_Ubuntu 19.04_01_09_2019_15_28_44.png"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+attachment/5286070/+files/VirtualBox_Ubuntu%2019.04_01_09_2019_15_28_44.png

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

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

Title:
  QuiteRSS crashes intermittently

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Fix Committed
Status in qtbase-opensource-src source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  This bug affects QuiteRSS and other Qt applications, like plasma-discover 
(see https://bugs.kde.org/show_bug.cgi?id=402848) and qbittorrent (see bug 
1814375). All they crash with similar stack traces.

  [Test Case]
  1. Open QuiteRSS.
  2. Leave it running for several hours.
  3. It should not crash.

  [Proposed Fix]
  The proposed fix is a backport of the following commit from upstream 5.12 
branch: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e431a3ac027915db

  [Regression Potential]
  This patch adds an additional check before re-sending the request. 
Regressions chance is minimal, but the potential regressions may be that the 
request is not re-sent where it was re-sent with the previous code.

  [Original Description]
  After opening QuiteRSS it will run until crash happens.  This happens 
intermittently within the hour usually.

  (gdb) bt
  #0  QHttpNetworkConnectionChannel::sendRequest (this=)
  at access/qhttpnetworkconnectionchannel.cpp:238
  #1  0x730deca2 in QHttpNetworkConnectionPrivate::_q_startNextRequest (
  this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015
  #2  0x72736122 in QObject::event (this=0x7fff48da89b0,
  e=) at kernel/qobject.cpp:1247
  #3  0x76f2482c in QApplicationPrivate::notify_helper(QObject*, 
QEvent*)
  () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #4  0x76f2c0f4 in QApplication::notify(QObject*, QEvent*) ()
     from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #5  0x727069a8 in QCoreApplication::notifyInternal2 (
  receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0)
  at kernel/qcoreapplication.cpp:1024
  #6  0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0,
  receiver=)
  at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233
  #7  QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
  event_type=event_type@entry=0, data=0x7fff60008e90)
  at kernel/qcoreapplication.cpp:1699
  #8  0x727096a8 in QCoreApplication::sendPostedEvents (
  receiver=receiver@entry=0x0, event_type=event_type@entry=0)
  at kernel/qcoreapplication.cpp:1553
  #9  0x727602c3 in postEventSourceDispatch (s=0x7fff48003f10)
  at kernel/qeventdispatcher_glib.cpp:276
  #10 0x7fffece96317 in g_main_context_dispatch ()
     from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x7fffece96550 in ?? () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #12 0x7fffece965dc in g_main_context_iteration ()
     from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #13 0x7275f8ef in QEventDispatcherGlib::processEvents (
  this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423
  #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60,
  flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
  #15 0x7252322a in QThread::exec (this=)
  at thread/qthread.cpp:515
  #16 0x7252816d in QThreadPrivate::start (arg=0x7fff60008a20)
  at thread/qthread_unix.cpp:368
  #17 0x722646db in start_thread (arg=0x7fff4700)
  at pthread_create.c:463
  #18 0x719ec88f in clone ()
  at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+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 1842205] Re: 18 second delay during login

2019-09-01 Thread Robert Dinse
Requested by lotuspsychje 

** Attachment added: "Output of systemd-analyze blame"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842205/+attachment/5286068/+files/blame

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

Title:
  18 second delay during login

Status in systemd package in Ubuntu:
  New

Bug description:
   I am experiencing an 18 second delay during login between the
  time the X-server and saved applications start, and the background,
  panels, and rest of the Mate desktop draw.

   I have tried new user with no configuration to eliminate user 
configuration date.  I've tried
  different desktop environments to eliminate them.  I've tried different 
greeters and different
  display managers.  Symptoms don't change.

   Out of desperation I grabbed the most recent systemd off of github and 
compiled and installed
  it, version 243 verses version 240 shipped with Ubuntu 19.04.

   With version 243 login no longer has delay but audio breaks.  The fact 
that replacing systemd
  got rid of the delay tells me the delay is in that package.  I can find 
nothing in the logs that
  would give me a clue as to what is wrong, no errors in that time frame, in 
fact NOTHING logs during
  that interval.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 240-6ubuntu5.4
  ProcVersionSignature: Ubuntu 5.0.0-27.28-lowlatency 5.0.21
  Uname: Linux 5.0.0-27-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Sep  1 03:19:08 2019
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-lowlatency 
root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro quiet splash 
xdg.force_integrated=1 modprobe.blacklist=nouveau vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1105
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z390-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1105:bd06/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.systemd.journald.conf: [modified]
  modified.conffile..etc.systemd.logind.conf: [modified]
  modified.conffile..etc.systemd.networkd.conf: [modified]
  modified.conffile..etc.systemd.resolved.conf: [modified]
  modified.conffile..etc.systemd.system.conf: [modified]
  modified.conffile..etc.systemd.timesyncd.conf: [modified]
  modified.conffile..etc.systemd.user.conf: [modified]
  mtime.conffile..etc.systemd.journald.conf: 2019-08-31T23:59:42.943575
  mtime.conffile..etc.systemd.logind.conf: 2019-09-01T00:28:56.884198
  mtime.conffile..etc.systemd.networkd.conf: 2019-08-31T23:59:42.978575
  mtime.conffile..etc.systemd.resolved.conf: 2019-09-01T00:28:56.953197
  mtime.conffile..etc.systemd.system.conf: 2019-09-01T00:28:56.906198
  mtime.conffile..etc.systemd.timesyncd.conf: 2019-09-01T00:28:56.956197
  mtime.conffile..etc.systemd.user.conf: 2019-09-01T00:28:56.907198

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

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


Re: [Touch-packages] [Bug 1842205] Re: 18 second delay during login

2019-09-01 Thread Robert Dinse
I've included them per your request but I do not think it will help
much because the issue isn't boot time, that happens in about 4 seconds,
it's login time, and specifically the time between when the X server starts
and displays saved apps and when it gets around to drawing the panels and
background.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Sun, 1 Sep 2019, lotuspsychje wrote:

> Date: Sun, 01 Sep 2019 11:53:47 -
> From: lotuspsychje 
> Reply-To: Bug 1842205 <1842...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1842205] Re: 18 second delay during login
> 
> Thank you for reporting this bug and make ubuntu better!
>
> Could you attach these outputs too please:
>
> systemd-analyze blame and
> systemd-analyze critical-chain
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1842205
>
> Title:
>  18 second delay during login
>
> Status in systemd package in Ubuntu:
>  New
>
> Bug description:
>   I am experiencing an 18 second delay during login between the
>  time the X-server and saved applications start, and the background,
>  panels, and rest of the Mate desktop draw.
>
>   I have tried new user with no configuration to eliminate user 
> configuration date.  I've tried
>  different desktop environments to eliminate them.  I've tried different 
> greeters and different
>  display managers.  Symptoms don't change.
>
>   Out of desperation I grabbed the most recent systemd off of github and 
> compiled and installed
>  it, version 243 verses version 240 shipped with Ubuntu 19.04.
>
>   With version 243 login no longer has delay but audio breaks.  The fact 
> that replacing systemd
>  got rid of the delay tells me the delay is in that package.  I can find 
> nothing in the logs that
>  would give me a clue as to what is wrong, no errors in that time frame, in 
> fact NOTHING logs during
>  that interval.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 19.04
>  Package: systemd 240-6ubuntu5.4
>  ProcVersionSignature: Ubuntu 5.0.0-27.28-lowlatency 5.0.21
>  Uname: Linux 5.0.0-27-lowlatency x86_64
>  ApportVersion: 2.20.10-0ubuntu27.1
>  Architecture: amd64
>  CurrentDesktop: MATE
>  Date: Sun Sep  1 03:19:08 2019
>  MachineType: System manufacturer System Product Name
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-lowlatency 
> root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro quiet splash 
> xdg.force_integrated=1 modprobe.blacklist=nouveau vt.handoff=1
>  SourcePackage: systemd
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  dmi.bios.date: 06/06/2019
>  dmi.bios.vendor: American Megatrends Inc.
>  dmi.bios.version: 1105
>  dmi.board.asset.tag: Default string
>  dmi.board.name: PRIME Z390-A
>  dmi.board.vendor: ASUSTeK COMPUTER INC.
>  dmi.board.version: Rev 1.xx
>  dmi.chassis.asset.tag: Default string
>  dmi.chassis.type: 3
>  dmi.chassis.vendor: Default string
>  dmi.chassis.version: Default string
>  dmi.modalias: 
> dmi:bvnAmericanMegatrendsInc.:bvr1105:bd06/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
>  dmi.product.family: To be filled by O.E.M.
>  dmi.product.name: System Product Name
>  dmi.product.sku: ASUS_MB_CNL
>  dmi.product.version: System Version
>  dmi.sys.vendor: System manufacturer
>  modified.conffile..etc.systemd.journald.conf: [modified]
>  modified.conffile..etc.systemd.logind.conf: [modified]
>  modified.conffile..etc.systemd.networkd.conf: [modified]
>  modified.conffile..etc.systemd.resolved.conf: [modified]
>  modified.conffile..etc.systemd.system.conf: [modified]
>  modified.conffile..etc.systemd.timesyncd.conf: [modified]
>  modified.conffile..etc.systemd.user.conf: [modified]
>  mtime.conffile..etc.systemd.journald.conf: 2019-08-31T23:59:42.943575
>  mtime.conffile..etc.systemd.logind.conf: 2019-09-01T00:28:56.884198
>  mtime.conffile..etc.systemd.networkd.conf: 2019-08-31T23:59:42.978575
>  mtime.conffile..etc.systemd.resolved.conf: 2019-09-01T00:28:56.953197
>  mtime.conffile..etc.systemd.system.conf: 2019-09-01T00:28:56.906198
>  mtime.conffile..etc.systemd.timesyncd.conf: 2019-09-01T00:28:56.956197
>  mtime.conffile..etc.systemd.user.conf: 2019-09-01T00:28:56.907198
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842205/+subscriptions
>

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

Title:
  18 second delay during login

Status in systemd package in Ubuntu:
  New

Bug 

[Touch-packages] [Bug 1842205] Re: 18 second delay during login

2019-09-01 Thread Robert Dinse
Requested by lotuspsychje 

** Attachment added: "Output of systemd-analyze critical-chain"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842205/+attachment/5286069/+files/critical-chain

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

Title:
  18 second delay during login

Status in systemd package in Ubuntu:
  New

Bug description:
   I am experiencing an 18 second delay during login between the
  time the X-server and saved applications start, and the background,
  panels, and rest of the Mate desktop draw.

   I have tried new user with no configuration to eliminate user 
configuration date.  I've tried
  different desktop environments to eliminate them.  I've tried different 
greeters and different
  display managers.  Symptoms don't change.

   Out of desperation I grabbed the most recent systemd off of github and 
compiled and installed
  it, version 243 verses version 240 shipped with Ubuntu 19.04.

   With version 243 login no longer has delay but audio breaks.  The fact 
that replacing systemd
  got rid of the delay tells me the delay is in that package.  I can find 
nothing in the logs that
  would give me a clue as to what is wrong, no errors in that time frame, in 
fact NOTHING logs during
  that interval.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 240-6ubuntu5.4
  ProcVersionSignature: Ubuntu 5.0.0-27.28-lowlatency 5.0.21
  Uname: Linux 5.0.0-27-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Sep  1 03:19:08 2019
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-lowlatency 
root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro quiet splash 
xdg.force_integrated=1 modprobe.blacklist=nouveau vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1105
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z390-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1105:bd06/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.systemd.journald.conf: [modified]
  modified.conffile..etc.systemd.logind.conf: [modified]
  modified.conffile..etc.systemd.networkd.conf: [modified]
  modified.conffile..etc.systemd.resolved.conf: [modified]
  modified.conffile..etc.systemd.system.conf: [modified]
  modified.conffile..etc.systemd.timesyncd.conf: [modified]
  modified.conffile..etc.systemd.user.conf: [modified]
  mtime.conffile..etc.systemd.journald.conf: 2019-08-31T23:59:42.943575
  mtime.conffile..etc.systemd.logind.conf: 2019-09-01T00:28:56.884198
  mtime.conffile..etc.systemd.networkd.conf: 2019-08-31T23:59:42.978575
  mtime.conffile..etc.systemd.resolved.conf: 2019-09-01T00:28:56.953197
  mtime.conffile..etc.systemd.system.conf: 2019-09-01T00:28:56.906198
  mtime.conffile..etc.systemd.timesyncd.conf: 2019-09-01T00:28:56.956197
  mtime.conffile..etc.systemd.user.conf: 2019-09-01T00:28:56.907198

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842205/+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 1841269] Re: dvbv5-scan Segmentation fault

2019-09-01 Thread Gregor Jasny
You could use the
https://launchpad.net/~libv4l/+archive/ubuntu/development PPA to get a
fixed version. I'll update the stable PPA soon.

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

Title:
  dvbv5-scan Segmentation fault

Status in v4l-utils package in Ubuntu:
  New

Bug description:
  LANG=en_US.UTF-8 gdb -ex=r --args dvbv5-scan -l UNIVERSAL -S0 -v -o 
Turksat.conf ./Turksat-42.0E 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Using LNBf UNIVERSAL
Universal, Europe
Freqs : 10800 to 11800 MHz, LO: 9750 MHz
Freqs : 11600 to 12700 MHz, LO: 10600 MHz
  using demux 'dvb0.demux0'
  Device Montage Technology DS3000/TS2020 (/dev/dvb/adapter0/frontend0) 
capabilities:
   CAN_2G_MODULATION
   CAN_FEC_1_2
   CAN_FEC_2_3
   CAN_FEC_3_4
   CAN_FEC_4_5
   CAN_FEC_5_6
   CAN_FEC_6_7
   CAN_FEC_7_8
   CAN_FEC_AUTO
   CAN_INVERSION_AUTO
   CAN_QPSK
   CAN_RECOVER
  DVB API Version 5.11, Current v5 delivery system: DVBS
  Supported delivery systems: 
  [DVBS]
   DVBS2
  Failed to guess country from the current locale setting.

  ERRORcommand BANDWIDTH_HZ (5) not found during retrieve
  Cannot calc frequency shift. Either bandwidth/symbol-rate is unavailable 
(yet).
  Scanning frequency #1 12346000
  frequency: 12346,00 MHz, high_band: 1
  SEC: set voltage to 18V
  DiSEqC TONE: OFF
  DiSEqC command: e0 10 38 f3 
  DiSEqC BURST: SEC_MINI_A
  DiSEqC TONE: ON
  L-Band frequency: 1746,00 MHz (offset = 10600,00 MHz)
  FREQUENCY = 12346000
  INVERSION = AUTO
  SYMBOL_RATE = 960
  INNER_FEC = 3/4
  POLARIZATION = HORIZONTAL
  DELIVERY_SYSTEM = DVBS
  Got parameters for DVBS:
  FREQUENCY = 12346000
  INVERSION = AUTO
  SYMBOL_RATE = 960
  INNER_FEC = 3/4
  POLARIZATION = HORIZONTAL
  DELIVERY_SYSTEM = DVBS
  Lock   (0x1f) Signal= 37,86% C/N= 47,97% UCB= 31440 postBER= 0
  dvb_read_sections: waiting for table ID 0x00, program ID 0x00
  dvb_parse_section: received table 0x00, extension ID 0xa414, section 0/0
  dvb_parse_section: table 0x00, extension ID 0xa414: done
  PAT
  | table_id 0x00
  | section_length  25
  | one 3
  | zero0
  | syntax  1
  | transport_stream_id 42004
  | current_next1
  | version 14
  | one23
  | section_number  0
  | last_section_number 0
  |\ 4 program pids
  |  pid 0x0010: service 0x
  |  pid 0x0065: service 0x3264
  |  pid 0x012d: service 0x3265
  |  pid 0x0066: service 0x3269
  Program #0 is network PID: 0x0010
  Program #1 ID 0x0065, service ID 0x3264
  dvb_read_sections: waiting for table ID 0x02, program ID 0x65
  dvb_parse_section: received table 0x02, extension ID 0x3264, section 0/0
  dvb_parse_section: table 0x02, extension ID 0x3264: done
  PMT
  | table_id 0x02
  | section_length  112
  | one 3
  | zero0
  | syntax  1
  | transport_stream_id 12900
  | current_next1
  | version 7
  | one23
  | section_number  0
  | last_section_number 0
  |- pcr_pid  0b54
  |  reserved2   7
  |  descriptor length   11
  |  zero3   0
  |  reserved3  15
  |0x0c: multiplex_buffer_utilization_descriptor
  |   80 b4 81 68...h
  |0x0e: maximum_bitrate_descriptor
  |   c0 3e a4   .>.
  |\
  |- stream 0x0b54: Video ISO/IEC 13818-2 (2)
  |descriptor length   16
  |0x52: stream_identifier_descriptor
  |   01 .
  |0x02: video_stream_descriptor
  |   1a 48 5f   .H_
  |0x06: ds_alignment_descriptor
  |   02 .
  |0x0e: maximum_bitrate_descriptor
  |   c0 39 4e   .9N
  |- stream 0x0bb8: Audio ISO/IEC 13818-3 (4)
  |descriptor length   17
  |0x52: stream_identifier_descriptor
  |   02 .
  |0x0a: iso639_language_descriptor
  |   lang: tur (type: 0)
  |0x03: audio_stream_descriptor
  |   67 g
  |0x0e: maximum_bitrate_descriptor
  |   c0 02 90   ...
  |- stream 0x0c1c: Audio ISO/IEC 13818-3 (4)
  |descriptor length   17
  |0x52: stream_identifier_descriptor
  |   03 .
  |0x0a: iso639_language_descriptor
  |   lang: eng (type: 0)
  |0x03: 

[Touch-packages] [Bug 1842133] Re: findutils shows wrong version number

2019-09-01 Thread Andreas Metzler
First off: Ubuntu/Debian do not ship "patched version of the GNU
findutils package [...] based on release 4.6.0". The ship a GIT
snapshot. e.g. 4.6.0+git+20170828-2  is upstream GIT as of 2017-08-28.
/usr/share/doc/findutils/changelog.Debian.gz even has the full
respective GIT revision. (febde26dd0e66dda5d4060fa29b85443ddc6a865.). To
clearly show that we are *not* shipping a upstream /release/ we are
using a +git version.

The version number upstream GIT snapshots report depends a little bit on
the way they are built (git present or not when make dist is invoked,
et.al), they might show 4.7.0-git or 4.6.0.235-f254 (That is
4.6.0+git+20190510-2).

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

Title:
  findutils shows wrong version number

Status in findutils package in Ubuntu:
  New

Bug description:
  This problem occurs on Ubuntu 18.04.3 LTS (bionic).
  It does not occur on Ubuntu 19.04 (disco)

  The "find" and "xargs" command are provided by a patched version of the
  GNU findutils package. The current version is based on release 4.6.0, but
  the "--version" option shows a version number of "4.7.0-git".

  As you can see, the "/usr/bin/find" executable is dated Nov 5 2017.
  findutils release 4.7.0 was released just yesterday, Aug 29 2017.

  Ubuntu 19.04 has findutils 4.6.0+git+20190209-2, and "find --version"
  shows "find (GNU findutils) 4.6.0.225-235f".

  Expected: "findutils --version" shows a version number based on 4.6.0
  Actual:   "findutils --version" shows a version number based on 4.7.0,
which had not yet been released

  Demonstration:

  $ lsb_release -rd
  Description:Ubuntu 18.04.3 LTS  
  Release:18.04
  $ apt-cache policy findutils
  findutils:
Installed: 4.6.0+git+20170828-2
Candidate: 4.6.0+git+20170828-2
Version table:
   *** 4.6.0+git+20170828-2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  $ ls -l /usr/bin/find
  -rwxr-xr-x 1 root root 238080 Nov  5  2017 /usr/bin/find
  $ /usr/bin/find --version
  find (GNU findutils) 4.7.0-git
  Copyright (C) 2017 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later .
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  Written by Eric B. Decker, James Youngman, and Kevin Dalley.
  Features enabled: D_TYPE O_NOFOLLOW(enabled) LEAF_OPTIMISATION FTS(FTS_CWDFD) 
CBO(level=2)
  $

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1842133/+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 1842205] Re: 18 second delay during login

2019-09-01 Thread lotuspsychje
Thank you for reporting this bug and make ubuntu better!

Could you attach these outputs too please:

systemd-analyze blame and
systemd-analyze critical-chain

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

Title:
  18 second delay during login

Status in systemd package in Ubuntu:
  New

Bug description:
   I am experiencing an 18 second delay during login between the
  time the X-server and saved applications start, and the background,
  panels, and rest of the Mate desktop draw.

   I have tried new user with no configuration to eliminate user 
configuration date.  I've tried
  different desktop environments to eliminate them.  I've tried different 
greeters and different
  display managers.  Symptoms don't change.

   Out of desperation I grabbed the most recent systemd off of github and 
compiled and installed
  it, version 243 verses version 240 shipped with Ubuntu 19.04.

   With version 243 login no longer has delay but audio breaks.  The fact 
that replacing systemd
  got rid of the delay tells me the delay is in that package.  I can find 
nothing in the logs that
  would give me a clue as to what is wrong, no errors in that time frame, in 
fact NOTHING logs during
  that interval.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 240-6ubuntu5.4
  ProcVersionSignature: Ubuntu 5.0.0-27.28-lowlatency 5.0.21
  Uname: Linux 5.0.0-27-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Sep  1 03:19:08 2019
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-lowlatency 
root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro quiet splash 
xdg.force_integrated=1 modprobe.blacklist=nouveau vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1105
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z390-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1105:bd06/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.systemd.journald.conf: [modified]
  modified.conffile..etc.systemd.logind.conf: [modified]
  modified.conffile..etc.systemd.networkd.conf: [modified]
  modified.conffile..etc.systemd.resolved.conf: [modified]
  modified.conffile..etc.systemd.system.conf: [modified]
  modified.conffile..etc.systemd.timesyncd.conf: [modified]
  modified.conffile..etc.systemd.user.conf: [modified]
  mtime.conffile..etc.systemd.journald.conf: 2019-08-31T23:59:42.943575
  mtime.conffile..etc.systemd.logind.conf: 2019-09-01T00:28:56.884198
  mtime.conffile..etc.systemd.networkd.conf: 2019-08-31T23:59:42.978575
  mtime.conffile..etc.systemd.resolved.conf: 2019-09-01T00:28:56.953197
  mtime.conffile..etc.systemd.system.conf: 2019-09-01T00:28:56.906198
  mtime.conffile..etc.systemd.timesyncd.conf: 2019-09-01T00:28:56.956197
  mtime.conffile..etc.systemd.user.conf: 2019-09-01T00:28:56.907198

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842205/+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 1841654] Re: Replace mawk with gawk in main

2019-09-01 Thread amano
@Thomas Dickey: 
Wow, you were fast to find that topic ;)

I didn't want to spread misleading information, so I guess that I
misread or misinterpreted my findings and mawk is still developed and
maintained by you? Which is great to know. I probably just couldn't find
your active development branch. Mind sharing some information about it?

I don't care if Debian/Ubuntu shipped with an updated mawk version (much
smaller and faster) but for shellscript compatibility between the likes
of say Fedora and Ubuntu a switch to gawk might still be worth
considering. Any input would be welcome.

The only thing which is certainly bad is the current situation with a
version from 2009 is shipped in main without being maintained by anyone
anymore.

** Summary changed:

- Replace mawk with gawk in main
+ Consider replacing mawk with gawk in main

** Description changed:

  For POSIX compatibility reasons Ubuntu ships with mawk ("Mike's awk" =
  mawk) in main. There is an awk-symlink to mawk, thus mawk is the
  official awk implementation in Ubuntu.
  
  == Reasons against keeping mawk ==
  
  *The mawk package is synced from debian and it is heavily
  undermaintained: Debian (and thus Ubuntu) still ships version 1.3.3-17,
  the same version at least since oldoldstable:
  https://packages.debian.org/search?searchon=names=mawk
  
  *part-time maintainer Thomas E. Dickey (https://invisible-
  island.net/mawk/) called officially out that Debian "neglected" mawk in
  2014 ("As noted, mawk has been neglected by some packagers (see for
  example this http://bugs.debian.org/cgi-
  bin/pkgreport.cgi?package=mawk)". And Debian (and Ubuntu) still ship the
  same version five years later
  
  *Most other distributions ship mawk at least in its last official
  incarnation 1.3.4 in their repositories. Dickey lists AIX, Fedora,
  FinkPorts (Mac OS X), FreeBSD port, Gentoo, HPUX, MacPorts (Mac OS X),
- NetBSD pkgsrc/lang, OpenCSW (Solaris). But even that version is from
- 2014 and doesn't seem to be developed anymore:
- https://github.com/ThomasDickey/mawk-20140914/commits/master
+ NetBSD pkgsrc/lang, OpenCSW (Solaris). That version is from 2014 and at
+ first it looked like it wasn't developed anymore:
+ https://github.com/ThomasDickey/mawk-20140914/commits/master A recent
+ comment by Thomas Dickey below indicates that he is still maintaining
+ mawk.
  
  *A planned rewrite mawk2 was planned by original author Mike Brennan in
  2016 but obviously came to nothing:
  https://github.com/ploxiln/mawk-2/commits/master
  
  *Thus mawk sits in Ubuntu main in a version published upstream in 2009
  and celebrates its 10th anniversary of negligence. In a state that
  Debian was called out for 5 years ago.
  
  *This year it is 10 years unmaintained and largely untouched. At the end
  of the next LTS-support-cycle we can celebrate 15 years of not
  supporting it.
  
  *awk is included in Linux for POSIX standard compliance. Mawk is known
  to be fast and small but it is the implementation that is farthest from
  being POSIX compliant, missing things like named character classes like
  [[:space:]] within its EREs.
  
  == Reasons for gawk as a replacement ==
  
  *It is the official GNU awk implementation and known to work well with
  the rest of the GNU userland.
  
  *It is actively maintained with the last version 5.01 shipping in June,
  2019 (even if Ubuntu will obviously still ship 4.2 for Eoan).
  
  *It is mostly compliant with the POSIX standard.
  
  *Most other distributions ship it as the standard POSIX implementation,
  with a awk symlink. So it had security reviews already by Red Hat and
  others.
  
  == Possible problems with switching to gawk in time for Ubuntu 20.4 ==
  
  - It might need to be MIRed by the Ubuntu security team and a review
  might take some time. So I filed this bug early with Eoan not yet out of
  the door.
  
  - It is much larger than mawk, the Ubuntu package is 1600 kB in size,
  while mawk is only about 190KB. Thus some might want to split out some
  basic functionality to save size. Like what is vim-tiny to vim. To start
  gawk in --traditional or --posix mode and disable the extensions at
  compile time might be a good start to reduce the size. See:
  https://www.gnu.org/software/gawk/manual/html_node/Additional-
  Configuration-Options.html#Additional-Configuration-Options
  
  =
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mawk 1.3.3-17ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 27 20:12:11 2019
  Dependencies:
   gcc-9-base 9.1.0-2ubuntu2~19.04
   libc6 2.29-0ubuntu2
   libgcc1 1:9.1.0-2ubuntu2~19.04
   libidn2-0 2.0.5-1
   libunistring2 0.9.10-1ubuntu2
  InstallationDate: Installed on 2018-02-23 (550 days ago)
  InstallationMedia: Ubuntu 18.04 

[Touch-packages] [Bug 1842205] [NEW] 18 second delay during login

2019-09-01 Thread Robert Dinse
Public bug reported:

 I am experiencing an 18 second delay during login between the time
the X-server and saved applications start, and the background, panels,
and rest of the Mate desktop draw.

 I have tried new user with no configuration to eliminate user 
configuration date.  I've tried
different desktop environments to eliminate them.  I've tried different 
greeters and different
display managers.  Symptoms don't change.

 Out of desperation I grabbed the most recent systemd off of github and 
compiled and installed
it, version 243 verses version 240 shipped with Ubuntu 19.04.

 With version 243 login no longer has delay but audio breaks.  The fact 
that replacing systemd
got rid of the delay tells me the delay is in that package.  I can find nothing 
in the logs that
would give me a clue as to what is wrong, no errors in that time frame, in fact 
NOTHING logs during
that interval.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: systemd 240-6ubuntu5.4
ProcVersionSignature: Ubuntu 5.0.0-27.28-lowlatency 5.0.21
Uname: Linux 5.0.0-27-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Sep  1 03:19:08 2019
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-lowlatency 
root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro quiet splash 
xdg.force_integrated=1 modprobe.blacklist=nouveau vt.handoff=1
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1105
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z390-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1105:bd06/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: ASUS_MB_CNL
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
modified.conffile..etc.systemd.journald.conf: [modified]
modified.conffile..etc.systemd.logind.conf: [modified]
modified.conffile..etc.systemd.networkd.conf: [modified]
modified.conffile..etc.systemd.resolved.conf: [modified]
modified.conffile..etc.systemd.system.conf: [modified]
modified.conffile..etc.systemd.timesyncd.conf: [modified]
modified.conffile..etc.systemd.user.conf: [modified]
mtime.conffile..etc.systemd.journald.conf: 2019-08-31T23:59:42.943575
mtime.conffile..etc.systemd.logind.conf: 2019-09-01T00:28:56.884198
mtime.conffile..etc.systemd.networkd.conf: 2019-08-31T23:59:42.978575
mtime.conffile..etc.systemd.resolved.conf: 2019-09-01T00:28:56.953197
mtime.conffile..etc.systemd.system.conf: 2019-09-01T00:28:56.906198
mtime.conffile..etc.systemd.timesyncd.conf: 2019-09-01T00:28:56.956197
mtime.conffile..etc.systemd.user.conf: 2019-09-01T00:28:56.907198

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


** Tags: amd64 apport-bug disco package-from-proposed

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

Title:
  18 second delay during login

Status in systemd package in Ubuntu:
  New

Bug description:
   I am experiencing an 18 second delay during login between the
  time the X-server and saved applications start, and the background,
  panels, and rest of the Mate desktop draw.

   I have tried new user with no configuration to eliminate user 
configuration date.  I've tried
  different desktop environments to eliminate them.  I've tried different 
greeters and different
  display managers.  Symptoms don't change.

   Out of desperation I grabbed the most recent systemd off of github and 
compiled and installed
  it, version 243 verses version 240 shipped with Ubuntu 19.04.

   With version 243 login no longer has delay but audio breaks.  The fact 
that replacing systemd
  got rid of the delay tells me the delay is in that package.  I can find 
nothing in the logs that
  would give me a clue as to what is wrong, no errors in that time frame, in 
fact NOTHING logs during
  that interval.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 240-6ubuntu5.4
  ProcVersionSignature: Ubuntu 5.0.0-27.28-lowlatency 5.0.21
  Uname: Linux 5.0.0-27-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Sep  1 03:19:08 2019
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-lowlatency 
root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro quiet splash 
xdg.force_integrated=1 

[Touch-packages] [Bug 1675079] Re: 16.04 LTS Partition /boot fills up with Kernel images, gets underwear in a twist

2019-09-01 Thread Jarno Suni
danhash, please read https://help.ubuntu.com/community/RemoveOldKernels

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

Title:
  16.04 LTS Partition /boot fills up with Kernel images, gets underwear
  in a twist

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

    sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

    sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]

  The unattended-upgrades fix is uploaded with many other fixes and
  those may cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  On a 16.04LTS system, the /boot partition will eventually fill with
  Kernel images, until the point where "apt-get autoremove" can't
  complete.

  This issue has previously been reported as fixed, but it is not fixed:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093

  Generally what I see is the final kernel image that fills the drive is
  incompletely installed (the header package does not make it).  "apt-
  get autoremove" tries to work, but fails.  I must manually remove
  kernel images to free enough space.

  I see this on a machine used by my elderly parents, where 'Download
  and install updates automatically' is set.  And on my home machines,
  where the setting is elsewhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1675079/+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 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

2019-09-01 Thread Julian Andres Klode
There are subtle differences between how the meta package is installed
and how tasks are installed, even if the meta package installs all task
packages.

tasksel effectively runs apt install xubuntu-desktop^, that is, it
installs all packages that have the xubuntu-desktop task field set. But
it might also include some other tasks, and I don't remember. That said,
both methods are somewhat crap as they do not mark packages properly as
autoremovable.

Consider a package X depending on A or B. If you install it, it will
install A as well. If you say install X B, it won't install X. That's
the same effect for tasks, and may lead to slightly different choices.

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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