From: Ricardo Wurmus <rekado@elephly.net>
To: raingloom <raingloom@riseup.net>, Mark H Weaver <mhw@netris.org>
Cc: 43610@debbugs.gnu.org
Subject: bug#43610: IceCat segfault
Date: Mon, 30 Nov 2020 21:12:48 +0100 [thread overview]
Message-ID: <87czzu8uyn.fsf@elephly.net> (raw)
In-Reply-To: <87ft4q8v9q.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> I have the same problem. Icecat segfaults right away without any window
>> appearing. “-safe-mode” does not make a difference, but with “-p” I’m
>> presented with the profile manager. I haven’t tried creating a new
>> profile yet, nor have I tried deleting files from my existing profile.
>>
>> I’m using Gnome on Guix System. To be sure that it isn’t caused by a
>> known bug in how we packaged Gnome Shell, I unset LD_LIBRARY_PATH before
>> running icecat, but with no effect.
>>
>> I see a segfault with the latest icecat-78.3.1-guix0-preview1 and with
>> the older 78.3.0-guix0-preview1. No segfault with
>> 68.12.0-guix0-preview1.
>
> Starting the new Icecat with “icecat --migration” and telling it to
> import the existing Icecat profile did the trick for me. I did not
> delete anything from my existing profile.
This is not a complete fix, though. Icecat goes straight back to
segfaulting when restarted. When I start it with “icecat --migration”
and import the profile (every time I start it) I can get past the
segfault. So, whatever it does there does not seem to be permanent.
--
Ricardo
next prev parent reply other threads:[~2020-11-30 20:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 13:26 bug#43610: IceCat segfault raingloom
2020-09-25 16:11 ` Mark H Weaver
2020-09-26 2:34 ` raingloom
2020-09-26 18:05 ` Mark H Weaver
2020-09-27 5:49 ` raingloom
2020-09-27 20:36 ` Mark H Weaver
2020-10-01 22:57 ` raingloom
2020-10-01 23:28 ` raingloom
2020-10-09 7:42 ` Ricardo Wurmus
2020-11-30 20:06 ` Ricardo Wurmus
2020-11-30 20:12 ` Ricardo Wurmus [this message]
2020-12-13 18:19 ` Alex ter Weele
2020-12-15 11:24 ` Ludovic Courtès
2022-07-11 18:38 ` Maxim Cournoyer
2020-10-01 1:56 ` Mike Gerwitz
2023-04-07 16:14 ` bug#43610: Segfault still an issue Dominik Delgado via Bug reports for GNU Guix
2023-04-08 7:55 ` Dominik Delgado via Bug reports for GNU Guix
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=87czzu8uyn.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=43610@debbugs.gnu.org \
--cc=mhw@netris.org \
--cc=raingloom@riseup.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.
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).