Closing as invalid for QEMU because it's an Incomplete bug against an
ancient QEMU version.
** Changed in: qemu
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
(ancient distro packaging bug so never valid for QEMU upstream itself;
marking Invalid there)
** Changed in: qemu
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
The 'qemu' binary (which is for x86 and kvm) is not always the same version as
the one used for ARM user-mode emulation (and in particular it is in a
different package for newer Ubuntu releases). What is the output of:
qemu-arm-static -h | grep version
?
--
You received this bug notification
The backtrace indicates that this is a multithreaded application. These
won't work reliably under qemu-user : they tend to crash, as you have
found.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Does this patch fix this issue?
http://patchwork.ozlabs.org/patch/309529/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1256546
Title:
qemu-s390x-static: segmentation fault entering
I've analysed this segfault. The problem is that we're not correctly
taking account of the IT state on entry to a Thumb translation block if
we're retranslating it for cpu_restore_state().
The offending TB here is:
0x0003dc00: movle r2, #0
0x0003dc02: ldrr1, [pc, #644] (0x3de88)
I have a patchset which fixes this bug, which I need to do a bit more
cleanup and testing with before I post it to the list.
** Changed in: qemu
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I've now posted this patchset; it comes in 7 parts:
http://patchwork.ozlabs.org/patch/77887/
http://patchwork.ozlabs.org/patch/77882/
http://patchwork.ozlabs.org/patch/77884/
http://patchwork.ozlabs.org/patch/77885/
http://patchwork.ozlabs.org/patch/77888/
http://patchwork.ozlabs.org/patch/77881/
Suggested patch sent upstream: http://patchwork.ozlabs.org/patch/83964/
I'll put this in qemu-linaro 2011.03 one way or another.
** Changed in: qemu-linaro
Status: New = In Progress
** Changed in: qemu-linaro
Importance: Undecided = Medium
** Changed in: qemu-linaro
Milestone:
Moving back to qemu-kvm as specific to that package.
** Package changed: qemu-linaro (Ubuntu) = qemu-kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/584480
Title:
Moving back to qemu-kvm as specific to that package.
** Package changed: qemu-linaro (Ubuntu) = qemu-kvm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/579227
Title:
** Changed in: qemu-linaro
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/721801
Title:
llseek bug in amd64 host
--
Ubuntu-server-bugs
** Changed in: qemu-linaro
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/721801
Title:
llseek bug in amd64 host
--
Actually, the interesting bit of the stack trace starts just below where
you cut it off, because object_initialize_with_type() is just asserting
that it wasn't called with a NULL pointer, so what we really want to
know is what the caller was...
--
You received this bug notification because you
Doing this only for aarch64 targets seems like a bad idea to me -- this
isn't an aarch64 specific issue. QEMU needs SIGSEGV to go to its own
handler (so we can unprotect pages we've marked as read-only in order to
catch guest writes to them so we can throw away invalidated translated
code), and
On 7 May 2014 15:34, Paul Jimenez 1317...@bugs.launchpad.net wrote:
Bug description:
Using the latest version of qemu-user-static from trusty, 2.0.0+dfsg-
2ubuntu1.
Reported to qemu and patch submitted long ago by the guy who wrote
http://www.devttys0.com/2011/12/qemu-vs-sstrip/
On 7 May 2014 15:48, Peter Maydell peter.mayd...@linaro.org wrote:
On 7 May 2014 15:34, Paul Jimenez 1317...@bugs.launchpad.net wrote:
Bug description:
Using the latest version of qemu-user-static from trusty, 2.0.0+dfsg-
2ubuntu1.
Reported to qemu and patch submitted long ago
On 9 May 2014 09:14, Riku Voipio riku.voi...@iki.fi wrote:
Hi Craig,
On Wed, May 07, 2014 at 03:53:38PM +0100, Peter Maydell wrote:
Original 2011 patch:
http://lists.gnu.org/archive/html/qemu-trivial/2011-12/msg00025.html
(hitting the 'reply' button gets us back the original email
address
That patch is not in mainline because it's an appalling hack. If we care
about multi-threaded guests we need to fix them properly, not paper over
the issues by constraining multiple threads to one CPU in the hopes the
race conditions don't bite us so often.
--
You received this bug notification
I think it's likely to happen eventually; it depends rather on the
balance between this and other work priorities (at least if it's going
to be Linaro doing the work). Regardless, I'm not taking hacky
workarounds like this into mainline (hacks are hard to get out once you
let them in, and they
Well, it won't make anything any worse, so it's your call based on how
much it actually improves your failure rate I guess.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1350435
Title:
On 9 August 2014 07:15, Erik de Castro Lopo 1042...@bugs.launchpad.net wrote:
Unfortunately the test case @pittit submitted is far harder to support
than the original test case. In this case the timer_create() syscall
gets passed pointers to functions and data in the target's address space
and
Patch which seems to at least make the test case work (tested with
i386-on-i386 linux-user): http://patchwork.ozlabs.org/patch/378769/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
** Changed in: qemu
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1349277
Title:
AArch64 emulation ignores SPSel=0 when taking (or returning from)
Public bug reported:
(This is a Dapper installation.)
The X 'fixed' font is a very popular font for use in terminal windows. I
found it totally bizarre that it didn't seem to be possible to use it in
gnome-terminal.
To reproduce:
Go to Edit-Profiles... in the menu. In the resulting dialog box,
Public bug reported:
I'm in an English locale (en_GB, as it happens), but when I bring up the
SCIM help dialogue for the SKK input method by pressing the '?' button
on the SCIM toolbar the contents of the dialogue box appear in Japanese.
For other input methods (eg 'raw code') the help message is
Public bug reported:
Binary package hint: mozilla-mplayer
This is a wishlist bug for a new feature.
If a web page has embedded video content, then mozilla-mplayer starts
playing it as soon as the page is loaded. It ought to have a
configuration option to make it not do this. It's incredibly
I note that (a) /etc/default/grub isn't documented in the update-grub(8)
manpage; (b) there's no indication that this supports_quiet setting is
supposed to be a user setting rather than a random internal script
variable that might stop working or behave differently in future (c)
there's no way to
o In the printer status window set Ctrl+R accelerator for Refresh menu
entry (LP: #137984).
That doesn't sound like it's fixed this bug; it's fixed a different bug
which somebody mentioned in a comment here. Should this bug really be
marked 'fix released' ?
--
'Document print
I'm not aware of any programmatic way to find a wide font, no.
UXTerm/XTerm just lists them manually in its app-defaults.
--
pterm should default to a wide character font
https://bugs.launchpad.net/bugs/134903
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: audacious
Package: audacious
Version: 1.5.0-2
(Ubuntu 8.04)
If you start audacious from a terminal window you see:
amidi-plug(amidi-plug.c:amidiplug_init:97): init, read configuration
amidi-plug(i_backend.c:i_backend_load:107): loading backend
bitmap fonts option no, it wasn't. I've turned it on, and 'fixed' does
now appear in the list of available fonts. (So I suppose the original
problem could be considered user error. As it happens I didn't do the
original install on this machine.)
However, gnome-terminal still doesn't seem to be
In my opinion forwarding upstream problems upstream is one of the jobs
of the distribution maintainer. Also I don't think that rejected is
the right category for good idea if we had the time -- it should be
enhancement or priority dogwash or some other thing that says yes
this is a bug but not one
Yes, this is still a problem (although the dialog is now under
menu-Settings-Settings Manager-Display). I'm using Hardy.
Were you unable to reproduce this, then?
--
xubuntu display preferences: gamma sliders don't stay in sync properly
https://bugs.launchpad.net/bugs/152213
You received this
OK, I'll have a look at that, but I'm afraid it won't be until the end
of November (which is when I'll be reunited with the external monitor).
--
in dual head config a row of pixels is drawn on the wrong monitor
https://bugs.launchpad.net/bugs/134464
You received this bug notification because
I'm seeing this in gutsy -- totem is overriding XV_SATURATION to 511
(should be 128) and XV_BRIGHTNESS to -1 (should be 0), with predictably
awful results. This is a Lenovo 3000 C200 with what lspci says is Intel
Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics
Controller (rev
Public bug reported:
Binary package hint: evince-gtk
Package: evince-gtk
Version: 2.20.0-0ubuntu2
Evince has a tickybox in the View menu which lets you disable the
toolbar (so more of your screen is available for the document and less
wasted on the UI). However, if you have the toolbar
disabling DRI makes the screen artifact go away.
I'm not so sure. I've seen this corruption on my multihead
configuration, and that never has DRI enabled, because the total width
is 2048 pixels so the Intel driver is forced to disable DRI on the 945
chipset...
--
screen artifacts after resume,
32 bit here.
--
screen artifacts after resume, part row of pixels in error (945GM)
https://bugs.launchpad.net/bugs/91966
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
How do you get it 2048 pixels width?
Your xorg.conf has to be set up with a Virtual screen size at least as
big as the largest you want to resize it to. See my xorg.conf over on
bug 134464. (PS: careful with running OpenGL programs in that
configuration, last time I tried it it made the X server
It's been suggested that my Xorg.0.log might be useful too.
** Attachment added: my Xorg.0.log
http://launchpadlibrarian.net/9804947/Xorg.0.log
--
in dual head config a row of pixels is drawn on the wrong monitor
https://bugs.launchpad.net/bugs/134464
You received this bug notification
Yes, with the caveat that unfortunately I'm going away on Monday (and
not taking my external monitor with me!) so I'm only going to be in a
position to test this weekend.
--
in dual head config a row of pixels is drawn on the wrong monitor
https://bugs.launchpad.net/bugs/134464
You received this
Interestingly, I can't currently reproduce this. (At the moment I have
xserver-xorg-video-intel 2:2.1.1-0ubuntu5 installed.) Dunno whether that
means it's been fixed by some change in the driver or if the bug has
just gone into hiding (it was always intermittent)...
--
in dual head config a row
Oh, here's a related issue. If you move the sliders to something far
from 1.00 (say 2.00) and then press the 'Revert' button then the sliders
are correctly moved back to 1.00 and the values displayed are updated.
However, if you move the sliders as close to 1.00 as you can manage (say
1.06) and
Public bug reported:
Bring up the Xubuntu display preferences dialog (menu-Settings-Display
settings). Confirm that the 'Sync sliders' checkbox is ticked and that the
initial values for red/green/blue are all equal (probably 1.00). Now grab the
red slider and move it up slowly, watching the
Public bug reported:
Binary package hint: system-config-printer
This is system-config-printer version 0.7.73+svn1429-0ubuntu1.
In the 'document print status' window, if you take a print job which is
in the 'Stopped' state, and right-click and select 'Cancel', the job
seems to be cancelled but
Public bug reported:
Binary package hint: gnome-mount
Package: gnome-mount
Version: 0.6-1ubuntu2
When gnome-mount needs root access to mount a disk it asks for a
password. The text for this dialog reads:
Access to this internal disk it is restricted to system
administrators for security
Public bug reported:
Package: xfce4-session
Version: 4.4.1-1ubuntu3
If you select 'Japanese' as your language in the initial login dialog on
xubuntu, then (obviously) xfce appears in Japanese. If you then select
the 'exit door' icon to bring up the dialog offering you the choice of
switch
Public bug reported:
Binary package hint: system-config-printer
Package: system-config-printer
Version: 0.7.73+svn1429-0ubuntu1
On xubuntu, if you select 'Settings-Printing' from the xfce menu, it brings up
the system-config-printer dialog.
If you then hit 'New printer' a dialog is popped up
Public bug reported:
Binary package hint: gdm
In Xubuntu 7.04 (gdm 2.18.1-0ubuntu1), select Settings-Login window
from the applications menu. (I believe this is gdmsetup.) In the General
tab, the 'Disable multiple logins for a single user' option has the
tooltip help text:
When the user logs in
Public bug reported:
Binary package hint: linux-image-2.6.22-9-generic
This is a Lenovo 3000 C200 laptop which has an Intel T2020 dual core
CPU. I'm running Xubuntu, and upgraded to gutsy this weekend.
If I select 'hibernate' from the exit menu, the system appears to
hibernate correctly, but on
Here's the full kern.log in case it's useful.
** Attachment added: kern.log of startup, suspend and resume
http://launchpadlibrarian.net/8696262/kern.log
--
Oops on resume from hibernate trying to restart second CPU
https://bugs.launchpad.net/bugs/130416
You received this bug notification
Sorry, somehow only cut and pasted the second half of the interesting
bit of the kern.log. Here's the first part:
Aug 4 20:27:28 canth kernel: [ 929.188000] Enabling non-boot CPUs ...
Aug 4 20:27:28 canth kernel: [ 929.20] SMP alternatives: switching to SMP
code
Aug 4 20:27:28 canth
Public bug reported:
Binary package hint: grub
This is grub version 0.97-29ubuntu3.
There doesn't seem to be any way to configure update-grub not to put the
'quiet' keyword into the menu.lst stanzas for any non-recovery kernel.
There's no menu.lst manpage, so the only documentation seems to be
No, that just removes 'quiet' from the kernel command line (which I've
already done). The grub 'quiet' keyword controls messages from grub
itself, and is something different.
--
no way to configure update-grub not to set 'quiet' option in menu.lst
non-recovery stanzas
Public bug reported:
Binary package hint: linux-image-2.6.22-10-generic
My Lenovo 3000 C200 laptop runs gutsy, primarily because feisty doesn't
support the sound hardware in it. Tribes 3 worked fine for sound.
However, I did a dist-upgrade last night to get the most recent gutsy
packages, and
*** This bug is a duplicate of bug 134146 ***
https://bugs.launchpad.net/bugs/134146
** This bug has been marked a duplicate of bug 134146
Realtek 861 sound broken on kernel 2.6.22-10.30
--
kernel 2.6.22-10 breaks sound on lenovo c200 (regression from 2.6.22-9)
** Attachment added: My xorg.conf
http://launchpadlibrarian.net/8968750/xorg.conf
--
in dual head config a row of pixels is drawn on the wrong monitor
https://bugs.launchpad.net/bugs/134464
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Public bug reported:
Binary package hint: xserver-xorg-video-intel
I have a gutsy system using the xserver-xorg-video-intel driver and
xrandr1.2 to do a dual-head configuration with a single desktop spanning
both monitors. Sometimes when I start up the system a single partial
line of pixels is
Public bug reported:
Binary package hint: pterm
If in a running pterm I use ctrl-right arrow to bring up a menu, select
'change settings', 'Fonts', 'Font used for ordinary text' and select
'mincho (kochi)' from the list, then press 'Apply', pterm crashes with a
SIGFPE.
You can also get it to
Public bug reported:
Binary package hint: putty
By default, pterm doesn't seem to pick a font which supports wide
characters (eg Japanese). As a test, start pterm,and type this:
zcat /usr/share/doc/groff-base/README.jp.gz | tcs -f jis | less
(assumes you have 'tcs' installed, also
I see this bug is still present in Gutsy.
I'm going to attach a dpatch patchfile which fixes this. (ie a file you
can dump in debian/patches and add to the debian/patches/00list). This
patch is against scim-skk 0.5.2-5.
This patch essentially just gettext-izes the help text. The existing
Oh yeah, and the version number quoted in the help is way out of date; I
didn't change that either.
--
SCIM help dialogue for scim-skk is in Japanese
https://bugs.launchpad.net/bugs/53407
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Public bug reported:
The instructions on http://www.xubuntu.org/get on how to upgrade Xubuntu
from 6.10 to 7.04 say:
Xubuntu users will need to execute the command gksudo update-manager
-c in a Terminal in order to launch the update manager
This is incorrect:
[EMAIL PROTECTED]:~$ gksudo
Ah, just realised that I'm currently on 6.06 not 6.10, so if gksudo
changed to not require the '--' between the two releases then this bug
report is mistaken. If I can manage to upgrade to 6.10 I'll check
this...
--
minor error in upgrade instructions on http://www.xubuntu.org/get
I've just run into this bug trying to upgrade a pristine dapper install
of xubuntu to edgy. I think that bugs 68799, 73467 and 96094 (currently
assigned to update-manager) are also duplicates of this one.
--
xine breaks dapper - edgy dist-upgrade on xubuntu
https://bugs.launchpad.net/bugs/71483
Well, I couldn't upgrade to 6.10 (ran into bug 71483/68799/73467/96094)
so I just did a from-scratch reinstall of 7.04. But 7.04 also needs the
'--' so chances are the website is incorrect.
--
minor error in upgrade instructions on http://www.xubuntu.org/get
Public bug reported:
Binary package hint: gnupod-tools
gnupod-tools doesn't seem to be able to read the playcount data from a
2nd gen ipod shuffle.
Repro instructions:
gnupod_INIT -m /media/IPOD
gnupod_addsong -m /media/IPOD *.flac --decode=aac
mktunes -m /media/IPOD
umount /media/IPOD
Is this issue still reproducible in Jaunty with Xfce 4.6?
I don't run the in-development versions of Ubuntu, so I won't be able to
check until Jaunty is actually released.
Presumably you have a Jaunty system; wouldn't it be better to take the
60 seconds to follow the instructions for
To Charlie: thanks for checking :-)
--
xubuntu display preferences: gamma sliders don't stay in sync properly
https://bugs.launchpad.net/bugs/152213
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
But thanks anyway, for trying to explain me what I should do while I'm
already doing it.
Sorry, I've obviously annoyed you (understandably, when I reread my
original comment). I was in a bit of a grumpy mood this afternoon (not
that that's a particularly good excuse.) Next time I'll try to take
Actually the line I'm using ends with
.. | sed -e '1{s/^\([[:alnum:]-]\+\).*$/\1/;q}')
(must have got truncated when I wrote that comment and I didn't notice).
I think this will ensure that you always get only one device name, which
yours doesn't.
--
vpnc: do_ifconfig() in /etc/vpnc/vpnc-script
Looks like the amidi-plug debug has gone, yes. That LASTFM: (cleanup)
Cleanup finished looks like debug output to me, though.
--
audacious seems to have debug tracing accidentally left in
https://bugs.launchpad.net/bugs/238818
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: scim-skk
If the user's SKK dictionary file ~/.skk-scim-jisyo is corrupt then the
skk-scim input method can throw an exception while trying to read it,
which results in the input method not being selectable.
To reproduce:
* copy the attached
** Attachment added: corrupt user dictionary file that provokes the problem
http://launchpadlibrarian.net/37002604/corrupt-skk-scim-jisyo
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37002605/Dependencies.txt
** Attachment added: XsessionErrors.txt
So, my original bug report included a simple single command line to
reproduce the bug. In Jaunty that exact same command still fails:
pm...@canth:~/anime$ pterm -fn '-kochi-mincho-
medium-r-normal-*-*-120-*-*-m-*-jisx0212.1990-0'
Gtk-WARNING **: Failed to load module libcanberra-gtk-module.so:
(Interesting that -fw doesn't seem to reproduce it. Of course it's
still a bug that -fn crashes ...)
font_width (which is erroneously zero) is set like this:
inst-font_width = gdk_char_width(inst-fonts[0], ' ');
so it's only -fn that affects it. (-fw sets fonts[1].)
Perhaps these fonts
Public bug reported:
Binary package hint: vpnc
This is Ubuntu 9.04, vpnc 0.5.3-1
When I connect to a VPN with vpnc I get this output:
pm...@canth:~$ sudo vpnc-connect arm
Device eth1
eth0 does not exist.
SIOCSIFMTU: Invalid argument
VPNC started in background (pid: 12716)...
(and the vpn then
If you replace the current line which sets DEV with this one:
DEV=$($IPROUTE route | sed -ne 's/^default.* dev
\([[:alnum:]-]\+\)\(.*metric \([0-9]\+\)\)\{0,1\}.*$/\1 \3/p' | sort -n -k2 |
sed -e '1{s/^\([[:alnum:]-]\+\).*$
then it works for me, at least. However, this could
This is the result of a bug in the configure script which was fixed by this
commit:
http://git.linaro.org/gitweb?p=qemu/qemu-linaro.git;a=commitdiff;h=20fa53ece42bec6ce5db801bead125277b26ab8a;hp=4429ab4419609f3a0b470e4b15c37c6cb5a6a400
That is in 2011.07 but not 2011.06.
SDL is only of any use for the system emulation targets. If you're just
building a linux-user target there is no point passing --enable-sdl to
configure. Just use ./configure --static --target-list=i386-linux-
user.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This workaround turns out to cause some regressions in other cases, for example:
http://comments.gmane.org/gmane.comp.emulators.qemu/138180
which seems to be because when we use -R (either explicitly or
implicitly because of this patch) we tend to map the guest stack
immediately above the guest
Your patch is wrong because the reason we disable use of ucontext on ARM
is because eglibc provides only stub versions which always fail...
The right fix here is to update the gthread code so it uses whatever the
non-deprecated APIs are (plus fallback to the deprecated versions so we
don't break
I'm not sure. I don't have a feel for whether it has fixed more cases
than it has broken or vice-versa, I'm afraid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/906922
Title:
qemu-arm-static
I've submitted this patch upstream:
http://patchwork.ozlabs.org/patch/144426/
(only tested compilation on a precise chroot on an i386 box with the configure
test nobbled to always fall back to gthreads, but it should fix the ARM build
problem too). The patch seems kinda ugly, although really
NB that that asflags thing is just a work around, not an actual fix.
This bug was addressed in the toolchain:
http://sourceware.org/bugzilla/show_bug.cgi?id=12698
and seems to be fixed in at least some of the linaro toolchain packages --
maybe it just failed to get into the lucid one somehow?
** Package changed: ubuntu = armel-cross-toolchain-base (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/947111
Title:
-march bug when building kernel
To manage notifications about this bug
** Changed in: qemu-linaro
Status: Confirmed = Fix Committed
** Changed in: qemu-linaro
Milestone: None = 2012.03
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928555
Title:
qemu-linaro
Oh, and also you (probably) don't want to set the environment variable
for running 64 bit guests as I suspect it will unnecessarily restrict
the total amount of RAM that they can use.
Re: doing it upstream: the current status of the discussion is here (plus
followups):
Loic: You don't want to do it on 32 bit platforms, but for 64 bit hosts
I think it should be OK.
The only thing that I can think of that is likely to break is if the
user has a ulimit -v setting which we would now be breaching.
--
You received this bug notification because you are a member of
This was fixed in device-tree-compiler 1.3.0-2, which now produces
libfdt1 and libfdt-dev packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/843013
Title:
Split device-tree-compiler and libfdt
LInaro QEMU releases are source tarball downloads, in this case at
https://launchpad.net/qemu-linaro/trunk/2012.01 . Fix released for
Linaro QEMU means in the source tarball.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Oh, boehm gc. There are several known problems with that. The OpenSuSE
folks have done some work which deals with this but it's not upstream
yet (and at least one of the fixes is a hack which won't get accepted
upstream and where the right fix is probably at least several weeks
work).
--
You
For the record, this bites QEMU compiled on Natty as well (and results
in an immediate crash on startup).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/721531
Title:
[armel] gcc computes wrong
Upstream says that apparently Spice does work on 32 bit hosts now (the
FAQ is out of date). I've put the necessary compilation warning fixes
into qemu-linaro pending them being committed upstream.
Steve: this means you'll want to unwind the 'don't build qemu-kvm-spice
on i386' change in the
Yes, I've seen the bash failures too. They should be fixed by
http://patchwork.ozlabs.org/patch/144476/ which I'm intending to put
into qemu-linaro for next week's release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've committed to qemu-linaro the default-to-R-on-64-bit-hosts patch (so
Steve, you'll want to drop it from the packaging) and also the followup
patch which fixes the bash issues Loic lists. These will both be in
qemu-linaro 2011.03 (due this Thursday!)
** Changed in: qemu-linaro
Status:
This time for sure!
** Changed in: qemu-linaro
Status: Triaged = Fix Committed
** Changed in: qemu-linaro
Milestone: None = 2012.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/928432
** Changed in: qemu-linaro
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696794
Title:
eglibc lacks getcontext() on ARM
To manage notifications about this bug go to:
I've committed the fix for missing ppoll on the basis that it is the bug
you've reported. I suspect it's not the bug you actually care about --
if the sigill still persists please file a new bug report, preferably
with a reasonably easy to reproduce test case...
** Changed in: qemu-linaro
1 - 100 of 262 matches
Mail list logo
