Discuss January 2018

discuss@lists.centos.org

89 participants
72 discussions

C6 KPTI cpuinfo flag?
by Robert Arkiletian 09 Jan '18

09 Jan '18

Noticed C6 had a kernel update on Friday. 2.6.32-696.18.7.el6.x86_64 What is the flag in /proc/cpuinfo that indicates the KPTI patch for Meltdown CVE-2017-5754 for C6? Some distros are using "kaiser" some like Fedora are using "pti". Also noticed some (like Fedora) are displaying "cpu_insecure" under the bugs: heading of cpuinfo.

2 1

Nvidia maximum pixel clock issue in kmod-nvidia-384.98
by Danny Smit 08 Jan '18

08 Jan '18

Hi everyone, On CentOS 7 I'm running into an issue with the latest nvidia driver from elrepo: kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 This driver version seem to introduce issue in detecting video modes when a monitor is connected using DVI. As soon as the machine attempts to start X, nothing happens and the monitor goes into sleep mode reporting that it has 'no signal'. It is interesting because it occurs with several monitors, but only when they are connected through DVI. When using VGA it works like a charm. Also it did work without problems with the previous driver version (kmod-nvidia-384.90-1.el7_4.elrepo.x86_64), with the exact same setup. In this case the issue occurs with an Nvidia NVS 315. I don't know if other nvidia cards are affected. The following information from Xorg.0.log seems of interest: [ 130.447] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0 [ 130.447] (--) NVIDIA(0): CRT-0 [ 130.447] (--) NVIDIA(0): CRT-1 [ 130.447] (--) NVIDIA(0): DFP-0 (boot) [ 130.447] (--) NVIDIA(0): DFP-1 [ 130.447] (--) NVIDIA(0): DFP-2 [ 130.447] (--) NVIDIA(0): DFP-3 [ 130.448] (II) NVIDIA(0): NVIDIA GPU NVS 315 (GF119) at PCI:1:0:0 (GPU-0) [ 130.448] (--) NVIDIA(0): Memory: 1048576 kBytes [ 130.448] (--) NVIDIA(0): VideoBIOS: 75.19.88.00.0b [ 130.448] (II) NVIDIA(0): Detected PCI Express Link width: 16X [ 130.462] (--) NVIDIA(GPU-0): CRT-0: disconnected [ 130.462] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock [ 130.462] (--) NVIDIA(GPU-0): [ 130.467] (--) NVIDIA(GPU-0): CRT-1: disconnected [ 130.467] (--) NVIDIA(GPU-0): CRT-1: 400.0 MHz maximum pixel clock [ 130.467] (--) NVIDIA(GPU-0): [ 130.488] (--) NVIDIA(GPU-0): Philips 240S4 (DFP-0): connected [ 130.488] (--) NVIDIA(GPU-0): Philips 240S4 (DFP-0): Internal TMDS [ 130.488] (--) NVIDIA(GPU-0): Philips 240S4 (DFP-0): 0.0 MHz maximum pixel clock [ 130.488] (--) NVIDIA(GPU-0): [ 130.493] (--) NVIDIA(GPU-0): DFP-1: disconnected [ 130.493] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS [ 130.493] (--) NVIDIA(GPU-0): DFP-1: 0.0 MHz maximum pixel clock [ 130.493] (--) NVIDIA(GPU-0): [ 130.493] (--) NVIDIA(GPU-0): DFP-2: disconnected [ 130.493] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort [ 130.493] (--) NVIDIA(GPU-0): DFP-2: 480.0 MHz maximum pixel clock [ 130.493] (--) NVIDIA(GPU-0): [ 130.493] (--) NVIDIA(GPU-0): DFP-3: disconnected [ 130.493] (--) NVIDIA(GPU-0): DFP-3: Internal DisplayPort [ 130.493] (--) NVIDIA(GPU-0): DFP-3: 480.0 MHz maximum pixel clock [ 130.493] (--) NVIDIA(GPU-0): [ 130.493] (EE) NVIDIA(GPU-0): Unable to add conservative default mode "nvidia-auto-select". [ 130.493] (EE) NVIDIA(GPU-0): Unable to add "nvidia-auto-select" mode to ModePool. [ 130.493] (==) NVIDIA(0): [ 130.493] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select" [ 130.493] (==) NVIDIA(0): will be used as the requested mode. [ 130.493] (==) NVIDIA(0): [ 130.493] (WW) NVIDIA(0): No valid modes for "DFP-0:nvidia-auto-select"; removing. [ 130.493] (WW) NVIDIA(0): [ 130.493] (WW) NVIDIA(0): Unable to validate any modes; falling back to the default mode [ 130.493] (WW) NVIDIA(0): "nvidia-auto-select". [ 130.493] (WW) NVIDIA(0): [ 130.493] (WW) NVIDIA(0): No valid modes for "DFP-0:nvidia-auto-select"; removing. [ 130.493] (EE) NVIDIA(0): Unable to use default mode "nvidia-auto-select". [ 130.493] (EE) NVIDIA(0): Failing initialization of X screen 0 The log shows "0.0 MHz maximum pixel clock" for the DVI connections. When enabling ModeDebug in the xorg.conf it shows that all of the resolutions are rejected because of incorrect maximum pixel clock: [ 1354.589] (II) NVIDIA(GPU-0): [ 1354.589] (II) NVIDIA(GPU-0): --- Building ModePool for Philips 240S4 (DFP-0) --- [ 1354.589] (WW) NVIDIA(GPU-0): Validating Mode "1920x1200_60": [ 1354.589] (WW) NVIDIA(GPU-0): Mode Source: EDID [ 1354.589] (WW) NVIDIA(GPU-0): 1920 x 1200 @ 60 Hz [ 1354.589] (WW) NVIDIA(GPU-0): Pixel Clock : 154.00 MHz [ 1354.589] (WW) NVIDIA(GPU-0): HRes, HSyncStart : 1920, 1968 [ 1354.589] (WW) NVIDIA(GPU-0): HSyncEnd, HTotal : 2000, 2080 [ 1354.589] (WW) NVIDIA(GPU-0): VRes, VSyncStart : 1200, 1203 [ 1354.589] (WW) NVIDIA(GPU-0): VSyncEnd, VTotal : 1209, 1235 [ 1354.589] (WW) NVIDIA(GPU-0): Sync Polarity : +H -V [ 1354.589] (WW) NVIDIA(GPU-0): Mode is rejected: PixelClock (154.0 MHz) too high for [ 1354.589] (WW) NVIDIA(GPU-0): Display Device (Max: 0.0 MHz). [ 1354.589] (WW) NVIDIA(GPU-0): Mode "1920x1200_60" is invalid. Note that with the previous driver (version 384.90), a valid value was detected for the 'maximum pixel clock': [ 124.804] (--) NVIDIA(GPU-0): Philips 240S4 (DFP-0): connected [ 124.804] (--) NVIDIA(GPU-0): Philips 240S4 (DFP-0): Internal TMDS [ 124.804] (--) NVIDIA(GPU-0): Philips 240S4 (DFP-0): 165.0 MHz maximum pixel clock Since it did work with version 384.90 and stopped working with version 384.98, it looks like a regression in the nvidia driver. What is the best way to report the issue and get an update in elrepo? Kind regards, Danny Smit

4 11

CentOS 7.4 fails to boot as Xen PV guest: resurfaces (now also) with centosplus kernel 693.11.6.el7
by David Groep 08 Jan '18

08 Jan '18

Dear all, Maybe I'm the only one - so before filing it as a bug: it appears that the latest set of kernel patches in 3.10.0-693.11.6.el7 makes issue 0013763 "CentOS 7.4 kernel (3.10.0-693*) fails to boot as Xen PV guest" re-surface *also* with the CentOS PLUS kernel. But maybe in a different way ... Thanks to the (great!) quick work on making the plus kernel available (in #14330, thanks for that!) I was able to test the following combinations: - 3.10.0-693.11.6.el7.centos.plus works fine on XenServer 7 HVM guests - 3.10.0-693.11.1.el7.centos.plus works fine on XenServer 7 XenPV guests - 3.10.0-693.11.6.el7.centos.plus crashes on boot for XS7 XenPV guests immediately after the boot stage where the PS/2 drivers are loaded Crashing does not depend on the amount of VM memory or #cores/sockets. Also, the tell-tale "mm/vmalloc.c" failure output is no longer present. The system 'just' crashes (with the kernel log lines as below) around the time of the i8042 controller probing. Obviously the stock upstream 3.10.0-693.11.6.el7 crashes as well for XS7 XenPV guests, but that was to be expected as per 0013763. It crashes in the same way, around the time of the i8042 probes. Can anyone (maybe bill_mcgonigle?) reproduce the issue? Did the KPTI patches break the XenPV fixes in CentOS Plus per 13763? Or is this a new XenPV issue? Interestingly, the crash is now sudden and (even at loglevel=7) without further information. The crash after the i8042/mousedev is (I think) unrelated to these devices, since the system crashes in the same way even with "i8042.debug i8042.nokbd i8042.noaux i8042.dumbkbd i8042.nomux i8042.noloop i8042.nopnp psmouse.proto=bare" added to the kernel command line (and then you don't see any PS/2 and mousedev). So something immediately after the mousy things triggers the crash: 0.2293541 io scheduler cfq registered 0.2295071 pci_hotplug: PCI Hot Plug PCI Core version: 0.5 0.2295241 pciehp: PCI Express Hot Plug Controller Driver version: 0.4 0.2301241 Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled 0.2306111 Non-volatile memory driver u1.3 0.2306601 Linux agpgart interface u0.103 0.2307641 crash memory driver: version 1.1 0.2308301 rdac: device handler registered 0.2308741 hp_sw: device handler registered 0.2308851 emc: device handler registered 0.2308941 alua: device handler registered 0.2309491 libphy: Fixed MDIO Bus: probed 0.2310301 ehci_hcd: USB 2.0 'Enhanced' Host Controller CEHCI) Driver 0.2310471 ehci-pci: EHCI PCI platform driver 0.2310671 ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver 0.2310791 ohci-pci: OHCI PCI platform driver 0.2310951 uhci_hcd: USB Universal Host Controller Interface driver 0.2311581 usbcore: registered new interface driver usbserial 0.2311741 usbcore: registered new interface driver usbserial_generic 0.2311941 usbserial: USB Serial support registered for generic 0.2312291 i8042: PNP: No PS/2 controller found. Probing ports directly. 1.2427071 i8042: No controller found 1.2428571 mousedev: PS/2 mouse device common for all mice [HANG - VM shuts down] although sometimes the boot stops at "i8042: PNP: No PS/2 controller found. Probing ports directly." and does not make it to the "mouse" bit. Anyone found similar behaviour? Thanks a lot! DavidG. -- David Groep ** Nikhef, Dutch National Institute for Subatomic Physics, PDP programme ** ** Room: H1.50 Phone: +31 20 5922179, PObox 41882, NL-1009DB Amsterdam NL ** ** PGP: 0xD80134C2 308E076A FP: 2facebea12803ba145685a21d80134c2308e076a **

3 2

CVE-2017-5715, CVE-2017-5753 and CVE-2017-5754
by Walter H. 07 Jan '18

07 Jan '18

Hello, will there be updates for these CVEs for CentOS 6? Thanks, Walter

6 5

Bug in gnome-control-center and network edit module in Centos 7.4
by Gregory P. Ennis 07 Jan '18

07 Jan '18

Everyone, I have been having a problem in setting up gateway/routers with Centos 7.4 machine and finally figured out the problem today. I am not sure if this bug occurred first in 7.3 but it is definitely in 7.4. I have other gateway routers that were created at the beginning of the Centos 7 that have been working perfectly even through the upgrades to 7.3 and 7.4, but the new gateways I have created would not work. It seems simple now that I have the solution, but it took me an embarrassingly too long a time to debug and resolves the problem. The problem appears to me to be a bug in the new gnome-command-center when using the network module to add or edit network interfaces. The problem that I identified is that the network module requires the user to enter a gateway ip address even on the internal networks. Normally the gateway ip address is left blank on the internal interfaces, and is only filled in on the external interface. I was never able to get the gui using the network editor within the gnome-control-center to be able to remove the gateway ip address from the; internal interfaces; I was forced to enter something, and I entered the external gateway ip address. However, to bypass and fix this problem, the gateway ip address is easily removed by editing the appropriate file or files in : /etc/sysconfig/network-scripts/ifcfg-emp3s0 /etc/sysconfig/network-scripts/ifcfg-emp4s0 The network editor in the gnome-control-center module required the entry of a gateway ip address. I had entered the gateway for the external ip address in this field, and all I did to solve the problem is to delete "GATEWAY=x.x.x.x" from both of the above files. This allowed both of the new gateway machines I have recently created to work like they should. Hope this saves someone else some time. Greg

1 0

Intel Flaw
by Chris Olson 05 Jan '18

05 Jan '18

How does the latest Intel flaw relate to CentOS 6.x systems that run under VirtualBox hosted on Windows 7 computers? Given the virtual machine degree of separation from the hardware, can this issue actually be detected and exploited in the operating systems that run virtually? If there is a slow down associated with the fix, how much might it impact the virtual systems?

3 2

CentOS-announce Digest, Vol 155, Issue 1
by centos-announce-request＠centos.org 05 Jan '18

05 Jan '18

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-2018:0007 Important CentOS 7 kernel Security Update (Karanbir Singh) 2. CESA-2018:0012 Important CentOS 7 microcode_ctl Security Update (Karanbir Singh) 3. CESA-2018:0014 Important CentOS 7 linux-firmware Security Update (Karanbir Singh) 4. [Infra] - planned outage : All services (Fabian Arrotin) 5. CESA-2018:0013 Important CentOS 6 microcode_ctl Security Update (Johnny Hughes) 6. CESA-2018:0008 Important CentOS 6 kernel Security Update (Johnny Hughes) 7. CESA-RHSA-2018:0024 Important CentOS 6 qemu-kvm Security Update (Johnny Hughes) 8. CESA-2018:0030 Important CentOS 6 libvirt Security Update (Johnny Hughes) 9. CESA-2018:0029 Important CentOS 7 libvirt Security Update (Johnny Hughes) 10. CESA-2018:0023 Important CentOS 7 qemu-kvm Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 4 Jan 2018 11:36:27 +0000 From: Karanbir Singh <kbsingh(a)centos.org> To: CentOS Announcements List <centos-announce(a)centos.org> Subject: [CentOS-announce] CESA-2018:0007 Important CentOS 7 kernel Security Update Message-ID: <d07d0b4b-cc89-329a-f517-08b3cd1bae7d(a)centos.org> Content-Type: text/plain; charset=utf-8 CentOS Errata and Security Advisory 2018:0007 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:0007 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 320ab3bd00bd1f051c69f65f2d4cd6ab64585f977d9cd7a52e64e8f8147894fc kernel-3.10.0-693.11.6.el7.x86_64.rpm 0eefdec5447d3ed2781f30d093e22f4654e8af201e1e8058a57876d1baf2ee64 kernel-abi-whitelists-3.10.0-693.11.6.el7.noarch.rpm 5137d0db8632342edfb355ce5bb0a4b4b80d5ffd4b9950bb8dcfcd78e4b8a9dc kernel-debug-3.10.0-693.11.6.el7.x86_64.rpm 882a6522bdafaa697173ff7adedd2cd6ceee5c4a6aa0cd1cb4cf042789420c78 kernel-debug-devel-3.10.0-693.11.6.el7.x86_64.rpm 9c0d7753c649d68cd25b212ee573cec37dc2211891444224e502128fcffdf301 kernel-devel-3.10.0-693.11.6.el7.x86_64.rpm d2005d6a85f2ddd627290dd4cd4d2084215ef45cd8b3f66077b68fe2b0cce61e kernel-doc-3.10.0-693.11.6.el7.noarch.rpm 34d8682b2df1e47c9675f913fbfb129420cce219beaf7985c607a69ccdb3e064 kernel-headers-3.10.0-693.11.6.el7.x86_64.rpm fd3eaf598546bcb502e5e7293d0301b48774c9358dd320b7e53bd042dfae7094 kernel-tools-3.10.0-693.11.6.el7.x86_64.rpm 3c53034adc4c942a02f1dd72f0adf688f558867caf086b5b239169262b75f570 kernel-tools-libs-3.10.0-693.11.6.el7.x86_64.rpm 91153ae59d0acf585201b9a5b453ed8e6504651bf114e3c21c725ce42c8675c5 kernel-tools-libs-devel-3.10.0-693.11.6.el7.x86_64.rpm 8ef1d6c1ef77af60bbb680fa58b1d15f7901c21220c7e5db05edbbbb56f7b17c perf-3.10.0-693.11.6.el7.x86_64.rpm b1f7bf92063bce0cec6286845686bc6ef96db126bdaa8987703b21a736a1a509 python-perf-3.10.0-693.11.6.el7.x86_64.rpm Source: b7756ceda51a35942e03d553f0ec6049ba2520c89e0d66e8e2cdae88f6db0d6a kernel-3.10.0-693.11.6.el7.src.rpm Note: 1) This is a widespread issue with potentially huge impact, we appreciate any help in spreading the word around so maximum number of users are able to find out, and patch their systems. 2) Upstream is curating information around this issue at https://access.redhat.com/security/vulnerabilities/speculativeexecution - information on that page would be helpful for most people on CentOS Linux as well. 3) Please reach out to us at #centos on irc.freenode.net for any feedback, comments, questions or concerns. -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc ------------------------------ Message: 2 Date: Thu, 4 Jan 2018 11:40:52 +0000 From: Karanbir Singh <kbsingh(a)centos.org> To: CentOS Announcements List <centos-announce(a)centos.org> Subject: [CentOS-announce] CESA-2018:0012 Important CentOS 7 microcode_ctl Security Update Message-ID: <ebbc916f-bc12-0a57-4228-cffde1956cdd(a)centos.org> Content-Type: text/plain; charset=utf-8 CentOS Errata and Security Advisory 2018:0012 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:0012 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ccb96b47da6ce420c39a38d09e57adcc7ab3696c721d081fee94298f19fc6cab microcode_ctl-2.1-22.2.el7.x86_64.rpm Source: 589fe27443e43fd6549f56e39968cf515d1cd2448dc922bf0cc980fc651f880d microcode_ctl-2.1-22.2.el7.src.rpm -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc ------------------------------ Message: 3 Date: Thu, 4 Jan 2018 11:47:37 +0000 From: Karanbir Singh <kbsingh(a)centos.org> To: CentOS Announcements List <centos-announce(a)centos.org> Subject: [CentOS-announce] CESA-2018:0014 Important CentOS 7 linux-firmware Security Update Message-ID: <d1551ccd-4d12-3bc1-b1d9-9d9bcac949ae(a)centos.org> Content-Type: text/plain; charset=utf-8 CentOS Errata and Security Advisory 2018:0014 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:0014 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: dad80246e21277864476614560cae38820cc147b9ceb44dd0d1776e3935b05df iwl1000-firmware-39.31.5.1-57.el7.noarch.rpm dbb0a9095b11d9af2b8db8f160e1004ead7f5b07add216df63c843e2ac470259 iwl100-firmware-39.31.5.1-57.el7.noarch.rpm 1ff7d3347a2759b15818d71817d5055643bcc4a9f7b091d186006948cf75a3f0 iwl105-firmware-18.168.6.1-57.el7.noarch.rpm e807e3cc6faa0be6df4675d9810db6292a534bc0c3f9c714dcc7c92fed0ba4fd iwl135-firmware-18.168.6.1-57.el7.noarch.rpm d24d6225079ec7d7870ca022226686c67d70f9d034af1167b36570e8506fdf02 iwl2000-firmware-18.168.6.1-57.el7.noarch.rpm 2eebc03a19e54f4b072f21886f02e43bdac41ff5e8290d9eb7c62e3ef1ed7352 iwl2030-firmware-18.168.6.1-57.el7.noarch.rpm d154f7ddb5ccca2772604f907d7a3c06e1b2f95b35665e81363226c98a9115c4 iwl3160-firmware-22.0.7.0-57.el7.noarch.rpm aaba72a90838c5dee3373004ee00530e3f43fbd0b9cd634223d02ea500c3cd6d iwl3945-firmware-15.32.2.9-57.el7.noarch.rpm f18caaca13e3ed06f43483870ecdc57ff6c8796bf3cb8375822519d0ced3b659 iwl4965-firmware-228.61.2.24-57.el7.noarch.rpm 257fe78f77c4e1c5c9bea3873421411c77020c12d907b1d7c511e7e96eaa3190 iwl5000-firmware-8.83.5.1_1-57.el7.noarch.rpm e9edf8b527e94302b0572ce1e3f0e91d62e9d11f74cf3ad1c0350c8e23684acc iwl5150-firmware-8.24.2.2-57.el7.noarch.rpm b63dc1829cca0afbb4a6e5681cebf54509cc4c507ab0bad6553856c4063616ed iwl6000-firmware-9.221.4.1-57.el7.noarch.rpm 8abb25db6c0dcedfa0c11f87028521f5098a88374dcb99376f485bda4596a567 iwl6000g2a-firmware-17.168.5.3-57.el7.noarch.rpm d35951cc21bfccae24e6611ad03901ac1fe0183614add09b2b04528a72d3ea4b iwl6000g2b-firmware-17.168.5.2-57.el7.noarch.rpm 8a2cd4dbabdbdcc36ed46a2529c07b9873716981610082db5b40ae134e12ee3d iwl6050-firmware-41.28.5.1-57.el7.noarch.rpm 357388ce0000543ce9714ebffbadc15ab1e3969c4f1256d6f1132f619c82afdc iwl7260-firmware-22.0.7.0-57.el7.noarch.rpm 75a235701d30e685ca87945e0dd583bda08e254f9078d50b3d466af4d5e3cfe6 iwl7265-firmware-22.0.7.0-57.el7.noarch.rpm 16164fc1c681f5a04a14879041e66855aa434c9c9c30d722a273519896b0f7b7 linux-firmware-20170606-57.gitc990aae.el7.noarch.rpm Source: ffa8541e30f72d79d88740d418943668d1da9535ebbee0df3c61ad4d7d576cdc linux-firmware-20170606-57.gitc990aae.el7.src.rpm -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc ------------------------------ Message: 4 Date: Thu, 4 Jan 2018 14:21:49 +0100 From: Fabian Arrotin <arrfab(a)centos.org> To: "The CentOS developers mailing list." <centos-devel(a)centos.org>, centos-announce(a)centos.org Subject: [CentOS-announce] [Infra] - planned outage : All services Message-ID: <eb940deb-7311-381d-c2f4-ede324e9ffe4(a)centos.org> Content-Type: text/plain; charset="utf-8" Due to important security updates that we need to apply within the whole CentOS infra, please be aware that some nodes/services will be unresponsive during that maintenance window. As it targets both CentOS 6 and CentOS 7, we'll probably apply those updates ASAP but we'll not notify for each impacted service, so this announce will cover all impacted services during the next hours/days. Thanks for your comprehending and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

possible issue with nvidia and new patches?
by Zube 04 Jan '18

04 Jan '18

Twitter user stintel, in this thread: https://twitter.com/stintel/status/948499157282623488 mentions a possible problem with the new patches and the nvidia driver: "As if the @Intel bug isn't bad enough, #KPTI renders @nvidia driver incompatible due to GPL-only symbol 'cpu_tlbstate'. #epicfail" Also: https://twitter.com/tomasz_gwozdz/status/948590364679655429 https://twitter.com/BitsAndChipsEng/status/948578609761054721 Cheers, Zube

3 2

Issues with qt-creator from EPEL 7
by Toralf Lund 04 Jan '18

04 Jan '18

Hi, Is anyone here using the "EPEL" package for qt-creator on CentOS 7? I'm having a few issues with it, and I though I'd run them by the list before I try Qt Forums or whatever (since they could be specific to the above mentioned build.) Most notably, 1. If I click on an error message in the "Issues" list after compilation (to display source code related to the error), I sometimes get a "File not found" message *if the file in question is already open*. If I close the file and repeat, the same file opens just fine. 2. There is something slightly odd about the icons in the display. In particular, when I open the search panes, I sometimes get buttons with labels "Find Previous" and "Find Next", but at other times, those same buttons have arrow icons. Has anyone else seen something like this? - Toralf

1 0

Gtkcdlabel + cdlabelgen on CentOS 7 ?
by Nicolas Kovacs 03 Jan '18

03 Jan '18

Hi, I've been using the nifty little application Gtkcdlabel for making CD and DVD covers since 2005, if I remember correctly. Later versions are written in Python, and it's a graphical frontend to the cdlabelgen utility. The application doesn't look very well maintained, since the 1.15 release dates back to 2011. Nevertheless, I've been successfully running it on Slackware Linux until the latest 14.2 release. I'm currently trying to install it on CentOS 7, and I'm only having a partial success, with a showstopper. Here's what I could manage so far. The 'cdlabelgen' command line utility is available on EPEL, so I installed that. I downloaded Gtkcdlabel on the project site: http://gtkcdlabel.sourceforge.net/ The installation process takes you back 25 years, since it amounts to this: # tar xvjf gtkcdlabel-1.15.tar.bz2 -C / This installs the application in /usr/bin/gtkcdlabel.py along with a new desktop entry (and the ugliest icon on the planet). The application shows OK when running it, but PostScript file generation fails. I launched it from a terminal by invoking gtkcdlabel.py, filled out a few fields like Title and Subtitle and then clicked on Preview. Normally this is supposed to launch the PDF viewer (/usr/bin/evince in the default configuration). And it launches, except it gets stuck here, since nothing is generated. Under the hood, in my terminal, I get the following string of error messages: (libspectre) ghostscript reports: invalidfont -10 (libspectre) ghostscript reports: invalidfont -10 (libspectre) ghostscript reports: invalidfont -10 (libspectre) ghostscript reports: invalidfont -10 (libspectre) ghostscript reports: invalidfont -10 I checked, and ghostscript as well as ghostscript-fonts are installed. Which leaves me clueless. Any help would be greatly appreciated, since I've been using this application for years on a daily basis. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

3 8

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss January 2018