[Touch-packages] [Bug 1882340] Re: Alert sounds are captured by the microphone

2020-08-07 Thread Launchpad Bug Tracker
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Alert sounds are captured by the microphone

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  On my Fossa the system sounds (e.g., the alert sound) are also
  captured by my microphone. Thus, if I press backspace in an empty
  terminal, my contacts in a video-call can hear the default bell sound
  making *pling*.

  When opening the System > Audio on Gnome I can see a rise on the
  volume bar as well.

  A workaround exists by disabling the alert sounds as described in the
  docs: https://help.ubuntu.com/stable/ubuntu-help/sound-alert.html.en

  This has been the default since installation for me and drives my
  contacts crazy. :-)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jl 3027 F pulseaudio
   /dev/snd/controlC0:  jl 3027 F pulseaudio
   /dev/snd/pcmC0D0p:   jl 3027 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  6 10:53:55 2020
  InstallationDate: Installed on 2020-04-24 (42 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: ThinkPad Thunderbolt 3 Dock USB Audio - ThinkPad Thunderbolt 3 
Dock USB
  Symptom_PulseAudioLog:
   Jun 05 20:03:08 x1c dbus-daemon[1617]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.37' (uid=125 pid=2067 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   Jun 05 20:03:24 x1c systemd[2021]: pulseaudio.service: Succeeded.
   Jun 05 20:03:34 x1c systemd[2021]: pulseaudio.socket: Succeeded.
  Symptom_Type: Volume slider, or mixer problems
  Title: [sof-hda-dsp - sof-hda-dsp, recording] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET47W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QES01L00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QES01L00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QES01L00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QES01L00
  dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1882340/+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 1872474] Re: Missing gpgme-json prevents use of popular Mailvelope browser extension

2020-08-07 Thread Launchpad Bug Tracker
This bug was fixed in the package gpgme1.0 - 1.13.1-9ubuntu2

---
gpgme1.0 (1.13.1-9ubuntu2) groovy; urgency=medium

  * Enable gpgme-json LP: #1872474
  * Add integration with Google Chrome.

 -- Dimitri John Ledkov   Sat, 18 Jul 2020 21:46:38
+0100

** Changed in: gpgme1.0 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Missing gpgme-json prevents use of popular Mailvelope browser
  extension

Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in gpgme1.0 source package in Focal:
  New
Status in gpgme1.0 package in Debian:
  New

Bug description:
  As described at the Mailvelope GitHub repository wiki here
   users are able to use their local GPG keyring via gpgme-
  json (rather than the included Openpgp.js library) with several
  popular webmail services, provided that the gpgme-json binary is
  available to the browser process. I reviewed the file lists for the
  binary packages produced from this source package and found no mention
  of it. Upon closer inspection of the packaging files, the d/rules has
  an override for dh_missing for the file and a note in the changelog
  from 2018, but there was no mention of what the circumstances were
  that necessitated that decision.

  If it's possible to correct the conditions that led to the file's
  exclusion I think it would be well worth pursuing as e-mail becomes
  evermore commercialized on top of an infrastructure that never did
  place much of a premium on privacy.

  I'm running the dev release of Kubuntu 20.04 LTS "Focal Fossa" with
  version 1.13.1-7ubuntu2 of the libgpgme11 package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1872474/+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 1888575] Re: Split motd-news config into a new package

2020-08-07 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/388922

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in base-files source package in Xenial:
  In Progress
Status in ubuntu-meta source package in Xenial:
  In Progress
Status in base-files source package in Bionic:
  In Progress
Status in ubuntu-meta source package in Bionic:
  In Progress
Status in base-files source package in Focal:
  In Progress
Status in ubuntu-meta source package in Focal:
  In Progress
Status in base-files source package in Groovy:
  In Progress
Status in ubuntu-meta source package in Groovy:
  In Progress

Bug description:
  The motd-news script is largely useless for desktop users, as they
  rarely login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a NEW package 
(motd-news-config)
  - have ubuntu-server depend on motd-news-config (or recommends)
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends (or recommends) on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888575/+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 1888572] Re: motd-news: use wget instead of curl

2020-08-07 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/388922

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

Title:
  motd-news: use wget instead of curl

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  In Progress
Status in base-files source package in Bionic:
  In Progress
Status in base-files source package in Focal:
  In Progress

Bug description:
  The motd-news script is using curl, but since that is an optional
  package, there is no guarantee that it will be installed. The script
  correctly checks for its presence before trying to use it, though, so
  it won't fail. As we don't want to add such a dependency to the base-
  files package, we should switch to wget, which is standard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888572/+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 1872560] Re: integer overflow in whoopsie 0.2.69

2020-08-07 Thread Launchpad Bug Tracker
This bug was fixed in the package whoopsie - 0.2.71

---
whoopsie (0.2.71) groovy; urgency=medium

  [ Marc Deslauriers ]
  * SECURITY UPDATE: integer overflow in bson parsing (LP: #1872560)
- lib/bson/*: updated to latest upstream release.
- CVE-2020-12135
  * SECURITY UPDATE: resource exhaustion via memory leak (LP: #1881982)
- src/whoopsie.c, src/tests/test_parse_report.c: properly handle
  GHashTable.
- CVE-2020-11937
  * SECURITY UPDATE: DoS via large data length (LP: #1882180)
- src/whoopsie.c, src/whoopsie.h, src/tests/test_parse_report.c: limit
  the size of a report file.
- CVE-2020-15570

 -- Brian Murray   Wed, 05 Aug 2020 15:00:45 -0700

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

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

Title:
  integer overflow in whoopsie 0.2.69

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Xenial:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released
Status in whoopsie source package in Eoan:
  Won't Fix
Status in whoopsie source package in Focal:
  Fix Released
Status in whoopsie source package in Groovy:
  Fix Released

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  ## Vulnerability in whoopsie
  - whoopsie 0.2.69 and earlier have a heap-based buffer overflow 
vulnerability. 
  - An attacker can cause a denial of service (memory corruption and 
application crash) via a crafted .crash file.

  
  ## Basic
  When a program has been crashed, Linux system tries to create a '.crash' file 
on '/var/crash/' directory with python script located in 
'/usr/share/apport/apport'. 
  The file contains a series of system crash information including core dump, 
syslog, stack trace, memory map info, etc.
  After the creation of '.crash' file, whoopsie extracts the above information 
from the '.crash' file and encodes it into binary json (bson) format.
  Lastly, whoopsie forwards the data to a remotely connected Ubuntu Error 
Report system.

   
  ## Vulnerability
  Unfortunately, we have found a heap-based buffer overflow vulnerability 
during the encoding, when whoopsie attempts to bsonify with crafted crash file.
  The data in '.crash' file is stored in key-value form and the whoopsie 
separately measures the length of 'key' and 'value' to allocate memory region 
during the encoding. 
  A heap-based buffer overflow can occur when an integer overflow happens on a 
variable that contains length of 'key'. 
  FYI, a issue to that raised by 'value' is well covered by performing 
exception handling.

  
@[bson.c:663][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n663]

  const uint32_t len = strlen( name ) + 1;

  - Integer overflow occurs when length of ‘name’ exceeds INT32_MAX value. 
  - Here, ‘name’ indicates the ‘key’ data in ‘.crash’ file.

  
@[bson.c:627][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n627]

  b->data = bson_realloc( b->data, new_size );

  - Unexpected small memory region is allocated due to above integer
  overflow.

  
@[bson.c:680][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n680]

  bson_append( b, name, len );

  - Memory corruption happens when unexpected small memory region is
  allocated.

  
  ## Attack Scenario
  1) Create a fake.crash file
  - '.crash' file is composed of the following format: 'key : value'.
  - To cause the overflow attack, the size of 'key' should be in double amount 
of INT32_MAX.
  - The size of 'value' doesn’t matter, but not zero length.

  $ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash
  $ cat fake.crash
  AAA … AA : B

  
  2) Trigger the whoopsie to read the fake.crash file
  - Just create 'fake.upload' file by touch command.
  - Or launch apport-gtk gui or apport-bug cli application.

  3) Check out the result
  - After a while, the whoopsie has been killed by segmentation fault.

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1872560/+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 1882180] Re: DoS vulnerability: fail to allocate

2020-08-07 Thread Launchpad Bug Tracker
This bug was fixed in the package whoopsie - 0.2.71

---
whoopsie (0.2.71) groovy; urgency=medium

  [ Marc Deslauriers ]
  * SECURITY UPDATE: integer overflow in bson parsing (LP: #1872560)
- lib/bson/*: updated to latest upstream release.
- CVE-2020-12135
  * SECURITY UPDATE: resource exhaustion via memory leak (LP: #1881982)
- src/whoopsie.c, src/tests/test_parse_report.c: properly handle
  GHashTable.
- CVE-2020-11937
  * SECURITY UPDATE: DoS via large data length (LP: #1882180)
- src/whoopsie.c, src/whoopsie.h, src/tests/test_parse_report.c: limit
  the size of a report file.
- CVE-2020-15570

 -- Brian Murray   Wed, 05 Aug 2020 15:00:45 -0700

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

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

Title:
  DoS vulnerability: fail to allocate

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Xenial:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released
Status in whoopsie source package in Eoan:
  Confirmed
Status in whoopsie source package in Focal:
  Fix Released
Status in whoopsie source package in Groovy:
  Fix Released

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  # Vulnerability description
  In whoopsie 0.2.69 and earlier, there is a denial of service vulnerability in 
the parse_report function.
  A crafted input, i.e., crash report located in '/var/crash/', will lead to a 
denial of service attack.
  During the parsing of the crash report, the data length is not checked.   
  
  The value of data length can be directly controlled by an input file. 
  
  In the parse_report() function, the g_malloc or g_realloc is called based on 
data length.
  If we set the value of data length close to the amount of system memory, it 
will cause the daemon process to terminate unexpectedly, hang the system, or 
trigger the OOM killer.

  # PoC
  Please check the below whoopsie_killer2.py

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1882180/+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 1881982] Re: DoS vulnerability: cause resource exhaustion

2020-08-07 Thread Launchpad Bug Tracker
This bug was fixed in the package whoopsie - 0.2.71

---
whoopsie (0.2.71) groovy; urgency=medium

  [ Marc Deslauriers ]
  * SECURITY UPDATE: integer overflow in bson parsing (LP: #1872560)
- lib/bson/*: updated to latest upstream release.
- CVE-2020-12135
  * SECURITY UPDATE: resource exhaustion via memory leak (LP: #1881982)
- src/whoopsie.c, src/tests/test_parse_report.c: properly handle
  GHashTable.
- CVE-2020-11937
  * SECURITY UPDATE: DoS via large data length (LP: #1882180)
- src/whoopsie.c, src/whoopsie.h, src/tests/test_parse_report.c: limit
  the size of a report file.
- CVE-2020-15570

 -- Brian Murray   Wed, 05 Aug 2020 15:00:45 -0700

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

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

Title:
  DoS vulnerability: cause resource exhaustion

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Xenial:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released
Status in whoopsie source package in Eoan:
  Confirmed
Status in whoopsie source package in Focal:
  Fix Released
Status in whoopsie source package in Groovy:
  Fix Released

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  # Vulnerability description
  The parse_report() function in whoopsie.c allows attackers to cause a denial 
of service (memory leak) via a crafted file. 
  Exploitation of this issue causes excessive memory consumption which results 
in the Linux kernel triggering OOM killer on arbitrary process.
  This results in the process being terminated by the OOM killer.

  
  # Details 
  We have found a memory leak vulnerability during the parsing the crash file, 
when a collision occurs on GHashTable through g_hash_table_insert().
  According to [1], if the key already exists in the GHashTable, its current 
value is replaced with the new value.
  If 'key_destory_func' and 'value_destroy_func' are supplied when creating the 
table, the old value and the passed key are freed using that function.
  Unfortunately, whoopsie does not handle the old value and the passed key when 
collision happens.
  If a crash file contains same repetitive key-value pairs, it leads to memory 
leak as much as the amount of repetition and results in denial-of-service.

  [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g
  -hash-table-insert

  
  # PoC (*Please check the below PoC: whoopsie_killer.py)
  1) Generates a certain malformed crash file that contains same repetitive 
key-value pairs.
  2) Trigger the whoopsie to read the generated crash file.
  3) After then, the whoopsie process has been killed.

  
  # Mitigation (*Please check the below patch: g_hash_table_memory_leak.patch)
  We should use g_hash_table_new_full() with ‘key_destroy_func’ and 
‘value_destroy_func’ functions instead of g_hash_table_new().
  Otherwise, before g_hash_table_insert(), we should check the collision via 
g_hash_table_lookup_extended() and obtain pointer to the old value and remove 
it.

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1881982/+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 1890716] [NEW] xdg-mime query filetype index.html reports wrong type

2020-08-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

For .html files `xdg-mime` reports wrong type. The culprit is the `"use
strict"` phrase which is used in JavaScript. It should not mistake .html
files for anything else except of text/html !

STEPS TO REPRODUCE:
Run the following step by step in any folder:
1. $ echo "\"use strict\"" > index.html
2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

Platform:
Ubuntu 20.04.1 LTS (Focal Fossa)"
Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

xdg-utils: 1.1.3-2ubuntu1

** Affects: shared-mime-info (Ubuntu)
 Importance: Low
 Status: Invalid


** Tags: 20.04 html kde kubuntu perl xdg-mime xdg-open
-- 
xdg-mime query filetype index.html reports wrong type
https://bugs.launchpad.net/bugs/1890716
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to shared-mime-info in Ubuntu.

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


[Touch-packages] [Bug 1560094] Re: Starting bluez service is denied

2020-08-06 Thread Launchpad Bug Tracker
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Starting bluez service is denied

Status in bluez package in Ubuntu:
  Expired

Bug description:
  If snappy core is updated in the background (on Raspberry Pi 2), and
  then bluez installed, starting the service is failing.

  
  Denials:

  [   45.955490] audit: type=1400 audit(1458574955.667:11): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=834 comm="c0
  [   46.197608] audit: type=1326 audit(1458574955.907:12): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=831 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.275680] audit: type=1400 audit(1458574955.987:13): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=829 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.276483] audit: type=1326 audit(1458574955.987:14): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=829 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.412021] audit: type=1326 audit(1458574956.123:15): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=839 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.504308] audit: type=1400 audit(1458574956.215:16): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=842 comm="c0
  [   46.520137] audit: type=1400 audit(1458574956.231:17): apparmor="DENIED" 
operation="create" profile="bluez5_bluez_5.37-2-armhf" pid=841 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1
  [   46.520800] audit: type=1326 audit(1458574956.231:18): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=841 comm="bluetoothd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/bluetoothd" sig=31 arch=4000
  [   46.625293] audit: type=1326 audit(1458574956.335:19): auid=4294967295 
uid=0 gid=0 ses=4294967295 pid=844 comm="obexd" 
exe="/snaps/bluez5/5.37-2-armhf/usr/lib/bluetooth/obexd" sig=31 arch=4028 
sysc0
  [   46.721080] audit: type=1400 audit(1458574956.431:20): apparmor="DENIED" 
operation="mknod" profile="bluez5_bluez_5.37-2-armhf" 
name="/etc/dbus-1/system.d/bluez5_bluez_5.37-2-armhf.conf" pid=847 comm="c2

  If trying to start bluetootctl:

  [  582.205066] audit: type=1400 audit(1458575491.915:31): apparmor="DENIED" 
operation="connect" profile="bluez5_bluetoothctl_5.37-2-armhf" 
name="/run/dbus/system_bus_socket" pid=993 comm="bluetoothctl" re0
  [bluetooth]# 

  
  ubuntu@localhost:~$ snappy list
  NameDate   Version  Developer 
  bluez5  2016-02-04 5.37-2-armhf canonical 
  canonical-pi2   2016-02-02 3.0  canonical 
  canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical 
  ubuntu-core 2016-03-08 16.04.0-15.armhf canonical 
  ubuntu@localhost:~$ 

  ubuntu@localhost:~$ snappy info
  release: core/rolling
  architecture: armhf
  frameworks: bluez5.canonical
  apps:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1560094/+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 1864287] Re: pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected

2020-08-06 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  pulseaudio still trying to reproduce audio to HDMI without the HDMI
  cable connected

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Yesterday I was using the HDMI cable to duplicate the monitor in the
  tv and play sound with the tv by selecting HDMI exit sound in ubuntu
  settings.

  With the pc turned off I removed the HDMI from the tv but ubuntu
  doesn't automatically set the exit sound to the default till in the
  settings there is only that option and till I selected it, ubuntu was
  still trying to reproduce the audio via HDMI...

  Also rebooting the system the problem persists.

  Also by reloading pulseaudio the problem persists.

  The only solution was installing a third-party program to switch
  correctly to the default audio exit...

  lsb_release -rd:
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  apt-cache policy pulseaudio:
  pulseaudio:
Installato: 1:11.1-1ubuntu7.2
Candidato:  1:11.1-1ubuntu7.4
Tabella versione:
   1:11.1-1ubuntu7.4 500
  500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   *** 1:11.1-1ubuntu7.2 100
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7 500
  500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1864287/+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 1405199] [NEW] Using open() on an optical drive with its tray open will close the tray

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I'm using Ubuntu 15.04 dev with udev 218-2ubuntu3 and if the tray of an
optical drive is open and open() will then be used on the device file
the tray will be closed. Here is an example code (compiled with "gcc
-Wall -pedantic -o test test.c"):

#include 

int main()
{
open("/dev/sr0", O_EXCL);
return 0;
}


Normally I would expect that the tray doesn't get closed so I'm assuming an 
udev rule causes this behavior.

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


** Tags: vivid
-- 
Using open() on an optical drive with its tray open will close the tray
https://bugs.launchpad.net/bugs/1405199
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1456338] [NEW] USB floppy drive is running without floppy

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When I connect USB floppy drive (Gembird) without floppy under Ubuntu, the 
drive engine seems to be running (the floppy drive LED is on and the drive is 
sounding). The same behaviour takes place if I connect the drive with a floppy 
and then remove the floppy. It seems that the system accesses the drive 
permanently when there is no floppy. Under Windows XP it works normally - when 
there is no floppy, the LED and engine are switched off. I have tried Ubuntu 
14.10 (amd64) with upstart, LXQt and KDE 5; Ubuntu 15.04 with systemd, LXQt - 
the same behaviour.
If I boot using bash as init (init=/bin/bash) and connect the floppy drive 
after boot, the engine is off (the normal behaviour).
lsof /dev/sdb during engine running outputs nothing.

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


** Tags: bot-comment floppy hardware usb
-- 
USB floppy drive is running without floppy
https://bugs.launchpad.net/bugs/1456338
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1495723] [NEW] Connecting USB devices failing

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

rob@DesktopUbuntu:~$ lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04

Ubuntu Software Center 13.10  (XUbuntu)

I have had a problem with connecting my phone as a memory/disk device on
Ubuntu 14.04 and found the same with a live install of 15.04. I recently
bought an expensive 3-D Robox-CEL printer and was also experiencing no
joy at all with extremely flaky connections.  Fortunately one of the
engineers at Robox-CEL published a patch to the udev .rules files and
this cured the 3-D Printer connections and when I applied the same to
the mobile phone .rules file it has been reliable as well.  His
assertion was the later Linux's (I am not sure how wide he sees this
problem here) have some sort of 'improvement' that interrogates the USB
devices and in my case these two devices don't work with this new
'feature' and are extremely flaky.

Here are the two new .rules I have added, that work for me

# Samsung
ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="685b", ENV{ID_MM_DEVICE_IGNORE}="1"
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="685b", 
GROUP="plugdev", NAME="GalaxySII", MODE="0666", OWNER=""

#Robox Rules to stop the Linux sending disruptive commands to the 3D-Printer
ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="081b", ENV{ID_MM_DEVICE_IGNORE}="1"
#Establish a standard name for the Robox tty interface
SUBSYSTEM=="tty", ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="081b", 
SYMLINK="robox%n", MODE="0666"

The first line in the .rules is the really critical one.

This has been a huge problem for me, and I registering it as a 'bug' as
I believe the OS should be a bit more clever with these devices and
should not require this sort of user work-around.  Over the last two
years my phone went from super reliable to unusable, wasting huge
amounts of my time, and recently made my 14 day old 3-D Printer from a
quality manufacturer useless.

Thank you for your time and patience. I can send you a log of the
transactions of the Robox machine's interactions with the USB port if
you need them.  However the above two files should give a good lead on
where I feel the problems lie.

Cheers, Rob Ward

PS The Robox people also altered the shell script in their software to
look for the newly named 'robox0' connection.

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


** Tags: bot-comment
-- 
Connecting USB devices failing
https://bugs.launchpad.net/bugs/1495723
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1526111] [NEW] RAID1 + LVM in 14.04.3 causes intermittent boot failure

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

This problem seems to be related to a timing bug within `udev`, and has been 
experienced by other users as seen here;
http://serverfault.com/questions/567579/boot-failure-with-root-on-md-raid1-lvm-udev-event-timing

Changing `/dev/md/0` to `/dev/md0` inside `/etc/mdadm/mdadm.conf` seems
to resolve the problem. However unless you apply this patch, the system
will intermittently fail to boot correctly, getting stuck here;

kernel: [3.003506] md: bind
kernel: [3.007705] md/raid1:md0: active with 1 out of 1 mirrors
kernel: [3.007768] md0: detected capacity change from 0 to 499972440064
kernel: [3.047284]  md0: unknown partition table
kernel: [3.124709] device-mapper: table: 252:0: linear: dm-linear: Device 
lookup failed
kernel: [3.124759] device-mapper: ioctl: error adding target to table
kernel: [3.125156] device-mapper: table: 252:1: linear: dm-linear: Device 
lookup failed
kernel: [3.125196] device-mapper: ioctl: error adding target to table

There is also an example `/lib/udev/rules.d/` patch inside the thread I
posted above, which proposes to add a `sleep` statement into LVM udev
rules.

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


** Tags: lvm mdadm raid
-- 
RAID1 + LVM in 14.04.3 causes intermittent boot failure
https://bugs.launchpad.net/bugs/1526111
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1562589] [NEW] USB DVDRW's No Longer Function Correctly in 15.10 or 16.04

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After upgrading several systems from 15.04 to 15.10, none of the systems
were able to recognize the DVDRW in userland. This was tested with two
different USB DVDRW's

*-cdrom
   description: DVD-RAM writer
   product: SuperMultiPA3761
   vendor: Toshiba
   physical id: 0.0.0
   bus info: scsi@4:0.0.0
   logical name: /dev/cdrom
   logical name: /dev/cdrw
   logical name: /dev/dvd
   logical name: /dev/dvdrw
   logical name: /dev/sr0
   version: TO01
   capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
   configuration: status=ready
 *-medium
  physical id: 0
  logical name: /dev/cdrom


And

  *-cdrom
   description: DVD-RAM writer
   product: DVD RW DRU-830A
   vendor: SONY
   physical id: 0.0.0
   bus info: scsi@5:0.0.0
   logical name: /dev/cdrom
   logical name: /dev/cdrw
   logical name: /dev/dvd
   logical name: /dev/dvdrw
   logical name: /dev/sr0
   version: SS15
   capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ram
   configuration: status=ready
 *-medium
  physical id: 0
  logical name: /dev/cdrom

This was also tested on 4 different systems. Three with Ubuntu and one
with Kubuntu. I upgraded Kubuntu to 16.04. The difference in 16.04 is
peculiar. The DVD player does not appear in any file manager. However, I
could access the DVD via VLC. Attempting to play the DVD failed however.
There was no sound and any option  chosen on the DVD menu resulted in a
blank/black screen.

This bug seems to afflict other users:

http://askubuntu.com/questions/692934/after-upgrade-to-ubuntu-15-10-can-
no-longer-access-video-files-on-cd-dvd

I've also included this report here:

https://bugs.launchpad.net/ubuntu/+source/udev/+bug/646293?comments=all

But am filing a new bug since the other seems to be dead and/or
outdated.

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

-- 
USB DVDRW's No Longer Function Correctly in 15.10 or 16.04
https://bugs.launchpad.net/bugs/1562589
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1559643] [NEW] kswapd0 high cpu

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

kswapd0 high cpu load.
System doesn't have swap partition / swap file.

Using AWS t2.nano

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-34-generic 4.2.0-34.39
ProcVersionSignature: User Name 4.2.0-34.39-generic 4.2.8-ckt4
Uname: Linux 4.2.0-34-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Mar 20 07:35 seq
 crw-rw 1 root audio 116, 33 Mar 20 07:35 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Sun Mar 20 07:57:52 2016
Ec2AMI: ami-b7443fc0
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: eu-west-1a
Ec2InstanceType: t2.nano
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
MachineType: Xen HVM domU
PciMultimedia:
 
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 0 cirrusdrmfb
 1 xen
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=b079c5f1-8fc8-4bb0-aa26-31610f9c5615 ro console=tty1 console=ttyS0
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-34-generic N/A
 linux-backports-modules-4.2.0-34-generic  N/A
 linux-firmware1.149.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2015-11-13 (127 days ago)
dmi.bios.date: 12/07/2015
dmi.bios.vendor: Xen
dmi.bios.version: 4.2.amazon
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/07/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
dmi.product.name: HVM domU
dmi.product.version: 4.2.amazon
dmi.sys.vendor: Xen

** Affects: linux (Ubuntu)
 Importance: Medium
 Status: Confirmed

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


** Tags: amd64 apport-bug ec2-images wily
-- 
kswapd0 high cpu
https://bugs.launchpad.net/bugs/1559643
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1564159] [NEW] vbox guest rules should be included by default

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Since vivid, Ubuntu ships the VirtualBox drivers as part of the main
kernel package, by incorporating the virtualbox-guest-dkms package
directly. See
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1418743 . However,
the udev rules (/lib/udev/rules.d/60-virtualbox-guest-dkms.rules) from
the same DKMS package are not beind shipped with the main udev
installation. This leads to incorrect permissions of the /dev/vboxuser
device. Since Ubuntu ships the kernel modules "by default" it should do
the same for the udev rules. This is broken in vivid, wily and xenial.

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

-- 
vbox guest rules should be included by default
https://bugs.launchpad.net/bugs/1564159
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1583372] [NEW] 73-special-net-names.rules is renaming manually created wifi interface

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The 73-special-net-names.rules file from 229-4ubuntu5 is renaming USB
wifi network interfaces that I create manually with "iw phy phy0
interface add wifi0 type managed":

# Use MAC based names for network interfaces which are directly or indirectly
# on USB and have an universally administered (stable) MAC address (second bit
# is 0).
ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb", NAME=="", 
ATTR{address}=="?[014589cd]:*", IMPORT{builtin}="net_id", 
NAME="$env{ID_NET_NAME_MAC}"


The device is being renamed by udev as soon as it is created:
KERNEL[3299.499637] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0 (net)
KERNEL[3299.500180] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/rx-0 (queues)
KERNEL[3299.500388] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-0 (queues)
KERNEL[3299.500548] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-1 (queues)
KERNEL[3299.500680] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-2 (queues)
KERNEL[3299.500811] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-3 (queues)
KERNEL[3299.502911] move 
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wlxc83a35c1 (net)
UDEV  [3299.546165] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wlxc83a35c1 (net)
UDEV  [3299.547977] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/rx-0 (queues)
UDEV  [3299.549123] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-0 (queues)
UDEV  [3299.550082] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-1 (queues)
UDEV  [3299.550353] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-2 (queues)
UDEV  [3299.550495] add  
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wifi0/queues/tx-3 (queues)
UDEV  [3299.552404] move 
/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/net/wlxc83a35c1 (net)

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

-- 
73-special-net-names.rules is renaming manually created wifi interface
https://bugs.launchpad.net/bugs/1583372
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1618471] [NEW] udev: init script unconditionally writes to /sys/kernel/uevent_helper

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The udev initramfs-tools script from trusty lts:

/usr/share/initramfs-tools/scripts/init-top/udev

does not check if uevent_helper does exist and fails to boot if it is
missing - which it is in recent kernels (e.g. 4.7.2 from the mainline
ppa or modern self build kernels where it is disabled per default
afaik).

See e.g.: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756312

Its fixed in xenials version (latest LTS) but fails in current supported LTS 
trusty to boot.
Please backport those simple fix:

if [ -w /sys/kernel/uevent_helper ]; then
echo > /sys/kernel/uevent_helper
fi

and maybe add

udevadm settle || true

at the end to support kernels without uevent_helper enabled.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: systemd (Debian)
 Importance: Unknown
 Status: Fix Released


** Tags: trusty
-- 
udev: init script unconditionally writes to /sys/kernel/uevent_helper
https://bugs.launchpad.net/bugs/1618471
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1634714] [NEW] ASUS T300 CHI Keyboard Fn Mappings

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I believe that this is in the incorrect queue, but Launchpad would not
allow me to move it to udev.

I am submitting this bug report following the directions at
https://wiki.ubuntu.com/Hotkeys/Troubleshooting

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
Ubuntu 16.10

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
  Installed: 231-9git1

The Fn+F5,F6,F7, and F9 combinations do not produce the desired behavior
of changing screen brightness or toggling the touchpad on the ASUS T300
Chi bluetooth keyboard. They do not produce any response whatsoever.

They key events (as according to evtest) and their functions are listed
below.

type 2 (EV_REL), code 9 (REL_MISC), value 16 : Brightness Down (Fn + F5)
type 2 (EV_REL), code 9 (REL_MISC), value 32 : Brightness Up (Fn + F6)
type 2 (EV_REL), code 9 (REL_MISC), value 53 : Disable LCD Backlight (Fn + F7)
type 2 (EV_REL), code 9 (REL_MISC), value 107 : Disable Touchpad (Fn + F9)

Please let me know if I missed anything, this is my first bug report.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: udev 231-9git1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Oct 18 20:04:07 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-10-18 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 06cb:11f0 Synaptics, Inc.
 Bus 001 Device 003: ID 0bda:57d2 Realtek Semiconductor Corp.
 Bus 001 Device 012: ID 8087:0a2a Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. T300CHI
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed 
root=UUID=33082bfc-d5e7-4dd9-869c-01e06d67bb28 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/06/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: T300CHI.207
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: T300CHI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.207:bd08/06/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: T300CHI
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug yakkety
-- 
ASUS T300 CHI Keyboard Fn Mappings
https://bugs.launchpad.net/bugs/1634714
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1635729] [NEW] bcache won't start on boot due to exotic block devices filtered in udev rules

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

If a bcache is created with a Curtis-Wright NVRAM card as caching
device, the bcache device will not show up on boot without manual
intervention.

Tracking this down show this being due to the fact, that line 9 of
/lib/udev/rules.d/60-persistent-storage.rules filters on a whitelist of
devices
(loop*|mmcblk*[0-9]|msblk*[0-9]|mspblk*[0-9]|nvme*|sd*|sr*|vd*|xvd*|bcache*|cciss*|dasd*|ubd*),
that doesn't include the NVRAM devices (umem*). A few steps later, this
results in bcache_register() not being called.

Trivially patching

-KERNEL!="loop*|mmcblk*[0-9]|msblk*[0-9]|mspblk*[0-9]|nvme*|sd*|sr*|vd*|xvd*|bcache*|cciss*|dasd*|ubd*",
 GOTO="persistent_storage_end"
+KERNEL!="loop*|mmcblk*[0-9]|msblk*[0-9]|mspblk*[0-9]|nvme*|sd*|sr*|vd*|xvd*|bcache*|cciss*|dasd*|ubd*|umem*",
 GOTO="persistent_storage_end"

resolves the issue.

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


** Tags: bot-comment
-- 
bcache won't start on boot due to exotic block devices filtered in udev rules
https://bugs.launchpad.net/bugs/1635729
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1638518] [NEW] USB port gets rarely disabled until the next reboot

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I'm using Ubuntu 17.04 dev with udev 231-10 and rarely (happened now the
second time within 1-2 months) I'm noticing that the USB port of my
mouse disables. This happens randomly on the current boot instance and
replugging the mouse into the same USB port does not solve the issue.
But plugging the mouse into another port causes it to work again but
trying to plugging it back to the old port causes it to not work
anymore. The only way to get the USB port working again is to reboot the
system.

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

-- 
USB port gets rarely disabled until the next reboot
https://bugs.launchpad.net/bugs/1638518
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1888572] Re: motd-news: use wget instead of curl

2020-08-06 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/388848

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

Title:
  motd-news: use wget instead of curl

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  In Progress
Status in base-files source package in Bionic:
  In Progress
Status in base-files source package in Focal:
  In Progress

Bug description:
  The motd-news script is using curl, but since that is an optional
  package, there is no guarantee that it will be installed. The script
  correctly checks for its presence before trying to use it, though, so
  it won't fail. As we don't want to add such a dependency to the base-
  files package, we should switch to wget, which is standard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888572/+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 1888575] Re: Split motd-news config into a new package

2020-08-06 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/388848

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in base-files source package in Xenial:
  In Progress
Status in ubuntu-meta source package in Xenial:
  In Progress
Status in base-files source package in Bionic:
  In Progress
Status in ubuntu-meta source package in Bionic:
  In Progress
Status in base-files source package in Focal:
  In Progress
Status in ubuntu-meta source package in Focal:
  In Progress
Status in base-files source package in Groovy:
  In Progress
Status in ubuntu-meta source package in Groovy:
  In Progress

Bug description:
  The motd-news script is largely useless for desktop users, as they
  rarely login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a NEW package 
(motd-news-config)
  - have ubuntu-server depend on motd-news-config (or recommends)
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends (or recommends) on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888575/+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 1646557] [NEW] /bin/udevadm should be exit 0 instead of exit 1

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

if [ "$1" = "trigger" ]; then
echo "some text halt was sinnvolle oder unsinniges zum Abruch
  exit 1
fi

apt-get install rfkill 
for example fails to configure 

why not in /bin/udevadm end with exit 0 in case of trigger
or settle? 

then apt-get install rfkill and 28 other packages can configure

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

-- 
/bin/udevadm should be exit 0 instead of exit 1
https://bugs.launchpad.net/bugs/1646557
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1647067] [NEW] Dangling UDEV links after removing FC LUNs

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

We're using Q-Logic QLE2562 Fibre Channel adapters (qla2xxx driver)
against a HPE 3PAR 7400c storage array in an OpenStack environment. The
OpenStack 3PAR driver manages volume attachments from the array to the
servers. There is 4 path multipath to every volume.

As the LUNs are removed, sometimes udev does not remove all links,
particularly in /run/udev/links and /dev/disk/by-path. The symptoms are
multiple records in one by-path directory under /run/udev/links, broken
links to no longer attached luns in dev/disk/by-path and links between
wrong LUNs and scsi devices there.

OpenStack relies on these links. When another volume is attached using a
LUN that has these leftover links and it happens that it is the first of
the 4 paths, OpenStack incorrectly identifies the volume and attaches
the same volume to multiple instances, leading to data loss.

What could be causing this behavior?

Ubuntu version 14.04 
Linux version Ubuntu 4.4.0-47.68~14.04.1-generic 4.4.24
udev 204-5ubuntu20.19
--- 
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CustomUdevRuleFiles: 20-3par-unmap.rulez
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2015-10-01 (429 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
MachineType: HP ProLiant DL380 Gen9
Package: udev 204-5ubuntu20.19
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic 
root=/dev/mapper/hostname--vg-root ro
ProcVersionSignature: Ubuntu 4.4.0-47.68~14.04.1-generic 4.4.24
Tags:  trusty
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 4.4.0-47-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
_MarkForUpload: True
dmi.bios.date: 11/03/2014
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrP89:bd11/03/2014:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr:
dmi.product.name: ProLiant DL380 Gen9
dmi.sys.vendor: HP

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


** Tags: apport-collected kernel-da-key trusty
-- 
Dangling UDEV links after removing FC LUNs
https://bugs.launchpad.net/bugs/1647067
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1647078] [NEW] udevadm trigger (falsely?) reports udev is not configured

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Eigentlich wollte ich nur ubuntu oder gnome als Desktop verwenden, da
beide nicht starteten nahm ich dann Meta das läuft wenigstens und bekam
die Fehlermeldung präsentiert. udisk2 ist wohl ein Abhängigkeitspaket
für ubuntu-Desktop oder gnome-desktop beide wollen nicht laufen, warum
auch immer.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: udisks2 2.1.7-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
Uname: Linux 4.4.0-51-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.2
Architecture: amd64
CustomUdevRuleFiles: 51-android.rules 69-usbmoto.rules 69-libmtp.rules 
60-raw1394.rules z60_hdaps-games.rules README.dpkg-new 51-hdaps.rules 
69-phicomm.rules
Date: Thu Dec  1 12:10:32 2016
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
MachineType: LENOVO 3093BU3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic 
root=UUID=7aead086-5ba6-492c-921a-17a5656dba11 ro locale=de_DE bootkbd=de 
console-setup/layoutcode=de quiet splash selinux=0 enforcing=0 acpi_osi=Linux 
loglevel=0 vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: udisks2
Title: package udisks2 2.1.7-1ubuntu1 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/11/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET70WW (1.40 )
dmi.board.name: 3093BU3
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:svnLENOVO:pn3093BU3:pvrThinkPadX201Tablet:rvnLENOVO:rn3093BU3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3093BU3
dmi.product.version: ThinkPad X201 Tablet
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package xenial
-- 
udevadm trigger (falsely?) reports udev is not configured
https://bugs.launchpad.net/bugs/1647078
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1652019] [NEW] udev does not read LINK files dynamically

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hello all,

To comply to SystemD's way of thinking, NIC names can be changed
assuming my MAC addresses.

I have then changed /etc/systemd/10-net.link assuming the nomenclature
in https://www.freedesktop.org/software/systemd/man/systemd.link.html.

Expected behavior: When restart, changes can be taken into account and
NIC names changed, just like udev udev raw rules in /etc/udev/rules.d.

Got: NIC names not changed. However: whane re-updating initramfs ( #
update-initramfs -u ), it works.

Question: why is udev not reading SystemD link files directly in the
root FS, but is able to read udev rules.d files ?

Distro : Ubuntu 16.04.4

Thanks,

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


** Tags: bot-comment
-- 
udev does not read LINK files dynamically
https://bugs.launchpad.net/bugs/1652019
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1665143] [NEW] Commission scripts select the wrong nvme device link, then fails to report any storage

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The udev package provides /lib/udev/rules.d/60-persistent-storage.rules
which creates two symlinks for nvme devices, under /dev/disk/by-id/. The
first link name includes the device wwid and the second includes the
device model/serial. The commission script selects the first link
discovered and subsequently attempts to store it in a FilePath field,
which allows for 100 characters. Since the wwid link is greater than 100
characters an exception is thrown, causing not only the nvme device not
to be registered but all other storage devices as well. Although
commissioning completes there is no storage assigned, which makes
deployment of the node impossible.

This issue has blocked all test runs performed by the CDO-QA test
infrastructure, since every run installs MAAS on a fresh machine and
commissions new nodes. The failure is seen when installing from either
ppa:maas/next (2.2.0~beta2) or ppa:maas/stable (2.1.3+bzr5573).

ubuntu@meowth:~$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion  
Architecture Description
+++-===---=
ii  maas2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all
  "Metal as a Service" is a physical cloud and IPAM
ii  maas-cli2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all
  MAAS client and command-line interface
un  maas-cluster-controller 
  (no description available)
ii  maas-common 2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all
  MAAS server common files
ii  maas-dhcp   2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all
  MAAS DHCP server
ii  maas-dns2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all
  MAAS DNS server
ii  maas-proxy  2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all
  MAAS Caching Proxy
ii  maas-rack-controller2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all
  Rack Controller for MAAS
ii  maas-region-api 2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all
  Region controller API service for MAAS
ii  maas-region-controller  2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all
  Region Controller for MAAS
un  maas-region-controller-min  
  (no description available)
un  python-django-maas  
  (no description available)
un  python-maas-client  
  (no description available)
un  python-maas-provisioningserver  
  (no description available)
ii  python3-django-maas 2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all
  MAAS server Django web framework (Python 3)
ii  python3-maas-client 2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all
  MAAS python API client (Python 3)
ii  python3-maas-provisioningserver 2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all
  MAAS server provisioning libraries (Python 3)

After re-commissioning one of the servers with ssh enabled the attached
log files were collected. Please note that from the shell it can be seen
that block devices are discovered and even the commissioning output
found in /tmp/user_data.sh.IK9yVp/out/00-maas-07-block-devices lists
devices (see attached), where-as this file is shown as a 0 byte file
from the GUI (see screen shot).

There are 'HTTP Error 500: INTERNAL SERVER ERROR' errors in cloud-init-
output.log

ubuntu@azurill:~$ uname -a
Linux azurill 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:55:08 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

ubuntu@azurill:~$ sudo lsblk  --exclude 1,2,7 -d -P -o NAME,RO,RM,MODEL,ROTA
NAME="sdb" RO="0" RM="0" MODEL="LOGICAL VOLUME  " ROTA="1"
NAME="sdc" RO="1" RM="0" MODEL="VIRTUAL-DISK" ROTA="1"
NAME="sda" RO="0" RM="0" MODEL="LOGICAL VOLUME  " ROTA="1"
NAME="nvme0n1" RO="0" RM="0" MODEL="INTEL SSDPEDME400G4

** Affects: maas
 Importance: High
 Status: Fix Released

** Affects: maas/2.1
 Importance: High
 Assignee: Andres Rodriguez (andreserl)
 Status: Fix Released

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


** Tags: cdo-qa sts
-- 
Commission scripts select the wrong nvme device link, then fails to report any 
storage
https://bugs.launchpad.net/bugs/1665143
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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

[Touch-packages] [Bug 1669420] [NEW] udevadm unconfigured script leaks into initrd causing boot failure

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

If update-initramfs is run while udevadm is "unconfigured", then the
system is rendered unbootable.  Instead of containing a working version
of udevadm, the "initrd" is built with the wrapper script that reports
an error, and proceeds no further (as per code below).

Please incorporate the check for 'unconfigured' into the code for
udevadm, so that the udevadm binary can work correctly whether it is on
an unconfigured system, or an initrd.

This was a sticky problem, because no amount of 'dpkg-reconfigure udev'
did the required 'mv udevadm.upgrade udevadm'

#!/bin/sh

if [ "$1" = "trigger" ]; then
echo "udevadm trigger is not permitted while udev is unconfigured." 1>&2
exit 1
fi
# ... snip ...
exec /bin/bash -c "exec -a \"\$0\" /bin/udevadm.upgrade \"\$@\"" "$0" "$@"

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

-- 
udevadm unconfigured script leaks into initrd causing boot failure
https://bugs.launchpad.net/bugs/1669420
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1702320] [NEW] CUPS serial backend don't initialize correctly USB to serial converters

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

CUPS serial backend don't initialize correctly USB to serial converters

See here for more details:

https://bugs.linuxfoundation.org/show_bug.cgi?id=1397

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: cups-filters 1.13.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Tue Jul  4 16:57:25 2017
InstallationDate: Installed on 2010-02-19 (2691 days ago)
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Lpstat: device for PRN-ttyS0: 
serial:/dev/ttyUSB0?baud=38400+bits=8+parity=none+flow=dtrdsr
MachineType: System manufacturer System Product Name
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=UUID=6c704848-ff2d-4ef5-ba14-bbbe8a620cd0 ro quiet splash vt.handoff=7
SourcePackage: cups-filters
UpgradeStatus: Upgraded to zesty on 2017-07-03 (0 days ago)
dmi.bios.date: 08/23/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1003
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5KPL-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.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.:bvr1003:bd08/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-VM:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug zesty
-- 
CUPS serial backend don't initialize correctly USB to serial converters
https://bugs.launchpad.net/bugs/1702320
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1712575] [NEW] Upgrade from Ubuntu 12.04 LTS to 14.04 LTS Server. Can't bring up eth0. RTNETLINK answers: no such process [61709.025401] bnx2: can't load firmware file bnx2/bnx2-

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hi. I just did a do-release-upgrade from Ubuntu Server 12.04 to 14.04
LTS. After the upgrade eth0 does not exist. Networking fails on boot.
Its on a Dell PowerEdge 2950 with one network connection and one static
address on eth0 only (dual nics, 2nd is not being used).

Here is the error I'm getting when trying to ifup eth0.

RTNETLINK answers: no such process
[61709.025401] bnx2: Can't load firmware file "bnx2/bnx2-mips-06-6.2.3.fw"
RTNETLINK answers: No such file or directory
Failed to bring up eth0.

If I check dmesg, I can see the same error that it can't load the
firmware file. I checked in /lib/firmware and the file is indeed there.


This could be a dupe of this bug. However, I was told to file a new one as it 
is still an issue.
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/842560

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

-- 
Upgrade from Ubuntu 12.04 LTS to 14.04 LTS Server. Can't bring up eth0. 
RTNETLINK answers: no such process [61709.025401] bnx2: can't load firmware 
file bnx2/bnx2-mips-06-6.2.3.fw
https://bugs.launchpad.net/bugs/1712575
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1720621] [NEW] Systemd does not start UDEV after remounting root

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Systemd under zesty starts udev before the root file system has been
made writeable.

This means that every insertion script (from /lib/udev/rules.d) that is
subsequently run, even long after system boot, is unable to change
anything in the world (for example can't create locks in /run/lock,
device files in /dev etc etc) can't even write to /tmp;

In my case scripts run at device insertion (including an attempt to log
data to /tmp) fail:

Oct  1 21:45:02 rata systemd-udevd[21055]: '/sbin/onerng.sh ttyACM0'(err) 
'/sbin/onerng.sh: 2: /sbin/onerng.sh: cannot create /tmp/yy: Read-only file 
system'
Oct  1 21:45:02 rata systemd-udevd[21055]: '/sbin/onerng.sh ttyACM0'(err) 
'warning: commands will be executed using /bin/sh'
Oct  1 21:45:02 rata systemd-udevd[21055]: '/sbin/onerng.sh ttyACM0'(err) 
'Cannot open lockfile /var/spool/cron/atjobs/.SEQ: Read-only file system'

This breaks add-on products already in the field that worked with
previous versions of Ubuntu

One can use "/etc/init.d/udev restart" to restart udev  and everything
works great after that - but devices that were discovered since udev was
originally started will already have had their startup scripts run and
fail - works great for devices that are only inserted after system boot,
fails for devices that were already present at boot time

The solution is to make sure that udev is started after the system
directories are remoutned RW

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

-- 
Systemd does not start UDEV after remounting root
https://bugs.launchpad.net/bugs/1720621
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1744928] [NEW] udev doesn't include a rule for security keys (including Yubico)

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

https://bugs.chromium.org/p/chromium/issues/detail?id=427966#c19

I can confirm that the following solves the problem on bionic:

sudo bash -c 'cat > /lib/udev/rules.d/50-securitykey.rules << EOF
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1050", MODE="0644", GROUP="plugdev"
EOF'
service udev restart

We might wish to flesh this out with a list of vendor IDs, but even just
Yubico (1050) will likely cover the vast majority of use cases due to
their market share.

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

-- 
udev doesn't include a rule for security keys (including Yubico)
https://bugs.launchpad.net/bugs/1744928
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1748698] [NEW] udevadm trigger kills X server

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Running Xubuntu 16.04.3, with udev version 229-4ubuntu21.1.

Every time I install the plexmediaserver package, no matter with what
mechanism, my X server crashes out completely, taking all my running
applications with it.

I traced it to a postinst script call to `udevadm trigger`.  Running
that one command manually will instantly kill the X server every time.

In looking at the logs, there's a segfault in radeon_drv.o that's
clearly the end of the X server.  syslog contains a set of messages
about Ethernet interfaces "changed", then a cluster of messages about
how various disk devices (/dev/sdX) appear twice with different sysfs
paths, and then suddenly xfce4 is logging about how the X server just
vanished.

A mess of UPower[d] messages show up in the log as well, but shutting
down upowerd before running another test yields no change, so it's not
responsible for this.

Whatever udev is doing to the X server is giving it a very bad day.
This makes it impractical for me to upgrade plex very frequently at all,
since my machine runs 24/7.  However, I'm having so many problems with
Plex right now that I'll be investigating other solutions anyway...

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

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

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


[Touch-packages] [Bug 1778833] [NEW] tty symlink incorrect after disconnect/reconnect, fixed by manual udevadm trigger

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I recently upgraded from Ubuntu 17.10 to 18.04 and encountered what appears to 
be a regression in udev. On 17.10 (and previous), the following udev rule to 
rename a USB serial device worked perfectly:
SUBSYSTEMS=="usb", ATTRS{product}=="IOTool", 
ATTRS{manufacturer}=="zplab.wustl.edu", ATTRS{serial}=="0x", 
SYMLINK+="ttyIOTool"

This would yield symlinks as expected:
> ls -l /dev/ttyIOTool
lrwxrwxrwx 1 root root 7 Jun 26 21:34 /dev/ttyIOTool -> ttyACM1

On 18.04, the same symlinks are made correctly at boot time. However, if
the device is unplugged and then re-plugged, the symlink instead goes to
/dev/bus/usb:

> ls -l /dev/ttyIOTool 
lrwxrwxrwx 1 root root 15 Jun 26 21:33 /dev/ttyIOTool -> bus/usb/003/013

This is a problem, because /dev/bus/usb devices can't be opened as
serial ports in the way that /dev/tty devices can.

However, manually triggering udev via `udevadm trigger` returns the
symlinks to the expected state. I am fairly certain that this behavior
represents a bug, because there shouldn't be any difference in behavior
between an auto-triggered event with a disconnect / reconnect, and one
manually triggered via udevadm trigger, right?

Version information: udevadm --version gives 237 on the 18.04 system
(with this broken behavior) and 234 on an identical 17.10 system with
the correct behavior. On a similar 16.10 system with udevadm version
231, such symlinks also work fine.

Note also that there are several reports of similar udev behavior around the 
web, which have left the users fairly perplexed; e.g.:
https://github.com/psi46/elComandante/issues/14
https://github.com/oskarpearson/mmeowlink/issues/52

Please let me know if there's anything further I can do to help debug
this problem. I can probably work around this by using /dev/serial/by-
id, but if anyone has other workarounds to try (different udev rules,
perhaps?), I would be grateful as well.

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

-- 
tty symlink incorrect after disconnect/reconnect, fixed by manual udevadm 
trigger
https://bugs.launchpad.net/bugs/1778833
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1778900] [NEW] udev mounts MTP devices in read-only mode.

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

In Ubuntu 18.04 udev mounts MTP devices (mine is Google Pixel C tablet)
in read-only mode by default, so that files cannot be copied over to the
device.

One has to manually create a udev rule to mount the device in read-write
mode. This is rather user-unfriendly.

Make udev mount MTP devices in read-write mode by default.

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


** Tags: mtp udev
-- 
udev mounts MTP devices in read-only mode.
https://bugs.launchpad.net/bugs/1778900
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1822451] [NEW] high cpu load

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Testing  Kubuntu 19.04 Disco Dingo
Same bug #1767968 on Dell Latitude E6400

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

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

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


[Touch-packages] [Bug 1767968] [NEW] systemd-udev cause high cpu load after upgrade to bionic

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After upgraded from xenial to bionic (kernel 4.15.0-20) systemd-udevd
runs with high cpu load in 2 instances (50%, 15%) on Dell Precision
M6500 when wlan switch will be enabled.

With xenial this problem did't happen and Dell bluetooth & wifi (b43)
are working.

After some research I found that /var/log/syslog gets filled with a lot
of messages (see log sample below).

If I modify /lib/udev/rules.d/97-hid2hci.rules (disable rule for
413c:8154, 413c:8158, 413c:8162), restart udev, turn wifi off/on by
hardware switch, the messages go away but the bluetooth adapter will be
not enabled anymore. It seems that udev is running in a loop.

My modification for the rule just was (just as proof):

--- before ---
ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01", 
ATTR{bInterfaceProtocol}=="02", \
  ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c", 
ATTRS{bmAttributes}=="e0", \
  RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"
--- end before ---

--- after ---
ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01", 
ATTR{bInterfaceProtocol}=="02", \
  ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c", 
ATTRS{bmAttributes}=="e0", \
  RUN+="/bin/sh", ENV{HID2HCI_SWITCH}="1"
--- end after ---

If you need some experiment or testing I can do (compiling software is
not a problem, I'm a developer).

lsusb:
Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 058: ID 413c:8162 Dell Computer Corp. Integrated Touchpad 
[Synaptics]
Bus 001 Device 057: ID 413c:8161 Dell Computer Corp. Integrated Keyboard
Bus 001 Device 056: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of 
BCM2046 Bluetooth)
Bus 001 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor
Bus 001 Device 003: ID 05ca:1815 Ricoh Co., Ltd 
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lspci:
Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 058: ID 413c:8162 Dell Computer Corp. Integrated Touchpad 
[Synaptics]
Bus 001 Device 057: ID 413c:8161 Dell Computer Corp. Integrated Keyboard
Bus 001 Device 056: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of 
BCM2046 Bluetooth)
Bus 001 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor
Bus 001 Device 003: ID 05ca:1815 Ricoh Co., Ltd 
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@precision:~# lspci
00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 
(rev 11)
00:08.0 System peripheral: Intel Corporation Core Processor System Management 
Registers (rev 11)
00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and 
Scratchpad Registers (rev 11)
00:08.2 System peripheral: Intel Corporation Core Processor System Control and 
Status Registers (rev 11)
00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous 
Registers (rev 11)
00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and 
Protocol Registers (rev 11)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 
Enhanced Host Controller (rev 05)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 1 (rev 05)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 2 (rev 05)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 3 (rev 05)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 4 (rev 05)
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 5 (rev 05)
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 6 (rev 05)
00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 7 (rev 05)
00:1c.7 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express 
Root Port 8 (rev 05)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 
Enhanced Host 

[Touch-packages] [Bug 1833443] [NEW] Calculator button does nothing (Calculator not launched)

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Troubleshoot steps followed:
https://wiki.ubuntu.com/Hotkeys/Troubleshooting.

Step-by-step Troubleshooting
1. Is latest I think
2. gnome-settings-daemon not running
3. No keypress event
4. Skip (see 3)
5. a. 

evtest output:
Event: time 1560959333.892425, -- SYN_REPORT 
Event: time 1560959337.916913, type 4 (EV_MSC), code 4 (MSC_SCAN), value a1
Event: time 1560959337.916913, type 1 (EV_KEY), code 140 (KEY_CALC), value 1
Event: time 1560959337.916913, -- SYN_REPORT 
Event: time 1560959338.121844, type 4 (EV_MSC), code 4 (MSC_SCAN), value a1
Event: time 1560959338.121844, type 1 (EV_KEY), code 140 (KEY_CALC), value 0
Event: time 1560959338.121844, -- SYN_REPORT 

   b. 140 (0x08c) not found in /usr/include/linux/input.h
7. N/A (see 4)

I can try provide info from https://wiki.ubuntu.com/DebuggingProcedures
if wanted.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: udev 237-3ubuntu10.22
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_4_15_0_51_55_generic_52
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 70-snap.warzone2100.rules 70-snap.core.rules 
70-snap.opendungeons.rules 56-hpmud.rules S99-2000S1.rules 
70-snap.minetest.rules 40-libsane.rules 70-snap.canonical-livepatch.rules 
70-snap.chromium.rules
Date: Wed Jun 19 17:58:19 2019
InstallationDate: Installed on 2019-05-14 (36 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=9b9d08ae-0424-4d09-87e0-5db4115b3a2b ro quiet splash vt.handoff=1
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/12/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SVD Ver. F.60
dmi.board.name: 1631
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 01.3F
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.60:bd03/12/2015:svnHewlett-Packard:pn:pvrA0001C02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3F:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.version: A0001C02
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug bionic
-- 
Calculator button does nothing (Calculator not launched)
https://bugs.launchpad.net/bugs/1833443
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1838992] [NEW] udev doesn't pick up volumes properly

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

[Only happens on Ubuntu, not other OS's, like Debian]

When we are attaching a volume to a running Ubuntu server (using
kvm/libvirt), most of the time the udev rules are not properly
triggered. In the end the volume will most of the time not be available
in `/dev/disk/by-id/virtio-`. Sometimes it works though
(10%/20%?).

The reason for this is that udev somehow doesn't pick it up when the
volume is attached. It looks like a timing issue. Just looking at
`/sys/devices/pci:00/:00:05.0/virtio2/block/vdb/serial` makes it
clear that it's there. However `udevadm info /dev/vdb` returns without
the `ID_SERIAL` key. Only a `udevadm trigger` leads to a correct entry
of `ID_SERIAL` and also fixes `/dev/disk/by-id`.

We are a small cloud provider (cloudscale.ch). We have tested this on
Ubuntu (16.04/18.04), Debian 9, CentOS, CoreOS. We haven't tested this
extensively, but it sure looks like it's only happening on Ubuntu. . We
never had any issues reported on other OS's about this.

I tried looking at the differences of Debian and Ubuntu udev packages,
but couldn't figure out what might be responsible for this behavior.

If someone needs an account for our control panel to reproduce this,
please contact me, I'm happy to give you the resources to debug this.

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

-- 
udev doesn't pick up volumes properly
https://bugs.launchpad.net/bugs/1838992
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1839156] [NEW] TCP/IP connection stuck when called from UDEV rule

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

It seems that in Eoan there is a lock/any other issue preventing
particular system calls to be executed by the triggered action handler.
I have an action executing wget when USB-serial adapter is plugged:

SUBSYSTEM=="tty", ACTION=="add", ATTRS{idVendor}=="1a86", 
ATTRS{idProduct}=="7523", MODE="0666", RUN+="/usr/bin/wget -v --method=POST 
http://127.0.0.1:4000/udev_trigger/add;
This action works perfectly in a prior versions - but in Eoan Ermine it hangs 
for ~30s and fails on a timeout. Analysis with strace shows that execution is 
stuck on connect() syscall - until it returns with ETIMEDOUT.

Same Wget command, being run from a command line, works perfectly.

The issue doesn't seem to be related to a particular IP
(localhost/remote) and/or the status of a listener process - execution
hangs also when listener is not running and port is free.

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

-- 
TCP/IP connection stuck when called from UDEV rule
https://bugs.launchpad.net/bugs/1839156
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1840772] [NEW] Script cannot access network when triggered by udev rule

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have a script that is triggered by a udev rule, and that needs to
connect to a remote host.

The example below works fine in 16.04, but fails in 18.04. It seems that
the process executing the script is somehow limited wrt. network access.
The script works fine when started from a shell prompt.

To reproduce:


- create /tmp/myscript:

#/bin/sh
wget -o /tmp/wget.log -O /tmp/index.html http://www.google.com


- create /etc/udev/rules.d/52-netaccess.rules

ACTION=="add", ATTRS{idVendor}=="cafe", MODE="0660", GROUP="root",
SUBSYSTEM=="usbmisc", RUN+="/tmp/myscript"


- Plugin a USB device with vendor ID 0xcafe, and check the wget output in 
/tmp/wget.log. 

On ubuntu 18.04 wget fails with this output:

--2019-08-19 14:49:43--  http://www.google.com/
Resolving www.google.com (www.google.com)... failed: Name or service not known.
wget: unable to resolve host address 'www.google.com'


If I use an IP address in the URL there is no resolve error, but then wget 
blocks in the socket connect() syscall (according to strace). At some point the 
script is killed.

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

-- 
Script cannot access network when triggered by udev rule
https://bugs.launchpad.net/bugs/1840772
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1846367] [NEW] udev /dev/null incorrect permissions after package auto upgrades

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I've been attempting to determine root cause of this problem for months.

Symptom is group/other permissions being dropped from all /dev/* files.

This only occurs on some machines, so some machine udev updates work,
some machines quietly fail.

Looks like the problem relates to...

1) APT /etc/apt/apt.conf.d/10periodic APT::Periodic::Update-Package-
Lists == 1, which triggers auto upgrades for critical packages.

2) This triggers the udev package run as an unattended/automatic
upgrade.

3) When udev package updates, /var/log/dpkg.log shows no errors.

4) /dev/* files have group/other permissions stripped.

5) LXD containers become unstable, as containers /dev points to machine
/dev.

Temp fix is change /etc/apt/apt.conf.d/10periodic - APT::Periodic
::Update-Package-Lists == 0 to disable all unattended upgrades.

Someone let me know where I can find APT/DPKG logs detailing exactly
what post install hook scripts run for udev, so I can look for errors.

Or if log verbosity has to be increased for this level of logging, let
me know how to increase verbosity, so next time udev updates, I can
provide logging detail sufficient to generate a fix for this problem.

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

-- 
udev /dev/null incorrect permissions after package auto upgrades
https://bugs.launchpad.net/bugs/1846367
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1873648] [NEW] After suspend, ttyusb0 is moved to ttyusb1

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have an old Core2 Duo running Ubuntu 20.04.
As it was sluggish with gnome, I installed the xfce environment (only xfce, not 
xubuntu)

Yesterday, I was using minicom then I suspended my laptop.
When I restarted minicom reported it could not open ttyusb0

After a few checks, I noticed that my usb to serial adapter was now
ttyusb1. I did not try to replicate.

This is quite annoying if you intend to rely a lot on suspend.

This behavior used to be in Windows in the past, but I believe they use
the UUID to always assign the same port to a USB device, as under
Windows, wherever I plug my US?B device, it always identifies as the
same "COM" port (used not to be the case before).

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


** Tags: bot-comment suspend-resume
-- 
After suspend, ttyusb0 is moved to ttyusb1
https://bugs.launchpad.net/bugs/1873648
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1874424] [NEW] USB external disks are not torn down correctly when they are unplugged

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

System information:

$ lsb_release -rd
Description:Ubuntu 19.10
Release:19.10
$ apt-cache policy udev
udev:
  Installed: 242-7ubuntu3.7
  Candidate: 242-7ubuntu3.7
  Version table:
 *** 242-7ubuntu3.7 500
500 http://gb.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages
100 /var/lib/dpkg/status
 242-7ubuntu3.6 500
500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages
 242-7ubuntu3 500
500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

I have a USB3 external SSD (VID/PID is /).  The whole device is
encrypted (ie /dev/sdc is an encrypted LUKS volume) and the encrypted
volume contains an LVM2 physical volume, a volume group called "vms" and
two logical volumes.

If I plug it into a booted system, everything works as expected.  I'm
prompted for the volume password, the volume is unlocked and LVM then
maps the logical volumes:

$ ls -l /dev/mapper
total 0
crw--- 1 root root 10, 236 Apr 23 11:49 control
lrwxrwxrwx 1 root root   7 Apr 23 11:51 
luks-5e586d40-5f49-4c33-8f73-22da39d2728a -> ../dm-3
lrwxrwxrwx 1 root root   7 Apr 23 11:49 nvme0n1p3_crypt -> ../dm-0
lrwxrwxrwx 1 root root   7 Apr 23 11:49 vgubuntu-root -> ../dm-1
lrwxrwxrwx 1 root root   7 Apr 23 11:49 vgubuntu-swap_1 -> ../dm-2
lrwxrwxrwx 1 root root   7 Apr 23 11:51 vms-veeabuild -> ../dm-4
lrwxrwxrwx 1 root root   7 Apr 23 11:51 vms-veea--mirror -> ../dm-5

(The volumes "vms-*" are the ones on the external disk).  I can mount
the volumes and use them.

If I'm careful to unmount the LVM volumes correctly and lock the disks,
everything works as expected:

$ vgchange -a n vms
  0 logical volume(s) in volume group "vms" now active
$ sudo udisksctl lock -b /dev/sdc
Locked /dev/sdc.

I then unplug the disk and repeat the process - everything works.  If,
for whatever reason, the device gets unplugged without the proper
cleanup, things get messy:

$ ls -l /dev/mapper
total 0
crw--- 1 root root 10, 236 Apr 23 11:49 control
lrwxrwxrwx 1 root root   7 Apr 23 12:04 
luks-5e586d40-5f49-4c33-8f73-22da39d2728a -> ../dm-3
lrwxrwxrwx 1 root root   7 Apr 23 11:49 nvme0n1p3_crypt -> ../dm-0
lrwxrwxrwx 1 root root   7 Apr 23 11:49 vgubuntu-root -> ../dm-1
lrwxrwxrwx 1 root root   7 Apr 23 11:49 vgubuntu-swap_1 -> ../dm-2
lrwxrwxrwx 1 root root   7 Apr 23 12:04 vms-veeabuild -> ../dm-4
lrwxrwxrwx 1 root root   7 Apr 23 12:04 vms-veea--mirror -> ../dm-5

Note that the "vms-*" volumes are still there.

$ ls -l /dev/dm-*
brw-rw 1 root disk 253, 0 Apr 23 11:49 /dev/dm-0
brw-rw 1 root disk 253, 1 Apr 23 11:49 /dev/dm-1
brw-rw 1 root disk 253, 2 Apr 23 11:49 /dev/dm-2
brw-rw 1 root disk 253, 3 Apr 23 12:04 /dev/dm-3
brw-rw 1 root disk 253, 4 Apr 23 12:04 /dev/dm-4
brw-rw 1 root disk 253, 5 Apr 23 12:04 /dev/dm-5

/dev/dm-* still exists.

However, sdc has been removed:

$ ls -l /dev/sdc
ls: cannot access '/dev/sdc': No such file or directory

If I then plug the disk in again, I'm again prompted for the passphrase
and the disk is mapped to /dev/sdd (not /dev/sdc like previous times).
If I try to mount one of the volumes:

$ sudo mount /dev/mapper/vms-veeabuild mnt2
mount: /home/tkcook/mnt2: can't read superblock on /dev/mapper/vms-veeabuild.

Something is not getting cleaned up when the disk is forcibly removed.
There doesn't seem to be any way to clean up from here; vgchange can't
deactivate the volume group and udisksctl can't lock the LUKS volume.
The only way I've found of using the disk again is to reboot (!)

I'm raising this on the udev package but that is a bit of a guess; I'm
assuming this is udev not processing the disconnection event correctly
(though since I can't find a way of cleaning this up, it's not clear
what it could do).

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

-- 
USB external disks are not torn down correctly when they are unplugged
https://bugs.launchpad.net/bugs/1874424
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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


[Touch-packages] [Bug 1890654] [NEW] udev service does not log

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

By default udev is supposed to log to /var/log.  In Ubuntu 20 it is not
logging.  Logging was then explicitly enabled by uncommenting this line
in /etc/udev/udev.conf:

"udev_log=info"

After running "systemctl restart udev" and plugging in a USB drive,
there is still no udev log in /var/log.  Yet /var/log/system shows that
a device was in fact attached.

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

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

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


[Touch-packages] [Bug 1890520] [NEW] catastrophic bug with deluser command -- destroys large number of system files

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I installed rygel and created a specific rygel user to run it with (as
directed by the docs). I then realized a specific user was not needed.
To reverse my steps, I ran deluser which proceeded to delete lots of
files that have nothing to do with the rygel user:

root@host:~# adduser --home /home/rygel --disabled-password --disabled-login 
--gecos 'Rygel media server' rygel
root@host:~# sudo su - rygel
rygel@host:$ systemctl start rygel
rygel@host:$ exit
root@host:~# deluser --remove-home --remove-all-files rygel
Looking for files to backup/remove ...
/usr/sbin/deluser: Cannot handle special file /etc/systemd/system/mdm.service
/usr/sbin/deluser: Cannot handle special file 
/etc/systemd/system/samba-ad-dc.service
/usr/sbin/deluser: Cannot handle special file 
/etc/systemd/system/cgmanager.service
/usr/sbin/deluser: Cannot handle special file 
/etc/systemd/system/cgproxy.service
/usr/sbin/deluser: Cannot handle special file /dev/vcsa7
/usr/sbin/deluser: Cannot handle special file /dev/vcsu7
/usr/sbin/deluser: Cannot handle special file /dev/vcs7
/usr/sbin/deluser: Cannot handle special file /dev/gpiochip0
/usr/sbin/deluser: Cannot handle special file /dev/dvdrw
/usr/sbin/deluser: Cannot handle special file /dev/dvd
/usr/sbin/deluser: Cannot handle special file /dev/cdrw
/usr/sbin/deluser: Cannot handle special file /dev/zfs
/usr/sbin/deluser: Cannot handle special file /dev/vhost-vsock
/usr/sbin/deluser: Cannot handle special file /dev/vhost-net
/usr/sbin/deluser: Cannot handle special file /dev/uhid
/usr/sbin/deluser: Cannot handle special file /dev/vhci
/usr/sbin/deluser: Cannot handle special file /dev/userio
/usr/sbin/deluser: Cannot handle special file /dev/nvram
/usr/sbin/deluser: Cannot handle special file /dev/btrfs-control
/usr/sbin/deluser: Cannot handle special file /dev/cuse
/usr/sbin/deluser: Cannot handle special file /dev/autofs
/usr/sbin/deluser: Cannot handle special file /dev/sde
/usr/sbin/deluser: Cannot handle special file /dev/sdd
/usr/sbin/deluser: Cannot handle special file /dev/sdc
/usr/sbin/deluser: Cannot handle special file /dev/sdb
/usr/sbin/deluser: Cannot handle special file /dev/sg5
/usr/sbin/deluser: Cannot handle special file /dev/sg4
/usr/sbin/deluser: Cannot handle special file /dev/sg3
/usr/sbin/deluser: Cannot handle special file /dev/sg2
/usr/sbin/deluser: Cannot handle special file /dev/vcsa6
/usr/sbin/deluser: Cannot handle special file /dev/vcsu6
/usr/sbin/deluser: Cannot handle special file /dev/vcs6
/usr/sbin/deluser: Cannot handle special file /dev/vcsa5
/usr/sbin/deluser: Cannot handle special file /dev/vcsu5
/usr/sbin/deluser: Cannot handle special file /dev/vcs5
/usr/sbin/deluser: Cannot handle special file /dev/vcsa4
/usr/sbin/deluser: Cannot handle special file /dev/vcsu4
/usr/sbin/deluser: Cannot handle special file /dev/vcs4
/usr/sbin/deluser: Cannot handle special file /dev/vcsa3
/usr/sbin/deluser: Cannot handle special file /dev/vcsu3
/usr/sbin/deluser: Cannot handle special file /dev/vcs3
/usr/sbin/deluser: Cannot handle special file /dev/vcsa2
/usr/sbin/deluser: Cannot handle special file /dev/vcsu2
/usr/sbin/deluser: Cannot handle special file /dev/vcs2
/usr/sbin/deluser: Cannot handle special file /dev/hidraw2
/usr/sbin/deluser: Cannot handle special file /dev/hidraw1
/usr/sbin/deluser: Cannot handle special file /dev/cdrom
/usr/sbin/deluser: Cannot handle special file /dev/hidraw0
/usr/sbin/deluser: Cannot handle special file /dev/fb0
/usr/sbin/deluser: Cannot handle special file /dev/i2c-5
/usr/sbin/deluser: Cannot handle special file /dev/i2c-4
/usr/sbin/deluser: Cannot handle special file /dev/i2c-3
/usr/sbin/deluser: Cannot handle special file /dev/i2c-2
/usr/sbin/deluser: Cannot handle special file /dev/i2c-1
/usr/sbin/deluser: Cannot handle special file /dev/i2c-0
/usr/sbin/deluser: Cannot handle special file /dev/rtc
/usr/sbin/deluser: Cannot handle special file /dev/stderr
/usr/sbin/deluser: Cannot handle special file /dev/stdout
/usr/sbin/deluser: Cannot handle special file /dev/stdin
/usr/sbin/deluser: Cannot handle special file /dev/sda6
/usr/sbin/deluser: Cannot handle special file /dev/sda5
/usr/sbin/deluser: Cannot handle special file /dev/sda3
/usr/sbin/deluser: Cannot handle special file /dev/sda2
/usr/sbin/deluser: Cannot handle special file /dev/sda1
/usr/sbin/deluser: Cannot handle special file /dev/sg1
/usr/sbin/deluser: Cannot handle special file /dev/sr0
/usr/sbin/deluser: Cannot handle special file /dev/sda
/usr/sbin/deluser: Cannot handle special file /dev/sg0
/usr/sbin/deluser: Cannot handle special file /dev/cpu_dma_latency
/usr/sbin/deluser: Cannot handle special file /dev/mcelog
/usr/sbin/deluser: Cannot handle special file /dev/rtc0
/usr/sbin/deluser: Cannot handle special file /dev/uinput
/usr/sbin/deluser: Cannot handle special file /dev/psaux
/usr/sbin/deluser: Cannot handle special file /dev/ppp
/usr/sbin/deluser: Cannot handle special file /dev/udmabuf
/usr/sbin/deluser: 

[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package

2020-08-06 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/388835

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in base-files source package in Xenial:
  In Progress
Status in ubuntu-meta source package in Xenial:
  In Progress
Status in base-files source package in Bionic:
  In Progress
Status in ubuntu-meta source package in Bionic:
  In Progress
Status in base-files source package in Focal:
  In Progress
Status in ubuntu-meta source package in Focal:
  In Progress
Status in base-files source package in Groovy:
  In Progress
Status in ubuntu-meta source package in Groovy:
  In Progress

Bug description:
  The motd-news script is largely useless for desktop users, as they
  rarely login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a NEW package 
(motd-news-config)
  - have ubuntu-server depend on motd-news-config (or recommends)
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends (or recommends) on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888575/+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 1890609] Re: improved resolved configuration

2020-08-06 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~xnox/ubuntu/+source/systemd/+git/systemd/+merge/388803

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

Title:
  improved resolved configuration

Status in systemd package in Ubuntu:
  New

Bug description:
  improved resolved configuration

  * isc-dhcp-client pushes DNS data to resolved via a hook it ships
  * ifupdown pushes DNS data to resolved via a hook it ships
  * resolvconf skips pulling DNS data that is pushed to resolved
  * systemd doesn't have enter hook anymore

  This way with or without resolvconf, resolved has all the information
  it needs and /etc/resolv.conf can be static, point at resolvconf
  managed file, or at resolved managed file as desired.

  isc-dhcp 4.4.1-2.1ubuntu7
  ifupdown 0.8.35ubuntu2
  resolvconf 1.82ubuntu1 
  systemd TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890609/+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 1888558] [NEW] VLC is using up to 2 GB of RAM just to play a regular 720px HD video

2020-08-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

On my computer running Ubuntu 20.04 and XFCE desktop, The VLC GUI player
is using an increasing amount of memory as time progressed. The video is
a typical H.264 movie (MP4 file format). I have let the application sit
for a few days, and here is the usage of RAM as the days went by:

Date   Time(EDT) VSIZE   RSS
2020-07-19 20:19:162848984455148
2020-07-20 13:09:063307736926156
2020-07-22 13:18:054487464   2059848

The process itself was started on:
Sat Jul 18 21:41:24 2020

I was playing the video only for about ~5 minutes when the program
started, then let the program sit idle for a few days. Today I found
that it consumed 2GB RSS as shown above!

I am reporting this issue to see if something in my system is messing up
VLC memory usage. In an older laptop, trying to play the same file (with
VLC version 2.0.3) has its memory consumption starting at just under
190M.


Wirawan

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: vlc 3.0.9.2-1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Wed Jul 22 13:19:21 2020
SourcePackage: vlc
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug focal
-- 
VLC is using up to 2 GB of RAM just to play a regular 720px HD video
https://bugs.launchpad.net/bugs/1888558
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mesa in Ubuntu.

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


[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

2020-08-05 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/bcache-tools/+git/bcache-tools/+merge/388774

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in bcache-tools source package in Focal:
  Fix Committed
Status in systemd source package in Focal:
  In Progress

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1876659] Re: Unhandled exception in run_hang()

2020-08-05 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu

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

Title:
  Unhandled exception in run_hang()

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  ## Description
  When we start apport-cli without PID, an unhandled exception in apport 
2.20.11 and earlier may allow an authenticated user to potentially enable a 
denial of service via local access.

  The following command may cause an application crash due to an
  unhandled exception.

  $ apport-cli --hanging

  *** Send problem report to the developers?

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

  What would you like to do? Your options are:
S: Send report (24.0 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): K
  Problem report file: /tmp/apport.apport.uc0_znhj.apport
  Traceback (most recent call last):
File "/usr/bin/apport-cli", line 387, in 
  if not app.run_argv():
File "/usr/lib/python3/dist-packages/apport/ui.py", line 690, in run_argv
  self.run_hang(self.options.pid)
File "/usr/lib/python3/dist-packages/apport/ui.py", line 410, in run_hang
  os.kill(int(pid), signal.SIGKILL)
  TypeError: int() argument must be a string, a bytes-like object or a number, 
not 'NoneType'

  
  Above command generates the following application crash file in /var/crash/ 
directory.

  ProblemType: Crash
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 19:09:41 2020
  ExecutablePath: /usr/bin/apport-cli
  ExecutableTimestamp: 1585099033
  InterpreterPath: /usr/bin/python3.6
  ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli --hanging
  ProcCwd: /home/user/apport/bin
  ProcEnviron:
   ...
  ProcMaps:
   ...
  ProcStatus:
   ...
  PythonArgs: ['/usr/bin/apport-cli', '--hanging']
  Traceback:
   Traceback (most recent call last):
 File "/usr/bin/apport-cli", line 387, in 
   if not app.run_argv():
 File "/usr/lib/python3/dist-packages/apport/ui.py", line 690, in run_argv
   self.run_hang(self.options.pid)
 File "/usr/lib/python3/dist-packages/apport/ui.py", line 410, in run_hang
   os.kill(int(pid), signal.SIGKILL)
   TypeError: int() argument must be a string, a bytes-like object or a number, 
not 'NoneType'
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _LogindSession: 6

  
  Many thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1876659/+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 1877023] Re: Unhandled exception in check_ignored()

2020-08-05 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu

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

Title:
  Unhandled exception in check_ignored()

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  I have found a security issue on apport 2.20.11 and earlier.

  ## Vulnerability 
  apport 2.20.11 and earlier have an unhandled exception vulnerability during 
parsing apport-ignore.xml.
  An attacker can cause a denial of service (i.e., application crash) via a 
crafted apport-ignore.xml file.

  ## Description
  Reports can be suppressed by blacklisting in apport-ignore.xml.

  This is an example of apport-ignore.xml

  
  
    
    
    
  

  Unfortunately, it may cause an unhandled exception when 'mtime'
  attribute is specified as a string value, not a number like this.

  
  
    
  

  It may disrupt apport service and allow an attacker to potentially
  enable a denial of service via local access.

  The flaw lies in improper exception handling of 'mtime' attribute in
  apport-ignore.xml (see
  
https://git.launchpad.net/ubuntu/+source/apport/tree/apport/report.py?h=applied/ubuntu/devel#n1104).

  ## Log
  Here is /var/log/apport.log when the above exception occurs.

  ERROR: apport (pid 25904) Tue May  5 18:38:21 2020: Unhandled exception:
  Traceback (most recent call last):
    File "/usr/share/apport/apport", line 629, in 
  if info.check_ignored():
    File "/usr/lib/python3/dist-packages/apport/report.py", line 1082, in 
check_ignored
  if float(ignore.getAttribute('mtime')) >= cur_mtime:
  ValueError: could not convert string to float: 'string'

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1877023/+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 1857769] Re: program linked to protobuf crashes before main

2020-08-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  program linked to protobuf crashes before main

Status in protobuf package in Ubuntu:
  Confirmed

Bug description:
  This simple test crashes on a system that I installed Ubuntu Server 20.04 
daily build on yesterday:
  echo "syntax = \"proto2\";" >| test.pbc
  echo "message TestMsg" >> test.pbc
  echo "{" >> test.pbc
  echo "  required double f1 = 1;" >> test.pbc
  echo "}" >> test.pbc

  echo "int main() {return 0;}" >| test.cc

  protoc --cpp_out=. ./test.pbc
  g++ -c -o test.pbc.pb.o test.pbc.pb.cc
  g++ -c -o test.o test.cc
  g++ -o test test.o test.pbc.pb.o -lprotobuf
  ./test
  terminate called after throwing an instance of 'std::system_error'
    what():  Unknown error -1
  Aborted (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: protobuf-compiler 3.6.1.3-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Sat Dec 28 19:10:20 2019
  InstallationDate: Installed on 2019-12-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 
(20191227)
  SourcePackage: protobuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/1857769/+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 1876513] Re: .bashrc color_prompt check only works for xterm-color, not xterm-256color

2020-08-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  .bashrc color_prompt check only works for xterm-color, not xterm-
  256color

Status in base-files package in Ubuntu:
  Confirmed

Bug description:
  The `share/dot.bashrc` file checks like this whether to enable
  `color_prompt`:

  case "$TERM" in
  xterm-color) color_prompt=yes;;
  esac

  Nowaways, most terminals support 256 colors (instead of 8 like xterm-
  color). Their $TERM will usually be something like `xterm-256color`.

  Accordingly, this check was modified in the `skel`-package
  `/etc/skel/.bashrc` like this:

  case "$TERM" in
  xterm-color|*-256color) color_prompt=yes;;
  esac

  
  I would suggest the same modification be done in the base-files .bashrc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1876513/+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 1890436] [NEW] Screen corruption with multi monitor setup

2020-08-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:


Hello, last week I was digging in the BIOS of my PC at work since I tried to 
see if there is a way to update the dbx for secure boot. Since there was no 
option to perform this task, I modified some settings. In detail, I disabled 
CSM in BIOS and that's when hell broke loose!

To get an idea about the hardware, the Lenovo machine isn't running the
latest BIOS as its updater is broken and won't update it within win or
its ISO image. It uses the previous version released by its
manufacturer.

The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled 
the DP monitor is lit first and then the VGA one prior OS loading. When CSM is 
disabled it goes the other way around. The VGA monitor is lit and the DP one 
opens up during OS load. With CSM disabled the VGA monitor is the primary one 
and it is corrupted as you can see on the pictures I have attached.
Interestingly printing screens within Ubuntu does not capture the corruption 
problem I am getting as you can see on the pictures I have also attached. 
Neither X log contains anything useful. The issue is repeatable on every boot.

As I have seen on other bug reports, I have enabled DRM debug, captured
the dmesg using a huge buffer to get it and have uploaded it as well. I
hope that it will help you track this issue down and fix it soon. Since
I will be away some days for vacation, I will have physical access to it
till this Friday and will get back to work at the 24th of August. In the
mean time, I hope that someone will pinpoint the root cause of it and
prepare a patch.

Since this machine is running w10 2004, it should be noted that in win I
do not get any corruption at all either in CSM mode or UEFI mode.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CasperVersion: 1.445
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug  5 11:30:51 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[17aa:3083]
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 3209C54
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed 
maybe-ubiquity quiet splash ---
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/17/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 9SKT9BAUS
dmi.board.name: MAHOBAY
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: 3209C54
dmi.product.sku: LENOVO_MT_3209
dmi.product.version: ThinkCentre M92p
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption focal third-party-packages ubuntu
-- 
Screen corruption with multi monitor setup
https://bugs.launchpad.net/bugs/1890436
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 1881972] Re: systemd-networkd crashes with invalid pointer

2020-08-05 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 237-3ubuntu10.42

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

  [ Dan Streetman ]
  * 
d/p/lp1860926/0001-networkd-Allow-to-retain-configs-even-if-carrier-is-.patch,

d/p/lp1860926/0002-network-Change-IgnoreCarrierLoss-default-to-value-of.patch,

d/p/lp1860926/0003-network-always-drop-configs-when-corresponding-netwo.patch:
- Add IgnoreCarrierLoss and default to value of ConfigureWithoutCarrier
  (LP: #1860926)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9a12a31a62f1a50cd3a67a164ee34c546809815e

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3cc3870fde47982a4dda53f820e18065e5488e7e
  * d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
  (LP: #1876018)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ba305d7ad00e80bc1a03f93e6986eef7cbbb18fc
  * d/p/lp1881972-network-strdup-iif-and-oif-when-creating-RoutingPoli.patch:
- Avoid double-free by strdup'ing iif/oif strings for new policy rules
  (LP: #1881972)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=874056f0d429aaa2cc872c3b35ec33cd3b740483
  * d/p/lp1886197-seccomp-more-comprehensive-protection-against-libsec.patch
- Fix FTBFS on arm64 due to libseccomp changes (LP: #1886197)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c284a72ca2e3d87bfe1c20afb2fcfb379cda544f
  * 
d/p/lp1832754/0001-umount-Try-unmounting-even-if-remounting-read-only-f.patch,

d/p/lp1832754/0002-umount-Don-t-bother-remounting-api-and-ro-filesystem.patch:
- Try unmounting even if ro-remount fails, and don't bother remounting 
api/ro fs
  (LP: #1832754)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a518baa673aeaaf42000a3a01b7e03347652b216

  [ Alex Murray, Jamie Strandboge ]
  * d/p/lp1886115-pid1-fix-free-of-uninitialized-pointer-in-unit_fail_.patch:
- Fix free of uninitialized pointer (LP: #1886115)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=491c76fd0f2fba0007a9b54d63a50f21add643c8

 -- Dan Streetman   Wed, 08 Jul 2020 14:59:14
-0400

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

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

Title:
  systemd-networkd crashes with invalid pointer

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

Bug description:
  [impact]

  systemd-networkd double-free causes crash under some circumstances,
  such as adding/removing ip rules

  [test case]

  Use networkd-dispatcher events to add and remove IP rules. The example
  scripts below are contrived (and by themselves likely to break access
  to a machine) but would be adequate to trigger the bug. Put scripts
  like these in place, reboot or run "netplan apply", and then leave the
  machine running for a few DHCP renewal cycles.

  === /etc/networkd-dispatcher/configured.d/test.sh ===
  #!/bin/bash

  /sbin/ip rule add iif lo lookup 99
  /sbin/ip rule add to 10.0.0.0/8 iif lo lookup main
  === END ===
  === /etc/networkd-dispatcher/configuring.d/test.sh ===
  #!/bin/bash

  # Tear down existing ip rules so they aren't duplicated
  OLDIFS="${IFS}"
  IFS="
  "
  for rule in `ip rule show|grep "iif lo" | cut -d: -f2-`; do
IFS="${OLDIFS}"
ip rule delete ${rule}
  done
  IFS="${OLDIFS}"
  === END ===

  [regression potential]

  this strdup's strings during addition of routing policy rules, so any
  regression would likely occur when adding/modifying/removing ip rules,
  possibly including networkd segfault or failure to add/remove/modify
  ip rules.

  [scope]

  this is needed for bionic.

  this is fixed by upstream commit
  eeab051b28ba6e1b4a56d369d4c6bf7cfa71947c which is included starting in
  v240, so this is already included in Focal and later.

  I did not research what original commit introduced the problem, but
  the reporter indicates this did not happen for Xenial so it's unlikely
  this is a problem in Xenial or earlier.

  [original description]

  This is a serious regression with systemd-networkd that I ran in to
  while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm-
  ssd/ubuntu-bionic-18.04-amd64-server-20200131 with
  systemd-237-3ubuntu10.33 does NOT have the problem, but the next most
  recent AWS AMI ubuntu/images/hvm-ssd/ubuntu-
  bionic-18.04-amd64-server-20200311 with systemd-including
  237-3ubuntu10.39 does.

  Also, a system booted from the (good) 20200131 AMI starts showing the
  problem after updating only systemd (to 237-3ubuntu10.41) and its
  direct dependencies (e.g. 'apt-get install systemd'). So I'm fairly
  confident that a change to the 

[Touch-packages] [Bug 1876018] Re: 40-vm-hotadd.rules attempts to set non-existent sysfs parameters

2020-08-05 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 237-3ubuntu10.42

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

  [ Dan Streetman ]
  * 
d/p/lp1860926/0001-networkd-Allow-to-retain-configs-even-if-carrier-is-.patch,

d/p/lp1860926/0002-network-Change-IgnoreCarrierLoss-default-to-value-of.patch,

d/p/lp1860926/0003-network-always-drop-configs-when-corresponding-netwo.patch:
- Add IgnoreCarrierLoss and default to value of ConfigureWithoutCarrier
  (LP: #1860926)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9a12a31a62f1a50cd3a67a164ee34c546809815e

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3cc3870fde47982a4dda53f820e18065e5488e7e
  * d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
  (LP: #1876018)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ba305d7ad00e80bc1a03f93e6986eef7cbbb18fc
  * d/p/lp1881972-network-strdup-iif-and-oif-when-creating-RoutingPoli.patch:
- Avoid double-free by strdup'ing iif/oif strings for new policy rules
  (LP: #1881972)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=874056f0d429aaa2cc872c3b35ec33cd3b740483
  * d/p/lp1886197-seccomp-more-comprehensive-protection-against-libsec.patch
- Fix FTBFS on arm64 due to libseccomp changes (LP: #1886197)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c284a72ca2e3d87bfe1c20afb2fcfb379cda544f
  * 
d/p/lp1832754/0001-umount-Try-unmounting-even-if-remounting-read-only-f.patch,

d/p/lp1832754/0002-umount-Don-t-bother-remounting-api-and-ro-filesystem.patch:
- Try unmounting even if ro-remount fails, and don't bother remounting 
api/ro fs
  (LP: #1832754)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a518baa673aeaaf42000a3a01b7e03347652b216

  [ Alex Murray, Jamie Strandboge ]
  * d/p/lp1886115-pid1-fix-free-of-uninitialized-pointer-in-unit_fail_.patch:
- Fix free of uninitialized pointer (LP: #1886115)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=491c76fd0f2fba0007a9b54d63a50f21add643c8

 -- Dan Streetman   Wed, 08 Jul 2020 14:59:14
-0400

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

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

Title:
  40-vm-hotadd.rules attempts to set non-existent sysfs parameters

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

Bug description:
  [impact]

  40-vm-hotadd.rules unconditionally tries onlining memory, which
  results in logged error messages if the memory is already online

  [test case]

  since this rules file restricts operation to only hyper-v or xen
  guests, boot a hyper-v or xen vm guest, and check for logged error
  msgs like:

  Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
  /usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
  ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
  argument

  alternately, to test on a vm guest other than hyper-v or xen,
  comment/remove the 'GOTO="vm_hotadd_end"' line from the rules file and
  reboot.

  [regression potential]

  as this adds a check before attempting to online memory for hyper-v
  and xen vm guests, any regression would likely involve failure to
  correctly online all memory on those guest platforms.

  [scope]

  this rule has been around for a long time, so is needed for x/b/f/g.

  [original description]

  In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
  tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes
  resulting in warnings such as:

  Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
  /usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
  ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
  argument

  Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
  removed, or something else. This behavior is present on systems
  upgraded from 18.04 (via d-r-u) as well as new focal systems, upon
  first reboot of the VM.

  udev: 245.4-4ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876018/+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 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

2020-08-05 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 237-3ubuntu10.42

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

  [ Dan Streetman ]
  * 
d/p/lp1860926/0001-networkd-Allow-to-retain-configs-even-if-carrier-is-.patch,

d/p/lp1860926/0002-network-Change-IgnoreCarrierLoss-default-to-value-of.patch,

d/p/lp1860926/0003-network-always-drop-configs-when-corresponding-netwo.patch:
- Add IgnoreCarrierLoss and default to value of ConfigureWithoutCarrier
  (LP: #1860926)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9a12a31a62f1a50cd3a67a164ee34c546809815e

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3cc3870fde47982a4dda53f820e18065e5488e7e
  * d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
  (LP: #1876018)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ba305d7ad00e80bc1a03f93e6986eef7cbbb18fc
  * d/p/lp1881972-network-strdup-iif-and-oif-when-creating-RoutingPoli.patch:
- Avoid double-free by strdup'ing iif/oif strings for new policy rules
  (LP: #1881972)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=874056f0d429aaa2cc872c3b35ec33cd3b740483
  * d/p/lp1886197-seccomp-more-comprehensive-protection-against-libsec.patch
- Fix FTBFS on arm64 due to libseccomp changes (LP: #1886197)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c284a72ca2e3d87bfe1c20afb2fcfb379cda544f
  * 
d/p/lp1832754/0001-umount-Try-unmounting-even-if-remounting-read-only-f.patch,

d/p/lp1832754/0002-umount-Don-t-bother-remounting-api-and-ro-filesystem.patch:
- Try unmounting even if ro-remount fails, and don't bother remounting 
api/ro fs
  (LP: #1832754)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a518baa673aeaaf42000a3a01b7e03347652b216

  [ Alex Murray, Jamie Strandboge ]
  * d/p/lp1886115-pid1-fix-free-of-uninitialized-pointer-in-unit_fail_.patch:
- Fix free of uninitialized pointer (LP: #1886115)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=491c76fd0f2fba0007a9b54d63a50f21add643c8

 -- Dan Streetman   Wed, 08 Jul 2020 14:59:14
-0400

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

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

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [test case, pre-focal]

  same netplan as above.  Reboot, and the bridge should have its address
  and route:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
     valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static linkdown
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown

  add and remove carrier, by adding and removing a slave interface:

  ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up
  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
     valid_lft forever preferred_lft forever
  inet6 fe80::5411:daff:fe23:bb93/64 scope link
     

[Touch-packages] [Bug 1832754] Re: "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs.

2020-08-05 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 237-3ubuntu10.42

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

  [ Dan Streetman ]
  * 
d/p/lp1860926/0001-networkd-Allow-to-retain-configs-even-if-carrier-is-.patch,

d/p/lp1860926/0002-network-Change-IgnoreCarrierLoss-default-to-value-of.patch,

d/p/lp1860926/0003-network-always-drop-configs-when-corresponding-netwo.patch:
- Add IgnoreCarrierLoss and default to value of ConfigureWithoutCarrier
  (LP: #1860926)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9a12a31a62f1a50cd3a67a164ee34c546809815e

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3cc3870fde47982a4dda53f820e18065e5488e7e
  * d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
  (LP: #1876018)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ba305d7ad00e80bc1a03f93e6986eef7cbbb18fc
  * d/p/lp1881972-network-strdup-iif-and-oif-when-creating-RoutingPoli.patch:
- Avoid double-free by strdup'ing iif/oif strings for new policy rules
  (LP: #1881972)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=874056f0d429aaa2cc872c3b35ec33cd3b740483
  * d/p/lp1886197-seccomp-more-comprehensive-protection-against-libsec.patch
- Fix FTBFS on arm64 due to libseccomp changes (LP: #1886197)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c284a72ca2e3d87bfe1c20afb2fcfb379cda544f
  * 
d/p/lp1832754/0001-umount-Try-unmounting-even-if-remounting-read-only-f.patch,

d/p/lp1832754/0002-umount-Don-t-bother-remounting-api-and-ro-filesystem.patch:
- Try unmounting even if ro-remount fails, and don't bother remounting 
api/ro fs
  (LP: #1832754)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a518baa673aeaaf42000a3a01b7e03347652b216

  [ Alex Murray, Jamie Strandboge ]
  * d/p/lp1886115-pid1-fix-free-of-uninitialized-pointer-in-unit_fail_.patch:
- Fix free of uninitialized pointer (LP: #1886115)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=491c76fd0f2fba0007a9b54d63a50f21add643c8

 -- Dan Streetman   Wed, 08 Jul 2020 14:59:14
-0400

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

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

Title:
  "shutdown[1]: Failed to wait for process: Protocol error" at shutdown
  or reboot and hangs.

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

Bug description:
  [impact]

  shutdown sometimes fails to unmount some fs, which causes shutdown
  hang

  [test case]

  it's unclear what the specific configuration is to be able to
  reproduce this, but there are some examples in the upstream bug

  [regression potential]

  as this adjusts shutdown umounting, any regression would likely
  involve either failure to unmount some filesystems on shutdown and/or
  failure to shutdown the system.

  [scope]

  this is needed for b.

  this is fixed upstream by PR 8429 which is included starting in v239,
  so this is fixed already in Focal and later.

  this was caused by upstream commit d5641e0d7e8 which was added in
  v236, so this bug is not present in x.

  [original description]

  I am using Xubuntu 18.04 64 bit and got "shutdown[1]: Failed to wait
  for process: Protocol error" at shutdown or reboot and hangs.

  systemd: 237-3ubuntu10.22

  It's this issue:
  https://github.com/systemd/systemd/issues/8155

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1832754/+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 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

2020-08-05 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 237-3ubuntu10.42

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

  [ Dan Streetman ]
  * 
d/p/lp1860926/0001-networkd-Allow-to-retain-configs-even-if-carrier-is-.patch,

d/p/lp1860926/0002-network-Change-IgnoreCarrierLoss-default-to-value-of.patch,

d/p/lp1860926/0003-network-always-drop-configs-when-corresponding-netwo.patch:
- Add IgnoreCarrierLoss and default to value of ConfigureWithoutCarrier
  (LP: #1860926)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9a12a31a62f1a50cd3a67a164ee34c546809815e

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3cc3870fde47982a4dda53f820e18065e5488e7e
  * d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
  (LP: #1876018)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ba305d7ad00e80bc1a03f93e6986eef7cbbb18fc
  * d/p/lp1881972-network-strdup-iif-and-oif-when-creating-RoutingPoli.patch:
- Avoid double-free by strdup'ing iif/oif strings for new policy rules
  (LP: #1881972)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=874056f0d429aaa2cc872c3b35ec33cd3b740483
  * d/p/lp1886197-seccomp-more-comprehensive-protection-against-libsec.patch
- Fix FTBFS on arm64 due to libseccomp changes (LP: #1886197)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c284a72ca2e3d87bfe1c20afb2fcfb379cda544f
  * 
d/p/lp1832754/0001-umount-Try-unmounting-even-if-remounting-read-only-f.patch,

d/p/lp1832754/0002-umount-Don-t-bother-remounting-api-and-ro-filesystem.patch:
- Try unmounting even if ro-remount fails, and don't bother remounting 
api/ro fs
  (LP: #1832754)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a518baa673aeaaf42000a3a01b7e03347652b216

  [ Alex Murray, Jamie Strandboge ]
  * d/p/lp1886115-pid1-fix-free-of-uninitialized-pointer-in-unit_fail_.patch:
- Fix free of uninitialized pointer (LP: #1886115)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=491c76fd0f2fba0007a9b54d63a50f21add643c8

 -- Dan Streetman   Wed, 08 Jul 2020 14:59:14
-0400

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

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Fix Released
Status in libseccomp source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [impact]

  systemd sometimes crashes on boot due to free of uninitalized var

  [test case]

  a specific system setup is required, see original description

  [regression potential]

  any regression would likely involve further crashes on boot.

  [scope]

  this is needed in b.

  this is fixed upstream by commit
  58d9d89b4b41189bdcea86c2ad5cf708b7d54aca which is included starting in
  v240, so this is included already in f and later.

  this is caused by commit 25cd49647c8 which is included starting in
  v237, so this bug does not exist in x.

  [original description]

  After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

    Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758,
  init=, fini=, rtld_fini=,
  

[Touch-packages] [Bug 1886197] Re: FTBFS in b due to libseccomp change

2020-08-05 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 237-3ubuntu10.42

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

  [ Dan Streetman ]
  * 
d/p/lp1860926/0001-networkd-Allow-to-retain-configs-even-if-carrier-is-.patch,

d/p/lp1860926/0002-network-Change-IgnoreCarrierLoss-default-to-value-of.patch,

d/p/lp1860926/0003-network-always-drop-configs-when-corresponding-netwo.patch:
- Add IgnoreCarrierLoss and default to value of ConfigureWithoutCarrier
  (LP: #1860926)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9a12a31a62f1a50cd3a67a164ee34c546809815e

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3cc3870fde47982a4dda53f820e18065e5488e7e
  * d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
  (LP: #1876018)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ba305d7ad00e80bc1a03f93e6986eef7cbbb18fc
  * d/p/lp1881972-network-strdup-iif-and-oif-when-creating-RoutingPoli.patch:
- Avoid double-free by strdup'ing iif/oif strings for new policy rules
  (LP: #1881972)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=874056f0d429aaa2cc872c3b35ec33cd3b740483
  * d/p/lp1886197-seccomp-more-comprehensive-protection-against-libsec.patch
- Fix FTBFS on arm64 due to libseccomp changes (LP: #1886197)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c284a72ca2e3d87bfe1c20afb2fcfb379cda544f
  * 
d/p/lp1832754/0001-umount-Try-unmounting-even-if-remounting-read-only-f.patch,

d/p/lp1832754/0002-umount-Don-t-bother-remounting-api-and-ro-filesystem.patch:
- Try unmounting even if ro-remount fails, and don't bother remounting 
api/ro fs
  (LP: #1832754)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a518baa673aeaaf42000a3a01b7e03347652b216

  [ Alex Murray, Jamie Strandboge ]
  * d/p/lp1886115-pid1-fix-free-of-uninitialized-pointer-in-unit_fail_.patch:
- Fix free of uninitialized pointer (LP: #1886115)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=491c76fd0f2fba0007a9b54d63a50f21add643c8

 -- Dan Streetman   Wed, 08 Jul 2020 14:59:14
-0400

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

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

Title:
  FTBFS in b due to libseccomp change

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

Bug description:
  [impact]

  systemd FTBFS in b because __NR__sysctl was force-defined by
  libseccomp in 2.4.1-0ubuntu0.18.04.2, but that force-defining was
  (correctly) reverted in the latest version 2.4.3-1ubuntu3.18.04.2.

  On arm64, __NR__sysctl is not defined, so the build now fails, e.g.:
  
https://launchpadlibrarian.net/486997294/buildlog_ubuntu-bionic-arm64.systemd_237-3ubuntu10.42~202007031245~ubuntu18.04.1_BUILDING.txt.gz

  ../src/test/test-seccomp.c: In function ‘test_protect_sysctl’:
  ../src/test/test-seccomp.c:251:5: error: "__NR__sysctl" is not defined, 
evaluates to 0 [-Werror=undef]
   #if __NR__sysctl > 0
   ^~~~

  [test case]

  build systemd on bionic with latest packages (i.e. with latest
  libseccomp2 package)

  [regression potential]

  this adds a defined() check before comparing the __NR__sysctl value,
  so any regression would be limited to the specific function
  test_protect_sysctl() which is part of the test framework, thus
  leading to a failed build or incorrectly passed/failed test.

  [scope]

  this is needed only in Bionic.

  This is fixed upstream by commit
  4df8fe8415eaf4abd5b93c3447452547c6ea9e5f which is included in v244 and
  later, so this is fixed already for Focal and later.

  Xenial does not include the __NR__sysctl check so does not need this
  patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1886197/+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 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)

2020-08-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu
   Status: New => Confirmed

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

Title:
  Images are washed out or colors are skewed in some apps (particularly
  Image Viewer and Chrome)

Status in GNOME Shell:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in colord package in Ubuntu:
  Confirmed
Status in eog package in Ubuntu:
  Confirmed
Status in inkscape package in Ubuntu:
  Confirmed

Bug description:
  Images are washed out or colors are skewed in some apps, notably
  Chrome/Chromium and Image Viewer (eog).

  Workaround:

  Settings > Devices > Colour >
  and disable or remove your monitor's colour profile

  Originally reported in
  https://bugzilla.gnome.org/show_bug.cgi?id=675645

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/938751/+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 1881976] Re: apport-gtk and apport-kde install xiterm+thai as dependency (x-terminal-emulator)

2020-08-04 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu

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

Title:
  apport-gtk and apport-kde install xiterm+thai as dependency (x
  -terminal-emulator)

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * When installing apport-gtk (or apport-kde) on a non-GUI installation 
(cloud image, server image) as a dependency providing x-terminal-emulator 
xiterm+thai package is pulled in, which is not appropriate for most locales.
  My understanding is it was selected due to lowest number of unsatisfied 
dependencies.

  [Test Case]

   * lxc launch ubuntu:20.04 test
   * lxc shell test
   * apt update
   * apt install apport-gtk
   * Examine the packages listed to be installed: xiterm+thai is one of them.

  [Regression Potential]

   * In dedicated archive mirrors with limited number of packages
  changing that may cause errors due to packages missing in the archive.
  However, that's unlikely.

  [Other Info]

   * It is not affecting bionic, since x-terminal-emulator is listed as 
'Suggests' not 'Depends' there.
   * Original bug description:

  Vanilla install of Ubuntu 20.04 set to an Australian locale includes the 
"Thai X Terminal" package.
  This package should not be included.

  I noticed that it is also reported against Xubuntu and Lubuntu:
  https://bugs.launchpad.net/lubuntu-next/+bug/1747341

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1881976/+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 1881982] Re: DoS vulnerability: cause resource exhaustion

2020-08-04 Thread Launchpad Bug Tracker
This bug was fixed in the package whoopsie - 0.2.62ubuntu0.5

---
whoopsie (0.2.62ubuntu0.5) bionic-security; urgency=medium

  * SECURITY UPDATE: integer overflow in bson parsing (LP: #1872560)
- lib/bson/*: updated to latest upstream release.
- CVE-2020-12135
  * SECURITY UPDATE: resource exhaustion via memory leak (LP: #1881982)
- src/whoopsie.c, src/tests/test_parse_report.c: properly handle
  GHashTable.
- CVE-2020-11937
  * SECURITY UPDATE: DoS via large data length (LP: #1882180)
- src/whoopsie.c, src/whoopsie.h, src/tests/test_parse_report.c: limit
  the size of a report file.
- CVE-2020-15570

 -- Marc Deslauriers   Fri, 24 Jul 2020
08:55:26 -0400

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

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

Title:
  DoS vulnerability: cause resource exhaustion

Status in whoopsie package in Ubuntu:
  Confirmed
Status in whoopsie source package in Xenial:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released
Status in whoopsie source package in Eoan:
  Confirmed
Status in whoopsie source package in Focal:
  Fix Released
Status in whoopsie source package in Groovy:
  Confirmed

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  # Vulnerability description
  The parse_report() function in whoopsie.c allows attackers to cause a denial 
of service (memory leak) via a crafted file. 
  Exploitation of this issue causes excessive memory consumption which results 
in the Linux kernel triggering OOM killer on arbitrary process.
  This results in the process being terminated by the OOM killer.

  
  # Details 
  We have found a memory leak vulnerability during the parsing the crash file, 
when a collision occurs on GHashTable through g_hash_table_insert().
  According to [1], if the key already exists in the GHashTable, its current 
value is replaced with the new value.
  If 'key_destory_func' and 'value_destroy_func' are supplied when creating the 
table, the old value and the passed key are freed using that function.
  Unfortunately, whoopsie does not handle the old value and the passed key when 
collision happens.
  If a crash file contains same repetitive key-value pairs, it leads to memory 
leak as much as the amount of repetition and results in denial-of-service.

  [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g
  -hash-table-insert

  
  # PoC (*Please check the below PoC: whoopsie_killer.py)
  1) Generates a certain malformed crash file that contains same repetitive 
key-value pairs.
  2) Trigger the whoopsie to read the generated crash file.
  3) After then, the whoopsie process has been killed.

  
  # Mitigation (*Please check the below patch: g_hash_table_memory_leak.patch)
  We should use g_hash_table_new_full() with ‘key_destroy_func’ and 
‘value_destroy_func’ functions instead of g_hash_table_new().
  Otherwise, before g_hash_table_insert(), we should check the collision via 
g_hash_table_lookup_extended() and obtain pointer to the old value and remove 
it.

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1881982/+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 1889416] Re: pulseaudio.service: Start request repeated too quickly.

2020-08-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  pulseaudio.service: Start request repeated too quickly.

Status in fscrypt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  PA doesn't start on it's own after the latest update.

  ```
  nafallo@wendigo:~$ systemctl --user status pulseaudio
  ● pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 
11min ago
  TriggeredBy: ● pulseaudio.socket
  Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no 
--log-target=journal (code=exited, status=1/FAILURE)
 Main PID: 2774 (code=exited, status=1/FAILURE)

  Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart 
job, restart counter is at 5.
  Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service.
  Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request 
repeated too quickly.
  Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 
'exit-code'.
  Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service.
  Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request 
repeated too quickly.
  Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 
'exit-code'.
  Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service.
  ```

  But works after starting it manually.

  ```
  nafallo@wendigo:~$ systemctl --user start pulseaudio
  nafallo@wendigo:~$ systemctl --user status pulseaudio
  ● pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago
  TriggeredBy: ● pulseaudio.socket
 Main PID: 5675 (pulseaudio)
   CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
   └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal

  Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service...
  Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nafallo5675 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 29 15:11:28 2020
  InstallationDate: Installed on 2018-06-27 (763 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0W970W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1889416/+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 1889416] Re: pulseaudio.service: Start request repeated too quickly.

2020-08-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  pulseaudio.service: Start request repeated too quickly.

Status in fscrypt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  PA doesn't start on it's own after the latest update.

  ```
  nafallo@wendigo:~$ systemctl --user status pulseaudio
  ● pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 
11min ago
  TriggeredBy: ● pulseaudio.socket
  Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no 
--log-target=journal (code=exited, status=1/FAILURE)
 Main PID: 2774 (code=exited, status=1/FAILURE)

  Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart 
job, restart counter is at 5.
  Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service.
  Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request 
repeated too quickly.
  Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 
'exit-code'.
  Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service.
  Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request 
repeated too quickly.
  Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 
'exit-code'.
  Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service.
  ```

  But works after starting it manually.

  ```
  nafallo@wendigo:~$ systemctl --user start pulseaudio
  nafallo@wendigo:~$ systemctl --user status pulseaudio
  ● pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago
  TriggeredBy: ● pulseaudio.socket
 Main PID: 5675 (pulseaudio)
   CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
   └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal

  Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service...
  Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nafallo5675 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 29 15:11:28 2020
  InstallationDate: Installed on 2018-06-27 (763 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0W970W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1889416/+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 1882180] Re: DoS vulnerability: fail to allocate

2020-08-04 Thread Launchpad Bug Tracker
This bug was fixed in the package whoopsie - 0.2.62ubuntu0.5

---
whoopsie (0.2.62ubuntu0.5) bionic-security; urgency=medium

  * SECURITY UPDATE: integer overflow in bson parsing (LP: #1872560)
- lib/bson/*: updated to latest upstream release.
- CVE-2020-12135
  * SECURITY UPDATE: resource exhaustion via memory leak (LP: #1881982)
- src/whoopsie.c, src/tests/test_parse_report.c: properly handle
  GHashTable.
- CVE-2020-11937
  * SECURITY UPDATE: DoS via large data length (LP: #1882180)
- src/whoopsie.c, src/whoopsie.h, src/tests/test_parse_report.c: limit
  the size of a report file.
- CVE-2020-15570

 -- Marc Deslauriers   Fri, 24 Jul 2020
08:55:26 -0400

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

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

Title:
  DoS vulnerability: fail to allocate

Status in whoopsie package in Ubuntu:
  Confirmed
Status in whoopsie source package in Xenial:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released
Status in whoopsie source package in Eoan:
  Confirmed
Status in whoopsie source package in Focal:
  Fix Released
Status in whoopsie source package in Groovy:
  Confirmed

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  # Vulnerability description
  In whoopsie 0.2.69 and earlier, there is a denial of service vulnerability in 
the parse_report function.
  A crafted input, i.e., crash report located in '/var/crash/', will lead to a 
denial of service attack.
  During the parsing of the crash report, the data length is not checked.   
  
  The value of data length can be directly controlled by an input file. 
  
  In the parse_report() function, the g_malloc or g_realloc is called based on 
data length.
  If we set the value of data length close to the amount of system memory, it 
will cause the daemon process to terminate unexpectedly, hang the system, or 
trigger the OOM killer.

  # PoC
  Please check the below whoopsie_killer2.py

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1882180/+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 1872560] Re: integer overflow in whoopsie 0.2.69

2020-08-04 Thread Launchpad Bug Tracker
This bug was fixed in the package whoopsie - 0.2.62ubuntu0.5

---
whoopsie (0.2.62ubuntu0.5) bionic-security; urgency=medium

  * SECURITY UPDATE: integer overflow in bson parsing (LP: #1872560)
- lib/bson/*: updated to latest upstream release.
- CVE-2020-12135
  * SECURITY UPDATE: resource exhaustion via memory leak (LP: #1881982)
- src/whoopsie.c, src/tests/test_parse_report.c: properly handle
  GHashTable.
- CVE-2020-11937
  * SECURITY UPDATE: DoS via large data length (LP: #1882180)
- src/whoopsie.c, src/whoopsie.h, src/tests/test_parse_report.c: limit
  the size of a report file.
- CVE-2020-15570

 -- Marc Deslauriers   Fri, 24 Jul 2020
08:55:26 -0400

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

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

Title:
  integer overflow in whoopsie 0.2.69

Status in whoopsie package in Ubuntu:
  Confirmed
Status in whoopsie source package in Xenial:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released
Status in whoopsie source package in Eoan:
  Confirmed
Status in whoopsie source package in Focal:
  Fix Released
Status in whoopsie source package in Groovy:
  Confirmed

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  ## Vulnerability in whoopsie
  - whoopsie 0.2.69 and earlier have a heap-based buffer overflow 
vulnerability. 
  - An attacker can cause a denial of service (memory corruption and 
application crash) via a crafted .crash file.

  
  ## Basic
  When a program has been crashed, Linux system tries to create a '.crash' file 
on '/var/crash/' directory with python script located in 
'/usr/share/apport/apport'. 
  The file contains a series of system crash information including core dump, 
syslog, stack trace, memory map info, etc.
  After the creation of '.crash' file, whoopsie extracts the above information 
from the '.crash' file and encodes it into binary json (bson) format.
  Lastly, whoopsie forwards the data to a remotely connected Ubuntu Error 
Report system.

   
  ## Vulnerability
  Unfortunately, we have found a heap-based buffer overflow vulnerability 
during the encoding, when whoopsie attempts to bsonify with crafted crash file.
  The data in '.crash' file is stored in key-value form and the whoopsie 
separately measures the length of 'key' and 'value' to allocate memory region 
during the encoding. 
  A heap-based buffer overflow can occur when an integer overflow happens on a 
variable that contains length of 'key'. 
  FYI, a issue to that raised by 'value' is well covered by performing 
exception handling.

  
@[bson.c:663][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n663]

  const uint32_t len = strlen( name ) + 1;

  - Integer overflow occurs when length of ‘name’ exceeds INT32_MAX value. 
  - Here, ‘name’ indicates the ‘key’ data in ‘.crash’ file.

  
@[bson.c:627][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n627]

  b->data = bson_realloc( b->data, new_size );

  - Unexpected small memory region is allocated due to above integer
  overflow.

  
@[bson.c:680][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n680]

  bson_append( b, name, len );

  - Memory corruption happens when unexpected small memory region is
  allocated.

  
  ## Attack Scenario
  1) Create a fake.crash file
  - '.crash' file is composed of the following format: 'key : value'.
  - To cause the overflow attack, the size of 'key' should be in double amount 
of INT32_MAX.
  - The size of 'value' doesn’t matter, but not zero length.

  $ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash
  $ cat fake.crash
  AAA … AA : B

  
  2) Trigger the whoopsie to read the fake.crash file
  - Just create 'fake.upload' file by touch command.
  - Or launch apport-gtk gui or apport-bug cli application.

  3) Check out the result
  - After a while, the whoopsie has been killed by segmentation fault.

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1872560/+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 1872560] Re: integer overflow in whoopsie 0.2.69

2020-08-04 Thread Launchpad Bug Tracker
This bug was fixed in the package whoopsie - 0.2.69ubuntu0.1

---
whoopsie (0.2.69ubuntu0.1) focal-security; urgency=medium

  * SECURITY UPDATE: integer overflow in bson parsing (LP: #1872560)
- lib/bson/*: updated to latest upstream release.
- CVE-2020-12135
  * SECURITY UPDATE: resource exhaustion via memory leak (LP: #1881982)
- src/whoopsie.c, src/tests/test_parse_report.c: properly handle
  GHashTable.
- CVE-2020-11937
  * SECURITY UPDATE: DoS via large data length (LP: #1882180)
- src/whoopsie.c, src/whoopsie.h, src/tests/test_parse_report.c: limit
  the size of a report file.
- CVE-2020-15570

 -- Marc Deslauriers   Fri, 24 Jul 2020
08:55:26 -0400

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

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

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

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

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

Title:
  integer overflow in whoopsie 0.2.69

Status in whoopsie package in Ubuntu:
  Confirmed
Status in whoopsie source package in Xenial:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released
Status in whoopsie source package in Eoan:
  Confirmed
Status in whoopsie source package in Focal:
  Fix Released
Status in whoopsie source package in Groovy:
  Confirmed

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  ## Vulnerability in whoopsie
  - whoopsie 0.2.69 and earlier have a heap-based buffer overflow 
vulnerability. 
  - An attacker can cause a denial of service (memory corruption and 
application crash) via a crafted .crash file.

  
  ## Basic
  When a program has been crashed, Linux system tries to create a '.crash' file 
on '/var/crash/' directory with python script located in 
'/usr/share/apport/apport'. 
  The file contains a series of system crash information including core dump, 
syslog, stack trace, memory map info, etc.
  After the creation of '.crash' file, whoopsie extracts the above information 
from the '.crash' file and encodes it into binary json (bson) format.
  Lastly, whoopsie forwards the data to a remotely connected Ubuntu Error 
Report system.

   
  ## Vulnerability
  Unfortunately, we have found a heap-based buffer overflow vulnerability 
during the encoding, when whoopsie attempts to bsonify with crafted crash file.
  The data in '.crash' file is stored in key-value form and the whoopsie 
separately measures the length of 'key' and 'value' to allocate memory region 
during the encoding. 
  A heap-based buffer overflow can occur when an integer overflow happens on a 
variable that contains length of 'key'. 
  FYI, a issue to that raised by 'value' is well covered by performing 
exception handling.

  
@[bson.c:663][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n663]

  const uint32_t len = strlen( name ) + 1;

  - Integer overflow occurs when length of ‘name’ exceeds INT32_MAX value. 
  - Here, ‘name’ indicates the ‘key’ data in ‘.crash’ file.

  
@[bson.c:627][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n627]

  b->data = bson_realloc( b->data, new_size );

  - Unexpected small memory region is allocated due to above integer
  overflow.

  
@[bson.c:680][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n680]

  bson_append( b, name, len );

  - Memory corruption happens when unexpected small memory region is
  allocated.

  
  ## Attack Scenario
  1) Create a fake.crash file
  - '.crash' file is composed of the following format: 'key : value'.
  - To cause the overflow attack, the size of 'key' should be in double amount 
of INT32_MAX.
  - The size of 'value' doesn’t matter, but not zero length.

  $ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash
  $ cat fake.crash
  AAA … AA : B

  
  2) Trigger the whoopsie to read the fake.crash file
  - Just create 'fake.upload' file by touch command.
  - Or launch apport-gtk gui or apport-bug cli application.

  3) Check out the result
  - After a while, the whoopsie has been killed by segmentation fault.

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1872560/+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 1872560] Re: integer overflow in whoopsie 0.2.69

2020-08-04 Thread Launchpad Bug Tracker
This bug was fixed in the package whoopsie - 0.2.52.5ubuntu0.5

---
whoopsie (0.2.52.5ubuntu0.5) xenial-security; urgency=medium

  * SECURITY UPDATE: integer overflow in bson parsing (LP: #1872560)
- lib/bson/*: updated to latest upstream release.
- CVE-2020-12135
  * SECURITY UPDATE: resource exhaustion via memory leak (LP: #1881982)
- src/whoopsie.c, src/tests/test_parse_report.c: properly handle
  GHashTable.
- CVE-2020-11937
  * SECURITY UPDATE: DoS via large data length (LP: #1882180)
- src/whoopsie.c, src/whoopsie.h, src/tests/test_parse_report.c: limit
  the size of a report file.
- CVE-2020-15570

 -- Marc Deslauriers   Fri, 24 Jul 2020
08:55:26 -0400

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

Title:
  integer overflow in whoopsie 0.2.69

Status in whoopsie package in Ubuntu:
  Confirmed
Status in whoopsie source package in Xenial:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released
Status in whoopsie source package in Eoan:
  Confirmed
Status in whoopsie source package in Focal:
  Fix Released
Status in whoopsie source package in Groovy:
  Confirmed

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  ## Vulnerability in whoopsie
  - whoopsie 0.2.69 and earlier have a heap-based buffer overflow 
vulnerability. 
  - An attacker can cause a denial of service (memory corruption and 
application crash) via a crafted .crash file.

  
  ## Basic
  When a program has been crashed, Linux system tries to create a '.crash' file 
on '/var/crash/' directory with python script located in 
'/usr/share/apport/apport'. 
  The file contains a series of system crash information including core dump, 
syslog, stack trace, memory map info, etc.
  After the creation of '.crash' file, whoopsie extracts the above information 
from the '.crash' file and encodes it into binary json (bson) format.
  Lastly, whoopsie forwards the data to a remotely connected Ubuntu Error 
Report system.

   
  ## Vulnerability
  Unfortunately, we have found a heap-based buffer overflow vulnerability 
during the encoding, when whoopsie attempts to bsonify with crafted crash file.
  The data in '.crash' file is stored in key-value form and the whoopsie 
separately measures the length of 'key' and 'value' to allocate memory region 
during the encoding. 
  A heap-based buffer overflow can occur when an integer overflow happens on a 
variable that contains length of 'key'. 
  FYI, a issue to that raised by 'value' is well covered by performing 
exception handling.

  
@[bson.c:663][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n663]

  const uint32_t len = strlen( name ) + 1;

  - Integer overflow occurs when length of ‘name’ exceeds INT32_MAX value. 
  - Here, ‘name’ indicates the ‘key’ data in ‘.crash’ file.

  
@[bson.c:627][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n627]

  b->data = bson_realloc( b->data, new_size );

  - Unexpected small memory region is allocated due to above integer
  overflow.

  
@[bson.c:680][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n680]

  bson_append( b, name, len );

  - Memory corruption happens when unexpected small memory region is
  allocated.

  
  ## Attack Scenario
  1) Create a fake.crash file
  - '.crash' file is composed of the following format: 'key : value'.
  - To cause the overflow attack, the size of 'key' should be in double amount 
of INT32_MAX.
  - The size of 'value' doesn’t matter, but not zero length.

  $ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash
  $ cat fake.crash
  AAA … AA : B

  
  2) Trigger the whoopsie to read the fake.crash file
  - Just create 'fake.upload' file by touch command.
  - Or launch apport-gtk gui or apport-bug cli application.

  3) Check out the result
  - After a while, the whoopsie has been killed by segmentation fault.

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1872560/+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 1881982] Re: DoS vulnerability: cause resource exhaustion

2020-08-04 Thread Launchpad Bug Tracker
This bug was fixed in the package whoopsie - 0.2.52.5ubuntu0.5

---
whoopsie (0.2.52.5ubuntu0.5) xenial-security; urgency=medium

  * SECURITY UPDATE: integer overflow in bson parsing (LP: #1872560)
- lib/bson/*: updated to latest upstream release.
- CVE-2020-12135
  * SECURITY UPDATE: resource exhaustion via memory leak (LP: #1881982)
- src/whoopsie.c, src/tests/test_parse_report.c: properly handle
  GHashTable.
- CVE-2020-11937
  * SECURITY UPDATE: DoS via large data length (LP: #1882180)
- src/whoopsie.c, src/whoopsie.h, src/tests/test_parse_report.c: limit
  the size of a report file.
- CVE-2020-15570

 -- Marc Deslauriers   Fri, 24 Jul 2020
08:55:26 -0400

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

Title:
  DoS vulnerability: cause resource exhaustion

Status in whoopsie package in Ubuntu:
  Confirmed
Status in whoopsie source package in Xenial:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released
Status in whoopsie source package in Eoan:
  Confirmed
Status in whoopsie source package in Focal:
  Fix Released
Status in whoopsie source package in Groovy:
  Confirmed

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  # Vulnerability description
  The parse_report() function in whoopsie.c allows attackers to cause a denial 
of service (memory leak) via a crafted file. 
  Exploitation of this issue causes excessive memory consumption which results 
in the Linux kernel triggering OOM killer on arbitrary process.
  This results in the process being terminated by the OOM killer.

  
  # Details 
  We have found a memory leak vulnerability during the parsing the crash file, 
when a collision occurs on GHashTable through g_hash_table_insert().
  According to [1], if the key already exists in the GHashTable, its current 
value is replaced with the new value.
  If 'key_destory_func' and 'value_destroy_func' are supplied when creating the 
table, the old value and the passed key are freed using that function.
  Unfortunately, whoopsie does not handle the old value and the passed key when 
collision happens.
  If a crash file contains same repetitive key-value pairs, it leads to memory 
leak as much as the amount of repetition and results in denial-of-service.

  [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g
  -hash-table-insert

  
  # PoC (*Please check the below PoC: whoopsie_killer.py)
  1) Generates a certain malformed crash file that contains same repetitive 
key-value pairs.
  2) Trigger the whoopsie to read the generated crash file.
  3) After then, the whoopsie process has been killed.

  
  # Mitigation (*Please check the below patch: g_hash_table_memory_leak.patch)
  We should use g_hash_table_new_full() with ‘key_destroy_func’ and 
‘value_destroy_func’ functions instead of g_hash_table_new().
  Otherwise, before g_hash_table_insert(), we should check the collision via 
g_hash_table_lookup_extended() and obtain pointer to the old value and remove 
it.

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1881982/+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 1881982] Re: DoS vulnerability: cause resource exhaustion

2020-08-04 Thread Launchpad Bug Tracker
This bug was fixed in the package whoopsie - 0.2.69ubuntu0.1

---
whoopsie (0.2.69ubuntu0.1) focal-security; urgency=medium

  * SECURITY UPDATE: integer overflow in bson parsing (LP: #1872560)
- lib/bson/*: updated to latest upstream release.
- CVE-2020-12135
  * SECURITY UPDATE: resource exhaustion via memory leak (LP: #1881982)
- src/whoopsie.c, src/tests/test_parse_report.c: properly handle
  GHashTable.
- CVE-2020-11937
  * SECURITY UPDATE: DoS via large data length (LP: #1882180)
- src/whoopsie.c, src/whoopsie.h, src/tests/test_parse_report.c: limit
  the size of a report file.
- CVE-2020-15570

 -- Marc Deslauriers   Fri, 24 Jul 2020
08:55:26 -0400

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

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

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

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

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

Title:
  DoS vulnerability: cause resource exhaustion

Status in whoopsie package in Ubuntu:
  Confirmed
Status in whoopsie source package in Xenial:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released
Status in whoopsie source package in Eoan:
  Confirmed
Status in whoopsie source package in Focal:
  Fix Released
Status in whoopsie source package in Groovy:
  Confirmed

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  # Vulnerability description
  The parse_report() function in whoopsie.c allows attackers to cause a denial 
of service (memory leak) via a crafted file. 
  Exploitation of this issue causes excessive memory consumption which results 
in the Linux kernel triggering OOM killer on arbitrary process.
  This results in the process being terminated by the OOM killer.

  
  # Details 
  We have found a memory leak vulnerability during the parsing the crash file, 
when a collision occurs on GHashTable through g_hash_table_insert().
  According to [1], if the key already exists in the GHashTable, its current 
value is replaced with the new value.
  If 'key_destory_func' and 'value_destroy_func' are supplied when creating the 
table, the old value and the passed key are freed using that function.
  Unfortunately, whoopsie does not handle the old value and the passed key when 
collision happens.
  If a crash file contains same repetitive key-value pairs, it leads to memory 
leak as much as the amount of repetition and results in denial-of-service.

  [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g
  -hash-table-insert

  
  # PoC (*Please check the below PoC: whoopsie_killer.py)
  1) Generates a certain malformed crash file that contains same repetitive 
key-value pairs.
  2) Trigger the whoopsie to read the generated crash file.
  3) After then, the whoopsie process has been killed.

  
  # Mitigation (*Please check the below patch: g_hash_table_memory_leak.patch)
  We should use g_hash_table_new_full() with ‘key_destroy_func’ and 
‘value_destroy_func’ functions instead of g_hash_table_new().
  Otherwise, before g_hash_table_insert(), we should check the collision via 
g_hash_table_lookup_extended() and obtain pointer to the old value and remove 
it.

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1881982/+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 1882180] Re: DoS vulnerability: fail to allocate

2020-08-04 Thread Launchpad Bug Tracker
This bug was fixed in the package whoopsie - 0.2.69ubuntu0.1

---
whoopsie (0.2.69ubuntu0.1) focal-security; urgency=medium

  * SECURITY UPDATE: integer overflow in bson parsing (LP: #1872560)
- lib/bson/*: updated to latest upstream release.
- CVE-2020-12135
  * SECURITY UPDATE: resource exhaustion via memory leak (LP: #1881982)
- src/whoopsie.c, src/tests/test_parse_report.c: properly handle
  GHashTable.
- CVE-2020-11937
  * SECURITY UPDATE: DoS via large data length (LP: #1882180)
- src/whoopsie.c, src/whoopsie.h, src/tests/test_parse_report.c: limit
  the size of a report file.
- CVE-2020-15570

 -- Marc Deslauriers   Fri, 24 Jul 2020
08:55:26 -0400

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

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

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

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

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

Title:
  DoS vulnerability: fail to allocate

Status in whoopsie package in Ubuntu:
  Confirmed
Status in whoopsie source package in Xenial:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released
Status in whoopsie source package in Eoan:
  Confirmed
Status in whoopsie source package in Focal:
  Fix Released
Status in whoopsie source package in Groovy:
  Confirmed

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  # Vulnerability description
  In whoopsie 0.2.69 and earlier, there is a denial of service vulnerability in 
the parse_report function.
  A crafted input, i.e., crash report located in '/var/crash/', will lead to a 
denial of service attack.
  During the parsing of the crash report, the data length is not checked.   
  
  The value of data length can be directly controlled by an input file. 
  
  In the parse_report() function, the g_malloc or g_realloc is called based on 
data length.
  If we set the value of data length close to the amount of system memory, it 
will cause the daemon process to terminate unexpectedly, hang the system, or 
trigger the OOM killer.

  # PoC
  Please check the below whoopsie_killer2.py

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1882180/+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 1882180] Re: DoS vulnerability: fail to allocate

2020-08-04 Thread Launchpad Bug Tracker
This bug was fixed in the package whoopsie - 0.2.52.5ubuntu0.5

---
whoopsie (0.2.52.5ubuntu0.5) xenial-security; urgency=medium

  * SECURITY UPDATE: integer overflow in bson parsing (LP: #1872560)
- lib/bson/*: updated to latest upstream release.
- CVE-2020-12135
  * SECURITY UPDATE: resource exhaustion via memory leak (LP: #1881982)
- src/whoopsie.c, src/tests/test_parse_report.c: properly handle
  GHashTable.
- CVE-2020-11937
  * SECURITY UPDATE: DoS via large data length (LP: #1882180)
- src/whoopsie.c, src/whoopsie.h, src/tests/test_parse_report.c: limit
  the size of a report file.
- CVE-2020-15570

 -- Marc Deslauriers   Fri, 24 Jul 2020
08:55:26 -0400

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

Title:
  DoS vulnerability: fail to allocate

Status in whoopsie package in Ubuntu:
  Confirmed
Status in whoopsie source package in Xenial:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Released
Status in whoopsie source package in Eoan:
  Confirmed
Status in whoopsie source package in Focal:
  Fix Released
Status in whoopsie source package in Groovy:
  Confirmed

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  # Vulnerability description
  In whoopsie 0.2.69 and earlier, there is a denial of service vulnerability in 
the parse_report function.
  A crafted input, i.e., crash report located in '/var/crash/', will lead to a 
denial of service attack.
  During the parsing of the crash report, the data length is not checked.   
  
  The value of data length can be directly controlled by an input file. 
  
  In the parse_report() function, the g_malloc or g_realloc is called based on 
data length.
  If we set the value of data length close to the amount of system memory, it 
will cause the daemon process to terminate unexpectedly, hang the system, or 
trigger the OOM killer.

  # PoC
  Please check the below whoopsie_killer2.py

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1882180/+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 1877023] Re: Unhandled exception in check_ignored()

2020-08-04 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.20.11-0ubuntu27.6

---
apport (2.20.11-0ubuntu27.6) focal-security; urgency=medium

  * SECURITY UPDATE: information disclosure issue (LP: #1885633)
- data/apport: also drop gid when checking if user session is closing.
- CVE-2020-11936
  * SECURITY UPDATE: crash via malformed ignore file (LP: #1877023)
- apport/report.py: don't crash on malformed mtime values.
- CVE-2020-15701
  * SECURITY UPDATE: TOCTOU in core file location
- data/apport: make sure the process hasn't been replaced after Apport
  has started.
- CVE-2020-15702
  * apport/ui.py, test/test_ui.py: make sure a PID is specified when using
--hanging (LP: #1876659)
  * WARNING: This package does _not_ contain the changes from
2.20.11-0ubuntu27.5 in focal-proposed.

 -- Marc Deslauriers   Fri, 31 Jul 2020
09:10:30 -0400

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

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

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

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

Title:
  Unhandled exception in check_ignored()

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  I have found a security issue on apport 2.20.11 and earlier.

  ## Vulnerability 
  apport 2.20.11 and earlier have an unhandled exception vulnerability during 
parsing apport-ignore.xml.
  An attacker can cause a denial of service (i.e., application crash) via a 
crafted apport-ignore.xml file.

  ## Description
  Reports can be suppressed by blacklisting in apport-ignore.xml.

  This is an example of apport-ignore.xml

  
  
    
    
    
  

  Unfortunately, it may cause an unhandled exception when 'mtime'
  attribute is specified as a string value, not a number like this.

  
  
    
  

  It may disrupt apport service and allow an attacker to potentially
  enable a denial of service via local access.

  The flaw lies in improper exception handling of 'mtime' attribute in
  apport-ignore.xml (see
  
https://git.launchpad.net/ubuntu/+source/apport/tree/apport/report.py?h=applied/ubuntu/devel#n1104).

  ## Log
  Here is /var/log/apport.log when the above exception occurs.

  ERROR: apport (pid 25904) Tue May  5 18:38:21 2020: Unhandled exception:
  Traceback (most recent call last):
    File "/usr/share/apport/apport", line 629, in 
  if info.check_ignored():
    File "/usr/lib/python3/dist-packages/apport/report.py", line 1082, in 
check_ignored
  if float(ignore.getAttribute('mtime')) >= cur_mtime:
  ValueError: could not convert string to float: 'string'

  Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1877023/+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 1876659] Re: Unhandled exception in run_hang()

2020-08-04 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.20.11-0ubuntu27.6

---
apport (2.20.11-0ubuntu27.6) focal-security; urgency=medium

  * SECURITY UPDATE: information disclosure issue (LP: #1885633)
- data/apport: also drop gid when checking if user session is closing.
- CVE-2020-11936
  * SECURITY UPDATE: crash via malformed ignore file (LP: #1877023)
- apport/report.py: don't crash on malformed mtime values.
- CVE-2020-15701
  * SECURITY UPDATE: TOCTOU in core file location
- data/apport: make sure the process hasn't been replaced after Apport
  has started.
- CVE-2020-15702
  * apport/ui.py, test/test_ui.py: make sure a PID is specified when using
--hanging (LP: #1876659)
  * WARNING: This package does _not_ contain the changes from
2.20.11-0ubuntu27.5 in focal-proposed.

 -- Marc Deslauriers   Fri, 31 Jul 2020
09:10:30 -0400

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

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

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

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

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

Title:
  Unhandled exception in run_hang()

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  ## Description
  When we start apport-cli without PID, an unhandled exception in apport 
2.20.11 and earlier may allow an authenticated user to potentially enable a 
denial of service via local access.

  The following command may cause an application crash due to an
  unhandled exception.

  $ apport-cli --hanging

  *** Send problem report to the developers?

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

  What would you like to do? Your options are:
S: Send report (24.0 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): K
  Problem report file: /tmp/apport.apport.uc0_znhj.apport
  Traceback (most recent call last):
File "/usr/bin/apport-cli", line 387, in 
  if not app.run_argv():
File "/usr/lib/python3/dist-packages/apport/ui.py", line 690, in run_argv
  self.run_hang(self.options.pid)
File "/usr/lib/python3/dist-packages/apport/ui.py", line 410, in run_hang
  os.kill(int(pid), signal.SIGKILL)
  TypeError: int() argument must be a string, a bytes-like object or a number, 
not 'NoneType'

  
  Above command generates the following application crash file in /var/crash/ 
directory.

  ProblemType: Crash
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 19:09:41 2020
  ExecutablePath: /usr/bin/apport-cli
  ExecutableTimestamp: 1585099033
  InterpreterPath: /usr/bin/python3.6
  ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli --hanging
  ProcCwd: /home/user/apport/bin
  ProcEnviron:
   ...
  ProcMaps:
   ...
  ProcStatus:
   ...
  PythonArgs: ['/usr/bin/apport-cli', '--hanging']
  Traceback:
   Traceback (most recent call last):
 File "/usr/bin/apport-cli", line 387, in 
   if not app.run_argv():
 File "/usr/lib/python3/dist-packages/apport/ui.py", line 690, in run_argv
   self.run_hang(self.options.pid)
 File "/usr/lib/python3/dist-packages/apport/ui.py", line 410, in run_hang
   os.kill(int(pid), signal.SIGKILL)
   TypeError: int() argument must be a string, a bytes-like object or a number, 
not 'NoneType'
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _LogindSession: 6

  
  Many thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1876659/+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 1888061] Re: "Line by line difference" of config files during release upgrade is an unreadable mess

2020-08-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: apt (Ubuntu)
   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/1888061

Title:
  "Line by line difference" of config files during release upgrade is an
  unreadable mess

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from 16.04 to 18.04, then to 19.10, then to 20.04.

  I'm not sure ini whih of the upgrades I noticed the issue but I'm
  pretty sure it applies to all of them.

  As usual, the upgrade had to install some configuration files which
  would replace some files I had modified, and so I got the prompt to
  choose what to do: whether to keep my modified version, or overwrite
  it with the packager's version.

  I don't remember the exact interface, but when you are prompted to
  choose that, you have a few options to see the differences between the
  two files. I think by default it shows a classical diff (with "+++"s
  and "---"s) but there is an option to show "line by line differences".

  I chose that for one file, and I expected to see a side-by-side diff
  similar to those I've seen in dozens of tools, where you see the two
  entire files side by side and the differences are highlighted in both
  sides in colors, such as lines that are added or removed and lines
  that are modified.

  Short of that, the very least that I would have expected was to show
  the two files side by side.

  
  Instead, this PATHETIC CRAP showed up which can be seen in the sceenshot.
  And don't remind me of the code of conduct. I'm not insulting anybody. It's a 
FACT that this is crap and that it is pathetic.

  
  Not only are DIFFERENCES not shown (line by line or otherwise). The two files 
are shown as one single text file, where each line of the second file is just 
appended to the corresponding line of the first file.
  You can't even tell where the line of one file begins and the line of the 
other ends.

  It's a completely useless way to show "differences" between two files.
  It's less useful than just showing the two files next to each other in
  two independent text boxes. Way less useful. Let alone compared to an
  actual side-by-side diff tool (and there are plenty to chose from).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.2ubuntu0.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Sat Jul 18 17:30:36 2020
  InstallationDate: Installed on 2013-10-11 (2471 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to focal on 2020-07-12 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1888061/+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 1890170] Re: ImportError libstdc++.so.6 cannot allocate memory after importing PyQt5.Qt PyQt5.QtCore and cv2

2020-08-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  ImportError libstdc++.so.6 cannot allocate memory after importing
  PyQt5.Qt PyQt5.QtCore and cv2

Status in mysql-8.0 package in Ubuntu:
  Confirmed
Status in opencv package in Ubuntu:
  Confirmed
Status in pyqt5 package in Ubuntu:
  Confirmed

Bug description:
  I'm using an updated Lubuntu focal. Starting maybe last week (monday July 
27th), if in python3 I do
  from PyQt5 import Qt, QtCore
  import cv2

  I get
  ImportError: /lib/x86_64-linux-gnu/libstdc++.so.6: cannot allocate memory in 
static TLS block

  I noticed only now that the reverse (first import cv2, then Qt,
  QtCore) seems to work correctly and displays no errors. I'm afraid I
  might not be able to do the reverse in my real software...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Mon Aug  3 17:49:20 2020
  InstallationDate: Installed on 2020-07-15 (19 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890170/+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 1890170] Re: ImportError libstdc++.so.6 cannot allocate memory after importing PyQt5.Qt PyQt5.QtCore and cv2

2020-08-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  ImportError libstdc++.so.6 cannot allocate memory after importing
  PyQt5.Qt PyQt5.QtCore and cv2

Status in mysql-8.0 package in Ubuntu:
  Confirmed
Status in opencv package in Ubuntu:
  Confirmed
Status in pyqt5 package in Ubuntu:
  Confirmed

Bug description:
  I'm using an updated Lubuntu focal. Starting maybe last week (monday July 
27th), if in python3 I do
  from PyQt5 import Qt, QtCore
  import cv2

  I get
  ImportError: /lib/x86_64-linux-gnu/libstdc++.so.6: cannot allocate memory in 
static TLS block

  I noticed only now that the reverse (first import cv2, then Qt,
  QtCore) seems to work correctly and displays no errors. I'm afraid I
  might not be able to do the reverse in my real software...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Mon Aug  3 17:49:20 2020
  InstallationDate: Installed on 2020-07-15 (19 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890170/+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 1890170] Re: ImportError libstdc++.so.6 cannot allocate memory after importing PyQt5.Qt PyQt5.QtCore and cv2

2020-08-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mysql-8.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  ImportError libstdc++.so.6 cannot allocate memory after importing
  PyQt5.Qt PyQt5.QtCore and cv2

Status in mysql-8.0 package in Ubuntu:
  Confirmed
Status in opencv package in Ubuntu:
  Confirmed
Status in pyqt5 package in Ubuntu:
  Confirmed

Bug description:
  I'm using an updated Lubuntu focal. Starting maybe last week (monday July 
27th), if in python3 I do
  from PyQt5 import Qt, QtCore
  import cv2

  I get
  ImportError: /lib/x86_64-linux-gnu/libstdc++.so.6: cannot allocate memory in 
static TLS block

  I noticed only now that the reverse (first import cv2, then Qt,
  QtCore) seems to work correctly and displays no errors. I'm afraid I
  might not be able to do the reverse in my real software...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Mon Aug  3 17:49:20 2020
  InstallationDate: Installed on 2020-07-15 (19 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890170/+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 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output

2020-08-04 Thread Launchpad Bug Tracker
This bug was fixed in the package pulseaudio - 1:11.1-1ubuntu7.10

---
pulseaudio (1:11.1-1ubuntu7.10) bionic; urgency=medium

  * d/p/0903-device-port-switch-on-port-available-fix-automatic-p.patch
  * (LP: #1882248)

 -- Hui Wang   Thu, 09 Jul 2020 16:03:25 +0800

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

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

Title:
  [SRU] plug headset won't proper reconfig ouput to it on machine with
  default output

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Released

Bug description:
  This is for pulseaudio bionic:

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, the active profile is Off, after users plug a
  headset to it and users select the headset from the pop-up dialogue,
  users expect the profile changes to analog-stereo (headset is on it),
  but the active_profile is still Off.

  [Fix]
  Upstream already has a patch to fix it, cherrypiack that patch to bionic.
  And that patch is already in the eoan, focal, ...

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and select the headset from UI, the profile changes to
  analog-stereo, and play some sound, we could hear it from the headset

  [Regression Risk]
  Low, this patch is already in the upstream for a long time, and it is
  already in the eoan and focal.


  
  For linux kernel (oem-b):

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, and users plug a headset, the sound couldn't
  output from headset.

  [Fix]
  reverse the order of headset mic and headphone mic

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and play sound, we could hear the sound from headset.

  [Regression Risk]
  Low, this patch only affects the machine without internal mic and
  internal spk, and I already tested this patch on the machine without
  internal mic and internal spk, it worked well.

  target machine does not have built-in speaker, and the monitor does
  not have an audio output (like d-sub VGA)

  As first boot, there will be a "dummy output" in g-c-c.

  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882248/+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 1873961] Re: tc filter show tcp_flags wrong mask value

2020-08-04 Thread Launchpad Bug Tracker
This bug was fixed in the package iproute2 - 4.15.0-2ubuntu1.2

---
iproute2 (4.15.0-2ubuntu1.2) bionic; urgency=medium

  * tc filter show tcp_flags wrong mask value (LP: #1873961)
- d/p/lp1873961-tc-fix-bugs-for-tcp_flags-and-ip_attr-hex-output.patch

 -- Stefan Bader   Wed, 15 Jul 2020 17:16:31
+0200

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

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

Title:
  tc filter show tcp_flags wrong mask value

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Fix Released

Bug description:
  [SRU Justification]

  Impact: The tc command does not show the correct values for tcp_flags
  (and ip_tos) on filter rules. This might break other scripts parsing
  that output but at least confuses users.

  Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output"
  from upstream iproute2.

  Testcase:
  tc qdisc add dev lo ingress
  tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32
  tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \
   tcp_flags 0x909/f00

  tc filter show dev lo parent :

  filter protocol ip pref 3 flower chain 0
  filter protocol ip pref 3 flower chain 0 handle 0x1
    eth_type ipv4
    ip_tos a9606c10 <-- bad, should be 0x8/32
    not_in_hw
  filter protocol ip pref 5 flower chain 0
  filter protocol ip pref 5 flower chain 0 handle 0x1
    eth_type ipv4
    ip_proto tcp
    tcp_flags 909909 <-- bad, should be 0x909/f00
    not_in_hw

  Note that the ip_tos value in the -j[son] output is correct, while the 
tcp_flags value is
  is incorrect in both cases.

  Risk of Regression:
  Low: Usually scripts would use the json output and that has at least the ip 
output correct. And the values shown in the bad case seem to be little useful. 
So it seems unlikely anybody relied on them. But cannot completely be ruled out.

  === Original description ===

  ---Problem Description---
  Problem Descriptions
  "tc" utility does not show correct TC rule's tcp_flags mask correctly in 
current "iproute2" package shipped on Genesis.
  # dpkg -l |grep iproute2
  ii  iproute2  4.15.0-2ubuntu1  ppc64el  networking and traffic control 
tools

  ---Steps to Reproduce---
   Steps to reproduce the problem:
  1) Add a tc rule to the testing VF (i.e. p0v2_r):
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2  
skip_sw action mirred egress redirect dev p0v0_r

  2) Validate the added TC rule:
  # tc filter show dev p0v2_r root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
    src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
    eth_type ipv4
    ip_proto tcp
    tcp_flags 22   /* <--- Wrong */
    skip_sw
    in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  3) If we add the tcp_flags using explicit mask 0x7:
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 
 skip_sw action mirred egress redirect dev p0v0_r

  After that, using "tc filter show dev p0v2_r root" to verify, we still
  see the same output (tcp_flags 22) as shown in 2) above, which is
  wrong.

  Userspace tool common name: tc

  The userspace tool has the following bit modes: 64-bit

  Userspace package: iproute2

  ==
  Fixes:
  There are 2 patches to fix the issue:
  patch 1:
  commit b85076cd74e77538918d35992b1a9cd17ff86af8
  Author: Stephen Hemminger 
  Date:   Tue Sep 11 08:29:33 2018 -0700
  lib: introduce print_nl
  Common pattern in iproute commands is to print a line seperator
  in non-json mode. Make that a simple function.
  /* This patch declares global variable "const char *_SL_ = "\n";" in 
lib/utils.c to be used by 2nd patch */

  patch 2:
  commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc
  Author: Keara Leibovitz 
  Date:   Thu Jul 26 09:45:30 2018 -0400
  tc: fix bugs for tcp_flags and ip_attr hex output
  Fix hex output for both the ip_attr and tcp_flags print functions.

  With the above 2 patches pull in, the new "tc" utility will show the correct 
tcp_flags mask:
  # tc filter show dev p0v2 root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
    src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
    eth_type ipv4
    ip_proto tcp
    tcp_flags 0x2/7   /* <--- Correct */
    skip_sw
    in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  
  This bug affects tc in Ubuntu 18.04.1 stock image.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1884265] Re: [fips] ntpq segfaults when attempting to use MD5 from FIPS-openssl library.

2020-08-04 Thread Launchpad Bug Tracker
This bug was fixed in the package ntp - 1:4.2.8p10+dfsg-5ubuntu7.2

---
ntp (1:4.2.8p10+dfsg-5ubuntu7.2) bionic; urgency=medium

  * ntpq should check return code from libcrypto calls (LP: #1884265)
- debian/patches/ntpq-openssl-check.patch

 -- Joy Latten   Thu, 09 Jul 2020 21:11:52
+

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

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

Title:
  [fips] ntpq segfaults when attempting to use MD5 from FIPS-openssl
  library.

Status in ntp package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  Fix Released
Status in ntp source package in Bionic:
  Fix Released
Status in openssl source package in Bionic:
  In Progress

Bug description:
  [Impact]
  In FIPS mode on Bionic MD5 is semi-disabled causing some applications to 
segfault.

  ntpq uses crypto hashes to authenticate its requests. By default it
  uses md5. However, when compiled with openssl it creates a lists of
  acceptable hashes from openssl that can be used.

  This issue is only applicable in bionic and when using fips-openssl.

  [Test Steps]
  Test case:
  sudo apt install ntp
  ntpq -p
  Segmentation fault (core dumped)

  What happens there is ntpq wants to iterate all available digests
  (list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this
  task.

  EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c.
  For FIPS mode it adds:
  EVP_add_digest(EVP_md5());

  What happens later in ntpq is (list_md_fn function inside ntpq.c):
  ctx = EVP_MD_CTX_new();
  EVP_DigestInit(ctx, EVP_get_digestbyname(name));
  EVP_DigestFinal(ctx, digest, _len);

  First digest it gets is MD5, but while running EVP_DigestInit for it, it gets 
to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex):
  #ifdef OPENSSL_FIPS
  if (FIPS_mode()) {
  if (!(type->flags & EVP_MD_FLAG_FIPS)
  && !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) {
  EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS);
  return 0;
  }
  }
  #endif

  Due to type->flags for MD5 being 0 there's an error set 
(EVP_R_DISABLED_FOR_FIPS).
  After getting back to ntpq.c:
  ctx->engine and ctx->digest are not set (due to the mentioned error), hence

  inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c)
  OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE);
  causes a segfault (ctx->digest is NULL).

  So either MD5 shouldn't be added in FIPS mode or it should have the
  EVP_MD_FLAG_FIPS to be properly initialized.

  [Regression Potential]

  I don't think this should regress ntpq + openssl from the Ubuntu
  archive.

  Current archive ntpq + openssl behaviour:
  openssl includes all message digests and hands ntpq a sorted digest-list.
  ntpq doesn't check return from EVP_Digest(Init|Final) and assumes all is well 
and sticks all digests into its list regardless if it is working or not.

  i.e.
  ntpq> help keytype
  function: set key type to use for authenticated requests, one of:
  MD4, MD5, RIPEMD160, SHA1, SHAKE128

  If somehow openssl library is corrupted and sends back erroneous
  results, its possible the authentication will just not ever work.

  Newly fixed archive ntpq + oenssl beahviour:
  openssl includes all message digests and hands ntpq a sorted digest-list.
  ntpq checks each one and includes each working digest. With a non-corrupted 
openssl, everything works fine and ntpq includes each into its list. Ends up 
with a list identical to the one above.

  If somehow opensll library is corrupted and sends back erroneous
  results, ntpq will hopefully catch it by checking return code and
  include only those algos that appear to be working. Its possible
  authentication will work for ntpq.

  The difference will be seen in ntpq + fips-openssl. ntpq will check
  return, and for fips-not-approved algos, return will indicate an
  error. So these algos will be skipped and ntpq will not include into
  its digest list. Resulting in a much shorter list of only fips-
  approved algos.

  i.e.
  ntpq> help keytype
  function: set key type to use for authenticated requests, one of:
  SHA1, SHAKE128

  Since md5 is ntpq's default auth algo, this will need to be changed to one of 
the above algos in the config files.
  But I think it is somewhat understood that MD5 is bad in a FIPS environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1884265/+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 1883880] Re: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic

2020-08-04 Thread Launchpad Bug Tracker
This bug was fixed in the package binutils - 2.30-21ubuntu1~18.04.4

---
binutils (2.30-21ubuntu1~18.04.4) bionic; urgency=medium

  * d/p/lp-1883880-x86-don-t-mistakenly-scale-non-8-bit-displacements.patch:
avoid scaling displacements that breaks e.g. some AVX512 code (LP: #1883880)

 -- Christian Ehrhardt   Thu, 18 Jun
2020 13:03:55 +0200

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

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

Title:
  fix non-8-bit x86 displacements breaking AVX512 builds on Bionic

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Bionic:
  Fix Released
Status in binutils package in Debian:
  Confirmed

Bug description:
  [Impact]

   * the assembler scales non 8 bit cases which was identified
 to break e.g. some AVX512 code. It is nasty as it isn't a compile/link/ 
 time error. Instead the instructions might silently be corrupted until 
 running. Things might even work on some but fail on other systems if 
 e.g. the AVX code paths only run on newer chips.

* The fix is upstream for a while and not re-changed again. Furthermore 
  it is in several Ubuntu releases without bugs due to that, which should 
  make the backport rather safe.

  [Test Case]

   * Simple example to trigger the bug:

  echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d
  avx.o | grep vmovaps

  The expected output is that the objdump output matches the vmovaps
  instruction input. When using binutils with the bug, the initial 0x40
  will be incorrect.

  Working:
  $ echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | 
grep vmovaps
 0: 62 f1 7c 48 28 04 05 vmovaps 0x40(,%rax,1),%zmm0
  Failing:
  $ echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | 
grep vmovaps
 0: 62 f1 7c 48 28 04 05 vmovaps 0x1(,%rax,1),%zmm0

  [Regression Potential]

   * Well, this is a double edged sword. On one hand this is fortunately a 
 small change and only affects something formerly clearly broken. So it 
 should be good and only change cases formerly being bad.
 But OTOH binutils areused in so many cases that I feel unable to say
 "nothing will happen". The change goes to the gnu assembler, so that is 
 the place to look out for regressions.

  [Other Info]
   
   * needs a sponsor experienced with binutils to check potential pitfalls


  
  ---

  
  Hi,
  DPDK has run into some issues in the past
   https://bugs.dpdk.org/show_bug.cgi?id=97
   https://bugs.dpdk.org/show_bug.cgi?id=249

  Eventually the issues got resolved in binutils via
   https://sourceware.org/bugzilla/show_bug.cgi?id=23465

  After binutils is fixed people rebuilding DPDK themselve can use
   http://patches.dpdk.org/patch/71679/
  to gain more performance while on Bionics bintuils level.

  Note: Bionic is on DPDK 17.11.x which will not get further stable release 
afaik. But quite often people build their own DPDK. In fact this came up as a 
request from Openvswitch upstream/Intel to allow such builds on Bionic.
  I'd ping those people about the bug and ask them to participate in the 
verification if this becomes an SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1883880/+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 1880575] Re: Cuenta Online en Google

2020-08-03 Thread Launchpad Bug Tracker
[Expired for gnome-online-accounts (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Cuenta Online en Google

Status in gnome-online-accounts package in Ubuntu:
  Expired

Bug description:
  Hasta la versión 18.04.4 LTS podía conectar la cuenta online de la
  universidad (@uoc.edu) sin problemas y sincronizar calendarios y
  contactos con evolution, es una cuenta que se accede a ella via
  google.

  Cuando lo intento con esta versión de ubuntu 20.04 LTS me da un error
  justo después de ingresar la cuenta de correo.

  "Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough).

  Y no puedo continuar con el registro de la cuenta.

  Puedo hacer algo yo a nivel local para solucionar este problema? Me
  resulta muy útil poder sincronizar los calendarios de actividades con
  la universidad y los contactos con mi tutor y los profesores de cada
  asignatura.

  Muchas gracias de antemano.
  Un saludo, quedo a la espera de alguna solución.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1880575/+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 64527] Re: dd segfault

2020-08-03 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 42264 ***
https://bugs.launchpad.net/bugs/42264

This bug was fixed in the package coreutils - 8.32-3ubuntu1

---
coreutils (8.32-3ubuntu1) groovy; urgency=medium

  * Merge with Debian unstable (LP: #1888046). Remaining changes:
- debian/rules:
  + Allow crossbuilding
  + Run tests
  + Ignore the cut-huge-range test failure on armhf, only seen on
the buildds.
- debian/tests:
  + Add dep8 tests
- debian/patches/80_fedora_sysinfo.patch
  + Make 'uname -i -p' return the real processor/hardware,
instead of unknown.
- debian/patches/99_float_endian_detection.patch:
  + Fix detection of floating point endianness.
- d/p/treat-devtmpfs-and-squashfs-as-dummy-filesystems.patch:
  + Avoid displaying snaps in output from df and other tools, by
excluding display of squashfs filesystems.
(LP #1219529, #1756595)
  + Exclude devtmpfs filesystems in output from df and other tools
since it is a dummy filesystem.
(LP #1219529)
  * Refresh d/patches/.
  * Fix FTBFS on ARM64.
- d/p/restore-ls-behavior-8.31.patch: Upstream patch to restore
  coreutils ls' 8.31 behavior on removed directories, which is
  necessary to prevent using SYS_getdents that doesn't exist on
  ARM64.
- d/p/improve-removed-directory-test.patch: Upstream patch to
  improve ls' removed-directory test.

 -- Sergio Durigan Junior   Fri, 24 Jul
2020 15:01:15 -0400

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

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

Title:
  dd segfault

Status in coreutils package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: coreutils

  try 
  # dd if=/dev/zero of=/var/tmp/blank.img bs=1k count=720
  720+0 records in
  720+0 records out
  Segmentation fault
  #

  as I tried this happens just on ubuntu coreutils version...
  SegFault may brings security related issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/64527/+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 1888046] Re: Please merge coreutils 8.32-2 (main) from Debian unstable (main)

2020-08-03 Thread Launchpad Bug Tracker
This bug was fixed in the package coreutils - 8.32-3ubuntu1

---
coreutils (8.32-3ubuntu1) groovy; urgency=medium

  * Merge with Debian unstable (LP: #1888046). Remaining changes:
- debian/rules:
  + Allow crossbuilding
  + Run tests
  + Ignore the cut-huge-range test failure on armhf, only seen on
the buildds.
- debian/tests:
  + Add dep8 tests
- debian/patches/80_fedora_sysinfo.patch
  + Make 'uname -i -p' return the real processor/hardware,
instead of unknown.
- debian/patches/99_float_endian_detection.patch:
  + Fix detection of floating point endianness.
- d/p/treat-devtmpfs-and-squashfs-as-dummy-filesystems.patch:
  + Avoid displaying snaps in output from df and other tools, by
excluding display of squashfs filesystems.
(LP #1219529, #1756595)
  + Exclude devtmpfs filesystems in output from df and other tools
since it is a dummy filesystem.
(LP #1219529)
  * Refresh d/patches/.
  * Fix FTBFS on ARM64.
- d/p/restore-ls-behavior-8.31.patch: Upstream patch to restore
  coreutils ls' 8.31 behavior on removed directories, which is
  necessary to prevent using SYS_getdents that doesn't exist on
  ARM64.
- d/p/improve-removed-directory-test.patch: Upstream patch to
  improve ls' removed-directory test.

 -- Sergio Durigan Junior   Fri, 24 Jul
2020 15:01:15 -0400

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

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

Title:
  Please merge coreutils 8.32-2 (main) from Debian unstable (main)

Status in coreutils package in Ubuntu:
  Fix Released

Bug description:
  New coreutils features are missing in Ubuntu. Especially, "ls
  --time=birth" available since 8.32, and time of file creation in
  stat(1) on btrfs or ext4 fixed since 8.31. Please consider to
  incorporate these features at least into Ubuntu 20.10 (Groovy
  Gorilla).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1888046/+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 1831467] Re: test-umockdev tests flaky on armhf (and sometimes other archs)

2020-08-03 Thread Launchpad Bug Tracker
This bug was fixed in the package umockdev - 0.14.2-1

---
umockdev (0.14.2-1) unstable; urgency=medium

  * New upstream version 0.14.2:
- preload: Fix incomplete reads scripts
- tests: Fix incomplete reads for fuzzy script tests
  (Closes: #767908)
- tests: Add $SLOW_TESTBED_FACTOR env var for slow architectures
  * Make autopkgtest robust for slow testbeds.
Set the new `$SLOW_TESTBED_FACTOR` to avoid frequent failures on armhf
and other slow/shared distro CI hardware. (LP: #1831467)
  * debian/rules: Add hack for code coverage related autoconf regression.

 -- Martin Pitt   Wed, 29 Jul 2020 18:08:15 +0200

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

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

Title:
  test-umockdev tests flaky on armhf (and sometimes other archs)

Status in umockdev package in Ubuntu:
  Fix Released
Status in umockdev source package in Xenial:
  In Progress
Status in umockdev source package in Bionic:
  In Progress
Status in umockdev source package in Focal:
  In Progress
Status in umockdev source package in Groovy:
  Fix Released

Bug description:
  [impact]

  these tests fail intermittently, due to various timing issues, as well
  as an actual code bug in how data fuzz is calculated.

  it looks like the failures are mostly on armhf, but do happen less
  often on other archs.

  [test case]

  check the previous autopkgtest logs, e.g.
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/armhf/u/umockdev/20190601_015323_8f795@/log.gz

  [regression potential]

  any regression would likely result in incorrectly failing/passing 
autopkgtests, or in a incorrect pass or incorrect fail of the ScriptRunner
  to verify the data's level of fuzz.

  [scope]

  as the tests are flaky on armhf all the way back to trusty, this is
  needed for all releases.

  [other info]

  Fixed upstream in PR https://github.com/martinpitt/umockdev/pull/103

  Most of the changes are test case fixes, but there is one fix to
  source code to fix the ScriptRunning function that validates the level
  of fuzz in data, so this is not *only* a testcase fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1831467/+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 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support

2020-08-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  gi.repository.GLib.GError: pk-client-error-quark: could not do
  untrusted question as no klass support

Status in packagekit package in Ubuntu:
  Triaged
Status in packagekit source package in Eoan:
  Triaged
Status in packagekit source package in Focal:
  Confirmed

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

  [Back trace]
  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 86, in on_pktask_finish
  results = self._pktask.generic_finish(result)
  gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted 
question as no klass support (8)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 89, in on_pktask_finish
  Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in 
__init__
  self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in 
__init__
  _window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
  TypeError: could not convert value for property `transient_for' from 
DialogCacheOutdated to GtkWindow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+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 1669156] Re: Fails writing with Caps Lock

2020-08-02 Thread Launchpad Bug Tracker
[Expired for lightdm (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Fails writing with Caps Lock

Status in lightdm package in Ubuntu:
  Expired

Bug description:
  On Ubuntu 16.04:

  When clicking on the following 3 keyboard keys simultaneously: 
  Left-CTRL + Left-ALT + F1
  Then you get to a textual terminal (CLI) where you can type commands.
  But there is a problem when typing English letters with Caps Lock turned on:
  Instead of English capital letters - you see squares, 
  so actually you can't login to your user that way
  if the username/password has Capital letters.

  The only method which allows you to write capital English letters
  is to simultaneously click Left-Shift + 'a letter'. 
  That is the only method that works well.

  Note that the Caps Lock key works well with the graphical terminal (pseudo / 
pts)
  that appears on Ubuntu when hitting simultaneously:
  Left-CTRL + Left-ALT + T

  ---

  I assumed the bug report is relevant to "shadow" package because that
  the "/bin/login" binary comes from that package.
  Package version of 'shadow' is: 1:4.2-3.1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1669156/+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 1880614] Re: Network Manager and the Menu Bar display a question mark, as though it wasn't able to connect to the internet, but Ubuntu can access the internet just fine; this was

2020-08-02 Thread Launchpad Bug Tracker
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Network Manager and the Menu Bar display a question mark, as though it
  wasn't able to connect to the internet, but Ubuntu can access the
  internet just fine; this was a false flag

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  A false flag of reporting a network without wifi access.

  This happens when leaving the computer idle for 20 minutes or more.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon May 25 19:01:36 2020
  InstallationDate: Installed on 2020-05-07 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 20600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.22.10  connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880614/+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 1881970] Re: [Satellite Pro L550, Realtek ALC272, Speaker, Internal] No sound at all

2020-08-02 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [Satellite Pro L550, Realtek ALC272, Speaker, Internal] No sound at
  all

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Problem of son. Sortie Fictive.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  auguen 1324 F pulseaudio
   /dev/snd/controlC0:  auguen 1324 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  3 23:10:09 2020
  InstallationDate: Installed on 2020-06-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Audio interne - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  auguen 1324 F pulseaudio
   /dev/snd/controlC0:  auguen 1324 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [Satellite Pro L550, Realtek ALC272, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2009
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.90
  dmi.board.name: KTWAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.90:bd12/18/2009:svnTOSHIBA:pnSatelliteProL550:pvrPSLW9E-01600GFR:rvnTOSHIBA:rnKTWAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
  dmi.product.name: Satellite Pro L550
  dmi.product.sku: 012345678912345678912345678
  dmi.product.version: PSLW9E-01600GFR
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881970/+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 1870088] Re: xz-utils ftbfs in focal

2020-08-02 Thread Launchpad Bug Tracker
This bug was fixed in the package xz-utils - 5.2.4-1ubuntu1

---
xz-utils (5.2.4-1ubuntu1) focal; urgency=medium

  * Use the generic % rule in debian/rules, otherwise it FTBFS with
debhelper 12.5. Closes: #945961. LP: #1870088.

 -- Tiago Stürmer Daitx   Mon, 20 Apr 2020
21:43:24 +

** Changed in: xz-utils (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  xz-utils ftbfs in focal

Status in xz-utils package in Ubuntu:
  Fix Released
Status in xz-utils source package in Focal:
  Fix Committed
Status in xz-utils package in Debian:
  New

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz

  dh build --parallel 
  make[2]: Leaving directory '/<>'
 dh_testroot -O--parallel
 dh_prep -O--parallel
 debian/rules override_dh_auto_install
  make[2]: Entering directory '/<>'
  dh_auto_install --builddirectory debian/xzdec-build
  dh_auto_install --builddirectory debian/normal-build
  dh_auto_install --builddirectory debian/static-build
  set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \
  install -d debian/tmp/lib/$arch; \
  mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \
  dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \
  ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so
  mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such 
file or directory
  make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [debian/rules:4: install] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:4: binary] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1870088/+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 1889991] [NEW] Highlight for the task switcher is too subtle

2020-08-01 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The task switcher has a highlight to enable the user can see which task
has focus. In Ubuntu 20.04 (but not earlier versions, I think) this
highlight is so subtle that one can easily miss it.

I'm all for subtlety, but this is *too* subtle. I find myself repeatedly
choosing the wrong task.

My vision is not perfect but decent. Users with poor vision may find
this problem particularly difficult.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug  1 12:50:46 2020
DistUpgraded: 2020-04-20 13:45:34,098 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.10, 5.4.0-40-generic, x86_64: installed
 virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo ThinkPad X1 Carbon 5th Gen [17aa:224f]
InstallationDate: Installed on 2017-12-08 (966 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 20HRCTO1WW
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=a890597b-ae6f-4f55-a929-cdd87de29f97 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-20 (102 days ago)
dmi.bios.date: 06/03/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N1MET63W (1.48 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HRCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET63W(1.48):bd06/03/2020:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 5th
dmi.product.name: 20HRCTO1WW
dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th
dmi.product.version: ThinkPad X1 Carbon 5th
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu
-- 
Highlight for the task switcher is too subtle
https://bugs.launchpad.net/bugs/1889991
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 1886585] [NEW] Restarting display / screen

2020-07-31 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The computer stops and restarts the screen and after about 2 secs the display 
works normally in maybe 30 secs . The proces repeats for several minutes (maybe 
24 mins) and then suddenly everything works normally.
If I go into some serous work like this report I am able to do that without 
disturbance.
If I go back to no working apps the operation continues with on/off working.

My system is the latest 20.04 software upgrade from the Beta-version.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.20
ProcVersionSignature: Ubuntu 5.4.0-41.45-generic 5.4.44
Uname: Linux 5.4.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul  6 22:52:53 2020
InstallationDate: Installed on 2019-10-20 (260 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptclonesystemstate.tar.gz:
 Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: Error executing command as another user: Not authorized
 
 This incident has been reported.
VarLogDistupgradeAptlog:
 Log time: 2020-06-25 21:27:41.194955
 Starting pkgProblemResolver with broken count: 0
 Starting 2 pkgProblemResolver with broken count: 0
 Done
 None

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


** Tags: amd64 apport-bug dist-upgrade focal package-from-proposed
-- 
Restarting display / screen
https://bugs.launchpad.net/bugs/1886585
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 1889742] [NEW] [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)

2020-07-31 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

== Comment: #0 - Heinz-Werner Seeck  - 
2020-07-31 03:28:30 ==
On z13 we have that vector alignment hints are already accepted. This backport 
enables GAS to accept such hints not only for target z14 but also for z13. 
Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit 
from such alignment hints. (note a separate bugzilla entry for GCC allowing to 
emit alignment hints for z13 will be opened shortly)

This is a backport of upstreams commit 26b6ab7a0e.
 
Userspace tool common name: as 
 
The userspace tool has the following bit modes: 64-bit 

Userspace rpm: binutils


Already included within 20.10 via LP:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654

This should also be SRUed for 20.04

** Affects: binutils (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-187207 severity-medium 
targetmilestone-inin2004
-- 
[UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)
https://bugs.launchpad.net/bugs/1889742
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to binutils in Ubuntu.

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


[Touch-packages] [Bug 1889699] Re: Brave is not included in the Ubuntu helpers

2020-07-30 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~fmarier/ubuntu/+source/apparmor/+git/apparmor/+merge/388439

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

Title:
  Brave is not included in the Ubuntu helpers

Status in apparmor package in Ubuntu:
  New

Bug description:
  The Brave browser is not included in /etc/apparmor.d/abstractions
  /ubuntu-browsers and /etc/apparmor.d/abstractions/ubuntu-helpers which
  means that when it's set as a default browser by a user, profiles like
  /etc/apparmor.d/usr.bin.evince break.

  In this case, it means that users can't click on web links in PDFs for
  example: https://community.brave.com/t/brave-does-not-open-links-
  clicked-when-set-as-default-browser/146608/9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1889699/+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 1880768] Re: usermod/userdel errantly believe user has running processes

2020-07-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  usermod/userdel errantly believe user has running processes

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  I have found an occasional inability to remove or modify users due to
  incorrect matching of process owners, e.g.

  # id -u bdobbs
  1047
  # usermod -u 1573552 bdobbs
  usermod: user bdobbs is currently used by process 6337
  # cat /proc/6337/status | grep Uid
  Uid:  3000400 3000400 3000400 3000400

  In `libmisc/user_busy.c` a check is performed for processes owned by a
  user which is being modified. Searching subordinate user IDs causes
  errant matches. This has been fixed upstream, and is included in
  passwd-4.8 and the issue does not appear to exist in groovy.

  https://github.com/shadow-
  maint/shadow/commit/fd4405b763d26649339069532e79bd45013c8c38 I believe
  this fix should be backported to xenial and bionic.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: passwd 1:4.2-3.1ubuntu5.4
  ProcVersionSignature: Ubuntu 4.4.0-1107.118-aws 4.4.219
  Uname: Linux 4.4.0-1107-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  Date: Tue May 26 22:18:00 2020
  Ec2AMI: ami-4e79ed36
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2a
  Ec2InstanceType: t3.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.cron.daily.passwd: [deleted]

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


  1   2   3   4   5   6   7   8   9   10   >