Does anybody actually look into them?
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?
Yes, you should report them, and if other people have the same problem, they can upvote the bug reports.
Unfortunately, due to limited resources, they are triaged and tend to be fixed only if they are urgent or really bad.
If you are able to program, you can submit a patch yourself. If you can’t program, unfortunately, you just have to hope.
1 Like
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.
1 Like
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?
1 Like
The patch is in the bug description. It’s basically a one liner. I have no idea how else to submit it
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
Yes, I did read the bug description, and nowhere did I see any indication that this was an Ubuntu packaging bug.
Just say that this is an Ubuntu packaging bug. 
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).
1 Like
Also checked salsa.debian.org, but it doesn’t seem to have this package.
Whats PR? Is it a patch? Is there a wiki to read about how to patch stuff meself?
I guess. Since for 24.10 you don’t need fbdev=1 anymore
Ahh ok i’ve got it. Basically the sources for the packages are at the code.launchpad.net?
Btw the same is with 570 driver package too 
And i tend to beleive with all of the further ones to come
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 
1 Like
“Sounds good, doesn’t work”
git push:
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.
ogra
15
PR actually means pull request AFAIK…
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)
But did you use the long line specified below, in the CODE tab? Because it’s not just a simple “push”…
yeah i did. i just didn’t quote it here for simplicity.
P.S. nvm i found the problem. Had to upload public key to launchpad
@ogra
@SergioCostas
Did anyone from ubuntu ever bothered to describe the PR process anywhere? What are the branches for? Or the process of PPA creation?
ogra
19
There used to be:
https://help.launchpad.net/Code/Review
But I’m not sure there is an equivalent to that since nLaunchpad switched to git trees by default …
EDI’T: there is Code/Git - Launchpad Help though …
Just bikeshedding on that myself.
I believe from bzr we used the term “MP” for Merge Proposal.
1 Like
