I had a similar issue upgrading from 22.04 to 24.04 (I think I hit
ctrl-C for a similar reason, to discard a shell command I was in the
middle of typing). After hitting ctrl-C I ended up in a weird state
where roughly half of the characters I typed made it through and half
didn't (didn't even get e
Using the vgabios from Dustin's PPA, bochs from Ubuntu (I'm running a
10.4 beta, so that's 2.4.2-1ubuntu1), and the guest OS is a Debian 3.0
image from Bochs' Sourceforge page. I can run X11 at 1024x768, 24-bit
color. Can't get any higher, but that's as likely a guest-OS limitation
as anything (any
I care about this bug and I can test against bochs within 24 hours. I
should be using vgabios 0.6b and whatever bochs is current in Ubuntu,
right?
--
kvm with -vga std is broken since karmic
https://bugs.launchpad.net/bugs/513273
You received this bug notification because you are a member of Ubun
I don't know a lot about this, but everything I've read in the last 15
minutes suggests that nothing should be linked dynamically toe libbfd
(it's stated in the package info for binutils-dev, for example), but
that it's rather easy to wind up with this on accident: http://www.mail-
archive.com/debi
I'm seeing it on karmic also. As far as I can tell opreport should
definitely be linked with this library statically. This mailing list
conversation (http://www.mail-archive.com/debian-bugs-
d...@lists.debian.org/msg631508.html) makes it sound like it's very easy
to accidentally build a version t
Public bug reported:
Binary package hint: qprof
I'm using qprof-0.5.2-5ubuntu1
On line 22 of /usr/bin/qprof I had:
while getopts "rvi:b:g:a:w:c:e:o:sqh"
As the -q flag takes an parameter, there should be a colon after the q.
It looks like this script was written by someone either at Debian or
