[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#210669: other apps also break



On Sat, Jul 03, 2004 at 12:50:08PM +0900, GOTO Masanori wrote:
> At Fri, 12 Sep 2003 13:05:59 -0700,
> John Wong wrote:
> > cmdlinkespeak worked fine with libc6-2.3.1-17.  It started seg faulting with
> > 2.3.2 (frist version tried was 2.3.2-2).  cmdlinespeak still seg faults
> > with 2.3.2-6.  When I attempt to keep the system at libc6-2.3.1-17, apt
> > breaks as well as perl and others.
> 
> If glibc breaks many other apps, then the system becomes unusable.  I
> wonder it's related with cmdlinkespeak.

The problem does appear to be with cmdlinespeak.  Unfortunately, it
(ViaVoice) was a binary only release from IBM which does not look to be 
availble for Linux anymore.

> > This problem is also brought up in with RedHat:
> > 
> > http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=98768
> 
> This bugzilla has been closed without glibc problem.

I believe it was a change in glibc which brought cmdlinespeak's
brokeness to light.

> At Sat, 27 Sep 2003 04:39:53 -0400,
> Andrew K. Bressen wrote:
> > I'm running an x86 debian system, mostly woody with a few sarge packages.
> > The transition from libc6 and locales 2.3.1-16 to 2.3.2-7 broke 
> > non-debian stuff for me too; I had to back it out. 
> > 
> > Among the affected apps were compupic (v5.1 build 1063), 
> > netrek (Paradise Client 2000rc2) and unison (static textui 2.9.1). 
> > 
> > All are static compiles, and strace seemed to indicate
> > things were breaking at or just after nss stuff; 
> > a strace of compupic follows...
> > 
> > I have a system that I could roll the change back into temporarily 
> > if further testing is desired. 
> 
> We have 2.3.2.ds1-13.  It's upper version of 2.3.2.  However, NSS code
> was changed in 2.3.2.ds1-1 and many static linked application was
> broken.  We can't fix this problem.  If you want to use such
> applications, please use LD_LIBRARY_PATH environment variable to point
> to the old glibc 2.3.1 extracted directory.
> 
> I think there's no bug in glibc.  The workaround LD_LIBRARY_PATH
> should avoid your problem.  If you have no objection, I'll close this
> bug.

I can't test this solution now since the sarge system was rolled back to
woody with a reinstall.

John

> Regards,
> -- gotom
> 
> 



Reply to: