reloading udev rules - failed

MintSpider

Tonight I reinstalled Solus At the end of the 455 package `[✓] Syncing filesystems [✓] Updating dynamic library cache [✓] Updating clr-boot-manager [✓] Running depmod on [✓] Updating hwdb [✓] Updating graphical [✓] Updating system users [✓] Updating systemd tmpfiles [✓] Reloading systemd configuration [✓] Re-executing systemd [✓] Compiling AppArmor profiles [✓] Reloading AppArmor profiles [✓] Compiling glib-schemas [✓] Rebuilding font cache [✓] Updating mimetype database [✓] Updating icon theme cache: hicolor [✓] Updating icon theme cache: solus-sc [✓] Updating icon theme cache: breeze-dark [✓] Updating icon theme cache: breeze [✓] Updating desktop database [✓] Updating manpages database [✓] Updating SSL certificates [✗] Reloading udev rules Plasma from the testing iso to my 2nd Alienware M15x laptop.
updates, eopkg ended with this:
success
success
success
kernel 4.20.10-111.current success
success
driver configuration success
success
success
success
success
success
success
success
success
success
success
success
success
success
success
success
success
failed

A copy of the command output follows:

[✗] Reloading udev rules failed

A copy of the command output follows:

peter@erma ~ $`

Machine details are below.
I seem to have this issue with the Current kernel, but LTS works just fine.
Before I install the LTS kernel, I wanted to reach out and test on this clean install.
Any suggestions?

peter@erma ~ $ inxi -Fz System: Host: erma Kernel: 4.18.14-95.current x86_64 bits: 64 Desktop: KDE Plasma 5.14.5 Distro: Solus 3.9999 Machine: Type: Portable System: Alienware product: M15x v: A07 serial: <filter> Mobo: Alienware model: N/A v: A07 serial: <filter> BIOS: Alienware v: A07 date: 07/21/2010 Battery: ID-1: BAT0 charge: 40.8 Wh condition: 40.8/57.7 Wh (71%) CPU: Topology: Dual Core model: Intel Core i5 M 540 bits: 64 type: MT MCP L2 cache: 3072 KiB Speed: 2527 MHz min/max: 1197/2527 MHz Core speeds (MHz): 1: 2527 2: 2527 3: 2527 4: 2527 Graphics: Device-1: NVIDIA G92M [GeForce GTX 260M] driver: nouveau v: kernel Display: x11 server: X.Org 1.20.2 driver: nouveau unloaded: fbdev,modesetting,vesa resolution: 1600x900~60Hz OpenGL: renderer: NV92 v: 3.3 Mesa 18.3.3 Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k4.18.14-95.current Network: Device-1: Intel 82577LC Gigabit Network driver: e1000e IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter> Device-2: Broadcom and subsidiaries BCM43224 802.11a/b/g/n driver: bcma-pci-bridge IF-ID-1: wlp7s0b1 state: down mac: <filter> Drives: Local Storage: total: 298.09 GiB used: 7.24 GiB (2.4%) ID-1: /dev/sda vendor: Seagate model: ST9320423AS size: 298.09 GiB Partition: ID-1: / size: 292.41 GiB used: 7.24 GiB (2.5%) fs: ext4 dev: /dev/sda1 Sensors: System Temperatures: cpu: 66.0 C mobo: N/A gpu: nouveau temp: 51 C Fan Speeds (RPM): N/A Info: Processes: 180 Uptime: 34m Memory: 7.78 GiB used: 1.93 GiB (24.8%) Shell: bash inxi: 3.0.32

MintSpider

My machine is having issues booting up with both:
4.20.10-111.current
4.18.14-95.current

The login screen shakes, does take my password, but the screen never fully gets to the desktop.
I see patches of the login manager and desktop at the same time.
To shut down the machine, I have to go into a TTY and run the command from there.
I am going to run this command to install LTS:
sudo clr-boot-manager set-timeout 5 && sudo eopkg it linux-lts && sudo clr-boot-manager update

MintSpider

This was in the TTY after installing the LTS kernel.
As you can see "Applying udev rules = success".
Still having the login manager / desktop issues, which makes the system unusable.
From TTY I did run this to fully test my system, and all seems to be fine in that regard:
sudo usysconf run -f && sudo eopkg rdb && sudo eopkg up

MintSpider

Here is what I am seeing upon boot.
Possibly something messed up with the 455 updates at once?
May try again tomorrow with Budgie to see how that goes.

Justin

I don't believe the number of updates would cause this kind of issue, as long as all the usysconf tick boxes were OK.

Looks like the display manager is having issues, I'd like to see how Budgie goes.

MintSpider

Justin I did not believe it was the updates either, so was really questioning that myself.
One thing I should do is reinstall from USB and reboot before running updates. See how that boots.

MintSpider

Something is definitely up with installing the Plasma desktop, whether via the testing iso or on top of another DE.
Tonight I installed Budgie, which went well (still have the udev issue though), updated, then installed Plasma with this command:
sudo eopkg install -c desktop.kde.core
Here is Plasma after boot and trying to use the menu:

@Justin and @JoshStrobl do you know of any issues with installing Plasma from the iso and updates or via eopkg?

Justin

I've installed using the Plasma ISO about 4 or 5 times now and had no issues. Solus Plasma uses SDDM as the display manager. Maybe it doesn't like something in your hardware. If you're keen to eliminate it, it may work with lightdm.

MintSpider

Justin SDDM worked fine as part of the whole iso on my hardware until the recent QT5 upgrade which broke boot on the LTS kernel.
I took the opportunity to borrow my machine to test run Peppermint on that hardware for another project. @JoshStrobl remembers that part! 😉
The SDDM problems have been since the full install after the QT5 fix.

Khio

Hi, had the same issue when i tried Solus Plasma.

Try this : before login in press CTRL ALT F2, log in in the terminal and run sudo nvidia-xconfig, and reboot

(( Edit : you seems to be running nouveau driver, maybe you will need to install the proprietary one, for the GTX 260M : nvidia-340-glx-driver for the LTS kernel or nvidia-340-glx-driver-current for the current one, might also need nvidia-340-glx-driver-32bit ))

MintSpider

Khio At this point I had Nvidia installed after installing Solus Budgie, with the 340.107 driver for my NVIDIA G92M [GeForce GTX 260M].
I tried your suggestion:

peter@erma ~ $ sudo nvidia-xconfig
Password:

WARNING: Unable to locate/open X configuration file.

sh: pkg-config: command not found
New X configuration file written to 'etc/X11/xorg.conf

After reboot I still had the same screen issues, but at a lower resolution! 😁
Think I am going to restart tonight testing fully with the installed iso, and test rebooting etc before running the updates.
Thanks so much for your assistance.
So glad it is my 2nd laptop. Hence why I have Budgie on my 1st!

MintSpider

Have reinstalled from the Solus Plasma iso.
Install went smooth, as did the reboot and login.
I "turned it off and on again" and all is well... at this point.
Have not installed anything, including updates or Nvidia.
Heading to work. Shall continue this evening.
(Note to self - check installed and repo versions of sddm)

sudo eopkg info sddm
installed = version 0.18.0, release 12
repository = version 0.18.0, release 16

MintSpider

sudo eopkg up = 455 packages to be downloaded and installed.
Packages downloaded fast then a checklist ran, with the expected: Reloading udev rules ... failed
Packages then installed fine, and another checklist was ran, with the same udev message.
Ran a full shutdown and boot-up.
In Grub, the default kernel is 4.20.10-111.current. Alternative boot kernel is 4.18.14-95.current, which came from the testing iso.
Entered my password, and noticed that sddm kept reappearing as the desktop tried to load, and this is now what I am looking at:

Would love to take a video as the screen is currently rotating between that photo and the desktop image as fullscreen.

So, in recap, all I did was install from the testing iso, restart, download the updates, and restart again.
Nvidia was not touched.

Went into TTY and checked the info on sddm. Now on release 16 as expected.
Fully checked the system with:
sudo usysconf run -f && sudo eopkg rdb && sudo eopkg up
Again, all checked fine, except udev, which I know I can solve by installing the LTS kernel, but this sddm boot-up issue is totally bugging me.
Recently there was a QT5 update which needed a fix the next day. Has anyone else fully installed Solus Plasma since that time?

MintSpider

While in TTY:
sudo eopkg remove sddm
sudo eopkg install lightdm
sudo shutdown now

@Justin let's see what happens when I power up again....

Ok, that really didn't work, as it just took me to the TTY login, which now gives me a new puzzle!

Justin

MintSpider Might need to sudo systemctl enable lightdm and/or sudo systemctl start lightdm and see what the second one says.

MintSpider

Justin Testing that now.... thanks for the input.
You are an absolute genius... that was the part I was missing. Very much appreciated.
Now the Plasma Desktop boots smoothly and the menu works as expected.

Still, one should not have to jump through hoops like this.
We need someone else to install Solus Plasma from scratch again and see how they do.

MintSpider

Quick search suggests installing slick-greeter, so did:
sudo eopkg install slick-greeter
After shutdown and restart, I got to the GUI login, recognised slick-greeter from Budgie including the background photo, and booted into the Plasma desktop.
However, I am still getting the same patchy graphics, and a menu system that is basically unusable.
Giving up on Plasma on this machine.
Something definitely changed not for the better in the update after installing from the testing iso.

Justin

MintSpider Happy to hear it's working!

MintSpider

For the record, I still plan on solving the udev issue.
Found this site on udev - https://linuxconfig.org/tutorial-on-how-to-write-basic-udev-rules-in-linux
Ran the command
sudo udevadm control --reload
which seemed to work without error, but when next I installed a package (playonlinux) the Reloading of udev rules failed again.

MintSpider

Back to the original theme of this thread: udev rules
Running Solus Plasma on kernel 4.20.10-111.current
udev not reloading is giving me 2 major issues:
1) Any software install takes ages, since this happens: [✗] Reloading udev rules failed
2) usb drives and devices are not auto-recognised. This has been tested with thumbdrives and gamepads.
Has anyone experienced this and/or have a solution?

Before reinstalling Solus Plasma on this machine I would run the LTS kernel and udev worked great.
However, unsure why, but the LTS kernel will no longer boot to a GUI login.
Note: I am running Solus Budgie on my main laptop (another Alienware M15x) with
the LTS kernel of 4.9.158-126.lts just fine.