Github messages for voidlinux
 help / color / mirror / Atom feed
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: Mon, 18 Jul 2022 21:31:51 +0200	[thread overview]
Message-ID: <20220718193151.HaVdB1K9whkRkoWLop5uaM6P5qWiYZHd-nXmG_PQYBU@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: 1347 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/37555#issuecomment-1188214908

Comment:
First of all, sorry for taking a long time, but I was away from my void boxes today.

Here's the report:

1) Yep, `dex /usr/share/applications/org.gnome.DiskUtility.desktop` works perfectly, which circumscribes the problem to a wofi bug? | lack of feature?

2) Not sure why other void users never noticed this bug though. Maybe usage of WMs instead of DEs is not that common, especially on wayland?

3) Not sure if this should be reported to https://todo.sr.ht/~scoopta/wofi since the wofi readme already remarks wofi "can experience issues on systems where a user session bus is not automatically started such as systems using elogind". Seems they're aware of this. 

4) Maybe something about this should be mentioned into the "[Session and Seat Management](https://docs.voidlinux.org/config/session-management.html#session-and-seat-management)" of the void handbook? As is "If you're having problems running .desktop files with elogind on wayland, try using gendesk and a custom local path to a .desktop file"?

You're the boss, you decide. Kinda funny this story though. I really think however the workaround with gendesk and the custom .desktop file should go into a manual somewhere. 

  parent reply	other threads:[~2022-07-18 19:31 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
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 [this message]
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=20220718193151.HaVdB1K9whkRkoWLop5uaM6P5qWiYZHd-nXmG_PQYBU@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).