From: malc <malc@pulsesoft.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Crash on fullscreen implementation
Date: Mon, 6 Feb 2006 20:34:49 +0300 (MSK) [thread overview]
Message-ID: <Pine.LNX.4.64.0602062033020.916@home.oyster.ru> (raw)
In-Reply-To: <3461d5200602060907i3d11a9deob30c490029e90bda@mail.gmail.com>
On Mon, 6 Feb 2006, Michael Fisher wrote:
> I am using Qemu to boot various Linux distro's on Windows & Linux hosts. I
> am noticing that the last two released versions (0.7.2 & 0.8.0) crash when
> pressing Ctrl-Alt-F for fullscreen. Version 0.7.0 appears to not have this
> problem.
>
> Is anyone else seeing this? am I missing something?
In the light of 0.8.0 containing a fix for fullscreen crash on windows
this is strange. If you can please provide some more input, i.e.
reproduction scenario and gdb backtrace.
--
mailto:malc@pulsesoft.com
next prev parent reply other threads:[~2006-02-06 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 17:07 [Qemu-devel] Crash on fullscreen implementation Michael Fisher
2006-02-06 17:34 ` malc [this message]
2006-02-06 22:34 ` Michael Fisher
2006-02-07 7:55 ` wangji
2006-02-07 11:56 ` Michael Fisher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0602062033020.916@home.oyster.ru \
--to=malc@pulsesoft.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).