Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1114207

Bug#1017739: emacs-lucid cannot start after upgrade

From Adam Lackorzynski <adam@os.inf.tu-dresden.de>
Newsgroups linux.debian.bugs.dist
Subject Bug#1017739: emacs-lucid cannot start after upgrade
Date 2022-08-23 11:10 +0200
Message-ID <EXy53-2uye-1@gated-at.bofh.it> (permalink)
References <EWfe9-1G9K-3@gated-at.bofh.it> <EXlhv-2m5P-3@gated-at.bofh.it> <EXnCF-2noA-3@gated-at.bofh.it> <EWfe9-1G9K-3@gated-at.bofh.it> <EXnCF-2noA-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Mon Aug 22, 2022 at 14:53:57 -0700, Russ Allbery wrote:
> Control: severity -1 important
> 
> Adam Lackorzynski <adam@os.inf.tu-dresden.de> writes:
> 
> > I had the same issue. Turned out my personal .emacs.d/eln-cache
> > directory and its folders belonged to root:
> 
> > $ ls -la $HOME/.emacs.d/eln-cache
> > total 16
> > drwxr-xr-x 4 root root  4096 Aug 21 19:32 .
> > drwx------ 4 adam users 4096 Aug 19 19:43 ..
> > drwxr-xr-x 2 root root  4096 Aug 21 19:32 28.1-20961986
> > drwxr-xr-x 2 root root  4096 Aug 19 19:43 28.1-aa5da5cc
> 
> > chown'ing it to me fixed it.
> 
> Oh, good catch!  The same thing was true of mine.
> 
> I think the dates were when I upgraded Emacs.  Let me take a guess: are
> you also old-school and use su from a regular user account when installing
> new packages?  HOME gets overridden by su, but LOGNAME and USER do not,
> and I suspect something in Emacs is deciding where to write files based on
> USER, and the installation process of emacs-lucid creates the eln-cache
> directory for some reason.

Indeed, yes. I'd follow the lines here that a Debian package should
ensure that content generated for global use (which I assume the package
positinst is generating) shall be in a location accessible for everyone.

> I'm downgrading the severity of this bug because I suspect the average
> user using sudo may not run into it (although the maintainer should feel
> free to raise the severity again if they disagree).  If I'm right, the
> best place to solve the problem may be in the Debian maintainer scripts,
> overwriting USER (and possibly LOGNAME, not sure if it matters) to some
> safe value like root while performing the installation.  This may also be
> necessary to do when installing Emacs add-on packges; I'm not sure.
> 
> I've removed the directory with the wrong ownership and upgraded again
> with USER and LOGNAME set to root, and now everything works fine.  (Well,
> my laptop gets extremely hot the first time I start the new Emacs, but I
> assume that's expected for the new compilation system.)
> 
> -- 
> Russ Allbery (rra@debian.org)              <https://www.eyrie.org/~eagle/>

Adam

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#1017739: emacs-lucid cannot start after upgrade Russ Allbery <rra@debian.org> - 2022-08-19 20:50 +0200
  Bug#1017739: emacs-lucid cannot start after upgrade Stefan Monnier <monnier@iro.umontreal.ca> - 2022-08-22 01:40 +0200
    Bug#1017739: emacs-lucid cannot start after upgrade Andrea Corallo <akrl@sdf.org> - 2022-08-22 11:30 +0200
  Bug#1017739: emacs-lucid cannot start after upgrade Adam Lackorzynski <adam@os.inf.tu-dresden.de> - 2022-08-22 21:30 +0200
  Bug#1017739: emacs-lucid cannot start after upgrade Rob Browning <rlb@defaultvalue.org> - 2022-08-23 06:30 +0200
    Bug#1017739: emacs-lucid cannot start after upgrade Russ Allbery <rra@debian.org> - 2022-08-23 06:50 +0200
      Bug#1017739: emacs-lucid cannot start after upgrade Rob Browning <rlb@defaultvalue.org> - 2022-08-23 07:10 +0200
  Bug#1017739: emacs-lucid cannot start after upgrade Adam Lackorzynski <adam@os.inf.tu-dresden.de> - 2022-08-23 11:10 +0200
  Bug#1017739: emacs-lucid cannot start after upgrade Stefan Monnier <monnier@iro.umontreal.ca> - 2022-08-23 16:40 +0200
    Bug#1017739: emacs-lucid cannot start after upgrade Rob Browning <rlb@defaultvalue.org> - 2022-08-24 04:00 +0200
      Bug#1017739: emacs-lucid cannot start after upgrade Stefan Monnier <monnier@iro.umontreal.ca> - 2022-08-24 04:10 +0200
        Bug#1017739: emacs-lucid cannot start after upgrade Russ Allbery <rra@debian.org> - 2022-08-24 05:10 +0200
          Bug#1017739: emacs-lucid cannot start after upgrade Stefan Monnier <monnier@iro.umontreal.ca> - 2022-08-24 14:00 +0200
          Bug#1017739: emacs-lucid cannot start after upgrade David Bremner <bremner@debian.org> - 2022-09-12 00:20 +0200
            Bug#1017739: emacs-lucid cannot start after upgrade Stefan Monnier <monnier@iro.umontreal.ca> - 2022-09-12 03:40 +0200
              Bug#1017739: emacs-lucid cannot start after upgrade David Bremner <bremner@debian.org> - 2022-09-13 02:10 +0200

csiph-web