libintl.so.3?
by Paul F. Johnson
Hi,
Just tried to to a yum update as well as one yesterday only to have php
requires libintl.so.3 which is unavailable come up both times.
Any idea which package it's from or is it just currently missing and I
need to wait a bit longer?
TTFN
Paul
--
"Your lives are in the hands of men no smarter than you or I, many of
them incompetent boobs. I know this because I worked alongside them,
gone bowling with them, watched them pass me over for promotions time
and again. And I say ... This stinks!" - Homer Simpson
19 years, 11 months
new mailman for FC1 available to fix password security problem
by John Dennis
Subject: Fedora Core 1 Test Update: mailman-2.1.5-6
---------------------------------------------------------------------
Fedora Test Update Notification
FEDORA-2004-167
2004-06-10
---------------------------------------------------------------------
Product : Fedora Core 1
Name : mailman
Version : 2.1.5
Release : 6
Summary : Mailing list manager with built in Web access.
Description :
Mailman is software to help manage email discussion lists, much like
Majordomo and Smartmail. Unlike most similar products, Mailman gives
each mailing list a webpage, and allows users to subscribe,
unsubscribe, etc. over the Web. Even the list manager can administer
his or her list entirely from the Web. Mailman also integrates most
things people want to do with mailing lists, including archiving, mail
<-> news gateways, and so on.
Documentation can be found in: /usr/share/doc/mailman-2.1.5
When the package has finished installing, you will need to perform some
additional installation steps, these are described in:
/usr/share/doc/mailman-2.1.5/INSTALL.REDHAT
---------------------------------------------------------------------
Update Information:
Fixes security issue CAN-2004-0412 noted in bug
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=123559
Mailman subscriber passwords could be retrieved by a remote attacker.
Security hole is fixed in mailman-2.1.5
Important Installation Note:
Some users have reported problems with bad queue counts after
upgrading to version 2.1.5, the operating assumption is this was
caused by performing an install while mailman was running. Prior to
installing this rpm stop the mailman service via:
% /sbin/service mailman stop
Then after installation completes restart the service via:
% /sbin/service mailman start
Red Hat RPM versions of mailman 2.1.5-6 and above have enhanced the
init.d script that controls the mailman service so that "/sbin/service
mailman status" now returns valid information. The RPM has been
augmented to detect if mailman is running prior to installation and if
so it will temporarily stop mailman during the install and restart
mailman after the install completes. If mailman was not running the
RPM will not start mailman after installation. Since the RPM depends
on service status working the installed version of mailman you are
replacing must be at least 2.1.5-6 for the automatic pausing of
mailman during installation to work. This also means since this is the
first RPM with this feature you will need to manually pause mailman
during installation, future upgrades should be automatic.
---------------------------------------------------------------------
---------------------------------------------------------------------
This update can be downloaded from:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/1/
bff6400afb0f212e81ffb7a2e2b0e617 SRPMS/mailman-2.1.5-6.src.rpm
fa23a12ebe267bc951f36836518c6205 i386/mailman-2.1.5-6.i386.rpm
97e885b25e126c2eef5943e82a37ea49
i386/debug/mailman-debuginfo-2.1.5-6.i386.rpm
f15fba5a424e91403cc54fa527755aab x86_64/mailman-2.1.5-6.x86_64.rpm
999512cc65437cf9542df2cdb82b41e1
x86_64/debug/mailman-debuginfo-2.1.5-6.x86_64.rpm
This update can also be installed with the Update Agent; you can
launch the Update Agent with the 'up2date' command. You may
need to edit your up2date channels configuration. Within
/etc/sysconfig/rhn/sources enable the following line:
yum updates-testing
http://fedora.redhat.com/updates/testing/fedora-core-1
---------------------------------------------------------------------
19 years, 11 months
SOHOWARE & FC2... compatible?
by jb
Just a quick question of the clan.
I have a TP570E and am running it dual-boot. I have a NCB100 CardBus
PCMCIA 10/100 network card (DEC 21*40 chipset, maybe tulip_cb?) that
works fine in WinXP, as well as previous installations of Linux (mostly
2.4 kernel). Now with 2.6.5? (whatever default was with FC2), the
memory locations are being disabled by FC2. IRQ11 is active and shared
by other applications/services, but Expansion ROM address, memory
address area and such are showing values but values in parens say disabled.
Suggestions? BTW... I searched for help online and found something that
said /modprobe yenta_socket /would help, then /service pcmcia restart/
until the next boot, but it doesn't seem to help with me. I think the
problem is bigger/different than that.
many thanks,
jontheisguy
19 years, 11 months
Re: OpenGL and the 2.6.6 kernel
by Mike Lurk
On Mon, Jun 07, 2004 at 01:22:56PM -0400, Mike Lurk wrote:
> Here is some info that might be useful after running xdpyinfo
Can you do the following
telinit 3
login on a text command line
startx
run the app which makes it bomb out
See what is in /var/log/Xorg.log.* (I think - used to be XFree86.log.*)
If an X crash occurred you'll get the needed info then
and telinit 5 will go back to gdm mode
____________________________________________________________________-
All looked fine in xorg.0.log until I saw this;
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: Open failed
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: Open failed
[drm] failed to load kernel module "agpgart"
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmGetBusid returned ''
at the bottom of the file is
Error in I810WaitLpRing(), now is 1332682, start is 1330681
pgetbl_ctl: 0xfdd0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 0
LP ring tail: 8 head: 0 len: 0 start 0
eir: 0 esr: 0 emr: 3d
instdone: ff7b instpm: 0
memmode: 4 instps: 0
hwstam: 9ac7 ier: 0 imr: 9ac7 iir: 0
space: 65520 wanted 65528
(II) I810(0): [drm] removed 1 reserved context for kernel
(II) I810(0): [drm] unmapping 8192 bytes of SAREA 0x128d9000 at
0xf6f49000
Fatal server error:
lockup
Please consult the The X.Org Foundation support
at http://wiki.X.Org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional
information.
Error in I810WaitLpRing(), now is 1337778, start is 1335777
pgetbl_ctl: 0xfdd0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 0
LP ring tail: 10 head: 0 len: 0 start 0
eir: 0 esr: 0 emr: 3d
instdone: ff7b instpm: 0
memmode: 4 instps: 0
hwstam: 9ac7 ier: 0 imr: 9ac7 iir: 0
space: 65512 wanted 65528
FatalError re-entered, aborting
lockup
Seems to be a problem with loading dri
Mike
19 years, 11 months
apm sleep 2.6.6-1.422 (and 2.6.5-1.358) on ThinkPad A22p (ATI R128)
by Ed Hill
Hi folks,
First, a big thanks to all for FC2--its running rather nicely on my
ThinkPad A22p.
The only big complaint so far is the inability to sleep with either ACPI
or APM. Using ACPI has exposed some serious problems with ksoftirqd
when certain pcmcia cards are used so I've disabled ACPI with the
"acpi=off" kernel parameter.
Previously, with Red Hat 7.2/7.3/8/9, the apm suspend-to-RAM
functionality worked well. Now, with both 2.6.6-1.422 and 2.6.5-1.358,
I'm unable to suspend even after killing X and rmmod-ing all the sound,
USB, and pcmcia kernel modules. I've tried suspending with both "apm
-s" and by closing the lid. In both cases, I get two "beeps" where one
is the usual about-to-suspend beep and the second sounds like an error
beep.
The logs suggest that there are no problems (pls see below) with the
suspend/resume cycles but the sounds coming from the laptop suggest
otherwise. Apparently, the CPU and CPU fan keep running.
Any help or suggestions would be appreciated!
thanks,
Ed
===
Jun 8 13:18:54 localhost apmd[1315]: System Suspend
Jun 8 13:19:04 localhost kernel: Disabled Privacy Extensions on device
022deac0(lo)
Jun 8 13:19:06 localhost apmd[1315]: Normal Resume after 00:00:12 (100%
unknown) AC power
Jun 8 13:19:39 localhost network: Shutting down loopback interface:
succeeded
Jun 8 13:19:40 localhost apmd[1315]: User Suspend
Jun 8 13:19:48 localhost kernel: Disabled Privacy Extensions on device
022deac0(lo)
Jun 8 13:19:49 localhost apmd[1315]: Normal Resume after 00:00:09 (100%
unknown) AC power
--
Edward H. Hill III, PhD
office: MIT Dept. of EAPS; Rm 54-1424; 77 Massachusetts Ave.
Cambridge, MA 02139-4307
emails: eh3(a)mit.edu ed(a)eh3.com
URLs: http://web.mit.edu/eh3/ http://eh3.com/
phone: 617-253-0098
fax: 617-253-4464
19 years, 11 months
bluez patch
by Santavy Peter
Hello,
I would like to ask you
is in the .424 kernel applied a patch-2.6.6-mh3 patch there?
With this patch from the bluez project (www.bluez.org) it is now
possible to use dynamic L2CAP PSM and RFCOMM channel allocation for
server sockets.
Peter
--
__________________________________
Peter Santavy
peter(a)santavy.sk
http://santavy.info
----------------------------------
I have been using legal software -> I have been using free software
Open source - for free and legally
19 years, 11 months
Re: [ltp] Thinkpad X40 and xorg-6.7.0-3
by Giuseppe Castagna
I have tried the drivers from http://www.xig.com (with kernel 2.4.7-rc3)
and according the configuration I use it either crashes the system or
enters an infinite loop with the keyboard disabled. So, this does not
seem a viable solution.Giuseppe Castagna <Giuseppe.Castagna(a)ens.fr>
writes:
On Wed, 2004-06-09 at 09:27, Jean-Louis Leroy wrote:
> > What is *really* annoying is that this corruption appears when I
> > switch to the external monitor as well (and the f1-f7 trick no longer
> > works since the image returns back on the LCD screen). This makes the
> > laptop not usable for presentations, which is one of the main uses
> > of it
>
> I'm in the same situation as you, it appears, and I didn't even know
> because I hadn't tried an external monitor yet.
>
> But here are some good news: I found out that if I kill X after
> switching to the external monitor, the image returns just there. Okay
> I loose my session in the process but it's still better than rebooting
> to XP isn't it?
Yes, in the meanwhile I had found a similar workaround. Simply boot the
X40 with the video-beamer plugged in, and the external output becomes
the default one: so the Ctrl-Alt-F1 Ctrl-Alt-F7 trick works on it, and
overlay is sent to it (so you can watch movies using xv on the external
exit).
Of course your solution is better but I am not sure that it will work
with xv since I guess the graphic driver will continue to use the
internal monitor for overlay. I will check.
Thanks a lot
---Beppe---
19 years, 11 months
Re: Thinkpad X40 and xorg-6.7.0-3
by Giuseppe Castagna
On Mon, 2004-06-07 at 14:03, Giuseppe Castagna wrote:
> use a commercial X-Server like Accelerated X [2].
> >
>
> I will try their demo driver. Thanks again
>
I have tried the drivers from http://www.xig.com (with kernel 2.4.7-rc3)
and according the configuration I use it either crashes the system or
enters an infinite loop with the keyboard disabled. So, this does not
seem a viable solution.
In the meanwhile I found the obvious (once you tried it) workaround to
the corruption on external monitor. Simply boot the X40 with the
video-beamer plugged in, and the external output becomes the default
one: so the Ctrl-Alt-F1 Ctrl-Alt-F7 trick works on it, and overlay is
sent to it (so you can watch movies using xv on the external exit).
Jean-Louis Leroy has found a even better solution but that may not work
with xv (I have not tested it)
On Wed, 2004-06-09 at 09:27, Jean-Louis Leroy wrote:
>
> I'm in the same situation as you, it appears, and I didn't even know
> because I hadn't tried an external monitor yet.
>
> But here are some good news: I found out that if I kill X after
> switching to the external monitor, the image returns just there. Okay
> I loose my session in the process but it's still better than rebooting
> to XP isn't it?
---Beppe---
19 years, 11 months
