| 2014-02-06 12:27:55 |
Alberto Milone |
bug |
|
|
added bug |
| 2014-02-06 12:28:14 |
Alberto Milone |
nominated for series |
|
Ubuntu Precise |
|
| 2014-02-06 12:28:14 |
Alberto Milone |
bug task added |
|
fglrx-pxpress (Ubuntu Precise) |
|
| 2014-02-06 12:28:29 |
Alberto Milone |
fglrx-pxpress (Ubuntu): status |
New |
Invalid |
|
| 2014-02-06 12:28:32 |
Alberto Milone |
fglrx-pxpress (Ubuntu Precise): status |
New |
Triaged |
|
| 2014-02-06 12:28:35 |
Alberto Milone |
fglrx-pxpress (Ubuntu Precise): importance |
Undecided |
Critical |
|
| 2014-02-06 12:28:38 |
Alberto Milone |
fglrx-pxpress (Ubuntu Precise): assignee |
|
Alberto Milone (albertomilone) |
|
| 2014-02-06 13:13:46 |
Alberto Milone |
description |
the amd-xconfig script gets stuck and keeps writing to the log in /var/log/upstart/amd-config.log |
SRU request:
Please accept fglrx-pxpress 0.6~hybrid0.0.2 in precise-proposed.
[Rationale]
Because of a regression in 0.6~hybrid0.0.1, the amd-config upstart job gets stuck, and, as a result, /var/log/upstart/amd-config.log keeps growing indefinitely
[Impact]
fglrx-pxpress is installed by jockey only on systems with hybrid graphics. This issue can make a system very slow and can also cause it to run out of space.
[Test case]
1) Remove the old log:
sudo rm /var/log/upstart/amd-config.log
2) Install fglrx-pxpress 0.6~hybrid0.0.2 on a hybrid system
3) Boot the system
4) see if /var/log/upstart/amd-config.log is created (it shouldn't be)
5) check that /var/log/amd-config.log exists
6) make sure that the upstart is not running any more by typing:
sudo initctl status amd-config
The correct output is "amd-config stop/waiting". |
|
| 2014-02-06 13:14:15 |
Alberto Milone |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2014-02-06 13:14:17 |
Alberto Milone |
fglrx-pxpress (Ubuntu Precise): status |
Triaged |
In Progress |
|
| 2014-02-06 13:48:03 |
Colin Watson |
fglrx-pxpress (Ubuntu Precise): status |
In Progress |
Fix Committed |
|
| 2014-02-06 13:48:06 |
Colin Watson |
bug |
|
|
added subscriber SRU Verification |
| 2014-02-06 13:48:18 |
Colin Watson |
tags |
|
verification-needed |
|
| 2014-02-06 13:57:37 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/precise-proposed/fglrx-pxpress |
|
| 2014-02-06 14:19:42 |
Alberto Milone |
description |
SRU request:
Please accept fglrx-pxpress 0.6~hybrid0.0.2 in precise-proposed.
[Rationale]
Because of a regression in 0.6~hybrid0.0.1, the amd-config upstart job gets stuck, and, as a result, /var/log/upstart/amd-config.log keeps growing indefinitely
[Impact]
fglrx-pxpress is installed by jockey only on systems with hybrid graphics. This issue can make a system very slow and can also cause it to run out of space.
[Test case]
1) Remove the old log:
sudo rm /var/log/upstart/amd-config.log
2) Install fglrx-pxpress 0.6~hybrid0.0.2 on a hybrid system
3) Boot the system
4) see if /var/log/upstart/amd-config.log is created (it shouldn't be)
5) check that /var/log/amd-config.log exists
6) make sure that the upstart is not running any more by typing:
sudo initctl status amd-config
The correct output is "amd-config stop/waiting". |
SRU request:
Please accept fglrx-pxpress 0.6~hybrid0.0.2 in precise-proposed.
[Rationale]
Because of a regression in 0.6~hybrid0.0.1, the amd-config upstart job gets stuck, and, as a result, /var/log/upstart/amd-config.log keeps growing indefinitely
[Impact]
fglrx-pxpress is installed by jockey only on systems with hybrid graphics. This issue can make a system very slow and can also cause it to run out of space.
[Test case]
1) Remove the old log:
sudo rm /var/log/upstart/amd-config.log
2) Install fglrx-pxpress 0.6~hybrid0.0.2 on a hybrid system
3) Boot the system
4) see if /var/log/upstart/amd-config.log is created (it shouldn't be)
5) check that /var/log/amd-xconfig.log exists
6) make sure that the upstart is not running any more by typing:
sudo initctl status amd-config
The correct output is "amd-config stop/waiting". |
|
| 2014-02-06 15:07:50 |
Alberto Milone |
description |
SRU request:
Please accept fglrx-pxpress 0.6~hybrid0.0.2 in precise-proposed.
[Rationale]
Because of a regression in 0.6~hybrid0.0.1, the amd-config upstart job gets stuck, and, as a result, /var/log/upstart/amd-config.log keeps growing indefinitely
[Impact]
fglrx-pxpress is installed by jockey only on systems with hybrid graphics. This issue can make a system very slow and can also cause it to run out of space.
[Test case]
1) Remove the old log:
sudo rm /var/log/upstart/amd-config.log
2) Install fglrx-pxpress 0.6~hybrid0.0.2 on a hybrid system
3) Boot the system
4) see if /var/log/upstart/amd-config.log is created (it shouldn't be)
5) check that /var/log/amd-xconfig.log exists
6) make sure that the upstart is not running any more by typing:
sudo initctl status amd-config
The correct output is "amd-config stop/waiting". |
SRU request:
Please accept fglrx-pxpress 0.6~hybrid0.0.2 in precise-proposed.
[Rationale]
Because of a regression in 0.6~hybrid0.0.1, the amd-config upstart job gets stuck, and, as a result, /var/log/upstart/amd-config.log keeps growing indefinitely
[Impact]
fglrx-pxpress is installed by jockey only on systems with hybrid graphics. This issue can make a system very slow and can also cause it to run out of space.
[Test case]
1) Remove the old log:
sudo rm /var/log/upstart/amd-config.*
2) Install fglrx-pxpress 0.6~hybrid0.0.2 on a hybrid system
3) Boot the system
4) see if /var/log/upstart/amd-config.log is created (it shouldn't be)
5) check that /var/log/amd-xconfig.log exists
6) make sure that the upstart is not running any more by typing:
sudo initctl status amd-config
The correct output is "amd-config stop/waiting". |
|
| 2014-02-06 15:10:36 |
Alberto Milone |
tags |
verification-needed |
verification-done |
|
| 2014-02-06 17:00:25 |
Colin Watson |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2014-02-06 17:06:11 |
Launchpad Janitor |
fglrx-pxpress (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
