Discuss May 2019

discuss@lists.centos.org

98 participants
72 discussions

JavaFX on C7 ?
by Fred Smith 01 Jun '19

01 Jun '19

Hi all! I'm getting: Error: JavaFX runtime components are missing, and are required to run this application for a certain Java app. I'm hoping someone can tell me what bits and pieces I need to install (and maybe where to find them) so I can satisfy that app's appetite without screwing up my system. Thanks in advance! Fred PS: I see openjfx at openjfx.io. I assume that if this version is appropriate for C7, that I need the one containing the jmods, not the SDK? Again, clues will be much appreciated! -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ---------------------------- Do you not know? Have you not heard? The LORD is the everlasting God, the Creator of the ends of the earth. He will not grow tired or weary, and his understanding no one can fathom. ----------------------------- Isaiah 40:28 (niv) -----------------------------

3 4

does centos 7.6 support TL-WN725N
by qw 01 Jun '19

01 Jun '19

Hi, Does centos 7.6 support TL-WN725N, which is a wireless adaptor? Thanks! Regards Andrew

2 2

CentOS 7, skype ceased functioning
by soko.tica 30 May '19

30 May '19

Hi, I have been using CentOS 7 on a laptop for a while now (about two years), using skypeforlinux all the time. After today's update, skype ceased to start as a service, as it used to be configured. It fails to start manually, e.g., it does start and is listed as a job, but it doesn't appear visible on the desktop. In the case you know something about it, please let us all know. Regards, [brn@hekuba ~]$ uname -a Linux hekuba.home.lan 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

3 4

safety vulnerability in tablet computer
by Mikhail Utin 30 May '19

30 May '19

We discovered safety hardware vulnerability in Samsung tablet computer model SM-T580 16GB SN: R52M20EG5WR – dangerous overheat of the tablet lithium-ion battery caused by short circuit to flash LED, which caused more likely by failed LED controlling hardware. We believe that similar design have other mobile computerized devices utilizing flash LED for digital camera. The computer in question has been in use for only three weeks. The temperature outside of the case was approximately 55C in open space. The LED was shining while the computer was power down. The battery discharged within approximately one hour. There is high degree of risk of overheating and potential fire and/or explosion related to the technology of lithium-ion batteries. In particular, if the device is packed inside of a luggage. Two Samsung companies in the US have been informed, but have not really proposed an investigation claiming high quality of the company products. We also informed TSA in three separate inquires (one to FAA), American Airlines and UK based The Registry news portal. However, considering that a lot of people in CentOS community use tablets and smartphones we decided to inform about existing risks caused by specific design of the hardware and may be firmware as well. Complete information and documents related to this case are on www.rubos.com<http://www.rubos.com>. Mikhail Utin Rubos, Inc.

1 0

UEFI boot manager sequence problems HP Envy
by Gary Stainburn 30 May '19

30 May '19

Morning all, I have a HP Envy dual boot system (Win8 for serious stuff, i.e. Train Sim and Flight Sim) and Centos 7 for everything else. In the past I've had the occasional problem where an update on the windows side has updated the UEFI boot sequence but using efibootmgr has always fixed it. On Friday I discovered that my HDD was failing so I tried using Clonezilla to move it on to a new SSD of the same size. Unfortunately the clone didn't work, failing half way through my main partition. Thankfully the Windows partitions and boot info cloned across so that side of the system worked. I then wiped all the Linux partitions and did a clean C7 install using the latest ISO, all went well, but when it reboot it went straight into Windows. Using F9 on reboot I chose CentOS Linux and the new system booted. Using efibootmgr I reset the boot sequence and all looked fine (see below). Unfortunately, when I then reboot it reverts to booting Windows. Using F9 to get back into Linux then shows that the boot sequence has reverted. This means that the updated sequence either was not stored properly, or something is resetting it. Legacy support in the BIOS is turned off as it should be, and the boot sequence in the BIOS only has a limited number of options. The sequence in the BIOS is: UEFI Boot Order USB Diskette on Key/USB Hard Drive OS boot Manager (shown in white) Internal CD/DVD ROM Drive USB CD/DVD ROM Drive ! Network Adapter Legacy Boot Order Notebook Hard Drive Internal CD/DVD ROM Drive USB Diskette on Key/USB Hard Drive USB CD/DVD ROM Drive ! Network Adapter If I press <F9> I get the same options as in efibootmgr but the first option "Windows Boot Manager" is selected. [root@gary ~]# efibootmgr BootCurrent: 0004 Timeout: 0 seconds BootOrder: 0002,3002,0000,0003,0004,0005,2001,2002,2003 Boot0000* Linux Boot0002* Windows Boot Manager Boot0003* Fedora Boot0004* CentOS Linux Boot0005* CentOS Boot2001* USB Drive (UEFI) Boot2002* Internal CD/DVD ROM Drive (UEFI) Boot3000* Internal Hard Disk or Solid State Disk Boot3002* Internal Hard Disk or Solid State Disk Boot3004* Internal Hard Disk or Solid State Disk [root@gary ~]# efibootmgr -o 0004,2001,2002,3000 BootCurrent: 0004 Timeout: 0 seconds BootOrder: 0004,2001,2002,3000 Boot0000* Linux Boot0002* Windows Boot Manager Boot0003* Fedora Boot0004* CentOS Linux Boot0005* CentOS Boot2001* USB Drive (UEFI) Boot2002* Internal CD/DVD ROM Drive (UEFI) Boot3000* Internal Hard Disk or Solid State Disk Boot3002* Internal Hard Disk or Solid State Disk Boot3004* Internal Hard Disk or Solid State Disk [root@gary ~]# efibootmgr BootCurrent: 0004 Timeout: 0 seconds BootOrder: 0004,2001,2002,3000 Boot0000* Linux Boot0002* Windows Boot Manager Boot0003* Fedora Boot0004* CentOS Linux Boot0005* CentOS Boot2001* USB Drive (UEFI) Boot2002* Internal CD/DVD ROM Drive (UEFI) Boot3000* Internal Hard Disk or Solid State Disk Boot3002* Internal Hard Disk or Solid State Disk Boot3004* Internal Hard Disk or Solid State Disk [root@gary ~]#

3 7

epel repository broken
by Günther J. Niederwimmer 30 May '19

30 May '19

Hello, I have now over two Days this errors on all my systems ? Updateinfo file is not valid XML: <open file '/var/cache/yum/x86_64/7/epel/ 92f2e15cad66d79ea1ad327e2af7af89d98e4d153d7a3e27ff41946f476af5b4- updateinfo.xml.zck', mode 'rt' at 0x7f464cf24420> a "yum clean all" dont't change the Problem! -- mit freundliche Grüßen / best regards, Günther J. Niederwimmer

3 2

CentOS-announce Digest, Vol 171, Issue 7
by centos-announce-request＠centos.org 30 May '19

30 May '19

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2019:1265 Critical CentOS 7 firefox Security Update (Johnny Hughes) 2. CESA-2019:1267 Critical CentOS 6 firefox Security Update (Johnny Hughes) 3. CESA-2019:1264 Important CentOS 7 libvirt Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 29 May 2019 19:47:30 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:1265 Critical CentOS 7 firefox Security Update Message-ID: <20190529194730.GA29248(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:1265 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2019:1265 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 6bf7b0a006db85d0ab1da140a2c48484033cdb242a87f32e47538b1477c7b5a6 firefox-60.7.0-1.el7.centos.i686.rpm 7180cf1102f4ce99f26f90cb19a23c66c1e8700a6756b148f58f9670ab778458 firefox-60.7.0-1.el7.centos.x86_64.rpm Source: fca10b620b7fce1190e8f2bc4ca013fc0729f7b4bd650e3ce2950a8a84db8ce8 firefox-60.7.0-1.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 29 May 2019 19:48:35 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:1267 Critical CentOS 6 firefox Security Update Message-ID: <20190529194835.GA29395(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:1267 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2019:1267 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 41e1920d03ef2d819fb3f6d4aba478231d91f2dc359c9d595afba3bc556e308e firefox-60.7.0-1.el6.centos.i686.rpm x86_64: 41e1920d03ef2d819fb3f6d4aba478231d91f2dc359c9d595afba3bc556e308e firefox-60.7.0-1.el6.centos.i686.rpm 8bcaa85425b5211864e55e0ff15e4f32e5b27eab33c0549fa90ee64c217f93f9 firefox-60.7.0-1.el6.centos.x86_64.rpm Source: eb7bc29e4bca2575c1a396b201c59f1f4f6a8691188e9b50ca0162a4281fb013 firefox-60.7.0-1.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Wed, 29 May 2019 19:55:31 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:1264 Important CentOS 7 libvirt Security Update Message-ID: <20190529195531.GA29956(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:1264 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:1264 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: a5576c9049af0f04106990794428c22802b42066eb0268dedf49e7d6079ca139 libvirt-4.5.0-10.el7_6.10.x86_64.rpm 176beb81864060547751b1f94bec282b9ff4bec6f9cc84f6ad1373a04141af41 libvirt-admin-4.5.0-10.el7_6.10.x86_64.rpm 66300eaeb5cf856c86544468159c42f71bd55464dda0f038422ef95b0089436a libvirt-bash-completion-4.5.0-10.el7_6.10.x86_64.rpm 389cc2129844395d02388d2f4c626b24af8ace55f5c54eb897de49e66537f9bb libvirt-client-4.5.0-10.el7_6.10.i686.rpm bf7e4e5dbffb93cf0c8f94dc44c41ec86b0ef33fb0ce83d4b5b61673e6615d4d libvirt-client-4.5.0-10.el7_6.10.x86_64.rpm 755e93422bc4a24ab6e0052b3b60e6cb0b84177ff79bf0f16c7e96e1b7471b46 libvirt-daemon-4.5.0-10.el7_6.10.x86_64.rpm d6d362b18c78ff212672e74a12540667131adbff047490248b4d2645a72b4a34 libvirt-daemon-config-network-4.5.0-10.el7_6.10.x86_64.rpm 609633c12c439f5cb41c48ecd019b8b7ee8d7e6bfbe0c2ec8c60ca78f120da3f libvirt-daemon-config-nwfilter-4.5.0-10.el7_6.10.x86_64.rpm fb743cfe2b3f6e5038dc2a33808232e9460135c6e8ce20e011148f7fd1d24517 libvirt-daemon-driver-interface-4.5.0-10.el7_6.10.x86_64.rpm 5e3a7320d6424f241882053013f2c1d0de0816cd89e1403a500227d74fbeeb67 libvirt-daemon-driver-lxc-4.5.0-10.el7_6.10.x86_64.rpm 533e8e12942ac647e5cd3f4c6585502dea905657cbc89ae0d25744e944c01c44 libvirt-daemon-driver-network-4.5.0-10.el7_6.10.x86_64.rpm fbacd781e9f1e289bcc1d3fa1bdf5372c75ba3312878a155e2b56be8274e2b54 libvirt-daemon-driver-nodedev-4.5.0-10.el7_6.10.x86_64.rpm d5f23f59942c1e0edb290bdf8d04060a29e45292f09632eb381d876ec6e2de88 libvirt-daemon-driver-nwfilter-4.5.0-10.el7_6.10.x86_64.rpm a3d77aa95864251b29893d6e03fcf365a3084b9154d26b01b2cdb1cc40d4b4c5 libvirt-daemon-driver-qemu-4.5.0-10.el7_6.10.x86_64.rpm 5e6632eea34452631190a52e89eb80949e06df0e202fe275e219d182f02e38a6 libvirt-daemon-driver-secret-4.5.0-10.el7_6.10.x86_64.rpm 085ad9d629fe198a424dbd74c6a9b37f5d0dd3db1aa4c3df55cbb80f926acda2 libvirt-daemon-driver-storage-4.5.0-10.el7_6.10.x86_64.rpm b14ec56f624f0e9ec7e1b0d89c10ba515ef2834b555fbdce6a7ccbe9430f8127 libvirt-daemon-driver-storage-core-4.5.0-10.el7_6.10.x86_64.rpm 7dd044d4d8468cfb84f0e70d78e5647fa2553216ec93c2611eb66bcd75f5995a libvirt-daemon-driver-storage-disk-4.5.0-10.el7_6.10.x86_64.rpm 0c566847c36d56b39fd8da5ee3f148030bae26d4d88debcaddeca3976e665d12 libvirt-daemon-driver-storage-gluster-4.5.0-10.el7_6.10.x86_64.rpm 10f2ed853329034bb99ace3939c83108312c94f20269273981ae8cfa5cd7c2a7 libvirt-daemon-driver-storage-iscsi-4.5.0-10.el7_6.10.x86_64.rpm 6a8020f76287f3275ce77bd229dfff0bbb250ce3ef57cd441140d12e826ddf7d libvirt-daemon-driver-storage-logical-4.5.0-10.el7_6.10.x86_64.rpm d651d40ec0e3a25b494b7fa77b3baac14a2e5f6ea8396f629ee84dee88fc83d3 libvirt-daemon-driver-storage-mpath-4.5.0-10.el7_6.10.x86_64.rpm 0871e70c35d704f95a491342fc07cda7cea8aec4eca9d57f621e87f314ffa12d libvirt-daemon-driver-storage-rbd-4.5.0-10.el7_6.10.x86_64.rpm 8447575086717ff7f2f849a438e5a6c8c4f4880e16d13e7a4e9b2014a4807b1f libvirt-daemon-driver-storage-scsi-4.5.0-10.el7_6.10.x86_64.rpm ceed3bc723b720d88c68797643e6fb630843a07fdcba303ae7a831a83a712943 libvirt-daemon-kvm-4.5.0-10.el7_6.10.x86_64.rpm dfdec791cfe35a65c760107c15bef447fa94519e185bb9f2c681c8caac9fa636 libvirt-daemon-lxc-4.5.0-10.el7_6.10.x86_64.rpm c65c648ef230bcb69868e9cbb7bfe46be2104c31129b4dcec3b88702f9fe7f84 libvirt-devel-4.5.0-10.el7_6.10.i686.rpm eff379405df411eabb2ea4067c891c7971d24d6ef7ee06bae43c7f09c275c09e libvirt-devel-4.5.0-10.el7_6.10.x86_64.rpm 08085811aa8893c3c63734dcca0778ce64155490c8b28da795df5176aa36775b libvirt-docs-4.5.0-10.el7_6.10.x86_64.rpm 70679dead45c2020ed8f5c8108561c4da8f57e7ad6e967d229fde3bdb157a930 libvirt-libs-4.5.0-10.el7_6.10.i686.rpm 9fb2a50456d461b3a17b09f445b6010d196fc1f7c7db3ee01768491d46883c40 libvirt-libs-4.5.0-10.el7_6.10.x86_64.rpm f1caa6ef12649f5b66d38ae8f4ed210d23aabf9d82efaa995ec9f267c8906974 libvirt-lock-sanlock-4.5.0-10.el7_6.10.x86_64.rpm 63f9d3a71d0e5284e3d3b0b951e9cacf209c5742f4acb510a51911f6291fa1b8 libvirt-login-shell-4.5.0-10.el7_6.10.x86_64.rpm 8dbbba481c031154da6a9b565b6a8ef6603498246912b5ce6b328f86931dc61b libvirt-nss-4.5.0-10.el7_6.10.i686.rpm b9b87149ca587933840a6902ceaa2c5e5c06e44ecfb8f2a0ff1679f193e7bf24 libvirt-nss-4.5.0-10.el7_6.10.x86_64.rpm Source: a0cf4841e95f14ecd88c8790013f306de60af534bb4c72355e7b0e2af7c2d68f libvirt-4.5.0-10.el7_6.10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 171, Issue 7 ***********************************************

1 0

Diskless Centos & Cgroup config changes
by Rory Falloon 29 May '19

29 May '19

Hi, I have OS 'image' that boots via PXE and mounts over NFS. (7.5.1804). I am wanting to explore allowing cgroup usage on this configuration. The root image is exported read-only over NFS and am using statetab & rwtab to allow some persistent parts of the filesystem as well as read/write where needed. I have tried setting /sys in the statetab and this causes the machine to fail, as I have tried /sys in the rwtab. The latter increases the boot time to a point which is not usable. Trying /sys/fs/cgroup in rwtab seems to improve boot time but also causes the machine not to complete booting. I had some more success using cgconfig.conf, I was able to mount the memory cgroup to a local disk (each node has a local temp disk) and manipulate this using cgcreate but the cpu would not mount in the same fashion; the error was: Error: cannot mount cpu to /var/tmp/cgroup/cpu: Device or resource busy So my question; in this particular environment, is how best to utilize cgroup if I want control over both cpu and mem? Is it possible with a read-only root image? Thanks,

1 0

Updateinfo file is not valid XML
by Nicolas Kovacs 29 May '19

29 May '19

Hi, Since last night, all my servers spew out the following error when trying to run an update, either via yum-cron or manually: # yum check-update Loaded plugins: fastestmirror, priorities Determining fastest mirrors ... 194 packages excluded due to repository priority protections Updateinfo file is not valid XML: <open file '/var/cache/yum/x86_64/7/epel/92f2e15cad66d79ea1ad327e2af7af89d98e4d153d7a3e27ff41946f476af5b4-updateinfo.xml.zck', mode 'rt' at 0x7fbd0e3e2f60> Any idea what's going on here? Something rotten in the state of EPEL? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

2 1

upgrade to kernel 4.19.43 fail.
by Allan 29 May '19

29 May '19

Hi all... I just upgraded to laatest kernel in experimental from 4.19.40 , and for my OpenCL app this now fails with this msg: amdgpu_device_initialize: DRM version is 2.50.0 but this driver is only compatible with 3.x.x. Booting back to 4.19.40 makes it work again. I have added a few files from amdgpu-pro package, to make openCL work here in centos7; but something must have changed in this new kernel for amdgpu support. As kernel 4.19.40 works fine, it is not a big issue here - just wanted to report it. Allan.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss May 2019