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

Bug#380086: marked as done (gconv_db.c:232: __gconv_release_step: assertion step->__end_fct == ((void *)0 failed)

Your message dated Mon, 5 Feb 2007 05:35:27 +0100
with message-id <20070205043525.GA27241@volta.aurel32.net>
and subject line totem (totem-xine) crashes always on launch wth an error:
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: totem
Version: 1.4.3-1
Severity: grave
Justification: renders package unusable

stderr output:
totem: gconv_db.c:232: __gconv_release_step:  l'assertion «
step->__end_fct == ((void *)0) » a échoué.
(dirty translation: totem: gconv_db.c:232: __gconv_release_step:
assertion "step->__end_fct == ((void *)0)" failed.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-k7
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)

Versions of packages totem depends on:
ii  totem-xine                    1.4.3-1    A simple media player for the Gnom

totem recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 2.5-0exp3

On Fri, Jan 26, 2007 at 10:24:13AM +0100, Yves Lambert wrote:
> Aurelien Jarno wrote:
> >Hi,
> >
> >Could you please retry with glibc 2.5 to see if the problem is fixed?
> >It is available in experimental.
> >  
> This works for me.
> afair the problem seemed to be related   to libc6-i686 - which is 
> expected to be optimized for AMD architecture too. I am shipping 
> libc6-i686 2.5-0exp3 and glibc/libc6 2.5-0exp3. Totem works fine.
> I experienced another probably reproducible totem crash but this one is 
> most probably not due to glibc but totem iself.
> 
> I blame myself not to have provided a basic test and not to have  
> reported before that it worked  for me since 2.5.0 first or second 
> experimental package.
> 

Thanks for your answer, I guess the bug can be closed now.

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

--- End Message ---
Reply to: