From: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
To: gentoo-user@lists.gentoo.org
Cc: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
Subject: [gentoo-user] Re: Strange sunbird segfault
Date: Wed, 4 Nov 2009 22:32:00 +0100 [thread overview]
Message-ID: <20091104213200.GH12983@vidovic> (raw)
In-Reply-To: <200910182235.13059.jcunning@cunning.ods.org>
On Sun, Oct 18, 2009 at 10:35:04PM -0700, Jim Cunning wrote:
> jcunning@jlc64 ~ $ sunbird
> Xlib: extension "Generic Event Extension" missing on display ":0.0".
> /usr/libexec/mozilla-launcher: line 119: 25986 Segmentation fault $(type
> -P aoss) "$mozbin" $xulparams "$@"
> sunbird-bin exited with non-zero status (139)
<...>
> Anyone have any suggestions where to look when sunbird segfaults again?
"segmentation fault"s should never happen. They are mainly due to
mistakes in the source code. The best thing to do is to check if this is
an already known bug at Gentoo and the sundbird project. If no, you
could send a bug report.
--
Nicolas Sebrecht
prev parent reply other threads:[~2009-11-04 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 5:35 [gentoo-user] Strange sunbird segfault Jim Cunning
2009-11-04 21:32 ` Nicolas Sebrecht [this message]
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=20091104213200.GH12983@vidovic \
--to=nicolas.s-dev@laposte.net \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox