public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] debugging pan crash
Date: Thu Oct 11 09:30:02 2001	[thread overview]
Message-ID: <1002814075.7370.4.camel@zoidberg> (raw)
In-Reply-To: <20011011111154.26277732.jlong@fedworld.gov>

[-- Attachment #1: Type: text/plain, Size: 2273 bytes --]

tor 2001-10-11 klockan 18.11 skrev James M Long:
> Well after a fairly lenghty compile, install... find an open newserver... I have tried the newest ebuild for PAN. The server I tried it on had the following setup:
> 
> portage 1.6.9 (yes I know I should have the newer portage installed but I wanted to try this anyway)
> glibc 2.2.4-r2
> gtk+-1.2.10-r4
> libxml-1.8.16
> gdk-pixbuf-0.11.0-r1
> gnome-libs-1.4.1.2-r2
> 
> My USE flags are as follows
> USE="slang ldap aalib perl mysql readline gpm berkdb gdbm tcpd pam libwww ssl lm_sensors lvm nls mmx mitshm lcms gif gtk X qt kde opengl mozilla"
> 
> I started up PAN and entered a newserver... and then downloaded the groups. Then I downloaded a number of headers from varioous grooups on the server. After downloading the message bodies, I quit PAN. I restarted and continued to download headers and messages for 15 minutes to see if I could get the bug to show up. The only time I could get any bugs or segfaults to showup was when I noticed that I still had gtk+-1.2.10-r3 installed and did a unmerge and restarted PAN in the same xterm I had open before. (Which caused similar errors to what Gold is Heavy has seen). Starting a new xterm solved that problem and I haven't gotten it to crash since. 
> 
> The server I just tested this on has never had the GNOME USE flags set at all and has only been up and running since the 30th of last month. So I don't think there is real issue with the dependances. Maybe someone else has a better idea of what the problem is. I can't find it at all, and after my mistakes earlier in this thread... I am being as careful as I can :)

The problem is probably related to the fact that we did a large move of
packages last weekend. Where we for example moved gtk+ from /usr/X11R6
into /usr and all of GNOME from /opt/gnome into /usr.

If actions haven't been taken to fix this _PLEASE_ read:
http://cvs.gentoo.org/pipermail/gentoo-dev/2001-October/007371.html
(the entire thread)

And _DON'T_ forget to remove /etc/env.d/90gnome, run env-update log out
and in again so that GNOMEDIR and GNOME_PATH is _NOT_ set.

Regards,
  Mikael Hallendal

-- 

Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

      reply	other threads:[~2001-10-11 15:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-10 18:08 [gentoo-dev] debugging pan crash Gold is Heavy
2001-10-11  6:57 ` James M Long
2001-10-11  7:07   ` Mikael Hallendal
2001-10-11  7:31   ` Gold is Heavy
2001-10-11  7:45     ` James M Long
2001-10-11  7:46     ` Mikael Hallendal
2001-10-11  9:05     ` James M Long
2001-10-11  9:30       ` Mikael Hallendal [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=1002814075.7370.4.camel@zoidberg \
    --to=hallski@gentoo.org \
    --cc=gentoo-dev@cvs.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