Activity log for bug #1282796

Date Who What changed Old value New value Message
2014-02-20 22:18:26 Daniel Dadap bug added bug
2014-02-20 22:18:26 Daniel Dadap attachment 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
2014-02-20 22:44:09 Aaron Plattner bug added subscriber Aaron Plattner
2014-02-21 00:23:29 Ubuntu Foundations Team Bug Bot tags patch
2014-02-21 00:23:34 Ubuntu Foundations Team Bug Bot bug added subscriber Ubuntu Review Team
2014-02-21 02:47:04 Tammy Yang bug added subscriber Tammy Yang
2014-02-21 03:04:36 Anthony Wong nvidia-prime (Ubuntu): assignee Alberto Milone (albertomilone)
2014-02-21 04:25:39 Tammy Yang attachment added nvidia-prime_0.5~hybrid0.0.2ubuntu1_amd64.deb https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1282796/+attachment/3989149/+files/nvidia-prime_0.5%7Ehybrid0.0.2ubuntu1_amd64.deb
2014-02-21 04:26:05 Tammy Yang bug added subscriber Pan Kuo
2014-02-21 08:41:51 Alberto Milone nvidia-prime (Ubuntu): status New Triaged
2014-02-21 08:42:02 Alberto Milone nominated for series Ubuntu Precise
2014-02-21 08:42:02 Alberto Milone bug task added nvidia-prime (Ubuntu Precise)
2014-02-21 08:42:10 Alberto Milone nvidia-prime (Ubuntu Precise): status New Triaged
2014-02-21 08:42:13 Alberto Milone nvidia-prime (Ubuntu): importance Undecided High
2014-02-21 08:42:15 Alberto Milone nvidia-prime (Ubuntu Precise): importance Undecided High
2014-02-21 08:42:17 Alberto Milone nvidia-prime (Ubuntu Precise): assignee Alberto Milone (albertomilone)
2014-02-21 08:56:18 Alberto Milone nvidia-prime (Ubuntu): status Triaged In Progress
2014-02-21 08:56:20 Alberto Milone nvidia-prime (Ubuntu Precise): status Triaged In Progress
2014-02-21 11:22:54 Alberto Milone description 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. SRU request: Please accept nvidia-prime (0.5~hybrid0.0.3) into precise-proposed. [Rationale] The fix . [Impact] Without this work, X will fail to start in some cases (see the "Full Explanation" section) on systems with hybrid graphics (Intel/NVIDIA). [Test Case] 1) Install the update on a hybrid system with Intel/NVIDIA GPUs 2) Make sure that the system can boot and that X doesn't fail. [Regression Potential] Low. Thanks to this fix, the xorg.conf, if anything, will have greater chances to work. [Full Explanation] 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.
2014-02-21 11:30:39 Launchpad Janitor nvidia-prime (Ubuntu): status In Progress Fix Released
2014-02-21 11:43:11 Alberto Milone nvidia-prime (Ubuntu Precise): milestone precise-updates
2014-02-21 11:43:24 Alberto Milone bug added subscriber Ubuntu Stable Release Updates Team
2014-02-22 15:36:10 Flames_in_Paradise tags patch patch precise
2014-02-27 00:02:29 Steve Langasek description SRU request: Please accept nvidia-prime (0.5~hybrid0.0.3) into precise-proposed. [Rationale] The fix . [Impact] Without this work, X will fail to start in some cases (see the "Full Explanation" section) on systems with hybrid graphics (Intel/NVIDIA). [Test Case] 1) Install the update on a hybrid system with Intel/NVIDIA GPUs 2) Make sure that the system can boot and that X doesn't fail. [Regression Potential] Low. Thanks to this fix, the xorg.conf, if anything, will have greater chances to work. [Full Explanation] 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. SRU request: Please accept nvidia-prime (0.5~hybrid0.0.3) into precise-proposed. [Rationale] The fix . [Impact] Without this work, X will fail to start in some cases (see the "Full Explanation" section) on systems with hybrid graphics (Intel/NVIDIA). [Test Case] 1) Install the update on a hybrid system with Intel/NVIDIA GPUs 2) Make sure that the system can boot and that X doesn't fail. [Regression Potential] Low. Thanks to this fix, the xorg.conf, if anything, will have greater chances to work. [Full Explanation] 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 -Dn` 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.
2014-02-27 00:06:02 Steve Langasek nvidia-prime (Ubuntu Precise): status In Progress Fix Committed
2014-02-27 02:59:30 Flames_in_Paradise tags patch precise patch precise verification-needed
2014-04-16 19:19:37 Flames_in_Paradise tags patch precise verification-needed hw-specific patch precise verification-needed
2014-04-22 12:19:21 Bartosz Kosiorek tags hw-specific patch precise verification-needed hw-specific patch precise verification-done
2014-04-26 05:20:45 Launchpad Janitor nvidia-prime (Ubuntu Precise): status Fix Committed Fix Released
2014-04-26 05:20:49 Adam Conrad removed subscriber Ubuntu Stable Release Updates Team
2014-10-30 08:32:16 Launchpad Janitor branch linked lp:ubuntu/nvidia-prime
2014-10-30 08:32:22 Launchpad Janitor branch linked lp:ubuntu/precise-updates/nvidia-prime