public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: forgottenwizard <phrexianreaper@hushmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] urxvtd segfaulting (no idea why)
Date: Wed, 23 Jan 2008 13:56:42 -0600	[thread overview]
Message-ID: <20080123195642.GA15054@localhost> (raw)

Recently (as in the last day or two), I have started to have problems
with urxvtd. I'm currently running version 8.9 (~x86), but on to the
problem itself.

I have had problems with urxvtd segfaulting after opening a terminal,
then closing it. It doesn't spit out an error that I have seen (running
as urxvtd & in an xterm), but after opening the term, and closing it
again, and trying to open a second term, it segfaults (according to jobs
in the same term I ran urxvtd).

Any clues as to a good way to track this down, as it seems to happen as
well in the stable version?

-- 
gentoo-user@lists.gentoo.org mailing list



             reply	other threads:[~2008-01-23 20:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-23 19:56 forgottenwizard [this message]
2008-01-23 20:37 ` [gentoo-user] urxvtd segfaulting (no idea why) Marcin Dzierzkowski
2008-01-23 20:54   ` forgottenwizard

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=20080123195642.GA15054@localhost \
    --to=phrexianreaper@hushmail.com \
    --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