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
Hi,
Could you please retry with glibc 2.5 to see if the problem is fixed?
It is available in experimental.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' [EMAIL PROTECTED] | [EMAIL PROTECTED]
`-
On Sun, Jul 30, 2006, Yves Lambert wrote:
sorry Loïc but Mozilla keeps on sending 8bit data in headers and
bugs.debian.org don't like it. With qp line it should be good...
Could you please install libc6-dbg and update the backtrace?
(FYI, you're running experimental libc6, so you need
Loïc Minier a écrit :
Could you please install libc6-dbg and update the backtrace?
(FYI, you're running experimental libc6, so you need libc6-dbg from
experimental as well.)
I am downgrading libc6.
Could you confirm this does not happen with the libc6 from unstable?
Nope. Totem
On Sun, Jul 30, 2006, Yves Lambert wrote:
I've uninstalled libc6-i686 and I've upgraded again libc6 and libc6-dbg
to experimental- no crash, no error
- You can close the bug as invalid (I don't know *why* I installed
libc6-i686 !!!)
What is your machine? If it's a K7,
Loïc Minier a écrit :
What is your machine? If it's a K7, libc6-686/experimental should
work.
It is an athlon and it actually does not work. If you are sure of that,
wouldn't it be a good idea to close this bug and open one against
libc6-686 with a basic test case ?
I can build a system
severity 380086 serious
reassign 380086 libc6-i686 2.3.999.2-8
# just in case
tags 380086 + experimental
stop
Hi,
On Sun, Jul 30, 2006, Yves Lambert wrote:
What is your machine? If it's a K7, libc6-686/experimental should
work.
It is an athlon and it actually does not work.
[...]
tags #380086 + unreproducible
severity 380086 important
retitle #380086 gconv_db.c:232: __gconv_release_step: assertion step-__end_fct
== ((void *)0 failed
stop
Hi,
On Thu, Jul 27, 2006, Yves Jean Marie Lambert wrote:
stderr output:
totem: gconv_db.c:232: __gconv_release_step:
Loïc Minier a écrit :
Hi,
sorry Loïc but Mozilla keeps on sending 8bit data in headers and
bugs.debian.org don't like it. With qp line it should be good...
Could you please try launching totem-xine from a terminal with:
LC_ALL=C totem?
Thank you for the tip...
~$ LC_ALL=C totem
totem:
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 ==
10 matches
Mail list logo
