[Touch-packages] [Bug 1440818] Re: apport-bug does not anonymize udevdb log

[Launchpad Bug Tracker]

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

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

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

Title:
  apport-bug does not anonymize udevdb log

Status in apport package in Ubuntu:
  Expired

Bug description:
  when apport-bug joins the output of 'udevadm info --export-db' as
  UdevDb.txt' in a bug report, various uuid related to partitions, file
  systems, and disks are not anonymized.

  More over serial number of disk, mac adress, or WWN are not anonymized
  either.

  I join a patch (to hookutils.py) that attempts to fix that

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportLog:
   
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CrashReports:
   640:1000:118:1466952:2015-04-02 01:07:55.905460014 +0200:2015-04-02 
02:29:42.472130210 +0200:/var/crash/_usr_bin_cryptkeeper.1000.crash
   600:109:118:0:2015-04-02 01:07:53.619086261 +0200:2015-04-02 
19:56:51.622507923 +0200:/var/crash/_usr_bin_cryptkeeper.1000.uploaded
   664:1000:118:0:2015-04-02 01:07:52.598016638 +0200:2015-04-02 
19:56:51.622507923 +0200:/var/crash/_usr_bin_cryptkeeper.1000.upload
   640:1000:118:8871994:2015-04-02 20:28:37.247845958 +0200:2015-04-02 
20:28:37.599849491 
+0200:/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
  CurrentDesktop: Unity
  Date: Mon Apr  6 19:28:41 2015
  InstallationDate: Installed on 2015-04-01 (4 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1440818/+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 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

[Mathew Hodson]

** Tags removed: verification-needed

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

Title:
  pulseaudio assert failure: pulseaudio: mixer.c:929:
  snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Won't Fix
Status in pulseaudio source package in Cosmic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250
  https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad
  https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669

  This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
  
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year

  [Test Case]

  No manual test case known. Just watch errors.ubuntu.com to check for
  recurrences.

  [Regression Potential]

  Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
  18.10 and later for a year so far.

  [Other Info]

  SRU sponsorship tracked in bug 1556439.

  [Original Report]

  Sidenote: Imediatly got that crash after the apt-xapian-index one (
  lp:1663524 ); does not know if it can exist a possible relationship
  between them.

  Got an other crash, and that time 'sound' is fully lost (pulseaudio
  not reloaded). Wonder if lp:1662860 can be concerned.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem4084 F pulseaudio
   /dev/snd/controlC0:  oem4084 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 10 09:55:45 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f92818e7188 "mixer", 
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
   __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 
"mixer.c", line=929, function=0x7f92818e76a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
   snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
  Title: pulseaudio assert failure: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1663528/+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 1801338] Re: apt fails to properly handle server-side connection closure

[Launchpad Bug Tracker]

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

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

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

Title:
  apt fails to properly handle server-side connection closure

Status in apt package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Triaged
Status in apt source package in Cosmic:
  Triaged

Bug description:
  [Impact]
  In some cases, apt does not correctly handle server-side connection closure 
after a pipeline, and aborts the file being downloaded with an "Undetermined 
Error" when the connection has been closed.

  [Test case]
  This could be seen by running apt build-dep evince on cosmic with a recent 
apt with the pipelining fix (such as 1.6.6) against a local mirror running 
apache from trusty. It remains to be seen whether this is easily reproducible 
for anyone.

  [Regression potential]
  N/A yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+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 1832672] Re: systemd-resolve not ignoring comments in /etc/hosts

[Dan Streetman]

** Description changed:

+ [impact]
+ 
+ resolved does not ignore comments properly in /etc/hosts
+ 
+ [test case]
+ 
+ see original description below
+ 
+ [regression potential]
+ 
+ as this modifies resolved parsing of /etc/hosts, regressions would
+ likely be in hostname lookups from hosts in /etc/hosts, or failure(s) to
+ parse /etc/hosts correctly.
+ 
+ [other info]
+ 
+ original description:
+ ---
+ 
+ 
  $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  
  $ LANG=C apt-cache policy systemd
  systemd:
-   Installed: 237-3ubuntu10.22
-   Candidate: 237-3ubuntu10.22
-   Version table:
-  *** 237-3ubuntu10.22 500
- 500 http://ch.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  237-3ubuntu10.19 500
- 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
-  237-3ubuntu10 500
- 500 http://ch.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
- 500 http://mirrors.kernel.org/ubuntu bionic/main amd64 Packages
- 
+   Installed: 237-3ubuntu10.22
+   Candidate: 237-3ubuntu10.22
+   Version table:
+  *** 237-3ubuntu10.22 500
+ 500 http://ch.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  237-3ubuntu10.19 500
+ 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
+  237-3ubuntu10 500
+ 500 http://ch.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+ 500 http://mirrors.kernel.org/ubuntu bionic/main amd64 Packages
  
  $ head -1 /etc/hosts
  127.0.2.1 foo # bar
  
  $ /usr/bin/systemd-resolve -4 bar
  
  expected
  --
  bar: resolve call failed: 'bar' not found
  
  What happened instead
  -
  bar: 127.0.2.1
  
- 
- HOSTS(5)  
+ HOSTS(5)
  > Text from a "#" character until the end of the line is a comment, and is 
ignored.
  
  This is fixed in upstream:
  https://github.com/systemd/systemd/issues/10779
  
https://github.com/systemd/systemd/commit/bd0052777981044cf54a1e9d6e3acb1c3d813656
  
  Please backport to current LTS version.
  I accidentally connected to wrong systems because of this bug.

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

Title:
  systemd-resolve not ignoring comments in /etc/hosts

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress

Bug description:
  [impact]

  resolved does not ignore comments properly in /etc/hosts

  [test case]

  see original description below

  [regression potential]

  as this modifies resolved parsing of /etc/hosts, regressions would
  likely be in hostname lookups from hosts in /etc/hosts, or failure(s)
  to parse /etc/hosts correctly.

  [other info]

  original description:
  ---

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

  $ LANG=C apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu10.22
    Candidate: 237-3ubuntu10.22
    Version table:
   *** 237-3ubuntu10.22 500
  500 http://ch.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10.19 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   237-3ubuntu10 500
  500 http://ch.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://mirrors.kernel.org/ubuntu bionic/main amd64 Packages

  $ head -1 /etc/hosts
  127.0.2.1 foo # bar

  $ /usr/bin/systemd-resolve -4 bar

  expected
  --
  bar: resolve call failed: 'bar' not found

  What happened instead
  -
  bar: 127.0.2.1

  HOSTS(5)
  > Text from a "#" character until the end of the line is a comment, and is 
ignored.

  This is fixed in upstream:
  https://github.com/systemd/systemd/issues/10779
  
https://github.com/systemd/systemd/commit/bd0052777981044cf54a1e9d6e3acb1c3d813656

  Please backport to current LTS version.
  I accidentally connected to wrong systems because of this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1832672/+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 1783994] Re: systemd spams log with "Failed to dissect: Input/output error" on systems with mmc

[Dan Streetman]

** Description changed:

- If a device has an mmc installed, systemd-gpt-auto-generator will fail 
because of "special partition" (rpmb, boot) and record a log message: 
+ [impact]
+ 
+ on systems with mmc device installed, systemd-gpt-auto-generator fails.
+ 
+ [test case]
+ 
+ on a system with mmc device installed, run systemd-gpt-auto-generator and 
check log for:
+ systemd-gpt-auto-generator[207]: Failed to dissect: Input/output error
+ 
+ [regression potential]
+ 
+ as this is related to boot, regressions might occur at boot, or while
+ modifying or configuring a boot loader.
+ 
+ [other info]
+ 
+ original description:
+ ---
+ 
+ 
+ If a device has an mmc installed, systemd-gpt-auto-generator will fail 
because of "special partition" (rpmb, boot) and record a log message:
  systemd-gpt-auto-generator[207]: Failed to dissect: Input/output error
  This issue was discussed here:  https://github.com/systemd/systemd/issues/5806
  and a fix is proposed for new systemd versions. Please include in bionic.

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

Title:
  systemd spams log with "Failed to dissect: Input/output error" on
  systems with mmc

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress

Bug description:
  [impact]

  on systems with mmc device installed, systemd-gpt-auto-generator
  fails.

  [test case]

  on a system with mmc device installed, run systemd-gpt-auto-generator and 
check log for:
  systemd-gpt-auto-generator[207]: Failed to dissect: Input/output error

  [regression potential]

  as this is related to boot, regressions might occur at boot, or while
  modifying or configuring a boot loader.

  [other info]

  original description:
  ---

  
  If a device has an mmc installed, systemd-gpt-auto-generator will fail 
because of "special partition" (rpmb, boot) and record a log message:
  systemd-gpt-auto-generator[207]: Failed to dissect: Input/output error
  This issue was discussed here:  https://github.com/systemd/systemd/issues/5806
  and a fix is proposed for new systemd versions. Please include in bionic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1783994/+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 1843381] Re: Dell system takes a long time to connect network with external dock

[Dan Streetman]

** Description changed:

+ [impact]
+ 
+ On Dell system with BIOS-based "MAC passthrough", there can be multiple
+ USB nics with identical MAC addresses.  Since the udev rules in Debian
+ and Ubuntu assign interface names for USB nics by mac address (because
+ that is the only consistent identifier for USB nics; their path can
+ change based on which USB port they are connected to), it's impossible
+ to name two interfaces with the same name.  As Ubuntu also carries a
+ patch to retry renaming of any interface when the first renaming fails,
+ this causes a 90 second delay before being able to the "MAC passthrough"
+ nic after connecting it.
+ 
+ [test case]
+ 
+ On a system with this "MAC passthrough" enabled and required devices,
+ boot the system and then connect to the dock or connect the second USB
+ nic with identical MAC.  It will not be usable for 90 seconds as its
+ renames takes that long to timeout.
+ 
+ [regression potential]
+ 
+ the change here is very limited to only Dell systems with the specific
+ USB vendor/product ID affected by this, and additionally the change only
+ sets a ENV flag in the udev rule, which is later used by udevd to skip
+ the rename-retries for 90 seconds.  So, the regression potential for
+ anyone else without a system affected by this "MAC passthrough" should
+ be very low, and any regression potential for those with this "MAC
+ passthrough" should still be low, as this only skips the rename-retry
+ that we know will never succeed.
+ 
+ However, the regression potential is likely limited to failure to
+ properly name a USB nic, or other bugs during the udev processing of new
+ USB nics.
+ 
+ [other info]
+ 
+ original description:
+ ---
+ 
+ 
  This is a bug reopen from
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700
  The original one caused systemd regressed.
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651
  
  This issue needs an alternative solution.
  

  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
+  # 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
  

[Touch-packages] [Bug 1847815] Re: storage autopkgtest is flaky

[Dan Streetman]

storage test on xenial and bionic appear 'good enough' - no regular
failures.  Let's leave them as is.

** Changed in: systemd (Ubuntu Xenial)
   Status: In Progress => Invalid

** Changed in: systemd (Ubuntu Bionic)
   Status: In Progress => Invalid

** Tags removed: bionic xenial

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

Title:
  storage autopkgtest is flaky

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  Invalid
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  the systemd autopkgtest 'storage' is flaky.

  [test case]

  look at the autopkgtest test log and see some of them are failures due
  to failing 'storage' test; on re-running the test is passes.

  [regression potential]

  only an autopkgtest fix; very low if any.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847815/+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 1848200] Re: gdb not stopping on breakpoint in a 32-bit program

[dann frazier]

I have a test fix building here, could one of you verify it?
https://launchpad.net/~dannf/+archive/ubuntu/lp1848200

** Changed in: gdb (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gdb (Ubuntu Bionic)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Invalid
Status in gdb source package in Bionic:
  In Progress
Status in gdb source package in Disco:
  New
Status in gdb source package in Eoan:
  Invalid
Status in gdb source package in Focal:
  Invalid

Bug description:
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not
  stop on breakpoint when running a 32-bit application (on 64-bit
  Ubuntu). This can be reproduced with a simple “hello world” program:

  $ cat hello.c 
  #include 
  int main()
  {
 // printf() displays the string inside quotation
 printf("Hello, World!");
 return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out 
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.

  --- (and not stopping nor outputting the text…) ---

  It works well with a 64-bit build (leaving out the gcc’s -m32 option).

  This problem has been already discussed on:
  https://stackoverflow.com/questions/58225562/how-to-fix-hang-in-gdb-
  in-ld-linux-so-2-when-running-a-32-bit-executable-on-a-64

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdb 8.1-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Oct 15 14:37:37 2019
  InstallationDate: Installed on 2015-12-08 (1407 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  SourcePackage: gdb
  UpgradeStatus: Upgraded to bionic on 2019-06-10 (127 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1848200/+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 1839290] Re: systemd doesn't restart a service after crashes

[Dan Streetman]

** Tags removed: bionic ddstreet systemd xenial

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

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

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

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

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

Title:
  systemd doesn't restart a service after crashes

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Incomplete
Status in systemd source package in Bionic:
  Incomplete
Status in systemd source package in Disco:
  Incomplete

Bug description:
  Affected versions of OS and systemd:
  $ cat /etc/issue
  Ubuntu 16.04.6 LTS \n \l
  $ systemd --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  Affected packages:
  systemd 229-4ubuntu21.22 and previous versions.

  Expected behaviour you didn't see:
  Scheduling restart of failed service.
  A process crashed by sigabrt and didn't restart.

  Description:
  The bug was reported to a systemd upstream repository: 
https://github.com/systemd/systemd/issues/11456
  The bug was fixed and accepted to the master branch: 
https://github.com/systemd/systemd/pull/11467/files

  Action:
  Include this patch to Ubuntu 16.04 and other version of Ubuntu which are 
supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1839290/+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 1521043] Re: less 458 crashes if search regex has many groups

[Bug Watch Updater]

** Changed in: less (Debian)
   Status: Incomplete => Fix Released

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

Title:
  less 458 crashes if search regex has many groups

Status in less package in Ubuntu:
  Fix Released
Status in less package in Debian:
  Fix Released

Bug description:
  less 458 crashes if there are enough capture groups in the regular
  expression used for search:

  newline=$(printf \\nx); newline=${newline%x}
  echo x | LESS="+g/(x)${newline}" less

  On amd64, the above produces a segfault:

  Segmentation fault (core dumped)

  On i386, the above triggers an assert:

  *** Error in `less': double free or corruption (fasttop): 0x0887f9e8 ***
  Aborted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/less/+bug/1521043/+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 1839290] Re: systemd doesn't restart a service after crashes

[Dan Streetman]

@voldemark, the testcase given in
https://github.com/systemd/systemd/issues/11456 doesn't appear to be
fixed in disco.  Do you have an example testcase of your specific
problem that is fixed by the patch from
https://github.com/systemd/systemd/pull/11467

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

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

Title:
  systemd doesn't restart a service after crashes

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

Bug description:
  Affected versions of OS and systemd:
  $ cat /etc/issue
  Ubuntu 16.04.6 LTS \n \l
  $ systemd --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  Affected packages:
  systemd 229-4ubuntu21.22 and previous versions.

  Expected behaviour you didn't see:
  Scheduling restart of failed service.
  A process crashed by sigabrt and didn't restart.

  Description:
  The bug was reported to a systemd upstream repository: 
https://github.com/systemd/systemd/issues/11456
  The bug was fixed and accepted to the master branch: 
https://github.com/systemd/systemd/pull/11467/files

  Action:
  Include this patch to Ubuntu 16.04 and other version of Ubuntu which are 
supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1839290/+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 1834494] Re: latest bzip2 reports crc errors incorrectly

[Bug Watch Updater]

** Changed in: bzip2 (Debian)
   Status: Confirmed => Fix Released

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  Fix Released
Status in bzip2 package in Ubuntu:
  In Progress
Status in bzip2 source package in Xenial:
  Fix Released
Status in bzip2 source package in Bionic:
  Fix Released
Status in bzip2 source package in Cosmic:
  Fix Released
Status in bzip2 source package in Disco:
  Fix Released
Status in bzip2 package in Debian:
  Fix Released

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzip2/+bug/1834494/+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 1848784] [NEW] Crash in Qt 5.12.2

[Dmitry Shachnev]

Public bug reported:

Originally reported by Robert Loehning in
:

Every application based on Qt will crash when opening a crafted plain
text file. Could you please add the patch below to your builds to fix
this?

https://codereview.qt-project.org/c/qt/qtbase/+/271889

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Crash in Qt 5.12.2

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Originally reported by Robert Loehning in
  :

  Every application based on Qt will crash when opening a crafted plain
  text file. Could you please add the patch below to your builds to fix
  this?

  https://codereview.qt-project.org/c/qt/qtbase/+/271889

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1848784/+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 1744457] Re: Installing systemd-cron removes ubuntu-standard

[Alexandre Detiste]

Reason: the Debian policy

Le ven. 18 oct. 2019 18:51, Gabriel de Perthuis <1744...@bugs.launchpad.net>
a écrit :

> Alternatively, systemd-cron could add a Provides: cron, which is what
> bcron does.
>
>

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

Title:
  Installing systemd-cron removes ubuntu-standard

Status in systemd-cron package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Installing systemd-cron removes ubuntu-standard, which has a
  dependency to cron.

  # apt show systemd-cron
  Package: systemd-cron
  Version: 1.5.12-1
  [...]
  Provides: anacron, cron-daemon
  [...]
  Conflicts: anacron, cron-daemon
  Replaces: anacron, cron
  [...]

  # apt show ubuntu-standard
  Package: ubuntu-standard
  Version: 1.407
  [...]
  Depends: busybox-static, cpio, cron, dmidecode, dnsutils, dosfstools, ed, 
file, ftp, hdparm, info, iptables, language-selector-common, libpam-systemd, 
logrotate, lshw, lsof, ltrace, man-db, mime-support, parted, pciutils, 
popularity-contest, psmisc, rsync, strace, time, usbutils, wget
  [...]

  Is there a reason to why cron is not in the Provides field?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-cron/+bug/1744457/+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 1835738] Re: SRU: Update Python interpreter to 3.6.9 and 3.7.5

[Launchpad Bug Tracker]

This bug was fixed in the package python3-stdlib-extensions -
3.7.5-1build1

---
python3-stdlib-extensions (3.7.5-1build1) eoan; urgency=medium

  * SRU: LP: #1835738.

python3-stdlib-extensions (3.7.5-1) unstable; urgency=medium

  * Update 3.7 extensions and modules to 3.7.5 release.
  * Update 3.8 extensions and modules to 3.8.0 release.

 -- Matthias Klose   Tue, 15 Oct 2019 18:17:14 +0200

** Changed in: python3-stdlib-extensions (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  SRU: Update Python interpreter to 3.6.9 and 3.7.5

Status in python3-defaults package in Ubuntu:
  New
Status in python3-stdlib-extensions package in Ubuntu:
  Fix Released
Status in python3.7 package in Ubuntu:
  Fix Released
Status in python3-defaults source package in Bionic:
  New
Status in python3-stdlib-extensions source package in Bionic:
  New
Status in python3.6 source package in Bionic:
  New
Status in python3.7 source package in Bionic:
  New
Status in python3-defaults source package in Disco:
  New
Status in python3-stdlib-extensions source package in Disco:
  New
Status in python3.7 source package in Disco:
  New
Status in python3-defaults source package in Eoan:
  New
Status in python3-stdlib-extensions source package in Eoan:
  Fix Committed
Status in python3.7 source package in Eoan:
  Fix Committed

Bug description:
  Update Python interpreter to 3.6.9 and 3.7.5.  As done with earlier
  subminor upstream releases (LP: #1822993).

  SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the
  3.6.9 release.

  python3-stdlib-extensions also updates the modules to the 3.6.9
  release for Python 3.6.

  Acceptance Criteria: The package builds, and the test suite doesn't
  show regressions. The test suite passes in the autopkg tests. The new
  packages don't cause regressions in a test rebuild of the main
  component.

  TODO: update after test rebuild
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html

  The test rebuilds are finished, and don't show any regressions for the
  main component.

  Regression Potential: Python 3.7 isn't used by default, so we don't have many 
default users.
  Regression Potential: Python 3.6 could see some regressions, although we are 
trying to minimize the risk by doing the test rebuild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1835738/+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 1835738] Re: SRU: Update Python interpreter to 3.6.9 and 3.7.5

[Launchpad Bug Tracker]

This bug was fixed in the package python3.7 - 3.7.5-1ubuntu1

---
python3.7 (3.7.5-1ubuntu1) eoan; urgency=medium

  * SRU: LP: #1835738, to build the final 3.7.5 release for eoan,
just introducing a delta for the SRU process.

python3.7 (3.7.5-1) unstable; urgency=medium

  * Python 3.7.5 release.

 -- Matthias Klose   Tue, 15 Oct 2019 18:15:10 +0200

** Changed in: python3.7 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  SRU: Update Python interpreter to 3.6.9 and 3.7.5

Status in python3-defaults package in Ubuntu:
  New
Status in python3-stdlib-extensions package in Ubuntu:
  Fix Released
Status in python3.7 package in Ubuntu:
  Fix Released
Status in python3-defaults source package in Bionic:
  New
Status in python3-stdlib-extensions source package in Bionic:
  New
Status in python3.6 source package in Bionic:
  New
Status in python3.7 source package in Bionic:
  New
Status in python3-defaults source package in Disco:
  New
Status in python3-stdlib-extensions source package in Disco:
  New
Status in python3.7 source package in Disco:
  New
Status in python3-defaults source package in Eoan:
  New
Status in python3-stdlib-extensions source package in Eoan:
  Fix Committed
Status in python3.7 source package in Eoan:
  Fix Committed

Bug description:
  Update Python interpreter to 3.6.9 and 3.7.5.  As done with earlier
  subminor upstream releases (LP: #1822993).

  SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the
  3.6.9 release.

  python3-stdlib-extensions also updates the modules to the 3.6.9
  release for Python 3.6.

  Acceptance Criteria: The package builds, and the test suite doesn't
  show regressions. The test suite passes in the autopkg tests. The new
  packages don't cause regressions in a test rebuild of the main
  component.

  TODO: update after test rebuild
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html

  The test rebuilds are finished, and don't show any regressions for the
  main component.

  Regression Potential: Python 3.7 isn't used by default, so we don't have many 
default users.
  Regression Potential: Python 3.6 could see some regressions, although we are 
trying to minimize the risk by doing the test rebuild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1835738/+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 1848354] Re: upgrade-between-snapshots autopkgtest is flaky

[Launchpad Bug Tracker]

This bug was fixed in the package unattended-upgrades - 1.14ubuntu1.1

---
unattended-upgrades (1.14ubuntu1.1) eoan; urgency=medium

  * debian/tests/control: Mark upgrade-between-snapshots as flaky
(Closes: #941752) (LP: #1848354)

 -- Balint Reczey   Wed, 16 Oct 2019 17:47:42 +0200

** Changed in: unattended-upgrades (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  upgrade-between-snapshots autopkgtest is flaky

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * Flaky upgrade-between-snapshots autopkgtest prevents developers to
  use the test efficiently.

  [Test Case]

   * Run autopkgtests, observe the upgrade-between-snapshots test
  passing or failing but being marked as FLAKY.

  [Regression Potential]

   * None, the test was failing often due to connectivity/internal
  errors of snapshot.debian.org.

  [Other Info]

   * The whole autopkgtest is marked to be failing on amd64 to mitigate
  the single flaky test, this marking can be removed after marking this
  single flaky test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1848354/+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 1848777] [NEW] Systemd is missing a patch to allow it to be used with SELinux

[zak]

Public bug reported:

Ubuntu Version:
Description: Ubuntu 18.04.3 LTS
Release: 18.04

Systemd version:
Installed: 273-ubuntu10.29
Candidate: 273-ubuntu10.31

Expected Behavior:
Systemd will only remount the cgroups if they need to be relabeled.

Actual Behavior:
Systemd will try to re-mount the cgroups for relabeling which will fail and 
break systemd services that use cgroups.

Upstream fix:
https://github.com/systemd/systemd/pull/8595

Additional Notes:
I was able to work around this issue by applying the patch linked and changing 
the line:
https://github.com/systemd/systemd/pull/8595/files#diff-9e1684efe63d10844b8dd6708fc60e8dR408
To use the 237 version of fix label. E.G. (void) label_fix("/sys/fs/cgroup", 
true, true);
While building the package from source.

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

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

Title:
  Systemd is missing a patch to allow it to be used with SELinux

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu Version:
  Description: Ubuntu 18.04.3 LTS
  Release: 18.04

  Systemd version:
  Installed: 273-ubuntu10.29
  Candidate: 273-ubuntu10.31

  Expected Behavior:
  Systemd will only remount the cgroups if they need to be relabeled.

  Actual Behavior:
  Systemd will try to re-mount the cgroups for relabeling which will fail and 
break systemd services that use cgroups.

  Upstream fix:
  https://github.com/systemd/systemd/pull/8595

  Additional Notes:
  I was able to work around this issue by applying the patch linked and 
changing the line:
  
https://github.com/systemd/systemd/pull/8595/files#diff-9e1684efe63d10844b8dd6708fc60e8dR408
  To use the 237 version of fix label. E.G. (void) label_fix("/sys/fs/cgroup", 
true, true);
  While building the package from source.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1848777/+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 1848200] Re: gdb not stopping on breakpoint in a 32-bit program

[dann frazier]

** Also affects: gdb (Ubuntu Focal)
   Importance: Undecided
   Status: Confirmed

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

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

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

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

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

** Changed in: gdb (Ubuntu Focal)
   Status: Fix Released => Invalid

** Changed in: gdb (Ubuntu Eoan)
   Status: Fix Released => Invalid

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

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Invalid
Status in gdb source package in Bionic:
  New
Status in gdb source package in Disco:
  New
Status in gdb source package in Eoan:
  Invalid
Status in gdb source package in Focal:
  Invalid

Bug description:
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not
  stop on breakpoint when running a 32-bit application (on 64-bit
  Ubuntu). This can be reproduced with a simple “hello world” program:

  $ cat hello.c 
  #include 
  int main()
  {
 // printf() displays the string inside quotation
 printf("Hello, World!");
 return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out 
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.

  --- (and not stopping nor outputting the text…) ---

  It works well with a 64-bit build (leaving out the gcc’s -m32 option).

  This problem has been already discussed on:
  https://stackoverflow.com/questions/58225562/how-to-fix-hang-in-gdb-
  in-ld-linux-so-2-when-running-a-32-bit-executable-on-a-64

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdb 8.1-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Oct 15 14:37:37 2019
  InstallationDate: Installed on 2015-12-08 (1407 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  SourcePackage: gdb
  UpgradeStatus: Upgraded to bionic on 2019-06-10 (127 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1848200/+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 1451103] Re: ubuntu-standard depends on cron

[Gabriel de Perthuis]

It should at least depend on `cron-daemon | cron`.

That way users are free to use an alternative implementation of cron.

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

Title:
  ubuntu-standard depends on cron

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-standard have a hardcoded dependency on cron package. Instead
  it should depend on systemd-cron to decrease learning curve for new
  users and simplify system maintenance: it's much easier if periodic
  tasks are administered the same way as all other tasks - via standard
  units. People who need legacy software for some reason could easily
  install it from the repository.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1451103/+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 1451103] Re: ubuntu-standard depends on cron

[Launchpad Bug Tracker]

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

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

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

Title:
  ubuntu-standard depends on cron

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-standard have a hardcoded dependency on cron package. Instead
  it should depend on systemd-cron to decrease learning curve for new
  users and simplify system maintenance: it's much easier if periodic
  tasks are administered the same way as all other tasks - via standard
  units. People who need legacy software for some reason could easily
  install it from the repository.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1451103/+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 1744457] Re: Installing systemd-cron removes ubuntu-standard

[Gabriel de Perthuis]

Alternatively, systemd-cron could add a Provides: cron, which is what
bcron does.

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

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

Title:
  Installing systemd-cron removes ubuntu-standard

Status in systemd-cron package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Installing systemd-cron removes ubuntu-standard, which has a
  dependency to cron.

  # apt show systemd-cron
  Package: systemd-cron
  Version: 1.5.12-1
  [...]
  Provides: anacron, cron-daemon
  [...]
  Conflicts: anacron, cron-daemon
  Replaces: anacron, cron
  [...]

  # apt show ubuntu-standard
  Package: ubuntu-standard
  Version: 1.407
  [...]
  Depends: busybox-static, cpio, cron, dmidecode, dnsutils, dosfstools, ed, 
file, ftp, hdparm, info, iptables, language-selector-common, libpam-systemd, 
logrotate, lshw, lsof, ltrace, man-db, mime-support, parted, pciutils, 
popularity-contest, psmisc, rsync, strace, time, usbutils, wget
  [...]

  Is there a reason to why cron is not in the Provides field?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-cron/+bug/1744457/+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 1821641] Re: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily

[Simple Machine]

The issue was there in 19.04. However, I was able to flip the laptop
upside down and then click the rotation button. This fixed the issue and
displayed the screen in proper orientation.

However, just upgraded to 19.10 and the issue is back. However, the
screen does not rotate when the laptop is flipped. So can't fix the
screen orientation like I did previously.

Any one else experience this?

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

Title:
  [HP Elitebook 840 G1] Screen is upside down on 19.04 daily

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On the 19.04 daily image (2019-03-24), the screen on my laptop is
  completely upside down, from the moment the GUI loads. This does not
  happen on 18.04 and 18.10.

  It appears to be an accelerometer issue since holding the laptop
  upside down flips the image to its correct orientation - basically the
  functionality of the accelerometer is suddenly inverted.

  Please contact me if you want me to help testing the issue on my hardware. 
Thanks!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sharper1380 F pulseaudio
   /dev/snd/controlC1:  sharper1380 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-03-30 (6 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190330)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=1e4bdc5f-0616-42f3-8da2-4ec27df3fc55 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/12/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.44
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: 5CG4430MGN
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.44:bd04/12/2018:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.sku: D1F44AV
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821641/+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 1846557] Re: Unable to debug any kernel on i386 qemu machine

[Vladislav K. Valtchev]

Hi guys,
any update on this?

Just to be sure, I tried to the Linux kernel 4.19.16 in the same
scenario and I got the same result. I built the kernel with buildroot
and I launched QEMU with:

qemu-system-i386 -kernel bzImage -S -s -append 'nokaslr'

I know it needs an initrd and a hdd img in order to boot a full system, but for 
me it was enough
to break on start_kernel and then trying to do `stepi`. Exactly like with the 
other project, with the gdb version `Ubuntu 8.1-0ubuntu3` it worked perfectly, 
while with gdb `Ubuntu 8.1-0ubuntu3.1` I got the same problem:


(gdb) b start_kernel
warning: Breakpoint address adjusted from 0xc17257cd to 0xc17257cd.
Breakpoint 1 at 0xc17257cd
(gdb) c
Continuing.

Program received signal SIGTRAP, Trace/breakpoint trap.
0xc17257cd in start_kernel ()
(gdb) si
0xc17257cd in start_kernel ()
(gdb) si
0xc17257cd in start_kernel ()
(gdb) si
0xc17257cd in start_kernel ()
(gdb) si


Therefore, as expected, the bug affects _definitively_ any kind of 32-bit code 
when remote debugging is used and the client is 64-bit. I also checked if the 
latest non-Ubuntu gdb is affected by this issue and it's not.

In conclusion, I believe that the following patch introduced the
regression:

http://launchpadlibrarian.net/431301516/gdb_8.1-0ubuntu3_8.1-0ubuntu3.1.diff.gz

And that the bug needs to get some attention. After all, people _cannot_
debug a 32-bit linux kernel running on a VM anymore, if they're using
Ubuntu.

@Manoj could you please comment?

Thanks

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

Title:
  Unable to debug any kernel on i386 qemu machine

Status in gdb package in Ubuntu:
  New

Bug description:
  Hi,
  On my x86_64 machine [running Ubuntu 18.04.3 LTS] with gdb version 'Ubuntu 
8.1-0ubuntu3' I could happily debug any kernel running on a i386 qemu VM 
(qemu-system-i386) by just doing the following:

  > target remote localhost:1234
  > b term.c:694

  and then, when the breakpoint was hit I used to observe output like:

  > Breakpoint 1, term_action_use_alt_buffer (t=0xc017514c , 
use_alt_buffer=true)
  > at /home/vlad/dev/tilck/kernel/char/tty/term.c:694

  And then I was able to do `s`, `si` or `c`, exactly like with regular
  user applications.

  With the newest update of gdb, version 'Ubuntu 8.1-0ubuntu3.1', instead, 
something is broken.
  By doing the same things I observe:

  > (gdb) b term.c:693
  > warning: Breakpoint address adjusted from 0xc01158fe to 0xc01158fe.

  Which seems (and actually is) a bad sign, for what comes later. [why
  do you need to change the address? why do you want to extend it to
  64-bit for a 32-bit machine?? mmm..]

  GDB detects the breakpoint, but in a weird way:

  Program received signal SIGTRAP, Trace/breakpoint trap.
  term_action_use_alt_buffer (t=0xc017514c , 
use_alt_buffer=true)

  At this point, I'm able to read the memory and the variables BUT, I
  cannot continue the execution, NOR doing any kind of step. The
  commands apparently don't get delivered to the remote side (QEMU), or
  they get delivered in a wrong way somehow. Example output:

  (gdb) b 709
  warning: Breakpoint address adjusted from 0xc0115a45 to 0xc0115a45.
  Breakpoint 2 at 0xc0115a45: file /home/vlad/dev/tilck/kernel/char/tty/term.c, 
line 709.
  (gdb) c
  Continuing.

  Program received signal SIGTRAP, Trace/breakpoint trap.
  term_action_use_alt_buffer (t=0xc017514c , 
use_alt_buffer=true)
  at /home/vlad/dev/tilck/kernel/char/tty/term.c:693
  693t->alt_buf = kmalloc(sizeof(u16) * t->rows * t->cols);
  (gdb) c
  Continuing.

  Program received signal SIGTRAP, Trace/breakpoint trap.
  term_action_use_alt_buffer (t=0xc017514c , 
use_alt_buffer=true)
  at /home/vlad/dev/tilck/kernel/char/tty/term.c:693
  693t->alt_buf = kmalloc(sizeof(u16) * t->rows * t->cols);
  (gdb) c
  Continuing.

  As you see, the whole QEMU VM is stuck until I quit GDB.

  Note: I downgraded exclusively GDB back to version 'Ubuntu
  8.1-0ubuntu3' in order to check if the problem would be fixed and it
  is. I'm sure the problem has been introduced in this specific version
  'Ubuntu 8.1-0ubuntu3.1' and it's *not* related with QEMU *nor* with
  the kernel that is being debugged. It's totally independent from that.

  Final remark: note that I'm running gdb on x86_64 machine, while I'm
  debugging a kernel running on a i386 (virtual) machine. I believe that
  the cross-arch scenario almost certainly has something to do with the
  bug, as it happened in the past on both sides (qemu and gdb).

  Thanks a lot,
  Vlad

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

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

[Touch-packages] [Bug 1848200] Re: gdb not stopping on breakpoint in a 32-bit program

[Manoj Iyer]

This works in Eoan.

$ gdb /tmp/x
GNU gdb (Ubuntu 8.3-0ubuntu1) 8.3
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /tmp/x...
(gdb) b x.c:5
Breakpoint 1 at 0x11ea: file /tmp/x.c, line 5.
(gdb) run
Starting program: /tmp/x 

Breakpoint 1, main () at /tmp/x.c:5
5  printf("Hello, World!");
(gdb) q
A debugging session is active.

Inferior 1 [process 10723] will be killed.

Quit anyway? (y or n) y

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

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not
  stop on breakpoint when running a 32-bit application (on 64-bit
  Ubuntu). This can be reproduced with a simple “hello world” program:

  $ cat hello.c 
  #include 
  int main()
  {
 // printf() displays the string inside quotation
 printf("Hello, World!");
 return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out 
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.

  --- (and not stopping nor outputting the text…) ---

  It works well with a 64-bit build (leaving out the gcc’s -m32 option).

  This problem has been already discussed on:
  https://stackoverflow.com/questions/58225562/how-to-fix-hang-in-gdb-
  in-ld-linux-so-2-when-running-a-32-bit-executable-on-a-64

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdb 8.1-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Oct 15 14:37:37 2019
  InstallationDate: Installed on 2015-12-08 (1407 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  SourcePackage: gdb
  UpgradeStatus: Upgraded to bionic on 2019-06-10 (127 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1848200/+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 1831787] Re: Bogus routes after DHCP lease change

[Dan Streetman]

** Description changed:

+ [impact]
+ 
+ networkd does not remove old route(s) after DHCP address change
+ 
+ [test case]
+ 
+ on a system using networkd, that is connected to a network where you can
+ control the addresses that the DHCP server provides, setup system with
+ networkd to get address via DHCP, e.g.
+ 
+ [Match]
+ Name=ens3
+ 
+ [Network]
+ DHCP=ipv4
+ 
+ 
+ (re)start networkd or reboot, so the system gets an ipv4 DHCP address, and 
corresponding route to the gateway.
+ 
+ 
+ Then on the dhcp server, change the subnet to a different subnet.  On the 
client, once its renews its DHCP address, the server will provide a new address 
in the new subnet, and the client will add a new default route to the new 
gateway address.  However, the old default route to the old gateway address 
isn't removed.
+ 
+ Note this also happens without changing the entire subnet, but is more
+ subtle as shown in the original description.
+ 
+ [regression potential]
+ 
+ this affects how networkd handles routes, so has the potential to leave
+ a system with partial or incorrect networking, or no networking at all.
+ Any regression would most likely occur during networkd (re)start or
+ during renewal of a DHCP lease, or when an interface is brought up.
+ 
+ [other info]
+ 
+ original description:
+ ---
+ 
+ 
  Netplan config:
  
  network:
-   version: 2
-   renderer: networkd
-   ethernets:
- eno4:
-   dhcp4: no
- eno1np0:
-   dhcp4: no
-   addresses: 
- - 172.16.0.2/24
-   bridges:
- br0:
-   dhcp4: yes
-   interfaces:
- - eno4
+   version: 2
+   renderer: networkd
+   ethernets:
+ eno4:
+   dhcp4: no
+ eno1np0:
+   dhcp4: no
+   addresses:
+ - 172.16.0.2/24
+   bridges:
+ br0:
+   dhcp4: yes
+   interfaces:
+ - eno4
  
  On initial boot, machine got 10.0.15.109 IP address:
  
  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: Configured
  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: DHCPv4 address 
10.0.15.109/23 via 10.0.15.253
  
  At one point, DHCP server reserver this IP address and client eventually
  picked up new IP address:
  
  May 03 15:01:12 ceph2 systemd-networkd[1137]: br0: DHCPv4 address
  10.0.15.128/23 via 10.0.15.253
  
  This resulted in IP addresses:
  
  # ip -o a
  1: loinet 127.0.0.1/8 scope host lo\   valid_lft forever 
preferred_lft forever
  1: loinet6 ::1/128 scope host \   valid_lft forever preferred_lft 
forever
  2: eno1np0inet 172.16.0.2/24 brd 172.16.0.255 scope global eno1np0\   
valid_lft forever preferred_lft forever
  2: eno1np0inet6 fe80::b226:28ff:fe53:56be/64 scope link \   valid_lft 
forever preferred_lft forever
  6: br0inet 10.0.15.128/23 brd 10.0.15.255 scope global dynamic br0\   
valid_lft 503sec preferred_lft 503sec
  6: br0inet6 fe80::b8d7:5eff:fe6b:62a/64 scope link \   valid_lft 
forever preferred_lft forever
  
  So far, everything is fine. But, the routes on the machine are bogus:
  
  # ip r
- default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.109 metric 100 
- default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.128 metric 100 
- 10.0.14.0/23 dev br0 proto kernel scope link src 10.0.15.128 
- 10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.109 metric 100 
- 10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.128 metric 100 
- 172.16.0.0/24 dev eno1np0 proto kernel scope link src 172.16.0.2 
+ default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.109 metric 100
+ default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.128 metric 100
+ 10.0.14.0/23 dev br0 proto kernel scope link src 10.0.15.128
+ 10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.109 metric 100
+ 10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.128 metric 100
+ 172.16.0.0/24 dev eno1np0 proto kernel scope link src 172.16.0.2
  
  routes with src 10.0.15.109 should have been removed when lease was
  renewed. I'm not sure if this is a bug in netplan or systemd. This is
  18.04, systemd 37-3ubuntu10.21, netplan 0.40.1~18.04.4.

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

Title:
  Bogus routes after DHCP lease change

Status in netplan:
  Invalid
Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  In Progress

Bug description:
  [impact]

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

  [test case]

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

  [Match]
  Name=ens3

  [Network]
  DHCP=ipv4

  
  (re)start networkd or reboot, so the system gets an ipv4 

Re: [Touch-packages] [Bug 1848587] [NEW] lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2

[Christian Brauner]

Is this a flake or consistently reproducible?

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

Title:
  lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2

Status in lxc package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587/+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 1825785] Re: lightdm: screen does not wake up on mouse/keyboard events

[He Xuxin]

I have same the issue on Debian after I upgrade to Debian buster. In my
experience, it looks like related to Linux kernel. This bug can't
reproduce on Linux 4.9:

Linux tomacat 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 
GNU/Linux
Linux tomacat 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u3 (2019-06-16) x86_64 
GNU/Linux

But I can reproduce on Linux 4.19:

Linux tomacat 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) 
x86_64 GNU/Linux
Linux tomacat 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08) 
x86_64 GNU/Linux

May be I should report it to Debian bug tracking system.

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

Title:
  lightdm: screen does not wake up on mouse/keyboard events

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce package in Ubuntu:
  Confirmed
Status in lightdm package in openSUSE:
  New

Bug description:
  Description: When session is locked either using dm-tool or light-
  locker, lightdm greeter is functional (you can type your password and
  press Enter to unlock the session) but screen is not turned on, and
  remains turned off even when you move the mouse or press any key.

  Although, it doesn't occur when you close your session instead locking
  it.

  Additional info:
  * xorg: 1:7.7+19ubuntu12
  * lightdm 1.28.0-0ubuntu1
  * xfce4-session: 4.12.1-6ubuntu1

  From lsb_release:
  Description:  Ubuntu 19.04
  Release:  19.04

  * Reproducible on other distributions as well. See here: 
https://bugs.archlinux.org/task/59750
  * Reproducible on both Intel UHD Graphics and AMDGPU Graphics.

  Steps to reproduce:
  * Lock the running session using lightdm
  * Screen is turned off, but it won't turn back on when you move the mouse or 
use the keyboard
  * You can type the password and press Enter to unlock the session. It the 
password is correct, the screen will finally turn on and you will be at your 
desktop.

  Note: switching out and then switching back to tty7 restores
  visibility of the lock screen.

  On Arch Linux, downgrading to xorg-server{,-common} 1.20.0-9 makes the
  screen behave as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Apr 22 02:06:42 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [1028:0725]
  InstallationDate: Installed on 2019-04-22 (0 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:28c0 Sunplus Innovation Technology Inc.
   Bus 001 Device 002: ID 8087:07dc Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 11-3162
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0NM68T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 11-3162
  dmi.product.sku: 0725
  dmi.product.version: 2.4.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: 

[Touch-packages] [Bug 494327] Re: Avahi is not able to browse it's own resources

[Alex Schuilenburg]

Sam problem with Debain 10, and the above (disabling ipv6) fixes it.

Did anyone figure out what the issue was?

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

Title:
  Avahi is not able to browse it's own resources

Status in avahi package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 9.10
  Release:  9.10

  avahi-daemon:
Installed: 0.6.25-1ubuntu5.1
Candidate: 0.6.25-1ubuntu5.1
Version table:
   *** 0.6.25-1ubuntu5.1 0
  500 http://us.archive.ubuntu.com karmic-updates/main Packages
  100 /var/lib/dpkg/status
   0.6.25-1ubuntu5 0
  500 http://us.archive.ubuntu.com karmic/main Packages

  Browsing Avahi's local resources stopped working in a recent update.

  It used to be working fine. Now:

  elventear@utumno:~$ avahi-browse -a -r
  +  br0 IPv4 thangorodrim  VNC Remote Access   
 local
  +  br0 IPv4 utumno media server   Web Site
 local
  +  br0 IPv4 utumno media server   iTunes Audio Access 
 local
  +  br0 IPv4 utumno media server   _rsp._tcp   
 local
  +  br0 IPv4 Virtualization Host utumno_libvirt._tcp   
 local
  +  br0 IPv4 thangorodrim  SSH Remote Terminal 
 local
  +  br0 IPv4 utumnoSSH Remote Terminal 
 local
  +  br0 IPv4 thangorodrim  SFTP File Transfer  
 local
  +  br0 IPv4 utumnoSFTP File Transfer  
 local
  +  br0 IPv4 thangorodrim  Apple File Sharing  
 local
  +  br0 IPv4 utumnoApple File Sharing  
 local

  Failed to resolve service 'utumno media server' of type '_http._tcp' in 
domain 'local': Timeout reached
  Failed to resolve service 'utumno media server' of type '_daap._tcp' in 
domain 'local': Timeout reached
  Failed to resolve service 'utumno media server' of type '_rsp._tcp' in domain 
'local': Timeout reached
  Failed to resolve service 'Virtualization Host utumno' of type 
'_libvirt._tcp' in domain 'local': Timeout reached
  Failed to resolve service 'utumno [00:24:8c:15:15:4d]' of type 
'_workstation._tcp' in domain 'local': Timeout reached
  Failed to resolve service 'utumno' of type '_ssh._tcp' in domain 'local': 
Timeout reached
  Failed to resolve service 'utumno' of type '_sftp-ssh._tcp' in domain 
'local': Timeout reached
  Failed to resolve service 'utumno' of type '_afpovertcp._tcp' in domain 
'local': Timeout reached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/494327/+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 1825785] Re: lightdm: screen does not wake up on mouse/keyboard events

[He Xuxin]

** No longer affects: lightdm (Debian)

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

Title:
  lightdm: screen does not wake up on mouse/keyboard events

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce package in Ubuntu:
  Confirmed
Status in lightdm package in openSUSE:
  New

Bug description:
  Description: When session is locked either using dm-tool or light-
  locker, lightdm greeter is functional (you can type your password and
  press Enter to unlock the session) but screen is not turned on, and
  remains turned off even when you move the mouse or press any key.

  Although, it doesn't occur when you close your session instead locking
  it.

  Additional info:
  * xorg: 1:7.7+19ubuntu12
  * lightdm 1.28.0-0ubuntu1
  * xfce4-session: 4.12.1-6ubuntu1

  From lsb_release:
  Description:  Ubuntu 19.04
  Release:  19.04

  * Reproducible on other distributions as well. See here: 
https://bugs.archlinux.org/task/59750
  * Reproducible on both Intel UHD Graphics and AMDGPU Graphics.

  Steps to reproduce:
  * Lock the running session using lightdm
  * Screen is turned off, but it won't turn back on when you move the mouse or 
use the keyboard
  * You can type the password and press Enter to unlock the session. It the 
password is correct, the screen will finally turn on and you will be at your 
desktop.

  Note: switching out and then switching back to tty7 restores
  visibility of the lock screen.

  On Arch Linux, downgrading to xorg-server{,-common} 1.20.0-9 makes the
  screen behave as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Apr 22 02:06:42 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [1028:0725]
  InstallationDate: Installed on 2019-04-22 (0 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:28c0 Sunplus Innovation Technology Inc.
   Bus 001 Device 002: ID 8087:07dc Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 11-3162
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0NM68T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 11-3162
  dmi.product.sku: 0725
  dmi.product.version: 2.4.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1825785/+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 1825785] Re: lightdm: screen does not wake up on mouse/keyboard events

[He Xuxin]

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

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

Title:
  lightdm: screen does not wake up on mouse/keyboard events

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce package in Ubuntu:
  Confirmed
Status in lightdm package in Debian:
  New
Status in lightdm package in openSUSE:
  New

Bug description:
  Description: When session is locked either using dm-tool or light-
  locker, lightdm greeter is functional (you can type your password and
  press Enter to unlock the session) but screen is not turned on, and
  remains turned off even when you move the mouse or press any key.

  Although, it doesn't occur when you close your session instead locking
  it.

  Additional info:
  * xorg: 1:7.7+19ubuntu12
  * lightdm 1.28.0-0ubuntu1
  * xfce4-session: 4.12.1-6ubuntu1

  From lsb_release:
  Description:  Ubuntu 19.04
  Release:  19.04

  * Reproducible on other distributions as well. See here: 
https://bugs.archlinux.org/task/59750
  * Reproducible on both Intel UHD Graphics and AMDGPU Graphics.

  Steps to reproduce:
  * Lock the running session using lightdm
  * Screen is turned off, but it won't turn back on when you move the mouse or 
use the keyboard
  * You can type the password and press Enter to unlock the session. It the 
password is correct, the screen will finally turn on and you will be at your 
desktop.

  Note: switching out and then switching back to tty7 restores
  visibility of the lock screen.

  On Arch Linux, downgrading to xorg-server{,-common} 1.20.0-9 makes the
  screen behave as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Apr 22 02:06:42 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [1028:0725]
  InstallationDate: Installed on 2019-04-22 (0 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:28c0 Sunplus Innovation Technology Inc.
   Bus 001 Device 002: ID 8087:07dc Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 11-3162
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0NM68T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 11-3162
  dmi.product.sku: 0725
  dmi.product.version: 2.4.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1825785/+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 1847896] Re: Unable to shutdown or restart from log-in screen

[Balint Reczey]

** Description changed:

+ [Impact]
+ 
+  * Shutdown and restart options don't work from the login screen, when
+ the user is not logged in.
+ 
+ [Test Case]
+ 
+  * Start the system and don't log in, or log out in case the system is set up 
with autologin.
+  * Restart, then shut down the system using the option in the upper right 
corner of the login screen.
+  * Observe both operations working.
+ 
+ [Regression Potential]
+ 
+  * The fix is treating treating the greeter as user display sessions by
+ cherry-picking upstream's change released in v243. The fix itself is
+ very small, but there may be non-obvious security implications.
+ 
+ [Original Bug Text]
+ 
  When selecting the shutdown icon from the log-in screen you are prompted
  with a dialog that allows you to either cancel, restart or shutdown.
  
  It has been noted that the restart and shutdown options no longer work.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 13 09:08:23 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-17 (148 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Unable to shutdown or restart from log-in screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Shutdown and restart options don't work from the login screen, when
  the user is not logged in.

  [Test Case]

   * Start the system and don't log in, or log out in case the system is set up 
with autologin.
   * Restart, then shut down the system using the option in the upper right 
corner of the login screen.
   * Observe both operations working.

  [Regression Potential]

   * The fix is treating treating the greeter as user display sessions
  by cherry-picking upstream's change released in v243. The fix itself
  is very small, but there may be non-obvious security implications.

  [Original Bug Text]

  When selecting the shutdown icon from the log-in screen you are
  prompted with a dialog that allows you to either cancel, restart or
  shutdown.

  It has been noted that the restart and shutdown options no longer
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 13 09:08:23 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-17 (148 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+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 1848623] Re: package systemd 237-3ubuntu10.31 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1

[Dan Streetman]

what does this show:

$ ls -ld /var /var/log /var/log/journal /var/log/journal/*

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

Title:
  package systemd 237-3ubuntu10.31 failed to install/upgrade: installed
  systemd package post-installation script subprocess returned error
  exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  This error appeared during release upgrade from 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.31
  ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16
  Uname: Linux 4.13.0-46-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: amd64
  Date: Fri Oct 18 06:15:02 2019
  ErrorMessage: installed systemd package post-installation script subprocess 
returned error exit status 1
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: DigitalOcean Droplet
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-46-generic 
root=UUID=a1c86501-45f5-4b0f-a356-9421fe46b341 ro console=tty1 console=ttyS0
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: systemd
  Title: package systemd 237-3ubuntu10.31 failed to install/upgrade: installed 
systemd package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2019-10-18 (0 days ago)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: DigitalOcean
  dmi.bios.version: 20171212
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr:
  dmi.product.family: DigitalOcean_Droplet
  dmi.product.name: Droplet
  dmi.product.version: 20171212
  dmi.sys.vendor: DigitalOcean

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1848623/+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 1820317] Re: The firewalld autopackage tests fail due to iptables

[Bug Watch Updater]

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

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

Title:
  The firewalld autopackage tests fail due to iptables

Status in firewalld package in Ubuntu:
  Fix Released
Status in iptables package in Ubuntu:
  Won't Fix
Status in iptables package in Debian:
  Fix Released

Bug description:
  The firewalld autopkgtest fail in disco on what looks like an iptables
  issue

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  disco/disco/amd64/f/firewalld/20190315_154203_ef4d6@/log.gz

  'Mar 15 15:41:39 autopkgtest firewalld[1691]: ERROR: 
'/usr/sbin/iptables-restore -w -n' failed: iptables-restore v1.8.2 (nf_tables): 
   line 4: RULE_REPLACE failed (No 
such file or directory): rule in chain INPUT
   line 4: RULE_REPLACE failed (No 
such file or directory): rule in chain OUTPUT'

  That looks like the issue reported on 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914694 which is fixed in 
upstream iptables
  https://git.netfilter.org/iptables/commit/?id=947c51c95

  That fix seems to depends on git master changes from libnftnl
  https://git.netfilter.org/libnftnl/log/
  ('chain: Support per chain rules list' and following commits)

  Unsure at this point what's best disco, if we should start looking at
  backporting those changes?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firewalld/+bug/1820317/+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 1717490] Re: LightDM keeps plain text login password in memory

[Marc Deslauriers]

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

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

Title:
  LightDM keeps plain text login password in memory

Status in Light Display Manager:
  Triaged
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  The lightdm process keeps the user password in memory, if the lightdm-
  greeter is used. This seems to be the case on Ubuntu up to the recent
  17.04 version. The issue was validated with lightdm  1.22.0-0ubuntu2
  (17.04) and 1.10.6-0ubuntu1 (14.04)

  Example:

  root@victim:~# ps fauxw | grep lightdm
  root   889  0.0  0.2 379344  8436 ?SLsl 12:43   0:00 
/usr/sbin/lightdm
  root   968  1.3  1.8 379900 72804 tty7 Ssl+ 12:43   0:01  \_ 
/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  root  1103  0.0  0.1 243564  6724 ?Sl   12:43   0:00  \_ lightdm 
--session-child 12 19
  root  2074  0.0  0.0  21328   976 pts/0S+   12:45   0:00  
\_ grep --color=auto lightdm
  root@victim:~# gcore 1103
  [...]
  Saved corefile core.1103
  root@victim:~# strings core.1103 | grep -A5 -B5 secretpassword
  ttyCH0
  ttyCH1
  #...ttyCH63
  # Moxa Intellio serial
  _pammodutil_getspnam_svbl_2
  secretpassword
  gkr_system_authtok
  -UN*X-FAIL-svbl
  svbl
  1000:1000:svbl,,,
  /home/svbl
  root@victim:~# 

  As far as I can tell it seems that the password is not cleared form
  memory after passing it to PAM. This is not a direct vulnerability or
  breaking a security boundary (root access required to dump the memory)
  but it seems not to be necessary for lightdm to keep the pw in memory.

  A similar issue was reported to gnome-keyring-daemon, where the need
  of keeping the password is a bit more understandable
  (https://bugzilla.gnome.org/show_bug.cgi?id=764014).

  Do you see any reason why LightDM needs to keep the password in
  memory?

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1717490/+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 1717476] Re: DHCP Transaction ID (xid) is logged with INFO loglevel

[Marc Deslauriers]

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Confirmed

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

Title:
  DHCP Transaction ID (xid) is logged with INFO loglevel

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  The patch dhcp-4.2.4-improved-xid.patch
  (https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1401141)
  added logging of the Transaction ID (xid) to dhclient:

  -   log_info ("DHCPACK from %s", piaddr (packet -> client_addr));
  +   log_info ("DHCPACK from %s (xid=0x%x)", piaddr (packet -> 
client_addr), client -> xid);
  -   log_info ("DHCPNAK from %s", piaddr (packet -> client_addr));
  +   log_info ("DHCPNAK from %s (xid=0x%x)", piaddr (packet -> 
client_addr), client -> xid);
  -   log_info ("DHCPDISCOVER on %s to %s port %d interval %ld",
  +   log_info ("DHCPDISCOVER on %s to %s port %d interval %ld (xid=0x%x)",
  -   log_info ("DHCPREQUEST of %s on %s to %s port %d", 
  +   log_info ("DHCPREQUEST of %s on %s to %s port %d (xid=0x%x)",
  -   log_info ("DHCPDECLINE on %s to %s port %d",
  +   log_info ("DHCPDECLINE on %s to %s port %d (xid=0x%x)",
  -   log_info ("DHCPRELEASE on %s to %s port %d",
  +   log_info ("DHCPRELEASE on %s to %s port %d (xid=0x%x)",

  Under certain circumstances, this can lead to the xid being leaked to
  remote machines (syslog) or visible to unprivileged users.

  Having the xid, it is possible to flood a target machine with DHCPACK
  replies and spoof a upcoming DHCPREQUEST answer (Proof of concept
  avail on request).

  I would not say this is a direct security issue, but more of a
  potential information disclosure and could lead to an issue in
  combination with other factors (e.g. syslog files of a target machine
  are accessible to an attacker). Still I don't see why this logging of
  xid is necessary and would recommend to either:

  - remove logging of the xid entirely
  - only log xid in log level DEBUG

  This issue was confirmed to be in place for the the most recent
  version of isc-dhcp-client shipped with Ubuntu 17.04.
  (4.3.5-3ubuntu1).

  Note: this patch is not included in the Debian package of isc-dhcp-
  client (https://packages.debian.org/stretch/isc-dhcp-client), therefor
  this issue does only affect Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1717476/+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 1791405] Re: bluetooth always in discoverable mode (security issue)

[Marc Deslauriers]

** Changed in: bluez (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/1791405

Title:
  bluetooth always in discoverable mode (security issue)

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in gnome-bluetooth source package in Bionic:
  Fix Released
Status in gnome-bluetooth source package in Cosmic:
  Fix Released
Status in gnome-bluetooth source package in Disco:
  Fix Released
Status in bluez source package in Eoan:
  Fix Committed
Status in gnome-bluetooth package in Fedora:
  Won't Fix

Bug description:
  Excerpt from a similar report
  (https://bugzilla.redhat.com/show_bug.cgi?id=1602985) :

  Opening the Bluetooth settings will make the device discoverable
  again, but does not make the device undiscoverable after the settings
  are closed (this is not intended behavior; devices should only be
  discoverable when the bluetooth settings UI is open).

  There seem to be a merge request :

  https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/1

  Could you please merge it asap, it should be treated as a security
  issue IMHO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1791405/+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 1823419] Re: jbig-kit calls abort() on invalid data, crashing many programs

[Marc Deslauriers]

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

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

Title:
  jbig-kit calls abort() on invalid data, crashing many programs

Status in jbigkit package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Sometimes I fuzz random packages that are dependencies of lots of
  other packages. Yesterday I picked up jbigkit.

  I've just reported upstream a crash where invalid input can cause it
  to call abort() rather than report an error up the stack.

  This is a DoS in itself, but it's massively exacerbated because TIFF
  files can include JBIG1-formatted streams. jbigkit is included in
  libtiff, and libtiff is itself included in a bunch of other things. So
  I wanted to highlight this to you because of it's widespread DoS
  potential.

  For example, if you process a corrupted tiff file in imagemagick, it
  will crash. If view a corrupted tiff file in e.g. eog or evince, it
  will crash. Worst, if you open a file picker in some apps, like chrome
  or chromium-browser, it will call out to libgdk-pixbuf to generate a
  preview, which will call out to libtiff, then jbigkit, then abort(),
  which kills your entire browser session. This also affects the file
  picker on pinta (and pinta itself), but not firefox or eog. I'm not
  sure why some are affected and some are not.

  Here's a trace from chromium-browser: I know it's not in main but it's
  a good demonstration.

  Thread 1 "chromium-browse" received signal SIGABRT, Aborted.
  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
  50../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
  (gdb) bt
  #0  0x75039077 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:50
  #1  0x7501a535 in __GI_abort () at abort.c:79
  #2  0x7fff4e15b1a3 in checked_malloc (nmemb=, 
size=) at jbig.c:139
  #3  0x7fff4e160803 in jbg_dec_in (s=s@entry=0x7ffea8c0, 
data=0x60317eb0 "", len=14761, cnt=0x7ffea838, cnt@entry=0x0) at 
jbig.c:2669
  #4  0x7fff941ccf50 in JBIGDecode (tif=0x6022cf70, 
buffer=0x604decc0 "", size=513216, s=) at tif_jbig.c:80
  #5  0x7fff941e46f4 in _TIFFReadEncodedStripAndAllocBuffer
  (tif=tif@entry=0x6022cf70, strip=0, buf=buf@entry=0x7ffeaed0, 
bufsizetoalloc=bufsizetoalloc@entry=513216, 
size_to_read=size_to_read@entry=513216)
  at tif_read.c:586
  #6  0x7fff941c93ff in gtStripContig (img=0x7ffeaf30, 
raster=0x7fff49cef010, w=1728, h=2376) at tif_getimage.c:960
  #7  0x7fff941cc958 in TIFFReadRGBAImageOriented
  (tif=tif@entry=0x6022cf70, rwidth=1728, rheight=2376, 
raster=raster@entry=0x7fff49cef010, orientation=orientation@entry=1, 
stop=stop@entry=1) at tif_getimage.c:532
  #8  0x7fffe81f668b in tiff_image_parse (tiff=tiff@entry=0x6022cf70, 
context=context@entry=0x5fbedaa0, error=error@entry=0x7ffeb4c0)
  at ../gdk-pixbuf/io-tiff.c:282
  #9  0x7fffe81f6b3b in gdk_pixbuf__tiff_image_stop_load 
(data=0x5fbedaa0, error=0x7ffeb4c0) at ../gdk-pixbuf/io-tiff.c:515
  #10 0x75398943 in gdk_pixbuf_loader_close 
(loader=loader@entry=0x5f7f0140 [GdkPixbufLoader], error=error@entry=0x0) 
at ../gdk-pixbuf/gdk-pixbuf-loader.c:846
  #11 0x7539601a in gdk_pixbuf_new_from_file_at_scale
  (filename=0x60072980 
"/home/dja/dev/research/wip/maintest/packages/fax/crash.tiff", width=, height=, preserve_aspect_ratio=, error=0x0) 
at ../gdk-pixbuf/gdk-pixbuf-io.c:1353
  #12 0x5af5d8bf in  ()
  #16 0x768f83a4 in  (instance=0x601263b0, detailed_signal=)
  at ../../../../gobject/gsignal.c:3487
  #13 0x768dbb6d in g_closure_invoke (closure=0x602ee6d0, 
return_value=0x0, n_param_values=1, param_values=0x7fffb800, 
invocation_hint=0x7fffb780)
  at ../../../../gobject/gclosure.c:810
  #14 0x768ee8f3 in signal_emit_unlocked_R
  (node=node@entry=0x5ff53be0, detail=detail@entry=0, 
instance=instance@entry=0x601263b0, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffb800) at 
../../../../gobject/gsignal.c:3635
  #15 0x768f7882 in g_signal_emit_valist
  (instance=instance@entry=0x601263b0, signal_id=signal_id@entry=335, 
detail=detail@entry=0, var_args=var_args@entry=0x7fffb9f8)
  at ../../../../gobject/gsignal.c:3391
  #20 0x768f83a4 in 
  (instance=instance@entry=0x600e0360, 
detailed_signal=detailed_signal@entry=0x758b67d8 "update-preview") at 
../../../../gobject/gsignal.c:3487
  --Type  for more, q to quit, c to continue without paging--c
  #17 0x768dbb6d in g_closure_invoke (closure=0x600e2fe0, 
return_value=0x0, n_param_values=1, param_values=0x7fffbcf0, 
invocation_hint=0x7fffbc70) at 

[Touch-packages] [Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

[Hui Wang]

Please test this kernel: https://people.canonical.com/~hwang4/lp1846148/

sudo dpkg -i linux-modules-.deb
sudo dpkg -i linux-modules-extra-xxx.deb
sudo dpkg -i linux-image-xxx.deb

reboot and boot with the new installed kernel.


upload dmesg and alsa-info.txt.

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1823070] Re: unattended-upgrades should tell the user (via motd) when security updates are held back

[Balint Reczey]

** Description changed:

+ [Impact]
+ 
+  * MOTD does not go into details about upgradable packages being security 
fixes or just normal updates.
+  * Users should be made aware if some of the security updates could not have 
been applied.
+  * The fix is adding a snipped to MOTD where the number of packages kept back 
by unattended-upgrades is shown.
+ 
+ [Test Case]
+ 
+  * The debian/tests/upgrade-all-security is extended to check if the number 
of kept back packages are shown in MOTD and a new test is added 
(test/test_motd.py) to check if the list of kept back packages are saved 
properly.
+  * To test the fix manually:
+1. Mark a package upgradable from the -security pocket as held, then run 
unattended-upgrades.
+2. Observe MOTD messate showing the number of packages being kept back.
+ 
+ [Regression Potential]
+ 
+  * Unattended-upgrades may crash when saving kept packages and always
+ return with failure. MOTD may hang or print error while printing the
+ packages kept back by u-u.
+ 
+ [Original Bug Text]
+ 
  Currently we have the following pieces as part of the default UX on
  Ubuntu 18.04 and later:
  
-  1) unattended-upgrades automatically installs security updates daily by 
default
-  2) the motd reports the number of available updates, including security 
updates.
+  1) unattended-upgrades automatically installs security updates daily by 
default
+  2) the motd reports the number of available updates, including security 
updates.
  
  A user who knows about 1) also knows that a non-zero number of pending
  security updates listed in 2) is nothing to worry about.
  
  However, unattended-upgrades will also cleverly detect when a security
  update cannot safely be installed non-interactively due to conffile
  changes on the system.
  
  In this case, unattended-upgrades should also inform the user via the
  motd that these updates are not being installed.  Otherwise, there's
  nothing to tell the user that the non-zero count of available security
  updates in motd is a *problem*.
  
  Suggested wording:
  
-  N security updates will not be automatically installed due to local changes.
-  See /var/log/foo for details.
+  N security updates will not be automatically installed due to local changes.
+  See /var/log/foo for details.

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

Title:
  unattended-upgrades should tell the user (via motd) when security
  updates are held back

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Confirmed
Status in unattended-upgrades source package in Disco:
  Confirmed

Bug description:
  [Impact]

   * MOTD does not go into details about upgradable packages being security 
fixes or just normal updates.
   * Users should be made aware if some of the security updates could not have 
been applied.
   * The fix is adding a snipped to MOTD where the number of packages kept back 
by unattended-upgrades is shown.

  [Test Case]

   * The debian/tests/upgrade-all-security is extended to check if the number 
of kept back packages are shown in MOTD and a new test is added 
(test/test_motd.py) to check if the list of kept back packages are saved 
properly.
   * To test the fix manually:
 1. Mark a package upgradable from the -security pocket as held, then run 
unattended-upgrades.
 2. Observe MOTD messate showing the number of packages being kept back.

  [Regression Potential]

   * Unattended-upgrades may crash when saving kept packages and always
  return with failure. MOTD may hang or print error while printing the
  packages kept back by u-u.

  [Original Bug Text]

  Currently we have the following pieces as part of the default UX on
  Ubuntu 18.04 and later:

   1) unattended-upgrades automatically installs security updates daily by 
default
   2) the motd reports the number of available updates, including security 
updates.

  A user who knows about 1) also knows that a non-zero number of pending
  security updates listed in 2) is nothing to worry about.

  However, unattended-upgrades will also cleverly detect when a security
  update cannot safely be installed non-interactively due to conffile
  changes on the system.

  In this case, unattended-upgrades should also inform the user via the
  motd that these updates are not being installed.  Otherwise, there's
  nothing to tell the user that the non-zero count of available security
  updates in motd is a *problem*.

  Suggested wording:

   N security updates will not be automatically installed due to local changes.
   See /var/log/foo for details.

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

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

[Touch-packages] [Bug 1828200] Re: [SRU] kernel package names ending with version without flavor are not matched by generated patterns

[Balint Reczey]

** Description changed:

+ [Impact]
+ 
+  * Most of the unused kernel packages are automatically removed by u-u, but 
kernel packages not including the flavor in the name are not removed taking up 
significant space after some time:
+  $ sudo apt autoremove
+ Reading package lists... Done
+ Building dependency tree   
+ Reading state information... Done
+ The following packages will be REMOVED:
+   linux-gcp-headers-4.15.0-1018 linux-gcp-headers-4.15.0-1019 
linux-gcp-headers-4.15.0-1021 linux-gcp-headers-4.15.0-1024 
linux-gcp-headers-4.15.0-1025 linux-gcp-headers-4.15.0-1026 
linux-gcp-headers-4.15.0-1027
+   linux-gcp-headers-4.15.0-1028 linux-gcp-headers-4.15.0-1029 
linux-gcp-headers-4.15.0-1030 linux-gcp-headers-4.15.0-1032 
linux-gcp-headers-4.15.0-1033 linux-gcp-headers-4.15.0-1034 
linux-gcp-headers-4.15.0-1036
+   linux-gcp-headers-4.15.0-1037 linux-gcp-headers-4.15.0-1042 nplan
+ 0 upgraded, 0 newly installed, 17 to remove and 16 not upgraded.
+ After this operation, 1234 MB disk space will be freed.
+ Do you want to continue? [Y/n]
+ 
+ [Test Case]
+ 
+  * A new test case is added to autopkgtest
+ (test/autopkgtest_kernel_patterns.py) to verify that all kernel-related
+ packages are covered having the same version of the running kernel.
+ 
+  * Install linux-gcp-headers-4.15.0-1042 and make it autoremovable
+  * Run unattended-upgrades
+  * Observe linux-gcp-headers-4.15.0-1042 being autoremoved with fixed u-u 
versions.
+ 
+ [Regression Potential]
+ 
+  * With the file name patterns changing u-u may select packages with names 
matching the patterns but not being versioned kernel packages. In case those 
packages are autoremovable they are removed by u-u.
+ To avoid this problem the fix for LP: #1848706 ensures that only 
linux-related packages are autoremoved in the kernel autoremoval phase.
+ 
+ 
+ [Original Bug Text]
+ 
  Apt ships VersionedKernelPackages regex patterns in
  /etc/apt/apt.conf.d/01autoremove from which /etc/kernel/postinst.d/apt-
  auto-removal generates kernel package name patterns by appending the
  running kernel version including the flavor like
  linux-.*-4.15.0-1010-kvm but those generated patterns don't cover
  versioned kernel package names including the version without the flavor,
  such as linux-kvm-tools-4.15.0-1012.
  
  Unattended-upgrades generates the patterns in a similar way and also
  don't cover linux-kvm-tools-4.15.0-1012 and similar packages.

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

Title:
  [SRU] kernel package names ending with version without flavor are not
  matched by generated patterns

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * Most of the unused kernel packages are automatically removed by u-u, but 
kernel packages not including the flavor in the name are not removed taking up 
significant space after some time:
   $ sudo apt autoremove
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
linux-gcp-headers-4.15.0-1018 linux-gcp-headers-4.15.0-1019 
linux-gcp-headers-4.15.0-1021 linux-gcp-headers-4.15.0-1024 
linux-gcp-headers-4.15.0-1025 linux-gcp-headers-4.15.0-1026 
linux-gcp-headers-4.15.0-1027
linux-gcp-headers-4.15.0-1028 linux-gcp-headers-4.15.0-1029 
linux-gcp-headers-4.15.0-1030 linux-gcp-headers-4.15.0-1032 
linux-gcp-headers-4.15.0-1033 linux-gcp-headers-4.15.0-1034 
linux-gcp-headers-4.15.0-1036
linux-gcp-headers-4.15.0-1037 linux-gcp-headers-4.15.0-1042 nplan
  0 upgraded, 0 newly installed, 17 to remove and 16 not upgraded.
  After this operation, 1234 MB disk space will be freed.
  Do you want to continue? [Y/n]

  [Test Case]

   * A new test case is added to autopkgtest
  (test/autopkgtest_kernel_patterns.py) to verify that all kernel-
  related packages are covered having the same version of the running
  kernel.

   * Install linux-gcp-headers-4.15.0-1042 and make it autoremovable
   * Run unattended-upgrades
   * Observe linux-gcp-headers-4.15.0-1042 being autoremoved with fixed u-u 
versions.

  [Regression Potential]

   * With the file name patterns changing u-u may select packages with names 
matching the patterns but not being versioned kernel packages. In case those 
packages are autoremovable they are removed by u-u.
  To avoid this problem the fix for LP: #1848706 ensures that only 
linux-related packages are autoremoved in the kernel autoremoval phase.

  
  [Original Bug Text]

  Apt ships VersionedKernelPackages regex patterns in
  /etc/apt/apt.conf.d/01autoremove from which /etc/kernel/postinst.d
  /apt-auto-removal generates kernel package name patterns by appending
  the running kernel version including the flavor like
  linux-.*-4.15.0-1010-kvm but those generated patterns don't cover
  versioned kernel 

[Touch-packages] [Bug 1848706] [NEW] Check if versioned kernel package to be auto-removed is built from a source named linux or linux-.*

[Balint Reczey]

Public bug reported:

[Impact]

 * Versioned kernel packages are chosen to be autoremoved by name which
is fairly reliable, but in very rare cases a packages which is not
kernel-related but named very similarly can also be selected and
autoremoved.

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Check if versioned kernel package to be auto-removed is built from a
  source named linux or linux-.*

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  [Impact]

   * Versioned kernel packages are chosen to be autoremoved by name
  which is fairly reliable, but in very rare cases a packages which is
  not kernel-related but named very similarly can also be selected and
  autoremoved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1848706/+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 1848700] [NEW] 18LTS SSH server does not accept sshv1+v2 clients

[ne1]

Public bug reported:

i.e receiving version SSH-1.99 - openssh-server drops connection saying wrong 
version received while it should be OK
upstream bug here: https://bugzilla.mindrot.org/show_bug.cgi?id=2810 i.e. fixed 
in 7.7

Problem n impact is detailed here (cannot make backups from network gear to 
18LTS):
https://community.cisco.com/t5/network-management/unable-to-ssh-from-xr-router-to-ubuntu-server/m-p/3844367

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

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

Title:
  18LTS SSH server does not accept sshv1+v2 clients

Status in openssh package in Ubuntu:
  New

Bug description:
  i.e receiving version SSH-1.99 - openssh-server drops connection saying wrong 
version received while it should be OK
  upstream bug here: https://bugzilla.mindrot.org/show_bug.cgi?id=2810 i.e. 
fixed in 7.7

  Problem n impact is detailed here (cannot make backups from network gear to 
18LTS):
  
https://community.cisco.com/t5/network-management/unable-to-ssh-from-xr-router-to-ubuntu-server/m-p/3844367

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

[peter.hutterer]

you'll need to run it against the correct event node, run libinput
record (libinput-utils.rpm) without arguments, it'll give you a list of
devices. Pick your touchpad from that list. Note that you may have 2
touchpad kernel devices, only one of which will send events. So while
libinput record is running, touch the device - if you see events scroll
past that's the right event node.

Once you identified the device node, use that same event node for the
touchpad-edge-detector

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

Status in systemd:
  Fix Released
Status in libinput package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged
Status in libinput package in Fedora:
  Confirmed

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1825499/+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 1825499]

[ali.sherif10]

How to use it? Sorry.
I tried:
$ sudo touchpad-edge-detector 40x60 /dev/input/event0
$ sudo touchpad-edge-detector 40x60 /dev/input/event1
The output was:
Error: this device does not have abs axes

I chose the size inaccurately.

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

Status in systemd:
  Fix Released
Status in libinput package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged
Status in libinput package in Fedora:
  Confirmed

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1825499/+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 1821376] Re: Report packages kept back by origins

[Balint Reczey]

** Description changed:

- Packages kept back are listed in the email report, but it is not clear
+ [Impact]
+ 
+ * Packages kept back are listed in the email report, but it is not clear
  from which origins they are installable. This information may help
  administrators to decide if the packages need to be manually upgraded.
+ 
+ [Test Case]
+ 
+ * test_mail.py test is updated to check if the kept back packages are
+ reported per origin and this is checked at build time.
+ 
+ *  For manual testing:
+   1. Configure u-u to allow upgrades from the -updates pocket and send email 
with the upgrade report.
+   2. Set up the system to have a few packages upgradable from both the 
-security and -updates pockets.
+   3. Mark a subset of packages which are upgradable as held, marking packages 
from each of the pockets.
+   4. Run u-u and observe the kept packages listed in the email. Each package 
is listed only in the allowed origin providing the highest version. (LP: 
#1848697 covers listing them in all origins from which the packages could be 
upgraded to.)
+ 
+ [Regression Potential]
+ 
+ * Unattended upgrades may crash while trying to perform updates or while
+ trying to send the summary email. Build-time tests and autopkgtests
+ include testing both functions.

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

Title:
  Report packages kept back by origins

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  * Packages kept back are listed in the email report, but it is not
  clear from which origins they are installable. This information may
  help administrators to decide if the packages need to be manually
  upgraded.

  [Test Case]

  * test_mail.py test is updated to check if the kept back packages are
  reported per origin and this is checked at build time.

  *  For manual testing:
1. Configure u-u to allow upgrades from the -updates pocket and send email 
with the upgrade report.
2. Set up the system to have a few packages upgradable from both the 
-security and -updates pockets.
3. Mark a subset of packages which are upgradable as held, marking packages 
from each of the pockets.
4. Run u-u and observe the kept packages listed in the email. Each package 
is listed only in the allowed origin providing the highest version. (LP: 
#1848697 covers listing them in all origins from which the packages could be 
upgraded to.)

  [Regression Potential]

  * Unattended upgrades may crash while trying to perform updates or
  while trying to send the summary email. Build-time tests and
  autopkgtests include testing both functions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1821376/+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 1848697] [NEW] Report packages kept back listing all allowed origins where it has higher version

[Balint Reczey]

Public bug reported:

With LP: #1821376 unattended-upgrades started listing packages by
origin, listing each package in the origin where the highest version
resides, but this hides the information, that the installed package
could be upgraded to a lower version which may contain only security
fixes.

** Affects: unattended-upgrades (Ubuntu)
 Importance: Wishlist
 Status: Triaged

** Changed in: unattended-upgrades (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Triaged

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

Title:
  Report packages kept back listing all allowed origins where it has
  higher version

Status in unattended-upgrades package in Ubuntu:
  Triaged

Bug description:
  With LP: #1821376 unattended-upgrades started listing packages by
  origin, listing each package in the origin where the highest version
  resides, but this hides the information, that the installed package
  could be upgraded to a lower version which may contain only security
  fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1848697/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

[Lilian Tao]

uname -srm
Linux 5.0.0-29-generic x86_64

upload dmesg

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5298159/+files/dmesg.txt

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1383819] Re: MTP crashes while deleting files (hang while deleting)

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: patch

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

Title:
  MTP crashes while deleting files (hang while deleting)

Status in mtp package in Ubuntu:
  Triaged
Status in mtp package in Ubuntu RTM:
  Triaged

Bug description:
  mtp-server crashes while deleting files; this can be seen as the
  delete operation starting, but never completing, until the operation
  times out and a generic error is displayed by nautilus.

  MTP logs show that MTP crashed at map::at; with an out_of_bounds error
  while in inotify_handler().

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1383819/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

[Lilian Tao]

retry installation and got a couple of warnings:

Module has been obsoleted due to being included
in kernel 4.99.  We will avoid installing
for future kernels above 4.99.
You may override by specifying --force.

logs attached.

** Attachment added: "log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5298147/+files/log.txt

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

[Lilian Tao]

reply #8, yes i rebooted.

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1383819] Re: MTP crashes while deleting files (hang while deleting)

[黄开辉]

** Patch added: 
"0005-MTP-crashes-while-deleting-files-hang-while-deleting.patch"
   
https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1383819/+attachment/5298129/+files/0005-MTP-crashes-while-deleting-files-hang-while-deleting.patch

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

Title:
  MTP crashes while deleting files (hang while deleting)

Status in mtp package in Ubuntu:
  Triaged
Status in mtp package in Ubuntu RTM:
  Triaged

Bug description:
  mtp-server crashes while deleting files; this can be seen as the
  delete operation starting, but never completing, until the operation
  times out and a generic error is displayed by nautilus.

  MTP logs show that MTP crashed at map::at; with an out_of_bounds error
  while in inotify_handler().

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1383819/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

[Hui Wang]

reply #5, did you reboot after installing the deb?

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 378783] Re: xdg-open *.desktop opens text editor

[Adeel Raza Azeemi]

Adding these two lines at the end of the .desktop file; makes it
possible to show allow launching from right click and made the file
actual executable shortcut

Type=Application
Terminal=0

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

Title:
  xdg-open *.desktop opens text editor

Status in GLib:
  New
Status in gvfs:
  New
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: xdg-utils

  In order to reproduce it execute "xdg-open *.desktop" (choose any
  .desktop file, e.g. one from /usr/share/applications). Actually your
  favorite text editor will open the file. Expected result: It'll be
  executed.

  Because of this bug, desktop entries with the new "#!/usr/bin/env xdg-
  open" shebang feature were opened in the text editor when executed
  from command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/378783/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

[Lilian Tao]

** Attachment added: "alsa-info.txt.9WOtkaYIiM"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5298127/+files/alsa-info.txt.9WOtkaYIiM

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

[Lilian Tao]

** Attachment added: "Screenshot from 2019-10-18 16-07-01.png"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5298126/+files/Screenshot%20from%202019-10-18%2016-07-01.png

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

[Lilian Tao]

@hui.wang

installed the deb package but still didn't work. 
One thing did change: the input used to be "dummy audio xxx" and now it's 
"analog input - built in audio".

Uploaded the alsa-info.txt and the scrennshot.

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1586528] Re: Avahi-daemon withdraws address record

[Trent Lloyd]

The bug was marked invalid for *Avahi* but Confirmed for network-manager
-- because the bug exists not in Avahi (it simply logs the message you
see as a result of the IP address being removed). So the bug is still
valid and confirmed, just for network-manager instead.

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

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 1848643] [NEW] [Huawei Matebook 13, Realtek ALC256, Black Headphone Out, Right] No sound at all

[Gong Chen]

Public bug reported:

it can not automatic switching between speakers and headphone.
The question is similar 
with:https://community.clearlinux.org/t/automatic-switching-between-speakers-and-headphones/916

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gong   1212 F pulseaudio
 /dev/snd/pcmC0D0c:   gong   1212 F...m pulseaudio
 /dev/snd/pcmC0D0p:   gong   1212 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 18 15:45:57 2019
InstallationDate: Installed on 2019-10-18 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gong   1212 F pulseaudio
 /dev/snd/pcmC0D0c:   gong   1212 F...m pulseaudio
 /dev/snd/pcmC0D0p:   gong   1212 F...m pulseaudio
Symptom_Jack: Black Headphone Out, Right
Symptom_Type: No sound at all
Title: [WRT-WX9, Realtek ALC256, Black Headphone Out, Right] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/12/2019
dmi.bios.vendor: HUAWEI
dmi.bios.version: 1.19
dmi.board.name: WRT-WX9-PCB
dmi.board.vendor: HUAWEI
dmi.board.version: M1020
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M1020
dmi.modalias: 
dmi:bvnHUAWEI:bvr1.19:bd08/12/2019:svnHUAWEI:pnWRT-WX9:pvrM1020:rvnHUAWEI:rnWRT-WX9-PCB:rvrM1020:cvnHUAWEI:ct10:cvrM1020:
dmi.product.family: MateBook
dmi.product.name: WRT-WX9
dmi.product.sku: C233
dmi.product.version: M1020
dmi.sys.vendor: HUAWEI

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


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

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

Title:
  [Huawei Matebook 13, Realtek ALC256, Black Headphone Out, Right] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  it can not automatic switching between speakers and headphone.
  The question is similar 
with:https://community.clearlinux.org/t/automatic-switching-between-speakers-and-headphones/916

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gong   1212 F pulseaudio
   /dev/snd/pcmC0D0c:   gong   1212 F...m pulseaudio
   /dev/snd/pcmC0D0p:   gong   1212 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 18 15:45:57 2019
  InstallationDate: Installed on 2019-10-18 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gong   1212 F pulseaudio
   /dev/snd/pcmC0D0c:   gong   1212 F...m pulseaudio
   /dev/snd/pcmC0D0p:   gong   1212 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: No sound at all
  Title: [WRT-WX9, Realtek ALC256, Black Headphone Out, Right] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2019
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.19
  dmi.board.name: WRT-WX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M1020
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M1020
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.19:bd08/12/2019:svnHUAWEI:pnWRT-WX9:pvrM1020:rvnHUAWEI:rnWRT-WX9-PCB:rvrM1020:cvnHUAWEI:ct10:cvrM1020:
  dmi.product.family: MateBook
  dmi.product.name: WRT-WX9
  dmi.product.sku: C233
  dmi.product.version: M1020
  dmi.sys.vendor: HUAWEI

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