Guix gc removes next-gtk-webkit input with next installed

  • Open
  • quality assurance status badge
Details
4 participants
  • Dimakakos Dimos
  • Konrad Hinsen
  • Pierre Neidhardt
  • Ricardo Wurmus
Owner
unassigned
Submitted by
Dimakakos Dimos
Severity
normal
D
D
Dimakakos Dimos wrote on 9 Sep 2019 18:13
(address . bug-guix@gnu.org)
87y2yxsb08.fsf@gmail.com
After running gc and trying to launch next-browser I get:

<INFO> [19:11:29] next base.lisp (start) - NEXT::+VERSION+: "1.3.1"
<INFO> [19:11:29] next base.lisp (load-lisp-file form-fun-4) -
Loading configuration from /home/bendersteed/.config/next/init.lisp...
<WARN> [19:11:30] next minibuffer.lisp (echo) -
Can't echo 'MINIBUFFER-MODE enabled.' without minibuffer or interface
<INFO> [19:11:30] next remote.lisp (ensure-dbus-session form-fun-4) -
Bus connection name: :1.103
<INFO> [19:11:30] next remote.lisp (initialize-instance :after remote-interface) -
Bus connection name: :1.104
<INFO> [19:11:30] next port.lisp (run-program port) -
Current directory: /home/bendersteed/
<INFO> [19:11:30] next port.lisp (run-program port) -
Platform port path: /gnu/store/5hh6qpp4lqa6gy1ghdb4ppvjamgb3mbc-next-gtk-webkit-1.3.1/bin/next-gtk-webkit
<INFO> [19:11:30] next port.lisp (run-program port) -
Platform port arguments: NIL
<INFO> [19:11:30] next port.lisp (run-program port) -
Platform port log file: /home/bendersteed/.local/share/next/next-gtk-webkit.log
<ERROR> [19:11:30] next base.lisp (initialize-port remote-interface fun24) -
Couldn't execute "/gnu/store/5hh6qpp4lqa6gy1ghdb4ppvjamgb3mbc-next-gtk-webkit-1.3.1/bin/next-gtk-webkit": No such file or directory
Make sure the platform port executable is either in the
PATH or set in you ~/.config/next/init.lisp, for instance:

(setf (get-default 'port 'path)
"~/common-lisp/next/ports/gtk-webkit/next-gtk-webkit")
;
; compilation unit aborted
; caught 1 fatal ERROR condition

Obviously the package should be live and not be picked up by gc, since
it's an input of a package in a current profile. Any ideas why that
could happen?
R
R
Ricardo Wurmus wrote on 9 Sep 2019 23:25
(name . Dimakakos Dimos)(address . bendersteed@gmail.com)(address . 37357@debbugs.gnu.org)
8736h59n6r.fsf@elephly.net
Dimakakos Dimos <bendersteed@gmail.com> writes:

Toggle quote (1 lines)
> After running gc and trying to launch next-browser I get:
[…]
Toggle quote (2 lines)
> <ERROR> [19:11:30] next base.lisp (initialize-port remote-interface fun24) -
> Couldn't execute "/gnu/store/5hh6qpp4lqa6gy1ghdb4ppvjamgb3mbc-next-gtk-webkit-1.3.1/bin/next-gtk-webkit": No such file or directory
[…]
Toggle quote (4 lines)
> Obviously the package should be live and not be picked up by gc, since
> it's an input of a package in a current profile. Any ideas why that
> could happen?

Can you tell us what version of Guix you used to install Next? There
was a short period during which the Next executable was compressed,
which effectively hid references from the garbage collector.

--
Ricardo
D
D
Dimakakos Dimos wrote on 10 Sep 2019 09:51
(address . 37357@debbugs.gnu.org)
87a7bcfv1c.fsf@gmail.com
Ricardo Wurmus writes:

Toggle quote (4 lines)
> Can you tell us what version of Guix you used to install Next? There
> was a short period during which the Next executable was compressed,
> which effectively hid references from the garbage collector.

OK, so I checked and it seems that I installed next while there was the
patch for the executable compression, particularly commit 79c6d8781b, in
master. I will try again to rebuild and then gc to check if it works as
intended and then close this bug. Thanks!
P
P
Pierre Neidhardt wrote on 19 Sep 2019 15:24
(name . Dimakakos Dimos)(address . bendersteed@gmail.com)
87impoa066.fsf@ambrevar.xyz
This is the known bug #33848, it's not related to core compression.

--
Pierre Neidhardt
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAl2DgaEACgkQm9z0l6S7
zH9GpAgAnjsmTeD6Xwyg7ya/wSocCmth9whF2vSIfTvhhDu/51Dn1FD/MydiwJqd
9ma2EbwQJbp5Nfz+h+foKWNqOIXLuuwZw2+VIf1epLMS1LqzVv/VjQ2tQ7jxHq3u
7+aEbFV3LoOZRJH5NGzdaXzXP3OpQlS+vfg4HaggZ0k1b+9bu9lW+R4eqZ/360FO
NvJq42bxDv4K482d5PYVF9pYd62lltYasuC+oTZmbABYSeVKSM5TcldLfSnyOf0y
3Ijjrw1t9Q2PS14PhZTj7Wt5houKqTGm9SiPTbaZjstQeQhljuR5IhHVdkshn/0y
1YxlUQG/EyWLQWRrlArcqJt66Z57pw==
=Evhq
-----END PGP SIGNATURE-----

K
K
Konrad Hinsen wrote on 26 Sep 2019 18:37
Is there a workaround?
(address . 37357@debbugs.gnu.org)
m1ftkjovyf.fsf@khs-macbook.home
I suspect that I am a victim of this bug as well. Is there a workaround?
I tried removing next, doing another gc to get a clean slate, and then
re-installed next. But it still complains that it can't find the
next-gtk-webkit executable.

Konrad.
K
K
Konrad Hinsen wrote on 26 Sep 2019 19:45
(address . 37357@debbugs.gnu.org)
m1d0fnossd.fsf@khs-macbook.home
Konrad Hinsen <konrad.hinsen@fastmail.net> writes:

Toggle quote (5 lines)
> I suspect that I am a victim of this bug as well. Is there a workaround?
> I tried removing next, doing another gc to get a clean slate, and then
> re-installed next. But it still complains that it can't find the
> next-gtk-webkit executable.

This actually does work, if you remove older generations of your profile
first that still contain next. So this is a workaround, but a somewhat
radical one because it requires throwing away a lot of stuff.

Konrad.
?