unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: ptibedo ptibedo <gnu.rooty@gmail.com>,41298@debbugs.gnu.org
Subject: bug#41298: les icones des applications ne s'affiche pas
Date: Fri, 15 May 2020 23:06:46 -0400	[thread overview]
Message-ID: <9D9F0D24-22EF-419D-84D1-882F105539F2@lepiller.eu> (raw)
In-Reply-To: <CAFLSg02xPfNws=m9bQpSWD1fywM8HOeNJRY_uxEiKBkNKE_nxA@mail.gmail.com>

Le 15 mai 2020 19:25:39 GMT-04:00, ptibedo ptibedo <gnu.rooty@gmail.com> a écrit :
>Bonsoir ! Cela fait un moment que ce bug existe et je trouve cela
>étonnant qu'il n'est pas été corrigé depuis.
>Quand j'installe une application je dois constamment fermé la session
>et l'ouvrir pour que les icones précédemment installé soient affichées.
>Je suis sur l'environnement de bureau GNOME.

Oh, since this is bug and not help, I guess it should be in English. Here is a summary for those who wonder what this is about:

When you install an application with guix, you need to log out and in again for the new applications to appear. This happens at jeast with the GNOME desktop environment.

I then suggested to use alt+f2 and type restart to reload the session without having to log out and in again. I think this is more of an issue with gnome not looking for new .desktop files, rather than an issue with guix itself. We don't really have any way to know what desktop environment is running and how to reload application lists.

This is a usability issue, so we should address it. Is there a more standard way to reload a session that I am not aware of? What would a mecanism to create effects (reloading a session) after an install be like? Or should we rather try and propose a patch for gnome to use inotify or similar to check for new .desktop files?

Thoughts?




      parent reply	other threads:[~2020-05-16  3:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 23:25 bug#41298: les icones des applications ne s'affiche pas ptibedo ptibedo
2020-05-16  2:53 ` Julien Lepiller
2020-05-16  8:48   ` zimoun
2020-05-16  3:06 ` Julien Lepiller [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9D9F0D24-22EF-419D-84D1-882F105539F2@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=41298@debbugs.gnu.org \
    --cc=gnu.rooty@gmail.com \
    /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 public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).