From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: org.gnome.DiskUtility.desktop not executing "gnome-disks" executable through an App Launcher, yet using a custom gendesk .desktop file works fine, CLI as well works
Date: Sun, 17 Jul 2022 17:38:18 +0200 [thread overview]
Message-ID: <20220717153818.r4hE9szL8Vihvn4pHJ9dbyU7kG651Q0MX2JB0ZejXj8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37555@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/37555#issuecomment-1186549202
Comment:
from https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html:
> DbusActivatable: A boolean value specifying if D-Bus activation is supported for this application. If this key is missing, the default value is false. If the value is true then implementations should ignore the Exec key and send a D-Bus message to launch the application. See D-Bus Activation for more information on how this works. Applications should still include Exec= lines in their desktop files for compatibility with implementations that do not understand the DBusActivatable key.
It seems like your system is missing the dbus user session, but wofi tries to launch gnome-disks with a dbus message.
I think this is a bug in wofi - wofi should fall back to just running Exec when the dbus user session is not available.
next prev parent reply other threads:[~2022-07-17 15:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 13:22 [ISSUE] org.gnome.DiskUtility.desktop not launching "gnome-disks" executable through an App Launcher, yet using a custom gendesk .desktop file works fine, CLI as well TeusLollo
2022-07-16 20:56 ` org.gnome.DiskUtility.desktop not executing "gnome-disks" executable through an App Launcher, yet using a custom gendesk .desktop file works fine, CLI as well works paper42
2022-07-17 12:35 ` TeusLollo
2022-07-17 12:44 ` TeusLollo
2022-07-17 13:20 ` paper42
2022-07-17 15:17 ` TeusLollo
2022-07-17 15:18 ` TeusLollo
2022-07-17 15:37 ` paper42
2022-07-17 15:38 ` paper42 [this message]
2022-07-17 16:41 ` TeusLollo
2022-07-17 16:41 ` TeusLollo
2022-07-17 16:44 ` TeusLollo
2022-07-17 16:53 ` paper42
2022-07-17 16:54 ` paper42
2022-07-17 18:08 ` TeusLollo
2022-07-17 18:09 ` TeusLollo
2022-07-17 18:09 ` TeusLollo
2022-07-17 18:10 ` TeusLollo
2022-07-18 18:23 ` paper42
2022-07-18 19:31 ` TeusLollo
2023-02-03 23:20 ` paper42
2023-02-03 23:20 ` [ISSUE] [CLOSED] " paper42
2024-01-25 12:39 ` bileslav
2024-01-28 18:08 ` TeusLollo
2024-01-28 18:10 ` TeusLollo
2024-02-02 23:58 ` bileslav
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=20220717153818.r4hE9szL8Vihvn4pHJ9dbyU7kG651Q0MX2JB0ZejXj8@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).