From: Thomas Huth <1868221@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1868221] Re: /usr/share/applications/qemu.desktop should have an "Exec=" key.
Date: Fri, 18 Jun 2021 15:45:25 -0000 [thread overview]
Message-ID: <162403112572.17937.4357188427592848872.launchpad@gac.canonical.com> (raw)
In-Reply-To: 158469084688.19486.16271224237247905413.malonedeb@chaenomeles.canonical.com
** Bug watch removed: KDE Bug Tracking System #430157
https://bugs.kde.org/show_bug.cgi?id=430157
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1868221
Title:
/usr/share/applications/qemu.desktop should have an "Exec=" key.
Status in QEMU:
Incomplete
Bug description:
According to the www.freedesktop.org .desktop-file specification, all
"Application" desktop files should have an "Exec=" key. The one in
qemu doesn't.
This can be easily verified by running kbuildsycoca4 if KDE4 is
present, but the issue is not DE-dependent.
Which binary exactly should be assigned as the default one, I don't
know.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1868221/+subscriptions
next prev parent reply other threads:[~2021-06-18 15:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 7:54 [Bug 1868221] [NEW] /usr/share/applications/qemu.desktop should have an "Exec=" key Lockywolf
2020-03-20 7:55 ` [Bug 1868221] " Lockywolf
2020-03-20 9:41 ` Daniel Berrange
2020-03-20 11:46 ` Daniel Berrange
2020-03-22 5:55 ` Lockywolf
2020-05-09 3:51 ` Frédéric Brière
2020-05-09 5:59 ` Lockywolf
2020-05-10 9:50 ` Michael Tokarev
2020-12-08 14:49 ` Lockywolf
2020-12-08 15:08 ` Lockywolf
2021-04-22 9:08 ` Thomas Huth
2021-06-18 15:45 ` Thomas Huth [this message]
2021-06-18 16:38 ` Lockywolf
2021-06-20 17:59 ` Thomas Huth
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=162403112572.17937.4357188427592848872.launchpad@gac.canonical.com \
--to=1868221@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.