unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: Mohammed Sadiq <sadiq@sadiqpk.org>, 24445@debbugs.gnu.org
Subject: bug#24445: GNOME desktop session crash when re-arranging dock
Date: Sun, 08 Oct 2017 21:18:28 +0200	[thread overview]
Message-ID: <87shetcut7.fsf@gnu.org> (raw)
In-Reply-To: <87infpr6om.fsf@thomasdanckaert.be> (Thomas Danckaert's message of "Sun, 08 Oct 2017 17:38:17 +0200")

Howdy!

Thomas Danckaert <post@thomasdanckaert.be> skribis:

> Ha, I was just going to reply the same (see attached patch).  I've
> tested it on my system as well, and it works.
>
> Indeed encoding the absolute file name of the icon theme seems hard,
> unless we set the icon theme inside the system configuration?  Not sure
> how we want to handle icon themes installed in user profiles.

Yeah, let’s just keep /run/current-system & co.

> In my patch, I included both system and user profile, in case users want
> to install icon themes in their profile, as well as the default ~/.icons
> (which seems to be a kind of standard as well, so thought we could keep
> it by default).

Yes, it’s a good idea to include ~/.icons and
~/.guix-profile/share/icons (I thought that XCURSOR_PATH did not take
override the default, which includes ~/.icons.)

> Also, I'm not sure if we need to set both paths in /etc/profile, or if
> we can just have icon theme packages prepend to the current XCURSOR_PATH
> when installed into a user profile (I'm not familiar with the details of
> http://bugs.gnu.org/20255)?

I think we should set XCURSOR_PATH via
‘session-environment-service-type’ like in the patch I posted.  I find
it marginally nicer than setting it in /etc/profile because that way it
remains close to ‘gnome-service-type’; we need to do the same in
‘xfce-service-type’ though.  WDYT?

Then, eventually, we can add XCURSOR_PATH as a search path definition of
‘libxcursor’, but due to bug 20255, it won’t be effective here; so
that’ll be a mostly cosmetic change.

Does that make sense?

Anyway, glad we have a fix.  :-)

Ludo’.

  reply	other threads:[~2017-10-08 19:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15 13:45 bug#24445: GNOME desktop session crash when re-arranging dock Ravishankar S
2017-09-27  7:48 ` Thomas Danckaert
2017-09-30  5:51 ` bug#24445: [No Subject] Mohammed Sadiq
2017-10-02 14:51   ` bug#24445: GNOME desktop session crash when re-arranging dock Ludovic Courtès
2017-10-02 18:01     ` Mohammed Sadiq
2017-10-02 18:34     ` Mark H Weaver
2017-10-08 13:50       ` Thomas Danckaert
2017-10-08 15:08         ` Ludovic Courtès
2017-10-08 15:38           ` Thomas Danckaert
2017-10-08 19:18             ` Ludovic Courtès [this message]
2017-10-09  8:58               ` Thomas Danckaert
2017-10-09  9:51                 ` Ludovic Courtès
2017-10-09 10:47                   ` Thomas Danckaert
2017-10-10  8:29                   ` Thomas Danckaert

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=87shetcut7.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=24445@debbugs.gnu.org \
    --cc=post@thomasdanckaert.be \
    --cc=sadiq@sadiqpk.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).