From: nightowl <nightowl@members.fsf.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: GNU Icecat crashed tab
Date: Sun, 30 Sep 2018 04:27:11 +0200 [thread overview]
Message-ID: <3ac8ccd7205e3bea3dc79b453187eb02@posteo.net> (raw)
In-Reply-To: <87k1n4btz3.fsf@elephly.net>
Thanks all for the help and advice on handling package upgrades and
memory management. I have been able to update my system now and use
icecat version 60. I can verify that the tab crash appears to be
resolved with this new version of icecat on my PC, however I also now
notice that scrolling is not as smooth as it used to be. There seem to
be some delay and jerkiness when scrolling up and down pages with allot
of content, like say a nice wikipedia page with some meaty topic and
lots of figures. I have compared this by booting into my old system
config, and find the scrolling in the previous icecat version is
definitely smoother. Gnome web also shows smoother scrolling than the
version 60 icecat. This new version looks to still be a pre-release, so
maybe there are some issues to address with the fluidity of the
scrolling.
On 29.09.2018 10:14, Ricardo Wurmus wrote:
> nightowl <nightowl@members.fsf.org> writes:
>
>> I have been trying to upgrade the icecat package. I am using the
>> 'guix system reconfigure' command, but seem to be running out of disk
>> space.
>
> Generally, I recommend keeping the user profile separate from a lean
> system profile. This allows you to upgrade your system even if some of
> your user packages cannot currently be built for some reason.
>
>> It is also starting to compile some things instead of using
>> substitutes, but maybe I need to wait for the servers to settle down.
>
> That’s possible. You can get an overview of what’s going to be
> downloaded and what will be built with the “--dry-run” option.
>
>> Currently after running garbage collection, my installation is still
>> about 17GB on a 20GB partition. I have several generations of past
>> configurations, so would it be possible to free up space by removing
>> some of the past generations? How would that be done, I do not see a
>> command for doing that?
>
> You need to manually remove old links of the form
> /var/guix/profiles/system-*-link — be careful not to remove the link
> corresponding to the current system! After that you can run “guix gc”.
>
> --
> Ricardo
next prev parent reply other threads:[~2018-09-30 2:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-22 2:09 GNU Icecat crashed tab nightowl
2018-09-22 10:14 ` Ricardo Wurmus
2018-09-22 10:30 ` Andreas Enge
2018-09-22 10:56 ` Ricardo Wurmus
2018-09-24 14:26 ` Ricardo Wurmus
2018-09-26 2:38 ` nightowl
2018-09-26 5:03 ` Mike Gerwitz
2018-09-27 1:36 ` nightowl
2018-09-27 2:26 ` Mike Gerwitz
2018-09-27 3:30 ` nightowl
2018-09-27 6:06 ` Björn Höfling
2018-09-29 3:26 ` nightowl
2018-09-29 8:14 ` Ricardo Wurmus
2018-09-30 2:27 ` nightowl [this message]
2018-09-30 15:20 ` Mike Gerwitz
2018-09-30 23:50 ` nightowl
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=3ac8ccd7205e3bea3dc79b453187eb02@posteo.net \
--to=nightowl@members.fsf.org \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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.
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).