+1
sudo project-rootstock/rootstock --fqdn ubuntu -d lucid --login ubuntu
--password 123456 --notarball --imagesize 3G --seed
ubuntu-desktop,openssh-server,build-essential
Host computer is intel core i5 4GB RAM, mainboard Gigabyte. Virtual
machine is virtualbox one with 1GB RAM. Guest OS is ubun
+1
This bug appears on the Tegra 2 as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/53
Title:
mono assembly installation under qemu-arm-static hangs
--
ubuntu-bugs mailing list
ubuntu-
command run was
sudo rootstock --dist maverick --seed ubuntu-netbook -f localhost
--login ubuntu --password ubuntu --imagesize 4G --notarball --fullname
"Ubuntu for Android" --kbmodel kbd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Just thought I'd add that I'm Having this issue with rootstock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/53
Title:
mono assembly installation under qemu-arm-static hangs
--
ubuntu-bugs ma
yes, you seem to be on something here, if the snapdragon (to my
knowledge being the only real HW this issue was seen on yet) behaves the
same as qemu there might be a similarity. upstream clearly pointed to
the boehm gc issues with the x86 /proc filesystem for our bug, would be
intresting to know w
As well, just finished a successful running 'apt-get install' as '--no-
install-recommends' in order to avoid mono packaging. Will work on a
kernel before claiming success to all us unlucky ARM'ers who are not on
omap. Start with ubuntu-minimal, work your way up from there...
--
You received this
I was working with a qualcomm snapdragon when not in qemu. So what you
are saying is that this is just one of those crazy coincidences, that
this install routine breaks at the same places in the qemu vm as well as
on the actual snapdragon?
--
You received this bug notification because you are a m
this seems to be an issue with your board, on the supported ubuntu
architectures native installation of mono packages works fine (there are
surely plenty issues with applications, but the breakage you describe
above observed in VMs yet) all our images build fine and install the
mono dependencies wi
Well, I am considering working around by never using and mono packages
in any ARM build of anything. I will collect the packages at least for
the dependencies of ubuntu-netbook, and filter out anything that depends
on mono. It seems that mono breaks ubuntu on ALL ARM PLATFORMS. Also,
this issue wil
Any work arounds for this ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/53
Title:
mono assembly installation under qemu-arm-static hangs
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
running this on a real arm board, snapdragon htc phone
this is a chroot apt-get install ubuntu-netbook. here is the results of my
'kill -SIGINT' for hanging mono processess, this does not appear to be an issue
related to kvm, since this has been done outside the virtual machine:
Setting up mono-
i saw this trying to build a maverick arm image with rootstock in
maverick. my log said:
Setting up mono-gac (2.6.7-3ubuntu1) ...
* Installing 2 assemblies from libappindicator0.1-cil into Mono
qemu: Unsupported syscall: 242
qemu: Unsupported syscall: 242
qemu: Unsupported syscall: 242
qemu: Unsup
This seems to be an issue that is unlikely to fixed in the distribution
development, and unsure if it's going to be fixed anytime soon upstream
as the linked mailing list threads go back to 2006. I'm going to mark
it "Won't Fix", but if someone does want to assign themselves to try and
resolve thi
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided => Medium
** Changed in: qemu-kvm (Ubuntu)
Status: New => Confirmed
--
mono assembly installation under qemu-arm-static hangs
https://bugs.launchpad.net/bugs/53
You received this bug notification because you are a member of Ubu
Riku told me it's related to the boehm gc not working properly under qemu.
This thread on the upstream boehm-gc group seems relevant:
http://thread.gmane.org/gmane.comp.programming.garbage-collection.boehmgc/1556
this was posted to qemu-devel:
http://www.mail-archive.com/qemu-de...@nongnu.org/ms
15 matches
Mail list logo