All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jorge Manuel B. S. Vicetto" <824074@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 824074] [NEW] Provide runtime option to expose the supported	list of keymaps for vnc
Date: Wed, 10 Aug 2011 16:57:35 -0000	[thread overview]
Message-ID: <20110810165735.14802.47701.malonedeb@soybean.canonical.com> (raw)
In-Reply-To: 20110810165735.14802.47701.malonedeb@soybean.canonical.com

Public bug reported:

As discussed in the ganeti group[1], I'm opening this bug to request
that qemu provides a runtime command or switch to list the supported
keymaps for vnc.

 [1] -
http://groups.google.com/group/ganeti/browse_thread/thread/dd524f5311d8d79e

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/824074

Title:
  Provide runtime option to expose the supported list of keymaps for vnc

Status in QEMU:
  New

Bug description:
  As discussed in the ganeti group[1], I'm opening this bug to request
  that qemu provides a runtime command or switch to list the supported
  keymaps for vnc.

   [1] -
  http://groups.google.com/group/ganeti/browse_thread/thread/dd524f5311d8d79e

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/824074/+subscriptions

       reply	other threads:[~2011-08-10 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 16:57 Jorge Manuel B. S. Vicetto [this message]
2017-01-20 18:02 ` [Qemu-devel] [Bug 824074] Re: Provide runtime option to expose the supported list of keymaps for vnc Thomas Huth
2020-11-20 18:41 ` Thomas Huth
2021-01-20  4:17 ` Launchpad Bug Tracker

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=20110810165735.14802.47701.malonedeb@soybean.canonical.com \
    --to=824074@bugs.launchpad.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.