[Touch-packages] [Bug 1901195] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de sali

[Launchpad Bug Tracker]

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

** Changed in: initramfs-tools (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: el
  subproceso instalado paquete initramfs-tools script post-installation
  devolvió el código de salida de error 1

Status in initramfs-tools package in Ubuntu:
  Expired

Bug description:
  Was upgrading from 18.04 to 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.3
  ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
  Uname: Linux 4.15.0-122-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct 23 11:02:21 2020
  ErrorMessage: el subproceso instalado paquete initramfs-tools script 
post-installation devolvió el código de salida de error 1
  InstallationDate: Installed on 2015-04-17 (2015 days ago)
  InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, 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.3 failed to install/upgrade: el 
subproceso instalado paquete initramfs-tools script post-installation devolvió 
el código de salida de error 1
  UpgradeStatus: Upgraded to focal on 2020-10-23 (0 days ago)

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

[Seth Arnold]

Hello,

chown: alterando o dono de '/etc/sudoers': Operação não permitida

Is there any chance you've set attrs on this file to prevent it from
being modified?

THanks

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

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

Title:
  package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: installed
  sudo package post-installation script subprocess returned error exit
  status 1

Status in sudo package in Ubuntu:
  Incomplete

Bug description:
  I've put the system to upgrade and this error occured!!

  I tried many ways to correct it but all attempts were unsuccesfull.

  Best regards,

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: sudo 1.8.31-1ubuntu1.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  AptOrdering:
   software-properties-common:amd64: Install
   software-properties-gtk:amd64: Install
   python3-software-properties:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb 17 13:43:57 2021
  DuplicateSignature:
   package:sudo:1.8.31-1ubuntu1.2
   Setting up sudo (1.8.31-1ubuntu1.2) ...
   chown: alterando o dono de '/etc/sudoers': Operação não permitida
   dpkg: error processing package sudo (--configure):
installed sudo package post-installation script subprocess returned error 
exit status 1
  ErrorMessage: installed sudo package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2018-12-12 (797 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: sudo
  Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: installed 
sudo package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-09-30 (139 days ago)
  VisudoCheck:
   /etc/sudoers: análise OK
   /etc/sudoers.d/README: análise OK
  mtime.conffile..etc.sudoers: 2020-12-30T18:27:17.782421

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915945/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Seth Arnold]

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

** Information type changed from Public Security to Public

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1915913] Re: OpenSSL Multiple Denial of Service Vulnerabilities

[Seth Arnold]

Hello, there are untested packages in https://launchpad.net/~ubuntu-
security-proposed/+archive/ubuntu/ppa/+packages in case you wish to test
them in your environment.

Thanks

** Information type changed from Private Security to Public Security

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

Title:
  OpenSSL Multiple Denial of Service Vulnerabilities

Status in openssl package in Ubuntu:
  New

Bug description:
  Multiple vulnerabilities have been reported in OpenSSL, which can be
  exploited by malicious people to cause a DoS (Denial of Service).

  1

  An error related to the "X509_issuer_and_serial_hash()" function
  (crypto/x509/x509_cmp.c) can be exploited to trigger a NULL pointer
  dereference and subsequently cause a crash.

  2

  An integer overflow error related to CipherUpdate calls can be
  exploited to cause a crash.

  The vulnerabilities are reported in versions prior to 1.1.1j and prior
  to 1.0.2y.

  Affected Software

  The following software is affected by the described vulnerability.
  Please check the vendor links below to see if exactly your version is
  affected.

  OpenSSL 1.x

  Solution

  Update to version 1.1.1j or 1.0.2y.

  References

  1. https://www.openssl.org/news/secadv/20210216.txt 

  2. 
https://github.com/openssl/openssl/commit/8130d654d1de922ea224fa18ee3bc7262edc39c0
 

  3. 
https://github.com/openssl/openssl/commit/c9fb704cf3af5524eb8e79961e31b60eee8c3c47
 


  
  Please provide an update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1915913/+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 1915908] Re: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status

[Seth Arnold]

Hello, note this line from the automatically added contents:

 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit
code 255: /etc/ssh/sshd_config line 1: garbage at end of line; "to".

It looks like your /etc/ssh/sshd_config file may be incorrect.

Thanks

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

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

Title:
  package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  sh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
   Active: activating (auto-restart) (Result: exit-code) since Wed 
2021-02-17 15:42:28 IST; 11ms ago
 Docs: man:sshd(8)
   man:sshd_config(5)
  Process: 24813 ExecStartPre=/usr/sbin/sshd -t (code=exited, 
status=255/EXCEPTION)
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Processing triggers for systemd (245.4-4ubuntu3.4) ...
  Processing triggers for man-db (2.9.1-1) ...
  Processing triggers for ufw (0.36-6) ...
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: openssh-server 1:8.2p1-4ubuntu0.1
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  AptOrdering:
   openssh-server:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb 17 15:42:28 2021
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-01-05 (42 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.5, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: /etc/ssh/sshd_config line 1: garbage at end of line; "to".
  SourcePackage: openssh
  Title: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2021-02-04 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1915908/+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 1915966] Re: Please merge initramfs-tools 0.139 from Debian unstable

[Ubuntu Foundations Team Bug Bot]

The attachment "1-1915966.debdiff" seems to be a debdiff.  The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

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

** Tags added: patch

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

Title:
  Please merge initramfs-tools 0.139 from Debian unstable

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Please merge initramfs-tools 0.139 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  shortly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1915966/+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 1915966] Re: Please merge initramfs-tools 0.139 from Debian unstable

[Dave Jones]

Attaching patch against Debian unstable. For ease of review, I've also
pushed relevant commits and tags to the following repository:

  https://code.launchpad.net/~waveform/ubuntu/+source/initramfs-
tools/+git/initramfs-tools

Specifically:

* The logical/0.137ubuntu12 tag represents our split-out delta on top of 
old/debian (0.137)
* The merge/0.139ubuntu1 tag represents the rebased delta on top of new/debian 
(0.139)

Hence, the following command may produce output useful to the purposes
of review:

  git range-diff old/debian..logical/0.137ubuntu12
new/debian..merge/0.139ubuntu1

A test package has been built in the following PPA:

  https://launchpad.net/~waveform/+archive/ubuntu/initramfs-tools

** Patch added: "1-1915966.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1915966/+attachment/5464675/+files/1-1915966.debdiff

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

Title:
  Please merge initramfs-tools 0.139 from Debian unstable

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Please merge initramfs-tools 0.139 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  shortly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1915966/+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 1915966] [NEW] Please merge initramfs-tools 0.139 from Debian unstable

[Dave Jones]

Public bug reported:

Please merge initramfs-tools 0.139 from Debian unstable.

Updated changelog and diff against Debian unstable to be attached
shortly.

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

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

Title:
  Please merge initramfs-tools 0.139 from Debian unstable

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Please merge initramfs-tools 0.139 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  shortly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1915966/+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 1852016] Re: Applications delayed on launch

[Digulla-hepe]

Just a heads up: I'm seeing exactly the same behavior on OpenSUSE LEAP
15.2

This happens with Xfce4 desktop.

It seems to be a rare bug; no one has hard about this when I asked on
the mailing list.

I did some debugging of keepassxc (since it's a relatively small app).

Installed some debug packages, then "gdb keypassxc", wait 5 seconds
until it stops printing "[New Thread 0x7fffe945b700 (LWP 18090)]", then
Ctrl+C to get the stack traces.

"info threads" to see which threads there are. "thread " + id to switch
between them.

The app hangs for 25 seconds when I try to start it which matches this
timeout:

__GI___poll (fds=0x55f994d0, nfds=1, timeout=25000) at
../sysdeps/unix/sysv/linux/poll.c:29

Googling returned this analysis:

https://freefilesync.org/forum/viewtopic.php?t=6704

The stack traces look very similar: Threads hanging in __lll_lock_wait
and __GI___poll called from ibus_bus_new_async_client and
g_simple_async_result_get_type respectively.

In the mean time, I've found more apps with the same symptom:

- qmmp

- qtconfig ("Qt 4 settings" in the Xfce settings dialog.)

I'm wondering about this line in the stack trace:

/usr/lib64/qt5/plugins/styles/libqgtk2style.so

Maybe there is a bug in the Qt style which I'm using.

Stack frame 45 says style is
"QGtk2Theme::themeHint(QPlatformTheme::ThemeHint)
const::{lambda()#1}::operator()() const::qstring_literal"

which would match the setting in the "Qt 4 settings" dialog but I'm
using Qt5. Or is the dialog for both?

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

Title:
  Applications delayed on launch

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  i am unsure if this is really a problem with dbus but my first
  research showed it could be related to dbus.

  1.) 
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 19.10
  Release:  19.10
  Codename: eoan

  Ubuntu Budgie on T460 with 256GB SSD and 16GB RAM

  2.)
  dbus:
Installed: 1.12.14-1ubuntu2
Candidate: 1.12.14-1ubuntu2
Version table:
   *** 1.12.14-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  3.) I've expected just "normal" loading applications

  4.) Some applications are delayed at startup. The application will
  take around 30s to launch, but afterwards it just runs fine. Affected
  application I found so far are KeepassXC, Filezilla and OnlyOffice
  Desktop-Editor. From strace I saw this applications are stopping (for
  about 20-30s) at this point:

  connect(12, {sa_family=AF_UNIX, sun_path="/run/user/1000/bus"}, 110) = 0
  getpid()= 8165
  geteuid()   = 1000
  getegid()   = 1000
  getpid()= 8165
  geteuid()   = 1000
  getegid()   = 1000
  sendmsg(12, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0", 
iov_len=1}], msg_iovlen=1, msg_control=[{cmsg_len=28, cmsg_level=SOL_SOCKET, 
cmsg_type=SCM_CREDENTIALS, cmsg_data={pid=8165, uid=1000, gid=1000}}], 
msg_controllen=32, msg_flags=0}, MSG_NOSIGNAL) = 1
  sendto(12, "AUTH\r\n", 6, MSG_NOSIGNAL, NULL, 0) = 6
  recvfrom(12, "REJECTED EXTERNAL\r\n", 4096, 0, NULL, NULL) = 19
  sendto(12, "AUTH EXTERNAL 31303030\r\n", 24, MSG_NOSIGNAL, NULL, 0) = 24
  recvfrom(12, "OK 7f079149c4e5e774135107445dc85"..., 4096, 0, NULL, NULL) = 37
  sendto(12, "NEGOTIATE_UNIX_FD\r\n", 19, MSG_NOSIGNAL, NULL, 0) = 19
  recvfrom(12, "AGREE_UNIX_FD\r\n", 4096, 0, NULL, NULL) = 15
  sendto(12, "BEGIN\r\n", 7, MSG_NOSIGNAL, NULL, 0) = 7
  write(15, "\1\0\0\0\0\0\0\0", 8)= 8
  eventfd2(0, EFD_CLOEXEC|EFD_NONBLOCK)   = 14
  write(14, "\1\0\0\0\0\0\0\0", 8)= 8
  write(15, "\1\0\0\0\0\0\0\0", 8)= 8
  poll([{fd=14, events=POLLIN}], 1, 25000) = 1 ([{fd=14, revents=POLLIN}])
  read(14, "\1\0\0\0\0\0\0\0", 16)= 8
  poll([{fd=14, events=POLLIN}], 1, 25000

  
  During my first research I found this following to topics related to the 
issue:
  
https://askubuntu.com/questions/1184774/some-applications-on-ubuntu-19-10-very-slow-to-start

  This Stackoverflow topic links to the archlinux forum:
  https://bbs.archlinux.org/viewtopic.php?id=230036

  I can confirm that running the delayed applications with "dbus-launch
  --exit-with-session application" or by running it as root they are all
  starting without any delay.

  Thanks for your help! Let me know if you need any further information.

  Best Regards,
  Sebastian

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

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

[Touch-packages] [Bug 1915947] Re: very slow

[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/1915947

Title:
  very slow

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes turns tabs into new screens.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155
  Uname: Linux 4.4.0-138-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Feb 17 10:14:15 2021
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8240 / R3 Series] 
[1002:9838] (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Kabini [Radeon HD 8240 
/ R3 Series] [1462:7865]
  InstallationDate: Installed on 2017-10-13 (1222 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: MSI MS-7865
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic 
root=UUID=295205a4-8b2e-4f0e-bbf9-521bf7ee3cdd ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: AM1I (MS-7865)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.2:bd12/24/2014:svnMSI:pnMS-7865:pvr2.0:rvnMSI:rnAM1I(MS-7865):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7865
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Feb 17 05:49:43 2021
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Gaming Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1915947/+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 1915746] Re: systemd-resolved configuration does not resolve any hostnames

[Dan Streetman]

> # cat /etc/resolv.conf (linked to /run/resolvconf/resolv.conf)

resolvconf has been discouraged for a while; you should remove it, and
have resolv.conf symlink to the systemd-resolved stub-resolv.conf file.

Even if you need to keep it, this isn't a systemd bug, it would be a bug
in resolvconf (or possibly just a local misconfiguration).

** Package changed: systemd (Ubuntu) => resolvconf (Ubuntu)

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

Title:
  systemd-resolved configuration does not resolve any hostnames

Status in resolvconf package in Ubuntu:
  New

Bug description:
  systemd-resolved will, unter certain circumstances create local only
  DNS resolution:

  # host google.com
  ;; connection timed out; no servers could be reached

  
  looking at what is going on behind:

  # cat /etc/resolv.conf (linked to /run/resolvconf/resolv.conf)
  nameserver 127.0.0.1
  nameserver 127.0.0.53
  searchDOMAINS

  # systemd-resolve --status
  Global
   Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: foreign
  Current DNS Server: 127.0.0.1
 DNS Servers: 127.0.0.1
  DNS Domain: DOMAINS   

  Link 2 (eth0)
  Current Scopes: none
   Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
  DNS Domain: DOMAINS

  Link 3 (virbr0)
  Current Scopes: none
   Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

  Link 4 (vmnet1)
  Current Scopes: none
   Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

  Link 5 (vmnet2)
  Current Scopes: none
   Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

  Link 6 (vmnet8)
  Current Scopes: none
   Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

  This is a useless configuration: dnsmasq asks systemd-resolvd,
  systemd-resolvd asks dnsmasq. Without ever going to any of the
  upstream servers. One of them: systemd-resolvd or dnsmasq shall ask
  upstream servers. But non of them does.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu57
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Feb 15 19:16:05 2021
  InstallationDate: Installed on 2014-01-31 (2572 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  MachineType: Hewlett-Packard HP Compaq 6200 Pro MT PC
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-36-generic 
root=UUID=de4af024-5d59-4f85-b5ca-11f17f085706 ro rootflags=subvol=@ 
consoleblank=0 video=DP-1:e,HDMI-1:e
  SourcePackage: systemd
  UpgradeStatus: Upgraded to hirsute on 2018-11-23 (815 days ago)
  dmi.bios.date: 11/10/2011
  dmi.bios.release: 2.15
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.15
  dmi.board.name: 1497
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:br2.15:svnHewlett-Packard:pnHPCompaq6200ProMTPC:pvr:rvnHewlett-Packard:rn1497:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq 6200 Pro MT PC
  dmi.product.sku: XL504AV
  dmi.sys.vendor: Hewlett-Packard
  mtime.conffile..etc.systemd.resolved.conf: 2021-02-15T19:09:12.129281

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1915746/+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 1915947] [NEW] very slow

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Sometimes turns tabs into new screens.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155
Uname: Linux 4.4.0-138-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Feb 17 10:14:15 2021
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8240 / R3 Series] 
[1002:9838] (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Kabini [Radeon HD 8240 / 
R3 Series] [1462:7865]
InstallationDate: Installed on 2017-10-13 (1222 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: MSI MS-7865
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic 
root=UUID=295205a4-8b2e-4f0e-bbf9-521bf7ee3cdd ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/24/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V10.2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: AM1I (MS-7865)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.2:bd12/24/2014:svnMSI:pnMS-7865:pvr2.0:rvnMSI:rnAM1I(MS-7865):rvr2.0:cvnMSI:ct3:cvr2.0:
dmi.product.name: MS-7865
dmi.product.version: 2.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Feb 17 05:49:43 2021
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech USB Gaming Mouse MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial
-- 
very slow
https://bugs.launchpad.net/bugs/1915947
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 1887372] Re: Cannot create lvm upon IMSM raid array

[Jeff Lane]

Can this please be targeted for 21.10?

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

Title:
  Cannot create lvm upon IMSM raid array

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Focal:
  Confirmed
Status in lvm2 source package in Groovy:
  Confirmed
Status in lvm2 source package in Hirsute:
  Confirmed

Bug description:
  The issue has been observed on 2.3.7 (Ubuntu 20.04).
  Reported to lvm team:
  https://bugzilla.redhat.com/show_bug.cgi?id=1855251

  Steps to Reproduce:
  1. Create IMSM raid array:
  #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1
  #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G

  2. Create lvm volume on raid:
  # pvcreate -ff -y /dev/md/vol
  # vgcreate group0 /dev/md/vol
  # lvcreate -Z y -y -l +100%FREE group0 -n lvm0

  Actual results:
  Vg creation fails.

  Expected results:
  LVM should be able to determine the best drive and ignore duplicates.

  Additional info:
  IMSM metadata is written at the end of the drive. The first drive sector 
belongs to the raid volume and other metadata saved there (like lvm) can be 
recognized directly on raid members.

  The following patches should fix the issue (not verified yet):
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887372/+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 1891798] Re: Backport fix from sudo 1.8.22 to fix "stair-stepped output" bug

[Brian Murray]

** Tags added: rls-bb-incoming

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

Title:
  Backport fix from sudo 1.8.22 to fix "stair-stepped output" bug

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

Bug description:
  sudo 1.8.20 introduced a bug in commit
  44dc15d02dc0b34bf03bc971ba08d3a761c3a031
  that is fixed by sudo 1.8.22 in commit
  3b88cdfcd8d1a39eabbb5b7d0c8fe8f035d7a264

  When the "use_pty" option is enabled, "stair-stepped output" occurs if
  sudo is piped to another command.

  Example output attached in a text file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: sudo 1.8.21p2-3ubuntu1.2
  Uname: Linux 5.4.50+ x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 16 12:29:23 2020
  InstallationDate: Installed on 2014-05-10 (2290 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: sudo
  UpgradeStatus: Upgraded to bionic on 2018-11-24 (630 days ago)
  modified.conffile..etc.pam.d.sudo: [inaccessible: [Errno 13] Permission 
denied: '/etc/pam.d/sudo']
  modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: 
'/etc/sudoers']
  modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/README']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1891798/+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 1915936] Re: systemd-coredump user is created by something other than its derived systemd packages

[Eric Desrochers]

d/rules:
   91 CONFFLAGS_deb = \
   92 -Dselinux=true \
   93 -Dhwdb=true \
=> 94 -Dsysusers=true \

Would it make sense to turn this off ?

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

Title:
  systemd-coredump user is created by something other than its derived
  systemd packages

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Focal:
  New
Status in systemd source package in Groovy:
  New
Status in systemd source package in Hirsute:
  New
Status in systemd package in Debian:
  Unknown

Bug description:
  systemd-coredump binary package is instructed as follows:

  #debian/systemd-coredump.postinst:
  adduser --quiet --system --group --no-create-home --home /run/systemd \
  --gecos "systemd Core Dumper" systemd-coredump

  But one doesn't need this package to be installed to have the systemd-
  coredump user created. This was taken from a focal 20.04.2 fresh
  installation (Right after a vanilla installation):

  # cat /etc/passwd:
  ...
  systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
  ...

  # dpkg -l | grep -i systemd
  ii  dbus-user-session1.12.16-2ubuntu2.1
amd64simple interprocess messaging system (systemd --user integration)
  ii  libnss-systemd:amd64 245.4-4ubuntu3.4  
amd64nss module providing dynamic user and group name resolution
  ii  libpam-systemd:amd64 245.4-4ubuntu3.4  
amd64system and service manager - PAM module
  ii  libsystemd0:amd64245.4-4ubuntu3.4  
amd64systemd utility library
  ii  networkd-dispatcher  2.0.1-1   
all  Dispatcher service for systemd-networkd connection status changes
  ii  python3-systemd  234-3build2   
amd64Python 3 bindings for systemd
  ii  systemd  245.4-4ubuntu3.4  
amd64system and service manager
  ii  systemd-sysv 245.4-4ubuntu3.4  
amd64system and service manager - SysV links
  ii  systemd-timesyncd245.4-4ubuntu3.4  
amd64minimalistic service to synchronize local time with NTP servers

  # /var/log/syslog
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating group 
systemd-coredump with gid 999.
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating user 
systemd-coredump (systemd Core Dumper) with uid 999 and gid 999.

  
  Additionnally, you may notice the home directory during the user creation at 
installation sets it to "/" as opposed to "/run/systemd" directive in the 
appropriate postint. It is contradictory.

  * Why systemd-coredump user is created at installation time and/or without 
'systemd-coredump' package installed ?
  * Why this early creation set the home directory to "/" ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915936/+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 1915936] Re: systemd-coredump user is created by something other than its derived systemd packages

[Eric Desrochers]

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

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

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

** Also affects: systemd (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/1915936

Title:
  systemd-coredump user is created by something other than its derived
  systemd packages

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Focal:
  New
Status in systemd source package in Groovy:
  New
Status in systemd source package in Hirsute:
  New
Status in systemd package in Debian:
  Unknown

Bug description:
  systemd-coredump binary package is instructed as follows:

  #debian/systemd-coredump.postinst:
  adduser --quiet --system --group --no-create-home --home /run/systemd \
  --gecos "systemd Core Dumper" systemd-coredump

  But one doesn't need this package to be installed to have the systemd-
  coredump user created. This was taken from a focal 20.04.2 fresh
  installation (Right after a vanilla installation):

  # cat /etc/passwd:
  ...
  systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
  ...

  # dpkg -l | grep -i systemd
  ii  dbus-user-session1.12.16-2ubuntu2.1
amd64simple interprocess messaging system (systemd --user integration)
  ii  libnss-systemd:amd64 245.4-4ubuntu3.4  
amd64nss module providing dynamic user and group name resolution
  ii  libpam-systemd:amd64 245.4-4ubuntu3.4  
amd64system and service manager - PAM module
  ii  libsystemd0:amd64245.4-4ubuntu3.4  
amd64systemd utility library
  ii  networkd-dispatcher  2.0.1-1   
all  Dispatcher service for systemd-networkd connection status changes
  ii  python3-systemd  234-3build2   
amd64Python 3 bindings for systemd
  ii  systemd  245.4-4ubuntu3.4  
amd64system and service manager
  ii  systemd-sysv 245.4-4ubuntu3.4  
amd64system and service manager - SysV links
  ii  systemd-timesyncd245.4-4ubuntu3.4  
amd64minimalistic service to synchronize local time with NTP servers

  # /var/log/syslog
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating group 
systemd-coredump with gid 999.
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating user 
systemd-coredump (systemd Core Dumper) with uid 999 and gid 999.

  
  Additionnally, you may notice the home directory during the user creation at 
installation sets it to "/" as opposed to "/run/systemd" directive in the 
appropriate postint. It is contradictory.

  * Why systemd-coredump user is created at installation time and/or without 
'systemd-coredump' package installed ?
  * Why this early creation set the home directory to "/" ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915936/+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 1505670] Re: "uncaptured python exception"

[Rolf Leggewie]

I've long been using the patch from this ticket successfully and have
now published a bionic package in my LTS ppa
https://launchpad.net/~r0lf/+archive/ubuntu/stable  Other release
pockets to follow.

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

Title:
  "uncaptured python exception"

Status in python2.7 package in Ubuntu:
  New
Status in squid-deb-proxy package in Ubuntu:
  Confirmed

Bug description:
  I get the following error when running the discovery script on the
  command line.

  $ /usr/share/squid-deb-proxy-client/apt-avahi-discover
  error: uncaptured python exception, closing channel  
('10.1.2.3', 3142): 2147483647 (:[Errno 111] Connection 
refused [/usr/lib/python2.7/asyncore.py|read|83] 
[/usr/lib/python2.7/asyncore.py|handle_read_event|446] 
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
  error: uncaptured python exception, closing channel  
('10.0.3.1', 3142): 2147483647 (:[Errno 111] Connection 
refused [/usr/lib/python2.7/asyncore.py|read|83] 
[/usr/lib/python2.7/asyncore.py|handle_read_event|446] 
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
  error: uncaptured python exception, closing channel  
('172.24.74.129', 3142): 2147483647 (:[Errno 111] 
Connection refused [/usr/lib/python2.7/asyncore.py|read|83] 
[/usr/lib/python2.7/asyncore.py|handle_read_event|446] 
[/usr/lib/python2.7/asyncore.py|handle_connect_event|454])
  http://172.24.74.145:3142/

  The last line still returns the proper proxy URI so as far as I can
  tell things are still working.  The IP 10.1.2.3 is for an n2n VPN.
  This is on trusty with version 0.8.6ubuntu1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1505670/+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 1903814] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From i...@de.ibm.com 2021-02-17 11:51 EDT---
Here is the original complaint: 
https://lore.kernel.org/bpf/20200611205040.GA1853644@krava/

If you build the kernel with CONFIG_DEBUG_INFO_BTF, there is a 50%
chance that you will see "Failed verification: in-kernel BTF is
malformed" during boot. There was also a hang, reported by one of our
kernel team members, that we tracked down to the same issue, but
unfortunately I cannot find any details about it right now.

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

Title:
  [binutils] Prevent GOT access rewrite for certain symbols

Status in Ubuntu on IBM z Systems:
  Triaged
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Bionic:
  New
Status in binutils package in Debian:
  New

Bug description:
  [Impact]

   * In s390 kernel context, this bug manifests itself as random errors
  and infinite loops.

  [Test Case]

   * Needs to be confirmed by IBM
   * Build-time tests-suite (applied upstream) backported to Bionic in
 + ld/testsuite/ld-s390/gotreloc-1.s
 + ld/testsuite/ld-s390/gotreloc-1.ver
 + ld/testsuite/ld-s390/gotreloc_31-1.dd
 + ld/testuite/ld-s390/gotreloc_64-1.dd

  [Where problems could occur]

   * Binutils is a base toolchain package
 - A problem could potentially affect the whole system
 - With compiler/linker errors
 - Or random errors in the produced binaries
   * This patch touches only architecture specific code in bfd/elf64-s390.c
 - It would only affect the s390x architecture in this case

  [Other Info]
   
   * While testing the fix in Bileto, we found one pending autopkgtest 
regression with linux/amd64 4.15.0-135.139 which is resolved in 4.15.0-136.140 
(currently in -proposed).

  
  == Original Description ==
  Please backport the following bugfix into Ubuntu LTS: 
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e6213e09ed0e

  Some relevant historic links:
  Debian bugreport: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961736
  glibc bugreport: https://sourceware.org/bugzilla/show_bug.cgi?id=18960

  In s390 kernel context, this bug manifests itself as random errors and
  infinite loops, so it's fairly severe.

  These are the current versions of binutils:
  Package binutils

  xenial (16.04LTS) (devel): GNU assembler, linker and binary utilities
  2.26.1-1ubuntu1~16.04.8 [security]: amd64 i386
  2.26-8ubuntu2 [ports]: arm64 armhf powerpc ppc64el s390x
  xenial-updates (devel): GNU assembler, linker and binary utilities
  2.26.1-1ubuntu1~16.04.8: amd64 arm64 armhf i386 powerpc ppc64el s390x
  bionic (18.04LTS) (devel): GNU assembler, linker and binary utilities
  2.30-21ubuntu1~18.04.4 [security]: amd64 i386
  2.30-15ubuntu1 [ports]: arm64 armhf ppc64el s390x
  bionic-updates (devel): GNU assembler, linker and binary utilities
  2.30-21ubuntu1~18.04.4: amd64 arm64 armhf i386 ppc64el s390x
  focal (20.04LTS) (devel): GNU assembler, linker and binary utilities
  2.34-6ubuntu1: amd64 arm64 armhf i386 ppc64el s390x
  groovy (devel): GNU assembler, linker and binary utilities
  2.35.1-1ubuntu1: amd64 arm64 armhf i386 ppc64el s390x

  The patch applies fine to 2.26 and 2.30 (except for tests, but we
  don't need them). We don't need it on 2.32+.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903814/+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 1915945] [NEW] package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: installed sudo package post-installation script subprocess returned error exit status 1

[Alex Leandro Rosa]

Public bug reported:

I've put the system to upgrade and this error occured!!

I tried many ways to correct it but all attempts were unsuccesfull.

Best regards,

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: sudo 1.8.31-1ubuntu1.2
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
AptOrdering:
 software-properties-common:amd64: Install
 software-properties-gtk:amd64: Install
 python3-software-properties:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Feb 17 13:43:57 2021
DuplicateSignature:
 package:sudo:1.8.31-1ubuntu1.2
 Setting up sudo (1.8.31-1ubuntu1.2) ...
 chown: alterando o dono de '/etc/sudoers': Operação não permitida
 dpkg: error processing package sudo (--configure):
  installed sudo package post-installation script subprocess returned error 
exit status 1
ErrorMessage: installed sudo package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2018-12-12 (797 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: sudo
Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: installed sudo 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-09-30 (139 days ago)
VisudoCheck:
 /etc/sudoers: análise OK
 /etc/sudoers.d/README: análise OK
mtime.conffile..etc.sudoers: 2020-12-30T18:27:17.782421

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

Title:
  package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: installed
  sudo package post-installation script subprocess returned error exit
  status 1

Status in sudo package in Ubuntu:
  New

Bug description:
  I've put the system to upgrade and this error occured!!

  I tried many ways to correct it but all attempts were unsuccesfull.

  Best regards,

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: sudo 1.8.31-1ubuntu1.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  AptOrdering:
   software-properties-common:amd64: Install
   software-properties-gtk:amd64: Install
   python3-software-properties:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb 17 13:43:57 2021
  DuplicateSignature:
   package:sudo:1.8.31-1ubuntu1.2
   Setting up sudo (1.8.31-1ubuntu1.2) ...
   chown: alterando o dono de '/etc/sudoers': Operação não permitida
   dpkg: error processing package sudo (--configure):
installed sudo package post-installation script subprocess returned error 
exit status 1
  ErrorMessage: installed sudo package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2018-12-12 (797 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: sudo
  Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: installed 
sudo package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-09-30 (139 days ago)
  VisudoCheck:
   /etc/sudoers: análise OK
   /etc/sudoers.d/README: análise OK
  mtime.conffile..etc.sudoers: 2020-12-30T18:27:17.782421

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915945/+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 1915945] Re: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: installed sudo package post-installation script subprocess returned error exit status 1

[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 sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1915945

Title:
  package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: installed
  sudo package post-installation script subprocess returned error exit
  status 1

Status in sudo package in Ubuntu:
  New

Bug description:
  I've put the system to upgrade and this error occured!!

  I tried many ways to correct it but all attempts were unsuccesfull.

  Best regards,

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: sudo 1.8.31-1ubuntu1.2
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  AptOrdering:
   software-properties-common:amd64: Install
   software-properties-gtk:amd64: Install
   python3-software-properties:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb 17 13:43:57 2021
  DuplicateSignature:
   package:sudo:1.8.31-1ubuntu1.2
   Setting up sudo (1.8.31-1ubuntu1.2) ...
   chown: alterando o dono de '/etc/sudoers': Operação não permitida
   dpkg: error processing package sudo (--configure):
installed sudo package post-installation script subprocess returned error 
exit status 1
  ErrorMessage: installed sudo package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2018-12-12 (797 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: sudo
  Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: installed 
sudo package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-09-30 (139 days ago)
  VisudoCheck:
   /etc/sudoers: análise OK
   /etc/sudoers.d/README: análise OK
  mtime.conffile..etc.sudoers: 2020-12-30T18:27:17.782421

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915945/+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 1915936] Re: systemd-coredump user is created by something other than its derived systemd packages

[Eric Desrochers]

** Bug watch added: Debian Bug tracker #982976
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982976

** Also affects: systemd (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982976
   Importance: Unknown
   Status: Unknown

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

Title:
  systemd-coredump user is created by something other than its derived
  systemd packages

Status in systemd package in Ubuntu:
  New
Status in systemd package in Debian:
  Unknown

Bug description:
  systemd-coredump binary package is instructed as follows:

  #debian/systemd-coredump.postinst:
  adduser --quiet --system --group --no-create-home --home /run/systemd \
  --gecos "systemd Core Dumper" systemd-coredump

  But one doesn't need this package to be installed to have the systemd-
  coredump user created. This was taken from a focal 20.04.2 fresh
  installation (Right after a vanilla installation):

  # cat /etc/passwd:
  ...
  systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
  ...

  # dpkg -l | grep -i systemd
  ii  dbus-user-session1.12.16-2ubuntu2.1
amd64simple interprocess messaging system (systemd --user integration)
  ii  libnss-systemd:amd64 245.4-4ubuntu3.4  
amd64nss module providing dynamic user and group name resolution
  ii  libpam-systemd:amd64 245.4-4ubuntu3.4  
amd64system and service manager - PAM module
  ii  libsystemd0:amd64245.4-4ubuntu3.4  
amd64systemd utility library
  ii  networkd-dispatcher  2.0.1-1   
all  Dispatcher service for systemd-networkd connection status changes
  ii  python3-systemd  234-3build2   
amd64Python 3 bindings for systemd
  ii  systemd  245.4-4ubuntu3.4  
amd64system and service manager
  ii  systemd-sysv 245.4-4ubuntu3.4  
amd64system and service manager - SysV links
  ii  systemd-timesyncd245.4-4ubuntu3.4  
amd64minimalistic service to synchronize local time with NTP servers

  # /var/log/syslog
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating group 
systemd-coredump with gid 999.
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating user 
systemd-coredump (systemd Core Dumper) with uid 999 and gid 999.

  
  Additionnally, you may notice the home directory during the user creation at 
installation sets it to "/" as opposed to "/run/systemd" directive in the 
appropriate postint. It is contradictory.

  * Why systemd-coredump user is created at installation time and/or without 
'systemd-coredump' package installed ?
  * Why this early creation set the home directory to "/" ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915936/+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 1915936] Re: systemd-coredump user is created by something other than its derived systemd packages

[Eric Desrochers]

Right, but it doesn't seem right to have it set by default to "/".

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

Title:
  systemd-coredump user is created by something other than its derived
  systemd packages

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-coredump binary package is instructed as follows:

  #debian/systemd-coredump.postinst:
  adduser --quiet --system --group --no-create-home --home /run/systemd \
  --gecos "systemd Core Dumper" systemd-coredump

  But one doesn't need this package to be installed to have the systemd-
  coredump user created. This was taken from a focal 20.04.2 fresh
  installation (Right after a vanilla installation):

  # cat /etc/passwd:
  ...
  systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
  ...

  # dpkg -l | grep -i systemd
  ii  dbus-user-session1.12.16-2ubuntu2.1
amd64simple interprocess messaging system (systemd --user integration)
  ii  libnss-systemd:amd64 245.4-4ubuntu3.4  
amd64nss module providing dynamic user and group name resolution
  ii  libpam-systemd:amd64 245.4-4ubuntu3.4  
amd64system and service manager - PAM module
  ii  libsystemd0:amd64245.4-4ubuntu3.4  
amd64systemd utility library
  ii  networkd-dispatcher  2.0.1-1   
all  Dispatcher service for systemd-networkd connection status changes
  ii  python3-systemd  234-3build2   
amd64Python 3 bindings for systemd
  ii  systemd  245.4-4ubuntu3.4  
amd64system and service manager
  ii  systemd-sysv 245.4-4ubuntu3.4  
amd64system and service manager - SysV links
  ii  systemd-timesyncd245.4-4ubuntu3.4  
amd64minimalistic service to synchronize local time with NTP servers

  # /var/log/syslog
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating group 
systemd-coredump with gid 999.
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating user 
systemd-coredump (systemd Core Dumper) with uid 999 and gid 999.

  
  Additionnally, you may notice the home directory during the user creation at 
installation sets it to "/" as opposed to "/run/systemd" directive in the 
appropriate postint. It is contradictory.

  * Why systemd-coredump user is created at installation time and/or without 
'systemd-coredump' package installed ?
  * Why this early creation set the home directory to "/" ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915936/+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 1915941] [NEW] Pinta crashes especially with large images

[MadhuSoodanan]

Public bug reported:

Pinta crashes especially with large images.  It occurred several times.
Pinta becomes useless. Can't use it for more than two minutes.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 17 22:05:00 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Device [8086:9ba8] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
InstallationDate: Installed on 2021-01-14 (34 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
 Bus 001 Device 002: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical 
Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
 |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
 |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
MachineType: Gigabyte Technology Co., Ltd. H410M S2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic 
root=UUID=2adc7727-391f-4ea4-8f4c-b89ee1d7120b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/08/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: Default string
dmi.board.name: H410M S2
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.:bvrF5:bd10/08/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnH410MS2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH410MS2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: H410 MB
dmi.product.name: H410M S2
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

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

Title:
  Pinta crashes especially with large images

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Pinta crashes especially with large images.  It occurred several
  times. Pinta becomes useless. Can't use it for more than two minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 17 22:05:00 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:9ba8] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2021-01-14 (34 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
   Bus 001 Device 002: ID 413c:301a Dell Computer Corp. Dell MS116 USB Optical 
Mouse
   Bus 0

[Touch-packages] [Bug 1915936] Re: systemd-coredump user is created by something other than its derived systemd packages

[Balint Reczey]

Yes, the user is created using /usr/lib/sysusers.d/systemd.conf .

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

Title:
  systemd-coredump user is created by something other than its derived
  systemd packages

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-coredump binary package is instructed as follows:

  #debian/systemd-coredump.postinst:
  adduser --quiet --system --group --no-create-home --home /run/systemd \
  --gecos "systemd Core Dumper" systemd-coredump

  But one doesn't need this package to be installed to have the systemd-
  coredump user created. This was taken from a focal 20.04.2 fresh
  installation (Right after a vanilla installation):

  # cat /etc/passwd:
  ...
  systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
  ...

  # dpkg -l | grep -i systemd
  ii  dbus-user-session1.12.16-2ubuntu2.1
amd64simple interprocess messaging system (systemd --user integration)
  ii  libnss-systemd:amd64 245.4-4ubuntu3.4  
amd64nss module providing dynamic user and group name resolution
  ii  libpam-systemd:amd64 245.4-4ubuntu3.4  
amd64system and service manager - PAM module
  ii  libsystemd0:amd64245.4-4ubuntu3.4  
amd64systemd utility library
  ii  networkd-dispatcher  2.0.1-1   
all  Dispatcher service for systemd-networkd connection status changes
  ii  python3-systemd  234-3build2   
amd64Python 3 bindings for systemd
  ii  systemd  245.4-4ubuntu3.4  
amd64system and service manager
  ii  systemd-sysv 245.4-4ubuntu3.4  
amd64system and service manager - SysV links
  ii  systemd-timesyncd245.4-4ubuntu3.4  
amd64minimalistic service to synchronize local time with NTP servers

  # /var/log/syslog
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating group 
systemd-coredump with gid 999.
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating user 
systemd-coredump (systemd Core Dumper) with uid 999 and gid 999.

  
  Additionnally, you may notice the home directory during the user creation at 
installation sets it to "/" as opposed to "/run/systemd" directive in the 
appropriate postint. It is contradictory.

  * Why systemd-coredump user is created at installation time and/or without 
'systemd-coredump' package installed ?
  * Why this early creation set the home directory to "/" ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915936/+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 1903814] Re: [binutils] Prevent GOT access rewrite for certain symbols

[Lukas Märdian]

So the regression tests are looking good so far. I'm currently still
verifying that the regression with the linux kernel on Intel (404s) is
fixed with 4.15.0-136.140 (from -proposed). If that works out, I'll copy
the packages to the archive for verification by the SRU team.

I've SRU'ifyed the description of this bug report. Is there any more
specific test case you could give to verify that this bug is indeed
fixed? How to reproduce those "random errors and infinite loops"?

** Description changed:

- Please backport the following bugfix into Ubuntu LTS:
- https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e6213e09ed0e
+ [Impact]
+ 
+  * In s390 kernel context, this bug manifests itself as random errors
+ and infinite loops.
+ 
+ [Test Case]
+ 
+  * Needs to be confirmed by IBM
+  * Build-time tests-suite (applied upstream) backported to Bionic in
++ ld/testsuite/ld-s390/gotreloc-1.s
++ ld/testsuite/ld-s390/gotreloc-1.ver
++ ld/testsuite/ld-s390/gotreloc_31-1.dd
++ ld/testuite/ld-s390/gotreloc_64-1.dd
+ 
+ [Where problems could occur]
+ 
+  * Binutils is a base toolchain package
+- A problem could potentially affect the whole system
+- With compiler/linker errors
+- Or random errors in the produced binaries
+  * This patch touches only architecture specific code in bfd/elf64-s390.c
+- It would only affect the s390x architecture in this case
+ 
+ [Other Info]
+  
+  * While testing the fix in Bileto, we found one pending autopkgtest 
regression with linux/amd64 4.15.0-135.139 which is resolved in 4.15.0-136.140 
(currently in -proposed).
+ 
+ 
+ == Original Description ==
+ Please backport the following bugfix into Ubuntu LTS: 
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e6213e09ed0e
  
  Some relevant historic links:
  Debian bugreport: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961736
  glibc bugreport: https://sourceware.org/bugzilla/show_bug.cgi?id=18960
  
  In s390 kernel context, this bug manifests itself as random errors and
  infinite loops, so it's fairly severe.
  
  These are the current versions of binutils:
  Package binutils
  
- xenial (16.04LTS) (devel): GNU assembler, linker and binary utilities
- 2.26.1-1ubuntu1~16.04.8 [security]: amd64 i386
- 2.26-8ubuntu2 [ports]: arm64 armhf powerpc ppc64el s390x
- xenial-updates (devel): GNU assembler, linker and binary utilities
- 2.26.1-1ubuntu1~16.04.8: amd64 arm64 armhf i386 powerpc ppc64el s390x
- bionic (18.04LTS) (devel): GNU assembler, linker and binary utilities
- 2.30-21ubuntu1~18.04.4 [security]: amd64 i386
- 2.30-15ubuntu1 [ports]: arm64 armhf ppc64el s390x
- bionic-updates (devel): GNU assembler, linker and binary utilities
- 2.30-21ubuntu1~18.04.4: amd64 arm64 armhf i386 ppc64el s390x
- focal (20.04LTS) (devel): GNU assembler, linker and binary utilities
- 2.34-6ubuntu1: amd64 arm64 armhf i386 ppc64el s390x
- groovy (devel): GNU assembler, linker and binary utilities
- 2.35.1-1ubuntu1: amd64 arm64 armhf i386 ppc64el s390x
+ xenial (16.04LTS) (devel): GNU assembler, linker and binary utilities
+ 2.26.1-1ubuntu1~16.04.8 [security]: amd64 i386
+ 2.26-8ubuntu2 [ports]: arm64 armhf powerpc ppc64el s390x
+ xenial-updates (devel): GNU assembler, linker and binary utilities
+ 2.26.1-1ubuntu1~16.04.8: amd64 arm64 armhf i386 powerpc ppc64el s390x
+ bionic (18.04LTS) (devel): GNU assembler, linker and binary utilities
+ 2.30-21ubuntu1~18.04.4 [security]: amd64 i386
+ 2.30-15ubuntu1 [ports]: arm64 armhf ppc64el s390x
+ bionic-updates (devel): GNU assembler, linker and binary utilities
+ 2.30-21ubuntu1~18.04.4: amd64 arm64 armhf i386 ppc64el s390x
+ focal (20.04LTS) (devel): GNU assembler, linker and binary utilities
+ 2.34-6ubuntu1: amd64 arm64 armhf i386 ppc64el s390x
+ groovy (devel): GNU assembler, linker and binary utilities
+ 2.35.1-1ubuntu1: amd64 arm64 armhf i386 ppc64el s390x
  
  The patch applies fine to 2.26 and 2.30 (except for tests, but we don't
  need them). We don't need it on 2.32+.

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

Title:
  [binutils] Prevent GOT access rewrite for certain symbols

Status in Ubuntu on IBM z Systems:
  Triaged
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Bionic:
  New
Status in binutils package in Debian:
  New

Bug description:
  [Impact]

   * In s390 kernel context, this bug manifests itself as random errors
  and infinite loops.

  [Test Case]

   * Needs to be confirmed by IBM
   * Build-time tests-suite (applied upstream) backported to Bionic in
 + ld/testsuite/ld-s390/gotreloc-1.s
 + ld/testsuite/ld-s390/gotreloc-1.ver
 + ld/testsuite/ld-s390/gotreloc_31-1.dd
 + ld/testuite/ld-s390/gotreloc_64-1.dd

  [Where problems could occur]

   

[Touch-packages] [Bug 1915936] Re: systemd-coredump user is created by something other than its derived systemd packages

[Eric Desrochers]

** Summary changed:

- systemd-coredump user is create by something other than its derived systemd 
packages
+ systemd-coredump user is created by something other than its derived systemd 
packages

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

Title:
  systemd-coredump user is created by something other than its derived
  systemd packages

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-coredump binary package is instructed as follows:

  #debian/systemd-coredump.postinst:
  adduser --quiet --system --group --no-create-home --home /run/systemd \
  --gecos "systemd Core Dumper" systemd-coredump

  But one doesn't need this package to be installed to have the systemd-
  coredump user created. This was taken from a focal 20.04.2 fresh
  installation (Right after a vanilla installation):

  # cat /etc/passwd:
  ...
  systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
  ...

  # dpkg -l | grep -i systemd
  ii  dbus-user-session1.12.16-2ubuntu2.1
amd64simple interprocess messaging system (systemd --user integration)
  ii  libnss-systemd:amd64 245.4-4ubuntu3.4  
amd64nss module providing dynamic user and group name resolution
  ii  libpam-systemd:amd64 245.4-4ubuntu3.4  
amd64system and service manager - PAM module
  ii  libsystemd0:amd64245.4-4ubuntu3.4  
amd64systemd utility library
  ii  networkd-dispatcher  2.0.1-1   
all  Dispatcher service for systemd-networkd connection status changes
  ii  python3-systemd  234-3build2   
amd64Python 3 bindings for systemd
  ii  systemd  245.4-4ubuntu3.4  
amd64system and service manager
  ii  systemd-sysv 245.4-4ubuntu3.4  
amd64system and service manager - SysV links
  ii  systemd-timesyncd245.4-4ubuntu3.4  
amd64minimalistic service to synchronize local time with NTP servers

  # /var/log/syslog
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating group 
systemd-coredump with gid 999.
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating user 
systemd-coredump (systemd Core Dumper) with uid 999 and gid 999.

  
  Additionnally, you may notice the home directory during the user creation at 
installation sets it to "/" as opposed to "/run/systemd" directive in the 
appropriate postint. It is contradictory.

  * Why systemd-coredump user is created at installation time and/or without 
'systemd-coredump' package installed ?
  * Why this early creation set the home directory to "/" ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915936/+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 1915936] Re: systemd-coredump user is create by something other than its derived systemd packages

[Eric Desrochers]

Home Directory¶
The home directory for a new system user. If omitted, defaults to the root 
directory.

Only applies to lines of type u and should otherwise be left unset (or
"-"). It is recommended to omit this, unless software strictly requires
a home directory to be set.

systemd-sysusers only sets the home directory record in the user
database. To actually create the directory, consider adding a
corresponding tmpfiles.d(5) fragment.

** Tags added: seg sts

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

Title:
  systemd-coredump user is create by something other than its derived
  systemd packages

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-coredump binary package is instructed as follows:

  #debian/systemd-coredump.postinst:
  adduser --quiet --system --group --no-create-home --home /run/systemd \
  --gecos "systemd Core Dumper" systemd-coredump

  But one doesn't need this package to be installed to have the systemd-
  coredump user created. This was taken from a focal 20.04.2 fresh
  installation (Right after a vanilla installation):

  # cat /etc/passwd:
  ...
  systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
  ...

  # dpkg -l | grep -i systemd
  ii  dbus-user-session1.12.16-2ubuntu2.1
amd64simple interprocess messaging system (systemd --user integration)
  ii  libnss-systemd:amd64 245.4-4ubuntu3.4  
amd64nss module providing dynamic user and group name resolution
  ii  libpam-systemd:amd64 245.4-4ubuntu3.4  
amd64system and service manager - PAM module
  ii  libsystemd0:amd64245.4-4ubuntu3.4  
amd64systemd utility library
  ii  networkd-dispatcher  2.0.1-1   
all  Dispatcher service for systemd-networkd connection status changes
  ii  python3-systemd  234-3build2   
amd64Python 3 bindings for systemd
  ii  systemd  245.4-4ubuntu3.4  
amd64system and service manager
  ii  systemd-sysv 245.4-4ubuntu3.4  
amd64system and service manager - SysV links
  ii  systemd-timesyncd245.4-4ubuntu3.4  
amd64minimalistic service to synchronize local time with NTP servers

  # /var/log/syslog
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating group 
systemd-coredump with gid 999.
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating user 
systemd-coredump (systemd Core Dumper) with uid 999 and gid 999.

  
  Additionnally, you may notice the home directory during the user creation at 
installation sets it to "/" as opposed to "/run/systemd" directive in the 
appropriate postint. It is contradictory.

  * Why systemd-coredump user is created at installation time and/or without 
'systemd-coredump' package installed ?
  * Why this early creation set the home directory to "/" ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915936/+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 1915936] Re: systemd-coredump user is create by something other than its derived systemd packages

[Eric Desrochers]

https://www.freedesktop.org/software/systemd/man/sysusers.d.html#

u
Create a system user and group of the specified name should they not exist yet. 
The user's primary group will be set to the group bearing the same name unless 
the ID field specifies it. The account will be created disabled, so that logins 
are not allowed.

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

Title:
  systemd-coredump user is create by something other than its derived
  systemd packages

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-coredump binary package is instructed as follows:

  #debian/systemd-coredump.postinst:
  adduser --quiet --system --group --no-create-home --home /run/systemd \
  --gecos "systemd Core Dumper" systemd-coredump

  But one doesn't need this package to be installed to have the systemd-
  coredump user created. This was taken from a focal 20.04.2 fresh
  installation (Right after a vanilla installation):

  # cat /etc/passwd:
  ...
  systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
  ...

  # dpkg -l | grep -i systemd
  ii  dbus-user-session1.12.16-2ubuntu2.1
amd64simple interprocess messaging system (systemd --user integration)
  ii  libnss-systemd:amd64 245.4-4ubuntu3.4  
amd64nss module providing dynamic user and group name resolution
  ii  libpam-systemd:amd64 245.4-4ubuntu3.4  
amd64system and service manager - PAM module
  ii  libsystemd0:amd64245.4-4ubuntu3.4  
amd64systemd utility library
  ii  networkd-dispatcher  2.0.1-1   
all  Dispatcher service for systemd-networkd connection status changes
  ii  python3-systemd  234-3build2   
amd64Python 3 bindings for systemd
  ii  systemd  245.4-4ubuntu3.4  
amd64system and service manager
  ii  systemd-sysv 245.4-4ubuntu3.4  
amd64system and service manager - SysV links
  ii  systemd-timesyncd245.4-4ubuntu3.4  
amd64minimalistic service to synchronize local time with NTP servers

  # /var/log/syslog
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating group 
systemd-coredump with gid 999.
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating user 
systemd-coredump (systemd Core Dumper) with uid 999 and gid 999.

  
  Additionnally, you may notice the home directory during the user creation at 
installation sets it to "/" as opposed to "/run/systemd" directive in the 
appropriate postint. It is contradictory.

  * Why systemd-coredump user is created at installation time and/or without 
'systemd-coredump' package installed ?
  * Why this early creation set the home directory to "/" ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915936/+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 1915936] Re: systemd-coredump user is create by something other than its derived systemd packages

[Eric Desrochers]

sudo /bin/systemd-sysusers --cat-config

# /usr/lib/sysusers.d/systemd.conf
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

g systemd-journal   - -
u systemd-network   - "systemd Network Management"
u systemd-resolve   - "systemd Resolver"
u systemd-timesync  - "systemd Time Synchronization"
u systemd-coredump  - "systemd Core Dumper"

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

Title:
  systemd-coredump user is create by something other than its derived
  systemd packages

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-coredump binary package is instructed as follows:

  #debian/systemd-coredump.postinst:
  adduser --quiet --system --group --no-create-home --home /run/systemd \
  --gecos "systemd Core Dumper" systemd-coredump

  But one doesn't need this package to be installed to have the systemd-
  coredump user created. This was taken from a focal 20.04.2 fresh
  installation (Right after a vanilla installation):

  # cat /etc/passwd:
  ...
  systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
  ...

  # dpkg -l | grep -i systemd
  ii  dbus-user-session1.12.16-2ubuntu2.1
amd64simple interprocess messaging system (systemd --user integration)
  ii  libnss-systemd:amd64 245.4-4ubuntu3.4  
amd64nss module providing dynamic user and group name resolution
  ii  libpam-systemd:amd64 245.4-4ubuntu3.4  
amd64system and service manager - PAM module
  ii  libsystemd0:amd64245.4-4ubuntu3.4  
amd64systemd utility library
  ii  networkd-dispatcher  2.0.1-1   
all  Dispatcher service for systemd-networkd connection status changes
  ii  python3-systemd  234-3build2   
amd64Python 3 bindings for systemd
  ii  systemd  245.4-4ubuntu3.4  
amd64system and service manager
  ii  systemd-sysv 245.4-4ubuntu3.4  
amd64system and service manager - SysV links
  ii  systemd-timesyncd245.4-4ubuntu3.4  
amd64minimalistic service to synchronize local time with NTP servers

  # /var/log/syslog
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating group 
systemd-coredump with gid 999.
  syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating user 
systemd-coredump (systemd Core Dumper) with uid 999 and gid 999.

  
  Additionnally, you may notice the home directory during the user creation at 
installation sets it to "/" as opposed to "/run/systemd" directive in the 
appropriate postint. It is contradictory.

  * Why systemd-coredump user is created at installation time and/or without 
'systemd-coredump' package installed ?
  * Why this early creation set the home directory to "/" ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915936/+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 1912052] Re: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 20.10 (not even wired, cable headset)

[Launchpad Bug Tracker]

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

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

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

Title:
  [Acer Spin 5 - SP513-54N] External headset microphone not working on
  Ubuntu 20.10 (not even wired, cable headset)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Recently, external microphone has stopped working while using classic
  wired audio combo jack headset.

  Basics:

  1) Headset's microphone works fine both in MS Windows on the same machine and 
on older Xubuntu on another machine.
  2) Internal laptop mic works normally.
  3) Yes, I have mic unmuted in settings.

  I've followed whole step1 from this troubleshoot guide:
  https://help.ubuntu.com/community/SoundTroubleshootingProcedure

  Did not help.

  There are more information with screenshots here:
  https://askubuntu.com/questions/1305942/external-headset-microphone-
  not-working-on-ubuntu-20-10-not-even-wired-cable-h:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crysman2301 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 16 13:31:13 2021
  InstallationDate: Installed on 2020-06-19 (210 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago)
  dmi.bios.date: 07/17/2020
  dmi.bios.release: 1.5
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.name: Caboom_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.05
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05:
  dmi.product.family: Spin 5
  dmi.product.name: Spin SP513-54N
  dmi.product.sku: 
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1912052/+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 1915936] [NEW] systemd-coredump user is create by something other than its derived systemd packages

[Eric Desrochers]

Public bug reported:

systemd-coredump binary package is instructed as follows:

#debian/systemd-coredump.postinst:
adduser --quiet --system --group --no-create-home --home /run/systemd \
--gecos "systemd Core Dumper" systemd-coredump

But one doesn't need this package to be installed to have the systemd-
coredump user created. This was taken from a focal 20.04.2 fresh
installation (Right after a vanilla installation):

# cat /etc/passwd:
...
systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
...

# dpkg -l | grep -i systemd
ii  dbus-user-session1.12.16-2ubuntu2.1
amd64simple interprocess messaging system (systemd --user integration)
ii  libnss-systemd:amd64 245.4-4ubuntu3.4  
amd64nss module providing dynamic user and group name resolution
ii  libpam-systemd:amd64 245.4-4ubuntu3.4  
amd64system and service manager - PAM module
ii  libsystemd0:amd64245.4-4ubuntu3.4  
amd64systemd utility library
ii  networkd-dispatcher  2.0.1-1   all  
Dispatcher service for systemd-networkd connection status changes
ii  python3-systemd  234-3build2   
amd64Python 3 bindings for systemd
ii  systemd  245.4-4ubuntu3.4  
amd64system and service manager
ii  systemd-sysv 245.4-4ubuntu3.4  
amd64system and service manager - SysV links
ii  systemd-timesyncd245.4-4ubuntu3.4  
amd64minimalistic service to synchronize local time with NTP servers

# /var/log/syslog
syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating group 
systemd-coredump with gid 999.
syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating user 
systemd-coredump (systemd Core Dumper) with uid 999 and gid 999.


Additionnally, you may notice the home directory during the user creation at 
installation sets it to "/" as opposed to "/run/systemd" directive in the 
appropriate postint. It is contradictory.

* Why systemd-coredump user is created at installation time and/or without 
'systemd-coredump' package installed ?
* Why this early creation set the home directory to "/" ?

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

** Description changed:

  systemd-coredump binary package is instructed as follows:
  
- #debian/systemd-coredump.postinst:
+ #debian/systemd-coredump.postinst:
  adduser --quiet --system --group --no-create-home --home /run/systemd \
  --gecos "systemd Core Dumper" systemd-coredump
  
  But one doesn't need this package to be installed to have the systemd-
  coredump user created. This was taken from a focal 20.04.2 fresh
  installation (Right after a vanilla installation):
  
  # cat /etc/passwd:
  ...
  systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
  ...
  
  # dpkg -l | grep -i systemd
  ii  dbus-user-session1.12.16-2ubuntu2.1
amd64simple interprocess messaging system (systemd --user integration)
  ii  libnss-systemd:amd64 245.4-4ubuntu3.4  
amd64nss module providing dynamic user and group name resolution
  ii  libpam-systemd:amd64 245.4-4ubuntu3.4  
amd64system and service manager - PAM module
  ii  libsystemd0:amd64245.4-4ubuntu3.4  
amd64systemd utility library
  ii  networkd-dispatcher  2.0.1-1   
all  Dispatcher service for systemd-networkd connection status changes
  ii  python3-systemd  234-3build2   
amd64Python 3 bindings for systemd
  ii  systemd  245.4-4ubuntu3.4  
amd64system and service manager
  ii  systemd-sysv 245.4-4ubuntu3.4  
amd64system and service manager - SysV links
  ii  systemd-timesyncd245.4-4ubuntu3.4  
amd64minimalistic service to synchronize local time with NTP servers
  
- 
- # /var/log/installer/installer-journal.txt
- Feb 17 15:27:19 ubuntu-server systemd-sysusers[844]: Creating group 
systemd-coredump with gid 998.
- Feb 17 15:27:19 ubuntu-server systemd-sysusers[844]: Creating user 
systemd-coredump (systemd Core Dumper) with uid 998 and gid 998.
+ # /var/log/syslog
+ syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating group 
systemd-coredump with gid 999.
+ syslog:Feb 17 15:31:56 test systemd-sysusers[402]: Creating user 
systemd-coredump (systemd Core Dumper) with uid 999 and gid 999.
  
  
  Additionnally, you may notice the home directory during the user creation at 
installation sets it to "/" as opposed to "/run/sy

[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones

[Mohd Imran Jamadar]

Mr Robert Joynt,


I am on Ubuntu 20.10, on OMEN-by-HP-Laptop-15-dc1xxx with this Realtek ALC295

I get sound, from head phone , loud and clear, if i plug in the
headphone jack, sound switches from speaker to headphone, and vice
versa.

But if remove the headphone , then the sound from the speaker like low
or mono in nature? will the above fix work?

Please advise?

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New
Status in Fedora:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1648183] Re: Crackling and popping sound when using headphones

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New
Status in Fedora:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Özgür Adem Işıklı]

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

** Information type changed from Public to Public Security

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1160048] Re: add-apt-repository won't uncomment a commented-out source

[Dan Streetman]

fixed when using add-apt-repository since groovy

** Changed in: software-properties (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  add-apt-repository won't uncomment a commented-out source

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Assume you're frequently testing software, so you add, remove (purge)
  and re-add PPAs.

  sudo add-apt-repository ppa:someteam/ppa
  sudo apt-get uppdate
  sudo apt-get install someprogram

  ... time passes and you no longer need that program, or wish to test
  your system without it ..

  sudo ppa-purge ppa:someteam/ppa

  This will remove the ppa by commenting out the "deb ..." line in the
  sources file in /etc/apt/sources.list.d

  Later, you need to do more testing of the app or some other app from
  the same ppa so you re-add it:-

  sudo add-apt-repository ppa:someteam/ppa

  However, this does _not_ add the PPA because the line/file already
  exists, albeit with a # in front of the "deb ...".

  Some might argue that it is the fault of ppa-purge for commenting the
  line out. I disagree. I believe ppa-purge _should_ comment out the
  "deb ..." line because sometimes you want to go back to the file to
  remind yourself what the ppa was that you got something from, or to
  just manually re-enable it.

  Given the single role of add-apt-repository is to add a ppa, I'd
  conclude it's add-apt-repository which is broken, given it doesn't add
  one in this common scenario.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: software-properties-common 0.92.17
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic x86_64
  ApportVersion: 2.9.2-0ubuntu4
  Architecture: amd64
  Date: Mon Mar 25 21:39:42 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-06-29 (269 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to raring on 2013-01-18 (66 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1160048/+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 1717522] Re: add-apt-repository --remove & software-properties-gtk do not delete PPA files

[Dan Streetman]

this has been fixed in g and later.

** Changed in: software-properties (Ubuntu)
   Status: New => Fix Released

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

Title:
  add-apt-repository --remove & software-properties-gtk  do not delete
  PPA files

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:

  When removing a ppa with software-properties-gtk or with :

  `sudo add-apt-repository --remove ppa:xxx/yyy
  `

  it merely empties the file one wants to remove and leaves an empty 
theuglyppa.list file in `/etc/apt/sources.list.d/` 
  This seem quite illogical to keep such residue especially for newbies who 
won't know that they should add :

  `sudo rm /etc/apt/sources.list.d/theuglyppa.list*
  `

  to their cleaning procedure.

  Could the removal actually remove ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1717522/+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 1717522] Re: add-apt-repository --remove & software-properties-gtk do not delete PPA files

[Dan Streetman]

> this has been fixed in g and later.

i should clarify, it's fixed when using add-apt-repository. software-
properties-gtk goes through a different path I believe, not sure if it
still leaves the empty file.

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

Title:
  add-apt-repository --remove & software-properties-gtk  do not delete
  PPA files

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:

  When removing a ppa with software-properties-gtk or with :

  `sudo add-apt-repository --remove ppa:xxx/yyy
  `

  it merely empties the file one wants to remove and leaves an empty 
theuglyppa.list file in `/etc/apt/sources.list.d/` 
  This seem quite illogical to keep such residue especially for newbies who 
won't know that they should add :

  `sudo rm /etc/apt/sources.list.d/theuglyppa.list*
  `

  to their cleaning procedure.

  Could the removal actually remove ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1717522/+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 1915250] Re: buildd file owner/group for shared libraries

[Dimitri John Ledkov]

fakeroot with glibc broke dpkg-deb for packages that do not use "Rules-
Requires-Root: no" was broken.

binutils stopped preserving permissions from objcopy & strip, leading to
incorrect permissions of files after stripping.

fakeroot is now patched with better glibc 2.33 support. TODO upstream
changes.

binutils is not fixed, as upstream changes are still being discussed.
Instead we have worked around objcopy/strip in debhelper to call those
tools from dh_strip in a safe manner.

We also rebuilt binutils against glibc 2.32, to avoid this new
behaviour. However, we need to resolve bintuils in a better way, one way
or another.

** Description changed:

+ fakeroot with glibc broke dpkg-deb for packages that do not use "Rules-
+ Requires-Root: no" was broken.
+ 
+ binutils stopped preserving permissions from objcopy & strip, leading to
+ incorrect permissions of files after stripping.
+ 
+ fakeroot is now patched with better glibc 2.33 support. TODO upstream
+ changes.
+ 
+ binutils is not fixed, as upstream changes are still being discussed.
+ Instead we have worked around objcopy/strip in debhelper to call those
+ tools from dh_strip in a safe manner.
+ 
+ We also rebuilt binutils against glibc 2.32, to avoid this new
+ behaviour. However, we need to resolve bintuils in a better way, one way
+ or another.
+ 
+ 
+ --
+ 
  the current state of -proposed creates deb packages with buildd file
  owner/group for shared libraries.
  
  reported at least for kwayland-integration.
  
  $ dpkg -c kwayland-integration_5.20.90-0ubuntu1_amd64.deb|grep \.so
  -rw-r--r-- doko/doko 18984 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/kmodifierkey_wayland.so
  -rw-r--r-- doko/doko 85392 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kwindowsystem/KF5WindowSystemKWaylandPlugin.so
  -rw-r--r-- doko/doko 35536 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeKWaylandPlugin.so
  
-  - in a release pocket, rebuild binutils from proposed. correctly
-restores the file ownership
+  - in a release pocket, rebuild binutils from proposed. correctly
+    restores the file ownership
  
-  - in a release pocket, update glibc from proposed. then rebuild
-binutils from proposed. shows the wrong ownership
+  - in a release pocket, update glibc from proposed. then rebuild
+    binutils from proposed. shows the wrong ownership

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

Title:
  buildd file owner/group for shared libraries

Status in binutils package in Ubuntu:
  Confirmed
Status in debhelper package in Ubuntu:
  Confirmed
Status in fakeroot package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in debhelper package in Debian:
  Unknown

Bug description:
  fakeroot with glibc broke dpkg-deb for packages that do not use
  "Rules-Requires-Root: no" was broken.

  binutils stopped preserving permissions from objcopy & strip, leading
  to incorrect permissions of files after stripping.

  fakeroot is now patched with better glibc 2.33 support. TODO upstream
  changes.

  binutils is not fixed, as upstream changes are still being discussed.
  Instead we have worked around objcopy/strip in debhelper to call those
  tools from dh_strip in a safe manner.

  We also rebuilt binutils against glibc 2.32, to avoid this new
  behaviour. However, we need to resolve bintuils in a better way, one
  way or another.

  
  --

  the current state of -proposed creates deb packages with buildd file
  owner/group for shared libraries.

  reported at least for kwayland-integration.

  $ dpkg -c kwayland-integration_5.20.90-0ubuntu1_amd64.deb|grep \.so
  -rw-r--r-- doko/doko 18984 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/kmodifierkey_wayland.so
  -rw-r--r-- doko/doko 85392 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kwindowsystem/KF5WindowSystemKWaylandPlugin.so
  -rw-r--r-- doko/doko 35536 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeKWaylandPlugin.so

   - in a release pocket, rebuild binutils from proposed. correctly
     restores the file ownership

   - in a release pocket, update glibc from proposed. then rebuild
     binutils from proposed. shows the wrong ownership

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1915250/+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 1915906] Re: Ensure SRP BN_mod_exp follows the constant time path

[Alex Murray]

** Information type changed from Public to Public Security

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

Title:
  Ensure SRP BN_mod_exp follows the constant time path

Status in openssl package in Ubuntu:
  New

Bug description:
  Hello,

  I'd like to point out that there are two fixes missing from the
  upstream, is there any chance to get them incorporated?

  https://github.com/openssl/openssl/pull/13888
  https://github.com/openssl/openssl/pull/13889

  There was no CVE assigned, it was fixed between 1.1.1i and 1.1.1j.

  Best regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1915906/+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 1915908] Re: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status

[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 openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1915908

Title:
  package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  sh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
   Active: activating (auto-restart) (Result: exit-code) since Wed 
2021-02-17 15:42:28 IST; 11ms ago
 Docs: man:sshd(8)
   man:sshd_config(5)
  Process: 24813 ExecStartPre=/usr/sbin/sshd -t (code=exited, 
status=255/EXCEPTION)
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Processing triggers for systemd (245.4-4ubuntu3.4) ...
  Processing triggers for man-db (2.9.1-1) ...
  Processing triggers for ufw (0.36-6) ...
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: openssh-server 1:8.2p1-4ubuntu0.1
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  AptOrdering:
   openssh-server:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb 17 15:42:28 2021
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-01-05 (42 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.5, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: /etc/ssh/sshd_config line 1: garbage at end of line; "to".
  SourcePackage: openssh
  Title: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2021-02-04 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1915908/+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 1915908] [NEW] package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit statu

[Chetas D L]

Public bug reported:

sh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: activating (auto-restart) (Result: exit-code) since Wed 2021-02-17 
15:42:28 IST; 11ms ago
   Docs: man:sshd(8)
 man:sshd_config(5)
Process: 24813 ExecStartPre=/usr/sbin/sshd -t (code=exited, 
status=255/EXCEPTION)
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess returned 
error exit status 1
Processing triggers for systemd (245.4-4ubuntu3.4) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for ufw (0.36-6) ...
Errors were encountered while processing:
 openssh-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: openssh-server 1:8.2p1-4ubuntu0.1
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
AptOrdering:
 openssh-server:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Feb 17 15:42:28 2021
ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2021-01-05 (42 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.5, python-is-python3, 3.8.2-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config line 1: garbage at end of line; "to".
SourcePackage: openssh
Title: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to focal on 2021-02-04 (12 days ago)

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

Title:
  package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  sh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
   Active: activating (auto-restart) (Result: exit-code) since Wed 
2021-02-17 15:42:28 IST; 11ms ago
 Docs: man:sshd(8)
   man:sshd_config(5)
  Process: 24813 ExecStartPre=/usr/sbin/sshd -t (code=exited, 
status=255/EXCEPTION)
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Processing triggers for systemd (245.4-4ubuntu3.4) ...
  Processing triggers for man-db (2.9.1-1) ...
  Processing triggers for ufw (0.36-6) ...
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: openssh-server 1:8.2p1-4ubuntu0.1
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  AptOrdering:
   openssh-server:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb 17 15:42:28 2021
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-01-05 (42 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.5, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: /etc/ssh/sshd_config line 1: garbage at end of line; "to".
  SourcePackage: openssh
  Title: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2021-02-04 (12 days ago)

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

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

[Touch-packages] [Bug 1073138] Re: Unattended-Upgrade::Allowed-Origins should be replaced by Unattended-Upgrade::Origins-Pattern

[Robert Euhus]

Please change this config for the next ubuntu release!

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

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

Title:
  Unattended-Upgrade::Allowed-Origins should be replaced by Unattended-
  Upgrade::Origins-Pattern

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  According to /usr/bin/unattended-upgrade, the Allowed-Origins variable
  is a legacy variable, so presumbly unattended-upgrades should be using
  its replacement, Origins-Pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unattended-upgrades 0.79.3ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Tue Oct 30 12:34:06 2012
  InstallationDate: Installed on 2011-05-24 (524 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to quantal on 2012-10-19 (10 days ago)
  modified.conffile..etc.apt.apt.conf.d.50unattended.upgrades: [modified]
  mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 
2012-10-30T12:33:25.981698

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1073138/+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 1073138] Re: Unattended-Upgrade::Allowed-Origins should be replaced by Unattended-Upgrade::Origins-Pattern

[Robert Euhus]

Hi all, especially Michael Vogt,

while I can understand that You don't want do change the config during a
release, I can not see any  reason why it is still not changed for *new
releases* of ubuntu. The bug report is 8 years old by now. There is no
advantage of keeping "Allowed-Origin", but many problems have been
pointed out. One more: i think it's impossible to configure "just
upgrade everything without asking".

So please change this config for the next ubuntu release!

Thanks and regards,
Robert

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

Title:
  Unattended-Upgrade::Allowed-Origins should be replaced by Unattended-
  Upgrade::Origins-Pattern

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  According to /usr/bin/unattended-upgrade, the Allowed-Origins variable
  is a legacy variable, so presumbly unattended-upgrades should be using
  its replacement, Origins-Pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unattended-upgrades 0.79.3ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Tue Oct 30 12:34:06 2012
  InstallationDate: Installed on 2011-05-24 (524 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to quantal on 2012-10-19 (10 days ago)
  modified.conffile..etc.apt.apt.conf.d.50unattended.upgrades: [modified]
  mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 
2012-10-30T12:33:25.981698

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1073138/+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 1915906] [NEW] Ensure SRP BN_mod_exp follows the constant time path

[Viacheslav]

Public bug reported:

Hello,

I'd like to point out that there are two fixes missing from the
upstream, is there any chance to get them incorporated?

https://github.com/openssl/openssl/pull/13888
https://github.com/openssl/openssl/pull/13889

There was no CVE assigned, it was fixed between 1.1.1i and 1.1.1j.

Best regards

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

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

Title:
  Ensure SRP BN_mod_exp follows the constant time path

Status in openssl package in Ubuntu:
  New

Bug description:
  Hello,

  I'd like to point out that there are two fixes missing from the
  upstream, is there any chance to get them incorporated?

  https://github.com/openssl/openssl/pull/13888
  https://github.com/openssl/openssl/pull/13889

  There was no CVE assigned, it was fixed between 1.1.1i and 1.1.1j.

  Best regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1915906/+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 1766108] Re: Battery indicator crashes when unchecking "Show Percentage in Menu Bar"

[Sai Vinoba]

This bug seems to be fixed in 21.04. I am not seeing it anymore on
21.04.

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

Title:
  Battery indicator crashes when unchecking "Show Percentage in Menu
  Bar"

Status in Ubuntu MATE:
  New
Status in ayatana-indicator-power package in Ubuntu:
  Confirmed
Status in indicator-power package in Ubuntu:
  Confirmed
Status in mate-indicator-applet package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

  1. Click on the battery indicator.
  2. Click "Show Percentage on Menu Bar" to enable it.
  3. Do it again to disable it.
  4. Battery indicator disappears

  
  Output from dmesg:

  [  613.877855] mate-panel[1604]: segfault at 1c ip 7f51b23daa20 sp 
7ffe8df7f5d8 error 4 in libcairo.so.2.11510.0[7f51b236c000+118000]
  [  749.662960] mate-panel[2930]: segfault at 38 ip 7fc98aa82300 sp 
7fffa5290f68 error 4 in libgdk-3.so.0.2200.30[7fc98aa3b000+eb000]
  [  775.815530] mate-panel[3127]: segfault at 1c ip 7fc317b61a20 sp 
7ffea6e1f028 error 4 in libcairo.so.2.11510.0[7fc317af3000+118000]
  [  816.504199] mate-panel[3225]: segfault at 38 ip 7fa314f0e300 sp 
7fffa993f928 error 4 in libgdk-3.so.0.2200.30[7fa314ec7000+eb000]
  [  841.353444] mate-panel[3363]: segfault at 38 ip 7fbc86c4a300 sp 
7ffd6b3a5d58 error 4 in libgdk-3.so.0.2200.30[7fbc86c03000+eb000]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1766108/+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 1874723] Re: MATE battery icon disappears when deselect "Show Time in Menu Bar"

[Sai Vinoba]

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

This bug seems to be fixed in 21.04. Not failing anymore for me (on
21.04).

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

Title:
  MATE battery icon disappears when deselect "Show Time in Menu Bar"

Status in Ubuntu MATE:
  Confirmed
Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  In the new Ubuntu MATE 20.04, with the default installation, right
  clicking on the battery icon in the upper right on the panel, and
  select either (or both) "Show Time in Menu Bar" or "Show Percentage in
  Menu Bar". Then, deselect the option, and the entire battery icon (not
  just the time or percentage) disappears from the tray/panel and can
  not be replaced. Or, I can not figure out how to replace it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1874723/+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 1874723] Re: MATE battery icon disappears when deselect "Show Time in Menu Bar"

[Sai Vinoba]

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

** This bug has been marked a duplicate of bug 1766108
   Battery indicator crashes when unchecking "Show Percentage in Menu Bar"

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

Title:
  MATE battery icon disappears when deselect "Show Time in Menu Bar"

Status in Ubuntu MATE:
  Confirmed
Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  In the new Ubuntu MATE 20.04, with the default installation, right
  clicking on the battery icon in the upper right on the panel, and
  select either (or both) "Show Time in Menu Bar" or "Show Percentage in
  Menu Bar". Then, deselect the option, and the entire battery icon (not
  just the time or percentage) disappears from the tray/panel and can
  not be replaced. Or, I can not figure out how to replace it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1874723/+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 1915903] [NEW] Up-to-date net-tools package tells me to recompile it

[Richard Brooksby]

Public bug reported:

Attempting to run

  netstat -f inet

results in

  netstat: feature `AF BLUETOOTH' not supported.
  Please recompile `net-tools' with newer kernel source or full configuration.

Both my net-tools and kernel packages are fully up-to-date.  (Version
details are in the report collected by ubuntu-bug.)

This looks to me like a package inconsistency.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: net-tools 1.60+git20161116.90da8a0-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18
Uname: Linux 4.15.0-135-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
Date: Wed Feb 17 09:02:39 2021
Dependencies:
 gcc-8-base 8.4.0-1ubuntu1~18.04
 libc6 2.27-3ubuntu1.4
 libgcc1 1:8.4.0-1ubuntu1~18.04
 libpcre3 2:8.39-9
 libselinux1 2.7-2build2
InstallationDate: Installed on 2017-12-02 (1172 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: net-tools
UpgradeStatus: Upgraded to bionic on 2018-09-04 (896 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Up-to-date net-tools package tells me to recompile it

Status in net-tools package in Ubuntu:
  New

Bug description:
  Attempting to run

netstat -f inet

  results in

netstat: feature `AF BLUETOOTH' not supported.
Please recompile `net-tools' with newer kernel source or full configuration.

  Both my net-tools and kernel packages are fully up-to-date.  (Version
  details are in the report collected by ubuntu-bug.)

  This looks to me like a package inconsistency.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: net-tools 1.60+git20161116.90da8a0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18
  Uname: Linux 4.15.0-135-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  Date: Wed Feb 17 09:02:39 2021
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1.4
   libgcc1 1:8.4.0-1ubuntu1~18.04
   libpcre3 2:8.39-9
   libselinux1 2.7-2build2
  InstallationDate: Installed on 2017-12-02 (1172 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: net-tools
  UpgradeStatus: Upgraded to bionic on 2018-09-04 (896 days ago)

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