From: raingloom <raingloom@riseup.net>
To: Mark H Weaver <mhw@netris.org>
Cc: 43610@debbugs.gnu.org
Subject: bug#43610: IceCat segfault
Date: Sat, 26 Sep 2020 04:34:25 +0200 [thread overview]
Message-ID: <20200926043425.7724956d@riseup.net> (raw)
In-Reply-To: <87r1qp96py.fsf@netris.org>
On Fri, 25 Sep 2020 12:11:10 -0400
Mark H Weaver <mhw@netris.org> wrote:
> Hi,
>
> raingloom <raingloom@riseup.net> writes:
> > Haven't had time to look deeper into it yet. It worked in my profile
> > from sept 11, it broke after pulling and upgrading yesterday.
> > Idk what my commit is because I'm using a private branch.
>
> On Sept 22, I pushed a major update of IceCat from 68.12.0 to 78.3.0:
>
> commit c7011ff850420fdbe1319b3d218bd362f2f9d618
> Author: Mark H Weaver <mhw@netris.org>
> Date: Sun Sep 6 21:47:33 2020 -0400
>
> gnu: icecat: Update to 78.3.0-guix0-preview1 [security-fixes].
>
> Includes fixes for CVE-2020-15673, CVE-2020-15676, CVE-2020-15677,
> and CVE-2020-15678.
>
> [...]
>
> More details would be helpful. For example, it's not clear from your
> report whether it segfaults immediately on startup or sometime later,
> whether a window appears, etc. Also, are you using Guix on top of a
> foreign distro, or natively? Wayland or X?
>
> It would also be useful to know how IceCat 78 behaves on your system
> with a fresh profile. Try it by running "icecat -p", creating a new
> profile from the profile manager window, and then starting icecat with
> that new profile selected. If that works, it would then be useful to
> try adding back any extensions that were installed in the profile that
> crashed, and see if that makes a difference.
>
> Thanks,
> Mark
It crashed immediately without any visible activity.
It does start up properly with a fresh profile. I'll try to bisect the
addons list later.
Tbh this would be a good time to have a debug output for IceCat on hand.
next prev parent reply other threads:[~2020-09-26 2:35 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200926043425.7724956d@riseup.net \
--to=raingloom@riseup.net \
--cc=43610@debbugs.gnu.org \
--cc=mhw@netris.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.