all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Jacob Hrbek <kreyren@rixotstudio.cz>, 56567@debbugs.gnu.org
Subject: bug#56567: [BUG] Gnome doesn't recognize applications path for flatpak
Date: Fri, 15 Jul 2022 10:17:18 +0200	[thread overview]
Message-ID: <ab65b14cc24ab3fa6d9d725d60e9fa4f366d9fe5.camel@ist.tugraz.at> (raw)
In-Reply-To: <80b11ebe-8ebd-274c-d4a0-6b94c6656cc8@rixotstudio.cz>

Am Freitag, dem 15.07.2022 um 01:07 +0000 schrieb Jacob Hrbek:
> Steps to reproduce:
> 1. Install any flatpak app from a GNOME environment
> 2. Try to launch the app from activities  (the gnome menu accessible 
> through super-key) and expect it to not find it
> 
> To fix this i was told that the path 
> `~/.local/share/flatpak/exports/share/applications` has to be
> appended in the environmental variable XDG_DATA_DIRS
Then why don't you simply do so?  Unlike certain distributions *cough*
Ubuntu *cough*, Guix System depends on neither Flatpak nor Snap to
offer "containerized" applications.  This configuration is thus yours
to make.  If your problem is that there's no Guix Home service to do
so, then fair enough, but assuming a regularly managed bash_profile,
that line should be easy enough to add (and more importantly how to add
it should be documented by Flatpak – if not, that's their issue).




       reply	other threads:[~2022-07-15  8:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <80b11ebe-8ebd-274c-d4a0-6b94c6656cc8@rixotstudio.cz>
2022-07-15  8:17 ` Liliana Marie Prikler [this message]
     [not found]   ` <823067fc-f926-8fde-f20c-c3fbbdb9f364@rixotstudio.cz>
2022-07-18  6:13     ` bug#56567: [BUG] Gnome doesn't recognize applications path for flatpak Liliana Marie Prikler
2023-09-12 11:57       ` Csepp

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=ab65b14cc24ab3fa6d9d725d60e9fa4f366d9fe5.camel@ist.tugraz.at \
    --to=liliana.prikler@ist.tugraz.at \
    --cc=56567@debbugs.gnu.org \
    --cc=kreyren@rixotstudio.cz \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.