From: TeusLollo <TeusLollo@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 18:41:31 +0200 [thread overview]
Message-ID: <20220717164131.DzazP4QigCNTKk-4iVN-SHlKxSJB1C5j766b-zY9TTw@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: 809 bytes --]
New comment by TeusLollo on void-packages repository
https://github.com/void-linux/void-packages/issues/37555#issuecomment-1186564338
Comment:
This gets even weirder.
I added the `DBusActivatable=true` parameter to my custom gendesk .desktop file, just to see if it would force wofi to start, and possibly fail, a dbus session.
But NO, the custom gendesk .desktop file STILL works fine, `wofi --show drun` reports NO error either.
I mean, the only relevant difference between package .desktop file, and custom .desktop file, are the `DBusActivatable=true` parameter, localization tags, and different directory locations.
I'm at loss here. Using `dbus-elogind-1.12.20_1` package, btw. It can't be a missing dependency and/or misconfiguration, since the custom .desktop file works fine. Weird.
next prev parent reply other threads:[~2022-07-17 16:41 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
2022-07-17 16:41 ` TeusLollo
2022-07-17 16:41 ` TeusLollo [this message]
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=20220717164131.DzazP4QigCNTKk-4iVN-SHlKxSJB1C5j766b-zY9TTw@z \
--to=teuslollo@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).