Public bug reported:
The BusID string created by prime-xconfig could be incorrect in any of
the following cases:
a) Any numeric component of the bus ID is greater than 9: prime-xconfig will
write a hexadecimal value, but X will parse it as decimal.
b) The system has more than one PCI domain: `lspci -n` will show the PCI
domain, which is normally hidden on systems with a single PCI domain. This
breaks the formatting assumptions made by nv_get_id() about which fields are in
which position.
Besides the potential correctness issues, the generated BusID string is
missing the following recommended (but optional) information:
a) Bus type. According to xorg.conf(5) this should be "PCI:"
b) PCI domain: omission of this field could lead to problems on systems with
multiple PCI domains
A patch against nvidia-prime 0.5.5 from Trusty is attached. The version
on github seems to be behind that version by quite a bit.
** Affects: nvidia-prime (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "prime-xconfig: format the BusID string correctly"
https://bugs.launchpad.net/bugs/1282796/+attachment/3988958/+files/0001-prime-xconfig-format-the-BusID-string-correctly.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282796
Title:
prime-xconfig can write an invalid BusID string
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1282796/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
