date:20200630

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

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

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

Title:
Audio settings strange behaviour with ASUS STXII sound card

Status in gnome-control-center package in Ubuntu:
New
Status in pulseaudio package in Ubuntu:
New

Bug description:
What happens:

If an Asus STXII 7.1 sound card is installed and another output device
is present, there is a strange behavior in the Gnome audio settings.

After the first start of Ubuntu the Asus soundcard is not the default
device. This can be selected in the Gnome settings. If a different
speaker configuration is selected now. E.g. stereo instead of 5.1 or
vice versa, the selection jumps from the Asus output device back to
the original output device. The Asus sound card can then be selected
again and the corresponding speaker configuration will fit now.

If 5.1 is selected as the mode, there is a second problem.
Moving the balance slider (left / right) moves the slider (front / back)
slightly as well.
The slider for lfe is grayed out, even when I enable the lfe remixing in
/etc/pulse/daemon.conf
In the speaker test, all 5.1 channels work fine, including the lfe.

For better illustration I made a screen video. (see attachment)

This is probably a general bug in Gnome - it has been occurring since
Ubuntu 18.x and affects all distros that use Gnome since then.
Unfortunately I was not able to make a report in Gnome, because the
registration on the Gnome site does not work anymore... Maybe you have
a good contact to the Gnome team?

Ubuntu 20.04 LTS (Release 20.04)
Package: gnome-control-center (1:3.36.1-1ubuntu5)

Expected behavior:
It should be possible to select the sound card and the setting should be
retained even if the speaker configuration is changed. Furthermore, the balance
sliders should not influence each other.
Lfe slider should work. (And in a perfect world this would also activate lfe
remixing and gives the user a cross over frequency option, but this is just an
idea :)

BR,
Mathias
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-04-23 (7 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
NonfreeKernelModules: nvidia_modeset nvidia
Package: pulseaudio
PackageArchitecture: amd64
ProcEnviron:
LANGUAGE=de_AT:de
TERM=xterm-256color
PATH=(custom, no user)
LANG=de_AT.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Tags: focal
Uname: Linux 5.4.0-28-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876267/+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 1876267] Re: Audio settings strange behaviour with ASUS STXII sound card

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

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

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

Title:
Audio settings strange behaviour with ASUS STXII sound card

Status in gnome-control-center package in Ubuntu:
Expired
Status in pulseaudio package in Ubuntu:
Expired

Bug description:
What happens:

If an Asus STXII 7.1 sound card is installed and another output device
is present, there is a strange behavior in the Gnome audio settings.

For better illustration I made a screen video. (see attachment)

Ubuntu 20.04 LTS (Release 20.04)
Package: gnome-control-center (1:3.36.1-1ubuntu5)

_MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876267/+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 1876267] Re: Audio settings strange behaviour with ASUS STXII sound card

[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Expired

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

Title:
Audio settings strange behaviour with ASUS STXII sound card

Status in gnome-control-center package in Ubuntu:
Expired
Status in pulseaudio package in Ubuntu:
Expired

Bug description:
What happens:

If an Asus STXII 7.1 sound card is installed and another output device
is present, there is a strange behavior in the Gnome audio settings.

For better illustration I made a screen video. (see attachment)

Ubuntu 20.04 LTS (Release 20.04)
Package: gnome-control-center (1:3.36.1-1ubuntu5)

_MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876267/+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 1885742] Re: Unable to suspend, error -16

I can't see where that error came from. Where did you see it? After it
happens next please run:

  journalctl -b0 > journal.txt

and then attach the resulting text file here.


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

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

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

Title:
  Unable to suspend, error -16

Status in Ubuntu:
  Incomplete

Bug description:
  Unable to suspend, error -16

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
  Uname: Linux 4.15.0-108-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 
PDT 2020
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 30 20:57:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.138, 4.15.0-108-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
   NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801]
  InstallationDate: Installed on 2018-08-29 (670 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20217
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic 
root=UUID=2674d4c6-6617-45bc-bd72-c1ecec60a6e9 ro quiet splash 
nouveau.modeset=0 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 1/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN47WW(V3.08)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 3194STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN47WW(V3.08):bd1/30/2015:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr3194STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1885742/+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 1877633] Re: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64

2020-06-30 Thread Alex Murray

I am not sure how packages.ubuntu.com generates its list but they were
published for all architectures on launchpad:
https://launchpad.net/ubuntu/+source/libseccomp/2.4.3-1ubuntu3.20.04.2

Also the debs are present on ports.ubuntu.com: http://ports.ubuntu.com
/ubuntu-ports/pool/main/libs/libseccomp/libseccomp-
dev_2.4.3-1ubuntu3.20.04.2_armhf.deb and listed in the focal-security
Packages.gz as expected.

So I suspect this is some artefact of packages.ubuntu.com perhaps only
taking into account the contents of the security / updates pocket on
amd64/i386 - but again I am not certain. However as far as apt is
concerned, these packages exist and should be installed automatically by
unattended-upgrades etc.

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

Title:
  libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the
  getrlimit syscall on arm64

Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Focal:
  Fix Released
Status in libseccomp source package in Groovy:
  Fix Released

Bug description:
  This was reported via the snapcraft forum[1]:

  On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2

  $ lsb_release -d
  Description:  Ubuntu 18.04.4 LTS
  $ scmp_sys_resolver -a aarch64 163
  getrlimit
  $ scmp_sys_resolver -a aarch64 getrlimit
  163

  focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__*

  $ lsb_release -d
  Description:  Ubuntu 20.04 LTS
  $ scmp_sys_resolver -a aarch64 163
  UNKNOWN
  $ scmp_sys_resolver -a aarch64 getrlimit
  -10180

  [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal-
  arm64/17237/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+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 1817721] Re: autopkgtest success rate in Bionic reached an unusable amount

2020-06-30 Thread Thadeu Lima de Souza Cascardo

So after some investigation on systemd failures on ppc64el triggered by
the kernel on eoan, I noticed some coredumps on processes when running
under qemu inside the ADT environment.

As one of these processes is sleep, I am pretty confident this is caused
by the lack of emulation or rather the failure to ignore mffsl extra
bits, aka LP: #1847806.

I am not sure this is the right bug as it mentions lots of other
upstream failures across all arches. But it looks like the ones we are
seeing, and as we are referring this bug in our results, I thought it
was worht mentioning.

Cascardo.

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

Title:
  autopkgtest success rate in Bionic reached an unusable amount

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  Sorry to bother you - it seems we have this discussion every few months or so.

  I was looking at this due to an SRU and I realized that the last 50-100 tests 
on all architectures are currently failing.
  http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/amd64
  http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/i386
  http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/ppc64el
  http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/s390x

  On one hand I see the known flaky boot-and-smoke but that is fine.
  On the other hand I see the test "upstream" failing always and it seems not 
related to the actual proposed packages.

  Please help to resolve this mid-term.
  Short term I'll submit a force-badtest for this as it seems to hold up more 
and more with no gain of seeing plenty of peopl just hitting retry every now 
and then.

  If test "upstream" is utterly broken consider skipping it in the next
  upload that you do for regular service. That would bring back at least
  the remaining tests coverage.

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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:
  Confirmed
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 1883670] Re: Disable IEC958 on HP Thunderbolt Dock

This bug was fixed in the package alsa-lib - 1.2.2-2.1ubuntu1

---
alsa-lib (1.2.2-2.1ubuntu1) focal; urgency=medium

  * 
debian/patches/0001-conf-USB-Audio-Add-HP-Thunderbolt-Dock-in-the-IEC958.patch:
- Disable IEC958 on HP Thunderbolt Dock (lp: #1883670)

 -- Kai-Heng Feng   Tue, 16 Jun 2020
17:52:07 +0800

** Changed in: alsa-lib (Ubuntu Focal)
   Status: Fix Committed => 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:
  Confirmed
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 1883116] Re: SRU the current 3.36.3 stable update

This bug was fixed in the package evolution-data-server -
3.36.3-0ubuntu1

---
evolution-data-server (3.36.3-0ubuntu1) focal; urgency=medium

  * New stable version (lp: #1883116)

 -- Sebastien Bacher   Thu, 11 Jun 2020 23:09:07
+0200

** Changed in: evolution-data-server (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  SRU the current 3.36.3 stable update

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1883116/+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 1883116] Update Released

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

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

Title:
  SRU the current 3.36.3 stable update

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1883116/+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 1884221] Re: `ubuntu-bug` fails with "UnboundLocalError: local variable 'project' referenced before assignment"

This bug was fixed in the package apport - 2.20.11-0ubuntu42

---
apport (2.20.11-0ubuntu42) groovy; urgency=medium

  * Fix pep8 errors regarding ambiguous variables.

 -- Brian Murray   Wed, 24 Jun 2020 09:15:51 -0700

** Changed in: apport (Ubuntu)
   Status: In Progress => 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/1884221

Title:
  `ubuntu-bug` fails with "UnboundLocalError: local variable 'project'
  referenced before assignment"

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  I just tried to `ubuntu-bug ubiquity` on a groovy(20.10) qa-test
  install using Xubuntu, however `ubuntu-bug` abended with python
  errors.

  I tried to file this with `ubuntu-bug apport` & again errors (but
  scanning it looks identical)

  I'm filing this report on my primary box and will apport-collect after
  filing, plus copy/paste the details from the actual box.

  "UnboundLocalError: local variable 'project' referenced before
  assignment"

  xubuntu@xubuntu:~$ ubuntu-bug ubiquity
  Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 597, in 
  app.run_argv()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 708, in run_argv
  return self.run_report_bug()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 549, in 
run_report_bug
  self.file_report()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 1396, in 
file_report
  url = self.crashdb.get_comment_url(self.report, ticket)
File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", 
line 247, in get_comment_url
  if not project:
  UnboundLocalError: local variable 'project' referenced before assignment

  xubuntu@xubuntu:~$ ubuntu-bug apport
  Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 597, in 
  app.run_argv()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 708, in run_argv
  return self.run_report_bug()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 549, in 
run_report_bug
  self.file_report()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 1396, in 
file_report
  url = self.crashdb.get_comment_url(self.report, ticket)
File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", 
line 247, in get_comment_url
  if not project:
  UnboundLocalError: local variable 'project' referenced before assignment

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu40
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.451
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.10
  LiveMediaBuild: Xubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200619)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: apport 2.20.11-0ubuntu40
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  groovy
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1884221/+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 1883027] Re: dump_acpi_tables.py: fix incorrect output and change format

This bug was fixed in the package apport - 2.20.11-0ubuntu42

---
apport (2.20.11-0ubuntu42) groovy; urgency=medium

  * Fix pep8 errors regarding ambiguous variables.

 -- Brian Murray   Wed, 24 Jun 2020 09:15:51 -0700

** Changed in: apport (Ubuntu Groovy)
   Status: In Progress => 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/1883027

Title:
  dump_acpi_tables.py: fix incorrect output and change format

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  In Progress
Status in apport source package in Groovy:
  Fix Released

Bug description:
  [Impact]

    dump_acpi_tables.py does not always generate 4-char table names
  (which is defined by ACPI spec), and it can miss or duplicate data of
  ACPI tables in /sys/firmware/acpi/tables.

  [Test Case]
    Tested with ACPI tables from Dell's Precision 3530. The outputs are almost 
the same as ones from "acpidump". The difference is the order of ACPI tables in 
the output but the order is not important.

1. run dump_acpi_tables.py
2. run acpidump 
3. compare the outputs

Note: acpidump is from acpica-tools

  [Regression Potential]

    Formats were changed to be the same as outputs from "acpidump", but
  known tools, such as acpiexec and fwts, by default reads outputs from
  acpidump and they do not reply on spaces and upper/lower cases.

  [Other Info]

    See original bug reports as below:

  dump_acpi_tables.py generates log files that is similar as the output
  from "acpidump" in acpica-tools. The output can be passed to other
  utilities in acpica-tools and fwts.

  It, however, has some subtle differences and some errors.

  Summary:

  1. ACPI tables have 4-char signatures - meaning SSDT's are SSDT, not
  SSDT1, SSDT2 and so on. Each table is unique by its table ID.

  Original:
    SSDT1, SSDT2, SSDT3 ...

  Changed:
    SSDT, SSDT, SSDT ...

  2. (Minor) acpidump outputs are all in upper cases

  3. (Minor) acpidump offset are aligned by data, not address

  Original:
    FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D  SAVCRDCANCRNrNPM
    1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43  VRDC

  Changed:
  FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D  SAVCRDCANCRNrNPM
     1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43  VRDC

  4. (Bug) dump_acpi_tables.py generates an extra line when data sizes
  are multiple of 16 bytes

  Original:
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44  00.HPSD.SPSD
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44 
 00.HPSD.SPSD

  Corrected:
  05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44  00.HPSD.SPSD

  5. (Bug) dump_acpi_tables.py misses an line when data sizes are
  multiple of 15 bytes

  Original:
  07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43  B..\/._SB_UBTCCC

  Corrected:
  07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43  B..\/._SB_UBTCCC
  07F0: 49 33 86 5C 2E 5F 53 42 5F 55 42 54 43 0A 80 I3.\._SB_UBTC..

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1883027/+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 1875665] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

2020-06-30 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-riscv package in Ubuntu:
  Fix Released
Status in rtkit package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Released
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux-kvm source package in Focal:
  Fix Released
Status in linux-oracle source package in Focal:
  Fix Released
Status in linux-riscv source package in Focal:
  Fix Released
Status in rtkit source package in Focal:
  Confirmed

Bug description:
  SRU Justification

  Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the
  lowlatency kernel since we expected most RT users to use that kernel.
  However we are getting RT regressions with the generic kernel. Digging
  deeper into this option, it seems to be pretty specialized and to
  require quite a bit of workload-specific configuration/tuning to be
  useful, so it doesn't really seem to make sense for a general-purpose
  kernel.

  Fix: Turn this option back off.

  Test Case: See comment #4.

  Regression Potential: This was turned on to support some docker
  functionality, so this functionality will no longer be available.
  We've had this option off for all releases prior to focal, so this
  seems acceptable.

  ---

  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665/+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 1884101] Re: [SRU] jackdbus produces high cpu load

2020-06-30 Thread Erich Eickmeyer

Unfortunately, that means this bug won't be fixed in this version of
Ubuntu.

** Changed in: jackd2 (Ubuntu Focal)
   Importance: High => Undecided

** Changed in: jackd2 (Ubuntu Focal)
   Status: Fix Committed => Won't Fix

** Changed in: jackd2 (Ubuntu Focal)
 Assignee: Erich Eickmeyer (eeickmeyer) => (unassigned)

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

Title:
  [SRU] jackdbus produces high cpu load

Status in jackd2 package in Ubuntu:
  Fix Released
Status in jackd2 source package in Focal:
  Won't Fix
Status in jackd2 source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * Users have reported issues with high CPU load when running jackd and 
 jackdbus, causing system slowdowns

   * This newer version was backported into the Ubuntu Studio Backports PPA 
 and has shown to have success in fixing this issue.

  [Test Case]

   * Attempt to run jackd and jackdbus, jackd tends to take 100% per CPU

   * Killing jackd and jackdbus reduces CPU down to nominal levels

   * Version in Ubuntu Studio Backports PPA does not have this issue,
  same version exists in Ubuntu Groovy Gorilla.

  [Regression Potential]

   * Since jackd is used by multiple professional audio applications and
  therefore there could be potential negative impact on those
  applicaitons.

   * Although that regression potential exists, multiple users have
  reported great success when using the newer version.

  [Other Info]
   
   * Although not a "bug" per se, upstream developer lamented the fact that the 
version in 20.04 is so far behind. 

   * Most audio applications and plugins in Ubuntu 20.04 have been
  developed with this version of Jackd in mind.

  
  Original bug report:

  
  if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load. jackd 
tends to take all availabl CPU power bringing the system to slow down 
remarkably. Killing jackd and jackdbus frees cpu and system load drops from 
100%/per CPU down to ~4% overall.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sct-muc1800 F pulseaudio
   /dev/snd/pcmC0D0c:   sct-muc1800 F...m pulseaudio
   /dev/snd/pcmC0D0p:   sct-muc1800 F...m pulseaudio
   /dev/snd/timer:  sct-muc1800 f pulseaudio
  CasperMD5CheckResult: skip
  Date: Thu Jun 18 18:08:25 2020
  InstallationDate: Installed on 2019-09-09 (282 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=screen
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/2020
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1884101/+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 1884326] Re: SRU the current 2.48.7 stable update

The Stable Release Update policy for GNOME says "GNOME (only the core
modules and apps, not the entirety of what is hosted on gnome.org)
(approved on 2012-06-22)" . Is librsvg part of the core modules and
apps? There has never been an SRU of librsvg before.

** Changed in: librsvg (Ubuntu Focal)
   Status: Fix Committed => Incomplete

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

Title:
  SRU the current 2.48.7 stable update

Status in librsvg package in Ubuntu:
  Fix Released
Status in librsvg source package in Focal:
  Incomplete

Bug description:
  * Impact
  That's the current GNOME stable update, which fixes a number of issues: 
https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Smoke testing by opening SVG images with eog or importing them with
  gimp can be performed to ensure there are no regressions.

  * Regression potential

  This is a bugfix-only stable micro-release, however librsvg is a core
  component with a number of reverse dependencies. A combination of
  autopkgtests and manual smoke testing to try and detect SVG rendering
  issues should be performed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1884326/+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 1884101] Proposed package upload rejected

An upload of jackd2 to focal-proposed has been rejected from the upload
queue for the following reason: "This is a version bump with a wide
variety of changes (according to Changelog.rst) that are not justified
for SRU'ing.".

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

Title:
  [SRU] jackdbus produces high cpu load

Status in jackd2 package in Ubuntu:
  Fix Released
Status in jackd2 source package in Focal:
  Fix Committed
Status in jackd2 source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * Users have reported issues with high CPU load when running jackd and 
 jackdbus, causing system slowdowns

   * This newer version was backported into the Ubuntu Studio Backports PPA 
 and has shown to have success in fixing this issue.

  [Test Case]

   * Attempt to run jackd and jackdbus, jackd tends to take 100% per CPU

   * Killing jackd and jackdbus reduces CPU down to nominal levels

   * Version in Ubuntu Studio Backports PPA does not have this issue,
  same version exists in Ubuntu Groovy Gorilla.

  [Regression Potential]

   * Since jackd is used by multiple professional audio applications and
  therefore there could be potential negative impact on those
  applicaitons.

   * Although that regression potential exists, multiple users have
  reported great success when using the newer version.

  [Other Info]
   
   * Although not a "bug" per se, upstream developer lamented the fact that the 
version in 20.04 is so far behind. 

   * Most audio applications and plugins in Ubuntu 20.04 have been
  developed with this version of Jackd in mind.

  
  Original bug report:

  
  if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load. jackd 
tends to take all availabl CPU power bringing the system to slow down 
remarkably. Killing jackd and jackdbus frees cpu and system load drops from 
100%/per CPU down to ~4% overall.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sct-muc1800 F pulseaudio
   /dev/snd/pcmC0D0c:   sct-muc1800 F...m pulseaudio
   /dev/snd/pcmC0D0p:   sct-muc1800 F...m pulseaudio
   /dev/snd/timer:  sct-muc1800 f pulseaudio
  CasperMD5CheckResult: skip
  Date: Thu Jun 18 18:08:25 2020
  InstallationDate: Installed on 2019-09-09 (282 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=screen
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/2020
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1884101/+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 1814302] Re: Quasselcore apparmor profile issue in lxd container.

This bug was fixed in the package quassel - 1:0.13.1-3ubuntu3

---
quassel (1:0.13.1-3ubuntu3) groovy; urgency=medium

  * 
d/p/lp1885436/0001-common-Disable-enum-type-stream-operators-for-Qt-5.1.patch,

d/p/lp1885436/0002-common-Always-let-QVariant-fromValue-deduce-the-type.patch,

d/p/lp1885436/0003-qa-Replace-deprecated-qVariantFromValue-by-QVariant-.patch,

d/p/lp1885436/0004-qa-Avoid-deprecation-warnings-for-QList-QSet-convers.patch,

d/p/lp1885436/0005-qa-Replace-deprecated-QString-sprintf-by-QString-asp.patch:
- Fix FTBFS due to QT 5.14 changes (LP: #1885436)
  * d/usr.bin.quasselcore:
- Update apparmor profile to allow running in lxd (LP: #1814302)

 -- Dan Streetman   Sun, 28 Jun 2020 10:54:49
-0400

** Changed in: quassel (Ubuntu Groovy)
   Status: In Progress => Fix Released

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

Title:
  Quasselcore apparmor profile issue in lxd container.

Status in AppArmor:
  Invalid
Status in apparmor package in Ubuntu:
  Invalid
Status in quassel package in Ubuntu:
  Fix Released
Status in apparmor source package in Bionic:
  Invalid
Status in quassel source package in Bionic:
  In Progress
Status in apparmor source package in Focal:
  Invalid
Status in quassel source package in Focal:
  In Progress
Status in apparmor source package in Groovy:
  Invalid
Status in quassel source package in Groovy:
  Fix Released

Bug description:
  [impact]

  quasselcore cannot start inside lxd container

  [test case]

  create lxd container, install quassel-core, check quasselcore service:

  $ systemctl status quasselcore
  ● quasselcore.service - distributed IRC client using a central core component
   Loaded: loaded (/lib/systemd/system/quasselcore.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: signal) since Tue 2020-06-30 18:32:40 UTC; 4s ago
 Docs: man:quasselcore(1)
  Process: 3853 ExecStart=/usr/bin/quasselcore --configdir=${DATADIR} 
--logfile=${LOGFILE} --loglevel=${LOGLEVEL} --port=${PORT} --listen=${LISTEN} 
(code=killed, signal=SEGV)
 Main PID: 3853 (code=killed, signal=SEGV)

  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Scheduled 
restart job, restart counter is at 7.
  Jun 30 18:32:40 lp1814302-f systemd[1]: Stopped distributed IRC client using 
a central core component.
  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Start request 
repeated too quickly.
  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Failed with 
result 'signal'.
  Jun 30 18:32:40 lp1814302-f systemd[1]: Failed to start distributed IRC 
client using a central core component.

  
  Also, the binary will segfault when run directly due to apparmor denials:

  $ /usr/bin/quasselcore 
  Segmentation fault

  [760149.590802] audit: type=1400 audit(1593542073.962:1058):
  apparmor="DENIED" operation="file_mmap" namespace="root//lxd-
  lp1814302-f_" profile="/usr/bin/quasselcore"
  name="/usr/bin/quasselcore" pid=2006430 comm="quasselcore"
  requested_mask="r" denied_mask="r" fsuid=1000110 ouid=100

  [regression potential]

  this expands the apparmor profile, so any regression would likely
  involve problems while starting due to apparmor.

  [scope]

  this is needed for b/f/g.

  this is also needed for e, but that is EOL in weeks and this is not
  important enough to bother there.

  [original description]

  
  Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04 
container. Everything up todate via apt.

  Install quassel-core. Service will not start.

  Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start.

  I then added "/usr/bin/quasselcore rm," to
  "/etc/apparmor.d/usr.bin.quasselcore".

  Set "aa-enforce /usr/bin/quasselcore". Restarted main host.

  Quasselcore service now starts and I can connect to it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1814302/+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 1865909] Re: py3compile crashed with Exception in from_package(): cannot get content of system-config-printer-common

** Information type changed from Private to Public

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

Title:
  py3compile crashed with Exception in from_package(): cannot get
  content of system-config-printer-common

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  It just bugged.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: python3-minimal 3.8.0-3ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  Date: Mon Mar  2 16:19:25 2020
  ExecutablePath: /usr/bin/py3compile
  InstallationDate: Installed on 2020-03-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220)
  InterpreterPath: /usr/bin/python3.8
  ProcCmdline: /usr/bin/python3 /usr/bin/py3compile -p 
system-config-printer-common /usr/share/system-config-printer
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.0-3ubuntu1
  PythonArgs: ['/usr/bin/py3compile', '-p', 'system-config-printer-common', 
'/usr/share/system-config-printer']
  PythonDetails: N/A
  SourcePackage: python3-defaults
  Title: py3compile crashed with Exception in from_package(): cannot get 
content of system-config-printer-common
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1865909/+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 1822712] Re: https mirrors apport-retrace crashed with SystemError in _get_primary_mirror_from_apt_sources(): cannot determine default mirror: /etc/apt/sources.list does not cont

Please provide your full /etc/apt/sources.list file so I can see what's
going on. Thanks in advance!

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

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

Title:
  https mirrors apport-retrace crashed with SystemError in
  _get_primary_mirror_from_apt_sources(): cannot determine default
  mirror: /etc/apt/sources.list does not contain a valid deb line

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  1. Have other crash occur.
  2. Click retrace locally.
  3. apport-retrace crashes.

  The only thing I can think is it's the fact that i changed my mirror to:
  deb https://mirrors.ocf.berkeley.edu/ubuntu/ disco main restricted universe 
multiverse
  deb-src https://mirrors.ocf.berkeley.edu/ubuntu/ disco main restricted 
universe multiverse

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: apport-retrace 2.20.10-0ubuntu23
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportLog:
   ERROR: apport (pid 10677) Mon Apr  1 19:40:34 2019: called for pid 8661, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 10677) Mon Apr  1 19:40:34 2019: executable: 
/usr/bin/gedit (command line "/usr/bin/gedit --gapplication-service")
   ERROR: apport (pid 10677) Mon Apr  1 19:40:34 2019: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 10677) Mon Apr  1 19:40:42 2019: wrote report 
/var/crash/_usr_bin_gedit.1000.crash
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CrashReports:
   640:1000:117:8118520:2019-04-01 20:06:04.204469680 -0700:2019-04-01 
20:06:05.204469680 -0700:/var/crash/_usr_bin_gedit.1000.crash
   640:1000:117:23602:2019-04-01 20:06:21.172740697 -0700:2019-04-01 
20:06:22.172740697 -0700:/var/crash/_usr_bin_apport-retrace.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 20:06:22 2019
  ExecutablePath: /usr/bin/apport-retrace
  InstallationDate: Installed on 2018-04-14 (352 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180414)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/apport-retrace -S system -C 
/home/username/.cache/apport/retrace -v --output 
/var/crash/_usr_bin_gedit.1000.crash /var/crash/_usr_bin_gedit.1000.crash
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.2-1
  PythonArgs: ['/usr/bin/apport-retrace', '-S', 'system', '-C', 
'/home/username/.cache/apport/retrace', '-v', '--output', 
'/var/crash/_usr_bin_gedit.1000.crash', '/var/crash/_usr_bin_gedit.1000.crash']
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  SourcePackage: apport
  Title: apport-retrace crashed with SystemError in 
_get_primary_mirror_from_apt_sources(): cannot determine default mirror: 
/etc/apt/sources.list does not contain a valid deb line
  UpgradeStatus: Upgraded to disco on 2019-01-05 (86 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1822712/+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 1878517] Re: please apply bash 5.0 patch 17

2020-06-30 Thread Matthieu Clemenceau

tested proposed package with Focal with 2 different instances with given script.
Both tests were successful. 

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

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

Title:
  please apply bash 5.0 patch 17

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

Bug description:
  This section is for Focal SRU purpose

  [Impact]
  From https://ftp.gnu.org/gnu/bash
  There were cases where bash 5.0 patch 16 reaped process substitution file 
descriptors (or FIFOs) and processes to early. This is a better fix for the 
problem that bash50-016 attempted to solve.

  [Test Case]
  This simple bash script pass when bash with patch 017 is installed
  Recommend to run it before and after installing the update to notice the 
difference

  ```
  #!/usr/bin/bash

  ouch() {
  cat < <(echo bar)
  cat "$1"
  }

  ouch2() {
  { cat; } < <(echo bar)
  cat "$1"
  }

  ouch <(echo "foo")
  ouch2 <(echo "foo")
  ```
  Expected output with the patch installed:

  foo
  bar
  foo
  bar

  [Regression Potential]
  This is an upstream patch level update with no additional modification. The 
regression potential should be fairly low. Also the patch is intended to only 
fix this problem.
  Possible regression would be unforeseen additional process substitutions that 
upstream bash would share.

  End SRU
  --
  Original Bug Description:

  I am using Ubuntu 20.04 for development and has hit a bug in bash 5.0
  patch 16.

  I can't reproduce it in pure bash, but with bats from
  https://github.com/bats-core/bats-core/ it is very easy to repro:

  ```
  # cat << EOF > ya.bats
  check() {
   echo "check $@"
   ls -l /proc/self/fd
  }

  @test "here file" {
   check -p <(echo "hey")
   false
  }
  EOF

  $ bats ya.bats
  ```

  Normally the output should contain the line

     lr-x-- 1 kir kir 64 May 14 02:01 63 -> pipe:[4616918]

  which is a result of a "here file" created by bash via <(echo "hey").

  In my testing, about 50% of runs don't have /dev/fd/63 listed.

  I found out this is a manifest of a bug introduced in bash 5.0 patch
  16 (see http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-016)

  The bug is fixed in 5.0 patch 17 (see
  http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-017).

  Please update bash to patchlevel 17.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+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 1885782] Re: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2020-06-30 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This error occurred during and upgrade of Ubuntu Server from 18.04LTS
  to 20.02LTS

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.2
  ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
  Uname: Linux 4.15.0-108-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun 30 21:46:27 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2014-12-28 (2011 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-06-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1885782/+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 1885782] [NEW] package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

2020-06-30 Thread DLambers

Public bug reported:

This error occurred during and upgrade of Ubuntu Server from 18.04LTS
to 20.02LTS

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.2
ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
Uname: Linux 4.15.0-108-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jun 30 21:46:27 2020
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2014-12-28 (2011 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to focal on 2020-06-30 (0 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This error occurred during and upgrade of Ubuntu Server from 18.04LTS
  to 20.02LTS

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.2
  ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
  Uname: Linux 4.15.0-108-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun 30 21:46:27 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2014-12-28 (2011 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-06-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1885782/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-06-30 Thread Michael Scott Roelker

#63 and #65 did not work for me, resulted in dummy audio - #66 also did
not work for me.

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-06-30 Thread Michael Scott Roelker

for #78 my specs

Linux michaelroelker-Lenovo-YOGA-C930-13IKB 5.4.0-39-generic #43-Ubuntu
SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

 List of CAPTURE Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC298 Analog [ALC298 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Headset [Logitech USB Headset], device 0: USB Audio [USB Audio]
  Subdevices: 0/1
  Subdevice #0: subdevice #0

experiencing issues in 18.04 and 20.04. headset workaround for now.

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1884281] Re: UC20 images do not use predictable interface names on RPi4

2020-06-30 Thread durex

As a sidenote: once the 'net.ifnames=0' is removed, indeed the eth0 and
wlan0 still get their old 'eth0' and 'wlan0' names, but aside the
aesthetics: the whole purpose of the predictable naming suddenly does
function: all USB cards get a predictable name, based on MAC Address...
so I'm guessing that's why the status of this bug is 'invalid'. Thanks
to whomever worked on this. Works beautifully and makes life a whole lot
easier!

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

Title:
  UC20 images do not use predictable interface names on RPi4

Status in snapd:
  Triaged
Status in linux-raspi package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  Image tested: http://cdimage.ubuntu.com/ubuntu-core/20/dangerous-
  beta/pending/ubuntu-core-20-arm64+raspi.img.xz

  Boot the image and check the naming of the ethernet interfaces. On
  most devices (amd64, rpi3 etc) systemd predicatable interface naming
  is applied e.g. enxb827eb7d1eee. However on specifically RPi4 devices
  traditional naming is used e.g. eth0, eth1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1884281/+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 1884281] Re: UC20 images do not use predictable interface names on RPi4

2020-06-30 Thread durex

Wow, am I glad I found this thread... I've been spending literally days
trying to find out why I didn't get the predictable names. Never thought
it would be a bug.

I have to say: whoever works on the predictable naming scheme is doing a
very noble job... not having these predictable names is just a
nightmare.

Can I do something to help? I'd like to see you guys succeed in this
one.

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

Title:
  UC20 images do not use predictable interface names on RPi4

Status in snapd:
  Triaged
Status in linux-raspi package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  Image tested: http://cdimage.ubuntu.com/ubuntu-core/20/dangerous-
  beta/pending/ubuntu-core-20-arm64+raspi.img.xz

  Boot the image and check the naming of the ethernet interfaces. On
  most devices (amd64, rpi3 etc) systemd predicatable interface naming
  is applied e.g. enxb827eb7d1eee. However on specifically RPi4 devices
  traditional naming is used e.g. eth0, eth1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1884281/+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 1885773] Re: [4125, recording] Recording problem - input device is not listed on my machine.

2020-06-30 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  [4125, recording] Recording problem - input device is not listed on my
  machine.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have connected two input device to my machine (Intel BOXNUC8). One
  is headphones, and the other is bluetooth speaker. I also have an HDMI
  monitor which allegedly supports input device. However, the only input
  device which is listed in the sound setting device is the NUC's
  internal microphone. The bug report tools suggested I'd use
  pavucontrol or the gnome setting interface. Pavucontrol does list the
  bluetooth speaker (under monitors). I also see the headphones there,
  listed as built-in input device but I can't seem to get them to work
  properly.

  The main bug here is that I won't see the input device listed under
  the computer settings.

  release: 20.04

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  geffen27236 F pulseaudio
   /dev/snd/pcmC0D0c:   geffen27236 F...m pulseaudio
   /dev/snd/pcmC0D0p:   geffen27236 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 30 22:18:26 2020
  InstallationDate: Installed on 2020-04-12 (79 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: 4125
  Symptom_Type: None of the above
  Title: [4125, recording] Recording problem
  UpgradeStatus: Upgraded to focal on 2020-04-28 (62 days ago)
  dmi.bios.date: 06/18/2019
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0073.2019.0618.1409
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72692-308
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0073.2019.0618.1409:bd06/18/2019:svnIntel(R)ClientSystems:pnNUC8i5BEH:pvrJ72747-306:rvnIntelCorporation:rnNUC8BEB:rvrJ72692-308:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: BE
  dmi.product.name: NUC8i5BEH
  dmi.product.sku: BOXNUC8i5BEH
  dmi.product.version: J72747-306
  dmi.sys.vendor: Intel(R) Client Systems
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-06-08T16:19:26.048126

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1885773/+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 1885773] [NEW] [4125, recording] Recording problem - input device is not listed on my machine.

You have been subscribed to a public bug:

I have connected two input device to my machine (Intel BOXNUC8). One is
headphones, and the other is bluetooth speaker. I also have an HDMI
monitor which allegedly supports input device. However, the only input
device which is listed in the sound setting device is the NUC's internal
microphone. The bug report tools suggested I'd use pavucontrol or the
gnome setting interface. Pavucontrol does list the bluetooth speaker
(under monitors). I also see the headphones there, listed as built-in
input device but I can't seem to get them to work properly.

The main bug here is that I won't see the input device listed under the
computer settings.

release: 20.04

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Uname: Linux 5.4.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  geffen27236 F pulseaudio
 /dev/snd/pcmC0D0c:   geffen27236 F...m pulseaudio
 /dev/snd/pcmC0D0p:   geffen27236 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 30 22:18:26 2020
InstallationDate: Installed on 2020-04-12 (79 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: 4125
Symptom_Type: None of the above
Title: [4125, recording] Recording problem
UpgradeStatus: Upgraded to focal on 2020-04-28 (62 days ago)
dmi.bios.date: 06/18/2019
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BECFL357.86A.0073.2019.0618.1409
dmi.board.name: NUC8BEB
dmi.board.vendor: Intel Corporation
dmi.board.version: J72692-308
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0073.2019.0618.1409:bd06/18/2019:svnIntel(R)ClientSystems:pnNUC8i5BEH:pvrJ72747-306:rvnIntelCorporation:rnNUC8BEB:rvrJ72692-308:cvnIntelCorporation:ct35:cvr2.0:
dmi.product.family: BE
dmi.product.name: NUC8i5BEH
dmi.product.sku: BOXNUC8i5BEH
dmi.product.version: J72747-306
dmi.sys.vendor: Intel(R) Client Systems
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-06-08T16:19:26.048126

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


** Tags: amd64 apport-bug focal
-- 
[4125, recording] Recording problem - input device is not listed on my machine. 
https://bugs.launchpad.net/bugs/1885773
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver in Ubuntu.

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

[Touch-packages] [Bug 1884887] Re: rsyslogd dmesg unit leaves /var/log/dmesg* world readable

2020-06-30 Thread Steve Beattie

Updated groovy debdiff against the merge from debian currently in
groovy-proposed.

** Patch added: "rsyslog_8.2006.0-2ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1884887/+attachment/5388559/+files/rsyslog_8.2006.0-2ubuntu2.debdiff

** Patch removed: "rsyslog_8.2001.0-1ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1884887/+attachment/5386928/+files/rsyslog_8.2001.0-1ubuntu2.debdiff

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

Title:
  rsyslogd dmesg unit leaves /var/log/dmesg* world readable

Status in rsyslog package in Ubuntu:
  New

Bug description:
  [Impact]

  The rsyslog dmesg systemd unit /lib/systemd/system/dmesg.service in
  eoan, focal, and groovy create /var/log/dmesg* with the following
  permissions:

-rw-r--r-- 1 root adm 45146 Jun 16 12:32 /var/log/dmesg

  Most other system logs in /var/log/ are only readable by root and
  group adm.

  While it's true that the kernel dmesg buffer by default can be read by
  anyone using the dmesg(1) command, this can be disabled by setting the
  sysctl kernel.dmesg_restrict to 1, but doing so as a hardening measure
  is thwarted by the world readable nature of /var/log/dmesg.

  The reason dmesg output is sensitive is that it sometimes contains
  kernel addresses for diagnosing kernel problems, but attackers looking
  to attack a kernel are also interested in kernel addresses and other
  information that shows up there.

  [Test Case]

  To reproduce:

   $ ls -l /var/log/dmesg*

  should show only root and group adm access like so:

   -rw-r- 1 root adm 50178 Jun 23 12:55 /var/log/dmesg
   -rw-r- 1 root adm 50217 Jun 23 12:55 /var/log/dmesg.0
   -rw-r- 1 root adm 13941 Jun 23 12:47 /var/log/dmesg.1.gz

  and not world readable:

   -rw-r--r-- 1 root adm 45146 Jun 16 12:32 /var/log/dmesg

  [Regression Potential]

  It's possible tools like apport and others might expect /var/log/dmesg
  to be world-readable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1884887/+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 1876018] Re: 40-vm-hotadd.rules attempts to set non-existent sysfs parameters

** Description changed:

+ [impact]
+ 
+ 40-vm-hotadd.rules unconditionally tries onlining memory, which results
+ in logged error messages if the memory is already online
+ 
+ [test case]
+ 
+ since this rules file restricts operation to only hyper-v or xen guests,
+ boot a hyper-v or xen vm guest, and check for logged error msgs like:
+ 
+ Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
+ /usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
+ ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
+ argument
+ 
+ alternately, to test on a vm guest other than hyper-v or xen,
+ comment/remove the 'GOTO="vm_hotadd_end"' line from the rules file and
+ reboot.
+ 
+ [regression potential]
+ 
+ as this adds a check before attempting to online memory for hyper-v and
+ xen vm guests, any regression would likely involve failure to correctly
+ online all memory on those guest platforms.
+ 
+ [scope]
+ 
+ this rule has been around for a long time, so is needed for x/b/f/g.
+ 
+ [original description]
+ 
  In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
  tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes resulting
  in warnings such as:
  
  Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
  /usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
  ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
  argument
  
  Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
  removed, or something else. This behavior is present on systems upgraded
  from 18.04 (via d-r-u) as well as new focal systems, upon first reboot
  of the VM.
  
  udev: 245.4-4ubuntu3

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

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

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

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

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

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

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

** Changed in: systemd (Ubuntu Focal)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

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

Bug description:
  [impact]

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

  [test case]

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

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

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

  [regression potential]

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

  [scope]

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

  [original description]

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

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

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

  udev: 245.4-4ubuntu3

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

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

[Touch-packages] [Bug 1855747] Re: systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop

2020-06-30 Thread costinel

also other people complained

https://www.reddit.com/r/VFIO/comments/90tg4h/after_loading_vfiopci_instead_of_nvidia_my_dmesg/

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

Title:
  systemd-udevd appears to be attempting to load Nvidia kernel modules
  in a tight loop

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Expired
Status in systemd package in Ubuntu:
  Expired

Bug description:
  I'm seeing these lines repeated:

  ```
  Dec 09 12:01:45 surprise systemd-udevd[731]: nvidia: Process 
'/usr/bin/nvidia-smi' failed with exit code 9.
  Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe 
nvidia-modeset' failed with exit code 1.
  Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe 
nvidia-drm' failed with exit code 1.
  Dec 09 12:01:47 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe 
nvidia-uvm' failed with exit code 1.
  Dec 09 12:01:48 surprise systemd-udevd[731]: nvidia: Process 
'/usr/bin/nvidia-smi' failed with exit code 9.
  Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe 
nvidia-modeset' failed with exit code 1.
  Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe 
nvidia-drm' failed with exit code 1.
  Dec 09 12:01:50 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe 
nvidia-uvm' failed with exit code 1.
  ```

  My system has been up ~an hour:

  $ uptime
   12:02:28 up  1:00,  1 user,  load average: 4.52, 4.80, 5.50

  and I've seen a lot of these:

  $ journalctl -u systemd-udevd.service -b0 | grep -c "exit code 9"
  1333

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 243-3ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13
  Uname: Linux 5.3.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: i3
  CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules
  Date: Mon Dec  9 11:59:10 2019
  InstallationDate: Installed on 2019-05-07 (215 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2019-11-15 (23 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.apport.crashdb.conf: [modified]
  modified.conffile..etc.udev.udev.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-25T16:40:26.261317
  mtime.conffile..etc.udev.udev.conf: 2019-11-28T09:22:42.096686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1855747/+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 1855747] Re: systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop

2020-06-30 Thread costinel

>Kai-Heng Feng (kaihengfeng) wrote on 2019-12-11:   #4

> Can you please run `sudo update-initramfs -u -k all` and see if the
issue still happens?

yes this persists even after that.

I have a nvidia card but I want to blacklist it. even blacklisted, the
systemd-udevd /lib/udev/rules.d/71-nvidia.rules attempt to run the rules
forever.

moving /lib/udev/rules.d/71-nvidia.rules away from udev rules search
path fixes that, but that's not the correct solution. why does systemd-
udev insist repeating instead of failing after first try?

18.04 lts here. drivers nvidia-driver-390

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

Title:
  systemd-udevd appears to be attempting to load Nvidia kernel modules
  in a tight loop

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Expired
Status in systemd package in Ubuntu:
  Expired

Bug description:
  I'm seeing these lines repeated:

  ```
  Dec 09 12:01:45 surprise systemd-udevd[731]: nvidia: Process 
'/usr/bin/nvidia-smi' failed with exit code 9.
  Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe 
nvidia-modeset' failed with exit code 1.
  Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe 
nvidia-drm' failed with exit code 1.
  Dec 09 12:01:47 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe 
nvidia-uvm' failed with exit code 1.
  Dec 09 12:01:48 surprise systemd-udevd[731]: nvidia: Process 
'/usr/bin/nvidia-smi' failed with exit code 9.
  Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe 
nvidia-modeset' failed with exit code 1.
  Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe 
nvidia-drm' failed with exit code 1.
  Dec 09 12:01:50 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe 
nvidia-uvm' failed with exit code 1.
  ```

  My system has been up ~an hour:

  $ uptime
   12:02:28 up  1:00,  1 user,  load average: 4.52, 4.80, 5.50

  and I've seen a lot of these:

  $ journalctl -u systemd-udevd.service -b0 | grep -c "exit code 9"
  1333

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 243-3ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13
  Uname: Linux 5.3.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu13
  Architecture: amd64
  CurrentDesktop: i3
  CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules
  Date: Mon Dec  9 11:59:10 2019
  InstallationDate: Installed on 2019-05-07 (215 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2019-11-15 (23 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.apport.crashdb.conf: [modified]
  modified.conffile..etc.udev.udev.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-25T16:40:26.261317
  mtime.conffile..etc.udev.udev.conf: 2019-11-28T09:22:42.096686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1855747/+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 1814302] Re: Quasselcore apparmor profile issue in lxd container.

** Description changed:

- Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04
- container. Everything up todate via apt.
+ [impact]
+ 
+ quasselcore cannot start inside lxd container
+ 
+ [test case]
+ 
+ create lxd container, install quassel-core, check quasselcore service:
+ 
+ $ systemctl status quasselcore
+ ● quasselcore.service - distributed IRC client using a central core component
+  Loaded: loaded (/lib/systemd/system/quasselcore.service; enabled; vendor 
preset: enabled)
+  Active: failed (Result: signal) since Tue 2020-06-30 18:32:40 UTC; 4s ago
+Docs: man:quasselcore(1)
+ Process: 3853 ExecStart=/usr/bin/quasselcore --configdir=${DATADIR} 
--logfile=${LOGFILE} --loglevel=${LOGLEVEL} --port=${PORT} --listen=${LISTEN} 
(code=killed, signal=SEGV)
+Main PID: 3853 (code=killed, signal=SEGV)
+ 
+ Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Scheduled 
restart job, restart counter is at 7.
+ Jun 30 18:32:40 lp1814302-f systemd[1]: Stopped distributed IRC client using 
a central core component.
+ Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Start request 
repeated too quickly.
+ Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Failed with 
result 'signal'.
+ Jun 30 18:32:40 lp1814302-f systemd[1]: Failed to start distributed IRC 
client using a central core component.
+ 
+ 
+ Also, the binary will segfault when run directly due to apparmor denials:
+ 
+ $ /usr/bin/quasselcore 
+ Segmentation fault
+ 
+ [760149.590802] audit: type=1400 audit(1593542073.962:1058):
+ apparmor="DENIED" operation="file_mmap" namespace="root//lxd-
+ lp1814302-f_" profile="/usr/bin/quasselcore"
+ name="/usr/bin/quasselcore" pid=2006430 comm="quasselcore"
+ requested_mask="r" denied_mask="r" fsuid=1000110 ouid=100
+ 
+ [regression potential]
+ 
+ this expands the apparmor profile, so any regression would likely
+ involve problems while starting due to apparmor.
+ 
+ [scope]
+ 
+ this is needed for b/f/g.
+ 
+ this is also needed for e, but that is EOL in weeks and this is not
+ important enough to bother there.
+ 
+ [original description]
+ 
+ 
+ Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04 
container. Everything up todate via apt.
  
  Install quassel-core. Service will not start.
  
  Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start.
  
  I then added "/usr/bin/quasselcore rm," to
  "/etc/apparmor.d/usr.bin.quasselcore".
  
  Set "aa-enforce /usr/bin/quasselcore". Restarted main host.
  
  Quasselcore service now starts and I can connect to it.

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

Title:
  Quasselcore apparmor profile issue in lxd container.

Status in AppArmor:
  Invalid
Status in apparmor package in Ubuntu:
  Invalid
Status in quassel package in Ubuntu:
  In Progress
Status in apparmor source package in Bionic:
  Invalid
Status in quassel source package in Bionic:
  In Progress
Status in apparmor source package in Focal:
  Invalid
Status in quassel source package in Focal:
  In Progress
Status in apparmor source package in Groovy:
  Invalid
Status in quassel source package in Groovy:
  In Progress

Bug description:
  [impact]

  quasselcore cannot start inside lxd container

  [test case]

  create lxd container, install quassel-core, check quasselcore service:

  $ systemctl status quasselcore
  ● quasselcore.service - distributed IRC client using a central core component
   Loaded: loaded (/lib/systemd/system/quasselcore.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: signal) since Tue 2020-06-30 18:32:40 UTC; 4s ago
 Docs: man:quasselcore(1)
  Process: 3853 ExecStart=/usr/bin/quasselcore --configdir=${DATADIR} 
--logfile=${LOGFILE} --loglevel=${LOGLEVEL} --port=${PORT} --listen=${LISTEN} 
(code=killed, signal=SEGV)
 Main PID: 3853 (code=killed, signal=SEGV)

  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Scheduled 
restart job, restart counter is at 7.
  Jun 30 18:32:40 lp1814302-f systemd[1]: Stopped distributed IRC client using 
a central core component.
  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Start request 
repeated too quickly.
  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Failed with 
result 'signal'.
  Jun 30 18:32:40 lp1814302-f systemd[1]: Failed to start distributed IRC 
client using a central core component.

  
  Also, the binary will segfault when run directly due to apparmor denials:

  $ /usr/bin/quasselcore 
  Segmentation fault

  [760149.590802] audit: type=1400 audit(1593542073.962:1058):
  apparmor="DENIED" operation="file_mmap" namespace="root//lxd-
  lp1814302-f_" profile="/usr/bin/quasselcore"
  name="/usr/bin/quasselcore" pid=2006430 comm="quasselcore"
  requested_mask="r" denied_mask="r" fsuid=1000110 ouid=100

[Touch-packages] [Bug 1814302] Re: Quasselcore apparmor profile issue in lxd container.

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

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

** Also affects: apparmor (Ubuntu Groovy)
   Importance: Undecided
   Status: Confirmed

** Also affects: quassel (Ubuntu Groovy)
   Importance: Undecided
   Status: Confirmed

** Also affects: apparmor (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: quassel (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: apparmor (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: apparmor (Ubuntu Focal)
   Status: New => Invalid

** Changed in: apparmor (Ubuntu Groovy)
   Status: Confirmed => Invalid

** Changed in: apparmor
   Status: New => Invalid

** Changed in: quassel (Ubuntu Focal)
   Status: New => In Progress

** Changed in: quassel (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: quassel (Ubuntu Groovy)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: quassel (Ubuntu Focal)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: quassel (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: quassel (Ubuntu Groovy)
   Importance: Undecided => Medium

** Changed in: quassel (Ubuntu Focal)
   Importance: Undecided => Medium

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

** Changed in: quassel (Ubuntu Groovy)
   Status: Confirmed => In Progress

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

Title:
  Quasselcore apparmor profile issue in lxd container.

Status in AppArmor:
  Invalid
Status in apparmor package in Ubuntu:
  Invalid
Status in quassel package in Ubuntu:
  In Progress
Status in apparmor source package in Bionic:
  Invalid
Status in quassel source package in Bionic:
  In Progress
Status in apparmor source package in Focal:
  Invalid
Status in quassel source package in Focal:
  In Progress
Status in apparmor source package in Groovy:
  Invalid
Status in quassel source package in Groovy:
  In Progress

Bug description:
  Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04
  container. Everything up todate via apt.

  Install quassel-core. Service will not start.

  Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start.

  I then added "/usr/bin/quasselcore rm," to
  "/etc/apparmor.d/usr.bin.quasselcore".

  Set "aa-enforce /usr/bin/quasselcore". Restarted main host.

  Quasselcore service now starts and I can connect to it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1814302/+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 1885749] Re: Enhancement: Remove default Emoji shortcuts

2020-06-30 Thread Gunnar Hjalmarsson

Thanks for your report.

The conflict you point at is unfortunate. Nevertheless, removing those
shortcuts is not an option. Especially Ctrl+Shift+u is a well
established method on Linux to type characters which are not available
via the keyboard layout you are using:

https://help.ubuntu.com/stable/ubuntu-help/tips-
specialchars.html#ctrlshiftu

Ctrl+Shift+e is newer, but probably used and appreciated by many users.

Your bug makes me think of this IBus issue:

https://github.com/ibus/ibus/issues/2163

That proved to be an Ubuntu specific bug which has been fixed in groovy
but not (yet) in focal. Fixing it in focal would be a way to improve the
situation. If you want that to happen, please file an ibus bug as I
suggested in my latest comment at that issue.

I think you make a too big deal of the fact that ibus-setup is not
searchable in Ubuntu. It's not an Ubuntu specific thing, btw, but it's
the same for GNOME irrespective of distro:

https://github.com/ibus/ibus/commit/66141bbc

Alt+F2 followed by ibus-setup is not "extremely difficult". But indeed,
you need be aware of the possibility to change it that way.

** Bug watch added: github.com/ibus/ibus/issues #2163
   https://github.com/ibus/ibus/issues/2163

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

Title:
  Enhancement: Remove default Emoji shortcuts

Status in ibus package in Ubuntu:
  New

Bug description:
  Current Situation
  ===

  (1) 
  Per default ibus preferences are hidden in Ubuntu
  (I would say it's very difficult to reach ibus feature)

  (2) 
  ibus has two default shortcuts, apparently for Emoji-something: 
 - Ctrl+shift+e 
 - Ctrl+shift+u

  (2.1) 
  These shortcuts can prevent shortcuts from other applications being used (one 
example: VSCode's "show files"

  (2.2) 
  Because of (1) it's extremely difficult to change these shortcuts, if they 
cause any problems - Especially because of (2.3).

  (2.3) 
  The user has no way of knowing that ibus introduced these shortcuts (because 
they would only use Settings->Region & Language, which does not show any 
shortcut options)

  (3)
  I guess the Emoji shortcuts ( (2) ) have no benefit for a normal user. Reason 
(guess): The normal user would not understand what to do after pressing the 
shortcut)

  
  Suggestion
  
  Remove shortcuts as a default setting

  
  Misc
  
  - Why is this bug not filed in github.com/ibus/ibus/issues?
-> Because in ibus as standalone, where the user has a direction connection 
to it, it might make sense to keep the shortcuts. For the moment I would say 
this is a Ubuntu related issue, as ubuntu is hiding the dialog. (... why is the 
dialog gui even installed, if we don't was to show it? ...)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2 [modified: 
usr/share/applications/org.freedesktop.IBus.Setup.desktop]
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  1 00:55:25 2020
  InstallationDate: Installed on 2020-06-29 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1885749/+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 1882583] Re: [SRU] Enable support for Victoria Cloud Archive

Hello Corey, or anyone else affected,

Accepted software-properties into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/software-
properties/0.98.9.1 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: software-properties (Ubuntu Focal)
   Status: Triaged => 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 software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1882583

Title:
  [SRU] Enable support for Victoria Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Focal:
  Fix Committed
Status in software-properties source package in Groovy:
  Fix Released

Bug description:
  Please add support for:

 cloud-archive:victoria
 cloud-archive:victoria-proposed

  This will also need to be SRU'd back to focal.

  [Impact]
  End users have to manually enable the victoria cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:victoria
  sudo add-apt-repository cloud-archive:victoria-proposed

  [Regression potential]
  Limited - just a data item addition

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

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

[Touch-packages] [Bug 1883880] Re: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic

2020-06-30 Thread Harry van Haaren (Intel)

Hey Folks,

Apologies I'm not familiar with the SRU testing process. I'd like to
help - have an 18.04 setup for testing here. Is there an easy way to add
the test-build PPA and just do an apt update && apt install binutils?

https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4105/+packages

Regards, -Harry

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

Title:
  fix non-8-bit x86 displacements breaking AVX512 builds on Bionic

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

Bug description:
  [Impact]

   * the assembler scales non 8 bit cases which was identified
 to break e.g. some AVX512 code. It is nasty as it isn't a compile/link/ 
 time error. Instead the instructions might silently be corrupted until 
 running. Things might even work on some but fail on other systems if 
 e.g. the AVX code paths only run on newer chips.

* The fix is upstream for a while and not re-changed again. Furthermore 
  it is in several Ubuntu releases without bugs due to that, which should 
  make the backport rather safe.

  [Test Case]

   * Simple example to trigger the bug:

  echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d
  avx.o | grep vmovaps

  The expected output is that the objdump output matches the vmovaps
  instruction input. When using binutils with the bug, the initial 0x40
  will be incorrect.

  Working:
  $ echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | 
grep vmovaps
 0: 62 f1 7c 48 28 04 05 vmovaps 0x40(,%rax,1),%zmm0
  Failing:
  $ echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | 
grep vmovaps
 0: 62 f1 7c 48 28 04 05 vmovaps 0x1(,%rax,1),%zmm0

  [Regression Potential]

   * Well, this is a double edged sword. On one hand this is fortunately a 
 small change and only affects something formerly clearly broken. So it 
 should be good and only change cases formerly being bad.
 But OTOH binutils areused in so many cases that I feel unable to say
 "nothing will happen". The change goes to the gnu assembler, so that is 
 the place to look out for regressions.

  [Other Info]
   
   * needs a sponsor experienced with binutils to check potential pitfalls


  
  ---

  
  Hi,
  DPDK has run into some issues in the past
   https://bugs.dpdk.org/show_bug.cgi?id=97
   https://bugs.dpdk.org/show_bug.cgi?id=249

  Eventually the issues got resolved in binutils via
   https://sourceware.org/bugzilla/show_bug.cgi?id=23465

  After binutils is fixed people rebuilding DPDK themselve can use
   http://patches.dpdk.org/patch/71679/
  to gain more performance while on Bionics bintuils level.

  Note: Bionic is on DPDK 17.11.x which will not get further stable release 
afaik. But quite often people build their own DPDK. In fact this came up as a 
request from Openvswitch upstream/Intel to allow such builds on Bionic.
  I'd ping those people about the bug and ask them to participate in the 
verification if this becomes an SRU.

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

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

[Touch-packages] [Bug 1885755] [NEW] systemd 245.6-1ubuntu1 ADT test failure with linux-5.8 5.8.0-3.4

2020-06-30 Thread Seth Forshee

Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/s/systemd/20200630_154532_b7979@/log.gz
arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/s/systemd/20200630_155538_0c63d@/log.gz
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/s/systemd/20200630_162720_b3e1b@/log.gz
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/s390x/s/systemd/20200630_140417_c5bdb@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  systemd 245.6-1ubuntu1 ADT test failure with linux-5.8 5.8.0-3.4

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/s/systemd/20200630_154532_b7979@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/s/systemd/20200630_155538_0c63d@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/s/systemd/20200630_162720_b3e1b@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/s390x/s/systemd/20200630_140417_c5bdb@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885755/+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 1855514] Re: ibus preferences do not show up in search or indicator bar

2020-06-30 Thread DarkTrick

I think I got a better picture. Thank you very much for your help!

I set this bug to Invalid.
I filed a new bug explicitly going after the shortcut settings in Ubuntu: 
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1885749

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

Title:
  ibus preferences do not show up in search or indicator bar

Status in ibus package in Ubuntu:
  Invalid

Bug description:
  This might be two separate bugs. But I feel like they have the same
  root, so I reported them as one.

  Remarks:
  [1] This report is *not* related to bug 1854610 in ibus-anthy (Ubuntu) "No 
Japanese input possible after upgrade from 19.04 to 19.10" [Undecided,New] 
https://launchpad.net/bugs/1854610

  [2] This report might be related to
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463, but I'm
  not sure. Someone with more technical knowledge should look into this.

   1 ---
  steps to reproduce:
  1) Have a fresh ubuntu 19.10 installation
  2) install ibus and ibus-anthy
  3) press windows key to open all applications
  4) type in ibus

  Actual:
  5) ibus settings will not show up

  Expected:
  5) ibus settings show up

  Workaround:
  6) open Software center
  7) search for ibus
  8) click "launch there"

   2 --
  steps to reproduce:
  1) Have a fresh Ubuntu 19.10 installation
  2) install ibus and ibus-anthy
  3) Set input method to "ibus"
  4) restart

  Actual:
  5) ibus preferences do not show up in the top bar at the indicators

  Expected
  6) "ibus preferences" is visible at the top bar inside the indicators area.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.21-1~exp2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 13:10:27 2019
  SourcePackage: ibus
  UpgradeStatus: no upgrade log present

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1855514/+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 1885749] [NEW] Enhancement: Remove default Emoji shortcuts

2020-06-30 Thread DarkTrick

Public bug reported:

Current Situation
===

(1) 
Per default ibus preferences are hidden in Ubuntu
(I would say it's very difficult to reach ibus feature)

(2) 
ibus has two default shortcuts, apparently for Emoji-something: 
   - Ctrl+shift+e 
   - Ctrl+shift+u

(2.1) 
These shortcuts can prevent shortcuts from other applications being used (one 
example: VSCode's "show files"

(2.2) 
Because of (1) it's extremely difficult to change these shortcuts, if they 
cause any problems - Especially because of (2.3).

(2.3) 
The user has no way of knowing that ibus introduced these shortcuts (because 
they would only use Settings->Region & Language, which does not show any 
shortcut options)

(3)
I guess the Emoji shortcuts ( (2) ) have no benefit for a normal user. Reason 
(guess): The normal user would not understand what to do after pressing the 
shortcut)


Suggestion

Remove shortcuts as a default setting


Misc

- Why is this bug not filed in github.com/ibus/ibus/issues?
  -> Because in ibus as standalone, where the user has a direction connection 
to it, it might make sense to keep the shortcuts. For the moment I would say 
this is a Ubuntu related issue, as ubuntu is hiding the dialog. (... why is the 
dialog gui even installed, if we don't was to show it? ...)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ibus 1.5.22-2ubuntu2 [modified: 
usr/share/applications/org.freedesktop.IBus.Setup.desktop]
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Uname: Linux 5.4.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul  1 00:55:25 2020
InstallationDate: Installed on 2020-06-29 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ibus (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 ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1885749

Title:
  Enhancement: Remove default Emoji shortcuts

Status in ibus package in Ubuntu:
  New

Bug description:
  Current Situation
  ===

  (1) 
  Per default ibus preferences are hidden in Ubuntu
  (I would say it's very difficult to reach ibus feature)

  (2) 
  ibus has two default shortcuts, apparently for Emoji-something: 
 - Ctrl+shift+e 
 - Ctrl+shift+u

  (2.1) 
  These shortcuts can prevent shortcuts from other applications being used (one 
example: VSCode's "show files"

  (2.2) 
  Because of (1) it's extremely difficult to change these shortcuts, if they 
cause any problems - Especially because of (2.3).

  (2.3) 
  The user has no way of knowing that ibus introduced these shortcuts (because 
they would only use Settings->Region & Language, which does not show any 
shortcut options)

  (3)
  I guess the Emoji shortcuts ( (2) ) have no benefit for a normal user. Reason 
(guess): The normal user would not understand what to do after pressing the 
shortcut)

  
  Suggestion
  
  Remove shortcuts as a default setting

  
  Misc
  
  - Why is this bug not filed in github.com/ibus/ibus/issues?
-> Because in ibus as standalone, where the user has a direction connection 
to it, it might make sense to keep the shortcuts. For the moment I would say 
this is a Ubuntu related issue, as ubuntu is hiding the dialog. (... why is the 
dialog gui even installed, if we don't was to show it? ...)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2 [modified: 
usr/share/applications/org.freedesktop.IBus.Setup.desktop]
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  1 00:55:25 2020
  InstallationDate: Installed on 2020-06-29 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1885749/+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 1855514] Re: ibus preferences do not show up in search or indicator bar

2020-06-30 Thread DarkTrick

** Changed in: ibus (Ubuntu)
   Status: Opinion => Invalid

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

Title:
  ibus preferences do not show up in search or indicator bar

Status in ibus package in Ubuntu:
  Invalid

Bug description:
  This might be two separate bugs. But I feel like they have the same
  root, so I reported them as one.

  Remarks:
  [1] This report is *not* related to bug 1854610 in ibus-anthy (Ubuntu) "No 
Japanese input possible after upgrade from 19.04 to 19.10" [Undecided,New] 
https://launchpad.net/bugs/1854610

  [2] This report might be related to
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463, but I'm
  not sure. Someone with more technical knowledge should look into this.

   1 ---
  steps to reproduce:
  1) Have a fresh ubuntu 19.10 installation
  2) install ibus and ibus-anthy
  3) press windows key to open all applications
  4) type in ibus

  Actual:
  5) ibus settings will not show up

  Expected:
  5) ibus settings show up

  Workaround:
  6) open Software center
  7) search for ibus
  8) click "launch there"

   2 --
  steps to reproduce:
  1) Have a fresh Ubuntu 19.10 installation
  2) install ibus and ibus-anthy
  3) Set input method to "ibus"
  4) restart

  Actual:
  5) ibus preferences do not show up in the top bar at the indicators

  Expected
  6) "ibus preferences" is visible at the top bar inside the indicators area.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.21-1~exp2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 13:10:27 2019
  SourcePackage: ibus
  UpgradeStatus: no upgrade log present

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1855514/+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 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

2020-06-30 Thread Julian Andres Klode

@rbalint As said before the kernel messages and bugs are irrelevant and
wrong. They pretend like intel_pstate is different, when in fact it's
this script that is configuring it here. And yes, it needs OS config.

Nor do other distros not do this, but we do it differently. We set the
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y option, and then transition to
that at the end of the boot. Other distributions do not set
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE and hence the kernel has
powersave as the default.

By removing this script, we are diverging from other distros, not
becoming closer to them - for pstates, anyway.

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

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during bootup. It's not clear to me that's
  actually useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1885717] Re: /etc/update-motd.d/50-motd-news not executable

2020-06-30 Thread Steve Langasek

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

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

Title:
  /etc/update-motd.d/50-motd-news not executable

Status in base-files package in Ubuntu:
  Incomplete

Bug description:
  On new installed 18.04, just caught a failed process to start: motd-
  news

  root@xps13 ~# systemctl list-units --state=failed
UNIT   LOAD   ACTIVE SUBDESCRIPTION 
 
  ● motd-news.service  loaded failed failed Message of the Day  
 

  Looking close:

  root@xps13 ~# systemctl status motd-news
  ● motd-news.service - Message of the Day
 Loaded: loaded (/lib/systemd/system/motd-news.service; static; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Tue 2020-06-30 09:16:54 CEST; 5h 
6min ago
   Docs: man:update-motd(8)
Process: 12505 ExecStart=/etc/update-motd.d/50-motd-news --force 
(code=exited, status=203/EXEC)
   Main PID: 12505 (code=exited, status=203/EXEC)

  Jun 30 09:16:54 elxa7r5lmh2 systemd[1]: Starting Message of the Day...
  Jun 30 09:16:54 elxa7r5lmh2 systemd[1]: motd-news.service: Main process 
exited, code=exited, status=203/EXEC
  Jun 30 09:16:54 elxa7r5lmh2 systemd[1]: motd-news.service: Failed with result 
'exit-code'.
  Jun 30 09:16:54 elxa7r5lmh2 systemd[1]: Failed to start Message of the Day.

  I could fix by a simple "chmod +x" to the file.

  root@xps13 ~# /etc/update-motd.d/50-motd-news
  fish: The file “/etc/update-motd.d/50-motd-news” is not executable by this 
user
  root@xps13 ~# chmod 755 /etc/update-motd.d/50-motd-news
  root@xps13 ~# /etc/update-motd.d/50-motd-news

  So there are 2 bugs here:
  1) missing executable permission on file
  2) executable placement inside /etc directory


  Extra info:
  1) Description:Ubuntu 18.04.4 LTS
  Release:18.04
  2) base-files:
Installed: 10.1ubuntu2.8
Candidate: 10.1ubuntu2.8
Version table:
   *** 10.1ubuntu2.8 500
  500 mirror://elx-install.lmera.ericsson.se/mirrors.txt 
bionic-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   10.1ubuntu2.2 500
  500 mirror://elx-install.lmera.ericsson.se/mirrors.txt 
bionic-security/main amd64 Packages
   10.1ubuntu2 500
  500 mirror://elx-install.lmera.ericsson.se/mirrors.txt bionic/main 
amd64 Packages
  3) Not to crash would be much better
  4) Crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1885717/+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 1885742] [NEW] Unable to suspend, error -16

2020-06-30 Thread Kurrey Consultancy Services

Public bug reported:

Unable to suspend, error -16

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
Uname: Linux 4.15.0-108-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 
PDT 2020
 GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 30 20:57:50 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 390.138, 4.15.0-108-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
 NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801]
InstallationDate: Installed on 2018-08-29 (670 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20217
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic 
root=UUID=2674d4c6-6617-45bc-bd72-c1ecec60a6e9 ro quiet splash 
nouveau.modeset=0 vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 1/30/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: 74CN47WW(V3.08)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIQY0Y1
dmi.board.vendor: LENOVO
dmi.board.version: 3194STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Y510P
dmi.modalias: 
dmi:bvnLENOVO:bvr74CN47WW(V3.08):bd1/30/2015:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr3194STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
dmi.product.family: IDEAPAD
dmi.product.name: 20217
dmi.product.version: Lenovo IdeaPad Y510P
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic 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/1885742

Title:
  Unable to suspend, error -16

Status in xorg package in Ubuntu:
  New

Bug description:
  Unable to suspend, error -16

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
  Uname: Linux 4.15.0-108-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 
PDT 2020
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 30 20:57:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.138, 4.15.0-108-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
   NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801]
  InstallationDate: Installed on 2018-08-29 (670 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20217
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic 
root=UUID=2674d4c6-6617-45bc-bd72-c1ecec60a6e9 ro quiet

[Touch-packages] [Bug 1885737] [NEW] package linux-image-5.4.0-39-generic 5.4.0-39.43 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2020-06-30 Thread Lascombes

Public bug reported:

When I boot Ubuntu it may come with a dark screen

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-39-generic 5.4.0-39.43
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Uname: Linux 5.4.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
AptOrdering:
 linux-modules-nvidia-440-5.4.0-39-generic:amd64: Install
 linux-modules-nvidia-440-generic-hwe-20.04:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jun 27 12:28:13 2020
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2020-05-07 (53 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IwConfig:
 lono wireless extensions.
 
 enp3s0no wireless extensions.
MachineType: MSI MS-7817
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=6cacf309-6f84-4171-bab2-6b3108367d92 ro recovery nomodeset
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.04-1ubuntu26
RfKill:
 
SourcePackage: initramfs-tools
Title: package linux-image-5.4.0-39-generic 5.4.0-39.43 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/30/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V4.9
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B85M-P33 (MS-7817)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV4.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnB85M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7817
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: MSI

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package linux-image-5.4.0-39-generic 5.4.0-39.43 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  When I boot Ubuntu it may come with a dark screen

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-39-generic 5.4.0-39.43
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  AptOrdering:
   linux-modules-nvidia-440-5.4.0-39-generic:amd64: Install
   linux-modules-nvidia-440-generic-hwe-20.04:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jun 27 12:28:13 2020
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2020-05-07 (53 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: MSI MS-7817
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=6cacf309-6f84-4171-bab2-6b3108367d92 ro recovery nomodeset
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-5.4.0-39-generic 5.4.0-39.43 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V4.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-P33 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV4.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnB85M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817

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

2020-06-30 Thread Ryan Harper

On Tue, Jun 30, 2020 at 6:35 AM Balint Reczey <1861...@bugs.launchpad.net>
wrote:

> @raharper I've forwarded the systemd fix for you with minimal tidying of
> the commit message https://github.com/systemd/systemd/pull/16317


Thanks!


>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1861941
>
> Title:
>   bcache by-uuid links disappear after mounting bcache0
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions
>

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in linux-signed source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in bcache-tools source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in bcache-tools source package in Groovy:
  Triaged
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

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

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

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

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

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

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

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

[Touch-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

2020-06-30 Thread Dimitri John Ledkov

@balint

Kernel has no facility to startup in one mode, and later transition to
another.

I think maybe we should measure the difference between "performance,
then on demand" vs "balanced performance".

If the difference is not significant, maybe we can simply change the
kernel default to "balanced performance"

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

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during bootup. It's not clear to me that's
  actually useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

2020-06-30 Thread Balint Reczey

The commit message removing ondemand.service has several bug references, too:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=65f46a7d14b335e5743350dbbc5b5ef1e72826f7

remove Ubuntu-specific ondemand.service
New processors handle scaling/throttling in internal firmware
(e.g. intel_pstate), and do not require OS config.

Additionally, nobody else does this, not even Debian.

And finally, this has caused problems for years, e.g.:

https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1497375
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1503773
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1480320
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579278
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1806012
https://bugs.launchpad.net/charm-sysconfig/+bug/1873028


IMO the kernel is a better place for setting the default governor properly and 
can even set different governors in cloud-specific kernels.
If the decision is to control the governor in user space in Ubuntu I'd prefer a 
solution shipped in an other package because systemd does too many things 
already.

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

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during bootup. It's not clear to me that's
  actually useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1885562] Re: [fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode

2020-06-30 Thread Dariusz Gadomski

I have briefly analyzed nss code - it uses the nspr library for, inter
alia, file access abstraction. From what I saw in the docs it does not
offer any form of symlink resolution, so it may be nontrivial to safely
implement it in nss code.

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

Title:
  [fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode

Status in nss package in Ubuntu:
  New
Status in nss source package in Bionic:
  New

Bug description:
  In FIPS mode there are some additional checks performed.

  They lead to verifying binaries signatures. Those signatures are
  shipped in the libnss3 package as *.chk files installed in
  /usr/lib/$(DEB_HOST_MULTIARCH)/nss. Along with those files are the
  libraries themselves (libfreebl3.so  libfreeblpriv3.so  libnssckbi.so
  libnssdbm3.so  libsoftokn3.so).

  Those libraries are symlinked to be present in /usr/lib/$(DEB_HOST_MULTIARCH):
  ls -l /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so
  lrwxrwxrwx 1 root root 21 Jun 10 18:54 
/usr/lib/x86_64-linux-gnu/libfreeblpriv3.so -> nss/libfreeblpriv3.so

  The client binaries are linked against the symlinks, so when the verification 
happens (lib/freebl/shvfy.c) the mkCheckFileName function takes path to the 
symlink to the shlib and replaces the .so extension with .chk.
  Then it tries to open that file. Obviosly it fails, because the actual file 
is in /usr/lib/$(DEB_HOST_MULTIARCH)/nss.

  [Test case]
  sudo apt install chrony
  sudo chronyd -d
  chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed.

  Potential solutions:
  Solution A:
  Drop the /usr/lib/$(DEB_HOST_MULTIARCH)/nss directory and put all signatures 
and libs in /usr/lib/$(DEB_HOST_MULTIARCH).

  Solution B:
  Implement and upstream NSS feature of resolving symlinks and looking for 
*.chk where the symlinks lead to.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1885562/+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 1885730] Missing required logs.

2020-06-30 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1885730

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during bootup. It's not clear to me that's
  actually useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

Tagging rls-gg-incoming so it's reviewed, that has a performance impact
on desktop and ideally should have been discussed before landing rather
than afterfact

** Tags added: rls-gg-incoming

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

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during bootup. It's not clear to me that's
  actually useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

2020-06-30 Thread Julian Andres Klode

Someone probably needs to look at non-pstate systems as I have no idea
about them.

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

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during bootup. It's not clear to me that's
  actually useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1885730] [NEW] Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor

2020-06-30 Thread Julian Andres Klode

Public bug reported:

In a recent merge from Debian we lost ondemand.service, meaning all CPUs
now run in Turbo all the time when idle, which is clearly suboptimal.

The discussion in bug 1806012 seems misleading, focusing on p-state vs
other drivers, when in fact, the script actually set the default
governor for the pstate driver on platforms that use pstate. Everything
below only looks at systems that use pstate.

pstate has two governors: performance and powerstate. performance runs
CPU at maximum frequency constantly, and powersave can be configured
using various energy profiles energy profiles:

- performance
- balanced performance
- balanced power
- power

It defaults to balanced performance, I think, but I'm not sure.

Whether performance governor is faster than powersave governor is not
even clear. https://www.phoronix.com/scan.php?page=article=linux50
-pstate-cpufreq=5 benchmarked them, but did not benchmark the
individual energy profiles.

For a desktop/laptop, the expected behavior is the powersave governor
with balanced_performance on AC and balanced_power on battery.

I don't know about servers or VMs, but the benchmark series seems to
indicate it does not really matter much performance wise.

I think most other distributions configure their kernels to use the
powersave governor by default, whereas we configure it to use the
performance governor and then switch it later in the boot to get the
maximum performance during bootup. It's not clear to me that's actually
useful.

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

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


** Tags: rls-gg-incoming

** Summary changed:

- Bring back ondemand.service - pstate now defaults to performance governor
+ Bring back ondemand.service or switch kernel default governor for pstate - 
pstate now defaults to performance governor

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Bring back ondemand.service or switch kernel default governor for
  pstate - pstate now defaults to performance governor

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  In a recent merge from Debian we lost ondemand.service, meaning all
  CPUs now run in Turbo all the time when idle, which is clearly
  suboptimal.

  The discussion in bug 1806012 seems misleading, focusing on p-state vs
  other drivers, when in fact, the script actually set the default
  governor for the pstate driver on platforms that use pstate.
  Everything below only looks at systems that use pstate.

  pstate has two governors: performance and powerstate. performance runs
  CPU at maximum frequency constantly, and powersave can be configured
  using various energy profiles energy profiles:

  - performance
  - balanced performance
  - balanced power
  - power

  It defaults to balanced performance, I think, but I'm not sure.

  Whether performance governor is faster than powersave governor is not
  even clear.
  https://www.phoronix.com/scan.php?page=article=linux50-pstate-
  cpufreq=5 benchmarked them, but did not benchmark the individual
  energy profiles.

  For a desktop/laptop, the expected behavior is the powersave governor
  with balanced_performance on AC and balanced_power on battery.

  I don't know about servers or VMs, but the benchmark series seems to
  indicate it does not really matter much performance wise.

  I think most other distributions configure their kernels to use the
  powersave governor by default, whereas we configure it to use the
  performance governor and then switch it later in the boot to get the
  maximum performance during bootup. It's not clear to me that's
  actually useful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms

** Changed in: systemd (Ubuntu Focal)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

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

Title:
  hwdb: Mask rfkill event from intel-hid on HP platforms

Status in HWE Next:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  Press wireless hotkey on HP's latest generation laptops generate two rfkill 
events, prevent airplane mode from turning off.

  One event is from intel-hid and the other one is from hp-wireless.

  [Fix]
  Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use 
rfkill from hp-wireless.

  [Test]
  With the one-liner fix, press wireless hotkey only generate one rfkill event, 
hence airplane mode works as expected.

  [Regression Potential]
  Low, use hp-wireless over intel-hid is anticipated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883846/+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 1861177] Re: seccomp_rule_add is very slow

uploaded to x/b/e/f/g, thanks!

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

Title:
  seccomp_rule_add is very slow

Status in snapd:
  Invalid
Status in libseccomp package in Ubuntu:
  In Progress
Status in libseccomp source package in Xenial:
  In Progress
Status in libseccomp source package in Bionic:
  In Progress
Status in libseccomp source package in Eoan:
  In Progress
Status in libseccomp source package in Focal:
  In Progress
Status in libseccomp source package in Groovy:
  In Progress

Bug description:
  [IMPACT]
  There is a known and patched issue with version 2.4 of libseccomp where 
certain operations have a large performance regression. This is causing some 
packages that use libseccomp such as container orchestration systems to 
occasionally time out or otherwise fail under certain workloads.

  Please consider porting the patch into the various Ubuntu versions
  that have version 2.4 of libseccomp and into the backports. The
  performance patch from version 2.5 (yet to be released) applies
  cleanly on top of the 2.4 branch of libseccomp.

  For more information, and for a copy of the patch (which can also be
  cherry picked from the upstream libseccomp repos) see the similar
  Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913

  Upstream issue : https://github.com/seccomp/libseccomp/issues/153
  Upstream fix : https://github.com/seccomp/libseccomp/pull/180/

  [Test Case]

  For this test case we use Docker on Ubuntu Groovy (20.10) :

  --> Current libseccomp version
  #dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu3 
 amd64high level interface to Linux seccomp filter

  ## pull ubuntu image
  # docker pull ubuntu
  ## create a container
  # docker run --name test_seccomp -it 74435f89ab78 /bin/bash

  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m10,319s
  user  0m0,018s
  sys   0m0,033s

  
  --> Patched libseccomp version

  # dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu4 
 amd64high level interface to Linux seccomp filter

  # docker start test_seccomp
  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m3,650s
  user  0m0,025s
  sys   0m0,028s

  [Regression Potential]

  The first of the 2 patches cleans up the code that adds rules to a
  single filter without changing the logic of the code. The second patch
  introduces the idea of shadow transactions. On a successful
  transaction commit the old transaction checkpoint is preserved and is
  brought up to date with the current filter. The next time a new
  transaction starts, it checks is the a shadow transaction exist and if
  so the shadow is used instead of creating a new checkpoint from
  scratch [1]. This is the patch that mitigates the performance
  regression. Any potential regression will involve the parts of the
  code that add rules to filters and/or the code that creates and checks
  the shadow transactions.

  
  [Other]

  Affected releases : Groovy, Focal, Eoan, Bionic, Xenial.

  [1]
  
https://github.com/seccomp/libseccomp/pull/180/commits/bc3a6c0453b0350ee43e4925482f705a2fbf5a4d

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1861177/+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 1860620] Re: ubuntu-desktop-minimal should not depend on mysql libs

2020-06-30 Thread Iain Lane

I’m not sure if depending on a library and -common (the initial apt log
shows the client and server themselves were *not* installed) is a
particular problem, but if so, this is coming from libsnmp35.

** Package changed: ubuntu-meta (Ubuntu) => net-snmp (Ubuntu)

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

Title:
  ubuntu-desktop-minimal should not depend on mysql libs

Status in net-snmp package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 20.04 I decided to remove packages that I don't
  need or use.

  I was surprised to find that mysql client, server and common packages
  were installed, as I could not remember having installed mysql -- I
  don't use it or develop for it...

  When I removed them, ubuntu-desktop-minimal went along for the ride:

  c@slate:~$ sudo apt-get purge -y mysql-client-core-5.7 mysql-common 
mysql-server-core-5.7 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package 'mysql-client-core-5.7' is not installed, so not removed
  Package 'mysql-server-core-5.7' is not installed, so not removed
  The following package was automatically installed and is no longer required:
libgsound0
  Use 'sudo apt autoremove' to remove it.
  The following packages will be REMOVED:
colord* gnome-control-center* libmysqlclient21* libsane* libsnmp30* 
mysql-common* ubuntu-desktop-minimal*
  0 upgraded, 0 newly installed, 7 to remove and 0 not upgraded.
  After this operation, 28.4 MB disk space will be freed.
  (Reading database ... 381127 files and directories currently installed.)
  Removing ubuntu-desktop-minimal (1.443) ...
  Removing gnome-control-center (1:3.34.1-1ubuntu3) ...
  Removing colord (1.4.4-1ubuntu1) ...
  Removing libsane:amd64 (1.0.27-3.2ubuntu3) ...
  Removing libsnmp30:amd64 (5.7.3+dfsg-5ubuntu6) ...
  Removing libmysqlclient21:amd64 (8.0.18-0ubuntu5) ...
  Removing mysql-common (5.8+1.0.5ubuntu2) ...
  Processing triggers for mime-support (3.64ubuntu1) ...
  Processing triggers for gnome-menus (3.32.0-1ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.63.3-1) ...
  Processing triggers for libc-bin (2.30-0ubuntu3) ...
  Processing triggers for man-db (2.9.0-2) ...
  Processing triggers for dbus (1.12.16-2ubuntu2) ...
  Processing triggers for udev (244-3ubuntu1) ...
  Processing triggers for desktop-file-utils (0.24-1ubuntu1) ...
  (Reading database ... 380812 files and directories currently installed.)
  Purging configuration files for mysql-common (5.8+1.0.5ubuntu2) ...
  Purging configuration files for colord (1.4.4-1ubuntu1) ...

  And, reinstalling ubuntu-desktop-minimal wants to brings them back,
  even with recommends and suggests turned off:

  c@slate:~$ sudo apt install ubuntu-desktop-minimal --no-install-recommends 
--no-install-
  --no-install-recommends  --no-install-suggests
  c@slate:~$ sudo apt install ubuntu-desktop-minimal --no-install-recommends 
--no-install-suggests 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
colord gnome-control-center libmysqlclient21 libsane libsnmp30 mysql-common
  Suggested packages:
colord-sensor-argyll gnome-user-share realmd libcanberra-gtk-module hplip
  Recommended packages:
gnome-online-accounts gnome-control-center-faces rygel | rygel-tracker 
sane-utils firefox hplip
  The following NEW packages will be installed:
colord gnome-control-center libmysqlclient21 libsane libsnmp30 mysql-common 
ubuntu-desktop-minimal
  0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/6,114 kB of archives.
  After this operation, 28.4 MB of additional disk space will be used.
  Do you want to continue? [Y/n] 

  This seems really wrong... and looks like a transitive dependency, as
  I don't see it in apt-get showpkg ubuntu-desktop-minimal.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop-minimal 1.443
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair binder_linux 
ashmem_linux
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 22 19:26:53 2020
  InstallationDate: Installed on 2018-08-26 (514 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-01-23 (0 days ago)

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

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

[Touch-packages] [Bug 1877633] Re: libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64

2020-06-30 Thread Matt Thalman

I don't see the updated applied to the ARM architecture. The versions of
arm64 and armhf at https://packages.ubuntu.com/focal/libseccomp-dev
still show 2.4.3-1ubuntu1.  What's the story on that?

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

Title:
  libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the
  getrlimit syscall on arm64

Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Focal:
  Fix Released
Status in libseccomp source package in Groovy:
  Fix Released

Bug description:
  This was reported via the snapcraft forum[1]:

  On bionic amd64, libseccomp 2.4.1-0ubuntu0.18.04.2

  $ lsb_release -d
  Description:  Ubuntu 18.04.4 LTS
  $ scmp_sys_resolver -a aarch64 163
  getrlimit
  $ scmp_sys_resolver -a aarch64 getrlimit
  163

  focal amd64, libseccomp 2.4.3-1ubuntu1 -- *__BROKEN__*

  $ lsb_release -d
  Description:  Ubuntu 20.04 LTS
  $ scmp_sys_resolver -a aarch64 163
  UNKNOWN
  $ scmp_sys_resolver -a aarch64 getrlimit
  -10180

  [1]https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal-
  arm64/17237/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+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 1885717] [NEW] /etc/update-motd.d/50-motd-news not executable

2020-06-30 Thread Helio Loureiro

Public bug reported:

On new installed 18.04, just caught a failed process to start: motd-news

root@xps13 ~# systemctl list-units --state=failed
  UNIT   LOAD   ACTIVE SUBDESCRIPTION   
   
● motd-news.service  loaded failed failed Message of the Day
   

Looking close:

root@xps13 ~# systemctl status motd-news
● motd-news.service - Message of the Day
   Loaded: loaded (/lib/systemd/system/motd-news.service; static; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-06-30 09:16:54 CEST; 5h 
6min ago
 Docs: man:update-motd(8)
  Process: 12505 ExecStart=/etc/update-motd.d/50-motd-news --force 
(code=exited, status=203/EXEC)
 Main PID: 12505 (code=exited, status=203/EXEC)

Jun 30 09:16:54 elxa7r5lmh2 systemd[1]: Starting Message of the Day...
Jun 30 09:16:54 elxa7r5lmh2 systemd[1]: motd-news.service: Main process exited, 
code=exited, status=203/EXEC
Jun 30 09:16:54 elxa7r5lmh2 systemd[1]: motd-news.service: Failed with result 
'exit-code'.
Jun 30 09:16:54 elxa7r5lmh2 systemd[1]: Failed to start Message of the Day.

I could fix by a simple "chmod +x" to the file.

root@xps13 ~# /etc/update-motd.d/50-motd-news
fish: The file “/etc/update-motd.d/50-motd-news” is not executable by this user
root@xps13 ~# chmod 755 /etc/update-motd.d/50-motd-news
root@xps13 ~# /etc/update-motd.d/50-motd-news

So there are 2 bugs here:
1) missing executable permission on file
2) executable placement inside /etc directory


Extra info:
1) Description:Ubuntu 18.04.4 LTS
Release:18.04
2) base-files:
  Installed: 10.1ubuntu2.8
  Candidate: 10.1ubuntu2.8
  Version table:
 *** 10.1ubuntu2.8 500
500 mirror://elx-install.lmera.ericsson.se/mirrors.txt 
bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status
 10.1ubuntu2.2 500
500 mirror://elx-install.lmera.ericsson.se/mirrors.txt 
bionic-security/main amd64 Packages
 10.1ubuntu2 500
500 mirror://elx-install.lmera.ericsson.se/mirrors.txt bionic/main 
amd64 Packages
3) Not to crash would be much better
4) Crashed

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  /etc/update-motd.d/50-motd-news not executable

Status in base-files package in Ubuntu:
  New

Bug description:
  On new installed 18.04, just caught a failed process to start: motd-
  news

  root@xps13 ~# systemctl list-units --state=failed
UNIT   LOAD   ACTIVE SUBDESCRIPTION 
 
  ● motd-news.service  loaded failed failed Message of the Day  
 

  Looking close:

  root@xps13 ~# systemctl status motd-news
  ● motd-news.service - Message of the Day
 Loaded: loaded (/lib/systemd/system/motd-news.service; static; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Tue 2020-06-30 09:16:54 CEST; 5h 
6min ago
   Docs: man:update-motd(8)
Process: 12505 ExecStart=/etc/update-motd.d/50-motd-news --force 
(code=exited, status=203/EXEC)
   Main PID: 12505 (code=exited, status=203/EXEC)

  Jun 30 09:16:54 elxa7r5lmh2 systemd[1]: Starting Message of the Day...
  Jun 30 09:16:54 elxa7r5lmh2 systemd[1]: motd-news.service: Main process 
exited, code=exited, status=203/EXEC
  Jun 30 09:16:54 elxa7r5lmh2 systemd[1]: motd-news.service: Failed with result 
'exit-code'.
  Jun 30 09:16:54 elxa7r5lmh2 systemd[1]: Failed to start Message of the Day.

  I could fix by a simple "chmod +x" to the file.

  root@xps13 ~# /etc/update-motd.d/50-motd-news
  fish: The file “/etc/update-motd.d/50-motd-news” is not executable by this 
user
  root@xps13 ~# chmod 755 /etc/update-motd.d/50-motd-news
  root@xps13 ~# /etc/update-motd.d/50-motd-news

  So there are 2 bugs here:
  1) missing executable permission on file
  2) executable placement inside /etc directory


  Extra info:
  1) Description:Ubuntu 18.04.4 LTS
  Release:18.04
  2) base-files:
Installed: 10.1ubuntu2.8
Candidate: 10.1ubuntu2.8
Version table:
   *** 10.1ubuntu2.8 500
  500 mirror://elx-install.lmera.ericsson.se/mirrors.txt 
bionic-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   10.1ubuntu2.2 500
  500 mirror://elx-install.lmera.ericsson.se/mirrors.txt 
bionic-security/main amd64 Packages
   10.1ubuntu2 500
  500 mirror://elx-install.lmera.ericsson.se/mirrors.txt bionic/main 
amd64 Packages
  3) Not to crash would be much better
  4) Crashed

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

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

[Touch-packages] [Bug 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install

Sorry for numerous messages, but I just did other things. First, I found that
checking at install "request password at logins", I was able to also install
Nvidia Drivers without any issue at all! This change basically solved all the
problems. When installing Ubuntu focal and checking "log in automatically" a
login loop was present after nvidia drivers got installed. LightDM fixed this
as it disables automatic login. Second, I run another journalctl report, this
time instantaneously at crash. Ctrl-alt-F worked by pressing it instantaneously.
Hopefully this may help. I noticed users on askubuntu complaining about login
loops after nvidia drivers install, but have not seen as a solution just to
enable password request at login screen. LightDM partly solves the situations,
but as I mentioned, when LightDM and automatic log in are activated and
accountsservice is being upgraded, the screen still flickers weirdly.

** Attachment added: "instantjournal.txt"

https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1885452/+attachment/5388452/+files/instantjournal.txt

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

Title:
pc freezes and crashes during accountsservice upgrade on fresh ubuntu
focal fossa install

Status in accountsservice package in Ubuntu:
Incomplete

Bug description:
After a fresh install of Focal Fossa and running sudo apt update and sudo apt
upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes,
then crashes. This was reproducible on another computer (laptop). I reinstalled
Ubuntu and put the package on hold. Later, I found that by installing and
activating lightdm, this problem was remediated. Found this solution
accidentally, while I was looking to correct login screen loops after I
installed the nvidia drivers. This is unrelated, since the laptop does not have
nvidia.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-06-29 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Package: accountsservice 0.6.55-0ubuntu12~20.04.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Tags: focal
Uname: Linux 5.4.0-39-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1885452/+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 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install

I forgot to mention that, after the "Oh no! Something has gone wrong" I also 
get, in fact, logged out automatically and sent to login screen and after I 
login the "Oh no! Something has gone wrong" appears again. After pressing 
ctrl-alt-f3 and ctrl-alt-f2 repeatedly, the desktop appears eventually. 
However, I found another interesting fix! I reinstalled ubuntu and checked: 
"ask for password every time I sign in" and not as I previously selected, which 
was "log in automatically". I could sudo apt upgrade with no problem, on 
default GDM, no freezes, crash stalls etc.
As I previously mentioned, using LightDM is also a fix. By installing and 
activating it before anything else, sudo apt upgrade runs well, but, I noticed 
that when accountsservice is getting set up (on GDM it is the point when 
computer crashes) the computer still freezes and flickers about 2-3 seconds, 
but no crash.

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

Title:
  pc freezes and crashes during accountsservice upgrade on fresh ubuntu
  focal fossa install

Status in accountsservice package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Focal Fossa and running sudo apt update and sudo apt 
upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes, 
then crashes. This was reproducible on another computer (laptop). I reinstalled 
Ubuntu and put the package on hold. Later, I found that by installing and 
activating lightdm, this problem was remediated. Found this solution 
accidentally, while I was looking to correct login screen loops after I 
installed the nvidia drivers. This is unrelated, since the laptop does not have 
nvidia.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: accountsservice 0.6.55-0ubuntu12~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1885452/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

2020-06-30 Thread Balint Reczey

@raharper I've forwarded the systemd fix for you with minimal tidying of
the commit message https://github.com/systemd/systemd/pull/16317

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in linux-signed source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in bcache-tools source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in bcache-tools source package in Groovy:
  Triaged
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

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

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

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

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

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

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

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

[Touch-packages] [Bug 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install

After I pressed log out on that screen, I ran journalctl -b 0 and I am
attaching it here. I am not sure if it is different from the previous
one, which was run after a full reboot of the PC.

** Attachment added: "newjournal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1885452/+attachment/5388450/+files/newjournal.txt

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

Title:
  pc freezes and crashes during accountsservice upgrade on fresh ubuntu
  focal fossa install

Status in accountsservice package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Focal Fossa and running sudo apt update and sudo apt 
upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes, 
then crashes. This was reproducible on another computer (laptop). I reinstalled 
Ubuntu and put the package on hold. Later, I found that by installing and 
activating lightdm, this problem was remediated. Found this solution 
accidentally, while I was looking to correct login screen loops after I 
installed the nvidia drivers. This is unrelated, since the laptop does not have 
nvidia.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: accountsservice 0.6.55-0ubuntu12~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1885452/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

2020-06-30 Thread Balint Reczey

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

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

** Also affects: bcache-tools (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-signed (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in linux-signed source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in bcache-tools source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in bcache-tools source package in Groovy:
  Triaged
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

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

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

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

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

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

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

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

[Touch-packages] [Bug 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install

Unfortunately, after the crash occurs and the 'something went wrong'
screen appears I cannot enter the VT. ctrl-alt-F3 makes the screen go
black and ctrl-alt-f2 reverts is to the 'something went wrong'. I took a
screenshot with PrtSc button but nothing was saved in the Pictures
Folder, but I did take a photo with my camera, just in case. I am
attaching it.

** Attachment added: "IMG_0779.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1885452/+attachment/5388449/+files/IMG_0779.jpg

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

Title:
  pc freezes and crashes during accountsservice upgrade on fresh ubuntu
  focal fossa install

Status in accountsservice package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Focal Fossa and running sudo apt update and sudo apt 
upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes, 
then crashes. This was reproducible on another computer (laptop). I reinstalled 
Ubuntu and put the package on hold. Later, I found that by installing and 
activating lightdm, this problem was remediated. Found this solution 
accidentally, while I was looking to correct login screen loops after I 
installed the nvidia drivers. This is unrelated, since the laptop does not have 
nvidia.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: accountsservice 0.6.55-0ubuntu12~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1885452/+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 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install

When did you get the log and at what time did you see the 'something
went wrong' screen? There is no obvious error in the log. When you see
the error screen could you take a screenshot, then switch to a VT (e.g
ctrl-alt-F3) and get the journalctl log from there?

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

Title:
  pc freezes and crashes during accountsservice upgrade on fresh ubuntu
  focal fossa install

Status in accountsservice package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Focal Fossa and running sudo apt update and sudo apt 
upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes, 
then crashes. This was reproducible on another computer (laptop). I reinstalled 
Ubuntu and put the package on hold. Later, I found that by installing and 
activating lightdm, this problem was remediated. Found this solution 
accidentally, while I was looking to correct login screen loops after I 
installed the nvidia drivers. This is unrelated, since the laptop does not have 
nvidia.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: accountsservice 0.6.55-0ubuntu12~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1885452/+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 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install

When did you get the log and at what time did you see the 'something
went wrong' screen? There is no obvious error in the log. When you see
the error screen could you take a screenshot, then switch to a VT (e.g
ctrl-alt-F3) and get the journalctl log from there?

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

Title:
  pc freezes and crashes during accountsservice upgrade on fresh ubuntu
  focal fossa install

Status in accountsservice package in Ubuntu:
  Incomplete

Bug description:
  After a fresh install of Focal Fossa and running sudo apt update and sudo apt 
upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes, 
then crashes. This was reproducible on another computer (laptop). I reinstalled 
Ubuntu and put the package on hold. Later, I found that by installing and 
activating lightdm, this problem was remediated. Found this solution 
accidentally, while I was looking to correct login screen loops after I 
installed the nvidia drivers. This is unrelated, since the laptop does not have 
nvidia.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-06-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: accountsservice 0.6.55-0ubuntu12~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Tags:  focal
  Uname: Linux 5.4.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1885452/+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 1884846] Re: Can't connect to internet if second user session

it seems to be a wpasupplicant / driver issue, from the log

jun 29 18:21:27 tanquita wpa_supplicant[949]: wlp4s0: WPS-TIMEOUT
Requested operation timed out

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

Title:
  Can't connect to internet if second user session

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  My kid was using the laptop, connected to internet in his user
  session.

  I switched to my user (but his session was still active), and
  NetworkManager couldn't connect to internet.

  Error from syslog:

  Jun 23 19:30:15 tanquita NetworkManager[854]: 
  [1592951415.1979] audit: op="connection-activate" uuid="a52379fa-
  0a44-4013-93b6-b04e63515fb9" name="Voyager" pid=34278 uid=1000
  result="fail" reason="Private connection already active on the device:
  uid 1000 has no permission to perform this operation"

  (uid 1000 is myself)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Jun 23 19:40:19 2020
  InstallationDate: Installed on 2020-06-20 (3 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.100.1 dev wlp4s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000 
   192.168.100.0/24 dev wlp4s0 proto kernel scope link src 192.168.100.103 
metric 600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1884846/+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 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise

This bug was fixed in the package network-manager - 1.24.2-1ubuntu2

---
network-manager (1.24.2-1ubuntu2) groovy; urgency=medium

  * debian/20-connectivity-ubuntu.conf: Add trailing dot to make
connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN
warning noise, thanks MarchH (lp: #1880258)

 -- Sebastien Bacher   Mon, 29 Jun 2020 16:20:07
+0200

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

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

Title:
  Add trailing dot to make connectivity-check.ubuntu.com. absolute and
  reduce NXDOMAIN warning noise

Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  I normally don't like this, but it's a one-character change so it's
  easier to start with the solution:

  diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf  
  +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  @@ -1,2 +1,2 @@
   [connectivity]
  -uri=http://connectivity-check.ubuntu.com/
  +uri=http://connectivity-check.ubuntu.com./

  Making this name absolute instead of relative avoids spurious
  resolutions of "connectivity-check.ubuntu.com.your_domain." This
  removes a fair amount of NXDOMAIN error noise in journalctl.

  
  Observing the issue and the fix requires 3 terminals:

  1. tcpdump -i any 'port domain'
  2. journalctl --boot -u systemd-resolved -f

  3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe the NXDOMAIN noise over a couple few minutes
   
  Now make the hostname absolute with the trailing dot above and run:
 systemctl reload NetworkManager
  Wait 1 min for things to stabilize. Test again:

  nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe non-zero but significantly reduced NXDOMAIN noise over a couple 
few minutes

  Originally reported at https://askubuntu.com/a/1242611/117217

  Plenty of people annoyed by NXDOMAIN warnings, just Google it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+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 1559650] Update Released

2020-06-30 Thread Timo Aaltonen

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

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

Title:
  gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

Status in libxau package in Ubuntu:
  Fix Released
Status in libxau source package in Bionic:
  Fix Released
Status in libxau source package in Eoan:
  Fix Released
Status in libxau source package in Focal:
  Fix Released

Bug description:
  [Impact]

  gnome-shell crashes a lot. Over 42000 times in bionic so far:
  https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7

  [Test Case]

  None known yet. Just keeping an eye on the above link for regressions.

  [Regression Potential]

  Low. The same fix has been released to newer distros for the past 2
  years already.

  [Other Info]

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Mar 16 17:15:11 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-13 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160311)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb   
$0x0,(%r12)
   PC (0x7f1ff33f46ab) ok
   source "$0x0" ok
   destination "(%r12)" (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at 
vsnprintf_chk.c:55
   ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34
   XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
  Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxau/+bug/1559650/+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 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

This bug was fixed in the package libxau - 1:1.0.8-1ubuntu1

---
libxau (1:1.0.8-1ubuntu1) bionic; urgency=medium

  * Add debian/patches/fix-lp1559650.patch to fix a common segfault in
___vsnprintf_chk() that's crashing gnome-shell (LP: #1559650)

 -- Daniel van Vugt   Tue, 21 Apr 2020
15:33:06 +0800

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

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

Title:
  gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

Status in libxau package in Ubuntu:
  Fix Released
Status in libxau source package in Bionic:
  Fix Released
Status in libxau source package in Eoan:
  Fix Released
Status in libxau source package in Focal:
  Fix Released

Bug description:
  [Impact]

  gnome-shell crashes a lot. Over 42000 times in bionic so far:
  https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7

  [Test Case]

  None known yet. Just keeping an eye on the above link for regressions.

  [Regression Potential]

  Low. The same fix has been released to newer distros for the past 2
  years already.

  [Other Info]

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Mar 16 17:15:11 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-13 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160311)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb   
$0x0,(%r12)
   PC (0x7f1ff33f46ab) ok
   source "$0x0" ok
   destination "(%r12)" (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at 
vsnprintf_chk.c:55
   ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34
   XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
  Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxau/+bug/1559650/+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 1881094] Re: Support kernel 5.4 Intel sound driver on bionic

2020-06-30 Thread Kai-Chuan Hsieh

** Changed in: oem-priority
   Status: New => In Progress

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

Title:
  Support kernel 5.4 Intel sound driver on bionic

Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Invalid
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * Some Intel platform bionic user audio function will be broken after
  upgrade to kernel 5.4

   * pulseaudio can't find working profile, since card name is changed
  in kernel 5.4

  [Test Case]

   * install kernel 5.4 and check audio function
     1. enable Pre-released updates in Developer Options
    Software & Updates > Developer Options > Pre-released updates 
(bionic-proposed)
     2. $ sudo apt update
     3. $ sudo apt install linux-generic-hwe-18.04-edge
     4. $ sudo reboot

   * install updated linux-firmware and pulseaudio
     $ sudo add-apt-repository ppa:kchsieh/training
     $ sudo apt-get update
     $ sudo apt install linux-firmware
     $ sudo apt install pulseaudio
     $ sudo reboot

   * test items
     1. check internal speaker/mic to playback and record audio
     2. plug headset and check headset functions
     3. plug HDMI from external monitor/TV, and check audio functions
     4. 1, 2, 3 works fine after resume from suspend

  [Regression Potential]

   * The updated pulseaudio breaks audio function on old kernel

  [Scope]

   * Need for bionic only

  [Bug Discussion]

   * https://bugs.launchpad.net/timbuktu/+bug/1880632
   * MP: 
https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1881094/+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 1885669] Re: screen blinking while start laptop

Can you please run:

  journalctl -b0 > journal.txt

and attach the resulting text file?

Also a video of the problem would be helpful.

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

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

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

Title:
  screen blinking while start laptop

Status in Ubuntu:
  Incomplete

Bug description:
  screen blinking

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
  Uname: Linux 4.15.0-108-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jun 30 11:41:00 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-108-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1]
  InstallationDate: Installed on 2015-10-17 (1717 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Hewlett-Packard HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic 
root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.0B
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C1
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 96.11
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May 28 11:49:11 2020
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1885669/+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 1885669] Re: screen blinking while start laptop

2020-06-30 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => xorg (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/1885669

Title:
  screen blinking while start laptop

Status in xorg package in Ubuntu:
  New

Bug description:
  screen blinking

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
  Uname: Linux 4.15.0-108-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jun 30 11:41:00 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-108-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1]
  InstallationDate: Installed on 2015-10-17 (1717 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Hewlett-Packard HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic 
root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.0B
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C1
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 96.11
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May 28 11:49:11 2020
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1885669/+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 1885646] Re: RM ring FTBFS

Removing packages from groovy:
ring 20190215.1.f152c98~ds1-1build2 in groovy
jami 20190215.1.f152c98~ds1-1build2 in groovy amd64
jami 20190215.1.f152c98~ds1-1build2 in groovy arm64
jami 20190215.1.f152c98~ds1-1build2 in groovy armhf
jami 20190215.1.f152c98~ds1-1build2 in groovy ppc64el
jami 20190215.1.f152c98~ds1-1build2 in groovy riscv64
jami 20190215.1.f152c98~ds1-1build2 in groovy s390x
jami-daemon 20190215.1.f152c98~ds1-1build2 in groovy amd64
jami-daemon 20190215.1.f152c98~ds1-1build2 in groovy arm64
jami-daemon 20190215.1.f152c98~ds1-1build2 in groovy armhf
jami-daemon 20190215.1.f152c98~ds1-1build2 in groovy ppc64el
jami-daemon 20190215.1.f152c98~ds1-1build2 in groovy riscv64
jami-daemon 20190215.1.f152c98~ds1-1build2 in groovy s390x
ring 20190215.1.f152c98~ds1-1build2 in groovy amd64
ring 20190215.1.f152c98~ds1-1build2 in groovy arm64
ring 20190215.1.f152c98~ds1-1build2 in groovy armhf
ring 20190215.1.f152c98~ds1-1build2 in groovy i386
ring 20190215.1.f152c98~ds1-1build2 in groovy ppc64el
ring 20190215.1.f152c98~ds1-1build2 in groovy riscv64
ring 20190215.1.f152c98~ds1-1build2 in groovy s390x
ring-daemon 20190215.1.f152c98~ds1-1build2 in groovy amd64
ring-daemon 20190215.1.f152c98~ds1-1build2 in groovy arm64
ring-daemon 20190215.1.f152c98~ds1-1build2 in groovy armhf
ring-daemon 20190215.1.f152c98~ds1-1build2 in groovy i386
ring-daemon 20190215.1.f152c98~ds1-1build2 in groovy ppc64el
ring-daemon 20190215.1.f152c98~ds1-1build2 in groovy riscv64
ring-daemon 20190215.1.f152c98~ds1-1build2 in groovy s390x
Comment: FTBFS, RC-buggy, removed from testing (lp: #1885646)
Remove [y|N]? y


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

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

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

Title:
  RM ring FTBFS

Status in nettle package in Ubuntu:
  Incomplete
Status in ring package in Ubuntu:
  Fix Released
Status in ring package in Debian:
  New

Bug description:
  Please remove
  ring 20190215.1.f152c98~ds1-1build4 groovy-proposed
  ring 20190215.1.f152c98~ds1-1build2 groovy-release

  FTBFS, RC-buggy, removed from testing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1885646/+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 1885669] [NEW] screen blinking while start laptop

You have been subscribed to a public bug:

screen blinking

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
Uname: Linux 4.15.0-108-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CompositorRunning: None
Date: Tue Jun 30 11:41:00 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-108-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1]
InstallationDate: Installed on 2015-10-17 (1717 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: Hewlett-Packard HP Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic 
root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/04/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.0B
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80C1
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 96.11
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu May 28 11:49:11 2020
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.4

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


** Tags: amd64 apport-bug bionic ubuntu
-- 
screen blinking while start laptop
https://bugs.launchpad.net/bugs/1885669
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1885675] Re: /usr/bin/mpv:11:stream_state:iris_blorp_exec:blorp_clear:clear_color:iris_clear