(Regress) removing nvidia-575xx-utils breaks dependency

Support System Updates
1

This is a regress of :
https://forum.manjaro.org/t/error-config-video-nvidia-575xx-conflicts-with-config-s-video-nvidia/181812/11

I cannot upgarde todays kernel-meta-packages. because of broken depencies.
this is what I get:

:: Starting full system upgrade...
:: Replace linux615 with core/linux-meta? [Y/n] y
:: Replace linux615-headers with core/linux-headers-meta? [Y/n] y
:: Replace linux615-virtualbox-host-modules with extra/linux-virtualbox-host-modules-meta? [Y/n] y
resolving dependencies...
looking for conflicting packages...
:: nvidia-utils-580.82.09-1 and nvidia-575xx-utils-575.64.05-1 are in conflict (nvidia-libgl). Remove nvidia-575xx-utils? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing nvidia-575xx-utils breaks dependency 'nvidia-575xx-utils=575.64.05' required by lib32-nvidia-575xx-utils
:: removing nvidia-575xx-utils breaks dependency 'nvidia-575xx-utils=575.64.05' required by linux612-nvidia-575xx-open
:: removing linux615 breaks dependency 'linux615' required by linux615-nvidia-575xx-open
:: removing nvidia-575xx-utils breaks dependency 'nvidia-575xx-utils=575.64.05' required by linux615-nvidia-575xx-open
:: removing nvidia-575xx-utils breaks dependency 'nvidia-575xx-utils=575.64.05' required by linux66-nvidia-575xx-open
:: removing nvidia-575xx-utils breaks dependency 'nvidia-575xx-utils' required by nvidia-575xx-settings

…Might be related to the recent changes in mhwd ?
I am running the 575-driver using kernel 6.12.x

2

Providing terminal output

:bangbang: Tip :bangbang:

When posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, before AND after the pasted text. Like this:

```
pasted text
```

Or three (3) tilde signs, like this:

~~~
pasted text
~~~

This will just cause it to be rendered like this:

Sed
sollicitudin dolor
eget nisl elit id
condimentum
arcu erat varius
cursus sem quis eros.

Instead of like this:

Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.

Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.

Thereby increasing legibility thus making it easier for those trying to provide assistance.

For more information, please see:

As I’m a moderator on the forum, I have taken the liberty of doing this for you, this time.

:bangbang::bangbang: Additionally

If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:

LC_ALL=C bluetoothctl

This will just cause the terminal output to be in English, making it easier to understand and debug.

Note that the above text is partially pre-prepared as a general introduction for new forum Users. Please take the time to to understand how it is done and encourage quality responses.

3

I will expand linux-meta packages to the recently added additional nvidia packages. You could also remove all meta packages and all currently installed linux615 packages manually or simply wait for the fix.

4

Sorry for the late reply..quite busy today.

I tried to remove the 6.15 kernel via mhwd, but got same depency-errors. So it was not removed.

I am not in a hurry, so I will wait for the fix and will report back as soon as available.

5

Just fyi:

I ended up with:

Removed all 5.15 related packages one by one, means worked myself through all the depencies:

-1. metapackages

-2. 3rd party kernel modules(Nvidia + Virtualbox)

-3. removed the kenel and it’s headers

Within mhwd, I am now left with an active and installed 6.12 kernel and would have the option to activate the allready installed 6.16 version.

Not sure if this was the way to go, but it seems working for me.

1 Like
6

mhwd-kernel is a pacman wrapper script which detect the current running kernel and its extramodules. Based on that info it will install similar packages based on the to be installed kernel.

pamac on the other hand has a similar feature to additionally install extramodules when detected automatically by just specify a new kernel to be installed.

7

Thanks for clarification. So mhwd-kernel and pamac are using the pacman-db.

It seems to be, that I have solved this issue…at least for me.

But, in general, if not doing this manual uninstalling (meta, kernel, modules), the system in its curent state, does not allow to upgrade from kernel 5.14 to 5.16, caused by the broken depencies.

So I hopefully this gets fixed. Except the need to stay on nvidia-575, I have a pretty much defaulted system. No further kernel tweak or AUR based dkms-modules.

8

Are there any fixes yet ?

Currently I am not able to:

-upgrade from NVIDIA 575.x to 580.x

-removing the installed Kernel 6.16 (I am running on 6.12)

Every time I got broken depencies like i.e. when trying to remove kernel 6.16 (to be able to change the NVDIA driver):

Removal of linux616-nvidia-575xx-open violates depency »linux616-nvidia-575xx-open«, required from linux-nvidia-575xx-open-meta

Things are really getting messy.

9

Just remove the linux-nvidia-575xx-open-meta package first:

pamac remove linux-nvidia-575xx-open-meta

or

sudo pacman -R linux-nvidia-575xx-open-meta

Removing it won’t break anything. You might also want to remove the linux-meta package if you have it installed on your system, as it currently ensures that linux616 is installed.

The purpose of the various linux -meta packages is to prevent users from running an unsupported kernel that has been removed from the repos. When linux615 was removed from the repos recently, the linux-meta package ensured that linux616 was installed, and removed linux615 from the user’s system.

If you want to manage your kernels yourself, then you can remove the linux -meta packages.

4 Likes
10

28 days later :zombie: :zombie:

It’s a package conflict - you decide which packages you want installed and which packages you don’t want installed.

1 Like
11

Unfortunately dependency issues sometimes need to be resolved before you are able to complete your goal. These issues arise often (but not always) due to failing to properly maintain one’s system.

If you don’t have a clue how to resolve such dependency issues, perhaps your first question could have been something to the extent:

“How do I resolve dependency issues when attempting to update Nvidia drivers?”

and then progress to explain the problem in greater detail while offering full examples of warnings encountered, in context, along with your system information (inxi output).

Your comments seem to indicate that you’re currently running kernel 6.12 (LTS) with an option to reboot into 6.16 if you wish.

If everything is running well enough for the time being, I’d suggest waiting for the update to automatically be applied, which should arguably kick in the next time a kernel you have installed reaches EOL.

Regards.

12

@dmt Thnaks for clarifiaction. I was not sure, If I “should” uninstall the meta-packages without harming my (still..default-)system.

After removing the meta-package, I was able to switch the NV-drivers to 580.x and back to 575.x withot issues.

@soundofthunder

>If you don’t have a clue how to resolve such dependency issues, perhaps your first question could have been something to the extent:…..

That’s nonsense. As you can see within the entire thread(and the therad I refering to), all started and with the some issues in mhwd, which have been resolved.

I was not sure, if removing kernel-based meta-packages was a good idea.

My understanding of “meta-package” is, that there plenty of packages bundles into one “meta-package”.

So…again, I was not sure, if removing such a “core-meta-package” might harm/remove the “real” packages.

It’s in general not a good idea to remove the current running kernel…IMHO.

So..I didn’t touch the meta-package.

1 Like
13

That’s not “nonsense” at all.

Asking for some clarification might have been helpful, and clearly, you were not aware of how to manage those dependency warnings.

My point was, and remains, when in doubt – ask.

Very true. In such a scenario one must usually;

a) Reboot and login with another kernel before removing the kernel in question.
b) Boot with a Manjaro installer and enter a chroot environment (some caveats apply) and perform the necessary operations from there.

In each case, the kernel in question is no longer current, in the sense that it is not actively used.

Regards.

14

A meta package is a package that doesn’t contain any software, it’s designed to pull in other packages, or to conflict with them. It’s usually used to pull in lots of packages, but not always.

In this case it pulls in the next oldest kernel and conflicts with all EOL kernels, to prevent people getting stuck on outdated kernels.

The other related linux meta packages are there to ensure that software which needs a particular kernel is kept in line with the kernel.

3 Likes
15

I mentioned this earlier in my previous thread:

I tried on a pure default system to switch the NV-driver as part of a trouble-shooting process.

The tool “mhwd” failed to perform it’s job, caused by and issues, which has been solved now.

The main-problem here is, that such an important indeep tool, which also acts as a selling-point for Manjaro, has zero decent documenation.

So, to try to understand what’s going on with this so called meta-packages-depency-breaker, is to reverse-engineer and asking questions within the forum.

My system runs per default since about 2.5 years. I have had never changed the default driver(s) or forced a special kernel.

Just to troubleshoot an issue, I went to 6.12(and will stay on it for a while).

And here…all the problems started. I have had no chance to “learn” something about mhwd’s miss-behaviour, caused by non-existent docs.

And about the acronym of ”meta-package”, I know, that this kind of packages are just pointers to real packages. BUT, I didn’t know(until dmt’s clarification), that they are not affecting the real-packages.

I worked a lot with Sun Solaris in the past, and I know for sure, what could happen if “just” removing one of this meta-packages….(i.e KUP-related packages…)

So…let’s close this thread……

16

As you have marked a solution post for this thread, and as the prominent notice (below) suggests, the topic will close automatically three days after the last reply.

Regards.

1 Like
17

I marked the solution, sorry probably should’ve mentioned it.

To be fair there’s nothing in those links about linux-meta and pals, and it’s specific to Manjaro, perhaps the wiki should be updated.

1 Like
18

Touting “non-existent documentation” as a cause for having no chance to “learn” anything, is hardly justified.

I agree, however, there seems to be no reference to meta-packages in the referenced links; hardly surprising considering one in particular dates to 2021.

However, a simple search of the forum should have revealed enough information to at least prompt some further enquiry.

The linked Wiki pages should nonetheless be useful;
assuming the OP has a chance.

19

Try something simple like “man mhwd” or “info mhwd”..or check “/usr/share/doc”…

I know the online-only documentation. But it just explains basic stuff which might work in a perfect world.

But there is no way to find anything, how it works technically…and how to trouble-shoot this tool in general..esp. if something which is mentioned within the online-only-”doc” does not work as intended.

And…exactly this was the case within thread, which I pointed to.(…which was very quickly solved btw).

cheers…