unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Oleg Pyhalov <go.wigust@gmail.com>
To: znavko@disroot.org
Cc: 36944@debbugs.gnu.org
Subject: bug#36944: Xfce Panel shortcuts after updates might not work
Date: Sun, 18 Aug 2019 13:12:28 +0300	[thread overview]
Message-ID: <87wofapysz.fsf@majordomo.ru> (raw)
In-Reply-To: <10d5b7fae299933b2e22d98b8b45b7de@disroot.org> (znavko@disroot.org's message of "Tue, 06 Aug 2019 07:42:43 +0000")

[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]

Hello,

znavko@disroot.org writes:

> Hello! Sometimes, when Icecat or Pcmanfm-qt update, I am not able to
> run them from shortcuts I've add to panel as Items (right mouse click
> - Panel - Add new Item).
> This is because applications addresses were changed after update
> (because guix adds hash to application folder).
> This makes me need to delete shortcut and add again.
> Xfce is not in account in this. Xfce does not use
> /home/user/.giux-profile/bin folder for those shortcuts. Xfce uses
> /gnu/store/hashhashahsh-icecat-60.1/bin/icecat instead. And this is my
> trouble.
>
> Do you think we can solve this?

What do you mean by “Xfce does not use /home/user/.giux-profile/bin
folder for those shortcuts”?  If you create a shortcut manually then you
could specify your Guix profile's directory, don't you?

I cannot reproduce the issue (I didn't update packages because of
virtual machine though).  Could you attach a screenshot with a window
where you specify Icecat or Pcmanfm-qt binary location, please?

Regards,
Oleg.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-08-18 10:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06  7:42 bug#36944: Xfce Panel shortcuts after updates might not work znavko
2019-08-18 10:12 ` Oleg Pyhalov [this message]
2019-08-18 15:26   ` Bengt Richter
2023-08-25 10:27 ` 宋文武 via Bug reports for GNU Guix

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=87wofapysz.fsf@majordomo.ru \
    --to=go.wigust@gmail.com \
    --cc=36944@debbugs.gnu.org \
    --cc=znavko@disroot.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.
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).