up vote 0 down vote favorite

The general question:
If faced with a Broken Package System error, can you wait for the culprit package(s) to be fixed or do you always manually have to fix this error yourself?
I am asking this because I read many posts handling this error differently (even if their underlying cause is the same), and the reported outcomes are also mixed.
If you can wait, how to keep your system up-to-date, particularly security wise, with this Broken Package System error?

My specific problem:
The Vendor-Neutral GL Dispatch Library tries to install libGLES, but this library was earlier installed by the Nvidia drivers 340.106, leading to a file conflict.
In the meantime a fixed Nvidia drivers 340.107 is in the 'proposed' repository. When this fixed Nvidia drivers 340.107 moves to the official repository, will this solve the Broken Package System error when I run the Software Updater?
The problem is also described in Broken package udpating Ubuntu 18.04 GL dispatch library There pibacco's answer suggests to let the Vendor-Neutral GL Dispatch Library forcefully overwrite Nvidia's libGLES. I think, but not being entirely sure, this is a proper solution, since the Nvidia drivers were fixed and not the Vendor-Neutral GL Dispatch Library. So I deduce that libGLES is no longer installed with the new Nvidia drivers 340.107.

share|improve this question
New contributor
Bart is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
up vote 1 down vote

In this case 'broken' simply means "The package manager knows that this package cannot be installed," which may slightly different from what you expect.

A 'broken' package could mean many things: Corrupted data, conflict with another package, incompatible version, etc. Each cause of 'broken' gets handled differently, of course.

Example: A new upstream version will fix only some causes. It usually fixes file corruption (very rare). It might --or might not-- fix a file conflict (moderately common). It won't fix most version conflicts (very common).

share|improve this answer
  • Yes, I know a Broken Package System can have various underlying causes. What bothers me is that there is little consensus how to solve this issue. Even for a single cause, e.g. file conflict, there are a plethora of posts describing how to proceed. I even don't know if I can wait for an automatic solution or not. – Bart 2 days ago
  • Since your question was general, with your case merely as an example, the answer is general. If you want a specific answer to your case, that's actually much easier: A new upstream release probably won't fix your problem, because the upstream developers probably don't have that problem (they would have fixed it). If somebody reported the bug, you can track if it's fixed or not. If nobody reported the bug, or if the upstream developers rejected the bug, then obviously no fix is forthcoming and you must do it yourself. – user535733 2 days ago
  • Well, I mentioned in my question the upcoming version is in fact a version that fixes my problem. Nevertheless, I decided to wait no longer, I found the risk of not updating my system too big. Hence I fixed the file conflict problem by following pibacco's answer in askubuntu.com/a/1077622 by forcing Vendor-Neutral GL Dispatch Library to overwrite Nvidia's libGLES. Now I hope this was the correct choice. Still, I hope these Broken Package System errors become more user-friendly to solve, instead of hoping you're following the correct procedure. – Bart 12 hours ago

Your Answer

Bart is a new contributor. Be nice, and check out our Code of Conduct.
 

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.