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

Bug#304413: marked as done (libc6: last update broke StarOffice52)

Your message dated Mon, 5 Feb 2007 18:27:18 +0100
with message-id <20070205172718.GA24169@mad.intersec.eu>
and subject line Bug#304413: libc6: last update broke StarOffice52
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: libc6
Version: 2.3.2.ds1-20
Severity: critical
Justification: breaks unrelated software

hello,

well, SO5.2 is Debian-unrelated since there's no .deb for it, though it's
related since it needs libc6. Whatever, it got broken, hope the Justification
is ehm formally justified. 

I've been using SO 5.2 rather smoothly, till last update above, after which
I get:

...
(no debugging symbols found)
(no debugging symbols found)
[New Thread -1259529296 (LWP 6811)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1259529296 (LWP 6811)]
0xb567b9c1 in osl_releaseMutex () from /usr/opt/office52/program/libsal1.so
(gdb) bt
#0  0xb567b9c1 in osl_releaseMutex () from /usr/opt/office52/program/libsal1.so
#1  0xb567bbda in osl_releaseMutex () from /usr/opt/office52/program/libsal1.so
#2  0xb54edb63 in start_thread () from /lib/tls/libpthread.so.0
#3  0xb546ac4a in clone () from /lib/tls/libc.so.6
(gdb)

apt-get updated a number of .deb as usual, though I think libc6 is likely 
to blame. Tried and verified on 2 similar (Sarge) systems.
SO 5.2 still works fine on Slackware 10.1 (libc-2.3.4).

Any clue? should I roll back a previous libc6 version? or grab an up 
version from unstable?

thanks
-- paolo


-- System Information
Debian Release: 3.1
Architecture: i386
Kernel: Linux npp 2.6.11.6-ck1-bs-ss-pm.3 #1 Fri Apr 25 21:26:09 CEST 2005 i686
Locale: LANG=it_IT@euro, LC_CTYPE=it_IT@euro

Versions of packages libc6 depends on:
ii  libdb1-compat                 2.1.3-7    The Berkeley database routines [gl

--- End Message ---
--- Begin Message --- 
On Mon, Jul 04, 2005 at 10:46:28AM +0200, Paolo wrote:
> On Fri, Apr 15, 2005 at 09:16:43AM +0900, GOTO Masanori wrote:
> > At Wed, 13 Apr 2005 00:48:17 +0200,
> > Paolo wrote:
> > > well, SO5.2 is Debian-unrelated since there's no .deb for it, though it's
> > > related since it needs libc6. Whatever, it got broken, hope the Justification
> > > is ehm formally justified. 
> > > 
> > > I've been using SO 5.2 rather smoothly, till last update above, after which
> > > I get:
> > > 
> > > ...
> > > (no debugging symbols found)
> > > (no debugging symbols found)
> > > [New Thread -1259529296 (LWP 6811)]
> > > 
> > > Program received signal SIGSEGV, Segmentation fault.
> ...
> > but the invoked thread routine in SO 5.2 did not work.  It might be SO
> > 5.2 specific problem.
> 
> maybe, but got similiar ssegv in other programs in Sarge (just can't 
> remember as I didn't keep track)

  AFAICT there has been none other (at least the BTS has no recollection
of them) so it's definitely a SO5.2 problem.

  given that OOo now exists and supersedes SO, I think we can safely
close that bug.

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

Attachment: pgpHFcqHTG48P.pgp
Description: PGP signature


--- End Message ---
Reply to: