BTW - I'm running Kubuntu, and doing the upgrade with kubuntu-devel-
release-upgrade works just fine without needing to update appstream to
0.12.2 first.

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

Title:
  g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

Status in AppStream:
  Fix Released
Status in appstream package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Invalid
Status in appstream package in Debian:
  Fix Released

Bug description:
  When running

    sudo apt update

  in a terminal I sometimes see the following message printed within the
  output.

    (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047:
  g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

  This started happening today (5th August). Otherwise apt update and
  apt upgrade seem to correctly update the system.

  ------------------------------

  https://gitlab.gnome.org/GNOME/glib/issues/1480

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libglib2.0-0 2.57.2-1
  ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9
  Uname: Linux 4.17.0-6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug  5 17:52:41 2018
  InstallationDate: Installed on 2018-07-12 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/appstream/+bug/1785498/+subscriptions

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

Reply via email to