Coz even easy to fix ones are still there, from version to version, despite they are trivial to fix. And there is absolutely no response at the bug page itself.
Does it make sense to report them, or nobody gives a hack anymore?
It is also useful to check if the problem comes from an upstream package (from Debian, Gnome, or other projects used by Ubuntu). In that case it is useful to open a bug in the upstream project bug tracker, and link the Ubuntu bug to that upstream bug.
Which doesn’t mean someone who is able to fix the bug hasn’t looked at it and decided to move on to something more important or urgent. According to the bug report that you quoted it affects just two users?
As already mentioned, some bugs need to be reported (and fixed) upstream initially otherwise Ubuntu developers need to forever patch new releases of updated packages that are brought into each release of Ubuntu and that is something that is very labour intensive.
Many users here forget that Ubuntu developers don’t write most of the software that gets included in each Ubuntu release but they seem to be tasked with fixing every bug.
@bugsgenerator has the issue that you referred to been reported directly to Nvidia for their developers to assess whether the problem is with the Nvidia software itself or Ubuntu’s packaging?
Or people simply try wayland on nvidia, realize that it doesn’t work, and move on, without bothering to dig into it, let alone report anything.
Did you bother to read the description at all? I frankly thought its pretty clear that the problem is a typo in packaging.
And even one liner fix was provided there.
If i was not clear, could you please come up with description which is clearer? I’ll change it there
I prepared a PR and sent to launchpad. I’m not very familiar with this package, anyway. Should I send a different PR for each version? (plucky, oracular-updates specifically).
A PR is a Push Request (or a Merge Request, they are basically the same). Is a request to apply a patch.
About how to do it by yourself, you just have to follow the instructions at the top of the “CODE” tab (for example, in https://code.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-560 ). You basically clone the GIT repo, do the changes you want, do a commit, and then do a PUSH with the command specified also there (where it says: “To fork this repository and propose fixes from there, push to this repository”). Then, when you do the push, in your terminal you will see a note specifying an URL to visit, to create the Merge Request itself. You just open it in your browser, fill the fields, and click on submit. Et voila! Digital magic
bugsgenerator@git.launchpad.net: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
You clone a copy of the repo into a place where you have permissions to push to (i.e.under your personal launchpad account), then push the fix to your own cloned tree and ask at the original tree that your pushed change gets pulled into the main tree by someone who has the permissions to do so… (We used to call them MR (merge request) in the past which makes it more clear that you ask someone else to merge your changed tree, sadly GitHub made the term “pull request” more popular, which makes it more confusing)