[Touch-packages] [Bug 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns

[Iain Lane]

I've removed the update from bionic-security and bionic-updates, and
restored the versions which were previously in there.

This won't help anyone that has already received the broken update - I
think the advice there is to restart, or there is a workaround in the OP
here - but it should prevent any further occurrences.

Note that there will be a delay of up to an hour or so for mirrors to
receive the deletion.

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

Title:
  Update to systemd 237-3ubuntu10.54 broke dns

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Two servers today that updated systemd to "systemd 237-3ubuntu10.54" 
  https://ubuntu.com/security/notices/USN-5583-1

  could not resolve dns anymore.
  no dns servers, normally set through dhcp.

  Ubuntu 18.04

  Temp fix.
   1. Edit /etc/systemd/resolved.conf
   1. Add/Uncomment # FallbackDNS=168.63.129.16
   1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service
   1. Confirm dns working with systemd-resolve google.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1928001] [NEW] [SRU] New stable release 2.68.1

[Iain Lane]

Public bug reported:

[ Description ]

Take this new upstream stable release.

* Fix a crash in `GKeyFile` when parsing a file which contains translations
  using a `GKeyFile` instance which has loaded another file previously (#2361)

* Pin GIO DLL in memory on Windows (!2016)

* Bugs fixed:
 - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines
 - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to 
glib-2-68
 - !2016 GIO W32: Pin gio DLL
 - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68
 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier
 - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68
 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple 
lines” to glib-2-68

[ QA ]

Upstream release, so QA already performed by maintainers

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

This upload will trigger many autopkgtests that we expect to not be
regressed by this upload.

[ What could go wrong ]

This update contains fixes in multiple places so multiple apps could be
affected. The consequences of a broken GLib can range from some
functions returning bad results sometimes, which have minimal runtime
implications, up to the system simply crashing all the time.

Pretty much all parts of GNOME use GLib, so test anything in the desktop
that you can. If you reboot the machine and can get to the desktop,
that's already tested GLib extensively. But also run applications like
GNOME terminal, Files and Epiphany.

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: glib2.0 (Ubuntu Hirsute)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Also affects: glib2.0 (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

** Changed in: glib2.0 (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Hirsute)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  [SRU] New stable release 2.68.1

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Hirsute:
  In Progress

Bug description:
  [ Description ]

  Take this new upstream stable release.

  * Fix a crash in `GKeyFile` when parsing a file which contains translations
using a `GKeyFile` instance which has loaded another file previously (#2361)

  * Pin GIO DLL in memory on Windows (!2016)

  * Bugs fixed:
   - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines
   - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to 
glib-2-68
   - !2016 GIO W32: Pin gio DLL
   - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68
   - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier
   - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68
   - !2035 Backport !2026 “Split g_test_log() messages that contain multiple 
lines” to glib-2-68

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ What could go wrong ]

  This update contains fixes in multiple places so multiple apps could
  be affected. The consequences of a broken GLib can range from some
  functions returning bad results sometimes, which have minimal runtime
  implications, up to the system simply crashing all the time.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can. If you reboot the machine and can get to the
  desktop, that's already tested GLib extensively. But also run
  applications like GNOME terminal, Files and Epiphany.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+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 1926843] Re: online accounts integration with fb isn't working

[Iain Lane]

I retried libgdata and it works now

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

Title:
  online accounts integration with fb isn't working

Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Hirsute:
  Fix Committed

Bug description:
  * Impact

  The online accounts setting are proposing a facebook item which isn't
  working

  * Test case

  Go to settings -> online account, browse the accounts option proposed,
  facebook shouldn't be in the list since it doesn't work.

  * Regression potential

  The change is to disable the facebook provider using the upstream
  provided build option. Check that facebook isn't listed anymore but
  that the other providers still are. Since it's a build option change
  it could fail to build so check for that as well on launchpad.

  Since the facebook service currently doesn't consider gnome-online-
  accounts as a valid client there should be no user with that provider
  configured. Even if there were since the service isn't working they
  would see a functional regression.

  ---

  Hi i tryed to use gnome-control-center online-accounts to make easy
  like windows 10 to login to email or add other login so its more easy
  with ID to use pincode or other ID fingerprint and other.

  But its look its much issue compared with windows 10 with thunderbird,
  firefox, and other program.

  Worst is facebook only little windows with issue with login?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-online-accounts 3.38.1-1ubuntu1
  Uname: Linux 5.12.0-051200-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  1 19:38:03 2021
  InstallationDate: Installed on 2019-05-07 (725 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1928001] Re: [SRU] New stable release 2.68.1

[Iain Lane]

automake-1.16> same started happening in impish too - you could cherry-
pick 2b8b44ffc37047231757780952f6290398fb73e2 to the hints maybe?

netplan.io> slyon told me this is known bad and is skipped in other
releases already (upstream) and will be included in the next SRU to
hirsute, if any. could be hinted too?

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

Title:
  [SRU] New stable release 2.68.1

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Hirsute:
  Fix Committed

Bug description:
  [ Description ]

  Take this new upstream stable release.

  * Fix a crash in `GKeyFile` when parsing a file which contains translations
using a `GKeyFile` instance which has loaded another file previously (#2361)

  * Pin GIO DLL in memory on Windows (!2016)

  * Bugs fixed:
   - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines
   - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to 
glib-2-68
   - !2016 GIO W32: Pin gio DLL
   - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68
   - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier
   - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68
   - !2035 Backport !2026 “Split g_test_log() messages that contain multiple 
lines” to glib-2-68

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ What could go wrong ]

  This update contains fixes in multiple places so multiple apps could
  be affected. The consequences of a broken GLib can range from some
  functions returning bad results sometimes, which have minimal runtime
  implications, up to the system simply crashing all the time.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can. If you reboot the machine and can get to the
  desktop, that's already tested GLib extensively. But also run
  applications like GNOME terminal, Files and Epiphany.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+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 1928931] [NEW] German strings in deja-dup.mo for en_GB

[Iain Lane]

Public bug reported:

[ Description ]

Some German strings were accidentally translated under en_GB. They
affect the default Ubuntu install - some of them are strings which are
displayed as a notification some time after first logging in, so it's
quite visible. See the attached screenshot.

[ Fix ]

Revert the German and go back to the proper English text. The way to fix
langpacks is to upload the language-pack-gnome-XX package which replaces
files in language-pack-gnome-XX-base.

[ Devel release ]

I'd like to propose to binary copy forward, and let the normal langpack
release schedule take care of eventually dominating these away in
impish.

[ QA ]

To verify the diff, compare deja-dup.po from language-pack-gnome-en-base
to the one in this upload. You'll have to do that manually.

  0. Be in en_GB.
  1. Install the SRU
  2. In an Ubuntu Desktop session, open a terminal and run `deja-dup --prompt`.
  3. Note the buttons in the notification that shows up. They should be in 
English.

[ What could go wrong ]

1. There could be other instances of this in different packages we haven't 
noticed yet
2. If I break the .po file, it could either break the build or the translations 
at runtime (but this is English, so if we fall back to C it's not too bad)
3. If my diff is wrong then I might have dropped some en_GB translations or 
made them wrong

** Affects: language-pack-gnome-en (Ubuntu)
 Importance: Undecided
 Status: In Progress

** Affects: language-pack-gnome-en (Ubuntu Hirsute)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Attachment added: "Screenshot from 2021-05-19 09-51-59.png"
   
https://bugs.launchpad.net/bugs/1928931/+attachment/5498717/+files/Screenshot%20from%202021-05-19%2009-51-59.png

** Also affects: language-pack-gnome-en-base (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: language-pack-gnome-en-base (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: language-pack-gnome-en-base (Ubuntu Hirsute)
     Assignee: (unassigned) => Iain Lane (laney)

** Changed in: language-pack-gnome-en-base (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: language-pack-gnome-en-base (Ubuntu)
   Status: New => In Progress

** Description changed:

  [ Description ]
  
  Some German strings were accidentally translated under en_GB. They
  affect the default Ubuntu install - some of them are strings which are
  displayed as a notification some time after first logging in, so it's
  quite visible. See the attached screenshot.
  
  [ Fix ]
  
  Revert the German and go back to the proper English text. The way to fix
  langpacks is to upload the language-pack-gnome-XX package which replaces
  files in language-pack-gnome-XX-base.
  
  [ Devel release ]
  
  I'd like to propose to binary copy forward, and let the normal langpack
  release schedule take care of eventually dominating these away in
  impish.
  
  [ QA ]
  
  To verify the diff, compare deja-dup.po from language-pack-gnome-en-base
  to the one in this upload. You'll have to do that manually.
  
-   0. Be in en_GB.
-   1. Install the SRU
-   2. In an Ubuntu Desktop session, open a terminal and run `deja-dup 
--prompt`.
-   3. Note the buttons in the notification that shows up. They should be in 
English.
+   0. Be in en_GB.
+   1. Install the SRU
+   2. In an Ubuntu Desktop session, open a terminal and run `deja-dup 
--prompt`.
+   3. Note the buttons in the notification that shows up. They should be in 
English.
  
  [ What could go wrong ]
  
- 1. I could have missed some strings, and so there might still be some Deutsch 
around
- 2. There could be other instances of this in different packages we haven't 
noticed yet
- 3. If I break the .po file, it could either break the build or the 
translations at runtime (but this is English, so if we fall back to C it's not 
too bad)
+ 1. There could be other instances of this in different packages we haven't 
noticed yet
+ 2. If I break the .po file, it could either break the build or the 
translations at runtime (but this is English, so if we fall back to C it's not 
too bad)

** Description changed:

  [ Description ]
  
  Some German strings were accidentally translated under en_GB. They
  affect the default Ubuntu install - some of them are strings which are
  displayed as a notification some time after first logging in, so it's
  quite visible. See the attached screenshot.
  
  [ Fix ]
  
  Revert the German and go back to the proper English text. The way to fix
  langpacks is to upload the language-pack-gnome-XX package which replaces
  files in language-pack-gnome-XX-base.
  
  [ Devel release ]
  
  I'd like to propose to binary copy forward, and let the normal langpack
  release schedule take care of eventually dominating these away in
  impish.
  
  [ QA ]
  
  To verify the diff, c

[Touch-packages] [Bug 1928001] Re: [SRU] New stable release 2.68.1

[Iain Lane]

I ran the applications listed in the description against
2.68.1-1~ubuntu21.04.1. I also generally exercised the desktop for a
while and didn't notice anything odd.

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

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

Title:
  [SRU] New stable release 2.68.1

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Hirsute:
  Fix Committed

Bug description:
  [ Description ]

  Take this new upstream stable release.

  * Fix a crash in `GKeyFile` when parsing a file which contains translations
using a `GKeyFile` instance which has loaded another file previously (#2361)

  * Pin GIO DLL in memory on Windows (!2016)

  * Bugs fixed:
   - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines
   - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to 
glib-2-68
   - !2016 GIO W32: Pin gio DLL
   - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68
   - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier
   - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68
   - !2035 Backport !2026 “Split g_test_log() messages that contain multiple 
lines” to glib-2-68

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ What could go wrong ]

  This update contains fixes in multiple places so multiple apps could
  be affected. The consequences of a broken GLib can range from some
  functions returning bad results sometimes, which have minimal runtime
  implications, up to the system simply crashing all the time.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can. If you reboot the machine and can get to the
  desktop, that's already tested GLib extensively. But also run
  applications like GNOME terminal, Files and Epiphany.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+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 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)

[Iain Lane]

Just to put the information on the bug, I reproduced this failure on a
Raspberry Pi, not a piece of the Scalingstack infrastructure in sight
;-)

As far as I can tell it looked as if it's timing out waiting for
network-online.target to become active. It seems as if installing
network-manager makes the target take way longer to activate, so long
that it is over autopkgtest's timeout. I suppose this isn't expected, so
maybe the next step is to look into why that happens?

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

Title:
  boot-and-services tests fails in impish on armhf (248.3)

Status in Auto Package Testing:
  New
Status in dnsmasq package in Ubuntu:
  Incomplete
Status in gdm3 package in Ubuntu:
  Incomplete
Status in glibc package in Ubuntu:
  Incomplete
Status in isc-dhcp package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf
  before now slipping into a bad mode.

  Now it seems all tests failed in boot-and-services by hanging until killed by
  VirtSubproc.Timeout of autokgtest.

  The last [1] test log has a bit more, it shows a python stack overflow
  ```
 VirtSubproc.Timeout
 Fatal Python error: Cannot recover from stack overflow.
 Python runtime state: initialized

 Current thread 0x7f108e840740 (most recent call first):
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command
  ```

  I have seen a bunch of packages including even gdm3 and glibc being blocked by
  that so I wanted to at least track down the issue until we can put it on
  someones task list to resolve.
  No one replied to my pings yet, but maybe that means someone is already
  debugging this and had enabled some debugging?

  By running the same in armhf container on arm64 VM on canonistack I've seen
  no issues. The test worked fine and had no hang/issues.

  root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services
  lxc
  1
  test_profile (__main__.AppArmorTest)
  AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352'
  test_help (__main__.CLITest)
  --help works and succeeds ... ok
  test_invalid_option (__main__.CLITest)
  Calling with invalid option fails ... ok
  test_version (__main__.CLITest)
  --version works and succeeds ... ok
  test_cpushares (__main__.CgroupsTest)
  service with CPUShares ... ok
  test_simple (__main__.CgroupsTest)
  simple service ... ok
  test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does 
not work in containers'
  test_log_for_service (__main__.JournalTest) ... ok
  test_no_options (__main__.JournalTest) ... ok
  test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
  test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
  test_failing (__main__.SeccompTest) ... ok
  test_0_init (__main__.ServicesTest)
  Verify that init is systemd ... ok
  test_cron (__main__.ServicesTest) ... ok
  test_dbus (__main__.ServicesTest) ... ok
  test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found'
  test_logind (__main__.ServicesTest) ... ok
  test_network_manager (__main__.ServicesTest) ... ok
  test_no_failed (__main__.ServicesTest)
  No failed units ... ok
  test_rsyslog (__main__.ServicesTest) ... ok
  test_tmp_cleanup (__main__.ServicesTest) ... ok
  test_tmp_mount (__main__.ServicesTest) ... ok
  test_udev (__main__.ServicesTest) ... skipped 'udev does not work in 
containers'
  --
  Ran 23 tests in 5.589s
  OK (skipped=6)

  So I can not reproduce this on canonistack, but it blocks autopkgtests of
  various packages pretty reproducibly :-/

  [1]: https://autopkgtest.ubuntu.com/results/autopkgtest-
  impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Iain Lane]

That's interesting actually. I thought this was an interaction between
reloading dbus-daemon and daemon-reloading systems at the same time. But
in this cloud case, I don't think dbus is being reloaded, is it?

It's going to be next to impossible for me to look into this in detail
without being able to reproduce it or getting a bit more debug
information.

Maybe you could crank up the system log level and try to reproduce this?

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel thermald[1256]: [WA

[Touch-packages] [Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)

[Iain Lane]

I have added a badtest hint for this version, so that the many packages
blocked by this can become unblocked. But could somebody please take a
look? The hint is only for this version so the issue will come back with
the next systemd upload unless fixed.

(I'll reset systemd to  "New" so that it appears on the rls-incoming
page)

** Tags added: rls-ii-incoming

** Changed in: auto-package-testing
   Status: New => Incomplete

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

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

Title:
  boot-and-services tests fails in impish on armhf (248.3)

Status in Auto Package Testing:
  Incomplete
Status in dnsmasq package in Ubuntu:
  Incomplete
Status in gdm3 package in Ubuntu:
  Incomplete
Status in glibc package in Ubuntu:
  Incomplete
Status in isc-dhcp package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf
  before now slipping into a bad mode.

  Now it seems all tests failed in boot-and-services by hanging until killed by
  VirtSubproc.Timeout of autokgtest.

  The last [1] test log has a bit more, it shows a python stack overflow
  ```
 VirtSubproc.Timeout
 Fatal Python error: Cannot recover from stack overflow.
 Python runtime state: initialized

 Current thread 0x7f108e840740 (most recent call first):
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command
  ```

  I have seen a bunch of packages including even gdm3 and glibc being blocked by
  that so I wanted to at least track down the issue until we can put it on
  someones task list to resolve.
  No one replied to my pings yet, but maybe that means someone is already
  debugging this and had enabled some debugging?

  By running the same in armhf container on arm64 VM on canonistack I've seen
  no issues. The test worked fine and had no hang/issues.

  root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services
  lxc
  1
  test_profile (__main__.AppArmorTest)
  AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352'
  test_help (__main__.CLITest)
  --help works and succeeds ... ok
  test_invalid_option (__main__.CLITest)
  Calling with invalid option fails ... ok
  test_version (__main__.CLITest)
  --version works and succeeds ... ok
  test_cpushares (__main__.CgroupsTest)
  service with CPUShares ... ok
  test_simple (__main__.CgroupsTest)
  simple service ... ok
  test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does 
not work in containers'
  test_log_for_service (__main__.JournalTest) ... ok
  test_no_options (__main__.JournalTest) ... ok
  test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
  test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
  test_failing (__main__.SeccompTest) ... ok
  test_0_init (__main__.ServicesTest)
  Verify that init is systemd ... ok
  test_cron (__main__.ServicesTest) ... ok
  test_dbus (__main__.ServicesTest) ... ok
  test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found'
  test_logind (__main__.ServicesTest) ... ok
  test_network_manager (__main__.ServicesTest) ... ok
  test_no_failed (__main__.ServicesTest)
  No failed units ... ok
  test_rsyslog (__main__.ServicesTest) ... ok
  test_tmp_cleanup (__main__.ServicesTest) ... ok
  test_tmp_mount (__main__.ServicesTest) ... ok
  test_udev (__main__.ServicesTest) ... skipped 'udev does not work in 
containers'
  --
  Ran 23 tests in 5.589s
  OK (skipped=6)

  So I can not reproduce this on canonistack, but it blocks autopkgtests of
  various packages pretty reproducibly :-/

  [1]: https://autopkgtest.ubuntu.com/results/autopkgtest-
  impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Iain Lane]

Thanks! Here's where I think the problem starts:

Ok, let's authenticate to dbus:

Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus 
bus-api-system: changing state AUTHENTICATING → HELLO
...
Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus 
bus-api-system: changing state HELLO → RUNNING

Right, systemd thinks it's done it at least. You can see a whole bunch
of messages being returned, the connection is working.

After a while (note this first timestamp jump; is that significant?
looks to be waiting for udev to settle I think so maybe not; could be
snapd related) we decide to do something with a Type=dbus unit:

Jun 16 08:55:25 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Sent message 
type=method_call sender=n/a destination=org.freedesktop.DBus 
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch 
cookie=1511 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Jun 16 08:55:25 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Sent message 
type=method_call sender=n/a destination=org.freedesktop.DBus 
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetNameOwner 
cookie=1512 reply_cookie=0 signature=s error-name=n/a error-message=n/a

And another timestamp jump, waiting for this timeout:

Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo dbus-daemon[711]: 
[system] Connection has not authenticated soon enough, closing it 
(auth_timeout=3ms, elapsed: 45129ms)
Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Got message 
type=method_return sender=org.freedesktop.DBus destination=:1.4 path=n/a 
interface=n/a member=n/a cookie=42 reply_cookie=1512 signature=s error-name=n/a 
error-message=n/a

The dbus-daemon didn't think that the connection was authenticated.

The last message AFAICS received on the bus connection was:

Jun 16 08:55:00 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Got message 
type=method_call sender=n/a destination=org.freedesktop.systemd1 
path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager 
member=Reload cookie=1 reply_cookie=0 signature=n/a error-name=n/a 
error-message=n/a
Jun 16 08:55:00 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Reloading.

No smoking gun yet, at least not to me. But interesting that the last
thing which happened successfully was reloading. Can we have another go
please, with these changes vs. an upstream clean image?

  - LogLevel=debug in /etc/systemd/system.conf
  - Using the dbus 1.12.20-2ubuntu1+ppa1 from ppa:ci-train-ppa-service/4587. 
This dbus is just the one from impish backported to hirsute with verbose 
debugging turned on.
  
And then attach the full `journalctl -b ` which will 
probably be quite large. :-)

Maybe we'll get some information out of the dbus side to say what it
thinks goes wrong with the connection.

** Please note ** The "connection has not authenticated" string does not
appear in the earlier logs from Christian or Steve. It could be that
there are two bugs here, with similar symptoms that systemd loses its
connection to the system bus.

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid
Status in accountsservice source package in Groovy:
  New
Status in dbus source package in Groovy:
  New
Status in gnome-shell source package in Groovy:
  New
Status in accountsservice source package in Hirsute:
  New
Status in dbus source package in Hirsute:
  New
Status in gnome-shell source package in Hirsute:
  New
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Incomplete
Status in gnome-shell source package in Impish:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
 

[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Iain Lane]

I filed an upstream bug with D-Bus:
https://gitlab.freedesktop.org/dbus/dbus/-/issues/337

Hopefully a maintainer there will be able to give a better opinion as to
what's going on here

** Bug watch added: gitlab.freedesktop.org/dbus/dbus/-/issues #337
   https://gitlab.freedesktop.org/dbus/dbus/-/issues/337

** Also affects: dbus via
   https://gitlab.freedesktop.org/dbus/dbus/-/issues/337
   Importance: Unknown
   Status: Unknown

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid
Status in accountsservice source package in Groovy:
  New
Status in dbus source package in Groovy:
  New
Status in gnome-shell source package in Groovy:
  New
Status in accountsservice source package in Hirsute:
  New
Status in dbus source package in Hirsute:
  New
Status in gnome-shell source package in Hirsute:
  New
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Incomplete
Status in gnome-shell source package in Impish:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal

Re: [Touch-packages] [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default

[Iain Lane]

On Mon, Jun 21, 2021 at 05:53:41AM -, Christian Ehrhardt  wrote:
> We finally got an answer to our questions/pings (thanks Simon)
> => 
> https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2021q2/015134.html
> 
> TL;DR: this might be wanted new behavior :/ ?!
> 
> @Laney - You initially started this when we have faced this bug
> I wonder now if we should indeed drop our delta and resolve the fallout in 
> other places like the formerly breaking tests.
> You have back then thought deeper into this, while I only carried this delta 
> a few times.
> Therefore I'd appreciate if you could let me know what you think of that 
> reply.
> 
> P.S. Because if we drop it then I guess we better do that now than e.g.
> late in 22.04 :-)

I don't know to be honest. What do you think, does that argument make 
sense? I don't really understand why it should be different whether 
you're using DHCPv6 or SLAAC, but maybe it's just me not getting 
something right now.

If it's fine, then feel free to drop the patch and upload a NM with 
adjusted regexes (preferrably committing to the VCS too).

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  [2.82 regression] router announcements have 'forever' lifetime by
  default

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq package in Debian:
  New

Bug description:
  The default lifetime was changed to 1 day in 2.82 in the change
  corresponding to this changelog entry:

  Change default lease time for DHCPv6 to one day.

  Fine, but the same commit also did this:

Alter calculation of preferred and valid times in router
advertisements, so that these do not have a floor applied
of the lease time in the dhcp-range if this is not explicitly
specified and is merely the default.

  And that change is buggy and causes advertisements to have infinite
  lifetime, when you are using the default.

  See this thread

http://lists.thekelleys.org.uk/pipermail/dnsmasq-
  discuss/2020q3/014341.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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 1928931] Re: German strings in deja-dup.mo for en_GB

[Iain Lane]

> hm, do we actually know *why* this happened?

Yes, someone mis-translated the strings on Launchpad. I reverted them
all now, but I don't think we have any way of dealing with that
happening again, do we?

I've just verified the SRU. I installed language-pack-gnome-en
1:21.10+20210415ubuntu1 and ran deja-dup --prompt. With the SRU the
buttons are in English again!

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

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

Title:
  German strings in deja-dup.mo for en_GB

Status in language-pack-gnome-en package in Ubuntu:
  In Progress
Status in language-pack-gnome-en source package in Hirsute:
  Fix Committed

Bug description:
  [ Description ]

  Some German strings were accidentally translated under en_GB. They
  affect the default Ubuntu install - some of them are strings which are
  displayed as a notification some time after first logging in, so it's
  quite visible. See the attached screenshot.

  [ Fix ]

  Revert the German and go back to the proper English text. The way to
  fix langpacks is to upload the language-pack-gnome-XX package which
  replaces files in language-pack-gnome-XX-base.

  [ Devel release ]

  I'd like to propose to binary copy forward, and let the normal
  langpack release schedule take care of eventually dominating these
  away in impish.

  [ QA ]

  To verify the diff, compare deja-dup.po from language-pack-gnome-en-
  base to the one in this upload. You'll have to do that manually.

    0. Be in en_GB.
    1. Install the SRU
    2. In an Ubuntu Desktop session, open a terminal and run `deja-dup 
--prompt`.
    3. Note the buttons in the notification that shows up. They should be in 
English.

  [ What could go wrong ]

  1. There could be other instances of this in different packages we haven't 
noticed yet
  2. If I break the .po file, it could either break the build or the 
translations at runtime (but this is English, so if we fall back to C it's not 
too bad)
  3. If my diff is wrong then I might have dropped some en_GB translations or 
made them wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en/+bug/1928931/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Iain Lane]

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

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

** Changed in: gnome-shell (Ubuntu Groovy)
   Status: New => Invalid

** Changed in: gnome-shell (Ubuntu Hirsute)
   Status: New => Invalid

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

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

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Incomplete
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Incomplete
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Incomplete
Status in gnome-shell source package in Impish:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log fil

[Touch-packages] [Bug 1932311] Re: migrate to llvm 12

[Iain Lane]

** Changed in: mesa (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu Hirsute)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  migrate to llvm 12

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  New
Status in mesa source package in Hirsute:
  New

Bug description:
  (split off from bug 1917763)

  [Impact]

  Mesa should migrate to llvm 12 for new AMDGPU features and HW support.
  Normally this would be done during the devel series, but this version
  was delayed too much to migrate before hirsute was out.

  [Fix]
  Build-depend on the new packages, including libclc which is now built from 
llvm sources.

  [Test case]

  Test AMD graphics and/or qemu desktop (llvmpipe) after installing
  migrated packages.

  [Regression potential]

  This has been in Impish for a month now without issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1932311/+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 1918855] Re: Xorg xserver got signal 6 to abort

[Iain Lane]

** Changed in: mesa (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu Hirsute)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Xorg xserver got signal 6 to abort

Status in Mesa:
  Unknown
Status in OEM Priority Project:
  In Progress
Status in Provider for Plainbox - Checkbox:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  New
Status in mesa source package in Hirsute:
  New

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may 
crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if 
kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session 
is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory 
pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on 
focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1918855/+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 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

[Iain Lane]

** Changed in: evolution-data-server (Ubuntu Hirsute)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Tags removed: rls-hh-incoming

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

Title:
  Recent iCloud versions trigger an issue in IMAP x

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

Bug description:
  * Impact

  The Icloud service introduced changes that are confusing evolution-
  data-server which means evolution is now failing to connect to the
  email server

  * Test case

  Set up an iCloud account and try to use it for emails in evolution

  * Regression potential

  The change is in the imapx connection code, it could create problems
  with other type of servers so we should try to test on different
  providers.

  
  -


  The bug has been fixed yesterday by Evolution's developer:
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1468

  However, the package in Ubuntu (at least in Focal Fosa) still needs to
  be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore

[Iain Lane]

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

** Also affects: gnome-weather (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: gnome-weather (Ubuntu)
   Status: Confirmed => Fix Released

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

** Changed in: gnome-weather (Ubuntu Focal)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: libgweather (Ubuntu Focal)
 Assignee: (unassigned) => Iain Lane (laney)

** Tags removed: rls-ff-incoming

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

Title:
  (Update libgweather to 3.36.2) Weather forecast and info is not
  available anymore

Status in libgweather:
  Unknown
Status in gnome-weather package in Ubuntu:
  Fix Released
Status in libgweather package in Ubuntu:
  Fix Released
Status in gnome-weather source package in Focal:
  New
Status in libgweather source package in Focal:
  New
Status in gnome-weather package in Fedora:
  New

Bug description:
  [Impact]

  The weather forecast is not available since one week now. Also, the
  weather info is gone from gnome-shell.

  The weather service provider retired their old API.
  
https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/

  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS

  ==
  Version 3.36.2
  ==

  This version switches the yr.no backend to use met.no instead. Please note
  that this backport is only meant as a compatibility layer. Where at all
  possible, the newer libgweather 40 should be used as applications cannot
  fully comply with the met.no ToS otherwise.

  
  [Test case]

  - gnome-weather shows the weather forecast
  - gnome-shell shows the weather forecast in the calendar menu

  
  [Regression potential]

  - Weather forecast is totally broken now and can't be more broken.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  7 09:54:52 2021
  InstallationDate: Installed on 2020-04-26 (314 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1918044/+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 1928931] Re: German strings in deja-dup.mo for en_GB

[Iain Lane]

Wait, isn't the version wrong? 1:21.10+20210415ubuntu1.

I'm going to re-upload to the queue with 1:21.04.

Also, can we just run a langpack export for impish to fix this there
please? The version is greater than hirsute's now so I can't just copy
up.

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

Title:
  German strings in deja-dup.mo for en_GB

Status in language-pack-gnome-en package in Ubuntu:
  In Progress
Status in language-pack-gnome-en source package in Hirsute:
  Fix Committed

Bug description:
  [ Description ]

  Some German strings were accidentally translated under en_GB. They
  affect the default Ubuntu install - some of them are strings which are
  displayed as a notification some time after first logging in, so it's
  quite visible. See the attached screenshot.

  [ Fix ]

  Revert the German and go back to the proper English text. The way to
  fix langpacks is to upload the language-pack-gnome-XX package which
  replaces files in language-pack-gnome-XX-base.

  [ Devel release ]

  I'd like to propose to binary copy forward, and let the normal
  langpack release schedule take care of eventually dominating these
  away in impish.

  [ QA ]

  To verify the diff, compare deja-dup.po from language-pack-gnome-en-
  base to the one in this upload. You'll have to do that manually.

    0. Be in en_GB.
    1. Install the SRU
    2. In an Ubuntu Desktop session, open a terminal and run `deja-dup 
--prompt`.
    3. Note the buttons in the notification that shows up. They should be in 
English.

  [ What could go wrong ]

  1. There could be other instances of this in different packages we haven't 
noticed yet
  2. If I break the .po file, it could either break the build or the 
translations at runtime (but this is English, so if we fall back to C it's not 
too bad)
  3. If my diff is wrong then I might have dropped some en_GB translations or 
made them wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en/+bug/1928931/+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 1928931] Re: German strings in deja-dup.mo for en_GB

[Iain Lane]

Okay, done. I think: remove this, let the removal publish, accept the
new one.

Hopefully the ageing period can be waived on that.

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

Title:
  German strings in deja-dup.mo for en_GB

Status in language-pack-gnome-en package in Ubuntu:
  In Progress
Status in language-pack-gnome-en source package in Hirsute:
  Fix Committed

Bug description:
  [ Description ]

  Some German strings were accidentally translated under en_GB. They
  affect the default Ubuntu install - some of them are strings which are
  displayed as a notification some time after first logging in, so it's
  quite visible. See the attached screenshot.

  [ Fix ]

  Revert the German and go back to the proper English text. The way to
  fix langpacks is to upload the language-pack-gnome-XX package which
  replaces files in language-pack-gnome-XX-base.

  [ Devel release ]

  I'd like to propose to binary copy forward, and let the normal
  langpack release schedule take care of eventually dominating these
  away in impish.

  [ QA ]

  To verify the diff, compare deja-dup.po from language-pack-gnome-en-
  base to the one in this upload. You'll have to do that manually.

    0. Be in en_GB.
    1. Install the SRU
    2. In an Ubuntu Desktop session, open a terminal and run `deja-dup 
--prompt`.
    3. Note the buttons in the notification that shows up. They should be in 
English.

  [ What could go wrong ]

  1. There could be other instances of this in different packages we haven't 
noticed yet
  2. If I break the .po file, it could either break the build or the 
translations at runtime (but this is English, so if we fall back to C it's not 
too bad)
  3. If my diff is wrong then I might have dropped some en_GB translations or 
made them wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en/+bug/1928931/+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 1928931] Re: German strings in deja-dup.mo for en_GB

[Iain Lane]

Hmm no, it needs removing first, my upload got rejected.

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

Title:
  German strings in deja-dup.mo for en_GB

Status in language-pack-gnome-en package in Ubuntu:
  In Progress
Status in language-pack-gnome-en source package in Hirsute:
  Fix Committed

Bug description:
  [ Description ]

  Some German strings were accidentally translated under en_GB. They
  affect the default Ubuntu install - some of them are strings which are
  displayed as a notification some time after first logging in, so it's
  quite visible. See the attached screenshot.

  [ Fix ]

  Revert the German and go back to the proper English text. The way to
  fix langpacks is to upload the language-pack-gnome-XX package which
  replaces files in language-pack-gnome-XX-base.

  [ Devel release ]

  I'd like to propose to binary copy forward, and let the normal
  langpack release schedule take care of eventually dominating these
  away in impish.

  [ QA ]

  To verify the diff, compare deja-dup.po from language-pack-gnome-en-
  base to the one in this upload. You'll have to do that manually.

    0. Be in en_GB.
    1. Install the SRU
    2. In an Ubuntu Desktop session, open a terminal and run `deja-dup 
--prompt`.
    3. Note the buttons in the notification that shows up. They should be in 
English.

  [ What could go wrong ]

  1. There could be other instances of this in different packages we haven't 
noticed yet
  2. If I break the .po file, it could either break the build or the 
translations at runtime (but this is English, so if we fall back to C it's not 
too bad)
  3. If my diff is wrong then I might have dropped some en_GB translations or 
made them wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en/+bug/1928931/+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

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

[Iain Lane]

On Thu, Feb 11, 2021 at 01:49:45PM -, Balint Reczey wrote:
> There is not much to do about the failures on systemd's side. The tests
> are reliably passing in qemu on my i5-4670 testbed from 2013, also
> passing on @paelzer's presumably newer machine.
> 
> This is an infra issue. The Release Team can decide if they want to hint
> the test and lose gating coverage, but I'm not filing the hint because
> IMO the test infra should be fixed.

Is there chance we can be a little bit more constructive? We're not 
warring factions here.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

-- 
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:
  New
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

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

[Iain Lane]

I'm running a test on Canonistack. I'm hoping that this will reproduce
the failures we're seeing, and then they can be investigated.

That is closer to what is running in production than the QEMU runner.

I don't think we have evidence that this is an 'infra issue', so I'm
marking the auto-package-testing task as incomplete.

Will follow back up probably tomorrow once that test is finished.

** Changed in: auto-package-testing
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/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

[Iain Lane]

Ok, here you go. I reproduced the (or a) failure in Canonistack. This
was the first run FWIW, so it wasn't too hard to get it to fail:

autopkgtest [14:05:12]: test systemd-fsckd: [---
test_fsck_failure (__main__.FsckdTest)
Ensure that a failing fsck doesn't prevent fsckd to stop ... bash: line 1:  
1250 Killed  
/tmp/autopkgtest.5SlVJo/build.mmt/src/debian/tests/systemd-fsckd 2> >(tee -a 
/tmp/autopkgtest.5SlVJo/systemd-fsckd-stderr >&2) > >(tee -a 
/tmp/autopkgtest.5SlVJo/systemd-fsckd-stdout)
autopkgtest [14:05:16]: test process requested reboot with marker 
test_fsck_failure
autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds...
test_fsck_failure (__main__.FsckdTest)
Ensure that a failing fsck doesn't prevent fsckd to stop ... FAIL

==
FAIL: test_fsck_failure (__main__.FsckdTest)
Ensure that a failing fsck doesn't prevent fsckd to stop
--
Traceback (most recent call last):
  File "/tmp/autopkgtest.5SlVJo/build.mmt/src/debian/tests/systemd-fsckd", line 
190, in test_fsck_failure
self.check_plymouth_start()
  File "/tmp/autopkgtest.5SlVJo/build.mmt/src/debian/tests/systemd-fsckd", line 
158, in check_plymouth_start
self.assertUnitStarted(unit)
  File "/tmp/autopkgtest.5SlVJo/build.mmt/src/debian/tests/systemd-fsckd", line 
228, in assertUnitStarted
self.assertTrue(has_unit_started(unit))
AssertionError: False is not true

--
Ran 1 test in 11.289s

FAILED (failures=1)
autopkgtest [14:06:11]: test systemd-fsckd: ---]
autopkgtest [14:06:12]: test systemd-fsckd:  - - - - - - - - - - results - - - 
- - - - - - -
systemd-fsckdFAIL non-zero exit status 1
autopkgtest [14:06:13]:  summary
timedatedPASS
hostnamedPASS
localed-locale   PASS
localed-x11-keymap   PASS
logind   PASS
unit-config  PASS
storage  PASS
networkd-test.py PASS
build-login  PASS
boot-and-servicesPASS
udev PASS
root-unittests   PASS
tests-in-lxd PASS
upstream PASS
boot-smoke   PASS
systemd-fsckdFAIL non-zero exit status 1

Full logs attached. The commandline is at the top of the log - is that
enough for you to be able to have a go, Balint? I suggest adding
--shell-fail of course so you can break in once it happens.

** Attachment added: "systemd-canonistack-cpu4-ram8-disk50.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915126/+attachment/5463223/+files/systemd-canonistack-cpu4-ram8-disk50.tar.xz

-- 
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.BTBTT

[Touch-packages] [Bug 1915784] Re: Permissions of executables pointing to "buildd"

[Iain Lane]

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

hi, thanks, the team are already tracking this in bug #1915250 and said
they are working on fixing everything

** This bug has been marked a duplicate of bug 1915250
   buildd file owner/group for shared libraries

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

Title:
  Permissions of executables pointing to "buildd"

Status in apport package in Ubuntu:
  New
Status in ccache package in Ubuntu:
  New
Status in fuse3 package in Ubuntu:
  New
Status in lzma package in Ubuntu:
  New
Status in netstat-nat package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  New
Status in pipewire package in Ubuntu:
  New
Status in psensor package in Ubuntu:
  New
Status in screen package in Ubuntu:
  New
Status in snap package in Ubuntu:
  New
Status in sudo package in Ubuntu:
  New
Status in wireshark package in Ubuntu:
  New
Status in xz-utils package in Ubuntu:
  New

Bug description:
  I've noticed this issue already with other applications, which have been 
updated recently, too.
  This morning I've updated the sudo package and it broke, too.

  The common issue is that fakeroot gets omitted or faulty in your build
  environment somehow.

  After looking into the current sudo package I've noticed that all
  files are owned by "buildd:buildd", which doesn't exist on my computer
  and thus the 2001:2501 on my local machine.

  I'll try to collect some other packages, too, which have the same
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: sudo 1.9.5p2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu58
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Feb 16 08:33:27 2021
  InstallationDate: Installed on 2020-01-27 (385 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

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

[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 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context

[Iain Lane]

I'm going to close this bug in the 2.67.5-1 upload which I'm just making
to experimental. There will still be "some" projects still affected, but
it's as fixed as it's going to get from glib2.0's side - we made the API
break opt in for packages that have followed glib's longstanding advice
and defined the MAX_ALLOWED/MIN_REQUIRED macros.

Affected projects can do either (but should do both) of these.

  - Define GLIB_VERSION_MAX_ALLOWED to something below GLIB_VERISON_2_66 to opt 
out or _2_68 to opt in to this new typesafe behaviour.
  - Not include glib's headers in an 'extern "C"' context. GLib has 
G_{BEGIN,END}_DECLS that might help with this.

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

** Changed in: glib2.0 (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  glib2.0 >=2.67.3 breaks include from an extern C context

Status in glib2.0 package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Triaged
Status in ukui-control-center package in Ubuntu:
  New

Bug description:
  qemu now breaks in Hirsute (it didn't 23h ago)
  Broken:
  
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz

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

  Error:

  ../../disas/arm-a64.cc
  In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
   from 
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
   from /usr/include/glib-2.0/glib/gtypes.h:32,
   from /usr/include/glib-2.0/glib/galloca.h:32,
   from /usr/include/glib-2.0/glib.h:30,
   from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
   from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
   from ../../disas/arm-a64.cc:21:
  /usr/include/c++/10/type_traits:56:3: error: template with C linkage
     56 |   template
    |   ^~~~
  ../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
     20 | extern "C" {
    | ^~

  Also in disas/nanomips.cpp, ...

  And indeed disas/arm-a64.cc has:
   20 extern "C" {
   21 #include "qemu/osdep.h"
   22 #include "disas/dis-asm.h"
   23 }

  Through the chain of headers as reported above this gets to the templates
  in /usr/include/c++/10/type_traits which fails due to that.

  So C++ constructs within a C scope which is this bug.

  Upstream qemu has not recently changed yet for this.
  The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
  Include osdep.h first" by Peter Maydell.

  But what was different before to break it now?
  To find that I was comparing Hirsute vs Hirsute-proposed ...

  It is indeed failing in -proposed but working in hirsute-release.

  10.2.1-20ubuntu1 : bad

  repro in broken build:
  $ cd /root/qemu-5.2+dfsg/b/qemu
  $ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader 
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16 
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr 
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall 
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef 
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2 
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits 
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body 
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs 
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem 
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote 
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote 
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote 
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED 
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ 
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d 
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp

  With that I have a test env...

  Doko asked me to test
  
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-1

[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)

[Iain Lane]

** Changed in: glib2.0 (Ubuntu)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => Iain Lane (laney)

-- 
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:
  Fix Committed

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 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context

[Iain Lane]

> Also open-vm-tools is also FTBFS by this, so I need to add a task and
work on that as well.

You want this kind of thing minimally to get over the FTBFS:

--- open-vm-tools-11.2.5.orig/open-vm-tools/configure.ac
+++ open-vm-tools-11.2.5/open-vm-tools/configure.ac
@@ -503,6 +503,9 @@ AC_CHECK_PROG([have_genmarshal],
   [yes],
   [no])
 
+AC_DEFINE(GLIB_VERSION_MIN_REQUIRED, GLIB_VERSION_2_34, [Ignore post 2.34 
deprecations])
+AC_DEFINE(GLIB_VERSION_MAX_ALLOWED, GLIB_VERSION_2_34, [Prevent post 2.34 
APIs])
+
 if test "$have_genmarshal" != "yes"; then
AC_MSG_ERROR([glib-genmarshal is required; make sure it is available in 
your path.])
 fi

But I would recommend also at least asking upstream to do the full fix
and move glib's headers out of 'extern "C"' too as outlined in comment
#2 here.

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

Title:
  glib2.0 >=2.67.3 breaks include from an extern C context

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in open-vm-tools package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Fix Released
Status in ukui-control-center package in Ubuntu:
  Triaged

Bug description:
  qemu now breaks in Hirsute (it didn't 23h ago)
  Broken:
  
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz

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

  Error:

  ../../disas/arm-a64.cc
  In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
   from 
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
   from /usr/include/glib-2.0/glib/gtypes.h:32,
   from /usr/include/glib-2.0/glib/galloca.h:32,
   from /usr/include/glib-2.0/glib.h:30,
   from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
   from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
   from ../../disas/arm-a64.cc:21:
  /usr/include/c++/10/type_traits:56:3: error: template with C linkage
     56 |   template
    |   ^~~~
  ../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
     20 | extern "C" {
    | ^~

  Also in disas/nanomips.cpp, ...

  And indeed disas/arm-a64.cc has:
   20 extern "C" {
   21 #include "qemu/osdep.h"
   22 #include "disas/dis-asm.h"
   23 }

  Through the chain of headers as reported above this gets to the templates
  in /usr/include/c++/10/type_traits which fails due to that.

  So C++ constructs within a C scope which is this bug.

  Upstream qemu has not recently changed yet for this.
  The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
  Include osdep.h first" by Peter Maydell.

  But what was different before to break it now?
  To find that I was comparing Hirsute vs Hirsute-proposed ...

  It is indeed failing in -proposed but working in hirsute-release.

  10.2.1-20ubuntu1 : bad

  repro in broken build:
  $ cd /root/qemu-5.2+dfsg/b/qemu
  $ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader 
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16 
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr 
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall 
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef 
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2 
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits 
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body 
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs 
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem 
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote 
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote 
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote 
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED 
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ 
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d 
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp

  With that I have a test env...

  Doko asked me to test
  
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb
  That f

[Touch-packages] [Bug 1917763] Re: FFE: new upstream release 21.0 and migrate to llvm 12

[Iain Lane]

ACK, go for it (with 11 for now, I agree that switching to an RC
compiler feels dodgy)

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

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

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

Title:
  FFE: new upstream release 21.0 and migrate to llvm 12

Status in mesa package in Ubuntu:
  Triaged

Bug description:
  Mesa 21.0.0 will be released soon, and we still want it in 21.04. It's
  been in Debian experimental since rc1. The packaging also migrates it
  to use llvm 12.

  The risks involve graphical issues or even crashes when running more
  intense OpenGL/Vulkan apps like games. Running a desktop is a simple
  use-case and should work fine across the board. Upstream gitlab has a
  fairly extensive CI for various drivers, while Intel tests on their
  own CI. This means that any showstoppers should be shaken out already.

  We will be able to pull maybe two point-releases before hirsute is
  frozen, and then push more as an SRU.

  I've tested 21.0.0-rc's on Intel and AMD (RX 5700) and the latter too
  with some games, all good.

  packages for hirsute are available on ppa:canonical-x/x-staging

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

[Iain Lane]

Julian, thanks for the fix. In crontab(5) in cron 3.0pl1-136ubuntu2 the manpage
is now wrong. It says:

> Several environment variables are set up automatically by the cron(8) daemon.
> […] PATH is set to "/usr/bin:/bin". HOME, SHELL, and PATH may be overridden
> by settings in the crontab […]

and also

> On the Debian GNU/Linux system, cron supports the pam_env module, and loads
> the environment specified by /etc/environment and /etc/security/pam_env.conf.
> It also reads locale information from /etc/default/locale.  However, the PAM
> settings do NOT override the settings described above nor any settings in the
> crontab file itself.  Note in particular that if you want a PATH other than
> "/usr/bin:/bin", you will need to set it in the crontab file.

These should be fixed I think. There might be other spots that I didn't notice
yet too.

Secondly, as there are now tasks for stable releases, I think the SRU team
needs to be made aware of the implications of SRUing this change. It means that
the default PATH (if not overridden) will be different after applying the
update.  There's a chance that users will then have different copies of
programs found resulting in their cron scripts potentially experiencing
behaviour changes. The benefits of consistency may outweigh the
risks/drawbacks of this behaviour change, but I think it should be considered
carefully when SRUing.

-- 
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:
  Fix Committed
Status in cron package in Ubuntu:
  Fix Committed
Status in anacron source package in Bionic:
  Confirmed
Status in cron source package in Bionic:
  Confirmed
Status in anacron source package in Focal:
  Confirmed
Status in cron source package in Focal:
  Confirmed
Status in anacron source package in Groovy:
  Confirmed
Status in cron source package in Groovy:
  Confirmed
Status in anacron source package in Hirsute:
  Fix Committed
Status in cron source package in Hirsute:
  Fix Committed

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 1920601] Re: Frequent test failures caused by networking issues on armhf runners

[Iain Lane]

I think both things would be fine. It's better to not surface these
problems to end users if we can, which we have a mechanism to do.

If and when apt gets a fix which works, then these retries will
automatically stop happening and we can remove the workarounds.

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

Title:
  Frequent test failures caused by networking issues on armhf runners

Status in Auto Package Testing:
  Triaged
Status in apt package in Ubuntu:
  New

Bug description:
  Armhf runners have been known to have networking issues for years.

  A test of Focal's glibc SRU in Bileto shows that those issues did not
  go away. The glibc package itself is not expected to cause regression,
  this was just a run to confirm that.

  The test resuts are shown here:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-4017-excuses/2021-03-20_09:25:01/4017_focal_excuses.html

  Out of the 114 failed tests 58 containst the 'Connection timed out'
  string and only test logs from armhf contain that string:

  $ zgrep -l 'Connection timed out' ~/.cache/ubuntu-archive-tools/focal_*.gz 
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_atk1.0_20210318_182825_daefa.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_axe-demultiplexer_20210318_183430_6b008.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_bacula_20210318_190411_e3ad7.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_dialign-t_20210318_204503_b4d94.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_elisa-player_20210318_211129_9537d.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_fyba_20210318_181755_7731e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-7_20210318_02_4d95c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-8_20210318_221659_0e69f.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_golang-github-mailru-easyjson_20210318_231917_67888.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gphoto2_20210318_200015_eb767.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gtk+3.0_20210318_235412_db3e5.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_ipmitool_20210319_003215_d03da.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kbibtex_20210319_004639_0ac1a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kcptun_20210318_193309_6dcd9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libcache-memcached-getparserxs-perl_20210319_024051_33029.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libclass-load-xs-perl_20210319_025846_01419.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libconvert-uulib-perl_20210319_034852_21cd1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhat-trie_20210319_060826_fd334.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhtml-tidy5-perl_20210319_070723_05fa8.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libimager-perl_20210319_063314_b19a2.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libipc-sharelite-perl_20210319_072246_0217e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_liblexical-var-perl_20210319_070235_4c450.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmarpa-r2-perl_20210319_073731_f7554.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmemcached-libmemcached-perl_20210319_011004_dbca1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-ldns-perl_20210319_081224_49912.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-pcap-perl_20210319_081606_4d772.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libparams-util-perl_20210319_084831_74d13.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-eol-perl_20210319_085645_97c6c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-layers-perl_20210319_085937_8bd70.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsass_20210319_092518_4db37.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsdl-perl_20210319_095502_00c8c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-bibtex-perl_20210319_105027_abf4a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-hunspell-perl_20210319_103326_4a603.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libunix-syslog-perl_20210319_111403_f4374.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libwx-scintilla-perl_20210319_114818_a6aab.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libzstd_20210319_114737_0c4d9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mod-gearman_20210319_132205_d41ca.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mrbayes_20210319_133633_10adb.gz
  
/home/rbalint/.cache/ub

[Touch-packages] [Bug 1920601] Re: Frequent test failures caused by networking issues on armhf runners

[Iain Lane]

Neat, can someone prepare a merge proposal for that?

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

Title:
  Frequent test failures caused by networking issues on armhf runners

Status in Auto Package Testing:
  Triaged
Status in apt package in Ubuntu:
  New

Bug description:
  Armhf runners have been known to have networking issues for years.

  A test of Focal's glibc SRU in Bileto shows that those issues did not
  go away. The glibc package itself is not expected to cause regression,
  this was just a run to confirm that.

  The test resuts are shown here:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-4017-excuses/2021-03-20_09:25:01/4017_focal_excuses.html

  Out of the 114 failed tests 58 containst the 'Connection timed out'
  string and only test logs from armhf contain that string:

  $ zgrep -l 'Connection timed out' ~/.cache/ubuntu-archive-tools/focal_*.gz 
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_atk1.0_20210318_182825_daefa.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_axe-demultiplexer_20210318_183430_6b008.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_bacula_20210318_190411_e3ad7.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_dialign-t_20210318_204503_b4d94.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_elisa-player_20210318_211129_9537d.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_fyba_20210318_181755_7731e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-7_20210318_02_4d95c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-8_20210318_221659_0e69f.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_golang-github-mailru-easyjson_20210318_231917_67888.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gphoto2_20210318_200015_eb767.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gtk+3.0_20210318_235412_db3e5.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_ipmitool_20210319_003215_d03da.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kbibtex_20210319_004639_0ac1a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kcptun_20210318_193309_6dcd9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libcache-memcached-getparserxs-perl_20210319_024051_33029.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libclass-load-xs-perl_20210319_025846_01419.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libconvert-uulib-perl_20210319_034852_21cd1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhat-trie_20210319_060826_fd334.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhtml-tidy5-perl_20210319_070723_05fa8.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libimager-perl_20210319_063314_b19a2.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libipc-sharelite-perl_20210319_072246_0217e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_liblexical-var-perl_20210319_070235_4c450.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmarpa-r2-perl_20210319_073731_f7554.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmemcached-libmemcached-perl_20210319_011004_dbca1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-ldns-perl_20210319_081224_49912.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-pcap-perl_20210319_081606_4d772.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libparams-util-perl_20210319_084831_74d13.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-eol-perl_20210319_085645_97c6c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-layers-perl_20210319_085937_8bd70.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsass_20210319_092518_4db37.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsdl-perl_20210319_095502_00c8c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-bibtex-perl_20210319_105027_abf4a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-hunspell-perl_20210319_103326_4a603.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libunix-syslog-perl_20210319_111403_f4374.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libwx-scintilla-perl_20210319_114818_a6aab.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libzstd_20210319_114737_0c4d9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mod-gearman_20210319_132205_d41ca.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mrbayes_20210319_133633_10adb.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_octave-interval_20210319_151509_8348f.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_open-isns_20210319_161741_dffad.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/f

[Touch-packages] [Bug 1922681] [NEW] manpages are wrong about PATH inheriting from the environment now

[Iain Lane]

Public bug reported:

I posted this on bug #1779767 but since that got closed it's probably
going to be lost there.

tl;dr the manpage(s) needs to be fixed for this change as well:

Julian, thanks for the fix. In crontab(5) in cron 3.0pl1-136ubuntu2 the
manpage is now wrong. It says:

> Several environment variables are set up automatically by the cron(8)
daemon. […] PATH is set to "/usr/bin:/bin". HOME, SHELL, and PATH may be
overridden by settings in the crontab […]

and also

> On the Debian GNU/Linux system, cron supports the pam_env module, and
loads the environment specified by /etc/environment and
/etc/security/pam_env.conf. It also reads locale information from
/etc/default/locale. However, the PAM settings do NOT override the
settings described above nor any settings in the crontab file itself.
Note in particular that if you want a PATH other than  "/usr/bin:/bin",
you will need to set it in the crontab file.

These should be fixed I think. There might be other spots that I didn't
notice yet too.

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


** Tags: rls-hh-incoming

** Description changed:

  I posted this on bug #1779767 but since that got closed it's probably
  going to be lost there.
  
  tl;dr the manpage(s) needs to be fixed for this change as well:
  
- Julian, thanks for the fix. In crontab(5) in cron 3.0pl1-136ubuntu2 the 
manpage
- is now wrong. It says:
+ Julian, thanks for the fix. In crontab(5) in cron 3.0pl1-136ubuntu2 the
+ manpage is now wrong. It says:
  
  > Several environment variables are set up automatically by the cron(8)
  daemon. […] PATH is set to "/usr/bin:/bin". HOME, SHELL, and PATH may be
  overridden by settings in the crontab […]
  
  and also
  
  > On the Debian GNU/Linux system, cron supports the pam_env module, and
  loads the environment specified by /etc/environment and
  /etc/security/pam_env.conf. It also reads locale information from
  /etc/default/locale. However, the PAM settings do NOT override the
  settings described above nor any settings in the crontab file itself.
  Note in particular that if you want a PATH other than  "/usr/bin:/bin",
  you will need to set it in the crontab file.
  
  These should be fixed I think. There might be other spots that I didn't
  notice yet too.

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

Title:
  manpages are wrong about PATH inheriting from the environment now

Status in cron package in Ubuntu:
  New

Bug description:
  I posted this on bug #1779767 but since that got closed it's probably
  going to be lost there.

  tl;dr the manpage(s) needs to be fixed for this change as well:

  Julian, thanks for the fix. In crontab(5) in cron 3.0pl1-136ubuntu2
  the manpage is now wrong. It says:

  > Several environment variables are set up automatically by the
  cron(8) daemon. […] PATH is set to "/usr/bin:/bin". HOME, SHELL, and
  PATH may be overridden by settings in the crontab […]

  and also

  > On the Debian GNU/Linux system, cron supports the pam_env module,
  and loads the environment specified by /etc/environment and
  /etc/security/pam_env.conf. It also reads locale information from
  /etc/default/locale. However, the PAM settings do NOT override the
  settings described above nor any settings in the crontab file itself.
  Note in particular that if you want a PATH other than
  "/usr/bin:/bin", you will need to set it in the crontab file.

  These should be fixed I think. There might be other spots that I
  didn't notice yet too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1922681/+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 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

[Iain Lane]

This came up on our tracking report for the desktop team, but we're not
clear what is required in libxcb/amdgpu vs. a fix in the WMs themselves.
Can someone clarify please?

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

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

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

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Focal)
   Status: New => Incomplete

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Groovy)
   Status: New => Incomplete

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in Linux:
  Unknown
Status in libxcb package in Ubuntu:
  Incomplete
Status in xfwm4 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete
Status in libxcb source package in Focal:
  Incomplete
Status in xfwm4 source package in Focal:
  In Progress
Status in xserver-xorg-video-amdgpu source package in Focal:
  Incomplete
Status in libxcb source package in Groovy:
  Incomplete
Status in xfwm4 source package in Groovy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Groovy:
  Incomplete

Bug description:
  [Impact]

   * This issue affects AMD graphics on Xfwm4 4.14.1.

   * Windows are displayed staggered with a multi-window layout

  [Test Plan]

   * Use AMD graphics drivers

   * Connect a second display at a different resolution

   * Open multiple windows

   * While the issue is present, the windows and desktop will appeared
  staggered

   * Once fixed, they display normally.

  [Where problems could occur]

   * Regression potential should be relatively low, as the release
  between 4.14.1 and 4.14.5 are bug releases.

   * With window managers, some changes could lead to different behavior
  and other broken displays. Non-AMD graphics users should also test for
  regressions.

  [Other Info]
   
   * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: 
https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44

  [Original Report]

  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-gener

[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

[Iain Lane]

assigning to timo for better tracking

** Changed in: mesa (Ubuntu Hirsute)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

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

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Incomplete
Status in mesa source package in Hirsute:
  Confirmed
Status in ubiquity source package in Hirsute:
  Incomplete

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  Cases where the crash can be triggered:

  - Using a Virtualbox VM, where graphics acceleration is handled by mesa with 
LLVMPIPE
  - Start the ISO on real hardware in 'safe graphics mode'

  Cases where the crash is not encountered:
  - Start the ISO on real intel (HD graphics) hardware with full acceleration.

  NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to
  the previous 20.3.4 in hirsute.

  Try/Install crash:

  Screen fails to start, or starts then crashes on any user action. The
  user is presented with:

  "Installation failed - The installer encountered an unrecoverable error.
  A desktop session will now be run so that you may investigate the problem or 
try installing again"

  Live session crash:

  The installer does not start from the desktop icon. Starting ubiquity
  from the terminal results in an "Aborted (core dumped)" message and
  nothing else.

  The crash is most commonly "malloc(): unaligned tcache chunk
  detected", but inevitably from this sort of memory issue can be
  something like "realloc(): invalid next size"

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+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 1821415] Re: pkexec fails in a non-graphical environment

[Iain Lane]

I don't think we would want to carry the proposed patch as a distro
patch. So as long as polkit doesn't have direct support for this, apport
should do as systemd does, and spawn pkttyagent (--fallback) itself.

I'll try quickly now to work on an initial patch for this.

** Changed in: policykit-1 (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in apport package in Ubuntu:
  Triaged
Status in policykit-1 package in Ubuntu:
  Won't Fix

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  N.B. you first need to create a /var/log/plymouth-debug.log file for
  the plymouth apport package hook to actually trigger this.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1821415] Re: pkexec fails in a non-graphical environment

[Iain Lane]

See the attached branch, it's a fix for this in apport.

** Branch linked: lp:~laney/apport/pkttyagent

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in apport package in Ubuntu:
  Triaged
Status in policykit-1 package in Ubuntu:
  Won't Fix

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  N.B. you first need to create a /var/log/plymouth-debug.log file for
  the plymouth apport package hook to actually trigger this.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1821415] Re: pkexec fails in a non-graphical environment

[Iain Lane]

(but I asked for some input there from an apport maintainer, it could be
better than I did it)

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in apport package in Ubuntu:
  Triaged
Status in policykit-1 package in Ubuntu:
  Won't Fix

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  N.B. you first need to create a /var/log/plymouth-debug.log file for
  the plymouth apport package hook to actually trigger this.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1907433] [NEW] [SRU] New stable release 2.64.6

[Iain Lane]

Public bug reported:

[ Description ]

Take this new upstrem stable release.

Overview of changes in GLib 2.64.6
==

* This is expected to be the last release in the 2.64 series; the new stable
  series is 2.66, and maintenance efforts will shift to that

* Bugs fixed:
 - #2194 gtk3/glib crash on gimp
 - #2209 gthreadedresolver: faulty logic in parse_res_txt
 - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64
 - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64
 - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to 
glib-2-64
 - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64
 - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not 
succeeding” to glib-2-64
 - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too 
far in the past” to glib-2-64

* Translation updates:
 - Croatian
 - Portuguese


Overview of changes in GLib 2.64.5
==

* Fix deadlock in `g_subprocess_communicate_async()` (work by Alexander
Larsson) (#2182)

* Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868)

* Bugs fixed:
 - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual 
Studio” to glib-2-64
 - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64
 - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked 
URI list” to glib-2-64
 - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to glib-2-64
 - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never blocks” 
to glib-2-64
 - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to glib-2-64


Overview of changes in GLib 2.64.4
==

* Bugs fixed:
 - #2140 calling malloc in fork child is undefined-behaviour
 - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to 
return” to glib-2-64
 - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64
 - !1547 Backport !1544 “Resolve "calling malloc in fork child is 
undefined-behaviour"” to glib-2-64

* Translation updates:
 - Kazakh
 - Slovenian

[ QA ]

Upstream release, so QA already performed by maintainers

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

This upload will trigger many autopkgtests that we expect to not be
regressed by this upload.

[ Regression potential ]

Various fixes in multiple places so multiple apps could be affected.
Pretty much all parts of GNOME use GLib, so test anything in the desktop
that you can. If you reboot the machine and can get to the desktop,
that's already tested GLib extensively. But also run applications like
GNOME terminal, Files and Epiphany.

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: glib2.0 (Ubuntu Focal)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Also affects: glib2.0 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: glib2.0 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Focal)
 Assignee: (unassigned) => Iain Lane (laney)

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

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

Title:
  [SRU] New stable release 2.64.6

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  In Progress

Bug description:
  [ Description ]

  Take this new upstrem stable release.

  Overview of changes in GLib 2.64.6
  ==

  * This is expected to be the last release in the 2.64 series; the new stable
series is 2.66, and maintenance efforts will shift to that

  * Bugs fixed:
   - #2194 gtk3/glib crash on gimp
   - #2209 gthreadedresolver: faulty logic in parse_res_txt
   - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64
   - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64
   - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to 
glib-2-64
   - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64
   - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not 
succeeding” to glib-2-64
   - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too 
far in the past” to glib-2-64

  * Translation updates:
   - Croatian
   - Portuguese

  
  Overview of changes in GLib 2.64.5
  ==

  * Fix deadlock in `g_subprocess_communicate_async()` (work by
  Alexander Larsson) (#2182)

  * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868)

  * Bugs fixed:
   - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual 
Studio” to glib-2

[Touch-packages] [Bug 1907433] Re: [SRU] New stable release 2.64.6

[Iain Lane]

** Description changed:

  [ Description ]
  
  Take this new upstrem stable release.
  
  Overview of changes in GLib 2.64.6
  ==
  
  * This is expected to be the last release in the 2.64 series; the new stable
-   series is 2.66, and maintenance efforts will shift to that
+   series is 2.66, and maintenance efforts will shift to that
  
  * Bugs fixed:
-  - #2194 gtk3/glib crash on gimp
-  - #2209 gthreadedresolver: faulty logic in parse_res_txt
-  - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64
-  - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64
-  - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to 
glib-2-64
-  - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64
-  - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not 
succeeding” to glib-2-64
-  - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too 
far in the past” to glib-2-64
+  - #2194 gtk3/glib crash on gimp
+  - #2209 gthreadedresolver: faulty logic in parse_res_txt
+  - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64
+  - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64
+  - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to 
glib-2-64
+  - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64
+  - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not 
succeeding” to glib-2-64
+  - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too 
far in the past” to glib-2-64
  
  * Translation updates:
-  - Croatian
-  - Portuguese
- 
+  - Croatian
+  - Portuguese
  
  Overview of changes in GLib 2.64.5
  ==
  
  * Fix deadlock in `g_subprocess_communicate_async()` (work by Alexander
  Larsson) (#2182)
  
  * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868)
  
  * Bugs fixed:
-  - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual 
Studio” to glib-2-64
-  - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64
-  - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked 
URI list” to glib-2-64
-  - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to 
glib-2-64
-  - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never 
blocks” to glib-2-64
-  - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to 
glib-2-64
- 
+  - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual 
Studio” to glib-2-64
+  - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64
+  - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked 
URI list” to glib-2-64
+  - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to 
glib-2-64
+  - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never 
blocks” to glib-2-64
+  - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to 
glib-2-64
  
  Overview of changes in GLib 2.64.4
  ==
  
  * Bugs fixed:
-  - #2140 calling malloc in fork child is undefined-behaviour
-  - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to 
return” to glib-2-64
-  - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64
-  - !1547 Backport !1544 “Resolve "calling malloc in fork child is 
undefined-behaviour"” to glib-2-64
+  - #2140 calling malloc in fork child is undefined-behaviour
+  - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to 
return” to glib-2-64
+  - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64
+  - !1547 Backport !1544 “Resolve "calling malloc in fork child is 
undefined-behaviour"” to glib-2-64
  
  * Translation updates:
-  - Kazakh
-  - Slovenian
+  - Kazakh
+  - Slovenian
  
  [ QA ]
  
  Upstream release, so QA already performed by maintainers
  
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
  
  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.
  
- [ Regression potential ]
+ [ What could go wrong ]
  
- Various fixes in multiple places so multiple apps could be affected.
+ This update contains fixes in multiple places so multiple apps could be
+ affected. The consequences of a broken GLib can range from some
+ functions returning bad results sometimes, which have minimal runtime
+ implications, up to the system simply crashing all the time.
+ 
  Pretty much all parts of GNOME use GLib, so test anything in the desktop
  that you can. If you reboot the machine and can get to the desktop,
  that's already tested GLib extensively. But also run applications like
  GNOME terminal, Files and Epiphany.

** Description changed:

  [ Description ]
  
  Take this new upstrem stable release.
+ 
+ It was easiest for me to merge the latest release in this series from
+ Debian, and

[Touch-packages] [Bug 1908136] Re: no_proxy=::1 is not honored by curl in Bionic and earlier versions

[Iain Lane]

** Changed in: auto-package-testing
   Status: New => Fix Released

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

Title:
  no_proxy=::1 is not honored by curl in Bionic and earlier versions

Status in Auto Package Testing:
  Fix Released
Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Xenial:
  New
Status in curl source package in Bionic:
  New
Status in curl source package in Focal:
  Fix Released

Bug description:
  Bionic:

  env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
  * Could not resolve proxy: foo
  * Closing connection 0
  curl: (5) Could not resolve proxy: foo

  Focal:

  $ env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
  * Uses proxy env variable no_proxy == '::1'
  *   Trying ::1:80...
  * TCP_NODELAY set
  * Immediate connect fail for ::1: Network is unreachable
  * Closing connection 0
  curl: (7) Couldn't connect to server

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1908136/+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 1627564] Re: Debconf crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades)

[Iain Lane]

> OTOH I think there is an easy fix for GTK+ to always include an
"image-missing" icon at compile time

I'm sorry, it's not that easy. A PNG icon is indeed included, and it
gets found properly (also from the actual icon theme; that is a
dependency of GTK). The problem is the ability to load PNGs *at all* is
not available sometimes during the middle of dist-upgrades.

I think extending that test program in Debconf (referred to in the IRC
log above) to do a bit more work - trying to load an icon - might make
the fallback trigger in this case too.

e.g:

  my $window = Gtk3::Window->new('toplevel');
  my $icontheme = Gtk3::IconTheme::get_default;
  my $icon = $icontheme->load_icon('image-missing', 32, []);

If you manually remove '/usr/lib/*/gdk-pixbuf-2.0/2.10.0/loaders.cache'
(suggest doing this in a VM) then you can reproduce this by extracting
the program out of Debconf.

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Invalid

** Changed in: gtk+3.0 (Ubuntu Focal)
   Status: New => Invalid

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

Title:
  Debconf crash due to assertion failure in ensure_surface_for_gicon
  [gtkiconhelper.c:493] (when png loader is missing/during upgrades)

Status in debconf package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in debconf source package in Focal:
  Confirmed
Status in gtk+3.0 source package in Focal:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/2b11576fed59ad23c640bc85a266cc82ec30a689
  https://errors.ubuntu.com/problem/9d612b3f25168e76adb91fa4eedc301ffa632383

  ---

  bubble opened up indicating there was a failure during the latest
  update.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: lightdm-gtk-greeter 2.0.1-2ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.4.0-9136-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  Date: Sun Sep 25 20:37:06 2016
  ExecutablePath: /usr/sbin/lightdm-gtk-greeter
  InstallationDate: Installed on 2016-08-04 (52 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727)
  ProcCmdline: /usr/sbin/lightdm-gtk-greeter
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 6
  SourcePackage: lightdm-gtk-greeter
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
   [greeter]
   theme-name = Lubuntu-dark-panel
  mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 
2016-08-14T22:33:57.293011

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1627564/+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 1908502] Re: [MIR] libtiff5 dependency on libdeflate0

[Iain Lane]

** Also affects: tiff (Ubuntu Hirsute)
   Importance: Undecided
 Assignee: Olivier Tilloy (osomon)
   Status: Confirmed

** Also affects: libdeflate (Ubuntu Hirsute)
   Importance: Undecided
   Status: Incomplete

** Tags removed: rls-hh-incoming

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

Title:
  [MIR] libtiff5 dependency on libdeflate0

Status in libdeflate package in Ubuntu:
  Incomplete
Status in tiff package in Ubuntu:
  Confirmed
Status in libdeflate source package in Hirsute:
  Incomplete
Status in tiff source package in Hirsute:
  Confirmed

Bug description:
  tiff 4.1.0+git201212-1 enabled deflate support, adding libdeflate0 as
  a dependency to libtiff5, making the package uninstallable.

  Therefor I uploaded 4.1.0+git201212-1ubuntu1 disabling the deflate
  support to make libtiff5 installable again.

  Either this package stays this way, or it needs a MIR for libdeflate.

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

[Iain Lane]

This bug is old but I'm going to un-duplicate it. I don't believe it is
fixed.

I've got a cron script on focal (cron 3.0pl1-136ubuntu1) which is
indirectly running `lxc` from a snap (/snap/bin/lxc).

I found the following in mail though:

/home/ubuntu/autopkgtest/tools/autopkgtest-build-lxd: 139: lxc: not found
/home/ubuntu/autopkgtest/tools/autopkgtest-build-lxd: 1: lxc: not found

crontab(5) mentions the default as being "/usr/bin:/bin", and how it
does NOT come from /etc/environment. What you have to do is set
"PATH=/snap/bin:/usr/bin:/bin" at the top of the crontab file if you
want to be able to use snaps. (You can't do "PATH=/snap/bin:$PATH"...)

pathnames.h has a #define for _PATH_DEFPATH where AFAICS this comes
from. Maybe it's that which we would want to modify to fix this for cron
in Ubuntu.

** This bug is no longer a duplicate of bug 1771858
   /snap/bin not in default PATH for units, snapd should ship 
system-environment-generators to inject /snap/bin into $PATH

** Changed in: cron (Ubuntu)
 Assignee: Dimitri John Ledkov (xnox) => (unassigned)

** Tags removed: rls-ee-incoming
** Tags added: rls-ff-incoming rls-hh-incoming

-- 
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 cron package in Ubuntu:
  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/cron/+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 1910576] Re: [MIR] libbpf (dependency of iproute2)

[Iain Lane]

laney@dev> ./change-override -S -c main -s hirsute libbpf
Override component to main
libbpf 0.3-2 in hirsute: universe/misc -> main
libbpf-dev 1:0.3-2 in hirsute amd64: universe/libdevel/optional/100% -> main
libbpf-dev 1:0.3-2 in hirsute arm64: universe/libdevel/optional/100% -> main
libbpf-dev 1:0.3-2 in hirsute armhf: universe/libdevel/optional/100% -> main
libbpf-dev 1:0.3-2 in hirsute ppc64el: universe/libdevel/optional/100% -> main
libbpf-dev 1:0.3-2 in hirsute riscv64: universe/libdevel/optional/100% -> main
libbpf-dev 1:0.3-2 in hirsute s390x: universe/libdevel/optional/100% -> main
libbpf0 1:0.3-2 in hirsute amd64: universe/libs/optional/100% -> main
libbpf0 1:0.3-2 in hirsute arm64: universe/libs/optional/100% -> main
libbpf0 1:0.3-2 in hirsute armhf: universe/libs/optional/100% -> main
libbpf0 1:0.3-2 in hirsute ppc64el: universe/libs/optional/100% -> main
libbpf0 1:0.3-2 in hirsute riscv64: universe/libs/optional/100% -> main
libbpf0 1:0.3-2 in hirsute s390x: universe/libs/optional/100% -> main
Override [y|N]? y
13 publications overridden.


** Changed in: libbpf (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 iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1910576

Title:
  [MIR] libbpf (dependency of iproute2)

Status in iproute2 package in Ubuntu:
  Invalid
Status in libbpf package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
  libbpf | 0.1.0-1 | groovy/universe  | source
  libbpf | 0.3-2   | hirsute/universe | source

  [Rationale]
  Libbpf is (or is about to become) a dependency for building iproute2 which 
already is in main. Using BPF is becoming more wide-spread. The library allows 
to load and use eBPF programs from user-space (functionality provided by the 
kernel). It is already maintained in main for Debian 
(https://tracker.debian.org/pkg/libbpf)

  [Security]
  Since the code is taken out of the Linux kernel, this should be treated 
similar to the kernel for security. Research uncovered no records about 
security issues.

  [Quality assurance]
  At this point there are no open bug reports against libbpf (except this one) 
in Ubuntu. Also no open bugs found in Debian. Project is taken from the kernel 
source and claims static analysis via LGTM and Coverty. Also has CI via Travis 
(https://travis-ci.com/github/libbpf/libbpf).
  Right now there are no dep-8 tests. Though potentially it should be possible 
to create those, would this really add additional benefit beyond having 
upstream CI?
  A test build on hirsute was showing no warnings beyond lintian complaining 
about things which would be changed if we had delta (unstable as series for 
example). Otherwise was clean.

  [Dependencies]
  libc6: main
  libelf1: main
  zlib1g: main

  [Standards compliance]
  $ lintian --pedantic libbpf_0.3-2.dsc
  P: libbpf source: no-homepage-field
  P: libbpf source: silent-on-rules-requiring-root

  [Maintenance]
  As this is only taking out code from the kernel into a separate library 
package, the maintenance effort should be minimal. Packaging is done in Debian 
and is synced into Ubuntu (no delta).

  [Background information]
  A discourse about why this is packaged outside the kernel can be found at 
https://lwn.net/Articles/836911/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1910576/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Iain Lane]

** Changed in: ubuntu-cdimage
 Assignee: Shamindra (wy-354) => (unassigned)

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  In Progress
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Committed
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main

[Touch-packages] [Bug 1907433] Re: [SRU] New stable release 2.64.6

[Iain Lane]

Okay I've verified this now, thanks for adding. Using
2.64.6-1~ubuntu20.04.1 I tested

  - Logging in to Ubuntu
  - Logging out from Ubuntu
  - Fast user switching w/gdm3
  - Many applications which use GLib, including gedit and epiphany-browser

It seems good to me.

There are two outstanding autopkgtest regressions.

The libxmlb failure is bug #1890313 and I just fixed it upstream, in
hirsute (devel) & uploaded to the queue for focal/groovy. If you prefer
you can accept that and retry the test, it should go green.

netplan.io's one I didn't look into, but I think it is bug #1875677
(i.e. pre-existing). Should be hinted if not fixed?

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

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

Title:
  [SRU] New stable release 2.64.6

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  Take this new upstrem stable release.

  It was easiest for me to merge the latest release in this series from
  Debian, and then import the subsequent point releases on top of that.

  Visually in the diff there is one change resulting from this:
  splitting a two-patch upstream cherry pick into two individual patch
  files. This is cleaner anyway IMO, but is also no change if you look
  at the resulting patched source.

  Overview of changes in GLib 2.64.6
  ==

  * This is expected to be the last release in the 2.64 series; the new stable
    series is 2.66, and maintenance efforts will shift to that

  * Bugs fixed:
   - #2194 gtk3/glib crash on gimp
   - #2209 gthreadedresolver: faulty logic in parse_res_txt
   - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64
   - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64
   - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to 
glib-2-64
   - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64
   - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not 
succeeding” to glib-2-64
   - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too 
far in the past” to glib-2-64

  * Translation updates:
   - Croatian
   - Portuguese

  Overview of changes in GLib 2.64.5
  ==

  * Fix deadlock in `g_subprocess_communicate_async()` (work by
  Alexander Larsson) (#2182)

  * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868)

  * Bugs fixed:
   - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual 
Studio” to glib-2-64
   - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64
   - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked 
URI list” to glib-2-64
   - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to 
glib-2-64
   - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never 
blocks” to glib-2-64
   - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to 
glib-2-64

  Overview of changes in GLib 2.64.4
  ==

  * Bugs fixed:
   - #2140 calling malloc in fork child is undefined-behaviour
   - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to 
return” to glib-2-64
   - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64
   - !1547 Backport !1544 “Resolve "calling malloc in fork child is 
undefined-behaviour"” to glib-2-64

  * Translation updates:
   - Kazakh
   - Slovenian

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ What could go wrong ]

  This update contains fixes in multiple places so multiple apps could
  be affected. The consequences of a broken GLib can range from some
  functions returning bad results sometimes, which have minimal runtime
  implications, up to the system simply crashing all the time.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can. If you reboot the machine and can get to the
  desktop, that's already tested GLib extensively. But also run
  applications like GNOME terminal, Files and Epiphany.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1907433/+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 1907433] Re: [SRU] New stable release 2.64.6

[Iain Lane]

> retry the test

with a trigger on libxmlb to get the -proposed version installed.

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

Title:
  [SRU] New stable release 2.64.6

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  Take this new upstrem stable release.

  It was easiest for me to merge the latest release in this series from
  Debian, and then import the subsequent point releases on top of that.

  Visually in the diff there is one change resulting from this:
  splitting a two-patch upstream cherry pick into two individual patch
  files. This is cleaner anyway IMO, but is also no change if you look
  at the resulting patched source.

  Overview of changes in GLib 2.64.6
  ==

  * This is expected to be the last release in the 2.64 series; the new stable
    series is 2.66, and maintenance efforts will shift to that

  * Bugs fixed:
   - #2194 gtk3/glib crash on gimp
   - #2209 gthreadedresolver: faulty logic in parse_res_txt
   - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64
   - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64
   - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to 
glib-2-64
   - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64
   - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not 
succeeding” to glib-2-64
   - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too 
far in the past” to glib-2-64

  * Translation updates:
   - Croatian
   - Portuguese

  Overview of changes in GLib 2.64.5
  ==

  * Fix deadlock in `g_subprocess_communicate_async()` (work by
  Alexander Larsson) (#2182)

  * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868)

  * Bugs fixed:
   - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual 
Studio” to glib-2-64
   - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64
   - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked 
URI list” to glib-2-64
   - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to 
glib-2-64
   - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never 
blocks” to glib-2-64
   - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to 
glib-2-64

  Overview of changes in GLib 2.64.4
  ==

  * Bugs fixed:
   - #2140 calling malloc in fork child is undefined-behaviour
   - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to 
return” to glib-2-64
   - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64
   - !1547 Backport !1544 “Resolve "calling malloc in fork child is 
undefined-behaviour"” to glib-2-64

  * Translation updates:
   - Kazakh
   - Slovenian

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ What could go wrong ]

  This update contains fixes in multiple places so multiple apps could
  be affected. The consequences of a broken GLib can range from some
  functions returning bad results sometimes, which have minimal runtime
  implications, up to the system simply crashing all the time.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can. If you reboot the machine and can get to the
  desktop, that's already tested GLib extensively. But also run
  applications like GNOME terminal, Files and Epiphany.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1907433/+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 1907433] Re: [SRU] New stable release 2.64.6

[Iain Lane]

> retry the test

That has been done. Now the only red is netplan.io.

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

Title:
  [SRU] New stable release 2.64.6

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  Take this new upstrem stable release.

  It was easiest for me to merge the latest release in this series from
  Debian, and then import the subsequent point releases on top of that.

  Visually in the diff there is one change resulting from this:
  splitting a two-patch upstream cherry pick into two individual patch
  files. This is cleaner anyway IMO, but is also no change if you look
  at the resulting patched source.

  Overview of changes in GLib 2.64.6
  ==

  * This is expected to be the last release in the 2.64 series; the new stable
    series is 2.66, and maintenance efforts will shift to that

  * Bugs fixed:
   - #2194 gtk3/glib crash on gimp
   - #2209 gthreadedresolver: faulty logic in parse_res_txt
   - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64
   - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64
   - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to 
glib-2-64
   - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64
   - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not 
succeeding” to glib-2-64
   - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too 
far in the past” to glib-2-64

  * Translation updates:
   - Croatian
   - Portuguese

  Overview of changes in GLib 2.64.5
  ==

  * Fix deadlock in `g_subprocess_communicate_async()` (work by
  Alexander Larsson) (#2182)

  * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868)

  * Bugs fixed:
   - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual 
Studio” to glib-2-64
   - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64
   - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked 
URI list” to glib-2-64
   - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to 
glib-2-64
   - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never 
blocks” to glib-2-64
   - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to 
glib-2-64

  Overview of changes in GLib 2.64.4
  ==

  * Bugs fixed:
   - #2140 calling malloc in fork child is undefined-behaviour
   - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to 
return” to glib-2-64
   - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64
   - !1547 Backport !1544 “Resolve "calling malloc in fork child is 
undefined-behaviour"” to glib-2-64

  * Translation updates:
   - Kazakh
   - Slovenian

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ What could go wrong ]

  This update contains fixes in multiple places so multiple apps could
  be affected. The consequences of a broken GLib can range from some
  functions returning bad results sometimes, which have minimal runtime
  implications, up to the system simply crashing all the time.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can. If you reboot the machine and can get to the
  desktop, that's already tested GLib extensively. But also run
  applications like GNOME terminal, Files and Epiphany.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1907433/+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 1934505] [NEW] gdb 11 doesn't work on impish: internal-error: displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion `gdbarch_d

[Iain Lane]

Public bug reported:

gdb doesn't work on impish/s390x at the minute. Even if you say 'no' to
both questions you still can't debug:

ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "s390x-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ls...
(No debugging symbols found in ls)
(gdb) run
Starting program: /usr/bin/ls
/build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n

This is a bug, please report it.  For instructions, see:
.

/build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
Command aborted.
(gdb)

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

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

Title:
  gdb 11 doesn't work on impish: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb package in Ubuntu:
  New

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1934505/+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 1934505] Re: gdb 11 doesn't work on impish/s390x: internal-error: displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion `gdbar

[Iain Lane]

** Summary changed:

- gdb 11 doesn't work on impish: internal-error: displaced_step_prepare_status 
linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion 
`gdbarch_data->num_disp_step_buffers > 0' failed.
+ gdb 11 doesn't work on impish/s390x: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.

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

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

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

Re: [Touch-packages] [Bug 1934505] Re: gdb 11 doesn't work on impish/s390x: internal-error: displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion `g

[Iain Lane]

On Wed, Jul 07, 2021 at 08:30:32AM -, Matthias Klose wrote:
> fixed in 11.0.90.20210705-0ubuntu2

yep, thanks for reproducing and forwarding!

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  <https://www.gnu.org/software/gdb/bugs/>.
  Find the GDB manual and other documentation resources online at:
  <http://www.gnu.org/software/gdb/documentation/>.

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  <https://www.gnu.org/software/gdb/bugs/>.

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1930359] Re: glib2.0: Uninitialised memory is written to gschema.compiled, failure to parse this file leads to gdm, gnome-shell failing to start

[Iain Lane]

Thanks, sponsored to the queue

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

Title:
  glib2.0: Uninitialised memory is written to gschema.compiled, failure
  to parse this file leads to gdm, gnome-shell failing to start

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  In Progress

Bug description:
  [Impact]

  A recent SRU of mutter 3.36.9-0ubuntu0.20.04.1 caused an outage for a
  user with 300 VDIs running Focal, where GNOME applications would fail
  to start, and if you reboot, gdm and gnome-shell both fail to start,
  and you are left with a black screen and a blinking cursor.

  After much investigation, mutter was not at fault. Instead, mutter-
  common calls the libglib2.0-0 hook on upgrade:

  Processing triggers for libglib2.0-0:amd64 (2.64.6-1~ubuntu20.04.3)
  ...

  This in turn calls glib-compile-schemas to recompile the gsettings
  gschema cache, from the files in /usr/share/glib-2.0/schemas/. The
  result is a binary gschemas.compiled file, which is loaded by
  libglib2.0 on every invocation of a GNOME application, or gdm or
  gnome-shell to fetch application default settings.

  Now, glib2.0 2.64.6-1~ubuntu20.04.3 in Focal has some non-
  deterministic behaviour when calling glib-compile-schemas, causing
  generated gschemas.compiled files to have differing contents on each
  run:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 D0
  3771 A4 DB

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 68
  3771 A4 30
  3772 55 56

  The bytes on the left are from a corrupted gschemas.compiled provided
  by an affected user. The changing bytes on the right are non-
  deterministic.

  I ran valgrind over glib-compile-schemas, and found that we are
  writing to uninitialised memory.

  https://paste.ubuntu.com/p/hvZccwdzxz/

  What is happening is that a submodule of glib, gvdb, contains the
  logic for serialising the gschema data structures, and when it
  allocates a buffer to store the eventual gschemas.compiled file, it
  does not initialise it.

  When we populate the fields in the buffer, some bytes are never
  overwritten, and these junk bytes find themselves written to
  gschemas.compiled.

  On boot, when gdm and gnome-shell attempt to parse and load this
  corrupted gschemas.compiled file, it can't parse the junk bytes, and
  raises and error, which propagates up to a breakpoint in glib logging,
  but no debugger is present, so the kernel traps the breakpoint, and
  terminates the library, and the calling application, e.g. gdm.

  The result is that the user is left starting at a black screen with a
  blinking pointer.

  [Testcase]

  On a Focal system, simply run valgrind over glib-compile-schemas:

  # valgrind glib-compile-schemas /usr/share/glib-2.0/schemas

  You will get output like this, with the warning "Syscall param
  write(buf) points to uninitialised byte(s)":

  https://paste.ubuntu.com/p/hvZccwdzxz/

  If you happen to have a large amount of gschema overrides present on
  your system, like my affected user does, you can save a copy of a
  generated gschema.compiled to your home directory and bindiff it
  against recompiles:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cp /usr/share/glib-2.0/schemas/gschema.compiled 
/home/ubuntu/schemas/gschemas.compiled
  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  If you install the test package from the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf311791-test

  When you run valgrind, it will report a clean run with no writing to
  uninitialised buffers, and all invocations of glib-compile-schemas
  will be deterministic, and generate the file same with the same sha256
  hash every time. The unwritten bytes if you do a bindiff from before
  and after will be all set to zero.

  [Where problems can occur]

  I am doubtful that any programs are relying on buggy non-deterministic
  behaviour from random bytes found in uninitialised memory, so this
  should be a 

[Touch-packages] [Bug 1930359] Re: glib2.0: Uninitialised memory is written to gschema.compiled, failure to parse this file leads to gdm, gnome-shell failing to start

[Iain Lane]

> Looks like both of us sponsored it for the queue. I'd appreciate
rejecting either one of them.

I pushed to the VCS[0] at the same time as sponsoring, so I'll reject
the other one which doesn't quite match up with it.

[0] https://salsa.debian.org/gnome-
team/glib/-/commits/ubuntu/2.64.6-1_ubuntu20.04.4/

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

Title:
  glib2.0: Uninitialised memory is written to gschema.compiled, failure
  to parse this file leads to gdm, gnome-shell failing to start

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  In Progress

Bug description:
  [Impact]

  A recent SRU of mutter 3.36.9-0ubuntu0.20.04.1 caused an outage for a
  user with 300 VDIs running Focal, where GNOME applications would fail
  to start, and if you reboot, gdm and gnome-shell both fail to start,
  and you are left with a black screen and a blinking cursor.

  After much investigation, mutter was not at fault. Instead, mutter-
  common calls the libglib2.0-0 hook on upgrade:

  Processing triggers for libglib2.0-0:amd64 (2.64.6-1~ubuntu20.04.3)
  ...

  This in turn calls glib-compile-schemas to recompile the gsettings
  gschema cache, from the files in /usr/share/glib-2.0/schemas/. The
  result is a binary gschemas.compiled file, which is loaded by
  libglib2.0 on every invocation of a GNOME application, or gdm or
  gnome-shell to fetch application default settings.

  Now, glib2.0 2.64.6-1~ubuntu20.04.3 in Focal has some non-
  deterministic behaviour when calling glib-compile-schemas, causing
  generated gschemas.compiled files to have differing contents on each
  run:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 D0
  3771 A4 DB

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 68
  3771 A4 30
  3772 55 56

  The bytes on the left are from a corrupted gschemas.compiled provided
  by an affected user. The changing bytes on the right are non-
  deterministic.

  I ran valgrind over glib-compile-schemas, and found that we are
  writing to uninitialised memory.

  https://paste.ubuntu.com/p/hvZccwdzxz/

  What is happening is that a submodule of glib, gvdb, contains the
  logic for serialising the gschema data structures, and when it
  allocates a buffer to store the eventual gschemas.compiled file, it
  does not initialise it.

  When we populate the fields in the buffer, some bytes are never
  overwritten, and these junk bytes find themselves written to
  gschemas.compiled.

  On boot, when gdm and gnome-shell attempt to parse and load this
  corrupted gschemas.compiled file, it can't parse the junk bytes, and
  raises and error, which propagates up to a breakpoint in glib logging,
  but no debugger is present, so the kernel traps the breakpoint, and
  terminates the library, and the calling application, e.g. gdm.

  The result is that the user is left starting at a black screen with a
  blinking pointer.

  [Testcase]

  On a Focal system, simply run valgrind over glib-compile-schemas:

  # valgrind glib-compile-schemas /usr/share/glib-2.0/schemas

  You will get output like this, with the warning "Syscall param
  write(buf) points to uninitialised byte(s)":

  https://paste.ubuntu.com/p/hvZccwdzxz/

  If you happen to have a large amount of gschema overrides present on
  your system, like my affected user does, you can save a copy of a
  generated gschema.compiled to your home directory and bindiff it
  against recompiles:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cp /usr/share/glib-2.0/schemas/gschema.compiled 
/home/ubuntu/schemas/gschemas.compiled
  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  If you install the test package from the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf311791-test

  When you run valgrind, it will report a clean run with no writing to
  uninitialised buffers, and all invocations of glib-compile-schemas
  will be deterministic, and generate the file same with the same sha256
  hash every time.

[Touch-packages] [Bug 1934936] Re: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is dif

[Iain Lane]

Yeah I'm getting this too on dist-upgrade, now that heimdal migrated to
impish.

laney@raleigh> diff -u <(xxd changelog.Debian.gz-amd64) <(xxd 
changelog.Debian.gz-i386)
--- /proc/self/fd/112021-07-16 11:20:29.165989264 +0100
+++ /proc/self/fd/202021-07-16 11:20:29.169989204 +0100
@@ -97,5 +97,5 @@
 0600: 8a9e 51d4 4f3c 479b 631a d7fa aea8 3049  ..Q.Ohttps://bugs.launchpad.net/bugs/1934936

Title:
  package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is
  different from other instances of package libwind0-heimdal:i386

Status in heimdal package in Ubuntu:
  Confirmed

Bug description:
  fresh 21.10 install and 1 reboot later it said there was additional
  updates and while doing so the error popped up

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: libwind0-heimdal 7.7.0+dfsg-2build1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul  8 01:45:16 2021
  DuplicateSignature:
   package:libwind0-heimdal:7.7.0+dfsg-2build1
   Unpacking libwind0-heimdal:i386 (7.7.0+dfsg-2build1) over (7.7.0+dfsg-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8FDC3J/53-libwind0-heimdal_7.7.0+dfsg-2build1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  InstallationDate: Installed on 2021-06-05 (32 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RebootRequiredPkgs:
   libc6
   libc6
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.6
  SourcePackage: heimdal
  Title: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  UpgradeStatus: Upgraded to impish on 2021-07-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1934936/+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 1934936] Re: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is dif

[Iain Lane]

welp, this is more sensible as a thing to look at:

laney@raleigh> diff -u <(zcat changelog.Debian.gz-amd64) <(zcat 
changelog.Debian.gz-i386)
--- /proc/self/fd/112021-07-16 11:22:45.935902600 +0100
+++ /proc/self/fd/202021-07-16 11:22:45.939902539 +0100
@@ -95,4 +95,4 @@
 
  -- Brian May   Wed, 26 Apr 2017 19:38:20 +1000
 
-# For older changelog entries, run 'apt-get changelog libwind0-heimdal'
+# For older changelog entries, run 'apt-get changelog libheimbase1-heimdal'

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

Title:
  package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is
  different from other instances of package libwind0-heimdal:i386

Status in heimdal package in Ubuntu:
  Confirmed

Bug description:
  fresh 21.10 install and 1 reboot later it said there was additional
  updates and while doing so the error popped up

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: libwind0-heimdal 7.7.0+dfsg-2build1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul  8 01:45:16 2021
  DuplicateSignature:
   package:libwind0-heimdal:7.7.0+dfsg-2build1
   Unpacking libwind0-heimdal:i386 (7.7.0+dfsg-2build1) over (7.7.0+dfsg-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8FDC3J/53-libwind0-heimdal_7.7.0+dfsg-2build1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  InstallationDate: Installed on 2021-06-05 (32 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RebootRequiredPkgs:
   libc6
   libc6
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.6
  SourcePackage: heimdal
  Title: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  UpgradeStatus: Upgraded to impish on 2021-07-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1934936/+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 1934936] Re: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is dif

[Iain Lane]

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

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

Title:
  package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is
  different from other instances of package libwind0-heimdal:i386

Status in heimdal package in Ubuntu:
  Confirmed

Bug description:
  fresh 21.10 install and 1 reboot later it said there was additional
  updates and while doing so the error popped up

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: libwind0-heimdal 7.7.0+dfsg-2build1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul  8 01:45:16 2021
  DuplicateSignature:
   package:libwind0-heimdal:7.7.0+dfsg-2build1
   Unpacking libwind0-heimdal:i386 (7.7.0+dfsg-2build1) over (7.7.0+dfsg-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8FDC3J/53-libwind0-heimdal_7.7.0+dfsg-2build1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  InstallationDate: Installed on 2021-06-05 (32 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RebootRequiredPkgs:
   libc6
   libc6
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.6
  SourcePackage: heimdal
  Title: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  UpgradeStatus: Upgraded to impish on 2021-07-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1934936/+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 1934936] Re: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is dif

[Iain Lane]

It's probably a bug in pkgstripfiles, will confirm

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

Title:
  package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is
  different from other instances of package libwind0-heimdal:i386

Status in heimdal package in Ubuntu:
  Confirmed

Bug description:
  fresh 21.10 install and 1 reboot later it said there was additional
  updates and while doing so the error popped up

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: libwind0-heimdal 7.7.0+dfsg-2build1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul  8 01:45:16 2021
  DuplicateSignature:
   package:libwind0-heimdal:7.7.0+dfsg-2build1
   Unpacking libwind0-heimdal:i386 (7.7.0+dfsg-2build1) over (7.7.0+dfsg-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8FDC3J/53-libwind0-heimdal_7.7.0+dfsg-2build1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  InstallationDate: Installed on 2021-06-05 (32 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RebootRequiredPkgs:
   libc6
   libc6
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.6
  SourcePackage: heimdal
  Title: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  UpgradeStatus: Upgraded to impish on 2021-07-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1934936/+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 1817344] Re: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results

[Iain Lane]

Thanks, I would guess that I broke this somehow in
https://git.launchpad.net/autopkgtest-
cloud/commit/?id=58adff467c108506f979e229aa8e9e955a7d0d0a - which was a
commit I made because systemd PRs were taking a long time after their
jobs finished (several hours) to report any results due to that script
having terrible runtime.

I'll stare at that code and see if I can see what I did wrong. Sorry
about that.

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

Title:
  Ubuntu CI that runs tests via autopkgtest for systemd on GitHub
  reports the wrong results

Status in autopkgtest-cloud:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I'm not sure this is the right place to report this, but apparently
  it's the best way to reach out to Dimitri John Ledkov
  (https://github.com/xnox) and Iain Lane (https://github.com/iainlane),
  who I believe at least know who maintains Ubuntu CI there.

  I'm copying the following verbatim from
  https://github.com/systemd/systemd/pull/11531#issuecomment-464731263
  (where we are kind of discussing the issue):

  > The two PRs you referenced to fail in the `make check` unit tests
  (test-path).

  That's correct that test-path failed but it failed in
  https://github.com/systemd/systemd/pull/11685 while Ubuntu CI reported
  it in https://github.com/systemd/systemd/pull/11686 (that is, in
  https://github.com/systemd/systemd/pull/11686 in the logs for some
  reason UPSTREAM_PULL_REQUEST is 11685 instead of 11686 and something
  like that has happened often lately).

  In
  https://github.com/systemd/systemd/pull/11743#issuecomment-464637797,
  the issue is that Ubuntu CI showed the results for the first version
  of the PR (where there was a bug) and it didn't run the tests against
  the latest version. But in that case it's hard to tell because there
  is no way to figure out what exactly Ubuntu CI tested. That's why I
  asked @xnox to add `git describe` to https://salsa.debian.org/systemd-
  team/systemd/blob/master/debian/extra/checkout-upstream so that by
  looking at UPSTREAM_PULL_REQUEST and the output of `git describe` it
  would be possible to find out what Ubuntu CI reports.

To manage notifications about this bug go to:
https://bugs.launchpad.net/autopkgtest-cloud/+bug/1817344/+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 1817344] Re: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results

[Iain Lane]

Yeah OK, I'm pretty sure that change is bogus. I think it'll mean that
if we hit the 'cache' we'll post back to the wrong status URL, since we
don't check the environment matches.

I'll just revert that for now. Sorry again.

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

Title:
  Ubuntu CI that runs tests via autopkgtest for systemd on GitHub
  reports the wrong results

Status in Auto Package Testing:
  Fix Released
Status in systemd package in Ubuntu:
  New

Bug description:
  I'm not sure this is the right place to report this, but apparently
  it's the best way to reach out to Dimitri John Ledkov
  (https://github.com/xnox) and Iain Lane (https://github.com/iainlane),
  who I believe at least know who maintains Ubuntu CI there.

  I'm copying the following verbatim from
  https://github.com/systemd/systemd/pull/11531#issuecomment-464731263
  (where we are kind of discussing the issue):

  > The two PRs you referenced to fail in the `make check` unit tests
  (test-path).

  That's correct that test-path failed but it failed in
  https://github.com/systemd/systemd/pull/11685 while Ubuntu CI reported
  it in https://github.com/systemd/systemd/pull/11686 (that is, in
  https://github.com/systemd/systemd/pull/11686 in the logs for some
  reason UPSTREAM_PULL_REQUEST is 11685 instead of 11686 and something
  like that has happened often lately).

  In
  https://github.com/systemd/systemd/pull/11743#issuecomment-464637797,
  the issue is that Ubuntu CI showed the results for the first version
  of the PR (where there was a bug) and it didn't run the tests against
  the latest version. But in that case it's hard to tell because there
  is no way to figure out what exactly Ubuntu CI tested. That's why I
  asked @xnox to add `git describe` to https://salsa.debian.org/systemd-
  team/systemd/blob/master/debian/extra/checkout-upstream so that by
  looking at UPSTREAM_PULL_REQUEST and the output of `git describe` it
  would be possible to find out what Ubuntu CI reports.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1817344/+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 1817344] Re: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results

[Iain Lane]

Done. Please let me know here if this is still a problem.

** Project changed: autopkgtest-cloud => auto-package-testing

** Changed in: auto-package-testing
   Status: New => Fix Released

** Changed in: auto-package-testing
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  Ubuntu CI that runs tests via autopkgtest for systemd on GitHub
  reports the wrong results

Status in Auto Package Testing:
  Fix Released
Status in systemd package in Ubuntu:
  New

Bug description:
  I'm not sure this is the right place to report this, but apparently
  it's the best way to reach out to Dimitri John Ledkov
  (https://github.com/xnox) and Iain Lane (https://github.com/iainlane),
  who I believe at least know who maintains Ubuntu CI there.

  I'm copying the following verbatim from
  https://github.com/systemd/systemd/pull/11531#issuecomment-464731263
  (where we are kind of discussing the issue):

  > The two PRs you referenced to fail in the `make check` unit tests
  (test-path).

  That's correct that test-path failed but it failed in
  https://github.com/systemd/systemd/pull/11685 while Ubuntu CI reported
  it in https://github.com/systemd/systemd/pull/11686 (that is, in
  https://github.com/systemd/systemd/pull/11686 in the logs for some
  reason UPSTREAM_PULL_REQUEST is 11685 instead of 11686 and something
  like that has happened often lately).

  In
  https://github.com/systemd/systemd/pull/11743#issuecomment-464637797,
  the issue is that Ubuntu CI showed the results for the first version
  of the PR (where there was a bug) and it didn't run the tests against
  the latest version. But in that case it's hard to tell because there
  is no way to figure out what exactly Ubuntu CI tested. That's why I
  asked @xnox to add `git describe` to https://salsa.debian.org/systemd-
  team/systemd/blob/master/debian/extra/checkout-upstream so that by
  looking at UPSTREAM_PULL_REQUEST and the output of `git describe` it
  would be possible to find out what Ubuntu CI reports.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1817344/+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 1760569] Re: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

[Iain Lane]

** Description changed:

+ [ Description ]
+ 
+ A crasher when using nautilus. No clear reproducer.
+ 
+ [ QA ]
+ 
+ Under the GNOME MRE, believe all bugs that upstream says are fixed are
+ really fixed without explicitly verifying them.
+ 
+ https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
+ 
+ Make sure nautilus works, and that the error tracker buckets listed
+ below at least don't increase more rapidly (but hopefully tail off with
+ the new version)
+ 
+ 
+ [ Regression potential ]
+ 
+ It's GLib. A regression could break the whole desktop, or any part of
+ it... Our QA should help us have confidence that the update is at least
+ not that bad.
+ 
+ [ Original description ]
+ 
  Happens when there's a "rename" to a file to its same value, no known
  reproducer though.
  
  Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456
  
  https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45
  https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9
  
  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AssertionMessage: munmap_chunk(): invalid pointer
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 09:04:45 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2018-03-31 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid 
pointer") at malloc.c:5350
   munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846
   __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117
   g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus assert failure: munmap_chunk(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

** Changed in: glib2.0 (Ubuntu Bionic)
   Status: Triaged => In Progress

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

Title:
  Nautilus crashes in g_free -> g_bookmark_file_move_item ->
  gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  In Progress
Status in nautilus source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  A crasher when using nautilus. No clear reproducer.

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Make sure nautilus works, and that the error tracker buckets listed
  below at least don't increase more rapidly (but hopefully tail off
  with the new version)

  
  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

  [ Original description ]

  Happens when there's a "rename" to a file to its same value, no known
  reproducer though.

  Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456

  https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45
  https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AssertionMessage: munmap_chunk(): invalid pointer
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 09:04:45 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 

[Touch-packages] [Bug 1816547] Re: SRU 2.56.4 to bionic

[Iain Lane]

** Description changed:

+ [ Description ]
+ 
+ New upstream bug fix microrelease
+ 
  * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582)
  
  * Bug fixes:
-  #1588 Moving a bookmark item to the same URI causes a crash
-  #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56
- 
+  #1588 Moving a bookmark item to the same URI causes a crash
+  #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56
  
  Plus fix for LP: #1760569
+ 
+ [ QA ]
+ 
+ Under the GNOME MRE, believe all bugs that upstream says are fixed are
+ really fixed without explicitly verifying them.
+ 
+ https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
+ 
+ Test various parts of the desktop.
+ 
+   - Logging in
+   - Shutting down
+   - Starting a variety of apps and checking that they work
+ + rhythmbox (play a song using gstreamer)
+ + cheese (look at yourself with your webcam using gstreamer)
+ + network-manager
+ + epiphany (web stuff works)

** Description changed:

  [ Description ]
  
  New upstream bug fix microrelease
  
  * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582)
  
  * Bug fixes:
   #1588 Moving a bookmark item to the same URI causes a crash
   #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56
  
  Plus fix for LP: #1760569
  
  [ QA ]
  
  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.
  
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
  
  Test various parts of the desktop.
  
-   - Logging in
-   - Shutting down
-   - Starting a variety of apps and checking that they work
- + rhythmbox (play a song using gstreamer)
- + cheese (look at yourself with your webcam using gstreamer)
- + network-manager
- + epiphany (web stuff works)
+   - Logging in
+   - Shutting down
+   - Starting a variety of apps and checking that they work
+ + rhythmbox (play a song using gstreamer)
+ + cheese (look at yourself with your webcam using gstreamer)
+ + network-manager
+ + epiphany (web stuff works)
+ 
+ Monitor the error tracker for any increases.
+ 
+ [ Regression potential ]
+ 
+ It's GLib. A regression could break the whole desktop, or any part of
+ it... Our QA should help us have confidence that the update is at least
+ not that bad.

** Changed in: glib2.0 (Ubuntu Bionic)
   Status: Triaged => In Progress

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

Title:
  SRU 2.56.4 to bionic

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  In Progress

Bug description:
  [ Description ]

  New upstream bug fix microrelease

  * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582)

  * Bug fixes:
   #1588 Moving a bookmark item to the same URI causes a crash
   #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56

  Plus fix for LP: #1760569

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Test various parts of the desktop.

    - Logging in
    - Shutting down
    - Starting a variety of apps and checking that they work
  + rhythmbox (play a song using gstreamer)
  + cheese (look at yourself with your webcam using gstreamer)
  + network-manager
  + epiphany (web stuff works)

  Monitor the error tracker for any increases.

  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

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

[Iain Lane]

uploaded to the SRU queue, now we wait

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

Title:
  SRU 2.56.4 to bionic

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  In Progress

Bug description:
  [ Description ]

  New upstream bug fix microrelease

  * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582)

  * Bug fixes:
   #1588 Moving a bookmark item to the same URI causes a crash
   #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56

  Plus fix for LP: #1760569

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Test various parts of the desktop.

    - Logging in
    - Shutting down
    - Starting a variety of apps and checking that they work
  + rhythmbox (play a song using gstreamer)
  + cheese (look at yourself with your webcam using gstreamer)
  + network-manager
  + epiphany (web stuff works)

  Monitor the error tracker for any increases.

  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1816547/+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 1760569] Re: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

[Iain Lane]

uploaded to the SRU queue, now we wait

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

Title:
  Nautilus crashes in g_free -> g_bookmark_file_move_item ->
  gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  In Progress
Status in nautilus source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  A crasher when using nautilus. No clear reproducer.

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Make sure nautilus works, and that the error tracker buckets listed
  below at least don't increase more rapidly (but hopefully tail off
  with the new version)

  
  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

  [ Original description ]

  Happens when there's a "rename" to a file to its same value, no known
  reproducer though.

  Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456

  https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45
  https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AssertionMessage: munmap_chunk(): invalid pointer
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 09:04:45 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2018-03-31 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid 
pointer") at malloc.c:5350
   munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846
   __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117
   g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus assert failure: munmap_chunk(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1760569/+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 1772898] Re: [SRU] New stable release 1.14.1

[Iain Lane]

No. A bug won't help get the work done, we know about it.

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

Title:
  [SRU] New stable release 1.14.1

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-bad1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-base1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-good1.0 source package in Bionic:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Bionic:
  Fix Released
Status in gst-python1.0 source package in Bionic:
  Fix Released
Status in gst-rtsp-server1.0 source package in Bionic:
  Fix Released
Status in gstreamer-editing-services1.0 source package in Bionic:
  Fix Released
Status in gstreamer-vaapi source package in Bionic:
  Fix Released
Status in gstreamer1.0 source package in Bionic:
  Fix Released

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1772898/+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 1819183] Re: FFe: Update pygobject to 3.32

[Iain Lane]

Yep, sure. (Ideally as a sync.)

It'd be nicer for me in future if you could paste the NEWS entries and
other things, so that I can read it all and reply directly from my email
client. :-)

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

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

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

Title:
  FFe: Update pygobject to 3.32

Status in pygobject package in Ubuntu:
  Confirmed

Bug description:
  Feature Freeze exception request
  
  Since we're updating the rest of GNOME to 3.32 (including glib and 
gobject-introspection), it seems like it would be a good idea to update 
pygobject also.

  3.32.0-1 is in Debian experimental ready to be synced over once this
  FFe is approved.

  https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS
  https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.32.0 (includes 
several commits that were already included in the current 3.30.4 version)

  Justification for lateness
  --
  Sorry, we've been a bit busy and this wasn't a high priority.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1819183/+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 1818516] Re: FFe: Mesa 19.0.x for disco

[Iain Lane]

what testing has happened / what are the risks?

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

Title:
  FFe: Mesa 19.0.x for disco

Status in mesa package in Ubuntu:
  New

Bug description:
  Mesa 19.0.0 will be soon released, and we should get that for disco,
  and then follow point-releases until the last one is released (roughly
  next July, will need an SRU).

  We'll also migrate it to use LLVM 8.

  New features according to upstream release notes:

  GL_AMD_texture_texture4 on all GL 4.0 drivers.
  GL_EXT_shader_implicit_conversions on all drivers (ES extension).
  GL_EXT_texture_compression_bptc on all GL 4.0 drivers (ES extension).
  GL_EXT_texture_compression_rgtc on all GL 3.0 drivers (ES extension).
  GL_EXT_render_snorm on gallium drivers (ES extension).
  GL_EXT_texture_view on drivers supporting texture views (ES extension).
  GL_OES_texture_view on drivers supporting texture views (ES extension).
  GL_NV_shader_atomic_float on nvc0 (Fermi/Kepler only).
  Shader-based software implementations of GL_ARB_gpu_shader_fp64, 
GL_ARB_gpu_shader_int64, GL_ARB_vertex_attrib_64bit, and GL_ARB_shader_ballot 
on i965.
  VK_ANDROID_external_memory_android_hardware_buffer on Intel
  Fixed and re-exposed VK_EXT_pci_bus_info on Intel and RADV
  VK_EXT_scalar_block_layout on Intel and RADV
  VK_KHR_depth_stencil_resolve on Intel
  VK_KHR_draw_indirect_count on Intel
  VK_EXT_conditional_rendering on Intel
  VK_EXT_memory_budget on RADV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1818516/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace

[Iain Lane]

** No longer affects: libnotify (Ubuntu Xenial)

** No longer affects: libnotify (Ubuntu Bionic)

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

Title:
  Notifications emitted by a snap with local files or desktop files use
  wrong namespace

Status in libnotify package in Ubuntu:
  In Progress

Bug description:
  As can be tested using this example snap:
   - https://github.com/3v1n0/notify-send-test-snap

  Basically the icons are referenced using absolute paths in snap
  environment, while they should be readapted so that they depend on
  $SNAP location.

  As we do with appindicators and libunity emblems.

  

  
  [ Impact ]

  Icons sonuds and desktop files referenced by a snapped app using
  notifications aren't exposed to the desktop in absolute paths

  [ Test case ]

  Build the test snap:
git clone https://github.com/3v1n0/notify-send-test-snap
snapcraft prime
snap try prime

  Check that icons are shown when launching:
notify-send-test-snap
notify-send-test-snap.image-path

  Running them with G_MESSAGES_DEBUG=all should provide translation
  logging

  [ Regression potential ]

  Normal applications that are run with a SNAP environment variable set,
  might use wrong paths for files or desktop file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1817453] Re: 19.04 installer displays keyboard layouts in the wrong language

[Iain Lane]

Think I've fixed this

** Package changed: ubiquity (Ubuntu Disco) => console-setup (Ubuntu
Disco)

** Changed in: console-setup (Ubuntu Disco)
   Status: Confirmed => In Progress

** Changed in: console-setup (Ubuntu Disco)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  19.04 installer displays keyboard layouts in the wrong language

Status in console-setup package in Ubuntu:
  In Progress
Status in console-setup source package in Disco:
  In Progress

Bug description:
  When you select the Spanish language in the installer, when you go to
  the keyboard layout selection these are in another language. The
  options for Latin American Spanish do not appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubiquity 19.04.5
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 24 06:51:45 2019
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1817453/+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 1817453] Re: 19.04 installer displays keyboard layouts in the wrong language

[Iain Lane]

This should be fixed in dailies from today (20190316)

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

Title:
  19.04 installer displays keyboard layouts in the wrong language

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Disco:
  Fix Released

Bug description:
  When you select the Spanish language in the installer, when you go to
  the keyboard layout selection these are in another language. The
  options for Latin American Spanish do not appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubiquity 19.04.5
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 24 06:51:45 2019
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1817453/+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 1816547] Re: SRU 2.56.4 to bionic

[Iain Lane]

bah, it failed on i386 and s390x:

Bail out! 
GLib:ERROR:../../../../glib/gvariant-serialiser.c:174:g_variant_serialised_check:
 assertion failed (alignment & (gsize) serialised.data == 0): (3 == 0)
ERROR: gvariant - Bail out! 
GLib:ERROR:../../../../glib/gvariant-serialiser.c:174:g_variant_serialised_check:
 assertion failed (alignment & (gsize) serialised.data == 0): (3 == 0)

I guess we need these from the branch:

*   commit d202953c47284a17d03dd2d14b67756aa5edc872
|\  Merge: 8723aba59 4ef58e566
| | Author: Simon McVittie 
| | Date:   Fri Jan 4 14:14:56 2019 +
| | 
| | Merge branch 'backport-552-gvariant-test-alignment-glib-2-56' into 
'glib-2-56'
| | 
| | Backport tests: Allocate gvariant data from the heap to guarantee 
alignment to glib-2-56
| | 
| | See merge request GNOME/glib!557
| | 
| * commit 4ef58e5661849317a1110c9b93957f2c608677dd
| | Author: Simon McVittie 
| | Date:   Thu Jan 3 08:21:40 2019 +
| | 
| | gvariant test: Also force alignment for tuple test data
| | 
| | glib!552 (commit 9eed22b3) fixed this for the tests that failed on i686,
| | but this additional test failed on Debian's s390x port
| | (IBM z/Architecture, 64-bit big-endian).
| | 
| | Signed-off-by: Simon McVittie 
| | 
| * commit 85c4031696add9797e2334ced20678edcd96c869
|/  Author: Mart Raudsepp 
|   Date:   Wed Dec 19 16:22:21 2018 +0200
|   
|   tests: Allocate gvariant data from the heap to guarantee alignment
|   
|   On glib-2-58 branch we don't have !455, thus we need aligned data
|   for the gvariant tests to not fail on i686.
|   
|   Fixes #1626


probably.

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

Title:
  SRU 2.56.4 to bionic

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  New upstream bug fix microrelease

  * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582)

  * Bug fixes:
   #1588 Moving a bookmark item to the same URI causes a crash
   #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56

  Plus fix for LP: #1760569

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Test various parts of the desktop.

    - Logging in
    - Shutting down
    - Starting a variety of apps and checking that they work
  + rhythmbox (play a song using gstreamer)
  + cheese (look at yourself with your webcam using gstreamer)
  + network-manager
  + epiphany (web stuff works)

  Monitor the error tracker for any increases.

  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1816547/+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 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]

[Iain Lane]

** Tags added: rls-cc-incoming

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

Title:
  Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from
  _mesa_reference_renderbuffer_() [often when running Skype or Slack
  snaps]

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca
  https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: ASUS All Series
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
  UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 16 18:18:18 2017
  xserver.configfile: default
  xserver.devices:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.19.3-1ubuntu

[Touch-packages] [Bug 1770271] Re: VegaM support

[Iain Lane]

** Changed in: mesa (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  VegaM support

Status in amd:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in mesa source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  New

Bug description:
  VegaM is a new GPU.  Please include support for VegaM in the next LTS
  (16.04.x and 18.04.x) and non-LTS releases.

  Kernel support starts here (32 patches):
  https://patchwork.freedesktop.org/patch/218839/

  Mesa support:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1770271/+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 1798597] Re: Backport packages for 18.04.2 HWE stack

[Iain Lane]

** Changed in: mesa (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Backport packages for 18.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-7 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  New
Status in libdrm source package in Bionic:
  New
Status in llvm-toolchain-7 source package in Bionic:
  New
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New

Bug description:
  [Impact]

  [Test case]

  [Regression potential]

  libdrm:

  llvm-7:

  libclc:

  mesa:

  xserver:

  drivers:

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)

[Iain Lane]

** Changed in: mesa (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

Status in X.Org X server:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in mesa source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Confirmed

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1714178/+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 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]

[Iain Lane]

** Also affects: mesa (Ubuntu Disco)
   Importance: High
   Status: Confirmed

** Also affects: xorg-server (Ubuntu Disco)
   Importance: High
 Assignee: Timo Aaltonen (tjaalton)
   Status: Confirmed

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

** Also affects: xorg-server (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: mesa (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: xorg-server (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: mesa (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu Cosmic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu Disco)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: xorg-server (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: xorg-server (Ubuntu Cosmic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from
  _mesa_reference_renderbuffer_() [often when running Skype or Slack
  snaps]

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New
Status in mesa source package in Cosmic:
  New
Status in xorg-server source package in Cosmic:
  New
Status in mesa source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca
  https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: ASUS All Series
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
  UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  dmi.board.vendor: A

[Touch-packages] [Bug 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]

[Iain Lane]

** Tags removed: rls-cc-incoming

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

Title:
  Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from
  _mesa_reference_renderbuffer_() [often when running Skype or Slack
  snaps]

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Incomplete
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New
Status in mesa source package in Cosmic:
  New
Status in xorg-server source package in Cosmic:
  Incomplete
Status in mesa source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Incomplete

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca
  https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  MachineType: ASUS All Series
  ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 
4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Title: Xwayland crashed with SIGABRT
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)
  UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy 
fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video

[Touch-packages] [Bug 1803487] Re: gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → gweather_location_format_two_deserialize → gweather_location_deserialize → ffi_call_unix64

[Iain Lane]

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

** Also affects: gnome-shell (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu Bionic)
   Status: New => Invalid

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

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

** Changed in: libgweather (Ubuntu Bionic)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gnome-shell crashes with SIGSEGV in
  gweather_location_common_deserialize →
  gweather_location_format_two_deserialize →
  gweather_location_deserialize → ffi_call_unix64 → ffi_call

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in libgweather package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Invalid
Status in libgweather source package in Bionic:
  In Progress

Bug description:
  [ Description ]

  The second stable release in the 3.28 series.

  [ QA ]

  Run Ubuntu session, expect the shell to show weather information and
  not to crash on timezone changes

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Weather location might be leaked. However this is very safe as
  upstream fix comes with proper testing.

  ---

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.28.3-0ubuntu0.18.04.3, the problem page at 
https://errors.ubuntu.com/problem/4ff1b7671a7dc53f26da1c0f78af65d0cc5168fa 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803487/+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 1803487] Re: gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → gweather_location_format_two_deserialize → gweather_location_deserialize → ffi_call_unix64

[Iain Lane]

It's uploaded, thanks.

I did make some changes though.

  - Drop the debian/rules changes - they made the package fail to build! (and 
aren't required for the SRU).
  - debian/control.in, debian/gbp.conf: Use the right branch.

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

Title:
  gnome-shell crashes with SIGSEGV in
  gweather_location_common_deserialize →
  gweather_location_format_two_deserialize →
  gweather_location_deserialize → ffi_call_unix64 → ffi_call

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in libgweather package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Invalid
Status in libgweather source package in Bionic:
  In Progress

Bug description:
  [ Description ]

  The second stable release in the 3.28 series.

  [ QA ]

  Run Ubuntu session, expect the shell to show weather information and
  not to crash on timezone changes

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Weather location might be leaked. However this is very safe as
  upstream fix comes with proper testing.

  ---

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.28.3-0ubuntu0.18.04.3, the problem page at 
https://errors.ubuntu.com/problem/4ff1b7671a7dc53f26da1c0f78af65d0cc5168fa 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803487/+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 1799647] Re: Patch: Add configuration for german provider winSIM

[Iain Lane]

hey,

thanks!

The upstream repository has moved to: https://gitlab.gnome.org/GNOME
/mobile-broadband-provider-info - could you try submitting there please?

I just edited that wiki page to update the links.

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

Title:
  Patch: Add configuration for german provider winSIM

Status in mobile-broadband-provider-info package in Ubuntu:
  New

Bug description:
  I was unable to contribute a patch to the upstream gnome package:
  
https://wiki.gnome.org/Projects/NetworkManager/MobileBroadband/ServiceProviders
  (They seem to have migrated their git servers away)

  I still think this little config change adds value to Ubuntu users, hence I 
am opening this issue.
  Find the patchfile attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mobile-broadband-provider-info/+bug/1799647/+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 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

[Iain Lane]

** Changed in: gtk+3.0 (Ubuntu)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

** Changed in: gtk+3.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

** Changed in: gtk+3.0 (Ubuntu Cosmic)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in cups-filters package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in cups-filters source package in Bionic:
  Invalid
Status in gtk+3.0 source package in Bionic:
  New
Status in cups-filters source package in Cosmic:
  Invalid
Status in gtk+3.0 source package in Cosmic:
  New

Bug description:
  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/cups/cupsd.conf']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1763520/+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 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

[Iain Lane]

I'm uploading to all supported releases, to be safe and to satisfy the
SRU process (trying to minimise the possibility of regressing the bug).

For cosmic, suggest running through the testcase and making sure it
still works.

At the time of writing, there's currently a gnome-shell verified for
release in cosmic-proposed; please don't clobber that if it's still
there when this upload is reviewed.

** Also affects: ibus (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: gnome-shell (Ubuntu Bionic)
   Status: Confirmed => In Progress

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: gnome-shell (Ubuntu Bionic)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: gnome-shell (Ubuntu Cosmic)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in ibus package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  In Progress
Status in gnome-shell source package in Cosmic:
  In Progress
Status in ibus source package in Cosmic:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/391

  ---

  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean
  users are simply unable to fill in password fields that previously
  were working fine. (see "ACTUAL RESULTS" below)

  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
    (click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).

  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1805857] Re: network-manager dep8 failure blocks dnsmasq proposed migration

[Iain Lane]

After looking for a while, I think that the error we were managing to
reproduce (LOWERLAYERDOWN) was probably a red herring, and we were
reproducing some other (valid) bug. The original cause of the testsuite
failure still exists.

Not entirely sure why but this only reproduces for me 'properly' when I
use the real autopkgtest cloud. It's quite reliable there, so I ran a
bisect and it resulted in this mail:

http://lists.thekelleys.org.uk/pipermail/dnsmasq-
discuss/2018q4/012709.html

I freely admit my relative ignorance here, so if anyone can help please
feel free to chip in.

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

Title:
  network-manager dep8 failure blocks dnsmasq proposed migration

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Disco:
  Triaged

Bug description:
  dnsmasq 2.80-1 is blocked from migrating to the release pocket because
  of, amongst other things, a network-manager dep8 regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1805857/+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 1422096] Re: Occasionally no network on resume

[Iain Lane]

No. I don't have that laptop any more though, but I do have a similar
network setup (connecting via wired and wireless to the same network).
This can probably be Incomplete -> expired.

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

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

Title:
  Occasionally no network on resume

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Sometimes I resume and n-m thinks that lxcbr0 is a connected wired
  network, so doesn't connect to the wireless network that I actually
  want to use until I restart it.

  laney@iota> nmcli d
  DEVICE TYPE  STATE CONNECTION 
  lxcbr0 bridgeconnected lxcbr0 
  virbr0 bridgeconnected virbr0 
  50:46:5D:18:E7:06  btdisconnected  -- 
  wlan0  wifi  disconnected  -- 
  eth0   ethernet  unavailable   -- 
  lo loopback  unmanaged -- 
  virbr0-nic tap   unmanaged -- 
  laney@iota> nmcli d w l ifname wlan0
  *  SSID  MODE  CHAN  RATE  SIGNAL  BARS  SECURITY 
  laney@iota> cat /etc/network/interfaces
  auto lo
  iface lo inet loopback

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Feb 15 10:37:28 2015
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-10-18 (850 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.134
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2014-07-30 (200 days ago)
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1422096/+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 1829366] [NEW] [SRU] Bugfix release 1.14.4

[Iain Lane]

Public bug reported:

We should update bionic with the (now quite old!) point release

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: gstreamer1.0 (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Also affects: gstreamer1.0 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  [SRU]  Bugfix release 1.14.4

Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gstreamer1.0 source package in Bionic:
  New

Bug description:
  We should update bionic with the (now quite old!) point release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1829366/+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 1829366] Re: [SRU] Bugfix release 1.14.4

[Iain Lane]

** Description changed:

- We should update bionic with the (now quite old!) point release
+ [ Description ]
+ 
+ We should keep up with GStreamer's bugfix releases in the 1.14 series
+ that 18.04 shipped with.
+ 
+ [ QA and testing ]
+ 
+ Play a range of videos in Totem. Play a range of audio tracks in
+ Rhythmbox. Try to stream audio and/or video. Try to install a missing
+ codec.
+ 
+ In all cases, make sure that everything which worked before still works.
+ 
+ [ Regression potential ]
+ 
+ If one of the fixes is bad then it might break video or audio playback,
+ or could crash any application that tries to use gstreamer.

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

Title:
  [SRU]  Bugfix release 1.14.4

Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gstreamer1.0 source package in Bionic:
  New

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio
  playback, or could crash any application that tries to use gstreamer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1829366/+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 1829366] Re: [SRU] Bugfix release 1.14.4

[Iain Lane]

** Changed in: gst-libav1.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gst-plugins-base1.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gst-plugins-good1.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gst-plugins-ugly1.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gst-python1.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gst-rtsp-server1.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gstreamer-editing-services1.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: gstreamer-vaapi (Ubuntu)
   Status: New => Fix Released

** Changed in: gst-libav1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gst-libav1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gst-plugins-bad1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gst-plugins-bad1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gst-plugins-base1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gst-plugins-base1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gst-plugins-good1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gst-plugins-good1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gst-plugins-ugly1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gst-plugins-ugly1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gst-python1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gst-python1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gst-rtsp-server1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gst-rtsp-server1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gstreamer-editing-services1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gstreamer-editing-services1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gstreamer-vaapi (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gstreamer-vaapi (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gstreamer1.0 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gstreamer1.0 (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  [SRU]  Bugfix release 1.14.4

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Bionic:
  In Progress
Status in gst-plugins-bad1.0 source package in Bionic:
  In Progress
Status in gst-plugins-base1.0 source package in Bionic:
  In Progress
Status in gst-plugins-good1.0 source package in Bionic:
  In Progress
Status in gst-plugins-ugly1.0 source package in Bionic:
  In Progress
Status in gst-python1.0 source package in Bionic:
  In Progress
Status in gst-rtsp-server1.0 source package in Bionic:
  In Progress
Status in gstreamer-editing-services1.0 source package in Bionic:
  In Progress
Status in gstreamer-vaapi source package in Bionic:
  In Progress
Status in gstreamer1.0 source package in Bionic:
  In Progress

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio
  playback, or could crash any application that tries to use gstreamer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+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 1829366] Re: [SRU] Bugfix release 1.14.4

[Iain Lane]

We can pick that up if it happens. Feel free to ask.

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

Title:
  [SRU]  Bugfix release 1.14.4

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Bionic:
  In Progress
Status in gst-plugins-bad1.0 source package in Bionic:
  In Progress
Status in gst-plugins-base1.0 source package in Bionic:
  In Progress
Status in gst-plugins-good1.0 source package in Bionic:
  In Progress
Status in gst-plugins-ugly1.0 source package in Bionic:
  In Progress
Status in gst-python1.0 source package in Bionic:
  In Progress
Status in gst-rtsp-server1.0 source package in Bionic:
  In Progress
Status in gstreamer-editing-services1.0 source package in Bionic:
  In Progress
Status in gstreamer-vaapi source package in Bionic:
  In Progress
Status in gstreamer1.0 source package in Bionic:
  In Progress

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio
  playback, or could crash any application that tries to use gstreamer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+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 1832458] [NEW] [SRU] 2.60.3

[Iain Lane]

Public bug reported:

[ Description ]

Upstream have release 2.60.3 in the 2.60 series

[ QA ]

Upstream release, so QA already performed by maintainers

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

Make sure no autopkgtests are regressed by this upload. Suggestion for
something explicit to test would be epiphany on secure websites.

[ Regression potential ]

A broken glib-networking could affect various applications' ability to
use networking properly, particularly TLS.

[ Upstream NEWS ]

2.60.3 - June 9, 2019
=

- Fix clobbering of the thread-default main context after certificate
  verification failure during async handshakes since 2.60.1 (#85)
- Fix GTlsDatabase initialization failures in OpenSSL backend due to
  uninitialized memory use
- Fix minor leak of ALPN protocols

2.60.2 - May 2, 2019


- OpenSSL backend now defaults to system trust store (#62)
- Fix client auth failure error with GnuTLS 3.6.7 (#70)

** Affects: glib-networking (Ubuntu)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Affects: glib-networking (Ubuntu Disco)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Also affects: glib-networking (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: glib-networking (Ubuntu)
   Status: New => In Progress

** Changed in: glib-networking (Ubuntu Disco)
   Status: New => In Progress

** Changed in: glib-networking (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: glib-networking (Ubuntu Disco)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  [SRU] 2.60.3

Status in glib-networking package in Ubuntu:
  In Progress
Status in glib-networking source package in Disco:
  In Progress

Bug description:
  [ Description ]

  Upstream have release 2.60.3 in the 2.60 series

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Make sure no autopkgtests are regressed by this upload. Suggestion for
  something explicit to test would be epiphany on secure websites.

  [ Regression potential ]

  A broken glib-networking could affect various applications' ability to
  use networking properly, particularly TLS.

  [ Upstream NEWS ]

  2.60.3 - June 9, 2019
  =

  - Fix clobbering of the thread-default main context after certificate
verification failure during async handshakes since 2.60.1 (#85)
  - Fix GTlsDatabase initialization failures in OpenSSL backend due to
uninitialized memory use
  - Fix minor leak of ALPN protocols

  2.60.2 - May 2, 2019
  

  - OpenSSL backend now defaults to system trust store (#62)
  - Fix client auth failure error with GnuTLS 3.6.7 (#70)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1832458/+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 1832457] [NEW] [SRU] 2.60.4

[Iain Lane]

Public bug reported:

[ Description ]

New stable release in the 2.60 series.

[ QA ]

Upstream release, so QA already performed by maintainers

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

This upload will trigger many autopkgtests that we expect to not be
regressed by this upload.

Pretty much all parts of GNOME use GLib, so test anything in the desktop
that you can.

[ Regression potential ]

Various fixes in multiple places so multiple apps could be affected.

[ Upstream NEWS ]

Overview of changes in GLib 2.60.4
==

* Fixes to improved network status detection with NetworkManager (#1788)

* Leak fixes to some `glib-genmarshal` generated code (#1793)

* Further fixes to the Happy Eyeballs (RFC 8305) implementation (!865)

* File system permissions fix to clamp down permissions in a small time window
  when copying files (CVE-2019-12450, !876)

* Bugs fixed:
 - #1755 Please revert #535 gmacros: Try to use the standard __func__ first in 
G_STRFUNC
 - #1788 GNetworkMonitor claims I am offline
 - #1792 glib-genmarshal generated valist marshal does not respect static scope 
for some types
 - #1793 glib-genmarshal generates wrong code for va marshaler for VARIANT type
 - #1795 Fix mingw32 CI on older branches
 - !865 gnetworkaddress: fix "happy eyeballs" logic
 - !878 Backport !876 “gfile: Limit access to files when copying” to glib-2-60

Overview of changes in GLib 2.60.3
==

* Various fixes to small key/value support in `GHashTable` (#1749,
#1780)

* Bugs fixed:
 - #1747 Critical in g_socket_client_async_connect_complete
 - #1749 New GHashTable implementation confuses valgrind
 - #1759 test_month_names: assertion failed
 - #1771 GNetworkAddressAddressEnumerator unsafely modifies cache in 
GNetworkAddress
 - #1774 Leaks in gsocketclient.c connection code
 - #1776 glib/date test fails
 - #1780 GDB pretty-printer for GHashTable no longer works
 - !815 Merge branch 'wip/tingping/socketclient-cancel-2' into 'master'
 - !816 Backport !814 “gschema.dtd: Add target attribute to alias” to glib-2-60
 - !826 Backport !824 “gsocketclient: Fix a leak in the connection code” to 
glib-2-60
 - !829 Backport !828 “build: Fix a typo in the test whether _NL_ABALTMON_n is 
supported” to glib-2-60
 - !834 Backport !823 "gnetworkaddress: Fix parallel enumerations interfering 
with eachother" to glib-2-60
 - !838 Backport !835 “Fix typo in German translation” to glib-2-60
 - !841 Backport !839 “tests: Update month name check for Greek locale” to 
glib-2-60
 - !844 Backport !840 “ghash: Disable small-arrays under valgrind” to glib-2-60
 - !846 Backport !845 “Fixing g_format_size_full() on Windows-x64” to glib-2-60
 - !855 Backport !848 (more GHashTable fixes) to glib-2-60
 - !858 Backport !852 “Update gdb pretty-printer for GHashTable” to glib-2-60

* Translation updates:
 - German

Overview of changes in GLib 2.60.2
==

* Fix crash when displaying notifications on macOS (!786)

* Improve network status detection with NetworkManager (!781)

* Bugs fixed:
 - !790 glib/gconstructor.h: Include stdlib.h for MSVC builds
 - !793 Backport !786: “cocoanotificationbackend: do not release readonly 
property” to glib-2-60
 - !803 Backport !781 “gnetworkmonitornm: Fix network available detection” to 
glib-2-60

* Translation updates:
 - Catalan

Overview of changes in GLib 2.60.1
==

* Fix documentation for `gdbus-tool wait` to use correct units

* Bugs fixed:
 - #1709 GResource generation test incompatible with stable LLVM on Linux
 - #1725 gosxappinfo.h is not installed on macOS
 - #1737 gdbus-tool wait command timeout argument incorrect unit reference
 - !711 socket: Fix annotation for flags in g_socket_receive_message
 - !722 Backport codegen: Fix use of uninitialised variable from !721 to 
glib-2-60
 - !727 Backport !719 “Handle an UNKNOWN NetworkManager connectivity as NONE” 
to glib-2-60
 - !729 Backport !728 “gsocket: Remove (type) annotation from flags arguments” 
to glib-2-60
 - !758 gdbusaddress, win32: backport using cwd for running rundll32
 - !775 meson: Hotfix for iconv detection on macOS

* Translation updates:
 - Basque
 - Dutch

** Affects: glib2.0 (Ubuntu)
     Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Affects: glib2.0 (Ubuntu Disco)
     Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Description changed:

  [ Description ]
  
  New stable release in the 2.60 series.
  
  [ QA ]
  
  Upstream release, so QA already performed by maintainers
  
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
  
  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.
  
  Pretty much all parts of GNOME use GLib, so test anything in the desktop
  that you can.
  
  [ Regression potential ]
  
  Various fixes in multiple places so multi

[Touch-packages] [Bug 1832457] Re: [SRU] 2.60.4

[Iain Lane]

disco in queue, will sync eoan once lp picks it up

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

Title:
  [SRU] 2.60.4

Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 source package in Disco:
  In Progress

Bug description:
  [ Description ]

  New stable release in the 2.60 series.

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can.

  [ Regression potential ]

  Various fixes in multiple places so multiple apps could be affected.

  [ Upstream NEWS ]

  Overview of changes in GLib 2.60.4
  ==

  * Fixes to improved network status detection with NetworkManager
  (#1788)

  * Leak fixes to some `glib-genmarshal` generated code (#1793)

  * Further fixes to the Happy Eyeballs (RFC 8305) implementation (!865)

  * File system permissions fix to clamp down permissions in a small time window
    when copying files (CVE-2019-12450, !876)

  * Bugs fixed:
   - #1755 Please revert #535 gmacros: Try to use the standard __func__ first 
in G_STRFUNC
   - #1788 GNetworkMonitor claims I am offline
   - #1792 glib-genmarshal generated valist marshal does not respect static 
scope for some types
   - #1793 glib-genmarshal generates wrong code for va marshaler for VARIANT 
type
   - #1795 Fix mingw32 CI on older branches
   - !865 gnetworkaddress: fix "happy eyeballs" logic
   - !878 Backport !876 “gfile: Limit access to files when copying” to glib-2-60

  Overview of changes in GLib 2.60.3
  ==

  * Various fixes to small key/value support in `GHashTable` (#1749,
  #1780)

  * Bugs fixed:
   - #1747 Critical in g_socket_client_async_connect_complete
   - #1749 New GHashTable implementation confuses valgrind
   - #1759 test_month_names: assertion failed
   - #1771 GNetworkAddressAddressEnumerator unsafely modifies cache in 
GNetworkAddress
   - #1774 Leaks in gsocketclient.c connection code
   - #1776 glib/date test fails
   - #1780 GDB pretty-printer for GHashTable no longer works
   - !815 Merge branch 'wip/tingping/socketclient-cancel-2' into 'master'
   - !816 Backport !814 “gschema.dtd: Add target attribute to alias” to 
glib-2-60
   - !826 Backport !824 “gsocketclient: Fix a leak in the connection code” to 
glib-2-60
   - !829 Backport !828 “build: Fix a typo in the test whether _NL_ABALTMON_n 
is supported” to glib-2-60
   - !834 Backport !823 "gnetworkaddress: Fix parallel enumerations interfering 
with eachother" to glib-2-60
   - !838 Backport !835 “Fix typo in German translation” to glib-2-60
   - !841 Backport !839 “tests: Update month name check for Greek locale” to 
glib-2-60
   - !844 Backport !840 “ghash: Disable small-arrays under valgrind” to 
glib-2-60
   - !846 Backport !845 “Fixing g_format_size_full() on Windows-x64” to 
glib-2-60
   - !855 Backport !848 (more GHashTable fixes) to glib-2-60
   - !858 Backport !852 “Update gdb pretty-printer for GHashTable” to glib-2-60

  * Translation updates:
   - German

  Overview of changes in GLib 2.60.2
  ==

  * Fix crash when displaying notifications on macOS (!786)

  * Improve network status detection with NetworkManager (!781)

  * Bugs fixed:
   - !790 glib/gconstructor.h: Include stdlib.h for MSVC builds
   - !793 Backport !786: “cocoanotificationbackend: do not release readonly 
property” to glib-2-60
   - !803 Backport !781 “gnetworkmonitornm: Fix network available detection” to 
glib-2-60

  * Translation updates:
   - Catalan

  Overview of changes in GLib 2.60.1
  ==

  * Fix documentation for `gdbus-tool wait` to use correct units

  * Bugs fixed:
   - #1709 GResource generation test incompatible with stable LLVM on Linux
   - #1725 gosxappinfo.h is not installed on macOS
   - #1737 gdbus-tool wait command timeout argument incorrect unit reference
   - !711 socket: Fix annotation for flags in g_socket_receive_message
   - !722 Backport codegen: Fix use of uninitialised variable from !721 to 
glib-2-60
   - !727 Backport !719 “Handle an UNKNOWN NetworkManager connectivity as NONE” 
to glib-2-60
   - !729 Backport !728 “gsocket: Remove (type) annotation from flags 
arguments” to glib-2-60
   - !758 gdbusaddress, win32: backport using cwd for running rundll32
   - !775 meson: Hotfix for iconv detection on macOS

  * Translation updates:
   - Basque
   - Dutch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1832457/+subscriptions

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

[Touch-packages] [Bug 1832458] Re: [SRU] 2.60.3

[Iain Lane]

disco in queue, will sync eoan once lp picks it up

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

Title:
  [SRU] 2.60.3

Status in glib-networking package in Ubuntu:
  In Progress
Status in glib-networking source package in Disco:
  In Progress

Bug description:
  [ Description ]

  Upstream have release 2.60.3 in the 2.60 series

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Make sure no autopkgtests are regressed by this upload. Suggestion for
  something explicit to test would be epiphany on secure websites.

  [ Regression potential ]

  A broken glib-networking could affect various applications' ability to
  use networking properly, particularly TLS.

  [ Upstream NEWS ]

  2.60.3 - June 9, 2019
  =

  - Fix clobbering of the thread-default main context after certificate
verification failure during async handshakes since 2.60.1 (#85)
  - Fix GTlsDatabase initialization failures in OpenSSL backend due to
uninitialized memory use
  - Fix minor leak of ALPN protocols

  2.60.2 - May 2, 2019
  

  - OpenSSL backend now defaults to system trust store (#62)
  - Fix client auth failure error with GnuTLS 3.6.7 (#70)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1832458/+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 1832457] Re: [SRU] 2.60.4

[Iain Lane]

** Changed in: glib2.0 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [SRU] 2.60.4

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Disco:
  In Progress

Bug description:
  [ Description ]

  New stable release in the 2.60 series.

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can.

  [ Regression potential ]

  Various fixes in multiple places so multiple apps could be affected.

  [ Upstream NEWS ]

  Overview of changes in GLib 2.60.4
  ==

  * Fixes to improved network status detection with NetworkManager
  (#1788)

  * Leak fixes to some `glib-genmarshal` generated code (#1793)

  * Further fixes to the Happy Eyeballs (RFC 8305) implementation (!865)

  * File system permissions fix to clamp down permissions in a small time window
    when copying files (CVE-2019-12450, !876)

  * Bugs fixed:
   - #1755 Please revert #535 gmacros: Try to use the standard __func__ first 
in G_STRFUNC
   - #1788 GNetworkMonitor claims I am offline
   - #1792 glib-genmarshal generated valist marshal does not respect static 
scope for some types
   - #1793 glib-genmarshal generates wrong code for va marshaler for VARIANT 
type
   - #1795 Fix mingw32 CI on older branches
   - !865 gnetworkaddress: fix "happy eyeballs" logic
   - !878 Backport !876 “gfile: Limit access to files when copying” to glib-2-60

  Overview of changes in GLib 2.60.3
  ==

  * Various fixes to small key/value support in `GHashTable` (#1749,
  #1780)

  * Bugs fixed:
   - #1747 Critical in g_socket_client_async_connect_complete
   - #1749 New GHashTable implementation confuses valgrind
   - #1759 test_month_names: assertion failed
   - #1771 GNetworkAddressAddressEnumerator unsafely modifies cache in 
GNetworkAddress
   - #1774 Leaks in gsocketclient.c connection code
   - #1776 glib/date test fails
   - #1780 GDB pretty-printer for GHashTable no longer works
   - !815 Merge branch 'wip/tingping/socketclient-cancel-2' into 'master'
   - !816 Backport !814 “gschema.dtd: Add target attribute to alias” to 
glib-2-60
   - !826 Backport !824 “gsocketclient: Fix a leak in the connection code” to 
glib-2-60
   - !829 Backport !828 “build: Fix a typo in the test whether _NL_ABALTMON_n 
is supported” to glib-2-60
   - !834 Backport !823 "gnetworkaddress: Fix parallel enumerations interfering 
with eachother" to glib-2-60
   - !838 Backport !835 “Fix typo in German translation” to glib-2-60
   - !841 Backport !839 “tests: Update month name check for Greek locale” to 
glib-2-60
   - !844 Backport !840 “ghash: Disable small-arrays under valgrind” to 
glib-2-60
   - !846 Backport !845 “Fixing g_format_size_full() on Windows-x64” to 
glib-2-60
   - !855 Backport !848 (more GHashTable fixes) to glib-2-60
   - !858 Backport !852 “Update gdb pretty-printer for GHashTable” to glib-2-60

  * Translation updates:
   - German

  Overview of changes in GLib 2.60.2
  ==

  * Fix crash when displaying notifications on macOS (!786)

  * Improve network status detection with NetworkManager (!781)

  * Bugs fixed:
   - !790 glib/gconstructor.h: Include stdlib.h for MSVC builds
   - !793 Backport !786: “cocoanotificationbackend: do not release readonly 
property” to glib-2-60
   - !803 Backport !781 “gnetworkmonitornm: Fix network available detection” to 
glib-2-60

  * Translation updates:
   - Catalan

  Overview of changes in GLib 2.60.1
  ==

  * Fix documentation for `gdbus-tool wait` to use correct units

  * Bugs fixed:
   - #1709 GResource generation test incompatible with stable LLVM on Linux
   - #1725 gosxappinfo.h is not installed on macOS
   - #1737 gdbus-tool wait command timeout argument incorrect unit reference
   - !711 socket: Fix annotation for flags in g_socket_receive_message
   - !722 Backport codegen: Fix use of uninitialised variable from !721 to 
glib-2-60
   - !727 Backport !719 “Handle an UNKNOWN NetworkManager connectivity as NONE” 
to glib-2-60
   - !729 Backport !728 “gsocket: Remove (type) annotation from flags 
arguments” to glib-2-60
   - !758 gdbusaddress, win32: backport using cwd for running rundll32
   - !775 meson: Hotfix for iconv detection on macOS

  * Translation updates:
   - Basque
   - Dutch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1832457/+subscriptions

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

[Touch-packages] [Bug 1832457] Re: [SRU] 2.60.4

[Iain Lane]

It was clear that the sync was what I was going for (comment #1), so it
would have been nice if the SRU would have been accepted by the way.
Brian could have synced it if necessary as well. Now we have to wait for
another go-round.

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

Title:
  [SRU] 2.60.4

Status in glib2.0 package in Ubuntu:
  Fix Committed
Status in glib2.0 source package in Disco:
  In Progress

Bug description:
  [ Description ]

  New stable release in the 2.60 series.

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can.

  [ Regression potential ]

  Various fixes in multiple places so multiple apps could be affected.

  [ Upstream NEWS ]

  Overview of changes in GLib 2.60.4
  ==

  * Fixes to improved network status detection with NetworkManager
  (#1788)

  * Leak fixes to some `glib-genmarshal` generated code (#1793)

  * Further fixes to the Happy Eyeballs (RFC 8305) implementation (!865)

  * File system permissions fix to clamp down permissions in a small time window
    when copying files (CVE-2019-12450, !876)

  * Bugs fixed:
   - #1755 Please revert #535 gmacros: Try to use the standard __func__ first 
in G_STRFUNC
   - #1788 GNetworkMonitor claims I am offline
   - #1792 glib-genmarshal generated valist marshal does not respect static 
scope for some types
   - #1793 glib-genmarshal generates wrong code for va marshaler for VARIANT 
type
   - #1795 Fix mingw32 CI on older branches
   - !865 gnetworkaddress: fix "happy eyeballs" logic
   - !878 Backport !876 “gfile: Limit access to files when copying” to glib-2-60

  Overview of changes in GLib 2.60.3
  ==

  * Various fixes to small key/value support in `GHashTable` (#1749,
  #1780)

  * Bugs fixed:
   - #1747 Critical in g_socket_client_async_connect_complete
   - #1749 New GHashTable implementation confuses valgrind
   - #1759 test_month_names: assertion failed
   - #1771 GNetworkAddressAddressEnumerator unsafely modifies cache in 
GNetworkAddress
   - #1774 Leaks in gsocketclient.c connection code
   - #1776 glib/date test fails
   - #1780 GDB pretty-printer for GHashTable no longer works
   - !815 Merge branch 'wip/tingping/socketclient-cancel-2' into 'master'
   - !816 Backport !814 “gschema.dtd: Add target attribute to alias” to 
glib-2-60
   - !826 Backport !824 “gsocketclient: Fix a leak in the connection code” to 
glib-2-60
   - !829 Backport !828 “build: Fix a typo in the test whether _NL_ABALTMON_n 
is supported” to glib-2-60
   - !834 Backport !823 "gnetworkaddress: Fix parallel enumerations interfering 
with eachother" to glib-2-60
   - !838 Backport !835 “Fix typo in German translation” to glib-2-60
   - !841 Backport !839 “tests: Update month name check for Greek locale” to 
glib-2-60
   - !844 Backport !840 “ghash: Disable small-arrays under valgrind” to 
glib-2-60
   - !846 Backport !845 “Fixing g_format_size_full() on Windows-x64” to 
glib-2-60
   - !855 Backport !848 (more GHashTable fixes) to glib-2-60
   - !858 Backport !852 “Update gdb pretty-printer for GHashTable” to glib-2-60

  * Translation updates:
   - German

  Overview of changes in GLib 2.60.2
  ==

  * Fix crash when displaying notifications on macOS (!786)

  * Improve network status detection with NetworkManager (!781)

  * Bugs fixed:
   - !790 glib/gconstructor.h: Include stdlib.h for MSVC builds
   - !793 Backport !786: “cocoanotificationbackend: do not release readonly 
property” to glib-2-60
   - !803 Backport !781 “gnetworkmonitornm: Fix network available detection” to 
glib-2-60

  * Translation updates:
   - Catalan

  Overview of changes in GLib 2.60.1
  ==

  * Fix documentation for `gdbus-tool wait` to use correct units

  * Bugs fixed:
   - #1709 GResource generation test incompatible with stable LLVM on Linux
   - #1725 gosxappinfo.h is not installed on macOS
   - #1737 gdbus-tool wait command timeout argument incorrect unit reference
   - !711 socket: Fix annotation for flags in g_socket_receive_message
   - !722 Backport codegen: Fix use of uninitialised variable from !721 to 
glib-2-60
   - !727 Backport !719 “Handle an UNKNOWN NetworkManager connectivity as NONE” 
to glib-2-60
   - !729 Backport !728 “gsocket: Remove (type) annotation from flags 
arguments” to glib-2-60
   - !758 gdbusaddress, win32: backport using cwd for running rundll32
   - !775 meson: Hotfix for iconv detection on macOS

  * Translation updates:
   - Basque
   - Dutch

To manage notifications about this bug go to:
https://bugs.launchpad.net/

[Touch-packages] [Bug 1832457] Re: [SRU] 2.60.4

[Iain Lane]

It's there now. The sync must have failed.

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

Title:
  [SRU] 2.60.4

Status in glib2.0 package in Ubuntu:
  Fix Committed
Status in glib2.0 source package in Disco:
  In Progress

Bug description:
  [ Description ]

  New stable release in the 2.60 series.

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can.

  [ Regression potential ]

  Various fixes in multiple places so multiple apps could be affected.

  [ Upstream NEWS ]

  Overview of changes in GLib 2.60.4
  ==

  * Fixes to improved network status detection with NetworkManager
  (#1788)

  * Leak fixes to some `glib-genmarshal` generated code (#1793)

  * Further fixes to the Happy Eyeballs (RFC 8305) implementation (!865)

  * File system permissions fix to clamp down permissions in a small time window
    when copying files (CVE-2019-12450, !876)

  * Bugs fixed:
   - #1755 Please revert #535 gmacros: Try to use the standard __func__ first 
in G_STRFUNC
   - #1788 GNetworkMonitor claims I am offline
   - #1792 glib-genmarshal generated valist marshal does not respect static 
scope for some types
   - #1793 glib-genmarshal generates wrong code for va marshaler for VARIANT 
type
   - #1795 Fix mingw32 CI on older branches
   - !865 gnetworkaddress: fix "happy eyeballs" logic
   - !878 Backport !876 “gfile: Limit access to files when copying” to glib-2-60

  Overview of changes in GLib 2.60.3
  ==

  * Various fixes to small key/value support in `GHashTable` (#1749,
  #1780)

  * Bugs fixed:
   - #1747 Critical in g_socket_client_async_connect_complete
   - #1749 New GHashTable implementation confuses valgrind
   - #1759 test_month_names: assertion failed
   - #1771 GNetworkAddressAddressEnumerator unsafely modifies cache in 
GNetworkAddress
   - #1774 Leaks in gsocketclient.c connection code
   - #1776 glib/date test fails
   - #1780 GDB pretty-printer for GHashTable no longer works
   - !815 Merge branch 'wip/tingping/socketclient-cancel-2' into 'master'
   - !816 Backport !814 “gschema.dtd: Add target attribute to alias” to 
glib-2-60
   - !826 Backport !824 “gsocketclient: Fix a leak in the connection code” to 
glib-2-60
   - !829 Backport !828 “build: Fix a typo in the test whether _NL_ABALTMON_n 
is supported” to glib-2-60
   - !834 Backport !823 "gnetworkaddress: Fix parallel enumerations interfering 
with eachother" to glib-2-60
   - !838 Backport !835 “Fix typo in German translation” to glib-2-60
   - !841 Backport !839 “tests: Update month name check for Greek locale” to 
glib-2-60
   - !844 Backport !840 “ghash: Disable small-arrays under valgrind” to 
glib-2-60
   - !846 Backport !845 “Fixing g_format_size_full() on Windows-x64” to 
glib-2-60
   - !855 Backport !848 (more GHashTable fixes) to glib-2-60
   - !858 Backport !852 “Update gdb pretty-printer for GHashTable” to glib-2-60

  * Translation updates:
   - German

  Overview of changes in GLib 2.60.2
  ==

  * Fix crash when displaying notifications on macOS (!786)

  * Improve network status detection with NetworkManager (!781)

  * Bugs fixed:
   - !790 glib/gconstructor.h: Include stdlib.h for MSVC builds
   - !793 Backport !786: “cocoanotificationbackend: do not release readonly 
property” to glib-2-60
   - !803 Backport !781 “gnetworkmonitornm: Fix network available detection” to 
glib-2-60

  * Translation updates:
   - Catalan

  Overview of changes in GLib 2.60.1
  ==

  * Fix documentation for `gdbus-tool wait` to use correct units

  * Bugs fixed:
   - #1709 GResource generation test incompatible with stable LLVM on Linux
   - #1725 gosxappinfo.h is not installed on macOS
   - #1737 gdbus-tool wait command timeout argument incorrect unit reference
   - !711 socket: Fix annotation for flags in g_socket_receive_message
   - !722 Backport codegen: Fix use of uninitialised variable from !721 to 
glib-2-60
   - !727 Backport !719 “Handle an UNKNOWN NetworkManager connectivity as NONE” 
to glib-2-60
   - !729 Backport !728 “gsocket: Remove (type) annotation from flags 
arguments” to glib-2-60
   - !758 gdbusaddress, win32: backport using cwd for running rundll32
   - !775 meson: Hotfix for iconv detection on macOS

  * Translation updates:
   - Basque
   - Dutch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1832457/+subscriptions

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

[Touch-packages] [Bug 1832457] Re: [SRU] 2.60.4

[Iain Lane]

I've retried the failing tests, except why3 which I think is just busted
(not glib2.0's fault - good for a badtest?)

Have smoke tested on disco and it seems good to me. I ran the desktop
for a bit, checking the video player, text editor, image viewer and web
browser. Shell itself of course uses GLib too.

desrt might want to test the specific usecase that she had in mind for
this upload. But it seems good to me.

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

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

Title:
  [SRU] 2.60.4

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Disco:
  Fix Committed

Bug description:
  [ Description ]

  New stable release in the 2.60 series.

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can.

  [ Regression potential ]

  Various fixes in multiple places so multiple apps could be affected.

  [ Upstream NEWS ]

  Overview of changes in GLib 2.60.4
  ==

  * Fixes to improved network status detection with NetworkManager
  (#1788)

  * Leak fixes to some `glib-genmarshal` generated code (#1793)

  * Further fixes to the Happy Eyeballs (RFC 8305) implementation (!865)

  * File system permissions fix to clamp down permissions in a small time window
    when copying files (CVE-2019-12450, !876)

  * Bugs fixed:
   - #1755 Please revert #535 gmacros: Try to use the standard __func__ first 
in G_STRFUNC
   - #1788 GNetworkMonitor claims I am offline
   - #1792 glib-genmarshal generated valist marshal does not respect static 
scope for some types
   - #1793 glib-genmarshal generates wrong code for va marshaler for VARIANT 
type
   - #1795 Fix mingw32 CI on older branches
   - !865 gnetworkaddress: fix "happy eyeballs" logic
   - !878 Backport !876 “gfile: Limit access to files when copying” to glib-2-60

  Overview of changes in GLib 2.60.3
  ==

  * Various fixes to small key/value support in `GHashTable` (#1749,
  #1780)

  * Bugs fixed:
   - #1747 Critical in g_socket_client_async_connect_complete
   - #1749 New GHashTable implementation confuses valgrind
   - #1759 test_month_names: assertion failed
   - #1771 GNetworkAddressAddressEnumerator unsafely modifies cache in 
GNetworkAddress
   - #1774 Leaks in gsocketclient.c connection code
   - #1776 glib/date test fails
   - #1780 GDB pretty-printer for GHashTable no longer works
   - !815 Merge branch 'wip/tingping/socketclient-cancel-2' into 'master'
   - !816 Backport !814 “gschema.dtd: Add target attribute to alias” to 
glib-2-60
   - !826 Backport !824 “gsocketclient: Fix a leak in the connection code” to 
glib-2-60
   - !829 Backport !828 “build: Fix a typo in the test whether _NL_ABALTMON_n 
is supported” to glib-2-60
   - !834 Backport !823 "gnetworkaddress: Fix parallel enumerations interfering 
with eachother" to glib-2-60
   - !838 Backport !835 “Fix typo in German translation” to glib-2-60
   - !841 Backport !839 “tests: Update month name check for Greek locale” to 
glib-2-60
   - !844 Backport !840 “ghash: Disable small-arrays under valgrind” to 
glib-2-60
   - !846 Backport !845 “Fixing g_format_size_full() on Windows-x64” to 
glib-2-60
   - !855 Backport !848 (more GHashTable fixes) to glib-2-60
   - !858 Backport !852 “Update gdb pretty-printer for GHashTable” to glib-2-60

  * Translation updates:
   - German

  Overview of changes in GLib 2.60.2
  ==

  * Fix crash when displaying notifications on macOS (!786)

  * Improve network status detection with NetworkManager (!781)

  * Bugs fixed:
   - !790 glib/gconstructor.h: Include stdlib.h for MSVC builds
   - !793 Backport !786: “cocoanotificationbackend: do not release readonly 
property” to glib-2-60
   - !803 Backport !781 “gnetworkmonitornm: Fix network available detection” to 
glib-2-60

  * Translation updates:
   - Catalan

  Overview of changes in GLib 2.60.1
  ==

  * Fix documentation for `gdbus-tool wait` to use correct units

  * Bugs fixed:
   - #1709 GResource generation test incompatible with stable LLVM on Linux
   - #1725 gosxappinfo.h is not installed on macOS
   - #1737 gdbus-tool wait command timeout argument incorrect unit reference
   - !711 socket: Fix annotation for flags in g_socket_receive_message
   - !722 Backport codegen: Fix use of uninitialised variable from !721 to 
glib-2-60
   - !727 Backport !719 “Handle an UNKNOWN NetworkManager connectivity as NONE” 
to glib-2-60
   - !729 Backport !728 “gsocket: R

[Touch-packages] [Bug 1829366] Re: [SRU] Bugfix release 1.14.4

[Iain Lane]

I've verified these as best as I can. I installed 1.14.4 and played a
load of different filetypes:

  - mp3
  - ogg
  - flac
  - opus
  - mp4 (H.264)

with different codecs, e.g. mpg123, libav, ...

and different players - epiphany, totem, rhythmbox.

I didn't find any regressions.

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

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

Title:
  [SRU]  Bugfix release 1.14.4

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Bionic:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Bionic:
  Fix Committed
Status in gst-plugins-base1.0 source package in Bionic:
  In Progress
Status in gst-plugins-good1.0 source package in Bionic:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Bionic:
  Fix Committed
Status in gst-python1.0 source package in Bionic:
  Fix Committed
Status in gst-rtsp-server1.0 source package in Bionic:
  Fix Committed
Status in gstreamer-editing-services1.0 source package in Bionic:
  Fix Committed
Status in gstreamer-vaapi source package in Bionic:
  Fix Committed
Status in gstreamer1.0 source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio
  playback, or could crash any application that tries to use gstreamer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+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 1832123] Re: [SRU] Bugfix release 1.14.5

[Iain Lane]

Amr Ibrahim, are you working on this

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

Title:
  [SRU] Bugfix release 1.14.5

Status in gst-libav1.0 package in Ubuntu:
  New
Status in gst-omx package in Ubuntu:
  New
Status in gst-plugins-bad1.0 package in Ubuntu:
  New
Status in gst-plugins-base1.0 package in Ubuntu:
  New
Status in gst-plugins-good1.0 package in Ubuntu:
  New
Status in gst-plugins-ugly1.0 package in Ubuntu:
  New
Status in gst-python1.0 package in Ubuntu:
  New
Status in gst-rtsp-server1.0 package in Ubuntu:
  New
Status in gstreamer-editing-services1.0 package in Ubuntu:
  New
Status in gstreamer-vaapi package in Ubuntu:
  New
Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio playback, or 
could crash any application that tries to use gstreamer.
  ---

  Highlighted bugfixes in 1.14.5

  GStreamer core

  -   aggregator: take the pad lock around queue gap event removal
  -   aggregator: don’t leak gap buffer when out of segment
  -   buffer: fix possible memory corruption in gst_buffer_foreach_meta() when 
removing metas
  -   bus: Make removing of signal/bus watches thread-safe
  -   bus: Don’t allow removing signal watches with gst_bus_remove_watch()
  -   controlbinding: Check if the weak pointer was cleared before explicitly 
removing it
  -   ptp clock: Wait for ANNOUNCE before selecting a master; increase 
tolerance for late follow-up and delay-resp
  -   segment: Allow stop == -1 in gst_segment_to_running_time() and negative 
rate
  -   g-i: annotations fixes

  gst-plugins-base

  -   audioconvert: fix endianness conversion for unpacked formats (e.g. 
S24_32BE)
  -   audioringbuffer: Fix wrong memcpy address when reordering channels
  -   decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup
  -   glviewconvert: fix output when a transformation matrix is used
  -   glupload: prevent segfault when updating caps
  -   gl/egl: Determine correct format on dmabuf import
  -   glupload: dmabuf: be explicit about gl formats used
  -   id3tag: validate the year from v1 tags before passing to GstDateTime
  -   rtpbasepayload: fix sequence numbers when using buffer lists
  -   rtspconnection: fix security issue, potential heap overflow 
(CVE-2019-9928)
  -   rtspconnection: fix GError set over the top of a previous GError
  -   rtspconnection: do not duplicate authentication headers
  -   subparse: don’t assert when failing to parse subrip timestamp
  -   video: various convert sample frame fixes
  -   video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, 
A420_10LE/BE to BGRA/RGBA which created corrupted output
  -   video-format: Fix GBRA_10/12 alpha channel pixel strides

  gst-plugins-good

  -   flv: Use 8kHz sample rate for alaw/mulaw audio
  -   flvdemux: Do not error out if the first added and chained pad is not 
linked
  -   flvmux: try harder to make sure timestamps are always increasing
  -   gdkpixbufdec: output a TIME segment which is what’s expected for raw video
  -   matroskademux: fix handling of MS ACM audio
  -   matroska: fix handling of FlagInterlaced
  -   pulsesink: Deal with not being able to convert a format to caps
  -   rtph265depay, rtph264depay; aggregation packet marker handling fixes
  -   rtpmp4gdepay: detect broken senders who send AAC with ADTS frames
  -   rtprawdepay: keep buffer pool around when flushing/seeking
  -   rtpssrcdemux: Forward serialized events to all pads
  -   qmlglsink: Handle OPENGL header guard changes
  -   qtdemux: fix track language code parsing; ignore corrupted CTTS box
  -   qtmux: Correctly set tkhd width/height to the display size
  -   splitmuxsink: various timecode meta handling fixes
  -   splitmuxsink: make work with audio-only encoders as muxers, e.g. wavenc
  -   v4l2sink: fix pool-less allocation query handling
  -   v4l2dec/enc: fix use after free when handling events
  -   vpx: Fix build against libvpx 1.8
  -   webmmux: allow resolutions above 4096

  gst-plugins-ugly

  -   sid: Fix cross-compilation by using AC_TRY_LINK instead of AC_TRY_RUN
  -   x264: Only enable dynamic loading code for x264 before v253

  gst-plugins-bad

  -   assrender: fix disappearing subtitles when seeking back in time
  -   decklinkvideosink: fix segfault when audiosink is closed before videosink
  -   decklinkvideosrc: respect pixel format property even if mode is s