Re: [CentOS] HP laptops with CentOS 7?

[Sorin Srbu]

> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of ken
> Sent: den 16 november 2017 17:00
> To: centos@centos.org
> Subject: Re: [CentOS] HP laptops with CentOS 7?
> 
> > I'm looking into getting HP laptops for our department running CentOS 7.
>
> For two years now I've been semi-happily using an HP Envy with the
> high-end Nvidia graphics card.  Installing CentOS7, everything worked
> out of box except the wifi.  The problem there was due to the drivers
> requiring a v.3.5 kernel which centos doesn't yet have.  There were some
> very occasional glitches in the video, but subsequent upgrades to the
> nvidia drivers eventually fixed those.
> 
> Audio worked initially, but after installing vlc I've had problems which
> I haven't been able to track down, so the sound with some apps just
> doesn't work.  Notably, anything audio through firefox doesn't work
> except that which uses flashplayer.  Audacity and vlc work just fine.
> 
> The body of the laptop is solid, made mostly out of carbon fiber... it
> seemed like it's bullet-proof.  The pop-out DVD tray I got is really
> flimsy, so must be handled quite gingerly.  I've read that it's been
> upgraded by HP to more solid version in more recent incarnations of the
> Envy.
> 
> I've never used the bluetooth, so I can't testify to how well that
> works, but I've never seen/read any complaints about it, so I'd assume
> it works.
> 
> Of the six or more laptops I've owned in my life, the keyboard of this
> one has been absolutely the most difficult one to get used to.  It seems
> that if I don't hit a key square in the middle of the key, that
> character doesn't make it to the screen.  Same failure if I press the
> key too hard.  This craps on my typing speed immensely,  I used to type
> at over 100 words/minute, but I'm now down to less than half that...
> sucks big time.
> 
> It's nice that it has a big touchpad and I use it all the time. Only
> very seldom to I plug in a usb mouse (e.g., in Blender).  But it's way
> too easy to accidently touch the touchpad, resulting in all kinds of
> random mayhem.  So I modified some code I found to disable/enable the
> touchpad and mapped that code to [Ctrl-`] so that it operates as a
> toggle.  Problem therewith nicely solved.
> 
> Talking with folks on a suse list about the sound problem, I learned
> that they have have no sound problems with there and, further, my
> problem might be a messed up packman stack... whatever that is.  Suse
> also has a much higher kernel version than we do in centos, so switching
> over to suse is in the works.  That's sad because I've been a happy
> RH/centos guy for a long time.
> 
> Hope this review is helpful.

It is, thank you!
Real life experiences are worth a lot to me, thanks again.

--
//Sorin
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] gnome boot problem

[dominic adair-jones]

Ok so I tried alt+d it switched over to text mode. I didn't see any error
it booted right to a black screen. I can ctl+alt+f2 to get to another
screen and I still get the "a start job is running for wait for Plymouth
boot screen to quit"

On Thu, Nov 16, 2017, 5:55 PM Gordon Messmer 
wrote:

> On 11/16/2017 02:01 PM, dominic adair-jones wrote:
> > On Thu, Nov 16, 2017, 4:55 PM Gordon Messmer 
> > wrote:
> >> Alt+d will switch to the text output of the init process.  Press that
> >> combo as soon as you see the boot animation.
> > Not understanding. At what point in the boot process should I be doing
> that
>
> ... as soon as you see the boot animation.  When you see the grey
> screen, use Alt+d on the keyboard to switch to the text output. There,
> you will typically see text that describes why the boot process isn't
> completing.
>
> > and why would I need to do that at all?
>
> Because long ago the debugging text was deemed confusing, and a
> graphical wallpaper was placed over it.
>
> > Seems like it's something wrong
> > with the Plymouth and plymouth-scirpt packages.
>
> That's unlikely.  Those packages are probably just hiding the actual
> problem.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] gnome boot problem

[Pete Biggs]

On Thu, 2017-11-16 at 22:45 +, dominic adair-jones wrote:
> Ok that's what I figured Ive narrowed it down to Plymouth but I haven't
> found much info on what the fix is.

No, plymouth is the process that controls the booting process. It is
not the problem. It is doing exactly what it's supposed to be doing -
waiting for a process to finish before going on to its next task. You
should use journalctl to see what task it is waiting on.


>  As of now I can ctl alt f2 and run
> startx to get to a desktop.

What graphics card do you have? 

>  When I try to run gui (such as keepnote or
> chromium) from within my vms now tho I get errors.

What errors.  

P.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] gnome boot problem

[Gordon Messmer]

On 11/16/2017 02:01 PM, dominic adair-jones wrote:

On Thu, Nov 16, 2017, 4:55 PM Gordon Messmer 
wrote:

Alt+d will switch to the text output of the init process.  Press that
combo as soon as you see the boot animation.

Not understanding. At what point in the boot process should I be doing that


... as soon as you see the boot animation.  When you see the grey 
screen, use Alt+d on the keyboard to switch to the text output. There, 
you will typically see text that describes why the boot process isn't 
completing.



and why would I need to do that at all?


Because long ago the debugging text was deemed confusing, and a 
graphical wallpaper was placed over it.



Seems like it's something wrong
with the Plymouth and plymouth-scirpt packages.


That's unlikely.  Those packages are probably just hiding the actual 
problem.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] gnome boot problem

[dominic adair-jones]

Ok that's what I figured Ive narrowed it down to Plymouth but I haven't
found much info on what the fix is. As of now I can ctl alt f2 and run
startx to get to a desktop. When I try to run gui (such as keepnote or
chromium) from within my vms now tho I get errors.

On Thu, Nov 16, 2017, 5:33 PM Pete Biggs  wrote:

> On Thu, 2017-11-16 at 16:28 -0500, dominic adair-jones wrote:
> > greetings all. running centos 7. i recently performed an upgrade and
> > the server rebooted later in the night. now everytime i start my
> > server its sits at the grey gnome background. i can hit ctl+atl+f2 to
> > get to another console and the error message states "a start job is
> > running for wait for plymouth boot screen to quit". i can ssh into the
> > server but i dont see any obvious issues. this is the brain of my
> > network and houses all my vms and documents. any help would be greatly
> > appreciated.
> >
>
> There's lots of reasons for this - try googling for that message.
>
> A common one is bad video drivers, especially nVidia - nVidia helpfully
> stop supporting certain older cards in the newer drivers, so if you
> have a card that drops support in the most recent driver, you have to
> specifically use an old driver version.
>
> But basically anything that holds up the boot process will eventually
> cause this message - it's not really an error message either, it's just
> telling you that it's waiting for something to happen - the problem is
> elsewhere.
>
> P.
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] gnome boot problem

[Phil Perry]

On 16/11/17 22:32, Pete Biggs wrote:

On Thu, 2017-11-16 at 16:28 -0500, dominic adair-jones wrote:

greetings all. running centos 7. i recently performed an upgrade and
the server rebooted later in the night. now everytime i start my
server its sits at the grey gnome background. i can hit ctl+atl+f2 to
get to another console and the error message states "a start job is
running for wait for plymouth boot screen to quit". i can ssh into the
server but i dont see any obvious issues. this is the brain of my
network and houses all my vms and documents. any help would be greatly
appreciated.



There's lots of reasons for this - try googling for that message.

A common one is bad video drivers, especially nVidia - nVidia helpfully
stop supporting certain older cards in the newer drivers, so if you
have a card that drops support in the most recent driver, you have to
specifically use an old driver version.



...and if you use the nvidia driver packages from elrepo, the 
yum-plugin-nvidia package prevents yum from updating nvidia drivers on 
older hardware where support for that hardware has been dropped.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] USB Serial Ports

[Chris Olson]

We have several CentOS 6 systems that are used in various configurations
of test equipment.  One of the primary functions of these systems is the
connectivity to serial ports of some operational systems that have serial
port control requirements.  Lack of interface bus slots led us to the use
of USB connected serial ports on these CentOS 6 systems.

We first used these USB connected serial ports in our RHEL 5 test equipment
systems.  With RHEL 5, shut down and boot up of the systems would often
cause the serial ports to have a different driver name, even though we had
not changed the ports where the USB devices were plugged in.  This caused
software access problems until we discovered what could be done using the
udev rules to lock in the driver names.

This problem seems to have gone away in our newer systems with CentOS 6,
and we would like to make sure that it does not return.  We are deploying
some of the systems and do not want to have software access issues in the
field where fixes are more difficult.  We would like to know if there is
some underlying factor that has solved this problem for us.  Any ideas on
what to check would be greatly appreciated.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] gnome boot problem

[Pete Biggs]

On Thu, 2017-11-16 at 16:28 -0500, dominic adair-jones wrote:
> greetings all. running centos 7. i recently performed an upgrade and
> the server rebooted later in the night. now everytime i start my
> server its sits at the grey gnome background. i can hit ctl+atl+f2 to
> get to another console and the error message states "a start job is
> running for wait for plymouth boot screen to quit". i can ssh into the
> server but i dont see any obvious issues. this is the brain of my
> network and houses all my vms and documents. any help would be greatly
> appreciated.
> 

There's lots of reasons for this - try googling for that message.

A common one is bad video drivers, especially nVidia - nVidia helpfully
stop supporting certain older cards in the newer drivers, so if you
have a card that drops support in the most recent driver, you have to
specifically use an old driver version.

But basically anything that holds up the boot process will eventually
cause this message - it's not really an error message either, it's just
telling you that it's waiting for something to happen - the problem is
elsewhere.

P.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] gnome boot problem

[dominic adair-jones]

Not understanding. At what point in the boot process should I be doing that
and why would I need to do that at all? Seems like it's something wrong
with the Plymouth and plymouth-scirpt packagesI uninstalled them and
rebooted I didn't get stuck in a loop but I didn't have a gui. I
reinstalled and I'm back at the Plymouth wait error.

On Thu, Nov 16, 2017, 4:55 PM Gordon Messmer 
wrote:

> On 11/16/2017 01:28 PM, dominic adair-jones wrote:
> > now everytime i start my
> > server its sits at the grey gnome background.
>
>
> Alt+d will switch to the text output of the init process.  Press that
> combo as soon as you see the boot animation.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 7 "Set Up Enterprise Login" after update and reboot

[Gordon Messmer]

On 11/16/2017 01:31 PM, Valeri Galtsev wrote:

But before giving login screen upon (re)boot it tries to walk
you through set of screens similar to first login to newly created
account.



Try removing the "firstboot" package or run "/bin/systemctl disable 
firstboot-graphical.service"


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] gnome boot problem

[Gordon Messmer]

On 11/16/2017 01:28 PM, dominic adair-jones wrote:

now everytime i start my
server its sits at the grey gnome background.



Alt+d will switch to the text output of the init process.  Press that 
combo as soon as you see the boot animation.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 7 "Set Up Enterprise Login" after update and reboot

[Richard]

> Date: Thursday, November 16, 2017 15:31:32 -0600
> From: Valeri Galtsev 
>
> Dear Experts,
> 
> Something went astray with one of my systems. Large number of
> updates were installed on it all at once at some point. Then after
> system was rebooted it does strange thing I haven't seen on other
> systems. The machine is set up to boot into graphic login
> ("runlevel 5" to say it using outdated language). But before giving
> login screen upon (re)boot it tries to walk you through set of
> screens similar to first login to newly created account. However,
> along that it forces to to "Set Up Enterprise Login", and there is
> no way to bypass that, or kill this thing to get graphic login
> screen.
> 
> As of this moment I suspect that something went astray during big
> update. I'm not excluding system compromise, however as of this
> moment this seems unlikely, as this system while online is
> constantly watched for "system integrity" (i.e. all files that only
> root should be able to touch are monitored for their checksums,
> etc.) and I would be alerted earlier were anything wrong.
> 
> Rolling back big update (using yum history) failed, I am going to
> restore all on the box to the state before that big update (and I
> also can just wipe the drive and reinstall the system). So I kind
> of have ways out.
> 
> Still, if anyone can shed some light onto what could have happened,
> or what  could have accidentally get changed, it would be really
> great.
> 
> I can ssh to the box, and I can switch it to "runlevel 3" and
> back...
> 
> 
> Thanks in advance to everybody who will respond for your insights!
> 
> Valeri
> 

I ran into the "first boot" (though not "set up enterprise login")
issue after C-7 updates in mid-september. This only happened on one
of three C-7/mate desktop machines. 

With "first boot" I went through the process, including setting up an
account, that was added to wheel as a part of the process. I then
logged out of that and was able to get into my regular account (via
the gui) just fine. I removed that spurious account and cleaned
things up, but ended up in "first boot" again the next time the
machine was rebooted. So, I've now neutered that account, but left it
in place and haven't run into "first boot" again. I haven't been able
to figure out what caused this, yet.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS 7 "Set Up Enterprise Login" after update and reboot

[Valeri Galtsev]

Dear Experts,

Something went astray with one of my systems. Large number of updates were
installed on it all at once at some point. Then after system was rebooted
it does strange thing I haven't seen on other systems. The machine is set
up to boot into graphic login ("runlevel 5" to say it using outdated
language). But before giving login screen upon (re)boot it tries to walk
you through set of screens similar to first login to newly created
account. However, along that it forces to to "Set Up Enterprise Login",
and there is no way to bypass that, or kill this thing to get graphic
login screen.

As of this moment I suspect that something went astray during big update.
I'm not excluding system compromise, however as of this moment this seems
unlikely, as this system while online is constantly watched for "system
integrity" (i.e. all files that only root should be able to touch are
monitored for their checksums, etc.) and I would be alerted earlier were
anything wrong.

Rolling back big update (using yum history) failed, I am going to restore
all on the box to the state before that big update (and I also can just
wipe the drive and reinstall the system). So I kind of have ways out.

Still, if anyone can shed some light onto what could have happened, or
what  could have accidentally get changed, it would be really great.

I can ssh to the box, and I can switch it to "runlevel 3" and back...


Thanks in advance to everybody who will respond for your insights!

Valeri


Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] gnome boot problem

[dominic adair-jones]

greetings all. running centos 7. i recently performed an upgrade and
the server rebooted later in the night. now everytime i start my
server its sits at the grey gnome background. i can hit ctl+atl+f2 to
get to another console and the error message states "a start job is
running for wait for plymouth boot screen to quit". i can ssh into the
server but i dont see any obvious issues. this is the brain of my
network and houses all my vms and documents. any help would be greatly
appreciated.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Issues with Virtualbox

[Abhinay Khanna]

Hi John,

I am getting this error while running it on centos 7. There is an 
initialization error while I try to run this application.


Get Outlook for Android


From: CentOS  on behalf of John R Pierce 

Sent: Thursday, November 16, 2017 10:56:49 PM
To: centos@centos.org
Subject: Re: [CentOS] Issues with Virtualbox

On 11/16/2017 7:46 AM, Abhinay Khanna wrote:
> I am getting an error in intializing VirtualBox . It's giving me an error
>
> "Failed to acquire the VirtualBox COM object".
> Result Code : NS_ERROR_FAILURE
>
> The application is keep getting terminated.

and how does this Oracle product relate to CentOS Linux ?

--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] How to blacklist a device driver (sysemd)

[Gordon Messmer]

On 11/16/2017 08:59 AM, Frank Thommen wrote:
Thanks for the hint.  However as this should only be a temporary 
measure and needs to be done on ca. 100 hosts I'm not sure if we want 
to go through the hassles.  Deploying a textfile is no problem, but 
creating new initrds for differing hardware



Well, use "lsinitrd /boot/" to confirm that the driver is 
actually part of yours.  If so, I suspect you'll at least need to add 
the kernel args.  At a minimum, that'd require distributing a modified 
/etc/default/grub and running "grub2-mkconfig -o /etc/grub2-efi.cfg".  
It might not require any other changes...


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Issues with Virtualbox

[John R Pierce]

On 11/16/2017 7:46 AM, Abhinay Khanna wrote:

I am getting an error in intializing VirtualBox . It's giving me an error

"Failed to acquire the VirtualBox COM object".
Result Code : NS_ERROR_FAILURE

The application is keep getting terminated.


and how does this Oracle product relate to CentOS Linux ?

--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Can't update

[Ilyass Kaouam]

Thank's

2017-11-16 16:57 GMT+00:00 Ulf Volmer :

> On 16.11.2017 17:17, Ilyass Kaouam wrote:
> >> On 16.11.2017 16:03, Ilyass Kaouam wrote:
> >>
> >>> yum update
> >>> Traceback (most recent call last):
> >>
> >> Hard to guess with this limited information. Usually this means either
> >> your yum or your python installation is broken.
> >>
> >> Are you using RPMs from outside of the CentOS or EPEL repos? Manually
> >> installed python versions? Manually installed python modules?
>
> > python-libs-2.6.6-64.el6.x86_64
>
> Please do not top post.
>
> As far as i can see in your list, several RPMs are not from official
> sources. And your version numbers are quite old (from 2015 if i remember
> correctly).
>
> Maybe it will be easier to do a fresh installation instead of debugging
> your current one.
>
> best regards
> Ulf
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>



--
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] How to blacklist a device driver (sysemd)

[Frank Thommen]

On 11/15/2017 07:50 PM, Gordon Messmer wrote:

On 11/15/2017 10:35 AM, Frank Thommen wrote:


I tried with the files
  /etc/modprobe.d/blacklist
  /etc/modprobe.d/blacklist.conf
and with entries
  blacklist mlx5_core
  blacklist mlx5_ib


The "blacklist" entries prevent a module being loaded by its alias
(typically a PCI ID), but not from being loaded if something explicitly
loads it by module name.  Most likely, those modules are included in
your initrd.

I'd suggest using the entries described above, and editing grub.conf to
add arguments to the kernel command line:
rd.driver.blacklist=mlx5_core rd.driver.blacklist=mlx5_ib
... then rebuilding your initrd using "dracut --force"


Thanks for the hint.  However as this should only be a temporary measure 
and needs to be done on ca. 100 hosts I'm not sure if we want to go 
through the hassles.  Deploying a textfile is no problem, but creating 
new initrds for differing hardware


frank
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Can't update

[Ulf Volmer]

On 16.11.2017 17:17, Ilyass Kaouam wrote:
>> On 16.11.2017 16:03, Ilyass Kaouam wrote:
>>
>>> yum update
>>> Traceback (most recent call last):
>>
>> Hard to guess with this limited information. Usually this means either
>> your yum or your python installation is broken.
>>
>> Are you using RPMs from outside of the CentOS or EPEL repos? Manually
>> installed python versions? Manually installed python modules?

> python-libs-2.6.6-64.el6.x86_64

Please do not top post.

As far as i can see in your list, several RPMs are not from official
sources. And your version numbers are quite old (from 2015 if i remember
correctly).

Maybe it will be easier to do a fresh installation instead of debugging
your current one.

best regards
Ulf
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Can't update

[Ilyass Kaouam]

Thank you for your response.

# python -V

Python 2.6.6

# rpm -qa|grep python

gnome-python2-bonobo-2.28.0-3.el6.x86_64

gnome-python2-extras-2.25.3-20.el6.x86_64

python-setuptools-0.6.10-3.el6.noarch

python-unittest2-0.5.1-3.el6.noarch

gnome-python2-gconf-2.28.0-3.el6.x86_64

python-psycopg2-2.6-1.rhel6.x86_64

python-feedparser-5.1.2-2.el6.noarch

python-iwlib-0.1-1.2.el6.x86_64

python-mock-0.8.0-2.el6.noarch

python-imaging-1.1.6-19.el6.x86_64

python-libs-2.6.6-64.el6.i686

dbus-python-0.83.0-6.1.el6.x86_64

python-docutils-0.6-1.el6.noarch

python-dateutil-1.4.1-6.el6.noarch

gnome-python2-desktop-2.28.0-5.el6.x86_64

python-matplotlib-0.99.1.2-1.el6.x86_64

gnome-python2-2.28.0-3.el6.x86_64

gnome-python2-applet-2.28.0-5.el6.x86_64

newt-python-0.52.11-3.el6.x86_64

python-iniparse-0.3.1-2.1.el6.noarch

python-gdata-2.0.11-1.el6.noarch

python-chardet-2.2.1-1.el6.noarch

python-markupsafe-0.9.2-4.el6.x86_64

python-urlgrabber-3.9.1-11.el6.noarch

python-suds-0.4.1-3.el6.noarch

python-psutil-0.6.1-1.el6.x86_64

libxslt-python-1.1.26-2.el6_3.1.x86_64

python-jinja2-2.2.1-2.el6_5.x86_64

gnome-python2-gnome-2.28.0-3.el6.x86_64

python-passlib-1.5.3-1.el6.noarch

hippo-canvas-python-0.3.0-6.el6.x86_64

python-beaker-1.3.1-7.el6.noarch

python-ethtool-0.6-5.el6.x86_64

python-nose-0.10.4-3.1.el6.noarch

python-lxml-2.2.3-1.1.el6.x86_64

python-vobject-0.8.1c-5.el6.noarch

python-yaml-3.09-3.el6.rf.x86_64

python-libs-2.6.6-64.el6.x86_64

python-mako-0.3.4-1.el6.noarch

python-requests-2.6.0-3.el6.noarch

python-devel-2.6.6-64.el6.x86_64

rpm-python-4.8.0-55.el6.x86_64

python-backports-ssl_match_hostname-3.4.0.2-4.el6.centos.noarch

python-reportlab-2.3-3.el6.x86_64

python-six-1.9.0-2.el6.noarch

python-babel-0.9.4-5.1.el6.noarch

gnome-python2-canvas-2.28.0-3.el6.x86_64

python-vatnumber-1.0-1.el6.noarch

gnome-python2-gnomevfs-2.28.0-3.el6.x86_64

at-spi-python-1.28.1-2.el6.centos.x86_64

python-simplejson-2.0.9-3.1.el6.x86_64

python-werkzeug-0.8.3-2.el6.noarch

python-tools-2.6.6-64.el6.x86_64

python-urllib3-1.10.2-1.el6.noarch

libxml2-python-2.7.6-21.el6_8.1.x86_64

python-pycurl-7.19.0-9.el6.x86_64

python-decorator-3.0.1-3.1.el6.noarch

python-openid-2.2.5-7.el6.noarch

python-2.6.6-64.el6.x86_64

gnome-python2-libegg-2.25.3-20.el6.x86_64

python-ldap-2.3.10-1.el6.x86_64

libproxy-python-0.3.0-10.el6.x86_64

python-backports-1.0-5.el6.x86_64

gnome-python2-libwnck-2.28.0-5.el6.x86_64



2017-11-16 16:11 GMT+00:00 Ulf Volmer :

> On 16.11.2017 16:03, Ilyass Kaouam wrote:
>
> > yum update
> > Traceback (most recent call last):
>
> Hard to guess with this limited information. Usually this means either
> your yum or your python installation is broken.
>
> Are you using RPMs from outside of the CentOS or EPEL repos? Manually
> installed python versions? Manually installed python modules?
>
> best regards
> Ulf Volmer
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Can't update

[Ulf Volmer]

On 16.11.2017 16:03, Ilyass Kaouam wrote:

> yum update
> Traceback (most recent call last):

Hard to guess with this limited information. Usually this means either
your yum or your python installation is broken.

Are you using RPMs from outside of the CentOS or EPEL repos? Manually
installed python versions? Manually installed python modules?

best regards
Ulf Volmer
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] HP laptops with CentOS 7?

[ken]

On 11/02/2017 09:29 AM, Sorin Srbu wrote:

Hello all,

I'm looking into getting HP laptops for our department running CentOS 7.

Last time I checked this was some five or so years ago, and when I look at
https://wiki.centos.org/HowTos/Laptops, nothing much seems to have happened
since.

At that time, I had to give up CentOS on laptops, as both Wi-Fi and graphics
wasn't too well supported with CentOS 5 and 6.
Is the situation better now with CentOS 7?

We're only allowed to buy the HP, Dell and Apple brands here at this
university, so what I'm looking at is basically HP. Apple is not of interest
because of their pricing.
All our desktops and laptops are HP's running Windows 7 and 10, and they
work fine.
We do have some Dells, but only in the server area.
Currently all our CentOS 6 and 7 workstations are custom built OEMs used for
molecular modelling, but are now getting rather long in the tooth.
I have a laptop at the office as a backup, running Ubuntu 16 LTS, as that
was the only thing that found all the hardware properly at the time.
However, I'd rather not go down that particular road for various reasons.

The thing that interests me first and foremost is whether the latest CentOS
7 iteration will install right out of the box with all hardware properly
detected, no manual compiling of drivers or jumping through hoops to _maybe_
getting stuff to work with eg a HP Elitebook 850 G4.

Anybody care to chime in with a comment or hint on the laptop situation
and-or their experiences?

For two years now I've been semi-happily using an HP Envy with the 
high-end Nvidia graphics card.  Installing CentOS7, everything worked 
out of box except the wifi.  The problem there was due to the drivers 
requiring a v.3.5 kernel which centos doesn't yet have.  There were some 
very occasional glitches in the video, but subsequent upgrades to the 
nvidia drivers eventually fixed those.


Audio worked initially, but after installing vlc I've had problems which 
I haven't been able to track down, so the sound with some apps just 
doesn't work.  Notably, anything audio through firefox doesn't work 
except that which uses flashplayer.  Audacity and vlc work just fine.


The body of the laptop is solid, made mostly out of carbon fiber... it 
seemed like it's bullet-proof.  The pop-out DVD tray I got is really 
flimsy, so must be handled quite gingerly.  I've read that it's been 
upgraded by HP to more solid version in more recent incarnations of the 
Envy.


I've never used the bluetooth, so I can't testify to how well that 
works, but I've never seen/read any complaints about it, so I'd assume 
it works.


Of the six or more laptops I've owned in my life, the keyboard of this 
one has been absolutely the most difficult one to get used to.  It seems 
that if I don't hit a key square in the middle of the key, that 
character doesn't make it to the screen.  Same failure if I press the 
key too hard.  This craps on my typing speed immensely,  I used to type 
at over 100 words/minute, but I'm now down to less than half that... 
sucks big time.


It's nice that it has a big touchpad and I use it all the time. Only 
very seldom to I plug in a usb mouse (e.g., in Blender).  But it's way 
too easy to accidently touch the touchpad, resulting in all kinds of 
random mayhem.  So I modified some code I found to disable/enable the 
touchpad and mapped that code to [Ctrl-`] so that it operates as a 
toggle.  Problem therewith nicely solved.


Talking with folks on a suse list about the sound problem, I learned 
that they have have no sound problems with there and, further, my 
problem might be a messed up packman stack... whatever that is.  Suse 
also has a much higher kernel version than we do in centos, so switching 
over to suse is in the works.  That's sad because I've been a happy 
RH/centos guy for a long time.


Hope this review is helpful.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Issues with Virtualbox

[Abhinay Khanna]

Hi Team,

I am getting an error in intializing VirtualBox . It's giving me an error

"Failed to acquire the VirtualBox COM object".
Result Code : NS_ERROR_FAILURE

The application is keep getting terminated.

TIA

Get Outlook for Android

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Can't update

[Ilyass Kaouam]

Hi,


I can't do update:

yum update
Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in 
yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 298, in user_main
errcode = main(args)
 File "/usr/share/yum-cli/yummain.py", line 110, in main
 base = cli.YumBaseCli()
  File "/usr/share/yum-cli/cli.py", line 72, in __init__
output.YumOutput.__init__(self)
  File "/usr/share/yum-cli/output.py", line 307, in __init__
self.reported_error_msgs = dict((k, False) for (k, v) in
ERRORS_TO_KBASE_ARTICLES.iteritems())
NameError: global name 'ERRORS_TO_KBASE_ARTICLES' is not defined

Any suggestion ?

Thank's​
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS-announce Digest, Vol 153, Issue 2

[centos-announce-request]

Send CentOS-announce mailing list submissions to
centos-annou...@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-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@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-2017:3221 Moderate CentOS 7 php Security Update
  (Johnny Hughes)
   2. CEBA-2017:3202 CentOS 6 autofs BugFix Update (Johnny Hughes)
   3. CEBA-2017:3199 CentOS 6 device-mapper-multipath   BugFix Update
  (Johnny Hughes)
   4. CEBA-2017:3206 CentOS 6 fence-agents BugFix Update (Johnny Hughes)
   5. CEBA-2017:3197 CentOS 6 kexec-tools BugFix Update (Johnny Hughes)
   6. CEBA-2017:3205 CentOS 6 ksh BugFix Update (Johnny Hughes)
   7. CEBA-2017:3209 CentOS 6 lvm2 BugFix Update (Johnny Hughes)
   8. CEBA-2017:3201 CentOS 6 nfs-utils BugFix Update (Johnny Hughes)
   9. CEBA-2017:3207 CentOS 6 util-linux-ng BugFix  Update
  (Johnny Hughes)
  10. CEBA-2017:3198 CentOS 6 cloud-init BugFix Update (Johnny Hughes)
  11. CEBA-2017:3203 CentOS 6 sos BugFix Update (Johnny Hughes)
  12. CESA-2017:3200 Important CentOS 6 kernel Security Update
  (Johnny Hughes)


--

Message: 1
Date: Wed, 15 Nov 2017 21:26:52 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2017:3221 Moderate CentOS 7 php
SecurityUpdate
Message-ID: <20171115212652.ga41...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2017:3221 Moderate

Upstream details at : https://access.redhat.com/errata/RHSA-2017:3221

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
121238a8a61a493e7dcbacfae325d82822bc2786134f3b824506dc9059ae35fe  
php-5.4.16-43.el7_4.x86_64.rpm
6ec9411ef98c72615a21eff38d93df7b436a5a7240b22bebe40df18a33b92825  
php-bcmath-5.4.16-43.el7_4.x86_64.rpm
edb93644bcde6ca82632a22d8b71a6920634558c0b9aa63c633a44dca08f1dff  
php-cli-5.4.16-43.el7_4.x86_64.rpm
bf306bbf00ce22c080b284d267c143df8c4430483fd49c27f589ea162d7a1e8e  
php-common-5.4.16-43.el7_4.x86_64.rpm
bfc2743370757a464003379348b1bab863f5f975c9926ec39a3e97405725a8e1  
php-dba-5.4.16-43.el7_4.x86_64.rpm
ec43a80352ddaa0aeccd5709f8165c6d33ea39d78e41d5cca4baa9a054be1e8a  
php-devel-5.4.16-43.el7_4.x86_64.rpm
e6d79b17c0a69659ca56771eaef810859e5aa297381eb8f46546cd4d09d742fa  
php-embedded-5.4.16-43.el7_4.x86_64.rpm
77884c190002fb9a4feba68b1bcd1164e9705f34e382520b1c7daeb19afa80c9  
php-enchant-5.4.16-43.el7_4.x86_64.rpm
266f022532ac1a3d3c70380141f3bcb3e3bb354d459300fe512da706d1ebfc7f  
php-fpm-5.4.16-43.el7_4.x86_64.rpm
d0c162b23743ed7e1ecfda994a8b039bacfee401e90fd85ffcacf12bda99816b  
php-gd-5.4.16-43.el7_4.x86_64.rpm
ccee165a03c579f4df3d951d1fa95c2e118effc15ad40317f1500afe9c62183e  
php-intl-5.4.16-43.el7_4.x86_64.rpm
40a1e1f0af8f3e52e55ee77de96600316865ddcaf2615d89948286029ae31d69  
php-ldap-5.4.16-43.el7_4.x86_64.rpm
9ce4096325d89e0301f7e012dd49188a195898efb6a4087cb2fe2ccb677ba859  
php-mbstring-5.4.16-43.el7_4.x86_64.rpm
948e0a481f5e0b6128966e2bae9620895ebffc6120014e18922ae8ace9fc3fd1  
php-mysql-5.4.16-43.el7_4.x86_64.rpm
e5b9842911c143c46eb81ebe163e47a38486be65a26cb8cd496851217793a196  
php-mysqlnd-5.4.16-43.el7_4.x86_64.rpm
cc23b6eebe80887a8c1465050476b7aed5d6a7f58f11936d6c476099aadd5f30  
php-odbc-5.4.16-43.el7_4.x86_64.rpm
27a58dc3f4915eaf49886802fade65893d5a1937050c85515a2aed4180483471  
php-pdo-5.4.16-43.el7_4.x86_64.rpm
eb880d14c75b86feb3568e803a1cf3042b041face51c70b8f9fe870990bc0628  
php-pgsql-5.4.16-43.el7_4.x86_64.rpm
84074f9f87417d86591cf9510b20c614b8cd717132bd1f5457138e9ef2e04a52  
php-process-5.4.16-43.el7_4.x86_64.rpm
a1bddbda8c9bcfc79b5da0755c77d339ab242df213ceef29794de204770327bc  
php-pspell-5.4.16-43.el7_4.x86_64.rpm
ec866e83f7318bd59a45daf6c22d18fd7a3ff1748a11261be31cfc7cfafe889d  
php-recode-5.4.16-43.el7_4.x86_64.rpm
fe6fa4427503d5bc07422c9df527cd0af609fc69b6372eb128e16731ae3d48cf  
php-snmp-5.4.16-43.el7_4.x86_64.rpm
b78413a695cd567203ba8dde95d14e55c633500845bd626b938e25cd0353b242  
php-soap-5.4.16-43.el7_4.x86_64.rpm
0722fd103a7674a843bcc5fac8c26f5db7297ec5270139f760a240aa60e1222b  
php-xml-5.4.16-43.el7_4.x86_64.rpm
bdefe8e96bc1450c03abb3e4759ed378868e6be857cffda2a972e6161d63ca8a  
php-xmlrpc-5.4.16-43.el7_4.x86_64.rpm

Source:
038eb5e24ba9714f6298f8e36afa24d6cfee0fad1ed6fa444c0c2ed90ca97794  
php-5.4.16-43.el7_4.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS



--

Message: 2
Date: Wed, 15 Nov 2017 21:31:06 +
From: Johnny Hughes 
To: centos-annou...

Re: [CentOS] Fwd: [CentOS-announce] CESA-2017:3200 Important CentOS 6 kernel Security Update

[Christian Anthon]

Found the answer myself. RHBA should of course have been RHSA so the 
correct link is


https://access.redhat.com/errata/RHSA-2017:3200

Cheers, Christian.

On 16-11-2017 09:53, Christian Anthon wrote:
The redhat errata link leads to a 404 page. Anybody know what this is 
about?


Cheers, Christian.



 Forwarded Message 
Subject: [CentOS-announce] CESA-2017:3200 Important CentOS 6 
kernel Security Update

Date: Wed, 15 Nov 2017 21:38:19 +
From: Johnny Hughes 
Reply-To: centos@centos.org
To: centos-annou...@centos.org



CentOS Errata and Security Advisory 2017:3200 Important

Upstream details at : https://access.redhat.com/errata/RHBA-2017:3200

The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )

i386:
5d284bfa08a5793517ec76a246754d2f4645ac012336d27f1c5807380a4e256e 
kernel-2.6.32-696.16.1.el6.i686.rpm
f85553367eece6ba51f2965caecd7ce09aafb0ce62160da55a135cfff6188114 
kernel-abi-whitelists-2.6.32-696.16.1.el6.noarch.rpm
95a65d3b9b1aa4a02457dd53ad321c1118e937d452bd4082498141a7ea20ce7a 
kernel-debug-2.6.32-696.16.1.el6.i686.rpm
3f5383b34f2933c3be876852126b2d577cfc22951f2e7d859b7efc8ce8c239e9 
kernel-debug-devel-2.6.32-696.16.1.el6.i686.rpm
13442b6c43647b8160f8cc15d099f078a6b2550d00b322857c067d82b9cadb6c 
kernel-devel-2.6.32-696.16.1.el6.i686.rpm
2d8b989b7f10dabed4df203bc4989dca906e6acfde39ed24585c22b739926974 
kernel-doc-2.6.32-696.16.1.el6.noarch.rpm
e5b26dc63d1fce0e966b7d5c8695cd7648ac716f93a547963536b09e01ce74f5 
kernel-firmware-2.6.32-696.16.1.el6.noarch.rpm
4f1380ddb2db054ea518d9186c04e4148644f5f4f9c201fcc1a563b9e4ef487f 
kernel-headers-2.6.32-696.16.1.el6.i686.rpm
f04384bf339595bedfdcc7bc008a59968f090bade0a6b8148d9eb22eac4964f5 
perf-2.6.32-696.16.1.el6.i686.rpm
58f5d8fef44bd215d01559cdc53fee903b3f9f6544c67c67fcafd4587d8ca4b1 
python-perf-2.6.32-696.16.1.el6.i686.rpm


x86_64:
9490bf087394c9c7e98444728438ab41ac99a44fbea99e8b22b39f7cebe7b1ca 
kernel-2.6.32-696.16.1.el6.x86_64.rpm
f85553367eece6ba51f2965caecd7ce09aafb0ce62160da55a135cfff6188114 
kernel-abi-whitelists-2.6.32-696.16.1.el6.noarch.rpm
9b754666727e4b8802f448a84279eff3a02285a227af4fa3199ed761798d7965 
kernel-debug-2.6.32-696.16.1.el6.x86_64.rpm
3f5383b34f2933c3be876852126b2d577cfc22951f2e7d859b7efc8ce8c239e9 
kernel-debug-devel-2.6.32-696.16.1.el6.i686.rpm
0da6ec2f05ed53d70b115c475f86b01ddbc11f85fe116127f648316265c565a3 
kernel-debug-devel-2.6.32-696.16.1.el6.x86_64.rpm
2fa496dc3ece90d97886030754340d8dd4f5816c3cad2182de275b1f0007ef75 
kernel-devel-2.6.32-696.16.1.el6.x86_64.rpm
2d8b989b7f10dabed4df203bc4989dca906e6acfde39ed24585c22b739926974 
kernel-doc-2.6.32-696.16.1.el6.noarch.rpm
e5b26dc63d1fce0e966b7d5c8695cd7648ac716f93a547963536b09e01ce74f5 
kernel-firmware-2.6.32-696.16.1.el6.noarch.rpm
6f451f1500fbcefac11541065c607cca80afcd74910dd72b54d8a659826835aa 
kernel-headers-2.6.32-696.16.1.el6.x86_64.rpm
e72ba7452350e398030e8d65bd53830cb003964c1444cc823378db5792b6588b 
perf-2.6.32-696.16.1.el6.x86_64.rpm
ce90fe8a317164248e18390182d9a4d4e1cf60c2aa13fd07d3df53bc8561ea1b 
python-perf-2.6.32-696.16.1.el6.x86_64.rpm


Source:
2909a2f8bd8cda02978aa674da4a7b0fbbabc65d817131193bdd50a11bf60555 
kernel-2.6.32-696.16.1.el6.src.rpm






___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Fwd: [CentOS-announce] CESA-2017:3200 Important CentOS 6 kernel Security Update

[Christian Anthon]

The redhat errata link leads to a 404 page. Anybody know what this is about?

Cheers, Christian.



 Forwarded Message 
Subject: 	[CentOS-announce] CESA-2017:3200 Important CentOS 6 kernel 
Security Update

Date:   Wed, 15 Nov 2017 21:38:19 +
From:   Johnny Hughes 
Reply-To:   centos@centos.org
To: centos-annou...@centos.org



CentOS Errata and Security Advisory 2017:3200 Important

Upstream details at : https://access.redhat.com/errata/RHBA-2017:3200

The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )

i386:
5d284bfa08a5793517ec76a246754d2f4645ac012336d27f1c5807380a4e256e  
kernel-2.6.32-696.16.1.el6.i686.rpm
f85553367eece6ba51f2965caecd7ce09aafb0ce62160da55a135cfff6188114  
kernel-abi-whitelists-2.6.32-696.16.1.el6.noarch.rpm
95a65d3b9b1aa4a02457dd53ad321c1118e937d452bd4082498141a7ea20ce7a  
kernel-debug-2.6.32-696.16.1.el6.i686.rpm
3f5383b34f2933c3be876852126b2d577cfc22951f2e7d859b7efc8ce8c239e9  
kernel-debug-devel-2.6.32-696.16.1.el6.i686.rpm
13442b6c43647b8160f8cc15d099f078a6b2550d00b322857c067d82b9cadb6c  
kernel-devel-2.6.32-696.16.1.el6.i686.rpm
2d8b989b7f10dabed4df203bc4989dca906e6acfde39ed24585c22b739926974  
kernel-doc-2.6.32-696.16.1.el6.noarch.rpm
e5b26dc63d1fce0e966b7d5c8695cd7648ac716f93a547963536b09e01ce74f5  
kernel-firmware-2.6.32-696.16.1.el6.noarch.rpm
4f1380ddb2db054ea518d9186c04e4148644f5f4f9c201fcc1a563b9e4ef487f  
kernel-headers-2.6.32-696.16.1.el6.i686.rpm
f04384bf339595bedfdcc7bc008a59968f090bade0a6b8148d9eb22eac4964f5  
perf-2.6.32-696.16.1.el6.i686.rpm
58f5d8fef44bd215d01559cdc53fee903b3f9f6544c67c67fcafd4587d8ca4b1  
python-perf-2.6.32-696.16.1.el6.i686.rpm

x86_64:
9490bf087394c9c7e98444728438ab41ac99a44fbea99e8b22b39f7cebe7b1ca  
kernel-2.6.32-696.16.1.el6.x86_64.rpm
f85553367eece6ba51f2965caecd7ce09aafb0ce62160da55a135cfff6188114  
kernel-abi-whitelists-2.6.32-696.16.1.el6.noarch.rpm
9b754666727e4b8802f448a84279eff3a02285a227af4fa3199ed761798d7965  
kernel-debug-2.6.32-696.16.1.el6.x86_64.rpm
3f5383b34f2933c3be876852126b2d577cfc22951f2e7d859b7efc8ce8c239e9  
kernel-debug-devel-2.6.32-696.16.1.el6.i686.rpm
0da6ec2f05ed53d70b115c475f86b01ddbc11f85fe116127f648316265c565a3  
kernel-debug-devel-2.6.32-696.16.1.el6.x86_64.rpm
2fa496dc3ece90d97886030754340d8dd4f5816c3cad2182de275b1f0007ef75  
kernel-devel-2.6.32-696.16.1.el6.x86_64.rpm
2d8b989b7f10dabed4df203bc4989dca906e6acfde39ed24585c22b739926974  
kernel-doc-2.6.32-696.16.1.el6.noarch.rpm
e5b26dc63d1fce0e966b7d5c8695cd7648ac716f93a547963536b09e01ce74f5  
kernel-firmware-2.6.32-696.16.1.el6.noarch.rpm
6f451f1500fbcefac11541065c607cca80afcd74910dd72b54d8a659826835aa  
kernel-headers-2.6.32-696.16.1.el6.x86_64.rpm
e72ba7452350e398030e8d65bd53830cb003964c1444cc823378db5792b6588b  
perf-2.6.32-696.16.1.el6.x86_64.rpm
ce90fe8a317164248e18390182d9a4d4e1cf60c2aa13fd07d3df53bc8561ea1b  
python-perf-2.6.32-696.16.1.el6.x86_64.rpm

Source:
2909a2f8bd8cda02978aa674da4a7b0fbbabc65d817131193bdd50a11bf60555  
kernel-2.6.32-696.16.1.el6.src.rpm



--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
centos-annou...@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos