[Bug 571432] Re: qemu-system-arm crashed with SIGSEGV in subpage_register()
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. https://bugs.launchpad.net/bugs/571432 Title: qemu-system-arm crashed with SIGSEGV in subpage_register() To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/571432/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 393430] Re: kvm: use PulseAudio instead of ALSA
(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. https://bugs.launchpad.net/bugs/393430 Title: kvm: use PulseAudio instead of ALSA To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/393430/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 694059] Re: qemu fatal cp15 message report and image creation block
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 because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/694059 Title: qemu fatal cp15 message report and image creation block To manage notifications about this bug go to: https://bugs.launchpad.net/linaro-image-tools/+bug/694059/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1246990] Re: [qemu-x86-64-linux-user 1.6.1] qemu: uncaught target signal 11 (Segmentation fault) - core dumped
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. https://bugs.launchpad.net/bugs/1246990 Title: [qemu-x86-64-linux-user 1.6.1] qemu: uncaught target signal 11 (Segmentation fault) - core dumped To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1246990/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1256546] Re: qemu-s390x-static: segmentation fault entering chroot
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 chroot To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1256546/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 604872] Re: qemu-system-arm segfaults emulating versatile machine after running debootstrap --second-stage inside vm
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) 0x0003dc04: cmpr3, #2 0x0003dc06: strr2, [r1, #0] 0x0003dc08: it eq 0x0003dc0a: ldreq r3, [r5, #8] 0x0003dc0c: beq.w 0x3ddce where the 'le' is because the TB before that ended with an 'it le'. When we execute this the str gets a data abort. qemu handles this by calling cpu_restore_state(), which reruns the translation process but this time generating a mapping between target and host addresses, so we can turn the host PC of the fault into a target PC. Unfortunately we retranslate without taking account of what the IT state at the start of the TB should have been: 0x0003dc00: movs r2, #0 0x0003dc02: ldrr1, [pc, #644] (0x3de88) 0x0003dc04: cmpr3, #2 0x0003dc06: strr2, [r1, #0] 0x0003dc08: it eq 0x0003dc0a: ldreq r3, [r5, #8] 0x0003dc0c: beq.w 0x3ddce ...note that that mov has become unconditional. (It's not just the disassembly, the generated intermediate code changes too.) Since cpu_restore_state() works by (a) actually rewriting the translated code into the buffer and (b) stopping when we get to the PC which faulted, this means we end up writing over the old generated code with half of a different version of the generated code. This is never going to go well, and we end up jumping off into the weeds the next time we execute the TB. I think this is related to but not the same as https://bugs.launchpad.net/qemu/+bug/581335. -- 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/604872 Title: qemu-system-arm segfaults emulating versatile machine after running debootstrap --second-stage inside vm -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 604872] Re: qemu-system-arm segfaults emulating versatile machine after running debootstrap --second-stage inside vm
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 qemu-kvm in ubuntu. https://bugs.launchpad.net/bugs/604872 Title: qemu-system-arm segfaults emulating versatile machine after running debootstrap --second-stage inside vm -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 604872] Re: qemu-system-arm segfaults emulating versatile machine after running debootstrap --second-stage inside vm
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/ http://patchwork.ozlabs.org/patch/77883/ An upstream qemu with those patches applied successfully runs the test case given in this bug. (it is patch 5/7 http://patchwork.ozlabs.org/patch/77888/ in particular which is dealing with the specific case you've hit here, but I haven't tested with that patch alone.) -- 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/604872 Title: qemu-system-arm segfaults emulating versatile machine after running debootstrap --second-stage inside vm -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 721801] Re: llseek bug in amd64 host
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: None = 2011.03 -- 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 mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 584480] Re: qemu-system-arm segfaults emulating versatile machine
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: qemu-system-arm segfaults emulating versatile machine -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 579227] Re: [qemu-system-arm] hardware error: pl011_read: Bad offset 16000018
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: [qemu-system-arm] hardware error: pl011_read: Bad offset 1618 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 721801] Re: llseek bug in amd64 host
** 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 mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 721801] Re: llseek bug in amd64 host
** 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1285505] Re: [ppa 2.0~git-20140225] SIGABRT with -virtfs
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 are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1285505 Title: [ppa 2.0~git-20140225] SIGABRT with -virtfs To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1285505/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1285363] Re: qemu-aarch64-static segfaults
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 that's true for all targets. It probably just happens more often on the aarch64 target than others you've tested because aarch64 has a signal-return trampoline on the stack frame, so we'll often see that page get translated and thrown away again. (Other targets with a trampoline include sparc, cris, openrisc and ppc.) PS: the comment this is not required for qemu to work just means that QEMU will work fine whether we tell the guest a lie about what's going on with SIGSEGV in one way (saying it's blocked) or the other (saying it's not blocked). -- 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/1285363 Title: qemu-aarch64-static segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1285363/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Qemu-devel] [Bug 1317090] Re: qemu fails on ELF files with no section headers
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/ but apparently dropped on the floor - at least, I can't find it in any qemu bug tracker anywhere. It's now keeping me from running openwrt binaries under qemu-arm-static (because the openwrt guys strip section headers to save space on their teeny embedded boxes). It's a one-line patch, reproduced here: --- qemu/linux-user/elfload.c 2011-12-02 15:16:07.637541215 -0500 +++ qemu-patched/linux-user/elfload.c 2011-12-02 15:27:24.061522798 -0500 @@ -1068,7 +1068,6 @@ static bool elf_check_ehdr(struct elfhdr return (elf_check_arch(ehdr-e_machine) ehdr-e_ehsize == sizeof(struct elfhdr) ehdr-e_phentsize == sizeof(struct elf_phdr) - ehdr-e_shentsize == sizeof(struct elf_shdr) (ehdr-e_type == ET_EXEC || ehdr-e_type == ET_DYN)); } Yeah; the equivalent kernel code: http://lxr.linux.no/#linux+v3.14.3/fs/binfmt_elf.c#L595 doesn't check the section header size, and nor should QEMU. thanks -- PMM -- 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/1317090 Title: qemu fails on ELF files with no section headers To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1317090/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Qemu-devel] [Bug 1317090] Re: qemu fails on ELF files with no section headers
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 by the guy who wrote http://www.devttys0.com/2011/12/qemu-vs-sstrip/ but apparently dropped on the floor - at least, I can't find it in any qemu bug tracker anywhere. It's now keeping me from running openwrt binaries under qemu-arm-static (because the openwrt guys strip section headers to save space on their teeny embedded boxes). It's a one-line patch, reproduced here: --- qemu/linux-user/elfload.c 2011-12-02 15:16:07.637541215 -0500 +++ qemu-patched/linux-user/elfload.c 2011-12-02 15:27:24.061522798 -0500 @@ -1068,7 +1068,6 @@ static bool elf_check_ehdr(struct elfhdr return (elf_check_arch(ehdr-e_machine) ehdr-e_ehsize == sizeof(struct elfhdr) ehdr-e_phentsize == sizeof(struct elf_phdr) - ehdr-e_shentsize == sizeof(struct elf_shdr) (ehdr-e_type == ET_EXEC || ehdr-e_type == ET_DYN)); } Yeah; the equivalent kernel code: http://lxr.linux.no/#linux+v3.14.3/fs/binfmt_elf.c#L595 doesn't check the section header size, and nor should QEMU. 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 to fix up the signed-off-by line with, so we can credit the fix to Craig properly.) thanks -- PMM -- 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/1317090 Title: qemu fails on ELF files with no section headers To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1317090/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Qemu-devel] [Bug 1317090] Re: qemu fails on ELF files with no section headers
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 to fix up the signed-off-by line with, so we can credit the fix to Craig properly.) Can you resend the patch with your Signed-Off-By: ? Seems a bit unnecessary to force a resend -- the original has the signoff, it's just the mailing list archive has mangled it, so we can just restore it... thanks -- PMM -- 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/1317090 Title: qemu fails on ELF files with no section headers To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1317090/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1350435] Re: tcg.c:1693: tcg fatal error
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 because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1350435 Title: tcg.c:1693: tcg fatal error To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1350435/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1350435] Re: tcg.c:1693: tcg fatal error
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 remove any motivation anybody might have had for fixing things properly). -- 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: tcg.c:1693: tcg fatal error To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1350435/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1350435] Re: tcg.c:1693: tcg fatal error
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: tcg.c:1693: tcg fatal error To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1350435/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Qemu-devel] [Bug 1042388] Re: qemu: Unsupported syscall: 257 (timer_create)
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 I have not figured out how to handle that yet.
Didn't we discuss this on the list a while back? You're confusing
the libc API with the kernel syscall API here -- the kernel definitely
does not take a pointer to a function to call here. (The timer_create
manpage explicitly says that the SIGEV_THREAD functionality
is implemented in the C library, not the kernel.) You can see
this if you strace it:
clone(child_stack=0xb76e5494,
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,
parent_tidptr=0xb76e5bd8, {entry_number:6, base_addr:0xb76e5b70,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
limit_in_pages:1, seg_not_present:0, useable:1},
child_tidptr=0xb76e5bd8) = 12666
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
futex(0xb76d324c, FUTEX_WAKE_PRIVATE, 2147483647) = 0
timer_create(CLOCK_REALTIME, {0x984b098, 32, SIGEV_THREAD_ID,
{12666}}, {0x1}) = 0
timer_settime(0x1, 0, {it_interval={0, 0}, it_value={0, 5000}}, NULL) = 0
Under the hood libc is creating a new thread with clone, and
what the timer_create() syscall gets passed is a struct including
the thread ID to be sent a signal when the timer expires (here
that's 12666).
So all you need to do is support SIGEV_THREAD_ID,
which I think doesn't require much more than copying
across the thread ID struct field.
(On the other hand that does mean that all programs which
use SIGEV_THREAD are by definition multithreaded, which
puts them into this isn't supported territory because of our
well known and longstanding threading issues.)
-- PMM
--
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/1042388
Title:
qemu: Unsupported syscall: 257 (timer_create)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1042388/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1042388] Re: qemu: Unsupported syscall: 257 (timer_create)
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. https://bugs.launchpad.net/bugs/1042388 Title: qemu: Unsupported syscall: 257 (timer_create) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1042388/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1349277] Re: AArch64 emulation ignores SPSel=0 when taking (or returning from) an exception at EL1 or greater
** 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) an exception at EL1 or greater To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1349277/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 52476] 'fixed' font doesn't seem to appear in gnome-terminal's font list
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, select 'Default', and press the Edit button. Select the 'General' tab, and untick 'Use the system terminal font' if it's ticked. Click on the font name to bring up the font selection dialog box. Expected result: fixed appears somewhere in the list of available fonts. Actual result: it isn't there. ** Affects: gnome-terminal (Ubuntu) Importance: Untriaged Status: Unconfirmed -- 'fixed' font doesn't seem to appear in gnome-terminal's font list https://launchpad.net/bugs/52476 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53407] SCIM help dialogue for scim-skk is in Japanese
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 correctly localised into English. (This is a dapper installation.) ** Affects: scim-skk (Ubuntu) Importance: Untriaged Status: Unconfirmed -- SCIM help dialogue for scim-skk is in Japanese https://launchpad.net/bugs/53407 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 181241] mozilla-mplayer: should be configurable not to automatically start playing
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 irritating when pages such as http://www.yomiuri.co.jp/dy/ start playing audio and video as soon as they're loaded even if you didn't want to watch the video, just read the text content. I'd like to be able to make the mplayer plugin default to not playing video until I press the 'play' button. ** Affects: mplayerplug-in (Ubuntu) Importance: Undecided Status: New -- mozilla-mplayer: should be configurable not to automatically start playing https://bugs.launchpad.net/bugs/181241 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137136] Re: no way to configure update-grub not to set 'quiet' option in menu.lst non-recovery stanzas
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 have some kernels have the grub 'quiet' setting but not others using this workaround. I don't think I agree with your reading of the use case either. The text of that page up to the use case bits is talking generally about all messages printed before the usplash kicks in, and to the extent that it distinguishes between grub's 'quiet' and the kernel's quiet, it's talking about the former, not the latter. So I disagree with this bug being closed as 'invalid'. -- no way to configure update-grub not to set 'quiet' option in menu.lst non-recovery stanzas https://bugs.launchpad.net/bugs/137136 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137984] Re: 'Document print status' window doesn't refresh when you cancel a print job
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 status' window doesn't refresh when you cancel a print job https://bugs.launchpad.net/bugs/137984 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134903] Re: pterm should default to a wide character font
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 238818] [NEW] audacious seems to have debug tracing accidentally left in
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 '/usr/lib/audacious/Input/amidi-plug/ap-alsa.so' amidi-plug(i_backend.c:i_backend_load:145): backend /usr/lib/audacious/Input/amidi-plug/ap-alsa.so (name 'alsa') successfully loaded This kind of debug waffle shouldn't be being printed by default. ** Affects: audacious (Ubuntu) Importance: Undecided Status: New -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 52476] Re: 'fixed' font doesn't seem to appear in gnome-terminal's font list
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 handling it correctly. This is a bitmap font, so it should only be offered at the right size (which happens to be 10 for 'fixed'), whereas gnome-terminal still allows you to set a size (and presumably scales the font) and gives no indication of what the natural size of the font is. Compare emacs, which gets this right -- the shift-right-click font menu just offers 'fixed' rather than any scaling options. I know that the fontconfig stuff is because it's really aimed at fully scalable truetype fonts for applications which want to display usually proportional text at the user's choice of font and size. But gnome- terminal isn't really that kind of application -- it's a terminal, and it needs a fixed-width font -- so using a standard font setup and font selection dialog is arguably the wrong thing. For example, the dialog lets you pick a non-fixed-width font (try 'Free Sans medium 10' and watch the display get messed up whenever there's an m) -- it should probably not display proportional fonts at all (or if it must, behind some kind of 'experts only' checkbox). So I suppose that's really what I'm complaining about -- gnome-terminal is trying to use a generic font selection system which is relatively poorly suited to a program displaying straightforward fixed-width text (so it lets you select totally unsuitable fonts and doesn't necessarily display fonts which are ideal for the terminal but which might be disabled in the system wide config because they don't make sense in the general case.) -- 'fixed' font doesn't seem to appear in gnome-terminal's font list https://launchpad.net/bugs/52476 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 52476] Re: 'fixed' font doesn't seem to appear in gnome-terminal's font list
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 we can or should fix immediately Or for that matter you could have a way to say forwarded upstream. But rejected is definitely the wrong thing because it means this is not a bug. Having said all that I don't care enough about this issue to do anything more so I guess it dies here. -- 'fixed' font doesn't seem to appear in gnome-terminal's font list https://launchpad.net/bugs/52476 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152213] Re: xubuntu display preferences: gamma sliders don't stay in sync properly
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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134464] Re: in dual head config a row of pixels is drawn on the wrong monitor
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 you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32963] Re: totem overrides XV_CONSTRAST to wrong default value (Xv movies on i810/i945 have horrible colour/gamma)
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 03). -- totem overrides XV_CONSTRAST to wrong default value (Xv movies on i810/i945 have horrible colour/gamma) https://bugs.launchpad.net/bugs/32963 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 148593] evince ignores 'no toolbar' preference in fullscreen mode
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 disabled and then select View-Full screen the toolbar reappears! Evince should honour the user's preference in both windowed and full screen mode (especially since presumably you've put it in full screen mode precisely in order to have as much document on screen as possible). (Before you ask why not just use presentation mode, presentation mode doesn't honour the 'Dual' tickybox in the View menu to show two pages at once.) ** Affects: evince-gtk (Ubuntu) Importance: Undecided Status: New -- evince ignores 'no toolbar' preference in fullscreen mode https://bugs.launchpad.net/bugs/148593 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91966] Re: screen artifacts after resume, part row of pixels in error (945GM)
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, 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91966] Re: screen artifacts after resume, part row of pixels in error (945GM)
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91966] Re: screen artifacts after resume, part row of pixels in error (945GM)
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 dump core [known bug, in launchpad somewhere]) -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134464] Re: in dual head config a row of pixels is drawn on the wrong monitor
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 because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134464] Re: in dual head config a row of pixels is drawn on the wrong monitor
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134464] Re: in dual head config a row of pixels is drawn on the wrong monitor
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 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 for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152213] Re: xubuntu display preferences: gamma sliders don't stay in sync properly
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 then press 'Revert' nothing seems to happen. It's only when you wave the mouse over the sliders that the displayed values update to read 1.00 rather than 1.06. Again, something should be causing the values to update and isn't. -- 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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152213] xubuntu display preferences: gamma sliders don't stay in sync properly
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 displayed numeric values for red, green and blue. In some positions, the red/green/blue values don't match; for example I've seen 2.21/2.12/2.12. If you move the mouse over the blue and green slider controls (you don't need to click on them) the value displayed updates to the value of the red slider. Similarly, switching virtual desktop away to another desktop and back again causes the values to be updated. So it looks like the problem is that the displayed values aren't always updated properly. ** Affects: ubuntu Importance: Undecided Status: New -- 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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137984] 'Document print status' window doesn't refresh when you cancel a print job
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 the list of jobs in the window is not updated (ie the job you've just cancelled is still listed). If you again right- click on it and 'Cancel', you get the error dialog: CUPS server error There was an error during the CUPS operation: 'client-error-not- possible'.. If you select Refresh from the document print status window's View menu, the list is updated and the cancelled job (correctly) disappears. The window should automatically refresh itself when you do some operation like cancel; the user shouldn't have to do this manually. ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New -- 'Document print status' window doesn't refresh when you cancel a print job https://bugs.launchpad.net/bugs/137984 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138477] grammar error in gnome-mount 'access to internal disk it is restricted' dialog
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 reasons. This should read Access to this internal disk is restricted [...], ie the it is spurious. The offending text is in debian/patches/03_root_mounting.patch . ** Affects: gnome-mount (Ubuntu) Importance: Undecided Status: New -- grammar error in gnome-mount 'access to internal disk it is restricted' dialog https://bugs.launchpad.net/bugs/138477 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138485] xfce4-session: Japanese translations for shutdown dialog buttons make dialog too wide for 1024x768 screen
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 user/log out/restart/shutdown/suspend/hibernate then the dialog is too wide to fit completely on a 1024x768 display. This is because the Japanese translations for these button labels are much wider than the English ones, so the dialog box gets laid out with very wide buttons (each of equal size, so the same size as the worst case length of translated text) and there isn't sufficient space on a small screen to fit them all in. It might be possible to fix this with judicious use of line breaks, assuming whatever's providing these button widgets allows line breaks in button labels. Or perhaps the translations could be trimmed. Otherwise I think you'd need to split the row of buttons into two if it wasn't going to fit all in one row. ** Affects: ubuntu Importance: Undecided Status: New -- xfce4-session: Japanese translations for shutdown dialog buttons make dialog too wide for 1024x768 screen https://bugs.launchpad.net/bugs/138485 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139335] system-config-printer: no way to cancel 'searching for printers'
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 saying 'Searching for printers' with a light bulb icon. This dialog box has no cancel button or window furniture, so there's no way to cancel the search if you hit 'new printer' by mistake. You just have to sit there and wait for it to finish. It would be nice if this dialog box had a more standard UI including a 'cancel button' to let you stop the search early. ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New -- system-config-printer: no way to cancel 'searching for printers' https://bugs.launchpad.net/bugs/139335 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128915] gdmsetup tooltip text has erroneous apostrophe
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 and already has an existing session, they are connected to that session rather than starting a new session. This only works for session's running on Virtual Terminals started with gdmflexiserver, and not with XDMCP. The apostrophe in session's is erroneous. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- gdmsetup tooltip text has erroneous apostrophe https://bugs.launchpad.net/bugs/128915 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130416] Oops on resume from hibernate trying to restart second CPU
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 restart there is a kernel Oops trying to restart the second CPU; the system then seems to resume from hibernate correctly, except that /proc/cpuinfo lists only one CPU rather than two. I'll attach the kern.log showing normal startup (timestamps 19:58 onward), suspend (20:12) and resume (20:27). Here's the bit with the Oops: Aug 4 20:27:28 canth kernel: [ 929.208000] EIP: 0060:[phys_startup_32+535810151/-1073741824]Not tainted VLI Aug 4 20:27:28 canth kernel: [ 929.208000] EFLAGS: 00010002 (2.6.22-9-generic #1) Aug 4 20:27:28 canth kernel: [ 929.208000] EIP is at 0x1fffd067 Aug 4 20:27:28 canth kernel: [ 929.208000] eax: c043c388 ebx: 0005 ecx: f000 edx: 1fffd067 Aug 4 20:27:28 canth kernel: [ 929.208000] esi: c043c388 edi: 0001 ebp: 0001 esp: df819f30 Aug 4 20:27:28 canth kernel: [ 929.208000] ds: 007b es: 007b fs: 00d8 gs: ss: 0068 Aug 4 20:27:28 canth kernel: [ 929.208000] Process swapper (pid: 0, ti=df818000 task=c18e2a40 task.ti=df818000) Aug 4 20:27:28 canth kernel: [ 929.208000] Stack: c0271fdd 0001 0100 c01018e1 0280 0320 c01180df Aug 4 20:27:28 canth kernel: [ 929.208000]0001 e0002073 c0438000 c010b60d 00050014 c0371e40 0001 Aug 4 20:27:28 canth kernel: [ 929.208000]c100897f 013ca000 0001 0100 0001 c0116e45 0001 Aug 4 20:27:28 canth kernel: [ 929.208000] Call Trace: Aug 4 20:27:28 canth kernel: [ 929.208000] [dmi_check_system+77/112] dmi_check_system+0x4d/0x70 Aug 4 20:27:28 canth kernel: [ 929.208000] [calibrate_delay+17/1840] calibrate_delay+0x11/0x730 Aug 4 20:27:28 canth kernel: [ 929.208000] [setup_local_APIC+655/672] setup_local_APIC+0x28f/0x2a0 Aug 4 20:27:28 canth kernel: [ 929.208000] [cpu_init+413/592] cpu_init+0x19d/0x250 Aug 4 20:27:28 canth kernel: [ 929.208000] [start_secondary+181/896] start_secondary+0xb5/0x380 Aug 4 20:27:28 canth kernel: [ 929.208000] [cpu_exit_clear+25/64] cpu_exit_clear+0x19/0x40 Aug 4 20:27:28 canth kernel: [ 929.208000] [f885d731] acpi_processor_idle+0x0/0x41f [processor] Aug 4 20:27:28 canth kernel: [ 929.208000] [cpu_idle+213/224] cpu_idle+0xd5/0xe0 Aug 4 20:27:28 canth kernel: [ 929.208000] === Aug 4 20:27:28 canth kernel: [ 929.208000] Code: Bad EIP value. Aug 4 20:27:28 canth kernel: [ 929.208000] EIP: [phys_startup_32+535810151/-1073741824] 0x1fffd067 SS:ESP 0068:df819f30 Aug 4 20:27:28 canth kernel: [ 929.208000] Kernel panic - not syncing: Attempted to kill the idle task! Aug 4 20:27:28 canth kernel: [ 934.196000] Stuck ?? Aug 4 20:27:28 canth kernel: [ 934.196000] Inquiring remote APIC #1... Aug 4 20:27:28 canth kernel: [ 934.196000] ... APIC #1 ID: failed Aug 4 20:27:28 canth kernel: [ 934.196000] ... APIC #1 VERSION: failed Aug 4 20:27:28 canth kernel: [ 934.196000] ... APIC #1 SPIV: failed Aug 4 20:27:28 canth kernel: [ 934.196000] skipping cpu1, didn't come online Aug 4 20:27:28 canth kernel: [ 934.196000] Error taking CPU1 up: -5 ** Affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: New -- Oops on resume from hibernate trying to restart second CPU https://bugs.launchpad.net/bugs/130416 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130416] Re: Oops on resume from hibernate trying to restart second CPU
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 because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 130416] Re: Oops on resume from hibernate trying to restart second CPU
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 kernel: [ 929.20] Booting processor 1/1 eip 3000 Aug 4 20:27:28 canth kernel: [ 929.208000] Initializing CPU#1 Aug 4 20:27:28 canth kernel: [ 929.208000] BUG: unable to handle kernel paging request at virtual address ffd5 Aug 4 20:27:28 canth kernel: [ 929.208000] printing eip: Aug 4 20:27:28 canth kernel: [ 929.208000] 1fffd067 Aug 4 20:27:28 canth kernel: [ 929.208000] *pde = 4067 Aug 4 20:27:28 canth kernel: [ 929.208000] *pte = Aug 4 20:27:28 canth kernel: [ 929.208000] Oops: 0002 [#1] Aug 4 20:27:28 canth kernel: [ 929.208000] SMP Aug 4 20:27:28 canth kernel: [ 929.208000] Modules linked in: michael_mic arc4 ecb blkcipher ieee80211_crypt_tkip ipv6 capability acpi_cpufreq cpufreq_stats cpufreq_userspace cpufreq_conservative cpufreq_ondemand freq_table cpufreq_powersave sbs video container button ac dock battery sbp2 parport_pc lp parport fuse joydev snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy pcmcia snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event iTCO_wdt iTCO_vendor_support snd_seq sdhci mmc_core yenta_socket rsrc_nonstatic pcmcia_core psmouse serio_raw snd_timer snd_seq_device ieee80211_crypt snd soundcore snd_page_alloc intel_agp agpgart af_packet shpchp pci_hotplug evdev ext3 jbd mbcache sg sd_mod sr_mod cdrom ata_piix 8139cp ohci1394 ieee1394 ata_generic libata mii scsi_mod uhci_hcd ehci_hcd usbcore thermal processor fan apparmor commoncap aamatch_pcre Aug 4 20:27:28 canth kernel: [ 929.208000] CPU:1 Aug 4 20:27:28 canth kernel: [ 929.208000] EIP: 0060:[phys_startup_32+535810151/-1073741824]Not tainted VLI Aug 4 20:27:28 canth kernel: [ 929.208000] EFLAGS: 00010002 (2.6.22-9-generic #1) Aug 4 20:27:28 canth kernel: [ 929.208000] EIP is at 0x1fffd067 -- Oops on resume from hibernate trying to restart second CPU https://bugs.launchpad.net/bugs/130416 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137136] no way to configure update-grub not to set 'quiet' option in menu.lst non-recovery stanzas
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 in the menu.lst file itself, and there's nothing about this there. Also, the update-grub script says: if [ ! -n $recovery_desc -a x$supports_quiet = xtrue ]; then echo quiet $buffer fi ie if this isn't a recovery kernel and grub supports the 'quiet' keyword then you always get it. The quieten-grub spec (https://wiki.ubuntu.com/QuietenGrub) lists user always wants to boot without 'quiet' as one of its use cases, so this ought to be possible somehow... ** Affects: grub (Ubuntu) Importance: Undecided Status: New -- no way to configure update-grub not to set 'quiet' option in menu.lst non-recovery stanzas https://bugs.launchpad.net/bugs/137136 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137136] Re: no way to configure update-grub not to set 'quiet' option in menu.lst non-recovery stanzas
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 https://bugs.launchpad.net/bugs/137136 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134236] kernel 2.6.22-10 breaks sound on lenovo c200 (regression from 2.6.22-9)
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 there is a regression: sound has stopped working. If I boot with the old kernel (2.6.22-9) then sound is fine; however with the new kernel (2.6.22-10) nothing plays. Apps like xmms don't claim to be unable to play, but there is no sound output. Also alsamixer shows a greatly reduced set of mixer controls. Alsamixer reports the sound chipset as Card: HDA Intel; Chip: Realtek ALC861-VD. ** Affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: New -- kernel 2.6.22-10 breaks sound on lenovo c200 (regression from 2.6.22-9) https://bugs.launchpad.net/bugs/134236 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134236] Re: kernel 2.6.22-10 breaks sound on lenovo c200 (regression from 2.6.22-9)
*** 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) https://bugs.launchpad.net/bugs/134236 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134464] Re: in dual head config a row of pixels is drawn on the wrong monitor
** 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 for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134464] in dual head config a row of pixels is drawn on the wrong monitor
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 drawn on the wrong monitor. That is, for about half to two-thirds of a single line of pixels starting from the right of the screen, the pixels that should be drawn on the external monitor are drawn on the internal laptop display, and vice-versa. (You can tell this because if you move windows around on one monitor the corrupted line on the other monitor changes colour to match what ought to be drawn in the corrupted line on the first monitor.) I'll attach my xorg.conf. I enable the desktop-spanning with: xrandr --output VGA --preferred xrandr --output VGA --left-of LVDS (for some bizarre reason it doesn't seem to be possible to do that in xorg.conf itself.) ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- 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 for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134902] pterm crashes with SIGFPE if 'mincho (kochi)' font selected
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 crash by asking for this font on the command line: pterm -fn '-kochi-mincho-medium-r-normal-*-*-120-*-*-m-*-jisx0212.1990-0' This is pterm 0.60-1. I built from source and ran under gdb, which shows that it's falling over here: Program received signal SIGFPE, Arithmetic exception. 0x0806cb46 in configure_area (widget=0x80d9598, event=0xbf99f8e0, data=0x80b2640) at ../unix/gtkwin.c:450 450 w = (event-width - 2*inst-cfg.window_border) / inst-font_width; because inst-font_width is zero. I believe the font comes from package ttf-kochi-mincho 1.0.20030809-4ubuntu2 . I suppose it's possible that the font is somehow broken, but in any case pterm shouldn't crash. ** Affects: putty (Ubuntu) Importance: Undecided Status: New -- pterm crashes with SIGFPE if 'mincho (kochi)' font selected https://bugs.launchpad.net/bugs/134902 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134903] pterm should default to a wide character font
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 'groff-base' and 'less', and that you have a UTF-8 locale). pterm will display dots where all the wide characters should be. For contrast, run uxterm (in the xterm package) and run the same command: all the wide characters should correctly display as Japanese characters. This is happening because pterm doesn't default to the 'wide' version of the fixed font. You can force use of the wide font like this: pterm -fn '-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1' (and if you run the test command under a pterm started like this you'll see that the characters are drawn correctly) but I think that it would be better if this was made to Just Work by having the wide versions be the default. ** Affects: putty (Ubuntu) Importance: Undecided Status: New -- 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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53407] Re: SCIM help dialogue for scim-skk is in Japanese
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 Japanese help message is moved unchanged into the ja.po. The English help message is a translation from the Japanese; I believe it to be accurate but may of course have made mistakes. It could probably be more helpful, but I chose to stick to a fairly straight translation rather than trying to improve on it as I went along. This is my first run-in with the gettext machinery, so it's possible I may have got something wrong. However I have checked that the help text displays the Japanese text in a Japanese locale (ja_JP.UTF-8) and the English text in a UK locale (en_GB.UTF-8) so it all seems to work. I have copied the URL unchanged from the Japanese help to the English; this is no loss because the URL is a 404 anyway :-) This probably ought to be fixed but that would involve finding a proper description of the input mode in both Japanese and English and referring to it instead. Or such a longer description could go in the help text instead of the current quick-reference information. Either way, I think that's out of the scope of this bug. You will note that the initial size of the help dialog box is such that bits of the text are cut off on the right hand side. This looks to me like a programming bug -- the dialog box is sized to fit the text except that no account has been taken of the need to allow space for the scrollbar. The Japanese help text has the same problem although by some fluke it only affects a single line of text and that not very badly. Anyway, I think that's a separate issue (for which I have not filed a bug report). Hope this helps! ** Attachment added: dpatch file debian/patches/20_i18n-help.dpatch which should fix this bug http://launchpadlibrarian.net/9002934/20_i18n-help.dpatch -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53407] Re: SCIM help dialogue for scim-skk is in Japanese
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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128101] minor error in upgrade instructions on http://www.xubuntu.org/get
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 update-manager -c gksudo: invalid option -- c GKsu version 1.3.7 Usage: gksudo [-u user] [-k] [-l] command [rest of usage message snipped] I think the correct command should be gksudo -- update-manager -c. ** Affects: Ubuntu Importance: Undecided Status: New -- minor error in upgrade instructions on http://www.xubuntu.org/get https://bugs.launchpad.net/bugs/128101 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128101] Re: minor error in upgrade instructions on http://www.xubuntu.org/get
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 https://bugs.launchpad.net/bugs/128101 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71483] Re: xine breaks dapper - edgy dist-upgrade on xubuntu
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128101] Re: minor error in upgrade instructions on http://www.xubuntu.org/get
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 https://bugs.launchpad.net/bugs/128101 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 311423] [NEW] gnupod: doesn't read playcount data from 2gen ipod shuffle
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 Play some of the tracks on the ipod. Then plug it back in and do: tunes2pod -m /media/IPOD --force gnupod_search -m /media/IPOD --view=ialtrc Expected results: the CNT field for the played tracks should be non-zero. Actual results: it's always zero. I think this is because gnupod doesn't support reading the iTunesStats that the shuffle stores this playcount data in. If you run gtkpod then it gets the play counts correct (because libgpod knows how to read this file). ** Affects: gnupod-tools (Ubuntu) Importance: Undecided Status: New -- gnupod: doesn't read playcount data from 2gen ipod shuffle https://bugs.launchpad.net/bugs/311423 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152213] Re: xubuntu display preferences: gamma sliders don't stay in sync properly
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 reproduction in the original bug report (as modified to allow for the fact that the specific package has been removed so presumably it's some other config utility) to find out whether this bug is still a problem? Then you could say something like The new display preferences utility in Jaunty is foobar; I checked and it doesn't have this bug. which is much more useful and informative and less likely to irritate bug submitters by sounding like a pointless health-check message; and then you would be able to actually close the bug... (You might like to read http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/ubuntu/2009-02-27 -bug-triage-rants.html) -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152213] Re: xubuntu display preferences: gamma sliders don't stay in sync properly
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 152213] Re: xubuntu display preferences: gamma sliders don't stay in sync properly
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 a bit more time to consider before bashing out a response like that. My apologies again. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 382168] Re: vpnc: do_ifconfig() in /etc/vpnc/vpnc-script misparses output of ip route
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 misparses output of ip route
https://bugs.launchpad.net/bugs/382168
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 238818] Re: audacious seems to have debug tracing accidentally left in
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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 498903] [NEW] skk input method not selectable if local dictionary file is corrupt
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 (presumably corrupt) dictionary file to ~/.skk-scim-jisyo * run scim-setup * select IMEngineGlobal Setup in the left pane * SKK should be listed in the right pane in the 'Japanese' section, but it is not I did some initial debugging on this, and what is happening is this: * the GTK panel enumerates all the IMEngine modules (including SKK) in (scim's) scim_imengine_setup.cpp get_factory_list(). * this eventually results in a call to skk_LTX_scim_imengine_module_create_factory in scim-skk * we instantiate an SKKFactory * SKKFactory's constructor calls reload_config() * part of this involves reloading the user dictionary via scim_skk::UserDict::load_dict() * some problem with the dictionary file causes it to throw an exception * this is caught by the code that was trying to instantiate the SKKFactory and treated as a failure * the scim setup code therefore doesn't put SKK in to its list of working input methods Corrupt dictionary files should be handled in some more graceful manner than skk stops working completely and with no information about what has gone wrong :-) ProblemType: Bug Architecture: i386 Date: Sun Dec 20 23:52:40 2009 DistroRelease: Ubuntu 9.10 Package: scim-skk 0.5.2-5.1 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: scim-skk Uname: Linux 2.6.31-14-generic i686 ** Affects: scim-skk (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- skk input method not selectable if local dictionary file is corrupt https://bugs.launchpad.net/bugs/498903 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 498903] Re: skk input method not selectable if local dictionary file is corrupt
** 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 http://launchpadlibrarian.net/37002606/XsessionErrors.txt ** Attachment removed: XsessionErrors.txt http://launchpadlibrarian.net/37002606/XsessionErrors.txt -- skk input method not selectable if local dictionary file is corrupt https://bugs.launchpad.net/bugs/498903 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134902] Re: pterm crashes with SIGFPE if 'mincho (kochi)' font selected
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: libcanberra-gtk-module.so: cannot open shared object file: No such file or directory Floating point exception The obvious conclusion is that you didn't even try to reproduce this bug before bouncing it back to me to say is it still there?. http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/ubuntu/2009-02-27 -bug-triage-rants.html points out that this just makes Ubuntu look kind of clueless. Please stop wasting my time. ** Changed in: putty (Ubuntu) Status: Incomplete = New -- pterm crashes with SIGFPE if 'mincho (kochi)' font selected https://bugs.launchpad.net/bugs/134902 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134902] Re: pterm crashes with SIGFPE if 'mincho (kochi)' font selected
(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 don't include the space character? -- pterm crashes with SIGFPE if 'mincho (kochi)' font selected https://bugs.launchpad.net/bugs/134902 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 382168] [NEW] vpnc: do_ifconfig() in /etc/vpnc/vpnc-script misparses output of ip route
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 seems to come up OK). This is because the /etc/vpnc/vpnc-script is not correctly parsing the output of /sbin/ip route on this machine. The function do_ifconfig() does this: DEV=$($IPROUTE route | grep ^default | sed 's/^.* dev \([[:alnum:]-]\+\).*$/\1/') MTU=$(($($IPROUTE link show $DEV | grep mtu | sed 's/^.* mtu \([[:digit:]]\+\).*$/\1/') - 88)) On this machine the output of 'ip route' is: 81.2.115.144/29 dev eth1 proto kernel scope link src 81.2.115.148 169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.4.250 default via 81.2.115.145 dev eth1 metric 100 default dev eth0 scope link metric 1000 and so: pm...@canth:~$ echo $(ip route | grep ^default | sed 's/^.* dev \([[:alnum:]-]\+\).*$/\1/') eth1 eth0 and then 'ip link show' complains when it's passed this string (with a literal \n in it) as the device name. I think that probably what the script ought to be doing is sorting all the results it gets in increasing order of metric and picking the first one. (Also the error handling here is clearly a bit ropy as the script has just ploughed on regardless.) ** Affects: vpnc (Ubuntu) Importance: Undecided Status: New -- vpnc: do_ifconfig() in /etc/vpnc/vpnc-script misparses output of ip route https://bugs.launchpad.net/bugs/382168 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 382168] Re: vpnc: do_ifconfig() in /etc/vpnc/vpnc-script misparses output of ip route
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 probably use testing to
make sure it doesn't break anything.
(Incidentally, I think the effect of this bug will be that the MTU will
be left at the default of 1500 rather than set to 1412, which will
probably break networking in some cases.)
--
vpnc: do_ifconfig() in /etc/vpnc/vpnc-script misparses output of ip route
https://bugs.launchpad.net/bugs/382168
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 832830] Re: qemu-linaro version 0.14.50-2011.06-0-0ubuntu1 failed to build in oneiric
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. qemu-linaro-0.15.50-2011.08 has been confirmed to build OK on oneiric. (Testing courtesy of David Gilbert.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/832830 Title: qemu-linaro version 0.14.50-2011.06-0-0ubuntu1 failed to build in oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-linaro/+bug/832830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 855630] Re: Qemu cant find SDL if --static build
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/855630 Title: Qemu cant find SDL if --static build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/855630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 906922] Re: qemu-arm-static chroots give copious memory errors when setting up java build dependencies
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 data/BSS segment. This means brk() will always fail, which is bad news for guest binaries that rely on it. -- 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 chroots give copious memory errors when setting up java build dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-linaro/+bug/906922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 928555] Re: qemu-linaro FTBFS on arm because of deprecated gthread calls
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 on older versions of glib). -- 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 FTBFS on arm because of deprecated gthread calls To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-linaro/+bug/928555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 906922] Re: qemu-arm-static chroots give copious memory errors when setting up java build dependencies
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 chroots give copious memory errors when setting up java build dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-linaro/+bug/906922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 928555] Re: qemu-linaro FTBFS on arm because of deprecated gthread calls
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 it's an ugliness forced on us by GLib API churn; we'll see what upstream think. -- 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 FTBFS on arm because of deprecated gthread calls To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-linaro/+bug/928555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 947111] Re: -march bug when building kernel
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? ** Bug watch added: Sourceware.org Bugzilla #12698 http://sourceware.org/bugzilla/show_bug.cgi?id=12698 -- 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 go to: https://bugs.launchpad.net/ubuntu/+bug/947111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 947111] Re: -march bug when building kernel
** 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 go to: https://bugs.launchpad.net/ubuntu/+source/armel-cross-toolchain-base/+bug/947111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 928555] Re: qemu-linaro FTBFS on arm because of deprecated gthread calls
** 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 FTBFS on arm because of deprecated gthread calls To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-linaro/+bug/928555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 906922] Re: qemu-arm-static chroots give copious memory errors when setting up java build dependencies
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): http://lists.gnu.org/archive/html/qemu-devel/2011-12/msg01697.html (that patch is the equivalent of setting the environment variable for 64 bit hosts running 32 bit guests). Basically there's general agreement that defaulting -R is probably the right thing, but it needs a little more investigation for the interactions with (a) ARM commpage and (b) user specified ulimit -v, and nobody's got round to actually investigating, writing and submitting a clean patch 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/906922 Title: qemu-arm-static chroots give copious memory errors when setting up java build dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-linaro/+bug/906922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 906922] Re: qemu-arm-static chroots give copious memory errors when setting up java build dependencies
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/906922 Title: qemu-arm-static chroots give copious memory errors when setting up java build dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-linaro/+bug/906922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 843013] Re: Split device-tree-compiler and libfdt
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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/device-tree-compiler/+bug/843013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 903239] Re: qemu-arm-static: Unsupported syscall for *xattr
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. https://bugs.launchpad.net/bugs/903239 Title: qemu-arm-static: Unsupported syscall for *xattr To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-linaro/+bug/903239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 943539] Re: cannot build pam inside a qemu-armel chroot due to segfault in w3m
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/943539 Title: cannot build pam inside a qemu-armel chroot due to segfault in w3m To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-linaro/+bug/943539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721531] Re: [armel] gcc computes wrong address for main() at build time
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 address for main() at build time To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/721531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 928432] Re: spice backend fails to build on i386 with -Werror
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 packaging. ** Changed in: qemu-linaro Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/928432 Title: spice backend fails to build on i386 with -Werror To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-linaro/+bug/928432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 906922] Re: qemu-arm-static chroots give copious memory errors when setting up java build dependencies
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. https://bugs.launchpad.net/bugs/906922 Title: qemu-arm-static chroots give copious memory errors when setting up java build dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-linaro/+bug/906922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 906922] Re: qemu-arm-static chroots give copious memory errors when setting up java build dependencies
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: New = 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/906922 Title: qemu-arm-static chroots give copious memory errors when setting up java build dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-linaro/+bug/906922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 928432] Re: spice backend fails to build on i386 with -Werror
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 Title: spice backend fails to build on i386 with -Werror To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-linaro/+bug/928432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696794] Re: eglibc lacks getcontext() on ARM
** 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: https://bugs.launchpad.net/linaro-toolchain-misc/+bug/696794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 956799] Re: qemu: Unsupported syscall: 336
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 Milestone: None = 2012.04 ** Changed in: qemu-linaro Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/956799 Title: qemu: Unsupported syscall: 336 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu-linaro/+bug/956799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
