Discuss

discuss@lists.centos.org

34753 discussions

Re Centos 7.2 Repos
by jd1008 17 May '16

17 May '16

Hi All, I am having a terrible time installing multi media tools like smplayer (which requires mplayer), which is not avaiable from the centos repos. I have installed epel.repo which containa the epel-release repo info for yum Still I cannot install many things. For example, I ran for i in faad2-libs liba52.so.0 libaa.so.1 libartsc.so.0 libass.so.4 libaudio.so.2 libavcodec.so.53 libavcodec.so.53 libavformat.so.53 libavformat.so.53 libavutil.so.51 libavutil.so.51 libBasicUsageEnvironment.so.0 libbluray.so.0 libbs2b.so.0 libcaca.so.0 libcdio_cdda.so.0 libcdio_cdda.so.0 libcdio_paranoia.so.0 libcdio_paranoia.so.0 libcdio.so.10 libdca.so.0 libdirac_decoder.so.0 libdirac_encoder.so.0 libdirectfb-1.7.so.4 libenca.so.0 libesd.so.0 libfaac.so.0 libfaad.so.2 libgroupsock.so.0 libjack.so.0 liblirc_client.so.0 libliveMedia.so.0 libmad.so.0 libmp3lame.so.0 libmpeg2.so.0 libmpg123.so.0 libnemesi.so.1 libopenal.so.1 libopencore-amrnb.so.0 libopencore-amrwb.so.0 libportaudio.so.2 libpostproc.so.52 libpostproc.so.52 librtmp.so.0 libschroedinger-1.0.so.0 libswscale.so.2 libswscale.so.2 libtwolame.so.0 libUsageEnvironment.so.0 libvga.so.1 libx264.so.120 libx264.so.142 libxmms.so.1 libxvidcore.so.4 mencoder mplayer-fonts mplayer-skins ; do yum provides $i done It found no match for any of these which required for installing: yum install mplayer-common-1.1-33.20150505svn.el7.nux.x86_64.rpm mplayer-1.2-92_snap20130920.el7.x86_64.rpm mplayer-1.0-0.140.20120205svn.el6.1.x86_64.rpm mplayer-tools-1.0-0.140.20120205svn.el6.1.x86_64.rpm mplayer-common-1.0-0.140.20120205svn.el6.1.x86_64.rpm mplayer-doc-1.0-0.140.20120205svn.el6.1.x86_64.rpm mplayer-gui-1.0-0.140.20120205svn.el6.1.x86_64.rpm mpg123-1.13.8-1.el6.x86_64.rpm mencoder-1.0-0.140.20120205svn.el6.1.x86_64.rpm mpg123-plugins-extras-1.13.8-1.el6.x86_64.rpm mpg123-plugins-jack-1.13.8-1.el6.x86_64.rpm mpg123-plugins-pulseaudio-1.13.8-1.el6.x86_64.rpm 2>&1 | grep -i requires > /tmp/mplayer So, please, if you have safe and reliable repos for linux MM tools, please share.

7 12

Xwindow: unable to connect to display in CR 6.8
by Gilbert Sebenste 17 May '16

17 May '16

Hello everyone, I just installed the CentOS 6.8 updates from the CR repository, and then I rebooted the server. I run some software to make weather images on a website, and I have run into a problem. When I do it, the software, as it tries to plot the image, says: Xwindow: unable to connect to display It just stopped working when I did the updates. Has anyone else seen this, or have an idea on what to look for to get this fixed? To plot it, I use syntax's of machine:0 machine:1 machine:2 Which lets me plot it using virtual frame buffers (Xvfb). When I do xhost + servername , it says it has been added to the control list...but it still doesn't fix the issue. Does anyone know what I may be doing wrong? Gilbert ******************************************************************************* Gilbert Sebenste ******** (My opinions only!) ****** *******************************************************************************

1 2

Rsyslog on C7
by Adrian P. van Bloois 17 May '16

17 May '16

Hi, I have problems with rsyslog on C7. In /etc/rsyslog.d/iptables.conf I have: # Log all iptables stuff separately :msg, contains, "iptables: " { action(type="omfile" file="/var/log/iptraf/info") stop } THis works fine. In /etc/rsyslog.d/mail.conf I have: # Log all the mail messages in one place. if ($syslogfacility-text == 'mail') then { action(type="omfile" file="/var/log/mail/info") stop } This does not work, neither does a line like: mail.* /var/log/mail/info if I put that in /etc/rsyslog.conf. What am I doing wrong??? Here is my /etc/rsyslog.conf: # rsyslog configuration file # For more information see /usr/share/doc/rsyslog-*/rsyslog_conf.html # If you experience problems, see http://www.rsyslog.com/doc/troubleshoot.html #### MODULES #### # The imjournal module bellow is now used as a message source instead of imuxsock. $ModLoad imuxsock # provides support for local system logging (e.g. via logger command) $OmitLocalLogging off $ModLoad imjournal # provides access to the systemd journal $ModLoad imklog # reads kernel messages (the same are read from journald) $ModLoad immark # provides --MARK-- message capability # Provides RELP syslog reception $ModLoad imrelp $InputRELPServerRun 2514 # provides RELP syslog transmission $ModLoad omrelp #### GLOBAL DIRECTIVES #### # Where to place auxiliary files $WorkDirectory /var/lib/rsyslog # Use default timestamp format $ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat # File syncing capability is disabled by default. This feature is usually not required, # not useful and an extreme performance hit #$ActionFileEnableSync on # Include all config files in /etc/rsyslog.d/ $IncludeConfig /etc/rsyslog.d/*.conf # File to store the position in the journal $IMJournalStateFile imjournal.state # Set the default permissions for all log files. $FileOwner root $FileGroup root $FileCreateMode 0644 $DirCreateMode 0755 $Umask 0022 # #### RULES #### # Log all kernel messages to the console. # Logging much else clutters up the screen. #kern.* /dev/console kern.crit :omusrmsg:* # Log anything (except mail) of level info or higher. # Don't log private authentication messages! kern.info;mail.none;authpriv.none;cron.none /var/log/messages # The authpriv file has restricted access. authpriv.* /var/log/auth/info auth.* /var/log/auth/info # Log daemon stuff daemon.* /var/log/daemon/info # Log cron stuff cron.* /var/log/cron # Everybody gets emergency messages #*.emerg :omusrmsg:* # Save boot messages also to boot.log local7.* /var/log/boot.log -- Adri P. van Bloois Antonlaan 104 email: adrian(a)pa0rda.nl 3701 VG Zeist voice: +31-(0)-30-6912741 The Netherlands fax: NONE 52 05'15.77"N 5 4'44.56"E QTH-locater JO 22 OC "Elegance is not a dispensable luxury but a factor that decides between success and failure." Edsger W. Dijkstra

1 0

ipmitool and CentOS 7
by m.roth＠5-cent.us 17 May '16

17 May '16

On Dells running CentOS 6, we could use this command ipmitool delloem lcd set mode userdefined "$(uname -n | sed -e 's/\..*//' )" to set the little LCD screen to display the system name, In the latest sevens, it fails, and gives me usage for the command... which displays exactly that syntax. Anyone have a clue? mark

3 2

devtoolset-4
by Jarosław Bober 17 May '16

17 May '16

Hello, my name is Jarek I am new here. I need some clarifications on how to distribute an app developed with devtoolset-4 enabled. I am developing a distributed app in c++ I wanted to upgrade toolchain to use new standard. Is it true that when I compile on centos 6.x with devtoolset enabled then I will be able to run this app on centos 7.x as well? Do I have to install devtoolset on all my machines that I want to run this app? Or would it use built-in libstdc++ library, linking statically only the missing parts? This confuses me a bit. Regards, -Jarek

1 0

C7 Desktop background
by Rob Kampen 17 May '16

17 May '16

Hi Just stumbled into a problem with my recent new build C7 work station. Fully updated, gnome desktop, all was working well until I had a play with Tweak Tool, I wanted to try some other themes for window layouts as the default seems to not show check boxes correctly in all situations. I haven't yet determined what is causing this but suspected another theme may work better, as not being able to see the correct status of a check box is somewhat frustrating. So I made and tried numerous changes with this Tweak Tool, but only used the items that were installed as default installed select options, no special import of any other themes or extensions. At one point I lost the Desktop background - cannot recall which change triggered this, however as I have tried all the other options on just about every tab, I still have a gray desktop. If I move the cursor to the top left corner and it shows all the open windows, the desktop wallpaper / background shows just fine, but when I select any window/app, my desktop reverts to gray. I have tried resetting the desktop background but it does not remove this aberration. Any gnome gurus out there that can point me to the gnome foo required to get my desktop looking 21st century and not like my old monochrome Windows386 circa late 1980's. Thanks Rob

3 4

Black screen after install / Centos 7.2
by Oliver Zemann 16 May '16

16 May '16

Hi, i just installed CentOS 7.2 on my little "server" but i get a black screen during boot. It is a Asrock Am1h-itx mainboard with an AMD 5350 CPU (onboard graphic). I created a raid 6 but i dont think thats the problem, as the boot process goes pretty far. I would even say its going until X should start, but it is a server install, so i guess there is no X. Can someone tell me what could i do to get more information? Is there some kind of nomodeset param available for the grub cmd line param which i could try? Thanks

4 5

CentOS-announce Digest, Vol 135, Issue 8
by centos-announce-request＠centos.org 16 May '16

16 May '16

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-2016:1041 Important CentOS 5 thunderbird Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Sun, 15 May 2016 15:53:30 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1041 Important CentOS 5 thunderbird Security Update Message-ID: <20160515155330.GA9279(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1041 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1041.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 13025140c4dd7909081f051c3acb3ac182ab7581a127dbad91195e4d39d200b2 thunderbird-38.8.0-1.el5.centos.i386.rpm x86_64: c45cdb331104bcd47f8aa26169585e8df65845ea3885aa86200ee94c12de5552 thunderbird-38.8.0-1.el5.centos.x86_64.rpm Source: 5c0f7e72c279d00bf8d7de78ebec7d8b9ee704c87dbad8885d78efdff8e550cf thunderbird-38.8.0-1.el5.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 135, Issue 8 ***********************************************

1 0

Black screen after boot on CentOS 7.2
by Oliver Zemann 16 May '16

16 May '16

1 0

16 May '16

Kernel parameters aside (console=ttyUSB0 console=tty0), I am trying to get a login console working on a USB-to-serial adapter. systemctl enable serial-getty(a)ttyUSB0.service systemctl start serial-getty(a)ttyUSB0.service This works without issue on Debian 8. However when running the same on CentOS 7, my logs are filled with: May 16 12:44:58 localhost.localdomain systemd[1]: Starting Serial Getty on ttyUSB0... May 16 12:44:58 localhost.localdomain agetty[1842]: /dev/ttyUSB0: cannot open as standard input: Permission denied May 16 12:45:08 localhost.localdomain systemd[1]: serial-getty(a)ttyUSB0.service holdoff time over, scheduling restart. May 16 12:45:08 localhost.localdomain systemd[1]: Started Serial Getty on ttyUSB0. May 16 12:45:08 localhost.localdomain systemd[1]: Starting Serial Getty on ttyUSB0... May 16 12:45:08 localhost.localdomain agetty[1845]: /dev/ttyUSB0: cannot open as standard input: Permission denied May 16 12:45:18 localhost.localdomain systemd[1]: serial-getty(a)ttyUSB0.service holdoff time over, scheduling restart. May 16 12:45:18 localhost.localdomain systemd[1]: Started Serial Getty on ttyUSB0. May 16 12:45:18 localhost.localdomain systemd[1]: Starting Serial Getty on ttyUSB0... May 16 12:45:18 localhost.localdomain agetty[1850]: /dev/ttyUSB0: cannot open as standard input: Permission denied May 16 12:45:29 localhost.localdomain systemd[1]: serial-getty(a)ttyUSB0.service holdoff time over, scheduling restart. May 16 12:45:29 localhost.localdomain systemd[1]: Started Serial Getty on ttyUSB0. May 16 12:45:29 localhost.localdomain systemd[1]: Starting Serial Getty on ttyUSB0... May 16 12:45:29 localhost.localdomain agetty[1853]: /dev/ttyUSB0: cannot open as standard input: Permission denied May 16 12:45:39 localhost.localdomain systemd[1]: serial-getty(a)ttyUSB0.service holdoff time over, scheduling restart. May 16 12:45:39 localhost.localdomain systemd[1]: Started Serial Getty on ttyUSB0. I thought this might be a permissions issue. But comparing the permission on the debian box to the centos box yeilds the same results. When no one is logged in on the serial line on both machines, the permissions on the device node are as follows: crw--w----. 1 root tty 188, 0 May 16 13:49 /dev/ttyUSB0 (root:tty 0640) Any ideas as to what is blocking the serial login on the CentOS 7 box?

1 0

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