unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Bradley Haggerty <bradigger@gmail.com>
To: 34454@debbugs.gnu.org
Subject: bug#34454: Icecat crashes after several seconds
Date: Fri, 15 Feb 2019 12:28:56 -0600	[thread overview]
Message-ID: <20190215122856.54fb4a0a@gmail.com> (raw)
In-Reply-To: <20190212041627.31de67cb@gmail.com>

GNU IceCat 60.5.0
guix (GNU Guix) a37bdf4289e9bb533907a6ee5c4c84e68e12c5b1
Fri Feb 15 12:15:29 CST 2019

After the problem the other day I rolled back to a previous working
generation. I've now updated and still had problems, so I'm back with
new crashes. I noticed it mentioned an environment variable to display
more info, so here are two crashes, the second one has it enabled.

icecat:3108): Gdk-ERROR **: 18:11:32.573: The program 'icecat' received
an X Window System error. This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 26875 error_code 8 request_code 2 (core protocol)
minor_code 0) (Note to programmers: normally, X errors are reported
asynchronously; that is, you will receive the error a while after
causing it. To debug your program, run it with the GDK_SYNCHRONIZE
environment variable to change this behavior. You can then get a
meaningful backtrace from your debugger if you break on the
gdk_x_error() function.) zsh: trace trap  icecat


(icecat:4060): Gdk-ERROR **: 18:16:33.014: The program 'icecat'
received an X Window System error. This probably reflects a bug in the
program. The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 10299 error_code 8 request_code 2 (core protocol)
minor_code 0) (Note to programmers: normally, X errors are reported
asynchronously; that is, you will receive the error a while after
causing it. To debug your program, run it with the GDK_SYNCHRONIZE
environment variable to change this behavior. You can then get a
meaningful backtrace from your debugger if you break on the
gdk_x_error() function.) Crash Annotation GraphicsCriticalError:
|[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown
(t=6.64841) [GFX1-]: Receive IPC close with reason=AbnormalShutdown
[Child 4208, Chrome_ChildThread] WARNING: pipe error: Broken pipe:
file /tmp/guix-build-icecat-60.5.0-guix1.drv-0/icecat-60.5.0-guix1/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
line 694 zsh: trace trap  icecat [Child 4108, Chrome_ChildThread]
WARNING: pipe error (3): Connection reset by peer:
file /tmp/guix-build-icecat-60.5.0-guix1.drv-0/icecat-60.5.0-guix1/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
line 342

  parent reply	other threads:[~2019-02-15 18:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12 10:16 bug#34454: After an update, icecat now segfaults very quickly after opening Bradley Haggerty
2019-02-12 10:31 ` bug#34454: (no subject) Bradley Haggerty
2019-02-15 18:28 ` Bradley Haggerty [this message]
2019-03-09 23:37 ` bug#34454: GTK programs segfaulting Bradley Haggerty
2019-03-10 17:45   ` Ludovic Courtès
2019-03-11  3:07 ` Bradley Haggerty
2019-03-12 13:11   ` Ludovic Courtès
2019-03-11  3:09 ` Bradley Haggerty
2019-03-14  4:19 ` Bradley Haggerty
2019-03-30  4:22 ` bug#34454: Gtk upstream bug #1280 causes crashes in IceCat and Emacs Mark H Weaver
2019-03-31  8:52 ` Bradley Haggerty

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=20190215122856.54fb4a0a@gmail.com \
    --to=bradigger@gmail.com \
    --cc=34454@debbugs.gnu.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 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).