similar to: GUI boot failure after latest shim (etc) updates

Hi, I?m running a special initrd generated for SystemImager with a special dracut module that relies on plyouth scripted theme. It works perfectly on CentOS-6, CentOS-7, OpenSUSE-42.3, Fedora-29 (not tested later) and used to work on CentOS-8.0 Since CentOS-8.1 was released, IT chrashes with the following error: Plymouthd crash 913: ply_event_loop_watch_for_timeout: Assertion `seconds >

Hi all! I was playing with plymouth themes on a c7 box. I found a page on redhat, in their rhel7 documentation that describes how to change to a different plymouth screen: plymouth-set-default-theme --list to find out what themes are installed. then I installed the remaining bunch the yum had available. so then installing one by doing plymouth-set-default-theme <theme name> dracut -f

Hi, I am very new to mailing lists so please excuse any mistakes I make regarding ettiquete etc. On a home network (Windows/Apple/Lunux) everybody has co-operated happily. I recently swapped my Linux system from Mint (Mate) to Debian (KDE) Buster. I can no longer access the Windows machine's printer form Debian. I have tried many things and done a great deal of googling but cannot seem to

On Tue, Oct 04, 2016 at 01:24:52PM +0000, Sorin Srbu wrote: > > -----Original Message----- > > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > > Behalf Of Frank Saporito > > Sent: den 4 oktober 2016 15:00 > > To: centos at centos.org > > Subject: Re: [CentOS] Alternative GUI > > > > I looked at Mate Desktop for a CentOS

Background: I have 2 SMB Servers; one is configured to be the Preferred Master (fserver), the other (upstairs) is configured to just share some files. I want it to connect and update the WINS configuration on the Preferred Master. Configuration files for both servers are attached. Also worth mentioning that both the 'fserver' and 'upstairs' reside on the same network. Some

Hi Roger et.al, Following messages are logged by journalctl when powering off. --snip-- Jun 25 11:26:32 fourpi01 containerd[1326]: time="2020-06-25T11:26:32.638781892+10:00" level=info msg="Stop CRI service" Jun 25 11:26:32 fourpi01 systemd[1]: Stopping Network UPS Tools - power device driver controller... Jun 25 11:26:32 fourpi01 upsdrvctl[258149]: Network UPS Tools - UPS

https://bugs.freedesktop.org/show_bug.cgi?id=100035 Bug ID: 100035 Summary: nouveau runtime pm causes soft lockups and hangs during boot Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

Hi all, This is happening on a Samba 3.0.1 PDC-controlled domain, so I'm not sure if the issue is Samba-related. If not, perhaps somebody can point me in the right direction. One of my users has a printer connected to his Win2k PC (name UPSTAIRS-SMALL). Printing to it from another (WinXP) workstation fails miserably. I tried to go back to first principles and go Start->Run

> > But, what happens if you let the kernel post install scripts do the work > or setting up the initrd things? Initially, I just rebooted from LiveCD and left Grub,kernel and dracut do their job with the defaults, but unfortunately, boot process stops at initrd (dracut) stage with the following error: [ 197.768159] localhost.localdomain dracut-initqueue[252]: Warning: Could > not

Hello, I have just installed CentOS 7 onto two servers and applied all the current patches. There are currently two kernels installed: # rpm -q kernel kernel-3.10.0-123.el7.x86_64 kernel-3.10.0-123.9.3.el7.x86_64 However, if I reboot the servers they both start up on the older kernel: # uname -r 3.10.0-123.el7.x86_64 I would have expected them to restart using kernel 3.10.0-123.9.3. I know I

A while back I added the pidgin repo to my yum configuration and installed pidgin. it has automatically updated itself a time or two since without trouble. but now that Pidgin 2.1.0 is out, it won't update properly. Yum finds a couple of libpurple packages to update as well as pidgin-devel, but not the pidgin package itself: --> Populating transaction set with selected packages. Please

Yannis Milios wrote: >> But, what happens if you let the kernel post install scripts do the >> work or setting up the initrd things? > > Initially, I just rebooted from LiveCD and left Grub,kernel and dracut do > their job with the defaults, but unfortunately, boot process stops at > initrd (dracut) stage with the following error: > > [ 197.768159]

Once upon a time, Johnny Hughes <johnny at centos.org> said: > The issues should now be resolved. > > If you just mount /mnt/sysimage, set an ip address and upgrade (to get > th new shim) .. then: > > yum reinstall <latest-version> I'm curious - why does the kernel need to be reinstalled? The shim-x64 package installs its files directly to the EFI partition

CentOS Errata and Bugfix Advisory 2014:1030 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1030.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7568b606796a506f71743a9ecfcf173289d3c585b05ebbeda42226068fd23794 plymouth-0.8.3-27.el6.centos.1.i686.rpm

CentOS Errata and Bugfix Advisory 2019:C001 This is a bug fix for for the following CentOS Bug: https://bugs.centos.org/view.php?id=15522 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 0ae55996308b507ba878377b35b71225c1fa28d4fb453c938a0d5dc9568501cc mokutil-15-2.el7.centos.x86_64.rpm

When we consolidated all CentOS Distro builders in a new centralized setup, covering all arches (so basically x86_64, i386, ppc64le, ppc64, aarch64 and armhfp those days), we wanted also to add redundancy where it was possible to. The interesting "SecureBoot" corner case came on the table and we had to find a different way to build the following packages: - shim (both signed and

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

<snip> >Your system was most likely rebuilding the initrd, and you interrupted >it leaving you with a broken initrd. > >Try booting off a rescue disk and chroot into the install, and run: > >dracut -f -v > >to regenerate all the initrds. > >Also, you don't need to reinstall the kernel but just do a 'yum >update' to get everything up to the latest

CentOS Errata and Security Advisory 2020:3217 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2020:3217 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 920e0075aa2fd067ef46bdaeac583b32d8d9871c01db67f1e2ec4b107926df04 shim-unsigned-ia32-15-7.el7_9.x86_64.rpm

CentOS Errata and Security Advisory 2020:3217 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2020:3217 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 46d78ecee751d736f35445677f13e9513bcc73e01c21e8b46e19f6d5f9fdb44f mokutil-15-7.el7_9.x86_64.rpm