*** This bug is a duplicate of bug 1104883 ***
https://bugs.launchpad.net/bugs/1104883
** Description changed:
Occured after the raring desktop amd64 installation on 20130125 on a VM
based on qemu-kvm usign virt-manager
+
+ 1. Boot a VM to raring desktop amd64 live session with the image
** Tags added: rls-r-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1104883
Title:
dconf-service crashed with SIGSEGV in g_variant_is_trusted()
To manage notifications about this bug go to:
The crash is occurring in a live system even where the installed version
on libglib2.0-bin is 2.35.4-0ubuntu5. This was observed on 20130128
raring desktop images.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Public bug reported:
Occured after the raring desktop amd64 installation on 20130129 on
hardware as well.
Probably a duplicate of lp:1105102 but this bug is reported for the
latest traces to be added.
1.Install raring amd64 desktop with the image of 20130129
3. Reboot after the installation
4. T
The latest traces are attached from an installation with 20130129
** Attachment added: "Stacktrace.txt"
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1105102/+attachment/3505562/+files/Stacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
** Attachment added: "ThreadStacktrace.txt"
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1105102/+attachment/3505564/+files/ThreadStacktrace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Description changed:
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 regressio
There is another way to reproduce this crash in precise and the crash
occurs even with apt-clone 0.2.2ubuntu3.
1. Install precise (select 'Erase disk and install ubuntu' on the 'Installation
type' screen)
2. Finish the installation, reboot and login
3. Do another installation on the same device w
Public bug reported:
An exception appears to have occurred during a preseeded raring desktop
amd64 installation. The following is taken from the available log,
Feb 18 09:46:09 ubuntu ubiquity: Traceback (most recent call last):
Feb 18 09:46:09 ubuntu ubiquity: File "/usr/lib/python3.3/site.py",
Public bug reported:
The raring virtual host server installations fail to complete due to
dependency problems like,
Feb 20 08:32:22 in-target: Errors were encountered while processing:
Feb 20 08:32:22 in-target: qemu-system-common
Feb 20 08:32:22 in-target: qemu-system-x86
Feb 20 08:32:22 in-ta
** Attachment added: "partman.txt"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1130591/+attachment/3537858/+files/partman.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/11305
** Attachment added: "media-info.txt"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1130591/+attachment/3537859/+files/media-info.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Platform QA Team (canonical-platform-qa) =>
Parameswaran Sivatharman (psivaa)
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => In Progress
--
You received this bug notifi
Retested with today's images 20130220 and could verify that the issue
does NOT occur with any desktop images.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1126107
Title:
Ubiquity does not start dur
No, Sorry. My wording is wrong. It only happened once so far on the
image with 20130218.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1129035
Title:
Exception during raring desktop amd64 installati
Public bug reported:
The following crash occurred during a manual crypted partitioned
installation of raring desktop,
Feb 22 14:11:33 ubiquity: Partman: auto_state = None
Exception caught in process_line:
Traceback (most recent call last):
File "/usr/lib/ubiquity/ubiquity/filteredcommand.py", l
** Tags added: rls-r-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1131761
Title:
ubi-partman fails with exit code 141 when setting up crypted
partitioned installation
To manage notifica
This occurred during a virtual-host preseeded installation of amd64
raring server image. The VM hanged when booting normally and threw a
kernel panic when booting via recovery mode.
https://jenkins.qa.ubuntu.com/view/Raring/view/Smoke%20Testing/job/raring-server-amd64-smoke-virtual-host/60/
is th
** Description changed:
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
Preseed file for automatic installation using utah
** Attachment added: "virtual-host.preseed"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3494533/+files/virtual-host.preseed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The .run file used to run the test using utah.
** Description changed:
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 usi
The preseed file
** Attachment added: "virtual-host.preseed"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3494539/+files/virtual-host.preseed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Utah runlist
** Attachment added: "virtual-host.run"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1100386/+attachment/3494544/+files/virtual-host.run
** Description changed:
Raring server installations with both amd64 and i386 fail to reboot
normally after the installations on VM
*** This bug is a duplicate of bug 1096531 ***
https://bugs.launchpad.net/bugs/1096531
So I installed an i386 server with nomodeset option selected and the
normal reboots are working fine ( although the recovery mode path I
tried out of curiosity still leads to the kernel panic) - The host is
*** This bug is a duplicate of bug 940944 ***
https://bugs.launchpad.net/bugs/940944
Public bug reported:
This crash occurred during a live session of raring-desktop-i386
20130123 on dell mini with the attached hw spec.
The steps:
1. dd raring desktop i386 image
2. Boot to a live session
P
The hang started on images with kernel version of Ubuntu
3.7.0-6-generic. This could be reproduced on the raring server i386
image of 20121213 and later
The hang can not be seen with images that contain kernel version
3.7.0-5-generic and earlier. Tested with raring server i386 images of
20121212
The profile used for the auto-upgrade
** Attachment added: "lts-universe-amd64.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1096022/+attachment/3498032/+files/lts-universe-amd64.tar.gz
** Description changed:
The following error occurred during lucid-precise upgrad
** Attachment added: "syslog_20130118.1_with"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1103982/+attachment/3498155/+files/syslog_20130118.1_with
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Public bug reported:
cpu-checker is not included in virtual host server installations from
20130120 onwards. Up until 20130118.1 this was part of virtual host
installations.
A d-i syslog from an earlier image (20130118.1) which contain cpu-
checker, a log from the new image (20130120), which does
** Attachment added: "syslog_20130120_without"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1103982/+attachment/3498156/+files/syslog_20130120_without
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
https://jenkins.qa.ubuntu.com/view/Raring/view/Smoke%20Testing/job
/raring-server-amd64-smoke-virtual-host/65/
is one of the impacted jobs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103982
Title:
Public bug reported:
The on screen keyboard does not come up on Nexus 7 afterfresh install
with 20130222 image. when clicked onthe dash search box
Steps:
1. Use ubuntu-nexus7-installer to install latest raring image
2. Click on the dash and then on the search box.
3. It could noticed that the
Another instance of this error that occurred in the run of 20130224 is
https://jenkins.qa.ubuntu.com/view/Precise/view/Upgrade%20Testing%20Dashboard/job/precise-upgrade-lucid-universe/391/ARCH=amd64,LTS=lts,PROFILE=universe,label=upgrade-test/
--
You received this bug notification because you ar
Public bug reported:
The following error occurred in 20130226 preseeded raring tomcat
installations.
Feb 26 08:19:58 in-target: The following information may help to resolve the
situation:
Feb 26 08:19:58 in-target:
Feb 26 08:19:58 in-target: The following packages have unmet dependencies:
Feb
** Description changed:
The following error occurred in 20130226 preseeded raring tomcat
- installations.
+ installations.(occurs on both amd64 and i386 images)
Feb 26 08:19:58 in-target: The following information may help to resolve the
situation:
- Feb 26 08:19:58 in-target:
+ Feb 26 08
Public bug reported:
This crash occurred during quantal to raring desktop auto-upgrades
amd64. The crash occurred only once and the consecutive run has passed.
A manual upgrade of an updated quantal desktop installation to raring
did not produce this crash either.
The testing was done in an autom
Public bug reported:
/home/oem/Desktop/oem-config-prepare-gtk.desktop is not present in the oem
installations in today's desktop images (20130227)
This occurs on both amd64 and i386 images.
Steps to reproduce:
1. Start the installation
2. At the keyboard-human screen press space bar
3. Press F4
** Description changed:
/home/oem/Desktop/oem-config-prepare-gtk.desktop is not present in the oem
installations in today's desktop images (20130227)
- This occurs on both amd64 and i386 images.
+ This occurs on both amd64 and i386 images.
Steps to reproduce:
1. Start the installation
** Changed in: kernel-sru-workflow/regression-testing
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1134424
Title:
linux: 3.2.0-39.62 -proposed tracker
To manage n
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Platform QA Team (canonical-platform-qa) =>
Parameswaran Sivatharman (psivaa)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Tags added: qa-testing-passed
** Changed in: kernel-sru-workflow/regression-testing
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1134424
Title:
linux:
** Changed in: kernel-sru-workflow/regression-testing
Status: New => In Progress
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Platform QA Team (canonical-platform-qa) =>
Parameswaran Sivatharman (psivaa)
--
You received this bug notification becau
Public bug reported:
The crash occurred when firefox was opened soon after the installation
of 20130201 precide amd64 desktop on a VM using virt-manager using KVM.
Steps:
1. Install precise desktop 20130201 amd64
2. Reboot after the installation and login
3. Double click firefox (twice): There wa
** Attachment added: "_usr_bin_debconf-communicate.0.crash"
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1112448/+attachment/3510209/+files/_usr_bin_debconf-communicate.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Tags added: qa-manual-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112448
Title:
debconf-communicate crashed with SIGSEGV in Perl_sv_upgrade() soon
after precise amd64 installation
T
** Attachment added: "history.log"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1115089/+attachment/3514216/+files/history.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115089
** Attachment added: "main.log"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1115089/+attachment/3514215/+files/main.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115089
Titl
** Attachment added: "apt-clone_system_state.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1115089/+attachment/3514220/+files/apt-clone_system_state.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
** Attachment added: "dpkg.log"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1115089/+attachment/3514217/+files/dpkg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115089
Titl
** Attachment added: "apt-term.log"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1115089/+attachment/3514219/+files/apt-term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/11150
** Attachment added: "apt.log"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1115089/+attachment/3514218/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115089
Title:
Public bug reported:
dpkg: unrecoverable fatal error, aborting:
unable to fsync updated status of `apache2.2-common': Input/output
error
Error in function:
SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2)
occurs during quantal to raring upgrade with the following server ta
The issue was not reproducible on a consecutive run and the upgrade went
fine. But we'll keep watching if this pops up again by any chance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115089
Title:
Public bug reported:
Raring virtual-host server preseeded installation failed with the
following error with 20130206 i386 image.
Feb 6 09:23:05 base-installer: apt-install or in-target is already running, so
you cannot run either of
Feb 6 09:23:05 base-installer: them again until the other ins
** Attachment added: "virtual-host.preseed"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1117292/+attachment/3517115/+files/virtual-host.preseed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Attachment added: "partman"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1117292/+attachment/3517116/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1117292
Titl
** Attachment added: "screenshot.png"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1117292/+attachment/3517117/+files/screenshot.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Description changed:
- Clicking 'New partiong table' for the second time makes the ubiquity crash.
+ Clicking 'New partiong table' for the second time makes the ubiquity crash.
This occurs with all the raring desktop images (i386 and amd64- 20130103).
Also occurrs on VMs and HWs.
The s
This crash still occurs when the (grayed out) 'New partition table'
button is clicked whilst 'Create new empty partition table on this
device?' pop up dialog is still present. This happens on both amd64 and
i386 and on live system and otherwise.
Today's crash with 20130206 is attached herewith.
Thanks for attempting. I could not reproduce this more than once. I have
tried in both amd64 and i386 images but with no further success.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112448
Title:
Public bug reported:
The attached crash occurred when the display resolution was changed soon
after the installation of 20130208 precise desktop amd64+mac image on a
Mac min 5.1
The following are the steps involved.
1. Install precise desktop amd64+mac 20130208 as given in
http://testcases.qa.ub
** Description changed:
The attached crash occurred when the display resolution was changed soon
after the installation of 20130208 precise desktop amd64+mac image on a
Mac min 5.1
The following are the steps involved.
1. Install precise desktop amd64+mac 20130208 as given in
http://
Public bug reported:
The following crash occurred during a precise desktop installation on a
system that already had precise installed. The crash occurs with VMs and
on hardwares with all three desktop images (20130208 i386,amd64 and
amd64+mac)
Feb 8 17:33:39 ubuntu ubiquity: Traceback (most rec
** Attachment added: "debug"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1119621/+attachment/3521076/+files/debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1119621
Title:
KeyErr
** Attachment added: "partman"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1119621/+attachment/3521077/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1119621
Title:
Ke
** Attachment added: "casper.log"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1119621/+attachment/3521078/+files/casper.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1119621
Title:
This bug was reported with no proposed enabled packages. The log with
0.2.2ubuntu3 was attached to bug 1066347 during its precise-proposed
verification process. Reattaching the same here for it being of
interest.
** Attachment added: "precise_fail_syslog.txt"
https://bugs.launchpad.net/ubuntu/
Confirmed with ubuntu-desktop-amd64 and ubuntu-desktop-i386 when using
VirtualBox. Did not see this issue on virt-manager using KVM and on
hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/112207
** Attachment added: "partman.txt"
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1124029/+attachment/3526360/+files/partman.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124029
Title:
Public bug reported:
The following error occurs during LTSP server installation on hardware
with Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64+mac
(20130213.1).
Feb 13 11:40:02 main-menu[409]: (process:21643): mount: mounting proc on
/target/proc failed: Device or resource busy
Feb 13 1
** Attachment added: "media-info.txt"
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1124029/+attachment/3526361/+files/media-info.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124029
Ti
** Attachment added: "hardware-summary.txt"
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1124029/+attachment/3526362/+files/hardware-summary.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Description changed:
The following error occurs during LTSP server installation on hardware
with Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64+mac
(20130213.1).
-
Feb 13 11:40:02 main-menu[409]: (process:21643): mount: mounting proc on
/target/proc failed: Device or resourc
Tried twice afterwords on amd64+mac image
First attempt: Entire disk with network connected ---> The installation
succeeded
Second attempt: Side-by-side with no network connected ---> The
installation failed. ( the installation fails even after connecting the
network afterwards)
--
You received
Public bug reported:
"Incomplete Language Support
The language support files for your selected language seem to be
incomplete."
Warning message popped up soon after the installation of i386 netboot
initiated by
http://archive.ubuntu.com/ubuntu/dists/precise-
proposed/main/installer-i386/2010102
Public bug reported:
Manual raring desktop installations do not start when using libvirt and
KVM when not going through live session. This is observed with 20130215
raring desktop both amd64 and i386 installations.
Steps:
1. Use Virtual Machine Manager for the installation
2. Boot with the iso
3.
** Description changed:
Manual raring desktop installations do not start when using libvirt and
KVM when not going through live session. This is observed with 20130215
raring desktop both amd64 and i386 installations.
Steps:
1. Use Virtual Machine Manager for the installation
2. Boo
** Tags added: qa-testing-passed
** Changed in: kernel-sru-workflow/regression-testing
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1135219
Title:
linux-
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Platform QA Team (canonical-platform-qa) =>
Parameswaran Sivatharman (psivaa)
--
You received this bug notifi
No regressions found:
http://reports.qa.ubuntu.com/sru/oneiric/
** Tags added: qa-testing-passed
** Changed in: kernel-sru-workflow/regression-testing
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
The following error occurred during raring smoke tests of lxc, with
20130304 imagages (both amd64 and i386)
dpkg-preconfigure: unable to re-open stdin:
lxc-execute: Failed to find an lxc-init
lxc-execute: invalid sequence number 1. expected 4
lxc-execute: faile
** Attachment added: "utah-5580-raring-server-amd64.syslog.log"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1144873/+attachment/3556864/+files/utah-5580-raring-server-amd64.syslog.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
One of the impacted jobs is
https://jenkins.qa.ubuntu.com/view/Raring/view/Smoke%20Testing/job/raring-server-amd64-smoke-lxc/110/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1144873
Title:
"lxc-
The tests appear to hang with the revno of 86. Unable to extract any
logs since the logs wont be written to any files until the tests finish
executing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/114
The tests have still been running for more than 3 hours with the revno of 87. I
am able to ssh to the host and I get 'test-lucid' returned when I run both
these commands,
sudo lxc-ls --active
sudo lxc-ls --running
--
You received this bug notification because you are
Yes, it never shuts down.
and /var/log/lxc/test-lucid.log in the host contains only the following,
lxc-execute 1362505584.513 ERRORlxc_conf - No such file or directory -
stat(/proc/2296/root/dev//console)
utah@utah-5629-raring-server-amd64:~$ sudo lxc-info --name test-lucid
[sudo] password f
Public bug reported:
Info will be added in a bit
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: ubiquity 2.13.12
ProcVersionSignature: Ubuntu 3.8.0-10.19-generic 3.8.2
Uname: Linux 3.8.0-10-generic i686
ApportVersion: 2.9-0ubuntu2
Architecture: i386
CasperVersion: 1.330
Date: Wed Mar 6 13
** Description changed:
- Info will be added in a bit
+ This crash occurred during the preseeded minimal config installation of
+ i386 raring desktop on a VM with 20130306 image.
+
+ This appears to be a one-time occurrence since the consecutive run has
+ not seen this crash. Also the amd64 insta
Yes at present the tests in amd64 are hanging. I ran it a couple of
times and every time the tests with amd64 installations hang
indefinitely (until I forcefully abort the tests). The test-lucid was
still running after more than 3 hours.
The tests in with i386 installations seem to pass after the
The following are the results of from a an amd64 vm from a test which was
running for more than 12 hours and still running
1) utah@utah-5695-raring-server-amd64:~$ ps -ef
(attached as a text file)
2) utah@utah-5695-raring-server-amd64:~$ sudo lxc-ls --fancy
Cannot open network namespace: No
Please see bug 1118589 for "In 13.04 the ‘Choose a picture’ step will be
removed"
** Package changed: ubuntu => ubiquity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1142751
Title:
Webcam screen b
** Changed in: kernel-sru-workflow/regression-testing
Status: New => In Progress
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Platform QA Team (canonical-platform-qa) =>
Parameswaran Sivatharman (psivaa)
--
You received this bug notification becau
** Tags removed: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1118589
Title:
Please remove WebCam step
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
No regressions observed
http://reports.qa.ubuntu.com/sru/oneiric_lts_hwe/
** Tags added: qa-testing-passed
** Changed in: kernel-sru-workflow/regression-testing
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Changed in: kernel-sru-workflow/regression-testing
Status: New => In Progress
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Platform QA Team (canonical-platform-qa) =>
Parameswaran Sivatharman (psivaa)
--
You received this bug notification becau
Public bug reported:
The 'Choose a picture' step does not capture photos during the raring
desktop installations. It could be noticed in both amd64 and i386
installations. The hardware that's used is Dell Inspiron N4010.
Steps to reproduce:
1. Start the installation on a real hardware with webca
** Attachment added: "dmidecode"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1152254/+attachment/3562345/+files/dmidecode
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1152254
Title:
** Attachment added: "lspci"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1152254/+attachment/3562344/+files/lspci
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1152254
Title:
Webcam
@hallyn,
This has happened in i386 test as well; a test is running for more than 2 hours
where 30 mins was the time it took when it passed in the previous runs. All the
outputs for the above commands are similar.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
The host is an amd64 installation of 12.04.1. Ill give the information
about accessing it separately. Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1144873
Title:
"lxc-execute: Failed to fi
501 - 600 of 1280 matches
Mail list logo
