Re: [Touch-packages] [Bug 1891663] Re: package systemd-timesyncd 245.4-4ubuntu3.2 failed to install/upgrade: package systemd-timesyncd is already installed and configured

[Helmut Meyer]

HI, Thank you for your email,but I am to stupid to understand. In the
links, I can see my failure, but nothing else.
Please answer in German... :-)

Thank you so much!

Helmut

Am Fr., 14. Aug. 2020 um 18:45 Uhr schrieb Balint Reczey <
1891...@bugs.launchpad.net>:

> There are many similar bugs filed against dpkg, is this an APT issue
> running dpkg wrong?
>
> ** Package changed: dpkg (Ubuntu) => apt (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1891663
>
> Title:
>   package systemd-timesyncd 245.4-4ubuntu3.2 failed to install/upgrade:
>   package systemd-timesyncd is already installed and configured
>
> Status in apt package in Ubuntu:
>   New
>
> Bug description:
>   This is my first linux experience, I am a totally Newbee. I tried to
>   update my language System, but it did not work. I would like to change
>   from QWERTY to QWERTZ... ;-)
>
>   Thank you! :-)
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 20.04
>   Package: systemd-timesyncd 245.4-4ubuntu3.2
>   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.6
>   AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.1
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CrashReports:
>600:120:125:37:2020-08-14 02:43:47.659610329 +0200:2020-08-14
> 02:43:47.659610329 +0200:/var/crash/_usr_bin_gnome-shell.1000.uploaded
>664:1000:125:0:2020-08-14 02:43:41.139536887 +0200:2020-08-14
> 02:43:41.139536887 +0200:/var/crash/_usr_bin_gnome-shell.1000.upload
>640:1000:125:30803273:2020-08-14 02:43:39.603530645 +0200:2020-08-14
> 02:43:41.139536887 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
>600:0:125:315407:2020-08-14 16:26:15.810850381 +0200:2020-08-14
> 16:26:16.810850381 +0200:/var/crash/systemd.0.crash
>600:0:125:315427:2020-08-14 16:26:15.790850400 +0200:2020-08-14
> 16:26:16.790850400 +0200:/var/crash/systemd-timesyncd.0.crash
>   Date: Fri Aug 14 16:26:16 2020
>   DuplicateSignature:
>package:systemd-timesyncd:245.4-4ubuntu3.2
>Setting up cups (2.3.1-9ubuntu1.1) ...
>   Log started: 2020-08-14  16:26:16
>dpkg: error processing package systemd-timesyncd (--configure):
> package systemd-timesyncd is already installed and configured
>   ErrorMessage: package systemd-timesyncd is already installed and
> configured
>   InstallationDate: Installed on 2020-08-14 (0 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal,
> 3.8.2-0ubuntu2
>   PythonDetails: N/A
>   RelatedPackageVersions:
>dpkg 1.19.7ubuntu3
>apt  2.0.2ubuntu0.1
>   SourcePackage: dpkg
>   Title: package systemd-timesyncd 245.4-4ubuntu3.2 failed to
> install/upgrade: package systemd-timesyncd is already installed and
> configured
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1891663/+subscriptions
>

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

Title:
  package systemd-timesyncd 245.4-4ubuntu3.2 failed to install/upgrade:
  package systemd-timesyncd is already installed and configured

Status in apt package in Ubuntu:
  New

Bug description:
  This is my first linux experience, I am a totally Newbee. I tried to
  update my language System, but it did not work. I would like to change
  from QWERTY to QWERTZ... ;-)

  Thank you! :-)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: systemd-timesyncd 245.4-4ubuntu3.2
  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.6
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   600:120:125:37:2020-08-14 02:43:47.659610329 +0200:2020-08-14 
02:43:47.659610329 +0200:/var/crash/_usr_bin_gnome-shell.1000.uploaded
   664:1000:125:0:2020-08-14 02:43:41.139536887 +0200:2020-08-14 
02:43:41.139536887 +0200:/var/crash/_usr_bin_gnome-shell.1000.upload
   640:1000:125:30803273:2020-08-14 02:43:39.603530645 +0200:2020-08-14 
02:43:41.139536887 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
   600:0:125:315407:2020-08-14 16:26:15.810850381 +0200:2020-08-14 
16:26:16.810850381 +0200:/var/crash/systemd.0.crash
   600:0:125:315427:2020-08-14 16:26:15.790850400 +0200:2020-08-14 
16:26:16.790850400 +0200:/var/crash/systemd-timesyncd.0.crash
  Date: Fri Aug 14 16:26:16 2020
  DuplicateSignature:
   package:systemd-timesyncd:245.4-4ubuntu3.2
   Setting up cups (2.3.1-9ubuntu1.1) ...
  Log started: 2020-08-14  16:26:16
   dpkg: error processing package systemd-timesyncd (--configure):
package systemd-timesyncd is already 

[Touch-packages] [Bug 1891479] Re: pycurl ftbfs in focal (wait-deps)

[Timo Aaltonen]

Hello Matthias, or anyone else affected,

Accepted pycurl into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/pycurl/7.43.0.2-1ubuntu6 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-focal

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

Title:
  pycurl ftbfs in focal (wait-deps)

Status in pycurl package in Ubuntu:
  Confirmed
Status in pycurl source package in Focal:
  Fix Committed

Bug description:
  [SRU Justification]
  This package is unbuildable due to unsatisfiable build-dependencies, as seen 
in a focal test rebuild:
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19799602

  Missing build dependencies: python-sphinx

  This makes the package unsupportable in the event a security update
  needs to be applied.

  [Test case]
  1. let the package attempt to build in focal
  2. check if it succeeds.

  [Regression potential]
  Because the missing build-dependency is python-sphinx, which is only used for 
building the package documentation, the risk of regression is confined to a 
misbuild of the documentation.  Regardless, this package will be held in 
-proposed because the runtime impact of a FTBFS is non-existent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1891479/+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 1891740] Re: Indicator Applet Crashes with unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

[Mister X]

I added some debugging output to the DateTime class to create stacktrace
when a DateTime is assigned whose `m_dt` field is a `nullptr`.

The following is the stack trace when this happens:
./indicator-datetime-service(_ZN5unity9indicator8datetime8DateTimeaSERKS2_+0x45)[0x55abe5d8ba6f]
./indicator-datetime-service(_ZN5unity9indicator8datetime9EdsEngine4Impl15get_appointmentEP11_ECalClientRSt10shared_ptrI13_GCancellableEP14_ECalComponentP10_GTimeZone+0x1c4)[0x55abe5d9210f]
./indicator-datetime-service(_ZN5unity9indicator8datetime9EdsEngine4Impl20add_event_to_subtaskEP14_ECalComponentPNS3_13ClientSubtaskEP10_GTimeZone+0x9c)[0x55abe5d92ce3]
./indicator-datetime-service(_ZN5unity9indicator8datetime9EdsEngine4Impl24on_event_fetch_list_doneEPv+0x21c)[0x55abe5d9171f]
./indicator-datetime-service(_ZN5unity9indicator8datetime9EdsEngine4Impl24fetch_detached_instancesEP8_GObjectP13_GAsyncResultPv+0xe5)[0x55abe5d91221]
./indicator-datetime-service(_ZN5unity9indicator8datetime9EdsEngine4Impl29on_event_generated_list_readyEPv+0x26)[0x55abe5d9131f]
/lib/x86_64-linux-gnu/libecal-2.0.so.1(+0x25d85)[0x7f2834aedd85]
/lib/x86_64-linux-gnu/libecal-2.0.so.1(+0x2d204)[0x7f2834af5204]
/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_simple_async_result_complete+0x86)[0x7f28346405c6]
/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xa068f)[0x7f283464068f]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x14e)[0x7f2834468e8e]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x52240)[0x7f2834469240]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x83)[0x7f2834469533]
./indicator-datetime-service(main+0x59b)[0x55abe5d5dffb]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x7f28340450b3]
./indicator-datetime-service(_start+0x2e)[0x55abe5d5ccee]

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

Title:
  Indicator Applet Crashes with
  unity::indicator::datetime::DateTime::get() const: assertion failed:
  (m_dt)

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  # Problem
  When the calendar is synced to a Google calendar that contains "task" 
entries, the indicator applet crashes. These entries are not shown in 
evolution/gnome-calendar either, so this issue might originate in some library 
code.

  # Error Message
  The date-time indicator crashes with the following error message when started 
in the terminal:
  
Indicator-Datetime:ERROR:/build/indicator-datetime-SpDTj1/indicator-datetime-15.10+20.04.20200217/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
  Bail out! 
Indicator-Datetime:ERROR:/build/indicator-datetime-SpDTj1/indicator-datetime-15.10+20.04.20200217/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

  # Steps to reproduce
  - Create a "task" in your Google calendar
  - Sync the Google account with the calendar using the Online Accounts 
application
  - the indicator applet will crash as soon as the data is synced

  # Version
  I am using the indicator applet version 15.10+20.04.20200217-0ubuntu1 on 
Ubuntu 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1891740/+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 1891740] Re: Indicator Applet Crashes with unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

[Mister X]

Ah, I see the comment box breaks lines. I add it as an attachment here.

** Attachment added: "stack.txt"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1891740/+attachment/5401678/+files/stack.txt

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

Title:
  Indicator Applet Crashes with
  unity::indicator::datetime::DateTime::get() const: assertion failed:
  (m_dt)

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  # Problem
  When the calendar is synced to a Google calendar that contains "task" 
entries, the indicator applet crashes. These entries are not shown in 
evolution/gnome-calendar either, so this issue might originate in some library 
code.

  # Error Message
  The date-time indicator crashes with the following error message when started 
in the terminal:
  
Indicator-Datetime:ERROR:/build/indicator-datetime-SpDTj1/indicator-datetime-15.10+20.04.20200217/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
  Bail out! 
Indicator-Datetime:ERROR:/build/indicator-datetime-SpDTj1/indicator-datetime-15.10+20.04.20200217/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

  # Steps to reproduce
  - Create a "task" in your Google calendar
  - Sync the Google account with the calendar using the Online Accounts 
application
  - the indicator applet will crash as soon as the data is synced

  # Version
  I am using the indicator applet version 15.10+20.04.20200217-0ubuntu1 on 
Ubuntu 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1891740/+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 1891634] Re: $ ubuntu-bug /var/crash/.crash does not work

[Tuomas Heino]

** Description changed:

  [Impact]
  1. When trying to send a report manually, you can not
- 2. When next possibly unrelated crash of same process happens, .crash 
gets overwritten even if .crash.upload exists (= upload not yet 
completed?)
- 3. When trying to copy-paste the stacktrace as text, UI does not have such 
functionality (and does not tell the user that .crash is just a text file)
+ 2. When next possibly unrelated crash of same process happens, .crash 
gets overwritten even when .crash.upload exists (upload not yet completed)
+ 3. When trying to copy-paste the stacktrace as text, UI does not have such 
functionality
  
  [Test Case]
  Start Ubuntu
  Open terminal
  $ ubuntu-bug /var/crash/.crash # does not appear to send anything to 
errors.ubuntu.com, when NetworkManager claims missing network connectivity.
  
  In multihomed host renderer: networkd in netplan with some of the
  redundant bridge members lacking physical connectivity and/or offline
  usb tether backup networks tend to result in perfectly functional state
  = "routable" network that many ubuntu GUI tools refuse to work with
  anyway, is apport one of them?
  
  Similarly to bug #1825822 I attempted to
  
- $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash but after clicking
- "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not change
- into ".uploaded". And before the "Send" there does not appear to be any
- obvious way to copy the report as text somewhere.
+ $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash # but after
+ clicking "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not
+ change into ".uploaded". And before the "Send" the UI does not contain
+ any obvious way to copy the report as text somewhere (note: just copy
+ the .crash which is text format with base64 parts anyway, at least for
+ now).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.6
  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.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 
12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload
   640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 
13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:28:31 2020
  InstallationDate: Installed on 2020-04-10 (125 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  $ ubuntu-bug /var/crash/.crash does not work

Status in apport package in Ubuntu:
  New

Bug description:
  [Impact]
  1. When trying to send a report manually, you can not
  2. When next possibly unrelated crash of same process happens, .crash 
gets overwritten even when .crash.upload exists (upload not yet completed)
  3. When trying to copy-paste the stacktrace as text, UI does not have such 
functionality

  [Test Case]
  Start Ubuntu
  Open terminal
  $ ubuntu-bug /var/crash/.crash # does not appear to send anything to 
errors.ubuntu.com, when NetworkManager claims missing network connectivity.

  In multihomed host renderer: networkd in netplan with some of the
  redundant bridge members lacking physical connectivity and/or offline
  usb tether backup networks tend to result in perfectly functional
  state = "routable" network that many ubuntu GUI tools refuse to work
  with anyway, is apport one of them?

  Similarly to bug #1825822 I attempted to

  $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash # but after
  clicking "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not
  change into ".uploaded". And before the "Send" the UI does not contain
  any obvious way to copy the report as text somewhere (note: just copy
  the .crash which is text format with base64 parts anyway, at least for
  now).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.6
  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.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 
12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload
   640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 
13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:28:31 2020
  InstallationDate: Installed on 2020-04-10 (125 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 

[Touch-packages] [Bug 1891740] Re: Indicator Applet Crashes with unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

[Mister X]

After investigating a bit more, the issue is probably that
`e_cal_component_get_dtstart` returns a nullptr for a call in
get_appointment in EdsEngine.

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

Title:
  Indicator Applet Crashes with
  unity::indicator::datetime::DateTime::get() const: assertion failed:
  (m_dt)

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  # Problem
  When the calendar is synced to a Google calendar that contains "task" 
entries, the indicator applet crashes. These entries are not shown in 
evolution/gnome-calendar either, so this issue might originate in some library 
code.

  # Error Message
  The date-time indicator crashes with the following error message when started 
in the terminal:
  
Indicator-Datetime:ERROR:/build/indicator-datetime-SpDTj1/indicator-datetime-15.10+20.04.20200217/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
  Bail out! 
Indicator-Datetime:ERROR:/build/indicator-datetime-SpDTj1/indicator-datetime-15.10+20.04.20200217/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

  # Steps to reproduce
  - Create a "task" in your Google calendar
  - Sync the Google account with the calendar using the Online Accounts 
application
  - the indicator applet will crash as soon as the data is synced

  # Version
  I am using the indicator applet version 15.10+20.04.20200217-0ubuntu1 on 
Ubuntu 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1891740/+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 1891634] Re: $ ubuntu-bug /var/crash/.crash does not work

[Tuomas Heino]

Also https://errors.ubuntu.com/user/$(sudo cat /var/lib/whoopsie
/whoopsie-id) claims "No errors have been reported from this system",
which is consistent with no ".uploaded" files appearing.

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

Title:
  $ ubuntu-bug /var/crash/.crash does not work

Status in apport package in Ubuntu:
  New

Bug description:
  [Impact]
  1. When trying to send a report manually, you can not
  2. When next possibly unrelated crash of same process happens, .crash 
gets overwritten even when .crash.upload exists (upload not yet completed)
  3. When trying to copy-paste the stacktrace as text, UI does not have such 
functionality

  [Test Case]
  Start Ubuntu
  Open terminal
  $ ubuntu-bug /var/crash/.crash # does not appear to send anything to 
errors.ubuntu.com, when NetworkManager claims missing network connectivity.

  In multihomed host renderer: networkd in netplan with some of the
  redundant bridge members lacking physical connectivity and/or offline
  usb tether backup networks tend to result in perfectly functional
  state = "routable" network that many ubuntu GUI tools refuse to work
  with anyway, is apport one of them?

  Similarly to bug #1825822 I attempted to

  $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash # but after
  clicking "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not
  change into ".uploaded". And before the "Send" the UI does not contain
  any obvious way to copy the report as text somewhere (note: just copy
  the .crash which is text format with base64 parts anyway, at least for
  now).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.6
  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.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 
12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload
   640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 
13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:28:31 2020
  InstallationDate: Installed on 2020-04-10 (125 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891634/+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 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

[Ilia]

CPU usage 100%
/var/log/syslog now takes more than 10GiB and grows...

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

Title:
  systemd 100% cpu usage apport-autoreport.service: Failed with result
  'start-limit-hit'

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  after upgrade from Ubuntu 20.04 to 20.10  
  seeing systemd use 100% cpu forever


  top

top - 10:16:19 up 20 min,  1 user,  load average: 3.91, 4.28, 3.39
Tasks: 332 total,   2 running, 330 sleeping,   0 stopped,   0 zombie
%Cpu(s): 18.7 us,  6.4 sy, 11.9 ni, 62.2 id,  0.0 wa,  0.0 hi,  0.8 si, 
 0.0 st
MiB Mem :  15917.6 total,   8553.4 free,   2604.3 used,   4759.9 
buff/cache
MiB Swap:   2048.0 total,   2048.0 free,  0.0 used.  12633.7 avail 
Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ 
COMMAND  
  1 root  20   0  177316  12252   8684 R 100.0   0.1  15:01.25 
systemd  
   4636 kush  39  19  633796 176152  16360 S  98.3   1.1  17:51.56 
tracker-miner-f  
820 message+  20   0   10740   6452   4212 S  39.8   0.0   6:19.06 
dbus-daemon  
316 root  19  -1  535916 322896 320824 S  15.3   2.0   3:16.41 
systemd-journal  
844 syslog20   0  221136   5840   3920 S  13.6   0.0   2:14.52 
rsyslogd 
858 root  20   0   83708  74124   7568 S  12.7   0.5   2:06.98 
systemd-logind   
  5 root  20   0   0  0  0 I   3.4   0.0   0:05.01 
kworker/0:0-events   
  35566 kush  20   0 3850088 588344 262192 S   2.5   3.6   0:30.48 
MainThread   
   5626 kush  20   0 5004788 260876  93400 S   1.7   1.6   3:05.19 
gnome-shell  
   7033 kush  20   0  869792  66440  44272 S   1.7   0.4   0:06.05 
gnome-terminal-  
  36790 kush  20   0 2525432 156636  98568 S   1.7   1.0   0:04.99 
Web Content  
957 root  20   0 1556196  45044  24284 S   0.8   0.3   0:02.48 
containerd   
   1038 root  20   0   10460   4412   3300 S   0.8   0.0   0:00.16 
fancontrol   



  
sudo tail -n 100 /var/log/syslog
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.

[Touch-packages] [Bug 1891740] [NEW] Indicator Applet Crashes with unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

[Mister X]

Public bug reported:

# Problem
When the calendar is synced to a Google calendar that contains "task" entries, 
the indicator applet crashes. These entries are not shown in 
evolution/gnome-calendar either, so this issue might originate in some library 
code.

# Error Message
The date-time indicator crashes with the following error message when started 
in the terminal:
Indicator-Datetime:ERROR:/build/indicator-datetime-SpDTj1/indicator-datetime-15.10+20.04.20200217/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
Bail out! 
Indicator-Datetime:ERROR:/build/indicator-datetime-SpDTj1/indicator-datetime-15.10+20.04.20200217/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

# Steps to reproduce
- Create a "task" in your Google calendar
- Sync the Google account with the calendar using the Online Accounts 
application
- the indicator applet will crash as soon as the data is synced

# Version
I am using the indicator applet version 15.10+20.04.20200217-0ubuntu1 on Ubuntu 
20.04.

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Indicator Applet Crashes with
  unity::indicator::datetime::DateTime::get() const: assertion failed:
  (m_dt)

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  # Problem
  When the calendar is synced to a Google calendar that contains "task" 
entries, the indicator applet crashes. These entries are not shown in 
evolution/gnome-calendar either, so this issue might originate in some library 
code.

  # Error Message
  The date-time indicator crashes with the following error message when started 
in the terminal:
  
Indicator-Datetime:ERROR:/build/indicator-datetime-SpDTj1/indicator-datetime-15.10+20.04.20200217/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
  Bail out! 
Indicator-Datetime:ERROR:/build/indicator-datetime-SpDTj1/indicator-datetime-15.10+20.04.20200217/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

  # Steps to reproduce
  - Create a "task" in your Google calendar
  - Sync the Google account with the calendar using the Online Accounts 
application
  - the indicator applet will crash as soon as the data is synced

  # Version
  I am using the indicator applet version 15.10+20.04.20200217-0ubuntu1 on 
Ubuntu 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1891740/+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 1891745] [NEW] Xorg crashed with SIGSEGV in dixSaveScreens()

[Tuomas Heino]

Public bug reported:

This instance happened after lockscreen, as such may be suspend-resume
related. On the other hand at least 0 and 10 parts on backtrace appear
similar to bug #1891636

While this appears to be a recent regression, DpkgLog.txt doesn't
contain xorg references. Could it be related to kernel upgrades then, or
just happened to slip by undetected after earlier upgrades?

 [ 81555.574] (EE) Backtrace:
 [ 81555.577] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x560d53a2ee0c]
 [ 81555.578] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 
[0x7fb62037b41f]
 [ 81555.578] (EE) unw_get_proc_name failed: no unwind info found [-10]
 [ 81555.578] (EE) 2: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb524a0]
 [ 81555.578] (EE) unw_get_proc_name failed: no unwind info found [-10]
 [ 81555.579] (EE) 3: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb52750]
 [ 81555.579] (EE) unw_get_proc_name failed: no unwind info found [-10]
 [ 81555.579] (EE) 4: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb4bb00]
 [ 81555.579] (EE) unw_get_proc_name failed: no unwind info found [-10]
 [ 81555.579] (EE) 5: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb4bba0]
 [ 81555.579] (EE) 6: /usr/lib/xorg/Xorg (dixSaveScreens+0x1e6) [0x560d538fceb6]
 [ 81555.580] (EE) 7: /usr/lib/xorg/Xorg (mieqProcessInputEvents+0x149) 
[0x560d53a0e779]
 [ 81555.580] (EE) 8: /usr/lib/xorg/Xorg (ProcessInputEvents+0x1d) 
[0x560d5390b65d]
 [ 81555.580] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x2c9) 
[0x560d538cdeb9]
 [ 81555.580] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x560d538d1fd4]
 [ 81555.580] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) 
[0x7fb6201990b3]
 [ 81555.581] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2e) [0x560d538bba3e]
 [ 81555.581] (EE) 
 [ 81555.581] (EE) Segmentation fault at address 0x0
 [ 81555.581] (EE) 
 Fatal server error:
 [ 81555.581] (EE) Caught signal 11 (Segmentation fault). Server aborting
 [ 81555.581] (EE) 
 [ 81555.581] (EE) 

P.S. Don't currently have a remote debugging setup since all the other
hosts nearby are headless.

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.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 15 13:17:57 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
InstallationDate: Installed on 2020-04-10 (126 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B WS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 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 N/A
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

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

Title:
  Xorg crashed with SIGSEGV in 

[Touch-packages] [Bug 1891634] Re: $ ubuntu-bug /var/crash/.crash does not work

[Tuomas Heino]

** Description changed:

  [Impact]
  1. When trying to send a report manually, you can not
- 2. When trying to copy-paste the stacktrace as text, you can not
+ 2. When next possibly unrelated crash of same process happens, .crash 
gets overwritten even if .crash.upload exists (= upload not yet 
completed?)
+ 3. When trying to copy-paste the stacktrace as text, UI does not have such 
functionality (and does not tell the user that .crash is just a text file)
  
  [Test Case]
  Start Ubuntu
  Open terminal
- $ ubuntu-bug /var/crash/.crash does not appear to send anything to 
errors.ubuntu.com, when NetworkManager claims missing network connectivity.
+ $ ubuntu-bug /var/crash/.crash # does not appear to send anything to 
errors.ubuntu.com, when NetworkManager claims missing network connectivity.
  
  In multihomed host renderer: networkd in netplan with some of the
  redundant bridge members lacking physical connectivity and/or offline
  usb tether backup networks tend to result in perfectly functional state
  = "routable" network that many ubuntu GUI tools refuse to work with
  anyway, is apport one of them?
  
  Similarly to bug #1825822 I attempted to
  
  $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash but after clicking
  "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not change
  into ".uploaded". And before the "Send" there does not appear to be any
  obvious way to copy the report as text somewhere.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.6
  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.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 
12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload
   640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 
13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:28:31 2020
  InstallationDate: Installed on 2020-04-10 (125 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  $ ubuntu-bug /var/crash/.crash does not work

Status in apport package in Ubuntu:
  New

Bug description:
  [Impact]
  1. When trying to send a report manually, you can not
  2. When next possibly unrelated crash of same process happens, .crash 
gets overwritten even when .crash.upload exists (upload not yet completed)
  3. When trying to copy-paste the stacktrace as text, UI does not have such 
functionality

  [Test Case]
  Start Ubuntu
  Open terminal
  $ ubuntu-bug /var/crash/.crash # does not appear to send anything to 
errors.ubuntu.com, when NetworkManager claims missing network connectivity.

  In multihomed host renderer: networkd in netplan with some of the
  redundant bridge members lacking physical connectivity and/or offline
  usb tether backup networks tend to result in perfectly functional
  state = "routable" network that many ubuntu GUI tools refuse to work
  with anyway, is apport one of them?

  Similarly to bug #1825822 I attempted to

  $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash # but after
  clicking "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not
  change into ".uploaded". And before the "Send" the UI does not contain
  any obvious way to copy the report as text somewhere (note: just copy
  the .crash which is text format with base64 parts anyway, at least for
  now).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.6
  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.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 
12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload
   640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 
13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:28:31 2020
  InstallationDate: Installed on 2020-04-10 (125 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1868915] Re: [focal] nm-online -s --timeout=10 timeout every time

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  [focal] nm-online -s --timeout=10 timeout every time

Status in MAAS:
  Invalid
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Also created bug on upstream :
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398

  
  This issue will cause "NetworkManager-wait-online.service: Failed with result 
'exit-code'."
  And cloud-init.service is counting on this service for network status.

  So this issue will finally cause MaaS deploying failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1 [modified: 
lib/systemd/system/NetworkManager-wait-online.service]
  ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8
  Uname: Linux 5.4.0-1002-oem x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  Date: Wed Mar 25 12:43:13 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09
  IfupdownConfig: source /etc/network/interfaces.d/*.cfg
  InstallationDate: Installed on 2020-03-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200316-08:40
  IpRoute:
   default via 192.168.101.1 dev eno1 proto static metric 100
   10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200
   169.254.0.0/16 dev eno1 scope link metric 1000
   192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 
100
  NetDevice.bonding_masters:
   Error: command ['udevadm', 'info', '--query=all', '--path', 
'/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device 
"/sys/class/net/bonding_masters": No such device

   X: INTERFACE_MAC=Error: command ['cat', 
'/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: 
/sys/class/net/bonding_masters/address: Not a directory
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL  AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE  FILENAME
   netplan-eno1  10838d80-caeb-349e-ba73-08ed16d4d666  ethernet  158577  
廿廿年三月廿五日 (週三) 十二時39分37秒  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes eno1activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/run/NetworkManager/system-connections/netplan-eno1.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN
   running  1.22.10  connected  starting  full  enabled disabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1868915/+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 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

[Rex Tsai]

** Changed in: oem-priority
   Status: Confirmed => Fix Committed

** Changed in: oem-priority
   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/1834138

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  Low, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  For the Bionic, This SRU also includes the fix of LP: #1556439, this
  fix is safe and is very low possible to introduce any regression too,
  because it just adds a sink-input/source-output state checking, if the
  sink-input/source-output is unlinking or unlinked, it is useless to
  move it to a new sink/source, furthermore it will trigger an assertion
  that make the pulseaudio crash, adding this check can fix this problem
  (LP: #1556439).

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 1840416] Re: 2.4g wifi connection failed randomly during wpa re-key

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  2.4g wifi connection failed randomly during wpa re-key

Status in OEM Priority Project:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm not sure this issue caused by WIFI AP or WIFI module.
  From log, it looks the tested machine can not get new key from WIFI AP 
randomly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-1030.35-oem 4.15.18
  Uname: Linux 4.15.0-1030-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 16 14:51:12 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-08-14 (2 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  IpRoute:
   default via 10.101.46.1 dev wlp2s0 proto dhcp metric 600 
   10.101.46.0/24 dev wlp2s0 proto kernel scope link src 10.101.46.198 metric 
600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Canonical-2.4GHz-g  f0a4469e-23e9-4899-a498-49a50b3a8e21  wifi  1565938016  
廿十九年八月十六日 (週五) 十四時46分56秒  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/5  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
Canonical-2.4GHz-g  f0a4469e-23e9-4899-a498-49a50b3a8e21  
/org/freedesktop/NetworkManager/ActiveConnection/5 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1840416/+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 1888352] Re: use builtin dump_acpi_tables.py in hookutils

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  New
Status in apport source package in Groovy:
  New

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+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 1883670] Re: Disable IEC958 on HP Thunderbolt Dock

[Rex Tsai]

** Changed in: oem-priority
   Status: Confirmed => Fix Released

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

Title:
  Disable IEC958 on HP Thunderbolt Dock

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On HP Thunderbolt Dock, unusable SPDIF can be selected as output from 
PulseAudio.

  [Fix]
  Disable IEC958 (SPDIF) through ALSA UCM.

  [Test]
  With the UCM applied, `pactl` and audio panel in gnome-control-center no 
longer have SPDIF option.

  [Regression Potential]
  Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883670/+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 1889378] Re: dbus method 'Sleep' not work

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  dbus method 'Sleep' not work

Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  refer to https://salsa.debian.org/utopia-team/network-
  
manager/-/blob/debian/master/introspection/org.freedesktop.NetworkManager.xml#L157

  
  
    
  

  But the network not be deactivated after the Sleep method be called.

  steps:
   1.$ gdbus call --system --dest org.freedesktop.NetworkManager --object-path 
/org/freedesktop/NetworkManager --method org.freedesktop.NetworkManager.Sleep 
true

   2.$ journal ctl ; # see the dbus method be called correctly.
  NetworkManager[843]:   [1596010870.8622] manager: sleep: sleep 
requested (sleeping: no  enabled: yes)
  NetworkManager[843]:   [1596010870.8626] device (p2p-dev-wlp0s20f3): 
state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 
'managed')
  NetworkManager[843]:   [1596010870.8632] manager: NetworkManager state 
is now ASLEEP
  NetworkManager[843]:   [1596010870.8635] audit: op="sleep-control" 
arg="on" pid=2825 uid=0 result="success"

  3. $ ping 8.8.8.8 ; # still work unexpectedly

  Note: this issue can be reproduced on the latest version of network-
  manager source : https://git.launchpad.net/network-
  manager/commit/?id=6e17a2e7ad9453c0afe34dab0e6768ad8ee447c2

  upstream bug:
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/503

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1889378/+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 1891745] Re: Xorg crashed with SIGSEGV in dixSaveScreens()

[Tuomas Heino]

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

Exact reproduction conditions of bug #1891636 and bug #1891745 unknown.
At least OOPS ID 6647d368-df04-11ea-af91-fa163ee63de6 uploaded to 
errors.ubuntu.com now, marking these two as duplicates for now.

** This bug has been marked a duplicate of bug 1891636
   After recent updates Xorg crashes whenever entering Display Settings

** Information type changed from Public to Private

** This bug is no longer a duplicate of bug 1891636
   After recent updates Xorg crashes whenever entering Display Settings
** This bug has been marked a duplicate of bug 1861609
   [focal] Xorg crashed with assertion failure (usually in a VM) at 
[privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and 
call stack comes from DRIMoveBuffersHelper

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

Title:
  Xorg crashed with SIGSEGV in dixSaveScreens()

Status in xorg package in Ubuntu:
  New

Bug description:
  This instance happened after lockscreen, as such may be suspend-resume
  related. On the other hand at least 0 and 10 parts on backtrace appear
  similar to bug #1891636

  While this appears to be a recent regression, DpkgLog.txt doesn't
  contain xorg references. Could it be related to kernel upgrades then,
  or just happened to slip by undetected after earlier upgrades?

   [ 81555.574] (EE) Backtrace:
   [ 81555.577] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) 
[0x560d53a2ee0c]
   [ 81555.578] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 
(funlockfile+0x60) [0x7fb62037b41f]
   [ 81555.578] (EE) unw_get_proc_name failed: no unwind info found [-10]
   [ 81555.578] (EE) 2: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb524a0]
   [ 81555.578] (EE) unw_get_proc_name failed: no unwind info found [-10]
   [ 81555.579] (EE) 3: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb52750]
   [ 81555.579] (EE) unw_get_proc_name failed: no unwind info found [-10]
   [ 81555.579] (EE) 4: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb4bb00]
   [ 81555.579] (EE) unw_get_proc_name failed: no unwind info found [-10]
   [ 81555.579] (EE) 5: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb4bba0]
   [ 81555.579] (EE) 6: /usr/lib/xorg/Xorg (dixSaveScreens+0x1e6) 
[0x560d538fceb6]
   [ 81555.580] (EE) 7: /usr/lib/xorg/Xorg (mieqProcessInputEvents+0x149) 
[0x560d53a0e779]
   [ 81555.580] (EE) 8: /usr/lib/xorg/Xorg (ProcessInputEvents+0x1d) 
[0x560d5390b65d]
   [ 81555.580] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x2c9) 
[0x560d538cdeb9]
   [ 81555.580] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x560d538d1fd4]
   [ 81555.580] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fb6201990b3]
   [ 81555.581] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2e) [0x560d538bba3e]
   [ 81555.581] (EE) 
   [ 81555.581] (EE) Segmentation fault at address 0x0
   [ 81555.581] (EE) 
   Fatal server error:
   [ 81555.581] (EE) Caught signal 11 (Segmentation fault). Server aborting
   [ 81555.581] (EE) 
   [ 81555.581] (EE) 

  P.S. Don't currently have a remote debugging setup since all the other
  hosts nearby are headless.

  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.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 15 13:17:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
  InstallationDate: Installed on 2020-04-10 (126 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  

[Touch-packages] [Bug 1891761] [NEW] Add a way to change the application_id of a toplevel wayland GdkSurface (so LibreOffice can reuse toplevels and get the right task icons in Wayland)

[Amr Ibrahim]

Public bug reported:

This is already committed upstream in GTK 3.24.22:
https://gitlab.gnome.org/GNOME/gtk/-/commit/2b74662b2befebb988b63118c8d7ee8c9d90e736

LibreOffice in a Wayland session uses the same generic icon for its
different apps, so when I have Writer, Calc and Impress open, they all
share the same generic LO icon, which is not a very good experience. The
upstream GTK commit should fix that, however, I have not tested it.

The reason why I'm using Wayland in Ubuntu 20.04 is that I have a second
4K UHD monitor and fractional scaling + 4K UHD resolution is unusable in
X11, so I'm kind of forced to use Wayland for fractional scaling. See
bug #1890802.

So I hope this fix could be committed in Ubuntu 20.04 to improve the
LibreOffice experience in Wayland.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libgtk-3-0 3.24.20-0ubuntu1
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.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 15 17:14:07 2020
InstallationDate: Installed on 2020-04-26 (111 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gtk+3.0
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Add a way to change the application_id of a toplevel wayland
  GdkSurface (so LibreOffice can reuse toplevels and get the right task
  icons in Wayland)

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  This is already committed upstream in GTK 3.24.22:
  
https://gitlab.gnome.org/GNOME/gtk/-/commit/2b74662b2befebb988b63118c8d7ee8c9d90e736

  LibreOffice in a Wayland session uses the same generic icon for its
  different apps, so when I have Writer, Calc and Impress open, they all
  share the same generic LO icon, which is not a very good experience.
  The upstream GTK commit should fix that, however, I have not tested
  it.

  The reason why I'm using Wayland in Ubuntu 20.04 is that I have a
  second 4K UHD monitor and fractional scaling + 4K UHD resolution is
  unusable in X11, so I'm kind of forced to use Wayland for fractional
  scaling. See bug #1890802.

  So I hope this fix could be committed in Ubuntu 20.04 to improve the
  LibreOffice experience in Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgtk-3-0 3.24.20-0ubuntu1
  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.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 15 17:14:07 2020
  InstallationDate: Installed on 2020-04-26 (111 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1891761/+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 986779] Re: ubuntu-bug lacks an option for collection stack trace of running process (infinite loop analysis)

[Tuomas Heino]

Actually
https://git.launchpad.net/ubuntu/+source/apport/commit/apport/ui.py?h=ubuntu/quantal=5080c104ebb3a02c4f16a3f6646449db8c72b545
lists a fix (--hanging) for this being available since quantal.

** Tags removed: focal

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

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

Title:
  ubuntu-bug lacks an option for collection stack trace of running
  process (infinite loop analysis)

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Wishlist: When ubuntu-bug is asked to send a bug on PID, it should
  check whether the PID shows symptoms of being in an infinite loop and
  if so, include stack trace of the process to the bug report or ask the
  user whether he would like to include details needed for retracing in
  the bug report.

  In many cases simply sending SEGV signal to the process does indeed
  manage to generate retraceable coredumps when
  /proc/sys/kernel/core_pattern points to apport, but such SEGVs can be
  masked for several reasons.

  Bug 986774 is an example of a bug report which would benefit from
  having this kind of feature in apport/ubuntu-bug - in that case
  pasuspender seems to be masking the apport SEGV handling.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: apport 2.0.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportLog:
   
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  Date: Sun Apr 22 10:01:02 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120112)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IE:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/986779/+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 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  [Impact]

   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).

   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.

  [Test Case]

   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend

   After resume from suspend, the Wi-Fi functiall still is normal.

   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633

  [Regression Potential]

   * No potential regressions.

  [Other Info]
   
   * None

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1891632/+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 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  unattended-upgrades does not block shutdown of system, as it is
  designed to

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  Triaged
Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in apt source package in Zesty:
  Won't Fix
Status in unattended-upgrades source package in Zesty:
  Won't Fix

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
    Installed: 0.90
    Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

  * APT SRU *
  [Impact]
  Stopping apt-daily-upgrade.service terminates dpkg and friends by sending the 
signals to all processes in the cgroup, and will send KILL quickly after.

  [Test case]
  Start apt-daily-upgrade.service and stop it while unattended-upgrades is 
running.

  The upgrade should run to completion or a safe exit point as long as
  it takes less than about 900s (which is the timeout for sending kill).

  [Regression potential]
  Leftover processes might remain in the apt-daily-upgrade cgroup if the 
postinst scripts or some apt hooks do something funny.

  Shutdown might take longer due to the 900 second timeout.

  * unattended-upgrades SRU

  [Impact]

   * Undattended-upgrades does not stop quickly gracefully when shutdown/reboot 
is initiated by the user.
   * The fix is performing the updates in minimal package sets and allow 
gracefully stopping between those steps when unattended-upgrades.service sends 
a TERM signal to running u-u. The signal is sent on receiving 
PrepareForShutdown() from logind 
(https://www.freedesktop.org/wiki/Software/systemd/inhibit/) to stop 
unattended-upgrades a bit earlier than the shutdown process starts (LP: 
#1803137).

  [Test Case]

  * Configure the system to have several 20+ packages upgradable by
  unattended-upgrades. One easy way of setting this up is starting with
  a system where packages from -security are installed but packages from
  -updates are not and enabling -updates in u-u:

# echo 'Unattended-Upgrade::Allowed-Origins::
  "${distro_id}:${distro_codename}-updates";' > /etc/apt/apt.conf.d
  /51unattended-upgrades-updates-too

  * Pre-download upgrades
# unattended-upgraded --download-only

  * Trigger unattended-upgrades run:
# service apt-daily-upgrade start

  * Shutdown the system from a graphical user session or by executing
# dbus-send --system --print-reply --dest=org.freedesktop.login1 
/org/freedesktop/login1 "org.freedesktop.login1.Manager.Reboot" boolean:false

   * Observe the system unattended-upgrades being gracefully stopped,
  checking /var/log/unattended-upgrades/unattended-upgrades.log. There
  should be packages left to be upgraded.

  [Regression Potential]

  On Xenial (with Unity) starting shutdown from the graphical session
  does not log the user out nor show any progress on the shutdown until
  the inhibition timer expires which is confusing. Users should be
  logged out on PrepareForShutdown() (LP: #1803581).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+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 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  Fix Released
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New

Bug description:
  [Impact]

   * It is a very bad user experience that the WiFi device is recognized
  as an Ethernet device making Ubuntu users unable to connect to WiFi
  network.

  [Test Case]

   * Find some laptop that can reduplicate this issue.
   * Keep rebooting the system until you see this issue.
   * Usually this issue can be reduplicated within 10 reboot cycles on the 
right laptop.

  [Regression Potential]

   * No trivial regression.

  [Other Info]
   
   * network-manager_1.2.6-0ubuntu0.16.04.2.debdiff (comment #8) is for xenial

  [Original Bug Description]

  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged--

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

  fix need landing LP: #1645698

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1647283/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  missing hardware/runtime info when reporing linux-firmware bugs via
  apport

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Bionic:
  Invalid
Status in linux-firmware source package in Eoan:
  Invalid
Status in apport source package in Focal:
  Fix Released
Status in linux-firmware source package in Focal:
  Invalid

Bug description:
  Updated Description to match SRU requirements for bionic

  [Impact]
  linux-firmware doesn't install any package hooks for apport, so it will only 
carry some default items leaving hardware list, kernel messages unattached. 
Suggest symlink /usr/share/apport/package-hooks/source_linux-firmware.py to 
source_linux.py as other linux image debs do in bug 1847967.

  [Test Case]
  1) On an Ubuntu 18.04 LTS system run 'apport-cli linux-firmware'.
  2) Choose 'View report'
  3) Observe that 'ProcFB' is not collected

  With the version of apport from -proposed 'ProcFB' will be in the
  report.

  
  [Regression Potential]
  Very limited, as we are just adding a symlink from linux-firmware to the 
linux source package hook. this change has been available in Focal and Groovy 
without problem


  Original Description
  
  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 10 19:15:15 2020
  Dependencies:

  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  PackageArchitecture: allSourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Dependencies:

  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  MachineType: Apple Inc. MacBookPro11,1
  NonfreeKernelModules: wl
  Package: linux-firmware
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic 
root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet 
splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/13/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 156.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1864813] Re: As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once.

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  As there is not built-in speaker, and not any output, the dummy output
  in g-c-c will disappear after plug headset once.

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  The dummy output in gnome-contol-center (g-c-c) will exists if

  - no built-in speaker
  - no headphone/earphone plugged
  - using display (like VGA, DVI) without audio out is plugged.

  However, in bionic, it will disappear as the headset is plugged and selected.
  After it disappears, a reboot won't make it appear again.

  bionic:
gnome-control-center: 1:3.28.2-0ubuntu0.18.04.6
pulseaudio: 1:11.1-1ubuntu7.4

  In Focal, dummy output won't disappear.

  focal:
    pulseaudio 1:13.0-3ubuntu2
    gnome-control-center 1:3.35.91-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1864813/+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 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:

  
  Summary
  ===

  Internal speakers work as expected, but when plugging headphones
  through the 3.5mm jack, the "Select Audio Device" panel doesn't show
  up (it normally shows up to allow user to select what kind of device
  has been plugged in, be it headphones, microphone or headset). In the
  Sound Settings, the Output Device automatically switches to
  "Headphones - sof-hda-dsp", but no sound can be heard even though the
  vumeter in the Sound Settings moves!

  Steps to reproduce
  ==

  1. Install focal beta
  2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
  3. Plug headphones in jack 3.5mm interface

  Expected Results
  

  - In Sound Settings, the headphones are automatically selected as output 
device
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound
  - Sound can be heard through the headphones

  
  Actual results
  ==

  - In Sound Settings, the headphones are automatically selected as output 
device (OK)
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound (OK)
  - No sound can be heard (Not OK)

  Attached are output of `pactl info` and `pactl list` before and after
  plugging headphones, while playing a tune on Bandcamp in Firefox.

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device: 
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 5590
  bios-version: 1.1.0
  CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
  kernel-version: 5.4.0-21-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1768 F pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
   /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 16:33:27 2020
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1871329/+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 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  [regression] Logitech M337 mice are automatically disconnected after
  connected

Status in Bluez Utilities:
  Confirmed
Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Invalid

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1773897/+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 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

[Aaron Lichtman]

I am experiencing this issue on Ubuntu 20.10.

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

Title:
  systemd 100% cpu usage apport-autoreport.service: Failed with result
  'start-limit-hit'

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  after upgrade from Ubuntu 20.04 to 20.10  
  seeing systemd use 100% cpu forever


  top

top - 10:16:19 up 20 min,  1 user,  load average: 3.91, 4.28, 3.39
Tasks: 332 total,   2 running, 330 sleeping,   0 stopped,   0 zombie
%Cpu(s): 18.7 us,  6.4 sy, 11.9 ni, 62.2 id,  0.0 wa,  0.0 hi,  0.8 si, 
 0.0 st
MiB Mem :  15917.6 total,   8553.4 free,   2604.3 used,   4759.9 
buff/cache
MiB Swap:   2048.0 total,   2048.0 free,  0.0 used.  12633.7 avail 
Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ 
COMMAND  
  1 root  20   0  177316  12252   8684 R 100.0   0.1  15:01.25 
systemd  
   4636 kush  39  19  633796 176152  16360 S  98.3   1.1  17:51.56 
tracker-miner-f  
820 message+  20   0   10740   6452   4212 S  39.8   0.0   6:19.06 
dbus-daemon  
316 root  19  -1  535916 322896 320824 S  15.3   2.0   3:16.41 
systemd-journal  
844 syslog20   0  221136   5840   3920 S  13.6   0.0   2:14.52 
rsyslogd 
858 root  20   0   83708  74124   7568 S  12.7   0.5   2:06.98 
systemd-logind   
  5 root  20   0   0  0  0 I   3.4   0.0   0:05.01 
kworker/0:0-events   
  35566 kush  20   0 3850088 588344 262192 S   2.5   3.6   0:30.48 
MainThread   
   5626 kush  20   0 5004788 260876  93400 S   1.7   1.6   3:05.19 
gnome-shell  
   7033 kush  20   0  869792  66440  44272 S   1.7   0.4   0:06.05 
gnome-terminal-  
  36790 kush  20   0 2525432 156636  98568 S   1.7   1.0   0:04.99 
Web Content  
957 root  20   0 1556196  45044  24284 S   0.8   0.3   0:02.48 
containerd   
   1038 root  20   0   10460   4412   3300 S   0.8   0.0   0:00.16 
fancontrol   



  
sudo tail -n 100 /var/log/syslog
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

[Aaron Lichtman]

$ systemctl status appoprt-autoreport.service
● apport-autoreport.service - Process error reports when automatic reporting is 
enabled
 Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static)
 Active: activating (start) since Sat 2020-08-15 12:43:54 CDT; 6ms ago
TriggeredBy: ● apport-autoreport.path
   Main PID: 8019 (whoopsie-upload)
  Tasks: 1 (limit: 38362)
 Memory: 0B
 CGroup: /system.slice/apport-autoreport.service
 └─8019 /usr/bin/python3 /usr/share/apport/whoopsie-upload-all

Aug 15 12:43:54 arctic systemd[1]: Starting Process error reports when 
automatic reporting is enabled...
Aug 15 12:43:54 arctic whoopsie-upload-all[8019]: 
/var/crash/_usr_bin_blueman-assistant.1000.crash already marked for upload, 
skipping
Aug 15 12:43:54 arctic whoopsie-upload-all[8019]: 
/var/crash/_usr_share_spotify_spotify.1000.crash already marked for upload, 
skipping
Aug 15 12:43:54 arctic whoopsie-upload-all[8019]: 
/var/crash/_usr_share_discord_Discord.1000.crash already marked for upload, 
skipping
Aug 15 12:43:54 arctic whoopsie-upload-all[8019]: All reports processed
Aug 15 12:43:54 arctic systemd[1]: apport-autoreport.service: Succeeded.
Aug 15 12:43:54 arctic systemd[1]: Finished Process error reports when 
automatic reporting is enabled.
Aug 15 12:43:54 arctic systemd[1]: Starting Process error reports when 
automatic reporting is enabled...
Aug 15 12:43:54 arctic whoopsie-upload-all[8029]: 
/var/crash/_usr_bin_blueman-assistant.1000.crash already marked for upload, 
skipping
Aug 15 12:43:54 arctic whoopsie-upload-all[8029]: 
/var/crash/_usr_share_spotify_spotify.1000.crash already marked for upload, 
skipping
Aug 15 12:43:54 arctic whoopsie-upload-all[8029]: 
/var/crash/_usr_share_discord_Discord.1000.crash already marked for upload, 
skipping
Aug 15 12:43:54 arctic whoopsie-upload-all[8029]: All reports processed
Aug 15 12:43:54 arctic systemd[1]: apport-autoreport.service: Succeeded.
Aug 15 12:43:54 arctic systemd[1]: Finished Process error reports when 
automatic reporting is enabled.
Aug 15 12:43:54 arctic systemd[1]: Starting Process error reports when 
automatic reporting is enabled...

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

Title:
  systemd 100% cpu usage apport-autoreport.service: Failed with result
  'start-limit-hit'

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  after upgrade from Ubuntu 20.04 to 20.10  
  seeing systemd use 100% cpu forever


  top

top - 10:16:19 up 20 min,  1 user,  load average: 3.91, 4.28, 3.39
Tasks: 332 total,   2 running, 330 sleeping,   0 stopped,   0 zombie
%Cpu(s): 18.7 us,  6.4 sy, 11.9 ni, 62.2 id,  0.0 wa,  0.0 hi,  0.8 si, 
 0.0 st
MiB Mem :  15917.6 total,   8553.4 free,   2604.3 used,   4759.9 
buff/cache
MiB Swap:   2048.0 total,   2048.0 free,  0.0 used.  12633.7 avail 
Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ 
COMMAND  
  1 root  20   0  177316  12252   8684 R 100.0   0.1  15:01.25 
systemd  
   4636 kush  39  19  633796 176152  16360 S  98.3   1.1  17:51.56 
tracker-miner-f  
820 message+  20   0   10740   6452   4212 S  39.8   0.0   6:19.06 
dbus-daemon  
316 root  19  -1  535916 322896 320824 S  15.3   2.0   3:16.41 
systemd-journal  
844 syslog20   0  221136   5840   3920 S  13.6   0.0   2:14.52 
rsyslogd 
858 root  20   0   83708  74124   7568 S  12.7   0.5   2:06.98 
systemd-logind   
  5 root  20   0   0  0  0 I   3.4   0.0   0:05.01 
kworker/0:0-events   
  35566 kush  20   0 3850088 588344 262192 S   2.5   3.6   0:30.48 
MainThread   
   5626 kush  20   0 5004788 260876  93400 S   1.7   1.6   3:05.19 
gnome-shell  
   7033 kush  20   0  869792  66440  44272 S   1.7   0.4   0:06.05 
gnome-terminal-  
  36790 kush  20   0 2525432 156636  98568 S   1.7   1.0   0:04.99 
Web Content  
957 root  20   0 1556196  45044  24284 S   0.8   0.3   0:02.48 
containerd   

[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'

[Aaron Lichtman]

This fix, published by the reporter of this bug, worked for me.

https://askubuntu.com/a/1267204

I only needed to follow the steps up to the first reboot.

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

Title:
  systemd 100% cpu usage apport-autoreport.service: Failed with result
  'start-limit-hit'

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  after upgrade from Ubuntu 20.04 to 20.10  
  seeing systemd use 100% cpu forever


  top

top - 10:16:19 up 20 min,  1 user,  load average: 3.91, 4.28, 3.39
Tasks: 332 total,   2 running, 330 sleeping,   0 stopped,   0 zombie
%Cpu(s): 18.7 us,  6.4 sy, 11.9 ni, 62.2 id,  0.0 wa,  0.0 hi,  0.8 si, 
 0.0 st
MiB Mem :  15917.6 total,   8553.4 free,   2604.3 used,   4759.9 
buff/cache
MiB Swap:   2048.0 total,   2048.0 free,  0.0 used.  12633.7 avail 
Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ 
COMMAND  
  1 root  20   0  177316  12252   8684 R 100.0   0.1  15:01.25 
systemd  
   4636 kush  39  19  633796 176152  16360 S  98.3   1.1  17:51.56 
tracker-miner-f  
820 message+  20   0   10740   6452   4212 S  39.8   0.0   6:19.06 
dbus-daemon  
316 root  19  -1  535916 322896 320824 S  15.3   2.0   3:16.41 
systemd-journal  
844 syslog20   0  221136   5840   3920 S  13.6   0.0   2:14.52 
rsyslogd 
858 root  20   0   83708  74124   7568 S  12.7   0.5   2:06.98 
systemd-logind   
  5 root  20   0   0  0  0 I   3.4   0.0   0:05.01 
kworker/0:0-events   
  35566 kush  20   0 3850088 588344 262192 S   2.5   3.6   0:30.48 
MainThread   
   5626 kush  20   0 5004788 260876  93400 S   1.7   1.6   3:05.19 
gnome-shell  
   7033 kush  20   0  869792  66440  44272 S   1.7   0.4   0:06.05 
gnome-terminal-  
  36790 kush  20   0 2525432 156636  98568 S   1.7   1.0   0:04.99 
Web Content  
957 root  20   0 1556196  45044  24284 S   0.8   0.3   0:02.48 
containerd   
   1038 root  20   0   10460   4412   3300 S   0.8   0.0   0:00.16 
fancontrol   



  
sudo tail -n 100 /var/log/syslog
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed 
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error 
reports when automatic reporting is enabled.
Aug 14 10:14:17 

[Touch-packages] [Bug 1872118] Re: [SRU] DHCP Cluster crashes after a few hours

[Andrew Welham]

Timo,
Just installed the updates I will let you know
I installed as follows 

apt-get install isc-dhcp-server

apt-get install libdns-export1109/focal-proposed
apt-get install libirs-export161/focal-proposed
apt-get install  libisc-export1105/focal-proposed


The installed version are
GW1
# dpkg -l | grep isc-dhcp-server
ii  isc-dhcp-server  4.4.1-2.1ubuntu5   
amd64ISC DHCP server for automatic IP address assignment
# dpkg -l | grep libdns-export1109
ii  libdns-export11091:9.11.16+dfsg-3~ubuntu1   
amd64Exported DNS Shared Library
# dpkg -l | grep libirs-export161
ii  libirs-export161 1:9.11.16+dfsg-3~ubuntu1   
amd64Exported IRS Shared Library
# dpkg -l | grep libisc-export1105
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~ubuntu1   
amd64Exported ISC Shared Library
#


GW2
# dpkg -l | grep isc-dhcp-server
ii  isc-dhcp-server  4.4.1-2.1ubuntu5   
amd64ISC DHCP server for automatic IP address assignment
# dpkg -l | grep libdns-export1109
ii  libdns-export11091:9.11.16+dfsg-3~ubuntu1   
amd64Exported DNS Shared Library
# dpkg -l | grep libirs-export161
ii  libirs-export161 1:9.11.16+dfsg-3~build1
amd64Exported IRS Shared Library
# dpkg -l | grep libisc-export1105
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~build1
amd64Exported ISC Shared Library

Can you please confirm the correct versions are installed

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

Title:
  [SRU] DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in bind9-libs source package in Focal:
  Fix Committed
Status in isc-dhcp source package in Focal:
  Invalid
Status in bind9-libs source package in Groovy:
  Fix Released
Status in isc-dhcp source package in Groovy:
  Invalid

Bug description:
  [Description]

  isc-dhcp-server uses libisc-export (coming from bind9-libs package) for 
handling the socket event(s) when configured in peer mode (master/secondary). 
It's possible that a sequence of messages dispatched by the master that 
requires acknowledgment from its peers holds a socket
  in a pending to send state, a timer or a subsequent write request can be 
scheduled into this socket and the !sock->pending_send assertion
  will be raised when trying to write again at the time data hasn't been 
flushed entirely and the pending_send flag hasn't been reset to 0 state.

  If this race condition happens, the following stacktrace will be
  hit:

  (gdb) info threads
    Id Target Id Frame
  * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:50
    2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait 
(futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52
    3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, 
processes_to_wake=1, futex_word=) at 
../sysdeps/nptl/futex-internal.h:364
    4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable 
(private=, expected=0, futex_word=0x7fb4de6cd0d0) at 
../sysdeps/nptl/futex-internal.h:183

  (gdb) frame 2
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  (gdb) bt
  #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  #4 process_fd (writeable=, readable=, fd=11, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054
  #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211
  #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397
  #7 0x7fb4dea68609 in start_thread (arg=) at 
pthread_create.c:477
  #8 0x7fb4deba4103 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  (gdb) frame 3
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  4041 in ../../../../lib/isc/unix/socket.c
  (gdb) p sock->pending_send
  $2 = 1

  [TEST CASE]

  1) Install isc-dhcp-server in 2 focal machine(s).
  2) Configure peer/cluster mode 

[Touch-packages] [Bug 1872118] Re: [SRU] DHCP Cluster crashes after a few hours

[Andrew Welham]

not looking good,

Aug 15 20:14:55 gw2-focal sh[741]: ../../../../lib/isc/unix/socket.c:4359: 
fatal error: select() failed: Bad file descriptor
Aug 15 20:14:55 gw2-focal systemd[1]: isc-dhcp-server.service: Main process 
exited, code=killed, status=6/ABRT
Aug 15 20:14:55 gw2-focal systemd[1]: isc-dhcp-server.service: Failed with 
result 'signal'.

have the correct files been installed ?

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

Title:
  [SRU] DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in bind9-libs source package in Focal:
  Fix Committed
Status in isc-dhcp source package in Focal:
  Invalid
Status in bind9-libs source package in Groovy:
  Fix Released
Status in isc-dhcp source package in Groovy:
  Invalid

Bug description:
  [Description]

  isc-dhcp-server uses libisc-export (coming from bind9-libs package) for 
handling the socket event(s) when configured in peer mode (master/secondary). 
It's possible that a sequence of messages dispatched by the master that 
requires acknowledgment from its peers holds a socket
  in a pending to send state, a timer or a subsequent write request can be 
scheduled into this socket and the !sock->pending_send assertion
  will be raised when trying to write again at the time data hasn't been 
flushed entirely and the pending_send flag hasn't been reset to 0 state.

  If this race condition happens, the following stacktrace will be
  hit:

  (gdb) info threads
    Id Target Id Frame
  * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:50
    2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait 
(futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52
    3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, 
processes_to_wake=1, futex_word=) at 
../sysdeps/nptl/futex-internal.h:364
    4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable 
(private=, expected=0, futex_word=0x7fb4de6cd0d0) at 
../sysdeps/nptl/futex-internal.h:183

  (gdb) frame 2
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  (gdb) bt
  #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  #4 process_fd (writeable=, readable=, fd=11, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054
  #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211
  #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397
  #7 0x7fb4dea68609 in start_thread (arg=) at 
pthread_create.c:477
  #8 0x7fb4deba4103 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  (gdb) frame 3
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  4041 in ../../../../lib/isc/unix/socket.c
  (gdb) p sock->pending_send
  $2 = 1

  [TEST CASE]

  1) Install isc-dhcp-server in 2 focal machine(s).
  2) Configure peer/cluster mode as follows:
     Primary configuration: https://pastebin.ubuntu.com/p/XYj648MghK/
     Secondary configuration: https://pastebin.ubuntu.com/p/PYkcshZCWK/
  2) Run dhcpd as follows in both machine(s)

  # dhcpd -f -d -4 -cf /etc/dhcp/dhcpd.conf --no-pid ens4

  3) Leave the cluster running for a long (2h) period until the
  crash/race condition is reproduced.

  [REGRESSION POTENTIAL]

  * The fix will prevent the assertion to happen in the dispatch_send
  path, later versions of isch-dhcp upstream lack this logic and entirely 
removed the existence of this flag. Therefore, removing the need for this
  assertion at process_fd shouldn't be problematic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhcp/+bug/1872118/+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 1872118] Re: [SRU] DHCP Cluster crashes after a few hours

[Andrew Welham]

Just tried this
apt-get -y remove isc-dhcp-server
apt-get -y remove libdns-export1109/focal-proposed
apt-get -y remove libirs-export161/focal-proposed
apt-get -y remove libisc-export1105/focal-proposed
apt-get -y install isc-dhcp-server
apt-get -y install libdns1109/focal-proposed
apt-get -y install libirs161/focal-proposed
apt-get -y install  libisc1105/focal-proposed


GW1
#  dpkg -l | grep isc-dhcp-server
ii  isc-dhcp-server  4.4.1-2.1ubuntu5   
amd64ISC DHCP server for automatic IP address assignment
#  dpkg -l | grep libdns
ii  libdns-export11001:9.11.3+dfsg-1ubuntu1.12  
amd64Exported DNS Shared Library
ii  libdns-export11091:9.11.16+dfsg-3~build1
amd64Exported DNS Shared Library
ii  libdns1109:amd64 1:9.11.16+dfsg-3~ubuntu1   
amd64DNS Shared Library used by BIND
# dpkg -l | grep libirs
ii  libirs-export160 1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported IRS Shared Library
ii  libirs-export161 1:9.11.16+dfsg-3~build1
amd64Exported IRS Shared Library
ii  libirs161:amd64  1:9.11.16+dfsg-3~ubuntu1   
amd64DNS Shared Library used by BIND
# dpkg -l | grep libisc
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~build1
amd64Exported ISC Shared Library
ii  libisc-export169:amd64   1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported ISC Shared Library
ii  libisc1105:amd64 1:9.11.16+dfsg-3~ubuntu1   
amd64ISC Shared Library used by BIND
ii  libisccc161:amd641:9.11.16+dfsg-3~ubuntu1   
amd64Command Channel Library used by BIND
ii  libisccfg-export160  1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported ISC CFG Shared Library
ii  libisccfg-export163  1:9.11.16+dfsg-3~build1
amd64Exported ISC CFG Shared Library
ii  libisccfg163:amd64   1:9.11.16+dfsg-3~ubuntu1   
amd64Config File Handling Library used by BIND


GW2
# dpkg -l | grep isc-dhcp-server
ii  isc-dhcp-server  4.4.1-2.1ubuntu5   
amd64ISC DHCP server for automatic IP address assignment
# dpkg -l | grep libdns
ii  libdns-export11001:9.11.3+dfsg-1ubuntu1.12  
amd64Exported DNS Shared Library
ii  libdns-export11091:9.11.16+dfsg-3~build1
amd64Exported DNS Shared Library
ii  libdns1109:amd64 1:9.11.16+dfsg-3~ubuntu1   
amd64DNS Shared Library used by BIND
# dpkg -l | grep libirs
ii  libirs-export160 1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported IRS Shared Library
ii  libirs-export161 1:9.11.16+dfsg-3~build1
amd64Exported IRS Shared Library
ii  libirs161:amd64  1:9.11.16+dfsg-3~ubuntu1   
amd64DNS Shared Library used by BIND
# dpkg -l | grep libisc
ii  libisc-export1105:amd64  1:9.11.16+dfsg-3~build1
amd64Exported ISC Shared Library
ii  libisc-export169:amd64   1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported ISC Shared Library
ii  libisc1105:amd64 1:9.11.16+dfsg-3~ubuntu1   
amd64ISC Shared Library used by BIND
ii  libisccc161:amd641:9.11.16+dfsg-3~ubuntu1   
amd64Command Channel Library used by BIND
ii  libisccfg-export160  1:9.11.3+dfsg-1ubuntu1.12  
amd64Exported ISC CFG Shared Library
ii  libisccfg-export163  1:9.11.16+dfsg-3~build1
amd64Exported ISC CFG Shared Library
ii  libisccfg163:amd64   1:9.11.16+dfsg-3~ubuntu1   
amd64Config File Handling Library used by BIND


still not good

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

Title:
  [SRU] DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in bind9-libs source package in Focal:
  Fix Committed
Status in isc-dhcp source package in Focal:
  Invalid
Status in bind9-libs source package in Groovy:
  Fix Released
Status in isc-dhcp source package in Groovy:
  Invalid

Bug description:
  [Description]

  isc-dhcp-server uses libisc-export (coming from bind9-libs package) for 
handling the socket event(s) when configured in peer mode (master/secondary). 
It's possible that a sequence of messages dispatched by the master that 
requires acknowledgment from its peers holds a socket
  in a pending to send state, a 

[Touch-packages] [Bug 1890804] Re: 20.10 groovy proposed: resolvconf-pull-resolved.service fails to start if resolvconf is installed at the same time

[Launchpad Bug Tracker]

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

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

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

Title:
  20.10 groovy proposed: resolvconf-pull-resolved.service fails to start
  if resolvconf is installed at the same time

Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  I was trying to find some resolutions when I found this fresh debian
  bug report: https://www.mail-archive.com/debian-bugs-
  d...@lists.debian.org/msg1759183.html

  Is likely reproducible similarly but I can't since all my machines
  were hit by this bug and barely made one working and virtualbox-dkms
  is broken on 5.8.0-12-generic (filed that one too). This made all my
  fallback kernels,recovery unbootable! The solution discussed there is
  to remove the offending package resolvconf. I tried that in recovery
  mode root shell (graphical won't boot), but dpkg hangs when it tries
  to reload daemons but it can't asking me to restart after 20 minutes
  leaving with a host of broken packages but the system is finally
  bootable.

  Journalctl logspam:

  Journal file 
/var/log/journal/383ea8c95927438c95c2011a5f5bbfbb/system@0005ac4607f96c17-321a00afc15a51fc.journal~
 is truncated, ignoring file.
  -- Logs begin at Fri 2020-08-07 06:46:27 UTC, end at Fri 2020-08-07 10:35:32 
UTC. --
  Aug 07 06:46:27 systemd[1]: Failed to start resolvconf-pull-resolved.service.
   Subject: A start job for unit resolvconf-pull-resolved.service has failed
   Defined-By: systemd
  Support: http://www.ubuntu.com/support
   A start job for unit resolvconf-pull-resolved.service has finished with a 
failure.
   The job identifier is 1649803534 and the job result is failed.
  Aug 07 06:46:29 systemd[1]: resolvconf-pull-resolved.service: Start request 
repeated too quickly.
  Aug 07 06:46:29 systemd[1]: resolvconf-pull-resolved.service: Start request 
repeated too quickly.
  Aug 07 06:46:29 systemd[1]: resolvconf-pull-resolved.service: Start request 
repeated too quickly.
  Aug 07 06:46:29 systemd[1]: resolvconf-pull-resolved.service: Start request 
repeated too quickly.
  Aug 07 06:46:29 systemd[1]: resolvconf-pull-resolved.service: Start request 
repeated too quickly.
  Aug 07 06:46:29 systemd[1]: resolvconf-pull-resolved.service: Start request 
repeated too quickly.
  Aug 07 06:46:29 systemd[1]: resolvconf-pull-resolved.service: Start request 
repeated too quickly.
  Aug 07 06:46:29 systemd[1]: resolvconf-pull-resolved.service: Start request 
repeated too quickly.
  .

  systemd   246-2ubuntu1
  systemd-sysv  246-2ubuntu1
  resolvconf1.82ubuntu1
  Kernel: 5.8.0-12-generic x86_64
  Distro: Ubuntu 20.10 (Groovy Gorilla) (*Proposed)

  Just to note the bug probably came with systemd 246-2ubuntu1 today for
  me since it was working fine yesterday, not sure. Also some other
  systemd services are failing since moving to proposed like UFW (filed
  one too.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1890804/+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 1890804] Re: 20.10 groovy proposed: resolvconf-pull-resolved.service fails to start if resolvconf is installed at the same time

[Sønke Lorenzen]

This also happened for me on a 20.10 with resolvconf yesterday, I do not
have proposed enabled on that system.

I used the chroot process described at
https://help.ubuntu.com/community/LiveCdRecovery to be able to get into
that system and then uninstalling resolvconf after finding this bug and
the mentioned debian bug.

That fixed it. I have that system since 12.10 so before systemd. On
another 20.10 I have installed as 19.10 there is no resolvconf installed
and that did not see this problem.

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

Title:
  20.10 groovy proposed: resolvconf-pull-resolved.service fails to start
  if resolvconf is installed at the same time

Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  I was trying to find some resolutions when I found this fresh debian
  bug report: https://www.mail-archive.com/debian-bugs-
  d...@lists.debian.org/msg1759183.html

  Is likely reproducible similarly but I can't since all my machines
  were hit by this bug and barely made one working and virtualbox-dkms
  is broken on 5.8.0-12-generic (filed that one too). This made all my
  fallback kernels,recovery unbootable! The solution discussed there is
  to remove the offending package resolvconf. I tried that in recovery
  mode root shell (graphical won't boot), but dpkg hangs when it tries
  to reload daemons but it can't asking me to restart after 20 minutes
  leaving with a host of broken packages but the system is finally
  bootable.

  Journalctl logspam:

  Journal file 
/var/log/journal/383ea8c95927438c95c2011a5f5bbfbb/system@0005ac4607f96c17-321a00afc15a51fc.journal~
 is truncated, ignoring file.
  -- Logs begin at Fri 2020-08-07 06:46:27 UTC, end at Fri 2020-08-07 10:35:32 
UTC. --
  Aug 07 06:46:27 systemd[1]: Failed to start resolvconf-pull-resolved.service.
   Subject: A start job for unit resolvconf-pull-resolved.service has failed
   Defined-By: systemd
  Support: http://www.ubuntu.com/support
   A start job for unit resolvconf-pull-resolved.service has finished with a 
failure.
   The job identifier is 1649803534 and the job result is failed.
  Aug 07 06:46:29 systemd[1]: resolvconf-pull-resolved.service: Start request 
repeated too quickly.
  Aug 07 06:46:29 systemd[1]: resolvconf-pull-resolved.service: Start request 
repeated too quickly.
  Aug 07 06:46:29 systemd[1]: resolvconf-pull-resolved.service: Start request 
repeated too quickly.
  Aug 07 06:46:29 systemd[1]: resolvconf-pull-resolved.service: Start request 
repeated too quickly.
  Aug 07 06:46:29 systemd[1]: resolvconf-pull-resolved.service: Start request 
repeated too quickly.
  Aug 07 06:46:29 systemd[1]: resolvconf-pull-resolved.service: Start request 
repeated too quickly.
  Aug 07 06:46:29 systemd[1]: resolvconf-pull-resolved.service: Start request 
repeated too quickly.
  Aug 07 06:46:29 systemd[1]: resolvconf-pull-resolved.service: Start request 
repeated too quickly.
  .

  systemd   246-2ubuntu1
  systemd-sysv  246-2ubuntu1
  resolvconf1.82ubuntu1
  Kernel: 5.8.0-12-generic x86_64
  Distro: Ubuntu 20.10 (Groovy Gorilla) (*Proposed)

  Just to note the bug probably came with systemd 246-2ubuntu1 today for
  me since it was working fine yesterday, not sure. Also some other
  systemd services are failing since moving to proposed like UFW (filed
  one too.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1890804/+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 1872118] Re: [SRU] DHCP Cluster crashes after a few hours

[Richard Laager]

Andrew, 1:9.11.16+dfsg-3~build1 is wrong. The correct version is
1:9.11.16+dfsg-3~ubuntu1 (~ubuntu1 instead of ~build1).

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

Title:
  [SRU] DHCP Cluster crashes after a few hours

Status in DHCP:
  New
Status in bind9-libs package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in bind9-libs source package in Focal:
  Fix Committed
Status in isc-dhcp source package in Focal:
  Invalid
Status in bind9-libs source package in Groovy:
  Fix Released
Status in isc-dhcp source package in Groovy:
  Invalid

Bug description:
  [Description]

  isc-dhcp-server uses libisc-export (coming from bind9-libs package) for 
handling the socket event(s) when configured in peer mode (master/secondary). 
It's possible that a sequence of messages dispatched by the master that 
requires acknowledgment from its peers holds a socket
  in a pending to send state, a timer or a subsequent write request can be 
scheduled into this socket and the !sock->pending_send assertion
  will be raised when trying to write again at the time data hasn't been 
flushed entirely and the pending_send flag hasn't been reset to 0 state.

  If this race condition happens, the following stacktrace will be
  hit:

  (gdb) info threads
    Id Target Id Frame
  * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:50
    2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait 
(futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52
    3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, 
processes_to_wake=1, futex_word=) at 
../sysdeps/nptl/futex-internal.h:364
    4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable 
(private=, expected=0, futex_word=0x7fb4de6cd0d0) at 
../sysdeps/nptl/futex-internal.h:183

  (gdb) frame 2
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  (gdb) bt
  #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79
  #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 
"../../../../lib/isc/unix/socket.c", line=line@entry=3361, 
type=type@entry=isc_assertiontype_insist,
  cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at 
../../../lib/isc/assertions.c:52
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  #4 process_fd (writeable=, readable=, fd=11, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054
  #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, 
manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211
  #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397
  #7 0x7fb4dea68609 in start_thread (arg=) at 
pthread_create.c:477
  #8 0x7fb4deba4103 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  (gdb) frame 3
  #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at 
../../../../lib/isc/unix/socket.c:4041
  4041 in ../../../../lib/isc/unix/socket.c
  (gdb) p sock->pending_send
  $2 = 1

  [TEST CASE]

  1) Install isc-dhcp-server in 2 focal machine(s).
  2) Configure peer/cluster mode as follows:
     Primary configuration: https://pastebin.ubuntu.com/p/XYj648MghK/
     Secondary configuration: https://pastebin.ubuntu.com/p/PYkcshZCWK/
  2) Run dhcpd as follows in both machine(s)

  # dhcpd -f -d -4 -cf /etc/dhcp/dhcpd.conf --no-pid ens4

  3) Leave the cluster running for a long (2h) period until the
  crash/race condition is reproduced.

  [REGRESSION POTENTIAL]

  * The fix will prevent the assertion to happen in the dispatch_send
  path, later versions of isch-dhcp upstream lack this logic and entirely 
removed the existence of this flag. Therefore, removing the need for this
  assertion at process_fd shouldn't be problematic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhcp/+bug/1872118/+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 1811580] Re: systemd fails to start sshd at reboot

[Darxus]

I think I had the same problem.  I think it was fixed with "chown
root:root /var".

Related to this:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891394

I think it also caused screen to be unusable until it was run by root.

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

Title:
  systemd fails to start sshd at reboot

Status in systemd package in Ubuntu:
  Expired

Bug description:
  So far reported issues turned out to be:
  - obsolete/buggy/vulnerable 3rd party provided kernels
  - bad permissions on /

  Please ensure / is owned by root:root.
  Please ensure you are running up to date kernels.

  
  ===

  Ubuntu 16.04.5, systemd 229-4ubuntu21.15

  The latest systemd update has somehow changed the method it uses to
  start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if
  /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and
  /var/run/sshd/ does not already exist. Being as this is the default,
  virtually EVERY Ubuntu 16.04 server in the world has
  UsePrivilegeSeparation set to yes. Furthermore, at the time when the
  user performs 'apt upgrade' and receives the newest version of
  systemd, /var/run/sshd/ already exists, so sshd successfully reloads
  for as long as the server doesn't get rebooted. BUT, as soon as the
  server is rebooted for any reason, /var/run/sshd/ gets cleaned away,
  and sshd fails to start, causing the remote user to be completely
  locked out of his system. This is a MAJOR issue for millions of VPS
  servers worldwide, as they are all about to get locked out of their
  servers and potentially lose data. The next reboot is a ticking time
  bomb waiting to spring. The bomb can be defused by implicitly setting
  'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however
  unsuspecting administrators are bound to be caught out by the
  millions. I got caught by it in the middle of setting up a new server
  yesterday, and it took a whole day to find the source.

  The appropriate fix would be to ensure that systemd can successfully
  'start ssh.service' even when 'UsePrivilegeSeparation yes' is set.
  systemd needs to test that /var/run/sshd/ exists before starting sshd,
  just as the init.d script for sshd does. openssl could also be patched
  so that UsePrivilegeSeparation is no longer enabled by default,
  however that is not going to solve the problem for millions of pre-
  existing config files. Only an update to openssl to force-override
  that flag to 'no' would solve the problem. Thus systemd still needs to
  be responsible for ensuring that it inits sshd properly by ensuring
  that /var/run/sshd/ exists before it sends the 'start' command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+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 1883723] Re: Some official repositories changed compression method from gzip to lz4 leading to checksum errors during apt-get update

[Launchpad Bug Tracker]

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

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

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

Title:
  Some official repositories changed compression method from gzip to lz4
  leading to checksum errors during apt-get update

Status in apt package in Ubuntu:
  Expired

Bug description:
  This includes bionic-security repositories:

  Reading package lists... Done
  E: Failed to fetch 
store:/var/lib/apt/lists/partial/pl.archive.ubuntu.com_ubuntu_dists_bionic-security_Contents-i386.gz
  Hash Sum mismatch
     Hashes of expected file:
  - Filesize:821731759 [weak]
  - SHA256:03b7fe601ba17908a5bfc628c8eb8309cd682f88ea5c2ed8139a4d46bb02df09
  - SHA1:5b0ca78303b67f3e1e78c828ac10474f4acf8c10 [weak]
  - MD5Sum:fa890ae0f75a803fa744ce126739bfa6 [weak]
     Hashes of received file:
  - SHA256:9cd965c8d4f68b92cfc20484aabf19899b53718f810dc316f7983c4b194108dd
  - SHA1:7c27b4efd7c3ca176b3e7ed85dec5d865a8928b8 [weak]
  - MD5Sum:c1a1a8baef4d45ce444962b981a

  Failed files:
  nusch@xps13:/etc/apt$ sudo ls -l /var/lib/apt/lists/partial/ | grep FAILED
  lrwxrwxrwx 1 root root   87 cze 16 16:52 
pl.archive.ubuntu.com_ubuntu_dists_bionic-proposed_Contents-i386.gz.FAILED -> 
/var/lib/apt/lists/pl.archive.ubuntu.com_ubuntu_dists_bionic-proposed_Contents-i386.lz4
  lrwxrwxrwx 1 root root   87 cze 16 16:52 
pl.archive.ubuntu.com_ubuntu_dists_bionic-security_Contents-i386.gz.FAILED -> 
/var/lib/apt/lists/pl.archive.ubuntu.com_ubuntu_dists_bionic-security_Contents-i386.lz4

  Not sure from where this issue comes - manual browsing of repository
  discovers only .gz file while downloaded copy have lz4 extension.
  After manual downloading .gz one and uncompromising diff command
  confirms both produce the same file.  Apt-get clean and deleting cache
  doesn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.12ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-107.108-generic 4.15.18
  Uname: Linux 4.15.0-107-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 16 16:49:31 2020
  InstallationDate: Installed on 2015-05-08 (1866 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2018-08-26 (659 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1883723/+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 1891394] Re: systemd breaks upgrade with useless error if /var is not owned by root

[Steve Langasek]

If your /var is not owned by root, your system is insecure. Why was /var
not owned by root?

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

Title:
  systemd breaks upgrade with useless error if /var is not owned by root

Status in systemd package in Ubuntu:
  New

Bug description:
  I just upgraded from 16.04 to 18.04.  The upgrade broke.  The error,
  from systemd, was:

  "Unsafe symlinks encountered in /var/log/journal, refusing."

  That directory was empty.  The fix was "chmod root:root /var".  Yes,
  it's weird that my /var wasn't owned by root, but upgrade breaking
  errors should say something useful.

  panic:~# chown darxus:darxus /var
  panic:~# dpkg-reconfigure systemd
  Unsafe symlinks encountered in /var/spool/rsyslog, refusing.
  Unsafe symlinks encountered in /var/lib/colord, refusing.
  Unsafe symlinks encountered in /var/lib/colord/icc, refusing.
  Unsafe symlinks encountered in /var/cache/man, refusing.
  Unsafe symlinks encountered in /var/run/opendkim, refusing.
  Unsafe symlinks encountered in /var/lib/systemd, refusing.
  Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing.
  Unsafe symlinks encountered in /var/log/wtmp, refusing.
  Unsafe symlinks encountered in /var/log/btmp, refusing.
  Unsafe symlinks encountered in /var/log/lastlog, refusing.
  Unsafe symlinks encountered in /var/log, refusing.
  Unsafe symlinks encountered in /var/log/auth.log, refusing.
  Unsafe symlinks encountered in /var/log/mail.err, refusing.
  Unsafe symlinks encountered in /var/log/mail.log, refusing.
  Unsafe symlinks encountered in /var/log/kern.log, refusing.
  Unsafe symlinks encountered in /var/log/syslog, refusing.
  Unsafe symlinks encountered in /var/log/journal, refusing.
  Unsafe symlinks encountered in /var/log/journal, refusing.
  Unsafe symlinks encountered in /var/log/journal, refusing.
  Unsafe symlinks encountered in /var/log/journal, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590/system.journal, refusing.
  Unsafe symlinks encountered in 
/var/log/journal/6118992be5f52430d74ed66e4cc8d590/system.journal, refusing.
  panic:~# chown root:root /var
  panic:~# dpkg-reconfigure systemd

  I found the fix here: https://askubuntu.com/a/1095796
  Showing that I'm not the only one encountering this.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.42
  Uname: Linux 5.6.14-x86_64-linode135 x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: i386
  Date: Wed Aug 12 15:58:33 2020
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: root=/dev/sda console=tty1 console=ttyS0 ro  
devtmpfs.mount=1
  ProcModules:
   
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2020-08-12 (0 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-3.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-3.1
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891394/+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 1883690] Re: ubuntu-bug - where and how?

[Launchpad Bug Tracker]

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

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

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

Title:
  ubuntu-bug - where and how?

Status in apport package in Ubuntu:
  Expired

Bug description:
  # cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04.4 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.4 LTS"

  
  The manual says, I shall use ubuntu-bug to report a bug, but:

  # ubuntu-bug
  -bash: ubuntu-bug: command not found

  # apt install ubuntu-bug
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  E: Unable to locate package ubuntu-bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1883690/+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 1891715] Re: [Asus P8H61-M LX3 R2.0, VIA VT1708S, Green Headphone Out, Front] No sound at all

[Daniel Letzeisen]

** Summary changed:

- [System Product Name, VIA VT1708S, Green Headphone Out, Front] No sound at all
+ [Asus P8H61-M LX3 R2.0, VIA VT1708S, Green Headphone Out, Front] No sound at 
all

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

Title:
  [Asus P8H61-M LX3 R2.0, VIA VT1708S, Green Headphone Out, Front] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  It doesn't work from the fresh install of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bloo   5334 F pulseaudio
   /dev/snd/controlC0:  bloo   5334 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 22:41:36 2020
  InstallationDate: Installed on 2020-08-08 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1083 F pulseaudio
bloo   5334 F pulseaudio
   /dev/snd/controlC0:  gdm1083 F pulseaudio
bloo   5334 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT1708S, Green Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0608
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX3 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0608:bd08/10/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX3R2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1891715/+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 1820374] Re: agetty needs option nonewline

[Robert Browne]

I use CLI and openbox minimum install

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

Title:
  agetty needs option nonewline

Status in systemd package in Ubuntu:
  New

Bug description:
   affects ubuntu/systemd

  Add nonewline option to agetty in
  /lib/systemd/system/getty@.service

  At console login agetty adds a newline after a short delay.
  It will cause a login error if you do not wait for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1820374/+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 1891772] [NEW] Sound is not working on Ubuntu 20.04. I am running Ubuntu 20.04 as a dual boot along with windows 10 on Asus Zenbook 15 UX534FT.

[Vidushi Garg]

Public bug reported:

Sound is not working on Ubuntu 20.04. I am running Ubuntu 20.04 as a
dual boot along with windows 10 on Asus Zenbook 15 UX534FT.  I have
tried updating the pulseaudio and even changed the parameters of
pulseaudio.service but still it is not working. I even tried altering
the parametes of alsamixer but still no luck.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.5 [modified: 
usr/lib/systemd/user/pulseaudio.service]
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vids   1416 F pulseaudio
 /dev/snd/pcmC0D0c:   vids   1416 F...m pulseaudio
 /dev/snd/pcmC0D0p:   vids   1416 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 16 03:02:37 2020
InstallationDate: Installed on 2020-08-15 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX534FT.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX534FT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX534FT.302:bd12/18/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX534FT_UX534FT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX534FT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX534FT_UX534FT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug focal

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

Title:
  Sound is not working on Ubuntu 20.04. I am running Ubuntu 20.04 as a
  dual boot along with windows 10 on Asus Zenbook 15 UX534FT.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sound is not working on Ubuntu 20.04. I am running Ubuntu 20.04 as a
  dual boot along with windows 10 on Asus Zenbook 15 UX534FT.  I have
  tried updating the pulseaudio and even changed the parameters of
  pulseaudio.service but still it is not working. I even tried altering
  the parametes of alsamixer but still no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.5 [modified: 
usr/lib/systemd/user/pulseaudio.service]
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vids   1416 F pulseaudio
   /dev/snd/pcmC0D0c:   vids   1416 F...m pulseaudio
   /dev/snd/pcmC0D0p:   vids   1416 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 16 03:02:37 2020
  InstallationDate: Installed on 2020-08-15 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX534FT.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX534FT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX534FT.302:bd12/18/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX534FT_UX534FT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX534FT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX534FT_UX534FT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1891772/+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 1891782] [NEW] python3 Math bug: In accordance with IEEE_754-1985, math.sqrt(-1.25) should return NaN, and print function should be able to indicate it.

[Dan Lott]

Public bug reported:

python3 Math bug: In accordance with IEEE_754-1985, math.sqrt(-1.25)
should return NaN, and print function should be able to indicate it.

Demo code: 
import math
c = math.sqrt(-1.25)
print(c)

When run produces:
Traceback (most recent call last):
  File "./float-test.py", line 4, in 
c = math.sqrt(-1.25)
ValueError: math domain error

Should produce:
NaN
OR:
NOT A NUMBER

For more information, see https://en.wikipedia.org/wiki/NaN

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.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Sat Aug 15 21:30:13 2020
InstallationDate: Installed on 2020-04-26 (112 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: python3-defaults
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  python3 Math bug: In accordance with IEEE_754-1985, math.sqrt(-1.25)
  should return NaN, and print function should be able to indicate it.

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  python3 Math bug: In accordance with IEEE_754-1985, math.sqrt(-1.25)
  should return NaN, and print function should be able to indicate it.

  Demo code: 
  import math
  c = math.sqrt(-1.25)
  print(c)

  When run produces:
  Traceback (most recent call last):
File "./float-test.py", line 4, in 
  c = math.sqrt(-1.25)
  ValueError: math domain error

  Should produce:
  NaN
OR:
  NOT A NUMBER

  For more information, see https://en.wikipedia.org/wiki/NaN

  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.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sat Aug 15 21:30:13 2020
  InstallationDate: Installed on 2020-04-26 (112 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/python3-defaults/+bug/1891782/+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 1891342] Re: network manager does not auto connect to hidden wifi networks

[PC]

Thanks to Thomas, the issue is resolved with NetworkManager 1.26

Refer to :
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/438

Closing this bug :)

** Information type changed from Public to Private

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Fix Released

** Attachment removed: "CRDA.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891342/+attachment/5401033/+files/CRDA.txt

** Description changed:

  Environment:
  Fresh installation of Lubuntu 20.04 (it also occurs in a fresh installation 
of Ubuntu 20.04)
  
  Steps to reproduce the situation:
  1) Lubuntu -> Network Manager -> Edit Connections -> Add SSID of a hidden 
WiFi network
  2) Network Manager does not connect automatically with the hidden Wifi Network
  
  However, once the WiFi network SSID is set to broadcast mode, it starts
  connecting automatically.
  
  The workaround suggested in Bug 1542733 works here.
  https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1542733
  
  However, it was suggested to create a new bug report for later releases.
  Please provide your assistance. Thank you.
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 20.04
- Package: network-manager 1.22.10-1ubuntu2.1
- ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
- Uname: Linux 5.4.0-42-generic x86_64
- NonfreeKernelModules: wl
- ApportVersion: 2.20.11-0ubuntu27.6
- Architecture: amd64
- CasperMD5CheckResult: skip
- CurrentDesktop: LXQt
- Date: Wed Aug 12 20:11:18 2020
- InstallationDate: Installed on 2020-08-09 (3 days ago)
- InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
- IpRoute:
-  default via 192.168.29.1 dev wlp2s0 proto dhcp metric 600 
-  192.168.29.0/24 dev wlp2s0 proto kernel scope link src 192.168.29.22 metric 
600
- SourcePackage: network-manager
- UpgradeStatus: No upgrade log present (probably fresh install)
- nmcli-dev:
-  DEVICE  TYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH 
 CONNECTION  CON-UUID   
   CON-PATH   
-  wlp2s0  wifi  connectedfull  full  
/org/freedesktop/NetworkManager/Devices/3  PCWiFi  
9a5f3d88-a43e-4862-9cac-b65102e9e135  
/org/freedesktop/NetworkManager/ActiveConnection/1 
-  enp3s0  ethernet  unavailable  none  none  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
-  lo  loopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
- nmcli-nm:
-  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
-  running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

** Attachment removed: "nmcli-con.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891342/+attachment/5401046/+files/nmcli-con.txt

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891342/+attachment/5401045/+files/WifiSyslog.txt

** Attachment removed: "IwConfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891342/+attachment/5401036/+files/IwConfig.txt

** Attachment removed: "IpAddr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891342/+attachment/5401035/+files/IpAddr.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891342/+attachment/5401034/+files/Dependencies.txt

** Attachment removed: "NetDevice.enp3s0.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891342/+attachment/5401037/+files/NetDevice.enp3s0.txt

** Attachment removed: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891342/+attachment/5401038/+files/NetDevice.lo.txt

** Attachment removed: "NetDevice.wlp2s0.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891342/+attachment/5401039/+files/NetDevice.wlp2s0.txt

** Attachment removed: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891342/+attachment/5401040/+files/NetworkManager.conf.txt

** Attachment removed: "PciNetwork.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891342/+attachment/5401041/+files/PciNetwork.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891342/+attachment/5401042/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891342/+attachment/5401043/+files/ProcEnviron.txt

** Attachment removed: "RfKill.txt"