unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: clement@lassieur.org (Clément Lassieur)
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 38309@debbugs.gnu.org, a@ajgrf.com
Subject: bug#38309: Recent $EMACSLOADPATH changes crash gnome-session
Date: Tue, 26 Nov 2019 10:20:46 +0100	[thread overview]
Message-ID: <87k17n0z9t.fsf@lassieur.org> (raw)
In-Reply-To: <874kyrvphw.fsf@gmail.com> (Maxim Cournoyer's message of "Tue, 26 Nov 2019 02:23:55 +0900")

Hello Maxim,

Thanks for taking the time to look into this.  I've seen your other
email, you can install libpcre3-dbg to have PCRE's debug symbols.  It
might help.

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

> Hello Ludovic,
>
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hi Maxim,
>>
>> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>>
>>> There would be a couple more commits to include in the revert to undo
>>> the changes (one to the build system, others to adapt the renaming of
>>> the emacs-set-load-path phase for some packages:
>>
>> Oh indeed.

Well, maybe it would make sense to squash them into one revert commit,
that would be re-reverted when the bug is fixed?

>> I must say I haven’t looked closely at the changes nor at the reasons
>> for the regression, but IIUC, the regression is serious enough that we
>> should have a way to address it quickly.
>
> The regression only seems to affect the "restarting the session",
> e.g. logout then login, not the first boot, which means there's an
> (inconvenient) workaround available for single user systems.

Before the patches, restarting Emacs was enough to have new packages
installed.  Now I have to reboot my computer every time I 'guix package
-i emacs-something'.  Emacs is central to my workflow and I often change
things around (as do a lot of Guix users).  It is inconvenient, really.

> I've been trying to reproduce in a VM to get a backtrace (if those
> affected by the problem could produce one, that'd help pinpoint the
> problematic call to PCRE and its origin), but that'll need some more
> time.

Even if you find a solution, the fix will take a lot of time to land
onto an Ubuntu release.

> If those affected judge the situation dire enough, I don't mind
> reverting the changes to the Emacs library loading mechanism for the
> time being.

Please, do so :)

Lots of users don't have that bug, but there's still a change in their
workflow: they have to restart their session after installing new Emacs
packages.  Maybe when that bug is fixed and this set of patch is
re-applied, there will be an opportunity to communicate about this?  On
info-guix maybe, or on 'guix pull'.  It would explain the pros and cons
of this new way of dealing with Emacs.  I don't know if there was such
an announcement already, I didn't see it.  WDYT?

Thanks again,
Clément

  reply	other threads:[~2019-11-26  9:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21  2:25 bug#38309: Recent $EMACSLOADPATH changes crash gnome-session Alex Griffin
2019-11-22 13:00 ` Clément Lassieur
2019-11-22 13:15   ` Mathieu Othacehe
2019-11-22 17:40     ` Maxim Cournoyer
2019-11-23 18:05       ` Ludovic Courtès
2019-11-24  3:45         ` Maxim Cournoyer
2019-11-24 17:56           ` Ludovic Courtès
2019-11-25 17:23             ` Maxim Cournoyer
2019-11-26  9:20               ` Clément Lassieur [this message]
2019-11-26  9:30                 ` Ludovic Courtès
2019-11-27 14:10                 ` Maxim Cournoyer
2019-11-27 14:15                   ` Clément Lassieur
2019-11-27 17:30                   ` Clément Lassieur
2019-11-26  9:43               ` Clément Lassieur
2019-11-26  4:04             ` Maxim Cournoyer
2019-11-26  8:56               ` Ludovic Courtès
2019-11-27  3:12                 ` Maxim Cournoyer
2019-11-27  9:04                   ` Clément Lassieur
2019-11-27  0:01 ` Leo Prikler
2019-11-27 13:58   ` Maxim Cournoyer
2019-11-27 14:21     ` Jelle Licht
2019-11-28  5:28       ` Maxim Cournoyer
2019-12-02 10:36     ` Clément Lassieur
2019-12-03  9:38       ` Arne Babenhauserheide
2019-12-04  9:14       ` Ludovic Courtès
2019-12-04 10:14         ` Clément Lassieur
2019-12-04 12:31           ` Arne Babenhauserheide
2019-12-04 11:11         ` Arne Babenhauserheide
2019-12-06 17:02           ` Maxim Cournoyer
2019-12-07 16:18             ` Arne Babenhauserheide

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=87k17n0z9t.fsf@lassieur.org \
    --to=clement@lassieur.org \
    --cc=38309@debbugs.gnu.org \
    --cc=a@ajgrf.com \
    --cc=maxim.cournoyer@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).