sbuild (Debian sbuild) 0.78.1 (09 February 2019) on mjolnir.einval.org

+==============================================================================+
| alarm-clock-applet 0.4.1-3 (i386)            Wed, 08 Mar 2023 11:01:44 +0000 |
+==============================================================================+

Package: alarm-clock-applet
Version: 0.4.1-3
Source Version: 0.4.1-3
Distribution: unstable
Machine Architecture: arm64
Host Architecture: i386
Build Architecture: arm64
Build Profiles: cross nocheck
Build Type: any

I: NOTICE: Log filtering will replace 'var/run/schroot/mount/crossqa-sid-b7bad164-852d-4afd-988a-fd41d73c56b9' with '<<CHROOT>>'
I: NOTICE: Log filtering will replace 'build/alarm-clock-applet-L9HzwY/resolver-TZmwUJ' with '<<RESOLVERDIR>>'

+------------------------------------------------------------------------------+
| Update chroot                                                                |
+------------------------------------------------------------------------------+

Get:1 http://mirror.einval.org/debian sid InRelease [180 kB]
Ign:2 http://mirror.einval.org/debian sid/main Sources.diff/Index
Ign:3 http://mirror.einval.org/debian sid/main arm64 Packages.diff/Index
Get:2 http://mirror.einval.org/debian sid/main Sources.diff/Index [63.6 kB]
Ign:2 http://mirror.einval.org/debian sid/main Sources.diff/Index
Ign:3 http://mirror.einval.org/debian sid/main arm64 Packages.diff/Index
Get:4 http://mirror.einval.org/debian sid/main i386 Packages [9313 kB]
Get:5 http://mirror.einval.org/debian sid/main Sources [10.1 MB]
Get:6 http://mirror.einval.org/debian sid/main arm64 Packages [9287 kB]
Fetched 28.8 MB in 8s (3515 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

+------------------------------------------------------------------------------+
| Fetch source files                                                           |
+------------------------------------------------------------------------------+


Check APT
---------

Checking available source versions...

Download source files with APT
------------------------------

Reading package lists...
NOTICE: 'alarm-clock-applet' packaging is maintained in the 'Git' version control system at:
https://salsa.debian.org/debian/alarm-clock-applet.git
Please use:
git clone https://salsa.debian.org/debian/alarm-clock-applet.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 218 kB of source archives.
Get:1 http://mirror.einval.org/debian sid/main alarm-clock-applet 0.4.1-3 (dsc) [2308 B]
Get:2 http://mirror.einval.org/debian sid/main alarm-clock-applet 0.4.1-3 (tar) [209 kB]
Get:3 http://mirror.einval.org/debian sid/main alarm-clock-applet 0.4.1-3 (diff) [7048 B]
Fetched 218 kB in 0s (3503 kB/s)
Download complete and in download only mode
I: NOTICE: Log filtering will replace 'build/alarm-clock-applet-L9HzwY/alarm-clock-applet-0.4.1' with '<<PKGBUILDDIR>>'
I: NOTICE: Log filtering will replace 'build/alarm-clock-applet-L9HzwY' with '<<BUILDDIR>>'

+------------------------------------------------------------------------------+
| Install package build dependencies                                           |
+------------------------------------------------------------------------------+


Setup apt archive
-----------------

Merged Build-Depends: debhelper-compat (= 12), cmake (>= 3.10), intltool (>= 0.40), libgtk-3-dev, libgstreamer1.0-dev, libnotify-dev, libayatana-appindicator3-dev, libglib2.0-dev, libgconf2-dev (>= 2.8.0), gnome-icon-theme (>= 2.15.91), libxml2-dev, gnome-common, libc-dev, libstdc++-dev, build-essential:arm64, fakeroot:arm64, crossbuild-essential-i386:arm64, libc-dev:i386, libstdc++-dev:i386
Filtered Build-Depends: debhelper-compat (= 12), cmake (>= 3.10), intltool (>= 0.40), libgtk-3-dev, libgstreamer1.0-dev, libnotify-dev, libayatana-appindicator3-dev, libglib2.0-dev, libgconf2-dev (>= 2.8.0), gnome-icon-theme (>= 2.15.91), libxml2-dev, gnome-common, libc-dev, libstdc++-dev, build-essential:arm64, fakeroot:arm64, crossbuild-essential-i386:arm64, libc-dev:i386, libstdc++-dev:i386
dpkg-deb: building package 'sbuild-build-depends-main-dummy' in '/<<RESOLVERDIR>>/apt_archive/sbuild-build-depends-main-dummy.deb'.
Ign:1 copy:/<<RESOLVERDIR>>/apt_archive ./ InRelease
Get:2 copy:/<<RESOLVERDIR>>/apt_archive ./ Release [957 B]
Ign:3 copy:/<<RESOLVERDIR>>/apt_archive ./ Release.gpg
Get:4 copy:/<<RESOLVERDIR>>/apt_archive ./ Sources [507 B]
Get:5 copy:/<<RESOLVERDIR>>/apt_archive ./ Packages [600 B]
Fetched 2064 B in 0s (50.8 kB/s)
Reading package lists...
Reading package lists...

Install main build dependencies (apt-based resolver)
----------------------------------------------------

Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  adwaita-icon-theme at-spi2-common autoconf autoconf-archive automake
  autopoint autotools-dev binutils-i686-linux-gnu bsdextrautils
  ca-certificates cmake cmake-data cpp-12-i686-linux-gnu cpp-i686-linux-gnu
  cross-config crossbuild-essential-i386 dbus dbus-bin dbus-daemon
  dbus-session-bus-common dbus-system-bus-common dbus-user-session
  dconf-gsettings-backend dconf-service debhelper dh-autoreconf
  dh-strip-nondeterminism dmsetup dpkg-cross dwz file fontconfig
  fontconfig-config fonts-dejavu-core g++-12-i686-linux-gnu g++-i686-linux-gnu
  gcc-12-base:i386 gcc-12-cross-base gcc-12-i686-linux-gnu
  gcc-12-i686-linux-gnu-base gcc-i686-linux-gnu gconf-service gconf2
  gconf2-common gettext gettext-base gir1.2-atk-1.0:i386 gir1.2-atspi-2.0:i386
  gir1.2-ayatanaappindicator3-0.1:i386 gir1.2-ayatanaido3-0.4:i386
  gir1.2-dbusmenu-glib-0.4:i386 gir1.2-freedesktop:i386 gir1.2-gconf-2.0:i386
  gir1.2-gdkpixbuf-2.0:i386 gir1.2-glib-2.0:i386 gir1.2-gstreamer-1.0:i386
  gir1.2-gtk-2.0:i386 gir1.2-gtk-3.0:i386 gir1.2-harfbuzz-0.0:i386
  gir1.2-notify-0.7:i386 gir1.2-pango-1.0:i386 gnome-common gnome-icon-theme
  groff-base gtk-update-icon-cache hicolor-icon-theme icu-devtools intltool
  intltool-debian libapparmor1 libarchive-zip-perl libarchive13 libargon2-1
  libasan8:i386 libasan8-i386-cross libatk-bridge2.0-0:i386
  libatk-bridge2.0-dev:i386 libatk1.0-0:i386 libatk1.0-dev:i386
  libatomic1:i386 libatomic1-i386-cross libatspi2.0-0:i386
  libatspi2.0-dev:i386 libavahi-client3:i386 libavahi-common-data:i386
  libavahi-common3:i386 libayatana-appindicator3-1:i386
  libayatana-appindicator3-dev:i386 libayatana-ido3-0.4-0:i386
  libayatana-ido3-dev:i386 libayatana-indicator3-7:i386
  libayatana-indicator3-dev:i386 libblkid-dev:i386 libblkid1:i386
  libbrotli-dev:i386 libbrotli1 libbrotli1:i386 libbsd0 libbsd0:i386
  libbz2-1.0:i386 libc6:i386 libc6-dev:i386 libc6-dev-i386-cross
  libc6-i386-cross libcairo-gobject2 libcairo-gobject2:i386
  libcairo-script-interpreter2:i386 libcairo2 libcairo2:i386
  libcairo2-dev:i386 libcap2:i386 libcap2-bin libclone-perl libcolord2:i386
  libcom-err2:i386 libconfig-auto-perl libconfig-inifiles-perl
  libcrypt-dev:i386 libcrypt1:i386 libcryptsetup12 libcups2:i386 libcurl4
  libdatrie-dev:i386 libdatrie1 libdatrie1:i386 libdbus-1-3 libdbus-1-3:i386
  libdbus-1-dev:i386 libdbus-glib-1-2 libdbus-glib-1-2:i386
  libdbusmenu-glib-dev:i386 libdbusmenu-glib4:i386 libdbusmenu-gtk3-4:i386
  libdconf1 libdebhelper-perl libdebian-dpkgcross-perl libdeflate-dev:i386
  libdeflate0 libdeflate0:i386 libdevmapper1.02.1 libdrm-amdgpu1:i386
  libdrm-common libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386
  libdrm2:i386 libdw-dev:i386 libdw1:i386 libedit2:i386 libegl-dev:i386
  libegl-mesa0:i386 libegl1:i386 libegl1-mesa-dev:i386 libelf-dev:i386 libelf1
  libelf1:i386 libencode-locale-perl libepoxy-dev:i386 libepoxy0:i386
  libexpat1 libexpat1:i386 libexpat1-dev:i386 libfdisk1 libffi-dev:i386
  libffi8:i386 libfile-homedir-perl libfile-listing-perl
  libfile-stripnondeterminism-perl libfile-which-perl libfontconfig-dev:i386
  libfontconfig1 libfontconfig1:i386 libfreetype-dev:i386 libfreetype6
  libfreetype6:i386 libfribidi-dev:i386 libfribidi0 libfribidi0:i386
  libgbm1:i386 libgcc-12-dev:i386 libgcc-12-dev-i386-cross libgcc-s1:i386
  libgcc-s1-i386-cross libgconf-2-4 libgconf-2-4:i386 libgconf2-dev:i386
  libgcrypt20:i386 libgdk-pixbuf-2.0-0 libgdk-pixbuf-2.0-0:i386
  libgdk-pixbuf-2.0-dev:i386 libgdk-pixbuf2.0-bin libgdk-pixbuf2.0-common
  libgirepository-1.0-1:i386 libgl-dev:i386 libgl1:i386 libgl1-mesa-dri:i386
  libglapi-mesa:i386 libgles-dev:i386 libgles1:i386 libgles2:i386 libglib2.0-0
  libglib2.0-0:i386 libglib2.0-bin libglib2.0-data libglib2.0-dev:i386
  libglib2.0-dev-bin libglvnd-core-dev:i386 libglvnd-dev:i386 libglvnd0:i386
  libglx-dev:i386 libglx-mesa0:i386 libglx0:i386 libgmp10:i386
  libgnutls30:i386 libgomp1:i386 libgomp1-i386-cross libgpg-error0:i386
  libgraphite2-3 libgraphite2-3:i386 libgraphite2-dev:i386
  libgssapi-krb5-2:i386 libgstreamer1.0-0:i386 libgstreamer1.0-dev:i386
  libgtk-3-0:i386 libgtk-3-common libgtk-3-dev:i386 libgtk2.0-0:i386
  libgtk2.0-common libgtk2.0-dev:i386 libharfbuzz-dev:i386
  libharfbuzz-gobject0:i386 libharfbuzz-icu0:i386 libharfbuzz-subset0:i386
  libharfbuzz0b libharfbuzz0b:i386 libhogweed6:i386 libhtml-parser-perl
  libhtml-tagset-perl libhtml-tree-perl libhttp-cookies-perl libhttp-date-perl
  libhttp-message-perl libhttp-negotiate-perl libice-dev:i386 libice6:i386
  libicu-dev:i386 libicu72 libicu72:i386 libidn2-0:i386 libio-html-perl
  libio-socket-ssl-perl libio-string-perl libip4tc2 libitm1:i386
  libitm1-i386-cross libjbig-dev:i386 libjbig0 libjbig0:i386 libjpeg-dev:i386
  libjpeg62-turbo libjpeg62-turbo:i386 libjpeg62-turbo-dev:i386 libjson-c5
  libjsoncpp25 libk5crypto3:i386 libkeyutils1:i386 libkmod2 libkrb5-3:i386
  libkrb5support0:i386 liblcms2-2:i386 libldap-2.5-0 liblerc-dev:i386 liblerc4
  liblerc4:i386 libllvm15:i386 liblocale-gettext-perl liblwp-mediatypes-perl
  liblwp-protocol-https-perl liblz4-1:i386 liblzma-dev:i386 liblzma5:i386
  liblzo2-2:i386 libmagic-mgc libmagic1 libmd0:i386 libmount-dev:i386
  libmount1:i386 libncursesw6 libnet-http-perl libnet-ssleay-perl
  libnettle8:i386 libnghttp2-14 libnotify-dev:i386 libnotify4:i386
  libnsl-dev:i386 libnsl2:i386 libopengl-dev:i386 libopengl0:i386
  libp11-kit0:i386 libpam-systemd libpango-1.0-0 libpango-1.0-0:i386
  libpango1.0-dev:i386 libpangocairo-1.0-0 libpangocairo-1.0-0:i386
  libpangoft2-1.0-0 libpangoft2-1.0-0:i386 libpangoxft-1.0-0
  libpangoxft-1.0-0:i386 libpciaccess0:i386 libpcre2-16-0:i386
  libpcre2-32-0:i386 libpcre2-8-0:i386 libpcre2-dev:i386 libpcre2-posix3:i386
  libpipeline1 libpixman-1-0 libpixman-1-0:i386 libpixman-1-dev:i386
  libpkgconf3 libpng-dev:i386 libpng16-16 libpng16-16:i386 libproc2-0 libpsl5
  libpthread-stubs0-dev:i386 libpython3-stdlib libpython3.11-minimal
  libpython3.11-stdlib libquadmath0:i386 libquadmath0-i386-cross libreadline8
  libregexp-ipv6-perl librhash0 librsvg2-2 librsvg2-common librtmp1 libsasl2-2
  libsasl2-modules-db libselinux1:i386 libselinux1-dev:i386 libsensors-config
  libsensors5:i386 libsepol-dev:i386 libsepol2:i386 libsm-dev:i386 libsm6:i386
  libsqlite3-0 libssh2-1 libssl3:i386 libstdc++-12-dev:i386
  libstdc++-12-dev-i386-cross libstdc++6:i386 libstdc++6-i386-cross
  libsub-override-perl libsystemd-shared libsystemd0:i386 libtasn1-6:i386
  libthai-data libthai-dev:i386 libthai0 libthai0:i386 libtiff-dev:i386
  libtiff6 libtiff6:i386 libtiffxx6:i386 libtimedate-perl libtinfo6:i386
  libtirpc-dev:i386 libtirpc3:i386 libtool libtry-tiny-perl libubsan1:i386
  libubsan1-i386-cross libuchardet0 libudev1:i386 libunistring2:i386
  libunwind-dev:i386 libunwind8:i386 liburi-perl libuuid1:i386 libuv1
  libwayland-bin libwayland-client0:i386 libwayland-cursor0:i386
  libwayland-dev:i386 libwayland-egl1:i386 libwayland-server0:i386
  libwebp-dev:i386 libwebp7 libwebp7:i386 libwebpdemux2:i386 libwebpmux3:i386
  libwww-perl libwww-robotrules-perl libx11-6 libx11-6:i386 libx11-data
  libx11-dev:i386 libx11-xcb1:i386 libxau-dev:i386 libxau6 libxau6:i386
  libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386
  libxcb-randr0:i386 libxcb-render0 libxcb-render0:i386
  libxcb-render0-dev:i386 libxcb-shm0 libxcb-shm0:i386 libxcb-shm0-dev:i386
  libxcb-sync1:i386 libxcb-xfixes0:i386 libxcb1 libxcb1:i386 libxcb1-dev:i386
  libxcomposite-dev:i386 libxcomposite1:i386 libxcursor-dev:i386
  libxcursor1:i386 libxdamage-dev:i386 libxdamage1:i386 libxdmcp-dev:i386
  libxdmcp6 libxdmcp6:i386 libxext-dev:i386 libxext6 libxext6:i386
  libxfixes-dev:i386 libxfixes3:i386 libxft-dev:i386 libxft2 libxft2:i386
  libxi-dev:i386 libxi6:i386 libxinerama-dev:i386 libxinerama1:i386
  libxkbcommon-dev:i386 libxkbcommon0:i386 libxml-libxml-perl
  libxml-namespacesupport-perl libxml-parser-perl libxml-sax-base-perl
  libxml-sax-perl libxml-simple-perl libxml2 libxml2:i386 libxml2-dev:i386
  libxml2-utils libxrandr-dev:i386 libxrandr2:i386 libxrender-dev:i386
  libxrender1 libxrender1:i386 libxshmfence1:i386 libxtst-dev:i386
  libxtst6:i386 libxxf86vm1:i386 libyaml-perl libz3-4:i386 libzstd-dev:i386
  libzstd1:i386 linux-libc-dev:i386 linux-libc-dev-i386-cross m4 man-db
  media-types netbase openssl pango1.0-tools perl-openssl-defaults pkg-config
  pkg-config:i386 pkgconf pkgconf:i386 pkgconf-bin po-debconf procps psmisc
  python3 python3-distutils python3-lib2to3 python3-minimal python3.11
  python3.11-minimal readline-common sensible-utils sgml-base shared-mime-info
  systemd systemd-sysv ucf uuid-dev:i386 wayland-protocols x11-common
  x11proto-dev xkb-data xml-core xorg-sgml-doctools xtrans-dev zlib1g:i386
  zlib1g-dev:i386
Suggested packages:
  gnu-standards autoconf-doc binutils-doc cmake-doc cmake-format
  elpa-cmake-mode ninja-build gcc-12-locales cpp-12-doc cpp-doc dh-make
  binutils-multiarch g++-12-multilib-i686-linux-gnu gcc-12-doc
  gcc-12-multilib-i686-linux-gnu manpages-dev flex bison gdb-i686-linux-gnu
  gcc-doc gconf-defaults-service gettext-doc libasprintf-dev libgettextpo-dev
  groff lrzip glibc-doc:i386 libc-l10n:i386 locales:i386 libnss-nis:i386
  libnss-nisplus:i386 manpages-dev:i386 libcairo2-doc:i386 colord:i386
  cups-common:i386 libdatrie-doc:i386 freetype2-doc:i386 rng-tools:i386
  low-memory-monitor low-memory-monitor:i386 libgirepository1.0-dev:i386
  libglib2.0-doc:i386 gnutls-bin:i386 libgraphite2-utils:i386 krb5-doc:i386
  krb5-user:i386 gstreamer1.0-tools:i386 gstreamer1.0-doc:i386 gvfs:i386
  libgtk-3-doc:i386 libgtk2.0-doc:i386 libdata-dump-perl libice-doc:i386
  icu-doc:i386 liblcms2-utils:i386 libcrypt-ssleay-perl liblzma-doc:i386
  cryptsetup-bin:i386 notification-daemon:i386 libpango1.0-doc:i386
  pciutils:i386 librsvg2-bin lm-sensors lm-sensors:i386 libsm-doc:i386
  libstdc++-12-doc:i386 libthai-doc:i386 libtool-doc gfortran
  | fortran95-compiler gcj-jdk libsub-name-perl libbusiness-isbn-perl
  libwayland-doc:i386 libauthen-ntlm-perl libx11-doc:i386 libxcb-doc:i386
  libxext-doc:i386 libyaml-shell-perl m4-doc apparmor less www-browser
  graphicsmagick libmail-box-perl python3-doc python3-tk python3-venv
  python3.11-venv python3.11-doc binfmt-support readline-doc sgml-base-doc
  systemd-container systemd-homed systemd-userdbd systemd-boot
  systemd-resolved libfido2-1 libqrencode4 libtss2-esys-3.0.2-0 libtss2-mu0
  libtss2-rc0 polkitd | policykit-1
Recommended packages:
  curl | wget | lynx at-spi2-core:i386 libpam-cap libarchive-cpio-perl
  libgconf2-doc:i386 xdg-user-dirs xdg-user-dirs:i386 libgpg-error-l10n:i386
  libgtk-3-bin:i386 librsvg2-common:i386 libgtk-3-0 libgail-common:i386
  libgtk2.0-bin:i386 libgtk2.0-0 libhtml-format-perl krb5-locales:i386
  libldap-common libgpm2 libpng-tools:i386 publicsuffix libsasl2-modules
  libltdl-dev uuid-runtime:i386 libdata-dump-perl libhtml-form-perl
  libhttp-daemon-perl libmailtools-perl libxml-sax-expat-perl
  libyaml-libyaml-perl | libyaml-syck-perl libmail-sendmail-perl
  systemd-timesyncd | time-daemon libnss-systemd
The following NEW packages will be installed:
  adwaita-icon-theme at-spi2-common autoconf autoconf-archive automake
  autopoint autotools-dev binutils-i686-linux-gnu bsdextrautils
  ca-certificates cmake cmake-data cpp-12-i686-linux-gnu cpp-i686-linux-gnu
  cross-config crossbuild-essential-i386 dbus dbus-bin dbus-daemon
  dbus-session-bus-common dbus-system-bus-common dbus-user-session
  dconf-gsettings-backend dconf-service debhelper dh-autoreconf
  dh-strip-nondeterminism dmsetup dpkg-cross dwz file fontconfig
  fontconfig-config fonts-dejavu-core g++-12-i686-linux-gnu g++-i686-linux-gnu
  gcc-12-base:i386 gcc-12-cross-base gcc-12-i686-linux-gnu
  gcc-12-i686-linux-gnu-base gcc-i686-linux-gnu gconf-service gconf2
  gconf2-common gettext gettext-base gir1.2-atk-1.0:i386 gir1.2-atspi-2.0:i386
  gir1.2-ayatanaappindicator3-0.1:i386 gir1.2-ayatanaido3-0.4:i386
  gir1.2-dbusmenu-glib-0.4:i386 gir1.2-freedesktop:i386 gir1.2-gconf-2.0:i386
  gir1.2-gdkpixbuf-2.0:i386 gir1.2-glib-2.0:i386 gir1.2-gstreamer-1.0:i386
  gir1.2-gtk-2.0:i386 gir1.2-gtk-3.0:i386 gir1.2-harfbuzz-0.0:i386
  gir1.2-notify-0.7:i386 gir1.2-pango-1.0:i386 gnome-common gnome-icon-theme
  groff-base gtk-update-icon-cache hicolor-icon-theme icu-devtools intltool
  intltool-debian libapparmor1 libarchive-zip-perl libarchive13 libargon2-1
  libasan8:i386 libasan8-i386-cross libatk-bridge2.0-0:i386
  libatk-bridge2.0-dev:i386 libatk1.0-0:i386 libatk1.0-dev:i386
  libatomic1:i386 libatomic1-i386-cross libatspi2.0-0:i386
  libatspi2.0-dev:i386 libavahi-client3:i386 libavahi-common-data:i386
  libavahi-common3:i386 libayatana-appindicator3-1:i386
  libayatana-appindicator3-dev:i386 libayatana-ido3-0.4-0:i386
  libayatana-ido3-dev:i386 libayatana-indicator3-7:i386
  libayatana-indicator3-dev:i386 libblkid-dev:i386 libblkid1:i386
  libbrotli-dev:i386 libbrotli1 libbrotli1:i386 libbsd0 libbsd0:i386
  libbz2-1.0:i386 libc6:i386 libc6-dev:i386 libc6-dev-i386-cross
  libc6-i386-cross libcairo-gobject2 libcairo-gobject2:i386
  libcairo-script-interpreter2:i386 libcairo2 libcairo2:i386
  libcairo2-dev:i386 libcap2:i386 libcap2-bin libclone-perl libcolord2:i386
  libcom-err2:i386 libconfig-auto-perl libconfig-inifiles-perl
  libcrypt-dev:i386 libcrypt1:i386 libcryptsetup12 libcups2:i386 libcurl4
  libdatrie-dev:i386 libdatrie1 libdatrie1:i386 libdbus-1-3 libdbus-1-3:i386
  libdbus-1-dev:i386 libdbus-glib-1-2 libdbus-glib-1-2:i386
  libdbusmenu-glib-dev:i386 libdbusmenu-glib4:i386 libdbusmenu-gtk3-4:i386
  libdconf1 libdebhelper-perl libdebian-dpkgcross-perl libdeflate-dev:i386
  libdeflate0 libdeflate0:i386 libdevmapper1.02.1 libdrm-amdgpu1:i386
  libdrm-common libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386
  libdrm2:i386 libdw-dev:i386 libdw1:i386 libedit2:i386 libegl-dev:i386
  libegl-mesa0:i386 libegl1:i386 libegl1-mesa-dev:i386 libelf-dev:i386 libelf1
  libelf1:i386 libencode-locale-perl libepoxy-dev:i386 libepoxy0:i386
  libexpat1 libexpat1:i386 libexpat1-dev:i386 libfdisk1 libffi-dev:i386
  libffi8:i386 libfile-homedir-perl libfile-listing-perl
  libfile-stripnondeterminism-perl libfile-which-perl libfontconfig-dev:i386
  libfontconfig1 libfontconfig1:i386 libfreetype-dev:i386 libfreetype6
  libfreetype6:i386 libfribidi-dev:i386 libfribidi0 libfribidi0:i386
  libgbm1:i386 libgcc-12-dev:i386 libgcc-12-dev-i386-cross libgcc-s1:i386
  libgcc-s1-i386-cross libgconf-2-4 libgconf-2-4:i386 libgconf2-dev:i386
  libgcrypt20:i386 libgdk-pixbuf-2.0-0 libgdk-pixbuf-2.0-0:i386
  libgdk-pixbuf-2.0-dev:i386 libgdk-pixbuf2.0-bin libgdk-pixbuf2.0-common
  libgirepository-1.0-1:i386 libgl-dev:i386 libgl1:i386 libgl1-mesa-dri:i386
  libglapi-mesa:i386 libgles-dev:i386 libgles1:i386 libgles2:i386 libglib2.0-0
  libglib2.0-0:i386 libglib2.0-bin libglib2.0-data libglib2.0-dev:i386
  libglib2.0-dev-bin libglvnd-core-dev:i386 libglvnd-dev:i386 libglvnd0:i386
  libglx-dev:i386 libglx-mesa0:i386 libglx0:i386 libgmp10:i386
  libgnutls30:i386 libgomp1:i386 libgomp1-i386-cross libgpg-error0:i386
  libgraphite2-3 libgraphite2-3:i386 libgraphite2-dev:i386
  libgssapi-krb5-2:i386 libgstreamer1.0-0:i386 libgstreamer1.0-dev:i386
  libgtk-3-0:i386 libgtk-3-common libgtk-3-dev:i386 libgtk2.0-0:i386
  libgtk2.0-common libgtk2.0-dev:i386 libharfbuzz-dev:i386
  libharfbuzz-gobject0:i386 libharfbuzz-icu0:i386 libharfbuzz-subset0:i386
  libharfbuzz0b libharfbuzz0b:i386 libhogweed6:i386 libhtml-parser-perl
  libhtml-tagset-perl libhtml-tree-perl libhttp-cookies-perl libhttp-date-perl
  libhttp-message-perl libhttp-negotiate-perl libice-dev:i386 libice6:i386
  libicu-dev:i386 libicu72 libicu72:i386 libidn2-0:i386 libio-html-perl
  libio-socket-ssl-perl libio-string-perl libip4tc2 libitm1:i386
  libitm1-i386-cross libjbig-dev:i386 libjbig0 libjbig0:i386 libjpeg-dev:i386
  libjpeg62-turbo libjpeg62-turbo:i386 libjpeg62-turbo-dev:i386 libjson-c5
  libjsoncpp25 libk5crypto3:i386 libkeyutils1:i386 libkmod2 libkrb5-3:i386
  libkrb5support0:i386 liblcms2-2:i386 libldap-2.5-0 liblerc-dev:i386 liblerc4
  liblerc4:i386 libllvm15:i386 liblocale-gettext-perl liblwp-mediatypes-perl
  liblwp-protocol-https-perl liblz4-1:i386 liblzma-dev:i386 liblzma5:i386
  liblzo2-2:i386 libmagic-mgc libmagic1 libmd0:i386 libmount-dev:i386
  libmount1:i386 libncursesw6 libnet-http-perl libnet-ssleay-perl
  libnettle8:i386 libnghttp2-14 libnotify-dev:i386 libnotify4:i386
  libnsl-dev:i386 libnsl2:i386 libopengl-dev:i386 libopengl0:i386
  libp11-kit0:i386 libpam-systemd libpango-1.0-0 libpango-1.0-0:i386
  libpango1.0-dev:i386 libpangocairo-1.0-0 libpangocairo-1.0-0:i386
  libpangoft2-1.0-0 libpangoft2-1.0-0:i386 libpangoxft-1.0-0
  libpangoxft-1.0-0:i386 libpciaccess0:i386 libpcre2-16-0:i386
  libpcre2-32-0:i386 libpcre2-8-0:i386 libpcre2-dev:i386 libpcre2-posix3:i386
  libpipeline1 libpixman-1-0 libpixman-1-0:i386 libpixman-1-dev:i386
  libpkgconf3 libpng-dev:i386 libpng16-16 libpng16-16:i386 libproc2-0 libpsl5
  libpthread-stubs0-dev:i386 libpython3-stdlib libpython3.11-minimal
  libpython3.11-stdlib libquadmath0:i386 libquadmath0-i386-cross libreadline8
  libregexp-ipv6-perl librhash0 librsvg2-2 librsvg2-common librtmp1 libsasl2-2
  libsasl2-modules-db libselinux1:i386 libselinux1-dev:i386 libsensors-config
  libsensors5:i386 libsepol-dev:i386 libsepol2:i386 libsm-dev:i386 libsm6:i386
  libsqlite3-0 libssh2-1 libssl3:i386 libstdc++-12-dev:i386
  libstdc++-12-dev-i386-cross libstdc++6:i386 libstdc++6-i386-cross
  libsub-override-perl libsystemd-shared libsystemd0:i386 libtasn1-6:i386
  libthai-data libthai-dev:i386 libthai0 libthai0:i386 libtiff-dev:i386
  libtiff6 libtiff6:i386 libtiffxx6:i386 libtimedate-perl libtinfo6:i386
  libtirpc-dev:i386 libtirpc3:i386 libtool libtry-tiny-perl libubsan1:i386
  libubsan1-i386-cross libuchardet0 libudev1:i386 libunistring2:i386
  libunwind-dev:i386 libunwind8:i386 liburi-perl libuuid1:i386 libuv1
  libwayland-bin libwayland-client0:i386 libwayland-cursor0:i386
  libwayland-dev:i386 libwayland-egl1:i386 libwayland-server0:i386
  libwebp-dev:i386 libwebp7 libwebp7:i386 libwebpdemux2:i386 libwebpmux3:i386
  libwww-perl libwww-robotrules-perl libx11-6 libx11-6:i386 libx11-data
  libx11-dev:i386 libx11-xcb1:i386 libxau-dev:i386 libxau6 libxau6:i386
  libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386
  libxcb-randr0:i386 libxcb-render0 libxcb-render0:i386
  libxcb-render0-dev:i386 libxcb-shm0 libxcb-shm0:i386 libxcb-shm0-dev:i386
  libxcb-sync1:i386 libxcb-xfixes0:i386 libxcb1 libxcb1:i386 libxcb1-dev:i386
  libxcomposite-dev:i386 libxcomposite1:i386 libxcursor-dev:i386
  libxcursor1:i386 libxdamage-dev:i386 libxdamage1:i386 libxdmcp-dev:i386
  libxdmcp6 libxdmcp6:i386 libxext-dev:i386 libxext6 libxext6:i386
  libxfixes-dev:i386 libxfixes3:i386 libxft-dev:i386 libxft2 libxft2:i386
  libxi-dev:i386 libxi6:i386 libxinerama-dev:i386 libxinerama1:i386
  libxkbcommon-dev:i386 libxkbcommon0:i386 libxml-libxml-perl
  libxml-namespacesupport-perl libxml-parser-perl libxml-sax-base-perl
  libxml-sax-perl libxml-simple-perl libxml2 libxml2:i386 libxml2-dev:i386
  libxml2-utils libxrandr-dev:i386 libxrandr2:i386 libxrender-dev:i386
  libxrender1 libxrender1:i386 libxshmfence1:i386 libxtst-dev:i386
  libxtst6:i386 libxxf86vm1:i386 libyaml-perl libz3-4:i386 libzstd-dev:i386
  libzstd1:i386 linux-libc-dev:i386 linux-libc-dev-i386-cross m4 man-db
  media-types netbase openssl pango1.0-tools perl-openssl-defaults pkg-config
  pkg-config:i386 pkgconf pkgconf:i386 pkgconf-bin po-debconf procps psmisc
  python3 python3-distutils python3-lib2to3 python3-minimal python3.11
  python3.11-minimal readline-common sbuild-build-depends-main-dummy:i386
  sensible-utils sgml-base shared-mime-info systemd systemd-sysv ucf
  uuid-dev:i386 wayland-protocols x11-common x11proto-dev xkb-data xml-core
  xorg-sgml-doctools xtrans-dev zlib1g:i386 zlib1g-dev:i386
0 upgraded, 506 newly installed, 0 to remove and 0 not upgraded.
Need to get 278 MB of archives.
After this operation, 1089 MB of additional disk space will be used.
Get:1 copy:/<<RESOLVERDIR>>/apt_archive ./ sbuild-build-depends-main-dummy 0.invalid.0 [1028 B]
Get:2 http://mirror.einval.org/debian sid/main arm64 libargon2-1 arm64 0~20190702-0.1 [18.7 kB]
Get:3 http://mirror.einval.org/debian sid/main arm64 dmsetup arm64 2:1.02.185-2 [75.2 kB]
Get:4 http://mirror.einval.org/debian sid/main arm64 libdevmapper1.02.1 arm64 2:1.02.185-2 [115 kB]
Get:5 http://mirror.einval.org/debian sid/main arm64 libjson-c5 arm64 0.16-2 [42.9 kB]
Get:6 http://mirror.einval.org/debian sid/main arm64 libcryptsetup12 arm64 2:2.6.1-2 [204 kB]
Get:7 http://mirror.einval.org/debian sid/main arm64 libfdisk1 arm64 2.38.1-5 [181 kB]
Get:8 http://mirror.einval.org/debian sid/main arm64 libkmod2 arm64 30+20221128-1 [54.4 kB]
Get:9 http://mirror.einval.org/debian sid/main arm64 libapparmor1 arm64 3.0.8-3 [40.3 kB]
Get:10 http://mirror.einval.org/debian sid/main arm64 libip4tc2 arm64 1.8.9-2 [18.5 kB]
Get:11 http://mirror.einval.org/debian sid/main arm64 libsystemd-shared arm64 252.6-1 [1501 kB]
Get:12 http://mirror.einval.org/debian sid/main arm64 systemd arm64 252.6-1 [2817 kB]
Get:13 http://mirror.einval.org/debian sid/main arm64 systemd-sysv arm64 252.6-1 [41.5 kB]
Get:14 http://mirror.einval.org/debian sid/main arm64 libdbus-1-3 arm64 1.14.6-1 [191 kB]
Get:15 http://mirror.einval.org/debian sid/main arm64 dbus-bin arm64 1.14.6-1 [102 kB]
Get:16 http://mirror.einval.org/debian sid/main arm64 dbus-session-bus-common all 1.14.6-1 [76.6 kB]
Get:17 http://mirror.einval.org/debian sid/main arm64 libexpat1 arm64 2.5.0-1 [84.8 kB]
Get:18 http://mirror.einval.org/debian sid/main arm64 dbus-daemon arm64 1.14.6-1 [173 kB]
Get:19 http://mirror.einval.org/debian sid/main arm64 dbus-system-bus-common all 1.14.6-1 [77.7 kB]
Get:20 http://mirror.einval.org/debian sid/main arm64 dbus arm64 1.14.6-1 [94.5 kB]
Get:21 http://mirror.einval.org/debian sid/main arm64 autoconf-archive all 20220903-3 [775 kB]
Get:22 http://mirror.einval.org/debian sid/main arm64 liblocale-gettext-perl arm64 1.07-5 [15.1 kB]
Get:23 http://mirror.einval.org/debian sid/main arm64 libpython3.11-minimal arm64 3.11.2-4 [806 kB]
Get:24 http://mirror.einval.org/debian sid/main arm64 python3.11-minimal arm64 3.11.2-4 [1857 kB]
Get:25 http://mirror.einval.org/debian sid/main arm64 python3-minimal arm64 3.11.2-1 [26.0 kB]
Get:26 http://mirror.einval.org/debian sid/main arm64 media-types all 10.0.0 [26.1 kB]
Get:27 http://mirror.einval.org/debian sid/main arm64 libncursesw6 arm64 6.4-2 [122 kB]
Get:28 http://mirror.einval.org/debian sid/main arm64 readline-common all 8.2-1.3 [69.0 kB]
Get:29 http://mirror.einval.org/debian sid/main arm64 libreadline8 arm64 8.2-1.3 [155 kB]
Get:30 http://mirror.einval.org/debian sid/main arm64 libsqlite3-0 arm64 3.40.1-1 [783 kB]
Get:31 http://mirror.einval.org/debian sid/main arm64 libpython3.11-stdlib arm64 3.11.2-4 [1744 kB]
Get:32 http://mirror.einval.org/debian sid/main arm64 python3.11 arm64 3.11.2-4 [572 kB]
Get:33 http://mirror.einval.org/debian sid/main arm64 libpython3-stdlib arm64 3.11.2-1 [9012 B]
Get:34 http://mirror.einval.org/debian sid/main arm64 python3 arm64 3.11.2-1 [26.0 kB]
Get:35 http://mirror.einval.org/debian sid/main arm64 sgml-base all 1.31 [15.4 kB]
Get:36 http://mirror.einval.org/debian sid/main arm64 netbase all 6.4 [12.8 kB]
Get:37 http://mirror.einval.org/debian sid/main arm64 libproc2-0 arm64 2:4.0.3-1 [60.5 kB]
Get:38 http://mirror.einval.org/debian sid/main arm64 procps arm64 2:4.0.3-1 [752 kB]
Get:39 http://mirror.einval.org/debian sid/main arm64 sensible-utils all 0.0.17+nmu1 [19.0 kB]
Get:40 http://mirror.einval.org/debian sid/main arm64 openssl arm64 3.0.8-1 [1373 kB]
Get:41 http://mirror.einval.org/debian sid/main arm64 ca-certificates all 20211016 [156 kB]
Get:42 http://mirror.einval.org/debian sid/main arm64 libmagic-mgc arm64 1:5.44-3 [305 kB]
Get:43 http://mirror.einval.org/debian sid/main arm64 libmagic1 arm64 1:5.44-3 [98.5 kB]
Get:44 http://mirror.einval.org/debian sid/main arm64 file arm64 1:5.44-3 [42.5 kB]
Get:45 http://mirror.einval.org/debian sid/main arm64 gettext-base arm64 0.21-12 [159 kB]
Get:46 http://mirror.einval.org/debian sid/main arm64 libuchardet0 arm64 0.0.7-1 [67.9 kB]
Get:47 http://mirror.einval.org/debian sid/main arm64 groff-base arm64 1.22.4-10 [861 kB]
Get:48 http://mirror.einval.org/debian sid/main arm64 libpam-systemd arm64 252.6-1 [207 kB]
Get:49 http://mirror.einval.org/debian sid/main arm64 bsdextrautils arm64 2.38.1-5 [86.6 kB]
Get:50 http://mirror.einval.org/debian sid/main arm64 libpipeline1 arm64 1.5.7-1 [36.4 kB]
Get:51 http://mirror.einval.org/debian sid/main arm64 man-db arm64 2.11.2-1 [1368 kB]
Get:52 http://mirror.einval.org/debian sid/main arm64 ucf all 3.0043+nmu1 [55.2 kB]
Get:53 http://mirror.einval.org/debian sid/main arm64 hicolor-icon-theme all 0.17-2 [11.4 kB]
Get:54 http://mirror.einval.org/debian sid/main arm64 libgdk-pixbuf2.0-common all 2.42.10+dfsg-1 [306 kB]
Get:55 http://mirror.einval.org/debian sid/main arm64 libglib2.0-0 arm64 2.74.6-1 [1311 kB]
Get:56 http://mirror.einval.org/debian sid/main arm64 libicu72 arm64 72.1-3 [9204 kB]
Get:57 http://mirror.einval.org/debian sid/main arm64 libxml2 arm64 2.9.14+dfsg-1.1+b3 [619 kB]
Get:58 http://mirror.einval.org/debian sid/main arm64 shared-mime-info arm64 2.2-1 [727 kB]
Get:59 http://mirror.einval.org/debian sid/main arm64 libjpeg62-turbo arm64 1:2.1.5-2 [171 kB]
Get:60 http://mirror.einval.org/debian sid/main arm64 libpng16-16 arm64 1.6.39-2 [269 kB]
Get:61 http://mirror.einval.org/debian sid/main arm64 libdeflate0 arm64 1.14-1 [54.3 kB]
Get:62 http://mirror.einval.org/debian sid/main arm64 libjbig0 arm64 2.1-6.1 [30.0 kB]
Get:63 http://mirror.einval.org/debian sid/main arm64 liblerc4 arm64 4.0.0+ds-2 [138 kB]
Get:64 http://mirror.einval.org/debian sid/main arm64 libwebp7 arm64 1.2.4-0.1 [259 kB]
Get:65 http://mirror.einval.org/debian sid/main arm64 libtiff6 arm64 4.5.0-5 [300 kB]
Get:66 http://mirror.einval.org/debian sid/main arm64 libgdk-pixbuf-2.0-0 arm64 2.42.10+dfsg-1+b1 [130 kB]
Get:67 http://mirror.einval.org/debian sid/main arm64 gtk-update-icon-cache arm64 3.24.36-4 [42.0 kB]
Get:68 http://mirror.einval.org/debian sid/main arm64 adwaita-icon-theme all 43-1 [5124 kB]
Get:69 http://mirror.einval.org/debian sid/main arm64 at-spi2-common all 2.46.0-5 [162 kB]
Get:70 http://mirror.einval.org/debian sid/main arm64 m4 arm64 1.4.19-3 [276 kB]
Get:71 http://mirror.einval.org/debian sid/main arm64 autoconf all 2.71-3 [332 kB]
Get:72 http://mirror.einval.org/debian sid/main arm64 autotools-dev all 20220109.1 [51.6 kB]
Get:73 http://mirror.einval.org/debian sid/main arm64 automake all 1:1.16.5-1.3 [823 kB]
Get:74 http://mirror.einval.org/debian sid/main arm64 autopoint all 0.21-12 [495 kB]
Get:75 http://mirror.einval.org/debian sid/main arm64 libarchive13 arm64 3.6.2-1 [316 kB]
Get:76 http://mirror.einval.org/debian sid/main arm64 libbrotli1 arm64 1.0.9-2+b6 [269 kB]
Get:77 http://mirror.einval.org/debian sid/main arm64 libsasl2-modules-db arm64 2.1.28+dfsg-11 [20.6 kB]
Get:78 http://mirror.einval.org/debian sid/main arm64 libsasl2-2 arm64 2.1.28+dfsg-11 [57.8 kB]
Get:79 http://mirror.einval.org/debian sid/main arm64 libldap-2.5-0 arm64 2.5.13+dfsg-5 [171 kB]
Get:80 http://mirror.einval.org/debian sid/main arm64 libnghttp2-14 arm64 1.52.0-1 [67.9 kB]
Get:81 http://mirror.einval.org/debian sid/main arm64 libpsl5 arm64 0.21.2-1 [58.6 kB]
Get:82 http://mirror.einval.org/debian sid/main arm64 librtmp1 arm64 2.4+20151223.gitfa8646d.1-2+b2 [59.4 kB]
Get:83 http://mirror.einval.org/debian sid/main arm64 libssh2-1 arm64 1.10.0-3+b1 [172 kB]
Get:84 http://mirror.einval.org/debian sid/main arm64 libcurl4 arm64 7.88.1-5 [361 kB]
Get:85 http://mirror.einval.org/debian sid/main arm64 libjsoncpp25 arm64 1.9.5-4 [72.3 kB]
Get:86 http://mirror.einval.org/debian sid/main arm64 librhash0 arm64 1.4.3-3 [131 kB]
Get:87 http://mirror.einval.org/debian sid/main arm64 libuv1 arm64 1.44.2-1 [133 kB]
Get:88 http://mirror.einval.org/debian sid/main arm64 cmake-data all 3.25.1-1 [2026 kB]
Get:89 http://mirror.einval.org/debian sid/main arm64 cmake arm64 3.25.1-1 [6806 kB]
Get:90 http://mirror.einval.org/debian sid/main arm64 gcc-12-i686-linux-gnu-base arm64 12.2.0-14cross1 [37.7 kB]
Get:91 http://mirror.einval.org/debian sid/main arm64 cpp-12-i686-linux-gnu arm64 12.2.0-14cross1 [8762 kB]
Get:92 http://mirror.einval.org/debian sid/main arm64 cpp-i686-linux-gnu arm64 4:12.2.0-3 [3968 B]
Get:93 http://mirror.einval.org/debian sid/main arm64 cross-config all 2.6.20 [16.3 kB]
Get:94 http://mirror.einval.org/debian sid/main arm64 binutils-i686-linux-gnu arm64 2.40-2 [2362 kB]
Get:95 http://mirror.einval.org/debian sid/main arm64 gcc-12-cross-base all 12.2.0-14cross1 [33.2 kB]
Get:96 http://mirror.einval.org/debian sid/main arm64 libc6-i386-cross all 2.36-8cross1 [1340 kB]
Get:97 http://mirror.einval.org/debian sid/main arm64 libgcc-s1-i386-cross all 12.2.0-14cross1 [59.6 kB]
Get:98 http://mirror.einval.org/debian sid/main arm64 libgomp1-i386-cross all 12.2.0-14cross1 [118 kB]
Get:99 http://mirror.einval.org/debian sid/main arm64 libitm1-i386-cross all 12.2.0-14cross1 [27.1 kB]
Get:100 http://mirror.einval.org/debian sid/main arm64 libatomic1-i386-cross all 12.2.0-14cross1 [7472 B]
Get:101 http://mirror.einval.org/debian sid/main arm64 libasan8-i386-cross all 12.2.0-14cross1 [2080 kB]
Get:102 http://mirror.einval.org/debian sid/main arm64 libstdc++6-i386-cross all 12.2.0-14cross1 [618 kB]
Get:103 http://mirror.einval.org/debian sid/main arm64 libubsan1-i386-cross all 12.2.0-14cross1 [870 kB]
Get:104 http://mirror.einval.org/debian sid/main arm64 libquadmath0-i386-cross all 12.2.0-14cross1 [227 kB]
Get:105 http://mirror.einval.org/debian sid/main arm64 libgcc-12-dev-i386-cross all 12.2.0-14cross1 [2428 kB]
Get:106 http://mirror.einval.org/debian sid/main arm64 gcc-12-i686-linux-gnu arm64 12.2.0-14cross1 [17.4 MB]
Get:107 http://mirror.einval.org/debian sid/main arm64 gcc-i686-linux-gnu arm64 4:12.2.0-3 [1464 B]
Get:108 http://mirror.einval.org/debian sid/main arm64 linux-libc-dev-i386-cross all 6.1.4-1cross1 [1839 kB]
Get:109 http://mirror.einval.org/debian sid/main arm64 libc6-dev-i386-cross all 2.36-8cross1 [1715 kB]
Get:110 http://mirror.einval.org/debian sid/main arm64 libstdc++-12-dev-i386-cross all 12.2.0-14cross1 [2084 kB]
Get:111 http://mirror.einval.org/debian sid/main arm64 g++-12-i686-linux-gnu arm64 12.2.0-14cross1 [9598 kB]
Get:112 http://mirror.einval.org/debian sid/main arm64 g++-i686-linux-gnu arm64 4:12.2.0-3 [1172 B]
Get:113 http://mirror.einval.org/debian sid/main arm64 libconfig-inifiles-perl all 3.000003-2 [45.9 kB]
Get:114 http://mirror.einval.org/debian sid/main arm64 libio-string-perl all 1.08-4 [12.1 kB]
Get:115 http://mirror.einval.org/debian sid/main arm64 libxml-namespacesupport-perl all 1.12-2 [15.1 kB]
Get:116 http://mirror.einval.org/debian sid/main arm64 libxml-sax-base-perl all 1.09-3 [20.6 kB]
Get:117 http://mirror.einval.org/debian sid/main arm64 libxml-sax-perl all 1.02+dfsg-3 [59.4 kB]
Get:118 http://mirror.einval.org/debian sid/main arm64 libxml-libxml-perl arm64 2.0207+dfsg+really+2.0134-1+b1 [309 kB]
Get:119 http://mirror.einval.org/debian sid/main arm64 libxml-simple-perl all 2.25-2 [69.8 kB]
Get:120 http://mirror.einval.org/debian sid/main arm64 libyaml-perl all 1.30-2 [63.4 kB]
Get:121 http://mirror.einval.org/debian sid/main arm64 libconfig-auto-perl all 0.44-2 [19.2 kB]
Get:122 http://mirror.einval.org/debian sid/main arm64 libfile-which-perl all 1.27-2 [15.1 kB]
Get:123 http://mirror.einval.org/debian sid/main arm64 libfile-homedir-perl all 1.006-2 [42.4 kB]
Get:124 http://mirror.einval.org/debian sid/main arm64 libdebian-dpkgcross-perl all 2.6.20 [15.3 kB]
Get:125 http://mirror.einval.org/debian sid/main arm64 dpkg-cross all 2.6.20 [25.8 kB]
Get:126 http://mirror.einval.org/debian sid/main arm64 crossbuild-essential-i386 all 12.9 [6704 B]
Get:127 http://mirror.einval.org/debian sid/main arm64 dbus-user-session arm64 1.14.6-1 [76.5 kB]
Get:128 http://mirror.einval.org/debian sid/main arm64 libdconf1 arm64 0.40.0-4 [39.2 kB]
Get:129 http://mirror.einval.org/debian sid/main arm64 dconf-service arm64 0.40.0-4 [30.0 kB]
Get:130 http://mirror.einval.org/debian sid/main arm64 dconf-gsettings-backend arm64 0.40.0-4 [26.3 kB]
Get:131 http://mirror.einval.org/debian sid/main arm64 libdebhelper-perl all 13.11.4 [81.2 kB]
Get:132 http://mirror.einval.org/debian sid/main arm64 libtool all 2.4.7-5 [517 kB]
Get:133 http://mirror.einval.org/debian sid/main arm64 dh-autoreconf all 20 [17.1 kB]
Get:134 http://mirror.einval.org/debian sid/main arm64 libarchive-zip-perl all 1.68-1 [104 kB]
Get:135 http://mirror.einval.org/debian sid/main arm64 libsub-override-perl all 0.09-4 [9304 B]
Get:136 http://mirror.einval.org/debian sid/main arm64 libfile-stripnondeterminism-perl all 1.13.1-1 [19.4 kB]
Get:137 http://mirror.einval.org/debian sid/main arm64 dh-strip-nondeterminism all 1.13.1-1 [8620 B]
Get:138 http://mirror.einval.org/debian sid/main arm64 libelf1 arm64 0.188-2.1 [173 kB]
Get:139 http://mirror.einval.org/debian sid/main arm64 dwz arm64 0.15-1 [101 kB]
Get:140 http://mirror.einval.org/debian sid/main arm64 gettext arm64 0.21-12 [1248 kB]
Get:141 http://mirror.einval.org/debian sid/main arm64 intltool-debian all 0.35.0+20060710.6 [22.9 kB]
Get:142 http://mirror.einval.org/debian sid/main arm64 po-debconf all 1.0.21+nmu1 [248 kB]
Get:143 http://mirror.einval.org/debian sid/main arm64 debhelper all 13.11.4 [942 kB]
Get:144 http://mirror.einval.org/debian sid/main arm64 libfreetype6 arm64 2.12.1+dfsg-4 [369 kB]
Get:145 http://mirror.einval.org/debian sid/main arm64 fonts-dejavu-core all 2.37-5 [1068 kB]
Get:146 http://mirror.einval.org/debian sid/main arm64 fontconfig-config arm64 2.14.1-4 [315 kB]
Get:147 http://mirror.einval.org/debian sid/main arm64 libfontconfig1 arm64 2.14.1-4 [381 kB]
Get:148 http://mirror.einval.org/debian sid/main arm64 fontconfig arm64 2.14.1-4 [449 kB]
Get:149 http://mirror.einval.org/debian sid/main i386 gcc-12-base i386 12.2.0-14 [37.5 kB]
Get:150 http://mirror.einval.org/debian sid/main arm64 libdbus-glib-1-2 arm64 0.112-3 [55.2 kB]
Get:151 http://mirror.einval.org/debian sid/main arm64 gconf2-common all 3.2.6-8 [1025 kB]
Get:152 http://mirror.einval.org/debian sid/main arm64 libgconf-2-4 arm64 3.2.6-8 [408 kB]
Get:153 http://mirror.einval.org/debian sid/main arm64 gconf-service arm64 3.2.6-8 [396 kB]
Get:154 http://mirror.einval.org/debian sid/main arm64 psmisc arm64 23.6-1 [257 kB]
Get:155 http://mirror.einval.org/debian sid/main arm64 gconf2 arm64 3.2.6-8 [410 kB]
Get:156 http://mirror.einval.org/debian sid/main i386 libgcc-s1 i386 12.2.0-14 [59.5 kB]
Get:157 http://mirror.einval.org/debian sid/main i386 libc6 i386 2.36-8 [2619 kB]
Get:158 http://mirror.einval.org/debian sid/main i386 libffi8 i386 3.4.4-1 [21.1 kB]
Get:159 http://mirror.einval.org/debian sid/main i386 libblkid1 i386 2.38.1-5 [161 kB]
Get:160 http://mirror.einval.org/debian sid/main i386 libpcre2-8-0 i386 10.42-1 [259 kB]
Get:161 http://mirror.einval.org/debian sid/main i386 libselinux1 i386 3.4-1+b5 [77.5 kB]
Get:162 http://mirror.einval.org/debian sid/main i386 libmount1 i386 2.38.1-5 [177 kB]
Get:163 http://mirror.einval.org/debian sid/main i386 zlib1g i386 1:1.2.13.dfsg-1 [82.6 kB]
Get:164 http://mirror.einval.org/debian sid/main i386 libglib2.0-0 i386 2.74.6-1 [1467 kB]
Get:165 http://mirror.einval.org/debian sid/main i386 libgirepository-1.0-1 i386 1.74.0-3 [108 kB]
Get:166 http://mirror.einval.org/debian sid/main i386 gir1.2-glib-2.0 i386 1.74.0-3 [159 kB]
Get:167 http://mirror.einval.org/debian sid/main i386 libatk1.0-0 i386 2.46.0-5 [49.4 kB]
Get:168 http://mirror.einval.org/debian sid/main i386 gir1.2-atk-1.0 i386 2.46.0-5 [23.7 kB]
Get:169 http://mirror.einval.org/debian sid/main i386 gir1.2-freedesktop i386 1.74.0-3 [37.2 kB]
Get:170 http://mirror.einval.org/debian sid/main i386 libcap2 i386 1:2.66-3 [28.2 kB]
Get:171 http://mirror.einval.org/debian sid/main i386 libgpg-error0 i386 1.46-1 [81.7 kB]
Get:172 http://mirror.einval.org/debian sid/main i386 libgcrypt20 i386 1.10.1-3 [680 kB]
Get:173 http://mirror.einval.org/debian sid/main i386 liblz4-1 i386 1.9.4-1 [65.2 kB]
Get:174 http://mirror.einval.org/debian sid/main i386 liblzma5 i386 5.4.1-0.2 [215 kB]
Get:175 http://mirror.einval.org/debian sid/main i386 libzstd1 i386 1.5.4+dfsg2-3 [274 kB]
Get:176 http://mirror.einval.org/debian sid/main i386 libsystemd0 i386 252.6-1 [351 kB]
Get:177 http://mirror.einval.org/debian sid/main i386 libdbus-1-3 i386 1.14.6-1 [213 kB]
Get:178 http://mirror.einval.org/debian sid/main i386 libxau6 i386 1:1.0.9-1 [20.0 kB]
Get:179 http://mirror.einval.org/debian sid/main i386 libmd0 i386 1.0.4-2 [30.5 kB]
Get:180 http://mirror.einval.org/debian sid/main i386 libbsd0 i386 0.11.7-4 [119 kB]
Get:181 http://mirror.einval.org/debian sid/main i386 libxdmcp6 i386 1:1.1.2-3 [26.7 kB]
Get:182 http://mirror.einval.org/debian sid/main i386 libxcb1 i386 1.15-1 [148 kB]
Get:183 http://mirror.einval.org/debian sid/main arm64 libx11-data all 2:1.8.4-2 [292 kB]
Get:184 http://mirror.einval.org/debian sid/main i386 libx11-6 i386 2:1.8.4-2 [782 kB]
Get:185 http://mirror.einval.org/debian sid/main i386 libxext6 i386 2:1.3.4-1+b1 [55.3 kB]
Get:186 http://mirror.einval.org/debian sid/main i386 libxi6 i386 2:1.8-1+b1 [86.2 kB]
Get:187 http://mirror.einval.org/debian sid/main i386 libatspi2.0-0 i386 2.46.0-5 [79.1 kB]
Get:188 http://mirror.einval.org/debian sid/main i386 gir1.2-atspi-2.0 i386 2.46.0-5 [20.6 kB]
Get:189 http://mirror.einval.org/debian sid/main i386 libjpeg62-turbo i386 1:2.1.5-2 [169 kB]
Get:190 http://mirror.einval.org/debian sid/main i386 libpng16-16 i386 1.6.39-2 [283 kB]
Get:191 http://mirror.einval.org/debian sid/main i386 libdeflate0 i386 1.14-1 [57.5 kB]
Get:192 http://mirror.einval.org/debian sid/main i386 libjbig0 i386 2.1-6.1 [31.6 kB]
Get:193 http://mirror.einval.org/debian sid/main i386 libstdc++6 i386 12.2.0-14 [661 kB]
Get:194 http://mirror.einval.org/debian sid/main i386 liblerc4 i386 4.0.0+ds-2 [181 kB]
Get:195 http://mirror.einval.org/debian sid/main i386 libwebp7 i386 1.2.4-0.1 [293 kB]
Get:196 http://mirror.einval.org/debian sid/main i386 libtiff6 i386 4.5.0-5 [332 kB]
Get:197 http://mirror.einval.org/debian sid/main i386 libgdk-pixbuf-2.0-0 i386 2.42.10+dfsg-1+b1 [147 kB]
Get:198 http://mirror.einval.org/debian sid/main i386 gir1.2-gdkpixbuf-2.0 i386 2.42.10+dfsg-1+b1 [13.5 kB]
Get:199 http://mirror.einval.org/debian sid/main i386 gir1.2-harfbuzz-0.0 i386 6.0.0+dfsg-3 [1579 kB]
Get:200 http://mirror.einval.org/debian sid/main i386 libfribidi0 i386 1.0.8-2.1 [65.6 kB]
Get:201 http://mirror.einval.org/debian sid/main i386 libbrotli1 i386 1.0.9-2+b6 [275 kB]
Get:202 http://mirror.einval.org/debian sid/main i386 libfreetype6 i386 2.12.1+dfsg-4 [410 kB]
Get:203 http://mirror.einval.org/debian sid/main i386 libgraphite2-3 i386 1.3.14-1 [84.0 kB]
Get:204 http://mirror.einval.org/debian sid/main i386 libharfbuzz0b i386 6.0.0+dfsg-3 [1966 kB]
Get:205 http://mirror.einval.org/debian sid/main arm64 libthai-data all 0.1.29-1 [176 kB]
Get:206 http://mirror.einval.org/debian sid/main i386 libdatrie1 i386 0.2.13-2+b1 [45.0 kB]
Get:207 http://mirror.einval.org/debian sid/main i386 libthai0 i386 0.1.29-1 [58.6 kB]
Get:208 http://mirror.einval.org/debian sid/main i386 libpango-1.0-0 i386 1.50.12+ds-1 [220 kB]
Get:209 http://mirror.einval.org/debian sid/main i386 libexpat1 i386 2.5.0-1 [103 kB]
Get:210 http://mirror.einval.org/debian sid/main i386 libfontconfig1 i386 2.14.1-4 [398 kB]
Get:211 http://mirror.einval.org/debian sid/main i386 libpixman-1-0 i386 0.42.2-1 [548 kB]
Get:212 http://mirror.einval.org/debian sid/main i386 libxcb-render0 i386 1.15-1 [116 kB]
Get:213 http://mirror.einval.org/debian sid/main i386 libxcb-shm0 i386 1.15-1 [106 kB]
Get:214 http://mirror.einval.org/debian sid/main i386 libxrender1 i386 1:0.9.10-1.1 [34.1 kB]
Get:215 http://mirror.einval.org/debian sid/main i386 libcairo2 i386 1.16.0-7 [627 kB]
Get:216 http://mirror.einval.org/debian sid/main i386 libpangoft2-1.0-0 i386 1.50.12+ds-1 [50.5 kB]
Get:217 http://mirror.einval.org/debian sid/main i386 libpangocairo-1.0-0 i386 1.50.12+ds-1 [35.4 kB]
Get:218 http://mirror.einval.org/debian sid/main i386 libxft2 i386 2.3.6-1 [62.8 kB]
Get:219 http://mirror.einval.org/debian sid/main i386 libpangoxft-1.0-0 i386 1.50.12+ds-1 [27.4 kB]
Get:220 http://mirror.einval.org/debian sid/main i386 gir1.2-pango-1.0 i386 1.50.12+ds-1 [37.4 kB]
Get:221 http://mirror.einval.org/debian sid/main i386 libatk-bridge2.0-0 i386 2.46.0-5 [69.8 kB]
Get:222 http://mirror.einval.org/debian sid/main i386 libcairo-gobject2 i386 1.16.0-7 [111 kB]
Get:223 http://mirror.einval.org/debian sid/main i386 liblcms2-2 i386 2.14-2 [165 kB]
Get:224 http://mirror.einval.org/debian sid/main i386 libudev1 i386 252.6-1 [111 kB]
Get:225 http://mirror.einval.org/debian sid/main i386 libcolord2 i386 1.4.6-2.2 [144 kB]
Get:226 http://mirror.einval.org/debian sid/main i386 libavahi-common-data i386 0.8-9 [107 kB]
Get:227 http://mirror.einval.org/debian sid/main i386 libavahi-common3 i386 0.8-9 [43.3 kB]
Get:228 http://mirror.einval.org/debian sid/main i386 libavahi-client3 i386 0.8-9 [47.3 kB]
Get:229 http://mirror.einval.org/debian sid/main i386 libgmp10 i386 2:6.2.1+dfsg1-1.1 [574 kB]
Get:230 http://mirror.einval.org/debian sid/main i386 libnettle8 i386 3.8.1-2 [301 kB]
Get:231 http://mirror.einval.org/debian sid/main i386 libhogweed6 i386 3.8.1-2 [331 kB]
Get:232 http://mirror.einval.org/debian sid/main i386 libunistring2 i386 1.0-2 [435 kB]
Get:233 http://mirror.einval.org/debian sid/main i386 libidn2-0 i386 2.3.3-1+b1 [126 kB]
Get:234 http://mirror.einval.org/debian sid/main i386 libp11-kit0 i386 0.24.1-2 [335 kB]
Get:235 http://mirror.einval.org/debian sid/main i386 libtasn1-6 i386 4.19.0-2 [58.4 kB]
Get:236 http://mirror.einval.org/debian sid/main i386 libgnutls30 i386 3.7.9-1 [1403 kB]
Get:237 http://mirror.einval.org/debian sid/main i386 libcom-err2 i386 1.47.0-2 [20.1 kB]
Get:238 http://mirror.einval.org/debian sid/main i386 libkrb5support0 i386 1.20.1-1 [34.9 kB]
Get:239 http://mirror.einval.org/debian sid/main i386 libk5crypto3 i386 1.20.1-1 [82.2 kB]
Get:240 http://mirror.einval.org/debian sid/main i386 libkeyutils1 i386 1.6.3-2 [9284 B]
Get:241 http://mirror.einval.org/debian sid/main i386 libssl3 i386 3.0.8-1 [2018 kB]
Get:242 http://mirror.einval.org/debian sid/main i386 libkrb5-3 i386 1.20.1-1 [359 kB]
Get:243 http://mirror.einval.org/debian sid/main i386 libgssapi-krb5-2 i386 1.20.1-1 [144 kB]
Get:244 http://mirror.einval.org/debian sid/main i386 libcups2 i386 2.4.2-2 [261 kB]
Get:245 http://mirror.einval.org/debian sid/main i386 libepoxy0 i386 1.5.10-1 [198 kB]
Get:246 http://mirror.einval.org/debian sid/main i386 libwayland-client0 i386 1.21.0-1 [29.0 kB]
Get:247 http://mirror.einval.org/debian sid/main i386 libwayland-cursor0 i386 1.21.0-1 [15.0 kB]
Get:248 http://mirror.einval.org/debian sid/main i386 libwayland-egl1 i386 1.21.0-1 [8740 B]
Get:249 http://mirror.einval.org/debian sid/main i386 libxcomposite1 i386 1:0.4.5-1 [16.9 kB]
Get:250 http://mirror.einval.org/debian sid/main i386 libxfixes3 i386 1:6.0.0-2 [23.0 kB]
Get:251 http://mirror.einval.org/debian sid/main i386 libxcursor1 i386 1:1.2.1-1 [42.4 kB]
Get:252 http://mirror.einval.org/debian sid/main i386 libxdamage1 i386 1:1.1.6-1 [15.3 kB]
Get:253 http://mirror.einval.org/debian sid/main i386 libxinerama1 i386 2:1.1.4-3 [18.1 kB]
Get:254 http://mirror.einval.org/debian sid/main arm64 xkb-data all 2.35.1-1 [764 kB]
Get:255 http://mirror.einval.org/debian sid/main i386 libxkbcommon0 i386 1.5.0-1 [112 kB]
Get:256 http://mirror.einval.org/debian sid/main i386 libxrandr2 i386 2:1.5.2-2+b1 [40.8 kB]
Get:257 http://mirror.einval.org/debian sid/main arm64 libgtk-3-common all 3.24.36-4 [3888 kB]
Get:258 http://mirror.einval.org/debian sid/main i386 libgtk-3-0 i386 3.24.36-4 [3043 kB]
Get:259 http://mirror.einval.org/debian sid/main i386 gir1.2-gtk-3.0 i386 3.24.36-4 [219 kB]
Get:260 http://mirror.einval.org/debian sid/main i386 libayatana-ido3-0.4-0 i386 0.9.3-1 [61.1 kB]
Get:261 http://mirror.einval.org/debian sid/main i386 libayatana-indicator3-7 i386 0.9.3-1 [34.5 kB]
Get:262 http://mirror.einval.org/debian sid/main i386 libdbusmenu-glib4 i386 18.10.20180917~bzr492+repack1-3 [45.1 kB]
Get:263 http://mirror.einval.org/debian sid/main i386 libdbusmenu-gtk3-4 i386 18.10.20180917~bzr492+repack1-3 [31.6 kB]
Get:264 http://mirror.einval.org/debian sid/main i386 libayatana-appindicator3-1 i386 0.5.92-1 [25.1 kB]
Get:265 http://mirror.einval.org/debian sid/main i386 gir1.2-ayatanaappindicator3-0.1 i386 0.5.92-1 [9024 B]
Get:266 http://mirror.einval.org/debian sid/main i386 gir1.2-ayatanaido3-0.4 i386 0.9.3-1 [9108 B]
Get:267 http://mirror.einval.org/debian sid/main i386 gir1.2-dbusmenu-glib-0.4 i386 18.10.20180917~bzr492+repack1-3 [7616 B]
Get:268 http://mirror.einval.org/debian sid/main i386 libdbus-glib-1-2 i386 0.112-3 [64.5 kB]
Get:269 http://mirror.einval.org/debian sid/main i386 libgconf-2-4 i386 3.2.6-8 [418 kB]
Get:270 http://mirror.einval.org/debian sid/main i386 gir1.2-gconf-2.0 i386 3.2.6-8 [349 kB]
Get:271 http://mirror.einval.org/debian sid/main i386 libbz2-1.0 i386 1.0.8-5+b1 [47.1 kB]
Get:272 http://mirror.einval.org/debian sid/main i386 libelf1 i386 0.188-2.1 [179 kB]
Get:273 http://mirror.einval.org/debian sid/main i386 libdw1 i386 0.188-2.1 [265 kB]
Get:274 http://mirror.einval.org/debian sid/main i386 libunwind8 i386 1.6.2-3 [49.0 kB]
Get:275 http://mirror.einval.org/debian sid/main arm64 libcap2-bin arm64 1:2.66-3 [33.9 kB]
Get:276 http://mirror.einval.org/debian sid/main i386 libgstreamer1.0-0 i386 1.22.0-2 [1220 kB]
Get:277 http://mirror.einval.org/debian sid/main i386 gir1.2-gstreamer-1.0 i386 1.22.0-2 [105 kB]
Get:278 http://mirror.einval.org/debian sid/main arm64 libgtk2.0-common all 2.24.33-2 [2700 kB]
Get:279 http://mirror.einval.org/debian sid/main arm64 libpixman-1-0 arm64 0.42.2-1 [470 kB]
Get:280 http://mirror.einval.org/debian sid/main arm64 libxau6 arm64 1:1.0.9-1 [19.7 kB]
Get:281 http://mirror.einval.org/debian sid/main arm64 libbsd0 arm64 0.11.7-4 [113 kB]
Get:282 http://mirror.einval.org/debian sid/main arm64 libxdmcp6 arm64 1:1.1.2-3 [25.4 kB]
Get:283 http://mirror.einval.org/debian sid/main arm64 libxcb1 arm64 1.15-1 [143 kB]
Get:284 http://mirror.einval.org/debian sid/main arm64 libx11-6 arm64 2:1.8.4-2 [736 kB]
Get:285 http://mirror.einval.org/debian sid/main arm64 libxcb-render0 arm64 1.15-1 [115 kB]
Get:286 http://mirror.einval.org/debian sid/main arm64 libxcb-shm0 arm64 1.15-1 [106 kB]
Get:287 http://mirror.einval.org/debian sid/main arm64 libxext6 arm64 2:1.3.4-1+b1 [51.7 kB]
Get:288 http://mirror.einval.org/debian sid/main arm64 libxrender1 arm64 1:0.9.10-1.1 [32.0 kB]
Get:289 http://mirror.einval.org/debian sid/main arm64 libcairo2 arm64 1.16.0-7 [527 kB]
Get:290 http://mirror.einval.org/debian sid/main arm64 libcairo-gobject2 arm64 1.16.0-7 [112 kB]
Get:291 http://mirror.einval.org/debian sid/main arm64 libfribidi0 arm64 1.0.8-2.1 [64.9 kB]
Get:292 http://mirror.einval.org/debian sid/main arm64 libgraphite2-3 arm64 1.3.14-1 [75.6 kB]
Get:293 http://mirror.einval.org/debian sid/main arm64 libharfbuzz0b arm64 6.0.0+dfsg-3 [1914 kB]
Get:294 http://mirror.einval.org/debian sid/main arm64 libdatrie1 arm64 0.2.13-2+b1 [42.6 kB]
Get:295 http://mirror.einval.org/debian sid/main arm64 libthai0 arm64 0.1.29-1 [56.2 kB]
Get:296 http://mirror.einval.org/debian sid/main arm64 libpango-1.0-0 arm64 1.50.12+ds-1 [200 kB]
Get:297 http://mirror.einval.org/debian sid/main arm64 libpangoft2-1.0-0 arm64 1.50.12+ds-1 [44.5 kB]
Get:298 http://mirror.einval.org/debian sid/main arm64 libpangocairo-1.0-0 arm64 1.50.12+ds-1 [32.0 kB]
Get:299 http://mirror.einval.org/debian sid/main arm64 librsvg2-2 arm64 2.54.5+dfsg-1 [2302 kB]
Get:300 http://mirror.einval.org/debian sid/main arm64 librsvg2-common arm64 2.54.5+dfsg-1 [34.1 kB]
Get:301 http://mirror.einval.org/debian sid/main arm64 gnome-icon-theme all 3.12.0-5 [9867 kB]
Get:302 http://mirror.einval.org/debian sid/main i386 libgtk2.0-0 i386 2.24.33-2 [1970 kB]
Get:303 http://mirror.einval.org/debian sid/main i386 gir1.2-gtk-2.0 i386 2.24.33-2 [215 kB]
Get:304 http://mirror.einval.org/debian sid/main i386 libnotify4 i386 0.8.1-1 [30.9 kB]
Get:305 http://mirror.einval.org/debian sid/main i386 gir1.2-notify-0.7 i386 0.8.1-1 [11.6 kB]
Get:306 http://mirror.einval.org/debian sid/main arm64 libpkgconf3 arm64 1.8.1-1 [35.3 kB]
Get:307 http://mirror.einval.org/debian sid/main arm64 pkgconf-bin arm64 1.8.1-1 [28.9 kB]
Get:308 http://mirror.einval.org/debian sid/main arm64 pkgconf arm64 1.8.1-1 [25.9 kB]
Get:309 http://mirror.einval.org/debian sid/main arm64 pkg-config arm64 1.8.1-1 [13.7 kB]
Get:310 http://mirror.einval.org/debian sid/main arm64 libregexp-ipv6-perl all 0.03-3 [5212 B]
Get:311 http://mirror.einval.org/debian sid/main arm64 liburi-perl all 5.17-1 [90.4 kB]
Get:312 http://mirror.einval.org/debian sid/main arm64 libencode-locale-perl all 1.05-3 [12.9 kB]
Get:313 http://mirror.einval.org/debian sid/main arm64 libtimedate-perl all 2.3300-2 [39.3 kB]
Get:314 http://mirror.einval.org/debian sid/main arm64 libhttp-date-perl all 6.05-2 [10.5 kB]
Get:315 http://mirror.einval.org/debian sid/main arm64 libfile-listing-perl all 6.15-1 [12.6 kB]
Get:316 http://mirror.einval.org/debian sid/main arm64 libhtml-tagset-perl all 3.20-6 [11.7 kB]
Get:317 http://mirror.einval.org/debian sid/main arm64 libhtml-parser-perl arm64 3.81-1 [98.6 kB]
Get:318 http://mirror.einval.org/debian sid/main arm64 libhtml-tree-perl all 5.07-3 [211 kB]
Get:319 http://mirror.einval.org/debian sid/main arm64 libclone-perl arm64 0.46-1 [13.5 kB]
Get:320 http://mirror.einval.org/debian sid/main arm64 libio-html-perl all 1.004-3 [16.2 kB]
Get:321 http://mirror.einval.org/debian sid/main arm64 liblwp-mediatypes-perl all 6.04-2 [20.2 kB]
Get:322 http://mirror.einval.org/debian sid/main arm64 libhttp-message-perl all 6.44-1 [81.7 kB]
Get:323 http://mirror.einval.org/debian sid/main arm64 libhttp-cookies-perl all 6.10-1 [19.6 kB]
Get:324 http://mirror.einval.org/debian sid/main arm64 libhttp-negotiate-perl all 6.01-2 [13.1 kB]
Get:325 http://mirror.einval.org/debian sid/main arm64 perl-openssl-defaults arm64 7+b1 [7924 B]
Get:326 http://mirror.einval.org/debian sid/main arm64 libnet-ssleay-perl arm64 1.92-2+b1 [308 kB]
Get:327 http://mirror.einval.org/debian sid/main arm64 libio-socket-ssl-perl all 2.081-2 [219 kB]
Get:328 http://mirror.einval.org/debian sid/main arm64 libnet-http-perl all 6.22-1 [25.3 kB]
Get:329 http://mirror.einval.org/debian sid/main arm64 liblwp-protocol-https-perl all 6.10-1 [12.2 kB]
Get:330 http://mirror.einval.org/debian sid/main arm64 libtry-tiny-perl all 0.31-2 [22.6 kB]
Get:331 http://mirror.einval.org/debian sid/main arm64 libwww-robotrules-perl all 6.02-1 [12.9 kB]
Get:332 http://mirror.einval.org/debian sid/main arm64 libwww-perl all 6.68-1 [186 kB]
Get:333 http://mirror.einval.org/debian sid/main arm64 libxml-parser-perl arm64 2.46-4 [198 kB]
Get:334 http://mirror.einval.org/debian sid/main arm64 intltool all 0.51.0-6 [50.8 kB]
Get:335 http://mirror.einval.org/debian sid/main arm64 gnome-common all 3.18.0-4 [134 kB]
Get:336 http://mirror.einval.org/debian sid/main arm64 icu-devtools arm64 72.1-3 [192 kB]
Get:337 http://mirror.einval.org/debian sid/main i386 libasan8 i386 12.2.0-14 [2079 kB]
Get:338 http://mirror.einval.org/debian sid/main i386 pkgconf i386 1.8.1-1 [25.9 kB]
Get:339 http://mirror.einval.org/debian sid/main i386 pkg-config i386 1.8.1-1 [13.7 kB]
Get:340 http://mirror.einval.org/debian sid/main i386 libffi-dev i386 3.4.4-1 [57.3 kB]
Get:341 http://mirror.einval.org/debian sid/main arm64 libglib2.0-data all 2.74.6-1 [1208 kB]
Get:342 http://mirror.einval.org/debian sid/main arm64 libglib2.0-bin arm64 2.74.6-1 [106 kB]
Get:343 http://mirror.einval.org/debian sid/main arm64 python3-lib2to3 all 3.11.2-2 [76.2 kB]
Get:344 http://mirror.einval.org/debian sid/main arm64 python3-distutils all 3.11.2-2 [131 kB]
Get:345 http://mirror.einval.org/debian sid/main arm64 libglib2.0-dev-bin arm64 2.74.6-1 [149 kB]
Get:346 http://mirror.einval.org/debian sid/main i386 linux-libc-dev i386 6.1.15-1 [1736 kB]
Get:347 http://mirror.einval.org/debian sid/main i386 libcrypt1 i386 1:4.4.33-2 [95.6 kB]
Get:348 http://mirror.einval.org/debian sid/main i386 libcrypt-dev i386 1:4.4.33-2 [126 kB]
Get:349 http://mirror.einval.org/debian sid/main i386 libtirpc3 i386 1.3.3+ds-1 [92.6 kB]
Get:350 http://mirror.einval.org/debian sid/main i386 libnsl2 i386 1.3.0-2 [42.2 kB]
Get:351 http://mirror.einval.org/debian sid/main i386 libtirpc-dev i386 1.3.3+ds-1 [202 kB]
Get:352 http://mirror.einval.org/debian sid/main i386 libnsl-dev i386 1.3.0-2 [70.6 kB]
Get:353 http://mirror.einval.org/debian sid/main i386 libc6-dev i386 2.36-8 [1717 kB]
Get:354 http://mirror.einval.org/debian sid/main i386 libuuid1 i386 2.38.1-5 [29.4 kB]
Get:355 http://mirror.einval.org/debian sid/main i386 uuid-dev i386 2.38.1-5 [40.0 kB]
Get:356 http://mirror.einval.org/debian sid/main i386 libblkid-dev i386 2.38.1-5 [201 kB]
Get:357 http://mirror.einval.org/debian sid/main i386 libsepol2 i386 3.4-2 [306 kB]
Get:358 http://mirror.einval.org/debian sid/main i386 libsepol-dev i386 3.4-2 [392 kB]
Get:359 http://mirror.einval.org/debian sid/main i386 libpcre2-16-0 i386 10.42-1 [243 kB]
Get:360 http://mirror.einval.org/debian sid/main i386 libpcre2-32-0 i386 10.42-1 [232 kB]
Get:361 http://mirror.einval.org/debian sid/main i386 libpcre2-posix3 i386 10.42-1 [55.4 kB]
Get:362 http://mirror.einval.org/debian sid/main i386 libpcre2-dev i386 10.42-1 [761 kB]
Get:363 http://mirror.einval.org/debian sid/main i386 libselinux1-dev i386 3.4-1+b5 [165 kB]
Get:364 http://mirror.einval.org/debian sid/main i386 libmount-dev i386 2.38.1-5 [22.2 kB]
Get:365 http://mirror.einval.org/debian sid/main i386 zlib1g-dev i386 1:1.2.13.dfsg-1 [913 kB]
Get:366 http://mirror.einval.org/debian sid/main i386 libglib2.0-dev i386 2.74.6-1 [1718 kB]
Get:367 http://mirror.einval.org/debian sid/main i386 libatk1.0-dev i386 2.46.0-5 [103 kB]
Get:368 http://mirror.einval.org/debian sid/main arm64 xml-core all 0.18+nmu1 [23.8 kB]
Get:369 http://mirror.einval.org/debian sid/main i386 libdbus-1-dev i386 1.14.6-1 [257 kB]
Get:370 http://mirror.einval.org/debian sid/main arm64 x11-common all 1:7.7+23 [252 kB]
Get:371 http://mirror.einval.org/debian sid/main i386 libxtst6 i386 2:1.2.3-1.1 [28.6 kB]
Get:372 http://mirror.einval.org/debian sid/main arm64 xorg-sgml-doctools all 1:1.11-1.1 [22.1 kB]
Get:373 http://mirror.einval.org/debian sid/main arm64 x11proto-dev all 2022.1-1 [599 kB]
Get:374 http://mirror.einval.org/debian sid/main i386 libxau-dev i386 1:1.0.9-1 [23.3 kB]
Get:375 http://mirror.einval.org/debian sid/main i386 libxdmcp-dev i386 1:1.1.2-3 [42.7 kB]
Get:376 http://mirror.einval.org/debian sid/main arm64 xtrans-dev all 1.4.0-1 [98.7 kB]
Get:377 http://mirror.einval.org/debian sid/main i386 libpthread-stubs0-dev i386 0.4-1 [5340 B]
Get:378 http://mirror.einval.org/debian sid/main i386 libxcb1-dev i386 1.15-1 [185 kB]
Get:379 http://mirror.einval.org/debian sid/main i386 libx11-dev i386 2:1.8.4-2 [866 kB]
Get:380 http://mirror.einval.org/debian sid/main i386 libxext-dev i386 2:1.3.4-1+b1 [110 kB]
Get:381 http://mirror.einval.org/debian sid/main i386 libxfixes-dev i386 1:6.0.0-2 [25.3 kB]
Get:382 http://mirror.einval.org/debian sid/main i386 libxi-dev i386 2:1.8-1+b1 [249 kB]
Get:383 http://mirror.einval.org/debian sid/main i386 libxtst-dev i386 2:1.2.3-1.1 [32.9 kB]
Get:384 http://mirror.einval.org/debian sid/main i386 libatspi2.0-dev i386 2.46.0-5 [76.3 kB]
Get:385 http://mirror.einval.org/debian sid/main i386 libatk-bridge2.0-dev i386 2.46.0-5 [8212 B]
Get:386 http://mirror.einval.org/debian sid/main i386 libatomic1 i386 12.2.0-14 [7692 B]
Get:387 http://mirror.einval.org/debian sid/main i386 liblzo2-2 i386 2.10-2 [59.7 kB]
Get:388 http://mirror.einval.org/debian sid/main i386 libcairo-script-interpreter2 i386 1.16.0-7 [153 kB]
Get:389 http://mirror.einval.org/debian sid/main i386 libexpat1-dev i386 2.5.0-1 [158 kB]
Get:390 http://mirror.einval.org/debian sid/main i386 libbrotli-dev i386 1.0.9-2+b6 [287 kB]
Get:391 http://mirror.einval.org/debian sid/main i386 libpng-dev i386 1.6.39-2 [367 kB]
Get:392 http://mirror.einval.org/debian sid/main i386 libfreetype-dev i386 2.12.1+dfsg-4 [585 kB]
Get:393 http://mirror.einval.org/debian sid/main i386 libfontconfig-dev i386 2.14.1-4 [425 kB]
Get:394 http://mirror.einval.org/debian sid/main i386 libpixman-1-dev i386 0.42.2-1 [573 kB]
Get:395 http://mirror.einval.org/debian sid/main i386 libice6 i386 2:1.0.10-1 [60.8 kB]
Get:396 http://mirror.einval.org/debian sid/main i386 libsm6 i386 2:1.2.3-1 [35.7 kB]
Get:397 http://mirror.einval.org/debian sid/main i386 libice-dev i386 2:1.0.10-1 [70.5 kB]
Get:398 http://mirror.einval.org/debian sid/main i386 libsm-dev i386 2:1.2.3-1 [38.8 kB]
Get:399 http://mirror.einval.org/debian sid/main i386 libxcb-render0-dev i386 1.15-1 [119 kB]
Get:400 http://mirror.einval.org/debian sid/main i386 libxcb-shm0-dev i386 1.15-1 [107 kB]
Get:401 http://mirror.einval.org/debian sid/main i386 libxrender-dev i386 1:0.9.10-1.1 [42.3 kB]
Get:402 http://mirror.einval.org/debian sid/main i386 libcairo2-dev i386 1.16.0-7 [800 kB]
Get:403 http://mirror.einval.org/debian sid/main i386 libglvnd0 i386 1.6.0-1 [42.7 kB]
Get:404 http://mirror.einval.org/debian sid/main arm64 libdrm-common all 2.4.114-1 [7112 B]
Get:405 http://mirror.einval.org/debian sid/main i386 libdrm2 i386 2.4.114-1 [40.6 kB]
Get:406 http://mirror.einval.org/debian sid/main i386 libwayland-server0 i386 1.21.0-1 [37.4 kB]
Get:407 http://mirror.einval.org/debian sid/main i386 libgbm1 i386 22.3.6-1 [39.1 kB]
Get:408 http://mirror.einval.org/debian sid/main i386 libglapi-mesa i386 22.3.6-1 [35.5 kB]
Get:409 http://mirror.einval.org/debian sid/main i386 libx11-xcb1 i386 2:1.8.4-2 [192 kB]
Get:410 http://mirror.einval.org/debian sid/main i386 libxcb-dri2-0 i386 1.15-1 [107 kB]
Get:411 http://mirror.einval.org/debian sid/main i386 libxcb-dri3-0 i386 1.15-1 [107 kB]
Get:412 http://mirror.einval.org/debian sid/main i386 libxcb-present0 i386 1.15-1 [106 kB]
Get:413 http://mirror.einval.org/debian sid/main i386 libxcb-randr0 i386 1.15-1 [118 kB]
Get:414 http://mirror.einval.org/debian sid/main i386 libxcb-sync1 i386 1.15-1 [109 kB]
Get:415 http://mirror.einval.org/debian sid/main i386 libxcb-xfixes0 i386 1.15-1 [110 kB]
Get:416 http://mirror.einval.org/debian sid/main i386 libxshmfence1 i386 1.3-1 [8976 B]
Get:417 http://mirror.einval.org/debian sid/main i386 libegl-mesa0 i386 22.3.6-1 [123 kB]
Get:418 http://mirror.einval.org/debian sid/main i386 libegl1 i386 1.6.0-1 [35.6 kB]
Get:419 http://mirror.einval.org/debian sid/main i386 libxcb-glx0 i386 1.15-1 [124 kB]
Get:420 http://mirror.einval.org/debian sid/main i386 libxxf86vm1 i386 1:1.1.4-1+b2 [21.7 kB]
Get:421 http://mirror.einval.org/debian sid/main i386 libdrm-amdgpu1 i386 2.4.114-1 [23.8 kB]
Get:422 http://mirror.einval.org/debian sid/main i386 libpciaccess0 i386 0.17-2 [53.4 kB]
Get:423 http://mirror.einval.org/debian sid/main i386 libdrm-intel1 i386 2.4.114-1 [67.5 kB]
Get:424 http://mirror.einval.org/debian sid/main i386 libdrm-nouveau2 i386 2.4.114-1 [20.4 kB]
Get:425 http://mirror.einval.org/debian sid/main i386 libdrm-radeon1 i386 2.4.114-1 [22.6 kB]
Get:426 http://mirror.einval.org/debian sid/main i386 libtinfo6 i386 6.4-2 [332 kB]
Get:427 http://mirror.einval.org/debian sid/main i386 libedit2 i386 3.1-20221030-2 [97.2 kB]
Get:428 http://mirror.einval.org/debian sid/main i386 libicu72 i386 72.1-3 [9541 kB]
Get:429 http://mirror.einval.org/debian sid/main i386 libxml2 i386 2.9.14+dfsg-1.1+b3 [720 kB]
Get:430 http://mirror.einval.org/debian sid/main i386 libz3-4 i386 4.8.12-3.1 [7853 kB]
Get:431 http://mirror.einval.org/debian sid/main i386 libllvm15 i386 1:15.0.7-1 [26.4 MB]
Get:432 http://mirror.einval.org/debian sid/main arm64 libsensors-config all 1:3.6.0-7.1 [14.3 kB]
Get:433 http://mirror.einval.org/debian sid/main i386 libsensors5 i386 1:3.6.0-7.1 [35.1 kB]
Get:434 http://mirror.einval.org/debian sid/main i386 libgl1-mesa-dri i386 22.3.6-1 [7416 kB]
Get:435 http://mirror.einval.org/debian sid/main i386 libglx-mesa0 i386 22.3.6-1 [155 kB]
Get:436 http://mirror.einval.org/debian sid/main i386 libglx0 i386 1.6.0-1 [36.6 kB]
Get:437 http://mirror.einval.org/debian sid/main i386 libgl1 i386 1.6.0-1 [82.1 kB]
Get:438 http://mirror.einval.org/debian sid/main i386 libglx-dev i386 1.6.0-1 [15.3 kB]
Get:439 http://mirror.einval.org/debian sid/main i386 libgl-dev i386 1.6.0-1 [100 kB]
Get:440 http://mirror.einval.org/debian sid/main i386 libegl-dev i386 1.6.0-1 [19.1 kB]
Get:441 http://mirror.einval.org/debian sid/main i386 libglvnd-core-dev i386 1.6.0-1 [12.9 kB]
Get:442 http://mirror.einval.org/debian sid/main i386 libgles1 i386 1.6.0-1 [11.6 kB]
Get:443 http://mirror.einval.org/debian sid/main i386 libgles2 i386 1.6.0-1 [16.3 kB]
Get:444 http://mirror.einval.org/debian sid/main i386 libgles-dev i386 1.6.0-1 [50.4 kB]
Get:445 http://mirror.einval.org/debian sid/main i386 libopengl0 i386 1.6.0-1 [29.2 kB]
Get:446 http://mirror.einval.org/debian sid/main i386 libopengl-dev i386 1.6.0-1 [4924 B]
Get:447 http://mirror.einval.org/debian sid/main i386 libglvnd-dev i386 1.6.0-1 [4688 B]
Get:448 http://mirror.einval.org/debian sid/main i386 libegl1-mesa-dev i386 22.3.6-1 [18.5 kB]
Get:449 http://mirror.einval.org/debian sid/main i386 libepoxy-dev i386 1.5.10-1 [128 kB]
Get:450 http://mirror.einval.org/debian sid/main i386 libfribidi-dev i386 1.0.8-2.1 [106 kB]
Get:451 http://mirror.einval.org/debian sid/main arm64 libgdk-pixbuf2.0-bin arm64 2.42.10+dfsg-1+b1 [18.0 kB]
Get:452 http://mirror.einval.org/debian sid/main i386 libjpeg62-turbo-dev i386 1:2.1.5-2 [304 kB]
Get:453 http://mirror.einval.org/debian sid/main i386 libjpeg-dev i386 1:2.1.5-2 [71.8 kB]
Get:454 http://mirror.einval.org/debian sid/main i386 libjbig-dev i386 2.1-6.1 [30.9 kB]
Get:455 http://mirror.einval.org/debian sid/main i386 liblzma-dev i386 5.4.1-0.2 [272 kB]
Get:456 http://mirror.einval.org/debian sid/main i386 libzstd-dev i386 1.5.4+dfsg2-3 [338 kB]
Get:457 http://mirror.einval.org/debian sid/main i386 libwebpmux3 i386 1.2.4-0.1 [111 kB]
Get:458 http://mirror.einval.org/debian sid/main i386 libwebpdemux2 i386 1.2.4-0.1 [99.7 kB]
Get:459 http://mirror.einval.org/debian sid/main i386 libwebp-dev i386 1.2.4-0.1 [414 kB]
Get:460 http://mirror.einval.org/debian sid/main i386 libtiffxx6 i386 4.5.0-5 [144 kB]
Get:461 http://mirror.einval.org/debian sid/main i386 libdeflate-dev i386 1.14-1 [53.5 kB]
Get:462 http://mirror.einval.org/debian sid/main i386 liblerc-dev i386 4.0.0+ds-2 [193 kB]
Get:463 http://mirror.einval.org/debian sid/main i386 libtiff-dev i386 4.5.0-5 [479 kB]
Get:464 http://mirror.einval.org/debian sid/main i386 libgdk-pixbuf-2.0-dev i386 2.42.10+dfsg-1+b1 [51.7 kB]
Get:465 http://mirror.einval.org/debian sid/main i386 libharfbuzz-icu0 i386 6.0.0+dfsg-3 [1557 kB]
Get:466 http://mirror.einval.org/debian sid/main i386 libharfbuzz-gobject0 i386 6.0.0+dfsg-3 [1570 kB]
Get:467 http://mirror.einval.org/debian sid/main i386 libharfbuzz-subset0 i386 6.0.0+dfsg-3 [1956 kB]
Get:468 http://mirror.einval.org/debian sid/main i386 libgraphite2-dev i386 1.3.14-1 [24.0 kB]
Get:469 http://mirror.einval.org/debian sid/main i386 libicu-dev i386 72.1-3 [10.6 MB]
Get:470 http://mirror.einval.org/debian sid/main i386 libharfbuzz-dev i386 6.0.0+dfsg-3 [1668 kB]
Get:471 http://mirror.einval.org/debian sid/main i386 libdatrie-dev i386 0.2.13-2+b1 [20.5 kB]
Get:472 http://mirror.einval.org/debian sid/main i386 libthai-dev i386 0.1.29-1 [25.7 kB]
Get:473 http://mirror.einval.org/debian sid/main i386 libxft-dev i386 2.3.6-1 [82.3 kB]
Get:474 http://mirror.einval.org/debian sid/main arm64 libxft2 arm64 2.3.6-1 [58.7 kB]
Get:475 http://mirror.einval.org/debian sid/main arm64 libpangoxft-1.0-0 arm64 1.50.12+ds-1 [25.9 kB]
Get:476 http://mirror.einval.org/debian sid/main arm64 pango1.0-tools arm64 1.50.12+ds-1 [39.2 kB]
Get:477 http://mirror.einval.org/debian sid/main i386 libpango1.0-dev i386 1.50.12+ds-1 [152 kB]
Get:478 http://mirror.einval.org/debian sid/main arm64 libwayland-bin arm64 1.21.0-1 [22.5 kB]
Get:479 http://mirror.einval.org/debian sid/main i386 libwayland-dev i386 1.21.0-1 [72.5 kB]
Get:480 http://mirror.einval.org/debian sid/main i386 libxcomposite-dev i386 1:0.4.5-1 [20.5 kB]
Get:481 http://mirror.einval.org/debian sid/main i386 libxcursor-dev i386 1:1.2.1-1 [54.1 kB]
Get:482 http://mirror.einval.org/debian sid/main i386 libxdamage-dev i386 1:1.1.6-1 [15.3 kB]
Get:483 http://mirror.einval.org/debian sid/main i386 libxinerama-dev i386 2:1.1.4-3 [20.4 kB]
Get:484 http://mirror.einval.org/debian sid/main i386 libxkbcommon-dev i386 1.5.0-1 [51.0 kB]
Get:485 http://mirror.einval.org/debian sid/main i386 libxrandr-dev i386 2:1.5.2-2+b1 [48.8 kB]
Get:486 http://mirror.einval.org/debian sid/main arm64 wayland-protocols all 1.31-1 [74.6 kB]
Get:487 http://mirror.einval.org/debian sid/main i386 libgtk-3-dev i386 3.24.36-4 [1114 kB]
Get:488 http://mirror.einval.org/debian sid/main i386 libayatana-ido3-dev i386 0.9.3-1 [17.1 kB]
Get:489 http://mirror.einval.org/debian sid/main i386 libayatana-indicator3-dev i386 0.9.3-1 [10.8 kB]
Get:490 http://mirror.einval.org/debian sid/main arm64 libxml2-utils arm64 2.9.14+dfsg-1.1+b3 [97.2 kB]
Get:491 http://mirror.einval.org/debian sid/main i386 libgtk2.0-dev i386 2.24.33-2 [827 kB]
Get:492 http://mirror.einval.org/debian sid/main i386 libdbusmenu-glib-dev i386 18.10.20180917~bzr492+repack1-3 [72.9 kB]
Get:493 http://mirror.einval.org/debian sid/main i386 libayatana-appindicator3-dev i386 0.5.92-1 [18.2 kB]
Get:494 http://mirror.einval.org/debian sid/main i386 libelf-dev i386 0.188-2.1 [80.0 kB]
Get:495 http://mirror.einval.org/debian sid/main i386 libdw-dev i386 0.188-2.1 [353 kB]
Get:496 http://mirror.einval.org/debian sid/main i386 libgomp1 i386 12.2.0-14 [121 kB]
Get:497 http://mirror.einval.org/debian sid/main i386 libitm1 i386 12.2.0-14 [27.6 kB]
Get:498 http://mirror.einval.org/debian sid/main i386 libubsan1 i386 12.2.0-14 [870 kB]
Get:499 http://mirror.einval.org/debian sid/main i386 libquadmath0 i386 12.2.0-14 [226 kB]
Get:500 http://mirror.einval.org/debian sid/main i386 libgcc-12-dev i386 12.2.0-14 [2432 kB]
Get:501 http://mirror.einval.org/debian sid/main i386 libgconf2-dev i386 3.2.6-8 [448 kB]
Get:502 http://mirror.einval.org/debian sid/main i386 libunwind-dev i386 1.6.2-3 [404 kB]
Get:503 http://mirror.einval.org/debian sid/main i386 libgstreamer1.0-dev i386 1.22.0-2 [549 kB]
Get:504 http://mirror.einval.org/debian sid/main i386 libnotify-dev i386 0.8.1-1 [17.5 kB]
Get:505 http://mirror.einval.org/debian sid/main i386 libstdc++-12-dev i386 12.2.0-14 [2101 kB]
Get:506 http://mirror.einval.org/debian sid/main i386 libxml2-dev i386 2.9.14+dfsg-1.1+b3 [845 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 278 MB in 6s (44.0 MB/s)
Selecting previously unselected package libargon2-1:arm64.
(Reading database ... 12186 files and directories currently installed.)
Preparing to unpack .../00-libargon2-1_0~20190702-0.1_arm64.deb ...
Unpacking libargon2-1:arm64 (0~20190702-0.1) ...
Selecting previously unselected package dmsetup.
Preparing to unpack .../01-dmsetup_2%3a1.02.185-2_arm64.deb ...
Unpacking dmsetup (2:1.02.185-2) ...
Selecting previously unselected package libdevmapper1.02.1:arm64.
Preparing to unpack .../02-libdevmapper1.02.1_2%3a1.02.185-2_arm64.deb ...
Unpacking libdevmapper1.02.1:arm64 (2:1.02.185-2) ...
Selecting previously unselected package libjson-c5:arm64.
Preparing to unpack .../03-libjson-c5_0.16-2_arm64.deb ...
Unpacking libjson-c5:arm64 (0.16-2) ...
Selecting previously unselected package libcryptsetup12:arm64.
Preparing to unpack .../04-libcryptsetup12_2%3a2.6.1-2_arm64.deb ...
Unpacking libcryptsetup12:arm64 (2:2.6.1-2) ...
Selecting previously unselected package libfdisk1:arm64.
Preparing to unpack .../05-libfdisk1_2.38.1-5_arm64.deb ...
Unpacking libfdisk1:arm64 (2.38.1-5) ...
Selecting previously unselected package libkmod2:arm64.
Preparing to unpack .../06-libkmod2_30+20221128-1_arm64.deb ...
Unpacking libkmod2:arm64 (30+20221128-1) ...
Selecting previously unselected package libapparmor1:arm64.
Preparing to unpack .../07-libapparmor1_3.0.8-3_arm64.deb ...
Unpacking libapparmor1:arm64 (3.0.8-3) ...
Selecting previously unselected package libip4tc2:arm64.
Preparing to unpack .../08-libip4tc2_1.8.9-2_arm64.deb ...
Unpacking libip4tc2:arm64 (1.8.9-2) ...
Selecting previously unselected package libsystemd-shared:arm64.
Preparing to unpack .../09-libsystemd-shared_252.6-1_arm64.deb ...
Unpacking libsystemd-shared:arm64 (252.6-1) ...
Selecting previously unselected package systemd.
Preparing to unpack .../10-systemd_252.6-1_arm64.deb ...
Unpacking systemd (252.6-1) ...
Setting up libargon2-1:arm64 (0~20190702-0.1) ...
Setting up libjson-c5:arm64 (0.16-2) ...
Setting up libfdisk1:arm64 (2.38.1-5) ...
Setting up libkmod2:arm64 (30+20221128-1) ...
Setting up libapparmor1:arm64 (3.0.8-3) ...
Setting up libip4tc2:arm64 (1.8.9-2) ...
Setting up libsystemd-shared:arm64 (252.6-1) ...
Setting up libdevmapper1.02.1:arm64 (2:1.02.185-2) ...
Setting up libcryptsetup12:arm64 (2:2.6.1-2) ...
Setting up systemd (252.6-1) ...
Created symlink /etc/systemd/system/getty.target.wants/getty@tty1.service → /lib/systemd/system/getty@.service.
Created symlink /etc/systemd/system/multi-user.target.wants/remote-fs.target → /lib/systemd/system/remote-fs.target.
Created symlink /etc/systemd/system/sysinit.target.wants/systemd-pstore.service → /lib/systemd/system/systemd-pstore.service.
Initializing machine ID from random generator.
Setting up dmsetup (2:1.02.185-2) ...
Selecting previously unselected package systemd-sysv.
(Reading database ... 13106 files and directories currently installed.)
Preparing to unpack .../00-systemd-sysv_252.6-1_arm64.deb ...
Unpacking systemd-sysv (252.6-1) ...
Selecting previously unselected package libdbus-1-3:arm64.
Preparing to unpack .../01-libdbus-1-3_1.14.6-1_arm64.deb ...
Unpacking libdbus-1-3:arm64 (1.14.6-1) ...
Selecting previously unselected package dbus-bin.
Preparing to unpack .../02-dbus-bin_1.14.6-1_arm64.deb ...
Unpacking dbus-bin (1.14.6-1) ...
Selecting previously unselected package dbus-session-bus-common.
Preparing to unpack .../03-dbus-session-bus-common_1.14.6-1_all.deb ...
Unpacking dbus-session-bus-common (1.14.6-1) ...
Selecting previously unselected package libexpat1:arm64.
Preparing to unpack .../04-libexpat1_2.5.0-1_arm64.deb ...
Unpacking libexpat1:arm64 (2.5.0-1) ...
Selecting previously unselected package dbus-daemon.
Preparing to unpack .../05-dbus-daemon_1.14.6-1_arm64.deb ...
Unpacking dbus-daemon (1.14.6-1) ...
Selecting previously unselected package dbus-system-bus-common.
Preparing to unpack .../06-dbus-system-bus-common_1.14.6-1_all.deb ...
Unpacking dbus-system-bus-common (1.14.6-1) ...
Selecting previously unselected package dbus.
Preparing to unpack .../07-dbus_1.14.6-1_arm64.deb ...
Unpacking dbus (1.14.6-1) ...
Selecting previously unselected package autoconf-archive.
Preparing to unpack .../08-autoconf-archive_20220903-3_all.deb ...
Unpacking autoconf-archive (20220903-3) ...
Selecting previously unselected package liblocale-gettext-perl.
Preparing to unpack .../09-liblocale-gettext-perl_1.07-5_arm64.deb ...
Unpacking liblocale-gettext-perl (1.07-5) ...
Selecting previously unselected package libpython3.11-minimal:arm64.
Preparing to unpack .../10-libpython3.11-minimal_3.11.2-4_arm64.deb ...
Unpacking libpython3.11-minimal:arm64 (3.11.2-4) ...
Selecting previously unselected package python3.11-minimal.
Preparing to unpack .../11-python3.11-minimal_3.11.2-4_arm64.deb ...
Unpacking python3.11-minimal (3.11.2-4) ...
Setting up libpython3.11-minimal:arm64 (3.11.2-4) ...
Setting up libexpat1:arm64 (2.5.0-1) ...
Setting up python3.11-minimal (3.11.2-4) ...
Selecting previously unselected package python3-minimal.
(Reading database ... 14709 files and directories currently installed.)
Preparing to unpack .../0-python3-minimal_3.11.2-1_arm64.deb ...
Unpacking python3-minimal (3.11.2-1) ...
Selecting previously unselected package media-types.
Preparing to unpack .../1-media-types_10.0.0_all.deb ...
Unpacking media-types (10.0.0) ...
Selecting previously unselected package libncursesw6:arm64.
Preparing to unpack .../2-libncursesw6_6.4-2_arm64.deb ...
Unpacking libncursesw6:arm64 (6.4-2) ...
Selecting previously unselected package readline-common.
Preparing to unpack .../3-readline-common_8.2-1.3_all.deb ...
Unpacking readline-common (8.2-1.3) ...
Selecting previously unselected package libreadline8:arm64.
Preparing to unpack .../4-libreadline8_8.2-1.3_arm64.deb ...
Unpacking libreadline8:arm64 (8.2-1.3) ...
Selecting previously unselected package libsqlite3-0:arm64.
Preparing to unpack .../5-libsqlite3-0_3.40.1-1_arm64.deb ...
Unpacking libsqlite3-0:arm64 (3.40.1-1) ...
Selecting previously unselected package libpython3.11-stdlib:arm64.
Preparing to unpack .../6-libpython3.11-stdlib_3.11.2-4_arm64.deb ...
Unpacking libpython3.11-stdlib:arm64 (3.11.2-4) ...
Selecting previously unselected package python3.11.
Preparing to unpack .../7-python3.11_3.11.2-4_arm64.deb ...
Unpacking python3.11 (3.11.2-4) ...
Selecting previously unselected package libpython3-stdlib:arm64.
Preparing to unpack .../8-libpython3-stdlib_3.11.2-1_arm64.deb ...
Unpacking libpython3-stdlib:arm64 (3.11.2-1) ...
Setting up python3-minimal (3.11.2-1) ...
Selecting previously unselected package python3.
(Reading database ... 15158 files and directories currently installed.)
Preparing to unpack .../000-python3_3.11.2-1_arm64.deb ...
Unpacking python3 (3.11.2-1) ...
Selecting previously unselected package sgml-base.
Preparing to unpack .../001-sgml-base_1.31_all.deb ...
Unpacking sgml-base (1.31) ...
Selecting previously unselected package netbase.
Preparing to unpack .../002-netbase_6.4_all.deb ...
Unpacking netbase (6.4) ...
Selecting previously unselected package libproc2-0:arm64.
Preparing to unpack .../003-libproc2-0_2%3a4.0.3-1_arm64.deb ...
Unpacking libproc2-0:arm64 (2:4.0.3-1) ...
Selecting previously unselected package procps.
Preparing to unpack .../004-procps_2%3a4.0.3-1_arm64.deb ...
Unpacking procps (2:4.0.3-1) ...
Selecting previously unselected package sensible-utils.
Preparing to unpack .../005-sensible-utils_0.0.17+nmu1_all.deb ...
Unpacking sensible-utils (0.0.17+nmu1) ...
Selecting previously unselected package openssl.
Preparing to unpack .../006-openssl_3.0.8-1_arm64.deb ...
Unpacking openssl (3.0.8-1) ...
Selecting previously unselected package ca-certificates.
Preparing to unpack .../007-ca-certificates_20211016_all.deb ...
Unpacking ca-certificates (20211016) ...
Selecting previously unselected package libmagic-mgc.
Preparing to unpack .../008-libmagic-mgc_1%3a5.44-3_arm64.deb ...
Unpacking libmagic-mgc (1:5.44-3) ...
Selecting previously unselected package libmagic1:arm64.
Preparing to unpack .../009-libmagic1_1%3a5.44-3_arm64.deb ...
Unpacking libmagic1:arm64 (1:5.44-3) ...
Selecting previously unselected package file.
Preparing to unpack .../010-file_1%3a5.44-3_arm64.deb ...
Unpacking file (1:5.44-3) ...
Selecting previously unselected package gettext-base.
Preparing to unpack .../011-gettext-base_0.21-12_arm64.deb ...
Unpacking gettext-base (0.21-12) ...
Selecting previously unselected package libuchardet0:arm64.
Preparing to unpack .../012-libuchardet0_0.0.7-1_arm64.deb ...
Unpacking libuchardet0:arm64 (0.0.7-1) ...
Selecting previously unselected package groff-base.
Preparing to unpack .../013-groff-base_1.22.4-10_arm64.deb ...
Unpacking groff-base (1.22.4-10) ...
Selecting previously unselected package libpam-systemd:arm64.
Preparing to unpack .../014-libpam-systemd_252.6-1_arm64.deb ...
Unpacking libpam-systemd:arm64 (252.6-1) ...
Selecting previously unselected package bsdextrautils.
Preparing to unpack .../015-bsdextrautils_2.38.1-5_arm64.deb ...
Unpacking bsdextrautils (2.38.1-5) ...
Selecting previously unselected package libpipeline1:arm64.
Preparing to unpack .../016-libpipeline1_1.5.7-1_arm64.deb ...
Unpacking libpipeline1:arm64 (1.5.7-1) ...
Selecting previously unselected package man-db.
Preparing to unpack .../017-man-db_2.11.2-1_arm64.deb ...
Unpacking man-db (2.11.2-1) ...
Selecting previously unselected package ucf.
Preparing to unpack .../018-ucf_3.0043+nmu1_all.deb ...
Moving old data out of the way
Unpacking ucf (3.0043+nmu1) ...
Selecting previously unselected package hicolor-icon-theme.
Preparing to unpack .../019-hicolor-icon-theme_0.17-2_all.deb ...
Unpacking hicolor-icon-theme (0.17-2) ...
Selecting previously unselected package libgdk-pixbuf2.0-common.
Preparing to unpack .../020-libgdk-pixbuf2.0-common_2.42.10+dfsg-1_all.deb ...
Unpacking libgdk-pixbuf2.0-common (2.42.10+dfsg-1) ...
Selecting previously unselected package libglib2.0-0:arm64.
Preparing to unpack .../021-libglib2.0-0_2.74.6-1_arm64.deb ...
Unpacking libglib2.0-0:arm64 (2.74.6-1) ...
Selecting previously unselected package libicu72:arm64.
Preparing to unpack .../022-libicu72_72.1-3_arm64.deb ...
Unpacking libicu72:arm64 (72.1-3) ...
Selecting previously unselected package libxml2:arm64.
Preparing to unpack .../023-libxml2_2.9.14+dfsg-1.1+b3_arm64.deb ...
Unpacking libxml2:arm64 (2.9.14+dfsg-1.1+b3) ...
Selecting previously unselected package shared-mime-info.
Preparing to unpack .../024-shared-mime-info_2.2-1_arm64.deb ...
Unpacking shared-mime-info (2.2-1) ...
Selecting previously unselected package libjpeg62-turbo:arm64.
Preparing to unpack .../025-libjpeg62-turbo_1%3a2.1.5-2_arm64.deb ...
Unpacking libjpeg62-turbo:arm64 (1:2.1.5-2) ...
Selecting previously unselected package libpng16-16:arm64.
Preparing to unpack .../026-libpng16-16_1.6.39-2_arm64.deb ...
Unpacking libpng16-16:arm64 (1.6.39-2) ...
Selecting previously unselected package libdeflate0:arm64.
Preparing to unpack .../027-libdeflate0_1.14-1_arm64.deb ...
Unpacking libdeflate0:arm64 (1.14-1) ...
Selecting previously unselected package libjbig0:arm64.
Preparing to unpack .../028-libjbig0_2.1-6.1_arm64.deb ...
Unpacking libjbig0:arm64 (2.1-6.1) ...
Selecting previously unselected package liblerc4:arm64.
Preparing to unpack .../029-liblerc4_4.0.0+ds-2_arm64.deb ...
Unpacking liblerc4:arm64 (4.0.0+ds-2) ...
Selecting previously unselected package libwebp7:arm64.
Preparing to unpack .../030-libwebp7_1.2.4-0.1_arm64.deb ...
Unpacking libwebp7:arm64 (1.2.4-0.1) ...
Selecting previously unselected package libtiff6:arm64.
Preparing to unpack .../031-libtiff6_4.5.0-5_arm64.deb ...
Unpacking libtiff6:arm64 (4.5.0-5) ...
Selecting previously unselected package libgdk-pixbuf-2.0-0:arm64.
Preparing to unpack .../032-libgdk-pixbuf-2.0-0_2.42.10+dfsg-1+b1_arm64.deb ...
Unpacking libgdk-pixbuf-2.0-0:arm64 (2.42.10+dfsg-1+b1) ...
Selecting previously unselected package gtk-update-icon-cache.
Preparing to unpack .../033-gtk-update-icon-cache_3.24.36-4_arm64.deb ...
Unpacking gtk-update-icon-cache (3.24.36-4) ...
Selecting previously unselected package adwaita-icon-theme.
Preparing to unpack .../034-adwaita-icon-theme_43-1_all.deb ...
Unpacking adwaita-icon-theme (43-1) ...
Selecting previously unselected package at-spi2-common.
Preparing to unpack .../035-at-spi2-common_2.46.0-5_all.deb ...
Unpacking at-spi2-common (2.46.0-5) ...
Selecting previously unselected package m4.
Preparing to unpack .../036-m4_1.4.19-3_arm64.deb ...
Unpacking m4 (1.4.19-3) ...
Selecting previously unselected package autoconf.
Preparing to unpack .../037-autoconf_2.71-3_all.deb ...
Unpacking autoconf (2.71-3) ...
Selecting previously unselected package autotools-dev.
Preparing to unpack .../038-autotools-dev_20220109.1_all.deb ...
Unpacking autotools-dev (20220109.1) ...
Selecting previously unselected package automake.
Preparing to unpack .../039-automake_1%3a1.16.5-1.3_all.deb ...
Unpacking automake (1:1.16.5-1.3) ...
Selecting previously unselected package autopoint.
Preparing to unpack .../040-autopoint_0.21-12_all.deb ...
Unpacking autopoint (0.21-12) ...
Selecting previously unselected package libarchive13:arm64.
Preparing to unpack .../041-libarchive13_3.6.2-1_arm64.deb ...
Unpacking libarchive13:arm64 (3.6.2-1) ...
Selecting previously unselected package libbrotli1:arm64.
Preparing to unpack .../042-libbrotli1_1.0.9-2+b6_arm64.deb ...
Unpacking libbrotli1:arm64 (1.0.9-2+b6) ...
Selecting previously unselected package libsasl2-modules-db:arm64.
Preparing to unpack .../043-libsasl2-modules-db_2.1.28+dfsg-11_arm64.deb ...
Unpacking libsasl2-modules-db:arm64 (2.1.28+dfsg-11) ...
Selecting previously unselected package libsasl2-2:arm64.
Preparing to unpack .../044-libsasl2-2_2.1.28+dfsg-11_arm64.deb ...
Unpacking libsasl2-2:arm64 (2.1.28+dfsg-11) ...
Selecting previously unselected package libldap-2.5-0:arm64.
Preparing to unpack .../045-libldap-2.5-0_2.5.13+dfsg-5_arm64.deb ...
Unpacking libldap-2.5-0:arm64 (2.5.13+dfsg-5) ...
Selecting previously unselected package libnghttp2-14:arm64.
Preparing to unpack .../046-libnghttp2-14_1.52.0-1_arm64.deb ...
Unpacking libnghttp2-14:arm64 (1.52.0-1) ...
Selecting previously unselected package libpsl5:arm64.
Preparing to unpack .../047-libpsl5_0.21.2-1_arm64.deb ...
Unpacking libpsl5:arm64 (0.21.2-1) ...
Selecting previously unselected package librtmp1:arm64.
Preparing to unpack .../048-librtmp1_2.4+20151223.gitfa8646d.1-2+b2_arm64.deb ...
Unpacking librtmp1:arm64 (2.4+20151223.gitfa8646d.1-2+b2) ...
Selecting previously unselected package libssh2-1:arm64.
Preparing to unpack .../049-libssh2-1_1.10.0-3+b1_arm64.deb ...
Unpacking libssh2-1:arm64 (1.10.0-3+b1) ...
Selecting previously unselected package libcurl4:arm64.
Preparing to unpack .../050-libcurl4_7.88.1-5_arm64.deb ...
Unpacking libcurl4:arm64 (7.88.1-5) ...
Selecting previously unselected package libjsoncpp25:arm64.
Preparing to unpack .../051-libjsoncpp25_1.9.5-4_arm64.deb ...
Unpacking libjsoncpp25:arm64 (1.9.5-4) ...
Selecting previously unselected package librhash0:arm64.
Preparing to unpack .../052-librhash0_1.4.3-3_arm64.deb ...
Unpacking librhash0:arm64 (1.4.3-3) ...
Selecting previously unselected package libuv1:arm64.
Preparing to unpack .../053-libuv1_1.44.2-1_arm64.deb ...
Unpacking libuv1:arm64 (1.44.2-1) ...
Selecting previously unselected package cmake-data.
Preparing to unpack .../054-cmake-data_3.25.1-1_all.deb ...
Unpacking cmake-data (3.25.1-1) ...
Selecting previously unselected package cmake.
Preparing to unpack .../055-cmake_3.25.1-1_arm64.deb ...
Unpacking cmake (3.25.1-1) ...
Selecting previously unselected package gcc-12-i686-linux-gnu-base:arm64.
Preparing to unpack .../056-gcc-12-i686-linux-gnu-base_12.2.0-14cross1_arm64.deb ...
Unpacking gcc-12-i686-linux-gnu-base:arm64 (12.2.0-14cross1) ...
Selecting previously unselected package cpp-12-i686-linux-gnu.
Preparing to unpack .../057-cpp-12-i686-linux-gnu_12.2.0-14cross1_arm64.deb ...
Unpacking cpp-12-i686-linux-gnu (12.2.0-14cross1) ...
Selecting previously unselected package cpp-i686-linux-gnu.
Preparing to unpack .../058-cpp-i686-linux-gnu_4%3a12.2.0-3_arm64.deb ...
Unpacking cpp-i686-linux-gnu (4:12.2.0-3) ...
Selecting previously unselected package cross-config.
Preparing to unpack .../059-cross-config_2.6.20_all.deb ...
Unpacking cross-config (2.6.20) ...
Selecting previously unselected package binutils-i686-linux-gnu.
Preparing to unpack .../060-binutils-i686-linux-gnu_2.40-2_arm64.deb ...
Unpacking binutils-i686-linux-gnu (2.40-2) ...
Selecting previously unselected package gcc-12-cross-base.
Preparing to unpack .../061-gcc-12-cross-base_12.2.0-14cross1_all.deb ...
Unpacking gcc-12-cross-base (12.2.0-14cross1) ...
Selecting previously unselected package libc6-i386-cross.
Preparing to unpack .../062-libc6-i386-cross_2.36-8cross1_all.deb ...
Unpacking libc6-i386-cross (2.36-8cross1) ...
Selecting previously unselected package libgcc-s1-i386-cross.
Preparing to unpack .../063-libgcc-s1-i386-cross_12.2.0-14cross1_all.deb ...
Unpacking libgcc-s1-i386-cross (12.2.0-14cross1) ...
Selecting previously unselected package libgomp1-i386-cross.
Preparing to unpack .../064-libgomp1-i386-cross_12.2.0-14cross1_all.deb ...
Unpacking libgomp1-i386-cross (12.2.0-14cross1) ...
Selecting previously unselected package libitm1-i386-cross.
Preparing to unpack .../065-libitm1-i386-cross_12.2.0-14cross1_all.deb ...
Unpacking libitm1-i386-cross (12.2.0-14cross1) ...
Selecting previously unselected package libatomic1-i386-cross.
Preparing to unpack .../066-libatomic1-i386-cross_12.2.0-14cross1_all.deb ...
Unpacking libatomic1-i386-cross (12.2.0-14cross1) ...
Selecting previously unselected package libasan8-i386-cross.
Preparing to unpack .../067-libasan8-i386-cross_12.2.0-14cross1_all.deb ...
Unpacking libasan8-i386-cross (12.2.0-14cross1) ...
Selecting previously unselected package libstdc++6-i386-cross.
Preparing to unpack .../068-libstdc++6-i386-cross_12.2.0-14cross1_all.deb ...
Unpacking libstdc++6-i386-cross (12.2.0-14cross1) ...
Selecting previously unselected package libubsan1-i386-cross.
Preparing to unpack .../069-libubsan1-i386-cross_12.2.0-14cross1_all.deb ...
Unpacking libubsan1-i386-cross (12.2.0-14cross1) ...
Selecting previously unselected package libquadmath0-i386-cross.
Preparing to unpack .../070-libquadmath0-i386-cross_12.2.0-14cross1_all.deb ...
Unpacking libquadmath0-i386-cross (12.2.0-14cross1) ...
Selecting previously unselected package libgcc-12-dev-i386-cross.
Preparing to unpack .../071-libgcc-12-dev-i386-cross_12.2.0-14cross1_all.deb ...
Unpacking libgcc-12-dev-i386-cross (12.2.0-14cross1) ...
Selecting previously unselected package gcc-12-i686-linux-gnu.
Preparing to unpack .../072-gcc-12-i686-linux-gnu_12.2.0-14cross1_arm64.deb ...
Unpacking gcc-12-i686-linux-gnu (12.2.0-14cross1) ...
Selecting previously unselected package gcc-i686-linux-gnu.
Preparing to unpack .../073-gcc-i686-linux-gnu_4%3a12.2.0-3_arm64.deb ...
Unpacking gcc-i686-linux-gnu (4:12.2.0-3) ...
Selecting previously unselected package linux-libc-dev-i386-cross.
Preparing to unpack .../074-linux-libc-dev-i386-cross_6.1.4-1cross1_all.deb ...
Unpacking linux-libc-dev-i386-cross (6.1.4-1cross1) ...
Selecting previously unselected package libc6-dev-i386-cross.
Preparing to unpack .../075-libc6-dev-i386-cross_2.36-8cross1_all.deb ...
Unpacking libc6-dev-i386-cross (2.36-8cross1) ...
Selecting previously unselected package libstdc++-12-dev-i386-cross.
Preparing to unpack .../076-libstdc++-12-dev-i386-cross_12.2.0-14cross1_all.deb ...
Unpacking libstdc++-12-dev-i386-cross (12.2.0-14cross1) ...
Selecting previously unselected package g++-12-i686-linux-gnu.
Preparing to unpack .../077-g++-12-i686-linux-gnu_12.2.0-14cross1_arm64.deb ...
Unpacking g++-12-i686-linux-gnu (12.2.0-14cross1) ...
Selecting previously unselected package g++-i686-linux-gnu.
Preparing to unpack .../078-g++-i686-linux-gnu_4%3a12.2.0-3_arm64.deb ...
Unpacking g++-i686-linux-gnu (4:12.2.0-3) ...
Selecting previously unselected package libconfig-inifiles-perl.
Preparing to unpack .../079-libconfig-inifiles-perl_3.000003-2_all.deb ...
Unpacking libconfig-inifiles-perl (3.000003-2) ...
Selecting previously unselected package libio-string-perl.
Preparing to unpack .../080-libio-string-perl_1.08-4_all.deb ...
Unpacking libio-string-perl (1.08-4) ...
Selecting previously unselected package libxml-namespacesupport-perl.
Preparing to unpack .../081-libxml-namespacesupport-perl_1.12-2_all.deb ...
Unpacking libxml-namespacesupport-perl (1.12-2) ...
Selecting previously unselected package libxml-sax-base-perl.
Preparing to unpack .../082-libxml-sax-base-perl_1.09-3_all.deb ...
Unpacking libxml-sax-base-perl (1.09-3) ...
Selecting previously unselected package libxml-sax-perl.
Preparing to unpack .../083-libxml-sax-perl_1.02+dfsg-3_all.deb ...
Unpacking libxml-sax-perl (1.02+dfsg-3) ...
Selecting previously unselected package libxml-libxml-perl.
Preparing to unpack .../084-libxml-libxml-perl_2.0207+dfsg+really+2.0134-1+b1_arm64.deb ...
Unpacking libxml-libxml-perl (2.0207+dfsg+really+2.0134-1+b1) ...
Selecting previously unselected package libxml-simple-perl.
Preparing to unpack .../085-libxml-simple-perl_2.25-2_all.deb ...
Unpacking libxml-simple-perl (2.25-2) ...
Selecting previously unselected package libyaml-perl.
Preparing to unpack .../086-libyaml-perl_1.30-2_all.deb ...
Unpacking libyaml-perl (1.30-2) ...
Selecting previously unselected package libconfig-auto-perl.
Preparing to unpack .../087-libconfig-auto-perl_0.44-2_all.deb ...
Unpacking libconfig-auto-perl (0.44-2) ...
Selecting previously unselected package libfile-which-perl.
Preparing to unpack .../088-libfile-which-perl_1.27-2_all.deb ...
Unpacking libfile-which-perl (1.27-2) ...
Selecting previously unselected package libfile-homedir-perl.
Preparing to unpack .../089-libfile-homedir-perl_1.006-2_all.deb ...
Unpacking libfile-homedir-perl (1.006-2) ...
Selecting previously unselected package libdebian-dpkgcross-perl.
Preparing to unpack .../090-libdebian-dpkgcross-perl_2.6.20_all.deb ...
Unpacking libdebian-dpkgcross-perl (2.6.20) ...
Selecting previously unselected package dpkg-cross.
Preparing to unpack .../091-dpkg-cross_2.6.20_all.deb ...
Unpacking dpkg-cross (2.6.20) ...
Selecting previously unselected package crossbuild-essential-i386.
Preparing to unpack .../092-crossbuild-essential-i386_12.9_all.deb ...
Unpacking crossbuild-essential-i386 (12.9) ...
Selecting previously unselected package dbus-user-session.
Preparing to unpack .../093-dbus-user-session_1.14.6-1_arm64.deb ...
Unpacking dbus-user-session (1.14.6-1) ...
Selecting previously unselected package libdconf1:arm64.
Preparing to unpack .../094-libdconf1_0.40.0-4_arm64.deb ...
Unpacking libdconf1:arm64 (0.40.0-4) ...
Selecting previously unselected package dconf-service.
Preparing to unpack .../095-dconf-service_0.40.0-4_arm64.deb ...
Unpacking dconf-service (0.40.0-4) ...
Selecting previously unselected package dconf-gsettings-backend:arm64.
Preparing to unpack .../096-dconf-gsettings-backend_0.40.0-4_arm64.deb ...
Unpacking dconf-gsettings-backend:arm64 (0.40.0-4) ...
Selecting previously unselected package libdebhelper-perl.
Preparing to unpack .../097-libdebhelper-perl_13.11.4_all.deb ...
Unpacking libdebhelper-perl (13.11.4) ...
Selecting previously unselected package libtool.
Preparing to unpack .../098-libtool_2.4.7-5_all.deb ...
Unpacking libtool (2.4.7-5) ...
Selecting previously unselected package dh-autoreconf.
Preparing to unpack .../099-dh-autoreconf_20_all.deb ...
Unpacking dh-autoreconf (20) ...
Selecting previously unselected package libarchive-zip-perl.
Preparing to unpack .../100-libarchive-zip-perl_1.68-1_all.deb ...
Unpacking libarchive-zip-perl (1.68-1) ...
Selecting previously unselected package libsub-override-perl.
Preparing to unpack .../101-libsub-override-perl_0.09-4_all.deb ...
Unpacking libsub-override-perl (0.09-4) ...
Selecting previously unselected package libfile-stripnondeterminism-perl.
Preparing to unpack .../102-libfile-stripnondeterminism-perl_1.13.1-1_all.deb ...
Unpacking libfile-stripnondeterminism-perl (1.13.1-1) ...
Selecting previously unselected package dh-strip-nondeterminism.
Preparing to unpack .../103-dh-strip-nondeterminism_1.13.1-1_all.deb ...
Unpacking dh-strip-nondeterminism (1.13.1-1) ...
Selecting previously unselected package libelf1:arm64.
Preparing to unpack .../104-libelf1_0.188-2.1_arm64.deb ...
Unpacking libelf1:arm64 (0.188-2.1) ...
Selecting previously unselected package dwz.
Preparing to unpack .../105-dwz_0.15-1_arm64.deb ...
Unpacking dwz (0.15-1) ...
Selecting previously unselected package gettext.
Preparing to unpack .../106-gettext_0.21-12_arm64.deb ...
Unpacking gettext (0.21-12) ...
Selecting previously unselected package intltool-debian.
Preparing to unpack .../107-intltool-debian_0.35.0+20060710.6_all.deb ...
Unpacking intltool-debian (0.35.0+20060710.6) ...
Selecting previously unselected package po-debconf.
Preparing to unpack .../108-po-debconf_1.0.21+nmu1_all.deb ...
Unpacking po-debconf (1.0.21+nmu1) ...
Selecting previously unselected package debhelper.
Preparing to unpack .../109-debhelper_13.11.4_all.deb ...
Unpacking debhelper (13.11.4) ...
Selecting previously unselected package libfreetype6:arm64.
Preparing to unpack .../110-libfreetype6_2.12.1+dfsg-4_arm64.deb ...
Unpacking libfreetype6:arm64 (2.12.1+dfsg-4) ...
Selecting previously unselected package fonts-dejavu-core.
Preparing to unpack .../111-fonts-dejavu-core_2.37-5_all.deb ...
Unpacking fonts-dejavu-core (2.37-5) ...
Selecting previously unselected package fontconfig-config.
Preparing to unpack .../112-fontconfig-config_2.14.1-4_arm64.deb ...
Unpacking fontconfig-config (2.14.1-4) ...
Selecting previously unselected package libfontconfig1:arm64.
Preparing to unpack .../113-libfontconfig1_2.14.1-4_arm64.deb ...
Unpacking libfontconfig1:arm64 (2.14.1-4) ...
Selecting previously unselected package fontconfig.
Preparing to unpack .../114-fontconfig_2.14.1-4_arm64.deb ...
Unpacking fontconfig (2.14.1-4) ...
Selecting previously unselected package gcc-12-base:i386.
Preparing to unpack .../115-gcc-12-base_12.2.0-14_i386.deb ...
Unpacking gcc-12-base:i386 (12.2.0-14) ...
Selecting previously unselected package libdbus-glib-1-2:arm64.
Preparing to unpack .../116-libdbus-glib-1-2_0.112-3_arm64.deb ...
Unpacking libdbus-glib-1-2:arm64 (0.112-3) ...
Selecting previously unselected package gconf2-common.
Preparing to unpack .../117-gconf2-common_3.2.6-8_all.deb ...
Unpacking gconf2-common (3.2.6-8) ...
Selecting previously unselected package libgconf-2-4:arm64.
Preparing to unpack .../118-libgconf-2-4_3.2.6-8_arm64.deb ...
Unpacking libgconf-2-4:arm64 (3.2.6-8) ...
Selecting previously unselected package gconf-service.
Preparing to unpack .../119-gconf-service_3.2.6-8_arm64.deb ...
Unpacking gconf-service (3.2.6-8) ...
Selecting previously unselected package psmisc.
Preparing to unpack .../120-psmisc_23.6-1_arm64.deb ...
Unpacking psmisc (23.6-1) ...
Selecting previously unselected package gconf2.
Preparing to unpack .../121-gconf2_3.2.6-8_arm64.deb ...
Unpacking gconf2 (3.2.6-8) ...
Selecting previously unselected package libgcc-s1:i386.
Preparing to unpack .../122-libgcc-s1_12.2.0-14_i386.deb ...
Unpacking libgcc-s1:i386 (12.2.0-14) ...
Selecting previously unselected package libc6:i386.
Preparing to unpack .../123-libc6_2.36-8_i386.deb ...
Unpacking libc6:i386 (2.36-8) ...
Selecting previously unselected package libffi8:i386.
Preparing to unpack .../124-libffi8_3.4.4-1_i386.deb ...
Unpacking libffi8:i386 (3.4.4-1) ...
Selecting previously unselected package libblkid1:i386.
Preparing to unpack .../125-libblkid1_2.38.1-5_i386.deb ...
Unpacking libblkid1:i386 (2.38.1-5) ...
Selecting previously unselected package libpcre2-8-0:i386.
Preparing to unpack .../126-libpcre2-8-0_10.42-1_i386.deb ...
Unpacking libpcre2-8-0:i386 (10.42-1) ...
Selecting previously unselected package libselinux1:i386.
Preparing to unpack .../127-libselinux1_3.4-1+b5_i386.deb ...
Unpacking libselinux1:i386 (3.4-1+b5) ...
Selecting previously unselected package libmount1:i386.
Preparing to unpack .../128-libmount1_2.38.1-5_i386.deb ...
Unpacking libmount1:i386 (2.38.1-5) ...
Selecting previously unselected package zlib1g:i386.
Preparing to unpack .../129-zlib1g_1%3a1.2.13.dfsg-1_i386.deb ...
Unpacking zlib1g:i386 (1:1.2.13.dfsg-1) ...
Selecting previously unselected package libglib2.0-0:i386.
Preparing to unpack .../130-libglib2.0-0_2.74.6-1_i386.deb ...
Unpacking libglib2.0-0:i386 (2.74.6-1) ...
Selecting previously unselected package libgirepository-1.0-1:i386.
Preparing to unpack .../131-libgirepository-1.0-1_1.74.0-3_i386.deb ...
Unpacking libgirepository-1.0-1:i386 (1.74.0-3) ...
Selecting previously unselected package gir1.2-glib-2.0:i386.
Preparing to unpack .../132-gir1.2-glib-2.0_1.74.0-3_i386.deb ...
Unpacking gir1.2-glib-2.0:i386 (1.74.0-3) ...
Selecting previously unselected package libatk1.0-0:i386.
Preparing to unpack .../133-libatk1.0-0_2.46.0-5_i386.deb ...
Unpacking libatk1.0-0:i386 (2.46.0-5) ...
Selecting previously unselected package gir1.2-atk-1.0:i386.
Preparing to unpack .../134-gir1.2-atk-1.0_2.46.0-5_i386.deb ...
Unpacking gir1.2-atk-1.0:i386 (2.46.0-5) ...
Selecting previously unselected package gir1.2-freedesktop:i386.
Preparing to unpack .../135-gir1.2-freedesktop_1.74.0-3_i386.deb ...
Unpacking gir1.2-freedesktop:i386 (1.74.0-3) ...
Selecting previously unselected package libcap2:i386.
Preparing to unpack .../136-libcap2_1%3a2.66-3_i386.deb ...
Unpacking libcap2:i386 (1:2.66-3) ...
Selecting previously unselected package libgpg-error0:i386.
Preparing to unpack .../137-libgpg-error0_1.46-1_i386.deb ...
Unpacking libgpg-error0:i386 (1.46-1) ...
Selecting previously unselected package libgcrypt20:i386.
Preparing to unpack .../138-libgcrypt20_1.10.1-3_i386.deb ...
Unpacking libgcrypt20:i386 (1.10.1-3) ...
Selecting previously unselected package liblz4-1:i386.
Preparing to unpack .../139-liblz4-1_1.9.4-1_i386.deb ...
Unpacking liblz4-1:i386 (1.9.4-1) ...
Selecting previously unselected package liblzma5:i386.
Preparing to unpack .../140-liblzma5_5.4.1-0.2_i386.deb ...
Unpacking liblzma5:i386 (5.4.1-0.2) ...
Selecting previously unselected package libzstd1:i386.
Preparing to unpack .../141-libzstd1_1.5.4+dfsg2-3_i386.deb ...
Unpacking libzstd1:i386 (1.5.4+dfsg2-3) ...
Selecting previously unselected package libsystemd0:i386.
Preparing to unpack .../142-libsystemd0_252.6-1_i386.deb ...
Unpacking libsystemd0:i386 (252.6-1) ...
Selecting previously unselected package libdbus-1-3:i386.
Preparing to unpack .../143-libdbus-1-3_1.14.6-1_i386.deb ...
Unpacking libdbus-1-3:i386 (1.14.6-1) ...
Selecting previously unselected package libxau6:i386.
Preparing to unpack .../144-libxau6_1%3a1.0.9-1_i386.deb ...
Unpacking libxau6:i386 (1:1.0.9-1) ...
Selecting previously unselected package libmd0:i386.
Preparing to unpack .../145-libmd0_1.0.4-2_i386.deb ...
Unpacking libmd0:i386 (1.0.4-2) ...
Selecting previously unselected package libbsd0:i386.
Preparing to unpack .../146-libbsd0_0.11.7-4_i386.deb ...
Unpacking libbsd0:i386 (0.11.7-4) ...
Selecting previously unselected package libxdmcp6:i386.
Preparing to unpack .../147-libxdmcp6_1%3a1.1.2-3_i386.deb ...
Unpacking libxdmcp6:i386 (1:1.1.2-3) ...
Selecting previously unselected package libxcb1:i386.
Preparing to unpack .../148-libxcb1_1.15-1_i386.deb ...
Unpacking libxcb1:i386 (1.15-1) ...
Selecting previously unselected package libx11-data.
Preparing to unpack .../149-libx11-data_2%3a1.8.4-2_all.deb ...
Unpacking libx11-data (2:1.8.4-2) ...
Selecting previously unselected package libx11-6:i386.
Preparing to unpack .../150-libx11-6_2%3a1.8.4-2_i386.deb ...
Unpacking libx11-6:i386 (2:1.8.4-2) ...
Selecting previously unselected package libxext6:i386.
Preparing to unpack .../151-libxext6_2%3a1.3.4-1+b1_i386.deb ...
Unpacking libxext6:i386 (2:1.3.4-1+b1) ...
Selecting previously unselected package libxi6:i386.
Preparing to unpack .../152-libxi6_2%3a1.8-1+b1_i386.deb ...
Unpacking libxi6:i386 (2:1.8-1+b1) ...
Selecting previously unselected package libatspi2.0-0:i386.
Preparing to unpack .../153-libatspi2.0-0_2.46.0-5_i386.deb ...
Unpacking libatspi2.0-0:i386 (2.46.0-5) ...
Selecting previously unselected package gir1.2-atspi-2.0:i386.
Preparing to unpack .../154-gir1.2-atspi-2.0_2.46.0-5_i386.deb ...
Unpacking gir1.2-atspi-2.0:i386 (2.46.0-5) ...
Selecting previously unselected package libjpeg62-turbo:i386.
Preparing to unpack .../155-libjpeg62-turbo_1%3a2.1.5-2_i386.deb ...
Unpacking libjpeg62-turbo:i386 (1:2.1.5-2) ...
Selecting previously unselected package libpng16-16:i386.
Preparing to unpack .../156-libpng16-16_1.6.39-2_i386.deb ...
Unpacking libpng16-16:i386 (1.6.39-2) ...
Selecting previously unselected package libdeflate0:i386.
Preparing to unpack .../157-libdeflate0_1.14-1_i386.deb ...
Unpacking libdeflate0:i386 (1.14-1) ...
Selecting previously unselected package libjbig0:i386.
Preparing to unpack .../158-libjbig0_2.1-6.1_i386.deb ...
Unpacking libjbig0:i386 (2.1-6.1) ...
Selecting previously unselected package libstdc++6:i386.
Preparing to unpack .../159-libstdc++6_12.2.0-14_i386.deb ...
Unpacking libstdc++6:i386 (12.2.0-14) ...
Selecting previously unselected package liblerc4:i386.
Preparing to unpack .../160-liblerc4_4.0.0+ds-2_i386.deb ...
Unpacking liblerc4:i386 (4.0.0+ds-2) ...
Selecting previously unselected package libwebp7:i386.
Preparing to unpack .../161-libwebp7_1.2.4-0.1_i386.deb ...
Unpacking libwebp7:i386 (1.2.4-0.1) ...
Selecting previously unselected package libtiff6:i386.
Preparing to unpack .../162-libtiff6_4.5.0-5_i386.deb ...
Unpacking libtiff6:i386 (4.5.0-5) ...
Selecting previously unselected package libgdk-pixbuf-2.0-0:i386.
Preparing to unpack .../163-libgdk-pixbuf-2.0-0_2.42.10+dfsg-1+b1_i386.deb ...
Unpacking libgdk-pixbuf-2.0-0:i386 (2.42.10+dfsg-1+b1) ...
Selecting previously unselected package gir1.2-gdkpixbuf-2.0:i386.
Preparing to unpack .../164-gir1.2-gdkpixbuf-2.0_2.42.10+dfsg-1+b1_i386.deb ...
Unpacking gir1.2-gdkpixbuf-2.0:i386 (2.42.10+dfsg-1+b1) ...
Selecting previously unselected package gir1.2-harfbuzz-0.0:i386.
Preparing to unpack .../165-gir1.2-harfbuzz-0.0_6.0.0+dfsg-3_i386.deb ...
Unpacking gir1.2-harfbuzz-0.0:i386 (6.0.0+dfsg-3) ...
Selecting previously unselected package libfribidi0:i386.
Preparing to unpack .../166-libfribidi0_1.0.8-2.1_i386.deb ...
Unpacking libfribidi0:i386 (1.0.8-2.1) ...
Selecting previously unselected package libbrotli1:i386.
Preparing to unpack .../167-libbrotli1_1.0.9-2+b6_i386.deb ...
Unpacking libbrotli1:i386 (1.0.9-2+b6) ...
Selecting previously unselected package libfreetype6:i386.
Preparing to unpack .../168-libfreetype6_2.12.1+dfsg-4_i386.deb ...
Unpacking libfreetype6:i386 (2.12.1+dfsg-4) ...
Selecting previously unselected package libgraphite2-3:i386.
Preparing to unpack .../169-libgraphite2-3_1.3.14-1_i386.deb ...
Unpacking libgraphite2-3:i386 (1.3.14-1) ...
Selecting previously unselected package libharfbuzz0b:i386.
Preparing to unpack .../170-libharfbuzz0b_6.0.0+dfsg-3_i386.deb ...
Unpacking libharfbuzz0b:i386 (6.0.0+dfsg-3) ...
Selecting previously unselected package libthai-data.
Preparing to unpack .../171-libthai-data_0.1.29-1_all.deb ...
Unpacking libthai-data (0.1.29-1) ...
Selecting previously unselected package libdatrie1:i386.
Preparing to unpack .../172-libdatrie1_0.2.13-2+b1_i386.deb ...
Unpacking libdatrie1:i386 (0.2.13-2+b1) ...
Selecting previously unselected package libthai0:i386.
Preparing to unpack .../173-libthai0_0.1.29-1_i386.deb ...
Unpacking libthai0:i386 (0.1.29-1) ...
Selecting previously unselected package libpango-1.0-0:i386.
Preparing to unpack .../174-libpango-1.0-0_1.50.12+ds-1_i386.deb ...
Unpacking libpango-1.0-0:i386 (1.50.12+ds-1) ...
Selecting previously unselected package libexpat1:i386.
Preparing to unpack .../175-libexpat1_2.5.0-1_i386.deb ...
Unpacking libexpat1:i386 (2.5.0-1) ...
Selecting previously unselected package libfontconfig1:i386.
Preparing to unpack .../176-libfontconfig1_2.14.1-4_i386.deb ...
Unpacking libfontconfig1:i386 (2.14.1-4) ...
Selecting previously unselected package libpixman-1-0:i386.
Preparing to unpack .../177-libpixman-1-0_0.42.2-1_i386.deb ...
Unpacking libpixman-1-0:i386 (0.42.2-1) ...
Selecting previously unselected package libxcb-render0:i386.
Preparing to unpack .../178-libxcb-render0_1.15-1_i386.deb ...
Unpacking libxcb-render0:i386 (1.15-1) ...
Selecting previously unselected package libxcb-shm0:i386.
Preparing to unpack .../179-libxcb-shm0_1.15-1_i386.deb ...
Unpacking libxcb-shm0:i386 (1.15-1) ...
Selecting previously unselected package libxrender1:i386.
Preparing to unpack .../180-libxrender1_1%3a0.9.10-1.1_i386.deb ...
Unpacking libxrender1:i386 (1:0.9.10-1.1) ...
Selecting previously unselected package libcairo2:i386.
Preparing to unpack .../181-libcairo2_1.16.0-7_i386.deb ...
Unpacking libcairo2:i386 (1.16.0-7) ...
Selecting previously unselected package libpangoft2-1.0-0:i386.
Preparing to unpack .../182-libpangoft2-1.0-0_1.50.12+ds-1_i386.deb ...
Unpacking libpangoft2-1.0-0:i386 (1.50.12+ds-1) ...
Selecting previously unselected package libpangocairo-1.0-0:i386.
Preparing to unpack .../183-libpangocairo-1.0-0_1.50.12+ds-1_i386.deb ...
Unpacking libpangocairo-1.0-0:i386 (1.50.12+ds-1) ...
Selecting previously unselected package libxft2:i386.
Preparing to unpack .../184-libxft2_2.3.6-1_i386.deb ...
Unpacking libxft2:i386 (2.3.6-1) ...
Selecting previously unselected package libpangoxft-1.0-0:i386.
Preparing to unpack .../185-libpangoxft-1.0-0_1.50.12+ds-1_i386.deb ...
Unpacking libpangoxft-1.0-0:i386 (1.50.12+ds-1) ...
Selecting previously unselected package gir1.2-pango-1.0:i386.
Preparing to unpack .../186-gir1.2-pango-1.0_1.50.12+ds-1_i386.deb ...
Unpacking gir1.2-pango-1.0:i386 (1.50.12+ds-1) ...
Selecting previously unselected package libatk-bridge2.0-0:i386.
Preparing to unpack .../187-libatk-bridge2.0-0_2.46.0-5_i386.deb ...
Unpacking libatk-bridge2.0-0:i386 (2.46.0-5) ...
Selecting previously unselected package libcairo-gobject2:i386.
Preparing to unpack .../188-libcairo-gobject2_1.16.0-7_i386.deb ...
Unpacking libcairo-gobject2:i386 (1.16.0-7) ...
Selecting previously unselected package liblcms2-2:i386.
Preparing to unpack .../189-liblcms2-2_2.14-2_i386.deb ...
Unpacking liblcms2-2:i386 (2.14-2) ...
Selecting previously unselected package libudev1:i386.
Preparing to unpack .../190-libudev1_252.6-1_i386.deb ...
Unpacking libudev1:i386 (252.6-1) ...
Selecting previously unselected package libcolord2:i386.
Preparing to unpack .../191-libcolord2_1.4.6-2.2_i386.deb ...
Unpacking libcolord2:i386 (1.4.6-2.2) ...
Selecting previously unselected package libavahi-common-data:i386.
Preparing to unpack .../192-libavahi-common-data_0.8-9_i386.deb ...
Unpacking libavahi-common-data:i386 (0.8-9) ...
Selecting previously unselected package libavahi-common3:i386.
Preparing to unpack .../193-libavahi-common3_0.8-9_i386.deb ...
Unpacking libavahi-common3:i386 (0.8-9) ...
Selecting previously unselected package libavahi-client3:i386.
Preparing to unpack .../194-libavahi-client3_0.8-9_i386.deb ...
Unpacking libavahi-client3:i386 (0.8-9) ...
Selecting previously unselected package libgmp10:i386.
Preparing to unpack .../195-libgmp10_2%3a6.2.1+dfsg1-1.1_i386.deb ...
Unpacking libgmp10:i386 (2:6.2.1+dfsg1-1.1) ...
Selecting previously unselected package libnettle8:i386.
Preparing to unpack .../196-libnettle8_3.8.1-2_i386.deb ...
Unpacking libnettle8:i386 (3.8.1-2) ...
Selecting previously unselected package libhogweed6:i386.
Preparing to unpack .../197-libhogweed6_3.8.1-2_i386.deb ...
Unpacking libhogweed6:i386 (3.8.1-2) ...
Selecting previously unselected package libunistring2:i386.
Preparing to unpack .../198-libunistring2_1.0-2_i386.deb ...
Unpacking libunistring2:i386 (1.0-2) ...
Selecting previously unselected package libidn2-0:i386.
Preparing to unpack .../199-libidn2-0_2.3.3-1+b1_i386.deb ...
Unpacking libidn2-0:i386 (2.3.3-1+b1) ...
Selecting previously unselected package libp11-kit0:i386.
Preparing to unpack .../200-libp11-kit0_0.24.1-2_i386.deb ...
Unpacking libp11-kit0:i386 (0.24.1-2) ...
Selecting previously unselected package libtasn1-6:i386.
Preparing to unpack .../201-libtasn1-6_4.19.0-2_i386.deb ...
Unpacking libtasn1-6:i386 (4.19.0-2) ...
Selecting previously unselected package libgnutls30:i386.
Preparing to unpack .../202-libgnutls30_3.7.9-1_i386.deb ...
Unpacking libgnutls30:i386 (3.7.9-1) ...
Selecting previously unselected package libcom-err2:i386.
Preparing to unpack .../203-libcom-err2_1.47.0-2_i386.deb ...
Unpacking libcom-err2:i386 (1.47.0-2) ...
Selecting previously unselected package libkrb5support0:i386.
Preparing to unpack .../204-libkrb5support0_1.20.1-1_i386.deb ...
Unpacking libkrb5support0:i386 (1.20.1-1) ...
Selecting previously unselected package libk5crypto3:i386.
Preparing to unpack .../205-libk5crypto3_1.20.1-1_i386.deb ...
Unpacking libk5crypto3:i386 (1.20.1-1) ...
Selecting previously unselected package libkeyutils1:i386.
Preparing to unpack .../206-libkeyutils1_1.6.3-2_i386.deb ...
Unpacking libkeyutils1:i386 (1.6.3-2) ...
Selecting previously unselected package libssl3:i386.
Preparing to unpack .../207-libssl3_3.0.8-1_i386.deb ...
Unpacking libssl3:i386 (3.0.8-1) ...
Selecting previously unselected package libkrb5-3:i386.
Preparing to unpack .../208-libkrb5-3_1.20.1-1_i386.deb ...
Unpacking libkrb5-3:i386 (1.20.1-1) ...
Selecting previously unselected package libgssapi-krb5-2:i386.
Preparing to unpack .../209-libgssapi-krb5-2_1.20.1-1_i386.deb ...
Unpacking libgssapi-krb5-2:i386 (1.20.1-1) ...
Selecting previously unselected package libcups2:i386.
Preparing to unpack .../210-libcups2_2.4.2-2_i386.deb ...
Unpacking libcups2:i386 (2.4.2-2) ...
Selecting previously unselected package libepoxy0:i386.
Preparing to unpack .../211-libepoxy0_1.5.10-1_i386.deb ...
Unpacking libepoxy0:i386 (1.5.10-1) ...
Selecting previously unselected package libwayland-client0:i386.
Preparing to unpack .../212-libwayland-client0_1.21.0-1_i386.deb ...
Unpacking libwayland-client0:i386 (1.21.0-1) ...
Selecting previously unselected package libwayland-cursor0:i386.
Preparing to unpack .../213-libwayland-cursor0_1.21.0-1_i386.deb ...
Unpacking libwayland-cursor0:i386 (1.21.0-1) ...
Selecting previously unselected package libwayland-egl1:i386.
Preparing to unpack .../214-libwayland-egl1_1.21.0-1_i386.deb ...
Unpacking libwayland-egl1:i386 (1.21.0-1) ...
Selecting previously unselected package libxcomposite1:i386.
Preparing to unpack .../215-libxcomposite1_1%3a0.4.5-1_i386.deb ...
Unpacking libxcomposite1:i386 (1:0.4.5-1) ...
Selecting previously unselected package libxfixes3:i386.
Preparing to unpack .../216-libxfixes3_1%3a6.0.0-2_i386.deb ...
Unpacking libxfixes3:i386 (1:6.0.0-2) ...
Selecting previously unselected package libxcursor1:i386.
Preparing to unpack .../217-libxcursor1_1%3a1.2.1-1_i386.deb ...
Unpacking libxcursor1:i386 (1:1.2.1-1) ...
Selecting previously unselected package libxdamage1:i386.
Preparing to unpack .../218-libxdamage1_1%3a1.1.6-1_i386.deb ...
Unpacking libxdamage1:i386 (1:1.1.6-1) ...
Selecting previously unselected package libxinerama1:i386.
Preparing to unpack .../219-libxinerama1_2%3a1.1.4-3_i386.deb ...
Unpacking libxinerama1:i386 (2:1.1.4-3) ...
Selecting previously unselected package xkb-data.
Preparing to unpack .../220-xkb-data_2.35.1-1_all.deb ...
Unpacking xkb-data (2.35.1-1) ...
Selecting previously unselected package libxkbcommon0:i386.
Preparing to unpack .../221-libxkbcommon0_1.5.0-1_i386.deb ...
Unpacking libxkbcommon0:i386 (1.5.0-1) ...
Selecting previously unselected package libxrandr2:i386.
Preparing to unpack .../222-libxrandr2_2%3a1.5.2-2+b1_i386.deb ...
Unpacking libxrandr2:i386 (2:1.5.2-2+b1) ...
Selecting previously unselected package libgtk-3-common.
Preparing to unpack .../223-libgtk-3-common_3.24.36-4_all.deb ...
Unpacking libgtk-3-common (3.24.36-4) ...
Selecting previously unselected package libgtk-3-0:i386.
Preparing to unpack .../224-libgtk-3-0_3.24.36-4_i386.deb ...
Unpacking libgtk-3-0:i386 (3.24.36-4) ...
Selecting previously unselected package gir1.2-gtk-3.0:i386.
Preparing to unpack .../225-gir1.2-gtk-3.0_3.24.36-4_i386.deb ...
Unpacking gir1.2-gtk-3.0:i386 (3.24.36-4) ...
Selecting previously unselected package libayatana-ido3-0.4-0:i386.
Preparing to unpack .../226-libayatana-ido3-0.4-0_0.9.3-1_i386.deb ...
Unpacking libayatana-ido3-0.4-0:i386 (0.9.3-1) ...
Selecting previously unselected package libayatana-indicator3-7:i386.
Preparing to unpack .../227-libayatana-indicator3-7_0.9.3-1_i386.deb ...
Unpacking libayatana-indicator3-7:i386 (0.9.3-1) ...
Selecting previously unselected package libdbusmenu-glib4:i386.
Preparing to unpack .../228-libdbusmenu-glib4_18.10.20180917~bzr492+repack1-3_i386.deb ...
Unpacking libdbusmenu-glib4:i386 (18.10.20180917~bzr492+repack1-3) ...
Selecting previously unselected package libdbusmenu-gtk3-4:i386.
Preparing to unpack .../229-libdbusmenu-gtk3-4_18.10.20180917~bzr492+repack1-3_i386.deb ...
Unpacking libdbusmenu-gtk3-4:i386 (18.10.20180917~bzr492+repack1-3) ...
Selecting previously unselected package libayatana-appindicator3-1:i386.
Preparing to unpack .../230-libayatana-appindicator3-1_0.5.92-1_i386.deb ...
Unpacking libayatana-appindicator3-1:i386 (0.5.92-1) ...
Selecting previously unselected package gir1.2-ayatanaappindicator3-0.1:i386.
Preparing to unpack .../231-gir1.2-ayatanaappindicator3-0.1_0.5.92-1_i386.deb ...
Unpacking gir1.2-ayatanaappindicator3-0.1:i386 (0.5.92-1) ...
Selecting previously unselected package gir1.2-ayatanaido3-0.4:i386.
Preparing to unpack .../232-gir1.2-ayatanaido3-0.4_0.9.3-1_i386.deb ...
Unpacking gir1.2-ayatanaido3-0.4:i386 (0.9.3-1) ...
Selecting previously unselected package gir1.2-dbusmenu-glib-0.4:i386.
Preparing to unpack .../233-gir1.2-dbusmenu-glib-0.4_18.10.20180917~bzr492+repack1-3_i386.deb ...
Unpacking gir1.2-dbusmenu-glib-0.4:i386 (18.10.20180917~bzr492+repack1-3) ...
Selecting previously unselected package libdbus-glib-1-2:i386.
Preparing to unpack .../234-libdbus-glib-1-2_0.112-3_i386.deb ...
Unpacking libdbus-glib-1-2:i386 (0.112-3) ...
Selecting previously unselected package libgconf-2-4:i386.
Preparing to unpack .../235-libgconf-2-4_3.2.6-8_i386.deb ...
Unpacking libgconf-2-4:i386 (3.2.6-8) ...
Selecting previously unselected package gir1.2-gconf-2.0:i386.
Preparing to unpack .../236-gir1.2-gconf-2.0_3.2.6-8_i386.deb ...
Unpacking gir1.2-gconf-2.0:i386 (3.2.6-8) ...
Selecting previously unselected package libbz2-1.0:i386.
Preparing to unpack .../237-libbz2-1.0_1.0.8-5+b1_i386.deb ...
Unpacking libbz2-1.0:i386 (1.0.8-5+b1) ...
Selecting previously unselected package libelf1:i386.
Preparing to unpack .../238-libelf1_0.188-2.1_i386.deb ...
Unpacking libelf1:i386 (0.188-2.1) ...
Selecting previously unselected package libdw1:i386.
Preparing to unpack .../239-libdw1_0.188-2.1_i386.deb ...
Unpacking libdw1:i386 (0.188-2.1) ...
Selecting previously unselected package libunwind8:i386.
Preparing to unpack .../240-libunwind8_1.6.2-3_i386.deb ...
Unpacking libunwind8:i386 (1.6.2-3) ...
Selecting previously unselected package libcap2-bin.
Preparing to unpack .../241-libcap2-bin_1%3a2.66-3_arm64.deb ...
Unpacking libcap2-bin (1:2.66-3) ...
Selecting previously unselected package libgstreamer1.0-0:i386.
Preparing to unpack .../242-libgstreamer1.0-0_1.22.0-2_i386.deb ...
Unpacking libgstreamer1.0-0:i386 (1.22.0-2) ...
Selecting previously unselected package gir1.2-gstreamer-1.0:i386.
Preparing to unpack .../243-gir1.2-gstreamer-1.0_1.22.0-2_i386.deb ...
Unpacking gir1.2-gstreamer-1.0:i386 (1.22.0-2) ...
Selecting previously unselected package libgtk2.0-common.
Preparing to unpack .../244-libgtk2.0-common_2.24.33-2_all.deb ...
Unpacking libgtk2.0-common (2.24.33-2) ...
Selecting previously unselected package libpixman-1-0:arm64.
Preparing to unpack .../245-libpixman-1-0_0.42.2-1_arm64.deb ...
Unpacking libpixman-1-0:arm64 (0.42.2-1) ...
Selecting previously unselected package libxau6:arm64.
Preparing to unpack .../246-libxau6_1%3a1.0.9-1_arm64.deb ...
Unpacking libxau6:arm64 (1:1.0.9-1) ...
Selecting previously unselected package libbsd0:arm64.
Preparing to unpack .../247-libbsd0_0.11.7-4_arm64.deb ...
Unpacking libbsd0:arm64 (0.11.7-4) ...
Selecting previously unselected package libxdmcp6:arm64.
Preparing to unpack .../248-libxdmcp6_1%3a1.1.2-3_arm64.deb ...
Unpacking libxdmcp6:arm64 (1:1.1.2-3) ...
Selecting previously unselected package libxcb1:arm64.
Preparing to unpack .../249-libxcb1_1.15-1_arm64.deb ...
Unpacking libxcb1:arm64 (1.15-1) ...
Selecting previously unselected package libx11-6:arm64.
Preparing to unpack .../250-libx11-6_2%3a1.8.4-2_arm64.deb ...
Unpacking libx11-6:arm64 (2:1.8.4-2) ...
Selecting previously unselected package libxcb-render0:arm64.
Preparing to unpack .../251-libxcb-render0_1.15-1_arm64.deb ...
Unpacking libxcb-render0:arm64 (1.15-1) ...
Selecting previously unselected package libxcb-shm0:arm64.
Preparing to unpack .../252-libxcb-shm0_1.15-1_arm64.deb ...
Unpacking libxcb-shm0:arm64 (1.15-1) ...
Selecting previously unselected package libxext6:arm64.
Preparing to unpack .../253-libxext6_2%3a1.3.4-1+b1_arm64.deb ...
Unpacking libxext6:arm64 (2:1.3.4-1+b1) ...
Selecting previously unselected package libxrender1:arm64.
Preparing to unpack .../254-libxrender1_1%3a0.9.10-1.1_arm64.deb ...
Unpacking libxrender1:arm64 (1:0.9.10-1.1) ...
Selecting previously unselected package libcairo2:arm64.
Preparing to unpack .../255-libcairo2_1.16.0-7_arm64.deb ...
Unpacking libcairo2:arm64 (1.16.0-7) ...
Selecting previously unselected package libcairo-gobject2:arm64.
Preparing to unpack .../256-libcairo-gobject2_1.16.0-7_arm64.deb ...
Unpacking libcairo-gobject2:arm64 (1.16.0-7) ...
Selecting previously unselected package libfribidi0:arm64.
Preparing to unpack .../257-libfribidi0_1.0.8-2.1_arm64.deb ...
Unpacking libfribidi0:arm64 (1.0.8-2.1) ...
Selecting previously unselected package libgraphite2-3:arm64.
Preparing to unpack .../258-libgraphite2-3_1.3.14-1_arm64.deb ...
Unpacking libgraphite2-3:arm64 (1.3.14-1) ...
Selecting previously unselected package libharfbuzz0b:arm64.
Preparing to unpack .../259-libharfbuzz0b_6.0.0+dfsg-3_arm64.deb ...
Unpacking libharfbuzz0b:arm64 (6.0.0+dfsg-3) ...
Selecting previously unselected package libdatrie1:arm64.
Preparing to unpack .../260-libdatrie1_0.2.13-2+b1_arm64.deb ...
Unpacking libdatrie1:arm64 (0.2.13-2+b1) ...
Selecting previously unselected package libthai0:arm64.
Preparing to unpack .../261-libthai0_0.1.29-1_arm64.deb ...
Unpacking libthai0:arm64 (0.1.29-1) ...
Selecting previously unselected package libpango-1.0-0:arm64.
Preparing to unpack .../262-libpango-1.0-0_1.50.12+ds-1_arm64.deb ...
Unpacking libpango-1.0-0:arm64 (1.50.12+ds-1) ...
Selecting previously unselected package libpangoft2-1.0-0:arm64.
Preparing to unpack .../263-libpangoft2-1.0-0_1.50.12+ds-1_arm64.deb ...
Unpacking libpangoft2-1.0-0:arm64 (1.50.12+ds-1) ...
Selecting previously unselected package libpangocairo-1.0-0:arm64.
Preparing to unpack .../264-libpangocairo-1.0-0_1.50.12+ds-1_arm64.deb ...
Unpacking libpangocairo-1.0-0:arm64 (1.50.12+ds-1) ...
Selecting previously unselected package librsvg2-2:arm64.
Preparing to unpack .../265-librsvg2-2_2.54.5+dfsg-1_arm64.deb ...
Unpacking librsvg2-2:arm64 (2.54.5+dfsg-1) ...
Selecting previously unselected package librsvg2-common:arm64.
Preparing to unpack .../266-librsvg2-common_2.54.5+dfsg-1_arm64.deb ...
Unpacking librsvg2-common:arm64 (2.54.5+dfsg-1) ...
Selecting previously unselected package gnome-icon-theme.
Preparing to unpack .../267-gnome-icon-theme_3.12.0-5_all.deb ...
Unpacking gnome-icon-theme (3.12.0-5) ...
Selecting previously unselected package libgtk2.0-0:i386.
Preparing to unpack .../268-libgtk2.0-0_2.24.33-2_i386.deb ...
Unpacking libgtk2.0-0:i386 (2.24.33-2) ...
Selecting previously unselected package gir1.2-gtk-2.0:i386.
Preparing to unpack .../269-gir1.2-gtk-2.0_2.24.33-2_i386.deb ...
Unpacking gir1.2-gtk-2.0:i386 (2.24.33-2) ...
Selecting previously unselected package libnotify4:i386.
Preparing to unpack .../270-libnotify4_0.8.1-1_i386.deb ...
Unpacking libnotify4:i386 (0.8.1-1) ...
Selecting previously unselected package gir1.2-notify-0.7:i386.
Preparing to unpack .../271-gir1.2-notify-0.7_0.8.1-1_i386.deb ...
Unpacking gir1.2-notify-0.7:i386 (0.8.1-1) ...
Selecting previously unselected package libpkgconf3:arm64.
Preparing to unpack .../272-libpkgconf3_1.8.1-1_arm64.deb ...
Unpacking libpkgconf3:arm64 (1.8.1-1) ...
Selecting previously unselected package pkgconf-bin.
Preparing to unpack .../273-pkgconf-bin_1.8.1-1_arm64.deb ...
Unpacking pkgconf-bin (1.8.1-1) ...
Selecting previously unselected package pkgconf:arm64.
Preparing to unpack .../274-pkgconf_1.8.1-1_arm64.deb ...
Unpacking pkgconf:arm64 (1.8.1-1) ...
Selecting previously unselected package pkg-config:arm64.
Preparing to unpack .../275-pkg-config_1.8.1-1_arm64.deb ...
Unpacking pkg-config:arm64 (1.8.1-1) ...
Selecting previously unselected package libregexp-ipv6-perl.
Preparing to unpack .../276-libregexp-ipv6-perl_0.03-3_all.deb ...
Unpacking libregexp-ipv6-perl (0.03-3) ...
Selecting previously unselected package liburi-perl.
Preparing to unpack .../277-liburi-perl_5.17-1_all.deb ...
Unpacking liburi-perl (5.17-1) ...
Selecting previously unselected package libencode-locale-perl.
Preparing to unpack .../278-libencode-locale-perl_1.05-3_all.deb ...
Unpacking libencode-locale-perl (1.05-3) ...
Selecting previously unselected package libtimedate-perl.
Preparing to unpack .../279-libtimedate-perl_2.3300-2_all.deb ...
Unpacking libtimedate-perl (2.3300-2) ...
Selecting previously unselected package libhttp-date-perl.
Preparing to unpack .../280-libhttp-date-perl_6.05-2_all.deb ...
Unpacking libhttp-date-perl (6.05-2) ...
Selecting previously unselected package libfile-listing-perl.
Preparing to unpack .../281-libfile-listing-perl_6.15-1_all.deb ...
Unpacking libfile-listing-perl (6.15-1) ...
Selecting previously unselected package libhtml-tagset-perl.
Preparing to unpack .../282-libhtml-tagset-perl_3.20-6_all.deb ...
Unpacking libhtml-tagset-perl (3.20-6) ...
Selecting previously unselected package libhtml-parser-perl:arm64.
Preparing to unpack .../283-libhtml-parser-perl_3.81-1_arm64.deb ...
Unpacking libhtml-parser-perl:arm64 (3.81-1) ...
Selecting previously unselected package libhtml-tree-perl.
Preparing to unpack .../284-libhtml-tree-perl_5.07-3_all.deb ...
Unpacking libhtml-tree-perl (5.07-3) ...
Selecting previously unselected package libclone-perl:arm64.
Preparing to unpack .../285-libclone-perl_0.46-1_arm64.deb ...
Unpacking libclone-perl:arm64 (0.46-1) ...
Selecting previously unselected package libio-html-perl.
Preparing to unpack .../286-libio-html-perl_1.004-3_all.deb ...
Unpacking libio-html-perl (1.004-3) ...
Selecting previously unselected package liblwp-mediatypes-perl.
Preparing to unpack .../287-liblwp-mediatypes-perl_6.04-2_all.deb ...
Unpacking liblwp-mediatypes-perl (6.04-2) ...
Selecting previously unselected package libhttp-message-perl.
Preparing to unpack .../288-libhttp-message-perl_6.44-1_all.deb ...
Unpacking libhttp-message-perl (6.44-1) ...
Selecting previously unselected package libhttp-cookies-perl.
Preparing to unpack .../289-libhttp-cookies-perl_6.10-1_all.deb ...
Unpacking libhttp-cookies-perl (6.10-1) ...
Selecting previously unselected package libhttp-negotiate-perl.
Preparing to unpack .../290-libhttp-negotiate-perl_6.01-2_all.deb ...
Unpacking libhttp-negotiate-perl (6.01-2) ...
Selecting previously unselected package perl-openssl-defaults:arm64.
Preparing to unpack .../291-perl-openssl-defaults_7+b1_arm64.deb ...
Unpacking perl-openssl-defaults:arm64 (7+b1) ...
Selecting previously unselected package libnet-ssleay-perl:arm64.
Preparing to unpack .../292-libnet-ssleay-perl_1.92-2+b1_arm64.deb ...
Unpacking libnet-ssleay-perl:arm64 (1.92-2+b1) ...
Selecting previously unselected package libio-socket-ssl-perl.
Preparing to unpack .../293-libio-socket-ssl-perl_2.081-2_all.deb ...
Unpacking libio-socket-ssl-perl (2.081-2) ...
Selecting previously unselected package libnet-http-perl.
Preparing to unpack .../294-libnet-http-perl_6.22-1_all.deb ...
Unpacking libnet-http-perl (6.22-1) ...
Selecting previously unselected package liblwp-protocol-https-perl.
Preparing to unpack .../295-liblwp-protocol-https-perl_6.10-1_all.deb ...
Unpacking liblwp-protocol-https-perl (6.10-1) ...
Selecting previously unselected package libtry-tiny-perl.
Preparing to unpack .../296-libtry-tiny-perl_0.31-2_all.deb ...
Unpacking libtry-tiny-perl (0.31-2) ...
Selecting previously unselected package libwww-robotrules-perl.
Preparing to unpack .../297-libwww-robotrules-perl_6.02-1_all.deb ...
Unpacking libwww-robotrules-perl (6.02-1) ...
Selecting previously unselected package libwww-perl.
Preparing to unpack .../298-libwww-perl_6.68-1_all.deb ...
Unpacking libwww-perl (6.68-1) ...
Selecting previously unselected package libxml-parser-perl.
Preparing to unpack .../299-libxml-parser-perl_2.46-4_arm64.deb ...
Unpacking libxml-parser-perl (2.46-4) ...
Selecting previously unselected package intltool.
Preparing to unpack .../300-intltool_0.51.0-6_all.deb ...
Unpacking intltool (0.51.0-6) ...
Selecting previously unselected package gnome-common.
Preparing to unpack .../301-gnome-common_3.18.0-4_all.deb ...
Unpacking gnome-common (3.18.0-4) ...
Selecting previously unselected package icu-devtools.
Preparing to unpack .../302-icu-devtools_72.1-3_arm64.deb ...
Unpacking icu-devtools (72.1-3) ...
Selecting previously unselected package libasan8:i386.
Preparing to unpack .../303-libasan8_12.2.0-14_i386.deb ...
Unpacking libasan8:i386 (12.2.0-14) ...
Selecting previously unselected package pkgconf:i386.
Preparing to unpack .../304-pkgconf_1.8.1-1_i386.deb ...
Unpacking pkgconf:i386 (1.8.1-1) ...
Selecting previously unselected package pkg-config:i386.
Preparing to unpack .../305-pkg-config_1.8.1-1_i386.deb ...
Unpacking pkg-config:i386 (1.8.1-1) ...
Selecting previously unselected package libffi-dev:i386.
Preparing to unpack .../306-libffi-dev_3.4.4-1_i386.deb ...
Unpacking libffi-dev:i386 (3.4.4-1) ...
Selecting previously unselected package libglib2.0-data.
Preparing to unpack .../307-libglib2.0-data_2.74.6-1_all.deb ...
Unpacking libglib2.0-data (2.74.6-1) ...
Selecting previously unselected package libglib2.0-bin.
Preparing to unpack .../308-libglib2.0-bin_2.74.6-1_arm64.deb ...
Unpacking libglib2.0-bin (2.74.6-1) ...
Selecting previously unselected package python3-lib2to3.
Preparing to unpack .../309-python3-lib2to3_3.11.2-2_all.deb ...
Unpacking python3-lib2to3 (3.11.2-2) ...
Selecting previously unselected package python3-distutils.
Preparing to unpack .../310-python3-distutils_3.11.2-2_all.deb ...
Unpacking python3-distutils (3.11.2-2) ...
Selecting previously unselected package libglib2.0-dev-bin.
Preparing to unpack .../311-libglib2.0-dev-bin_2.74.6-1_arm64.deb ...
Unpacking libglib2.0-dev-bin (2.74.6-1) ...
Selecting previously unselected package linux-libc-dev:i386.
Preparing to unpack .../312-linux-libc-dev_6.1.15-1_i386.deb ...
Unpacking linux-libc-dev:i386 (6.1.15-1) ...
Selecting previously unselected package libcrypt1:i386.
Preparing to unpack .../313-libcrypt1_1%3a4.4.33-2_i386.deb ...
Unpacking libcrypt1:i386 (1:4.4.33-2) ...
Selecting previously unselected package libcrypt-dev:i386.
Preparing to unpack .../314-libcrypt-dev_1%3a4.4.33-2_i386.deb ...
Unpacking libcrypt-dev:i386 (1:4.4.33-2) ...
Selecting previously unselected package libtirpc3:i386.
Preparing to unpack .../315-libtirpc3_1.3.3+ds-1_i386.deb ...
Unpacking libtirpc3:i386 (1.3.3+ds-1) ...
Selecting previously unselected package libnsl2:i386.
Preparing to unpack .../316-libnsl2_1.3.0-2_i386.deb ...
Unpacking libnsl2:i386 (1.3.0-2) ...
Selecting previously unselected package libtirpc-dev:i386.
Preparing to unpack .../317-libtirpc-dev_1.3.3+ds-1_i386.deb ...
Unpacking libtirpc-dev:i386 (1.3.3+ds-1) ...
Selecting previously unselected package libnsl-dev:i386.
Preparing to unpack .../318-libnsl-dev_1.3.0-2_i386.deb ...
Unpacking libnsl-dev:i386 (1.3.0-2) ...
Selecting previously unselected package libc6-dev:i386.
Preparing to unpack .../319-libc6-dev_2.36-8_i386.deb ...
Unpacking libc6-dev:i386 (2.36-8) ...
Selecting previously unselected package libuuid1:i386.
Preparing to unpack .../320-libuuid1_2.38.1-5_i386.deb ...
Unpacking libuuid1:i386 (2.38.1-5) ...
Selecting previously unselected package uuid-dev:i386.
Preparing to unpack .../321-uuid-dev_2.38.1-5_i386.deb ...
Unpacking uuid-dev:i386 (2.38.1-5) ...
Selecting previously unselected package libblkid-dev:i386.
Preparing to unpack .../322-libblkid-dev_2.38.1-5_i386.deb ...
Unpacking libblkid-dev:i386 (2.38.1-5) ...
Selecting previously unselected package libsepol2:i386.
Preparing to unpack .../323-libsepol2_3.4-2_i386.deb ...
Unpacking libsepol2:i386 (3.4-2) ...
Selecting previously unselected package libsepol-dev:i386.
Preparing to unpack .../324-libsepol-dev_3.4-2_i386.deb ...
Unpacking libsepol-dev:i386 (3.4-2) ...
Selecting previously unselected package libpcre2-16-0:i386.
Preparing to unpack .../325-libpcre2-16-0_10.42-1_i386.deb ...
Unpacking libpcre2-16-0:i386 (10.42-1) ...
Selecting previously unselected package libpcre2-32-0:i386.
Preparing to unpack .../326-libpcre2-32-0_10.42-1_i386.deb ...
Unpacking libpcre2-32-0:i386 (10.42-1) ...
Selecting previously unselected package libpcre2-posix3:i386.
Preparing to unpack .../327-libpcre2-posix3_10.42-1_i386.deb ...
Unpacking libpcre2-posix3:i386 (10.42-1) ...
Selecting previously unselected package libpcre2-dev:i386.
Preparing to unpack .../328-libpcre2-dev_10.42-1_i386.deb ...
Unpacking libpcre2-dev:i386 (10.42-1) ...
Selecting previously unselected package libselinux1-dev:i386.
Preparing to unpack .../329-libselinux1-dev_3.4-1+b5_i386.deb ...
Unpacking libselinux1-dev:i386 (3.4-1+b5) ...
Selecting previously unselected package libmount-dev:i386.
Preparing to unpack .../330-libmount-dev_2.38.1-5_i386.deb ...
Unpacking libmount-dev:i386 (2.38.1-5) ...
Selecting previously unselected package zlib1g-dev:i386.
Preparing to unpack .../331-zlib1g-dev_1%3a1.2.13.dfsg-1_i386.deb ...
Unpacking zlib1g-dev:i386 (1:1.2.13.dfsg-1) ...
Selecting previously unselected package libglib2.0-dev:i386.
Preparing to unpack .../332-libglib2.0-dev_2.74.6-1_i386.deb ...
Unpacking libglib2.0-dev:i386 (2.74.6-1) ...
Selecting previously unselected package libatk1.0-dev:i386.
Preparing to unpack .../333-libatk1.0-dev_2.46.0-5_i386.deb ...
Unpacking libatk1.0-dev:i386 (2.46.0-5) ...
Selecting previously unselected package xml-core.
Preparing to unpack .../334-xml-core_0.18+nmu1_all.deb ...
Unpacking xml-core (0.18+nmu1) ...
Selecting previously unselected package libdbus-1-dev:i386.
Preparing to unpack .../335-libdbus-1-dev_1.14.6-1_i386.deb ...
Unpacking libdbus-1-dev:i386 (1.14.6-1) ...
Selecting previously unselected package x11-common.
Preparing to unpack .../336-x11-common_1%3a7.7+23_all.deb ...
Unpacking x11-common (1:7.7+23) ...
Selecting previously unselected package libxtst6:i386.
Preparing to unpack .../337-libxtst6_2%3a1.2.3-1.1_i386.deb ...
Unpacking libxtst6:i386 (2:1.2.3-1.1) ...
Selecting previously unselected package xorg-sgml-doctools.
Preparing to unpack .../338-xorg-sgml-doctools_1%3a1.11-1.1_all.deb ...
Unpacking xorg-sgml-doctools (1:1.11-1.1) ...
Selecting previously unselected package x11proto-dev.
Preparing to unpack .../339-x11proto-dev_2022.1-1_all.deb ...
Unpacking x11proto-dev (2022.1-1) ...
Selecting previously unselected package libxau-dev:i386.
Preparing to unpack .../340-libxau-dev_1%3a1.0.9-1_i386.deb ...
Unpacking libxau-dev:i386 (1:1.0.9-1) ...
Selecting previously unselected package libxdmcp-dev:i386.
Preparing to unpack .../341-libxdmcp-dev_1%3a1.1.2-3_i386.deb ...
Unpacking libxdmcp-dev:i386 (1:1.1.2-3) ...
Selecting previously unselected package xtrans-dev.
Preparing to unpack .../342-xtrans-dev_1.4.0-1_all.deb ...
Unpacking xtrans-dev (1.4.0-1) ...
Selecting previously unselected package libpthread-stubs0-dev:i386.
Preparing to unpack .../343-libpthread-stubs0-dev_0.4-1_i386.deb ...
Unpacking libpthread-stubs0-dev:i386 (0.4-1) ...
Selecting previously unselected package libxcb1-dev:i386.
Preparing to unpack .../344-libxcb1-dev_1.15-1_i386.deb ...
Unpacking libxcb1-dev:i386 (1.15-1) ...
Selecting previously unselected package libx11-dev:i386.
Preparing to unpack .../345-libx11-dev_2%3a1.8.4-2_i386.deb ...
Unpacking libx11-dev:i386 (2:1.8.4-2) ...
Selecting previously unselected package libxext-dev:i386.
Preparing to unpack .../346-libxext-dev_2%3a1.3.4-1+b1_i386.deb ...
Unpacking libxext-dev:i386 (2:1.3.4-1+b1) ...
Selecting previously unselected package libxfixes-dev:i386.
Preparing to unpack .../347-libxfixes-dev_1%3a6.0.0-2_i386.deb ...
Unpacking libxfixes-dev:i386 (1:6.0.0-2) ...
Selecting previously unselected package libxi-dev:i386.
Preparing to unpack .../348-libxi-dev_2%3a1.8-1+b1_i386.deb ...
Unpacking libxi-dev:i386 (2:1.8-1+b1) ...
Selecting previously unselected package libxtst-dev:i386.
Preparing to unpack .../349-libxtst-dev_2%3a1.2.3-1.1_i386.deb ...
Unpacking libxtst-dev:i386 (2:1.2.3-1.1) ...
Selecting previously unselected package libatspi2.0-dev:i386.
Preparing to unpack .../350-libatspi2.0-dev_2.46.0-5_i386.deb ...
Unpacking libatspi2.0-dev:i386 (2.46.0-5) ...
Selecting previously unselected package libatk-bridge2.0-dev:i386.
Preparing to unpack .../351-libatk-bridge2.0-dev_2.46.0-5_i386.deb ...
Unpacking libatk-bridge2.0-dev:i386 (2.46.0-5) ...
Selecting previously unselected package libatomic1:i386.
Preparing to unpack .../352-libatomic1_12.2.0-14_i386.deb ...
Unpacking libatomic1:i386 (12.2.0-14) ...
Selecting previously unselected package liblzo2-2:i386.
Preparing to unpack .../353-liblzo2-2_2.10-2_i386.deb ...
Unpacking liblzo2-2:i386 (2.10-2) ...
Selecting previously unselected package libcairo-script-interpreter2:i386.
Preparing to unpack .../354-libcairo-script-interpreter2_1.16.0-7_i386.deb ...
Unpacking libcairo-script-interpreter2:i386 (1.16.0-7) ...
Selecting previously unselected package libexpat1-dev:i386.
Preparing to unpack .../355-libexpat1-dev_2.5.0-1_i386.deb ...
Unpacking libexpat1-dev:i386 (2.5.0-1) ...
Selecting previously unselected package libbrotli-dev:i386.
Preparing to unpack .../356-libbrotli-dev_1.0.9-2+b6_i386.deb ...
Unpacking libbrotli-dev:i386 (1.0.9-2+b6) ...
Selecting previously unselected package libpng-dev:i386.
Preparing to unpack .../357-libpng-dev_1.6.39-2_i386.deb ...
Unpacking libpng-dev:i386 (1.6.39-2) ...
Selecting previously unselected package libfreetype-dev:i386.
Preparing to unpack .../358-libfreetype-dev_2.12.1+dfsg-4_i386.deb ...
Unpacking libfreetype-dev:i386 (2.12.1+dfsg-4) ...
Selecting previously unselected package libfontconfig-dev:i386.
Preparing to unpack .../359-libfontconfig-dev_2.14.1-4_i386.deb ...
Unpacking libfontconfig-dev:i386 (2.14.1-4) ...
Selecting previously unselected package libpixman-1-dev:i386.
Preparing to unpack .../360-libpixman-1-dev_0.42.2-1_i386.deb ...
Unpacking libpixman-1-dev:i386 (0.42.2-1) ...
Selecting previously unselected package libice6:i386.
Preparing to unpack .../361-libice6_2%3a1.0.10-1_i386.deb ...
Unpacking libice6:i386 (2:1.0.10-1) ...
Selecting previously unselected package libsm6:i386.
Preparing to unpack .../362-libsm6_2%3a1.2.3-1_i386.deb ...
Unpacking libsm6:i386 (2:1.2.3-1) ...
Selecting previously unselected package libice-dev:i386.
Preparing to unpack .../363-libice-dev_2%3a1.0.10-1_i386.deb ...
Unpacking libice-dev:i386 (2:1.0.10-1) ...
Selecting previously unselected package libsm-dev:i386.
Preparing to unpack .../364-libsm-dev_2%3a1.2.3-1_i386.deb ...
Unpacking libsm-dev:i386 (2:1.2.3-1) ...
Selecting previously unselected package libxcb-render0-dev:i386.
Preparing to unpack .../365-libxcb-render0-dev_1.15-1_i386.deb ...
Unpacking libxcb-render0-dev:i386 (1.15-1) ...
Selecting previously unselected package libxcb-shm0-dev:i386.
Preparing to unpack .../366-libxcb-shm0-dev_1.15-1_i386.deb ...
Unpacking libxcb-shm0-dev:i386 (1.15-1) ...
Selecting previously unselected package libxrender-dev:i386.
Preparing to unpack .../367-libxrender-dev_1%3a0.9.10-1.1_i386.deb ...
Unpacking libxrender-dev:i386 (1:0.9.10-1.1) ...
Selecting previously unselected package libcairo2-dev:i386.
Preparing to unpack .../368-libcairo2-dev_1.16.0-7_i386.deb ...
Unpacking libcairo2-dev:i386 (1.16.0-7) ...
Selecting previously unselected package libglvnd0:i386.
Preparing to unpack .../369-libglvnd0_1.6.0-1_i386.deb ...
Unpacking libglvnd0:i386 (1.6.0-1) ...
Selecting previously unselected package libdrm-common.
Preparing to unpack .../370-libdrm-common_2.4.114-1_all.deb ...
Unpacking libdrm-common (2.4.114-1) ...
Selecting previously unselected package libdrm2:i386.
Preparing to unpack .../371-libdrm2_2.4.114-1_i386.deb ...
Unpacking libdrm2:i386 (2.4.114-1) ...
Selecting previously unselected package libwayland-server0:i386.
Preparing to unpack .../372-libwayland-server0_1.21.0-1_i386.deb ...
Unpacking libwayland-server0:i386 (1.21.0-1) ...
Selecting previously unselected package libgbm1:i386.
Preparing to unpack .../373-libgbm1_22.3.6-1_i386.deb ...
Unpacking libgbm1:i386 (22.3.6-1) ...
Selecting previously unselected package libglapi-mesa:i386.
Preparing to unpack .../374-libglapi-mesa_22.3.6-1_i386.deb ...
Unpacking libglapi-mesa:i386 (22.3.6-1) ...
Selecting previously unselected package libx11-xcb1:i386.
Preparing to unpack .../375-libx11-xcb1_2%3a1.8.4-2_i386.deb ...
Unpacking libx11-xcb1:i386 (2:1.8.4-2) ...
Selecting previously unselected package libxcb-dri2-0:i386.
Preparing to unpack .../376-libxcb-dri2-0_1.15-1_i386.deb ...
Unpacking libxcb-dri2-0:i386 (1.15-1) ...
Selecting previously unselected package libxcb-dri3-0:i386.
Preparing to unpack .../377-libxcb-dri3-0_1.15-1_i386.deb ...
Unpacking libxcb-dri3-0:i386 (1.15-1) ...
Selecting previously unselected package libxcb-present0:i386.
Preparing to unpack .../378-libxcb-present0_1.15-1_i386.deb ...
Unpacking libxcb-present0:i386 (1.15-1) ...
Selecting previously unselected package libxcb-randr0:i386.
Preparing to unpack .../379-libxcb-randr0_1.15-1_i386.deb ...
Unpacking libxcb-randr0:i386 (1.15-1) ...
Selecting previously unselected package libxcb-sync1:i386.
Preparing to unpack .../380-libxcb-sync1_1.15-1_i386.deb ...
Unpacking libxcb-sync1:i386 (1.15-1) ...
Selecting previously unselected package libxcb-xfixes0:i386.
Preparing to unpack .../381-libxcb-xfixes0_1.15-1_i386.deb ...
Unpacking libxcb-xfixes0:i386 (1.15-1) ...
Selecting previously unselected package libxshmfence1:i386.
Preparing to unpack .../382-libxshmfence1_1.3-1_i386.deb ...
Unpacking libxshmfence1:i386 (1.3-1) ...
Selecting previously unselected package libegl-mesa0:i386.
Preparing to unpack .../383-libegl-mesa0_22.3.6-1_i386.deb ...
Unpacking libegl-mesa0:i386 (22.3.6-1) ...
Selecting previously unselected package libegl1:i386.
Preparing to unpack .../384-libegl1_1.6.0-1_i386.deb ...
Unpacking libegl1:i386 (1.6.0-1) ...
Selecting previously unselected package libxcb-glx0:i386.
Preparing to unpack .../385-libxcb-glx0_1.15-1_i386.deb ...
Unpacking libxcb-glx0:i386 (1.15-1) ...
Selecting previously unselected package libxxf86vm1:i386.
Preparing to unpack .../386-libxxf86vm1_1%3a1.1.4-1+b2_i386.deb ...
Unpacking libxxf86vm1:i386 (1:1.1.4-1+b2) ...
Selecting previously unselected package libdrm-amdgpu1:i386.
Preparing to unpack .../387-libdrm-amdgpu1_2.4.114-1_i386.deb ...
Unpacking libdrm-amdgpu1:i386 (2.4.114-1) ...
Selecting previously unselected package libpciaccess0:i386.
Preparing to unpack .../388-libpciaccess0_0.17-2_i386.deb ...
Unpacking libpciaccess0:i386 (0.17-2) ...
Selecting previously unselected package libdrm-intel1:i386.
Preparing to unpack .../389-libdrm-intel1_2.4.114-1_i386.deb ...
Unpacking libdrm-intel1:i386 (2.4.114-1) ...
Selecting previously unselected package libdrm-nouveau2:i386.
Preparing to unpack .../390-libdrm-nouveau2_2.4.114-1_i386.deb ...
Unpacking libdrm-nouveau2:i386 (2.4.114-1) ...
Selecting previously unselected package libdrm-radeon1:i386.
Preparing to unpack .../391-libdrm-radeon1_2.4.114-1_i386.deb ...
Unpacking libdrm-radeon1:i386 (2.4.114-1) ...
Selecting previously unselected package libtinfo6:i386.
Preparing to unpack .../392-libtinfo6_6.4-2_i386.deb ...
Unpacking libtinfo6:i386 (6.4-2) ...
Selecting previously unselected package libedit2:i386.
Preparing to unpack .../393-libedit2_3.1-20221030-2_i386.deb ...
Unpacking libedit2:i386 (3.1-20221030-2) ...
Selecting previously unselected package libicu72:i386.
Preparing to unpack .../394-libicu72_72.1-3_i386.deb ...
Unpacking libicu72:i386 (72.1-3) ...
Selecting previously unselected package libxml2:i386.
Preparing to unpack .../395-libxml2_2.9.14+dfsg-1.1+b3_i386.deb ...
Unpacking libxml2:i386 (2.9.14+dfsg-1.1+b3) ...
Selecting previously unselected package libz3-4:i386.
Preparing to unpack .../396-libz3-4_4.8.12-3.1_i386.deb ...
Unpacking libz3-4:i386 (4.8.12-3.1) ...
Selecting previously unselected package libllvm15:i386.
Preparing to unpack .../397-libllvm15_1%3a15.0.7-1_i386.deb ...
Unpacking libllvm15:i386 (1:15.0.7-1) ...
Selecting previously unselected package libsensors-config.
Preparing to unpack .../398-libsensors-config_1%3a3.6.0-7.1_all.deb ...
Unpacking libsensors-config (1:3.6.0-7.1) ...
Selecting previously unselected package libsensors5:i386.
Preparing to unpack .../399-libsensors5_1%3a3.6.0-7.1_i386.deb ...
Unpacking libsensors5:i386 (1:3.6.0-7.1) ...
Selecting previously unselected package libgl1-mesa-dri:i386.
Preparing to unpack .../400-libgl1-mesa-dri_22.3.6-1_i386.deb ...
Unpacking libgl1-mesa-dri:i386 (22.3.6-1) ...
Selecting previously unselected package libglx-mesa0:i386.
Preparing to unpack .../401-libglx-mesa0_22.3.6-1_i386.deb ...
Unpacking libglx-mesa0:i386 (22.3.6-1) ...
Selecting previously unselected package libglx0:i386.
Preparing to unpack .../402-libglx0_1.6.0-1_i386.deb ...
Unpacking libglx0:i386 (1.6.0-1) ...
Selecting previously unselected package libgl1:i386.
Preparing to unpack .../403-libgl1_1.6.0-1_i386.deb ...
Unpacking libgl1:i386 (1.6.0-1) ...
Selecting previously unselected package libglx-dev:i386.
Preparing to unpack .../404-libglx-dev_1.6.0-1_i386.deb ...
Unpacking libglx-dev:i386 (1.6.0-1) ...
Selecting previously unselected package libgl-dev:i386.
Preparing to unpack .../405-libgl-dev_1.6.0-1_i386.deb ...
Unpacking libgl-dev:i386 (1.6.0-1) ...
Selecting previously unselected package libegl-dev:i386.
Preparing to unpack .../406-libegl-dev_1.6.0-1_i386.deb ...
Unpacking libegl-dev:i386 (1.6.0-1) ...
Selecting previously unselected package libglvnd-core-dev:i386.
Preparing to unpack .../407-libglvnd-core-dev_1.6.0-1_i386.deb ...
Unpacking libglvnd-core-dev:i386 (1.6.0-1) ...
Selecting previously unselected package libgles1:i386.
Preparing to unpack .../408-libgles1_1.6.0-1_i386.deb ...
Unpacking libgles1:i386 (1.6.0-1) ...
Selecting previously unselected package libgles2:i386.
Preparing to unpack .../409-libgles2_1.6.0-1_i386.deb ...
Unpacking libgles2:i386 (1.6.0-1) ...
Selecting previously unselected package libgles-dev:i386.
Preparing to unpack .../410-libgles-dev_1.6.0-1_i386.deb ...
Unpacking libgles-dev:i386 (1.6.0-1) ...
Selecting previously unselected package libopengl0:i386.
Preparing to unpack .../411-libopengl0_1.6.0-1_i386.deb ...
Unpacking libopengl0:i386 (1.6.0-1) ...
Selecting previously unselected package libopengl-dev:i386.
Preparing to unpack .../412-libopengl-dev_1.6.0-1_i386.deb ...
Unpacking libopengl-dev:i386 (1.6.0-1) ...
Selecting previously unselected package libglvnd-dev:i386.
Preparing to unpack .../413-libglvnd-dev_1.6.0-1_i386.deb ...
Unpacking libglvnd-dev:i386 (1.6.0-1) ...
Selecting previously unselected package libegl1-mesa-dev:i386.
Preparing to unpack .../414-libegl1-mesa-dev_22.3.6-1_i386.deb ...
Unpacking libegl1-mesa-dev:i386 (22.3.6-1) ...
Selecting previously unselected package libepoxy-dev:i386.
Preparing to unpack .../415-libepoxy-dev_1.5.10-1_i386.deb ...
Unpacking libepoxy-dev:i386 (1.5.10-1) ...
Selecting previously unselected package libfribidi-dev:i386.
Preparing to unpack .../416-libfribidi-dev_1.0.8-2.1_i386.deb ...
Unpacking libfribidi-dev:i386 (1.0.8-2.1) ...
Selecting previously unselected package libgdk-pixbuf2.0-bin.
Preparing to unpack .../417-libgdk-pixbuf2.0-bin_2.42.10+dfsg-1+b1_arm64.deb ...
Unpacking libgdk-pixbuf2.0-bin (2.42.10+dfsg-1+b1) ...
Selecting previously unselected package libjpeg62-turbo-dev:i386.
Preparing to unpack .../418-libjpeg62-turbo-dev_1%3a2.1.5-2_i386.deb ...
Unpacking libjpeg62-turbo-dev:i386 (1:2.1.5-2) ...
Selecting previously unselected package libjpeg-dev:i386.
Preparing to unpack .../419-libjpeg-dev_1%3a2.1.5-2_i386.deb ...
Unpacking libjpeg-dev:i386 (1:2.1.5-2) ...
Selecting previously unselected package libjbig-dev:i386.
Preparing to unpack .../420-libjbig-dev_2.1-6.1_i386.deb ...
Unpacking libjbig-dev:i386 (2.1-6.1) ...
Selecting previously unselected package liblzma-dev:i386.
Preparing to unpack .../421-liblzma-dev_5.4.1-0.2_i386.deb ...
Unpacking liblzma-dev:i386 (5.4.1-0.2) ...
Selecting previously unselected package libzstd-dev:i386.
Preparing to unpack .../422-libzstd-dev_1.5.4+dfsg2-3_i386.deb ...
Unpacking libzstd-dev:i386 (1.5.4+dfsg2-3) ...
Selecting previously unselected package libwebpmux3:i386.
Preparing to unpack .../423-libwebpmux3_1.2.4-0.1_i386.deb ...
Unpacking libwebpmux3:i386 (1.2.4-0.1) ...
Selecting previously unselected package libwebpdemux2:i386.
Preparing to unpack .../424-libwebpdemux2_1.2.4-0.1_i386.deb ...
Unpacking libwebpdemux2:i386 (1.2.4-0.1) ...
Selecting previously unselected package libwebp-dev:i386.
Preparing to unpack .../425-libwebp-dev_1.2.4-0.1_i386.deb ...
Unpacking libwebp-dev:i386 (1.2.4-0.1) ...
Selecting previously unselected package libtiffxx6:i386.
Preparing to unpack .../426-libtiffxx6_4.5.0-5_i386.deb ...
Unpacking libtiffxx6:i386 (4.5.0-5) ...
Selecting previously unselected package libdeflate-dev:i386.
Preparing to unpack .../427-libdeflate-dev_1.14-1_i386.deb ...
Unpacking libdeflate-dev:i386 (1.14-1) ...
Selecting previously unselected package liblerc-dev:i386.
Preparing to unpack .../428-liblerc-dev_4.0.0+ds-2_i386.deb ...
Unpacking liblerc-dev:i386 (4.0.0+ds-2) ...
Selecting previously unselected package libtiff-dev:i386.
Preparing to unpack .../429-libtiff-dev_4.5.0-5_i386.deb ...
Unpacking libtiff-dev:i386 (4.5.0-5) ...
Selecting previously unselected package libgdk-pixbuf-2.0-dev:i386.
Preparing to unpack .../430-libgdk-pixbuf-2.0-dev_2.42.10+dfsg-1+b1_i386.deb ...
Unpacking libgdk-pixbuf-2.0-dev:i386 (2.42.10+dfsg-1+b1) ...
Selecting previously unselected package libharfbuzz-icu0:i386.
Preparing to unpack .../431-libharfbuzz-icu0_6.0.0+dfsg-3_i386.deb ...
Unpacking libharfbuzz-icu0:i386 (6.0.0+dfsg-3) ...
Selecting previously unselected package libharfbuzz-gobject0:i386.
Preparing to unpack .../432-libharfbuzz-gobject0_6.0.0+dfsg-3_i386.deb ...
Unpacking libharfbuzz-gobject0:i386 (6.0.0+dfsg-3) ...
Selecting previously unselected package libharfbuzz-subset0:i386.
Preparing to unpack .../433-libharfbuzz-subset0_6.0.0+dfsg-3_i386.deb ...
Unpacking libharfbuzz-subset0:i386 (6.0.0+dfsg-3) ...
Selecting previously unselected package libgraphite2-dev:i386.
Preparing to unpack .../434-libgraphite2-dev_1.3.14-1_i386.deb ...
Unpacking libgraphite2-dev:i386 (1.3.14-1) ...
Selecting previously unselected package libicu-dev:i386.
Preparing to unpack .../435-libicu-dev_72.1-3_i386.deb ...
Unpacking libicu-dev:i386 (72.1-3) ...
Selecting previously unselected package libharfbuzz-dev:i386.
Preparing to unpack .../436-libharfbuzz-dev_6.0.0+dfsg-3_i386.deb ...
Unpacking libharfbuzz-dev:i386 (6.0.0+dfsg-3) ...
Selecting previously unselected package libdatrie-dev:i386.
Preparing to unpack .../437-libdatrie-dev_0.2.13-2+b1_i386.deb ...
Unpacking libdatrie-dev:i386 (0.2.13-2+b1) ...
Selecting previously unselected package libthai-dev:i386.
Preparing to unpack .../438-libthai-dev_0.1.29-1_i386.deb ...
Unpacking libthai-dev:i386 (0.1.29-1) ...
Selecting previously unselected package libxft-dev:i386.
Preparing to unpack .../439-libxft-dev_2.3.6-1_i386.deb ...
Unpacking libxft-dev:i386 (2.3.6-1) ...
Selecting previously unselected package libxft2:arm64.
Preparing to unpack .../440-libxft2_2.3.6-1_arm64.deb ...
Unpacking libxft2:arm64 (2.3.6-1) ...
Selecting previously unselected package libpangoxft-1.0-0:arm64.
Preparing to unpack .../441-libpangoxft-1.0-0_1.50.12+ds-1_arm64.deb ...
Unpacking libpangoxft-1.0-0:arm64 (1.50.12+ds-1) ...
Selecting previously unselected package pango1.0-tools.
Preparing to unpack .../442-pango1.0-tools_1.50.12+ds-1_arm64.deb ...
Unpacking pango1.0-tools (1.50.12+ds-1) ...
Selecting previously unselected package libpango1.0-dev:i386.
Preparing to unpack .../443-libpango1.0-dev_1.50.12+ds-1_i386.deb ...
Unpacking libpango1.0-dev:i386 (1.50.12+ds-1) ...
Selecting previously unselected package libwayland-bin.
Preparing to unpack .../444-libwayland-bin_1.21.0-1_arm64.deb ...
Unpacking libwayland-bin (1.21.0-1) ...
Selecting previously unselected package libwayland-dev:i386.
Preparing to unpack .../445-libwayland-dev_1.21.0-1_i386.deb ...
Unpacking libwayland-dev:i386 (1.21.0-1) ...
Selecting previously unselected package libxcomposite-dev:i386.
Preparing to unpack .../446-libxcomposite-dev_1%3a0.4.5-1_i386.deb ...
Unpacking libxcomposite-dev:i386 (1:0.4.5-1) ...
Selecting previously unselected package libxcursor-dev:i386.
Preparing to unpack .../447-libxcursor-dev_1%3a1.2.1-1_i386.deb ...
Unpacking libxcursor-dev:i386 (1:1.2.1-1) ...
Selecting previously unselected package libxdamage-dev:i386.
Preparing to unpack .../448-libxdamage-dev_1%3a1.1.6-1_i386.deb ...
Unpacking libxdamage-dev:i386 (1:1.1.6-1) ...
Selecting previously unselected package libxinerama-dev:i386.
Preparing to unpack .../449-libxinerama-dev_2%3a1.1.4-3_i386.deb ...
Unpacking libxinerama-dev:i386 (2:1.1.4-3) ...
Selecting previously unselected package libxkbcommon-dev:i386.
Preparing to unpack .../450-libxkbcommon-dev_1.5.0-1_i386.deb ...
Unpacking libxkbcommon-dev:i386 (1.5.0-1) ...
Selecting previously unselected package libxrandr-dev:i386.
Preparing to unpack .../451-libxrandr-dev_2%3a1.5.2-2+b1_i386.deb ...
Unpacking libxrandr-dev:i386 (2:1.5.2-2+b1) ...
Selecting previously unselected package wayland-protocols.
Preparing to unpack .../452-wayland-protocols_1.31-1_all.deb ...
Unpacking wayland-protocols (1.31-1) ...
Selecting previously unselected package libgtk-3-dev:i386.
Preparing to unpack .../453-libgtk-3-dev_3.24.36-4_i386.deb ...
Unpacking libgtk-3-dev:i386 (3.24.36-4) ...
Selecting previously unselected package libayatana-ido3-dev:i386.
Preparing to unpack .../454-libayatana-ido3-dev_0.9.3-1_i386.deb ...
Unpacking libayatana-ido3-dev:i386 (0.9.3-1) ...
Selecting previously unselected package libayatana-indicator3-dev:i386.
Preparing to unpack .../455-libayatana-indicator3-dev_0.9.3-1_i386.deb ...
Unpacking libayatana-indicator3-dev:i386 (0.9.3-1) ...
Selecting previously unselected package libxml2-utils.
Preparing to unpack .../456-libxml2-utils_2.9.14+dfsg-1.1+b3_arm64.deb ...
Unpacking libxml2-utils (2.9.14+dfsg-1.1+b3) ...
Selecting previously unselected package libgtk2.0-dev:i386.
Preparing to unpack .../457-libgtk2.0-dev_2.24.33-2_i386.deb ...
Unpacking libgtk2.0-dev:i386 (2.24.33-2) ...
Selecting previously unselected package libdbusmenu-glib-dev:i386.
Preparing to unpack .../458-libdbusmenu-glib-dev_18.10.20180917~bzr492+repack1-3_i386.deb ...
Unpacking libdbusmenu-glib-dev:i386 (18.10.20180917~bzr492+repack1-3) ...
Selecting previously unselected package libayatana-appindicator3-dev:i386.
Preparing to unpack .../459-libayatana-appindicator3-dev_0.5.92-1_i386.deb ...
Unpacking libayatana-appindicator3-dev:i386 (0.5.92-1) ...
Selecting previously unselected package libelf-dev:i386.
Preparing to unpack .../460-libelf-dev_0.188-2.1_i386.deb ...
Unpacking libelf-dev:i386 (0.188-2.1) ...
Selecting previously unselected package libdw-dev:i386.
Preparing to unpack .../461-libdw-dev_0.188-2.1_i386.deb ...
Unpacking libdw-dev:i386 (0.188-2.1) ...
Selecting previously unselected package libgomp1:i386.
Preparing to unpack .../462-libgomp1_12.2.0-14_i386.deb ...
Unpacking libgomp1:i386 (12.2.0-14) ...
Selecting previously unselected package libitm1:i386.
Preparing to unpack .../463-libitm1_12.2.0-14_i386.deb ...
Unpacking libitm1:i386 (12.2.0-14) ...
Selecting previously unselected package libubsan1:i386.
Preparing to unpack .../464-libubsan1_12.2.0-14_i386.deb ...
Unpacking libubsan1:i386 (12.2.0-14) ...
Selecting previously unselected package libquadmath0:i386.
Preparing to unpack .../465-libquadmath0_12.2.0-14_i386.deb ...
Unpacking libquadmath0:i386 (12.2.0-14) ...
Selecting previously unselected package libgcc-12-dev:i386.
Preparing to unpack .../466-libgcc-12-dev_12.2.0-14_i386.deb ...
Unpacking libgcc-12-dev:i386 (12.2.0-14) ...
Selecting previously unselected package libgconf2-dev:i386.
Preparing to unpack .../467-libgconf2-dev_3.2.6-8_i386.deb ...
Unpacking libgconf2-dev:i386 (3.2.6-8) ...
Selecting previously unselected package libunwind-dev:i386.
Preparing to unpack .../468-libunwind-dev_1.6.2-3_i386.deb ...
Unpacking libunwind-dev:i386 (1.6.2-3) ...
Selecting previously unselected package libgstreamer1.0-dev:i386.
Preparing to unpack .../469-libgstreamer1.0-dev_1.22.0-2_i386.deb ...
Unpacking libgstreamer1.0-dev:i386 (1.22.0-2) ...
Selecting previously unselected package libnotify-dev:i386.
Preparing to unpack .../470-libnotify-dev_0.8.1-1_i386.deb ...
Unpacking libnotify-dev:i386 (0.8.1-1) ...
Selecting previously unselected package libstdc++-12-dev:i386.
Preparing to unpack .../471-libstdc++-12-dev_12.2.0-14_i386.deb ...
Unpacking libstdc++-12-dev:i386 (12.2.0-14) ...
Selecting previously unselected package libxml2-dev:i386.
Preparing to unpack .../472-libxml2-dev_2.9.14+dfsg-1.1+b3_i386.deb ...
Unpacking libxml2-dev:i386 (2.9.14+dfsg-1.1+b3) ...
Selecting previously unselected package sbuild-build-depends-main-dummy:i386.
Preparing to unpack .../473-sbuild-build-depends-main-dummy_0.invalid.0_i386.deb ...
Unpacking sbuild-build-depends-main-dummy:i386 (0.invalid.0) ...
Setting up libconfig-inifiles-perl (3.000003-2) ...
Setting up media-types (10.0.0) ...
Setting up libpipeline1:arm64 (1.5.7-1) ...
Setting up libgraphite2-3:arm64 (1.3.14-1) ...
Setting up libpixman-1-0:arm64 (0.42.2-1) ...
Setting up libfile-which-perl (1.27-2) ...
Setting up systemd-sysv (252.6-1) ...
Setting up libxau6:arm64 (1:1.0.9-1) ...
Setting up libpsl5:arm64 (0.21.2-1) ...
Setting up libicu72:arm64 (72.1-3) ...
Setting up gcc-12-cross-base (12.2.0-14cross1) ...
Setting up liblerc4:arm64 (4.0.0+ds-2) ...
Setting up bsdextrautils (2.38.1-5) ...
Setting up libglvnd-core-dev:i386 (1.6.0-1) ...
Setting up hicolor-icon-theme (0.17-2) ...
Setting up libdatrie1:arm64 (0.2.13-2+b1) ...
Setting up libmagic-mgc (1:5.44-3) ...
Setting up psmisc (23.6-1) ...
Setting up libclone-perl:arm64 (0.46-1) ...
Setting up libarchive-zip-perl (1.68-1) ...
Setting up libglib2.0-0:arm64 (2.74.6-1) ...
Setting up libhtml-tagset-perl (3.20-6) ...
Setting up binutils-i686-linux-gnu (2.40-2) ...
Setting up libdebhelper-perl (13.11.4) ...
Setting up libbrotli1:arm64 (1.0.9-2+b6) ...
Setting up libsqlite3-0:arm64 (3.40.1-1) ...
Setting up liblwp-mediatypes-perl (6.04-2) ...
Setting up libgdk-pixbuf2.0-common (2.42.10+dfsg-1) ...
Setting up x11-common (1:7.7+23) ...
Running in chroot, ignoring request.
All runlevel operations denied by policy
invoke-rc.d: policy-rc.d denied execution of restart.
Setting up libtry-tiny-perl (0.31-2) ...
Setting up libsensors-config (1:3.6.0-7.1) ...
Setting up libnghttp2-14:arm64 (1.52.0-1) ...
Setting up libmagic1:arm64 (1:5.44-3) ...
Setting up libdeflate0:arm64 (1.14-1) ...
Setting up perl-openssl-defaults:arm64 (7+b1) ...
Setting up linux-libc-dev:i386 (6.1.15-1) ...
Setting up libxml-namespacesupport-perl (1.12-2) ...
Setting up gettext-base (0.21-12) ...
Setting up m4 (1.4.19-3) ...
Setting up xkb-data (2.35.1-1) ...
Setting up libencode-locale-perl (1.05-3) ...
Setting up autoconf-archive (20220903-3) ...
Setting up file (1:5.44-3) ...
Setting up libyaml-perl (1.30-2) ...
Setting up libpthread-stubs0-dev:i386 (0.4-1) ...
Setting up libjbig0:arm64 (2.1-6.1) ...
Setting up gcc-12-base:i386 (12.2.0-14) ...
Setting up libsasl2-modules-db:arm64 (2.1.28+dfsg-11) ...
Setting up libcap2-bin (1:2.66-3) ...
Setting up gcc-12-i686-linux-gnu-base:arm64 (12.2.0-14cross1) ...
Setting up libdconf1:arm64 (0.40.0-4) ...
Setting up libxml-sax-base-perl (1.09-3) ...
Setting up libio-string-perl (1.08-4) ...
Setting up xtrans-dev (1.4.0-1) ...
Setting up linux-libc-dev-i386-cross (6.1.4-1cross1) ...
Setting up autotools-dev (20220109.1) ...
Setting up libglib2.0-data (2.74.6-1) ...
Setting up cross-config (2.6.20) ...
Setting up libpkgconf3:arm64 (1.8.1-1) ...
Setting up libuv1:arm64 (1.44.2-1) ...
Setting up libjpeg62-turbo:arm64 (1:2.1.5-2) ...
Setting up libx11-data (2:1.8.4-2) ...
Setting up librtmp1:arm64 (2.4+20151223.gitfa8646d.1-2+b2) ...
Setting up libavahi-common-data:i386 (0.8-9) ...
Setting up libdbus-1-3:arm64 (1.14.6-1) ...
Setting up libfribidi0:arm64 (1.0.8-2.1) ...
Setting up libproc2-0:arm64 (2:4.0.3-1) ...
Setting up libpng16-16:arm64 (1.6.39-2) ...
Setting up libio-html-perl (1.004-3) ...
Setting up autopoint (0.21-12) ...
Setting up libjsoncpp25:arm64 (1.9.5-4) ...
Setting up icu-devtools (72.1-3) ...
Setting up fonts-dejavu-core (2.37-5) ...
Setting up pkgconf-bin (1.8.1-1) ...
Setting up libncursesw6:arm64 (6.4-2) ...
Setting up libsasl2-2:arm64 (2.1.28+dfsg-11) ...
Setting up autoconf (2.71-3) ...
Setting up libwebp7:arm64 (1.2.4-0.1) ...
Setting up libtimedate-perl (2.3300-2) ...
Setting up libregexp-ipv6-perl (0.03-3) ...
Setting up wayland-protocols (1.31-1) ...
Setting up sensible-utils (0.0.17+nmu1) ...
Setting up at-spi2-common (2.46.0-5) ...
Setting up librhash0:arm64 (1.4.3-3) ...
Setting up libtiff6:arm64 (4.5.0-5) ...
Setting up dbus-session-bus-common (1.14.6-1) ...
Setting up libuchardet0:arm64 (0.0.7-1) ...
Setting up procps (2:4.0.3-1) ...
Setting up libc6-i386-cross (2.36-8cross1) ...
Setting up libsub-override-perl (0.09-4) ...
Setting up libthai-data (0.1.29-1) ...
Setting up libssh2-1:arm64 (1.10.0-3+b1) ...
Setting up xorg-sgml-doctools (1:1.11-1.1) ...
Setting up netbase (6.4) ...
Setting up sgml-base (1.31) ...
Setting up libgtk2.0-common (2.24.33-2) ...
Setting up cmake-data (3.25.1-1) ...
Setting up dbus-system-bus-common (1.14.6-1) ...
Setting up libfile-homedir-perl (1.006-2) ...
Setting up openssl (3.0.8-1) ...
Setting up libbsd0:arm64 (0.11.7-4) ...
Setting up libquadmath0-i386-cross (12.2.0-14cross1) ...
Setting up libdrm-common (2.4.114-1) ...
Setting up libelf1:arm64 (0.188-2.1) ...
Setting up readline-common (8.2-1.3) ...
Setting up libxml2:arm64 (2.9.14+dfsg-1.1+b3) ...
Setting up liburi-perl (5.17-1) ...
Setting up dbus-bin (1.14.6-1) ...
Setting up liblocale-gettext-perl (1.07-5) ...
Setting up libnet-ssleay-perl:arm64 (1.92-2+b1) ...
Setting up automake (1:1.16.5-1.3) ...
update-alternatives: using /usr/bin/automake-1.16 to provide /usr/bin/automake (automake) in auto mode
Setting up x11proto-dev (2022.1-1) ...
Setting up libfile-stripnondeterminism-perl (1.13.1-1) ...
Setting up libhttp-date-perl (6.05-2) ...
Setting up libxdmcp6:arm64 (1:1.1.2-3) ...
Setting up libxcb1:arm64 (1.15-1) ...
Setting up gettext (0.21-12) ...
Setting up cpp-12-i686-linux-gnu (12.2.0-14cross1) ...
Setting up libfile-listing-perl (6.15-1) ...
Setting up libtool (2.4.7-5) ...
Setting up libatomic1-i386-cross (12.2.0-14cross1) ...
Setting up libarchive13:arm64 (3.6.2-1) ...
Setting up libxcb-render0:arm64 (1.15-1) ...
Setting up fontconfig-config (2.14.1-4) ...
Setting up libreadline8:arm64 (8.2-1.3) ...
Setting up libglib2.0-bin (2.74.6-1) ...
Setting up libnet-http-perl (6.22-1) ...
Setting up libgomp1-i386-cross (12.2.0-14cross1) ...
Setting up libxcb-shm0:arm64 (1.15-1) ...
Setting up dbus-daemon (1.14.6-1) ...
Setting up libc6-dev-i386-cross (2.36-8cross1) ...
Setting up libldap-2.5-0:arm64 (2.5.13+dfsg-5) ...
Setting up pkgconf:arm64 (1.8.1-1) ...
Setting up pkgconf:i386 (1.8.1-1) ...
Setting up intltool-debian (0.35.0+20060710.6) ...
Setting up libgcc-s1-i386-cross (12.2.0-14cross1) ...
Setting up dh-autoreconf (20) ...
Setting up libthai0:arm64 (0.1.29-1) ...
Setting up ca-certificates (20211016) ...
Updating certificates in /etc/ssl/certs...
127 added, 0 removed; done.
Setting up libwayland-bin (1.21.0-1) ...
Setting up libfreetype6:arm64 (2.12.1+dfsg-4) ...
Setting up libdbus-glib-1-2:arm64 (0.112-3) ...
Setting up dbus (1.14.6-1) ...
Running in chroot, ignoring request.
All runlevel operations denied by policy
invoke-rc.d: policy-rc.d denied execution of start.
Setting up shared-mime-info (2.2-1) ...
Setting up libitm1-i386-cross (12.2.0-14cross1) ...
Setting up pkg-config:arm64 (1.8.1-1) ...
Setting up pkg-config:i386 (1.8.1-1) ...
Setting up ucf (3.0043+nmu1) ...
Setting up dh-strip-nondeterminism (1.13.1-1) ...
Setting up libwww-robotrules-perl (6.02-1) ...
Setting up dwz (0.15-1) ...
Setting up groff-base (1.22.4-10) ...
Setting up xml-core (0.18+nmu1) ...
Setting up libhtml-parser-perl:arm64 (3.81-1) ...
Setting up libpam-systemd:arm64 (252.6-1) ...
Setting up libcurl4:arm64 (7.88.1-5) ...
Setting up libx11-6:arm64 (2:1.8.4-2) ...
Setting up libharfbuzz0b:arm64 (6.0.0+dfsg-3) ...
Setting up libgdk-pixbuf-2.0-0:arm64 (2.42.10+dfsg-1+b1) ...
Setting up cpp-i686-linux-gnu (4:12.2.0-3) ...
Setting up libfontconfig1:arm64 (2.14.1-4) ...
Setting up libxml2-utils (2.9.14+dfsg-1.1+b3) ...
Setting up libio-socket-ssl-perl (2.081-2) ...
Setting up libhttp-message-perl (6.44-1) ...
Setting up gtk-update-icon-cache (3.24.36-4) ...
Setting up libhttp-negotiate-perl (6.01-2) ...
Setting up fontconfig (2.14.1-4) ...
Regenerating fonts cache... done.
Setting up libxrender1:arm64 (1:0.9.10-1.1) ...
Setting up libhttp-cookies-perl (6.10-1) ...
Setting up po-debconf (1.0.21+nmu1) ...
Setting up libhtml-tree-perl (5.07-3) ...
Setting up libpython3.11-stdlib:arm64 (3.11.2-4) ...
Setting up libpango-1.0-0:arm64 (1.50.12+ds-1) ...
Setting up libxext6:arm64 (2:1.3.4-1+b1) ...
Setting up man-db (2.11.2-1) ...
Not building database; man-db/auto-update is not 'true'.
Created symlink /etc/systemd/system/timers.target.wants/man-db.timer → /lib/systemd/system/man-db.timer.
Setting up libxml-sax-perl (1.02+dfsg-3) ...
update-perl-sax-parsers: Registering Perl SAX parser XML::SAX::PurePerl with priority 10...
update-perl-sax-parsers: Updating overall Perl SAX parser modules info file...

Creating config file /etc/perl/XML/SAX/ParserDetails.ini with new version
Setting up libcairo2:arm64 (1.16.0-7) ...
Setting up libasan8-i386-cross (12.2.0-14cross1) ...
Setting up libstdc++6-i386-cross (12.2.0-14cross1) ...
Setting up dbus-user-session (1.14.6-1) ...
Setting up gconf2-common (3.2.6-8) ...

Creating config file /etc/gconf/2/path with new version
Setting up adwaita-icon-theme (43-1) ...
update-alternatives: using /usr/share/icons/Adwaita/cursor.theme to provide /usr/share/icons/default/index.theme (x-cursor-theme) in auto mode
Setting up libxml-libxml-perl (2.0207+dfsg+really+2.0134-1+b1) ...
update-perl-sax-parsers: Registering Perl SAX parser XML::LibXML::SAX::Parser with priority 50...
update-perl-sax-parsers: Registering Perl SAX parser XML::LibXML::SAX with priority 50...
update-perl-sax-parsers: Updating overall Perl SAX parser modules info file...
Replacing config file /etc/perl/XML/SAX/ParserDetails.ini with new version
Setting up libgdk-pixbuf2.0-bin (2.42.10+dfsg-1+b1) ...
Setting up cmake (3.25.1-1) ...
Setting up libcairo-gobject2:arm64 (1.16.0-7) ...
Setting up libpangoft2-1.0-0:arm64 (1.50.12+ds-1) ...
Setting up libpangocairo-1.0-0:arm64 (1.50.12+ds-1) ...
Setting up libpython3-stdlib:arm64 (3.11.2-1) ...
Setting up python3.11 (3.11.2-4) ...
Setting up libxft2:arm64 (2.3.6-1) ...
Setting up libpangoxft-1.0-0:arm64 (1.50.12+ds-1) ...
Setting up libgconf-2-4:arm64 (3.2.6-8) ...
Setting up pango1.0-tools (1.50.12+ds-1) ...
Setting up debhelper (13.11.4) ...
Setting up dconf-service (0.40.0-4) ...
Setting up python3 (3.11.2-1) ...
Setting up libubsan1-i386-cross (12.2.0-14cross1) ...
Setting up librsvg2-2:arm64 (2.54.5+dfsg-1) ...
Setting up libxml-simple-perl (2.25-2) ...
Setting up librsvg2-common:arm64 (2.54.5+dfsg-1) ...
Setting up gconf-service (3.2.6-8) ...
Setting up python3-lib2to3 (3.11.2-2) ...
Setting up python3-distutils (3.11.2-2) ...
Setting up libglib2.0-dev-bin (2.74.6-1) ...
Setting up dconf-gsettings-backend:arm64 (0.40.0-4) ...
Setting up libgcc-12-dev-i386-cross (12.2.0-14cross1) ...
Setting up libconfig-auto-perl (0.44-2) ...
Setting up gconf2 (3.2.6-8) ...
Setting up gnome-icon-theme (3.12.0-5) ...
update-alternatives: using /usr/share/icons/gnome/scalable/places/debian-swirl.svg to provide /usr/share/icons/gnome/scalable/places/start-here.svg (start-here.svg) in auto mode
Setting up libstdc++-12-dev-i386-cross (12.2.0-14cross1) ...
Setting up libgtk-3-common (3.24.36-4) ...
Setting up libdebian-dpkgcross-perl (2.6.20) ...
Setting up gcc-12-i686-linux-gnu (12.2.0-14cross1) ...
Setting up g++-12-i686-linux-gnu (12.2.0-14cross1) ...
Setting up gcc-i686-linux-gnu (4:12.2.0-3) ...
Setting up dpkg-cross (2.6.20) ...
Setting up g++-i686-linux-gnu (4:12.2.0-3) ...
Setting up crossbuild-essential-i386 (12.9) ...
Setting up libgcc-s1:i386 (12.2.0-14) ...
Setting up libc6:i386 (2.36-8) ...
Setting up libwebp7:i386 (1.2.4-0.1) ...
Setting up libudev1:i386 (252.6-1) ...
Setting up libffi8:i386 (3.4.4-1) ...
Setting up libdrm2:i386 (2.4.114-1) ...
Setting up libmd0:i386 (1.0.4-2) ...
Setting up libxshmfence1:i386 (1.3-1) ...
Setting up libasan8:i386 (12.2.0-14) ...
Setting up libtasn1-6:i386 (4.19.0-2) ...
Setting up libwayland-egl1:i386 (1.21.0-1) ...
Setting up libbz2-1.0:i386 (1.0.8-5+b1) ...
Setting up libwebpmux3:i386 (1.2.4-0.1) ...
Setting up libbsd0:i386 (0.11.7-4) ...
Setting up libblkid1:i386 (2.38.1-5) ...
Setting up libstdc++6:i386 (12.2.0-14) ...
Setting up libitm1:i386 (12.2.0-14) ...
Setting up libtinfo6:i386 (6.4-2) ...
Setting up libdrm-amdgpu1:i386 (2.4.114-1) ...
Setting up libxkbcommon0:i386 (1.5.0-1) ...
Setting up libwayland-client0:i386 (1.21.0-1) ...
Setting up libexpat1:i386 (2.5.0-1) ...
Setting up liblwp-protocol-https-perl (6.10-1) ...
Setting up libgraphite2-3:i386 (1.3.14-1) ...
Setting up liblcms2-2:i386 (2.14-2) ...
Setting up libpixman-1-0:i386 (0.42.2-1) ...
Setting up libwayland-server0:i386 (1.21.0-1) ...
Setting up libzstd1:i386 (1.5.4+dfsg2-3) ...
Setting up libice6:i386 (2:1.0.10-1) ...
Setting up libxau6:i386 (1:1.0.9-1) ...
Setting up libxdmcp6:i386 (1:1.1.2-3) ...
Setting up libkeyutils1:i386 (1.6.3-2) ...
Setting up libdrm-nouveau2:i386 (2.4.114-1) ...
Setting up libxcb1:i386 (1.15-1) ...
Setting up libpixman-1-dev:i386 (0.42.2-1) ...
Setting up libicu72:i386 (72.1-3) ...
Setting up libxcb-xfixes0:i386 (1.15-1) ...
Setting up liblerc4:i386 (4.0.0+ds-2) ...
Setting up libzstd-dev:i386 (1.5.4+dfsg2-3) ...
Setting up libxau-dev:i386 (1:1.0.9-1) ...
Setting up libwww-perl (6.68-1) ...
Setting up liblzma5:i386 (5.4.1-0.2) ...
Setting up libgpg-error0:i386 (1.46-1) ...
Setting up libdatrie1:i386 (0.2.13-2+b1) ...
Setting up libice-dev:i386 (2:1.0.10-1) ...
Setting up libgbm1:i386 (22.3.6-1) ...
Setting up libxcb-render0:i386 (1.15-1) ...
Setting up libdrm-radeon1:i386 (2.4.114-1) ...
Setting up liblz4-1:i386 (1.9.4-1) ...
Setting up libglvnd0:i386 (1.6.0-1) ...
Setting up libxcb-glx0:i386 (1.15-1) ...
Setting up libwebpdemux2:i386 (1.2.4-0.1) ...
Setting up libxkbcommon-dev:i386 (1.5.0-1) ...
Setting up libbrotli1:i386 (1.0.9-2+b6) ...
Setting up libedit2:i386 (3.1-20221030-2) ...
Setting up libavahi-common3:i386 (0.8-9) ...
Setting up libssl3:i386 (3.0.8-1) ...
Setting up libunistring2:i386 (1.0-2) ...
Setting up libdeflate0:i386 (1.14-1) ...
Setting up libgcrypt20:i386 (1.10.1-3) ...
Setting up liblzo2-2:i386 (2.10-2) ...
Setting up zlib1g:i386 (1:1.2.13.dfsg-1) ...
Setting up libcrypt1:i386 (1:4.4.33-2) ...
Setting up libidn2-0:i386 (2.3.3-1+b1) ...
Setting up libxcb-shm0:i386 (1.15-1) ...
Setting up libcom-err2:i386 (1.47.0-2) ...
Setting up libgomp1:i386 (12.2.0-14) ...
Setting up libffi-dev:i386 (3.4.4-1) ...
Setting up libunwind8:i386 (1.6.2-3) ...
Setting up libjbig0:i386 (2.1-6.1) ...
Setting up libpcre2-16-0:i386 (10.42-1) ...
Setting up libcap2:i386 (1:2.66-3) ...
Setting up libopengl0:i386 (1.6.0-1) ...
Setting up libkrb5support0:i386 (1.20.1-1) ...
Setting up libxcb-present0:i386 (1.15-1) ...
Setting up libthai0:i386 (0.1.29-1) ...
Setting up libxdmcp-dev:i386 (1:1.1.2-3) ...
Setting up libgraphite2-dev:i386 (1.3.14-1) ...
Setting up libz3-4:i386 (4.8.12-3.1) ...
Setting up libpcre2-32-0:i386 (10.42-1) ...
Setting up libwebp-dev:i386 (1.2.4-0.1) ...
Setting up libgles2:i386 (1.6.0-1) ...
Setting up libjpeg62-turbo:i386 (1:2.1.5-2) ...
Setting up libnettle8:i386 (3.8.1-2) ...
Setting up libepoxy0:i386 (1.5.10-1) ...
Setting up libxcb-sync1:i386 (1.15-1) ...
Setting up libgmp10:i386 (2:6.2.1+dfsg1-1.1) ...
Setting up libgles1:i386 (1.6.0-1) ...
Setting up libfribidi0:i386 (1.0.8-2.1) ...
Setting up libquadmath0:i386 (12.2.0-14) ...
Setting up libp11-kit0:i386 (0.24.1-2) ...
Setting up libpng16-16:i386 (1.6.39-2) ...
Setting up libatomic1:i386 (12.2.0-14) ...
Setting up libuuid1:i386 (2.38.1-5) ...
Setting up libsepol2:i386 (3.4-2) ...
Setting up libsepol-dev:i386 (3.4-2) ...
Setting up libsensors5:i386 (1:3.6.0-7.1) ...
Setting up libpcre2-8-0:i386 (10.42-1) ...
Setting up liblerc-dev:i386 (4.0.0+ds-2) ...
Setting up libk5crypto3:i386 (1.20.1-1) ...
Setting up libglapi-mesa:i386 (22.3.6-1) ...
Setting up liblzma-dev:i386 (5.4.1-0.2) ...
Setting up libubsan1:i386 (12.2.0-14) ...
Setting up libxcb-dri2-0:i386 (1.15-1) ...
Setting up libpcre2-posix3:i386 (10.42-1) ...
Setting up libdatrie-dev:i386 (0.2.13-2+b1) ...
Setting up libcrypt-dev:i386 (1:4.4.33-2) ...
Setting up libtiff6:i386 (4.5.0-5) ...
Setting up libwayland-cursor0:i386 (1.21.0-1) ...
Setting up libxcb-randr0:i386 (1.15-1) ...
Setting up libx11-6:i386 (2:1.8.4-2) ...
Setting up libkrb5-3:i386 (1.20.1-1) ...
Setting up libopengl-dev:i386 (1.6.0-1) ...
Setting up libtiffxx6:i386 (4.5.0-5) ...
Setting up libdeflate-dev:i386 (1.14-1) ...
Setting up libelf1:i386 (0.188-2.1) ...
Setting up libxcomposite1:i386 (1:0.4.5-1) ...
Setting up libsm6:i386 (2:1.2.3-1) ...
Setting up libxml2:i386 (2.9.14+dfsg-1.1+b3) ...
Setting up libbrotli-dev:i386 (1.0.9-2+b6) ...
Setting up libxcb-dri3-0:i386 (1.15-1) ...
Setting up libxml-parser-perl (2.46-4) ...
Setting up libx11-xcb1:i386 (2:1.8.4-2) ...
Setting up libpciaccess0:i386 (0.17-2) ...
Setting up libdw1:i386 (0.188-2.1) ...
Setting up libhogweed6:i386 (3.8.1-2) ...
Setting up libxdamage1:i386 (1:1.1.6-1) ...
Setting up libxcb1-dev:i386 (1.15-1) ...
Setting up libunwind-dev:i386 (1.6.2-3) ...
Setting up libxrender1:i386 (1:0.9.10-1.1) ...
Setting up libsm-dev:i386 (2:1.2.3-1) ...
Setting up libfribidi-dev:i386 (1.0.8-2.1) ...
Setting up libdrm-intel1:i386 (2.4.114-1) ...
Setting up libjbig-dev:i386 (2.1-6.1) ...
Setting up libx11-dev:i386 (2:1.8.4-2) ...
Setting up libxext6:i386 (2:1.3.4-1+b1) ...
Setting up libwayland-dev:i386 (1.21.0-1) ...
Setting up libsystemd0:i386 (252.6-1) ...
Setting up libxxf86vm1:i386 (1:1.1.4-1+b2) ...
Setting up libselinux1:i386 (3.4-1+b5) ...
Setting up libxcb-shm0-dev:i386 (1.15-1) ...
Setting up libegl-mesa0:i386 (22.3.6-1) ...
Setting up libgnutls30:i386 (3.7.9-1) ...
Setting up libfreetype6:i386 (2.12.1+dfsg-4) ...
Setting up libxfixes3:i386 (1:6.0.0-2) ...
Setting up libdbus-1-3:i386 (1.14.6-1) ...
Setting up libgcc-12-dev:i386 (12.2.0-14) ...
Setting up libxinerama1:i386 (2:1.1.4-3) ...
Setting up libgssapi-krb5-2:i386 (1.20.1-1) ...
Setting up libxrandr2:i386 (2:1.5.2-2+b1) ...
Setting up intltool (0.51.0-6) ...
Setting up libxcb-render0-dev:i386 (1.15-1) ...
Setting up libxext-dev:i386 (2:1.3.4-1+b1) ...
Setting up libthai-dev:i386 (0.1.29-1) ...
Setting up libmount1:i386 (2.38.1-5) ...
Setting up libllvm15:i386 (1:15.0.7-1) ...
Setting up libegl1:i386 (1.6.0-1) ...
Setting up libfontconfig1:i386 (2.14.1-4) ...
Setting up libxrender-dev:i386 (1:0.9.10-1.1) ...
Setting up libavahi-client3:i386 (0.8-9) ...
Setting up libtirpc3:i386 (1.3.3+ds-1) ...
Setting up libxft2:i386 (2.3.6-1) ...
Setting up libxi6:i386 (2:1.8-1+b1) ...
Setting up libglib2.0-0:i386 (2.74.6-1) ...
/var/lib/dpkg/info/libglib2.0-0:i386.postinst: 42: /usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas: Exec format error
/var/lib/dpkg/info/libglib2.0-0:i386.postinst: 43: /usr/lib/i386-linux-gnu/glib-2.0/gio-querymodules: Exec format error
Setting up libxtst6:i386 (2:1.2.3-1.1) ...
Setting up libdbusmenu-glib4:i386 (18.10.20180917~bzr492+repack1-3) ...
Setting up libxcursor1:i386 (1:1.2.1-1) ...
Setting up libgl1-mesa-dri:i386 (22.3.6-1) ...
Setting up libatspi2.0-0:i386 (2.46.0-5) ...
Setting up gnome-common (3.18.0-4) ...
Setting up libcairo2:i386 (1.16.0-7) ...
Setting up libcolord2:i386 (1.4.6-2.2) ...
Setting up libxfixes-dev:i386 (1:6.0.0-2) ...
Setting up libxrandr-dev:i386 (2:1.5.2-2+b1) ...
Setting up libtirpc-dev:i386 (1.3.3+ds-1) ...
Setting up libdbus-glib-1-2:i386 (0.112-3) ...
Setting up libxinerama-dev:i386 (2:1.1.4-3) ...
Setting up libcups2:i386 (2.4.2-2) ...
Setting up libnsl2:i386 (1.3.0-2) ...
Setting up libharfbuzz0b:i386 (6.0.0+dfsg-3) ...
Setting up libgirepository-1.0-1:i386 (1.74.0-3) ...
Setting up libgdk-pixbuf-2.0-0:i386 (2.42.10+dfsg-1+b1) ...
/var/lib/dpkg/info/libgdk-pixbuf-2.0-0:i386.postinst: 30: /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders: Exec format error
Setting up libcairo-gobject2:i386 (1.16.0-7) ...
Setting up libatk1.0-0:i386 (2.46.0-5) ...
Setting up libxi-dev:i386 (2:1.8-1+b1) ...
Setting up libgstreamer1.0-0:i386 (1.22.0-2) ...
Setcap worked! gst-ptp-helper is not suid!
Setting up libxtst-dev:i386 (2:1.2.3-1.1) ...
Setting up libxdamage-dev:i386 (1:1.1.6-1) ...
Setting up libcairo-script-interpreter2:i386 (1.16.0-7) ...
Setting up libharfbuzz-icu0:i386 (6.0.0+dfsg-3) ...
Setting up libglx-mesa0:i386 (22.3.6-1) ...
Setting up libglx0:i386 (1.6.0-1) ...
Setting up libgconf-2-4:i386 (3.2.6-8) ...
Setting up libxcomposite-dev:i386 (1:0.4.5-1) ...
Setting up libxcursor-dev:i386 (1:1.2.1-1) ...
Setting up libpango-1.0-0:i386 (1.50.12+ds-1) ...
Setting up libharfbuzz-gobject0:i386 (6.0.0+dfsg-3) ...
Setting up libatk-bridge2.0-0:i386 (2.46.0-5) ...
Setting up libgl1:i386 (1.6.0-1) ...
Setting up libnotify4:i386 (0.8.1-1) ...
Setting up gir1.2-glib-2.0:i386 (1.74.0-3) ...
Setting up libnsl-dev:i386 (1.3.0-2) ...
Setting up libharfbuzz-subset0:i386 (6.0.0+dfsg-3) ...
Setting up libc6-dev:i386 (2.36-8) ...
Setting up libglx-dev:i386 (1.6.0-1) ...
Setting up libpangoft2-1.0-0:i386 (1.50.12+ds-1) ...
Setting up libicu-dev:i386 (72.1-3) ...
Setting up libgl-dev:i386 (1.6.0-1) ...
Setting up libpangocairo-1.0-0:i386 (1.50.12+ds-1) ...
Setting up gir1.2-gconf-2.0:i386 (3.2.6-8) ...
Setting up gir1.2-gstreamer-1.0:i386 (1.22.0-2) ...
Setting up libdbusmenu-gtk3-4:i386 (18.10.20180917~bzr492+repack1-3) ...
Setting up gir1.2-freedesktop:i386 (1.74.0-3) ...
Setting up libpangoxft-1.0-0:i386 (1.50.12+ds-1) ...
Setting up gir1.2-dbusmenu-glib-0.4:i386 (18.10.20180917~bzr492+repack1-3) ...
Setting up libpcre2-dev:i386 (10.42-1) ...
Setting up gir1.2-gdkpixbuf-2.0:i386 (2.42.10+dfsg-1+b1) ...
Setting up libegl-dev:i386 (1.6.0-1) ...
Setting up libstdc++-12-dev:i386 (12.2.0-14) ...
Setting up gir1.2-atk-1.0:i386 (2.46.0-5) ...
Setting up libselinux1-dev:i386 (3.4-1+b5) ...
Setting up libgtk-3-0:i386 (3.24.36-4) ...
/var/lib/dpkg/info/libgtk-3-0:i386.postinst: 17: /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: Exec format error
Setting up libgtk2.0-0:i386 (2.24.33-2) ...
/var/lib/dpkg/info/libgtk2.0-0:i386.postinst: 19: /usr/lib/i386-linux-gnu/libgtk2.0-0/gtk-query-immodules-2.0: Exec format error
Setting up libepoxy-dev:i386 (1.5.10-1) ...
Setting up gir1.2-atspi-2.0:i386 (2.46.0-5) ...
Setting up libayatana-ido3-0.4-0:i386 (0.9.3-1) ...
Setting up gir1.2-harfbuzz-0.0:i386 (6.0.0+dfsg-3) ...
Setting up gir1.2-pango-1.0:i386 (1.50.12+ds-1) ...
Setting up libxml2-dev:i386 (2.9.14+dfsg-1.1+b3) ...
Setting up libexpat1-dev:i386 (2.5.0-1) ...
Setting up libjpeg62-turbo-dev:i386 (1:2.1.5-2) ...
Setting up gir1.2-gtk-2.0:i386 (2.24.33-2) ...
Setting up uuid-dev:i386 (2.38.1-5) ...
Setting up gir1.2-ayatanaido3-0.4:i386 (0.9.3-1) ...
Setting up zlib1g-dev:i386 (1:1.2.13.dfsg-1) ...
Setting up gir1.2-notify-0.7:i386 (0.8.1-1) ...
Setting up libgles-dev:i386 (1.6.0-1) ...
Setting up libayatana-indicator3-7:i386 (0.9.3-1) ...
Setting up libblkid-dev:i386 (2.38.1-5) ...
Setting up libpng-dev:i386 (1.6.39-2) ...
Setting up gir1.2-gtk-3.0:i386 (3.24.36-4) ...
Setting up libjpeg-dev:i386 (1:2.1.5-2) ...
Setting up libglvnd-dev:i386 (1.6.0-1) ...
Setting up libfreetype-dev:i386 (2.12.1+dfsg-4) ...
Setting up libtiff-dev:i386 (4.5.0-5) ...
Setting up libayatana-appindicator3-1:i386 (0.5.92-1) ...
Setting up libelf-dev:i386 (0.188-2.1) ...
Setting up gir1.2-ayatanaappindicator3-0.1:i386 (0.5.92-1) ...
Setting up libmount-dev:i386 (2.38.1-5) ...
Setting up libegl1-mesa-dev:i386 (22.3.6-1) ...
Setting up libfontconfig-dev:i386 (2.14.1-4) ...
Setting up libdw-dev:i386 (0.188-2.1) ...
Setting up libglib2.0-dev:i386 (2.74.6-1) ...
Setting up libcairo2-dev:i386 (1.16.0-7) ...
Setting up libatk1.0-dev:i386 (2.46.0-5) ...
Setting up libxft-dev:i386 (2.3.6-1) ...
Setting up libgdk-pixbuf-2.0-dev:i386 (2.42.10+dfsg-1+b1) ...
Setting up libharfbuzz-dev:i386 (6.0.0+dfsg-3) ...
Setting up libnotify-dev:i386 (0.8.1-1) ...
Setting up libgstreamer1.0-dev:i386 (1.22.0-2) ...
Setting up libpango1.0-dev:i386 (1.50.12+ds-1) ...
Setting up libgtk2.0-dev:i386 (2.24.33-2) ...
Setting up libdbusmenu-glib-dev:i386 (18.10.20180917~bzr492+repack1-3) ...
Processing triggers for libc-bin (2.36-8) ...
Processing triggers for systemd (252.6-1) ...
Processing triggers for sgml-base (1.31) ...
Setting up libdbus-1-dev:i386 (1.14.6-1) ...
Setting up libatspi2.0-dev:i386 (2.46.0-5) ...
Setting up libgconf2-dev:i386 (3.2.6-8) ...
Setting up libatk-bridge2.0-dev:i386 (2.46.0-5) ...
Setting up libgtk-3-dev:i386 (3.24.36-4) ...
Setting up libayatana-ido3-dev:i386 (0.9.3-1) ...
Setting up libayatana-indicator3-dev:i386 (0.9.3-1) ...
Setting up libayatana-appindicator3-dev:i386 (0.5.92-1) ...
Setting up sbuild-build-depends-main-dummy:i386 (0.invalid.0) ...
Processing triggers for ca-certificates (20211016) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Processing triggers for libgdk-pixbuf-2.0-0:arm64 (2.42.10+dfsg-1+b1) ...

+------------------------------------------------------------------------------+
| Check architectures                                                          |
+------------------------------------------------------------------------------+

Arch check ok (i386 included in any)

+------------------------------------------------------------------------------+
| Build environment                                                            |
+------------------------------------------------------------------------------+

Kernel: Linux 5.10.0-0.bpo.15-arm64 #1 SMP Debian 5.10.120-1~bpo10+1 (2022-06-13) arm64 (aarch64)
Toolchain package versions: binutils_2.40-2 dpkg-dev_1.21.21 g++-12_12.2.0-14 gcc-12_12.2.0-14 libc6-dev_2.36-8 libstdc++-12-dev_12.2.0-14 libstdc++-12-dev-i386-cross_12.2.0-14cross1 libstdc++6_12.2.0-14 libstdc++6-i386-cross_12.2.0-14cross1 linux-libc-dev_6.1.15-1
Package versions: adduser_3.131 adwaita-icon-theme_43-1 apt_2.6.0 at-spi2-common_2.46.0-5 autoconf_2.71-3 autoconf-archive_20220903-3 automake_1:1.16.5-1.3 autopoint_0.21-12 autotools-dev_20220109.1 base-files_12.4 base-passwd_3.6.1 bash_5.2.15-2+b1 binutils_2.40-2 binutils-aarch64-linux-gnu_2.40-2 binutils-common_2.40-2 binutils-i686-linux-gnu_2.40-2 bsdextrautils_2.38.1-5 bsdutils_1:2.38.1-5 build-essential_12.9 bzip2_1.0.8-5+b1 ca-certificates_20211016 cmake_3.25.1-1 cmake-data_3.25.1-1 coreutils_9.1-1 cpp_4:12.2.0-3 cpp-12_12.2.0-14 cpp-12-i686-linux-gnu_12.2.0-14cross1 cpp-i686-linux-gnu_4:12.2.0-3 cross-config_2.6.20 crossbuild-essential-i386_12.9 dash_0.5.12-2 dbus_1.14.6-1 dbus-bin_1.14.6-1 dbus-daemon_1.14.6-1 dbus-session-bus-common_1.14.6-1 dbus-system-bus-common_1.14.6-1 dbus-user-session_1.14.6-1 dconf-gsettings-backend_0.40.0-4 dconf-service_0.40.0-4 debconf_1.5.82 debhelper_13.11.4 debian-archive-keyring_2021.1.1 debianutils_5.7-0.4 dh-autoreconf_20 dh-strip-nondeterminism_1.13.1-1 diffutils_1:3.8-4 dmsetup_2:1.02.185-2 dpkg_1.21.21 dpkg-cross_2.6.20 dpkg-dev_1.21.21 dwz_0.15-1 fakeroot_1.31-1.1 file_1:5.44-3 findutils_4.9.0-4 fontconfig_2.14.1-4 fontconfig-config_2.14.1-4 fonts-dejavu-core_2.37-5 g++_4:12.2.0-3 g++-12_12.2.0-14 g++-12-i686-linux-gnu_12.2.0-14cross1 g++-i686-linux-gnu_4:12.2.0-3 gcc_4:12.2.0-3 gcc-12_12.2.0-14 gcc-12-base_12.2.0-14 gcc-12-cross-base_12.2.0-14cross1 gcc-12-i686-linux-gnu_12.2.0-14cross1 gcc-12-i686-linux-gnu-base_12.2.0-14cross1 gcc-i686-linux-gnu_4:12.2.0-3 gconf-service_3.2.6-8 gconf2_3.2.6-8 gconf2-common_3.2.6-8 gettext_0.21-12 gettext-base_0.21-12 gir1.2-atk-1.0_2.46.0-5 gir1.2-atspi-2.0_2.46.0-5 gir1.2-ayatanaappindicator3-0.1_0.5.92-1 gir1.2-ayatanaido3-0.4_0.9.3-1 gir1.2-dbusmenu-glib-0.4_18.10.20180917~bzr492+repack1-3 gir1.2-freedesktop_1.74.0-3 gir1.2-gconf-2.0_3.2.6-8 gir1.2-gdkpixbuf-2.0_2.42.10+dfsg-1+b1 gir1.2-glib-2.0_1.74.0-3 gir1.2-gstreamer-1.0_1.22.0-2 gir1.2-gtk-2.0_2.24.33-2 gir1.2-gtk-3.0_3.24.36-4 gir1.2-harfbuzz-0.0_6.0.0+dfsg-3 gir1.2-notify-0.7_0.8.1-1 gir1.2-pango-1.0_1.50.12+ds-1 gnome-common_3.18.0-4 gnome-icon-theme_3.12.0-5 gpgv_2.2.40-1 grep_3.8-5 groff-base_1.22.4-10 gtk-update-icon-cache_3.24.36-4 gzip_1.12-1 hicolor-icon-theme_0.17-2 hostname_3.23+nmu1 icu-devtools_72.1-3 init-system-helpers_1.65.2 intltool_0.51.0-6 intltool-debian_0.35.0+20060710.6 libacl1_2.3.1-3 libapparmor1_3.0.8-3 libapt-pkg6.0_2.6.0 libarchive-zip-perl_1.68-1 libarchive13_3.6.2-1 libargon2-1_0~20190702-0.1 libasan8_12.2.0-14 libasan8-i386-cross_12.2.0-14cross1 libatk-bridge2.0-0_2.46.0-5 libatk-bridge2.0-dev_2.46.0-5 libatk1.0-0_2.46.0-5 libatk1.0-dev_2.46.0-5 libatomic1_12.2.0-14 libatomic1-i386-cross_12.2.0-14cross1 libatspi2.0-0_2.46.0-5 libatspi2.0-dev_2.46.0-5 libattr1_1:2.5.1-4 libaudit-common_1:3.0.9-1 libaudit1_1:3.0.9-1 libavahi-client3_0.8-9 libavahi-common-data_0.8-9 libavahi-common3_0.8-9 libayatana-appindicator3-1_0.5.92-1 libayatana-appindicator3-dev_0.5.92-1 libayatana-ido3-0.4-0_0.9.3-1 libayatana-ido3-dev_0.9.3-1 libayatana-indicator3-7_0.9.3-1 libayatana-indicator3-dev_0.9.3-1 libbinutils_2.40-2 libblkid-dev_2.38.1-5 libblkid1_2.38.1-5 libbrotli-dev_1.0.9-2+b6 libbrotli1_1.0.9-2+b6 libbsd0_0.11.7-4 libbz2-1.0_1.0.8-5+b1 libc-bin_2.36-8 libc-dev-bin_2.36-8 libc6_2.36-8 libc6-dev_2.36-8 libc6-dev-i386-cross_2.36-8cross1 libc6-i386-cross_2.36-8cross1 libcairo-gobject2_1.16.0-7 libcairo-script-interpreter2_1.16.0-7 libcairo2_1.16.0-7 libcairo2-dev_1.16.0-7 libcap-ng0_0.8.3-1+b3 libcap2_1:2.66-3 libcap2-bin_1:2.66-3 libcc1-0_12.2.0-14 libclone-perl_0.46-1 libcolord2_1.4.6-2.2 libcom-err2_1.47.0-2 libconfig-auto-perl_0.44-2 libconfig-inifiles-perl_3.000003-2 libcrypt-dev_1:4.4.33-2 libcrypt1_1:4.4.33-2 libcryptsetup12_2:2.6.1-2 libctf-nobfd0_2.40-2 libctf0_2.40-2 libcups2_2.4.2-2 libcurl4_7.88.1-5 libdatrie-dev_0.2.13-2+b1 libdatrie1_0.2.13-2+b1 libdb5.3_5.3.28+dfsg2-1 libdbus-1-3_1.14.6-1 libdbus-1-dev_1.14.6-1 libdbus-glib-1-2_0.112-3 libdbusmenu-glib-dev_18.10.20180917~bzr492+repack1-3 libdbusmenu-glib4_18.10.20180917~bzr492+repack1-3 libdbusmenu-gtk3-4_18.10.20180917~bzr492+repack1-3 libdconf1_0.40.0-4 libdebconfclient0_0.267 libdebhelper-perl_13.11.4 libdebian-dpkgcross-perl_2.6.20 libdeflate-dev_1.14-1 libdeflate0_1.14-1 libdevmapper1.02.1_2:1.02.185-2 libdpkg-perl_1.21.21 libdrm-amdgpu1_2.4.114-1 libdrm-common_2.4.114-1 libdrm-intel1_2.4.114-1 libdrm-nouveau2_2.4.114-1 libdrm-radeon1_2.4.114-1 libdrm2_2.4.114-1 libdw-dev_0.188-2.1 libdw1_0.188-2.1 libedit2_3.1-20221030-2 libegl-dev_1.6.0-1 libegl-mesa0_22.3.6-1 libegl1_1.6.0-1 libegl1-mesa-dev_22.3.6-1 libelf-dev_0.188-2.1 libelf1_0.188-2.1 libencode-locale-perl_1.05-3 libepoxy-dev_1.5.10-1 libepoxy0_1.5.10-1 libexpat1_2.5.0-1 libexpat1-dev_2.5.0-1 libfakeroot_1.31-1.1 libfdisk1_2.38.1-5 libffi-dev_3.4.4-1 libffi8_3.4.4-1 libfile-find-rule-perl_0.34-3 libfile-homedir-perl_1.006-2 libfile-listing-perl_6.15-1 libfile-stripnondeterminism-perl_1.13.1-1 libfile-which-perl_1.27-2 libfontconfig-dev_2.14.1-4 libfontconfig1_2.14.1-4 libfreetype-dev_2.12.1+dfsg-4 libfreetype6_2.12.1+dfsg-4 libfribidi-dev_1.0.8-2.1 libfribidi0_1.0.8-2.1 libgbm1_22.3.6-1 libgcc-12-dev_12.2.0-14 libgcc-12-dev-i386-cross_12.2.0-14cross1 libgcc-s1_12.2.0-14 libgcc-s1-i386-cross_12.2.0-14cross1 libgconf-2-4_3.2.6-8 libgconf2-dev_3.2.6-8 libgcrypt20_1.10.1-3 libgdbm-compat4_1.23-3 libgdbm6_1.23-3 libgdk-pixbuf-2.0-0_2.42.10+dfsg-1+b1 libgdk-pixbuf-2.0-dev_2.42.10+dfsg-1+b1 libgdk-pixbuf2.0-bin_2.42.10+dfsg-1+b1 libgdk-pixbuf2.0-common_2.42.10+dfsg-1 libgirepository-1.0-1_1.74.0-3 libgl-dev_1.6.0-1 libgl1_1.6.0-1 libgl1-mesa-dri_22.3.6-1 libglapi-mesa_22.3.6-1 libgles-dev_1.6.0-1 libgles1_1.6.0-1 libgles2_1.6.0-1 libglib2.0-0_2.74.6-1 libglib2.0-bin_2.74.6-1 libglib2.0-data_2.74.6-1 libglib2.0-dev_2.74.6-1 libglib2.0-dev-bin_2.74.6-1 libglvnd-core-dev_1.6.0-1 libglvnd-dev_1.6.0-1 libglvnd0_1.6.0-1 libglx-dev_1.6.0-1 libglx-mesa0_22.3.6-1 libglx0_1.6.0-1 libgmp10_2:6.2.1+dfsg1-1.1 libgnutls30_3.7.9-1 libgomp1_12.2.0-14 libgomp1-i386-cross_12.2.0-14cross1 libgpg-error0_1.46-1 libgprofng0_2.40-2 libgraphite2-3_1.3.14-1 libgraphite2-dev_1.3.14-1 libgssapi-krb5-2_1.20.1-1 libgstreamer1.0-0_1.22.0-2 libgstreamer1.0-dev_1.22.0-2 libgtk-3-0_3.24.36-4 libgtk-3-common_3.24.36-4 libgtk-3-dev_3.24.36-4 libgtk2.0-0_2.24.33-2 libgtk2.0-common_2.24.33-2 libgtk2.0-dev_2.24.33-2 libharfbuzz-dev_6.0.0+dfsg-3 libharfbuzz-gobject0_6.0.0+dfsg-3 libharfbuzz-icu0_6.0.0+dfsg-3 libharfbuzz-subset0_6.0.0+dfsg-3 libharfbuzz0b_6.0.0+dfsg-3 libhogweed6_3.8.1-2 libhtml-parser-perl_3.81-1 libhtml-tagset-perl_3.20-6 libhtml-tree-perl_5.07-3 libhttp-cookies-perl_6.10-1 libhttp-date-perl_6.05-2 libhttp-message-perl_6.44-1 libhttp-negotiate-perl_6.01-2 libhwasan0_12.2.0-14 libice-dev_2:1.0.10-1 libice6_2:1.0.10-1 libicu-dev_72.1-3 libicu72_72.1-3 libidn2-0_2.3.3-1+b1 libio-html-perl_1.004-3 libio-socket-ssl-perl_2.081-2 libio-string-perl_1.08-4 libip4tc2_1.8.9-2 libisl23_0.25-1 libitm1_12.2.0-14 libitm1-i386-cross_12.2.0-14cross1 libjansson4_2.14-2 libjbig-dev_2.1-6.1 libjbig0_2.1-6.1 libjpeg-dev_1:2.1.5-2 libjpeg62-turbo_1:2.1.5-2 libjpeg62-turbo-dev_1:2.1.5-2 libjson-c5_0.16-2 libjsoncpp25_1.9.5-4 libk5crypto3_1.20.1-1 libkeyutils1_1.6.3-2 libkmod2_30+20221128-1 libkrb5-3_1.20.1-1 libkrb5support0_1.20.1-1 liblcms2-2_2.14-2 libldap-2.5-0_2.5.13+dfsg-5 liblerc-dev_4.0.0+ds-2 liblerc4_4.0.0+ds-2 libllvm15_1:15.0.7-1 liblocale-gettext-perl_1.07-5 liblsan0_12.2.0-14 liblwp-mediatypes-perl_6.04-2 liblwp-protocol-https-perl_6.10-1 liblz4-1_1.9.4-1 liblzma-dev_5.4.1-0.2 liblzma5_5.4.1-0.2 liblzo2-2_2.10-2 libmagic-mgc_1:5.44-3 libmagic1_1:5.44-3 libmd0_1.0.4-2 libmount-dev_2.38.1-5 libmount1_2.38.1-5 libmpc3_1.3.1-1 libmpfr6_4.2.0-1 libncursesw6_6.4-2 libnet-http-perl_6.22-1 libnet-ssleay-perl_1.92-2+b1 libnettle8_3.8.1-2 libnghttp2-14_1.52.0-1 libnotify-dev_0.8.1-1 libnotify4_0.8.1-1 libnsl-dev_1.3.0-2 libnsl2_1.3.0-2 libnumber-compare-perl_0.03-3 libopengl-dev_1.6.0-1 libopengl0_1.6.0-1 libp11-kit0_0.24.1-2 libpam-modules_1.5.2-6 libpam-modules-bin_1.5.2-6 libpam-runtime_1.5.2-6 libpam-systemd_252.6-1 libpam0g_1.5.2-6 libpango-1.0-0_1.50.12+ds-1 libpango1.0-dev_1.50.12+ds-1 libpangocairo-1.0-0_1.50.12+ds-1 libpangoft2-1.0-0_1.50.12+ds-1 libpangoxft-1.0-0_1.50.12+ds-1 libpciaccess0_0.17-2 libpcre2-16-0_10.42-1 libpcre2-32-0_10.42-1 libpcre2-8-0_10.42-1 libpcre2-dev_10.42-1 libpcre2-posix3_10.42-1 libperl5.36_5.36.0-7 libpipeline1_1.5.7-1 libpixman-1-0_0.42.2-1 libpixman-1-dev_0.42.2-1 libpkgconf3_1.8.1-1 libpng-dev_1.6.39-2 libpng16-16_1.6.39-2 libproc2-0_2:4.0.3-1 libpsl5_0.21.2-1 libpthread-stubs0-dev_0.4-1 libpython3-stdlib_3.11.2-1 libpython3.11-minimal_3.11.2-4 libpython3.11-stdlib_3.11.2-4 libquadmath0_12.2.0-14 libquadmath0-i386-cross_12.2.0-14cross1 libreadline8_8.2-1.3 libregexp-ipv6-perl_0.03-3 librhash0_1.4.3-3 librsvg2-2_2.54.5+dfsg-1 librsvg2-common_2.54.5+dfsg-1 librtmp1_2.4+20151223.gitfa8646d.1-2+b2 libsasl2-2_2.1.28+dfsg-11 libsasl2-modules-db_2.1.28+dfsg-11 libseccomp2_2.5.4-1+b3 libselinux1_3.4-1+b5 libselinux1-dev_3.4-1+b5 libsemanage-common_3.4-1 libsemanage2_3.4-1+b5 libsensors-config_1:3.6.0-7.1 libsensors5_1:3.6.0-7.1 libsepol-dev_3.4-2 libsepol2_3.4-2 libsm-dev_2:1.2.3-1 libsm6_2:1.2.3-1 libsmartcols1_2.38.1-5 libsqlite3-0_3.40.1-1 libssh2-1_1.10.0-3+b1 libssl3_3.0.8-1 libstdc++-12-dev_12.2.0-14 libstdc++-12-dev-i386-cross_12.2.0-14cross1 libstdc++6_12.2.0-14 libstdc++6-i386-cross_12.2.0-14cross1 libsub-override-perl_0.09-4 libsystemd-shared_252.6-1 libsystemd0_252.6-1 libtasn1-6_4.19.0-2 libtext-glob-perl_0.11-3 libthai-data_0.1.29-1 libthai-dev_0.1.29-1 libthai0_0.1.29-1 libtiff-dev_4.5.0-5 libtiff6_4.5.0-5 libtiffxx6_4.5.0-5 libtimedate-perl_2.3300-2 libtinfo6_6.4-2 libtirpc-common_1.3.3+ds-1 libtirpc-dev_1.3.3+ds-1 libtirpc3_1.3.3+ds-1 libtool_2.4.7-5 libtry-tiny-perl_0.31-2 libtsan2_12.2.0-14 libubsan1_12.2.0-14 libubsan1-i386-cross_12.2.0-14cross1 libuchardet0_0.0.7-1 libudev1_252.6-1 libunistring2_1.0-2 libunwind-dev_1.6.2-3 libunwind8_1.6.2-3 liburi-perl_5.17-1 libuuid1_2.38.1-5 libuv1_1.44.2-1 libwayland-bin_1.21.0-1 libwayland-client0_1.21.0-1 libwayland-cursor0_1.21.0-1 libwayland-dev_1.21.0-1 libwayland-egl1_1.21.0-1 libwayland-server0_1.21.0-1 libwebp-dev_1.2.4-0.1 libwebp7_1.2.4-0.1 libwebpdemux2_1.2.4-0.1 libwebpmux3_1.2.4-0.1 libwww-perl_6.68-1 libwww-robotrules-perl_6.02-1 libx11-6_2:1.8.4-2 libx11-data_2:1.8.4-2 libx11-dev_2:1.8.4-2 libx11-xcb1_2:1.8.4-2 libxau-dev_1:1.0.9-1 libxau6_1:1.0.9-1 libxcb-dri2-0_1.15-1 libxcb-dri3-0_1.15-1 libxcb-glx0_1.15-1 libxcb-present0_1.15-1 libxcb-randr0_1.15-1 libxcb-render0_1.15-1 libxcb-render0-dev_1.15-1 libxcb-shm0_1.15-1 libxcb-shm0-dev_1.15-1 libxcb-sync1_1.15-1 libxcb-xfixes0_1.15-1 libxcb1_1.15-1 libxcb1-dev_1.15-1 libxcomposite-dev_1:0.4.5-1 libxcomposite1_1:0.4.5-1 libxcursor-dev_1:1.2.1-1 libxcursor1_1:1.2.1-1 libxdamage-dev_1:1.1.6-1 libxdamage1_1:1.1.6-1 libxdmcp-dev_1:1.1.2-3 libxdmcp6_1:1.1.2-3 libxext-dev_2:1.3.4-1+b1 libxext6_2:1.3.4-1+b1 libxfixes-dev_1:6.0.0-2 libxfixes3_1:6.0.0-2 libxft-dev_2.3.6-1 libxft2_2.3.6-1 libxi-dev_2:1.8-1+b1 libxi6_2:1.8-1+b1 libxinerama-dev_2:1.1.4-3 libxinerama1_2:1.1.4-3 libxkbcommon-dev_1.5.0-1 libxkbcommon0_1.5.0-1 libxml-libxml-perl_2.0207+dfsg+really+2.0134-1+b1 libxml-namespacesupport-perl_1.12-2 libxml-parser-perl_2.46-4 libxml-sax-base-perl_1.09-3 libxml-sax-perl_1.02+dfsg-3 libxml-simple-perl_2.25-2 libxml2_2.9.14+dfsg-1.1+b3 libxml2-dev_2.9.14+dfsg-1.1+b3 libxml2-utils_2.9.14+dfsg-1.1+b3 libxrandr-dev_2:1.5.2-2+b1 libxrandr2_2:1.5.2-2+b1 libxrender-dev_1:0.9.10-1.1 libxrender1_1:0.9.10-1.1 libxshmfence1_1.3-1 libxtst-dev_2:1.2.3-1.1 libxtst6_2:1.2.3-1.1 libxxf86vm1_1:1.1.4-1+b2 libxxhash0_0.8.1-1 libyaml-perl_1.30-2 libz3-4_4.8.12-3.1 libzstd-dev_1.5.4+dfsg2-3 libzstd1_1.5.4+dfsg2-3 linux-libc-dev_6.1.15-1 linux-libc-dev-i386-cross_6.1.4-1cross1 login_1:4.13+dfsg1-1 m4_1.4.19-3 make_4.3-4.1 man-db_2.11.2-1 mawk_1.3.4.20200120-3.1 media-types_10.0.0 mount_2.38.1-5 ncurses-base_6.4-2 ncurses-bin_6.4-2 netbase_6.4 openssl_3.0.8-1 pango1.0-tools_1.50.12+ds-1 passwd_1:4.13+dfsg1-1 patch_2.7.6-7 perl_5.36.0-7 perl-base_5.36.0-7 perl-modules-5.36_5.36.0-7 perl-openssl-defaults_7+b1 pkg-config_1.8.1-1 pkgconf_1.8.1-1 pkgconf-bin_1.8.1-1 po-debconf_1.0.21+nmu1 procps_2:4.0.3-1 psmisc_23.6-1 python3_3.11.2-1 python3-distutils_3.11.2-2 python3-lib2to3_3.11.2-2 python3-minimal_3.11.2-1 python3.11_3.11.2-4 python3.11-minimal_3.11.2-4 readline-common_8.2-1.3 rpcsvc-proto_1.4.3-1 sbuild-build-depends-main-dummy_0.invalid.0 sed_4.9-1 sensible-utils_0.0.17+nmu1 sgml-base_1.31 shared-mime-info_2.2-1 systemd_252.6-1 systemd-sysv_252.6-1 sysvinit-utils_3.06-2 tar_1.34+dfsg-1.1 tzdata_2022g-7 ucf_3.0043+nmu1 usrmerge_35 util-linux_2.38.1-5 util-linux-extra_2.38.1-5 uuid-dev_2.38.1-5 wayland-protocols_1.31-1 x11-common_1:7.7+23 x11proto-dev_2022.1-1 xkb-data_2.35.1-1 xml-core_0.18+nmu1 xorg-sgml-doctools_1:1.11-1.1 xtrans-dev_1.4.0-1 xz-utils_5.4.1-0.2 zlib1g_1:1.2.13.dfsg-1 zlib1g-dev_1:1.2.13.dfsg-1

+------------------------------------------------------------------------------+
| Build                                                                        |
+------------------------------------------------------------------------------+


Unpack source
-------------

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 3.0 (quilt)
Source: alarm-clock-applet
Binary: alarm-clock-applet, alarm-clock-applet-gconf-migration
Architecture: any
Version: 0.4.1-3
Maintainer: Chow Loong Jin <hyperair@debian.org>
Uploaders: Johannes H. Jensen <joh@pseudoberries.com>
Homepage: https://alarm-clock-applet.github.io
Standards-Version: 4.4.1
Vcs-Browser: https://salsa.debian.org/debian/alarm-clock-applet
Vcs-Git: https://salsa.debian.org/debian/alarm-clock-applet.git
Build-Depends: debhelper-compat (= 12), cmake (>= 3.10), intltool (>= 0.40), libgtk-3-dev, libgstreamer1.0-dev, libnotify-dev, libayatana-appindicator3-dev, libglib2.0-dev, libgconf2-dev (>= 2.8.0), gnome-icon-theme (>= 2.15.91), libxml2-dev, gnome-common
Package-List:
 alarm-clock-applet deb gnome optional arch=any
 alarm-clock-applet-gconf-migration deb gnome optional arch=any
Checksums-Sha1:
 4d46097df9f2ee213c44c8917e8a073227e76302 208601 alarm-clock-applet_0.4.1.orig.tar.gz
 e0cf93f55adf354081d48b065d073f3df833a34e 7048 alarm-clock-applet_0.4.1-3.debian.tar.xz
Checksums-Sha256:
 2483804fd6a2a3f6035f9eb4926ab9c74c2a95f68a904dde2df59765a252300b 208601 alarm-clock-applet_0.4.1.orig.tar.gz
 12cc1c45859f354b41ba56df0632cd70a0353e9a8359387b17e23607dd83b53a 7048 alarm-clock-applet_0.4.1-3.debian.tar.xz
Files:
 5be11d3bc84be80c2a15f143a6920af7 208601 alarm-clock-applet_0.4.1.orig.tar.gz
 b3f50c3e2ff2b939412f632d7e032d78 7048 alarm-clock-applet_0.4.1-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEEuDQnfs/9/dZ027Q+9UiW1iHUqEFAmPs1ncACgkQ+9UiW1iH
UqFWWQ/+OB9JoiDzhQf4Um3rlAg66vN5t8amj+FdR2CJ+3+IASsN2CHd37YZtzMM
vAuCHLJYbQgigdb9GCxjGeZjauBDqSeAAH6u02dZOIlruDz25kOpdxBwl9LVq+MS
orpbNKhZuSIamd1i/ClwrRARrtHPYBlQ8eMG0Dgtog/1mFubDpnMHggWtl+GCDCK
1O9vGh3o0eOO0rJQZVN3vE3NscdUtP/qUr/tYOFF1b4sTThVD4ILxocaPo9NdSyr
rMzD6HMSGtPls/OL/B0cYVBOC/PVGY7nSYHQZ5VIodt4VC8BuzhFUOsOBv2Fqb7l
k+FVAfEBmJPUhPEBzy39Ti+v4iMyOn81r3Wz6RNR0RR5Q29lGJGjPpE/WTW332+M
FvjDLeHCgGUXfZeCodRjF18ui/ltcDjXijUsNlcJA/tlx+JIzPLYNlIAeEXBNH+F
20EF1Ri7ThozudPCg4BALWqSERJId7BGYWCbQkdh297OdNLZMjcjXtlIdM+Gz1Pi
/lP9u/8PFybgIx3CurKKG9eSir7JwuG9jf13grlEku5KPTC+5sXvZMcX9ktqmfbz
agoJCh2Qim+XrSZ0Y2rdzdpVzzw3zUqH9sbFWVyGXox34JjWSQeyBlHrhaGlMPtk
PFH18Xjh4HrcsXmE2mI5taH1VIRqLnNMz51B2ZCDh+oOmMsJZrg=
=0jY1
-----END PGP SIGNATURE-----

gpgv: Signature made Wed Feb 15 12:56:23 2023 UTC
gpgv:                using RSA key 12E0D09DFB3FF7F759D36ED0FBD5225B588752A1
gpgv: Can't check signature: No public key
dpkg-source: warning: cannot verify inline signature for ./alarm-clock-applet_0.4.1-3.dsc: no acceptable signature found
dpkg-source: info: extracting alarm-clock-applet in /<<PKGBUILDDIR>>
dpkg-source: info: unpacking alarm-clock-applet_0.4.1.orig.tar.gz
dpkg-source: info: unpacking alarm-clock-applet_0.4.1-3.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying Drop-debian-subdirectory-from-cmake.patch
dpkg-source: info: applying Move-gconf-schemas-into-usr-share-gconf-schemas.patch
dpkg-source: info: applying Fix-assert-fail-when-no-vorbis-players-are-available.patch
dpkg-source: info: applying Handle-default-player-not-being-in-app-list.patch

Check disk space
----------------

Sufficient free space for build

+------------------------------------------------------------------------------+
| Starting Timed Build Commands                                                |
+------------------------------------------------------------------------------+


ulimit -c
---------

0

I: Finished running 'ulimit -c'.

Finished processing commands.
--------------------------------------------------------------------------------

User Environment
----------------

APT_CONFIG=/var/lib/sbuild/apt.conf
CONFIG_SITE=/etc/dpkg-cross/cross-config.i386
DEB_BUILD_OPTIONS=nocheck
HOME=/sbuild-nonexistent
LANG=en_GB.UTF-8
LC_ALL=C.UTF-8
LOGNAME=helmutg
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=crossqa-sid
SCHROOT_CHROOT_NAME=crossqa-sid
SCHROOT_COMMAND=env
SCHROOT_GID=1002
SCHROOT_GROUP=helmutg
SCHROOT_SESSION_ID=crossqa-sid-b7bad164-852d-4afd-988a-fd41d73c56b9
SCHROOT_UID=1002
SCHROOT_USER=helmutg
SHELL=/bin/sh
USER=helmutg

dpkg-buildpackage
-----------------

Command: dpkg-buildpackage -ai386 -Pcross,nocheck -us -uc -B -rfakeroot --jobs-try=1
dpkg-buildpackage: info: source package alarm-clock-applet
dpkg-buildpackage: info: source version 0.4.1-3
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Chow Loong Jin <hyperair@debian.org>
dpkg-architecture: warning: specified GNU system type i686-linux-gnu does not match CC system type aarch64-linux-gnu, try setting a correct CC environment variable
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture i386
 fakeroot debian/rules clean
dh clean
   dh_clean
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
	cd obj-i686-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_SYSTEM_NAME=Linux -DCMAKE_SYSTEM_PROCESSOR=i686 -DCMAKE_C_COMPILER=i686-linux-gnu-gcc -DCMAKE_CXX_COMPILER=i686-linux-gnu-g\+\+ -DPKG_CONFIG_EXECUTABLE=/usr/bin/i686-linux-gnu-pkg-config -DPKGCONFIG_EXECUTABLE=/usr/bin/i686-linux-gnu-pkg-config -DQMAKE_EXECUTABLE=/usr/bin/i686-linux-gnu-qmake -DCMAKE_INSTALL_LIBDIR=lib/i386-linux-gnu ..
-- The C compiler identification is GNU 12.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/i686-linux-gnu-gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Found PkgConfig: /usr/bin/i686-linux-gnu-pkg-config (found version "1.8.1") 
-- Found Gettext: /usr/bin/msgmerge (found version "0.21") 
-- Checking for module 'gio-2.0'
--   Found gio-2.0, version 2.74.6
-- Checking for module 'gconf-2.0'
--   Found gconf-2.0, version 3.2.6
-- Checking for module 'gtk+-3.0'
--   Found gtk+-3.0, version 3.24.36
-- Checking for module 'gstreamer-1.0'
--   Found gstreamer-1.0, version 1.22.0
-- Checking for module 'libnotify'
--   Found libnotify, version 0.8.1
-- Checking for module 'ayatana-appindicator3-0.1'
--   Found ayatana-appindicator3-0.1, version 0.5.90
-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

    CMAKE_CXX_COMPILER
    CMAKE_EXPORT_NO_PACKAGE_REGISTRY
    CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY
    FETCHCONTENT_FULLY_DISCONNECTED
    PKGCONFIG_EXECUTABLE
    QMAKE_EXECUTABLE


-- Build files have been written to: /<<PKGBUILDDIR>>/obj-i686-linux-gnu
   dh_auto_build -a
	cd obj-i686-linux-gnu && make -j1 "INSTALL=install --strip-program=true" VERBOSE=1
make[1]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
/usr/bin/cmake -S/<<PKGBUILDDIR>> -B/<<PKGBUILDDIR>>/obj-i686-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /<<PKGBUILDDIR>>/obj-i686-linux-gnu/CMakeFiles /<<PKGBUILDDIR>>/obj-i686-linux-gnu//CMakeFiles/progress.marks
make  -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make  -f gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/build.make gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/depend
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/gconf-migration /<<PKGBUILDDIR>>/obj-i686-linux-gnu /<<PKGBUILDDIR>>/obj-i686-linux-gnu/gconf-migration /<<PKGBUILDDIR>>/obj-i686-linux-gnu/gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/DependInfo.cmake --color=
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make  -f gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/build.make gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/build
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
[  1%] Building C object gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/alarm-clock-gconf-migration.c.o
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/gconf-migration && /usr/bin/i686-linux-gnu-gcc  -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu -I/usr/include/gconf/2 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include -I/usr/include/libmount -I/usr/include/blkid -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu11 -MD -MT gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/alarm-clock-gconf-migration.c.o -MF CMakeFiles/alarm-clock-applet-gconf-migration.dir/alarm-clock-gconf-migration.c.o.d -o CMakeFiles/alarm-clock-applet-gconf-migration.dir/alarm-clock-gconf-migration.c.o -c /<<PKGBUILDDIR>>/gconf-migration/alarm-clock-gconf-migration.c
[  3%] Linking C executable alarm-clock-applet-gconf-migration
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/gconf-migration && /usr/bin/cmake -E cmake_link_script CMakeFiles/alarm-clock-applet-gconf-migration.dir/link.txt --verbose=1
/usr/bin/i686-linux-gnu-gcc -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,--as-needed -Wl,-z,defs "CMakeFiles/alarm-clock-applet-gconf-migration.dir/alarm-clock-gconf-migration.c.o" -o alarm-clock-applet-gconf-migration  -lgconf-2 -lglib-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lgio-2.0 -lgobject-2.0 
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
[  3%] Built target alarm-clock-applet-gconf-migration
make  -f po/CMakeFiles/translations_1.dir/build.make po/CMakeFiles/translations_1.dir/depend
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/po /<<PKGBUILDDIR>>/obj-i686-linux-gnu /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/CMakeFiles/translations_1.dir/DependInfo.cmake --color=
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make  -f po/CMakeFiles/translations_1.dir/build.make po/CMakeFiles/translations_1.dir/build
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
[  5%] Generating ar.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/ar.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/ar.gmo /<<PKGBUILDDIR>>/po/ar.po
[  6%] Generating ast.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/ast.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/ast.gmo /<<PKGBUILDDIR>>/po/ast.po
[  8%] Generating be.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/be.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/be.gmo /<<PKGBUILDDIR>>/po/be.po
[ 10%] Generating bg.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/bg.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/bg.gmo /<<PKGBUILDDIR>>/po/bg.po
[ 11%] Generating ca.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/ca.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/ca.gmo /<<PKGBUILDDIR>>/po/ca.po
[ 13%] Generating cs.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/cs.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/cs.gmo /<<PKGBUILDDIR>>/po/cs.po
[ 15%] Generating da.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/da.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/da.gmo /<<PKGBUILDDIR>>/po/da.po
[ 16%] Generating de.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/de.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/de.gmo /<<PKGBUILDDIR>>/po/de.po
[ 18%] Generating el.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/el.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/el.gmo /<<PKGBUILDDIR>>/po/el.po
[ 20%] Generating es.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/es.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/es.gmo /<<PKGBUILDDIR>>/po/es.po
[ 22%] Generating et.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/et.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/et.gmo /<<PKGBUILDDIR>>/po/et.po
[ 23%] Generating fi.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/fi.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/fi.gmo /<<PKGBUILDDIR>>/po/fi.po
[ 25%] Generating fo.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/fo.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/fo.gmo /<<PKGBUILDDIR>>/po/fo.po
[ 27%] Generating fr.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/fr.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/fr.gmo /<<PKGBUILDDIR>>/po/fr.po
[ 28%] Generating gl.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/gl.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/gl.gmo /<<PKGBUILDDIR>>/po/gl.po
[ 30%] Generating he.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/he.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/he.gmo /<<PKGBUILDDIR>>/po/he.po
[ 32%] Generating hi.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/hi.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/hi.gmo /<<PKGBUILDDIR>>/po/hi.po
[ 33%] Generating hu.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/hu.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/hu.gmo /<<PKGBUILDDIR>>/po/hu.po
[ 35%] Generating id.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/id.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/id.gmo /<<PKGBUILDDIR>>/po/id.po
[ 37%] Generating it.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/it.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/it.gmo /<<PKGBUILDDIR>>/po/it.po
[ 38%] Generating ja.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/ja.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/ja.gmo /<<PKGBUILDDIR>>/po/ja.po
[ 40%] Generating ka.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/ka.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/ka.gmo /<<PKGBUILDDIR>>/po/ka.po
[ 42%] Generating la.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/la.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/la.gmo /<<PKGBUILDDIR>>/po/la.po
[ 44%] Generating ms.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/ms.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/ms.gmo /<<PKGBUILDDIR>>/po/ms.po
[ 45%] Generating nb.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/nb.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/nb.gmo /<<PKGBUILDDIR>>/po/nb.po
[ 47%] Generating nl.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/nl.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/nl.gmo /<<PKGBUILDDIR>>/po/nl.po
[ 49%] Generating nn.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/nn.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/nn.gmo /<<PKGBUILDDIR>>/po/nn.po
[ 50%] Generating pl.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/pl.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/pl.gmo /<<PKGBUILDDIR>>/po/pl.po
[ 52%] Generating pt_BR.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/pt_BR.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/pt_BR.gmo /<<PKGBUILDDIR>>/po/pt_BR.po
[ 54%] Generating pt.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/pt.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/pt.gmo /<<PKGBUILDDIR>>/po/pt.po
[ 55%] Generating ru.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/ru.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/ru.gmo /<<PKGBUILDDIR>>/po/ru.po
[ 57%] Generating si.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/si.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/si.gmo /<<PKGBUILDDIR>>/po/si.po
[ 59%] Generating sv.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/sv.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/sv.gmo /<<PKGBUILDDIR>>/po/sv.po
[ 61%] Generating tr.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/tr.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/tr.gmo /<<PKGBUILDDIR>>/po/tr.po
[ 62%] Generating uk.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/uk.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/uk.gmo /<<PKGBUILDDIR>>/po/uk.po
[ 64%] Generating zh_CN.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/zh_CN.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/zh_CN.gmo /<<PKGBUILDDIR>>/po/zh_CN.po
[ 66%] Generating zh_TW.gmo
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgmerge --quiet --update --backup=none -s /<<PKGBUILDDIR>>/po/zh_TW.po /<<PKGBUILDDIR>>/po/alarm-clock-applet.pot
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po && /usr/bin/msgfmt -o /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/zh_TW.gmo /<<PKGBUILDDIR>>/po/zh_TW.po
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
[ 66%] Built target translations_1
make  -f po/CMakeFiles/linguas.dir/build.make po/CMakeFiles/linguas.dir/depend
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/po /<<PKGBUILDDIR>>/obj-i686-linux-gnu /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/CMakeFiles/linguas.dir/DependInfo.cmake --color=
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make  -f po/CMakeFiles/linguas.dir/build.make po/CMakeFiles/linguas.dir/build
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make[3]: Nothing to be done for 'po/CMakeFiles/linguas.dir/build'.
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
[ 66%] Built target linguas
make  -f po/CMakeFiles/translations.dir/build.make po/CMakeFiles/translations.dir/depend
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/po /<<PKGBUILDDIR>>/obj-i686-linux-gnu /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/CMakeFiles/translations.dir/DependInfo.cmake --color=
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make  -f po/CMakeFiles/translations.dir/build.make po/CMakeFiles/translations.dir/build
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make[3]: Nothing to be done for 'po/CMakeFiles/translations.dir/build'.
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
[ 66%] Built target translations
make  -f src/CMakeFiles/alarm-clock-applet.dir/build.make src/CMakeFiles/alarm-clock-applet.dir/depend
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
[ 67%] Generating io.github.alarm-clock-applet.enums.gschema.xml
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/glib-mkenums --comments "<!-- @comment@ -->" --fhead "<schemalist>" --vhead "  <@type@ id=\"io.github.alarm-clock-applet.@EnumName@\">" --vprod "    <value nick=\"@valuenick@\" value=\"@valuenum@\"/>" --vtail "  </@type@>" --ftail "</schemalist>" /<<PKGBUILDDIR>>/src/alarm-enums.h --output io.github.alarm-clock-applet.enums.gschema.xml
[ 69%] Generating alarm-clock-applet.desktop
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/msgfmt --desktop --template /<<PKGBUILDDIR>>/data/alarm-clock-applet.desktop.in --output alarm-clock-applet.desktop -d /<<PKGBUILDDIR>>/po/
[ 71%] Generating alarm-glib-enums.c
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/glib-mkenums --template /<<PKGBUILDDIR>>/src/alarm-glib-enums.c.etemplate --output alarm-glib-enums.c /<<PKGBUILDDIR>>/src/alarm-enums.h
[ 72%] Generating alarm-glib-enums.h
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/glib-mkenums --template /<<PKGBUILDDIR>>/src/alarm-glib-enums.h.etemplate --output alarm-glib-enums.h /<<PKGBUILDDIR>>/src/alarm-enums.h
[ 74%] Generating autostart/alarm-clock-applet.desktop
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src/autostart && /usr/bin/msgfmt --desktop --template /<<PKGBUILDDIR>>/data/alarm-clock-applet_autostart.desktop.in --output alarm-clock-applet.desktop -d /<<PKGBUILDDIR>>/po/
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/src /<<PKGBUILDDIR>>/obj-i686-linux-gnu /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src/CMakeFiles/alarm-clock-applet.dir/DependInfo.cmake --color=
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make  -f src/CMakeFiles/alarm-clock-applet.dir/build.make src/CMakeFiles/alarm-clock-applet.dir/build
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
[ 76%] Building C object src/CMakeFiles/alarm-clock-applet.dir/alarm-applet.c.o
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/i686-linux-gnu-gcc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu/src -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/alarm-applet.c.o -MF CMakeFiles/alarm-clock-applet.dir/alarm-applet.c.o.d -o CMakeFiles/alarm-clock-applet.dir/alarm-applet.c.o -c /<<PKGBUILDDIR>>/src/alarm-applet.c
[ 77%] Building C object src/CMakeFiles/alarm-clock-applet.dir/player.c.o
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/i686-linux-gnu-gcc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu/src -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/player.c.o -MF CMakeFiles/alarm-clock-applet.dir/player.c.o.d -o CMakeFiles/alarm-clock-applet.dir/player.c.o -c /<<PKGBUILDDIR>>/src/player.c
[ 79%] Building C object src/CMakeFiles/alarm-clock-applet.dir/util.c.o
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/i686-linux-gnu-gcc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu/src -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/util.c.o -MF CMakeFiles/alarm-clock-applet.dir/util.c.o.d -o CMakeFiles/alarm-clock-applet.dir/util.c.o -c /<<PKGBUILDDIR>>/src/util.c
[ 81%] Building C object src/CMakeFiles/alarm-clock-applet.dir/list-entry.c.o
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/i686-linux-gnu-gcc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu/src -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/list-entry.c.o -MF CMakeFiles/alarm-clock-applet.dir/list-entry.c.o.d -o CMakeFiles/alarm-clock-applet.dir/list-entry.c.o -c /<<PKGBUILDDIR>>/src/list-entry.c
[ 83%] Building C object src/CMakeFiles/alarm-clock-applet.dir/alarm.c.o
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/i686-linux-gnu-gcc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu/src -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/alarm.c.o -MF CMakeFiles/alarm-clock-applet.dir/alarm.c.o.d -o CMakeFiles/alarm-clock-applet.dir/alarm.c.o -c /<<PKGBUILDDIR>>/src/alarm.c
[ 84%] Building C object src/CMakeFiles/alarm-clock-applet.dir/alarm-gsettings.c.o
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/i686-linux-gnu-gcc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu/src -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/alarm-gsettings.c.o -MF CMakeFiles/alarm-clock-applet.dir/alarm-gsettings.c.o.d -o CMakeFiles/alarm-clock-applet.dir/alarm-gsettings.c.o -c /<<PKGBUILDDIR>>/src/alarm-gsettings.c
[ 86%] Building C object src/CMakeFiles/alarm-clock-applet.dir/ui.c.o
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/i686-linux-gnu-gcc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu/src -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/ui.c.o -MF CMakeFiles/alarm-clock-applet.dir/ui.c.o.d -o CMakeFiles/alarm-clock-applet.dir/ui.c.o -c /<<PKGBUILDDIR>>/src/ui.c
[ 88%] Building C object src/CMakeFiles/alarm-clock-applet.dir/alarm-actions.c.o
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/i686-linux-gnu-gcc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu/src -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/alarm-actions.c.o -MF CMakeFiles/alarm-clock-applet.dir/alarm-actions.c.o.d -o CMakeFiles/alarm-clock-applet.dir/alarm-actions.c.o -c /<<PKGBUILDDIR>>/src/alarm-actions.c
[ 89%] Building C object src/CMakeFiles/alarm-clock-applet.dir/alarm-list-window.c.o
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/i686-linux-gnu-gcc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu/src -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/alarm-list-window.c.o -MF CMakeFiles/alarm-clock-applet.dir/alarm-list-window.c.o.d -o CMakeFiles/alarm-clock-applet.dir/alarm-list-window.c.o -c /<<PKGBUILDDIR>>/src/alarm-list-window.c
[ 91%] Building C object src/CMakeFiles/alarm-clock-applet.dir/alarm-settings.c.o
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/i686-linux-gnu-gcc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu/src -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/alarm-settings.c.o -MF CMakeFiles/alarm-clock-applet.dir/alarm-settings.c.o.d -o CMakeFiles/alarm-clock-applet.dir/alarm-settings.c.o -c /<<PKGBUILDDIR>>/src/alarm-settings.c
[ 93%] Building C object src/CMakeFiles/alarm-clock-applet.dir/prefs.c.o
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/i686-linux-gnu-gcc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu/src -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/prefs.c.o -MF CMakeFiles/alarm-clock-applet.dir/prefs.c.o.d -o CMakeFiles/alarm-clock-applet.dir/prefs.c.o -c /<<PKGBUILDDIR>>/src/prefs.c
[ 94%] Building C object src/CMakeFiles/alarm-clock-applet.dir/alarm-glib-enums.c.o
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/i686-linux-gnu-gcc -DG_LOG_DOMAIN=\"alarm-clock-applet\" -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include -I/usr/include/gstreamer-1.0 -I/usr/include/libayatana-appindicator3-0.1 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libdbusmenu-glib-0.4 -I/<<PKGBUILDDIR>>/obj-i686-linux-gnu/src -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wshadow -Werror=return-type -pthread -std=gnu11 -MD -MT src/CMakeFiles/alarm-clock-applet.dir/alarm-glib-enums.c.o -MF CMakeFiles/alarm-clock-applet.dir/alarm-glib-enums.c.o.d -o CMakeFiles/alarm-clock-applet.dir/alarm-glib-enums.c.o -c /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src/alarm-glib-enums.c
[ 96%] Linking C executable alarm-clock-applet
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/alarm-clock-applet.dir/link.txt --verbose=1
/usr/bin/i686-linux-gnu-gcc -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,--as-needed -Wl,-z,defs -rdynamic "CMakeFiles/alarm-clock-applet.dir/alarm-applet.c.o" "CMakeFiles/alarm-clock-applet.dir/player.c.o" "CMakeFiles/alarm-clock-applet.dir/util.c.o" "CMakeFiles/alarm-clock-applet.dir/list-entry.c.o" "CMakeFiles/alarm-clock-applet.dir/alarm.c.o" "CMakeFiles/alarm-clock-applet.dir/alarm-gsettings.c.o" "CMakeFiles/alarm-clock-applet.dir/ui.c.o" "CMakeFiles/alarm-clock-applet.dir/alarm-actions.c.o" "CMakeFiles/alarm-clock-applet.dir/alarm-list-window.c.o" "CMakeFiles/alarm-clock-applet.dir/alarm-settings.c.o" "CMakeFiles/alarm-clock-applet.dir/prefs.c.o" "CMakeFiles/alarm-clock-applet.dir/alarm-glib-enums.c.o" -o alarm-clock-applet  -lgtk-3 -lgdk-3 -lz -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lnotify -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -layatana-appindicator3 -layatana-indicator3 -layatana-ido3-0.4 -ldbusmenu-glib -lgtk-3 -lgdk-3 -lz -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lgstreamer-1.0 -lnotify -layatana-appindicator3 -layatana-indicator3 -layatana-ido3-0.4 -ldbusmenu-glib 
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
[ 96%] Built target alarm-clock-applet
make  -f src/CMakeFiles/man-alarm-clock-applet.dir/build.make src/CMakeFiles/man-alarm-clock-applet.dir/depend
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/src /<<PKGBUILDDIR>>/obj-i686-linux-gnu /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src/CMakeFiles/man-alarm-clock-applet.dir/DependInfo.cmake --color=
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make  -f src/CMakeFiles/man-alarm-clock-applet.dir/build.make src/CMakeFiles/man-alarm-clock-applet.dir/build
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
[ 98%] Generating alarm-clock-applet.1
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/pod2man --utf8 --section="1" --center="General\ Commands\ Manual" --release="0.4.1" --name="ALARM-CLOCK-APPLET" /<<PKGBUILDDIR>>/src/alarm-clock-applet.pod /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src/alarm-clock-applet.1
[100%] Generating alarm-clock-applet.1.gz
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src && /usr/bin/gzip -f -k --best -n /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src/alarm-clock-applet.1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
[100%] Built target man-alarm-clock-applet
make[2]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
/usr/bin/cmake -E cmake_progress_start /<<PKGBUILDDIR>>/obj-i686-linux-gnu/CMakeFiles 0
make[1]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-arch
dh binary-arch
   dh_testroot -a
   dh_prep -a
   dh_auto_install -a
	cd obj-i686-linux-gnu && make -j1 install DESTDIR=/<<PKGBUILDDIR>>/debian/tmp AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
/usr/bin/cmake -S/<<PKGBUILDDIR>> -B/<<PKGBUILDDIR>>/obj-i686-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start /<<PKGBUILDDIR>>/obj-i686-linux-gnu/CMakeFiles /<<PKGBUILDDIR>>/obj-i686-linux-gnu//CMakeFiles/progress.marks
make  -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make  -f gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/build.make gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/depend
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/gconf-migration /<<PKGBUILDDIR>>/obj-i686-linux-gnu /<<PKGBUILDDIR>>/obj-i686-linux-gnu/gconf-migration /<<PKGBUILDDIR>>/obj-i686-linux-gnu/gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/DependInfo.cmake --color=
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make  -f gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/build.make gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/build
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make[3]: Nothing to be done for 'gconf-migration/CMakeFiles/alarm-clock-applet-gconf-migration.dir/build'.
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
[  3%] Built target alarm-clock-applet-gconf-migration
make  -f po/CMakeFiles/translations_1.dir/build.make po/CMakeFiles/translations_1.dir/depend
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/po /<<PKGBUILDDIR>>/obj-i686-linux-gnu /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/CMakeFiles/translations_1.dir/DependInfo.cmake --color=
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make  -f po/CMakeFiles/translations_1.dir/build.make po/CMakeFiles/translations_1.dir/build
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make[3]: Nothing to be done for 'po/CMakeFiles/translations_1.dir/build'.
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
[ 66%] Built target translations_1
make  -f po/CMakeFiles/linguas.dir/build.make po/CMakeFiles/linguas.dir/depend
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/po /<<PKGBUILDDIR>>/obj-i686-linux-gnu /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/CMakeFiles/linguas.dir/DependInfo.cmake --color=
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make  -f po/CMakeFiles/linguas.dir/build.make po/CMakeFiles/linguas.dir/build
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make[3]: Nothing to be done for 'po/CMakeFiles/linguas.dir/build'.
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
[ 66%] Built target linguas
make  -f po/CMakeFiles/translations.dir/build.make po/CMakeFiles/translations.dir/depend
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/po /<<PKGBUILDDIR>>/obj-i686-linux-gnu /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po /<<PKGBUILDDIR>>/obj-i686-linux-gnu/po/CMakeFiles/translations.dir/DependInfo.cmake --color=
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make  -f po/CMakeFiles/translations.dir/build.make po/CMakeFiles/translations.dir/build
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make[3]: Nothing to be done for 'po/CMakeFiles/translations.dir/build'.
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
[ 66%] Built target translations
make  -f src/CMakeFiles/alarm-clock-applet.dir/build.make src/CMakeFiles/alarm-clock-applet.dir/depend
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/src /<<PKGBUILDDIR>>/obj-i686-linux-gnu /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src/CMakeFiles/alarm-clock-applet.dir/DependInfo.cmake --color=
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make  -f src/CMakeFiles/alarm-clock-applet.dir/build.make src/CMakeFiles/alarm-clock-applet.dir/build
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make[3]: Nothing to be done for 'src/CMakeFiles/alarm-clock-applet.dir/build'.
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
[ 96%] Built target alarm-clock-applet
make  -f src/CMakeFiles/man-alarm-clock-applet.dir/build.make src/CMakeFiles/man-alarm-clock-applet.dir/depend
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
cd /<<PKGBUILDDIR>>/obj-i686-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<<PKGBUILDDIR>> /<<PKGBUILDDIR>>/src /<<PKGBUILDDIR>>/obj-i686-linux-gnu /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src /<<PKGBUILDDIR>>/obj-i686-linux-gnu/src/CMakeFiles/man-alarm-clock-applet.dir/DependInfo.cmake --color=
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make  -f src/CMakeFiles/man-alarm-clock-applet.dir/build.make src/CMakeFiles/man-alarm-clock-applet.dir/build
make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make[3]: Nothing to be done for 'src/CMakeFiles/man-alarm-clock-applet.dir/build'.
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
[100%] Built target man-alarm-clock-applet
make[2]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
/usr/bin/cmake -E cmake_progress_start /<<PKGBUILDDIR>>/obj-i686-linux-gnu/CMakeFiles 0
make  -f CMakeFiles/Makefile2 preinstall
make[2]: Entering directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
make[2]: Nothing to be done for 'preinstall'.
make[2]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
Install the project...
/usr/bin/cmake -P cmake_install.cmake
-- Install configuration: "None"
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/bin/alarm-clock-applet-gconf-migration
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/gconf/schemas/alarm-clock.schemas

(gconftool-2:22873): GConf-WARNING **: 11:07:58.872: Client failed to connect to the D-BUS daemon:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Attached schema `/schemas/apps/alarm-clock/show_label' to key `/apps/alarm-clock/show_label'
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `sv': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `zh_TW': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `tr': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `si': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `ast': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `uk': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `ka': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `nl': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/show_label', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/show_label', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `ka': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `si': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `uk': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `sv': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `ca': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `ast': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `ar': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `tr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `cs': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `fi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `et': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `nl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/type', locale `zh_TW': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `ka': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `si': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `uk': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `sv': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `ca': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `ast': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `ar': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `tr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `fi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `nl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/timestamp', locale `zh_TW': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/timestamp', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `ka': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `si': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `uk': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `sv': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `ca': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `ast': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `ar': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `tr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `cs': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `fi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `nl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/time', locale `zh_TW': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/time', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `ka': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `si': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `uk': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `sv': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `ca': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `ast': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `ar': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `tr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `cs': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `fi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `et': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `nl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/message', locale `zh_TW': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/message', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `ka': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `si': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `uk': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `sv': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `ca': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `ast': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `ar': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `tr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `fi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `nl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/active', locale `zh_TW': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/active', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `ka': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `si': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `uk': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `sv': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `ca': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `ast': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `ar': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `tr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `cs': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `fi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `nl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/repeat', locale `zh_TW': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `ka': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `si': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `uk': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `sv': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `ca': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `ast': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `ar': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `tr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `cs': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `fi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `nl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/notify_type', locale `zh_TW': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/notify_type', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `ka': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `si': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `uk': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `sv': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `ca': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `ast': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `ar': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `tr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `cs': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `fi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `et': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `nl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_file', locale `zh_TW': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_file', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `ka': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `si': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `uk': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `sv': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `ca': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `ast': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `ar': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `tr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `cs': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `fi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `nl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/sound_repeat', locale `zh_TW': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/sound_repeat', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `he': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `ka': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `nb': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `si': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `pt_BR': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `de': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `ja': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `ms': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `be': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `pt': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `nn': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `zh_CN': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `gl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `ru': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `fr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `C': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `da': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `uk': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `sv': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `ca': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `ast': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `bg': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `es': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `ar': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `hi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `tr': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `cs': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `id': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `fi': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `et': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `pl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `hu': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `fo': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `nl': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
WARNING: failed to install schema `/schemas/apps/alarm-clock/alarm/command', locale `zh_TW': Unable to store a value at key '/schemas/apps/alarm-clock/alarm/command', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/ar/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/ast/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/be/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/bg/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/ca/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/cs/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/da/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/de/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/el/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/es/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/et/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/fi/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/fo/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/fr/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/gl/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/he/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/hi/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/hu/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/id/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/it/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/ja/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/ka/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/la/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/ms/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/nb/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/nl/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/nn/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/pl/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/pt_BR/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/pt/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/ru/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/si/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/sv/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/tr/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/uk/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/zh_CN/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/locale/zh_TW/LC_MESSAGES/alarm-clock-applet.mo
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/bin/alarm-clock-applet
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/alarm-clock-applet/alarm-clock.ui
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/alarm-clock-applet/alarm-clock.css
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/applications/alarm-clock-applet.desktop
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/etc/xdg/autostart/alarm-clock-applet.desktop
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/glib-2.0/schemas/io.github.alarm-clock-applet.gschema.xml
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/glib-2.0/schemas/io.github.alarm-clock-applet.enums.gschema.xml
Failed to create file “/usr/share/glib-2.0/schemas/gschemas.compiled.UWGH11”: Permission denied
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/64x64
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/64x64/apps
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/64x64/apps/alarm-timer.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/64x64/apps/alarm-clock-triggered.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/64x64/apps/alarm-clock.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/scalable
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/scalable/apps
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/scalable/apps/alarm-timer.svg
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/scalable/apps/alarm-clock-triggered.svg
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/scalable/apps/alarm-clock.svg
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/36x36
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/36x36/apps
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/36x36/apps/alarm-timer.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/36x36/apps/alarm-clock-triggered.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/36x36/apps/alarm-clock.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/24x24
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/24x24/apps
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/24x24/apps/alarm-timer.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/24x24/apps/alarm-clock-triggered.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/24x24/apps/alarm-clock.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/22x22
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/22x22/apps
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/22x22/apps/alarm-timer.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/22x22/apps/alarm-clock-triggered.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/22x22/apps/alarm-clock.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/16x16
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/16x16/apps
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/16x16/apps/alarm-timer.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/16x16/apps/alarm-clock-triggered.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/16x16/apps/alarm-clock.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/48x48
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/48x48/apps
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/48x48/apps/alarm-timer.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/48x48/apps/alarm-clock-triggered.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/48x48/apps/alarm-clock.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/32x32
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/32x32/apps
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/32x32/apps/alarm-timer.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/32x32/apps/alarm-clock-triggered.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/icons/hicolor/32x32/apps/alarm-clock.png
-- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/share/man/man1/alarm-clock-applet.1.gz
make[1]: Leaving directory '/<<PKGBUILDDIR>>/obj-i686-linux-gnu'
   dh_install -a
   dh_installdocs -a
   debian/rules override_dh_installchangelogs
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_installchangelogs ChangeLog
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_installman -a
   dh_installgsettings -a
   dh_icons -a
   dh_perl -a
   dh_link -a
   dh_strip_nondeterminism -a
	Normalized debian/alarm-clock-applet/usr/share/locale/ja/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/ka/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/nb/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/it/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/fr/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/uk/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/be/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/pt/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/id/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/ast/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/cs/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/fo/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/el/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/nn/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/pt_BR/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/bg/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/gl/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/zh_CN/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/tr/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/ru/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/la/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/de/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/si/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/ar/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/pl/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/hi/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/hu/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/es/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/sv/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/ca/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/zh_TW/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/da/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/nl/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/fi/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/et/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/ms/LC_MESSAGES/alarm-clock-applet.mo
	Normalized debian/alarm-clock-applet/usr/share/locale/he/LC_MESSAGES/alarm-clock-applet.mo
   dh_compress -a
   dh_fixperms -a
   dh_missing -a
   dh_dwz -a
   dh_strip -a
   dh_makeshlibs -a
   dh_shlibdeps -a
   dh_installdeb -a
   dh_gencontrol -a
   dh_md5sums -a
   dh_builddeb -a
dpkg-deb: building package 'alarm-clock-applet' in '../alarm-clock-applet_0.4.1-3_i386.deb'.
dpkg-deb: building package 'alarm-clock-applet-dbgsym' in '../alarm-clock-applet-dbgsym_0.4.1-3_i386.deb'.
dpkg-deb: building package 'alarm-clock-applet-gconf-migration' in '../alarm-clock-applet-gconf-migration_0.4.1-3_i386.deb'.
dpkg-deb: building package 'alarm-clock-applet-gconf-migration-dbgsym' in '../alarm-clock-applet-gconf-migration-dbgsym_0.4.1-3_i386.deb'.
 dpkg-genbuildinfo --build=any -O../alarm-clock-applet_0.4.1-3_i386.buildinfo
 dpkg-genchanges --build=any -O../alarm-clock-applet_0.4.1-3_i386.changes
dpkg-genchanges: info: binary-only arch-specific upload (source code and arch-indep packages not included)
 dpkg-source --after-build .
dpkg-buildpackage: info: binary-only upload (no source included)
--------------------------------------------------------------------------------
Build finished at 2023-03-08T11:08:16Z

Finished
--------

I: Built successfully

+------------------------------------------------------------------------------+
| Changes                                                                      |
+------------------------------------------------------------------------------+


alarm-clock-applet_0.4.1-3_i386.changes:
----------------------------------------

Format: 1.8
Date: Wed, 15 Feb 2023 20:56:06 +0800
Source: alarm-clock-applet
Binary: alarm-clock-applet alarm-clock-applet-dbgsym alarm-clock-applet-gconf-migration alarm-clock-applet-gconf-migration-dbgsym
Built-For-Profiles: cross nocheck
Architecture: i386
Version: 0.4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Chow Loong Jin <hyperair@debian.org>
Changed-By: Chow Loong Jin <hyperair@debian.org>
Description:
 alarm-clock-applet - alarm clock panel indicator
 alarm-clock-applet-gconf-migration - alarm clock panel indicator - gconf migration
Changes:
 alarm-clock-applet (0.4.1-3) unstable; urgency=medium
 .
   * [03c7bb1] Add suggests: playerctl
Checksums-Sha1:
 a6172f459d6c32dba4d02c399804ae0ca43818c0 90424 alarm-clock-applet-dbgsym_0.4.1-3_i386.deb
 940794a83ed406d77db603b4aa8716078de000e0 7928 alarm-clock-applet-gconf-migration-dbgsym_0.4.1-3_i386.deb
 ff815647c60f0b14bc61c8af5ad04a7be38317b5 22656 alarm-clock-applet-gconf-migration_0.4.1-3_i386.deb
 b36892944850ec0dc63046df83f5737b52164511 16420 alarm-clock-applet_0.4.1-3_i386.buildinfo
 5461f65ddeac73914a1da0e44f97f471b3cf6677 136140 alarm-clock-applet_0.4.1-3_i386.deb
Checksums-Sha256:
 d85d346b5b3c4b5feb27fbf64b6d718bf6cf2aa2d375011cfe1709d937f09501 90424 alarm-clock-applet-dbgsym_0.4.1-3_i386.deb
 bbd0f101235154778dcebd94dd7e203e38861c8db9aeb5d1b4de1d4110696c49 7928 alarm-clock-applet-gconf-migration-dbgsym_0.4.1-3_i386.deb
 bb29f64002b1b5cd94344843fb16f630b751d81a2b1badcd487e3d6bb9c32e14 22656 alarm-clock-applet-gconf-migration_0.4.1-3_i386.deb
 462f9eb0f2bd195741c846e21c8562814a43ddda81dc5cb022f2a6fb87e3971c 16420 alarm-clock-applet_0.4.1-3_i386.buildinfo
 3fdf1074024d0b63c4e5f98b1c0eb5e06413c8b1e191c2aebc739c90a425435c 136140 alarm-clock-applet_0.4.1-3_i386.deb
Files:
 d97489ee82ebece871abd3c091e567e9 90424 debug optional alarm-clock-applet-dbgsym_0.4.1-3_i386.deb
 6a0ae31847a678328b077e7f8df3c8ce 7928 debug optional alarm-clock-applet-gconf-migration-dbgsym_0.4.1-3_i386.deb
 75e97b0971253c83ff62cbe9ba340c1d 22656 gnome optional alarm-clock-applet-gconf-migration_0.4.1-3_i386.deb
 571e67e9cf871cb4c6f0f1e39407a9c6 16420 gnome optional alarm-clock-applet_0.4.1-3_i386.buildinfo
 2a7ad3437ff1a6228a4d8b032f564228 136140 gnome optional alarm-clock-applet_0.4.1-3_i386.deb

+------------------------------------------------------------------------------+
| Buildinfo                                                                    |
+------------------------------------------------------------------------------+

Format: 1.0
Source: alarm-clock-applet
Binary: alarm-clock-applet alarm-clock-applet-dbgsym alarm-clock-applet-gconf-migration alarm-clock-applet-gconf-migration-dbgsym
Architecture: i386
Version: 0.4.1-3
Checksums-Md5:
 d97489ee82ebece871abd3c091e567e9 90424 alarm-clock-applet-dbgsym_0.4.1-3_i386.deb
 6a0ae31847a678328b077e7f8df3c8ce 7928 alarm-clock-applet-gconf-migration-dbgsym_0.4.1-3_i386.deb
 75e97b0971253c83ff62cbe9ba340c1d 22656 alarm-clock-applet-gconf-migration_0.4.1-3_i386.deb
 2a7ad3437ff1a6228a4d8b032f564228 136140 alarm-clock-applet_0.4.1-3_i386.deb
Checksums-Sha1:
 a6172f459d6c32dba4d02c399804ae0ca43818c0 90424 alarm-clock-applet-dbgsym_0.4.1-3_i386.deb
 940794a83ed406d77db603b4aa8716078de000e0 7928 alarm-clock-applet-gconf-migration-dbgsym_0.4.1-3_i386.deb
 ff815647c60f0b14bc61c8af5ad04a7be38317b5 22656 alarm-clock-applet-gconf-migration_0.4.1-3_i386.deb
 5461f65ddeac73914a1da0e44f97f471b3cf6677 136140 alarm-clock-applet_0.4.1-3_i386.deb
Checksums-Sha256:
 d85d346b5b3c4b5feb27fbf64b6d718bf6cf2aa2d375011cfe1709d937f09501 90424 alarm-clock-applet-dbgsym_0.4.1-3_i386.deb
 bbd0f101235154778dcebd94dd7e203e38861c8db9aeb5d1b4de1d4110696c49 7928 alarm-clock-applet-gconf-migration-dbgsym_0.4.1-3_i386.deb
 bb29f64002b1b5cd94344843fb16f630b751d81a2b1badcd487e3d6bb9c32e14 22656 alarm-clock-applet-gconf-migration_0.4.1-3_i386.deb
 3fdf1074024d0b63c4e5f98b1c0eb5e06413c8b1e191c2aebc739c90a425435c 136140 alarm-clock-applet_0.4.1-3_i386.deb
Build-Origin: Debian
Build-Architecture: arm64
Build-Date: Wed, 08 Mar 2023 11:08:14 +0000
Build-Path: /<<PKGBUILDDIR>>
Build-Tainted-By:
 merged-usr-via-aliased-dirs
Installed-Build-Depends:
 adduser (= 3.131),
 adwaita-icon-theme (= 43-1),
 at-spi2-common (= 2.46.0-5),
 autoconf (= 2.71-3),
 autoconf-archive (= 20220903-3),
 automake (= 1:1.16.5-1.3),
 autopoint (= 0.21-12),
 autotools-dev (= 20220109.1),
 base-files (= 12.4),
 base-passwd (= 3.6.1),
 bash (= 5.2.15-2+b1),
 binutils (= 2.40-2),
 binutils-aarch64-linux-gnu (= 2.40-2),
 binutils-common (= 2.40-2),
 bsdextrautils (= 2.38.1-5),
 bsdutils (= 1:2.38.1-5),
 build-essential (= 12.9),
 bzip2 (= 1.0.8-5+b1),
 ca-certificates (= 20211016),
 cmake (= 3.25.1-1),
 cmake-data (= 3.25.1-1),
 coreutils (= 9.1-1),
 cpp (= 4:12.2.0-3),
 cpp-12 (= 12.2.0-14),
 dash (= 0.5.12-2),
 dbus (= 1.14.6-1),
 dbus-bin (= 1.14.6-1),
 dbus-daemon (= 1.14.6-1),
 dbus-session-bus-common (= 1.14.6-1),
 dbus-system-bus-common (= 1.14.6-1),
 dbus-user-session (= 1.14.6-1),
 dconf-gsettings-backend (= 0.40.0-4),
 dconf-service (= 0.40.0-4),
 debconf (= 1.5.82),
 debhelper (= 13.11.4),
 debianutils (= 5.7-0.4),
 dh-autoreconf (= 20),
 dh-strip-nondeterminism (= 1.13.1-1),
 diffutils (= 1:3.8-4),
 dmsetup (= 2:1.02.185-2),
 dpkg (= 1.21.21),
 dpkg-dev (= 1.21.21),
 dwz (= 0.15-1),
 file (= 1:5.44-3),
 findutils (= 4.9.0-4),
 fontconfig (= 2.14.1-4),
 fontconfig-config (= 2.14.1-4),
 fonts-dejavu-core (= 2.37-5),
 g++ (= 4:12.2.0-3),
 g++-12 (= 12.2.0-14),
 gcc (= 4:12.2.0-3),
 gcc-12 (= 12.2.0-14),
 gcc-12-base (= 12.2.0-14),
 gconf-service (= 3.2.6-8),
 gconf2 (= 3.2.6-8),
 gconf2-common (= 3.2.6-8),
 gettext (= 0.21-12),
 gettext-base (= 0.21-12),
 gir1.2-atk-1.0 (= 2.46.0-5),
 gir1.2-atspi-2.0 (= 2.46.0-5),
 gir1.2-ayatanaappindicator3-0.1 (= 0.5.92-1),
 gir1.2-ayatanaido3-0.4 (= 0.9.3-1),
 gir1.2-dbusmenu-glib-0.4 (= 18.10.20180917~bzr492+repack1-3),
 gir1.2-freedesktop (= 1.74.0-3),
 gir1.2-gconf-2.0 (= 3.2.6-8),
 gir1.2-gdkpixbuf-2.0 (= 2.42.10+dfsg-1+b1),
 gir1.2-glib-2.0 (= 1.74.0-3),
 gir1.2-gstreamer-1.0 (= 1.22.0-2),
 gir1.2-gtk-2.0 (= 2.24.33-2),
 gir1.2-gtk-3.0 (= 3.24.36-4),
 gir1.2-harfbuzz-0.0 (= 6.0.0+dfsg-3),
 gir1.2-notify-0.7 (= 0.8.1-1),
 gir1.2-pango-1.0 (= 1.50.12+ds-1),
 gnome-common (= 3.18.0-4),
 gnome-icon-theme (= 3.12.0-5),
 grep (= 3.8-5),
 groff-base (= 1.22.4-10),
 gtk-update-icon-cache (= 3.24.36-4),
 gzip (= 1.12-1),
 hicolor-icon-theme (= 0.17-2),
 hostname (= 3.23+nmu1),
 icu-devtools (= 72.1-3),
 init-system-helpers (= 1.65.2),
 intltool (= 0.51.0-6),
 intltool-debian (= 0.35.0+20060710.6),
 libacl1 (= 2.3.1-3),
 libapparmor1 (= 3.0.8-3),
 libarchive-zip-perl (= 1.68-1),
 libarchive13 (= 3.6.2-1),
 libargon2-1 (= 0~20190702-0.1),
 libasan8 (= 12.2.0-14),
 libatk-bridge2.0-0 (= 2.46.0-5),
 libatk-bridge2.0-dev (= 2.46.0-5),
 libatk1.0-0 (= 2.46.0-5),
 libatk1.0-dev (= 2.46.0-5),
 libatomic1 (= 12.2.0-14),
 libatspi2.0-0 (= 2.46.0-5),
 libatspi2.0-dev (= 2.46.0-5),
 libattr1 (= 1:2.5.1-4),
 libaudit-common (= 1:3.0.9-1),
 libaudit1 (= 1:3.0.9-1),
 libavahi-client3 (= 0.8-9),
 libavahi-common-data (= 0.8-9),
 libavahi-common3 (= 0.8-9),
 libayatana-appindicator3-1 (= 0.5.92-1),
 libayatana-appindicator3-dev (= 0.5.92-1),
 libayatana-ido3-0.4-0 (= 0.9.3-1),
 libayatana-ido3-dev (= 0.9.3-1),
 libayatana-indicator3-7 (= 0.9.3-1),
 libayatana-indicator3-dev (= 0.9.3-1),
 libbinutils (= 2.40-2),
 libblkid-dev (= 2.38.1-5),
 libblkid1 (= 2.38.1-5),
 libbrotli-dev (= 1.0.9-2+b6),
 libbrotli1 (= 1.0.9-2+b6),
 libbsd0 (= 0.11.7-4),
 libbz2-1.0 (= 1.0.8-5+b1),
 libc-bin (= 2.36-8),
 libc-dev-bin (= 2.36-8),
 libc6 (= 2.36-8),
 libc6-dev (= 2.36-8),
 libcairo-gobject2 (= 1.16.0-7),
 libcairo-script-interpreter2 (= 1.16.0-7),
 libcairo2 (= 1.16.0-7),
 libcairo2-dev (= 1.16.0-7),
 libcap-ng0 (= 0.8.3-1+b3),
 libcap2 (= 1:2.66-3),
 libcap2-bin (= 1:2.66-3),
 libcc1-0 (= 12.2.0-14),
 libclone-perl (= 0.46-1),
 libcolord2 (= 1.4.6-2.2),
 libcom-err2 (= 1.47.0-2),
 libcrypt-dev (= 1:4.4.33-2),
 libcrypt1 (= 1:4.4.33-2),
 libcryptsetup12 (= 2:2.6.1-2),
 libctf-nobfd0 (= 2.40-2),
 libctf0 (= 2.40-2),
 libcups2 (= 2.4.2-2),
 libcurl4 (= 7.88.1-5),
 libdatrie-dev (= 0.2.13-2+b1),
 libdatrie1 (= 0.2.13-2+b1),
 libdb5.3 (= 5.3.28+dfsg2-1),
 libdbus-1-3 (= 1.14.6-1),
 libdbus-1-dev (= 1.14.6-1),
 libdbus-glib-1-2 (= 0.112-3),
 libdbusmenu-glib-dev (= 18.10.20180917~bzr492+repack1-3),
 libdbusmenu-glib4 (= 18.10.20180917~bzr492+repack1-3),
 libdbusmenu-gtk3-4 (= 18.10.20180917~bzr492+repack1-3),
 libdconf1 (= 0.40.0-4),
 libdebconfclient0 (= 0.267),
 libdebhelper-perl (= 13.11.4),
 libdeflate-dev (= 1.14-1),
 libdeflate0 (= 1.14-1),
 libdevmapper1.02.1 (= 2:1.02.185-2),
 libdpkg-perl (= 1.21.21),
 libdrm-amdgpu1 (= 2.4.114-1),
 libdrm-common (= 2.4.114-1),
 libdrm-intel1 (= 2.4.114-1),
 libdrm-nouveau2 (= 2.4.114-1),
 libdrm-radeon1 (= 2.4.114-1),
 libdrm2 (= 2.4.114-1),
 libdw-dev (= 0.188-2.1),
 libdw1 (= 0.188-2.1),
 libedit2 (= 3.1-20221030-2),
 libegl-dev (= 1.6.0-1),
 libegl-mesa0 (= 22.3.6-1),
 libegl1 (= 1.6.0-1),
 libegl1-mesa-dev (= 22.3.6-1),
 libelf-dev (= 0.188-2.1),
 libelf1 (= 0.188-2.1),
 libencode-locale-perl (= 1.05-3),
 libepoxy-dev (= 1.5.10-1),
 libepoxy0 (= 1.5.10-1),
 libexpat1 (= 2.5.0-1),
 libexpat1-dev (= 2.5.0-1),
 libfdisk1 (= 2.38.1-5),
 libffi-dev (= 3.4.4-1),
 libffi8 (= 3.4.4-1),
 libfile-find-rule-perl (= 0.34-3),
 libfile-listing-perl (= 6.15-1),
 libfile-stripnondeterminism-perl (= 1.13.1-1),
 libfontconfig-dev (= 2.14.1-4),
 libfontconfig1 (= 2.14.1-4),
 libfreetype-dev (= 2.12.1+dfsg-4),
 libfreetype6 (= 2.12.1+dfsg-4),
 libfribidi-dev (= 1.0.8-2.1),
 libfribidi0 (= 1.0.8-2.1),
 libgbm1 (= 22.3.6-1),
 libgcc-12-dev (= 12.2.0-14),
 libgcc-s1 (= 12.2.0-14),
 libgconf-2-4 (= 3.2.6-8),
 libgconf2-dev (= 3.2.6-8),
 libgcrypt20 (= 1.10.1-3),
 libgdbm-compat4 (= 1.23-3),
 libgdbm6 (= 1.23-3),
 libgdk-pixbuf-2.0-0 (= 2.42.10+dfsg-1+b1),
 libgdk-pixbuf-2.0-dev (= 2.42.10+dfsg-1+b1),
 libgdk-pixbuf2.0-bin (= 2.42.10+dfsg-1+b1),
 libgdk-pixbuf2.0-common (= 2.42.10+dfsg-1),
 libgirepository-1.0-1 (= 1.74.0-3),
 libgl-dev (= 1.6.0-1),
 libgl1 (= 1.6.0-1),
 libgl1-mesa-dri (= 22.3.6-1),
 libglapi-mesa (= 22.3.6-1),
 libgles-dev (= 1.6.0-1),
 libgles1 (= 1.6.0-1),
 libgles2 (= 1.6.0-1),
 libglib2.0-0 (= 2.74.6-1),
 libglib2.0-bin (= 2.74.6-1),
 libglib2.0-data (= 2.74.6-1),
 libglib2.0-dev (= 2.74.6-1),
 libglib2.0-dev-bin (= 2.74.6-1),
 libglvnd-core-dev (= 1.6.0-1),
 libglvnd-dev (= 1.6.0-1),
 libglvnd0 (= 1.6.0-1),
 libglx-dev (= 1.6.0-1),
 libglx-mesa0 (= 22.3.6-1),
 libglx0 (= 1.6.0-1),
 libgmp10 (= 2:6.2.1+dfsg1-1.1),
 libgnutls30 (= 3.7.9-1),
 libgomp1 (= 12.2.0-14),
 libgpg-error0 (= 1.46-1),
 libgprofng0 (= 2.40-2),
 libgraphite2-3 (= 1.3.14-1),
 libgraphite2-dev (= 1.3.14-1),
 libgssapi-krb5-2 (= 1.20.1-1),
 libgstreamer1.0-0 (= 1.22.0-2),
 libgstreamer1.0-dev (= 1.22.0-2),
 libgtk-3-0 (= 3.24.36-4),
 libgtk-3-common (= 3.24.36-4),
 libgtk-3-dev (= 3.24.36-4),
 libgtk2.0-0 (= 2.24.33-2),
 libgtk2.0-common (= 2.24.33-2),
 libgtk2.0-dev (= 2.24.33-2),
 libharfbuzz-dev (= 6.0.0+dfsg-3),
 libharfbuzz-gobject0 (= 6.0.0+dfsg-3),
 libharfbuzz-icu0 (= 6.0.0+dfsg-3),
 libharfbuzz-subset0 (= 6.0.0+dfsg-3),
 libharfbuzz0b (= 6.0.0+dfsg-3),
 libhogweed6 (= 3.8.1-2),
 libhtml-parser-perl (= 3.81-1),
 libhtml-tagset-perl (= 3.20-6),
 libhtml-tree-perl (= 5.07-3),
 libhttp-cookies-perl (= 6.10-1),
 libhttp-date-perl (= 6.05-2),
 libhttp-message-perl (= 6.44-1),
 libhttp-negotiate-perl (= 6.01-2),
 libhwasan0 (= 12.2.0-14),
 libice-dev (= 2:1.0.10-1),
 libice6 (= 2:1.0.10-1),
 libicu-dev (= 72.1-3),
 libicu72 (= 72.1-3),
 libidn2-0 (= 2.3.3-1+b1),
 libio-html-perl (= 1.004-3),
 libio-socket-ssl-perl (= 2.081-2),
 libip4tc2 (= 1.8.9-2),
 libisl23 (= 0.25-1),
 libitm1 (= 12.2.0-14),
 libjansson4 (= 2.14-2),
 libjbig-dev (= 2.1-6.1),
 libjbig0 (= 2.1-6.1),
 libjpeg-dev (= 1:2.1.5-2),
 libjpeg62-turbo (= 1:2.1.5-2),
 libjpeg62-turbo-dev (= 1:2.1.5-2),
 libjson-c5 (= 0.16-2),
 libjsoncpp25 (= 1.9.5-4),
 libk5crypto3 (= 1.20.1-1),
 libkeyutils1 (= 1.6.3-2),
 libkmod2 (= 30+20221128-1),
 libkrb5-3 (= 1.20.1-1),
 libkrb5support0 (= 1.20.1-1),
 liblcms2-2 (= 2.14-2),
 libldap-2.5-0 (= 2.5.13+dfsg-5),
 liblerc-dev (= 4.0.0+ds-2),
 liblerc4 (= 4.0.0+ds-2),
 libllvm15 (= 1:15.0.7-1),
 liblsan0 (= 12.2.0-14),
 liblwp-mediatypes-perl (= 6.04-2),
 liblwp-protocol-https-perl (= 6.10-1),
 liblz4-1 (= 1.9.4-1),
 liblzma-dev (= 5.4.1-0.2),
 liblzma5 (= 5.4.1-0.2),
 liblzo2-2 (= 2.10-2),
 libmagic-mgc (= 1:5.44-3),
 libmagic1 (= 1:5.44-3),
 libmd0 (= 1.0.4-2),
 libmount-dev (= 2.38.1-5),
 libmount1 (= 2.38.1-5),
 libmpc3 (= 1.3.1-1),
 libmpfr6 (= 4.2.0-1),
 libncursesw6 (= 6.4-2),
 libnet-http-perl (= 6.22-1),
 libnet-ssleay-perl (= 1.92-2+b1),
 libnettle8 (= 3.8.1-2),
 libnghttp2-14 (= 1.52.0-1),
 libnotify-dev (= 0.8.1-1),
 libnotify4 (= 0.8.1-1),
 libnsl-dev (= 1.3.0-2),
 libnsl2 (= 1.3.0-2),
 libnumber-compare-perl (= 0.03-3),
 libopengl-dev (= 1.6.0-1),
 libopengl0 (= 1.6.0-1),
 libp11-kit0 (= 0.24.1-2),
 libpam-modules (= 1.5.2-6),
 libpam-modules-bin (= 1.5.2-6),
 libpam-runtime (= 1.5.2-6),
 libpam-systemd (= 252.6-1),
 libpam0g (= 1.5.2-6),
 libpango-1.0-0 (= 1.50.12+ds-1),
 libpango1.0-dev (= 1.50.12+ds-1),
 libpangocairo-1.0-0 (= 1.50.12+ds-1),
 libpangoft2-1.0-0 (= 1.50.12+ds-1),
 libpangoxft-1.0-0 (= 1.50.12+ds-1),
 libpciaccess0 (= 0.17-2),
 libpcre2-16-0 (= 10.42-1),
 libpcre2-32-0 (= 10.42-1),
 libpcre2-8-0 (= 10.42-1),
 libpcre2-dev (= 10.42-1),
 libpcre2-posix3 (= 10.42-1),
 libperl5.36 (= 5.36.0-7),
 libpipeline1 (= 1.5.7-1),
 libpixman-1-0 (= 0.42.2-1),
 libpixman-1-dev (= 0.42.2-1),
 libpkgconf3 (= 1.8.1-1),
 libpng-dev (= 1.6.39-2),
 libpng16-16 (= 1.6.39-2),
 libproc2-0 (= 2:4.0.3-1),
 libpsl5 (= 0.21.2-1),
 libpthread-stubs0-dev (= 0.4-1),
 libpython3-stdlib (= 3.11.2-1),
 libpython3.11-minimal (= 3.11.2-4),
 libpython3.11-stdlib (= 3.11.2-4),
 libreadline8 (= 8.2-1.3),
 libregexp-ipv6-perl (= 0.03-3),
 librhash0 (= 1.4.3-3),
 librsvg2-2 (= 2.54.5+dfsg-1),
 librsvg2-common (= 2.54.5+dfsg-1),
 librtmp1 (= 2.4+20151223.gitfa8646d.1-2+b2),
 libsasl2-2 (= 2.1.28+dfsg-11),
 libsasl2-modules-db (= 2.1.28+dfsg-11),
 libseccomp2 (= 2.5.4-1+b3),
 libselinux1 (= 3.4-1+b5),
 libselinux1-dev (= 3.4-1+b5),
 libsemanage-common (= 3.4-1),
 libsemanage2 (= 3.4-1+b5),
 libsensors-config (= 1:3.6.0-7.1),
 libsensors5 (= 1:3.6.0-7.1),
 libsepol-dev (= 3.4-2),
 libsepol2 (= 3.4-2),
 libsm-dev (= 2:1.2.3-1),
 libsm6 (= 2:1.2.3-1),
 libsmartcols1 (= 2.38.1-5),
 libsqlite3-0 (= 3.40.1-1),
 libssh2-1 (= 1.10.0-3+b1),
 libssl3 (= 3.0.8-1),
 libstdc++-12-dev (= 12.2.0-14),
 libstdc++6 (= 12.2.0-14),
 libsub-override-perl (= 0.09-4),
 libsystemd-shared (= 252.6-1),
 libsystemd0 (= 252.6-1),
 libtasn1-6 (= 4.19.0-2),
 libtext-glob-perl (= 0.11-3),
 libthai-data (= 0.1.29-1),
 libthai-dev (= 0.1.29-1),
 libthai0 (= 0.1.29-1),
 libtiff-dev (= 4.5.0-5),
 libtiff6 (= 4.5.0-5),
 libtiffxx6 (= 4.5.0-5),
 libtimedate-perl (= 2.3300-2),
 libtinfo6 (= 6.4-2),
 libtirpc-common (= 1.3.3+ds-1),
 libtirpc-dev (= 1.3.3+ds-1),
 libtirpc3 (= 1.3.3+ds-1),
 libtool (= 2.4.7-5),
 libtry-tiny-perl (= 0.31-2),
 libtsan2 (= 12.2.0-14),
 libubsan1 (= 12.2.0-14),
 libuchardet0 (= 0.0.7-1),
 libudev1 (= 252.6-1),
 libunistring2 (= 1.0-2),
 libunwind-dev (= 1.6.2-3),
 libunwind8 (= 1.6.2-3),
 liburi-perl (= 5.17-1),
 libuuid1 (= 2.38.1-5),
 libuv1 (= 1.44.2-1),
 libwayland-bin (= 1.21.0-1),
 libwayland-client0 (= 1.21.0-1),
 libwayland-cursor0 (= 1.21.0-1),
 libwayland-dev (= 1.21.0-1),
 libwayland-egl1 (= 1.21.0-1),
 libwayland-server0 (= 1.21.0-1),
 libwebp-dev (= 1.2.4-0.1),
 libwebp7 (= 1.2.4-0.1),
 libwebpdemux2 (= 1.2.4-0.1),
 libwebpmux3 (= 1.2.4-0.1),
 libwww-perl (= 6.68-1),
 libwww-robotrules-perl (= 6.02-1),
 libx11-6 (= 2:1.8.4-2),
 libx11-data (= 2:1.8.4-2),
 libx11-dev (= 2:1.8.4-2),
 libx11-xcb1 (= 2:1.8.4-2),
 libxau-dev (= 1:1.0.9-1),
 libxau6 (= 1:1.0.9-1),
 libxcb-dri2-0 (= 1.15-1),
 libxcb-dri3-0 (= 1.15-1),
 libxcb-glx0 (= 1.15-1),
 libxcb-present0 (= 1.15-1),
 libxcb-randr0 (= 1.15-1),
 libxcb-render0 (= 1.15-1),
 libxcb-render0-dev (= 1.15-1),
 libxcb-shm0 (= 1.15-1),
 libxcb-shm0-dev (= 1.15-1),
 libxcb-sync1 (= 1.15-1),
 libxcb-xfixes0 (= 1.15-1),
 libxcb1 (= 1.15-1),
 libxcb1-dev (= 1.15-1),
 libxcomposite-dev (= 1:0.4.5-1),
 libxcomposite1 (= 1:0.4.5-1),
 libxcursor-dev (= 1:1.2.1-1),
 libxcursor1 (= 1:1.2.1-1),
 libxdamage-dev (= 1:1.1.6-1),
 libxdamage1 (= 1:1.1.6-1),
 libxdmcp-dev (= 1:1.1.2-3),
 libxdmcp6 (= 1:1.1.2-3),
 libxext-dev (= 2:1.3.4-1+b1),
 libxext6 (= 2:1.3.4-1+b1),
 libxfixes-dev (= 1:6.0.0-2),
 libxfixes3 (= 1:6.0.0-2),
 libxft-dev (= 2.3.6-1),
 libxft2 (= 2.3.6-1),
 libxi-dev (= 2:1.8-1+b1),
 libxi6 (= 2:1.8-1+b1),
 libxinerama-dev (= 2:1.1.4-3),
 libxinerama1 (= 2:1.1.4-3),
 libxkbcommon-dev (= 1.5.0-1),
 libxkbcommon0 (= 1.5.0-1),
 libxml-parser-perl (= 2.46-4),
 libxml2 (= 2.9.14+dfsg-1.1+b3),
 libxml2-dev (= 2.9.14+dfsg-1.1+b3),
 libxml2-utils (= 2.9.14+dfsg-1.1+b3),
 libxrandr-dev (= 2:1.5.2-2+b1),
 libxrandr2 (= 2:1.5.2-2+b1),
 libxrender-dev (= 1:0.9.10-1.1),
 libxrender1 (= 1:0.9.10-1.1),
 libxshmfence1 (= 1.3-1),
 libxtst-dev (= 2:1.2.3-1.1),
 libxtst6 (= 2:1.2.3-1.1),
 libxxf86vm1 (= 1:1.1.4-1+b2),
 libz3-4 (= 4.8.12-3.1),
 libzstd-dev (= 1.5.4+dfsg2-3),
 libzstd1 (= 1.5.4+dfsg2-3),
 linux-libc-dev (= 6.1.15-1),
 login (= 1:4.13+dfsg1-1),
 m4 (= 1.4.19-3),
 make (= 4.3-4.1),
 man-db (= 2.11.2-1),
 mawk (= 1.3.4.20200120-3.1),
 media-types (= 10.0.0),
 mount (= 2.38.1-5),
 ncurses-base (= 6.4-2),
 ncurses-bin (= 6.4-2),
 netbase (= 6.4),
 openssl (= 3.0.8-1),
 pango1.0-tools (= 1.50.12+ds-1),
 passwd (= 1:4.13+dfsg1-1),
 patch (= 2.7.6-7),
 perl (= 5.36.0-7),
 perl-base (= 5.36.0-7),
 perl-modules-5.36 (= 5.36.0-7),
 perl-openssl-defaults (= 7+b1),
 pkg-config (= 1.8.1-1),
 pkgconf (= 1.8.1-1),
 pkgconf-bin (= 1.8.1-1),
 po-debconf (= 1.0.21+nmu1),
 procps (= 2:4.0.3-1),
 psmisc (= 23.6-1),
 python3 (= 3.11.2-1),
 python3-distutils (= 3.11.2-2),
 python3-lib2to3 (= 3.11.2-2),
 python3-minimal (= 3.11.2-1),
 python3.11 (= 3.11.2-4),
 python3.11-minimal (= 3.11.2-4),
 readline-common (= 8.2-1.3),
 rpcsvc-proto (= 1.4.3-1),
 sed (= 4.9-1),
 sensible-utils (= 0.0.17+nmu1),
 sgml-base (= 1.31),
 shared-mime-info (= 2.2-1),
 systemd (= 252.6-1),
 systemd-sysv (= 252.6-1),
 sysvinit-utils (= 3.06-2),
 tar (= 1.34+dfsg-1.1),
 ucf (= 3.0043+nmu1),
 usrmerge (= 35),
 util-linux (= 2.38.1-5),
 util-linux-extra (= 2.38.1-5),
 uuid-dev (= 2.38.1-5),
 wayland-protocols (= 1.31-1),
 x11-common (= 1:7.7+23),
 x11proto-dev (= 2022.1-1),
 xkb-data (= 2.35.1-1),
 xml-core (= 0.18+nmu1),
 xorg-sgml-doctools (= 1:1.11-1.1),
 xtrans-dev (= 1.4.0-1),
 xz-utils (= 5.4.1-0.2),
 zlib1g (= 1:1.2.13.dfsg-1),
 zlib1g-dev (= 1:1.2.13.dfsg-1)
Environment:
 DEB_BUILD_OPTIONS="nocheck parallel=1"
 DEB_BUILD_PROFILES="cross nocheck"
 LANG="en_GB.UTF-8"
 LC_ALL="C.UTF-8"
 SOURCE_DATE_EPOCH="1676465766"


+------------------------------------------------------------------------------+
| Package contents                                                             |
+------------------------------------------------------------------------------+


alarm-clock-applet-dbgsym_0.4.1-3_i386.deb
------------------------------------------

 new Debian package, version 2.0.
 size 90424 bytes: control archive=524 bytes.
     377 bytes,    12 lines      control              
     106 bytes,     1 lines      md5sums              
 Package: alarm-clock-applet-dbgsym
 Source: alarm-clock-applet
 Version: 0.4.1-3
 Auto-Built-Package: debug-symbols
 Architecture: i386
 Maintainer: Chow Loong Jin <hyperair@debian.org>
 Installed-Size: 115
 Depends: alarm-clock-applet (= 0.4.1-3)
 Section: debug
 Priority: optional
 Description: debug symbols for alarm-clock-applet
 Build-Ids: 509d73a6721f778a1507467ca81bf4b61a6d4127

drwxr-xr-x root/root         0 2023-02-15 12:56 ./
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/lib/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/lib/debug/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/lib/debug/.build-id/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/lib/debug/.build-id/50/
-rw-r--r-- root/root    106868 2023-02-15 12:56 ./usr/lib/debug/.build-id/50/9d73a6721f778a1507467ca81bf4b61a6d4127.debug
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/doc/
lrwxrwxrwx root/root         0 2023-02-15 12:56 ./usr/share/doc/alarm-clock-applet-dbgsym -> alarm-clock-applet


alarm-clock-applet-gconf-migration-dbgsym_0.4.1-3_i386.deb
----------------------------------------------------------

 new Debian package, version 2.0.
 size 7928 bytes: control archive=540 bytes.
     424 bytes,    12 lines      control              
     106 bytes,     1 lines      md5sums              
 Package: alarm-clock-applet-gconf-migration-dbgsym
 Source: alarm-clock-applet
 Version: 0.4.1-3
 Auto-Built-Package: debug-symbols
 Architecture: i386
 Maintainer: Chow Loong Jin <hyperair@debian.org>
 Installed-Size: 20
 Depends: alarm-clock-applet-gconf-migration (= 0.4.1-3)
 Section: debug
 Priority: optional
 Description: debug symbols for alarm-clock-applet-gconf-migration
 Build-Ids: d0fdcace42b224dfa55a1427adbe4c80217c0ec5

drwxr-xr-x root/root         0 2023-02-15 12:56 ./
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/lib/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/lib/debug/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/lib/debug/.build-id/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/lib/debug/.build-id/d0/
-rw-r--r-- root/root     10068 2023-02-15 12:56 ./usr/lib/debug/.build-id/d0/fdcace42b224dfa55a1427adbe4c80217c0ec5.debug
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/doc/
lrwxrwxrwx root/root         0 2023-02-15 12:56 ./usr/share/doc/alarm-clock-applet-gconf-migration-dbgsym -> alarm-clock-applet-gconf-migration


alarm-clock-applet-gconf-migration_0.4.1-3_i386.deb
---------------------------------------------------

 new Debian package, version 2.0.
 size 22656 bytes: control archive=968 bytes.
    1016 bytes,    23 lines      control              
     447 bytes,     5 lines      md5sums              
 Package: alarm-clock-applet-gconf-migration
 Source: alarm-clock-applet
 Version: 0.4.1-3
 Architecture: i386
 Maintainer: Chow Loong Jin <hyperair@debian.org>
 Installed-Size: 100
 Depends: alarm-clock-applet (>= 0.4.1), gconf-service, libc6 (>= 2.34), libgconf-2-4 (>= 3.2.5), libglib2.0-0 (>= 2.49.2)
 Conflicts: alarm-clock-applet (<< 0.4.1~)
 Replaces: alarm-clock-applet (<< 0.4.1~)
 Section: gnome
 Priority: optional
 Homepage: https://alarm-clock-applet.github.io
 Description: alarm clock panel indicator - gconf migration
  Alarm Clock is a fully-featured alarm clock which resides in the notification
  area. It is easy to use yet powerful with support for multiple and repeatable
  alarms, as well as snoozing and a flexible notification system.
  .
  Two types of alarms are supported: Alarm Clocks and Timers.
  Notification is done by either playing a sound or launching an
  application.
  .
  This contains the gconf migration helper and can be safely uninstalled after
  the first successful run of alarm-clock-applet.

drwxr-xr-x root/root         0 2023-02-15 12:56 ./
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/bin/
-rwxr-xr-x root/root     13856 2023-02-15 12:56 ./usr/bin/alarm-clock-applet-gconf-migration
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/doc/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/doc/alarm-clock-applet-gconf-migration/
-rw-r--r-- root/root       812 2023-02-15 12:56 ./usr/share/doc/alarm-clock-applet-gconf-migration/changelog.Debian.gz
-rw-r--r-- root/root        66 2023-01-09 05:09 ./usr/share/doc/alarm-clock-applet-gconf-migration/changelog.gz
-rw-r--r-- root/root      2973 2023-02-15 12:56 ./usr/share/doc/alarm-clock-applet-gconf-migration/copyright
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/gconf/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/gconf/schemas/
-rw-r--r-- root/root     73207 2023-01-09 05:09 ./usr/share/gconf/schemas/alarm-clock.schemas


alarm-clock-applet_0.4.1-3_i386.deb
-----------------------------------

 new Debian package, version 2.0.
 size 136140 bytes: control archive=2584 bytes.
      46 bytes,     1 lines      conffiles            
     955 bytes,    19 lines      control              
    6228 bytes,    71 lines      md5sums              
 Package: alarm-clock-applet
 Version: 0.4.1-3
 Architecture: i386
 Maintainer: Chow Loong Jin <hyperair@debian.org>
 Installed-Size: 553
 Depends: gstreamer1.0-plugins-base, gstreamer1.0-plugins-good, libayatana-appindicator3-1 (>= 0.4.90), libc6 (>= 2.34), libglib2.0-0 (>= 2.39.90), libgstreamer1.0-0 (>= 1.0.0), libgtk-3-0 (>= 3.11.5), libnotify4 (>= 0.7.0), dconf-gsettings-backend | gsettings-backend
 Recommends: alarm-clock-applet-gconf-migration
 Suggests: playerctl
 Section: gnome
 Priority: optional
 Homepage: https://alarm-clock-applet.github.io
 Description: alarm clock panel indicator
  Alarm Clock is a fully-featured alarm clock which resides in the notification
  area. It is easy to use yet powerful with support for multiple and repeatable
  alarms, as well as snoozing and a flexible notification system.
  .
  Two types of alarms are supported: Alarm Clocks and Timers.
  Notification is done by either playing a sound or launching an
  application.

drwxr-xr-x root/root         0 2023-02-15 12:56 ./
drwxr-xr-x root/root         0 2023-02-15 12:56 ./etc/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./etc/xdg/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./etc/xdg/autostart/
-rw-r--r-- root/root      2335 2023-02-15 12:56 ./etc/xdg/autostart/alarm-clock-applet.desktop
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/bin/
-rwxr-xr-x root/root    117508 2023-02-15 12:56 ./usr/bin/alarm-clock-applet
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/alarm-clock-applet/
-rw-r--r-- root/root        87 2023-01-09 05:09 ./usr/share/alarm-clock-applet/alarm-clock.css
-rw-r--r-- root/root     71850 2023-01-09 05:09 ./usr/share/alarm-clock-applet/alarm-clock.ui
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/applications/
-rw-r--r-- root/root      2326 2023-02-15 12:56 ./usr/share/applications/alarm-clock-applet.desktop
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/doc/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/doc/alarm-clock-applet/
-rw-r--r-- root/root       806 2023-02-15 12:56 ./usr/share/doc/alarm-clock-applet/changelog.Debian.gz
-rw-r--r-- root/root        66 2023-01-09 05:09 ./usr/share/doc/alarm-clock-applet/changelog.gz
-rw-r--r-- root/root      2973 2023-02-15 12:56 ./usr/share/doc/alarm-clock-applet/copyright
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/glib-2.0/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/glib-2.0/schemas/
-rw-r--r-- root/root       975 2023-02-15 12:56 ./usr/share/glib-2.0/schemas/io.github.alarm-clock-applet.enums.gschema.xml
-rw-r--r-- root/root      3506 2023-01-09 05:09 ./usr/share/glib-2.0/schemas/io.github.alarm-clock-applet.gschema.xml
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/hicolor/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/hicolor/16x16/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/hicolor/16x16/apps/
-rw-r--r-- root/root      1013 2023-01-09 05:09 ./usr/share/icons/hicolor/16x16/apps/alarm-clock-triggered.png
-rw-r--r-- root/root       904 2023-01-09 05:09 ./usr/share/icons/hicolor/16x16/apps/alarm-clock.png
-rw-r--r-- root/root       711 2023-01-09 05:09 ./usr/share/icons/hicolor/16x16/apps/alarm-timer.png
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/hicolor/22x22/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/hicolor/22x22/apps/
-rw-r--r-- root/root      1619 2023-01-09 05:09 ./usr/share/icons/hicolor/22x22/apps/alarm-clock-triggered.png
-rw-r--r-- root/root      1277 2023-01-09 05:09 ./usr/share/icons/hicolor/22x22/apps/alarm-clock.png
-rw-r--r-- root/root      1250 2023-01-09 05:09 ./usr/share/icons/hicolor/22x22/apps/alarm-timer.png
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/hicolor/24x24/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/hicolor/24x24/apps/
-rw-r--r-- root/root      1866 2023-01-09 05:09 ./usr/share/icons/hicolor/24x24/apps/alarm-clock-triggered.png
-rw-r--r-- root/root      1518 2023-01-09 05:09 ./usr/share/icons/hicolor/24x24/apps/alarm-clock.png
-rw-r--r-- root/root      1366 2023-01-09 05:09 ./usr/share/icons/hicolor/24x24/apps/alarm-timer.png
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/hicolor/32x32/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/hicolor/32x32/apps/
-rw-r--r-- root/root      2864 2023-01-09 05:09 ./usr/share/icons/hicolor/32x32/apps/alarm-clock-triggered.png
-rw-r--r-- root/root      2167 2023-01-09 05:09 ./usr/share/icons/hicolor/32x32/apps/alarm-clock.png
-rw-r--r-- root/root      2021 2023-01-09 05:09 ./usr/share/icons/hicolor/32x32/apps/alarm-timer.png
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/hicolor/36x36/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/hicolor/36x36/apps/
-rw-r--r-- root/root      3438 2023-01-09 05:09 ./usr/share/icons/hicolor/36x36/apps/alarm-clock-triggered.png
-rw-r--r-- root/root      2518 2023-01-09 05:09 ./usr/share/icons/hicolor/36x36/apps/alarm-clock.png
-rw-r--r-- root/root      2257 2023-01-09 05:09 ./usr/share/icons/hicolor/36x36/apps/alarm-timer.png
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/hicolor/48x48/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/hicolor/48x48/apps/
-rw-r--r-- root/root      5358 2023-01-09 05:09 ./usr/share/icons/hicolor/48x48/apps/alarm-clock-triggered.png
-rw-r--r-- root/root      3453 2023-01-09 05:09 ./usr/share/icons/hicolor/48x48/apps/alarm-clock.png
-rw-r--r-- root/root      2999 2023-01-09 05:09 ./usr/share/icons/hicolor/48x48/apps/alarm-timer.png
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/hicolor/64x64/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/hicolor/64x64/apps/
-rw-r--r-- root/root      8404 2023-01-09 05:09 ./usr/share/icons/hicolor/64x64/apps/alarm-clock-triggered.png
-rw-r--r-- root/root      4912 2023-01-09 05:09 ./usr/share/icons/hicolor/64x64/apps/alarm-clock.png
-rw-r--r-- root/root      4360 2023-01-09 05:09 ./usr/share/icons/hicolor/64x64/apps/alarm-timer.png
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/hicolor/scalable/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/icons/hicolor/scalable/apps/
-rw-r--r-- root/root     11772 2023-01-09 05:09 ./usr/share/icons/hicolor/scalable/apps/alarm-clock-triggered.svg
-rw-r--r-- root/root     10076 2023-01-09 05:09 ./usr/share/icons/hicolor/scalable/apps/alarm-clock.svg
-rw-r--r-- root/root      8970 2023-01-09 05:09 ./usr/share/icons/hicolor/scalable/apps/alarm-timer.svg
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/ar/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/ar/LC_MESSAGES/
-rw-r--r-- root/root      4117 2023-02-15 12:56 ./usr/share/locale/ar/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/ast/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/ast/LC_MESSAGES/
-rw-r--r-- root/root      3873 2023-02-15 12:56 ./usr/share/locale/ast/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/be/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/be/LC_MESSAGES/
-rw-r--r-- root/root      4573 2023-02-15 12:56 ./usr/share/locale/be/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/bg/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/bg/LC_MESSAGES/
-rw-r--r-- root/root      4838 2023-02-15 12:56 ./usr/share/locale/bg/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/ca/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/ca/LC_MESSAGES/
-rw-r--r-- root/root      3747 2023-02-15 12:56 ./usr/share/locale/ca/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/cs/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/cs/LC_MESSAGES/
-rw-r--r-- root/root      1014 2023-02-15 12:56 ./usr/share/locale/cs/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/da/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/da/LC_MESSAGES/
-rw-r--r-- root/root      3591 2023-02-15 12:56 ./usr/share/locale/da/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/de/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/de/LC_MESSAGES/
-rw-r--r-- root/root      3849 2023-02-15 12:56 ./usr/share/locale/de/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/el/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/el/LC_MESSAGES/
-rw-r--r-- root/root      5154 2023-02-15 12:56 ./usr/share/locale/el/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/es/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/es/LC_MESSAGES/
-rw-r--r-- root/root      4100 2023-02-15 12:56 ./usr/share/locale/es/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/et/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/et/LC_MESSAGES/
-rw-r--r-- root/root      2399 2023-02-15 12:56 ./usr/share/locale/et/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/fi/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/fi/LC_MESSAGES/
-rw-r--r-- root/root      3282 2023-02-15 12:56 ./usr/share/locale/fi/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/fo/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/fo/LC_MESSAGES/
-rw-r--r-- root/root      3574 2023-02-15 12:56 ./usr/share/locale/fo/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/fr/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/fr/LC_MESSAGES/
-rw-r--r-- root/root      3930 2023-02-15 12:56 ./usr/share/locale/fr/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/gl/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/gl/LC_MESSAGES/
-rw-r--r-- root/root      3858 2023-02-15 12:56 ./usr/share/locale/gl/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/he/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/he/LC_MESSAGES/
-rw-r--r-- root/root      4174 2023-02-15 12:56 ./usr/share/locale/he/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/hi/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/hi/LC_MESSAGES/
-rw-r--r-- root/root      2204 2023-02-15 12:56 ./usr/share/locale/hi/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/hu/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/hu/LC_MESSAGES/
-rw-r--r-- root/root      3995 2023-02-15 12:56 ./usr/share/locale/hu/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/id/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/id/LC_MESSAGES/
-rw-r--r-- root/root      2603 2023-02-15 12:56 ./usr/share/locale/id/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/it/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/it/LC_MESSAGES/
-rw-r--r-- root/root       418 2023-02-15 12:56 ./usr/share/locale/it/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/ja/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/ja/LC_MESSAGES/
-rw-r--r-- root/root      3930 2023-02-15 12:56 ./usr/share/locale/ja/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/ka/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/ka/LC_MESSAGES/
-rw-r--r-- root/root      5481 2023-02-15 12:56 ./usr/share/locale/ka/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/la/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/la/LC_MESSAGES/
-rw-r--r-- root/root       996 2023-02-15 12:56 ./usr/share/locale/la/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/ms/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/ms/LC_MESSAGES/
-rw-r--r-- root/root      3732 2023-02-15 12:56 ./usr/share/locale/ms/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/nb/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/nb/LC_MESSAGES/
-rw-r--r-- root/root      3723 2023-02-15 12:56 ./usr/share/locale/nb/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/nl/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/nl/LC_MESSAGES/
-rw-r--r-- root/root      3522 2023-02-15 12:56 ./usr/share/locale/nl/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/nn/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/nn/LC_MESSAGES/
-rw-r--r-- root/root       715 2023-02-15 12:56 ./usr/share/locale/nn/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/pl/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/pl/LC_MESSAGES/
-rw-r--r-- root/root      3744 2023-02-15 12:56 ./usr/share/locale/pl/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/pt/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/pt/LC_MESSAGES/
-rw-r--r-- root/root       820 2023-02-15 12:56 ./usr/share/locale/pt/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/pt_BR/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/pt_BR/LC_MESSAGES/
-rw-r--r-- root/root      4078 2023-02-15 12:56 ./usr/share/locale/pt_BR/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/ru/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/ru/LC_MESSAGES/
-rw-r--r-- root/root      4889 2023-02-15 12:56 ./usr/share/locale/ru/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/si/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/si/LC_MESSAGES/
-rw-r--r-- root/root      5925 2023-02-15 12:56 ./usr/share/locale/si/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/sv/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/sv/LC_MESSAGES/
-rw-r--r-- root/root      2425 2023-02-15 12:56 ./usr/share/locale/sv/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/tr/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/tr/LC_MESSAGES/
-rw-r--r-- root/root      3941 2023-02-15 12:56 ./usr/share/locale/tr/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/uk/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/uk/LC_MESSAGES/
-rw-r--r-- root/root      4673 2023-02-15 12:56 ./usr/share/locale/uk/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/zh_CN/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/zh_CN/LC_MESSAGES/
-rw-r--r-- root/root      3731 2023-02-15 12:56 ./usr/share/locale/zh_CN/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/zh_TW/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/locale/zh_TW/LC_MESSAGES/
-rw-r--r-- root/root      3695 2023-02-15 12:56 ./usr/share/locale/zh_TW/LC_MESSAGES/alarm-clock-applet.mo
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/man/
drwxr-xr-x root/root         0 2023-02-15 12:56 ./usr/share/man/man1/
-rw-r--r-- root/root      2026 2023-02-15 12:56 ./usr/share/man/man1/alarm-clock-applet.1.gz


lintian
-------


Setup apt archive
-----------------

Merged Build-Depends: lintian:arm64
Filtered Build-Depends: lintian:arm64
dpkg-deb: building package 'sbuild-build-depends-lintian-dummy' in '/<<RESOLVERDIR>>/apt_archive/sbuild-build-depends-lintian-dummy.deb'.
Ign:1 copy:/<<RESOLVERDIR>>/apt_archive ./ InRelease
Get:2 copy:/<<RESOLVERDIR>>/apt_archive ./ Release [963 B]
Ign:3 copy:/<<RESOLVERDIR>>/apt_archive ./ Release.gpg
Get:4 copy:/<<RESOLVERDIR>>/apt_archive ./ Sources [641 B]
Get:5 copy:/<<RESOLVERDIR>>/apt_archive ./ Packages [731 B]
Fetched 2335 B in 0s (59.3 kB/s)
Reading package lists...
Reading package lists...

Install lintian build dependencies (apt-based resolver)
-------------------------------------------------------

Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  diffstat gpg gpgconf iso-codes libaliased-perl libapt-pkg-perl libassuan0
  libb-hooks-endofscope-perl libb-hooks-op-check-perl libberkeleydb-perl
  libcapture-tiny-perl libcgi-pm-perl libclass-data-inheritable-perl
  libclass-method-modifiers-perl libclass-xsaccessor-perl libconfig-tiny-perl
  libconst-fast-perl libcpanel-json-xs-perl libdata-dpath-perl
  libdata-messagepack-perl libdata-optlist-perl libdata-validate-domain-perl
  libdata-validate-ip-perl libdata-validate-uri-perl libdevel-callchecker-perl
  libdevel-size-perl libdevel-stacktrace-perl libdynaloader-functions-perl
  libemail-address-xs-perl libexception-class-perl libfile-basedir-perl
  libfont-ttf-perl libhtml-form-perl libhtml-html5-entities-perl
  libhtml-tokeparser-simple-perl libimport-into-perl libio-interactive-perl
  libipc-run3-perl libipc-system-simple-perl libiterator-perl
  libiterator-util-perl libjson-maybexs-perl liblist-compare-perl
  liblist-someutils-perl liblist-utilsby-perl liblz1 liblzo2-2 libmarkdown2
  libmldbm-perl libmodule-implementation-perl libmodule-runtime-perl
  libmoo-perl libmoox-aliases-perl libmouse-perl libnamespace-clean-perl
  libnet-domain-tld-perl libnet-ipv6addr-perl libnet-netmask-perl
  libnetaddr-ip-perl libpackage-stash-perl libparams-classify-perl
  libparams-util-perl libpath-tiny-perl libperlio-gzip-perl
  libperlio-utf8-strict-perl libproc-processtable-perl
  libregexp-wildcards-perl librole-tiny-perl libsereal-decoder-perl
  libsereal-encoder-perl libsort-versions-perl libstrictures-perl
  libsub-exporter-perl libsub-exporter-progressive-perl libsub-identify-perl
  libsub-install-perl libsub-name-perl libsub-quote-perl
  libsyntax-keyword-try-perl libterm-readkey-perl libtext-levenshteinxs-perl
  libtext-markdown-discount-perl libtext-xslate-perl libtime-duration-perl
  libtime-moment-perl libunicode-utf8-perl libvariable-magic-perl
  libwww-mechanize-perl libxs-parse-keyword-perl libyaml-0-2
  libyaml-libyaml-perl lintian lzop patchutils plzip t1utils unzip
Suggested packages:
  isoquery libscalar-number-perl libbareword-filehandles-perl libindirect-perl
  libmultidimensional-perl binutils-multiarch libtext-template-perl zip
Recommended packages:
  gnupg libcgi-fast-perl liblist-someutils-xs-perl libfreezethaw-perl
  libmath-base85-perl libsocket6-perl libpackage-stash-xs-perl libxstring-perl
The following NEW packages will be installed:
  diffstat gpg gpgconf iso-codes libaliased-perl libapt-pkg-perl libassuan0
  libb-hooks-endofscope-perl libb-hooks-op-check-perl libberkeleydb-perl
  libcapture-tiny-perl libcgi-pm-perl libclass-data-inheritable-perl
  libclass-method-modifiers-perl libclass-xsaccessor-perl libconfig-tiny-perl
  libconst-fast-perl libcpanel-json-xs-perl libdata-dpath-perl
  libdata-messagepack-perl libdata-optlist-perl libdata-validate-domain-perl
  libdata-validate-ip-perl libdata-validate-uri-perl libdevel-callchecker-perl
  libdevel-size-perl libdevel-stacktrace-perl libdynaloader-functions-perl
  libemail-address-xs-perl libexception-class-perl libfile-basedir-perl
  libfont-ttf-perl libhtml-form-perl libhtml-html5-entities-perl
  libhtml-tokeparser-simple-perl libimport-into-perl libio-interactive-perl
  libipc-run3-perl libipc-system-simple-perl libiterator-perl
  libiterator-util-perl libjson-maybexs-perl liblist-compare-perl
  liblist-someutils-perl liblist-utilsby-perl liblz1 liblzo2-2 libmarkdown2
  libmldbm-perl libmodule-implementation-perl libmodule-runtime-perl
  libmoo-perl libmoox-aliases-perl libmouse-perl libnamespace-clean-perl
  libnet-domain-tld-perl libnet-ipv6addr-perl libnet-netmask-perl
  libnetaddr-ip-perl libpackage-stash-perl libparams-classify-perl
  libparams-util-perl libpath-tiny-perl libperlio-gzip-perl
  libperlio-utf8-strict-perl libproc-processtable-perl
  libregexp-wildcards-perl librole-tiny-perl libsereal-decoder-perl
  libsereal-encoder-perl libsort-versions-perl libstrictures-perl
  libsub-exporter-perl libsub-exporter-progressive-perl libsub-identify-perl
  libsub-install-perl libsub-name-perl libsub-quote-perl
  libsyntax-keyword-try-perl libterm-readkey-perl libtext-levenshteinxs-perl
  libtext-markdown-discount-perl libtext-xslate-perl libtime-duration-perl
  libtime-moment-perl libunicode-utf8-perl libvariable-magic-perl
  libwww-mechanize-perl libxs-parse-keyword-perl libyaml-0-2
  libyaml-libyaml-perl lintian lzop patchutils plzip
  sbuild-build-depends-lintian-dummy:i386 t1utils unzip
0 upgraded, 98 newly installed, 0 to remove and 0 not upgraded.
Need to get 9478 kB of archives.
After this operation, 43.5 MB of additional disk space will be used.
Get:1 copy:/<<RESOLVERDIR>>/apt_archive ./ sbuild-build-depends-lintian-dummy 0.invalid.0 [848 B]
Get:2 http://mirror.einval.org/debian sid/main arm64 diffstat arm64 1.65-1 [31.2 kB]
Get:3 http://mirror.einval.org/debian sid/main arm64 libassuan0 arm64 2.5.5-5 [45.9 kB]
Get:4 http://mirror.einval.org/debian sid/main arm64 gpgconf arm64 2.2.40-1 [556 kB]
Get:5 http://mirror.einval.org/debian sid/main arm64 gpg arm64 2.2.40-1 [903 kB]
Get:6 http://mirror.einval.org/debian sid/main arm64 iso-codes all 4.13.0-1 [2899 kB]
Get:7 http://mirror.einval.org/debian sid/main arm64 libaliased-perl all 0.34-3 [13.5 kB]
Get:8 http://mirror.einval.org/debian sid/main arm64 libapt-pkg-perl arm64 0.1.40+b2 [66.1 kB]
Get:9 http://mirror.einval.org/debian sid/main arm64 libb-hooks-op-check-perl arm64 0.22-2+b1 [10.4 kB]
Get:10 http://mirror.einval.org/debian sid/main arm64 libdynaloader-functions-perl all 0.003-3 [12.7 kB]
Get:11 http://mirror.einval.org/debian sid/main arm64 libdevel-callchecker-perl arm64 0.008-2 [15.9 kB]
Get:12 http://mirror.einval.org/debian sid/main arm64 libparams-classify-perl arm64 0.015-2+b1 [22.9 kB]
Get:13 http://mirror.einval.org/debian sid/main arm64 libmodule-runtime-perl all 0.016-2 [19.6 kB]
Get:14 http://mirror.einval.org/debian sid/main arm64 libmodule-implementation-perl all 0.09-2 [12.6 kB]
Get:15 http://mirror.einval.org/debian sid/main arm64 libsub-exporter-progressive-perl all 0.001013-3 [7496 B]
Get:16 http://mirror.einval.org/debian sid/main arm64 libvariable-magic-perl arm64 0.63-1+b1 [42.8 kB]
Get:17 http://mirror.einval.org/debian sid/main arm64 libb-hooks-endofscope-perl all 0.26-1 [19.6 kB]
Get:18 http://mirror.einval.org/debian sid/main arm64 libberkeleydb-perl arm64 0.64-2+b1 [121 kB]
Get:19 http://mirror.einval.org/debian sid/main arm64 libcapture-tiny-perl all 0.48-2 [24.6 kB]
Get:20 http://mirror.einval.org/debian sid/main arm64 libcgi-pm-perl all 4.55-1 [220 kB]
Get:21 http://mirror.einval.org/debian sid/main arm64 libclass-data-inheritable-perl all 0.08-3 [8588 B]
Get:22 http://mirror.einval.org/debian sid/main arm64 libclass-method-modifiers-perl all 2.14-1 [18.1 kB]
Get:23 http://mirror.einval.org/debian sid/main arm64 libclass-xsaccessor-perl arm64 1.19-4+b1 [35.3 kB]
Get:24 http://mirror.einval.org/debian sid/main arm64 libconfig-tiny-perl all 2.28-2 [16.4 kB]
Get:25 http://mirror.einval.org/debian sid/main arm64 libparams-util-perl arm64 1.102-2+b1 [24.2 kB]
Get:26 http://mirror.einval.org/debian sid/main arm64 libsub-install-perl all 0.929-1 [10.5 kB]
Get:27 http://mirror.einval.org/debian sid/main arm64 libdata-optlist-perl all 0.113-1 [10.6 kB]
Get:28 http://mirror.einval.org/debian sid/main arm64 libsub-exporter-perl all 0.989-1 [50.5 kB]
Get:29 http://mirror.einval.org/debian sid/main arm64 libconst-fast-perl all 0.014-2 [8792 B]
Get:30 http://mirror.einval.org/debian sid/main arm64 libcpanel-json-xs-perl arm64 4.35-1 [128 kB]
Get:31 http://mirror.einval.org/debian sid/main arm64 libdevel-stacktrace-perl all 2.0400-2 [26.8 kB]
Get:32 http://mirror.einval.org/debian sid/main arm64 libexception-class-perl all 1.45-1 [34.6 kB]
Get:33 http://mirror.einval.org/debian sid/main arm64 libiterator-perl all 0.03+ds1-2 [18.8 kB]
Get:34 http://mirror.einval.org/debian sid/main arm64 libiterator-util-perl all 0.02+ds1-2 [14.0 kB]
Get:35 http://mirror.einval.org/debian sid/main arm64 libdata-dpath-perl all 0.58-2 [43.6 kB]
Get:36 http://mirror.einval.org/debian sid/main arm64 libdata-messagepack-perl arm64 1.02-1+b1 [34.0 kB]
Get:37 http://mirror.einval.org/debian sid/main arm64 libnet-domain-tld-perl all 1.75-3 [31.9 kB]
Get:38 http://mirror.einval.org/debian sid/main arm64 libdata-validate-domain-perl all 0.10-1.1 [11.1 kB]
Get:39 http://mirror.einval.org/debian sid/main arm64 libnet-ipv6addr-perl all 1.02-1 [21.7 kB]
Get:40 http://mirror.einval.org/debian sid/main arm64 libnet-netmask-perl all 2.0002-2 [28.6 kB]
Get:41 http://mirror.einval.org/debian sid/main arm64 libnetaddr-ip-perl arm64 4.079+dfsg-2+b1 [98.8 kB]
Get:42 http://mirror.einval.org/debian sid/main arm64 libdata-validate-ip-perl all 0.31-1 [20.6 kB]
Get:43 http://mirror.einval.org/debian sid/main arm64 libdata-validate-uri-perl all 0.07-2 [11.2 kB]
Get:44 http://mirror.einval.org/debian sid/main arm64 libdevel-size-perl arm64 0.83-2+b1 [24.2 kB]
Get:45 http://mirror.einval.org/debian sid/main arm64 libemail-address-xs-perl arm64 1.05-1+b1 [28.3 kB]
Get:46 http://mirror.einval.org/debian sid/main arm64 libipc-system-simple-perl all 1.30-2 [26.8 kB]
Get:47 http://mirror.einval.org/debian sid/main arm64 libfile-basedir-perl all 0.09-2 [15.1 kB]
Get:48 http://mirror.einval.org/debian sid/main arm64 libfont-ttf-perl all 1.06-2 [318 kB]
Get:49 http://mirror.einval.org/debian sid/main arm64 libhtml-form-perl all 6.11-1 [33.1 kB]
Get:50 http://mirror.einval.org/debian sid/main arm64 libhtml-html5-entities-perl all 0.004-3 [21.0 kB]
Get:51 http://mirror.einval.org/debian sid/main arm64 libhtml-tokeparser-simple-perl all 3.16-4 [39.1 kB]
Get:52 http://mirror.einval.org/debian sid/main arm64 libimport-into-perl all 1.002005-2 [11.3 kB]
Get:53 http://mirror.einval.org/debian sid/main arm64 libio-interactive-perl all 1.023-2 [11.0 kB]
Get:54 http://mirror.einval.org/debian sid/main arm64 libipc-run3-perl all 0.048-3 [33.2 kB]
Get:55 http://mirror.einval.org/debian sid/main arm64 libjson-maybexs-perl all 1.004004-1 [13.3 kB]
Get:56 http://mirror.einval.org/debian sid/main arm64 liblist-compare-perl all 0.55-2 [65.7 kB]
Get:57 http://mirror.einval.org/debian sid/main arm64 liblist-someutils-perl all 0.59-1 [37.1 kB]
Get:58 http://mirror.einval.org/debian sid/main arm64 liblist-utilsby-perl all 0.12-2 [15.5 kB]
Get:59 http://mirror.einval.org/debian sid/main arm64 liblz1 arm64 1.13-5 [38.9 kB]
Get:60 http://mirror.einval.org/debian sid/main arm64 liblzo2-2 arm64 2.10-2 [51.8 kB]
Get:61 http://mirror.einval.org/debian sid/main arm64 libmarkdown2 arm64 2.2.7-2 [34.1 kB]
Get:62 http://mirror.einval.org/debian sid/main arm64 libmldbm-perl all 2.05-4 [16.8 kB]
Get:63 http://mirror.einval.org/debian sid/main arm64 librole-tiny-perl all 2.002004-1 [21.4 kB]
Get:64 http://mirror.einval.org/debian sid/main arm64 libsub-quote-perl all 2.006008-1 [21.8 kB]
Get:65 http://mirror.einval.org/debian sid/main arm64 libmoo-perl all 2.005005-1 [58.0 kB]
Get:66 http://mirror.einval.org/debian sid/main arm64 libstrictures-perl all 2.000006-1 [18.6 kB]
Get:67 http://mirror.einval.org/debian sid/main arm64 libmoox-aliases-perl all 0.001006-2 [7156 B]
Get:68 http://mirror.einval.org/debian sid/main arm64 libmouse-perl arm64 2.5.10-1+b3 [167 kB]
Get:69 http://mirror.einval.org/debian sid/main arm64 libpackage-stash-perl all 0.40-1 [22.0 kB]
Get:70 http://mirror.einval.org/debian sid/main arm64 libsub-identify-perl arm64 0.14-3 [10.9 kB]
Get:71 http://mirror.einval.org/debian sid/main arm64 libsub-name-perl arm64 0.26-2+b1 [12.4 kB]
Get:72 http://mirror.einval.org/debian sid/main arm64 libnamespace-clean-perl all 0.27-2 [17.8 kB]
Get:73 http://mirror.einval.org/debian sid/main arm64 libpath-tiny-perl all 0.144-1 [56.4 kB]
Get:74 http://mirror.einval.org/debian sid/main arm64 libperlio-gzip-perl arm64 0.20-1+b1 [17.1 kB]
Get:75 http://mirror.einval.org/debian sid/main arm64 libperlio-utf8-strict-perl arm64 0.010-1 [11.2 kB]
Get:76 http://mirror.einval.org/debian sid/main arm64 libproc-processtable-perl arm64 0.634-1+b2 [42.4 kB]
Get:77 http://mirror.einval.org/debian sid/main arm64 libregexp-wildcards-perl all 1.05-3 [14.1 kB]
Get:78 http://mirror.einval.org/debian sid/main arm64 libsereal-decoder-perl arm64 5.003+ds-1 [95.6 kB]
Get:79 http://mirror.einval.org/debian sid/main arm64 libsereal-encoder-perl arm64 5.003+ds-1 [97.1 kB]
Get:80 http://mirror.einval.org/debian sid/main arm64 libsort-versions-perl all 1.62-3 [8928 B]
Get:81 http://mirror.einval.org/debian sid/main arm64 libxs-parse-keyword-perl arm64 0.33-1 [57.0 kB]
Get:82 http://mirror.einval.org/debian sid/main arm64 libsyntax-keyword-try-perl arm64 0.28-1 [28.2 kB]
Get:83 http://mirror.einval.org/debian sid/main arm64 libterm-readkey-perl arm64 2.38-2+b1 [24.1 kB]
Get:84 http://mirror.einval.org/debian sid/main arm64 libtext-levenshteinxs-perl arm64 0.03-5+b1 [8396 B]
Get:85 http://mirror.einval.org/debian sid/main arm64 libtext-markdown-discount-perl arm64 0.16-1 [13.0 kB]
Get:86 http://mirror.einval.org/debian sid/main arm64 libtext-xslate-perl arm64 3.5.9-1+b2 [196 kB]
Get:87 http://mirror.einval.org/debian sid/main arm64 libtime-duration-perl all 1.21-2 [13.1 kB]
Get:88 http://mirror.einval.org/debian sid/main arm64 libtime-moment-perl arm64 0.44-2+b1 [72.2 kB]
Get:89 http://mirror.einval.org/debian sid/main arm64 libunicode-utf8-perl arm64 0.62-2 [19.9 kB]
Get:90 http://mirror.einval.org/debian sid/main arm64 libwww-mechanize-perl all 2.16-1 [116 kB]
Get:91 http://mirror.einval.org/debian sid/main arm64 libyaml-0-2 arm64 0.2.5-1 [50.4 kB]
Get:92 http://mirror.einval.org/debian sid/main arm64 libyaml-libyaml-perl arm64 0.86+ds-1 [32.8 kB]
Get:93 http://mirror.einval.org/debian sid/main arm64 plzip arm64 1.10-5 [58.0 kB]
Get:94 http://mirror.einval.org/debian sid/main arm64 lzop arm64 1.04-2 [82.8 kB]
Get:95 http://mirror.einval.org/debian sid/main arm64 patchutils arm64 0.4.2-1 [73.5 kB]
Get:96 http://mirror.einval.org/debian sid/main arm64 t1utils arm64 1.41-4 [59.8 kB]
Get:97 http://mirror.einval.org/debian sid/main arm64 unzip arm64 6.0-28 [157 kB]
Get:98 http://mirror.einval.org/debian sid/main arm64 lintian all 2.116.3 [1130 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 9478 kB in 0s (36.8 MB/s)
Selecting previously unselected package diffstat.
(Reading database ... 45883 files and directories currently installed.)
Preparing to unpack .../00-diffstat_1.65-1_arm64.deb ...
Unpacking diffstat (1.65-1) ...
Selecting previously unselected package libassuan0:arm64.
Preparing to unpack .../01-libassuan0_2.5.5-5_arm64.deb ...
Unpacking libassuan0:arm64 (2.5.5-5) ...
Selecting previously unselected package gpgconf.
Preparing to unpack .../02-gpgconf_2.2.40-1_arm64.deb ...
Unpacking gpgconf (2.2.40-1) ...
Selecting previously unselected package gpg.
Preparing to unpack .../03-gpg_2.2.40-1_arm64.deb ...
Unpacking gpg (2.2.40-1) ...
Selecting previously unselected package iso-codes.
Preparing to unpack .../04-iso-codes_4.13.0-1_all.deb ...
Unpacking iso-codes (4.13.0-1) ...
Selecting previously unselected package libaliased-perl.
Preparing to unpack .../05-libaliased-perl_0.34-3_all.deb ...
Unpacking libaliased-perl (0.34-3) ...
Selecting previously unselected package libapt-pkg-perl.
Preparing to unpack .../06-libapt-pkg-perl_0.1.40+b2_arm64.deb ...
Unpacking libapt-pkg-perl (0.1.40+b2) ...
Selecting previously unselected package libb-hooks-op-check-perl:arm64.
Preparing to unpack .../07-libb-hooks-op-check-perl_0.22-2+b1_arm64.deb ...
Unpacking libb-hooks-op-check-perl:arm64 (0.22-2+b1) ...
Selecting previously unselected package libdynaloader-functions-perl.
Preparing to unpack .../08-libdynaloader-functions-perl_0.003-3_all.deb ...
Unpacking libdynaloader-functions-perl (0.003-3) ...
Selecting previously unselected package libdevel-callchecker-perl:arm64.
Preparing to unpack .../09-libdevel-callchecker-perl_0.008-2_arm64.deb ...
Unpacking libdevel-callchecker-perl:arm64 (0.008-2) ...
Selecting previously unselected package libparams-classify-perl:arm64.
Preparing to unpack .../10-libparams-classify-perl_0.015-2+b1_arm64.deb ...
Unpacking libparams-classify-perl:arm64 (0.015-2+b1) ...
Selecting previously unselected package libmodule-runtime-perl.
Preparing to unpack .../11-libmodule-runtime-perl_0.016-2_all.deb ...
Unpacking libmodule-runtime-perl (0.016-2) ...
Selecting previously unselected package libmodule-implementation-perl.
Preparing to unpack .../12-libmodule-implementation-perl_0.09-2_all.deb ...
Unpacking libmodule-implementation-perl (0.09-2) ...
Selecting previously unselected package libsub-exporter-progressive-perl.
Preparing to unpack .../13-libsub-exporter-progressive-perl_0.001013-3_all.deb ...
Unpacking libsub-exporter-progressive-perl (0.001013-3) ...
Selecting previously unselected package libvariable-magic-perl.
Preparing to unpack .../14-libvariable-magic-perl_0.63-1+b1_arm64.deb ...
Unpacking libvariable-magic-perl (0.63-1+b1) ...
Selecting previously unselected package libb-hooks-endofscope-perl.
Preparing to unpack .../15-libb-hooks-endofscope-perl_0.26-1_all.deb ...
Unpacking libb-hooks-endofscope-perl (0.26-1) ...
Selecting previously unselected package libberkeleydb-perl:arm64.
Preparing to unpack .../16-libberkeleydb-perl_0.64-2+b1_arm64.deb ...
Unpacking libberkeleydb-perl:arm64 (0.64-2+b1) ...
Selecting previously unselected package libcapture-tiny-perl.
Preparing to unpack .../17-libcapture-tiny-perl_0.48-2_all.deb ...
Unpacking libcapture-tiny-perl (0.48-2) ...
Selecting previously unselected package libcgi-pm-perl.
Preparing to unpack .../18-libcgi-pm-perl_4.55-1_all.deb ...
Unpacking libcgi-pm-perl (4.55-1) ...
Selecting previously unselected package libclass-data-inheritable-perl.
Preparing to unpack .../19-libclass-data-inheritable-perl_0.08-3_all.deb ...
Unpacking libclass-data-inheritable-perl (0.08-3) ...
Selecting previously unselected package libclass-method-modifiers-perl.
Preparing to unpack .../20-libclass-method-modifiers-perl_2.14-1_all.deb ...
Unpacking libclass-method-modifiers-perl (2.14-1) ...
Selecting previously unselected package libclass-xsaccessor-perl.
Preparing to unpack .../21-libclass-xsaccessor-perl_1.19-4+b1_arm64.deb ...
Unpacking libclass-xsaccessor-perl (1.19-4+b1) ...
Selecting previously unselected package libconfig-tiny-perl.
Preparing to unpack .../22-libconfig-tiny-perl_2.28-2_all.deb ...
Unpacking libconfig-tiny-perl (2.28-2) ...
Selecting previously unselected package libparams-util-perl.
Preparing to unpack .../23-libparams-util-perl_1.102-2+b1_arm64.deb ...
Unpacking libparams-util-perl (1.102-2+b1) ...
Selecting previously unselected package libsub-install-perl.
Preparing to unpack .../24-libsub-install-perl_0.929-1_all.deb ...
Unpacking libsub-install-perl (0.929-1) ...
Selecting previously unselected package libdata-optlist-perl.
Preparing to unpack .../25-libdata-optlist-perl_0.113-1_all.deb ...
Unpacking libdata-optlist-perl (0.113-1) ...
Selecting previously unselected package libsub-exporter-perl.
Preparing to unpack .../26-libsub-exporter-perl_0.989-1_all.deb ...
Unpacking libsub-exporter-perl (0.989-1) ...
Selecting previously unselected package libconst-fast-perl.
Preparing to unpack .../27-libconst-fast-perl_0.014-2_all.deb ...
Unpacking libconst-fast-perl (0.014-2) ...
Selecting previously unselected package libcpanel-json-xs-perl:arm64.
Preparing to unpack .../28-libcpanel-json-xs-perl_4.35-1_arm64.deb ...
Unpacking libcpanel-json-xs-perl:arm64 (4.35-1) ...
Selecting previously unselected package libdevel-stacktrace-perl.
Preparing to unpack .../29-libdevel-stacktrace-perl_2.0400-2_all.deb ...
Unpacking libdevel-stacktrace-perl (2.0400-2) ...
Selecting previously unselected package libexception-class-perl.
Preparing to unpack .../30-libexception-class-perl_1.45-1_all.deb ...
Unpacking libexception-class-perl (1.45-1) ...
Selecting previously unselected package libiterator-perl.
Preparing to unpack .../31-libiterator-perl_0.03+ds1-2_all.deb ...
Unpacking libiterator-perl (0.03+ds1-2) ...
Selecting previously unselected package libiterator-util-perl.
Preparing to unpack .../32-libiterator-util-perl_0.02+ds1-2_all.deb ...
Unpacking libiterator-util-perl (0.02+ds1-2) ...
Selecting previously unselected package libdata-dpath-perl.
Preparing to unpack .../33-libdata-dpath-perl_0.58-2_all.deb ...
Unpacking libdata-dpath-perl (0.58-2) ...
Selecting previously unselected package libdata-messagepack-perl.
Preparing to unpack .../34-libdata-messagepack-perl_1.02-1+b1_arm64.deb ...
Unpacking libdata-messagepack-perl (1.02-1+b1) ...
Selecting previously unselected package libnet-domain-tld-perl.
Preparing to unpack .../35-libnet-domain-tld-perl_1.75-3_all.deb ...
Unpacking libnet-domain-tld-perl (1.75-3) ...
Selecting previously unselected package libdata-validate-domain-perl.
Preparing to unpack .../36-libdata-validate-domain-perl_0.10-1.1_all.deb ...
Unpacking libdata-validate-domain-perl (0.10-1.1) ...
Selecting previously unselected package libnet-ipv6addr-perl.
Preparing to unpack .../37-libnet-ipv6addr-perl_1.02-1_all.deb ...
Unpacking libnet-ipv6addr-perl (1.02-1) ...
Selecting previously unselected package libnet-netmask-perl.
Preparing to unpack .../38-libnet-netmask-perl_2.0002-2_all.deb ...
Unpacking libnet-netmask-perl (2.0002-2) ...
Selecting previously unselected package libnetaddr-ip-perl.
Preparing to unpack .../39-libnetaddr-ip-perl_4.079+dfsg-2+b1_arm64.deb ...
Unpacking libnetaddr-ip-perl (4.079+dfsg-2+b1) ...
Selecting previously unselected package libdata-validate-ip-perl.
Preparing to unpack .../40-libdata-validate-ip-perl_0.31-1_all.deb ...
Unpacking libdata-validate-ip-perl (0.31-1) ...
Selecting previously unselected package libdata-validate-uri-perl.
Preparing to unpack .../41-libdata-validate-uri-perl_0.07-2_all.deb ...
Unpacking libdata-validate-uri-perl (0.07-2) ...
Selecting previously unselected package libdevel-size-perl.
Preparing to unpack .../42-libdevel-size-perl_0.83-2+b1_arm64.deb ...
Unpacking libdevel-size-perl (0.83-2+b1) ...
Selecting previously unselected package libemail-address-xs-perl.
Preparing to unpack .../43-libemail-address-xs-perl_1.05-1+b1_arm64.deb ...
Unpacking libemail-address-xs-perl (1.05-1+b1) ...
Selecting previously unselected package libipc-system-simple-perl.
Preparing to unpack .../44-libipc-system-simple-perl_1.30-2_all.deb ...
Unpacking libipc-system-simple-perl (1.30-2) ...
Selecting previously unselected package libfile-basedir-perl.
Preparing to unpack .../45-libfile-basedir-perl_0.09-2_all.deb ...
Unpacking libfile-basedir-perl (0.09-2) ...
Selecting previously unselected package libfont-ttf-perl.
Preparing to unpack .../46-libfont-ttf-perl_1.06-2_all.deb ...
Unpacking libfont-ttf-perl (1.06-2) ...
Selecting previously unselected package libhtml-form-perl.
Preparing to unpack .../47-libhtml-form-perl_6.11-1_all.deb ...
Unpacking libhtml-form-perl (6.11-1) ...
Selecting previously unselected package libhtml-html5-entities-perl.
Preparing to unpack .../48-libhtml-html5-entities-perl_0.004-3_all.deb ...
Unpacking libhtml-html5-entities-perl (0.004-3) ...
Selecting previously unselected package libhtml-tokeparser-simple-perl.
Preparing to unpack .../49-libhtml-tokeparser-simple-perl_3.16-4_all.deb ...
Unpacking libhtml-tokeparser-simple-perl (3.16-4) ...
Selecting previously unselected package libimport-into-perl.
Preparing to unpack .../50-libimport-into-perl_1.002005-2_all.deb ...
Unpacking libimport-into-perl (1.002005-2) ...
Selecting previously unselected package libio-interactive-perl.
Preparing to unpack .../51-libio-interactive-perl_1.023-2_all.deb ...
Unpacking libio-interactive-perl (1.023-2) ...
Selecting previously unselected package libipc-run3-perl.
Preparing to unpack .../52-libipc-run3-perl_0.048-3_all.deb ...
Unpacking libipc-run3-perl (0.048-3) ...
Selecting previously unselected package libjson-maybexs-perl.
Preparing to unpack .../53-libjson-maybexs-perl_1.004004-1_all.deb ...
Unpacking libjson-maybexs-perl (1.004004-1) ...
Selecting previously unselected package liblist-compare-perl.
Preparing to unpack .../54-liblist-compare-perl_0.55-2_all.deb ...
Unpacking liblist-compare-perl (0.55-2) ...
Selecting previously unselected package liblist-someutils-perl.
Preparing to unpack .../55-liblist-someutils-perl_0.59-1_all.deb ...
Unpacking liblist-someutils-perl (0.59-1) ...
Selecting previously unselected package liblist-utilsby-perl.
Preparing to unpack .../56-liblist-utilsby-perl_0.12-2_all.deb ...
Unpacking liblist-utilsby-perl (0.12-2) ...
Selecting previously unselected package liblz1:arm64.
Preparing to unpack .../57-liblz1_1.13-5_arm64.deb ...
Unpacking liblz1:arm64 (1.13-5) ...
Selecting previously unselected package liblzo2-2:arm64.
Preparing to unpack .../58-liblzo2-2_2.10-2_arm64.deb ...
Unpacking liblzo2-2:arm64 (2.10-2) ...
Selecting previously unselected package libmarkdown2:arm64.
Preparing to unpack .../59-libmarkdown2_2.2.7-2_arm64.deb ...
Unpacking libmarkdown2:arm64 (2.2.7-2) ...
Selecting previously unselected package libmldbm-perl.
Preparing to unpack .../60-libmldbm-perl_2.05-4_all.deb ...
Unpacking libmldbm-perl (2.05-4) ...
Selecting previously unselected package librole-tiny-perl.
Preparing to unpack .../61-librole-tiny-perl_2.002004-1_all.deb ...
Unpacking librole-tiny-perl (2.002004-1) ...
Selecting previously unselected package libsub-quote-perl.
Preparing to unpack .../62-libsub-quote-perl_2.006008-1_all.deb ...
Unpacking libsub-quote-perl (2.006008-1) ...
Selecting previously unselected package libmoo-perl.
Preparing to unpack .../63-libmoo-perl_2.005005-1_all.deb ...
Unpacking libmoo-perl (2.005005-1) ...
Selecting previously unselected package libstrictures-perl.
Preparing to unpack .../64-libstrictures-perl_2.000006-1_all.deb ...
Unpacking libstrictures-perl (2.000006-1) ...
Selecting previously unselected package libmoox-aliases-perl.
Preparing to unpack .../65-libmoox-aliases-perl_0.001006-2_all.deb ...
Unpacking libmoox-aliases-perl (0.001006-2) ...
Selecting previously unselected package libmouse-perl.
Preparing to unpack .../66-libmouse-perl_2.5.10-1+b3_arm64.deb ...
Unpacking libmouse-perl (2.5.10-1+b3) ...
Selecting previously unselected package libpackage-stash-perl.
Preparing to unpack .../67-libpackage-stash-perl_0.40-1_all.deb ...
Unpacking libpackage-stash-perl (0.40-1) ...
Selecting previously unselected package libsub-identify-perl.
Preparing to unpack .../68-libsub-identify-perl_0.14-3_arm64.deb ...
Unpacking libsub-identify-perl (0.14-3) ...
Selecting previously unselected package libsub-name-perl:arm64.
Preparing to unpack .../69-libsub-name-perl_0.26-2+b1_arm64.deb ...
Unpacking libsub-name-perl:arm64 (0.26-2+b1) ...
Selecting previously unselected package libnamespace-clean-perl.
Preparing to unpack .../70-libnamespace-clean-perl_0.27-2_all.deb ...
Unpacking libnamespace-clean-perl (0.27-2) ...
Selecting previously unselected package libpath-tiny-perl.
Preparing to unpack .../71-libpath-tiny-perl_0.144-1_all.deb ...
Unpacking libpath-tiny-perl (0.144-1) ...
Selecting previously unselected package libperlio-gzip-perl.
Preparing to unpack .../72-libperlio-gzip-perl_0.20-1+b1_arm64.deb ...
Unpacking libperlio-gzip-perl (0.20-1+b1) ...
Selecting previously unselected package libperlio-utf8-strict-perl.
Preparing to unpack .../73-libperlio-utf8-strict-perl_0.010-1_arm64.deb ...
Unpacking libperlio-utf8-strict-perl (0.010-1) ...
Selecting previously unselected package libproc-processtable-perl:arm64.
Preparing to unpack .../74-libproc-processtable-perl_0.634-1+b2_arm64.deb ...
Unpacking libproc-processtable-perl:arm64 (0.634-1+b2) ...
Selecting previously unselected package libregexp-wildcards-perl.
Preparing to unpack .../75-libregexp-wildcards-perl_1.05-3_all.deb ...
Unpacking libregexp-wildcards-perl (1.05-3) ...
Selecting previously unselected package libsereal-decoder-perl.
Preparing to unpack .../76-libsereal-decoder-perl_5.003+ds-1_arm64.deb ...
Unpacking libsereal-decoder-perl (5.003+ds-1) ...
Selecting previously unselected package libsereal-encoder-perl.
Preparing to unpack .../77-libsereal-encoder-perl_5.003+ds-1_arm64.deb ...
Unpacking libsereal-encoder-perl (5.003+ds-1) ...
Selecting previously unselected package libsort-versions-perl.
Preparing to unpack .../78-libsort-versions-perl_1.62-3_all.deb ...
Unpacking libsort-versions-perl (1.62-3) ...
Selecting previously unselected package libxs-parse-keyword-perl.
Preparing to unpack .../79-libxs-parse-keyword-perl_0.33-1_arm64.deb ...
Unpacking libxs-parse-keyword-perl (0.33-1) ...
Selecting previously unselected package libsyntax-keyword-try-perl.
Preparing to unpack .../80-libsyntax-keyword-try-perl_0.28-1_arm64.deb ...
Unpacking libsyntax-keyword-try-perl (0.28-1) ...
Selecting previously unselected package libterm-readkey-perl.
Preparing to unpack .../81-libterm-readkey-perl_2.38-2+b1_arm64.deb ...
Unpacking libterm-readkey-perl (2.38-2+b1) ...
Selecting previously unselected package libtext-levenshteinxs-perl.
Preparing to unpack .../82-libtext-levenshteinxs-perl_0.03-5+b1_arm64.deb ...
Unpacking libtext-levenshteinxs-perl (0.03-5+b1) ...
Selecting previously unselected package libtext-markdown-discount-perl.
Preparing to unpack .../83-libtext-markdown-discount-perl_0.16-1_arm64.deb ...
Unpacking libtext-markdown-discount-perl (0.16-1) ...
Selecting previously unselected package libtext-xslate-perl:arm64.
Preparing to unpack .../84-libtext-xslate-perl_3.5.9-1+b2_arm64.deb ...
Unpacking libtext-xslate-perl:arm64 (3.5.9-1+b2) ...
Selecting previously unselected package libtime-duration-perl.
Preparing to unpack .../85-libtime-duration-perl_1.21-2_all.deb ...
Unpacking libtime-duration-perl (1.21-2) ...
Selecting previously unselected package libtime-moment-perl.
Preparing to unpack .../86-libtime-moment-perl_0.44-2+b1_arm64.deb ...
Unpacking libtime-moment-perl (0.44-2+b1) ...
Selecting previously unselected package libunicode-utf8-perl.
Preparing to unpack .../87-libunicode-utf8-perl_0.62-2_arm64.deb ...
Unpacking libunicode-utf8-perl (0.62-2) ...
Selecting previously unselected package libwww-mechanize-perl.
Preparing to unpack .../88-libwww-mechanize-perl_2.16-1_all.deb ...
Unpacking libwww-mechanize-perl (2.16-1) ...
Selecting previously unselected package libyaml-0-2:arm64.
Preparing to unpack .../89-libyaml-0-2_0.2.5-1_arm64.deb ...
Unpacking libyaml-0-2:arm64 (0.2.5-1) ...
Selecting previously unselected package libyaml-libyaml-perl.
Preparing to unpack .../90-libyaml-libyaml-perl_0.86+ds-1_arm64.deb ...
Unpacking libyaml-libyaml-perl (0.86+ds-1) ...
Selecting previously unselected package plzip.
Preparing to unpack .../91-plzip_1.10-5_arm64.deb ...
Unpacking plzip (1.10-5) ...
Selecting previously unselected package lzop.
Preparing to unpack .../92-lzop_1.04-2_arm64.deb ...
Unpacking lzop (1.04-2) ...
Selecting previously unselected package patchutils.
Preparing to unpack .../93-patchutils_0.4.2-1_arm64.deb ...
Unpacking patchutils (0.4.2-1) ...
Selecting previously unselected package t1utils.
Preparing to unpack .../94-t1utils_1.41-4_arm64.deb ...
Unpacking t1utils (1.41-4) ...
Selecting previously unselected package unzip.
Preparing to unpack .../95-unzip_6.0-28_arm64.deb ...
Unpacking unzip (6.0-28) ...
Selecting previously unselected package lintian.
Preparing to unpack .../96-lintian_2.116.3_all.deb ...
Unpacking lintian (2.116.3) ...
Selecting previously unselected package sbuild-build-depends-lintian-dummy:i386.
Preparing to unpack .../97-sbuild-build-depends-lintian-dummy_0.invalid.0_i386.deb ...
Unpacking sbuild-build-depends-lintian-dummy:i386 (0.invalid.0) ...
Setting up libapt-pkg-perl (0.1.40+b2) ...
Setting up liblz1:arm64 (1.13-5) ...
Setting up libberkeleydb-perl:arm64 (0.64-2+b1) ...
Setting up plzip (1.10-5) ...
update-alternatives: using /usr/bin/lzip.plzip to provide /usr/bin/lzip (lzip) in auto mode
update-alternatives: using /usr/bin/lzip.plzip to provide /usr/bin/lzip-compressor (lzip-compressor) in auto mode
update-alternatives: using /usr/bin/lzip.plzip to provide /usr/bin/lzip-decompressor (lzip-decompressor) in auto mode
Setting up libunicode-utf8-perl (0.62-2) ...
Setting up libmouse-perl (2.5.10-1+b3) ...
Setting up libdata-messagepack-perl (1.02-1+b1) ...
Setting up libdynaloader-functions-perl (0.003-3) ...
Setting up libclass-method-modifiers-perl (2.14-1) ...
Setting up liblist-compare-perl (0.55-2) ...
Setting up libyaml-0-2:arm64 (0.2.5-1) ...
Setting up libsub-identify-perl (0.14-3) ...
Setting up libcpanel-json-xs-perl:arm64 (4.35-1) ...
Setting up libdevel-size-perl (0.83-2+b1) ...
Setting up unzip (6.0-28) ...
Setting up libcgi-pm-perl (4.55-1) ...
Setting up libyaml-libyaml-perl (0.86+ds-1) ...
Setting up libio-interactive-perl (1.023-2) ...
Setting up libmldbm-perl (2.05-4) ...
Setting up liblzo2-2:arm64 (2.10-2) ...
Setting up libtime-moment-perl (0.44-2+b1) ...
Setting up libassuan0:arm64 (2.5.5-5) ...
Setting up libconfig-tiny-perl (2.28-2) ...
Setting up libsereal-encoder-perl (5.003+ds-1) ...
Setting up liblist-utilsby-perl (0.12-2) ...
Setting up libnet-netmask-perl (2.0002-2) ...
Setting up libsub-install-perl (0.929-1) ...
Setting up libhtml-tokeparser-simple-perl (3.16-4) ...
Setting up patchutils (0.4.2-1) ...
Setting up libjson-maybexs-perl (1.004004-1) ...
Setting up libnetaddr-ip-perl (4.079+dfsg-2+b1) ...
Setting up libclass-data-inheritable-perl (0.08-3) ...
Setting up libxs-parse-keyword-perl (0.33-1) ...
Setting up libipc-system-simple-perl (1.30-2) ...
Setting up libnet-domain-tld-perl (1.75-3) ...
Setting up libperlio-utf8-strict-perl (0.010-1) ...
Setting up t1utils (1.41-4) ...
Setting up diffstat (1.65-1) ...
Setting up libvariable-magic-perl (0.63-1+b1) ...
Setting up libb-hooks-op-check-perl:arm64 (0.22-2+b1) ...
Setting up libparams-util-perl (1.102-2+b1) ...
Setting up libtime-duration-perl (1.21-2) ...
Setting up libtext-xslate-perl:arm64 (3.5.9-1+b2) ...
Setting up libsub-exporter-progressive-perl (0.001013-3) ...
Setting up libcapture-tiny-perl (0.48-2) ...
Setting up libsub-name-perl:arm64 (0.26-2+b1) ...
Setting up libsyntax-keyword-try-perl (0.28-1) ...
Setting up libdata-validate-domain-perl (0.10-1.1) ...
Setting up libproc-processtable-perl:arm64 (0.634-1+b2) ...
Setting up libpath-tiny-perl (0.144-1) ...
Setting up lzop (1.04-2) ...
Setting up gpgconf (2.2.40-1) ...
Setting up librole-tiny-perl (2.002004-1) ...
Setting up libipc-run3-perl (0.048-3) ...
Setting up libregexp-wildcards-perl (1.05-3) ...
Setting up libaliased-perl (0.34-3) ...
Setting up libstrictures-perl (2.000006-1) ...
Setting up libsub-quote-perl (2.006008-1) ...
Setting up libdevel-stacktrace-perl (2.0400-2) ...
Setting up libclass-xsaccessor-perl (1.19-4+b1) ...
Setting up libsort-versions-perl (1.62-3) ...
Setting up libterm-readkey-perl (2.38-2+b1) ...
Setting up libfont-ttf-perl (1.06-2) ...
Setting up libtext-levenshteinxs-perl (0.03-5+b1) ...
Setting up libperlio-gzip-perl (0.20-1+b1) ...
Setting up libhtml-html5-entities-perl (0.004-3) ...
Setting up libsereal-decoder-perl (5.003+ds-1) ...
Setting up libmarkdown2:arm64 (2.2.7-2) ...
Setting up iso-codes (4.13.0-1) ...
Setting up libnet-ipv6addr-perl (1.02-1) ...
Setting up gpg (2.2.40-1) ...
Setting up libdata-validate-ip-perl (0.31-1) ...
Setting up libhtml-form-perl (6.11-1) ...
Setting up libemail-address-xs-perl (1.05-1+b1) ...
Setting up libfile-basedir-perl (0.09-2) ...
Setting up libtext-markdown-discount-perl (0.16-1) ...
Setting up libexception-class-perl (1.45-1) ...
Setting up libdevel-callchecker-perl:arm64 (0.008-2) ...
Setting up libdata-validate-uri-perl (0.07-2) ...
Setting up libwww-mechanize-perl (2.16-1) ...
Setting up libdata-optlist-perl (0.113-1) ...
Setting up libsub-exporter-perl (0.989-1) ...
Setting up libiterator-perl (0.03+ds1-2) ...
Setting up libiterator-util-perl (0.02+ds1-2) ...
Setting up libparams-classify-perl:arm64 (0.015-2+b1) ...
Setting up libmodule-runtime-perl (0.016-2) ...
Setting up libconst-fast-perl (0.014-2) ...
Setting up libdata-dpath-perl (0.58-2) ...
Setting up libmodule-implementation-perl (0.09-2) ...
Setting up libpackage-stash-perl (0.40-1) ...
Setting up libimport-into-perl (1.002005-2) ...
Setting up libmoo-perl (2.005005-1) ...
Setting up liblist-someutils-perl (0.59-1) ...
Setting up libmoox-aliases-perl (0.001006-2) ...
Setting up libb-hooks-endofscope-perl (0.26-1) ...
Setting up libnamespace-clean-perl (0.27-2) ...
Processing triggers for man-db (2.11.2-1) ...
Not building database; man-db/auto-update is not 'true'.
Processing triggers for sgml-base (1.31) ...
Processing triggers for libc-bin (2.36-8) ...
Setting up lintian (2.116.3) ...
Setting up sbuild-build-depends-lintian-dummy:i386 (0.invalid.0) ...

I: Lintian run was successful.

+------------------------------------------------------------------------------+
| Post Build                                                                   |
+------------------------------------------------------------------------------+


+------------------------------------------------------------------------------+
| Cleanup                                                                      |
+------------------------------------------------------------------------------+

Purging /<<BUILDDIR>>
Not cleaning session: cloned chroot in use

+------------------------------------------------------------------------------+
| Summary                                                                      |
+------------------------------------------------------------------------------+

Build Architecture: arm64
Build Profiles: cross nocheck
Build Type: any
Build-Space: 7864
Build-Time: 53
Distribution: unstable
Foreign Architectures: i386
Host Architecture: i386
Install-Time: 303
Job: alarm-clock-applet_0.4.1-3
Lintian: pass
Machine Architecture: arm64
Package: alarm-clock-applet
Package-Time: 392
Source-Version: 0.4.1-3
Space: 7864
Status: successful
Version: 0.4.1-3
--------------------------------------------------------------------------------
Finished at 2023-03-08T11:08:16Z
Build needed 00:06:32, 7864k disk space