Discuss

discuss@lists.centos.org

1 participants
34753 discussions

Audacious broken on CentOS 7.6
by Nicolas Kovacs 07 Dec '18

07 Dec '18

Hi, Looks like the Audacious audio player from EPEL (which has worked fine in previous versions) is broken under CentOS 7.6. It refuses to start, and when I try to start it from the command line, here's what I get. [microlinux@bernadette:~] $ rpm -qa | grep audacious audacious-3.9-1.el7.x86_64 audacious-libs-3.9-1.el7.x86_64 audacious-plugins-3.9-1.el7.x86_64 [microlinux@bernadette:~] $ audacious ERROR plugin-load.cc:72 [plugin_load]: /usr/lib64/audacious/Effect/ladspa.so could not be loaded: /lib64/libcairo.so.2: undefined symbol: FT_Get_Var_Design_Coordinates ERROR plugin-load.cc:72 [plugin_load]: /usr/lib64/audacious/General/skins.so could not be loaded: /lib64/libcairo.so.2: undefined symbol: FT_Get_Var_Design_Coordinates ERROR plugin-load.cc:72 [plugin_load]: /usr/lib64/audacious/General/statusicon.so could not be loaded: /lib64/libcairo.so.2: undefined symbol: FT_Get_Var_Design_Coordinates ERROR plugin-load.cc:72 [plugin_load]: /usr/lib64/audacious/General/alarm.so could not be loaded: /lib64/libcairo.so.2: undefined symbol: FT_Get_Var_Design_Coordinates ERROR plugin-load.cc:72 [plugin_load]: /usr/lib64/audacious/General/delete-files.so could not be loaded: /lib64/libcairo.so.2: undefined symbol: FT_Get_Var_Design_Coordinates ERROR plugin-load.cc:72 [plugin_load]: /usr/lib64/audacious/General/notify.so could not be loaded: /lib64/libcairo.so.2: undefined symbol: FT_Get_Var_Design_Coordinates ERROR plugin-load.cc:72 [plugin_load]: /usr/lib64/audacious/General/gtkui.so could not be loaded: /lib64/libcairo.so.2: undefined symbol: FT_Get_Var_Design_Coordinates ERROR plugin-load.cc:72 [plugin_load]: /usr/lib64/audacious/General/hotkey.so could not be loaded: /lib64/libcairo.so.2: undefined symbol: FT_Get_Var_Design_Coordinates ERROR plugin-load.cc:72 [plugin_load]: /usr/lib64/audacious/General/gnomeshortcuts.so could not be loaded: /lib64/libcairo.so.2: undefined symbol: FT_Get_Var_Design_Coordinates ERROR plugin-load.cc:72 [plugin_load]: /usr/lib64/audacious/General/playlist-manager.so could not be loaded: /lib64/libcairo.so.2: undefined symbol: FT_Get_Var_Design_Coordinates ERROR plugin-load.cc:72 [plugin_load]: /usr/lib64/audacious/General/search-tool.so could not be loaded: /lib64/libcairo.so.2: undefined symbol: FT_Get_Var_Design_Coordinates ERROR plugin-load.cc:72 [plugin_load]: /usr/lib64/audacious/General/albumart.so could not be loaded: /lib64/libcairo.so.2: undefined symbol: FT_Get_Var_Design_Coordinates ERROR plugin-load.cc:72 [plugin_load]: /usr/lib64/audacious/General/aosd.so could not be loaded: /lib64/libcairo.so.2: undefined symbol: FT_Get_Var_Design_Coordinates ERROR plugin-load.cc:72 [plugin_load]: /usr/lib64/audacious/General/lyricwiki.so could not be loaded: /lib64/libcairo.so.2: undefined symbol: FT_Get_Var_Design_Coordinates ERROR plugin-load.cc:72 [plugin_load]: /usr/lib64/audacious/Visualization/blur_scope.so could not be loaded: /lib64/libcairo.so.2: undefined symbol: FT_Get_Var_Design_Coordinates ERROR plugin-load.cc:72 [plugin_load]: /usr/lib64/audacious/Visualization/cairo-spectrum.so could not be loaded: /lib64/libcairo.so.2: undefined symbol: FT_Get_Var_Design_Coordinates ERROR plugin-load.cc:72 [plugin_load]: /usr/lib64/audacious/Visualization/gl-spectrum.so could not be loaded: /lib64/libcairo.so.2: undefined symbol: FT_Get_Var_Design_Coordinates ERROR plugin-init.cc:147 [start_required]: No interface plugin found. (Did you forget to install audacious-plugins?) Abandon Any idea what's wrong here ? 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 3

ZFS fails with C7 957
by david 07 Dec '18

07 Dec '18

Folks I have two USB connected drives, configured as a mirrored-pair in ZFS. It's been working fine UNTIL I updated Centos from 3.10.0-862.14.4.el7.x86_64 to 3.10.0-957.1.3.el7.x86_64 The import of the pools didn't happen at boot. When I tried executing: zpool list I got the diagnostic suggesting I do /sbin/modprobe zfs And that command claimed the module didn't exist. YUM claims my updates are all up-to-date. I had to revert back to 862. Help? David

3 2

Re: [CentOS] Update failure: Mate requires libgtop-2.0.so.10
by Richard 06 Dec '18

06 Dec '18

> Date: Monday, December 03, 2018 20:41:20 -0600 > From: Frank Cox <theatre(a)sasktel.net> > > I just tried updating this laptop to the shiny new Centos version > and it appears that Mate doesn't like the new version of libgtop, > as you can see here: > > Error: Package: marco-1.16.1-3.el7.x86_64 (@epel) > Requires: libgtop-2.0.so.10()(64bit) > Removing: libgtop2-2.34.2-2.el7.x86_64 (@base) > libgtop-2.0.so.10()(64bit) > Updated By: libgtop2-2.38.0-3.el7.x86_64 (base) > ~libgtop-2.0.so.11()(64bit) > Error: Package: mate-applets-1.16.0-1.el7.x86_64 (@epel) > Requires: libgtop-2.0.so.10()(64bit) > Removing: libgtop2-2.34.2-2.el7.x86_64 (@base) > libgtop-2.0.so.10()(64bit) > Updated By: libgtop2-2.38.0-3.el7.x86_64 (base) > ~libgtop-2.0.so.11()(64bit) > Error: Package: mate-disk-usage-analyzer-1.16.1-1.el7.x86_64 (@epel) > Requires: libgtop-2.0.so.10()(64bit) > Removing: libgtop2-2.34.2-2.el7.x86_64 (@base) > libgtop-2.0.so.10()(64bit) > Updated By: libgtop2-2.38.0-3.el7.x86_64 (base) > ~libgtop-2.0.so.11()(64bit) > Error: Package: mate-system-monitor-1.16.0-1.el7.x86_64 (@epel) > Requires: libgtop-2.0.so.10()(64bit) > Removing: libgtop2-2.34.2-2.el7.x86_64 (@base) > libgtop-2.0.so.10()(64bit) > Updated By: libgtop2-2.38.0-3.el7.x86_64 (base) > ~libgtop-2.0.so.11()(64bit) Updated versions of those @epel packages are in the epel-testing repo, which resolved this issue for me when I updated using the CR repo a couple of weeks ago.

3 2

Bastion server
by Ilyass Kaouam 06 Dec '18

06 Dec '18

Hi, Please can you give me an equivalent off Wallix but open source? Thanks Ilyass KAOUAM SysAdmin

4 7

Firefox showing bogus sites after 'yum update'
by Gary Stainburn 06 Dec '18

06 Dec '18

I have just done a yum update for the first time in a while, and as part of that I believe Firefox got upgraded. After the reboot I restarted Firefox which had been closed down with the option to retain all open tabs/windows. However, when I restarted Firefox it had three new tabs, one being the ususal Firefox upgrade page. The other two were Phishing sites, one pretending to be Amazon the other I cannot remember. Has anyone else experienced this?

1 0

CentOS 7.6.1810 UEFI/Shim issue .. feedback wanted !
by Fabian Arrotin 06 Dec '18

06 Dec '18

We got some reports from people unable to reboot their nodes after updating to 7.6.1810, and basically to newer shim (v15). It seems to affect only nodes in UEFI mode, but without SecureBoot. We wrote that in the ReleaseNotes, including a link to the bug report : https://bugs.centos.org/view.php?id=15522 We have now a workaround in that bug report, and also a new interim build (not signed by Microsoft yet) but we need feedback , as the only node on which I could test this myself is my old 2008 iMac computer .. :-( Once we'll have enough positive (but also negative) feedback about this new build, we'll be able to send to Microsoft for signing and so consider that bug closed. Worth also noticing that if we can have that ready in the updates, we'll be able to spin a monthly iso that will then work on such uefi nodes too. Kind Regards, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

2 1

LVM failure after CentOS 7.6 upgrade -- possible corruption
by Gordon Messmer 06 Dec '18

06 Dec '18

I've started updating systems to CentOS 7.6, and so far I have one failure. This system has two peculiarities which might have triggered the problem. The first is that one of the software RAID arrays on this system is degraded. While troubleshooting the problem, I saw similar error messages mentioned in bug reports indicating that sGNU/Linux ystems would not boot with degraded software RAID arrays. The other peculiar aspect is that the system uses dm-cache. Logs from some of the early failed boots are not available, but before I completely fixed the problem, I was able to bring the system up once, and captured logs which look substantially similar to the initial boot. The content of /var/log/messages is here: https://paste.fedoraproject.org/paste/n-E6X76FWIKzIvzPOw97uw The output of lsblk (minus some VM logical volumes) is here: https://paste.fedoraproject.org/paste/OizFvMeGn81vF52VEvUbyg As best I can tell, the LVM tools were treating software RAID component devices as PVs, and detecting a conflict between those and the assembled RAID volume. When running "pvs" on the broken system, no RAID volumes were listed, only component devices. At the moment, I don't know if the LVs that were activated by the initrd were backed by component devices or the RAID devices, so it's possible that this bug might corrupt software RAID arrays. In order to correct the problem, I had to add a global_filter to /etc/lvm/lvm.conf and rebuild the initrd (dracut -f): global_filter = [ "r|vm_.*_data|", "a|sdd1|", "r|sd..|" ] This filter excludes the LVs that contain VM data, accepts "/dev/sdd1" which is the dm-cache device, and rejects all other partitions on SCSI(SATA) device nodes, as all of those are RAID component devices. I'm still working on the details of the problem, but I wanted to share what I know now in case anyone else might be affected. After updating, look at the output of "pvs" if you use LVM on software RAID.

4 7

CR repo update disaster for my desktop.
by Rob Kampen 05 Dec '18

05 Dec '18

I have a centos 7.5 desktop workstation with dual nvidia graphic cards running three monitors. I use the i915 motherboard graphics adapter for the third monitor with bumblebee to work the magic to enable the three contiguous work spaces. I use the kmod nvidia drivers for the two graphics cards. This has worked without a hitch for 5 months until this weekend. I enabled the CR repo and did the yum update. Some 800+ rpms were offered and all seemed to resolve depenancies OK, so yes it was started. The updates completed and all looked good, until the reboot. Initially the new kernel would boot just fine but the gdm/gnome desktop hung. No login offered. Reboot and select previous kernel, great, offered login, but the desktop barely settles before gnome crashes, and gdm restarts and I get to login afresh. Eventually I have, removed bumblebee, disabled the on board graphics adapter, reinstalled gnome multiple times, removed nvidia drivers, blown away my .gnome and related folders, tried as a new user, (no customizations of the desktop) all to no avail. Current situation is under my user account cannot get stable desktop for more than 10 seconds before it sends segfault error 4 in libc-2.17.so What do I do now? Seems that these big updates need to be applied in sub batches with reboots in between so that one can back out. Any ideas appreciated. Rob ⁣Sent from BlueMail

9 16

Accidentally nuked my system - any suggestions ?
by Nicolas Kovacs 05 Dec '18

05 Dec '18

Hi, My workstation is running CentOS 7 on two disks (sda and sdb) in a software RAID 1 setup. It looks like I accidentally nuked it. I wanted to write an installation ISO file to a USB disk, and instead of typing dd if=install.iso of=/dev/sdc I typed /dev/sdb. As soon as I hit <Enter>, the screen froze. I tried a hard reset, but of course, the boot process would stop short very early in the process. Now, I have backups of the important stuff of course, so no real catastrophe. But it would be nice if I could get back the data from my disk directly. I booted a rescue disk (Slax 9.6.4) and I can see my disks as well as raid arrays /dev/md125, /dev/md126 and /dev/md127. Oh, my partitioning scheme is manual and quite simple. Everything is RAID 1, I have a /boot array on /dev/sda1 + /dev/sdb1, swap on /dev/sda2 + /dev/sdb2 and / on /dev/sda3 + /dev/sdb3. I tried to mount /dev/sda3 directly from the rescue disk: # mount /dev/sda3 /mnt But I only get this: mount: unknown filesystem type 'linux_raid_member' I'd be very grateful for suggestions. 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

5 11

7.5 -> 7.6 problems
by Gregory P. Ennis 05 Dec '18

05 Dec '18

To all, I started the process of updating some of our systems from 7.5 to 7.6. Most of the servers had no problems, but several of the desktops had some difficulties. I was required to perform several yum commands to update as much as possible in the format of yum update a* then b* etc. Then after I got everything updated that would update in this manner and after the use of "rpm -Va --nofiles --nodigest" and with the use of yum update --skip-broken I am getting the following that would not update : Packages skipped because of dependency problems: libvirt-bash-completion-4.5.0-10.el7_6.3.x86_64 from updates libvirt-client-4.5.0-10.el7_6.3.x86_64 from updates libvirt-daemon-4.5.0-10.el7_6.3.x86_64 from updates libvirt-daemon-config-network-4.5.0-10.el7_6.3.x86_64 from updates libvirt-daemon-config-nwfilter-4.5.0-10.el7_6.3.x86_64 from updates libvirt-daemon-driver-interface-4.5.0-10.el7_6.3.x86_64 from updates libvirt-daemon-driver-lxc-4.5.0-10.el7_6.3.x86_64 from updates libvirt-daemon-driver-network-4.5.0-10.el7_6.3.x86_64 from updates libvirt-daemon-driver-nodedev-4.5.0-10.el7_6.3.x86_64 from updates libvirt-daemon-driver-nwfilter-4.5.0-10.el7_6.3.x86_64 from updates libvirt-daemon-driver-qemu-4.5.0-10.el7_6.3.x86_64 from updates libvirt-daemon-driver-secret-4.5.0-10.el7_6.3.x86_64 from updates libvirt-daemon-driver-storage-4.5.0-10.el7_6.3.x86_64 from updates libvirt-daemon-driver-storage-core-4.5.0-10.el7_6.3.x86_64 from updates libvirt-daemon-driver-storage-disk-4.5.0-10.el7_6.3.x86_64 from updates libvirt-daemon-driver-storage-gluster-4.5.0-10.el7_6.3.x86_64 from upd libvirt-daemon-driver-storage-iscsi-4.5.0-10.el7_6.3.x86_64 from upd libvirt-daemon-driver-storage-logical-4.5.0-10.el7_6.3.x86_64 from upd libvirt-daemon-driver-storage-mpath-4.5.0-10.el7_6.3.x86_64 from upd libvirt-daemon-driver-storage-rbd-4.5.0-10.el7_6.3.x86_64 from updates libvirt-daemon-driver-storage-scsi-4.5.0-10.el7_6.3.x86_64 from updates libvirt-daemon-kvm-4.5.0-10.el7_6.3.x86_64 from updates libvirt-devel-4.5.0-10.el7_6.3.x86_64 from updates libvirt-libs-4.5.0-10.el7.x86_64 from base libvirt-libs-4.5.0-10.el7_6.2.x86_64 from updates libvirt-libs-4.5.0-10.el7_6.3.x86_64 from updates libvirt-python-4.5.0-1.el7.x86_64 from base Is there something I can do to finish this process or is this just related to a repository problem. -- Greg Ennis

2 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss