Re: [CentOS] usb problem on Dell Latitude 3570
On 07/02/2018 01:49 AM, johan.vermeul...@telenet.be wrote: > Hello All, > > after update to Centos7.5 all our Latitudes 3570 - some 150- suffer usb > problems. > Plug and play doesn't work any more, people need to insert usb devices - > mouse, keyboard, eidreader - first and then boot > in order to use them. > > dmesg | tail -n15 gives these EM: > > [ 25.164396] usb 1-8: device descriptor read/64, error -110 > [ 25.418387] usb 1-8: new full-speed USB device number 6 using xhci_hcd > [ 30.571460] usb 1-8: device descriptor read/64, error -110 > [ 53.084387] xhci_hcd :00:14.0: Timeout while waiting for setup device > command > [ 53.084435] xhci_hcd :00:14.0: Timeout while waiting for stop endpoint > command > [ 53.285343] usb 1-8: device not accepting address 7, error -62 > [ 58.300369] xhci_hcd :00:14.0: ERROR mismatched command completion event > [ 58.300384] xhci_hcd :00:14.0: Command completion event does not match > command > [ 58.300394] xhci_hcd :00:14.0: ERROR mismatched command completion event > [ 58.300401] xhci_hcd :00:14.0: ERROR mismatched command completion event > [ 58.300408] xhci_hcd :00:14.0: ERROR mismatched command completion event > [ 58.300415] xhci_hcd :00:14.0: ERROR mismatched command completion event > [ 58.300421] xhci_hcd :00:14.0: ERROR mismatched command completion event > [ 58.300428] xhci_hcd :00:14.0: ERROR mismatched command completion event > [ 58.300435] xhci_hcd :00:14.0: ERROR mismatched command completion event > [ 58.300441] xhci_hcd :00:14.0: ERROR mismatched command completion event > [ 58.300448] xhci_hcd :00:14.0: ERROR mismatched command completion event > > Googling this is see some posts with similar problems, but none on Centos7 > and none resolved. > I suppose this is some driver-shift-update in Centos7.5. > We are running MATE desktop, if that could be an issue > > Many thanks for any advise. > Jul 1 07:15:06 pygeum kernel: [ 10.85] usb 3-1: device descriptor > read/64, error -110 > Jul 1 07:15:06 pygeum kernel: [ 26.460443] usb 3-1: device descriptor > read/64, error -110 > Jul 1 07:15:06 pygeum kernel: [ 26.696308] usb 3-1: new full-speed USB > device number 3 using xhci_hcd > Jul 1 07:15:06 pygeum kernel: [ 31.836441] usb 3-1: device descriptor > read/64, error -110 > Jul 1 07:15:06 pygeum kernel: [ 47.452351] usb 3-1: device descriptor > read/64, error -110 > Jul 1 07:15:06 pygeum kernel: [ 47.560390] usb usb3-port1: attempt power > cycle > Jul 1 07:15:06 pygeum kernel: [ 48.212366] usb 3-1: new full-speed USB > device number 4 using xhci_hcd > Jul 1 07:15:06 pygeum kernel: [ 53.468442] xhci_hcd :39:00.0: Timeout > while waiting for setup device command > Jul 1 07:15:06 pygeum kernel: [ 58.88] xhci_hcd :39:00.0: Timeout > while waiting for setup device command > Jul 1 07:15:06 pygeum kernel: [ 59.052359] usb 3-1: device not accepting > address 4, error -62 > Jul 1 07:15:06 pygeum kernel: [ 59.180277] usb 3-1: new full-speed USB > device number 5 using xhci_hcd > Jul 1 07:15:06 pygeum kernel: [ 64.220453] xhci_hcd :39:00.0: Timeout > while waiting for setup device command > Jul 1 07:15:06 pygeum kernel: [ 69.596378] xhci_hcd :39:00.0: Timeout > while waiting for setup device command > Jul 1 07:15:06 pygeum kernel: [ 69.804359] usb 3-1: device not accepting > address 5, error -62 > Jul 1 07:15:06 pygeum kernel: [ 69.805459] usb usb3-port1: unable to > enumerate USB device > > Greetings, J. > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos Interesting. I get the following errors from my external monitor plugged into a USB C port on a Dell XPS 9360. This is under Ubuntu 18.04, kernel 4.15.0-23-generic. When I unplug and replug the USB C cable, the error goes away, but I don't believe it is a cable or connector problem. Most of the time the external monitor works even with these errors, but occasionally I have to reboot to get it to work. Biggest problem is it takes a long time to boot when it gets these errors. Jul 1 07:15:06 pygeum kernel: [ 10.85] usb 3-1: device descriptor read/64, error -110 Jul 1 07:15:06 pygeum kernel: [ 26.460443] usb 3-1: device descriptor read/64, error -110 Jul 1 07:15:06 pygeum kernel: [ 26.696308] usb 3-1: new full-speed USB device number 3 using xhci_hcd Jul 1 07:15:06 pygeum kernel: [ 31.836441] usb 3-1: device descriptor read/64, error -110 Jul 1 07:15:06 pygeum kernel: [ 47.452351] usb 3-1: device descriptor read/64, error -110 Jul 1 07:15:06 pygeum kernel: [ 47.560390] usb usb3-port1: attempt power cycle Jul 1 07:15:06 pygeum kernel: [ 48.212366] usb 3-1: new full-speed USB device number 4 using xhci_hcd Jul 1 07:15:06 pygeum kernel: [ 53.468442] xhci_hcd :39:00.0: Timeout while waiting for setup device command Jul 1
Re: [CentOS] LVM problems
On 02.07.2018 18:23, Thomas Schweikle wrote: > System boots into emergency mode because it does not find any of the > logical volumes defined, because it does not enable the LVM volume > group. > > Giving "lvm", then "vgchange -a y", followed by CTRL-D continues to > boot to full multiuser mode. maybe 'rootdelay=5' as kernel parameter will solve this issue. best regards Ulf ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] LVM problems
Hi! Folowing setup: 4x HD 500TB 1st: /boot 4GB, remaining part LVM 2nd, 3rd, 4th all LVM LVM volumes: - 30G /root - 8G /var - 8G /tmp - 200G /var/log/pgsql - 800G /var/spacewalk - 4G swap System boots into emergency mode because it does not find any of the logical volumes defined, because it does not enable the LVM volume group. Giving "lvm", then "vgchange -a y", followed by CTRL-D continues to boot to full multiuser mode. How can I make the system to enable the volume group and automatically boot to full multiuser mode? Looks there is something broken at some point and ths system does not enable the volume group. Any idea? -- Thomas ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Firefox 60.0.1.0 ESR Progress?
On 07/02/2018 06:57 AM, Sean wrote:
Is there a way to track CentOS's progress on RHSA-2018-2113?
https://access.redhat.com/errata/RHSA-2018:2113
Thanks!
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
This is what I do and it works well, script run as root after
downloading compiled tarball from upstream.
--
#!/bin/bash
TMP=`mktemp -d /tmp/ff.`
mv $1 ${TMP}/
pushd ${TMP}
FFOX=`echo $1 |sed -e s?"\.tar\.bz2"?""?`
tar -jxf ${1}
chown -R root:root firefox
mv firefox /usr/local/${FFOX}
popd
pushd /usr/local
rm -f firefox && ln -s ${FFOX} firefox
popd
rm -rf ${TMP}
-
$1 is the FireFox downloaded from upstream (compiled)
Installing it as root means I am safe from malware over-writing bits of
it, but I do have to manually download.
/usr/local/firefox/firefox then starts it - and old versions are
preserved in case something breaks (I just change which one the
/usr/local/firefox link points to - though I almost never have to revert)
It's not RPM but there are too many advantages to newer FireFox for me
to wait.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 7.5 on Vmware
I agree with Nataraj about kvm/qemu/libvirt, we have 10+ hypervisors running it and it meets our needs but none of them are particularly heavily loaded. The only caution I would give is that there are occasions (mainly in the snapshot-associated arena) where the man page may simply say "do this" but, when you run the command on a distribution focusing on longer term support, you find it's not yet supported. And there are areas where Red Hat flatly states that there are issues (snapshots of the operating environment rather that just disk images). While this is true (for example, reverting to a snapshot reverts causes the system to have the date/time of the revert as well), we have still found value in these kinds of snapshots in a development environment. Save the Date 2018 Momentum User Conference September 25 - 28, 2018 Athens, Georgia: The Classic Center Leroy Tennison Network Information/Cyber Security Specialist E: le...@datavoiceint.com 2220 Bush Dr McKinney, Texas 75070 www.datavoiceint.com TThis message has been sent on behalf of a company that is part of the Harris Operating Group of Constellation Software Inc. These companies are listed here . If you prefer not to be contacted by Harris Operating Group please notify us . This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged or confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message. From: CentOS on behalf of Gregory P. Ennis Sent: Sunday, July 1, 2018 9:53 PM To: CentOS mailing list Subject: [EXTERNAL] Re: [CentOS] Centos 7.5 on Vmware On 06/28/2018 02:03 PM, Gregory P. Ennis wrote: > Everyone, > > I am in the initial study phase of putting together a larger virtual > server while using Centos 7.5 as the operating system of choice for > the > individual virtual machines. > > How do you all like VMware for this, or what other software allows > for > the development of virtural servers that use Centos 7.5 > > Thanks ahead of time for giving me a head start with your > experiences > It would be helpful if you gave more details about what you were looking for? Are you planning to run a bare metal hypervisor, or vmware under Linux or windows? What are you performance requirements? IO? CPU? What will the VM's be used for? Do guests requre a graphics console? Various vmware products ranging from ESXI to vmware workstation are very popular. I've run several of them. They work. I now use the Linux included, kvm/qemu based Red Hat/CentOS virtualization and it meets my needs very well for general testing/development, email server, web server kind of stuff. I also use this setup along with spice to run test systems with various graphic GUI's. I would not say that my virt servers are very heavily loaded. I have a Dell R210 running CentOS6 KVM/Qemu and a Dell XPS 9360 running Ubuntu 18.04 with kvm/qemu. If you prefer fancy mangement GUI's over writing scripts and editing config files, vmware might be better for you. kvm/qemu does include virt-manager which is a fairly simply GUI to create and manage VM's, but the user interface is not as comprehensive as the interface for managing ESXi. Red Hat does have their high end virtualization products, of which I believe at least 1 is a bare metal hypervisor. I have no personal experience with those products, though if client came to me with need, I would examine and seriously consider the Redhat products. One advantage to the kvm/qemu solution or possibly the redhat virtualization product is more integrated support. When I ran vmware, I used to run into situations where I wanted to beta test the newest release of some random linux distribution only to find out that vmware had not yet implemented support for the graphics driver or some other new hardware feature being used in the OS that I was trying to test. In this way, kvm/qemu feels more integrated. Like other software, kvm/qemu has bugs here and there, but overall, I'm very happy with it and I like the price of using it under CentOS and Ubuntu. I see clients all the time, go out and spend a fortune on huge vmware clusters, that end up very lightly loaded and could easily be run on a simple kvm/qemu server running under CentOS (or even one of the desktop virtualization solutions) with a backup server for redundancy, so I suggest to consider what your requirements really are. You could always go with Redhat if you require support. Nataraj - Nataraj, Thank you very much for your comments. I have not put together a virtual machine at this point, so my tree
[CentOS] Firefox 60.0.1.0 ESR Progress?
Is there a way to track CentOS's progress on RHSA-2018-2113? https://access.redhat.com/errata/RHSA-2018:2113 Thanks! ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] cron.daily and others, not running
Hello James,
On Mon, 2 Jul 2018 11:31:07 + James Pearson
wrote:
> wwp wrote:
>
> >
> > On Mon, 02 Jul 2018 09:59:17 +0100 Pete Biggs wrote:
> >
> >>>
> >>> So, service is running but what could happen that makes /etc/cron.* not
> >>> being fired?
> >>
> >> You don't say, but if this is CentOS 7, then cron.daily/weekly/monthly
> >> is run using anacron, not cron.
> >
> > Oops, yes CentOS 7, sorry.
> >
> > For the record:
> > # service anacron status
> > Redirecting to /bin/systemctl status anacron.service
> > Unit anacron.service could not be found.
> > You have mail in /var/spool/mail/root
> >
> > Sure, anacron is not installed. So how could stuff in
> > /etc/cron.{daily,weekly}
> > work until June 02?
> > Probably because it didn't need anacron at all, no? I've looked at yum
> > history, it doesn't talk at all about anacron (but cronie-anacron) so
> > it's not been installed and removed).
>
> anacron is part of the cronie-anacron package
>
> There is no anacron service file ... anacron is run by cron - see below:
Oh-oh, thanks for your lights.
> >> It's configured in /etc/anacrontab and is usually run once a day by the
> >> script /etc/cron.hourly/0anacron - cron.hourly is still run by cron.
> >> If the script doesn't exist, then anacron won't run and cron.daily etc
> >> won't happen.
> >
> > There's a /etc/cron.d/0hourly here:
> > -
> > # Run the hourly jobs
> > SHELL=/bin/bash
> > PATH=/sbin:/bin:/usr/sbin:/usr/bin
> > MAILTO=root
> > 01 * * * * root run-parts /etc/cron.hourly
> > -
> >
> > I'm still not sure that talking about anacron is relevant here, and I
> > don't know why either if you say it should be anacron in CentOS 7.
>
> grep for anacron in /var/log/cron* for any clues
Hah!
Log excerpts, something that may matter but that I missed at first:
anacron[22814]: Job `cron.daily' locked by another anacron - skipping
Don't know exactly what went wrong there, but I killed a few processes
and I'll see how it behaves naturally this night, if it still fails I
know have enough to observe, understand and fix. I think you helped me
understanding few things here and how to fix it, thanks, James and Pete!
Regards,
--
wwp
pgp5Gv4OtOQUr.pgp
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] cron.daily and others, not running
Hello Pete,
On Mon, 02 Jul 2018 12:31:55 +0100 Pete Biggs wrote:
> > For the record:
> > # service anacron status
> > Redirecting to /bin/systemctl status anacron.service
> > Unit anacron.service could not be found.
> > You have mail in /var/spool/mail/root
>
> It's not a service. As I said, it's run using a script in
> /etc/cron.hourly
Got it!
> > Sure, anacron is not installed. So how could stuff in
> > /etc/cron.{daily,weekly}
> > work until June 02?
>
> Don't know. But that's how cron.daily is processed and has been since
> CentOS7 was released. In fact I think CentOS 6 even used anacron.
> Perhaps you have inadvertently removed an important file like
> /etc/anacrontab or /etc/cron.hourly/0anacron
>
> > Probably because it didn't need anacron at all, no? I've looked at yum
> > history, it doesn't talk at all about anacron (but cronie-anacron) so
> > it's not been installed and removed).
>
> Yes, anacron *is* cronie-anacron
>
> > > It's configured in /etc/anacrontab and is usually run once a day by the
> > > script /etc/cron.hourly/0anacron - cron.hourly is still run by cron.
> > > If the script doesn't exist, then anacron won't run and cron.daily etc
> > > won't happen.
> >
> > There's a /etc/cron.d/0hourly here:
> > -
> > # Run the hourly jobs
> > SHELL=/bin/bash
> > PATH=/sbin:/bin:/usr/sbin:/usr/bin
> > MAILTO=root
> > 01 * * * * root run-parts /etc/cron.hourly
> > -
>
> OK. So that's the bit of cron config that tells it to run the stuff in
> cron.hourly - what is in /etc/cron.hourly/ ? If there is no 0anacron
> file in /etc/cron.hourly/ the cron.daily and cron.weekly will not be
> processed.
>
> >
> > I'm still not sure that talking about anacron is relevant here, and I
> > don't know why either if you say it should be anacron in CentOS 7.
> >
> Because that's how cron.daily etc is processed in CentOS 7. I'm not
> entirely sure why you don't believe me.
Can't always believe without proof, I'm afraid (I'm sure you've been
answered incorrect/incomplete stuff many times here or elsewhere too).
BUT, your answers and James' brought me some light, now I understand
how it all works and how anacron is a concept that is not a service,
and I thank you all for your help :-), appreciated.
Regards,
--
wwp
pgpfV3hesbVxp.pgp
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] cron.daily and others, not running
>
> For the record:
> # service anacron status
> Redirecting to /bin/systemctl status anacron.service
> Unit anacron.service could not be found.
> You have mail in /var/spool/mail/root
It's not a service. As I said, it's run using a script in
/etc/cron.hourly
>
> Sure, anacron is not installed. So how could stuff in /etc/cron.{daily,weekly}
> work until June 02?
Don't know. But that's how cron.daily is processed and has been since
CentOS7 was released. In fact I think CentOS 6 even used anacron.
Perhaps you have inadvertently removed an important file like
/etc/anacrontab or /etc/cron.hourly/0anacron
> Probably because it didn't need anacron at all, no? I've looked at yum
> history, it doesn't talk at all about anacron (but cronie-anacron) so
> it's not been installed and removed).
Yes, anacron *is* cronie-anacron
>
>
> > It's configured in /etc/anacrontab and is usually run once a day by the
> > script /etc/cron.hourly/0anacron - cron.hourly is still run by cron.
> > If the script doesn't exist, then anacron won't run and cron.daily etc
> > won't happen.
>
> There's a /etc/cron.d/0hourly here:
> -
> # Run the hourly jobs
> SHELL=/bin/bash
> PATH=/sbin:/bin:/usr/sbin:/usr/bin
> MAILTO=root
> 01 * * * * root run-parts /etc/cron.hourly
> -
OK. So that's the bit of cron config that tells it to run the stuff in
cron.hourly - what is in /etc/cron.hourly/ ? If there is no 0anacron
file in /etc/cron.hourly/ the cron.daily and cron.weekly will not be
processed.
>
> I'm still not sure that talking about anacron is relevant here, and I
> don't know why either if you say it should be anacron in CentOS 7.
>
Because that's how cron.daily etc is processed in CentOS 7. I'm not
entirely sure why you don't believe me.
P.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] cron.daily and others, not running
wwp wrote:
>
> On Mon, 02 Jul 2018 09:59:17 +0100 Pete Biggs wrote:
>
>>>
>>> So, service is running but what could happen that makes /etc/cron.* not
>>> being fired?
>>
>> You don't say, but if this is CentOS 7, then cron.daily/weekly/monthly
>> is run using anacron, not cron.
>
> Oops, yes CentOS 7, sorry.
>
> For the record:
> # service anacron status
> Redirecting to /bin/systemctl status anacron.service
> Unit anacron.service could not be found.
> You have mail in /var/spool/mail/root
>
> Sure, anacron is not installed. So how could stuff in /etc/cron.{daily,weekly}
> work until June 02?
> Probably because it didn't need anacron at all, no? I've looked at yum
> history, it doesn't talk at all about anacron (but cronie-anacron) so
> it's not been installed and removed).
anacron is part of the cronie-anacron package
There is no anacron service file ... anacron is run by cron - see below:
>> It's configured in /etc/anacrontab and is usually run once a day by the
>> script /etc/cron.hourly/0anacron - cron.hourly is still run by cron.
>> If the script doesn't exist, then anacron won't run and cron.daily etc
>> won't happen.
>
> There's a /etc/cron.d/0hourly here:
> -
> # Run the hourly jobs
> SHELL=/bin/bash
> PATH=/sbin:/bin:/usr/sbin:/usr/bin
> MAILTO=root
> 01 * * * * root run-parts /etc/cron.hourly
> -
>
> I'm still not sure that talking about anacron is relevant here, and I
> don't know why either if you say it should be anacron in CentOS 7.
grep for anacron in /var/log/cron* for any clues
James Pearson
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] cron.daily and others, not running
Hello Pete,
On Mon, 02 Jul 2018 09:59:17 +0100 Pete Biggs wrote:
> >
> > So, service is running but what could happen that makes /etc/cron.* not
> > being fired?
>
> You don't say, but if this is CentOS 7, then cron.daily/weekly/monthly
> is run using anacron, not cron.
Oops, yes CentOS 7, sorry.
For the record:
# service anacron status
Redirecting to /bin/systemctl status anacron.service
Unit anacron.service could not be found.
You have mail in /var/spool/mail/root
Sure, anacron is not installed. So how could stuff in /etc/cron.{daily,weekly}
work until June 02?
Probably because it didn't need anacron at all, no? I've looked at yum
history, it doesn't talk at all about anacron (but cronie-anacron) so
it's not been installed and removed).
> It's configured in /etc/anacrontab and is usually run once a day by the
> script /etc/cron.hourly/0anacron - cron.hourly is still run by cron.
> If the script doesn't exist, then anacron won't run and cron.daily etc
> won't happen.
There's a /etc/cron.d/0hourly here:
-
# Run the hourly jobs
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
01 * * * * root run-parts /etc/cron.hourly
-
I'm still not sure that talking about anacron is relevant here, and I
don't know why either if you say it should be anacron in CentOS 7.
Regards,
--
wwp
pgpX0eOFCyPRo.pgp
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] cron.daily and others, not running
> > So, service is running but what could happen that makes /etc/cron.* not > being fired? You don't say, but if this is CentOS 7, then cron.daily/weekly/monthly is run using anacron, not cron. It's configured in /etc/anacrontab and is usually run once a day by the script /etc/cron.hourly/0anacron - cron.hourly is still run by cron. If the script doesn't exist, then anacron won't run and cron.daily etc won't happen. P. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] usb problem on Dell Latitude 3570
Hello All, after update to Centos7.5 all our Latitudes 3570 - some 150- suffer usb problems. Plug and play doesn't work any more, people need to insert usb devices - mouse, keyboard, eidreader - first and then boot in order to use them. dmesg | tail -n15 gives these EM: [ 25.164396] usb 1-8: device descriptor read/64, error -110 [ 25.418387] usb 1-8: new full-speed USB device number 6 using xhci_hcd [ 30.571460] usb 1-8: device descriptor read/64, error -110 [ 53.084387] xhci_hcd :00:14.0: Timeout while waiting for setup device command [ 53.084435] xhci_hcd :00:14.0: Timeout while waiting for stop endpoint command [ 53.285343] usb 1-8: device not accepting address 7, error -62 [ 58.300369] xhci_hcd :00:14.0: ERROR mismatched command completion event [ 58.300384] xhci_hcd :00:14.0: Command completion event does not match command [ 58.300394] xhci_hcd :00:14.0: ERROR mismatched command completion event [ 58.300401] xhci_hcd :00:14.0: ERROR mismatched command completion event [ 58.300408] xhci_hcd :00:14.0: ERROR mismatched command completion event [ 58.300415] xhci_hcd :00:14.0: ERROR mismatched command completion event [ 58.300421] xhci_hcd :00:14.0: ERROR mismatched command completion event [ 58.300428] xhci_hcd :00:14.0: ERROR mismatched command completion event [ 58.300435] xhci_hcd :00:14.0: ERROR mismatched command completion event [ 58.300441] xhci_hcd :00:14.0: ERROR mismatched command completion event [ 58.300448] xhci_hcd :00:14.0: ERROR mismatched command completion event Googling this is see some posts with similar problems, but none on Centos7 and none resolved. I suppose this is some driver-shift-update in Centos7.5. We are running MATE desktop, if that could be an issue Many thanks for any advise. Greetings, J. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS7/Mate Qt bugs/features?
James Pearson wrote: >> >> Thanks - given that it works OK on F28, I had a look through the Marco >> bugs and commits and came across: >> >> https://github.com/mate-desktop/marco/issues/324 >> >> which appears to describe the problem and using the patch at: >> >> https://github.com/mate-desktop/marco/commit/59756b8d77dfbd0948d7e4d3349477173aa2728a >> >> does indeed appear to fix the problem when 'compositing-manager' is set >> to 'true' ... which is good > > I reported this as an EPEL bug - and a new build with the fix is > currently in the EPEL7 testing repo : > >https://bugzilla.redhat.com/show_bug.cgi?id=1591973 In case anyone is interested, the EPEL7 repo has now been updated with the fixed version of marco James Pearson ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] cron.daily and others, not running
Hello there,
I've just noticed that scripts in /etc/cron.{daily,weekly,...} are not
launched for several weeks (I noticed a `locate` not finding a recently
added binary). Exactly, it's since June 02, and `# service cron status`
says:
Redirecting to /bin/systemctl status crond.service
* crond.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor
preset: enabled)
Active: active (running) since Sat 2018-06-02 19:22:57 CEST; 4 weeks 1 days
ago
Main PID: 1379 (crond)
Tasks: 1
Memory: 5.8M
CGroup: /system.slice/crond.service
`-1379 /usr/sbin/crond -n
Jun 02 19:22:57 ladybug systemd[1]: Started Command Scheduler.
Jun 02 19:22:57 ladybug systemd[1]: Starting Command Scheduler...
Jun 02 19:22:57 ladybug crond[1379]: (CRON) INFO (RANDOM_DELAY will be scaled
with factor 73% if used.)
Jun 02 19:22:57 ladybug crond[1379]: (CRON) INFO (running with inotify support)
Jun 30 11:22:01 ladybug crond[1379]: (*system*) RELOAD (/etc/crontab)
Jun 30 20:06:01 ladybug crond[1379]: (*system*) RELOAD (/etc/crontab)
---
So, service is running but what could happen that makes /etc/cron.* not
being fired?
/etc/sysconfig/crond hasn't been touched and defines an empty CRONDARGS=.
Stuff in /etc/crontab is running as expected, but it's maybe not
related anyway.
Regards,
--
wwp
pgp1HztBw8Cyg.pgp
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
