hello

Yesterday I tried to fix my Lenovo Legion y720 laptops keyboard backlight. They do not work with linux so I search on the internet and found some and tried fix them.

I tried to changed some of .conf files and it didnt work. The broken files are /usr/lib/ tmpfiles.d/udisks2.conf and /usr/lib/modprobe.d/nvidia.conf

When I start my laptop the screen goes black and blinking sencor appers. By using Ctrl+Alt+f2 and using eopkg check I managed to see the broken files.

Now I cannot change them back and dont know what the original writing in files were. How can I fix them?

    Maasi This is why it's always a good idea to take a backup of A) your system and B) system files you plan on changing.

    When you say you cannot change them do you mean you don't know the original content or don't have permissions to?

      Also you should not modify the files under /usr/lib/... but you should rather take a copy under /etc/... and modify them there as these are stateless packages this way if you mess up with the config file you just delete it and the system will fallback on the default configuration.

        Justin lesson learn. I do not know the original contest, didnt see before changing it

        does anybody know how to fix them? just delete them? or do I need to install solus all over again and lose all my data?

          Maasi Backup your user data before re-installing. Boot into the Solus live environment, open the drive and copy the data.

          Maasi sudo eopkg it --reinstall udisks
          Same for your nvidia thing but make sure to reinstall the same nvidia package as the one you're currently using and not just any random package that contains nvidia in its name.

            Staudey

            The following packeage(s) are already installed and are not going to be imstalled again: nvidia-glx-driver-common udisks
            system error. Program terminated.
            Repo item reinstall not found.

            I tried, not working

              Maasi Sounds like you entered reinstall instead of --reinstall

              But, now that we know the name of the packages, try a simple
              sudo eopkg it --reinstall nvidia-glx-driver-common udisks

              Don't forget the dashes! πŸ˜‰

                Maasi I fubar'd my own system yesterday due to impatience and spent 10 hours in tty and live disk.
                What Staudey gave you: https://getsol.us/articles/troubleshooting/general-troubleshooting/en/ saved my life.
                I have a hard time believing you have no broken packages with that grep command.

                try: sudo eopkg check | grep Broken
                at least you can see what happened.
                sudo eopkg rdb is fast and deletes another variable.
                moreover----read that help article and use those two terminal commands to check your lts

                how I wrapped this up in 12 hours? throwing everything at the wall until finally using that troubleshooting page...

                  Maasi There's no way you're getting that message if you just enter that command correctly.
                  Are you perhaps mistakenly putting a space between the dashes and reinstall? It should be exactly like this:
                  --reinstall all characters connected, without anything in between.

                    Staudey Unless they've removed their repository, then you wouldn't find anything. 😁

                    Staudey it was space, thank you.

                    now nvidia is fine and udisks is still broken. I reinstall them and check after that I reboot, still black screen.

                      brent

                      tried the link, the one eith linux-lts does not work but linux-current works. saw clr-boot-manager boot and my computer have the same kernels.

                      also tried sudo eopkg rdb.

                      nvidia is not broken now but udisks still is broken. I reboot the system still black screen.

                      the comparison thing was just to see if version numbers matched, I belive. then there was a plan i the help page from there.

                      blank screen patience. my ctrl+alt+whatever took a lot longer to appear.
                      you are right about one thing: when it was close to come back to life for me, udisk and nvidia were prominent.

                      it took a LONG time but the grep command finally worked in TTY. I had to manually remove and reinstall a lot of broken stuff before command worked--I know it goes by fast but I wrote as muc broken down on paper as I could remember. then rdb. then reboot. then after 10 hours FINALLY the login greeter except the wrong one. then boot into a HIDEOUS pitch-black OS called openbox. It's like a pitch black room and the flashlight is the rightclick.

                      Apparently we nuked our display managers somehow. took forever to get lightdm to work. And budgie itself was gone as well as some necessay gnome apps.
                      then AFTER grep "fixed" all packages in TTY, I ran the same command in the UI/OS to find more broken. Once that was settled I am back in business with some minor installs.

                      Coinciding, for me, with the update, is me ripping a lot of programs out this week (for space) without considering deps. That's on me. Then I aborted a 200-package update while SYNCING Friday (accident).

                      I am whole again.. the reason this reply is so long is there might be on thing you can take away to get you further down the road while my trauma is still freshπŸ™‚

                      edit/fixed one typo, left the rest...