| 2013-01-16 17:29:40 |
Para Siva |
bug |
|
|
added bug |
| 2013-01-16 17:29:40 |
Para Siva |
attachment added |
|
i386_recovery_mode.jpg https://bugs.launchpad.net/bugs/1100386/+attachment/3484858/+files/i386_recovery_mode.jpg |
|
| 2013-01-16 17:30:09 |
Brad Figg |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2013-01-16 17:30:12 |
Brad Figg |
tags |
iso-testing qa-daily-testing qa-manual-testing rls-r-incoming |
iso-testing qa-daily-testing qa-manual-testing raring rls-r-incoming |
|
| 2013-01-16 17:32:55 |
Para Siva |
attachment added |
|
amd86_reboot.mp4 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3484885/+files/amd86_reboot.mp4 |
|
| 2013-01-16 17:48:15 |
Joseph Salisbury |
linux (Ubuntu): importance |
Undecided |
High |
|
| 2013-01-16 17:48:25 |
Joseph Salisbury |
tags |
iso-testing qa-daily-testing qa-manual-testing raring rls-r-incoming |
iso-testing kernel-key qa-daily-testing qa-manual-testing raring rls-r-incoming |
|
| 2013-01-16 18:04:42 |
Para Siva |
attachment added |
|
log.tar.gz https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3484942/+files/log.tar.gz |
|
| 2013-01-16 18:05:01 |
Para Siva |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2013-01-17 11:11:44 |
Para Siva |
summary |
Raring server installations on KVM fail to reboot after the installations |
Raring server installations on VMs fail to reboot after the installations |
|
| 2013-01-17 11:23:55 |
Para Siva |
attachment added |
|
VBox_kernel_panic_i386_recovery.png https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3486079/+files/VBox_kernel_panic_i386_recovery.png |
|
| 2013-01-17 11:25:28 |
Para Siva |
attachment added |
|
i386_vbox_log.tar.gz https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3486081/+files/i386_vbox_log.tar.gz |
|
| 2013-01-17 11:32:59 |
Para Siva |
description |
Raring server installations with both amd64 and i386 fail to reboot normally after the installations on KVM. This occurs with both amd64 and i386 images when installing on KVM, (using libvirt and virt-manager).
1. Install raring server on KVM with no package selected, leaving the default answers for the questions
2. Reboot after the grub installation is complete
On i386 installations booting via the recovery mode causes "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600" as shown in the attached image.
On amd64 installations booting via the recovery mode completes the booting successfully most of the time. Standard booting causes the similar type of hang as that in i386 cases. (please see the video attached)
This issue can not be seen in hardware installations. |
Raring server installations with both amd64 and i386 fail to reboot normally after the installations on VMs. This occurs with both amd64 and i386 images when installing VMs, (using libvirt and virt-manager and also using VirtBox).
1. Install raring server on a VM with no package selected, leaving the default answers for the questions
2. Reboot after the grub installation is complete
On i386 installations booting via the recovery mode causes "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600" as shown in the attached image.
On amd64 installations booting via the recovery mode completes the booting successfully most of the time. Standard booting causes the similar type of hang as that in i386 cases. (please see the video attached)
This issue can not be seen in hardware installations. |
|
| 2013-01-21 10:30:31 |
Para Siva |
description |
Raring server installations with both amd64 and i386 fail to reboot normally after the installations on VMs. This occurs with both amd64 and i386 images when installing VMs, (using libvirt and virt-manager and also using VirtBox).
1. Install raring server on a VM with no package selected, leaving the default answers for the questions
2. Reboot after the grub installation is complete
On i386 installations booting via the recovery mode causes "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600" as shown in the attached image.
On amd64 installations booting via the recovery mode completes the booting successfully most of the time. Standard booting causes the similar type of hang as that in i386 cases. (please see the video attached)
This issue can not be seen in hardware installations. |
Raring server installations with both amd64 and i386 fail to reboot normally after the installations on VMs. This occurs with both amd64 and i386 images when installing VMs, (using libvirt and virt-manager and also using VirtBox).
1. Install raring server on a VM with no package selected, leaving the default answers for the questions
2. Reboot after the grub installation is complete
On i386 installations booting via the recovery mode causes "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600" as shown in the attached image.
Latest amd64 (20130121) installations with virtual-host package selection also reported the kernel panic when booting via recovery mode with the same message above, "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600".
Standard booting causes the similar type of hang as that in i386 cases. (please see the video attached)
This issue can not be seen in hardware installations. |
|
| 2013-01-22 09:56:47 |
Para Siva |
description |
Raring server installations with both amd64 and i386 fail to reboot normally after the installations on VMs. This occurs with both amd64 and i386 images when installing VMs, (using libvirt and virt-manager and also using VirtBox).
1. Install raring server on a VM with no package selected, leaving the default answers for the questions
2. Reboot after the grub installation is complete
On i386 installations booting via the recovery mode causes "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600" as shown in the attached image.
Latest amd64 (20130121) installations with virtual-host package selection also reported the kernel panic when booting via recovery mode with the same message above, "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600".
Standard booting causes the similar type of hang as that in i386 cases. (please see the video attached)
This issue can not be seen in hardware installations. |
Raring server installations with both amd64 and i386 fail to reboot normally after the installations on VMs. This occurs with both amd64 and i386 images when installing VMs, (using libvirt and virt-manager and also using VirtBox).
1. Install raring server on a VM with no package selected, leaving the default answers for the questions. The host of the VM is irrelevant, this has been observed on raring, quantal and precise hosts where the VM is installed.
2. Reboot after the grub installation is complete
On i386 installations booting via the recovery mode causes "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600" as shown in the attached image.
Latest amd64 (20130121) installations with virtual-host package selection also reported the kernel panic when booting via recovery mode with the same message above, "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600".
Standard booting causes the similar type of hang as that in i386 cases. (please see the video attached)
This issue can not be seen in hardware installations. |
|
| 2013-01-22 13:38:36 |
Para Siva |
attachment added |
|
virtual-host.preseed https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3494533/+files/virtual-host.preseed |
|
| 2013-01-22 13:39:11 |
Para Siva |
attachment added |
|
virtual-host.run https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3494534/+files/virtual-host.run |
|
| 2013-01-22 13:41:21 |
Para Siva |
description |
Raring server installations with both amd64 and i386 fail to reboot normally after the installations on VMs. This occurs with both amd64 and i386 images when installing VMs, (using libvirt and virt-manager and also using VirtBox).
1. Install raring server on a VM with no package selected, leaving the default answers for the questions. The host of the VM is irrelevant, this has been observed on raring, quantal and precise hosts where the VM is installed.
2. Reboot after the grub installation is complete
On i386 installations booting via the recovery mode causes "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600" as shown in the attached image.
Latest amd64 (20130121) installations with virtual-host package selection also reported the kernel panic when booting via recovery mode with the same message above, "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600".
Standard booting causes the similar type of hang as that in i386 cases. (please see the video attached)
This issue can not be seen in hardware installations. |
Raring server installations with both amd64 and i386 fail to reboot normally after the installations on VMs. This occurs with both amd64 and i386 images when installing VMs, (using libvirt and virt-manager and also using VirtBox).
On i386 installations booting via the recovery mode causes "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600" as shown in the attached image.
Latest amd64 (20130121) installations with virtual-host package selection also reported the kernel panic when booting via recovery mode with the same message above, "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600".
Standard booting causes the similar type of hang as that in i386 cases. (please see the video attached)
This issue can not be seen in hardware installations.
Steps to reproduce:
A) Manual steps:
1. Install raring server on a VM with no package selected, leaving the default answers for the questions. The host of the VM is irrelevant, this has been observed on raring, quantal and precise 64 bit hosts where the VM is installed.
2. Reboot after the grub installation is complete
B) Automated steps:
1. Do a preseed installation of raring desktop with the attached preseed file (virtual-host.preseed) and the virtual-host.run using utah. The automation instructions are below
2. Reboot the machine
(I used utah for automated installation, the how to is given in http://utah.readthedocs.org/en/latest/introduction.html#how-to-start-running-tests)
The steps are
1. use the attached .preseed file (attachment 13) and .run file (attachment 14) to execute the following command (please provide the absolute path to the files and the iso)
sudo -i -u utah run_utah_tests.py -i /path/to/iso -p /path/to/preseed /path/to/.run -n -x /etc/utah/bridged-network-vm.xml
2. Reboot the VM after the installation |
|
| 2013-01-22 13:44:12 |
Para Siva |
attachment removed |
virtual-host.preseed https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3494533/+files/virtual-host.preseed |
|
|
| 2013-01-22 13:44:27 |
Para Siva |
attachment removed |
virtual-host.run https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3494534/+files/virtual-host.run |
|
|
| 2013-01-22 13:44:54 |
Para Siva |
attachment added |
|
virtual-host.preseed https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3494539/+files/virtual-host.preseed |
|
| 2013-01-22 13:45:25 |
Para Siva |
attachment added |
|
virtual-host.run https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3494544/+files/virtual-host.run |
|
| 2013-01-22 13:45:55 |
Para Siva |
description |
Raring server installations with both amd64 and i386 fail to reboot normally after the installations on VMs. This occurs with both amd64 and i386 images when installing VMs, (using libvirt and virt-manager and also using VirtBox).
On i386 installations booting via the recovery mode causes "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600" as shown in the attached image.
Latest amd64 (20130121) installations with virtual-host package selection also reported the kernel panic when booting via recovery mode with the same message above, "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600".
Standard booting causes the similar type of hang as that in i386 cases. (please see the video attached)
This issue can not be seen in hardware installations.
Steps to reproduce:
A) Manual steps:
1. Install raring server on a VM with no package selected, leaving the default answers for the questions. The host of the VM is irrelevant, this has been observed on raring, quantal and precise 64 bit hosts where the VM is installed.
2. Reboot after the grub installation is complete
B) Automated steps:
1. Do a preseed installation of raring desktop with the attached preseed file (virtual-host.preseed) and the virtual-host.run using utah. The automation instructions are below
2. Reboot the machine
(I used utah for automated installation, the how to is given in http://utah.readthedocs.org/en/latest/introduction.html#how-to-start-running-tests)
The steps are
1. use the attached .preseed file (attachment 13) and .run file (attachment 14) to execute the following command (please provide the absolute path to the files and the iso)
sudo -i -u utah run_utah_tests.py -i /path/to/iso -p /path/to/preseed /path/to/.run -n -x /etc/utah/bridged-network-vm.xml
2. Reboot the VM after the installation |
Raring server installations with both amd64 and i386 fail to reboot normally after the installations on VMs. This occurs with both amd64 and i386 images when installing VMs, (using libvirt and virt-manager and also using VirtBox).
On i386 installations booting via the recovery mode causes "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600" as shown in the attached image.
Latest amd64 (20130121) installations with virtual-host package selection also reported the kernel panic when booting via recovery mode with the same message above, "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600".
Standard booting causes the similar type of hang as that in i386 cases. (please see the video attached)
This issue can not be seen in hardware installations.
Steps to reproduce:
A) Manual steps:
1. Install raring server on a VM with no package selected, leaving the default answers for the questions. The host of the VM is irrelevant, this has been observed on raring, quantal and precise 64 bit hosts where the VM is installed.
2. Reboot after the grub installation is complete
B) Automated steps:
1. Do a preseed installation of raring desktop with the attached preseed file (virtual-host.preseed) and the virtual-host.run using utah. The automation instructions are below
2. Reboot the machine
(I used utah for automated installation, the how to is given in http://utah.readthedocs.org/en/latest/introduction.html#how-to-start-running-tests)
The steps are
1. use the attached .preseed file (attachment 15) and .run file (attachment 16) to execute the following command (please provide the absolute path to the files and the iso)
sudo -i -u utah run_utah_tests.py -i /path/to/iso -p /path/to/preseed /path/to/.run -n -x /etc/utah/bridged-network-vm.xml
2. Reboot the VM after the installation |
|
| 2013-01-22 14:58:25 |
Joseph Salisbury |
tags |
iso-testing kernel-key qa-daily-testing qa-manual-testing raring rls-r-incoming |
iso-testing qa-daily-testing qa-manual-testing raring rls-r-incoming |
|
| 2013-01-22 14:58:49 |
Joseph Salisbury |
marked as duplicate |
|
1096531 |
|
| 2013-01-22 17:23:47 |
Stefan Bader |
bug |
|
|
added subscriber Stefan Bader |
| 2013-01-22 18:19:22 |
Stefan Bader |
removed duplicate marker |
1096531 |
|
|
| 2013-01-30 10:12:27 |
Para Siva |
description |
Raring server installations with both amd64 and i386 fail to reboot normally after the installations on VMs. This occurs with both amd64 and i386 images when installing VMs, (using libvirt and virt-manager and also using VirtBox).
On i386 installations booting via the recovery mode causes "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600" as shown in the attached image.
Latest amd64 (20130121) installations with virtual-host package selection also reported the kernel panic when booting via recovery mode with the same message above, "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600".
Standard booting causes the similar type of hang as that in i386 cases. (please see the video attached)
This issue can not be seen in hardware installations.
Steps to reproduce:
A) Manual steps:
1. Install raring server on a VM with no package selected, leaving the default answers for the questions. The host of the VM is irrelevant, this has been observed on raring, quantal and precise 64 bit hosts where the VM is installed.
2. Reboot after the grub installation is complete
B) Automated steps:
1. Do a preseed installation of raring desktop with the attached preseed file (virtual-host.preseed) and the virtual-host.run using utah. The automation instructions are below
2. Reboot the machine
(I used utah for automated installation, the how to is given in http://utah.readthedocs.org/en/latest/introduction.html#how-to-start-running-tests)
The steps are
1. use the attached .preseed file (attachment 15) and .run file (attachment 16) to execute the following command (please provide the absolute path to the files and the iso)
sudo -i -u utah run_utah_tests.py -i /path/to/iso -p /path/to/preseed /path/to/.run -n -x /etc/utah/bridged-network-vm.xml
2. Reboot the VM after the installation |
Raring server installations with both amd64 and i386 fail to reboot normally after the installations on VMs. This occurs with both amd64 and i386 images when installing VMs, (using libvirt and virt-manager and also using VirtBox).
This appears to be a regression started with Ubuntu 3.7.0-6-generic. Earlier versions do not have this issue.
On i386 installations booting via the recovery mode causes "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600" as shown in the attached image.
Latest amd64 (20130121) installations with virtual-host package selection also reported the kernel panic when booting via recovery mode with the same message above, "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600".
Standard booting causes the similar type of hang as that in i386 cases. (please see the video attached)
This issue can not be seen in hardware installations.
Steps to reproduce:
A) Manual steps:
1. Install raring server on a VM with no package selected, leaving the default answers for the questions. The host of the VM is irrelevant, this has been observed on raring, quantal and precise 64 bit hosts where the VM is installed.
2. Reboot after the grub installation is complete
B) Automated steps:
1. Do a preseed installation of raring desktop with the attached preseed file (virtual-host.preseed) and the virtual-host.run using utah. The automation instructions are below
2. Reboot the machine
(I used utah for automated installation, the how to is given in http://utah.readthedocs.org/en/latest/introduction.html#how-to-start-running-tests)
The steps are
1. use the attached .preseed file (attachment 15) and .run file (attachment 16) to execute the following command (please provide the absolute path to the files and the iso)
sudo -i -u utah run_utah_tests.py -i /path/to/iso -p /path/to/preseed /path/to/.run -n -x /etc/utah/bridged-network-vm.xml
2. Reboot the VM after the installation |
|
| 2013-01-30 10:29:01 |
Stefan Bader |
linux (Ubuntu): assignee |
|
Andy Whitcroft (apw) |
|
| 2013-02-28 16:59:15 |
Andy Doan |
bug |
|
|
added subscriber Andy Doan |
| 2013-04-16 14:04:01 |
Paul Larson |
bug |
|
|
added subscriber Paul Larson |
| 2013-05-13 21:44:46 |
Jamie Strandboge |
bug |
|
|
added subscriber Jamie Strandboge |
| 2013-05-14 20:44:59 |
Brad Figg |
tags |
iso-testing qa-daily-testing qa-manual-testing raring rls-r-incoming |
iso-testing kernel-stable-key qa-daily-testing qa-manual-testing raring rls-r-incoming |
|
| 2013-05-20 16:03:41 |
Para Siva |
summary |
Raring server installations on VMs fail to reboot after the installations |
Server installations on VMs fail to reboot after the installations |
|
| 2013-05-20 16:04:04 |
Para Siva |
description |
Raring server installations with both amd64 and i386 fail to reboot normally after the installations on VMs. This occurs with both amd64 and i386 images when installing VMs, (using libvirt and virt-manager and also using VirtBox).
This appears to be a regression started with Ubuntu 3.7.0-6-generic. Earlier versions do not have this issue.
On i386 installations booting via the recovery mode causes "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600" as shown in the attached image.
Latest amd64 (20130121) installations with virtual-host package selection also reported the kernel panic when booting via recovery mode with the same message above, "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600".
Standard booting causes the similar type of hang as that in i386 cases. (please see the video attached)
This issue can not be seen in hardware installations.
Steps to reproduce:
A) Manual steps:
1. Install raring server on a VM with no package selected, leaving the default answers for the questions. The host of the VM is irrelevant, this has been observed on raring, quantal and precise 64 bit hosts where the VM is installed.
2. Reboot after the grub installation is complete
B) Automated steps:
1. Do a preseed installation of raring desktop with the attached preseed file (virtual-host.preseed) and the virtual-host.run using utah. The automation instructions are below
2. Reboot the machine
(I used utah for automated installation, the how to is given in http://utah.readthedocs.org/en/latest/introduction.html#how-to-start-running-tests)
The steps are
1. use the attached .preseed file (attachment 15) and .run file (attachment 16) to execute the following command (please provide the absolute path to the files and the iso)
sudo -i -u utah run_utah_tests.py -i /path/to/iso -p /path/to/preseed /path/to/.run -n -x /etc/utah/bridged-network-vm.xml
2. Reboot the VM after the installation |
Raring and saucy server installations with both amd64 and i386 fail to reboot normally after the installations on VMs. This occurs with both amd64 and i386 images when installing VMs, (using libvirt and virt-manager and also using VirtBox).
This appears to be a regression started with Ubuntu 3.7.0-6-generic. Earlier versions do not have this issue.
On i386 installations booting via the recovery mode causes "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600" as shown in the attached image.
Latest amd64 (20130121) installations with virtual-host package selection also reported the kernel panic when booting via recovery mode with the same message above, "Kernel panic - not syncing: Attempted to kill init! exit code 0x00000600".
Standard booting causes the similar type of hang as that in i386 cases. (please see the video attached)
This issue can not be seen in hardware installations.
Steps to reproduce:
A) Manual steps:
1. Install raring server on a VM with no package selected, leaving the default answers for the questions. The host of the VM is irrelevant, this has been observed on raring, quantal and precise 64 bit hosts where the VM is installed.
2. Reboot after the grub installation is complete
B) Automated steps:
1. Do a preseed installation of raring desktop with the attached preseed file (virtual-host.preseed) and the virtual-host.run using utah. The automation instructions are below
2. Reboot the machine
(I used utah for automated installation, the how to is given in http://utah.readthedocs.org/en/latest/introduction.html#how-to-start-running-tests)
The steps are
1. use the attached .preseed file (attachment 15) and .run file (attachment 16) to execute the following command (please provide the absolute path to the files and the iso)
sudo -i -u utah run_utah_tests.py -i /path/to/iso -p /path/to/preseed /path/to/.run -n -x /etc/utah/bridged-network-vm.xml
2. Reboot the VM after the installation |
|
| 2013-05-21 15:51:32 |
Andy Whitcroft |
nominated for series |
|
Ubuntu Raring |
|
| 2013-05-21 15:51:32 |
Andy Whitcroft |
bug task added |
|
linux (Ubuntu Raring) |
|
| 2013-05-21 15:51:40 |
Andy Whitcroft |
linux (Ubuntu Raring): status |
New |
Confirmed |
|
| 2013-05-21 15:51:44 |
Andy Whitcroft |
linux (Ubuntu Raring): importance |
Undecided |
High |
|
| 2013-05-21 15:51:46 |
Andy Whitcroft |
linux (Ubuntu Raring): assignee |
|
Andy Whitcroft (apw) |
|
| 2013-05-21 15:51:59 |
Andy Whitcroft |
bug task added |
|
udev (Ubuntu) |
|
| 2013-05-21 15:52:08 |
Andy Whitcroft |
bug task added |
|
systemd (Ubuntu) |
|
| 2013-05-21 15:52:19 |
Andy Whitcroft |
systemd (Ubuntu Raring): status |
New |
Invalid |
|
| 2013-05-21 15:52:27 |
Andy Whitcroft |
udev (Ubuntu): status |
New |
Invalid |
|
| 2013-05-21 15:52:32 |
Andy Whitcroft |
systemd (Ubuntu): status |
New |
In Progress |
|
| 2013-05-21 15:52:36 |
Andy Whitcroft |
udev (Ubuntu Raring): status |
New |
In Progress |
|
| 2013-05-21 15:52:42 |
Andy Whitcroft |
systemd (Ubuntu): importance |
Undecided |
High |
|
| 2013-05-21 15:52:46 |
Andy Whitcroft |
udev (Ubuntu Raring): importance |
Undecided |
High |
|
| 2013-05-21 15:52:50 |
Andy Whitcroft |
udev (Ubuntu Raring): assignee |
|
Andy Whitcroft (apw) |
|
| 2013-05-21 15:52:52 |
Andy Whitcroft |
systemd (Ubuntu): assignee |
|
Andy Whitcroft (apw) |
|
| 2013-05-22 06:24:13 |
Martin Pitt |
summary |
Server installations on VMs fail to reboot after the installations |
[udev] Server installations on VMs fail to reboot after the installations |
|
| 2013-05-22 06:25:29 |
Martin Pitt |
summary |
[udev] Server installations on VMs fail to reboot after the installations |
Server installations on VMs fail to reboot after the installations |
|
| 2013-05-22 09:45:08 |
Andy Whitcroft |
attachment added |
|
lp1100386-systemd.diff https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3683733/+files/lp1100386-systemd.diff |
|
| 2013-05-22 10:12:59 |
Martin Pitt |
systemd (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2013-05-22 10:15:15 |
Andy Whitcroft |
linux (Ubuntu Raring): status |
Confirmed |
Won't Fix |
|
| 2013-05-22 10:15:19 |
Andy Whitcroft |
linux (Ubuntu): status |
Confirmed |
Won't Fix |
|
| 2013-05-22 10:37:23 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/saucy-proposed/systemd |
|
| 2013-05-22 12:04:19 |
Launchpad Janitor |
systemd (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2014-12-05 05:27:42 |
Rolf Leggewie |
udev (Ubuntu Raring): status |
In Progress |
Won't Fix |
|
