Warning: Permanently added '2620:52:3:1:dead:beef:cafe:c150' (ED25519) to the list of known hosts. Running: /usr/bin/copr-rpmbuild --verbose --drop-resultdir --build-id 4688546 --chroot epel-7-x86_64 --detached Version: 0.60 PID: 5931 Logging PID: 5932 Task: {'appstream': True, 'background': False, 'bootstrap': 'on', 'build_id': 4688546, 'buildroot_pkgs': [], 'chroot': 'epel-7-x86_64', 'enable_net': True, 'fedora_review': False, 'git_hash': '45a9f813cb3fb7cf97f4399e1523f795e1af3b67', 'git_repo': 'https://copr-dist-git.fedorainfracloud.org/git/vomaraz/Alarm-Clock/alarm-clock', 'isolation': 'default', 'memory_reqs': 2048, 'package_name': 'alarm-clock', 'package_version': 'master-1', 'project_dirname': 'Alarm-Clock', 'project_name': 'Alarm-Clock', 'project_owner': 'vomaraz', 'repos': [{'baseurl': 'https://download.copr.fedorainfracloud.org/results/vomaraz/Alarm-Clock/epel-7-x86_64/', 'id': 'copr_base', 'name': 'Copr repository'}], 'sandbox': 'vomaraz/Alarm-Clock--vomaraz', 'source_json': {}, 'source_type': None, 'submitter': 'vomaraz', 'tags': [], 'task_id': '4688546-epel-7-x86_64', 'timeout': 18000, 'uses_devel_repo': False, 'with_opts': [], 'without_opts': []} Running: git clone https://copr-dist-git.fedorainfracloud.org/git/vomaraz/Alarm-Clock/alarm-clock /var/lib/copr-rpmbuild/workspace/workdir-sgcn9yk_/alarm-clock --depth 500 --no-single-branch --recursive cmd: ['git', 'clone', 'https://copr-dist-git.fedorainfracloud.org/git/vomaraz/Alarm-Clock/alarm-clock', '/var/lib/copr-rpmbuild/workspace/workdir-sgcn9yk_/alarm-clock', '--depth', '500', '--no-single-branch', '--recursive'] cwd: . rc: 0 stdout: stderr: Cloning into '/var/lib/copr-rpmbuild/workspace/workdir-sgcn9yk_/alarm-clock'... Running: git checkout 45a9f813cb3fb7cf97f4399e1523f795e1af3b67 cmd: ['git', 'checkout', '45a9f813cb3fb7cf97f4399e1523f795e1af3b67'] cwd: /var/lib/copr-rpmbuild/workspace/workdir-sgcn9yk_/alarm-clock rc: 0 stdout: stderr: Note: switching to '45a9f813cb3fb7cf97f4399e1523f795e1af3b67'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by switching back to a branch. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -c with the switch command. Example: git switch -c Or undo this operation with: git switch - Turn off this advice by setting config variable advice.detachedHead to false HEAD is now at 45a9f81 automatic import of alarm-clock Running: copr-distgit-client sources cmd: ['copr-distgit-client', 'sources'] cwd: /var/lib/copr-rpmbuild/workspace/workdir-sgcn9yk_/alarm-clock rc: 0 stdout: stderr: INFO: Reading stdout from command: git rev-parse --abbrev-ref HEAD INFO: Reading stdout from command: git rev-parse HEAD INFO: Reading sources specification file: sources INFO: Downloading master.zip INFO: Calling: curl -H Pragma: -o master.zip --location --remote-time --show-error --fail https://copr-dist-git.fedorainfracloud.org/repo/pkgs/vomaraz/Alarm-Clock/alarm-clock/master.zip/md5/f6f79e5b7f1020acd91fef3e8b98f984/master.zip % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 283k 100 283k 0 0 4148k 0 --:--:-- --:--:-- --:--:-- 4163k INFO: Reading stdout from command: md5sum master.zip /usr/bin/tail: /var/lib/copr-rpmbuild/main.log: file truncated Running (timeout=18000): unbuffer mock --buildsrpm --spec /var/lib/copr-rpmbuild/workspace/workdir-sgcn9yk_/alarm-clock/gnome-applet-alarm-clock-0.3.4.fc23.x86_64.spec --sources /var/lib/copr-rpmbuild/workspace/workdir-sgcn9yk_/alarm-clock --resultdir /var/lib/copr-rpmbuild/results --uniqueext 1658945077.221752 -r /var/lib/copr-rpmbuild/results/configs/child.cfg INFO: mock.py version 3.0 starting (python version = 3.10.4, NVR = mock-3.0-1.fc35)... INFO: Using 'dnf' instead of 'yum' for bootstrap chroot Start(bootstrap): init plugins INFO: tmpfs initialized INFO: selinux enabled INFO: chroot_scan: initialized INFO: compress_logs: initialized Finish(bootstrap): init plugins Start: init plugins INFO: tmpfs initialized INFO: selinux enabled INFO: chroot_scan: initialized INFO: compress_logs: initialized Finish: init plugins INFO: Signal handler active Start: run INFO: Start(/var/lib/copr-rpmbuild/workspace/workdir-sgcn9yk_/alarm-clock/gnome-applet-alarm-clock-0.3.4.fc23.x86_64.spec) Config(centos+epel-7-x86_64) Start: clean chroot Finish: clean chroot Start(bootstrap): chroot init INFO: mounting tmpfs at /var/lib/mock/centos+epel-7-x86_64-bootstrap-1658945077.221752/root. INFO: calling preinit hooks INFO: enabled root cache INFO: enabled package manager cache Start(bootstrap): cleaning package manager metadata Finish(bootstrap): cleaning package manager metadata INFO: enabled HW Info plugin Mock Version: 3.0 INFO: Mock Version: 3.0 Start(bootstrap): dnf install No matches found for the following disable plugin patterns: local, spacewalk, versionlock Updating Subscription Management repositories. Unable to read consumer identity This system is not registered with an entitlement server. You can use subscription-manager to register. Copr repository 21 kB/s | 2.8 kB 00:00 CentOS-7 - Base 19 MB/s | 10 MB 00:00 CentOS-7 - Updates 16 MB/s | 20 MB 00:01 CentOS-7 - Extras 909 kB/s | 331 kB 00:00 Extra Packages for Enterprise Linux 7 - x86_64 13 MB/s | 17 MB 00:01 Dependencies resolved. ================================================================================ Package Arch Version Repo Size ================================================================================ Installing: yum noarch 3.4.3-168.el7.centos base 1.2 M yum-utils noarch 1.1.31-54.el7_8 base 122 k Installing dependencies: audit-libs x86_64 2.8.5-4.el7 base 102 k basesystem noarch 10.0-7.el7.centos base 5.0 k bash x86_64 4.2.46-35.el7_9 updates 1.0 M bzip2-libs x86_64 1.0.6-13.el7 base 40 k ca-certificates noarch 2021.2.50-72.el7_9 updates 379 k centos-release x86_64 7-9.2009.1.el7.centos updates 27 k chkconfig x86_64 1.7.6-1.el7 base 182 k coreutils x86_64 8.22-24.el7_9.2 updates 3.3 M cpio x86_64 2.11-28.el7 base 211 k curl x86_64 7.29.0-59.el7_9.1 updates 271 k cyrus-sasl-lib x86_64 2.1.26-24.el7_9 updates 156 k diffutils x86_64 3.3-5.el7 base 322 k elfutils-libelf x86_64 0.176-5.el7 base 195 k expat x86_64 2.1.0-14.el7_9 updates 83 k file-libs x86_64 5.11-37.el7 base 340 k filesystem x86_64 3.2-25.el7 base 1.0 M findutils x86_64 1:4.5.11-6.el7 base 559 k gawk x86_64 4.0.2-4.el7_3.1 base 874 k gdbm x86_64 1.10-8.el7 base 70 k glib2 x86_64 2.56.1-9.el7_9 updates 2.5 M glibc x86_64 2.17-326.el7_9 updates 3.6 M glibc-common x86_64 2.17-326.el7_9 updates 12 M gmp x86_64 1:6.0.0-15.el7 base 281 k gnupg2 x86_64 2.0.22-5.el7_5 base 1.5 M gpgme x86_64 1.3.2-5.el7 base 146 k grep x86_64 2.20-3.el7 base 344 k info x86_64 5.1-5.el7 base 233 k keyutils-libs x86_64 1.5.8-3.el7 base 25 k krb5-libs x86_64 1.15.1-54.el7_9 updates 810 k libacl x86_64 2.2.51-15.el7 base 27 k libassuan x86_64 2.1.0-3.el7 base 63 k libattr x86_64 2.4.46-13.el7 base 18 k libblkid x86_64 2.23.2-65.el7_9.1 updates 183 k libcap x86_64 2.22-11.el7 base 47 k libcap-ng x86_64 0.7.5-4.el7 base 25 k libcom_err x86_64 1.42.9-19.el7 base 42 k libcurl x86_64 7.29.0-59.el7_9.1 updates 223 k libdb x86_64 5.3.21-25.el7 base 720 k libdb-utils x86_64 5.3.21-25.el7 base 132 k libffi x86_64 3.0.13-19.el7 base 30 k libgcc x86_64 4.8.5-44.el7 base 103 k libgcrypt x86_64 1.5.3-14.el7 base 263 k libgpg-error x86_64 1.12-3.el7 base 87 k libidn x86_64 1.28-4.el7 base 209 k libmount x86_64 2.23.2-65.el7_9.1 updates 185 k libselinux x86_64 2.5-15.el7 base 162 k libsepol x86_64 2.5-10.el7 base 297 k libssh2 x86_64 1.8.0-4.el7 base 88 k libstdc++ x86_64 4.8.5-44.el7 base 306 k libtasn1 x86_64 4.10-1.el7 base 320 k libuuid x86_64 2.23.2-65.el7_9.1 updates 84 k libverto x86_64 0.2.5-4.el7 base 16 k libxml2 x86_64 2.9.1-6.el7_9.6 updates 668 k libxml2-python x86_64 2.9.1-6.el7_9.6 updates 247 k lua x86_64 5.1.4-15.el7 base 201 k ncurses x86_64 5.9-14.20130511.el7_4 base 304 k ncurses-base noarch 5.9-14.20130511.el7_4 base 68 k ncurses-libs x86_64 5.9-14.20130511.el7_4 base 316 k nspr x86_64 4.32.0-1.el7_9 updates 127 k nss x86_64 3.67.0-4.el7_9 updates 882 k nss-pem x86_64 1.0.3-7.el7 base 74 k nss-softokn x86_64 3.67.0-3.el7_9 updates 358 k nss-softokn-freebl x86_64 3.67.0-3.el7_9 updates 337 k nss-sysinit x86_64 3.67.0-4.el7_9 updates 66 k nss-tools x86_64 3.67.0-4.el7_9 updates 549 k nss-util x86_64 3.67.0-1.el7_9 updates 79 k openldap x86_64 2.4.44-25.el7_9 updates 356 k openssl-libs x86_64 1:1.0.2k-25.el7_9 updates 1.2 M p11-kit x86_64 0.23.5-3.el7 base 252 k p11-kit-trust x86_64 0.23.5-3.el7 base 129 k pcre x86_64 8.32-17.el7 base 422 k pinentry x86_64 0.8.1-17.el7 base 73 k popt x86_64 1.13-16.el7 base 42 k pth x86_64 2.0.7-23.el7 base 89 k pygpgme x86_64 0.3-9.el7 base 63 k pyliblzma x86_64 0.5.3-11.el7 base 47 k python x86_64 2.7.5-92.el7_9 updates 96 k python-chardet noarch 2.2.1-3.el7 base 227 k python-iniparse noarch 0.4-9.el7 base 39 k python-kitchen noarch 1.1.1-5.el7 base 267 k python-libs x86_64 2.7.5-92.el7_9 updates 5.6 M python-pycurl x86_64 7.19.0-19.el7 base 80 k python-urlgrabber noarch 3.10-10.el7 base 108 k pyxattr x86_64 0.5.1-5.el7 base 28 k readline x86_64 6.2-11.el7 base 193 k rpm x86_64 4.11.3-48.el7_9 updates 1.2 M rpm-build-libs x86_64 4.11.3-48.el7_9 updates 108 k rpm-libs x86_64 4.11.3-48.el7_9 updates 279 k rpm-python x86_64 4.11.3-48.el7_9 updates 84 k sed x86_64 4.2.2-7.el7 base 231 k setup noarch 2.8.71-11.el7 base 166 k shared-mime-info x86_64 1.8-5.el7 base 312 k sqlite x86_64 3.7.17-8.el7_7.1 base 394 k tzdata noarch 2022a-1.el7 updates 501 k xz-libs x86_64 5.2.2-2.el7_9 updates 103 k yum-metadata-parser x86_64 1.1.4-10.el7 base 28 k yum-plugin-fastestmirror noarch 1.1.31-54.el7_8 base 34 k zlib x86_64 1.2.7-20.el7_9 updates 90 k Transaction Summary ================================================================================ Install 100 Packages Total download size: 52 M Installed size: 354 M Downloading Packages: (1/100): basesystem-10.0-7.el7.centos.noarch.rp 82 kB/s | 5.0 kB 00:00 (2/100): bzip2-libs-1.0.6-13.el7.x86_64.rpm 360 kB/s | 40 kB 00:00 (3/100): audit-libs-2.8.5-4.el7.x86_64.rpm 657 kB/s | 102 kB 00:00 (4/100): chkconfig-1.7.6-1.el7.x86_64.rpm 1.3 MB/s | 182 kB 00:00 (5/100): cpio-2.11-28.el7.x86_64.rpm 1.8 MB/s | 211 kB 00:00 (6/100): diffutils-3.3-5.el7.x86_64.rpm 3.3 MB/s | 322 kB 00:00 (7/100): elfutils-libelf-0.176-5.el7.x86_64.rpm 3.1 MB/s | 195 kB 00:00 (8/100): file-libs-5.11-37.el7.x86_64.rpm 4.8 MB/s | 340 kB 00:00 (9/100): findutils-4.5.11-6.el7.x86_64.rpm 7.6 MB/s | 559 kB 00:00 (10/100): filesystem-3.2-25.el7.x86_64.rpm 11 MB/s | 1.0 MB 00:00 (11/100): gdbm-1.10-8.el7.x86_64.rpm 2.2 MB/s | 70 kB 00:00 (12/100): gawk-4.0.2-4.el7_3.1.x86_64.rpm 11 MB/s | 874 kB 00:00 (13/100): gmp-6.0.0-15.el7.x86_64.rpm 7.9 MB/s | 281 kB 00:00 (14/100): gpgme-1.3.2-5.el7.x86_64.rpm 4.2 MB/s | 146 kB 00:00 (15/100): grep-2.20-3.el7.x86_64.rpm 9.3 MB/s | 344 kB 00:00 (16/100): gnupg2-2.0.22-5.el7_5.x86_64.rpm 19 MB/s | 1.5 MB 00:00 (17/100): keyutils-libs-1.5.8-3.el7.x86_64.rpm 819 kB/s | 25 kB 00:00 (18/100): info-5.1-5.el7.x86_64.rpm 6.4 MB/s | 233 kB 00:00 (19/100): libacl-2.2.51-15.el7.x86_64.rpm 891 kB/s | 27 kB 00:00 (20/100): libassuan-2.1.0-3.el7.x86_64.rpm 2.0 MB/s | 63 kB 00:00 (21/100): libattr-2.4.46-13.el7.x86_64.rpm 587 kB/s | 18 kB 00:00 (22/100): libcap-2.22-11.el7.x86_64.rpm 1.5 MB/s | 47 kB 00:00 (23/100): libcap-ng-0.7.5-4.el7.x86_64.rpm 786 kB/s | 25 kB 00:00 (24/100): libcom_err-1.42.9-19.el7.x86_64.rpm 1.3 MB/s | 42 kB 00:00 (25/100): libdb-utils-5.3.21-25.el7.x86_64.rpm 3.9 MB/s | 132 kB 00:00 (26/100): libffi-3.0.13-19.el7.x86_64.rpm 903 kB/s | 30 kB 00:00 (27/100): libdb-5.3.21-25.el7.x86_64.rpm 18 MB/s | 720 kB 00:00 (28/100): libgcc-4.8.5-44.el7.x86_64.rpm 3.2 MB/s | 103 kB 00:00 (29/100): libgpg-error-1.12-3.el7.x86_64.rpm 2.7 MB/s | 87 kB 00:00 (30/100): libgcrypt-1.5.3-14.el7.x86_64.rpm 7.1 MB/s | 263 kB 00:00 (31/100): libidn-1.28-4.el7.x86_64.rpm 6.1 MB/s | 209 kB 00:00 (32/100): libselinux-2.5-15.el7.x86_64.rpm 4.8 MB/s | 162 kB 00:00 (33/100): libsepol-2.5-10.el7.x86_64.rpm 8.0 MB/s | 297 kB 00:00 (34/100): libssh2-1.8.0-4.el7.x86_64.rpm 2.7 MB/s | 88 kB 00:00 (35/100): libstdc++-4.8.5-44.el7.x86_64.rpm 8.9 MB/s | 306 kB 00:00 (36/100): libtasn1-4.10-1.el7.x86_64.rpm 8.5 MB/s | 320 kB 00:00 (37/100): libverto-0.2.5-4.el7.x86_64.rpm 539 kB/s | 16 kB 00:00 (38/100): lua-5.1.4-15.el7.x86_64.rpm 6.1 MB/s | 201 kB 00:00 (39/100): ncurses-5.9-14.20130511.el7_4.x86_64. 7.9 MB/s | 304 kB 00:00 (40/100): ncurses-base-5.9-14.20130511.el7_4.no 2.1 MB/s | 68 kB 00:00 (41/100): ncurses-libs-5.9-14.20130511.el7_4.x8 9.1 MB/s | 316 kB 00:00 (42/100): nss-pem-1.0.3-7.el7.x86_64.rpm 2.3 MB/s | 74 kB 00:00 (43/100): p11-kit-0.23.5-3.el7.x86_64.rpm 7.1 MB/s | 252 kB 00:00 (44/100): p11-kit-trust-0.23.5-3.el7.x86_64.rpm 4.0 MB/s | 129 kB 00:00 (45/100): pcre-8.32-17.el7.x86_64.rpm 10 MB/s | 422 kB 00:00 (46/100): pinentry-0.8.1-17.el7.x86_64.rpm 2.3 MB/s | 73 kB 00:00 (47/100): popt-1.13-16.el7.x86_64.rpm 1.3 MB/s | 42 kB 00:00 (48/100): pth-2.0.7-23.el7.x86_64.rpm 2.7 MB/s | 89 kB 00:00 (49/100): pygpgme-0.3-9.el7.x86_64.rpm 2.0 MB/s | 63 kB 00:00 (50/100): pyliblzma-0.5.3-11.el7.x86_64.rpm 1.5 MB/s | 47 kB 00:00 (51/100): python-iniparse-0.4-9.el7.noarch.rpm 1.2 MB/s | 39 kB 00:00 (52/100): python-chardet-2.2.1-3.el7.noarch.rpm 6.2 MB/s | 227 kB 00:00 (53/100): python-kitchen-1.1.1-5.el7.noarch.rpm 7.9 MB/s | 267 kB 00:00 (54/100): python-pycurl-7.19.0-19.el7.x86_64.rp 2.5 MB/s | 80 kB 00:00 (55/100): python-urlgrabber-3.10-10.el7.noarch. 3.3 MB/s | 108 kB 00:00 (56/100): pyxattr-0.5.1-5.el7.x86_64.rpm 906 kB/s | 28 kB 00:00 (57/100): readline-6.2-11.el7.x86_64.rpm 5.5 MB/s | 193 kB 00:00 (58/100): sed-4.2.2-7.el7.x86_64.rpm 6.4 MB/s | 231 kB 00:00 (59/100): setup-2.8.71-11.el7.noarch.rpm 5.1 MB/s | 166 kB 00:00 (60/100): shared-mime-info-1.8-5.el7.x86_64.rpm 8.5 MB/s | 312 kB 00:00 (61/100): sqlite-3.7.17-8.el7_7.1.x86_64.rpm 9.8 MB/s | 394 kB 00:00 (62/100): yum-3.4.3-168.el7.centos.noarch.rpm 19 MB/s | 1.2 MB 00:00 (63/100): yum-metadata-parser-1.1.4-10.el7.x86_ 828 kB/s | 28 kB 00:00 (64/100): yum-plugin-fastestmirror-1.1.31-54.el 1.1 MB/s | 34 kB 00:00 (65/100): yum-utils-1.1.31-54.el7_8.noarch.rpm 3.7 MB/s | 122 kB 00:00 (66/100): centos-release-7-9.2009.1.el7.centos. 220 kB/s | 27 kB 00:00 (67/100): ca-certificates-2021.2.50-72.el7_9.no 1.5 MB/s | 379 kB 00:00 (68/100): curl-7.29.0-59.el7_9.1.x86_64.rpm 6.1 MB/s | 271 kB 00:00 (69/100): bash-4.2.46-35.el7_9.x86_64.rpm 3.0 MB/s | 1.0 MB 00:00 (70/100): cyrus-sasl-lib-2.1.26-24.el7_9.x86_64 3.6 MB/s | 156 kB 00:00 (71/100): expat-2.1.0-14.el7_9.x86_64.rpm 1.9 MB/s | 83 kB 00:00 (72/100): coreutils-8.22-24.el7_9.2.x86_64.rpm 11 MB/s | 3.3 MB 00:00 (73/100): glib2-2.56.1-9.el7_9.x86_64.rpm 17 MB/s | 2.5 MB 00:00 (74/100): glibc-2.17-326.el7_9.x86_64.rpm 25 MB/s | 3.6 MB 00:00 (75/100): krb5-libs-1.15.1-54.el7_9.x86_64.rpm 13 MB/s | 810 kB 00:00 (76/100): libblkid-2.23.2-65.el7_9.1.x86_64.rpm 4.0 MB/s | 183 kB 00:00 (77/100): libcurl-7.29.0-59.el7_9.1.x86_64.rpm 4.9 MB/s | 223 kB 00:00 (78/100): libmount-2.23.2-65.el7_9.1.x86_64.rpm 4.1 MB/s | 185 kB 00:00 (79/100): libuuid-2.23.2-65.el7_9.1.x86_64.rpm 1.9 MB/s | 84 kB 00:00 (80/100): libxml2-2.9.1-6.el7_9.6.x86_64.rpm 12 MB/s | 668 kB 00:00 (81/100): libxml2-python-2.9.1-6.el7_9.6.x86_64 5.3 MB/s | 247 kB 00:00 (82/100): glibc-common-2.17-326.el7_9.x86_64.rp 48 MB/s | 12 MB 00:00 (83/100): nspr-4.32.0-1.el7_9.x86_64.rpm 3.0 MB/s | 127 kB 00:00 (84/100): nss-3.67.0-4.el7_9.x86_64.rpm 17 MB/s | 882 kB 00:00 (85/100): nss-softokn-3.67.0-3.el7_9.x86_64.rpm 8.0 MB/s | 358 kB 00:00 (86/100): nss-softokn-freebl-3.67.0-3.el7_9.x86 7.5 MB/s | 337 kB 00:00 (87/100): nss-sysinit-3.67.0-4.el7_9.x86_64.rpm 1.6 MB/s | 66 kB 00:00 (88/100): nss-tools-3.67.0-4.el7_9.x86_64.rpm 12 MB/s | 549 kB 00:00 (89/100): nss-util-3.67.0-1.el7_9.x86_64.rpm 1.9 MB/s | 79 kB 00:00 (90/100): openldap-2.4.44-25.el7_9.x86_64.rpm 7.9 MB/s | 356 kB 00:00 (91/100): python-2.7.5-92.el7_9.x86_64.rpm 2.2 MB/s | 96 kB 00:00 (92/100): openssl-libs-1.0.2k-25.el7_9.x86_64.r 22 MB/s | 1.2 MB 00:00 (93/100): rpm-build-libs-4.11.3-48.el7_9.x86_64 2.4 MB/s | 108 kB 00:00 (94/100): rpm-4.11.3-48.el7_9.x86_64.rpm 19 MB/s | 1.2 MB 00:00 (95/100): rpm-libs-4.11.3-48.el7_9.x86_64.rpm 6.0 MB/s | 279 kB 00:00 (96/100): rpm-python-4.11.3-48.el7_9.x86_64.rpm 2.0 MB/s | 84 kB 00:00 (97/100): python-libs-2.7.5-92.el7_9.x86_64.rpm 40 MB/s | 5.6 MB 00:00 (98/100): tzdata-2022a-1.el7.noarch.rpm 11 MB/s | 501 kB 00:00 (99/100): xz-libs-5.2.2-2.el7_9.x86_64.rpm 2.4 MB/s | 103 kB 00:00 (100/100): zlib-1.2.7-20.el7_9.x86_64.rpm 2.1 MB/s | 90 kB 00:00 -------------------------------------------------------------------------------- Total 25 MB/s | 52 MB 00:02 CentOS-7 - Base 1.6 MB/s | 1.7 kB 00:00 Importing GPG key 0xF4A80EB5: Userid : "CentOS-7 Key (CentOS 7 Official Signing Key) " Fingerprint: 6341 AB27 53D7 8A78 A7C2 7BB1 24C6 A8A7 F4A8 0EB5 From : /usr/share/distribution-gpg-keys/centos/RPM-GPG-KEY-CentOS-7 Key imported successfully Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Running scriptlet: filesystem-3.2-25.el7.x86_64 1/1 Preparing : 1/1 Installing : libgcc-4.8.5-44.el7.x86_64 1/100 Running scriptlet: libgcc-4.8.5-44.el7.x86_64 1/100 Installing : tzdata-2022a-1.el7.noarch 2/100 Installing : centos-release-7-9.2009.1.el7.centos.x86_64 3/100 Installing : setup-2.8.71-11.el7.noarch 4/100 Running scriptlet: setup-2.8.71-11.el7.noarch 4/100 Installing : filesystem-3.2-25.el7.x86_64 5/100 Installing : basesystem-10.0-7.el7.centos.noarch 6/100 Installing : ncurses-base-5.9-14.20130511.el7_4.noarch 7/100 Installing : glibc-common-2.17-326.el7_9.x86_64 8/100 Running scriptlet: glibc-common-2.17-326.el7_9.x86_64 8/100 Installing : nss-softokn-freebl-3.67.0-3.el7_9.x86_64 9/100 Running scriptlet: glibc-2.17-326.el7_9.x86_64 10/100 Installing : glibc-2.17-326.el7_9.x86_64 10/100 Running scriptlet: glibc-2.17-326.el7_9.x86_64 10/100 Installing : nspr-4.32.0-1.el7_9.x86_64 11/100 Running scriptlet: nspr-4.32.0-1.el7_9.x86_64 11/100 Installing : nss-util-3.67.0-1.el7_9.x86_64 12/100 Running scriptlet: nss-util-3.67.0-1.el7_9.x86_64 12/100 Installing : libstdc++-4.8.5-44.el7.x86_64 13/100 Running scriptlet: libstdc++-4.8.5-44.el7.x86_64 13/100 Installing : ncurses-libs-5.9-14.20130511.el7_4.x86_64 14/100 Running scriptlet: ncurses-libs-5.9-14.20130511.el7_4.x86_64 14/100 Installing : bash-4.2.46-35.el7_9.x86_64 15/100 Running scriptlet: bash-4.2.46-35.el7_9.x86_64 15/100 Installing : pcre-8.32-17.el7.x86_64 16/100 Running scriptlet: pcre-8.32-17.el7.x86_64 16/100 Installing : libsepol-2.5-10.el7.x86_64 17/100 Running scriptlet: libsepol-2.5-10.el7.x86_64 17/100 Installing : libselinux-2.5-15.el7.x86_64 18/100 Running scriptlet: libselinux-2.5-15.el7.x86_64 18/100 Installing : zlib-1.2.7-20.el7_9.x86_64 19/100 Running scriptlet: zlib-1.2.7-20.el7_9.x86_64 19/100 Installing : info-5.1-5.el7.x86_64 20/100 Running scriptlet: info-5.1-5.el7.x86_64 20/100 Installing : libdb-5.3.21-25.el7.x86_64 21/100 Running scriptlet: libdb-5.3.21-25.el7.x86_64 21/100 Installing : xz-libs-5.2.2-2.el7_9.x86_64 22/100 Running scriptlet: xz-libs-5.2.2-2.el7_9.x86_64 22/100 Installing : bzip2-libs-1.0.6-13.el7.x86_64 23/100 Running scriptlet: bzip2-libs-1.0.6-13.el7.x86_64 23/100 Installing : popt-1.13-16.el7.x86_64 24/100 Running scriptlet: popt-1.13-16.el7.x86_64 24/100 Installing : readline-6.2-11.el7.x86_64 25/100 Running scriptlet: readline-6.2-11.el7.x86_64 25/100 Installing : lua-5.1.4-15.el7.x86_64 26/100 Installing : elfutils-libelf-0.176-5.el7.x86_64 27/100 Running scriptlet: elfutils-libelf-0.176-5.el7.x86_64 27/100 Installing : libattr-2.4.46-13.el7.x86_64 28/100 Running scriptlet: libattr-2.4.46-13.el7.x86_64 28/100 Installing : libacl-2.2.51-15.el7.x86_64 29/100 Running scriptlet: libacl-2.2.51-15.el7.x86_64 29/100 Installing : libcap-2.22-11.el7.x86_64 30/100 Running scriptlet: libcap-2.22-11.el7.x86_64 30/100 Installing : libcom_err-1.42.9-19.el7.x86_64 31/100 Running scriptlet: libcom_err-1.42.9-19.el7.x86_64 31/100 Installing : libffi-3.0.13-19.el7.x86_64 32/100 Running scriptlet: libffi-3.0.13-19.el7.x86_64 32/100 Installing : libgpg-error-1.12-3.el7.x86_64 33/100 Running scriptlet: libgpg-error-1.12-3.el7.x86_64 33/100 Installing : sqlite-3.7.17-8.el7_7.1.x86_64 34/100 Running scriptlet: sqlite-3.7.17-8.el7_7.1.x86_64 34/100 Installing : chkconfig-1.7.6-1.el7.x86_64 35/100 Installing : libxml2-2.9.1-6.el7_9.6.x86_64 36/100 Running scriptlet: libxml2-2.9.1-6.el7_9.6.x86_64 36/100 Installing : nss-softokn-3.67.0-3.el7_9.x86_64 37/100 Running scriptlet: nss-softokn-3.67.0-3.el7_9.x86_64 37/100 Installing : libassuan-2.1.0-3.el7.x86_64 38/100 Running scriptlet: libassuan-2.1.0-3.el7.x86_64 38/100 Installing : p11-kit-0.23.5-3.el7.x86_64 39/100 Running scriptlet: p11-kit-0.23.5-3.el7.x86_64 39/100 Installing : grep-2.20-3.el7.x86_64 40/100 Running scriptlet: grep-2.20-3.el7.x86_64 40/100 Installing : sed-4.2.2-7.el7.x86_64 41/100 Running scriptlet: sed-4.2.2-7.el7.x86_64 41/100 Installing : file-libs-5.11-37.el7.x86_64 42/100 Running scriptlet: file-libs-5.11-37.el7.x86_64 42/100 Installing : keyutils-libs-1.5.8-3.el7.x86_64 43/100 Running scriptlet: keyutils-libs-1.5.8-3.el7.x86_64 43/100 Installing : libuuid-2.23.2-65.el7_9.1.x86_64 44/100 Running scriptlet: libuuid-2.23.2-65.el7_9.1.x86_64 44/100 Running scriptlet: pinentry-0.8.1-17.el7.x86_64 45/100 Installing : pinentry-0.8.1-17.el7.x86_64 45/100 Running scriptlet: pinentry-0.8.1-17.el7.x86_64 45/100 Installing : libgcrypt-1.5.3-14.el7.x86_64 46/100 Running scriptlet: libgcrypt-1.5.3-14.el7.x86_64 46/100 Installing : libdb-utils-5.3.21-25.el7.x86_64 47/100 Installing : cpio-2.11-28.el7.x86_64 48/100 Running scriptlet: cpio-2.11-28.el7.x86_64 48/100 Installing : diffutils-3.3-5.el7.x86_64 49/100 Running scriptlet: diffutils-3.3-5.el7.x86_64 49/100 Installing : findutils-1:4.5.11-6.el7.x86_64 50/100 Running scriptlet: findutils-1:4.5.11-6.el7.x86_64 50/100 Installing : gawk-4.0.2-4.el7_3.1.x86_64 51/100 Running scriptlet: gawk-4.0.2-4.el7_3.1.x86_64 51/100 Installing : libidn-1.28-4.el7.x86_64 52/100 Running scriptlet: libidn-1.28-4.el7.x86_64 52/100 Installing : ncurses-5.9-14.20130511.el7_4.x86_64 53/100 Installing : gmp-1:6.0.0-15.el7.x86_64 54/100 Running scriptlet: gmp-1:6.0.0-15.el7.x86_64 54/100 Installing : gdbm-1.10-8.el7.x86_64 55/100 Running scriptlet: gdbm-1.10-8.el7.x86_64 55/100 Installing : libcap-ng-0.7.5-4.el7.x86_64 56/100 Running scriptlet: libcap-ng-0.7.5-4.el7.x86_64 56/100 Installing : audit-libs-2.8.5-4.el7.x86_64 57/100 Running scriptlet: audit-libs-2.8.5-4.el7.x86_64 57/100 Installing : libtasn1-4.10-1.el7.x86_64 58/100 Running scriptlet: libtasn1-4.10-1.el7.x86_64 58/100 Installing : p11-kit-trust-0.23.5-3.el7.x86_64 59/100 Running scriptlet: p11-kit-trust-0.23.5-3.el7.x86_64 59/100 Running scriptlet: ca-certificates-2021.2.50-72.el7_9.noarch 60/100 Installing : ca-certificates-2021.2.50-72.el7_9.noarch 60/100 Running scriptlet: ca-certificates-2021.2.50-72.el7_9.noarch 60/100 Installing : libverto-0.2.5-4.el7.x86_64 61/100 Running scriptlet: libverto-0.2.5-4.el7.x86_64 61/100 Running scriptlet: coreutils-8.22-24.el7_9.2.x86_64 62/100 Installing : coreutils-8.22-24.el7_9.2.x86_64 62/100 Running scriptlet: coreutils-8.22-24.el7_9.2.x86_64 62/100 Installing : krb5-libs-1.15.1-54.el7_9.x86_64 63/100 Running scriptlet: krb5-libs-1.15.1-54.el7_9.x86_64 63/100 Installing : openssl-libs-1:1.0.2k-25.el7_9.x86_64 64/100 Running scriptlet: openssl-libs-1:1.0.2k-25.el7_9.x86_64 64/100 Installing : libssh2-1.8.0-4.el7.x86_64 65/100 Running scriptlet: libssh2-1.8.0-4.el7.x86_64 65/100 Installing : cyrus-sasl-lib-2.1.26-24.el7_9.x86_64 66/100 Running scriptlet: cyrus-sasl-lib-2.1.26-24.el7_9.x86_64 66/100 Installing : libblkid-2.23.2-65.el7_9.1.x86_64 67/100 Running scriptlet: libblkid-2.23.2-65.el7_9.1.x86_64 67/100 Installing : libmount-2.23.2-65.el7_9.1.x86_64 68/100 Running scriptlet: libmount-2.23.2-65.el7_9.1.x86_64 68/100 Installing : glib2-2.56.1-9.el7_9.x86_64 69/100 Running scriptlet: glib2-2.56.1-9.el7_9.x86_64 69/100 Installing : shared-mime-info-1.8-5.el7.x86_64 70/100 Running scriptlet: shared-mime-info-1.8-5.el7.x86_64 70/100 Installing : nss-pem-1.0.3-7.el7.x86_64 71/100 Installing : nss-3.67.0-4.el7_9.x86_64 72/100 Running scriptlet: nss-3.67.0-4.el7_9.x86_64 72/100 Installing : nss-sysinit-3.67.0-4.el7_9.x86_64 73/100 Installing : nss-tools-3.67.0-4.el7_9.x86_64 74/100 Installing : libcurl-7.29.0-59.el7_9.1.x86_64 75/100 Running scriptlet: libcurl-7.29.0-59.el7_9.1.x86_64 75/100 Installing : curl-7.29.0-59.el7_9.1.x86_64 76/100 Installing : rpm-libs-4.11.3-48.el7_9.x86_64 77/100 Running scriptlet: rpm-libs-4.11.3-48.el7_9.x86_64 77/100 Installing : rpm-4.11.3-48.el7_9.x86_64 78/100 Installing : openldap-2.4.44-25.el7_9.x86_64 79/100 Running scriptlet: openldap-2.4.44-25.el7_9.x86_64 79/100 Installing : pth-2.0.7-23.el7.x86_64 80/100 Running scriptlet: pth-2.0.7-23.el7.x86_64 80/100 Installing : gnupg2-2.0.22-5.el7_5.x86_64 81/100 Running scriptlet: gnupg2-2.0.22-5.el7_5.x86_64 81/100 Installing : gpgme-1.3.2-5.el7.x86_64 82/100 Running scriptlet: gpgme-1.3.2-5.el7.x86_64 82/100 Installing : rpm-build-libs-4.11.3-48.el7_9.x86_64 83/100 Running scriptlet: rpm-build-libs-4.11.3-48.el7_9.x86_64 83/100 Installing : expat-2.1.0-14.el7_9.x86_64 84/100 Running scriptlet: expat-2.1.0-14.el7_9.x86_64 84/100 Installing : python-libs-2.7.5-92.el7_9.x86_64 85/100 Running scriptlet: python-libs-2.7.5-92.el7_9.x86_64 85/100 Installing : python-2.7.5-92.el7_9.x86_64 86/100 Installing : pygpgme-0.3-9.el7.x86_64 87/100 Installing : pyliblzma-0.5.3-11.el7.x86_64 88/100 Installing : python-chardet-2.2.1-3.el7.noarch 89/100 Installing : python-kitchen-1.1.1-5.el7.noarch 90/100 Installing : python-iniparse-0.4-9.el7.noarch 91/100 Installing : python-pycurl-7.19.0-19.el7.x86_64 92/100 Installing : python-urlgrabber-3.10-10.el7.noarch 93/100 Installing : pyxattr-0.5.1-5.el7.x86_64 94/100 Installing : yum-metadata-parser-1.1.4-10.el7.x86_64 95/100 Installing : libxml2-python-2.9.1-6.el7_9.6.x86_64 96/100 Installing : rpm-python-4.11.3-48.el7_9.x86_64 97/100 Installing : yum-plugin-fastestmirror-1.1.31-54.el7_8.noarch 98/100 Installing : yum-3.4.3-168.el7.centos.noarch 99/100 warning: /etc/yum.conf created as /etc/yum.conf.rpmnew Installing : yum-utils-1.1.31-54.el7_8.noarch 100/100 Running scriptlet: filesystem-3.2-25.el7.x86_64 100/100 Running scriptlet: p11-kit-trust-0.23.5-3.el7.x86_64 100/100 Running scriptlet: shared-mime-info-1.8-5.el7.x86_64 100/100 Running scriptlet: rpm-4.11.3-48.el7_9.x86_64 100/100 Verifying : audit-libs-2.8.5-4.el7.x86_64 1/100 Verifying : basesystem-10.0-7.el7.centos.noarch 2/100 Verifying : bzip2-libs-1.0.6-13.el7.x86_64 3/100 Verifying : chkconfig-1.7.6-1.el7.x86_64 4/100 Verifying : cpio-2.11-28.el7.x86_64 5/100 Verifying : diffutils-3.3-5.el7.x86_64 6/100 Verifying : elfutils-libelf-0.176-5.el7.x86_64 7/100 Verifying : file-libs-5.11-37.el7.x86_64 8/100 Verifying : filesystem-3.2-25.el7.x86_64 9/100 Verifying : findutils-1:4.5.11-6.el7.x86_64 10/100 Verifying : gawk-4.0.2-4.el7_3.1.x86_64 11/100 Verifying : gdbm-1.10-8.el7.x86_64 12/100 Verifying : gmp-1:6.0.0-15.el7.x86_64 13/100 Verifying : gnupg2-2.0.22-5.el7_5.x86_64 14/100 Verifying : gpgme-1.3.2-5.el7.x86_64 15/100 Verifying : grep-2.20-3.el7.x86_64 16/100 Verifying : info-5.1-5.el7.x86_64 17/100 Verifying : keyutils-libs-1.5.8-3.el7.x86_64 18/100 Verifying : libacl-2.2.51-15.el7.x86_64 19/100 Verifying : libassuan-2.1.0-3.el7.x86_64 20/100 Verifying : libattr-2.4.46-13.el7.x86_64 21/100 Verifying : libcap-2.22-11.el7.x86_64 22/100 Verifying : libcap-ng-0.7.5-4.el7.x86_64 23/100 Verifying : libcom_err-1.42.9-19.el7.x86_64 24/100 Verifying : libdb-5.3.21-25.el7.x86_64 25/100 Verifying : libdb-utils-5.3.21-25.el7.x86_64 26/100 Verifying : libffi-3.0.13-19.el7.x86_64 27/100 Verifying : libgcc-4.8.5-44.el7.x86_64 28/100 Verifying : libgcrypt-1.5.3-14.el7.x86_64 29/100 Verifying : libgpg-error-1.12-3.el7.x86_64 30/100 Verifying : libidn-1.28-4.el7.x86_64 31/100 Verifying : libselinux-2.5-15.el7.x86_64 32/100 Verifying : libsepol-2.5-10.el7.x86_64 33/100 Verifying : libssh2-1.8.0-4.el7.x86_64 34/100 Verifying : libstdc++-4.8.5-44.el7.x86_64 35/100 Verifying : libtasn1-4.10-1.el7.x86_64 36/100 Verifying : libverto-0.2.5-4.el7.x86_64 37/100 Verifying : lua-5.1.4-15.el7.x86_64 38/100 Verifying : ncurses-5.9-14.20130511.el7_4.x86_64 39/100 Verifying : ncurses-base-5.9-14.20130511.el7_4.noarch 40/100 Verifying : ncurses-libs-5.9-14.20130511.el7_4.x86_64 41/100 Verifying : nss-pem-1.0.3-7.el7.x86_64 42/100 Verifying : p11-kit-0.23.5-3.el7.x86_64 43/100 Verifying : p11-kit-trust-0.23.5-3.el7.x86_64 44/100 Verifying : pcre-8.32-17.el7.x86_64 45/100 Verifying : pinentry-0.8.1-17.el7.x86_64 46/100 Verifying : popt-1.13-16.el7.x86_64 47/100 Verifying : pth-2.0.7-23.el7.x86_64 48/100 Verifying : pygpgme-0.3-9.el7.x86_64 49/100 Verifying : pyliblzma-0.5.3-11.el7.x86_64 50/100 Verifying : python-chardet-2.2.1-3.el7.noarch 51/100 Verifying : python-iniparse-0.4-9.el7.noarch 52/100 Verifying : python-kitchen-1.1.1-5.el7.noarch 53/100 Verifying : python-pycurl-7.19.0-19.el7.x86_64 54/100 Verifying : python-urlgrabber-3.10-10.el7.noarch 55/100 Verifying : pyxattr-0.5.1-5.el7.x86_64 56/100 Verifying : readline-6.2-11.el7.x86_64 57/100 Verifying : sed-4.2.2-7.el7.x86_64 58/100 Verifying : setup-2.8.71-11.el7.noarch 59/100 Verifying : shared-mime-info-1.8-5.el7.x86_64 60/100 Verifying : sqlite-3.7.17-8.el7_7.1.x86_64 61/100 Verifying : yum-3.4.3-168.el7.centos.noarch 62/100 Verifying : yum-metadata-parser-1.1.4-10.el7.x86_64 63/100 Verifying : yum-plugin-fastestmirror-1.1.31-54.el7_8.noarch 64/100 Verifying : yum-utils-1.1.31-54.el7_8.noarch 65/100 Verifying : bash-4.2.46-35.el7_9.x86_64 66/100 Verifying : ca-certificates-2021.2.50-72.el7_9.noarch 67/100 Verifying : centos-release-7-9.2009.1.el7.centos.x86_64 68/100 Verifying : coreutils-8.22-24.el7_9.2.x86_64 69/100 Verifying : curl-7.29.0-59.el7_9.1.x86_64 70/100 Verifying : cyrus-sasl-lib-2.1.26-24.el7_9.x86_64 71/100 Verifying : expat-2.1.0-14.el7_9.x86_64 72/100 Verifying : glib2-2.56.1-9.el7_9.x86_64 73/100 Verifying : glibc-2.17-326.el7_9.x86_64 74/100 Verifying : glibc-common-2.17-326.el7_9.x86_64 75/100 Verifying : krb5-libs-1.15.1-54.el7_9.x86_64 76/100 Verifying : libblkid-2.23.2-65.el7_9.1.x86_64 77/100 Verifying : libcurl-7.29.0-59.el7_9.1.x86_64 78/100 Verifying : libmount-2.23.2-65.el7_9.1.x86_64 79/100 Verifying : libuuid-2.23.2-65.el7_9.1.x86_64 80/100 Verifying : libxml2-2.9.1-6.el7_9.6.x86_64 81/100 Verifying : libxml2-python-2.9.1-6.el7_9.6.x86_64 82/100 Verifying : nspr-4.32.0-1.el7_9.x86_64 83/100 Verifying : nss-3.67.0-4.el7_9.x86_64 84/100 Verifying : nss-softokn-3.67.0-3.el7_9.x86_64 85/100 Verifying : nss-softokn-freebl-3.67.0-3.el7_9.x86_64 86/100 Verifying : nss-sysinit-3.67.0-4.el7_9.x86_64 87/100 Verifying : nss-tools-3.67.0-4.el7_9.x86_64 88/100 Verifying : nss-util-3.67.0-1.el7_9.x86_64 89/100 Verifying : openldap-2.4.44-25.el7_9.x86_64 90/100 Verifying : openssl-libs-1:1.0.2k-25.el7_9.x86_64 91/100 Verifying : python-2.7.5-92.el7_9.x86_64 92/100 Verifying : python-libs-2.7.5-92.el7_9.x86_64 93/100 Verifying : rpm-4.11.3-48.el7_9.x86_64 94/100 Verifying : rpm-build-libs-4.11.3-48.el7_9.x86_64 95/100 Verifying : rpm-libs-4.11.3-48.el7_9.x86_64 96/100 Verifying : rpm-python-4.11.3-48.el7_9.x86_64 97/100 Verifying : tzdata-2022a-1.el7.noarch 98/100 Verifying : xz-libs-5.2.2-2.el7_9.x86_64 99/100 Verifying : zlib-1.2.7-20.el7_9.x86_64 100/100 Installed products updated. Installed: audit-libs-2.8.5-4.el7.x86_64 basesystem-10.0-7.el7.centos.noarch bash-4.2.46-35.el7_9.x86_64 bzip2-libs-1.0.6-13.el7.x86_64 ca-certificates-2021.2.50-72.el7_9.noarch centos-release-7-9.2009.1.el7.centos.x86_64 chkconfig-1.7.6-1.el7.x86_64 coreutils-8.22-24.el7_9.2.x86_64 cpio-2.11-28.el7.x86_64 curl-7.29.0-59.el7_9.1.x86_64 cyrus-sasl-lib-2.1.26-24.el7_9.x86_64 diffutils-3.3-5.el7.x86_64 elfutils-libelf-0.176-5.el7.x86_64 expat-2.1.0-14.el7_9.x86_64 file-libs-5.11-37.el7.x86_64 filesystem-3.2-25.el7.x86_64 findutils-1:4.5.11-6.el7.x86_64 gawk-4.0.2-4.el7_3.1.x86_64 gdbm-1.10-8.el7.x86_64 glib2-2.56.1-9.el7_9.x86_64 glibc-2.17-326.el7_9.x86_64 glibc-common-2.17-326.el7_9.x86_64 gmp-1:6.0.0-15.el7.x86_64 gnupg2-2.0.22-5.el7_5.x86_64 gpgme-1.3.2-5.el7.x86_64 grep-2.20-3.el7.x86_64 info-5.1-5.el7.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-54.el7_9.x86_64 libacl-2.2.51-15.el7.x86_64 libassuan-2.1.0-3.el7.x86_64 libattr-2.4.46-13.el7.x86_64 libblkid-2.23.2-65.el7_9.1.x86_64 libcap-2.22-11.el7.x86_64 libcap-ng-0.7.5-4.el7.x86_64 libcom_err-1.42.9-19.el7.x86_64 libcurl-7.29.0-59.el7_9.1.x86_64 libdb-5.3.21-25.el7.x86_64 libdb-utils-5.3.21-25.el7.x86_64 libffi-3.0.13-19.el7.x86_64 libgcc-4.8.5-44.el7.x86_64 libgcrypt-1.5.3-14.el7.x86_64 libgpg-error-1.12-3.el7.x86_64 libidn-1.28-4.el7.x86_64 libmount-2.23.2-65.el7_9.1.x86_64 libselinux-2.5-15.el7.x86_64 libsepol-2.5-10.el7.x86_64 libssh2-1.8.0-4.el7.x86_64 libstdc++-4.8.5-44.el7.x86_64 libtasn1-4.10-1.el7.x86_64 libuuid-2.23.2-65.el7_9.1.x86_64 libverto-0.2.5-4.el7.x86_64 libxml2-2.9.1-6.el7_9.6.x86_64 libxml2-python-2.9.1-6.el7_9.6.x86_64 lua-5.1.4-15.el7.x86_64 ncurses-5.9-14.20130511.el7_4.x86_64 ncurses-base-5.9-14.20130511.el7_4.noarch ncurses-libs-5.9-14.20130511.el7_4.x86_64 nspr-4.32.0-1.el7_9.x86_64 nss-3.67.0-4.el7_9.x86_64 nss-pem-1.0.3-7.el7.x86_64 nss-softokn-3.67.0-3.el7_9.x86_64 nss-softokn-freebl-3.67.0-3.el7_9.x86_64 nss-sysinit-3.67.0-4.el7_9.x86_64 nss-tools-3.67.0-4.el7_9.x86_64 nss-util-3.67.0-1.el7_9.x86_64 openldap-2.4.44-25.el7_9.x86_64 openssl-libs-1:1.0.2k-25.el7_9.x86_64 p11-kit-0.23.5-3.el7.x86_64 p11-kit-trust-0.23.5-3.el7.x86_64 pcre-8.32-17.el7.x86_64 pinentry-0.8.1-17.el7.x86_64 popt-1.13-16.el7.x86_64 pth-2.0.7-23.el7.x86_64 pygpgme-0.3-9.el7.x86_64 pyliblzma-0.5.3-11.el7.x86_64 python-2.7.5-92.el7_9.x86_64 python-chardet-2.2.1-3.el7.noarch python-iniparse-0.4-9.el7.noarch python-kitchen-1.1.1-5.el7.noarch python-libs-2.7.5-92.el7_9.x86_64 python-pycurl-7.19.0-19.el7.x86_64 python-urlgrabber-3.10-10.el7.noarch pyxattr-0.5.1-5.el7.x86_64 readline-6.2-11.el7.x86_64 rpm-4.11.3-48.el7_9.x86_64 rpm-build-libs-4.11.3-48.el7_9.x86_64 rpm-libs-4.11.3-48.el7_9.x86_64 rpm-python-4.11.3-48.el7_9.x86_64 sed-4.2.2-7.el7.x86_64 setup-2.8.71-11.el7.noarch shared-mime-info-1.8-5.el7.x86_64 sqlite-3.7.17-8.el7_7.1.x86_64 tzdata-2022a-1.el7.noarch xz-libs-5.2.2-2.el7_9.x86_64 yum-3.4.3-168.el7.centos.noarch yum-metadata-parser-1.1.4-10.el7.x86_64 yum-plugin-fastestmirror-1.1.31-54.el7_8.noarch yum-utils-1.1.31-54.el7_8.noarch zlib-1.2.7-20.el7_9.x86_64 Complete! Finish(bootstrap): dnf install Start(bootstrap): creating root cache Finish(bootstrap): creating root cache Finish(bootstrap): chroot init Start: chroot init INFO: mounting tmpfs at /var/lib/mock/centos+epel-7-x86_64-1658945077.221752/root. INFO: calling preinit hooks INFO: enabled root cache INFO: enabled package manager cache Start: cleaning package manager metadata Finish: cleaning package manager metadata INFO: enabled HW Info plugin Mock Version: 3.0 INFO: Mock Version: 3.0 Start: yum install Failed to set locale, defaulting to C copr_base | 3.3 kB 00:00 base | 3.6 kB 00:00 centos-sclo-rh | 3.0 kB 00:00 centos-sclo-sclo | 3.0 kB 00:00 epel | 4.7 kB 00:00 extras | 2.9 kB 00:00 updates | 2.9 kB 00:00 (1/7): copr_base/primary_db | 3.9 kB 00:00 (2/7): base/x86_64/primary_db | 6.1 MB 00:00 (3/7): extras/x86_64/primary_db | 247 kB 00:00 (4/7): centos-sclo-sclo/x86_64/primary_db | 300 kB 00:00 (5/7): centos-sclo-rh/x86_64/primary_db | 3.4 MB 00:00 (6/7): epel/x86_64/primary_db | 7.0 MB 00:00 (7/7): updates/x86_64/primary_db | 16 MB 00:02 base/x86_64/group_gz | 153 kB 00:00 epel/x86_64/group_gz | 96 kB 00:00 Resolving Dependencies --> Running transaction check ---> Package bash.x86_64 0:4.2.46-35.el7_9 will be installed --> Processing Dependency: rtld(GNU_HASH) for package: bash-4.2.46-35.el7_9.x86_64 --> Processing Dependency: libdl.so.2(GLIBC_2.2.5)(64bit) for package: bash-4.2.46-35.el7_9.x86_64 --> Processing Dependency: libc.so.6(GLIBC_2.15)(64bit) for package: bash-4.2.46-35.el7_9.x86_64 --> Processing Dependency: libtinfo.so.5()(64bit) for package: bash-4.2.46-35.el7_9.x86_64 --> Processing Dependency: libdl.so.2()(64bit) for package: bash-4.2.46-35.el7_9.x86_64 ---> Package bzip2.x86_64 0:1.0.6-13.el7 will be installed --> Processing Dependency: bzip2-libs = 1.0.6-13.el7 for package: bzip2-1.0.6-13.el7.x86_64 --> Processing Dependency: libbz2.so.1()(64bit) for package: bzip2-1.0.6-13.el7.x86_64 ---> Package coreutils.x86_64 0:8.22-24.el7_9.2 will be installed --> Processing Dependency: ncurses for package: coreutils-8.22-24.el7_9.2.x86_64 --> Processing Dependency: libcrypto.so.10(libcrypto.so.10)(64bit) for package: coreutils-8.22-24.el7_9.2.x86_64 --> Processing Dependency: libattr.so.1(ATTR_1.1)(64bit) for package: coreutils-8.22-24.el7_9.2.x86_64 --> Processing Dependency: libacl.so.1(ACL_1.0)(64bit) for package: coreutils-8.22-24.el7_9.2.x86_64 --> Processing Dependency: gmp for package: coreutils-8.22-24.el7_9.2.x86_64 --> Processing Dependency: libselinux.so.1()(64bit) for package: coreutils-8.22-24.el7_9.2.x86_64 --> Processing Dependency: libgmp.so.10()(64bit) for package: coreutils-8.22-24.el7_9.2.x86_64 --> Processing Dependency: libcrypto.so.10()(64bit) for package: coreutils-8.22-24.el7_9.2.x86_64 --> Processing Dependency: libcap.so.2()(64bit) for package: coreutils-8.22-24.el7_9.2.x86_64 --> Processing Dependency: libattr.so.1()(64bit) for package: coreutils-8.22-24.el7_9.2.x86_64 --> Processing Dependency: libacl.so.1()(64bit) for package: coreutils-8.22-24.el7_9.2.x86_64 ---> Package cpio.x86_64 0:2.11-28.el7 will be installed ---> Package diffutils.x86_64 0:3.3-5.el7 will be installed ---> Package epel-release.noarch 0:7-14 will be installed --> Processing Dependency: redhat-release >= 7 for package: epel-release-7-14.noarch ---> Package epel-rpm-macros.noarch 0:7-35 will be installed --> Processing Dependency: lua-srpm-macros for package: epel-rpm-macros-7-35.noarch --> Processing Dependency: python-rpm-macros for package: epel-rpm-macros-7-35.noarch --> Processing Dependency: python-srpm-macros for package: epel-rpm-macros-7-35.noarch --> Processing Dependency: python2-rpm-macros for package: epel-rpm-macros-7-35.noarch ---> Package findutils.x86_64 1:4.5.11-6.el7 will be installed ---> Package gawk.x86_64 0:4.0.2-4.el7_3.1 will be installed ---> Package gcc.x86_64 0:4.8.5-44.el7 will be installed --> Processing Dependency: libgomp = 4.8.5-44.el7 for package: gcc-4.8.5-44.el7.x86_64 --> Processing Dependency: cpp = 4.8.5-44.el7 for package: gcc-4.8.5-44.el7.x86_64 --> Processing Dependency: libgcc >= 4.8.5-44.el7 for package: gcc-4.8.5-44.el7.x86_64 --> Processing Dependency: glibc-devel >= 2.2.90-12 for package: gcc-4.8.5-44.el7.x86_64 --> Processing Dependency: binutils >= 2.20.51.0.2-12 for package: gcc-4.8.5-44.el7.x86_64 --> Processing Dependency: libz.so.1()(64bit) for package: gcc-4.8.5-44.el7.x86_64 --> Processing Dependency: libmpfr.so.4()(64bit) for package: gcc-4.8.5-44.el7.x86_64 --> Processing Dependency: libmpc.so.3()(64bit) for package: gcc-4.8.5-44.el7.x86_64 --> Processing Dependency: libgomp.so.1()(64bit) for package: gcc-4.8.5-44.el7.x86_64 --> Processing Dependency: libgcc_s.so.1()(64bit) for package: gcc-4.8.5-44.el7.x86_64 ---> Package gcc-c++.x86_64 0:4.8.5-44.el7 will be installed --> Processing Dependency: libstdc++-devel = 4.8.5-44.el7 for package: gcc-c++-4.8.5-44.el7.x86_64 --> Processing Dependency: libstdc++ = 4.8.5-44.el7 for package: gcc-c++-4.8.5-44.el7.x86_64 --> Processing Dependency: libstdc++.so.6()(64bit) for package: gcc-c++-4.8.5-44.el7.x86_64 ---> Package grep.x86_64 0:2.20-3.el7 will be installed --> Processing Dependency: libpcre.so.1()(64bit) for package: grep-2.20-3.el7.x86_64 ---> Package gzip.x86_64 0:1.5-11.el7_9 will be installed ---> Package info.x86_64 0:5.1-5.el7 will be installed ---> Package make.x86_64 1:3.82-24.el7 will be installed ---> Package patch.x86_64 0:2.7.1-12.el7_7 will be installed ---> Package redhat-rpm-config.noarch 0:9.1.0-88.el7.centos will be installed --> Processing Dependency: rpm >= 4.9.0 for package: redhat-rpm-config-9.1.0-88.el7.centos.noarch --> Processing Dependency: dwz >= 0.4 for package: redhat-rpm-config-9.1.0-88.el7.centos.noarch --> Processing Dependency: zip for package: redhat-rpm-config-9.1.0-88.el7.centos.noarch --> Processing Dependency: perl-srpm-macros for package: redhat-rpm-config-9.1.0-88.el7.centos.noarch --> Processing Dependency: perl(Getopt::Long) for package: redhat-rpm-config-9.1.0-88.el7.centos.noarch --> Processing Dependency: /usr/bin/perl for package: redhat-rpm-config-9.1.0-88.el7.centos.noarch ---> Package rpm-build.x86_64 0:4.11.3-48.el7_9 will be installed --> Processing Dependency: pkgconfig >= 1:0.24 for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: elfutils >= 0.128 for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: perl(threads) for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: perl(Thread::Queue) for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: perl(File::Temp) for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: libpopt.so.0(LIBPOPT_0)(64bit) for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: libelf.so.1(ELFUTILS_1.0)(64bit) for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: file for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: /usr/bin/gdb-add-index for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: librpmio.so.3()(64bit) for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: librpmbuild.so.3()(64bit) for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: librpm.so.3()(64bit) for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: libpopt.so.0()(64bit) for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: libnss3.so()(64bit) for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: libmagic.so.1()(64bit) for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: liblzma.so.5()(64bit) for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: liblua-5.1.so()(64bit) for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: libelf.so.1()(64bit) for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: libdb-5.3.so()(64bit) for package: rpm-build-4.11.3-48.el7_9.x86_64 --> Processing Dependency: libaudit.so.1()(64bit) for package: rpm-build-4.11.3-48.el7_9.x86_64 ---> Package sed.x86_64 0:4.2.2-7.el7 will be installed ---> Package shadow-utils.x86_64 2:4.6-5.el7 will be installed --> Processing Dependency: setup for package: 2:shadow-utils-4.6-5.el7.x86_64 --> Processing Dependency: libsemanage.so.1(LIBSEMANAGE_1.0)(64bit) for package: 2:shadow-utils-4.6-5.el7.x86_64 --> Processing Dependency: libsemanage.so.1()(64bit) for package: 2:shadow-utils-4.6-5.el7.x86_64 ---> Package tar.x86_64 2:1.26-35.el7 will be installed ---> Package unzip.x86_64 0:6.0-24.el7_9 will be installed ---> Package util-linux.x86_64 0:2.23.2-65.el7_9.1 will be installed --> Processing Dependency: libuuid = 2.23.2-65.el7_9.1 for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libsmartcols = 2.23.2-65.el7_9.1 for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libmount = 2.23.2-65.el7_9.1 for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libblkid = 2.23.2-65.el7_9.1 for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: pam >= 1.1.3-7 for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libuuid.so.1(UUID_1.0)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libutempter.so.0(UTEMPTER_1.1)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libudev.so.1(LIBUDEV_183)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libsystemd.so.0(LIBSYSTEMD_209)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libsmartcols.so.1(SMARTCOLS_2.25)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libpam_misc.so.0(LIBPAM_MISC_1.0)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libpam.so.0(LIBPAM_1.0)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libmount.so.1(MOUNT_2.25)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libmount.so.1(MOUNT_2.23)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libmount.so.1(MOUNT_2.22)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libmount.so.1(MOUNT_2.21)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libmount.so.1(MOUNT_2.20)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libmount.so.1(MOUNT_2.19)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libblkid.so.1(BLKID_2.21)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libblkid.so.1(BLKID_2.20)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libblkid.so.1(BLKID_2.18)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libblkid.so.1(BLKID_2.17)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libblkid.so.1(BLKID_2.15)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libblkid.so.1(BLKID_1.0)(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: /etc/pam.d/system-auth for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libuuid.so.1()(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libutempter.so.0()(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libuser.so.1()(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libudev.so.1()(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libsystemd.so.0()(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libsmartcols.so.1()(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libpam_misc.so.0()(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libpam.so.0()(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libmount.so.1()(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libcap-ng.so.0()(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 --> Processing Dependency: libblkid.so.1()(64bit) for package: util-linux-2.23.2-65.el7_9.1.x86_64 ---> Package which.x86_64 0:2.20-7.el7 will be installed ---> Package xz.x86_64 0:5.2.2-2.el7_9 will be installed --> Running transaction check ---> Package audit-libs.x86_64 0:2.8.5-4.el7 will be installed ---> Package binutils.x86_64 0:2.27-44.base.el7_9.1 will be installed --> Processing Dependency: /usr/sbin/alternatives for package: binutils-2.27-44.base.el7_9.1.x86_64 --> Processing Dependency: /usr/sbin/alternatives for package: binutils-2.27-44.base.el7_9.1.x86_64 ---> Package bzip2-libs.x86_64 0:1.0.6-13.el7 will be installed ---> Package centos-release.x86_64 0:7-9.2009.1.el7.centos will be installed ---> Package cpp.x86_64 0:4.8.5-44.el7 will be installed --> Processing Dependency: filesystem >= 3 for package: cpp-4.8.5-44.el7.x86_64 ---> Package dwz.x86_64 0:0.11-3.el7 will be installed ---> Package elfutils.x86_64 0:0.176-5.el7 will be installed --> Processing Dependency: elfutils-libs(x86-64) = 0.176-5.el7 for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.175)(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.173)(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.171)(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.167)(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.165)(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.161)(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.160)(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.159)(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.158)(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.149)(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.148)(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.138)(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.130)(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.127)(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.126)(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libdw.so.1(ELFUTILS_0.122)(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libasm.so.1(ELFUTILS_1.0)(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libdw.so.1()(64bit) for package: elfutils-0.176-5.el7.x86_64 --> Processing Dependency: libasm.so.1()(64bit) for package: elfutils-0.176-5.el7.x86_64 ---> Package elfutils-libelf.x86_64 0:0.176-5.el7 will be installed ---> Package file.x86_64 0:5.11-37.el7 will be installed ---> Package file-libs.x86_64 0:5.11-37.el7 will be installed ---> Package gdb.x86_64 0:7.6.1-120.el7 will be installed --> Processing Dependency: libreadline.so.6()(64bit) for package: gdb-7.6.1-120.el7.x86_64 --> Processing Dependency: libpython2.7.so.1.0()(64bit) for package: gdb-7.6.1-120.el7.x86_64 --> Processing Dependency: libexpat.so.1()(64bit) for package: gdb-7.6.1-120.el7.x86_64 ---> Package glibc.x86_64 0:2.17-326.el7_9 will be installed --> Processing Dependency: glibc-common = 2.17-326.el7_9 for package: glibc-2.17-326.el7_9.x86_64 --> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3)(64bit) for package: glibc-2.17-326.el7_9.x86_64 --> Processing Dependency: basesystem for package: glibc-2.17-326.el7_9.x86_64 --> Processing Dependency: libfreebl3.so()(64bit) for package: glibc-2.17-326.el7_9.x86_64 ---> Package glibc-devel.x86_64 0:2.17-326.el7_9 will be installed --> Processing Dependency: glibc-headers = 2.17-326.el7_9 for package: glibc-devel-2.17-326.el7_9.x86_64 --> Processing Dependency: glibc-headers for package: glibc-devel-2.17-326.el7_9.x86_64 ---> Package gmp.x86_64 1:6.0.0-15.el7 will be installed ---> Package libacl.x86_64 0:2.2.51-15.el7 will be installed ---> Package libattr.x86_64 0:2.4.46-13.el7 will be installed ---> Package libblkid.x86_64 0:2.23.2-65.el7_9.1 will be installed ---> Package libcap.x86_64 0:2.22-11.el7 will be installed ---> Package libcap-ng.x86_64 0:0.7.5-4.el7 will be installed ---> Package libdb.x86_64 0:5.3.21-25.el7 will be installed ---> Package libgcc.x86_64 0:4.8.5-44.el7 will be installed ---> Package libgomp.x86_64 0:4.8.5-44.el7 will be installed ---> Package libmount.x86_64 0:2.23.2-65.el7_9.1 will be installed ---> Package libmpc.x86_64 0:1.0.1-3.el7 will be installed ---> Package libselinux.x86_64 0:2.5-15.el7 will be installed --> Processing Dependency: libsepol(x86-64) >= 2.5-10 for package: libselinux-2.5-15.el7.x86_64 --> Processing Dependency: libsepol.so.1(LIBSEPOL_1.0)(64bit) for package: libselinux-2.5-15.el7.x86_64 --> Processing Dependency: libsepol.so.1()(64bit) for package: libselinux-2.5-15.el7.x86_64 ---> Package libsemanage.x86_64 0:2.5-14.el7 will be installed --> Processing Dependency: libustr-1.0.so.1(USTR_1.0.1)(64bit) for package: libsemanage-2.5-14.el7.x86_64 --> Processing Dependency: libustr-1.0.so.1(USTR_1.0)(64bit) for package: libsemanage-2.5-14.el7.x86_64 --> Processing Dependency: libustr-1.0.so.1()(64bit) for package: libsemanage-2.5-14.el7.x86_64 ---> Package libsmartcols.x86_64 0:2.23.2-65.el7_9.1 will be installed ---> Package libstdc++.x86_64 0:4.8.5-44.el7 will be installed ---> Package libstdc++-devel.x86_64 0:4.8.5-44.el7 will be installed ---> Package libuser.x86_64 0:0.60-9.el7 will be installed --> Processing Dependency: libldap-2.4.so.2()(64bit) for package: libuser-0.60-9.el7.x86_64 --> Processing Dependency: libgobject-2.0.so.0()(64bit) for package: libuser-0.60-9.el7.x86_64 --> Processing Dependency: libgmodule-2.0.so.0()(64bit) for package: libuser-0.60-9.el7.x86_64 --> Processing Dependency: libglib-2.0.so.0()(64bit) for package: libuser-0.60-9.el7.x86_64 ---> Package libutempter.x86_64 0:1.1.6-4.el7 will be installed ---> Package libuuid.x86_64 0:2.23.2-65.el7_9.1 will be installed ---> Package lua.x86_64 0:5.1.4-15.el7 will be installed ---> Package lua-srpm-macros.noarch 0:1-3.el7 will be installed ---> Package mpfr.x86_64 0:3.1.1-4.el7 will be installed ---> Package ncurses.x86_64 0:5.9-14.20130511.el7_4 will be installed ---> Package ncurses-libs.x86_64 0:5.9-14.20130511.el7_4 will be installed --> Processing Dependency: ncurses-base = 5.9-14.20130511.el7_4 for package: ncurses-libs-5.9-14.20130511.el7_4.x86_64 ---> Package nss.x86_64 0:3.67.0-4.el7_9 will be installed --> Processing Dependency: nss-util >= 3.67.0-1 for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: nss-softokn(x86-64) >= 3.67.0-1 for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: nspr >= 4.31.0 for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: nss-system-init for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: nss-pem(x86-64) for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: libnssutil3.so(NSSUTIL_3.59)(64bit) for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: libnssutil3.so(NSSUTIL_3.39)(64bit) for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: libnssutil3.so(NSSUTIL_3.38)(64bit) for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: libnssutil3.so(NSSUTIL_3.31)(64bit) for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: libnssutil3.so(NSSUTIL_3.24)(64bit) for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: libnssutil3.so(NSSUTIL_3.21)(64bit) for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: libnssutil3.so(NSSUTIL_3.17.1)(64bit) for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: libnssutil3.so(NSSUTIL_3.15)(64bit) for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: libnssutil3.so(NSSUTIL_3.14)(64bit) for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: libnssutil3.so(NSSUTIL_3.13)(64bit) for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: libnssutil3.so(NSSUTIL_3.12.5)(64bit) for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: libnssutil3.so(NSSUTIL_3.12.3)(64bit) for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: libnssutil3.so(NSSUTIL_3.12)(64bit) for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: libplds4.so()(64bit) for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: libplc4.so()(64bit) for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: libnssutil3.so()(64bit) for package: nss-3.67.0-4.el7_9.x86_64 --> Processing Dependency: libnspr4.so()(64bit) for package: nss-3.67.0-4.el7_9.x86_64 ---> Package openssl-libs.x86_64 1:1.0.2k-25.el7_9 will be installed --> Processing Dependency: ca-certificates >= 2008-5 for package: 1:openssl-libs-1.0.2k-25.el7_9.x86_64 --> Processing Dependency: libkrb5.so.3(krb5_3_MIT)(64bit) for package: 1:openssl-libs-1.0.2k-25.el7_9.x86_64 --> Processing Dependency: libk5crypto.so.3(k5crypto_3_MIT)(64bit) for package: 1:openssl-libs-1.0.2k-25.el7_9.x86_64 --> Processing Dependency: libkrb5.so.3()(64bit) for package: 1:openssl-libs-1.0.2k-25.el7_9.x86_64 --> Processing Dependency: libk5crypto.so.3()(64bit) for package: 1:openssl-libs-1.0.2k-25.el7_9.x86_64 --> Processing Dependency: libgssapi_krb5.so.2()(64bit) for package: 1:openssl-libs-1.0.2k-25.el7_9.x86_64 --> Processing Dependency: libcom_err.so.2()(64bit) for package: 1:openssl-libs-1.0.2k-25.el7_9.x86_64 ---> Package pam.x86_64 0:1.1.8-23.el7 will be installed --> Processing Dependency: libpwquality >= 0.9.9 for package: pam-1.1.8-23.el7.x86_64 --> Processing Dependency: cracklib-dicts >= 2.8 for package: pam-1.1.8-23.el7.x86_64 --> Processing Dependency: libcrack.so.2()(64bit) for package: pam-1.1.8-23.el7.x86_64 ---> Package pcre.x86_64 0:8.32-17.el7 will be installed ---> Package perl.x86_64 4:5.16.3-299.el7_9 will be installed --> Processing Dependency: perl-libs = 4:5.16.3-299.el7_9 for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(Socket) >= 1.3 for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(Scalar::Util) >= 1.10 for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl-macros for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl-libs for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(threads::shared) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(constant) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(Time::Local) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(Time::HiRes) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(Storable) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(Socket) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(Scalar::Util) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(Pod::Simple::XHTML) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(Pod::Simple::Search) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(Filter::Util::Call) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(File::Spec::Unix) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(File::Spec::Functions) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(File::Spec) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(File::Path) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(Exporter) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(Cwd) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: perl(Carp) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: libperl.so()(64bit) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: libgdbm_compat.so.4()(64bit) for package: 4:perl-5.16.3-299.el7_9.x86_64 --> Processing Dependency: libgdbm.so.4()(64bit) for package: 4:perl-5.16.3-299.el7_9.x86_64 ---> Package perl-File-Temp.noarch 0:0.23.01-3.el7 will be installed ---> Package perl-Getopt-Long.noarch 0:2.40-3.el7 will be installed --> Processing Dependency: perl(Pod::Usage) >= 1.14 for package: perl-Getopt-Long-2.40-3.el7.noarch --> Processing Dependency: perl(Text::ParseWords) for package: perl-Getopt-Long-2.40-3.el7.noarch ---> Package perl-Thread-Queue.noarch 0:3.02-2.el7 will be installed ---> Package perl-srpm-macros.noarch 0:1-8.el7 will be installed ---> Package perl-threads.x86_64 0:1.87-4.el7 will be installed ---> Package pkgconfig.x86_64 1:0.27.1-4.el7 will be installed ---> Package popt.x86_64 0:1.13-16.el7 will be installed ---> Package python-rpm-macros.noarch 0:3-34.el7 will be installed ---> Package python-srpm-macros.noarch 0:3-34.el7 will be installed ---> Package python2-rpm-macros.noarch 0:3-34.el7 will be installed ---> Package rpm.x86_64 0:4.11.3-48.el7_9 will be installed --> Processing Dependency: curl for package: rpm-4.11.3-48.el7_9.x86_64 --> Processing Dependency: /usr/bin/db_stat for package: rpm-4.11.3-48.el7_9.x86_64 ---> Package rpm-build-libs.x86_64 0:4.11.3-48.el7_9 will be installed --> Processing Dependency: /usr/bin/gpg2 for package: rpm-build-libs-4.11.3-48.el7_9.x86_64 ---> Package rpm-libs.x86_64 0:4.11.3-48.el7_9 will be installed ---> Package setup.noarch 0:2.8.71-11.el7 will be installed ---> Package systemd-libs.x86_64 0:219-78.el7_9.5 will be installed --> Processing Dependency: libgcrypt.so.11(GCRYPT_1.2)(64bit) for package: systemd-libs-219-78.el7_9.5.x86_64 --> Processing Dependency: liblz4.so.1()(64bit) for package: systemd-libs-219-78.el7_9.5.x86_64 --> Processing Dependency: libgpg-error.so.0()(64bit) for package: systemd-libs-219-78.el7_9.5.x86_64 --> Processing Dependency: libgcrypt.so.11()(64bit) for package: systemd-libs-219-78.el7_9.5.x86_64 ---> Package xz-libs.x86_64 0:5.2.2-2.el7_9 will be installed ---> Package zip.x86_64 0:3.0-11.el7 will be installed ---> Package zlib.x86_64 0:1.2.7-20.el7_9 will be installed --> Running transaction check ---> Package basesystem.noarch 0:10.0-7.el7.centos will be installed ---> Package ca-certificates.noarch 0:2021.2.50-72.el7_9 will be installed --> Processing Dependency: p11-kit-trust >= 0.23.5 for package: ca-certificates-2021.2.50-72.el7_9.noarch --> Processing Dependency: p11-kit >= 0.23.5 for package: ca-certificates-2021.2.50-72.el7_9.noarch ---> Package chkconfig.x86_64 0:1.7.6-1.el7 will be installed ---> Package cracklib.x86_64 0:2.9.0-11.el7 will be installed ---> Package cracklib-dicts.x86_64 0:2.9.0-11.el7 will be installed ---> Package curl.x86_64 0:7.29.0-59.el7_9.1 will be installed --> Processing Dependency: libcurl = 7.29.0-59.el7_9.1 for package: curl-7.29.0-59.el7_9.1.x86_64 --> Processing Dependency: libcurl.so.4()(64bit) for package: curl-7.29.0-59.el7_9.1.x86_64 ---> Package elfutils-libs.x86_64 0:0.176-5.el7 will be installed --> Processing Dependency: default-yama-scope for package: elfutils-libs-0.176-5.el7.x86_64 ---> Package expat.x86_64 0:2.1.0-14.el7_9 will be installed ---> Package filesystem.x86_64 0:3.2-25.el7 will be installed ---> Package gdbm.x86_64 0:1.10-8.el7 will be installed ---> Package glib2.x86_64 0:2.56.1-9.el7_9 will be installed --> Processing Dependency: shared-mime-info for package: glib2-2.56.1-9.el7_9.x86_64 --> Processing Dependency: libffi.so.6()(64bit) for package: glib2-2.56.1-9.el7_9.x86_64 ---> Package glibc-common.x86_64 0:2.17-326.el7_9 will be installed --> Processing Dependency: tzdata >= 2003a for package: glibc-common-2.17-326.el7_9.x86_64 ---> Package glibc-headers.x86_64 0:2.17-326.el7_9 will be installed --> Processing Dependency: kernel-headers >= 2.2.1 for package: glibc-headers-2.17-326.el7_9.x86_64 --> Processing Dependency: kernel-headers for package: glibc-headers-2.17-326.el7_9.x86_64 ---> Package gnupg2.x86_64 0:2.0.22-5.el7_5 will be installed --> Processing Dependency: pinentry for package: gnupg2-2.0.22-5.el7_5.x86_64 --> Processing Dependency: libassuan.so.0(LIBASSUAN_1.0)(64bit) for package: gnupg2-2.0.22-5.el7_5.x86_64 --> Processing Dependency: libpth.so.20()(64bit) for package: gnupg2-2.0.22-5.el7_5.x86_64 --> Processing Dependency: libassuan.so.0()(64bit) for package: gnupg2-2.0.22-5.el7_5.x86_64 ---> Package krb5-libs.x86_64 0:1.15.1-54.el7_9 will be installed --> Processing Dependency: keyutils-libs >= 1.5.8 for package: krb5-libs-1.15.1-54.el7_9.x86_64 --> Processing Dependency: libkeyutils.so.1(KEYUTILS_1.5)(64bit) for package: krb5-libs-1.15.1-54.el7_9.x86_64 --> Processing Dependency: libkeyutils.so.1(KEYUTILS_1.0)(64bit) for package: krb5-libs-1.15.1-54.el7_9.x86_64 --> Processing Dependency: libkeyutils.so.1(KEYUTILS_0.3)(64bit) for package: krb5-libs-1.15.1-54.el7_9.x86_64 --> Processing Dependency: libverto.so.1()(64bit) for package: krb5-libs-1.15.1-54.el7_9.x86_64 --> Processing Dependency: libkeyutils.so.1()(64bit) for package: krb5-libs-1.15.1-54.el7_9.x86_64 ---> Package libcom_err.x86_64 0:1.42.9-19.el7 will be installed ---> Package libdb-utils.x86_64 0:5.3.21-25.el7 will be installed ---> Package libgcrypt.x86_64 0:1.5.3-14.el7 will be installed ---> Package libgpg-error.x86_64 0:1.12-3.el7 will be installed ---> Package libpwquality.x86_64 0:1.2.3-5.el7 will be installed ---> Package libsepol.x86_64 0:2.5-10.el7 will be installed ---> Package lz4.x86_64 0:1.8.3-1.el7 will be installed ---> Package ncurses-base.noarch 0:5.9-14.20130511.el7_4 will be installed ---> Package nspr.x86_64 0:4.32.0-1.el7_9 will be installed ---> Package nss-pem.x86_64 0:1.0.3-7.el7 will be installed ---> Package nss-softokn.x86_64 0:3.67.0-3.el7_9 will be installed --> Processing Dependency: libsqlite3.so.0()(64bit) for package: nss-softokn-3.67.0-3.el7_9.x86_64 ---> Package nss-softokn-freebl.x86_64 0:3.67.0-3.el7_9 will be installed ---> Package nss-sysinit.x86_64 0:3.67.0-4.el7_9 will be installed ---> Package nss-util.x86_64 0:3.67.0-1.el7_9 will be installed ---> Package openldap.x86_64 0:2.4.44-25.el7_9 will be installed --> Processing Dependency: nss-tools for package: openldap-2.4.44-25.el7_9.x86_64 --> Processing Dependency: libsasl2.so.3()(64bit) for package: openldap-2.4.44-25.el7_9.x86_64 ---> Package perl-Carp.noarch 0:1.26-244.el7 will be installed ---> Package perl-Exporter.noarch 0:5.68-3.el7 will be installed ---> Package perl-File-Path.noarch 0:2.09-2.el7 will be installed ---> Package perl-Filter.x86_64 0:1.49-3.el7 will be installed ---> Package perl-PathTools.x86_64 0:3.40-5.el7 will be installed ---> Package perl-Pod-Simple.noarch 1:3.28-4.el7 will be installed --> Processing Dependency: perl(Pod::Escapes) >= 1.04 for package: 1:perl-Pod-Simple-3.28-4.el7.noarch --> Processing Dependency: perl(Encode) for package: 1:perl-Pod-Simple-3.28-4.el7.noarch ---> Package perl-Pod-Usage.noarch 0:1.63-3.el7 will be installed --> Processing Dependency: perl(Pod::Text) >= 3.15 for package: perl-Pod-Usage-1.63-3.el7.noarch --> Processing Dependency: perl-Pod-Perldoc for package: perl-Pod-Usage-1.63-3.el7.noarch ---> Package perl-Scalar-List-Utils.x86_64 0:1.27-248.el7 will be installed ---> Package perl-Socket.x86_64 0:2.010-5.el7 will be installed ---> Package perl-Storable.x86_64 0:2.45-3.el7 will be installed ---> Package perl-Text-ParseWords.noarch 0:3.29-4.el7 will be installed ---> Package perl-Time-HiRes.x86_64 4:1.9725-3.el7 will be installed ---> Package perl-Time-Local.noarch 0:1.2300-2.el7 will be installed ---> Package perl-constant.noarch 0:1.27-2.el7 will be installed ---> Package perl-libs.x86_64 4:5.16.3-299.el7_9 will be installed ---> Package perl-macros.x86_64 4:5.16.3-299.el7_9 will be installed ---> Package perl-threads-shared.x86_64 0:1.43-6.el7 will be installed ---> Package python-libs.x86_64 0:2.7.5-92.el7_9 will be installed ---> Package readline.x86_64 0:6.2-11.el7 will be installed ---> Package ustr.x86_64 0:1.0.4-16.el7 will be installed --> Running transaction check ---> Package cyrus-sasl-lib.x86_64 0:2.1.26-24.el7_9 will be installed ---> Package elfutils-default-yama-scope.noarch 0:0.176-5.el7 will be installed --> Processing Dependency: systemd for package: elfutils-default-yama-scope-0.176-5.el7.noarch --> Processing Dependency: systemd for package: elfutils-default-yama-scope-0.176-5.el7.noarch ---> Package kernel-headers.x86_64 0:3.10.0-1160.71.1.el7 will be installed ---> Package keyutils-libs.x86_64 0:1.5.8-3.el7 will be installed ---> Package libassuan.x86_64 0:2.1.0-3.el7 will be installed ---> Package libcurl.x86_64 0:7.29.0-59.el7_9.1 will be installed --> Processing Dependency: libssh2(x86-64) >= 1.8.0 for package: libcurl-7.29.0-59.el7_9.1.x86_64 --> Processing Dependency: libidn.so.11(LIBIDN_1.0)(64bit) for package: libcurl-7.29.0-59.el7_9.1.x86_64 --> Processing Dependency: libssh2.so.1()(64bit) for package: libcurl-7.29.0-59.el7_9.1.x86_64 --> Processing Dependency: libidn.so.11()(64bit) for package: libcurl-7.29.0-59.el7_9.1.x86_64 ---> Package libffi.x86_64 0:3.0.13-19.el7 will be installed ---> Package libverto.x86_64 0:0.2.5-4.el7 will be installed ---> Package nss-tools.x86_64 0:3.67.0-4.el7_9 will be installed ---> Package p11-kit.x86_64 0:0.23.5-3.el7 will be installed ---> Package p11-kit-trust.x86_64 0:0.23.5-3.el7 will be installed --> Processing Dependency: libtasn1.so.6(LIBTASN1_0_3)(64bit) for package: p11-kit-trust-0.23.5-3.el7.x86_64 --> Processing Dependency: libtasn1.so.6()(64bit) for package: p11-kit-trust-0.23.5-3.el7.x86_64 ---> Package perl-Encode.x86_64 0:2.51-7.el7 will be installed ---> Package perl-Pod-Escapes.noarch 1:1.04-299.el7_9 will be installed ---> Package perl-Pod-Perldoc.noarch 0:3.20-4.el7 will be installed --> Processing Dependency: perl(parent) for package: perl-Pod-Perldoc-3.20-4.el7.noarch --> Processing Dependency: perl(HTTP::Tiny) for package: perl-Pod-Perldoc-3.20-4.el7.noarch --> Processing Dependency: groff-base for package: perl-Pod-Perldoc-3.20-4.el7.noarch ---> Package perl-podlators.noarch 0:2.5.1-3.el7 will be installed ---> Package pinentry.x86_64 0:0.8.1-17.el7 will be installed ---> Package pth.x86_64 0:2.0.7-23.el7 will be installed ---> Package shared-mime-info.x86_64 0:1.8-5.el7 will be installed --> Processing Dependency: libxml2.so.2(LIBXML2_2.4.30)(64bit) for package: shared-mime-info-1.8-5.el7.x86_64 --> Processing Dependency: libxml2.so.2()(64bit) for package: shared-mime-info-1.8-5.el7.x86_64 ---> Package sqlite.x86_64 0:3.7.17-8.el7_7.1 will be installed ---> Package tzdata.noarch 0:2022a-1.el7 will be installed --> Running transaction check ---> Package groff-base.x86_64 0:1.22.2-8.el7 will be installed ---> Package libidn.x86_64 0:1.28-4.el7 will be installed ---> Package libssh2.x86_64 0:1.8.0-4.el7 will be installed ---> Package libtasn1.x86_64 0:4.10-1.el7 will be installed ---> Package libxml2.x86_64 0:2.9.1-6.el7_9.6 will be installed ---> Package perl-HTTP-Tiny.noarch 0:0.033-3.el7 will be installed ---> Package perl-parent.noarch 1:0.225-244.el7 will be installed ---> Package systemd.x86_64 0:219-78.el7_9.5 will be installed --> Processing Dependency: kmod >= 18-4 for package: systemd-219-78.el7_9.5.x86_64 --> Processing Dependency: libkmod.so.2(LIBKMOD_5)(64bit) for package: systemd-219-78.el7_9.5.x86_64 --> Processing Dependency: libcryptsetup.so.12(CRYPTSETUP_2.0)(64bit) for package: systemd-219-78.el7_9.5.x86_64 --> Processing Dependency: dbus for package: systemd-219-78.el7_9.5.x86_64 --> Processing Dependency: acl for package: systemd-219-78.el7_9.5.x86_64 --> Processing Dependency: libqrencode.so.3()(64bit) for package: systemd-219-78.el7_9.5.x86_64 --> Processing Dependency: libkmod.so.2()(64bit) for package: systemd-219-78.el7_9.5.x86_64 --> Processing Dependency: libcryptsetup.so.12()(64bit) for package: systemd-219-78.el7_9.5.x86_64 --> Running transaction check ---> Package acl.x86_64 0:2.2.51-15.el7 will be installed ---> Package cryptsetup-libs.x86_64 0:2.0.3-6.el7 will be installed --> Processing Dependency: libdevmapper.so.1.02(DM_1_02_97)(64bit) for package: cryptsetup-libs-2.0.3-6.el7.x86_64 --> Processing Dependency: libdevmapper.so.1.02(Base)(64bit) for package: cryptsetup-libs-2.0.3-6.el7.x86_64 --> Processing Dependency: libjson-c.so.2()(64bit) for package: cryptsetup-libs-2.0.3-6.el7.x86_64 --> Processing Dependency: libdevmapper.so.1.02()(64bit) for package: cryptsetup-libs-2.0.3-6.el7.x86_64 ---> Package dbus.x86_64 1:1.10.24-15.el7 will be installed --> Processing Dependency: dbus-libs(x86-64) = 1:1.10.24-15.el7 for package: 1:dbus-1.10.24-15.el7.x86_64 --> Processing Dependency: libdbus-1.so.3(LIBDBUS_PRIVATE_1.10.24)(64bit) for package: 1:dbus-1.10.24-15.el7.x86_64 --> Processing Dependency: libdbus-1.so.3(LIBDBUS_1_3)(64bit) for package: 1:dbus-1.10.24-15.el7.x86_64 --> Processing Dependency: libdbus-1.so.3()(64bit) for package: 1:dbus-1.10.24-15.el7.x86_64 ---> Package kmod.x86_64 0:20-28.el7 will be installed --> Processing Dependency: dracut for package: kmod-20-28.el7.x86_64 ---> Package kmod-libs.x86_64 0:20-28.el7 will be installed ---> Package qrencode-libs.x86_64 0:3.4.1-3.el7 will be installed --> Running transaction check ---> Package dbus-libs.x86_64 1:1.10.24-15.el7 will be installed ---> Package device-mapper-libs.x86_64 7:1.02.170-6.el7_9.5 will be installed --> Processing Dependency: device-mapper = 7:1.02.170-6.el7_9.5 for package: 7:device-mapper-libs-1.02.170-6.el7_9.5.x86_64 ---> Package dracut.x86_64 0:033-572.el7 will be installed --> Processing Dependency: procps-ng for package: dracut-033-572.el7.x86_64 --> Processing Dependency: kpartx for package: dracut-033-572.el7.x86_64 --> Processing Dependency: hardlink for package: dracut-033-572.el7.x86_64 ---> Package json-c.x86_64 0:0.11-4.el7_0 will be installed --> Running transaction check ---> Package device-mapper.x86_64 7:1.02.170-6.el7_9.5 will be installed ---> Package hardlink.x86_64 1:1.0-19.el7 will be installed ---> Package kpartx.x86_64 0:0.4.9-135.el7_9 will be installed ---> Package procps-ng.x86_64 0:3.3.10-28.el7 will be installed --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing for group install "Buildsystem building group": bash x86_64 4.2.46-35.el7_9 updates 1.0 M bzip2 x86_64 1.0.6-13.el7 base 52 k coreutils x86_64 8.22-24.el7_9.2 updates 3.3 M cpio x86_64 2.11-28.el7 base 211 k diffutils x86_64 3.3-5.el7 base 322 k epel-release noarch 7-14 epel 15 k epel-rpm-macros noarch 7-35 epel 19 k findutils x86_64 1:4.5.11-6.el7 base 559 k gawk x86_64 4.0.2-4.el7_3.1 base 874 k gcc x86_64 4.8.5-44.el7 base 16 M gcc-c++ x86_64 4.8.5-44.el7 base 7.2 M grep x86_64 2.20-3.el7 base 344 k gzip x86_64 1.5-11.el7_9 updates 130 k info x86_64 5.1-5.el7 base 233 k make x86_64 1:3.82-24.el7 base 421 k patch x86_64 2.7.1-12.el7_7 base 111 k redhat-rpm-config noarch 9.1.0-88.el7.centos base 81 k rpm-build x86_64 4.11.3-48.el7_9 updates 150 k sed x86_64 4.2.2-7.el7 base 231 k shadow-utils x86_64 2:4.6-5.el7 base 1.2 M tar x86_64 2:1.26-35.el7 base 846 k unzip x86_64 6.0-24.el7_9 updates 172 k util-linux x86_64 2.23.2-65.el7_9.1 updates 2.0 M which x86_64 2.20-7.el7 base 41 k xz x86_64 5.2.2-2.el7_9 updates 229 k Installing for dependencies: acl x86_64 2.2.51-15.el7 base 81 k audit-libs x86_64 2.8.5-4.el7 base 102 k basesystem noarch 10.0-7.el7.centos base 5.0 k binutils x86_64 2.27-44.base.el7_9.1 updates 5.9 M bzip2-libs x86_64 1.0.6-13.el7 base 40 k ca-certificates noarch 2021.2.50-72.el7_9 updates 379 k centos-release x86_64 7-9.2009.1.el7.centos updates 27 k chkconfig x86_64 1.7.6-1.el7 base 182 k cpp x86_64 4.8.5-44.el7 base 5.9 M cracklib x86_64 2.9.0-11.el7 base 80 k cracklib-dicts x86_64 2.9.0-11.el7 base 3.6 M cryptsetup-libs x86_64 2.0.3-6.el7 base 339 k curl x86_64 7.29.0-59.el7_9.1 updates 271 k cyrus-sasl-lib x86_64 2.1.26-24.el7_9 updates 156 k dbus x86_64 1:1.10.24-15.el7 base 245 k dbus-libs x86_64 1:1.10.24-15.el7 base 169 k device-mapper x86_64 7:1.02.170-6.el7_9.5 updates 297 k device-mapper-libs x86_64 7:1.02.170-6.el7_9.5 updates 325 k dracut x86_64 033-572.el7 base 329 k dwz x86_64 0.11-3.el7 base 99 k elfutils x86_64 0.176-5.el7 base 308 k elfutils-default-yama-scope noarch 0.176-5.el7 base 33 k elfutils-libelf x86_64 0.176-5.el7 base 195 k elfutils-libs x86_64 0.176-5.el7 base 291 k expat x86_64 2.1.0-14.el7_9 updates 83 k file x86_64 5.11-37.el7 base 57 k file-libs x86_64 5.11-37.el7 base 340 k filesystem x86_64 3.2-25.el7 base 1.0 M gdb x86_64 7.6.1-120.el7 base 2.4 M gdbm x86_64 1.10-8.el7 base 70 k glib2 x86_64 2.56.1-9.el7_9 updates 2.5 M glibc x86_64 2.17-326.el7_9 updates 3.6 M glibc-common x86_64 2.17-326.el7_9 updates 12 M glibc-devel x86_64 2.17-326.el7_9 updates 1.1 M glibc-headers x86_64 2.17-326.el7_9 updates 691 k gmp x86_64 1:6.0.0-15.el7 base 281 k gnupg2 x86_64 2.0.22-5.el7_5 base 1.5 M groff-base x86_64 1.22.2-8.el7 base 942 k hardlink x86_64 1:1.0-19.el7 base 14 k json-c x86_64 0.11-4.el7_0 base 31 k kernel-headers x86_64 3.10.0-1160.71.1.el7 updates 9.1 M keyutils-libs x86_64 1.5.8-3.el7 base 25 k kmod x86_64 20-28.el7 base 123 k kmod-libs x86_64 20-28.el7 base 51 k kpartx x86_64 0.4.9-135.el7_9 updates 81 k krb5-libs x86_64 1.15.1-54.el7_9 updates 810 k libacl x86_64 2.2.51-15.el7 base 27 k libassuan x86_64 2.1.0-3.el7 base 63 k libattr x86_64 2.4.46-13.el7 base 18 k libblkid x86_64 2.23.2-65.el7_9.1 updates 183 k libcap x86_64 2.22-11.el7 base 47 k libcap-ng x86_64 0.7.5-4.el7 base 25 k libcom_err x86_64 1.42.9-19.el7 base 42 k libcurl x86_64 7.29.0-59.el7_9.1 updates 223 k libdb x86_64 5.3.21-25.el7 base 720 k libdb-utils x86_64 5.3.21-25.el7 base 132 k libffi x86_64 3.0.13-19.el7 base 30 k libgcc x86_64 4.8.5-44.el7 base 103 k libgcrypt x86_64 1.5.3-14.el7 base 263 k libgomp x86_64 4.8.5-44.el7 base 159 k libgpg-error x86_64 1.12-3.el7 base 87 k libidn x86_64 1.28-4.el7 base 209 k libmount x86_64 2.23.2-65.el7_9.1 updates 185 k libmpc x86_64 1.0.1-3.el7 base 51 k libpwquality x86_64 1.2.3-5.el7 base 85 k libselinux x86_64 2.5-15.el7 base 162 k libsemanage x86_64 2.5-14.el7 base 151 k libsepol x86_64 2.5-10.el7 base 297 k libsmartcols x86_64 2.23.2-65.el7_9.1 updates 143 k libssh2 x86_64 1.8.0-4.el7 base 88 k libstdc++ x86_64 4.8.5-44.el7 base 306 k libstdc++-devel x86_64 4.8.5-44.el7 base 1.5 M libtasn1 x86_64 4.10-1.el7 base 320 k libuser x86_64 0.60-9.el7 base 400 k libutempter x86_64 1.1.6-4.el7 base 25 k libuuid x86_64 2.23.2-65.el7_9.1 updates 84 k libverto x86_64 0.2.5-4.el7 base 16 k libxml2 x86_64 2.9.1-6.el7_9.6 updates 668 k lua x86_64 5.1.4-15.el7 base 201 k lua-srpm-macros noarch 1-3.el7 epel 4.8 k lz4 x86_64 1.8.3-1.el7 base 85 k mpfr x86_64 3.1.1-4.el7 base 203 k ncurses x86_64 5.9-14.20130511.el7_4 base 304 k ncurses-base noarch 5.9-14.20130511.el7_4 base 68 k ncurses-libs x86_64 5.9-14.20130511.el7_4 base 316 k nspr x86_64 4.32.0-1.el7_9 updates 127 k nss x86_64 3.67.0-4.el7_9 updates 882 k nss-pem x86_64 1.0.3-7.el7 base 74 k nss-softokn x86_64 3.67.0-3.el7_9 updates 358 k nss-softokn-freebl x86_64 3.67.0-3.el7_9 updates 337 k nss-sysinit x86_64 3.67.0-4.el7_9 updates 66 k nss-tools x86_64 3.67.0-4.el7_9 updates 549 k nss-util x86_64 3.67.0-1.el7_9 updates 79 k openldap x86_64 2.4.44-25.el7_9 updates 356 k openssl-libs x86_64 1:1.0.2k-25.el7_9 updates 1.2 M p11-kit x86_64 0.23.5-3.el7 base 252 k p11-kit-trust x86_64 0.23.5-3.el7 base 129 k pam x86_64 1.1.8-23.el7 base 721 k pcre x86_64 8.32-17.el7 base 422 k perl x86_64 4:5.16.3-299.el7_9 updates 8.0 M perl-Carp noarch 1.26-244.el7 base 19 k perl-Encode x86_64 2.51-7.el7 base 1.5 M perl-Exporter noarch 5.68-3.el7 base 28 k perl-File-Path noarch 2.09-2.el7 base 26 k perl-File-Temp noarch 0.23.01-3.el7 base 56 k perl-Filter x86_64 1.49-3.el7 base 76 k perl-Getopt-Long noarch 2.40-3.el7 base 56 k perl-HTTP-Tiny noarch 0.033-3.el7 base 38 k perl-PathTools x86_64 3.40-5.el7 base 82 k perl-Pod-Escapes noarch 1:1.04-299.el7_9 updates 52 k perl-Pod-Perldoc noarch 3.20-4.el7 base 87 k perl-Pod-Simple noarch 1:3.28-4.el7 base 216 k perl-Pod-Usage noarch 1.63-3.el7 base 27 k perl-Scalar-List-Utils x86_64 1.27-248.el7 base 36 k perl-Socket x86_64 2.010-5.el7 base 49 k perl-Storable x86_64 2.45-3.el7 base 77 k perl-Text-ParseWords noarch 3.29-4.el7 base 14 k perl-Thread-Queue noarch 3.02-2.el7 base 17 k perl-Time-HiRes x86_64 4:1.9725-3.el7 base 45 k perl-Time-Local noarch 1.2300-2.el7 base 24 k perl-constant noarch 1.27-2.el7 base 19 k perl-libs x86_64 4:5.16.3-299.el7_9 updates 690 k perl-macros x86_64 4:5.16.3-299.el7_9 updates 44 k perl-parent noarch 1:0.225-244.el7 base 12 k perl-podlators noarch 2.5.1-3.el7 base 112 k perl-srpm-macros noarch 1-8.el7 base 4.6 k perl-threads x86_64 1.87-4.el7 base 49 k perl-threads-shared x86_64 1.43-6.el7 base 39 k pinentry x86_64 0.8.1-17.el7 base 73 k pkgconfig x86_64 1:0.27.1-4.el7 base 54 k popt x86_64 1.13-16.el7 base 42 k procps-ng x86_64 3.3.10-28.el7 base 291 k pth x86_64 2.0.7-23.el7 base 89 k python-libs x86_64 2.7.5-92.el7_9 updates 5.6 M python-rpm-macros noarch 3-34.el7 base 9.1 k python-srpm-macros noarch 3-34.el7 base 8.8 k python2-rpm-macros noarch 3-34.el7 base 8.1 k qrencode-libs x86_64 3.4.1-3.el7 base 50 k readline x86_64 6.2-11.el7 base 193 k rpm x86_64 4.11.3-48.el7_9 updates 1.2 M rpm-build-libs x86_64 4.11.3-48.el7_9 updates 108 k rpm-libs x86_64 4.11.3-48.el7_9 updates 279 k setup noarch 2.8.71-11.el7 base 166 k shared-mime-info x86_64 1.8-5.el7 base 312 k sqlite x86_64 3.7.17-8.el7_7.1 base 394 k systemd x86_64 219-78.el7_9.5 updates 5.1 M systemd-libs x86_64 219-78.el7_9.5 updates 419 k tzdata noarch 2022a-1.el7 updates 501 k ustr x86_64 1.0.4-16.el7 base 92 k xz-libs x86_64 5.2.2-2.el7_9 updates 103 k zip x86_64 3.0-11.el7 base 260 k zlib x86_64 1.2.7-20.el7_9 updates 90 k Transaction Summary ================================================================================ Install 25 Packages (+152 Dependent packages) Total download size: 131 M Installed size: 563 M Downloading packages: warning: /var/lib/mock/centos+epel-7-x86_64-1658945077.221752/root/var/cache/yum/base/packages/acl-2.2.51-15.el7.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY Public key for acl-2.2.51-15.el7.x86_64.rpm is not installed (1/177): acl-2.2.51-15.el7.x86_64.rpm | 81 kB 00:00 (2/177): basesystem-10.0-7.el7.centos.noarch.rpm | 5.0 kB 00:00 (3/177): audit-libs-2.8.5-4.el7.x86_64.rpm | 102 kB 00:00 (4/177): bzip2-1.0.6-13.el7.x86_64.rpm | 52 kB 00:00 (5/177): bzip2-libs-1.0.6-13.el7.x86_64.rpm | 40 kB 00:00 Public key for bash-4.2.46-35.el7_9.x86_64.rpm is not installed (6/177): bash-4.2.46-35.el7_9.x86_64.rpm | 1.0 MB 00:00 (7/177): ca-certificates-2021.2.50-72.el7_9.noarch.rpm | 379 kB 00:00 (8/177): centos-release-7-9.2009.1.el7.centos.x86_64.rpm | 27 kB 00:00 (9/177): binutils-2.27-44.base.el7_9.1.x86_64.rpm | 5.9 MB 00:00 (10/177): chkconfig-1.7.6-1.el7.x86_64.rpm | 182 kB 00:00 (11/177): coreutils-8.22-24.el7_9.2.x86_64.rpm | 3.3 MB 00:00 (12/177): cpio-2.11-28.el7.x86_64.rpm | 211 kB 00:00 (13/177): cracklib-2.9.0-11.el7.x86_64.rpm | 80 kB 00:00 (14/177): cpp-4.8.5-44.el7.x86_64.rpm | 5.9 MB 00:00 (15/177): curl-7.29.0-59.el7_9.1.x86_64.rpm | 271 kB 00:00 (16/177): cryptsetup-libs-2.0.3-6.el7.x86_64.rpm | 339 kB 00:00 (17/177): dbus-1.10.24-15.el7.x86_64.rpm | 245 kB 00:00 (18/177): cracklib-dicts-2.9.0-11.el7.x86_64.rpm | 3.6 MB 00:00 (19/177): dbus-libs-1.10.24-15.el7.x86_64.rpm | 169 kB 00:00 (20/177): device-mapper-1.02.170-6.el7_9.5.x86_64.rpm | 297 kB 00:00 (21/177): device-mapper-libs-1.02.170-6.el7_9.5.x86_64.rpm | 325 kB 00:00 (22/177): diffutils-3.3-5.el7.x86_64.rpm | 322 kB 00:00 (23/177): cyrus-sasl-lib-2.1.26-24.el7_9.x86_64.rpm | 156 kB 00:00 (24/177): dwz-0.11-3.el7.x86_64.rpm | 99 kB 00:00 (25/177): elfutils-0.176-5.el7.x86_64.rpm | 308 kB 00:00 (26/177): elfutils-default-yama-scope-0.176-5.el7.noarch.r | 33 kB 00:00 (27/177): elfutils-libelf-0.176-5.el7.x86_64.rpm | 195 kB 00:00 (28/177): elfutils-libs-0.176-5.el7.x86_64.rpm | 291 kB 00:00 (29/177): dracut-033-572.el7.x86_64.rpm | 329 kB 00:00 (30/177): expat-2.1.0-14.el7_9.x86_64.rpm | 83 kB 00:00 (31/177): file-5.11-37.el7.x86_64.rpm | 57 kB 00:00 (32/177): file-libs-5.11-37.el7.x86_64.rpm | 340 kB 00:00 (33/177): filesystem-3.2-25.el7.x86_64.rpm | 1.0 MB 00:00 warning: /var/lib/mock/centos+epel-7-x86_64-1658945077.221752/root/var/cache/yum/epel/packages/epel-release-7-14.noarch.rpm: Header V4 RSA/SHA256 Signature, key ID 352c64e5: NOKEY Public key for epel-release-7-14.noarch.rpm is not installed (34/177): epel-release-7-14.noarch.rpm | 15 kB 00:00 (35/177): findutils-4.5.11-6.el7.x86_64.rpm | 559 kB 00:00 (36/177): gawk-4.0.2-4.el7_3.1.x86_64.rpm | 874 kB 00:00 (37/177): epel-rpm-macros-7-35.noarch.rpm | 19 kB 00:00 (38/177): gcc-4.8.5-44.el7.x86_64.rpm | 16 MB 00:00 (39/177): gcc-c++-4.8.5-44.el7.x86_64.rpm | 7.2 MB 00:00 (40/177): gdbm-1.10-8.el7.x86_64.rpm | 70 kB 00:00 (41/177): gdb-7.6.1-120.el7.x86_64.rpm | 2.4 MB 00:00 (42/177): glibc-2.17-326.el7_9.x86_64.rpm | 3.6 MB 00:00 (43/177): glib2-2.56.1-9.el7_9.x86_64.rpm | 2.5 MB 00:00 (44/177): glibc-common-2.17-326.el7_9.x86_64.rpm | 12 MB 00:00 (45/177): gmp-6.0.0-15.el7.x86_64.rpm | 281 kB 00:00 (46/177): grep-2.20-3.el7.x86_64.rpm | 344 kB 00:00 (47/177): glibc-headers-2.17-326.el7_9.x86_64.rpm | 691 kB 00:00 (48/177): gzip-1.5-11.el7_9.x86_64.rpm | 130 kB 00:00 (49/177): groff-base-1.22.2-8.el7.x86_64.rpm | 942 kB 00:00 (50/177): hardlink-1.0-19.el7.x86_64.rpm | 14 kB 00:00 (51/177): info-5.1-5.el7.x86_64.rpm | 233 kB 00:00 (52/177): glibc-devel-2.17-326.el7_9.x86_64.rpm | 1.1 MB 00:00 (53/177): json-c-0.11-4.el7_0.x86_64.rpm | 31 kB 00:00 (54/177): keyutils-libs-1.5.8-3.el7.x86_64.rpm | 25 kB 00:00 (55/177): kmod-20-28.el7.x86_64.rpm | 123 kB 00:00 (56/177): gnupg2-2.0.22-5.el7_5.x86_64.rpm | 1.5 MB 00:00 (57/177): kmod-libs-20-28.el7.x86_64.rpm | 51 kB 00:00 (58/177): kpartx-0.4.9-135.el7_9.x86_64.rpm | 81 kB 00:00 (59/177): libacl-2.2.51-15.el7.x86_64.rpm | 27 kB 00:00 (60/177): libattr-2.4.46-13.el7.x86_64.rpm | 18 kB 00:00 (61/177): libassuan-2.1.0-3.el7.x86_64.rpm | 63 kB 00:00 (62/177): krb5-libs-1.15.1-54.el7_9.x86_64.rpm | 810 kB 00:00 (63/177): libcap-2.22-11.el7.x86_64.rpm | 47 kB 00:00 (64/177): libblkid-2.23.2-65.el7_9.1.x86_64.rpm | 183 kB 00:00 (65/177): libcom_err-1.42.9-19.el7.x86_64.rpm | 42 kB 00:00 (66/177): libcap-ng-0.7.5-4.el7.x86_64.rpm | 25 kB 00:00 (67/177): kernel-headers-3.10.0-1160.71.1.el7.x86_64.rpm | 9.1 MB 00:00 (68/177): libcurl-7.29.0-59.el7_9.1.x86_64.rpm | 223 kB 00:00 (69/177): libdb-5.3.21-25.el7.x86_64.rpm | 720 kB 00:00 (70/177): libdb-utils-5.3.21-25.el7.x86_64.rpm | 132 kB 00:00 (71/177): libffi-3.0.13-19.el7.x86_64.rpm | 30 kB 00:00 (72/177): libgcrypt-1.5.3-14.el7.x86_64.rpm | 263 kB 00:00 (73/177): libgcc-4.8.5-44.el7.x86_64.rpm | 103 kB 00:00 (74/177): libgomp-4.8.5-44.el7.x86_64.rpm | 159 kB 00:00 (75/177): libgpg-error-1.12-3.el7.x86_64.rpm | 87 kB 00:00 (76/177): libidn-1.28-4.el7.x86_64.rpm | 209 kB 00:00 (77/177): libmpc-1.0.1-3.el7.x86_64.rpm | 51 kB 00:00 (78/177): libpwquality-1.2.3-5.el7.x86_64.rpm | 85 kB 00:00 (79/177): libmount-2.23.2-65.el7_9.1.x86_64.rpm | 185 kB 00:00 (80/177): libsemanage-2.5-14.el7.x86_64.rpm | 151 kB 00:00 (81/177): libselinux-2.5-15.el7.x86_64.rpm | 162 kB 00:00 (82/177): libsepol-2.5-10.el7.x86_64.rpm | 297 kB 00:00 (83/177): libssh2-1.8.0-4.el7.x86_64.rpm | 88 kB 00:00 (84/177): libstdc++-4.8.5-44.el7.x86_64.rpm | 306 kB 00:00 (85/177): libsmartcols-2.23.2-65.el7_9.1.x86_64.rpm | 143 kB 00:00 (86/177): libtasn1-4.10-1.el7.x86_64.rpm | 320 kB 00:00 (87/177): libuser-0.60-9.el7.x86_64.rpm | 400 kB 00:00 (88/177): libstdc++-devel-4.8.5-44.el7.x86_64.rpm | 1.5 MB 00:00 (89/177): libutempter-1.1.6-4.el7.x86_64.rpm | 25 kB 00:00 (90/177): libuuid-2.23.2-65.el7_9.1.x86_64.rpm | 84 kB 00:00 (91/177): libverto-0.2.5-4.el7.x86_64.rpm | 16 kB 00:00 (92/177): lua-5.1.4-15.el7.x86_64.rpm | 201 kB 00:00 (93/177): lz4-1.8.3-1.el7.x86_64.rpm | 85 kB 00:00 (94/177): make-3.82-24.el7.x86_64.rpm | 421 kB 00:00 (95/177): mpfr-3.1.1-4.el7.x86_64.rpm | 203 kB 00:00 (96/177): lua-srpm-macros-1-3.el7.noarch.rpm | 4.8 kB 00:00 (97/177): ncurses-base-5.9-14.20130511.el7_4.noarch.rpm | 68 kB 00:00 (98/177): ncurses-5.9-14.20130511.el7_4.x86_64.rpm | 304 kB 00:00 (99/177): ncurses-libs-5.9-14.20130511.el7_4.x86_64.rpm | 316 kB 00:00 (100/177): nspr-4.32.0-1.el7_9.x86_64.rpm | 127 kB 00:00 (101/177): nss-pem-1.0.3-7.el7.x86_64.rpm | 74 kB 00:00 (102/177): libxml2-2.9.1-6.el7_9.6.x86_64.rpm | 668 kB 00:00 (103/177): nss-softokn-3.67.0-3.el7_9.x86_64.rpm | 358 kB 00:00 (104/177): nss-softokn-freebl-3.67.0-3.el7_9.x86_64.rpm | 337 kB 00:00 (105/177): nss-sysinit-3.67.0-4.el7_9.x86_64.rpm | 66 kB 00:00 (106/177): nss-tools-3.67.0-4.el7_9.x86_64.rpm | 549 kB 00:00 (107/177): nss-util-3.67.0-1.el7_9.x86_64.rpm | 79 kB 00:00 (108/177): nss-3.67.0-4.el7_9.x86_64.rpm | 882 kB 00:00 (109/177): openldap-2.4.44-25.el7_9.x86_64.rpm | 356 kB 00:00 (110/177): p11-kit-0.23.5-3.el7.x86_64.rpm | 252 kB 00:00 (111/177): pam-1.1.8-23.el7.x86_64.rpm | 721 kB 00:00 (112/177): patch-2.7.1-12.el7_7.x86_64.rpm | 111 kB 00:00 (113/177): pcre-8.32-17.el7.x86_64.rpm | 422 kB 00:00 (114/177): perl-Carp-1.26-244.el7.noarch.rpm | 19 kB 00:00 (115/177): p11-kit-trust-0.23.5-3.el7.x86_64.rpm | 129 kB 00:00 (116/177): perl-Encode-2.51-7.el7.x86_64.rpm | 1.5 MB 00:00 (117/177): perl-Exporter-5.68-3.el7.noarch.rpm | 28 kB 00:00 (118/177): perl-File-Path-2.09-2.el7.noarch.rpm | 26 kB 00:00 (119/177): perl-File-Temp-0.23.01-3.el7.noarch.rpm | 56 kB 00:00 (120/177): perl-Filter-1.49-3.el7.x86_64.rpm | 76 kB 00:00 (121/177): perl-Getopt-Long-2.40-3.el7.noarch.rpm | 56 kB 00:00 (122/177): perl-HTTP-Tiny-0.033-3.el7.noarch.rpm | 38 kB 00:00 (123/177): perl-5.16.3-299.el7_9.x86_64.rpm | 8.0 MB 00:00 (124/177): perl-PathTools-3.40-5.el7.x86_64.rpm | 82 kB 00:00 (125/177): perl-Pod-Perldoc-3.20-4.el7.noarch.rpm | 87 kB 00:00 (126/177): perl-Pod-Escapes-1.04-299.el7_9.noarch.rpm | 52 kB 00:00 (127/177): perl-Pod-Usage-1.63-3.el7.noarch.rpm | 27 kB 00:00 (128/177): perl-Scalar-List-Utils-1.27-248.el7.x86_64.rpm | 36 kB 00:00 (129/177): perl-Pod-Simple-3.28-4.el7.noarch.rpm | 216 kB 00:00 (130/177): openssl-libs-1.0.2k-25.el7_9.x86_64.rpm | 1.2 MB 00:00 (131/177): perl-Socket-2.010-5.el7.x86_64.rpm | 49 kB 00:00 (132/177): perl-Storable-2.45-3.el7.x86_64.rpm | 77 kB 00:00 (133/177): perl-Text-ParseWords-3.29-4.el7.noarch.rpm | 14 kB 00:00 (134/177): perl-Thread-Queue-3.02-2.el7.noarch.rpm | 17 kB 00:00 (135/177): perl-Time-HiRes-1.9725-3.el7.x86_64.rpm | 45 kB 00:00 (136/177): perl-Time-Local-1.2300-2.el7.noarch.rpm | 24 kB 00:00 (137/177): perl-constant-1.27-2.el7.noarch.rpm | 19 kB 00:00 (138/177): perl-parent-0.225-244.el7.noarch.rpm | 12 kB 00:00 (139/177): perl-podlators-2.5.1-3.el7.noarch.rpm | 112 kB 00:00 (140/177): perl-srpm-macros-1-8.el7.noarch.rpm | 4.6 kB 00:00 (141/177): perl-threads-1.87-4.el7.x86_64.rpm | 49 kB 00:00 (142/177): perl-threads-shared-1.43-6.el7.x86_64.rpm | 39 kB 00:00 (143/177): pinentry-0.8.1-17.el7.x86_64.rpm | 73 kB 00:00 (144/177): pkgconfig-0.27.1-4.el7.x86_64.rpm | 54 kB 00:00 (145/177): popt-1.13-16.el7.x86_64.rpm | 42 kB 00:00 (146/177): pth-2.0.7-23.el7.x86_64.rpm | 89 kB 00:00 (147/177): perl-macros-5.16.3-299.el7_9.x86_64.rpm | 44 kB 00:00 (148/177): procps-ng-3.3.10-28.el7.x86_64.rpm | 291 kB 00:00 (149/177): python-rpm-macros-3-34.el7.noarch.rpm | 9.1 kB 00:00 (150/177): python-srpm-macros-3-34.el7.noarch.rpm | 8.8 kB 00:00 (151/177): perl-libs-5.16.3-299.el7_9.x86_64.rpm | 690 kB 00:00 (152/177): python2-rpm-macros-3-34.el7.noarch.rpm | 8.1 kB 00:00 (153/177): qrencode-libs-3.4.1-3.el7.x86_64.rpm | 50 kB 00:00 (154/177): readline-6.2-11.el7.x86_64.rpm | 193 kB 00:00 (155/177): redhat-rpm-config-9.1.0-88.el7.centos.noarch.rp | 81 kB 00:00 (156/177): python-libs-2.7.5-92.el7_9.x86_64.rpm | 5.6 MB 00:00 (157/177): rpm-build-4.11.3-48.el7_9.x86_64.rpm | 150 kB 00:00 (158/177): rpm-build-libs-4.11.3-48.el7_9.x86_64.rpm | 108 kB 00:00 (159/177): rpm-4.11.3-48.el7_9.x86_64.rpm | 1.2 MB 00:00 (160/177): rpm-libs-4.11.3-48.el7_9.x86_64.rpm | 279 kB 00:00 (161/177): sed-4.2.2-7.el7.x86_64.rpm | 231 kB 00:00 (162/177): shadow-utils-4.6-5.el7.x86_64.rpm | 1.2 MB 00:00 (163/177): shared-mime-info-1.8-5.el7.x86_64.rpm | 312 kB 00:00 (164/177): setup-2.8.71-11.el7.noarch.rpm | 166 kB 00:00 (165/177): sqlite-3.7.17-8.el7_7.1.x86_64.rpm | 394 kB 00:00 (166/177): systemd-219-78.el7_9.5.x86_64.rpm | 5.1 MB 00:00 (167/177): tar-1.26-35.el7.x86_64.rpm | 846 kB 00:00 (168/177): tzdata-2022a-1.el7.noarch.rpm | 501 kB 00:00 (169/177): ustr-1.0.4-16.el7.x86_64.rpm | 92 kB 00:00 (170/177): unzip-6.0-24.el7_9.x86_64.rpm | 172 kB 00:00 (171/177): which-2.20-7.el7.x86_64.rpm | 41 kB 00:00 (172/177): util-linux-2.23.2-65.el7_9.1.x86_64.rpm | 2.0 MB 00:00 (173/177): systemd-libs-219-78.el7_9.5.x86_64.rpm | 419 kB 00:00 (174/177): xz-5.2.2-2.el7_9.x86_64.rpm | 229 kB 00:00 (175/177): zip-3.0-11.el7.x86_64.rpm | 260 kB 00:00 (176/177): xz-libs-5.2.2-2.el7_9.x86_64.rpm | 103 kB 00:00 (177/177): zlib-1.2.7-20.el7_9.x86_64.rpm | 90 kB 00:00 -------------------------------------------------------------------------------- Total 19 MB/s | 131 MB 00:06 Retrieving key from file:///usr/share/distribution-gpg-keys/centos/RPM-GPG-KEY-CentOS-7 Importing GPG key 0xF4A80EB5: Userid : "CentOS-7 Key (CentOS 7 Official Signing Key) " Fingerprint: 6341 ab27 53d7 8a78 a7c2 7bb1 24c6 a8a7 f4a8 0eb5 From : /usr/share/distribution-gpg-keys/centos/RPM-GPG-KEY-CentOS-7 Retrieving key from file:///usr/share/distribution-gpg-keys/epel/RPM-GPG-KEY-EPEL-7 Importing GPG key 0x352C64E5: Userid : "Fedora EPEL (7) " Fingerprint: 91e9 7d7c 4a5e 96f1 7f3e 888f 6a2f aea2 352c 64e5 From : /usr/share/distribution-gpg-keys/epel/RPM-GPG-KEY-EPEL-7 Running transaction check Running transaction test Transaction test succeeded Running transaction Installing : libgcc-4.8.5-44.el7.x86_64 1/177 Installing : centos-release-7-9.2009.1.el7.centos.x86_64 2/177 Installing : setup-2.8.71-11.el7.noarch 3/177 Installing : filesystem-3.2-25.el7.x86_64 4/177 Installing : python-srpm-macros-3-34.el7.noarch 5/177 Installing : python-rpm-macros-3-34.el7.noarch 6/177 Installing : basesystem-10.0-7.el7.centos.noarch 7/177 Installing : ncurses-base-5.9-14.20130511.el7_4.noarch 8/177 Installing : perl-srpm-macros-1-8.el7.noarch 9/177 Installing : kernel-headers-3.10.0-1160.71.1.el7.x86_64 10/177 Installing : python2-rpm-macros-3-34.el7.noarch 11/177 Installing : tzdata-2022a-1.el7.noarch 12/177 Installing : nss-softokn-freebl-3.67.0-3.el7_9.x86_64 13/177 Installing : glibc-common-2.17-326.el7_9.x86_64 14/177 Installing : glibc-2.17-326.el7_9.x86_64 15/177 Installing : nspr-4.32.0-1.el7_9.x86_64 16/177 Installing : nss-util-3.67.0-1.el7_9.x86_64 17/177 Installing : libstdc++-4.8.5-44.el7.x86_64 18/177 Installing : ncurses-libs-5.9-14.20130511.el7_4.x86_64 19/177 Installing : bash-4.2.46-35.el7_9.x86_64 20/177 Installing : libsepol-2.5-10.el7.x86_64 21/177 Installing : pcre-8.32-17.el7.x86_64 22/177 Installing : libselinux-2.5-15.el7.x86_64 23/177 Installing : zlib-1.2.7-20.el7_9.x86_64 24/177 Installing : info-5.1-5.el7.x86_64 25/177 Installing : bzip2-libs-1.0.6-13.el7.x86_64 26/177 Installing : xz-libs-5.2.2-2.el7_9.x86_64 27/177 Installing : elfutils-libelf-0.176-5.el7.x86_64 28/177 Installing : libdb-5.3.21-25.el7.x86_64 29/177 Installing : sed-4.2.2-7.el7.x86_64 30/177 Installing : 1:gmp-6.0.0-15.el7.x86_64 31/177 Installing : popt-1.13-16.el7.x86_64 32/177 Installing : libattr-2.4.46-13.el7.x86_64 33/177 Installing : libacl-2.2.51-15.el7.x86_64 34/177 Installing : libcap-2.22-11.el7.x86_64 35/177 Installing : readline-6.2-11.el7.x86_64 36/177 Installing : libgpg-error-1.12-3.el7.x86_64 37/177 Installing : libgcrypt-1.5.3-14.el7.x86_64 38/177 Installing : lua-5.1.4-15.el7.x86_64 39/177 Installing : chkconfig-1.7.6-1.el7.x86_64 40/177 Installing : mpfr-3.1.1-4.el7.x86_64 41/177 Installing : grep-2.20-3.el7.x86_64 42/177 Installing : libffi-3.0.13-19.el7.x86_64 43/177 Installing : libuuid-2.23.2-65.el7_9.1.x86_64 44/177 Installing : libcom_err-1.42.9-19.el7.x86_64 45/177 Installing : libmpc-1.0.1-3.el7.x86_64 46/177 Installing : xz-5.2.2-2.el7_9.x86_64 47/177 Installing : gawk-4.0.2-4.el7_3.1.x86_64 48/177 Installing : diffutils-3.3-5.el7.x86_64 49/177 Installing : 1:findutils-4.5.11-6.el7.x86_64 50/177 Installing : cpio-2.11-28.el7.x86_64 51/177 Installing : file-libs-5.11-37.el7.x86_64 52/177 Installing : expat-2.1.0-14.el7_9.x86_64 53/177 Installing : libcap-ng-0.7.5-4.el7.x86_64 54/177 Installing : audit-libs-2.8.5-4.el7.x86_64 55/177 Installing : p11-kit-0.23.5-3.el7.x86_64 56/177 Installing : sqlite-3.7.17-8.el7_7.1.x86_64 57/177 Installing : nss-softokn-3.67.0-3.el7_9.x86_64 58/177 Installing : 2:tar-1.26-35.el7.x86_64 59/177 Installing : lz4-1.8.3-1.el7.x86_64 60/177 Installing : gdbm-1.10-8.el7.x86_64 61/177 Installing : file-5.11-37.el7.x86_64 62/177 Installing : cpp-4.8.5-44.el7.x86_64 63/177 Installing : pinentry-0.8.1-17.el7.x86_64 64/177 Installing : libassuan-2.1.0-3.el7.x86_64 65/177 Installing : acl-2.2.51-15.el7.x86_64 66/177 Installing : patch-2.7.1-12.el7_7.x86_64 67/177 Installing : groff-base-1.22.2-8.el7.x86_64 68/177 Installing : 1:perl-parent-0.225-244.el7.noarch 69/177 Installing : perl-HTTP-Tiny-0.033-3.el7.noarch 70/177 Installing : perl-podlators-2.5.1-3.el7.noarch 71/177 Installing : perl-Pod-Perldoc-3.20-4.el7.noarch 72/177 Installing : 1:perl-Pod-Escapes-1.04-299.el7_9.noarch 73/177 Installing : perl-Text-ParseWords-3.29-4.el7.noarch 74/177 Installing : perl-Encode-2.51-7.el7.x86_64 75/177 Installing : perl-Pod-Usage-1.63-3.el7.noarch 76/177 Installing : 4:perl-Time-HiRes-1.9725-3.el7.x86_64 77/177 Installing : perl-threads-1.87-4.el7.x86_64 78/177 Installing : perl-Storable-2.45-3.el7.x86_64 79/177 Installing : perl-Carp-1.26-244.el7.noarch 80/177 Installing : perl-Filter-1.49-3.el7.x86_64 81/177 Installing : perl-Exporter-5.68-3.el7.noarch 82/177 Installing : perl-constant-1.27-2.el7.noarch 83/177 Installing : perl-Socket-2.010-5.el7.x86_64 84/177 Installing : 4:perl-macros-5.16.3-299.el7_9.x86_64 85/177 Installing : perl-Time-Local-1.2300-2.el7.noarch 86/177 Installing : perl-File-Path-2.09-2.el7.noarch 87/177 Installing : perl-File-Temp-0.23.01-3.el7.noarch 88/177 Installing : perl-PathTools-3.40-5.el7.x86_64 89/177 Installing : perl-threads-shared-1.43-6.el7.x86_64 90/177 Installing : perl-Scalar-List-Utils-1.27-248.el7.x86_64 91/177 Installing : 4:perl-libs-5.16.3-299.el7_9.x86_64 92/177 Installing : 1:perl-Pod-Simple-3.28-4.el7.noarch 93/177 Installing : perl-Getopt-Long-2.40-3.el7.noarch 94/177 Installing : 4:perl-5.16.3-299.el7_9.x86_64 95/177 Installing : perl-Thread-Queue-3.02-2.el7.noarch 96/177 Installing : libdb-utils-5.3.21-25.el7.x86_64 97/177 Installing : dwz-0.11-3.el7.x86_64 98/177 Installing : kmod-libs-20-28.el7.x86_64 99/177 Installing : libxml2-2.9.1-6.el7_9.6.x86_64 100/177 Installing : bzip2-1.0.6-13.el7.x86_64 101/177 Installing : unzip-6.0-24.el7_9.x86_64 102/177 Installing : zip-3.0-11.el7.x86_64 103/177 Installing : libidn-1.28-4.el7.x86_64 104/177 Installing : libgomp-4.8.5-44.el7.x86_64 105/177 Installing : glibc-headers-2.17-326.el7_9.x86_64 106/177 Installing : glibc-devel-2.17-326.el7_9.x86_64 107/177 Installing : ncurses-5.9-14.20130511.el7_4.x86_64 108/177 Installing : libstdc++-devel-4.8.5-44.el7.x86_64 109/177 Installing : pth-2.0.7-23.el7.x86_64 110/177 Installing : libsmartcols-2.23.2-65.el7_9.1.x86_64 111/177 Installing : ustr-1.0.4-16.el7.x86_64 112/177 Installing : libsemanage-2.5-14.el7.x86_64 113/177 Installing : libverto-0.2.5-4.el7.x86_64 114/177 Installing : libtasn1-4.10-1.el7.x86_64 115/177 Installing : p11-kit-trust-0.23.5-3.el7.x86_64 116/177 Installing : ca-certificates-2021.2.50-72.el7_9.noarch 117/177 Installing : 1:hardlink-1.0-19.el7.x86_64 118/177 Installing : qrencode-libs-3.4.1-3.el7.x86_64 119/177 Installing : keyutils-libs-1.5.8-3.el7.x86_64 120/177 Installing : 1:openssl-libs-1.0.2k-25.el7_9.x86_64 121/177 Installing : coreutils-8.22-24.el7_9.2.x86_64 122/177 Installing : krb5-libs-1.15.1-54.el7_9.x86_64 123/177 Installing : libblkid-2.23.2-65.el7_9.1.x86_64 124/177 Installing : gzip-1.5-11.el7_9.x86_64 125/177 Installing : cracklib-2.9.0-11.el7.x86_64 126/177 Installing : libmount-2.23.2-65.el7_9.1.x86_64 127/177 Installing : glib2-2.56.1-9.el7_9.x86_64 128/177 Installing : shared-mime-info-1.8-5.el7.x86_64 129/177 Installing : binutils-2.27-44.base.el7_9.1.x86_64 130/177 Installing : 2:shadow-utils-4.6-5.el7.x86_64 131/177 Installing : 1:pkgconfig-0.27.1-4.el7.x86_64 132/177 Installing : cracklib-dicts-2.9.0-11.el7.x86_64 133/177 Installing : pam-1.1.8-23.el7.x86_64 134/177 Installing : libpwquality-1.2.3-5.el7.x86_64 135/177 Installing : libutempter-1.1.6-4.el7.x86_64 136/177 Installing : gcc-4.8.5-44.el7.x86_64 137/177 Installing : cyrus-sasl-lib-2.1.26-24.el7_9.x86_64 138/177 Installing : python-libs-2.7.5-92.el7_9.x86_64 139/177 Installing : gdb-7.6.1-120.el7.x86_64 140/177 Installing : nss-pem-1.0.3-7.el7.x86_64 141/177 Installing : nss-3.67.0-4.el7_9.x86_64 142/177 Installing : nss-sysinit-3.67.0-4.el7_9.x86_64 143/177 Installing : nss-tools-3.67.0-4.el7_9.x86_64 144/177 Installing : libssh2-1.8.0-4.el7.x86_64 145/177 Installing : libcurl-7.29.0-59.el7_9.1.x86_64 146/177 Installing : curl-7.29.0-59.el7_9.1.x86_64 147/177 Installing : rpm-libs-4.11.3-48.el7_9.x86_64 148/177 Installing : rpm-4.11.3-48.el7_9.x86_64 149/177 Installing : openldap-2.4.44-25.el7_9.x86_64 150/177 Installing : libuser-0.60-9.el7.x86_64 151/177 Installing : gnupg2-2.0.22-5.el7_5.x86_64 152/177 Installing : rpm-build-libs-4.11.3-48.el7_9.x86_64 153/177 Installing : lua-srpm-macros-1-3.el7.noarch 154/177 Installing : redhat-rpm-config-9.1.0-88.el7.centos.noarch 155/177 Installing : json-c-0.11-4.el7_0.x86_64 156/177 Installing : util-linux-2.23.2-65.el7_9.1.x86_64 157/177 Installing : procps-ng-3.3.10-28.el7.x86_64 158/177 Installing : 7:device-mapper-1.02.170-6.el7_9.5.x86_64 159/177 Installing : kpartx-0.4.9-135.el7_9.x86_64 160/177 Installing : 7:device-mapper-libs-1.02.170-6.el7_9.5.x86_64 161/177 Installing : cryptsetup-libs-2.0.3-6.el7.x86_64 162/177 Installing : dracut-033-572.el7.x86_64 163/177 Installing : kmod-20-28.el7.x86_64 164/177 Installing : elfutils-libs-0.176-5.el7.x86_64 165/177 Installing : systemd-libs-219-78.el7_9.5.x86_64 166/177 Installing : 1:dbus-libs-1.10.24-15.el7.x86_64 167/177 Installing : systemd-219-78.el7_9.5.x86_64 168/177 Failed to get D-Bus connection: Operation not permitted Installing : 1:dbus-1.10.24-15.el7.x86_64 169/177 Installing : elfutils-default-yama-scope-0.176-5.el7.noarch 170/177 Installing : elfutils-0.176-5.el7.x86_64 171/177 Installing : rpm-build-4.11.3-48.el7_9.x86_64 172/177 Installing : epel-rpm-macros-7-35.noarch 173/177 Installing : gcc-c++-4.8.5-44.el7.x86_64 174/177 Installing : which-2.20-7.el7.x86_64 175/177 Installing : 1:make-3.82-24.el7.x86_64 176/177 Installing : epel-release-7-14.noarch 177/177 Verifying : perl-HTTP-Tiny-0.033-3.el7.noarch 1/177 Verifying : gcc-c++-4.8.5-44.el7.x86_64 2/177 Verifying : acl-2.2.51-15.el7.x86_64 3/177 Verifying : libblkid-2.23.2-65.el7_9.1.x86_64 4/177 Verifying : 1:pkgconfig-0.27.1-4.el7.x86_64 5/177 Verifying : nss-tools-3.67.0-4.el7_9.x86_64 6/177 Verifying : libacl-2.2.51-15.el7.x86_64 7/177 Verifying : libdb-utils-5.3.21-25.el7.x86_64 8/177 Verifying : libcap-2.22-11.el7.x86_64 9/177 Verifying : pcre-8.32-17.el7.x86_64 10/177 Verifying : pth-2.0.7-23.el7.x86_64 11/177 Verifying : lua-srpm-macros-1-3.el7.noarch 12/177 Verifying : readline-6.2-11.el7.x86_64 13/177 Verifying : sqlite-3.7.17-8.el7_7.1.x86_64 14/177 Verifying : which-2.20-7.el7.x86_64 15/177 Verifying : groff-base-1.22.2-8.el7.x86_64 16/177 Verifying : centos-release-7-9.2009.1.el7.centos.x86_64 17/177 Verifying : libsmartcols-2.23.2-65.el7_9.1.x86_64 18/177 Verifying : nss-pem-1.0.3-7.el7.x86_64 19/177 Verifying : shared-mime-info-1.8-5.el7.x86_64 20/177 Verifying : 1:dbus-1.10.24-15.el7.x86_64 21/177 Verifying : libselinux-2.5-15.el7.x86_64 22/177 Verifying : util-linux-2.23.2-65.el7_9.1.x86_64 23/177 Verifying : libsemanage-2.5-14.el7.x86_64 24/177 Verifying : nss-3.67.0-4.el7_9.x86_64 25/177 Verifying : kmod-libs-20-28.el7.x86_64 26/177 Verifying : libcurl-7.29.0-59.el7_9.1.x86_64 27/177 Verifying : tzdata-2022a-1.el7.noarch 28/177 Verifying : procps-ng-3.3.10-28.el7.x86_64 29/177 Verifying : openldap-2.4.44-25.el7_9.x86_64 30/177 Verifying : python2-rpm-macros-3-34.el7.noarch 31/177 Verifying : cracklib-dicts-2.9.0-11.el7.x86_64 32/177 Verifying : cpp-4.8.5-44.el7.x86_64 33/177 Verifying : libstdc++-4.8.5-44.el7.x86_64 34/177 Verifying : nss-util-3.67.0-1.el7_9.x86_64 35/177 Verifying : 7:device-mapper-1.02.170-6.el7_9.5.x86_64 36/177 Verifying : perl-Text-ParseWords-3.29-4.el7.noarch 37/177 Verifying : python-srpm-macros-3-34.el7.noarch 38/177 Verifying : epel-rpm-macros-7-35.noarch 39/177 Verifying : perl-File-Path-2.09-2.el7.noarch 40/177 Verifying : ustr-1.0.4-16.el7.x86_64 41/177 Verifying : lua-5.1.4-15.el7.x86_64 42/177 Verifying : libgcc-4.8.5-44.el7.x86_64 43/177 Verifying : libutempter-1.1.6-4.el7.x86_64 44/177 Verifying : file-5.11-37.el7.x86_64 45/177 Verifying : libidn-1.28-4.el7.x86_64 46/177 Verifying : libxml2-2.9.1-6.el7_9.6.x86_64 47/177 Verifying : glibc-2.17-326.el7_9.x86_64 48/177 Verifying : 4:perl-Time-HiRes-1.9725-3.el7.x86_64 49/177 Verifying : ncurses-libs-5.9-14.20130511.el7_4.x86_64 50/177 Verifying : chkconfig-1.7.6-1.el7.x86_64 51/177 Verifying : pam-1.1.8-23.el7.x86_64 52/177 Verifying : kpartx-0.4.9-135.el7_9.x86_64 53/177 Verifying : elfutils-default-yama-scope-0.176-5.el7.noarch 54/177 Verifying : libmount-2.23.2-65.el7_9.1.x86_64 55/177 Verifying : dracut-033-572.el7.x86_64 56/177 Verifying : 1:dbus-libs-1.10.24-15.el7.x86_64 57/177 Verifying : libassuan-2.1.0-3.el7.x86_64 58/177 Verifying : nss-softokn-freebl-3.67.0-3.el7_9.x86_64 59/177 Verifying : bzip2-1.0.6-13.el7.x86_64 60/177 Verifying : 7:device-mapper-libs-1.02.170-6.el7_9.5.x86_64 61/177 Verifying : basesystem-10.0-7.el7.centos.noarch 62/177 Verifying : libverto-0.2.5-4.el7.x86_64 63/177 Verifying : gdb-7.6.1-120.el7.x86_64 64/177 Verifying : 1:make-3.82-24.el7.x86_64 65/177 Verifying : info-5.1-5.el7.x86_64 66/177 Verifying : binutils-2.27-44.base.el7_9.1.x86_64 67/177 Verifying : bzip2-libs-1.0.6-13.el7.x86_64 68/177 Verifying : 1:perl-parent-0.225-244.el7.noarch 69/177 Verifying : libsepol-2.5-10.el7.x86_64 70/177 Verifying : zlib-1.2.7-20.el7_9.x86_64 71/177 Verifying : libmpc-1.0.1-3.el7.x86_64 72/177 Verifying : perl-Pod-Usage-1.63-3.el7.noarch 73/177 Verifying : curl-7.29.0-59.el7_9.1.x86_64 74/177 Verifying : libssh2-1.8.0-4.el7.x86_64 75/177 Verifying : bash-4.2.46-35.el7_9.x86_64 76/177 Verifying : libuser-0.60-9.el7.x86_64 77/177 Verifying : libtasn1-4.10-1.el7.x86_64 78/177 Verifying : perl-threads-1.87-4.el7.x86_64 79/177 Verifying : glibc-devel-2.17-326.el7_9.x86_64 80/177 Verifying : 1:hardlink-1.0-19.el7.x86_64 81/177 Verifying : cracklib-2.9.0-11.el7.x86_64 82/177 Verifying : libgpg-error-1.12-3.el7.x86_64 83/177 Verifying : perl-Getopt-Long-2.40-3.el7.noarch 84/177 Verifying : nss-softokn-3.67.0-3.el7_9.x86_64 85/177 Verifying : cyrus-sasl-lib-2.1.26-24.el7_9.x86_64 86/177 Verifying : libgomp-4.8.5-44.el7.x86_64 87/177 Verifying : gnupg2-2.0.22-5.el7_5.x86_64 88/177 Verifying : epel-release-7-14.noarch 89/177 Verifying : popt-1.13-16.el7.x86_64 90/177 Verifying : libffi-3.0.13-19.el7.x86_64 91/177 Verifying : p11-kit-0.23.5-3.el7.x86_64 92/177 Verifying : 2:shadow-utils-4.6-5.el7.x86_64 93/177 Verifying : perl-Storable-2.45-3.el7.x86_64 94/177 Verifying : kernel-headers-3.10.0-1160.71.1.el7.x86_64 95/177 Verifying : unzip-6.0-24.el7_9.x86_64 96/177 Verifying : cryptsetup-libs-2.0.3-6.el7.x86_64 97/177 Verifying : perl-File-Temp-0.23.01-3.el7.noarch 98/177 Verifying : lz4-1.8.3-1.el7.x86_64 99/177 Verifying : libattr-2.4.46-13.el7.x86_64 100/177 Verifying : gawk-4.0.2-4.el7_3.1.x86_64 101/177 Verifying : ca-certificates-2021.2.50-72.el7_9.noarch 102/177 Verifying : audit-libs-2.8.5-4.el7.x86_64 103/177 Verifying : perl-srpm-macros-1-8.el7.noarch 104/177 Verifying : qrencode-libs-3.4.1-3.el7.x86_64 105/177 Verifying : python-rpm-macros-3-34.el7.noarch 106/177 Verifying : setup-2.8.71-11.el7.noarch 107/177 Verifying : 1:perl-Pod-Escapes-1.04-299.el7_9.noarch 108/177 Verifying : grep-2.20-3.el7.x86_64 109/177 Verifying : xz-libs-5.2.2-2.el7_9.x86_64 110/177 Verifying : patch-2.7.1-12.el7_7.x86_64 111/177 Verifying : perl-Encode-2.51-7.el7.x86_64 112/177 Verifying : filesystem-3.2-25.el7.x86_64 113/177 Verifying : perl-Carp-1.26-244.el7.noarch 114/177 Verifying : libdb-5.3.21-25.el7.x86_64 115/177 Verifying : rpm-build-4.11.3-48.el7_9.x86_64 116/177 Verifying : file-libs-5.11-37.el7.x86_64 117/177 Verifying : gdbm-1.10-8.el7.x86_64 118/177 Verifying : gcc-4.8.5-44.el7.x86_64 119/177 Verifying : coreutils-8.22-24.el7_9.2.x86_64 120/177 Verifying : elfutils-libelf-0.176-5.el7.x86_64 121/177 Verifying : 2:tar-1.26-35.el7.x86_64 122/177 Verifying : rpm-libs-4.11.3-48.el7_9.x86_64 123/177 Verifying : diffutils-3.3-5.el7.x86_64 124/177 Verifying : 1:findutils-4.5.11-6.el7.x86_64 125/177 Verifying : perl-Pod-Perldoc-3.20-4.el7.noarch 126/177 Verifying : libuuid-2.23.2-65.el7_9.1.x86_64 127/177 Verifying : 4:perl-5.16.3-299.el7_9.x86_64 128/177 Verifying : mpfr-3.1.1-4.el7.x86_64 129/177 Verifying : perl-Filter-1.49-3.el7.x86_64 130/177 Verifying : dwz-0.11-3.el7.x86_64 131/177 Verifying : ncurses-5.9-14.20130511.el7_4.x86_64 132/177 Verifying : ncurses-base-5.9-14.20130511.el7_4.noarch 133/177 Verifying : krb5-libs-1.15.1-54.el7_9.x86_64 134/177 Verifying : expat-2.1.0-14.el7_9.x86_64 135/177 Verifying : python-libs-2.7.5-92.el7_9.x86_64 136/177 Verifying : rpm-4.11.3-48.el7_9.x86_64 137/177 Verifying : perl-Exporter-5.68-3.el7.noarch 138/177 Verifying : perl-constant-1.27-2.el7.noarch 139/177 Verifying : perl-PathTools-3.40-5.el7.x86_64 140/177 Verifying : keyutils-libs-1.5.8-3.el7.x86_64 141/177 Verifying : pinentry-0.8.1-17.el7.x86_64 142/177 Verifying : perl-Socket-2.010-5.el7.x86_64 143/177 Verifying : 4:perl-macros-5.16.3-299.el7_9.x86_64 144/177 Verifying : glib2-2.56.1-9.el7_9.x86_64 145/177 Verifying : nss-sysinit-3.67.0-4.el7_9.x86_64 146/177 Verifying : libcom_err-1.42.9-19.el7.x86_64 147/177 Verifying : perl-Thread-Queue-3.02-2.el7.noarch 148/177 Verifying : glibc-headers-2.17-326.el7_9.x86_64 149/177 Verifying : 1:perl-Pod-Simple-3.28-4.el7.noarch 150/177 Verifying : perl-Time-Local-1.2300-2.el7.noarch 151/177 Verifying : perl-threads-shared-1.43-6.el7.x86_64 152/177 Verifying : libstdc++-devel-4.8.5-44.el7.x86_64 153/177 Verifying : json-c-0.11-4.el7_0.x86_64 154/177 Verifying : kmod-20-28.el7.x86_64 155/177 Verifying : 1:openssl-libs-1.0.2k-25.el7_9.x86_64 156/177 Verifying : libcap-ng-0.7.5-4.el7.x86_64 157/177 Verifying : 1:gmp-6.0.0-15.el7.x86_64 158/177 Verifying : perl-Scalar-List-Utils-1.27-248.el7.x86_64 159/177 Verifying : p11-kit-trust-0.23.5-3.el7.x86_64 160/177 Verifying : sed-4.2.2-7.el7.x86_64 161/177 Verifying : libgcrypt-1.5.3-14.el7.x86_64 162/177 Verifying : cpio-2.11-28.el7.x86_64 163/177 Verifying : gzip-1.5-11.el7_9.x86_64 164/177 Verifying : glibc-common-2.17-326.el7_9.x86_64 165/177 Verifying : perl-podlators-2.5.1-3.el7.noarch 166/177 Verifying : elfutils-0.176-5.el7.x86_64 167/177 Verifying : zip-3.0-11.el7.x86_64 168/177 Verifying : nspr-4.32.0-1.el7_9.x86_64 169/177 Verifying : systemd-libs-219-78.el7_9.5.x86_64 170/177 Verifying : libpwquality-1.2.3-5.el7.x86_64 171/177 Verifying : xz-5.2.2-2.el7_9.x86_64 172/177 Verifying : 4:perl-libs-5.16.3-299.el7_9.x86_64 173/177 Verifying : systemd-219-78.el7_9.5.x86_64 174/177 Verifying : rpm-build-libs-4.11.3-48.el7_9.x86_64 175/177 Verifying : elfutils-libs-0.176-5.el7.x86_64 176/177 Verifying : redhat-rpm-config-9.1.0-88.el7.centos.noarch 177/177 Installed: bash.x86_64 0:4.2.46-35.el7_9 bzip2.x86_64 0:1.0.6-13.el7 coreutils.x86_64 0:8.22-24.el7_9.2 cpio.x86_64 0:2.11-28.el7 diffutils.x86_64 0:3.3-5.el7 epel-release.noarch 0:7-14 epel-rpm-macros.noarch 0:7-35 findutils.x86_64 1:4.5.11-6.el7 gawk.x86_64 0:4.0.2-4.el7_3.1 gcc.x86_64 0:4.8.5-44.el7 gcc-c++.x86_64 0:4.8.5-44.el7 grep.x86_64 0:2.20-3.el7 gzip.x86_64 0:1.5-11.el7_9 info.x86_64 0:5.1-5.el7 make.x86_64 1:3.82-24.el7 patch.x86_64 0:2.7.1-12.el7_7 redhat-rpm-config.noarch 0:9.1.0-88.el7.centos rpm-build.x86_64 0:4.11.3-48.el7_9 sed.x86_64 0:4.2.2-7.el7 shadow-utils.x86_64 2:4.6-5.el7 tar.x86_64 2:1.26-35.el7 unzip.x86_64 0:6.0-24.el7_9 util-linux.x86_64 0:2.23.2-65.el7_9.1 which.x86_64 0:2.20-7.el7 xz.x86_64 0:5.2.2-2.el7_9 Dependency Installed: acl.x86_64 0:2.2.51-15.el7 audit-libs.x86_64 0:2.8.5-4.el7 basesystem.noarch 0:10.0-7.el7.centos binutils.x86_64 0:2.27-44.base.el7_9.1 bzip2-libs.x86_64 0:1.0.6-13.el7 ca-certificates.noarch 0:2021.2.50-72.el7_9 centos-release.x86_64 0:7-9.2009.1.el7.centos chkconfig.x86_64 0:1.7.6-1.el7 cpp.x86_64 0:4.8.5-44.el7 cracklib.x86_64 0:2.9.0-11.el7 cracklib-dicts.x86_64 0:2.9.0-11.el7 cryptsetup-libs.x86_64 0:2.0.3-6.el7 curl.x86_64 0:7.29.0-59.el7_9.1 cyrus-sasl-lib.x86_64 0:2.1.26-24.el7_9 dbus.x86_64 1:1.10.24-15.el7 dbus-libs.x86_64 1:1.10.24-15.el7 device-mapper.x86_64 7:1.02.170-6.el7_9.5 device-mapper-libs.x86_64 7:1.02.170-6.el7_9.5 dracut.x86_64 0:033-572.el7 dwz.x86_64 0:0.11-3.el7 elfutils.x86_64 0:0.176-5.el7 elfutils-default-yama-scope.noarch 0:0.176-5.el7 elfutils-libelf.x86_64 0:0.176-5.el7 elfutils-libs.x86_64 0:0.176-5.el7 expat.x86_64 0:2.1.0-14.el7_9 file.x86_64 0:5.11-37.el7 file-libs.x86_64 0:5.11-37.el7 filesystem.x86_64 0:3.2-25.el7 gdb.x86_64 0:7.6.1-120.el7 gdbm.x86_64 0:1.10-8.el7 glib2.x86_64 0:2.56.1-9.el7_9 glibc.x86_64 0:2.17-326.el7_9 glibc-common.x86_64 0:2.17-326.el7_9 glibc-devel.x86_64 0:2.17-326.el7_9 glibc-headers.x86_64 0:2.17-326.el7_9 gmp.x86_64 1:6.0.0-15.el7 gnupg2.x86_64 0:2.0.22-5.el7_5 groff-base.x86_64 0:1.22.2-8.el7 hardlink.x86_64 1:1.0-19.el7 json-c.x86_64 0:0.11-4.el7_0 kernel-headers.x86_64 0:3.10.0-1160.71.1.el7 keyutils-libs.x86_64 0:1.5.8-3.el7 kmod.x86_64 0:20-28.el7 kmod-libs.x86_64 0:20-28.el7 kpartx.x86_64 0:0.4.9-135.el7_9 krb5-libs.x86_64 0:1.15.1-54.el7_9 libacl.x86_64 0:2.2.51-15.el7 libassuan.x86_64 0:2.1.0-3.el7 libattr.x86_64 0:2.4.46-13.el7 libblkid.x86_64 0:2.23.2-65.el7_9.1 libcap.x86_64 0:2.22-11.el7 libcap-ng.x86_64 0:0.7.5-4.el7 libcom_err.x86_64 0:1.42.9-19.el7 libcurl.x86_64 0:7.29.0-59.el7_9.1 libdb.x86_64 0:5.3.21-25.el7 libdb-utils.x86_64 0:5.3.21-25.el7 libffi.x86_64 0:3.0.13-19.el7 libgcc.x86_64 0:4.8.5-44.el7 libgcrypt.x86_64 0:1.5.3-14.el7 libgomp.x86_64 0:4.8.5-44.el7 libgpg-error.x86_64 0:1.12-3.el7 libidn.x86_64 0:1.28-4.el7 libmount.x86_64 0:2.23.2-65.el7_9.1 libmpc.x86_64 0:1.0.1-3.el7 libpwquality.x86_64 0:1.2.3-5.el7 libselinux.x86_64 0:2.5-15.el7 libsemanage.x86_64 0:2.5-14.el7 libsepol.x86_64 0:2.5-10.el7 libsmartcols.x86_64 0:2.23.2-65.el7_9.1 libssh2.x86_64 0:1.8.0-4.el7 libstdc++.x86_64 0:4.8.5-44.el7 libstdc++-devel.x86_64 0:4.8.5-44.el7 libtasn1.x86_64 0:4.10-1.el7 libuser.x86_64 0:0.60-9.el7 libutempter.x86_64 0:1.1.6-4.el7 libuuid.x86_64 0:2.23.2-65.el7_9.1 libverto.x86_64 0:0.2.5-4.el7 libxml2.x86_64 0:2.9.1-6.el7_9.6 lua.x86_64 0:5.1.4-15.el7 lua-srpm-macros.noarch 0:1-3.el7 lz4.x86_64 0:1.8.3-1.el7 mpfr.x86_64 0:3.1.1-4.el7 ncurses.x86_64 0:5.9-14.20130511.el7_4 ncurses-base.noarch 0:5.9-14.20130511.el7_4 ncurses-libs.x86_64 0:5.9-14.20130511.el7_4 nspr.x86_64 0:4.32.0-1.el7_9 nss.x86_64 0:3.67.0-4.el7_9 nss-pem.x86_64 0:1.0.3-7.el7 nss-softokn.x86_64 0:3.67.0-3.el7_9 nss-softokn-freebl.x86_64 0:3.67.0-3.el7_9 nss-sysinit.x86_64 0:3.67.0-4.el7_9 nss-tools.x86_64 0:3.67.0-4.el7_9 nss-util.x86_64 0:3.67.0-1.el7_9 openldap.x86_64 0:2.4.44-25.el7_9 openssl-libs.x86_64 1:1.0.2k-25.el7_9 p11-kit.x86_64 0:0.23.5-3.el7 p11-kit-trust.x86_64 0:0.23.5-3.el7 pam.x86_64 0:1.1.8-23.el7 pcre.x86_64 0:8.32-17.el7 perl.x86_64 4:5.16.3-299.el7_9 perl-Carp.noarch 0:1.26-244.el7 perl-Encode.x86_64 0:2.51-7.el7 perl-Exporter.noarch 0:5.68-3.el7 perl-File-Path.noarch 0:2.09-2.el7 perl-File-Temp.noarch 0:0.23.01-3.el7 perl-Filter.x86_64 0:1.49-3.el7 perl-Getopt-Long.noarch 0:2.40-3.el7 perl-HTTP-Tiny.noarch 0:0.033-3.el7 perl-PathTools.x86_64 0:3.40-5.el7 perl-Pod-Escapes.noarch 1:1.04-299.el7_9 perl-Pod-Perldoc.noarch 0:3.20-4.el7 perl-Pod-Simple.noarch 1:3.28-4.el7 perl-Pod-Usage.noarch 0:1.63-3.el7 perl-Scalar-List-Utils.x86_64 0:1.27-248.el7 perl-Socket.x86_64 0:2.010-5.el7 perl-Storable.x86_64 0:2.45-3.el7 perl-Text-ParseWords.noarch 0:3.29-4.el7 perl-Thread-Queue.noarch 0:3.02-2.el7 perl-Time-HiRes.x86_64 4:1.9725-3.el7 perl-Time-Local.noarch 0:1.2300-2.el7 perl-constant.noarch 0:1.27-2.el7 perl-libs.x86_64 4:5.16.3-299.el7_9 perl-macros.x86_64 4:5.16.3-299.el7_9 perl-parent.noarch 1:0.225-244.el7 perl-podlators.noarch 0:2.5.1-3.el7 perl-srpm-macros.noarch 0:1-8.el7 perl-threads.x86_64 0:1.87-4.el7 perl-threads-shared.x86_64 0:1.43-6.el7 pinentry.x86_64 0:0.8.1-17.el7 pkgconfig.x86_64 1:0.27.1-4.el7 popt.x86_64 0:1.13-16.el7 procps-ng.x86_64 0:3.3.10-28.el7 pth.x86_64 0:2.0.7-23.el7 python-libs.x86_64 0:2.7.5-92.el7_9 python-rpm-macros.noarch 0:3-34.el7 python-srpm-macros.noarch 0:3-34.el7 python2-rpm-macros.noarch 0:3-34.el7 qrencode-libs.x86_64 0:3.4.1-3.el7 readline.x86_64 0:6.2-11.el7 rpm.x86_64 0:4.11.3-48.el7_9 rpm-build-libs.x86_64 0:4.11.3-48.el7_9 rpm-libs.x86_64 0:4.11.3-48.el7_9 setup.noarch 0:2.8.71-11.el7 shared-mime-info.x86_64 0:1.8-5.el7 sqlite.x86_64 0:3.7.17-8.el7_7.1 systemd.x86_64 0:219-78.el7_9.5 systemd-libs.x86_64 0:219-78.el7_9.5 tzdata.noarch 0:2022a-1.el7 ustr.x86_64 0:1.0.4-16.el7 xz-libs.x86_64 0:5.2.2-2.el7_9 zip.x86_64 0:3.0-11.el7 zlib.x86_64 0:1.2.7-20.el7_9 Complete! Finish: yum install Start: creating root cache Finish: creating root cache Finish: chroot init INFO: Installed packages: INFO: audit-libs-2.8.5-4.el7.x86_64 gmp-6.0.0-15.el7.x86_64 libsepol-2.5-10.el7.x86_64 procps-ng-3.3.10-28.el7.x86_64 gdb-7.6.1-120.el7.x86_64 perl-Pod-Perldoc-3.20-4.el7.noarch libstdc++-devel-4.8.5-44.el7.x86_64 rpm-build-libs-4.11.3-48.el7_9.x86_64 qrencode-libs-3.4.1-3.el7.x86_64 perl-Socket-2.010-5.el7.x86_64 bzip2-1.0.6-13.el7.x86_64 perl-5.16.3-299.el7_9.x86_64 libffi-3.0.13-19.el7.x86_64 libgpg-error-1.12-3.el7.x86_64 perl-threads-1.87-4.el7.x86_64 zlib-1.2.7-20.el7_9.x86_64 libcap-ng-0.7.5-4.el7.x86_64 xz-libs-5.2.2-2.el7_9.x86_64 perl-Exporter-5.68-3.el7.noarch p11-kit-trust-0.23.5-3.el7.x86_64 perl-srpm-macros-1-8.el7.noarch perl-macros-5.16.3-299.el7_9.x86_64 bash-4.2.46-35.el7_9.x86_64 make-3.82-24.el7.x86_64 expat-2.1.0-14.el7_9.x86_64 libmount-2.23.2-65.el7_9.1.x86_64 shared-mime-info-1.8-5.el7.x86_64 perl-Time-Local-1.2300-2.el7.noarch libtasn1-4.10-1.el7.x86_64 device-mapper-1.02.170-6.el7_9.5.x86_64 perl-Pod-Usage-1.63-3.el7.noarch info-5.1-5.el7.x86_64 acl-2.2.51-15.el7.x86_64 python-rpm-macros-3-34.el7.noarch lua-srpm-macros-1-3.el7.noarch filesystem-3.2-25.el7.x86_64 which-2.20-7.el7.x86_64 grep-2.20-3.el7.x86_64 dracut-033-572.el7.x86_64 ncurses-5.9-14.20130511.el7_4.x86_64 openldap-2.4.44-25.el7_9.x86_64 lua-5.1.4-15.el7.x86_64 tar-1.26-35.el7.x86_64 shadow-utils-4.6-5.el7.x86_64 libuuid-2.23.2-65.el7_9.1.x86_64 perl-parent-0.225-244.el7.noarch gawk-4.0.2-4.el7_3.1.x86_64 perl-PathTools-3.40-5.el7.x86_64 python-libs-2.7.5-92.el7_9.x86_64 libcurl-7.29.0-59.el7_9.1.x86_64 gdbm-1.10-8.el7.x86_64 openssl-libs-1.0.2k-25.el7_9.x86_64 pcre-8.32-17.el7.x86_64 file-5.11-37.el7.x86_64 nspr-4.32.0-1.el7_9.x86_64 kpartx-0.4.9-135.el7_9.x86_64 xz-5.2.2-2.el7_9.x86_64 perl-Time-HiRes-1.9725-3.el7.x86_64 sed-4.2.2-7.el7.x86_64 popt-1.13-16.el7.x86_64 file-libs-5.11-37.el7.x86_64 groff-base-1.22.2-8.el7.x86_64 pinentry-0.8.1-17.el7.x86_64 perl-threads-shared-1.43-6.el7.x86_64 unzip-6.0-24.el7_9.x86_64 nss-3.67.0-4.el7_9.x86_64 libattr-2.4.46-13.el7.x86_64 nss-sysinit-3.67.0-4.el7_9.x86_64 ca-certificates-2021.2.50-72.el7_9.noarch elfutils-libs-0.176-5.el7.x86_64 elfutils-0.176-5.el7.x86_64 epel-rpm-macros-7-35.noarch cpp-4.8.5-44.el7.x86_64 pam-1.1.8-23.el7.x86_64 python-srpm-macros-3-34.el7.noarch perl-podlators-2.5.1-3.el7.noarch libgcc-4.8.5-44.el7.x86_64 nss-softokn-freebl-3.67.0-3.el7_9.x86_64 hardlink-1.0-19.el7.x86_64 kmod-20-28.el7.x86_64 diffutils-3.3-5.el7.x86_64 perl-Getopt-Long-2.40-3.el7.noarch perl-constant-1.27-2.el7.noarch dbus-1.10.24-15.el7.x86_64 util-linux-2.23.2-65.el7_9.1.x86_64 perl-libs-5.16.3-299.el7_9.x86_64 perl-File-Path-2.09-2.el7.noarch tzdata-2022a-1.el7.noarch glibc-headers-2.17-326.el7_9.x86_64 binutils-2.27-44.base.el7_9.1.x86_64 pth-2.0.7-23.el7.x86_64 kernel-headers-3.10.0-1160.71.1.el7.x86_64 mpfr-3.1.1-4.el7.x86_64 perl-Pod-Escapes-1.04-299.el7_9.noarch device-mapper-libs-1.02.170-6.el7_9.5.x86_64 rpm-build-4.11.3-48.el7_9.x86_64 cyrus-sasl-lib-2.1.26-24.el7_9.x86_64 libselinux-2.5-15.el7.x86_64 libgcrypt-1.5.3-14.el7.x86_64 perl-Thread-Queue-3.02-2.el7.noarch libcom_err-1.42.9-19.el7.x86_64 cracklib-2.9.0-11.el7.x86_64 readline-6.2-11.el7.x86_64 coreutils-8.22-24.el7_9.2.x86_64 json-c-0.11-4.el7_0.x86_64 zip-3.0-11.el7.x86_64 ncurses-libs-5.9-14.20130511.el7_4.x86_64 nss-pem-1.0.3-7.el7.x86_64 perl-HTTP-Tiny-0.033-3.el7.noarch elfutils-default-yama-scope-0.176-5.el7.noarch perl-Text-ParseWords-3.29-4.el7.noarch gcc-4.8.5-44.el7.x86_64 dwz-0.11-3.el7.x86_64 perl-File-Temp-0.23.01-3.el7.noarch gnupg2-2.0.22-5.el7_5.x86_64 nss-util-3.67.0-1.el7_9.x86_64 libmpc-1.0.1-3.el7.x86_64 curl-7.29.0-59.el7_9.1.x86_64 glib2-2.56.1-9.el7_9.x86_64 glibc-devel-2.17-326.el7_9.x86_64 sqlite-3.7.17-8.el7_7.1.x86_64 findutils-4.5.11-6.el7.x86_64 libstdc++-4.8.5-44.el7.x86_64 rpm-libs-4.11.3-48.el7_9.x86_64 libssh2-1.8.0-4.el7.x86_64 redhat-rpm-config-9.1.0-88.el7.centos.noarch libidn-1.28-4.el7.x86_64 perl-Encode-2.51-7.el7.x86_64 ncurses-base-5.9-14.20130511.el7_4.noarch perl-Storable-2.45-3.el7.x86_64 p11-kit-0.23.5-3.el7.x86_64 cpio-2.11-28.el7.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 elfutils-libelf-0.176-5.el7.x86_64 gzip-1.5-11.el7_9.x86_64 kmod-libs-20-28.el7.x86_64 libsmartcols-2.23.2-65.el7_9.1.x86_64 libassuan-2.1.0-3.el7.x86_64 libsemanage-2.5-14.el7.x86_64 centos-release-7-9.2009.1.el7.centos.x86_64 nss-softokn-3.67.0-3.el7_9.x86_64 libdb-utils-5.3.21-25.el7.x86_64 dbus-libs-1.10.24-15.el7.x86_64 glibc-common-2.17-326.el7_9.x86_64 libuser-0.60-9.el7.x86_64 chkconfig-1.7.6-1.el7.x86_64 gpg-pubkey-f4a80eb5-53a7ff4b bzip2-libs-1.0.6-13.el7.x86_64 libutempter-1.1.6-4.el7.x86_64 libpwquality-1.2.3-5.el7.x86_64 systemd-219-78.el7_9.5.x86_64 cryptsetup-libs-2.0.3-6.el7.x86_64 pkgconfig-0.27.1-4.el7.x86_64 ustr-1.0.4-16.el7.x86_64 libdb-5.3.21-25.el7.x86_64 libacl-2.2.51-15.el7.x86_64 lz4-1.8.3-1.el7.x86_64 systemd-libs-219-78.el7_9.5.x86_64 libblkid-2.23.2-65.el7_9.1.x86_64 perl-Pod-Simple-3.28-4.el7.noarch nss-tools-3.67.0-4.el7_9.x86_64 gcc-c++-4.8.5-44.el7.x86_64 libverto-0.2.5-4.el7.x86_64 glibc-2.17-326.el7_9.x86_64 rpm-4.11.3-48.el7_9.x86_64 libgomp-4.8.5-44.el7.x86_64 perl-Filter-1.49-3.el7.x86_64 krb5-libs-1.15.1-54.el7_9.x86_64 perl-Carp-1.26-244.el7.noarch cracklib-dicts-2.9.0-11.el7.x86_64 python2-rpm-macros-3-34.el7.noarch epel-release-7-14.noarch perl-Scalar-List-Utils-1.27-248.el7.x86_64 libcap-2.22-11.el7.x86_64 gpg-pubkey-352c64e5-52ae6884 basesystem-10.0-7.el7.centos.noarch libxml2-2.9.1-6.el7_9.6.x86_64 setup-2.8.71-11.el7.noarch patch-2.7.1-12.el7_7.x86_64 Start: buildsrpm Start: rpmbuild -bs Building target platforms: x86_64 Building for target x86_64 Wrote: /builddir/build/SRPMS/alarm-clock-master-1.el7.src.rpm Finish: rpmbuild -bs Finish: buildsrpm INFO: Done(/var/lib/copr-rpmbuild/workspace/workdir-sgcn9yk_/alarm-clock/gnome-applet-alarm-clock-0.3.4.fc23.x86_64.spec) Config(child) 1 minutes 28 seconds INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results INFO: Cleaning up build root ('cleanup_on_success=True') Start: clean chroot INFO: unmounting tmpfs. Finish: clean chroot Finish: run Running (timeout=18000): unbuffer mock --rebuild /var/lib/copr-rpmbuild/results/alarm-clock-master-1.el7.src.rpm --resultdir /var/lib/copr-rpmbuild/results --uniqueext 1658945077.221752 -r /var/lib/copr-rpmbuild/results/configs/child.cfg INFO: mock.py version 3.0 starting (python version = 3.10.4, NVR = mock-3.0-1.fc35)... INFO: Using 'dnf' instead of 'yum' for bootstrap chroot Start(bootstrap): init plugins INFO: tmpfs initialized INFO: selinux enabled INFO: chroot_scan: initialized INFO: compress_logs: initialized Finish(bootstrap): init plugins Start: init plugins INFO: tmpfs initialized INFO: selinux enabled INFO: chroot_scan: initialized INFO: compress_logs: initialized Finish: init plugins INFO: Signal handler active Start: run INFO: Start(/var/lib/copr-rpmbuild/results/alarm-clock-master-1.el7.src.rpm) Config(centos+epel-7-x86_64) Start: clean chroot Finish: clean chroot Start(bootstrap): chroot init INFO: mounting tmpfs at /var/lib/mock/centos+epel-7-x86_64-bootstrap-1658945077.221752/root. INFO: reusing tmpfs at /var/lib/mock/centos+epel-7-x86_64-bootstrap-1658945077.221752/root. INFO: calling preinit hooks INFO: enabled root cache INFO: enabled package manager cache Start(bootstrap): cleaning package manager metadata Finish(bootstrap): cleaning package manager metadata INFO: enabled HW Info plugin Mock Version: 3.0 INFO: Mock Version: 3.0 Finish(bootstrap): chroot init Start: chroot init INFO: mounting tmpfs at /var/lib/mock/centos+epel-7-x86_64-1658945077.221752/root. INFO: calling preinit hooks INFO: enabled root cache Start: unpacking root cache Finish: unpacking root cache INFO: enabled package manager cache Start: cleaning package manager metadata Finish: cleaning package manager metadata INFO: enabled HW Info plugin Mock Version: 3.0 INFO: Mock Version: 3.0 Start: yum update Failed to set locale, defaulting to C copr_base | 3.3 kB 00:00 base | 3.6 kB 00:00 centos-sclo-rh | 3.0 kB 00:00 centos-sclo-sclo | 3.0 kB 00:00 epel | 4.7 kB 00:00 extras | 2.9 kB 00:00 updates | 2.9 kB 00:00 epel/x86_64/primary_db | 7.0 MB 00:00 No packages marked for update Finish: yum update Finish: chroot init Start: build phase for alarm-clock-master-1.el7.src.rpm Start: build setup for alarm-clock-master-1.el7.src.rpm Building target platforms: x86_64 Building for target x86_64 Wrote: /builddir/build/SRPMS/alarm-clock-master-1.el7.src.rpm Failed to set locale, defaulting to C copr_base | 3.3 kB 00:00 base | 3.6 kB 00:00 centos-sclo-rh | 3.0 kB 00:00 centos-sclo-sclo | 3.0 kB 00:00 epel | 4.7 kB 00:00 extras | 2.9 kB 00:00 updates | 2.9 kB 00:00 Getting requirements for alarm-clock-master-1.el7.src --> glib2-devel-2.56.1-9.el7_9.x86_64 --> gtk2-devel-2.24.31-1.el7.x86_64 --> GConf2-devel-3.2.6-8.el7.x86_64 --> gstreamer1-devel-1.10.4-2.el7.x86_64 --> libnotify-devel-0.7.7-1.el7.x86_64 --> libxml2-devel-2.9.1-6.el7_9.6.x86_64 --> unique-devel-1.1.6-10.el7.x86_64 --> libappindicator-devel-12.10.0-13.el7.x86_64 --> intltool-0.50.2-7.el7.noarch --> gnome-icon-theme-devel-3.12.0-1.el7.noarch --> dh-autoreconf-19-1.el7.noarch --> gnome-common-3.18.0-1.el7.noarch --> Running transaction check ---> Package GConf2-devel.x86_64 0:3.2.6-8.el7 will be installed --> Processing Dependency: GConf2 = 3.2.6-8.el7 for package: GConf2-devel-3.2.6-8.el7.x86_64 --> Processing Dependency: pkgconfig(dbus-1) for package: GConf2-devel-3.2.6-8.el7.x86_64 --> Processing Dependency: automake for package: GConf2-devel-3.2.6-8.el7.x86_64 --> Processing Dependency: /usr/bin/python for package: GConf2-devel-3.2.6-8.el7.x86_64 --> Processing Dependency: libgconf-2.so.4()(64bit) for package: GConf2-devel-3.2.6-8.el7.x86_64 ---> Package dh-autoreconf.noarch 0:19-1.el7 will be installed --> Processing Dependency: autoconf for package: dh-autoreconf-19-1.el7.noarch --> Processing Dependency: cdbs for package: dh-autoreconf-19-1.el7.noarch --> Processing Dependency: debhelper for package: dh-autoreconf-19-1.el7.noarch --> Processing Dependency: gettext-devel for package: dh-autoreconf-19-1.el7.noarch --> Processing Dependency: libtool for package: dh-autoreconf-19-1.el7.noarch --> Processing Dependency: perl(Debian::Debhelper::Dh_Lib) for package: dh-autoreconf-19-1.el7.noarch ---> Package glib2-devel.x86_64 0:2.56.1-9.el7_9 will be installed --> Processing Dependency: pkgconfig(libpcre) for package: glib2-devel-2.56.1-9.el7_9.x86_64 ---> Package gnome-common.noarch 0:3.18.0-1.el7 will be installed --> Processing Dependency: yelp-tools for package: gnome-common-3.18.0-1.el7.noarch --> Processing Dependency: gettext for package: gnome-common-3.18.0-1.el7.noarch --> Processing Dependency: autoconf-archive for package: gnome-common-3.18.0-1.el7.noarch ---> Package gnome-icon-theme-devel.noarch 0:3.12.0-1.el7 will be installed --> Processing Dependency: gnome-icon-theme = 3.12.0-1.el7 for package: gnome-icon-theme-devel-3.12.0-1.el7.noarch ---> Package gstreamer1-devel.x86_64 0:1.10.4-2.el7 will be installed --> Processing Dependency: gstreamer1 = 1.10.4-2.el7 for package: gstreamer1-devel-1.10.4-2.el7.x86_64 --> Processing Dependency: check-devel for package: gstreamer1-devel-1.10.4-2.el7.x86_64 --> Processing Dependency: libgstreamer-1.0.so.0()(64bit) for package: gstreamer1-devel-1.10.4-2.el7.x86_64 --> Processing Dependency: libgstnet-1.0.so.0()(64bit) for package: gstreamer1-devel-1.10.4-2.el7.x86_64 --> Processing Dependency: libgstcontroller-1.0.so.0()(64bit) for package: gstreamer1-devel-1.10.4-2.el7.x86_64 --> Processing Dependency: libgstcheck-1.0.so.0()(64bit) for package: gstreamer1-devel-1.10.4-2.el7.x86_64 --> Processing Dependency: libgstbase-1.0.so.0()(64bit) for package: gstreamer1-devel-1.10.4-2.el7.x86_64 ---> Package gtk2-devel.x86_64 0:2.24.31-1.el7 will be installed --> Processing Dependency: gtk2 = 2.24.31-1.el7 for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: pango-devel >= 1.20.0-1 for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: cairo-devel >= 1.6.0-1 for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: atk-devel >= 1.29.4-2 for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: pkgconfig(pangoft2) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: pkgconfig(pangocairo) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: pkgconfig(pango) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: pkgconfig(gdk-pixbuf-2.0) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: pkgconfig(cairo) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: pkgconfig(atk) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libXrandr-devel for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libXinerama-devel for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libXi-devel for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libXfixes-devel for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libXext-devel for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libXcursor-devel for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libXcomposite-devel for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libX11-devel for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: gdk-pixbuf2-devel for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libpangoft2-1.0.so.0()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libpangocairo-1.0.so.0()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libpango-1.0.so.0()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libgtk-x11-2.0.so.0()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libgdk_pixbuf-2.0.so.0()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libgdk-x11-2.0.so.0()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libgailutil.so.18()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libfreetype.so.6()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libfontconfig.so.1()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libcairo.so.2()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libatk-1.0.so.0()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libXrender.so.1()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libXrandr.so.2()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libXinerama.so.1()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libXi.so.6()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libXfixes.so.3()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libXext.so.6()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libXdamage.so.1()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libXcursor.so.1()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libXcomposite.so.1()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 --> Processing Dependency: libX11.so.6()(64bit) for package: gtk2-devel-2.24.31-1.el7.x86_64 ---> Package intltool.noarch 0:0.50.2-7.el7 will be installed --> Processing Dependency: perl(XML::Parser) for package: intltool-0.50.2-7.el7.noarch ---> Package libappindicator-devel.x86_64 0:12.10.0-13.el7 will be installed --> Processing Dependency: libappindicator = 12.10.0-13.el7 for package: libappindicator-devel-12.10.0-13.el7.x86_64 --> Processing Dependency: pkgconfig(dbusmenu-glib-0.4) for package: libappindicator-devel-12.10.0-13.el7.x86_64 --> Processing Dependency: libdbusmenu-devel for package: libappindicator-devel-12.10.0-13.el7.x86_64 --> Processing Dependency: dbus-glib-devel for package: libappindicator-devel-12.10.0-13.el7.x86_64 --> Processing Dependency: libappindicator.so.1()(64bit) for package: libappindicator-devel-12.10.0-13.el7.x86_64 ---> Package libnotify-devel.x86_64 0:0.7.7-1.el7 will be installed --> Processing Dependency: libnotify(x86-64) = 0.7.7-1.el7 for package: libnotify-devel-0.7.7-1.el7.x86_64 --> Processing Dependency: libnotify.so.4()(64bit) for package: libnotify-devel-0.7.7-1.el7.x86_64 ---> Package libxml2-devel.x86_64 0:2.9.1-6.el7_9.6 will be installed --> Processing Dependency: zlib-devel for package: libxml2-devel-2.9.1-6.el7_9.6.x86_64 --> Processing Dependency: xz-devel for package: libxml2-devel-2.9.1-6.el7_9.6.x86_64 ---> Package unique-devel.x86_64 0:1.1.6-10.el7 will be installed --> Processing Dependency: unique = 1.1.6-10.el7 for package: unique-devel-1.1.6-10.el7.x86_64 --> Processing Dependency: libunique-1.0.so.0()(64bit) for package: unique-devel-1.1.6-10.el7.x86_64 --> Running transaction check ---> Package GConf2.x86_64 0:3.2.6-8.el7 will be installed --> Processing Dependency: /usr/bin/killall for package: GConf2-3.2.6-8.el7.x86_64 --> Processing Dependency: libpolkit-gobject-1.so.0()(64bit) for package: GConf2-3.2.6-8.el7.x86_64 --> Processing Dependency: libdbus-glib-1.so.2()(64bit) for package: GConf2-3.2.6-8.el7.x86_64 ---> Package atk.x86_64 0:2.28.1-2.el7 will be installed ---> Package atk-devel.x86_64 0:2.28.1-2.el7 will be installed ---> Package autoconf.noarch 0:2.69-11.el7 will be installed --> Processing Dependency: m4 >= 1.4.14 for package: autoconf-2.69-11.el7.noarch --> Processing Dependency: perl(Data::Dumper) for package: autoconf-2.69-11.el7.noarch ---> Package autoconf-archive.noarch 0:2017.03.21-1.el7 will be installed ---> Package automake.noarch 0:1.13.4-3.el7 will be installed --> Processing Dependency: perl(TAP::Parser) for package: automake-1.13.4-3.el7.noarch ---> Package cairo.x86_64 0:1.15.12-4.el7 will be installed --> Processing Dependency: libpng15.so.15(PNG15_0)(64bit) for package: cairo-1.15.12-4.el7.x86_64 --> Processing Dependency: libxcb.so.1()(64bit) for package: cairo-1.15.12-4.el7.x86_64 --> Processing Dependency: libxcb-shm.so.0()(64bit) for package: cairo-1.15.12-4.el7.x86_64 --> Processing Dependency: libxcb-render.so.0()(64bit) for package: cairo-1.15.12-4.el7.x86_64 --> Processing Dependency: libpng15.so.15()(64bit) for package: cairo-1.15.12-4.el7.x86_64 --> Processing Dependency: libpixman-1.so.0()(64bit) for package: cairo-1.15.12-4.el7.x86_64 --> Processing Dependency: libGL.so.1()(64bit) for package: cairo-1.15.12-4.el7.x86_64 --> Processing Dependency: libEGL.so.1()(64bit) for package: cairo-1.15.12-4.el7.x86_64 ---> Package cairo-devel.x86_64 0:1.15.12-4.el7 will be installed --> Processing Dependency: pkgconfig(xrender) >= 0.6 for package: cairo-devel-1.15.12-4.el7.x86_64 --> Processing Dependency: pkgconfig(xcb-render) >= 1.6 for package: cairo-devel-1.15.12-4.el7.x86_64 --> Processing Dependency: pkgconfig(xcb) >= 1.6 for package: cairo-devel-1.15.12-4.el7.x86_64 --> Processing Dependency: pkgconfig(pixman-1) >= 0.30.0 for package: cairo-devel-1.15.12-4.el7.x86_64 --> Processing Dependency: pkgconfig(freetype2) >= 9.7.3 for package: cairo-devel-1.15.12-4.el7.x86_64 --> Processing Dependency: pkgconfig(fontconfig) >= 2.2.95 for package: cairo-devel-1.15.12-4.el7.x86_64 --> Processing Dependency: pkgconfig(xcb-shm) for package: cairo-devel-1.15.12-4.el7.x86_64 --> Processing Dependency: pkgconfig(libpng) for package: cairo-devel-1.15.12-4.el7.x86_64 --> Processing Dependency: pkgconfig(gl) for package: cairo-devel-1.15.12-4.el7.x86_64 --> Processing Dependency: pkgconfig(egl) for package: cairo-devel-1.15.12-4.el7.x86_64 ---> Package cdbs.noarch 0:0.4.150-3.el7 will be installed --> Processing Dependency: perl(Font::TTF::Font) for package: cdbs-0.4.150-3.el7.noarch --> Processing Dependency: perl(Font::TTF::Ttc) for package: cdbs-0.4.150-3.el7.noarch --> Processing Dependency: perl(Image::ExifTool) for package: cdbs-0.4.150-3.el7.noarch --> Processing Dependency: perl(Regexp::Assemble) for package: cdbs-0.4.150-3.el7.noarch --> Processing Dependency: perl(autodie) for package: cdbs-0.4.150-3.el7.noarch ---> Package check-devel.x86_64 0:0.9.9-5.el7 will be installed --> Processing Dependency: check(x86-64) = 0.9.9-5.el7 for package: check-devel-0.9.9-5.el7.x86_64 --> Processing Dependency: libcheck.so.0()(64bit) for package: check-devel-0.9.9-5.el7.x86_64 ---> Package dbus-devel.x86_64 1:1.10.24-15.el7 will be installed ---> Package dbus-glib-devel.x86_64 0:0.100-7.el7 will be installed ---> Package debhelper.noarch 0:11.4-2.el7 will be installed --> Processing Dependency: dpkg-dev >= 1.18.0 for package: debhelper-11.4-2.el7.noarch --> Processing Dependency: html2text for package: debhelper-11.4-2.el7.noarch --> Processing Dependency: perl(Dpkg::BuildProfiles) for package: debhelper-11.4-2.el7.noarch --> Processing Dependency: po-debconf for package: debhelper-11.4-2.el7.noarch ---> Package fontconfig.x86_64 0:2.13.0-4.3.el7 will be installed --> Processing Dependency: fontpackages-filesystem for package: fontconfig-2.13.0-4.3.el7.x86_64 --> Processing Dependency: dejavu-sans-fonts for package: fontconfig-2.13.0-4.3.el7.x86_64 ---> Package freetype.x86_64 0:2.8-14.el7_9.1 will be installed ---> Package gdk-pixbuf2.x86_64 0:2.36.12-3.el7 will be installed --> Processing Dependency: libtiff.so.5(LIBTIFF_4.0)(64bit) for package: gdk-pixbuf2-2.36.12-3.el7.x86_64 --> Processing Dependency: libjpeg.so.62(LIBJPEG_6.2)(64bit) for package: gdk-pixbuf2-2.36.12-3.el7.x86_64 --> Processing Dependency: libtiff.so.5()(64bit) for package: gdk-pixbuf2-2.36.12-3.el7.x86_64 --> Processing Dependency: libjpeg.so.62()(64bit) for package: gdk-pixbuf2-2.36.12-3.el7.x86_64 --> Processing Dependency: libjasper.so.1()(64bit) for package: gdk-pixbuf2-2.36.12-3.el7.x86_64 ---> Package gdk-pixbuf2-devel.x86_64 0:2.36.12-3.el7 will be installed ---> Package gettext.x86_64 0:0.19.8.1-3.el7 will be installed --> Processing Dependency: gettext-libs(x86-64) = 0.19.8.1-3.el7 for package: gettext-0.19.8.1-3.el7.x86_64 --> Processing Dependency: libunistring.so.0()(64bit) for package: gettext-0.19.8.1-3.el7.x86_64 --> Processing Dependency: libgettextsrc-0.19.8.1.so()(64bit) for package: gettext-0.19.8.1-3.el7.x86_64 --> Processing Dependency: libgettextlib-0.19.8.1.so()(64bit) for package: gettext-0.19.8.1-3.el7.x86_64 --> Processing Dependency: libcroco-0.6.so.3()(64bit) for package: gettext-0.19.8.1-3.el7.x86_64 ---> Package gettext-devel.x86_64 0:0.19.8.1-3.el7 will be installed --> Processing Dependency: gettext-common-devel = 0.19.8.1-3.el7 for package: gettext-devel-0.19.8.1-3.el7.x86_64 --> Processing Dependency: git for package: gettext-devel-0.19.8.1-3.el7.x86_64 ---> Package gnome-icon-theme.noarch 0:3.12.0-1.el7 will be installed --> Processing Dependency: hicolor-icon-theme for package: gnome-icon-theme-3.12.0-1.el7.noarch ---> Package gstreamer1.x86_64 0:1.10.4-2.el7 will be installed ---> Package gtk2.x86_64 0:2.24.31-1.el7 will be installed --> Processing Dependency: gtk-update-icon-cache for package: gtk2-2.24.31-1.el7.x86_64 --> Processing Dependency: libcups.so.2()(64bit) for package: gtk2-2.24.31-1.el7.x86_64 ---> Package libX11.x86_64 0:1.6.7-4.el7_9 will be installed --> Processing Dependency: libX11-common >= 1.6.7-4.el7_9 for package: libX11-1.6.7-4.el7_9.x86_64 ---> Package libX11-devel.x86_64 0:1.6.7-4.el7_9 will be installed --> Processing Dependency: pkgconfig(xproto) for package: libX11-devel-1.6.7-4.el7_9.x86_64 --> Processing Dependency: pkgconfig(kbproto) for package: libX11-devel-1.6.7-4.el7_9.x86_64 ---> Package libXcomposite.x86_64 0:0.4.4-4.1.el7 will be installed ---> Package libXcomposite-devel.x86_64 0:0.4.4-4.1.el7 will be installed ---> Package libXcursor.x86_64 0:1.1.15-1.el7 will be installed ---> Package libXcursor-devel.x86_64 0:1.1.15-1.el7 will be installed ---> Package libXdamage.x86_64 0:1.1.4-4.1.el7 will be installed ---> Package libXext.x86_64 0:1.3.3-3.el7 will be installed ---> Package libXext-devel.x86_64 0:1.3.3-3.el7 will be installed ---> Package libXfixes.x86_64 0:5.0.3-1.el7 will be installed ---> Package libXfixes-devel.x86_64 0:5.0.3-1.el7 will be installed ---> Package libXi.x86_64 0:1.7.9-1.el7 will be installed ---> Package libXi-devel.x86_64 0:1.7.9-1.el7 will be installed ---> Package libXinerama.x86_64 0:1.1.3-2.1.el7 will be installed ---> Package libXinerama-devel.x86_64 0:1.1.3-2.1.el7 will be installed ---> Package libXrandr.x86_64 0:1.5.1-2.el7 will be installed ---> Package libXrandr-devel.x86_64 0:1.5.1-2.el7 will be installed ---> Package libXrender.x86_64 0:0.9.10-1.el7 will be installed ---> Package libappindicator.x86_64 0:12.10.0-13.el7 will be installed --> Processing Dependency: libindicator.so.7()(64bit) for package: libappindicator-12.10.0-13.el7.x86_64 --> Processing Dependency: libdbusmenu-gtk.so.4()(64bit) for package: libappindicator-12.10.0-13.el7.x86_64 --> Processing Dependency: libdbusmenu-glib.so.4()(64bit) for package: libappindicator-12.10.0-13.el7.x86_64 ---> Package libdbusmenu-devel.x86_64 0:16.04.0-4.el7 will be installed ---> Package libnotify.x86_64 0:0.7.7-1.el7 will be installed ---> Package libtool.x86_64 0:2.4.2-22.el7_3 will be installed ---> Package pango.x86_64 0:1.42.4-4.el7_7 will be installed --> Processing Dependency: libthai(x86-64) >= 0.1.9 for package: pango-1.42.4-4.el7_7.x86_64 --> Processing Dependency: libXft(x86-64) >= 2.0.0 for package: pango-1.42.4-4.el7_7.x86_64 --> Processing Dependency: harfbuzz(x86-64) >= 1.4.2 for package: pango-1.42.4-4.el7_7.x86_64 --> Processing Dependency: fribidi(x86-64) >= 1.0 for package: pango-1.42.4-4.el7_7.x86_64 --> Processing Dependency: libthai.so.0(LIBTHAI_0.1)(64bit) for package: pango-1.42.4-4.el7_7.x86_64 --> Processing Dependency: libthai.so.0()(64bit) for package: pango-1.42.4-4.el7_7.x86_64 --> Processing Dependency: libharfbuzz.so.0()(64bit) for package: pango-1.42.4-4.el7_7.x86_64 --> Processing Dependency: libfribidi.so.0()(64bit) for package: pango-1.42.4-4.el7_7.x86_64 --> Processing Dependency: libXft.so.2()(64bit) for package: pango-1.42.4-4.el7_7.x86_64 ---> Package pango-devel.x86_64 0:1.42.4-4.el7_7 will be installed --> Processing Dependency: pkgconfig(xft) for package: pango-devel-1.42.4-4.el7_7.x86_64 --> Processing Dependency: pkgconfig(harfbuzz) for package: pango-devel-1.42.4-4.el7_7.x86_64 --> Processing Dependency: pkgconfig(fribidi) for package: pango-devel-1.42.4-4.el7_7.x86_64 ---> Package pcre-devel.x86_64 0:8.32-17.el7 will be installed ---> Package perl-XML-Parser.x86_64 0:2.41-10.el7 will be installed ---> Package python.x86_64 0:2.7.5-92.el7_9 will be installed ---> Package unique.x86_64 0:1.1.6-10.el7 will be installed ---> Package xz-devel.x86_64 0:5.2.2-2.el7_9 will be installed ---> Package yelp-tools.noarch 0:3.28.0-1.el7 will be installed --> Processing Dependency: yelp-xsl for package: yelp-tools-3.28.0-1.el7.noarch --> Processing Dependency: mallard-rng for package: yelp-tools-3.28.0-1.el7.noarch --> Processing Dependency: /usr/bin/itstool for package: yelp-tools-3.28.0-1.el7.noarch ---> Package zlib-devel.x86_64 0:1.2.7-20.el7_9 will be installed --> Running transaction check ---> Package check.x86_64 0:0.9.9-5.el7 will be installed ---> Package cups-libs.x86_64 1:1.6.3-51.el7 will be installed --> Processing Dependency: libavahi-common.so.3()(64bit) for package: 1:cups-libs-1.6.3-51.el7.x86_64 --> Processing Dependency: libavahi-client.so.3()(64bit) for package: 1:cups-libs-1.6.3-51.el7.x86_64 ---> Package dbus-glib.x86_64 0:0.100-7.el7 will be installed ---> Package dejavu-sans-fonts.noarch 0:2.33-6.el7 will be installed --> Processing Dependency: dejavu-fonts-common = 2.33-6.el7 for package: dejavu-sans-fonts-2.33-6.el7.noarch ---> Package dpkg-dev.noarch 0:1.18.25-10.el7 will be installed --> Processing Dependency: lzma for package: dpkg-dev-1.18.25-10.el7.noarch --> Processing Dependency: perl(MIME::Lite) for package: dpkg-dev-1.18.25-10.el7.noarch ---> Package dpkg-perl.noarch 0:1.18.25-10.el7 will be installed --> Processing Dependency: dpkg = 1.18.25-10.el7 for package: dpkg-perl-1.18.25-10.el7.noarch --> Processing Dependency: perl(Digest) for package: dpkg-perl-1.18.25-10.el7.noarch --> Processing Dependency: perl(Digest::MD5) for package: dpkg-perl-1.18.25-10.el7.noarch --> Processing Dependency: perl(Digest::SHA) for package: dpkg-perl-1.18.25-10.el7.noarch --> Processing Dependency: perl(Digest::SHA1) for package: dpkg-perl-1.18.25-10.el7.noarch --> Processing Dependency: perl(Digest::SHA3) for package: dpkg-perl-1.18.25-10.el7.noarch --> Processing Dependency: perl(Time::Piece) for package: dpkg-perl-1.18.25-10.el7.noarch --> Processing Dependency: perl-Time-Piece for package: dpkg-perl-1.18.25-10.el7.noarch --> Processing Dependency: perl-TimeDate for package: dpkg-perl-1.18.25-10.el7.noarch ---> Package fontconfig-devel.x86_64 0:2.13.0-4.3.el7 will be installed --> Processing Dependency: pkgconfig(uuid) for package: fontconfig-devel-2.13.0-4.3.el7.x86_64 --> Processing Dependency: pkgconfig(expat) for package: fontconfig-devel-2.13.0-4.3.el7.x86_64 ---> Package fontpackages-filesystem.noarch 0:1.44-8.el7 will be installed ---> Package freetype-devel.x86_64 0:2.8-14.el7_9.1 will be installed ---> Package fribidi.x86_64 0:1.0.2-1.el7_7.1 will be installed ---> Package fribidi-devel.x86_64 0:1.0.2-1.el7_7.1 will be installed ---> Package gettext-common-devel.noarch 0:0.19.8.1-3.el7 will be installed ---> Package gettext-libs.x86_64 0:0.19.8.1-3.el7 will be installed ---> Package git.x86_64 0:1.8.3.1-23.el7_8 will be installed --> Processing Dependency: perl-Git = 1.8.3.1-23.el7_8 for package: git-1.8.3.1-23.el7_8.x86_64 --> Processing Dependency: rsync for package: git-1.8.3.1-23.el7_8.x86_64 --> Processing Dependency: perl(Term::ReadKey) for package: git-1.8.3.1-23.el7_8.x86_64 --> Processing Dependency: perl(Git) for package: git-1.8.3.1-23.el7_8.x86_64 --> Processing Dependency: perl(Error) for package: git-1.8.3.1-23.el7_8.x86_64 --> Processing Dependency: openssh-clients for package: git-1.8.3.1-23.el7_8.x86_64 --> Processing Dependency: less for package: git-1.8.3.1-23.el7_8.x86_64 ---> Package gtk-update-icon-cache.x86_64 0:3.22.30-8.el7_9 will be installed ---> Package harfbuzz.x86_64 0:1.7.5-2.el7 will be installed --> Processing Dependency: libgraphite2.so.3()(64bit) for package: harfbuzz-1.7.5-2.el7.x86_64 ---> Package harfbuzz-devel.x86_64 0:1.7.5-2.el7 will be installed --> Processing Dependency: harfbuzz-icu(x86-64) = 1.7.5-2.el7 for package: harfbuzz-devel-1.7.5-2.el7.x86_64 --> Processing Dependency: pkgconfig(icu-uc) for package: harfbuzz-devel-1.7.5-2.el7.x86_64 --> Processing Dependency: pkgconfig(graphite2) for package: harfbuzz-devel-1.7.5-2.el7.x86_64 --> Processing Dependency: libharfbuzz-icu.so.0()(64bit) for package: harfbuzz-devel-1.7.5-2.el7.x86_64 ---> Package hicolor-icon-theme.noarch 0:0.12-7.el7 will be installed ---> Package itstool.noarch 0:2.0.2-1.el7 will be installed --> Processing Dependency: libxml2-python for package: itstool-2.0.2-1.el7.noarch ---> Package jasper-libs.x86_64 0:1.900.1-33.el7 will be installed ---> Package libX11-common.noarch 0:1.6.7-4.el7_9 will be installed ---> Package libXft.x86_64 0:2.3.2-2.el7 will be installed ---> Package libXft-devel.x86_64 0:2.3.2-2.el7 will be installed ---> Package libXrender-devel.x86_64 0:0.9.10-1.el7 will be installed ---> Package libcroco.x86_64 0:0.6.12-6.el7_9 will be installed ---> Package libdbusmenu.x86_64 0:16.04.0-4.el7 will be installed ---> Package libdbusmenu-gtk2.x86_64 0:16.04.0-4.el7 will be installed ---> Package libglvnd-egl.x86_64 1:1.0.1-0.8.git5baa1e5.el7 will be installed --> Processing Dependency: libglvnd(x86-64) = 1:1.0.1-0.8.git5baa1e5.el7 for package: 1:libglvnd-egl-1.0.1-0.8.git5baa1e5.el7.x86_64 --> Processing Dependency: mesa-libEGL(x86-64) >= 13.0.4-1 for package: 1:libglvnd-egl-1.0.1-0.8.git5baa1e5.el7.x86_64 --> Processing Dependency: libGLdispatch.so.0()(64bit) for package: 1:libglvnd-egl-1.0.1-0.8.git5baa1e5.el7.x86_64 ---> Package libglvnd-glx.x86_64 1:1.0.1-0.8.git5baa1e5.el7 will be installed --> Processing Dependency: mesa-libGL(x86-64) >= 13.0.4-1 for package: 1:libglvnd-glx-1.0.1-0.8.git5baa1e5.el7.x86_64 ---> Package libindicator.x86_64 0:12.10.1-6.el7 will be installed ---> Package libjpeg-turbo.x86_64 0:1.2.90-8.el7 will be installed ---> Package libpng.x86_64 2:1.5.13-8.el7 will be installed ---> Package libpng-devel.x86_64 2:1.5.13-8.el7 will be installed ---> Package libthai.x86_64 0:0.1.14-9.el7 will be installed ---> Package libtiff.x86_64 0:4.0.3-35.el7 will be installed --> Processing Dependency: libjbig.so.2.0()(64bit) for package: libtiff-4.0.3-35.el7.x86_64 ---> Package libunistring.x86_64 0:0.9.3-9.el7 will be installed ---> Package libxcb.x86_64 0:1.13-1.el7 will be installed --> Processing Dependency: libXau.so.6()(64bit) for package: libxcb-1.13-1.el7.x86_64 ---> Package libxcb-devel.x86_64 0:1.13-1.el7 will be installed --> Processing Dependency: pkgconfig(xau) >= 0.99.2 for package: libxcb-devel-1.13-1.el7.x86_64 ---> Package m4.x86_64 0:1.4.16-10.el7 will be installed ---> Package mallard-rng.noarch 0:1.0.2-1.el7 will be installed --> Processing Dependency: xml-common for package: mallard-rng-1.0.2-1.el7.noarch --> Processing Dependency: xml-common for package: mallard-rng-1.0.2-1.el7.noarch ---> Package mesa-libEGL-devel.x86_64 0:18.3.4-12.el7_9 will be installed --> Processing Dependency: mesa-khr-devel(x86-64) = 18.3.4-12.el7_9 for package: mesa-libEGL-devel-18.3.4-12.el7_9.x86_64 --> Processing Dependency: pkgconfig(xdamage) >= 1.1 for package: mesa-libEGL-devel-18.3.4-12.el7_9.x86_64 --> Processing Dependency: pkgconfig(libdrm) >= 2.4.75 for package: mesa-libEGL-devel-18.3.4-12.el7_9.x86_64 --> Processing Dependency: pkgconfig(xxf86vm) for package: mesa-libEGL-devel-18.3.4-12.el7_9.x86_64 --> Processing Dependency: libglvnd-devel(x86-64) for package: mesa-libEGL-devel-18.3.4-12.el7_9.x86_64 ---> Package mesa-libGL-devel.x86_64 0:18.3.4-12.el7_9 will be installed --> Processing Dependency: gl-manpages for package: mesa-libGL-devel-18.3.4-12.el7_9.x86_64 --> Processing Dependency: libglapi.so.0()(64bit) for package: mesa-libGL-devel-18.3.4-12.el7_9.x86_64 ---> Package perl-Data-Dumper.x86_64 0:2.145-3.el7 will be installed ---> Package perl-Font-TTF.noarch 0:1.02-3.el7 will be installed --> Processing Dependency: perl(IO::String) for package: perl-Font-TTF-1.02-3.el7.noarch ---> Package perl-Image-ExifTool.noarch 0:12.38-1.el7 will be installed ---> Package perl-Regexp-Assemble.noarch 0:0.35-11.el7 will be installed ---> Package perl-Test-Harness.noarch 0:3.28-3.el7 will be installed ---> Package perl-autodie.noarch 0:2.16-2.el7 will be installed ---> Package pixman.x86_64 0:0.34.0-1.el7 will be installed ---> Package pixman-devel.x86_64 0:0.34.0-1.el7 will be installed ---> Package po-debconf.noarch 0:1.0.20-5.el7 will be installed --> Processing Dependency: perl(Compress::Zlib) for package: po-debconf-1.0.20-5.el7.noarch --> Processing Dependency: perl(Debconf::AutoSelect) for package: po-debconf-1.0.20-5.el7.noarch --> Processing Dependency: perl(Debconf::Config) for package: po-debconf-1.0.20-5.el7.noarch --> Processing Dependency: perl(Debconf::Db) for package: po-debconf-1.0.20-5.el7.noarch --> Processing Dependency: perl(Debconf::Template::Transient) for package: po-debconf-1.0.20-5.el7.noarch --> Processing Dependency: perl(Mail::Box::Manager) for package: po-debconf-1.0.20-5.el7.noarch --> Processing Dependency: perl(Mail::Sendmail) for package: po-debconf-1.0.20-5.el7.noarch ---> Package polkit.x86_64 0:0.112-26.el7_9.1 will be installed --> Processing Dependency: polkit-pkla-compat for package: polkit-0.112-26.el7_9.1.x86_64 --> Processing Dependency: libmozjs-17.0.so(mozjs_17.0)(64bit) for package: polkit-0.112-26.el7_9.1.x86_64 --> Processing Dependency: libmozjs-17.0.so()(64bit) for package: polkit-0.112-26.el7_9.1.x86_64 ---> Package psmisc.x86_64 0:22.20-17.el7 will be installed ---> Package python3-html2text.noarch 0:2019.9.26-3.el7 will be installed --> Processing Dependency: python(abi) = 3.6 for package: python3-html2text-2019.9.26-3.el7.noarch --> Processing Dependency: /usr/bin/python3 for package: python3-html2text-2019.9.26-3.el7.noarch ---> Package xorg-x11-proto-devel.noarch 0:2018.4-1.el7 will be installed ---> Package yelp-xsl.noarch 0:3.28.0-1.el7 will be installed --> Running transaction check ---> Package avahi-libs.x86_64 0:0.6.31-20.el7 will be installed ---> Package debconf.noarch 0:1.5.79-1.el7 will be installed --> Processing Dependency: perl(CGI) for package: debconf-1.5.79-1.el7.noarch --> Processing Dependency: perl(Locale::gettext) for package: debconf-1.5.79-1.el7.noarch --> Processing Dependency: perl(Text::CharWidth) for package: debconf-1.5.79-1.el7.noarch --> Processing Dependency: perl(Text::Iconv) for package: debconf-1.5.79-1.el7.noarch --> Processing Dependency: perl(Text::WrapI18N) for package: debconf-1.5.79-1.el7.noarch ---> Package dejavu-fonts-common.noarch 0:2.33-6.el7 will be installed ---> Package dpkg.x86_64 0:1.18.25-10.el7 will be installed ---> Package expat-devel.x86_64 0:2.1.0-14.el7_9 will be installed ---> Package gl-manpages.noarch 0:1.1-7.20130122.el7 will be installed ---> Package graphite2.x86_64 0:1.3.10-1.el7_3 will be installed ---> Package graphite2-devel.x86_64 0:1.3.10-1.el7_3 will be installed ---> Package harfbuzz-icu.x86_64 0:1.7.5-2.el7 will be installed --> Processing Dependency: libicuuc.so.50()(64bit) for package: harfbuzz-icu-1.7.5-2.el7.x86_64 --> Processing Dependency: libicudata.so.50()(64bit) for package: harfbuzz-icu-1.7.5-2.el7.x86_64 ---> Package jbigkit-libs.x86_64 0:2.0-11.el7 will be installed ---> Package less.x86_64 0:458-9.el7 will be installed ---> Package libXau.x86_64 0:1.0.8-2.1.el7 will be installed ---> Package libXau-devel.x86_64 0:1.0.8-2.1.el7 will be installed ---> Package libXdamage-devel.x86_64 0:1.1.4-4.1.el7 will be installed ---> Package libXxf86vm-devel.x86_64 0:1.1.4-1.el7 will be installed --> Processing Dependency: libXxf86vm = 1.1.4-1.el7 for package: libXxf86vm-devel-1.1.4-1.el7.x86_64 --> Processing Dependency: libXxf86vm.so.1()(64bit) for package: libXxf86vm-devel-1.1.4-1.el7.x86_64 ---> Package libdrm-devel.x86_64 0:2.4.97-2.el7 will be installed --> Processing Dependency: libdrm = 2.4.97-2.el7 for package: libdrm-devel-2.4.97-2.el7.x86_64 --> Processing Dependency: libkms.so.1()(64bit) for package: libdrm-devel-2.4.97-2.el7.x86_64 --> Processing Dependency: libdrm_radeon.so.1()(64bit) for package: libdrm-devel-2.4.97-2.el7.x86_64 --> Processing Dependency: libdrm_nouveau.so.2()(64bit) for package: libdrm-devel-2.4.97-2.el7.x86_64 --> Processing Dependency: libdrm_intel.so.1()(64bit) for package: libdrm-devel-2.4.97-2.el7.x86_64 --> Processing Dependency: libdrm_amdgpu.so.1()(64bit) for package: libdrm-devel-2.4.97-2.el7.x86_64 --> Processing Dependency: libdrm.so.2()(64bit) for package: libdrm-devel-2.4.97-2.el7.x86_64 ---> Package libglvnd.x86_64 1:1.0.1-0.8.git5baa1e5.el7 will be installed ---> Package libglvnd-devel.x86_64 1:1.0.1-0.8.git5baa1e5.el7 will be installed --> Processing Dependency: libglvnd-opengl(x86-64) = 1:1.0.1-0.8.git5baa1e5.el7 for package: 1:libglvnd-devel-1.0.1-0.8.git5baa1e5.el7.x86_64 --> Processing Dependency: libglvnd-gles(x86-64) = 1:1.0.1-0.8.git5baa1e5.el7 for package: 1:libglvnd-devel-1.0.1-0.8.git5baa1e5.el7.x86_64 --> Processing Dependency: libglvnd-core-devel(x86-64) = 1:1.0.1-0.8.git5baa1e5.el7 for package: 1:libglvnd-devel-1.0.1-0.8.git5baa1e5.el7.x86_64 --> Processing Dependency: libOpenGL.so.0()(64bit) for package: 1:libglvnd-devel-1.0.1-0.8.git5baa1e5.el7.x86_64 --> Processing Dependency: libGLESv2.so.2()(64bit) for package: 1:libglvnd-devel-1.0.1-0.8.git5baa1e5.el7.x86_64 --> Processing Dependency: libGLESv1_CM.so.1()(64bit) for package: 1:libglvnd-devel-1.0.1-0.8.git5baa1e5.el7.x86_64 ---> Package libicu-devel.x86_64 0:50.2-4.el7_7 will be installed ---> Package libuuid-devel.x86_64 0:2.23.2-65.el7_9.1 will be installed ---> Package libxml2-python.x86_64 0:2.9.1-6.el7_9.6 will be installed ---> Package mesa-khr-devel.x86_64 0:18.3.4-12.el7_9 will be installed ---> Package mesa-libEGL.x86_64 0:18.3.4-12.el7_9 will be installed --> Processing Dependency: mesa-libgbm = 18.3.4-12.el7_9 for package: mesa-libEGL-18.3.4-12.el7_9.x86_64 --> Processing Dependency: libxshmfence.so.1()(64bit) for package: mesa-libEGL-18.3.4-12.el7_9.x86_64 --> Processing Dependency: libwayland-server.so.0()(64bit) for package: mesa-libEGL-18.3.4-12.el7_9.x86_64 --> Processing Dependency: libwayland-client.so.0()(64bit) for package: mesa-libEGL-18.3.4-12.el7_9.x86_64 --> Processing Dependency: libgbm.so.1()(64bit) for package: mesa-libEGL-18.3.4-12.el7_9.x86_64 ---> Package mesa-libGL.x86_64 0:18.3.4-12.el7_9 will be installed ---> Package mesa-libglapi.x86_64 0:18.3.4-12.el7_9 will be installed ---> Package mozjs17.x86_64 0:17.0.0-20.el7 will be installed ---> Package openssh-clients.x86_64 0:7.4p1-22.el7_9 will be installed --> Processing Dependency: openssh = 7.4p1-22.el7_9 for package: openssh-clients-7.4p1-22.el7_9.x86_64 --> Processing Dependency: fipscheck-lib(x86-64) >= 1.3.0 for package: openssh-clients-7.4p1-22.el7_9.x86_64 --> Processing Dependency: libfipscheck.so.1()(64bit) for package: openssh-clients-7.4p1-22.el7_9.x86_64 --> Processing Dependency: libedit.so.0()(64bit) for package: openssh-clients-7.4p1-22.el7_9.x86_64 ---> Package perl-Digest.noarch 0:1.17-245.el7 will be installed ---> Package perl-Digest-MD5.x86_64 0:2.52-3.el7 will be installed ---> Package perl-Digest-SHA.x86_64 1:5.85-4.el7 will be installed ---> Package perl-Digest-SHA1.x86_64 0:2.13-9.el7 will be installed ---> Package perl-Digest-SHA3.x86_64 0:0.24-1.el7 will be installed ---> Package perl-Error.noarch 1:0.17020-2.el7 will be installed ---> Package perl-Git.noarch 0:1.8.3.1-23.el7_8 will be installed ---> Package perl-IO-Compress.noarch 0:2.061-2.el7 will be installed --> Processing Dependency: perl(Compress::Raw::Zlib) >= 2.061 for package: perl-IO-Compress-2.061-2.el7.noarch --> Processing Dependency: perl(Compress::Raw::Bzip2) >= 2.061 for package: perl-IO-Compress-2.061-2.el7.noarch ---> Package perl-IO-String.noarch 0:1.08-19.el7 will be installed ---> Package perl-MIME-Lite.noarch 0:3.030-1.el7 will be installed --> Processing Dependency: perl(MIME::Types) >= 1.28 for package: perl-MIME-Lite-3.030-1.el7.noarch --> Processing Dependency: perl(Email::Date::Format) for package: perl-MIME-Lite-3.030-1.el7.noarch ---> Package perl-Mail-Box.noarch 0:2.120-2.el7 will be installed --> Processing Dependency: perl(Mail::Transport::Dbx) >= 0.04 for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(Devel::GlobalDestruction) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(Digest::HMAC_MD5) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(Email::Simple) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(File::FcntlLock) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(File::Remove) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(HTML::FormatText) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(HTML::TreeBuilder) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(IO::Lines) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(MIME::Entity) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(MIME::Parser) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(Mail::Address) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(Mail::Header) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(Mail::IMAPClient) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(Mail::Identity) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(Mail::Internet) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(Object::Realize::Later) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(Text::Autoformat) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(URI) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(User::Identity::Collection) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(User::Identity::Collection::Emails) for package: perl-Mail-Box-2.120-2.el7.noarch --> Processing Dependency: perl(User::Identity::Item) for package: perl-Mail-Box-2.120-2.el7.noarch ---> Package perl-Mail-Sendmail.noarch 0:0.79-21.el7 will be installed ---> Package perl-TermReadKey.x86_64 0:2.30-20.el7 will be installed ---> Package perl-Time-Piece.x86_64 0:1.20.1-299.el7_9 will be installed ---> Package perl-TimeDate.noarch 1:2.30-2.el7 will be installed ---> Package polkit-pkla-compat.x86_64 0:0.1-4.el7 will be installed ---> Package python3.x86_64 0:3.6.8-18.el7 will be installed --> Processing Dependency: python3-libs(x86-64) = 3.6.8-18.el7 for package: python3-3.6.8-18.el7.x86_64 --> Processing Dependency: python3-setuptools for package: python3-3.6.8-18.el7.x86_64 --> Processing Dependency: python3-pip for package: python3-3.6.8-18.el7.x86_64 --> Processing Dependency: libpython3.6m.so.1.0()(64bit) for package: python3-3.6.8-18.el7.x86_64 ---> Package rsync.x86_64 0:3.1.2-10.el7 will be installed ---> Package xml-common.noarch 0:0.6.3-39.el7 will be installed ---> Package xz-lzma-compat.x86_64 0:5.2.2-2.el7_9 will be installed --> Running transaction check ---> Package fipscheck-lib.x86_64 0:1.4.1-6.el7 will be installed --> Processing Dependency: /usr/bin/fipscheck for package: fipscheck-lib-1.4.1-6.el7.x86_64 ---> Package libXxf86vm.x86_64 0:1.1.4-1.el7 will be installed ---> Package libdrm.x86_64 0:2.4.97-2.el7 will be installed --> Processing Dependency: libpciaccess.so.0()(64bit) for package: libdrm-2.4.97-2.el7.x86_64 ---> Package libedit.x86_64 0:3.0-12.20121213cvs.el7 will be installed ---> Package libglvnd-core-devel.x86_64 1:1.0.1-0.8.git5baa1e5.el7 will be installed ---> Package libglvnd-gles.x86_64 1:1.0.1-0.8.git5baa1e5.el7 will be installed ---> Package libglvnd-opengl.x86_64 1:1.0.1-0.8.git5baa1e5.el7 will be installed ---> Package libicu.x86_64 0:50.2-4.el7_7 will be installed ---> Package libwayland-client.x86_64 0:1.15.0-1.el7 will be installed ---> Package libwayland-server.x86_64 0:1.15.0-1.el7 will be installed ---> Package libxshmfence.x86_64 0:1.2-1.el7 will be installed ---> Package mesa-libgbm.x86_64 0:18.3.4-12.el7_9 will be installed ---> Package openssh.x86_64 0:7.4p1-22.el7_9 will be installed ---> Package perl-CGI.noarch 0:3.63-4.el7 will be installed --> Processing Dependency: perl(FCGI) >= 0.67 for package: perl-CGI-3.63-4.el7.noarch ---> Package perl-Compress-Raw-Bzip2.x86_64 0:2.061-3.el7 will be installed ---> Package perl-Compress-Raw-Zlib.x86_64 1:2.061-4.el7 will be installed ---> Package perl-Devel-GlobalDestruction.noarch 0:0.12-1.el7 will be installed --> Processing Dependency: perl(Sub::Exporter::Progressive) for package: perl-Devel-GlobalDestruction-0.12-1.el7.noarch ---> Package perl-Digest-HMAC.noarch 0:1.03-5.el7 will be installed ---> Package perl-Email-Date-Format.noarch 0:1.002-15.el7 will be installed ---> Package perl-Email-Simple.noarch 0:2.214-1.el7 will be installed ---> Package perl-File-FcntlLock.x86_64 0:0.22-6.el7 will be installed ---> Package perl-File-Remove.noarch 0:1.52-6.el7 will be installed ---> Package perl-HTML-Format.noarch 0:2.10-7.el7 will be installed --> Processing Dependency: perl(Font::Metrics::TimesRoman) for package: perl-HTML-Format-2.10-7.el7.noarch --> Processing Dependency: perl(Font::Metrics::TimesItalic) for package: perl-HTML-Format-2.10-7.el7.noarch --> Processing Dependency: perl(Font::Metrics::TimesBoldItalic) for package: perl-HTML-Format-2.10-7.el7.noarch --> Processing Dependency: perl(Font::Metrics::TimesBold) for package: perl-HTML-Format-2.10-7.el7.noarch --> Processing Dependency: perl(Font::Metrics::HelveticaOblique) for package: perl-HTML-Format-2.10-7.el7.noarch --> Processing Dependency: perl(Font::Metrics::HelveticaBoldOblique) for package: perl-HTML-Format-2.10-7.el7.noarch --> Processing Dependency: perl(Font::Metrics::HelveticaBold) for package: perl-HTML-Format-2.10-7.el7.noarch --> Processing Dependency: perl(Font::Metrics::Helvetica) for package: perl-HTML-Format-2.10-7.el7.noarch --> Processing Dependency: perl(Font::Metrics::CourierOblique) for package: perl-HTML-Format-2.10-7.el7.noarch --> Processing Dependency: perl(Font::Metrics::CourierBoldOblique) for package: perl-HTML-Format-2.10-7.el7.noarch --> Processing Dependency: perl(Font::Metrics::CourierBold) for package: perl-HTML-Format-2.10-7.el7.noarch --> Processing Dependency: perl(Font::Metrics::Courier) for package: perl-HTML-Format-2.10-7.el7.noarch ---> Package perl-HTML-Tree.noarch 1:5.03-2.el7 will be installed --> Processing Dependency: perl(HTML::Tagset) >= 3.02 for package: 1:perl-HTML-Tree-5.03-2.el7.noarch --> Processing Dependency: perl(HTML::Parser) >= 3.46 for package: 1:perl-HTML-Tree-5.03-2.el7.noarch --> Processing Dependency: perl(LWP::UserAgent) for package: 1:perl-HTML-Tree-5.03-2.el7.noarch --> Processing Dependency: perl(HTML::Tagset) for package: 1:perl-HTML-Tree-5.03-2.el7.noarch --> Processing Dependency: perl(HTML::Entities) for package: 1:perl-HTML-Tree-5.03-2.el7.noarch ---> Package perl-IO-stringy.noarch 0:2.110-22.el7 will be installed ---> Package perl-MIME-Types.noarch 0:1.38-2.el7 will be installed ---> Package perl-MIME-tools.noarch 0:5.505-1.el7 will be installed --> Processing Dependency: perl(Convert::BinHex) for package: perl-MIME-tools-5.505-1.el7.noarch ---> Package perl-Mail-IMAPClient.noarch 0:3.37-1.el7 will be installed --> Processing Dependency: perl(Parse::RecDescent) for package: perl-Mail-IMAPClient-3.37-1.el7.noarch ---> Package perl-Mail-Transport-Dbx.x86_64 0:0.07-28.el7 will be installed ---> Package perl-MailTools.noarch 0:2.12-2.el7 will be installed --> Processing Dependency: perl(Net::SMTP::SSL) for package: perl-MailTools-2.12-2.el7.noarch ---> Package perl-Object-Realize-Later.noarch 0:0.19-6.el7 will be installed ---> Package perl-Text-Autoformat.noarch 0:1.669004-1.el7 will be installed --> Processing Dependency: perl(Text::Reform) for package: perl-Text-Autoformat-1.669004-1.el7.noarch ---> Package perl-Text-CharWidth.x86_64 0:0.04-18.el7 will be installed ---> Package perl-Text-Iconv.x86_64 0:1.7-18.el7 will be installed ---> Package perl-Text-WrapI18N.noarch 0:0.06-17.el7 will be installed ---> Package perl-URI.noarch 0:1.60-9.el7 will be installed --> Processing Dependency: perl(Business::ISBN) for package: perl-URI-1.60-9.el7.noarch ---> Package perl-User-Identity.noarch 0:0.96-1.el7 will be installed ---> Package perl-gettext.x86_64 0:1.05-28.el7 will be installed ---> Package python3-libs.x86_64 0:3.6.8-18.el7 will be installed --> Processing Dependency: libtirpc.so.1()(64bit) for package: python3-libs-3.6.8-18.el7.x86_64 ---> Package python3-pip.noarch 0:9.0.3-8.el7 will be installed ---> Package python3-setuptools.noarch 0:39.2.0-10.el7 will be installed --> Running transaction check ---> Package fipscheck.x86_64 0:1.4.1-6.el7 will be installed ---> Package libpciaccess.x86_64 0:0.14-1.el7 will be installed --> Processing Dependency: hwdata for package: libpciaccess-0.14-1.el7.x86_64 ---> Package libtirpc.x86_64 0:0.2.4-0.16.el7 will be installed ---> Package perl-Business-ISBN.noarch 0:2.06-2.el7 will be installed --> Processing Dependency: perl(Business::ISBN::Data) >= 20120719.001 for package: perl-Business-ISBN-2.06-2.el7.noarch ---> Package perl-Convert-BinHex.noarch 0:1.119-20.el7 will be installed ---> Package perl-FCGI.x86_64 1:0.74-8.el7 will be installed ---> Package perl-Font-AFM.noarch 0:1.20-13.el7 will be installed ---> Package perl-HTML-Parser.x86_64 0:3.71-4.el7 will be installed --> Processing Dependency: perl(HTTP::Headers) for package: perl-HTML-Parser-3.71-4.el7.x86_64 ---> Package perl-HTML-Tagset.noarch 0:3.20-15.el7 will be installed ---> Package perl-Net-SMTP-SSL.noarch 0:1.01-13.el7 will be installed --> Processing Dependency: perl(IO::Socket::SSL) for package: perl-Net-SMTP-SSL-1.01-13.el7.noarch ---> Package perl-Parse-RecDescent.noarch 0:1.967009-5.el7 will be installed ---> Package perl-Sub-Exporter-Progressive.noarch 0:0.001011-1.el7 will be installed --> Processing Dependency: perl(Sub::Exporter) for package: perl-Sub-Exporter-Progressive-0.001011-1.el7.noarch ---> Package perl-Text-Reform.noarch 0:1.20-9.el7 will be installed --> Processing Dependency: perl(TeX::Hyphen) for package: perl-Text-Reform-1.20-9.el7.noarch ---> Package perl-libwww-perl.noarch 0:6.05-2.el7 will be installed --> Processing Dependency: perl(WWW::RobotRules) >= 6 for package: perl-libwww-perl-6.05-2.el7.noarch --> Processing Dependency: perl(Net::HTTP) >= 6.04 for package: perl-libwww-perl-6.05-2.el7.noarch --> Processing Dependency: perl(LWP::MediaTypes) >= 6 for package: perl-libwww-perl-6.05-2.el7.noarch --> Processing Dependency: perl(HTTP::Negotiate) >= 6 for package: perl-libwww-perl-6.05-2.el7.noarch --> Processing Dependency: perl(HTTP::Date) >= 6 for package: perl-libwww-perl-6.05-2.el7.noarch --> Processing Dependency: perl(HTTP::Daemon) >= 6 for package: perl-libwww-perl-6.05-2.el7.noarch --> Processing Dependency: perl(HTTP::Cookies) >= 6 for package: perl-libwww-perl-6.05-2.el7.noarch --> Processing Dependency: perl(File::Listing) >= 6 for package: perl-libwww-perl-6.05-2.el7.noarch --> Processing Dependency: perl(Encode::Locale) for package: perl-libwww-perl-6.05-2.el7.noarch --> Running transaction check ---> Package hwdata.x86_64 0:0.252-9.7.el7 will be installed ---> Package perl-Business-ISBN-Data.noarch 0:20120719.001-2.el7 will be installed ---> Package perl-Encode-Locale.noarch 0:1.03-5.el7 will be installed ---> Package perl-File-Listing.noarch 0:6.04-7.el7 will be installed ---> Package perl-HTTP-Cookies.noarch 0:6.01-5.el7 will be installed ---> Package perl-HTTP-Daemon.noarch 0:6.01-8.el7 will be installed --> Processing Dependency: perl(IO::Socket::IP) for package: perl-HTTP-Daemon-6.01-8.el7.noarch ---> Package perl-HTTP-Date.noarch 0:6.02-8.el7 will be installed ---> Package perl-HTTP-Message.noarch 0:6.06-6.el7 will be installed --> Processing Dependency: perl(IO::HTML) for package: perl-HTTP-Message-6.06-6.el7.noarch ---> Package perl-HTTP-Negotiate.noarch 0:6.01-5.el7 will be installed ---> Package perl-IO-Socket-SSL.noarch 0:1.94-7.el7 will be installed --> Processing Dependency: perl-Net-SSLeay >= 1.55-5 for package: perl-IO-Socket-SSL-1.94-7.el7.noarch --> Processing Dependency: perl(Net::SSLeay) >= 1.21 for package: perl-IO-Socket-SSL-1.94-7.el7.noarch --> Processing Dependency: openssl >= 0.9.8 for package: perl-IO-Socket-SSL-1.94-7.el7.noarch --> Processing Dependency: perl(Net::SSLeay) for package: perl-IO-Socket-SSL-1.94-7.el7.noarch --> Processing Dependency: perl(Net::LibIDN) for package: perl-IO-Socket-SSL-1.94-7.el7.noarch --> Processing Dependency: perl(Mozilla::CA) for package: perl-IO-Socket-SSL-1.94-7.el7.noarch ---> Package perl-LWP-MediaTypes.noarch 0:6.02-2.el7 will be installed --> Processing Dependency: mailcap for package: perl-LWP-MediaTypes-6.02-2.el7.noarch ---> Package perl-Net-HTTP.noarch 0:6.06-2.el7 will be installed ---> Package perl-Sub-Exporter.noarch 0:0.986-2.el7 will be installed --> Processing Dependency: perl(Sub::Install) >= 0.92 for package: perl-Sub-Exporter-0.986-2.el7.noarch --> Processing Dependency: perl(Params::Util) >= 0.14 for package: perl-Sub-Exporter-0.986-2.el7.noarch --> Processing Dependency: perl(Data::OptList) >= 0.100 for package: perl-Sub-Exporter-0.986-2.el7.noarch --> Processing Dependency: perl(Params::Util) for package: perl-Sub-Exporter-0.986-2.el7.noarch --> Processing Dependency: perl(Package::Generator) for package: perl-Sub-Exporter-0.986-2.el7.noarch --> Processing Dependency: perl(Data::OptList) for package: perl-Sub-Exporter-0.986-2.el7.noarch ---> Package perl-TeX-Hyphen.noarch 0:1.01-1.el7 will be installed ---> Package perl-WWW-RobotRules.noarch 0:6.02-5.el7 will be installed --> Running transaction check ---> Package mailcap.noarch 0:2.1.41-2.el7 will be installed ---> Package openssl.x86_64 1:1.0.2k-25.el7_9 will be installed ---> Package perl-Data-OptList.noarch 0:0.107-9.el7 will be installed ---> Package perl-IO-HTML.noarch 0:1.00-2.el7 will be installed ---> Package perl-IO-Socket-IP.noarch 0:0.21-5.el7 will be installed ---> Package perl-Mozilla-CA.noarch 0:20130114-5.el7 will be installed ---> Package perl-Net-LibIDN.x86_64 0:0.12-15.el7 will be installed ---> Package perl-Net-SSLeay.x86_64 0:1.55-6.el7 will be installed ---> Package perl-Package-Generator.noarch 0:0.103-14.el7 will be installed ---> Package perl-Params-Util.x86_64 0:1.07-6.el7 will be installed ---> Package perl-Sub-Install.noarch 0:0.926-6.el7 will be installed --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: GConf2-devel x86_64 3.2.6-8.el7 base 110 k dh-autoreconf noarch 19-1.el7 epel 21 k glib2-devel x86_64 2.56.1-9.el7_9 updates 453 k gnome-common noarch 3.18.0-1.el7 base 130 k gnome-icon-theme-devel noarch 3.12.0-1.el7 base 16 k gstreamer1-devel x86_64 1.10.4-2.el7 base 442 k gtk2-devel x86_64 2.24.31-1.el7 base 3.0 M intltool noarch 0.50.2-7.el7 base 59 k libappindicator-devel x86_64 12.10.0-13.el7 base 16 k libnotify-devel x86_64 0.7.7-1.el7 base 31 k libxml2-devel x86_64 2.9.1-6.el7_9.6 updates 1.1 M unique-devel x86_64 1.1.6-10.el7 epel 28 k Installing for dependencies: GConf2 x86_64 3.2.6-8.el7 base 1.0 M atk x86_64 2.28.1-2.el7 base 263 k atk-devel x86_64 2.28.1-2.el7 base 184 k autoconf noarch 2.69-11.el7 base 701 k autoconf-archive noarch 2017.03.21-1.el7 base 612 k automake noarch 1.13.4-3.el7 base 679 k avahi-libs x86_64 0.6.31-20.el7 base 62 k cairo x86_64 1.15.12-4.el7 base 741 k cairo-devel x86_64 1.15.12-4.el7 base 267 k cdbs noarch 0.4.150-3.el7 epel 58 k check x86_64 0.9.9-5.el7 base 102 k check-devel x86_64 0.9.9-5.el7 base 27 k cups-libs x86_64 1:1.6.3-51.el7 base 359 k dbus-devel x86_64 1:1.10.24-15.el7 base 54 k dbus-glib x86_64 0.100-7.el7 base 102 k dbus-glib-devel x86_64 0.100-7.el7 base 53 k debconf noarch 1.5.79-1.el7 epel 189 k debhelper noarch 11.4-2.el7 epel 939 k dejavu-fonts-common noarch 2.33-6.el7 base 64 k dejavu-sans-fonts noarch 2.33-6.el7 base 1.4 M dpkg x86_64 1.18.25-10.el7 epel 1.3 M dpkg-dev noarch 1.18.25-10.el7 epel 706 k dpkg-perl noarch 1.18.25-10.el7 epel 248 k expat-devel x86_64 2.1.0-14.el7_9 updates 58 k fipscheck x86_64 1.4.1-6.el7 base 21 k fipscheck-lib x86_64 1.4.1-6.el7 base 11 k fontconfig x86_64 2.13.0-4.3.el7 base 254 k fontconfig-devel x86_64 2.13.0-4.3.el7 base 138 k fontpackages-filesystem noarch 1.44-8.el7 base 9.9 k freetype x86_64 2.8-14.el7_9.1 updates 380 k freetype-devel x86_64 2.8-14.el7_9.1 updates 447 k fribidi x86_64 1.0.2-1.el7_7.1 base 79 k fribidi-devel x86_64 1.0.2-1.el7_7.1 base 25 k gdk-pixbuf2 x86_64 2.36.12-3.el7 base 570 k gdk-pixbuf2-devel x86_64 2.36.12-3.el7 base 215 k gettext x86_64 0.19.8.1-3.el7 base 1.0 M gettext-common-devel noarch 0.19.8.1-3.el7 base 410 k gettext-devel x86_64 0.19.8.1-3.el7 base 320 k gettext-libs x86_64 0.19.8.1-3.el7 base 502 k git x86_64 1.8.3.1-23.el7_8 base 4.4 M gl-manpages noarch 1.1-7.20130122.el7 base 994 k gnome-icon-theme noarch 3.12.0-1.el7 base 9.7 M graphite2 x86_64 1.3.10-1.el7_3 base 115 k graphite2-devel x86_64 1.3.10-1.el7_3 base 40 k gstreamer1 x86_64 1.10.4-2.el7 base 1.2 M gtk-update-icon-cache x86_64 3.22.30-8.el7_9 updates 27 k gtk2 x86_64 2.24.31-1.el7 base 3.4 M harfbuzz x86_64 1.7.5-2.el7 base 267 k harfbuzz-devel x86_64 1.7.5-2.el7 base 167 k harfbuzz-icu x86_64 1.7.5-2.el7 base 12 k hicolor-icon-theme noarch 0.12-7.el7 base 42 k hwdata x86_64 0.252-9.7.el7 base 2.5 M itstool noarch 2.0.2-1.el7 base 35 k jasper-libs x86_64 1.900.1-33.el7 base 150 k jbigkit-libs x86_64 2.0-11.el7 base 46 k less x86_64 458-9.el7 base 120 k libX11 x86_64 1.6.7-4.el7_9 updates 607 k libX11-common noarch 1.6.7-4.el7_9 updates 164 k libX11-devel x86_64 1.6.7-4.el7_9 updates 981 k libXau x86_64 1.0.8-2.1.el7 base 29 k libXau-devel x86_64 1.0.8-2.1.el7 base 14 k libXcomposite x86_64 0.4.4-4.1.el7 base 22 k libXcomposite-devel x86_64 0.4.4-4.1.el7 base 16 k libXcursor x86_64 1.1.15-1.el7 base 30 k libXcursor-devel x86_64 1.1.15-1.el7 base 24 k libXdamage x86_64 1.1.4-4.1.el7 base 20 k libXdamage-devel x86_64 1.1.4-4.1.el7 base 9.7 k libXext x86_64 1.3.3-3.el7 base 39 k libXext-devel x86_64 1.3.3-3.el7 base 75 k libXfixes x86_64 5.0.3-1.el7 base 18 k libXfixes-devel x86_64 5.0.3-1.el7 base 13 k libXft x86_64 2.3.2-2.el7 base 58 k libXft-devel x86_64 2.3.2-2.el7 base 19 k libXi x86_64 1.7.9-1.el7 base 40 k libXi-devel x86_64 1.7.9-1.el7 base 105 k libXinerama x86_64 1.1.3-2.1.el7 base 14 k libXinerama-devel x86_64 1.1.3-2.1.el7 base 13 k libXrandr x86_64 1.5.1-2.el7 base 27 k libXrandr-devel x86_64 1.5.1-2.el7 base 21 k libXrender x86_64 0.9.10-1.el7 base 26 k libXrender-devel x86_64 0.9.10-1.el7 base 17 k libXxf86vm x86_64 1.1.4-1.el7 base 18 k libXxf86vm-devel x86_64 1.1.4-1.el7 base 18 k libappindicator x86_64 12.10.0-13.el7 base 37 k libcroco x86_64 0.6.12-6.el7_9 updates 105 k libdbusmenu x86_64 16.04.0-4.el7 base 132 k libdbusmenu-devel x86_64 16.04.0-4.el7 base 28 k libdbusmenu-gtk2 x86_64 16.04.0-4.el7 base 34 k libdrm x86_64 2.4.97-2.el7 base 151 k libdrm-devel x86_64 2.4.97-2.el7 base 143 k libedit x86_64 3.0-12.20121213cvs.el7 base 92 k libglvnd x86_64 1:1.0.1-0.8.git5baa1e5.el7 base 89 k libglvnd-core-devel x86_64 1:1.0.1-0.8.git5baa1e5.el7 base 20 k libglvnd-devel x86_64 1:1.0.1-0.8.git5baa1e5.el7 base 11 k libglvnd-egl x86_64 1:1.0.1-0.8.git5baa1e5.el7 base 44 k libglvnd-gles x86_64 1:1.0.1-0.8.git5baa1e5.el7 base 34 k libglvnd-glx x86_64 1:1.0.1-0.8.git5baa1e5.el7 base 125 k libglvnd-opengl x86_64 1:1.0.1-0.8.git5baa1e5.el7 base 43 k libicu x86_64 50.2-4.el7_7 base 6.9 M libicu-devel x86_64 50.2-4.el7_7 base 703 k libindicator x86_64 12.10.1-6.el7 base 63 k libjpeg-turbo x86_64 1.2.90-8.el7 base 135 k libnotify x86_64 0.7.7-1.el7 base 39 k libpciaccess x86_64 0.14-1.el7 base 26 k libpng x86_64 2:1.5.13-8.el7 base 213 k libpng-devel x86_64 2:1.5.13-8.el7 base 122 k libthai x86_64 0.1.14-9.el7 base 187 k libtiff x86_64 4.0.3-35.el7 base 172 k libtirpc x86_64 0.2.4-0.16.el7 base 89 k libtool x86_64 2.4.2-22.el7_3 base 588 k libunistring x86_64 0.9.3-9.el7 base 293 k libuuid-devel x86_64 2.23.2-65.el7_9.1 updates 93 k libwayland-client x86_64 1.15.0-1.el7 base 33 k libwayland-server x86_64 1.15.0-1.el7 base 39 k libxcb x86_64 1.13-1.el7 base 214 k libxcb-devel x86_64 1.13-1.el7 base 1.1 M libxml2-python x86_64 2.9.1-6.el7_9.6 updates 247 k libxshmfence x86_64 1.2-1.el7 base 7.2 k m4 x86_64 1.4.16-10.el7 base 256 k mailcap noarch 2.1.41-2.el7 base 31 k mallard-rng noarch 1.0.2-1.el7 base 14 k mesa-khr-devel x86_64 18.3.4-12.el7_9 updates 20 k mesa-libEGL x86_64 18.3.4-12.el7_9 updates 110 k mesa-libEGL-devel x86_64 18.3.4-12.el7_9 updates 33 k mesa-libGL x86_64 18.3.4-12.el7_9 updates 166 k mesa-libGL-devel x86_64 18.3.4-12.el7_9 updates 164 k mesa-libgbm x86_64 18.3.4-12.el7_9 updates 39 k mesa-libglapi x86_64 18.3.4-12.el7_9 updates 46 k mozjs17 x86_64 17.0.0-20.el7 base 1.4 M openssh x86_64 7.4p1-22.el7_9 updates 510 k openssh-clients x86_64 7.4p1-22.el7_9 updates 655 k openssl x86_64 1:1.0.2k-25.el7_9 updates 494 k pango x86_64 1.42.4-4.el7_7 base 280 k pango-devel x86_64 1.42.4-4.el7_7 base 320 k pcre-devel x86_64 8.32-17.el7 base 480 k perl-Business-ISBN noarch 2.06-2.el7 base 25 k perl-Business-ISBN-Data noarch 20120719.001-2.el7 base 24 k perl-CGI noarch 3.63-4.el7 base 250 k perl-Compress-Raw-Bzip2 x86_64 2.061-3.el7 base 32 k perl-Compress-Raw-Zlib x86_64 1:2.061-4.el7 base 57 k perl-Convert-BinHex noarch 1.119-20.el7 epel 44 k perl-Data-Dumper x86_64 2.145-3.el7 base 47 k perl-Data-OptList noarch 0.107-9.el7 base 23 k perl-Devel-GlobalDestruction noarch 0.12-1.el7 epel 18 k perl-Digest noarch 1.17-245.el7 base 23 k perl-Digest-HMAC noarch 1.03-5.el7 base 16 k perl-Digest-MD5 x86_64 2.52-3.el7 base 30 k perl-Digest-SHA x86_64 1:5.85-4.el7 base 58 k perl-Digest-SHA1 x86_64 2.13-9.el7 base 50 k perl-Digest-SHA3 x86_64 0.24-1.el7 epel 32 k perl-Email-Date-Format noarch 1.002-15.el7 epel 17 k perl-Email-Simple noarch 2.214-1.el7 epel 36 k perl-Encode-Locale noarch 1.03-5.el7 base 16 k perl-Error noarch 1:0.17020-2.el7 base 32 k perl-FCGI x86_64 1:0.74-8.el7 base 42 k perl-File-FcntlLock x86_64 0.22-6.el7 epel 41 k perl-File-Listing noarch 6.04-7.el7 base 13 k perl-File-Remove noarch 1.52-6.el7 base 26 k perl-Font-AFM noarch 1.20-13.el7 base 19 k perl-Font-TTF noarch 1.02-3.el7 base 358 k perl-Git noarch 1.8.3.1-23.el7_8 base 56 k perl-HTML-Format noarch 2.10-7.el7 base 51 k perl-HTML-Parser x86_64 3.71-4.el7 base 115 k perl-HTML-Tagset noarch 3.20-15.el7 base 18 k perl-HTML-Tree noarch 1:5.03-2.el7 base 218 k perl-HTTP-Cookies noarch 6.01-5.el7 base 26 k perl-HTTP-Daemon noarch 6.01-8.el7 base 21 k perl-HTTP-Date noarch 6.02-8.el7 base 14 k perl-HTTP-Message noarch 6.06-6.el7 base 82 k perl-HTTP-Negotiate noarch 6.01-5.el7 base 17 k perl-IO-Compress noarch 2.061-2.el7 base 260 k perl-IO-HTML noarch 1.00-2.el7 base 23 k perl-IO-Socket-IP noarch 0.21-5.el7 base 36 k perl-IO-Socket-SSL noarch 1.94-7.el7 base 115 k perl-IO-String noarch 1.08-19.el7 base 16 k perl-IO-stringy noarch 2.110-22.el7 base 71 k perl-Image-ExifTool noarch 12.38-1.el7 epel 3.3 M perl-LWP-MediaTypes noarch 6.02-2.el7 base 24 k perl-MIME-Lite noarch 3.030-1.el7 epel 96 k perl-MIME-Types noarch 1.38-2.el7 epel 38 k perl-MIME-tools noarch 5.505-1.el7 epel 256 k perl-Mail-Box noarch 2.120-2.el7 epel 1.1 M perl-Mail-IMAPClient noarch 3.37-1.el7 epel 221 k perl-Mail-Sendmail noarch 0.79-21.el7 epel 29 k perl-Mail-Transport-Dbx x86_64 0.07-28.el7 epel 41 k perl-MailTools noarch 2.12-2.el7 base 108 k perl-Mozilla-CA noarch 20130114-5.el7 base 11 k perl-Net-HTTP noarch 6.06-2.el7 base 29 k perl-Net-LibIDN x86_64 0.12-15.el7 base 28 k perl-Net-SMTP-SSL noarch 1.01-13.el7 base 9.1 k perl-Net-SSLeay x86_64 1.55-6.el7 base 285 k perl-Object-Realize-Later noarch 0.19-6.el7 epel 21 k perl-Package-Generator noarch 0.103-14.el7 base 23 k perl-Params-Util x86_64 1.07-6.el7 base 38 k perl-Parse-RecDescent noarch 1.967009-5.el7 base 203 k perl-Regexp-Assemble noarch 0.35-11.el7 epel 82 k perl-Sub-Exporter noarch 0.986-2.el7 base 70 k perl-Sub-Exporter-Progressive noarch 0.001011-1.el7 epel 13 k perl-Sub-Install noarch 0.926-6.el7 base 21 k perl-TeX-Hyphen noarch 1.01-1.el7 epel 35 k perl-TermReadKey x86_64 2.30-20.el7 base 31 k perl-Test-Harness noarch 3.28-3.el7 base 302 k perl-Text-Autoformat noarch 1.669004-1.el7 epel 37 k perl-Text-CharWidth x86_64 0.04-18.el7 base 15 k perl-Text-Iconv x86_64 1.7-18.el7 base 23 k perl-Text-Reform noarch 1.20-9.el7 epel 43 k perl-Text-WrapI18N noarch 0.06-17.el7 base 12 k perl-Time-Piece x86_64 1.20.1-299.el7_9 updates 70 k perl-TimeDate noarch 1:2.30-2.el7 base 52 k perl-URI noarch 1.60-9.el7 base 106 k perl-User-Identity noarch 0.96-1.el7 epel 88 k perl-WWW-RobotRules noarch 6.02-5.el7 base 18 k perl-XML-Parser x86_64 2.41-10.el7 base 223 k perl-autodie noarch 2.16-2.el7 base 77 k perl-gettext x86_64 1.05-28.el7 base 21 k perl-libwww-perl noarch 6.05-2.el7 base 205 k pixman x86_64 0.34.0-1.el7 base 248 k pixman-devel x86_64 0.34.0-1.el7 base 20 k po-debconf noarch 1.0.20-5.el7 epel 147 k polkit x86_64 0.112-26.el7_9.1 updates 170 k polkit-pkla-compat x86_64 0.1-4.el7 base 39 k psmisc x86_64 22.20-17.el7 base 141 k python x86_64 2.7.5-92.el7_9 updates 96 k python3 x86_64 3.6.8-18.el7 updates 70 k python3-html2text noarch 2019.9.26-3.el7 epel 58 k python3-libs x86_64 3.6.8-18.el7 updates 6.9 M python3-pip noarch 9.0.3-8.el7 base 1.6 M python3-setuptools noarch 39.2.0-10.el7 base 629 k rsync x86_64 3.1.2-10.el7 base 404 k unique x86_64 1.1.6-10.el7 epel 55 k xml-common noarch 0.6.3-39.el7 base 26 k xorg-x11-proto-devel noarch 2018.4-1.el7 base 280 k xz-devel x86_64 5.2.2-2.el7_9 updates 46 k xz-lzma-compat x86_64 5.2.2-2.el7_9 updates 18 k yelp-tools noarch 3.28.0-1.el7 base 33 k yelp-xsl noarch 3.28.0-1.el7 base 204 k zlib-devel x86_64 1.2.7-20.el7_9 updates 50 k Transaction Summary ================================================================================ Install 12 Packages (+237 Dependent packages) Total download size: 83 M Installed size: 310 M Downloading packages: (1/249): GConf2-devel-3.2.6-8.el7.x86_64.rpm | 110 kB 00:00 (2/249): atk-2.28.1-2.el7.x86_64.rpm | 263 kB 00:00 (3/249): GConf2-3.2.6-8.el7.x86_64.rpm | 1.0 MB 00:00 (4/249): atk-devel-2.28.1-2.el7.x86_64.rpm | 184 kB 00:00 (5/249): autoconf-2.69-11.el7.noarch.rpm | 701 kB 00:00 (6/249): automake-1.13.4-3.el7.noarch.rpm | 679 kB 00:00 (7/249): autoconf-archive-2017.03.21-1.el7.noarch.rpm | 612 kB 00:00 (8/249): avahi-libs-0.6.31-20.el7.x86_64.rpm | 62 kB 00:00 (9/249): cairo-1.15.12-4.el7.x86_64.rpm | 741 kB 00:00 (10/249): cairo-devel-1.15.12-4.el7.x86_64.rpm | 267 kB 00:00 (11/249): check-0.9.9-5.el7.x86_64.rpm | 102 kB 00:00 (12/249): check-devel-0.9.9-5.el7.x86_64.rpm | 27 kB 00:00 (13/249): cups-libs-1.6.3-51.el7.x86_64.rpm | 359 kB 00:00 (14/249): dbus-devel-1.10.24-15.el7.x86_64.rpm | 54 kB 00:00 (15/249): dbus-glib-0.100-7.el7.x86_64.rpm | 102 kB 00:00 (16/249): dbus-glib-devel-0.100-7.el7.x86_64.rpm | 53 kB 00:00 (17/249): dejavu-fonts-common-2.33-6.el7.noarch.rpm | 64 kB 00:00 (18/249): cdbs-0.4.150-3.el7.noarch.rpm | 58 kB 00:00 (19/249): dh-autoreconf-19-1.el7.noarch.rpm | 21 kB 00:00 (20/249): dejavu-sans-fonts-2.33-6.el7.noarch.rpm | 1.4 MB 00:00 (21/249): dpkg-dev-1.18.25-10.el7.noarch.rpm | 706 kB 00:00 (22/249): dpkg-perl-1.18.25-10.el7.noarch.rpm | 248 kB 00:00 (23/249): fipscheck-1.4.1-6.el7.x86_64.rpm | 21 kB 00:00 (24/249): fipscheck-lib-1.4.1-6.el7.x86_64.rpm | 11 kB 00:00 (25/249): dpkg-1.18.25-10.el7.x86_64.rpm | 1.3 MB 00:00 (26/249): fontconfig-devel-2.13.0-4.3.el7.x86_64.rpm | 138 kB 00:00 (27/249): fontconfig-2.13.0-4.3.el7.x86_64.rpm | 254 kB 00:00 (28/249): fontpackages-filesystem-1.44-8.el7.noarch.rpm | 9.9 kB 00:00 (29/249): debconf-1.5.79-1.el7.noarch.rpm | 189 kB 00:00 (30/249): expat-devel-2.1.0-14.el7_9.x86_64.rpm | 58 kB 00:00 (31/249): debhelper-11.4-2.el7.noarch.rpm | 939 kB 00:00 (32/249): fribidi-1.0.2-1.el7_7.1.x86_64.rpm | 79 kB 00:00 (33/249): gdk-pixbuf2-2.36.12-3.el7.x86_64.rpm | 570 kB 00:00 (34/249): gdk-pixbuf2-devel-2.36.12-3.el7.x86_64.rpm | 215 kB 00:00 (35/249): fribidi-devel-1.0.2-1.el7_7.1.x86_64.rpm | 25 kB 00:00 (36/249): freetype-devel-2.8-14.el7_9.1.x86_64.rpm | 447 kB 00:00 (37/249): gettext-0.19.8.1-3.el7.x86_64.rpm | 1.0 MB 00:00 (38/249): gettext-devel-0.19.8.1-3.el7.x86_64.rpm | 320 kB 00:00 (39/249): freetype-2.8-14.el7_9.1.x86_64.rpm | 380 kB 00:00 (40/249): gettext-libs-0.19.8.1-3.el7.x86_64.rpm | 502 kB 00:00 (41/249): gettext-common-devel-0.19.8.1-3.el7.noarch.rpm | 410 kB 00:00 (42/249): git-1.8.3.1-23.el7_8.x86_64.rpm | 4.4 MB 00:00 (43/249): glib2-devel-2.56.1-9.el7_9.x86_64.rpm | 453 kB 00:00 (44/249): gl-manpages-1.1-7.20130122.el7.noarch.rpm | 994 kB 00:00 (45/249): gnome-common-3.18.0-1.el7.noarch.rpm | 130 kB 00:00 (46/249): gnome-icon-theme-devel-3.12.0-1.el7.noarch.rpm | 16 kB 00:00 (47/249): graphite2-1.3.10-1.el7_3.x86_64.rpm | 115 kB 00:00 (48/249): graphite2-devel-1.3.10-1.el7_3.x86_64.rpm | 40 kB 00:00 (49/249): gstreamer1-1.10.4-2.el7.x86_64.rpm | 1.2 MB 00:00 (50/249): gstreamer1-devel-1.10.4-2.el7.x86_64.rpm | 442 kB 00:00 (51/249): gtk-update-icon-cache-3.22.30-8.el7_9.x86_64.rpm | 27 kB 00:00 (52/249): gnome-icon-theme-3.12.0-1.el7.noarch.rpm | 9.7 MB 00:00 (53/249): gtk2-2.24.31-1.el7.x86_64.rpm | 3.4 MB 00:00 (54/249): gtk2-devel-2.24.31-1.el7.x86_64.rpm | 3.0 MB 00:00 (55/249): harfbuzz-1.7.5-2.el7.x86_64.rpm | 267 kB 00:00 (56/249): harfbuzz-devel-1.7.5-2.el7.x86_64.rpm | 167 kB 00:00 (57/249): harfbuzz-icu-1.7.5-2.el7.x86_64.rpm | 12 kB 00:00 (58/249): hicolor-icon-theme-0.12-7.el7.noarch.rpm | 42 kB 00:00 (59/249): intltool-0.50.2-7.el7.noarch.rpm | 59 kB 00:00 (60/249): hwdata-0.252-9.7.el7.x86_64.rpm | 2.5 MB 00:00 (61/249): itstool-2.0.2-1.el7.noarch.rpm | 35 kB 00:00 (62/249): jasper-libs-1.900.1-33.el7.x86_64.rpm | 150 kB 00:00 (63/249): jbigkit-libs-2.0-11.el7.x86_64.rpm | 46 kB 00:00 (64/249): less-458-9.el7.x86_64.rpm | 120 kB 00:00 (65/249): libX11-1.6.7-4.el7_9.x86_64.rpm | 607 kB 00:00 (66/249): libXau-1.0.8-2.1.el7.x86_64.rpm | 29 kB 00:00 (67/249): libXcomposite-0.4.4-4.1.el7.x86_64.rpm | 22 kB 00:00 (68/249): libX11-devel-1.6.7-4.el7_9.x86_64.rpm | 981 kB 00:00 (69/249): libXcomposite-devel-0.4.4-4.1.el7.x86_64.rpm | 16 kB 00:00 (70/249): libXcursor-1.1.15-1.el7.x86_64.rpm | 30 kB 00:00 (71/249): libXau-devel-1.0.8-2.1.el7.x86_64.rpm | 14 kB 00:00 (72/249): libXcursor-devel-1.1.15-1.el7.x86_64.rpm | 24 kB 00:00 (73/249): libX11-common-1.6.7-4.el7_9.noarch.rpm | 164 kB 00:00 (74/249): libXdamage-1.1.4-4.1.el7.x86_64.rpm | 20 kB 00:00 (75/249): libXdamage-devel-1.1.4-4.1.el7.x86_64.rpm | 9.7 kB 00:00 (76/249): libXext-devel-1.3.3-3.el7.x86_64.rpm | 75 kB 00:00 (77/249): libXext-1.3.3-3.el7.x86_64.rpm | 39 kB 00:00 (78/249): libXfixes-5.0.3-1.el7.x86_64.rpm | 18 kB 00:00 (79/249): libXfixes-devel-5.0.3-1.el7.x86_64.rpm | 13 kB 00:00 (80/249): libXft-2.3.2-2.el7.x86_64.rpm | 58 kB 00:00 (81/249): libXi-1.7.9-1.el7.x86_64.rpm | 40 kB 00:00 (82/249): libXft-devel-2.3.2-2.el7.x86_64.rpm | 19 kB 00:00 (83/249): libXi-devel-1.7.9-1.el7.x86_64.rpm | 105 kB 00:00 (84/249): libXinerama-1.1.3-2.1.el7.x86_64.rpm | 14 kB 00:00 (85/249): libXinerama-devel-1.1.3-2.1.el7.x86_64.rpm | 13 kB 00:00 (86/249): libXrandr-1.5.1-2.el7.x86_64.rpm | 27 kB 00:00 (87/249): libXrandr-devel-1.5.1-2.el7.x86_64.rpm | 21 kB 00:00 (88/249): libXrender-devel-0.9.10-1.el7.x86_64.rpm | 17 kB 00:00 (89/249): libXrender-0.9.10-1.el7.x86_64.rpm | 26 kB 00:00 (90/249): libXxf86vm-1.1.4-1.el7.x86_64.rpm | 18 kB 00:00 (91/249): libXxf86vm-devel-1.1.4-1.el7.x86_64.rpm | 18 kB 00:00 (92/249): libappindicator-12.10.0-13.el7.x86_64.rpm | 37 kB 00:00 (93/249): libappindicator-devel-12.10.0-13.el7.x86_64.rpm | 16 kB 00:00 (94/249): libdbusmenu-16.04.0-4.el7.x86_64.rpm | 132 kB 00:00 (95/249): libcroco-0.6.12-6.el7_9.x86_64.rpm | 105 kB 00:00 (96/249): libdbusmenu-devel-16.04.0-4.el7.x86_64.rpm | 28 kB 00:00 (97/249): libdbusmenu-gtk2-16.04.0-4.el7.x86_64.rpm | 34 kB 00:00 (98/249): libdrm-devel-2.4.97-2.el7.x86_64.rpm | 143 kB 00:00 (99/249): libedit-3.0-12.20121213cvs.el7.x86_64.rpm | 92 kB 00:00 (100/249): libdrm-2.4.97-2.el7.x86_64.rpm | 151 kB 00:00 (101/249): libglvnd-1.0.1-0.8.git5baa1e5.el7.x86_64.rpm | 89 kB 00:00 (102/249): libglvnd-core-devel-1.0.1-0.8.git5baa1e5.el7.x8 | 20 kB 00:00 (103/249): libglvnd-devel-1.0.1-0.8.git5baa1e5.el7.x86_64. | 11 kB 00:00 (104/249): libglvnd-egl-1.0.1-0.8.git5baa1e5.el7.x86_64.rp | 44 kB 00:00 (105/249): libglvnd-gles-1.0.1-0.8.git5baa1e5.el7.x86_64.r | 34 kB 00:00 (106/249): libglvnd-opengl-1.0.1-0.8.git5baa1e5.el7.x86_64 | 43 kB 00:00 (107/249): libglvnd-glx-1.0.1-0.8.git5baa1e5.el7.x86_64.rp | 125 kB 00:00 (108/249): libicu-devel-50.2-4.el7_7.x86_64.rpm | 703 kB 00:00 (109/249): libindicator-12.10.1-6.el7.x86_64.rpm | 63 kB 00:00 (110/249): libicu-50.2-4.el7_7.x86_64.rpm | 6.9 MB 00:00 (111/249): libjpeg-turbo-1.2.90-8.el7.x86_64.rpm | 135 kB 00:00 (112/249): libnotify-0.7.7-1.el7.x86_64.rpm | 39 kB 00:00 (113/249): libnotify-devel-0.7.7-1.el7.x86_64.rpm | 31 kB 00:00 (114/249): libpciaccess-0.14-1.el7.x86_64.rpm | 26 kB 00:00 (115/249): libpng-1.5.13-8.el7.x86_64.rpm | 213 kB 00:00 (116/249): libpng-devel-1.5.13-8.el7.x86_64.rpm | 122 kB 00:00 (117/249): libthai-0.1.14-9.el7.x86_64.rpm | 187 kB 00:00 (118/249): libtiff-4.0.3-35.el7.x86_64.rpm | 172 kB 00:00 (119/249): libtirpc-0.2.4-0.16.el7.x86_64.rpm | 89 kB 00:00 (120/249): libunistring-0.9.3-9.el7.x86_64.rpm | 293 kB 00:00 (121/249): libtool-2.4.2-22.el7_3.x86_64.rpm | 588 kB 00:00 (122/249): libwayland-client-1.15.0-1.el7.x86_64.rpm | 33 kB 00:00 (123/249): libwayland-server-1.15.0-1.el7.x86_64.rpm | 39 kB 00:00 (124/249): libuuid-devel-2.23.2-65.el7_9.1.x86_64.rpm | 93 kB 00:00 (125/249): libxcb-1.13-1.el7.x86_64.rpm | 214 kB 00:00 (126/249): libxcb-devel-1.13-1.el7.x86_64.rpm | 1.1 MB 00:00 (127/249): libxshmfence-1.2-1.el7.x86_64.rpm | 7.2 kB 00:00 (128/249): m4-1.4.16-10.el7.x86_64.rpm | 256 kB 00:00 (129/249): libxml2-python-2.9.1-6.el7_9.6.x86_64.rpm | 247 kB 00:00 (130/249): mailcap-2.1.41-2.el7.noarch.rpm | 31 kB 00:00 (131/249): mallard-rng-1.0.2-1.el7.noarch.rpm | 14 kB 00:00 (132/249): mesa-khr-devel-18.3.4-12.el7_9.x86_64.rpm | 20 kB 00:00 (133/249): mesa-libEGL-18.3.4-12.el7_9.x86_64.rpm | 110 kB 00:00 (134/249): mesa-libEGL-devel-18.3.4-12.el7_9.x86_64.rpm | 33 kB 00:00 (135/249): mesa-libGL-18.3.4-12.el7_9.x86_64.rpm | 166 kB 00:00 (136/249): mesa-libGL-devel-18.3.4-12.el7_9.x86_64.rpm | 164 kB 00:00 (137/249): mesa-libgbm-18.3.4-12.el7_9.x86_64.rpm | 39 kB 00:00 (138/249): libxml2-devel-2.9.1-6.el7_9.6.x86_64.rpm | 1.1 MB 00:00 (139/249): mesa-libglapi-18.3.4-12.el7_9.x86_64.rpm | 46 kB 00:00 (140/249): openssh-7.4p1-22.el7_9.x86_64.rpm | 510 kB 00:00 (141/249): mozjs17-17.0.0-20.el7.x86_64.rpm | 1.4 MB 00:00 (142/249): openssl-1.0.2k-25.el7_9.x86_64.rpm | 494 kB 00:00 (143/249): pango-devel-1.42.4-4.el7_7.x86_64.rpm | 320 kB 00:00 (144/249): openssh-clients-7.4p1-22.el7_9.x86_64.rpm | 655 kB 00:00 (145/249): pcre-devel-8.32-17.el7.x86_64.rpm | 480 kB 00:00 (146/249): perl-Business-ISBN-2.06-2.el7.noarch.rpm | 25 kB 00:00 (147/249): perl-Business-ISBN-Data-20120719.001-2.el7.noar | 24 kB 00:00 (148/249): perl-CGI-3.63-4.el7.noarch.rpm | 250 kB 00:00 (149/249): perl-Compress-Raw-Bzip2-2.061-3.el7.x86_64.rpm | 32 kB 00:00 (150/249): pango-1.42.4-4.el7_7.x86_64.rpm | 280 kB 00:00 (151/249): perl-Compress-Raw-Zlib-2.061-4.el7.x86_64.rpm | 57 kB 00:00 (152/249): perl-Data-Dumper-2.145-3.el7.x86_64.rpm | 47 kB 00:00 (153/249): perl-Data-OptList-0.107-9.el7.noarch.rpm | 23 kB 00:00 (154/249): perl-Digest-1.17-245.el7.noarch.rpm | 23 kB 00:00 (155/249): perl-Digest-HMAC-1.03-5.el7.noarch.rpm | 16 kB 00:00 (156/249): perl-Digest-MD5-2.52-3.el7.x86_64.rpm | 30 kB 00:00 (157/249): perl-Digest-SHA-5.85-4.el7.x86_64.rpm | 58 kB 00:00 (158/249): perl-Devel-GlobalDestruction-0.12-1.el7.noarch. | 18 kB 00:00 (159/249): perl-Digest-SHA1-2.13-9.el7.x86_64.rpm | 50 kB 00:00 (160/249): perl-Convert-BinHex-1.119-20.el7.noarch.rpm | 44 kB 00:00 (161/249): perl-Email-Date-Format-1.002-15.el7.noarch.rpm | 17 kB 00:00 (162/249): perl-Encode-Locale-1.03-5.el7.noarch.rpm | 16 kB 00:00 (163/249): perl-Error-0.17020-2.el7.noarch.rpm | 32 kB 00:00 (164/249): perl-FCGI-0.74-8.el7.x86_64.rpm | 42 kB 00:00 (165/249): perl-File-Listing-6.04-7.el7.noarch.rpm | 13 kB 00:00 (166/249): perl-Email-Simple-2.214-1.el7.noarch.rpm | 36 kB 00:00 (167/249): perl-File-Remove-1.52-6.el7.noarch.rpm | 26 kB 00:00 (168/249): perl-Digest-SHA3-0.24-1.el7.x86_64.rpm | 32 kB 00:00 (169/249): perl-Font-AFM-1.20-13.el7.noarch.rpm | 19 kB 00:00 (170/249): perl-Font-TTF-1.02-3.el7.noarch.rpm | 358 kB 00:00 (171/249): perl-Git-1.8.3.1-23.el7_8.noarch.rpm | 56 kB 00:00 (172/249): perl-File-FcntlLock-0.22-6.el7.x86_64.rpm | 41 kB 00:00 (173/249): perl-HTML-Format-2.10-7.el7.noarch.rpm | 51 kB 00:00 (174/249): perl-HTML-Tagset-3.20-15.el7.noarch.rpm | 18 kB 00:00 (175/249): perl-HTML-Parser-3.71-4.el7.x86_64.rpm | 115 kB 00:00 (176/249): perl-HTML-Tree-5.03-2.el7.noarch.rpm | 218 kB 00:00 (177/249): perl-HTTP-Cookies-6.01-5.el7.noarch.rpm | 26 kB 00:00 (178/249): perl-HTTP-Daemon-6.01-8.el7.noarch.rpm | 21 kB 00:00 (179/249): perl-HTTP-Date-6.02-8.el7.noarch.rpm | 14 kB 00:00 (180/249): perl-HTTP-Message-6.06-6.el7.noarch.rpm | 82 kB 00:00 (181/249): perl-HTTP-Negotiate-6.01-5.el7.noarch.rpm | 17 kB 00:00 (182/249): perl-IO-Compress-2.061-2.el7.noarch.rpm | 260 kB 00:00 (183/249): perl-IO-HTML-1.00-2.el7.noarch.rpm | 23 kB 00:00 (184/249): perl-IO-Socket-IP-0.21-5.el7.noarch.rpm | 36 kB 00:00 (185/249): perl-IO-Socket-SSL-1.94-7.el7.noarch.rpm | 115 kB 00:00 (186/249): perl-IO-String-1.08-19.el7.noarch.rpm | 16 kB 00:00 (187/249): perl-LWP-MediaTypes-6.02-2.el7.noarch.rpm | 24 kB 00:00 (188/249): perl-MIME-Lite-3.030-1.el7.noarch.rpm | 96 kB 00:00 (189/249): perl-IO-stringy-2.110-22.el7.noarch.rpm | 71 kB 00:00 (190/249): perl-MIME-tools-5.505-1.el7.noarch.rpm | 256 kB 00:00 (191/249): perl-MIME-Types-1.38-2.el7.noarch.rpm | 38 kB 00:00 (192/249): perl-Mail-Sendmail-0.79-21.el7.noarch.rpm | 29 kB 00:00 (193/249): perl-Mail-IMAPClient-3.37-1.el7.noarch.rpm | 221 kB 00:00 (194/249): perl-Image-ExifTool-12.38-1.el7.noarch.rpm | 3.3 MB 00:00 (195/249): perl-Mail-Transport-Dbx-0.07-28.el7.x86_64.rpm | 41 kB 00:00 (196/249): perl-Mail-Box-2.120-2.el7.noarch.rpm | 1.1 MB 00:00 (197/249): perl-Mozilla-CA-20130114-5.el7.noarch.rpm | 11 kB 00:00 (198/249): perl-Net-HTTP-6.06-2.el7.noarch.rpm | 29 kB 00:00 (199/249): perl-MailTools-2.12-2.el7.noarch.rpm | 108 kB 00:00 (200/249): perl-Net-LibIDN-0.12-15.el7.x86_64.rpm | 28 kB 00:00 (201/249): perl-Net-SMTP-SSL-1.01-13.el7.noarch.rpm | 9.1 kB 00:00 (202/249): perl-Package-Generator-0.103-14.el7.noarch.rpm | 23 kB 00:00 (203/249): perl-Params-Util-1.07-6.el7.x86_64.rpm | 38 kB 00:00 (204/249): perl-Net-SSLeay-1.55-6.el7.x86_64.rpm | 285 kB 00:00 (205/249): perl-Object-Realize-Later-0.19-6.el7.noarch.rpm | 21 kB 00:00 (206/249): perl-Regexp-Assemble-0.35-11.el7.noarch.rpm | 82 kB 00:00 (207/249): perl-Sub-Exporter-0.986-2.el7.noarch.rpm | 70 kB 00:00 (208/249): perl-Sub-Exporter-Progressive-0.001011-1.el7.no | 13 kB 00:00 (209/249): perl-Parse-RecDescent-1.967009-5.el7.noarch.rpm | 203 kB 00:00 (210/249): perl-Sub-Install-0.926-6.el7.noarch.rpm | 21 kB 00:00 (211/249): perl-TermReadKey-2.30-20.el7.x86_64.rpm | 31 kB 00:00 (212/249): perl-Text-Autoformat-1.669004-1.el7.noarch.rpm | 37 kB 00:00 (213/249): perl-Test-Harness-3.28-3.el7.noarch.rpm | 302 kB 00:00 (214/249): perl-Text-CharWidth-0.04-18.el7.x86_64.rpm | 15 kB 00:00 (215/249): perl-Text-Iconv-1.7-18.el7.x86_64.rpm | 23 kB 00:00 (216/249): perl-Text-WrapI18N-0.06-17.el7.noarch.rpm | 12 kB 00:00 (217/249): perl-Text-Reform-1.20-9.el7.noarch.rpm | 43 kB 00:00 (218/249): perl-Time-Piece-1.20.1-299.el7_9.x86_64.rpm | 70 kB 00:00 (219/249): perl-TimeDate-2.30-2.el7.noarch.rpm | 52 kB 00:00 (220/249): perl-TeX-Hyphen-1.01-1.el7.noarch.rpm | 35 kB 00:00 (221/249): perl-URI-1.60-9.el7.noarch.rpm | 106 kB 00:00 (222/249): perl-User-Identity-0.96-1.el7.noarch.rpm | 88 kB 00:00 (223/249): perl-WWW-RobotRules-6.02-5.el7.noarch.rpm | 18 kB 00:00 (224/249): perl-XML-Parser-2.41-10.el7.x86_64.rpm | 223 kB 00:00 (225/249): perl-autodie-2.16-2.el7.noarch.rpm | 77 kB 00:00 (226/249): perl-gettext-1.05-28.el7.x86_64.rpm | 21 kB 00:00 (227/249): perl-libwww-perl-6.05-2.el7.noarch.rpm | 205 kB 00:00 (228/249): pixman-devel-0.34.0-1.el7.x86_64.rpm | 20 kB 00:00 (229/249): pixman-0.34.0-1.el7.x86_64.rpm | 248 kB 00:00 (230/249): polkit-pkla-compat-0.1-4.el7.x86_64.rpm | 39 kB 00:00 (231/249): psmisc-22.20-17.el7.x86_64.rpm | 141 kB 00:00 (232/249): polkit-0.112-26.el7_9.1.x86_64.rpm | 170 kB 00:00 (233/249): python3-html2text-2019.9.26-3.el7.noarch.rpm | 58 kB 00:00 (234/249): python3-3.6.8-18.el7.x86_64.rpm | 70 kB 00:00 (235/249): po-debconf-1.0.20-5.el7.noarch.rpm | 147 kB 00:00 (236/249): python3-pip-9.0.3-8.el7.noarch.rpm | 1.6 MB 00:00 (237/249): python-2.7.5-92.el7_9.x86_64.rpm | 96 kB 00:00 (238/249): rsync-3.1.2-10.el7.x86_64.rpm | 404 kB 00:00 (239/249): unique-devel-1.1.6-10.el7.x86_64.rpm | 28 kB 00:00 (240/249): xml-common-0.6.3-39.el7.noarch.rpm | 26 kB 00:00 (241/249): xorg-x11-proto-devel-2018.4-1.el7.noarch.rpm | 280 kB 00:00 (242/249): python3-libs-3.6.8-18.el7.x86_64.rpm | 6.9 MB 00:00 (243/249): xz-devel-5.2.2-2.el7_9.x86_64.rpm | 46 kB 00:00 (244/249): yelp-tools-3.28.0-1.el7.noarch.rpm | 33 kB 00:00 (245/249): python3-setuptools-39.2.0-10.el7.noarch.rpm | 629 kB 00:00 (246/249): xz-lzma-compat-5.2.2-2.el7_9.x86_64.rpm | 18 kB 00:00 (247/249): yelp-xsl-3.28.0-1.el7.noarch.rpm | 204 kB 00:00 (248/249): unique-1.1.6-10.el7.x86_64.rpm | 55 kB 00:00 (249/249): zlib-devel-1.2.7-20.el7_9.x86_64.rpm | 50 kB 00:00 -------------------------------------------------------------------------------- Total 13 MB/s | 83 MB 00:06 Running transaction check Running transaction test Transaction test succeeded Running transaction Installing : xorg-x11-proto-devel-2018.4-1.el7.noarch 1/249 Installing : python-2.7.5-92.el7_9.x86_64 2/249 Installing : perl-Data-Dumper-2.145-3.el7.x86_64 3/249 Installing : atk-2.28.1-2.el7.x86_64 4/249 Installing : 2:libpng-1.5.13-8.el7.x86_64 5/249 Installing : freetype-2.8-14.el7_9.1.x86_64 6/249 Installing : 1:libglvnd-1.0.1-0.8.git5baa1e5.el7.x86_64 7/249 Installing : 1:perl-TimeDate-2.30-2.el7.noarch 8/249 Installing : perl-HTTP-Date-6.02-8.el7.noarch 9/249 Installing : mesa-libglapi-18.3.4-12.el7_9.x86_64 10/249 Installing : fipscheck-1.4.1-6.el7.x86_64 11/249 Installing : fipscheck-lib-1.4.1-6.el7.x86_64 12/249 Installing : dbus-glib-0.100-7.el7.x86_64 13/249 Installing : 1:perl-Compress-Raw-Zlib-2.061-4.el7.x86_64 14/249 Installing : libjpeg-turbo-1.2.90-8.el7.x86_64 15/249 Installing : perl-Digest-1.17-245.el7.noarch 16/249 Installing : perl-Digest-MD5-2.52-3.el7.x86_64 17/249 Installing : zlib-devel-1.2.7-20.el7_9.x86_64 18/249 Installing : 2:libpng-devel-1.5.13-8.el7.x86_64 19/249 Installing : freetype-devel-2.8-14.el7_9.1.x86_64 20/249 Installing : libdbusmenu-16.04.0-4.el7.x86_64 21/249 Installing : 1:perl-Digest-SHA-5.85-4.el7.x86_64 22/249 Installing : perl-Email-Date-Format-1.002-15.el7.noarch 23/249 Installing : 1:perl-Error-0.17020-2.el7.noarch 24/249 Installing : perl-Params-Util-1.07-6.el7.x86_64 25/249 Installing : perl-Text-CharWidth-0.04-18.el7.x86_64 26/249 Installing : mesa-khr-devel-18.3.4-12.el7_9.x86_64 27/249 Installing : graphite2-1.3.10-1.el7_3.x86_64 28/249 Installing : harfbuzz-1.7.5-2.el7.x86_64 29/249 Installing : perl-Sub-Install-0.926-6.el7.noarch 30/249 Installing : libxshmfence-1.2-1.el7.x86_64 31/249 Installing : perl-IO-Socket-IP-0.21-5.el7.noarch 32/249 Installing : fribidi-1.0.2-1.el7_7.1.x86_64 33/249 Installing : 1:dbus-devel-1.10.24-15.el7.x86_64 34/249 Installing : hicolor-icon-theme-0.12-7.el7.noarch 35/249 Installing : fontpackages-filesystem-1.44-8.el7.noarch 36/249 Installing : libunistring-0.9.3-9.el7.x86_64 37/249 Installing : perl-HTML-Tagset-3.20-15.el7.noarch 38/249 Installing : pixman-0.34.0-1.el7.x86_64 39/249 Installing : perl-Encode-Locale-1.03-5.el7.noarch 40/249 Installing : libcroco-0.6.12-6.el7_9.x86_64 41/249 Installing : gettext-libs-0.19.8.1-3.el7.x86_64 42/249 Installing : gettext-0.19.8.1-3.el7.x86_64 43/249 Installing : perl-XML-Parser-2.41-10.el7.x86_64 44/249 Installing : perl-MIME-Types-1.38-2.el7.noarch 45/249 Installing : libXau-1.0.8-2.1.el7.x86_64 46/249 Installing : libxcb-1.13-1.el7.x86_64 47/249 Installing : libicu-50.2-4.el7_7.x86_64 48/249 Installing : libwayland-server-1.15.0-1.el7.x86_64 49/249 Installing : libicu-devel-50.2-4.el7_7.x86_64 50/249 Installing : harfbuzz-icu-1.7.5-2.el7.x86_64 51/249 Installing : libXau-devel-1.0.8-2.1.el7.x86_64 52/249 Installing : libxcb-devel-1.13-1.el7.x86_64 53/249 Installing : perl-MIME-Lite-3.030-1.el7.noarch 54/249 Installing : pixman-devel-0.34.0-1.el7.x86_64 55/249 Installing : dejavu-fonts-common-2.33-6.el7.noarch 56/249 Installing : dejavu-sans-fonts-2.33-6.el7.noarch 57/249 Installing : fontconfig-2.13.0-4.3.el7.x86_64 58/249 Installing : gnome-icon-theme-3.12.0-1.el7.noarch 59/249 Installing : fribidi-devel-1.0.2-1.el7_7.1.x86_64 60/249 Installing : perl-Data-OptList-0.107-9.el7.noarch 61/249 Installing : graphite2-devel-1.3.10-1.el7_3.x86_64 62/249 Installing : perl-Text-WrapI18N-0.06-17.el7.noarch 63/249 Installing : perl-Email-Simple-2.214-1.el7.noarch 64/249 Installing : perl-Digest-HMAC-1.03-5.el7.noarch 65/249 Installing : jasper-libs-1.900.1-33.el7.x86_64 66/249 Installing : openssh-7.4p1-22.el7_9.x86_64 67/249 Installing : perl-File-Listing-6.04-7.el7.noarch 68/249 Installing : 1:libglvnd-opengl-1.0.1-0.8.git5baa1e5.el7.x86_64 69/249 Installing : perl-IO-String-1.08-19.el7.noarch 70/249 Installing : perl-Font-TTF-1.02-3.el7.noarch 71/249 Installing : libxml2-python-2.9.1-6.el7_9.6.x86_64 72/249 Installing : itstool-2.0.2-1.el7.noarch 73/249 Installing : libX11-common-1.6.7-4.el7_9.noarch 74/249 Installing : libX11-1.6.7-4.el7_9.x86_64 75/249 Installing : libX11-devel-1.6.7-4.el7_9.x86_64 76/249 Installing : libXext-1.3.3-3.el7.x86_64 77/249 Installing : libXext-devel-1.3.3-3.el7.x86_64 78/249 Installing : libXrender-0.9.10-1.el7.x86_64 79/249 Installing : libXfixes-5.0.3-1.el7.x86_64 80/249 Installing : libXfixes-devel-5.0.3-1.el7.x86_64 81/249 Installing : libXdamage-1.1.4-4.1.el7.x86_64 82/249 Installing : libXrender-devel-0.9.10-1.el7.x86_64 83/249 Installing : libXcursor-1.1.15-1.el7.x86_64 84/249 Installing : libXrandr-1.5.1-2.el7.x86_64 85/249 Installing : libXi-1.7.9-1.el7.x86_64 86/249 Installing : libXinerama-1.1.3-2.1.el7.x86_64 87/249 Installing : libXcomposite-0.4.4-4.1.el7.x86_64 88/249 Installing : libXdamage-devel-1.1.4-4.1.el7.x86_64 89/249 Installing : libXft-2.3.2-2.el7.x86_64 90/249 Installing : libXxf86vm-1.1.4-1.el7.x86_64 91/249 Installing : libXxf86vm-devel-1.1.4-1.el7.x86_64 92/249 Installing : libXcomposite-devel-0.4.4-4.1.el7.x86_64 93/249 Installing : libXinerama-devel-1.1.3-2.1.el7.x86_64 94/249 Installing : libXi-devel-1.7.9-1.el7.x86_64 95/249 Installing : libXrandr-devel-1.5.1-2.el7.x86_64 96/249 Installing : libXcursor-devel-1.1.15-1.el7.x86_64 97/249 Installing : perl-IO-stringy-2.110-22.el7.noarch 98/249 Installing : jbigkit-libs-2.0-11.el7.x86_64 99/249 Installing : libtiff-4.0.3-35.el7.x86_64 100/249 Installing : gdk-pixbuf2-2.36.12-3.el7.x86_64 101/249 Installing : libnotify-0.7.7-1.el7.x86_64 102/249 Installing : gtk-update-icon-cache-3.22.30-8.el7_9.x86_64 103/249 Installing : perl-Net-SSLeay-1.55-6.el7.x86_64 104/249 Installing : xml-common-0.6.3-39.el7.noarch 105/249 Installing : mallard-rng-1.0.2-1.el7.noarch 106/249 Installing : expat-devel-2.1.0-14.el7_9.x86_64 107/249 Installing : perl-Digest-SHA1-2.13-9.el7.x86_64 108/249 Installing : libthai-0.1.14-9.el7.x86_64 109/249 Installing : perl-Business-ISBN-Data-20120719.001-2.el7.noarch 110/249 Installing : perl-Business-ISBN-2.06-2.el7.noarch 111/249 Installing : perl-URI-1.60-9.el7.noarch 112/249 Installing : perl-WWW-RobotRules-6.02-5.el7.noarch 113/249 Installing : perl-autodie-2.16-2.el7.noarch 114/249 Installing : 1:openssl-1.0.2k-25.el7_9.x86_64 115/249 Installing : perl-Font-AFM-1.20-13.el7.noarch 116/249 Installing : libtirpc-0.2.4-0.16.el7.x86_64 117/249 Installing : python3-libs-3.6.8-18.el7.x86_64 118/249 Installing : python3-3.6.8-18.el7.x86_64 119/249 Installing : python3-setuptools-39.2.0-10.el7.noarch 120/249 Installing : python3-pip-9.0.3-8.el7.noarch 121/249 Installing : python3-html2text-2019.9.26-3.el7.noarch 122/249 Installing : less-458-9.el7.x86_64 123/249 Installing : dpkg-1.18.25-10.el7.x86_64 124/249 Installing : check-0.9.9-5.el7.x86_64 125/249 Installing : check-devel-0.9.9-5.el7.x86_64 126/249 Installing : gettext-common-devel-0.19.8.1-3.el7.noarch 127/249 Installing : perl-Parse-RecDescent-1.967009-5.el7.noarch 128/249 Installing : perl-Mail-IMAPClient-3.37-1.el7.noarch 129/249 Installing : perl-gettext-1.05-28.el7.x86_64 130/249 Installing : perl-Mail-Sendmail-0.79-21.el7.noarch 131/249 Installing : yelp-xsl-3.28.0-1.el7.noarch 132/249 Installing : yelp-tools-3.28.0-1.el7.noarch 133/249 Installing : perl-Time-Piece-1.20.1-299.el7_9.x86_64 134/249 Installing : perl-Test-Harness-3.28-3.el7.noarch 135/249 Installing : perl-User-Identity-0.96-1.el7.noarch 136/249 Installing : perl-Compress-Raw-Bzip2-2.061-3.el7.x86_64 137/249 Installing : perl-IO-Compress-2.061-2.el7.noarch 138/249 Installing : m4-1.4.16-10.el7.x86_64 139/249 Installing : autoconf-2.69-11.el7.noarch 140/249 Installing : automake-1.13.4-3.el7.noarch 141/249 Installing : libtool-2.4.2-22.el7_3.x86_64 142/249 Installing : autoconf-archive-2017.03.21-1.el7.noarch 143/249 Installing : pcre-devel-8.32-17.el7.x86_64 144/249 Installing : glib2-devel-2.56.1-9.el7_9.x86_64 145/249 Installing : dbus-glib-devel-0.100-7.el7.x86_64 146/249 Installing : gdk-pixbuf2-devel-2.36.12-3.el7.x86_64 147/249 Installing : libdbusmenu-devel-16.04.0-4.el7.x86_64 148/249 Installing : atk-devel-2.28.1-2.el7.x86_64 149/249 Installing : gstreamer1-1.10.4-2.el7.x86_64 150/249 Installing : mailcap-2.1.41-2.el7.noarch 151/249 Installing : perl-LWP-MediaTypes-6.02-2.el7.noarch 152/249 Installing : perl-Convert-BinHex-1.119-20.el7.noarch 153/249 Installing : avahi-libs-0.6.31-20.el7.x86_64 154/249 Installing : 1:cups-libs-1.6.3-51.el7.x86_64 155/249 Installing : psmisc-22.20-17.el7.x86_64 156/249 Installing : perl-IO-HTML-1.00-2.el7.noarch 157/249 Installing : perl-HTTP-Message-6.06-6.el7.noarch 158/249 Installing : perl-HTML-Parser-3.71-4.el7.x86_64 159/249 Installing : perl-HTTP-Negotiate-6.01-5.el7.noarch 160/249 Installing : perl-HTTP-Daemon-6.01-8.el7.noarch 161/249 Installing : perl-HTTP-Cookies-6.01-5.el7.noarch 162/249 Installing : mozjs17-17.0.0-20.el7.x86_64 163/249 Installing : polkit-0.112-26.el7_9.1.x86_64 164/249 Installing : polkit-pkla-compat-0.1-4.el7.x86_64 165/249 Installing : GConf2-3.2.6-8.el7.x86_64 166/249 Installing : rsync-3.1.2-10.el7.x86_64 167/249 Installing : perl-Digest-SHA3-0.24-1.el7.x86_64 168/249 Installing : dpkg-perl-1.18.25-10.el7.noarch 169/249 Installing : perl-Mail-Transport-Dbx-0.07-28.el7.x86_64 170/249 Installing : hwdata-0.252-9.7.el7.x86_64 171/249 Installing : libpciaccess-0.14-1.el7.x86_64 172/249 Installing : libdrm-2.4.97-2.el7.x86_64 173/249 Installing : 1:libglvnd-glx-1.0.1-0.8.git5baa1e5.el7.x86_64 174/249 Installing : mesa-libGL-18.3.4-12.el7_9.x86_64 175/249 Installing : libdrm-devel-2.4.97-2.el7.x86_64 176/249 Installing : mesa-libgbm-18.3.4-12.el7_9.x86_64 177/249 Installing : 1:libglvnd-core-devel-1.0.1-0.8.git5baa1e5.el7.x86_64 178/249 Installing : perl-Image-ExifTool-12.38-1.el7.noarch 179/249 Installing : perl-Package-Generator-0.103-14.el7.noarch 180/249 Installing : perl-Sub-Exporter-0.986-2.el7.noarch 181/249 Installing : perl-Sub-Exporter-Progressive-0.001011-1.el7.noarch 182/249 Installing : perl-Devel-GlobalDestruction-0.12-1.el7.noarch 183/249 Installing : libuuid-devel-2.23.2-65.el7_9.1.x86_64 184/249 Installing : fontconfig-devel-2.13.0-4.3.el7.x86_64 185/249 Installing : libXft-devel-2.3.2-2.el7.x86_64 186/249 Installing : xz-lzma-compat-5.2.2-2.el7_9.x86_64 187/249 Installing : dpkg-dev-1.18.25-10.el7.noarch 188/249 Installing : libedit-3.0-12.20121213cvs.el7.x86_64 189/249 Installing : openssh-clients-7.4p1-22.el7_9.x86_64 190/249 Installing : libwayland-client-1.15.0-1.el7.x86_64 191/249 Installing : 1:libglvnd-egl-1.0.1-0.8.git5baa1e5.el7.x86_64 192/249 Installing : mesa-libEGL-18.3.4-12.el7_9.x86_64 193/249 Installing : cairo-1.15.12-4.el7.x86_64 194/249 Installing : pango-1.42.4-4.el7_7.x86_64 195/249 Installing : gtk2-2.24.31-1.el7.x86_64 196/249 Installing : libindicator-12.10.1-6.el7.x86_64 197/249 Installing : libdbusmenu-gtk2-16.04.0-4.el7.x86_64 198/249 Installing : libappindicator-12.10.0-13.el7.x86_64 199/249 Installing : unique-1.1.6-10.el7.x86_64 200/249 Installing : harfbuzz-devel-1.7.5-2.el7.x86_64 201/249 Installing : 1:libglvnd-gles-1.0.1-0.8.git5baa1e5.el7.x86_64 202/249 Installing : 1:libglvnd-devel-1.0.1-0.8.git5baa1e5.el7.x86_64 203/249 Installing : mesa-libEGL-devel-18.3.4-12.el7_9.x86_64 204/249 Installing : perl-TeX-Hyphen-1.01-1.el7.noarch 205/249 Installing : perl-Text-Reform-1.20-9.el7.noarch 206/249 Installing : perl-Text-Autoformat-1.669004-1.el7.noarch 207/249 Installing : perl-File-Remove-1.52-6.el7.noarch 208/249 Installing : perl-Mozilla-CA-20130114-5.el7.noarch 209/249 Installing : 1:perl-FCGI-0.74-8.el7.x86_64 210/249 Installing : perl-CGI-3.63-4.el7.noarch 211/249 Installing : xz-devel-5.2.2-2.el7_9.x86_64 212/249 Installing : libxml2-devel-2.9.1-6.el7_9.6.x86_64 213/249 Installing : perl-Object-Realize-Later-0.19-6.el7.noarch 214/249 Installing : gl-manpages-1.1-7.20130122.el7.noarch 215/249 Installing : mesa-libGL-devel-18.3.4-12.el7_9.x86_64 216/249 Installing : cairo-devel-1.15.12-4.el7.x86_64 217/249 Installing : pango-devel-1.42.4-4.el7_7.x86_64 218/249 Installing : gtk2-devel-2.24.31-1.el7.x86_64 219/249 Installing : perl-File-FcntlLock-0.22-6.el7.x86_64 220/249 Installing : perl-TermReadKey-2.30-20.el7.x86_64 221/249 Installing : perl-Git-1.8.3.1-23.el7_8.noarch 222/249 Installing : git-1.8.3.1-23.el7_8.x86_64 223/249 Installing : gettext-devel-0.19.8.1-3.el7.x86_64 224/249 Installing : intltool-0.50.2-7.el7.noarch 225/249 Installing : perl-Regexp-Assemble-0.35-11.el7.noarch 226/249 Installing : cdbs-0.4.150-3.el7.noarch 227/249 Installing : perl-Net-LibIDN-0.12-15.el7.x86_64 228/249 Installing : perl-IO-Socket-SSL-1.94-7.el7.noarch 229/249 Installing : perl-Net-HTTP-6.06-2.el7.noarch 230/249 Installing : perl-libwww-perl-6.05-2.el7.noarch 231/249 Installing : perl-HTML-Format-2.10-7.el7.noarch 232/249 Installing : 1:perl-HTML-Tree-5.03-2.el7.noarch 233/249 Installing : perl-Net-SMTP-SSL-1.01-13.el7.noarch 234/249 Installing : perl-MailTools-2.12-2.el7.noarch 235/249 Installing : perl-MIME-tools-5.505-1.el7.noarch 236/249 Installing : perl-Mail-Box-2.120-2.el7.noarch 237/249 Installing : perl-Text-Iconv-1.7-18.el7.x86_64 238/249 Installing : debconf-1.5.79-1.el7.noarch 239/249 Installing : po-debconf-1.0.20-5.el7.noarch 240/249 Installing : debhelper-11.4-2.el7.noarch 241/249 Installing : dh-autoreconf-19-1.el7.noarch 242/249 Installing : libappindicator-devel-12.10.0-13.el7.x86_64 243/249 Installing : unique-devel-1.1.6-10.el7.x86_64 244/249 Installing : gstreamer1-devel-1.10.4-2.el7.x86_64 245/249 Installing : GConf2-devel-3.2.6-8.el7.x86_64 246/249 Installing : libnotify-devel-0.7.7-1.el7.x86_64 247/249 Installing : gnome-common-3.18.0-1.el7.noarch 248/249 Installing : gnome-icon-theme-devel-3.12.0-1.el7.noarch 249/249 Verifying : libXext-1.3.3-3.el7.x86_64 1/249 Verifying : fipscheck-lib-1.4.1-6.el7.x86_64 2/249 Verifying : libXi-1.7.9-1.el7.x86_64 3/249 Verifying : python3-setuptools-39.2.0-10.el7.noarch 4/249 Verifying : gnome-icon-theme-3.12.0-1.el7.noarch 5/249 Verifying : perl-Text-Iconv-1.7-18.el7.x86_64 6/249 Verifying : libXrender-0.9.10-1.el7.x86_64 7/249 Verifying : libnotify-0.7.7-1.el7.x86_64 8/249 Verifying : libwayland-server-1.15.0-1.el7.x86_64 9/249 Verifying : perl-Net-LibIDN-0.12-15.el7.x86_64 10/249 Verifying : perl-HTTP-Date-6.02-8.el7.noarch 11/249 Verifying : perl-Regexp-Assemble-0.35-11.el7.noarch 12/249 Verifying : git-1.8.3.1-23.el7_8.x86_64 13/249 Verifying : perl-LWP-MediaTypes-6.02-2.el7.noarch 14/249 Verifying : gstreamer1-devel-1.10.4-2.el7.x86_64 15/249 Verifying : perl-TermReadKey-2.30-20.el7.x86_64 16/249 Verifying : perl-File-Listing-6.04-7.el7.noarch 17/249 Verifying : perl-Business-ISBN-2.06-2.el7.noarch 18/249 Verifying : xorg-x11-proto-devel-2018.4-1.el7.noarch 19/249 Verifying : perl-File-FcntlLock-0.22-6.el7.x86_64 20/249 Verifying : python-2.7.5-92.el7_9.x86_64 21/249 Verifying : libX11-devel-1.6.7-4.el7_9.x86_64 22/249 Verifying : gl-manpages-1.1-7.20130122.el7.noarch 23/249 Verifying : perl-Devel-GlobalDestruction-0.12-1.el7.noarch 24/249 Verifying : perl-IO-Socket-SSL-1.94-7.el7.noarch 25/249 Verifying : cairo-devel-1.15.12-4.el7.x86_64 26/249 Verifying : libdbusmenu-16.04.0-4.el7.x86_64 27/249 Verifying : 1:libglvnd-1.0.1-0.8.git5baa1e5.el7.x86_64 28/249 Verifying : libXrender-devel-0.9.10-1.el7.x86_64 29/249 Verifying : perl-Text-Reform-1.20-9.el7.noarch 30/249 Verifying : libxcb-1.13-1.el7.x86_64 31/249 Verifying : mesa-libgbm-18.3.4-12.el7_9.x86_64 32/249 Verifying : perl-Data-Dumper-2.145-3.el7.x86_64 33/249 Verifying : itstool-2.0.2-1.el7.noarch 34/249 Verifying : fipscheck-1.4.1-6.el7.x86_64 35/249 Verifying : libicu-50.2-4.el7_7.x86_64 36/249 Verifying : perl-Object-Realize-Later-0.19-6.el7.noarch 37/249 Verifying : 1:libglvnd-glx-1.0.1-0.8.git5baa1e5.el7.x86_64 38/249 Verifying : dejavu-sans-fonts-2.33-6.el7.noarch 39/249 Verifying : libXext-devel-1.3.3-3.el7.x86_64 40/249 Verifying : libXcomposite-0.4.4-4.1.el7.x86_64 41/249 Verifying : python3-html2text-2019.9.26-3.el7.noarch 42/249 Verifying : xz-devel-5.2.2-2.el7_9.x86_64 43/249 Verifying : perl-HTTP-Message-6.06-6.el7.noarch 44/249 Verifying : mesa-libGL-devel-18.3.4-12.el7_9.x86_64 45/249 Verifying : graphite2-devel-1.3.10-1.el7_3.x86_64 46/249 Verifying : gnome-icon-theme-devel-3.12.0-1.el7.noarch 47/249 Verifying : pixman-devel-0.34.0-1.el7.x86_64 48/249 Verifying : 1:perl-FCGI-0.74-8.el7.x86_64 49/249 Verifying : perl-Net-HTTP-6.06-2.el7.noarch 50/249 Verifying : libXcomposite-devel-0.4.4-4.1.el7.x86_64 51/249 Verifying : autoconf-2.69-11.el7.noarch 52/249 Verifying : gettext-0.19.8.1-3.el7.x86_64 53/249 Verifying : gtk-update-icon-cache-3.22.30-8.el7_9.x86_64 54/249 Verifying : yelp-tools-3.28.0-1.el7.noarch 55/249 Verifying : perl-WWW-RobotRules-6.02-5.el7.noarch 56/249 Verifying : libxml2-python-2.9.1-6.el7_9.6.x86_64 57/249 Verifying : perl-Mozilla-CA-20130114-5.el7.noarch 58/249 Verifying : libXau-1.0.8-2.1.el7.x86_64 59/249 Verifying : perl-Data-OptList-0.107-9.el7.noarch 60/249 Verifying : perl-File-Remove-1.52-6.el7.noarch 61/249 Verifying : perl-TeX-Hyphen-1.01-1.el7.noarch 62/249 Verifying : freetype-2.8-14.el7_9.1.x86_64 63/249 Verifying : libXau-devel-1.0.8-2.1.el7.x86_64 64/249 Verifying : libpciaccess-0.14-1.el7.x86_64 65/249 Verifying : 1:libglvnd-devel-1.0.1-0.8.git5baa1e5.el7.x86_64 66/249 Verifying : 2:libpng-devel-1.5.13-8.el7.x86_64 67/249 Verifying : libwayland-client-1.15.0-1.el7.x86_64 68/249 Verifying : libxml2-devel-2.9.1-6.el7_9.6.x86_64 69/249 Verifying : libedit-3.0-12.20121213cvs.el7.x86_64 70/249 Verifying : mallard-rng-1.0.2-1.el7.noarch 71/249 Verifying : perl-MIME-Lite-3.030-1.el7.noarch 72/249 Verifying : atk-devel-2.28.1-2.el7.x86_64 73/249 Verifying : xz-lzma-compat-5.2.2-2.el7_9.x86_64 74/249 Verifying : perl-MIME-Types-1.38-2.el7.noarch 75/249 Verifying : python3-3.6.8-18.el7.x86_64 76/249 Verifying : perl-XML-Parser-2.41-10.el7.x86_64 77/249 Verifying : gettext-libs-0.19.8.1-3.el7.x86_64 78/249 Verifying : po-debconf-1.0.20-5.el7.noarch 79/249 Verifying : 1:cups-libs-1.6.3-51.el7.x86_64 80/249 Verifying : 1:perl-Digest-SHA-5.85-4.el7.x86_64 81/249 Verifying : libuuid-devel-2.23.2-65.el7_9.1.x86_64 82/249 Verifying : perl-Package-Generator-0.103-14.el7.noarch 83/249 Verifying : libcroco-0.6.12-6.el7_9.x86_64 84/249 Verifying : dh-autoreconf-19-1.el7.noarch 85/249 Verifying : libappindicator-devel-12.10.0-13.el7.x86_64 86/249 Verifying : gnome-common-3.18.0-1.el7.noarch 87/249 Verifying : glib2-devel-2.56.1-9.el7_9.x86_64 88/249 Verifying : mesa-libGL-18.3.4-12.el7_9.x86_64 89/249 Verifying : perl-Image-ExifTool-12.38-1.el7.noarch 90/249 Verifying : 1:libglvnd-core-devel-1.0.1-0.8.git5baa1e5.el7.x86_64 91/249 Verifying : perl-Encode-Locale-1.03-5.el7.noarch 92/249 Verifying : harfbuzz-devel-1.7.5-2.el7.x86_64 93/249 Verifying : mesa-libglapi-18.3.4-12.el7_9.x86_64 94/249 Verifying : perl-MIME-tools-5.505-1.el7.noarch 95/249 Verifying : perl-Digest-HMAC-1.03-5.el7.noarch 96/249 Verifying : hwdata-0.252-9.7.el7.x86_64 97/249 Verifying : pixman-0.34.0-1.el7.x86_64 98/249 Verifying : zlib-devel-1.2.7-20.el7_9.x86_64 99/249 Verifying : perl-HTML-Tagset-3.20-15.el7.noarch 100/249 Verifying : mesa-libEGL-devel-18.3.4-12.el7_9.x86_64 101/249 Verifying : libXinerama-devel-1.1.3-2.1.el7.x86_64 102/249 Verifying : perl-Net-SMTP-SSL-1.01-13.el7.noarch 103/249 Verifying : libXfixes-devel-5.0.3-1.el7.x86_64 104/249 Verifying : 1:libglvnd-egl-1.0.1-0.8.git5baa1e5.el7.x86_64 105/249 Verifying : perl-Mail-Transport-Dbx-0.07-28.el7.x86_64 106/249 Verifying : jasper-libs-1.900.1-33.el7.x86_64 107/249 Verifying : perl-Digest-SHA3-0.24-1.el7.x86_64 108/249 Verifying : rsync-3.1.2-10.el7.x86_64 109/249 Verifying : mozjs17-17.0.0-20.el7.x86_64 110/249 Verifying : perl-IO-HTML-1.00-2.el7.noarch 111/249 Verifying : libXfixes-5.0.3-1.el7.x86_64 112/249 Verifying : atk-2.28.1-2.el7.x86_64 113/249 Verifying : perl-Digest-1.17-245.el7.noarch 114/249 Verifying : psmisc-22.20-17.el7.x86_64 115/249 Verifying : perl-Digest-MD5-2.52-3.el7.x86_64 116/249 Verifying : pango-devel-1.42.4-4.el7_7.x86_64 117/249 Verifying : avahi-libs-0.6.31-20.el7.x86_64 118/249 Verifying : libXft-devel-2.3.2-2.el7.x86_64 119/249 Verifying : fontconfig-2.13.0-4.3.el7.x86_64 120/249 Verifying : check-devel-0.9.9-5.el7.x86_64 121/249 Verifying : gdk-pixbuf2-2.36.12-3.el7.x86_64 122/249 Verifying : perl-Convert-BinHex-1.119-20.el7.noarch 123/249 Verifying : mailcap-2.1.41-2.el7.noarch 124/249 Verifying : gstreamer1-1.10.4-2.el7.x86_64 125/249 Verifying : openssh-clients-7.4p1-22.el7_9.x86_64 126/249 Verifying : unique-devel-1.1.6-10.el7.x86_64 127/249 Verifying : libunistring-0.9.3-9.el7.x86_64 128/249 Verifying : pcre-devel-8.32-17.el7.x86_64 129/249 Verifying : libXcursor-1.1.15-1.el7.x86_64 130/249 Verifying : cdbs-0.4.150-3.el7.noarch 131/249 Verifying : perl-Sub-Exporter-0.986-2.el7.noarch 132/249 Verifying : python3-pip-9.0.3-8.el7.noarch 133/249 Verifying : m4-1.4.16-10.el7.x86_64 134/249 Verifying : perl-Mail-Box-2.120-2.el7.noarch 135/249 Verifying : perl-Compress-Raw-Bzip2-2.061-3.el7.x86_64 136/249 Verifying : fontpackages-filesystem-1.44-8.el7.noarch 137/249 Verifying : hicolor-icon-theme-0.12-7.el7.noarch 138/249 Verifying : libindicator-12.10.1-6.el7.x86_64 139/249 Verifying : perl-HTML-Parser-3.71-4.el7.x86_64 140/249 Verifying : fontconfig-devel-2.13.0-4.3.el7.x86_64 141/249 Verifying : perl-User-Identity-0.96-1.el7.noarch 142/249 Verifying : gtk2-devel-2.24.31-1.el7.x86_64 143/249 Verifying : 1:dbus-devel-1.10.24-15.el7.x86_64 144/249 Verifying : perl-Test-Harness-3.28-3.el7.noarch 145/249 Verifying : debhelper-11.4-2.el7.noarch 146/249 Verifying : pango-1.42.4-4.el7_7.x86_64 147/249 Verifying : fribidi-1.0.2-1.el7_7.1.x86_64 148/249 Verifying : libXi-devel-1.7.9-1.el7.x86_64 149/249 Verifying : libdrm-2.4.97-2.el7.x86_64 150/249 Verifying : perl-Time-Piece-1.20.1-299.el7_9.x86_64 151/249 Verifying : libdbusmenu-gtk2-16.04.0-4.el7.x86_64 152/249 Verifying : libtool-2.4.2-22.el7_3.x86_64 153/249 Verifying : yelp-xsl-3.28.0-1.el7.noarch 154/249 Verifying : libjpeg-turbo-1.2.90-8.el7.x86_64 155/249 Verifying : perl-Mail-Sendmail-0.79-21.el7.noarch 156/249 Verifying : libXcursor-devel-1.1.15-1.el7.x86_64 157/249 Verifying : python3-libs-3.6.8-18.el7.x86_64 158/249 Verifying : gettext-devel-0.19.8.1-3.el7.x86_64 159/249 Verifying : perl-gettext-1.05-28.el7.x86_64 160/249 Verifying : perl-Font-TTF-1.02-3.el7.noarch 161/249 Verifying : harfbuzz-1.7.5-2.el7.x86_64 162/249 Verifying : perl-Parse-RecDescent-1.967009-5.el7.noarch 163/249 Verifying : perl-MailTools-2.12-2.el7.noarch 164/249 Verifying : libXdamage-devel-1.1.4-4.1.el7.x86_64 165/249 Verifying : perl-HTTP-Negotiate-6.01-5.el7.noarch 166/249 Verifying : libXrandr-1.5.1-2.el7.x86_64 167/249 Verifying : 2:libpng-1.5.13-8.el7.x86_64 168/249 Verifying : perl-IO-Socket-IP-0.21-5.el7.noarch 169/249 Verifying : perl-HTTP-Daemon-6.01-8.el7.noarch 170/249 Verifying : perl-HTML-Format-2.10-7.el7.noarch 171/249 Verifying : perl-IO-Compress-2.061-2.el7.noarch 172/249 Verifying : libicu-devel-50.2-4.el7_7.x86_64 173/249 Verifying : libxshmfence-1.2-1.el7.x86_64 174/249 Verifying : perl-Sub-Install-0.926-6.el7.noarch 175/249 Verifying : fribidi-devel-1.0.2-1.el7_7.1.x86_64 176/249 Verifying : 1:perl-TimeDate-2.30-2.el7.noarch 177/249 Verifying : libX11-1.6.7-4.el7_9.x86_64 178/249 Verifying : 1:perl-HTML-Tree-5.03-2.el7.noarch 179/249 Verifying : libXdamage-1.1.4-4.1.el7.x86_64 180/249 Verifying : gettext-common-devel-0.19.8.1-3.el7.noarch 181/249 Verifying : check-0.9.9-5.el7.x86_64 182/249 Verifying : dpkg-1.18.25-10.el7.x86_64 183/249 Verifying : less-458-9.el7.x86_64 184/249 Verifying : libtirpc-0.2.4-0.16.el7.x86_64 185/249 Verifying : perl-Font-AFM-1.20-13.el7.noarch 186/249 Verifying : dpkg-dev-1.18.25-10.el7.noarch 187/249 Verifying : libXinerama-1.1.3-2.1.el7.x86_64 188/249 Verifying : automake-1.13.4-3.el7.noarch 189/249 Verifying : perl-HTTP-Cookies-6.01-5.el7.noarch 190/249 Verifying : libXxf86vm-1.1.4-1.el7.x86_64 191/249 Verifying : graphite2-1.3.10-1.el7_3.x86_64 192/249 Verifying : perl-Sub-Exporter-Progressive-0.001011-1.el7.noarch 193/249 Verifying : perl-Text-WrapI18N-0.06-17.el7.noarch 194/249 Verifying : openssh-7.4p1-22.el7_9.x86_64 195/249 Verifying : mesa-khr-devel-18.3.4-12.el7_9.x86_64 196/249 Verifying : gtk2-2.24.31-1.el7.x86_64 197/249 Verifying : libXxf86vm-devel-1.1.4-1.el7.x86_64 198/249 Verifying : libXrandr-devel-1.5.1-2.el7.x86_64 199/249 Verifying : 1:openssl-1.0.2k-25.el7_9.x86_64 200/249 Verifying : mesa-libEGL-18.3.4-12.el7_9.x86_64 201/249 Verifying : libtiff-4.0.3-35.el7.x86_64 202/249 Verifying : dejavu-fonts-common-2.33-6.el7.noarch 203/249 Verifying : perl-autodie-2.16-2.el7.noarch 204/249 Verifying : perl-Business-ISBN-Data-20120719.001-2.el7.noarch 205/249 Verifying : libthai-0.1.14-9.el7.x86_64 206/249 Verifying : perl-Mail-IMAPClient-3.37-1.el7.noarch 207/249 Verifying : intltool-0.50.2-7.el7.noarch 208/249 Verifying : libappindicator-12.10.0-13.el7.x86_64 209/249 Verifying : libXft-2.3.2-2.el7.x86_64 210/249 Verifying : perl-Email-Simple-2.214-1.el7.noarch 211/249 Verifying : autoconf-archive-2017.03.21-1.el7.noarch 212/249 Verifying : perl-Git-1.8.3.1-23.el7_8.noarch 213/249 Verifying : perl-Text-CharWidth-0.04-18.el7.x86_64 214/249 Verifying : 1:libglvnd-gles-1.0.1-0.8.git5baa1e5.el7.x86_64 215/249 Verifying : perl-IO-String-1.08-19.el7.noarch 216/249 Verifying : libdrm-devel-2.4.97-2.el7.x86_64 217/249 Verifying : perl-Params-Util-1.07-6.el7.x86_64 218/249 Verifying : dbus-glib-devel-0.100-7.el7.x86_64 219/249 Verifying : 1:perl-Error-0.17020-2.el7.noarch 220/249 Verifying : polkit-pkla-compat-0.1-4.el7.x86_64 221/249 Verifying : unique-1.1.6-10.el7.x86_64 222/249 Verifying : libdbusmenu-devel-16.04.0-4.el7.x86_64 223/249 Verifying : 1:perl-Compress-Raw-Zlib-2.061-4.el7.x86_64 224/249 Verifying : perl-libwww-perl-6.05-2.el7.noarch 225/249 Verifying : dbus-glib-0.100-7.el7.x86_64 226/249 Verifying : freetype-devel-2.8-14.el7_9.1.x86_64 227/249 Verifying : GConf2-devel-3.2.6-8.el7.x86_64 228/249 Verifying : perl-Digest-SHA1-2.13-9.el7.x86_64 229/249 Verifying : cairo-1.15.12-4.el7.x86_64 230/249 Verifying : GConf2-3.2.6-8.el7.x86_64 231/249 Verifying : 1:libglvnd-opengl-1.0.1-0.8.git5baa1e5.el7.x86_64 232/249 Verifying : expat-devel-2.1.0-14.el7_9.x86_64 233/249 Verifying : perl-CGI-3.63-4.el7.noarch 234/249 Verifying : xml-common-0.6.3-39.el7.noarch 235/249 Verifying : libxcb-devel-1.13-1.el7.x86_64 236/249 Verifying : perl-Net-SSLeay-1.55-6.el7.x86_64 237/249 Verifying : debconf-1.5.79-1.el7.noarch 238/249 Verifying : perl-Text-Autoformat-1.669004-1.el7.noarch 239/249 Verifying : harfbuzz-icu-1.7.5-2.el7.x86_64 240/249 Verifying : gdk-pixbuf2-devel-2.36.12-3.el7.x86_64 241/249 Verifying : jbigkit-libs-2.0-11.el7.x86_64 242/249 Verifying : libnotify-devel-0.7.7-1.el7.x86_64 243/249 Verifying : perl-IO-stringy-2.110-22.el7.noarch 244/249 Verifying : perl-URI-1.60-9.el7.noarch 245/249 Verifying : dpkg-perl-1.18.25-10.el7.noarch 246/249 Verifying : polkit-0.112-26.el7_9.1.x86_64 247/249 Verifying : libX11-common-1.6.7-4.el7_9.noarch 248/249 Verifying : perl-Email-Date-Format-1.002-15.el7.noarch 249/249 Installed: GConf2-devel.x86_64 0:3.2.6-8.el7 dh-autoreconf.noarch 0:19-1.el7 glib2-devel.x86_64 0:2.56.1-9.el7_9 gnome-common.noarch 0:3.18.0-1.el7 gnome-icon-theme-devel.noarch 0:3.12.0-1.el7 gstreamer1-devel.x86_64 0:1.10.4-2.el7 gtk2-devel.x86_64 0:2.24.31-1.el7 intltool.noarch 0:0.50.2-7.el7 libappindicator-devel.x86_64 0:12.10.0-13.el7 libnotify-devel.x86_64 0:0.7.7-1.el7 libxml2-devel.x86_64 0:2.9.1-6.el7_9.6 unique-devel.x86_64 0:1.1.6-10.el7 Dependency Installed: GConf2.x86_64 0:3.2.6-8.el7 atk.x86_64 0:2.28.1-2.el7 atk-devel.x86_64 0:2.28.1-2.el7 autoconf.noarch 0:2.69-11.el7 autoconf-archive.noarch 0:2017.03.21-1.el7 automake.noarch 0:1.13.4-3.el7 avahi-libs.x86_64 0:0.6.31-20.el7 cairo.x86_64 0:1.15.12-4.el7 cairo-devel.x86_64 0:1.15.12-4.el7 cdbs.noarch 0:0.4.150-3.el7 check.x86_64 0:0.9.9-5.el7 check-devel.x86_64 0:0.9.9-5.el7 cups-libs.x86_64 1:1.6.3-51.el7 dbus-devel.x86_64 1:1.10.24-15.el7 dbus-glib.x86_64 0:0.100-7.el7 dbus-glib-devel.x86_64 0:0.100-7.el7 debconf.noarch 0:1.5.79-1.el7 debhelper.noarch 0:11.4-2.el7 dejavu-fonts-common.noarch 0:2.33-6.el7 dejavu-sans-fonts.noarch 0:2.33-6.el7 dpkg.x86_64 0:1.18.25-10.el7 dpkg-dev.noarch 0:1.18.25-10.el7 dpkg-perl.noarch 0:1.18.25-10.el7 expat-devel.x86_64 0:2.1.0-14.el7_9 fipscheck.x86_64 0:1.4.1-6.el7 fipscheck-lib.x86_64 0:1.4.1-6.el7 fontconfig.x86_64 0:2.13.0-4.3.el7 fontconfig-devel.x86_64 0:2.13.0-4.3.el7 fontpackages-filesystem.noarch 0:1.44-8.el7 freetype.x86_64 0:2.8-14.el7_9.1 freetype-devel.x86_64 0:2.8-14.el7_9.1 fribidi.x86_64 0:1.0.2-1.el7_7.1 fribidi-devel.x86_64 0:1.0.2-1.el7_7.1 gdk-pixbuf2.x86_64 0:2.36.12-3.el7 gdk-pixbuf2-devel.x86_64 0:2.36.12-3.el7 gettext.x86_64 0:0.19.8.1-3.el7 gettext-common-devel.noarch 0:0.19.8.1-3.el7 gettext-devel.x86_64 0:0.19.8.1-3.el7 gettext-libs.x86_64 0:0.19.8.1-3.el7 git.x86_64 0:1.8.3.1-23.el7_8 gl-manpages.noarch 0:1.1-7.20130122.el7 gnome-icon-theme.noarch 0:3.12.0-1.el7 graphite2.x86_64 0:1.3.10-1.el7_3 graphite2-devel.x86_64 0:1.3.10-1.el7_3 gstreamer1.x86_64 0:1.10.4-2.el7 gtk-update-icon-cache.x86_64 0:3.22.30-8.el7_9 gtk2.x86_64 0:2.24.31-1.el7 harfbuzz.x86_64 0:1.7.5-2.el7 harfbuzz-devel.x86_64 0:1.7.5-2.el7 harfbuzz-icu.x86_64 0:1.7.5-2.el7 hicolor-icon-theme.noarch 0:0.12-7.el7 hwdata.x86_64 0:0.252-9.7.el7 itstool.noarch 0:2.0.2-1.el7 jasper-libs.x86_64 0:1.900.1-33.el7 jbigkit-libs.x86_64 0:2.0-11.el7 less.x86_64 0:458-9.el7 libX11.x86_64 0:1.6.7-4.el7_9 libX11-common.noarch 0:1.6.7-4.el7_9 libX11-devel.x86_64 0:1.6.7-4.el7_9 libXau.x86_64 0:1.0.8-2.1.el7 libXau-devel.x86_64 0:1.0.8-2.1.el7 libXcomposite.x86_64 0:0.4.4-4.1.el7 libXcomposite-devel.x86_64 0:0.4.4-4.1.el7 libXcursor.x86_64 0:1.1.15-1.el7 libXcursor-devel.x86_64 0:1.1.15-1.el7 libXdamage.x86_64 0:1.1.4-4.1.el7 libXdamage-devel.x86_64 0:1.1.4-4.1.el7 libXext.x86_64 0:1.3.3-3.el7 libXext-devel.x86_64 0:1.3.3-3.el7 libXfixes.x86_64 0:5.0.3-1.el7 libXfixes-devel.x86_64 0:5.0.3-1.el7 libXft.x86_64 0:2.3.2-2.el7 libXft-devel.x86_64 0:2.3.2-2.el7 libXi.x86_64 0:1.7.9-1.el7 libXi-devel.x86_64 0:1.7.9-1.el7 libXinerama.x86_64 0:1.1.3-2.1.el7 libXinerama-devel.x86_64 0:1.1.3-2.1.el7 libXrandr.x86_64 0:1.5.1-2.el7 libXrandr-devel.x86_64 0:1.5.1-2.el7 libXrender.x86_64 0:0.9.10-1.el7 libXrender-devel.x86_64 0:0.9.10-1.el7 libXxf86vm.x86_64 0:1.1.4-1.el7 libXxf86vm-devel.x86_64 0:1.1.4-1.el7 libappindicator.x86_64 0:12.10.0-13.el7 libcroco.x86_64 0:0.6.12-6.el7_9 libdbusmenu.x86_64 0:16.04.0-4.el7 libdbusmenu-devel.x86_64 0:16.04.0-4.el7 libdbusmenu-gtk2.x86_64 0:16.04.0-4.el7 libdrm.x86_64 0:2.4.97-2.el7 libdrm-devel.x86_64 0:2.4.97-2.el7 libedit.x86_64 0:3.0-12.20121213cvs.el7 libglvnd.x86_64 1:1.0.1-0.8.git5baa1e5.el7 libglvnd-core-devel.x86_64 1:1.0.1-0.8.git5baa1e5.el7 libglvnd-devel.x86_64 1:1.0.1-0.8.git5baa1e5.el7 libglvnd-egl.x86_64 1:1.0.1-0.8.git5baa1e5.el7 libglvnd-gles.x86_64 1:1.0.1-0.8.git5baa1e5.el7 libglvnd-glx.x86_64 1:1.0.1-0.8.git5baa1e5.el7 libglvnd-opengl.x86_64 1:1.0.1-0.8.git5baa1e5.el7 libicu.x86_64 0:50.2-4.el7_7 libicu-devel.x86_64 0:50.2-4.el7_7 libindicator.x86_64 0:12.10.1-6.el7 libjpeg-turbo.x86_64 0:1.2.90-8.el7 libnotify.x86_64 0:0.7.7-1.el7 libpciaccess.x86_64 0:0.14-1.el7 libpng.x86_64 2:1.5.13-8.el7 libpng-devel.x86_64 2:1.5.13-8.el7 libthai.x86_64 0:0.1.14-9.el7 libtiff.x86_64 0:4.0.3-35.el7 libtirpc.x86_64 0:0.2.4-0.16.el7 libtool.x86_64 0:2.4.2-22.el7_3 libunistring.x86_64 0:0.9.3-9.el7 libuuid-devel.x86_64 0:2.23.2-65.el7_9.1 libwayland-client.x86_64 0:1.15.0-1.el7 libwayland-server.x86_64 0:1.15.0-1.el7 libxcb.x86_64 0:1.13-1.el7 libxcb-devel.x86_64 0:1.13-1.el7 libxml2-python.x86_64 0:2.9.1-6.el7_9.6 libxshmfence.x86_64 0:1.2-1.el7 m4.x86_64 0:1.4.16-10.el7 mailcap.noarch 0:2.1.41-2.el7 mallard-rng.noarch 0:1.0.2-1.el7 mesa-khr-devel.x86_64 0:18.3.4-12.el7_9 mesa-libEGL.x86_64 0:18.3.4-12.el7_9 mesa-libEGL-devel.x86_64 0:18.3.4-12.el7_9 mesa-libGL.x86_64 0:18.3.4-12.el7_9 mesa-libGL-devel.x86_64 0:18.3.4-12.el7_9 mesa-libgbm.x86_64 0:18.3.4-12.el7_9 mesa-libglapi.x86_64 0:18.3.4-12.el7_9 mozjs17.x86_64 0:17.0.0-20.el7 openssh.x86_64 0:7.4p1-22.el7_9 openssh-clients.x86_64 0:7.4p1-22.el7_9 openssl.x86_64 1:1.0.2k-25.el7_9 pango.x86_64 0:1.42.4-4.el7_7 pango-devel.x86_64 0:1.42.4-4.el7_7 pcre-devel.x86_64 0:8.32-17.el7 perl-Business-ISBN.noarch 0:2.06-2.el7 perl-Business-ISBN-Data.noarch 0:20120719.001-2.el7 perl-CGI.noarch 0:3.63-4.el7 perl-Compress-Raw-Bzip2.x86_64 0:2.061-3.el7 perl-Compress-Raw-Zlib.x86_64 1:2.061-4.el7 perl-Convert-BinHex.noarch 0:1.119-20.el7 perl-Data-Dumper.x86_64 0:2.145-3.el7 perl-Data-OptList.noarch 0:0.107-9.el7 perl-Devel-GlobalDestruction.noarch 0:0.12-1.el7 perl-Digest.noarch 0:1.17-245.el7 perl-Digest-HMAC.noarch 0:1.03-5.el7 perl-Digest-MD5.x86_64 0:2.52-3.el7 perl-Digest-SHA.x86_64 1:5.85-4.el7 perl-Digest-SHA1.x86_64 0:2.13-9.el7 perl-Digest-SHA3.x86_64 0:0.24-1.el7 perl-Email-Date-Format.noarch 0:1.002-15.el7 perl-Email-Simple.noarch 0:2.214-1.el7 perl-Encode-Locale.noarch 0:1.03-5.el7 perl-Error.noarch 1:0.17020-2.el7 perl-FCGI.x86_64 1:0.74-8.el7 perl-File-FcntlLock.x86_64 0:0.22-6.el7 perl-File-Listing.noarch 0:6.04-7.el7 perl-File-Remove.noarch 0:1.52-6.el7 perl-Font-AFM.noarch 0:1.20-13.el7 perl-Font-TTF.noarch 0:1.02-3.el7 perl-Git.noarch 0:1.8.3.1-23.el7_8 perl-HTML-Format.noarch 0:2.10-7.el7 perl-HTML-Parser.x86_64 0:3.71-4.el7 perl-HTML-Tagset.noarch 0:3.20-15.el7 perl-HTML-Tree.noarch 1:5.03-2.el7 perl-HTTP-Cookies.noarch 0:6.01-5.el7 perl-HTTP-Daemon.noarch 0:6.01-8.el7 perl-HTTP-Date.noarch 0:6.02-8.el7 perl-HTTP-Message.noarch 0:6.06-6.el7 perl-HTTP-Negotiate.noarch 0:6.01-5.el7 perl-IO-Compress.noarch 0:2.061-2.el7 perl-IO-HTML.noarch 0:1.00-2.el7 perl-IO-Socket-IP.noarch 0:0.21-5.el7 perl-IO-Socket-SSL.noarch 0:1.94-7.el7 perl-IO-String.noarch 0:1.08-19.el7 perl-IO-stringy.noarch 0:2.110-22.el7 perl-Image-ExifTool.noarch 0:12.38-1.el7 perl-LWP-MediaTypes.noarch 0:6.02-2.el7 perl-MIME-Lite.noarch 0:3.030-1.el7 perl-MIME-Types.noarch 0:1.38-2.el7 perl-MIME-tools.noarch 0:5.505-1.el7 perl-Mail-Box.noarch 0:2.120-2.el7 perl-Mail-IMAPClient.noarch 0:3.37-1.el7 perl-Mail-Sendmail.noarch 0:0.79-21.el7 perl-Mail-Transport-Dbx.x86_64 0:0.07-28.el7 perl-MailTools.noarch 0:2.12-2.el7 perl-Mozilla-CA.noarch 0:20130114-5.el7 perl-Net-HTTP.noarch 0:6.06-2.el7 perl-Net-LibIDN.x86_64 0:0.12-15.el7 perl-Net-SMTP-SSL.noarch 0:1.01-13.el7 perl-Net-SSLeay.x86_64 0:1.55-6.el7 perl-Object-Realize-Later.noarch 0:0.19-6.el7 perl-Package-Generator.noarch 0:0.103-14.el7 perl-Params-Util.x86_64 0:1.07-6.el7 perl-Parse-RecDescent.noarch 0:1.967009-5.el7 perl-Regexp-Assemble.noarch 0:0.35-11.el7 perl-Sub-Exporter.noarch 0:0.986-2.el7 perl-Sub-Exporter-Progressive.noarch 0:0.001011-1.el7 perl-Sub-Install.noarch 0:0.926-6.el7 perl-TeX-Hyphen.noarch 0:1.01-1.el7 perl-TermReadKey.x86_64 0:2.30-20.el7 perl-Test-Harness.noarch 0:3.28-3.el7 perl-Text-Autoformat.noarch 0:1.669004-1.el7 perl-Text-CharWidth.x86_64 0:0.04-18.el7 perl-Text-Iconv.x86_64 0:1.7-18.el7 perl-Text-Reform.noarch 0:1.20-9.el7 perl-Text-WrapI18N.noarch 0:0.06-17.el7 perl-Time-Piece.x86_64 0:1.20.1-299.el7_9 perl-TimeDate.noarch 1:2.30-2.el7 perl-URI.noarch 0:1.60-9.el7 perl-User-Identity.noarch 0:0.96-1.el7 perl-WWW-RobotRules.noarch 0:6.02-5.el7 perl-XML-Parser.x86_64 0:2.41-10.el7 perl-autodie.noarch 0:2.16-2.el7 perl-gettext.x86_64 0:1.05-28.el7 perl-libwww-perl.noarch 0:6.05-2.el7 pixman.x86_64 0:0.34.0-1.el7 pixman-devel.x86_64 0:0.34.0-1.el7 po-debconf.noarch 0:1.0.20-5.el7 polkit.x86_64 0:0.112-26.el7_9.1 polkit-pkla-compat.x86_64 0:0.1-4.el7 psmisc.x86_64 0:22.20-17.el7 python.x86_64 0:2.7.5-92.el7_9 python3.x86_64 0:3.6.8-18.el7 python3-html2text.noarch 0:2019.9.26-3.el7 python3-libs.x86_64 0:3.6.8-18.el7 python3-pip.noarch 0:9.0.3-8.el7 python3-setuptools.noarch 0:39.2.0-10.el7 rsync.x86_64 0:3.1.2-10.el7 unique.x86_64 0:1.1.6-10.el7 xml-common.noarch 0:0.6.3-39.el7 xorg-x11-proto-devel.noarch 0:2018.4-1.el7 xz-devel.x86_64 0:5.2.2-2.el7_9 xz-lzma-compat.x86_64 0:5.2.2-2.el7_9 yelp-tools.noarch 0:3.28.0-1.el7 yelp-xsl.noarch 0:3.28.0-1.el7 zlib-devel.x86_64 0:1.2.7-20.el7_9 Complete! Finish: build setup for alarm-clock-master-1.el7.src.rpm Start: rpmbuild alarm-clock-master-1.el7.src.rpm Building target platforms: x86_64 Building for target x86_64 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.wZ75b6 + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf alarm-clock-master + /usr/bin/unzip -qq /builddir/build/SOURCES/master.zip + STATUS=0 + '[' 0 -ne 0 ']' + cd alarm-clock-master + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.q2QMlp + umask 022 + cd /builddir/build/BUILD + cd alarm-clock-master + ./autogen.sh /usr/bin/gnome-autogen.sh ***Warning*** PKG_NAME is deprecated, you may remove it from autogen.sh checking for automake >= 1.9... testing automake... found 1.13.4 checking for autoreconf >= 2.53... testing autoreconf... found 2.69 checking for glib-gettext >= 2.2.0... testing glib-gettextize... found 2.56.1 checking for intltool >= 0.40.0... testing intltoolize... found 0.50.2 checking for pkg-config >= 0.14.0... testing pkg-config... found 0.27.1 Checking for required M4 macros... **Warning**: I am going to run `configure' with no arguments. If you wish to pass any to it, please specify them on the `./autogen.sh' command line. Processing ./configure.ac Running glib-gettextize... Ignore non-fatal messages. Copying file po/Makefile.in.in Please add the files codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 progtest.m4 from the /usr/share/aclocal directory to your autoconf macro directory or directly to your aclocal.m4 file. You will also need config.guess and config.sub, which you can get from ftp://ftp.gnu.org/pub/gnu/config/. Running intltoolize... Running autoreconf... autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force --warnings=no-portability configure.ac:42: warning: AC_PROG_CC was called before AX_CHECK_ENABLE_DEBUG /usr/share/aclocal/ax_check_enable_debug.m4:47: AX_CHECK_ENABLE_DEBUG is expanded from... /usr/share/aclocal/gnome-common.m4:6: GNOME_DEBUG_CHECK is expanded from... configure.ac:42: the top level autoreconf: configure.ac: tracing configure.ac:42: warning: AC_PROG_CC was called before AX_CHECK_ENABLE_DEBUG aclocal.m4:69: AX_CHECK_ENABLE_DEBUG is expanded from... aclocal.m4:685: GNOME_DEBUG_CHECK is expanded from... configure.ac:42: the top level autoreconf: configure.ac: not using Libtool autoreconf: running: /usr/bin/autoconf --force --warnings=no-portability configure.ac:42: warning: AC_PROG_CC was called before AX_CHECK_ENABLE_DEBUG aclocal.m4:69: AX_CHECK_ENABLE_DEBUG is expanded from... aclocal.m4:685: GNOME_DEBUG_CHECK is expanded from... configure.ac:42: the top level autoreconf: running: /usr/bin/autoheader --force --warnings=no-portability configure.ac:42: warning: AC_PROG_CC was called before AX_CHECK_ENABLE_DEBUG aclocal.m4:69: AX_CHECK_ENABLE_DEBUG is expanded from... aclocal.m4:685: GNOME_DEBUG_CHECK is expanded from... configure.ac:42: the top level autoreconf: running: automake --add-missing --copy --force-missing --warnings=no-portability configure.ac:42: warning: AC_PROG_CC was called before AX_CHECK_ENABLE_DEBUG aclocal.m4:69: AX_CHECK_ENABLE_DEBUG is expanded from... aclocal.m4:685: GNOME_DEBUG_CHECK is expanded from... configure.ac:42: the top level configure.ac:19: installing './install-sh' configure.ac:19: installing './missing' src/Makefile.am: installing './depcomp' autoreconf: Leaving directory `.' Running ./configure --enable-maintainer-mode ... checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether to enable maintainer-specific portions of Makefiles... yes checking whether make supports nested variables... (cached) yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 ./configure: line 4048: GNOME_COMMON_INIT: command not found checking whether to enable debugging... no checking whether gcc understands -Wall... yes checking whether gcc understands -Wstrict-prototypes... yes checking whether gcc understands -Wnested-externs... yes checking whether gcc understands -Werror=missing-prototypes... yes checking whether gcc understands -Werror=implicit-function-declaration... yes checking whether gcc understands -Werror=pointer-arith... yes checking whether gcc understands -Werror=init-self... yes checking whether gcc understands -Werror=format-security... no checking whether gcc understands -Werror=format=2... yes checking whether gcc understands -Werror=missing-include-dirs... yes checking whether gcc understands -Werror=return-type... yes checking what warning flags to pass to the C compiler... -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format=2 -Werror=missing-include-dirs -Werror=return-type checking what language compliance flags to pass to the C compiler... checking for BASE... yes checking for GTK... yes checking for GSTREAMER... yes checking for GNOME... yes checking for gconftool-2... /usr/bin/gconftool-2 Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation Using $(sysconfdir)/gconf/schemas as install directory for schema files checking for LIBNOTIFY_0_7... yes checking for APP_INDICATOR... yes checking whether NLS is requested... yes checking for intltool >= 0.40.0... 0.50.2 found checking for intltool-update... /usr/bin/intltool-update checking for intltool-merge... /usr/bin/intltool-merge checking for intltool-extract... /usr/bin/intltool-extract checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for perl... /usr/bin/perl checking for perl >= 5.8.1... 5.16.3 checking for XML::Parser... ok checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking for CFPreferencesCopyAppValue... no checking for CFLocaleCopyCurrent... no checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... yes checking for dgettext in libc... yes checking for bind_textdomain_codeset... yes checking for msgfmt... (cached) /usr/bin/msgfmt checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... (cached) /usr/bin/msgfmt checking for xgettext... (cached) /usr/bin/xgettext checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating src/tests/Makefile config.status: creating data/Makefile config.status: creating data/icons/Makefile config.status: creating po/Makefile.in config.status: creating config.h config.status: executing depfiles commands config.status: executing default-1 commands config.status: executing po/stamp-it commands ************************************************* alarm-clock 0.3.4 Configure summary: prefix: /usr/local source code location: . application indicators: yes ************************************************* Now type `make' to compile alarm-clock + autoconf -i configure.ac:42: warning: AC_PROG_CC was called before AX_CHECK_ENABLE_DEBUG aclocal.m4:69: AX_CHECK_ENABLE_DEBUG is expanded from... aclocal.m4:685: GNOME_DEBUG_CHECK is expanded from... configure.ac:42: the top level + CFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic' + export CFLAGS + CXXFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic' + export CXXFLAGS + FFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -I/usr/lib64/gfortran/modules' + export FFLAGS + FCFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -I/usr/lib64/gfortran/modules' + export FCFLAGS + LDFLAGS='-Wl,-z,relro ' + export LDFLAGS + '[' 1 == 1 ']' + '[' x86_64 == ppc64le ']' ++ find . -name config.guess -o -name config.sub + ./configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether to enable maintainer-specific portions of Makefiles... yes checking whether make supports nested variables... (cached) yes checking for x86_64-redhat-linux-gnu-pkg-config... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for x86_64-redhat-linux-gnu-gcc... no checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... none ./configure: line 4048: GNOME_COMMON_INIT: command not found checking whether to enable debugging... no checking whether gcc understands -Wall... yes checking whether gcc understands -Wstrict-prototypes... yes checking whether gcc understands -Wnested-externs... yes checking whether gcc understands -Werror=missing-prototypes... yes checking whether gcc understands -Werror=implicit-function-declaration... yes checking whether gcc understands -Werror=pointer-arith... yes checking whether gcc understands -Werror=init-self... yes checking whether gcc understands -Werror=format-security... yes checking whether gcc understands -Werror=format=2... yes checking whether gcc understands -Werror=missing-include-dirs... yes checking whether gcc understands -Werror=return-type... yes checking what warning flags to pass to the C compiler... -Wall -Wstrict-prototypes -Wnested-externs -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=pointer-arith -Werror=init-self -Werror=format-security -Werror=format=2 -Werror=missing-include-dirs -Werror=return-type checking what language compliance flags to pass to the C compiler... checking for BASE... yes checking for GTK... yes checking for GSTREAMER... yes checking for GNOME... yes checking for gconftool-2... /usr/bin/gconftool-2 Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation Using $(sysconfdir)/gconf/schemas as install directory for schema files checking for LIBNOTIFY_0_7... yes checking for APP_INDICATOR... yes checking whether NLS is requested... yes checking for intltool >= 0.40.0... 0.50.2 found checking for intltool-update... /usr/bin/intltool-update checking for intltool-merge... /usr/bin/intltool-merge checking for intltool-extract... /usr/bin/intltool-extract checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for perl... /usr/bin/perl checking for perl >= 5.8.1... 5.16.3 checking for XML::Parser... ok checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking for CFPreferencesCopyAppValue... no checking for CFLocaleCopyCurrent... no checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... yes checking for dgettext in libc... yes checking for bind_textdomain_codeset... yes checking for msgfmt... (cached) /usr/bin/msgfmt checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... (cached) /usr/bin/msgfmt checking for xgettext... (cached) /usr/bin/xgettext checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating src/tests/Makefile config.status: creating data/Makefile config.status: creating data/icons/Makefile config.status: creating po/Makefile.in config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands config.status: executing default-1 commands config.status: executing po/stamp-it commands ************************************************* alarm-clock 0.3.4 Configure summary: prefix: /usr source code location: . application indicators: yes ************************************************* + make -j2 make all-recursive make[1]: Entering directory `/builddir/build/BUILD/alarm-clock-master' Making all in src make[2]: Entering directory `/builddir/build/BUILD/alarm-clock-master/src' Making all in tests make[3]: Entering directory `/builddir/build/BUILD/alarm-clock-master/src/tests' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/src/tests' make[3]: Entering directory `/builddir/build/BUILD/alarm-clock-master/src' CC alarm-applet.o CC player.o CC util.o In file included from /usr/include/gtk-2.0/gtk/gtk.h:234:0, from alarm-applet.h:32, from alarm-applet.c:26: /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] typedef void (*GtkItemFactoryCallback) (); ^ alarm-applet.c: In function 'unique_app_message_cb': alarm-applet.c:552:9: warning: case value '1' not in enumerated type 'UniqueCommand' [-Wswitch] case UNIQUE_STOP_ALL: ^ alarm-applet.c:557:9: warning: case value '2' not in enumerated type 'UniqueCommand' [-Wswitch] case UNIQUE_SNOOZE_ALL: ^ CC list-entry.o CC alarm.o In file included from /usr/include/gtk-2.0/gtk/gtk.h:234:0, from list-entry.c:26: /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] typedef void (*GtkItemFactoryCallback) (); ^ alarm.c: In function 'alarm_repeat_to_pretty': alarm.c:2008:9: warning: case value '62' not in enumerated type 'AlarmRepeat' [-Wswitch] case ALARM_REPEAT_WEEKDAYS: ^ alarm.c:2011:9: warning: case value '65' not in enumerated type 'AlarmRepeat' [-Wswitch] case ALARM_REPEAT_WEEKENDS: ^ alarm.c:2014:9: warning: case value '127' not in enumerated type 'AlarmRepeat' [-Wswitch] case ALARM_REPEAT_ALL: ^ CC alarm-gconf.o In file included from /usr/include/gtk-2.0/gtk/gtk.h:234:0, from alarm-applet.h:32, from alarm-gconf.c:26: /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] typedef void (*GtkItemFactoryCallback) (); ^ CC ui.o CC alarm-actions.o In file included from /usr/include/gtk-2.0/gtk/gtk.h:234:0, from alarm-applet.h:32, from ui.c:28: /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] typedef void (*GtkItemFactoryCallback) (); ^ In file included from /usr/include/gtk-2.0/gtk/gtk.h:234:0, from alarm-applet.h:32, from alarm-actions.h:28, from alarm-actions.c:24: /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] typedef void (*GtkItemFactoryCallback) (); ^ CC alarm-list-window.o CC alarm-settings.o In file included from /usr/include/gtk-2.0/gtk/gtk.h:234:0, from alarm-list-window.h:27, from alarm-list-window.c:26: /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] typedef void (*GtkItemFactoryCallback) (); ^ In file included from /usr/include/gtk-2.0/gtk/gtk.h:234:0, from alarm-applet.h:32, from alarm-settings.h:32, from alarm-settings.c:24: /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] typedef void (*GtkItemFactoryCallback) (); ^ CC prefs.o In file included from /usr/include/gtk-2.0/gtk/gtk.h:234:0, from alarm-applet.h:32, from prefs.h:27, from prefs.c:28: /usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] typedef void (*GtkItemFactoryCallback) (); ^ prefs.c:129:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] prefs_autostart_get_current () ^ prefs.c:219:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] prefs_create_autostart_user_file() ^ CCLD alarm-clock-applet make[3]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/src' make[2]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/src' Making all in data make[2]: Entering directory `/builddir/build/BUILD/alarm-clock-master/data' Making all in icons make[3]: Entering directory `/builddir/build/BUILD/alarm-clock-master/data/icons' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/data/icons' make[3]: Entering directory `/builddir/build/BUILD/alarm-clock-master/data' ITMRG alarm-clock-applet.desktop ITMRG alarm-clock.schemas make[3]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/data' make[2]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/data' Making all in po make[2]: Entering directory `/builddir/build/BUILD/alarm-clock-master/po' MSGFMT ar.gmo MSGFMT ast.gmo MSGFMT be.gmo MSGFMT bg.gmo MSGFMT ca.gmo MSGFMT cs.gmo MSGFMT da.gmo MSGFMT de.gmo MSGFMT es.gmo MSGFMT et.gmo MSGFMT fi.gmo MSGFMT fo.gmo MSGFMT fr.gmo MSGFMT gl.gmo MSGFMT he.gmo MSGFMT hi.gmo MSGFMT hu.gmo MSGFMT id.gmo MSGFMT it.gmo MSGFMT ja.gmo MSGFMT ka.gmo MSGFMT la.gmo MSGFMT ms.gmo MSGFMT nb.gmo MSGFMT nl.gmo MSGFMT nn.gmo MSGFMT pl.gmo MSGFMT pt_BR.gmo MSGFMT pt.gmo MSGFMT ru.gmo MSGFMT si.gmo MSGFMT sv.gmo MSGFMT tr.gmo MSGFMT uk.gmo MSGFMT zh_CN.gmo MSGFMT zh_TW.gmo make[2]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/po' make[2]: Entering directory `/builddir/build/BUILD/alarm-clock-master' make[2]: Leaving directory `/builddir/build/BUILD/alarm-clock-master' make[1]: Leaving directory `/builddir/build/BUILD/alarm-clock-master' + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.Kuxqvb + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64 ++ dirname /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64 + cd alarm-clock-master + rm -rf /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64 + /usr/bin/make install DESTDIR=/builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64 Making install in src make[1]: Entering directory `/builddir/build/BUILD/alarm-clock-master/src' Making install in tests make[2]: Entering directory `/builddir/build/BUILD/alarm-clock-master/src/tests' make[3]: Entering directory `/builddir/build/BUILD/alarm-clock-master/src/tests' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/src/tests' make[2]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/src/tests' make[2]: Entering directory `/builddir/build/BUILD/alarm-clock-master/src' make[3]: Entering directory `/builddir/build/BUILD/alarm-clock-master/src' /usr/bin/mkdir -p '/builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/bin' /usr/bin/install -c alarm-clock-applet '/builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/bin' make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/src' make[2]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/src' make[1]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/src' Making install in data make[1]: Entering directory `/builddir/build/BUILD/alarm-clock-master/data' Making install in icons make[2]: Entering directory `/builddir/build/BUILD/alarm-clock-master/data/icons' make[3]: Entering directory `/builddir/build/BUILD/alarm-clock-master/data/icons' make[3]: Nothing to be done for `install-exec-am'. for icon in alarm-clock.svg alarm-clock.16.png alarm-clock.22.png alarm-clock.24.png alarm-clock.32.png alarm-clock.36.png alarm-clock.48.png alarm-clock.64.png alarm-timer.svg alarm-timer.16.png alarm-timer.22.png alarm-timer.24.png alarm-timer.32.png alarm-timer.36.png alarm-timer.48.png alarm-timer.64.png alarm-clock-triggered.16.png alarm-clock-triggered.22.png alarm-clock-triggered.24.png alarm-clock-triggered.32.png alarm-clock-triggered.36.png alarm-clock-triggered.48.png alarm-clock-triggered.64.png ; do \ SIZE=`basename $icon | cut -d. -f2`; \ FILE=`basename $icon | cut -d. -f1,3`; \ if [ "$SIZE" = "svg" ]; then \ SIZE="scalable"; \ FILE="$FILE.svg"; \ else \ SIZE="${SIZE}x${SIZE}"; \ fi; \ mkdir -p /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/icons/hicolor/$SIZE/apps/; \ /usr/bin/install -c -m 644 ./$icon /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/icons/hicolor/$SIZE/apps/$FILE; \ done *** Icon cache not updated. After (un)install, run this: *** gtk-update-icon-cache -f -t /usr/share/icons/hicolor make[3]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/data/icons' make[2]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/data/icons' make[2]: Entering directory `/builddir/build/BUILD/alarm-clock-master/data' make[3]: Entering directory `/builddir/build/BUILD/alarm-clock-master/data' make[3]: Nothing to be done for `install-exec-am'. GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults \ /usr/bin/gconftool-2 --makefile-install-rule alarm-clock.schemas 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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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_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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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_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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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/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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 /usr/bin/mkdir -p '/builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/applications' /usr/bin/install -c -m 644 alarm-clock-applet.desktop '/builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/applications' /usr/bin/mkdir -p '/builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/etc/gconf/schemas' /usr/bin/install -c -m 644 alarm-clock.schemas '/builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/etc/gconf/schemas' /usr/bin/mkdir -p '/builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/alarm-clock-applet' /usr/bin/install -c -m 644 alarm-clock.ui '/builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/alarm-clock-applet' make[3]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/data' make[2]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/data' make[1]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/data' Making install in po make[1]: Entering directory `/builddir/build/BUILD/alarm-clock-master/po' linguas="ar ast be bg ca cs da de es et fi fo fr gl he hi hu id it ja ka la ms nb nl nn pl pt_BR pt ru si sv tr uk zh_CN zh_TW "; \ for lang in $linguas; do \ dir=/builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/$lang/LC_MESSAGES; \ /bin/sh /builddir/build/BUILD/alarm-clock-master/install-sh -d $dir; \ if test -r $lang.gmo; then \ /usr/bin/install -c -m 644 $lang.gmo $dir/alarm-clock-applet.mo; \ echo "installing $lang.gmo as $dir/alarm-clock-applet.mo"; \ else \ /usr/bin/install -c -m 644 ./$lang.gmo $dir/alarm-clock-applet.mo; \ echo "installing ./$lang.gmo as" \ "$dir/alarm-clock-applet.mo"; \ fi; \ if test -r $lang.gmo.m; then \ /usr/bin/install -c -m 644 $lang.gmo.m $dir/alarm-clock-applet.mo.m; \ echo "installing $lang.gmo.m as $dir/alarm-clock-applet.mo.m"; \ else \ if test -r ./$lang.gmo.m ; then \ /usr/bin/install -c -m 644 ./$lang.gmo.m \ $dir/alarm-clock-applet.mo.m; \ echo "installing ./$lang.gmo.m as" \ "$dir/alarm-clock-applet.mo.m"; \ else \ true; \ fi; \ fi; \ done installing ar.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/ar/LC_MESSAGES/alarm-clock-applet.mo installing ast.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/ast/LC_MESSAGES/alarm-clock-applet.mo installing be.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/be/LC_MESSAGES/alarm-clock-applet.mo installing bg.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/bg/LC_MESSAGES/alarm-clock-applet.mo installing ca.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/ca/LC_MESSAGES/alarm-clock-applet.mo installing cs.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/cs/LC_MESSAGES/alarm-clock-applet.mo installing da.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/da/LC_MESSAGES/alarm-clock-applet.mo installing de.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/de/LC_MESSAGES/alarm-clock-applet.mo installing es.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/es/LC_MESSAGES/alarm-clock-applet.mo installing et.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/et/LC_MESSAGES/alarm-clock-applet.mo installing fi.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/fi/LC_MESSAGES/alarm-clock-applet.mo installing fo.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/fo/LC_MESSAGES/alarm-clock-applet.mo installing fr.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/fr/LC_MESSAGES/alarm-clock-applet.mo installing gl.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/gl/LC_MESSAGES/alarm-clock-applet.mo installing he.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/he/LC_MESSAGES/alarm-clock-applet.mo installing hi.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/hi/LC_MESSAGES/alarm-clock-applet.mo installing hu.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/hu/LC_MESSAGES/alarm-clock-applet.mo installing id.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/id/LC_MESSAGES/alarm-clock-applet.mo installing it.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/it/LC_MESSAGES/alarm-clock-applet.mo installing ja.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/ja/LC_MESSAGES/alarm-clock-applet.mo installing ka.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/ka/LC_MESSAGES/alarm-clock-applet.mo installing la.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/la/LC_MESSAGES/alarm-clock-applet.mo installing ms.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/ms/LC_MESSAGES/alarm-clock-applet.mo installing nb.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/nb/LC_MESSAGES/alarm-clock-applet.mo installing nl.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/nl/LC_MESSAGES/alarm-clock-applet.mo installing nn.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/nn/LC_MESSAGES/alarm-clock-applet.mo installing pl.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/pl/LC_MESSAGES/alarm-clock-applet.mo installing pt_BR.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/pt_BR/LC_MESSAGES/alarm-clock-applet.mo installing pt.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/pt/LC_MESSAGES/alarm-clock-applet.mo installing ru.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/ru/LC_MESSAGES/alarm-clock-applet.mo installing si.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/si/LC_MESSAGES/alarm-clock-applet.mo installing sv.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/sv/LC_MESSAGES/alarm-clock-applet.mo installing tr.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/tr/LC_MESSAGES/alarm-clock-applet.mo installing uk.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/uk/LC_MESSAGES/alarm-clock-applet.mo installing zh_CN.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/zh_CN/LC_MESSAGES/alarm-clock-applet.mo installing zh_TW.gmo as /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/locale/zh_TW/LC_MESSAGES/alarm-clock-applet.mo make[1]: Leaving directory `/builddir/build/BUILD/alarm-clock-master/po' make[1]: Entering directory `/builddir/build/BUILD/alarm-clock-master' make[2]: Entering directory `/builddir/build/BUILD/alarm-clock-master' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/builddir/build/BUILD/alarm-clock-master' make[1]: Leaving directory `/builddir/build/BUILD/alarm-clock-master' + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/alarm-clock-master extracting debug info from /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/bin/alarm-clock-applet dwz: Too few files for multifile optimization /usr/lib/rpm/sepdebugcrcfix: Updated 1 CRC32s, 0 CRC32s did match. 399 blocks + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-compress + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1 + /usr/lib/rpm/redhat/brp-python-hardlink + /usr/lib/rpm/redhat/brp-java-repack-jars Processing files: alarm-clock-master-1.el7.x86_64 Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.OxQe7Z + umask 022 + cd /builddir/build/BUILD + cd alarm-clock-master + DOCDIR=/builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/doc/alarm-clock-master + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/doc/alarm-clock-master + cp -pr AUTHORS /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/doc/alarm-clock-master + cp -pr ChangeLog /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/doc/alarm-clock-master + cp -pr COPYING /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/doc/alarm-clock-master + cp -pr NEWS /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/doc/alarm-clock-master + cp -pr README /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64/usr/share/doc/alarm-clock-master + exit 0 Provides: alarm-clock = master-1.el7 alarm-clock(x86-64) = master-1.el7 application() application(alarm-clock-applet.desktop) Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: libappindicator.so.1()(64bit) libatk-1.0.so.0()(64bit) libc.so.6()(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.4)(64bit) libc.so.6(GLIBC_2.7)(64bit) libcairo.so.2()(64bit) libdbusmenu-glib.so.4()(64bit) libfontconfig.so.1()(64bit) libfreetype.so.6()(64bit) libgconf-2.so.4()(64bit) libgdk-x11-2.0.so.0()(64bit) libgdk_pixbuf-2.0.so.0()(64bit) libgio-2.0.so.0()(64bit) libglib-2.0.so.0()(64bit) libgmodule-2.0.so.0()(64bit) libgobject-2.0.so.0()(64bit) libgstreamer-1.0.so.0()(64bit) libgtk-x11-2.0.so.0()(64bit) libnotify.so.4()(64bit) libpango-1.0.so.0()(64bit) libpangocairo-1.0.so.0()(64bit) libpangoft2-1.0.so.0()(64bit) libpthread.so.0()(64bit) libunique-1.0.so.0()(64bit) libxml2.so.2()(64bit) libxml2.so.2(LIBXML2_2.4.30)(64bit) rtld(GNU_HASH) Processing files: alarm-clock-debuginfo-master-1.el7.x86_64 Provides: alarm-clock-debuginfo = master-1.el7 alarm-clock-debuginfo(x86-64) = master-1.el7 Requires(rpmlib): rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64 Wrote: /builddir/build/RPMS/alarm-clock-master-1.el7.x86_64.rpm Wrote: /builddir/build/RPMS/alarm-clock-debuginfo-master-1.el7.x86_64.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.eH0XUs + umask 022 + cd /builddir/build/BUILD + cd alarm-clock-master + /usr/bin/rm -rf /builddir/build/BUILDROOT/alarm-clock-master-1.el7.x86_64 + exit 0 Finish: rpmbuild alarm-clock-master-1.el7.src.rpm Finish: build phase for alarm-clock-master-1.el7.src.rpm INFO: Done(/var/lib/copr-rpmbuild/results/alarm-clock-master-1.el7.src.rpm) Config(child) 0 minutes 44 seconds INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results INFO: Cleaning up build root ('cleanup_on_success=True') Start: clean chroot INFO: unmounting tmpfs. Finish: clean chroot Finish: run Running RPMResults tool