From icculus at clutteredmind.org  Tue Apr  8 17:49:02 2003
From: icculus at clutteredmind.org (Ryan C. Gordon)
Date: Tue, 8 Apr 2003 17:49:02 -0400 (EDT)
Subject: glibc 2.3 - loki updates segfaulting? (fwd)
Message-ID: <Pine.LNX.4.33.0304081748500.1731-100000@wickedsick.verizon.net>


Is this in the FAQ yet?

--ryan.



---------- Forwarded message ----------
Date: Tue, 08 Apr 2003 15:40:18 -0500 (CDT)
From: "adam at damek.org" <adam at damek.org>
To: "icculus at clutteredmind.org" <icculus at clutteredmind.org>
Subject: glibc 2.3 - loki updates segfaulting?

Hi - I don't really know if you are the right person to contact, or if you will even care :) ... if not,
sorry to bother you.

The reason for this email is that I'm having problems updating some old Loki stuff.  Every time
I set up a new linux box, one of the first things I do is set up the few old Loki games I have.
At the moment I've set up a new Red Hat 9 box and a new Mandrake 9.1 box.  On both of
them, I've installed the Alpha Centauri planetary pack.  The game plays fine, but when I try to
run the smac update program to update the game to 6.0a, it segfaults:

-----
Uncompressing Sid Meier's Alpha Centauri 6.0a Update...................
./update.sh: line 60:  8564 Segmentation fault      loki_patch --verify patch.dat
The program returned an error code (1)
-----

I also can't update loki_update - the most recent (1.0.13, i think) .run file I can find on google
also segfaults.  From searching with google, the best I can tell is that these programs are
crashing because glibc is now at 2.3.x ... does that sound right?  If so, is there any possibility
of getting updated updaters?

I can just play the games without them - it's no big deal.  I'm mostly just wondering what you
may know about the problem.

Keep up the good work!

-Adam Piontek



From vogon at icculus.org  Tue Apr  8 17:56:34 2003
From: vogon at icculus.org (Colin Bayer)
Date: Tue, 08 Apr 2003 14:56:34 -0700
Subject: [lgfaq] glibc 2.3 - loki updates segfaulting? (fwd)
In-Reply-To: <Pine.LNX.4.33.0304081748500.1731-100000@wickedsick.verizon.net>
References: <Pine.LNX.4.33.0304081748500.1731-100000@wickedsick.verizon.net>
Message-ID: <3E934592.6090102@icculus.org>

Ryan C. Gordon wrote:
> Is this in the FAQ yet?
> 
> --ryan.

I think it is.

-- Colin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3415 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://icculus.org/pipermail/lgfaq/attachments/20030408/a0b2b843/attachment.bin>

From icculus at clutteredmind.org  Mon Apr 28 00:39:42 2003
From: icculus at clutteredmind.org (Ryan C. Gordon)
Date: Mon, 28 Apr 2003 00:39:42 -0400 (EDT)
Subject: Updates:
Message-ID: <Pine.LNX.4.33.0304280025030.3271-100000@wickedsick>


Is anyone maintaining this thing now? Some notes for the audio section:

1) We (4Front, jvalenzu and I) just fixed a problem in OpenAL, so the
latest CVS should work correctly with commercial OSS drivers...this fixes
UT1 and UT2003 (and ArmyOps, and Devastation, and...). I mention this
because of the question:

  "In UT, I get some generally scary effects with latency & other things,
even though I'm not running arts or esd."

"Build the latest CVS of OpenAL" is the new correct answer. "Upgrade to
the latest UTPG" will be the correct option in the next few weeks...unless
you want to use the GenericAudioSubsystem, which (arguably) will be lower
sound quality if you've got a decent OpenAL setup.

2) Can someone with KDE installed give better instructions than "killall
-9 artsd" for disabling the sound server? There's user interface in place
to turn it off and keep it from coming back, and restart it if you are so
inclined.

Thanks,
--ryan.




From zakk at timedoctor.org  Mon Apr 28 00:40:43 2003
From: zakk at timedoctor.org (zakk)
Date: 28 Apr 2003 00:40:43 -0400
Subject: [lgfaq] Updates:
In-Reply-To: <Pine.LNX.4.33.0304280025030.3271-100000@wickedsick>
References: <Pine.LNX.4.33.0304280025030.3271-100000@wickedsick>
Message-ID: <1051504842.13866.0.camel@TARDIS.MKII>

On Mon, 2003-04-28 at 00:39, Ryan C. Gordon wrote:
> Is anyone maintaining this thing now? Some notes for the audio section:
> 
> 1) We (4Front, jvalenzu and I) just fixed a problem in OpenAL, so the
> latest CVS should work correctly with commercial OSS drivers...this fixes
> UT1 and UT2003 (and ArmyOps, and Devastation, and...). I mention this
> because of the question:
> 
>   "In UT, I get some generally scary effects with latency & other things,
> even though I'm not running arts or esd."
> 
> "Build the latest CVS of OpenAL" is the new correct answer. "Upgrade to
> the latest UTPG" will be the correct option in the next few weeks...unless
> you want to use the GenericAudioSubsystem, which (arguably) will be lower
> sound quality if you've got a decent OpenAL setup.
> 
> 2) Can someone with KDE installed give better instructions than "killall
> -9 artsd" for disabling the sound server? There's user interface in place
> to turn it off and keep it from coming back, and restart it if you are so
> inclined.
> 
> Thanks,
> --ryan.
I'll take care of this stuff when I get home tommorow.
-- 
zakk <zakk at timedoctor.org>



From zakk at timedoctor.org  Mon Apr 28 20:52:20 2003
From: zakk at timedoctor.org (zakk)
Date: 28 Apr 2003 20:52:20 -0400
Subject: [lgfaq] Updates:
In-Reply-To: <Pine.LNX.4.33.0304280025030.3271-100000@wickedsick>
References: <Pine.LNX.4.33.0304280025030.3271-100000@wickedsick>
Message-ID: <1051577540.22507.2.camel@TARDIS.MKII>

1 is done
2 needs me to install KDE, waiting for me to figure out why cdrom
burning isn't working.
-- 
zakk <zakk at timedoctor.org>



From Aivils.Stoss at unibanka.lv  Tue Apr 29 02:30:52 2003
From: Aivils.Stoss at unibanka.lv (Aivils.Stoss at unibanka.lv)
Date: Tue, 29 Apr 2003 07:30:52 +0100
Subject: [lgfaq] Updates:
Message-ID: <OF2E6AFC52.B5BCBA70-ONC2256D17.0022AB8A@unibanka.lv>


>2) Can someone with KDE installed give better instructions than "killall
>-9 artsd" for disabling the sound server? There's user interface in place
>to turn it off and keep it from coming back, and restart it if you are so
>inclined.

Unfortunately I do not understand why artsd must be disabled.

Here is my /usr/share/config/kcmatrsrc
[Arts]
AddOptions=
Arguments=\s-F 10 -S 4096 -D /dev/dsp -s 5 -m artsmessage -l 3 -f
AudioIO=
AutoSuspend=true
Bits=0
DeviceName=/dev/dsp
FullDuplex=false
Latency=250
LoggingLevel=3
MessageApplication=artsmessage
NetworkTransparent=false
SamplingRate=0
StartRealtime=true
StartServer=true
SuspendTime=60
X11GlobalComm=false


-s <seconds> auto-suspend time in seconds.
In my case after 5 sec artsd gonna suspended and FREE /dev/dsp.
So if KDE play "bang-bang-bang", after 5 sec user can use sound
device file. Default 60 sec is to long.

Aivils Stoss



From alkini at linuxgames.com  Tue Apr 29 09:55:58 2003
From: alkini at linuxgames.com (Al Koskelin)
Date: 29 Apr 2003 08:55:58 -0500
Subject: [lgfaq] Updates:
In-Reply-To: <Pine.LNX.4.33.0304280025030.3271-100000@wickedsick>
References: <Pine.LNX.4.33.0304280025030.3271-100000@wickedsick>
Message-ID: <1051624557.8230.6.camel@peasoup.salaries.com>

I'm not sure how to update the doc directly (CVS?) so I'm just posting
this here with the hopes that somebody (zakk) can either make the change
for me or let me know how to do it.

To disable artsd:
- start the control center
- under the "Index" tab, go to Sound --> Sound Server
- if you want to disable artsd from starting in the first place, uncheck
the first option: "Start aRts soundserver on KDE startup". When you
click "Apply" to make the changes take place, you're prompted with:
"Shut down sound-server now? ..." so just click the "Yes" button and
artsd is gone.
- if you want to make the changes that Aivils Stoss was talking about,
you can make them here too with the "Autosuspend if idle for" option,
etc.

This was all based on the KDE that ships with Red Hat 8.0 (KDE 3.0). I
hope it helps.

Al

On Sun, 2003-04-27 at 23:39, Ryan C. Gordon wrote:
> 2) Can someone with KDE installed give better instructions than "killall
> -9 artsd" for disabling the sound server? There's user interface in place
> to turn it off and keep it from coming back, and restart it if you are so
> inclined.