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

Bug#504196: marked as done (glibc: experimental upgrade breaks epiphany-browser)

Your message dated Sun, 26 Jul 2009 18:28:34 +0200
with message-id <20090726162834.GA29888@volta.aurel32.net>
and subject line Re: Bug#504196: glibc: experimental upgrade breaks epiphany-browser
has caused the Debian Bug report #504196,
regarding glibc: experimental upgrade breaks epiphany-browser
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
504196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504196
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: glibc
Version: 2.8+20080809-1
Severity: normal

I have no idea why, but upgrading to libc6 from experimental
on an otherwise mostly unstable system breaks epiphany-browser,
it will segfault right away at start.

So doing
sudo apt-get -t experimental install locales

(which will upgrade libc6 et al) will break epiphany, and you can fix it by
doing
sudo apt-get install libc6/unstable libc6-dbg/unstable libc6-dev/unstable
locales/unstable lib64gcc1/unstable  libc6-ppc64/unstable
g++-4.3-multilib/unstable g++-multilib/unstable gcc-4.3-multilib/unstable
gcc-multilib/unstable libc6-dev-ppc64/unstable

again.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: powerpc (ppc)

Kernel: Linux 2.6.28-rc2-wl-04239-gd80fe00-dirty (PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
On Tue, May 05, 2009 at 01:32:01AM +0200, Johannes Berg wrote:
> On Tue, 2009-05-05 at 01:24 +0200, Aurelien Jarno wrote:
> 
> > > Problem is that the backtrace is making no sense, it's crashing in
> > > libglib:
> > > 
> > > #0  0x0e8d1290 in waitpid () from /lib/libpthread.so.0
> > > #1  0x0e7a5630 in IA__g_spawn_sync (working_directory=<value optimized out>, 
> > >     argv=<value optimized out>, envp=0x0, flags=<value optimized out>, 
> > >     child_setup=<value optimized out>, user_data=<value optimized out>, 
> > >     standard_output=0x0, standard_error=0x0, exit_status=0x0, 
> > >     error=0xbf9e2818) at /build/buildd/glib2.0-2.18.2/glib/gspawn.c:382
> > > 
> > 
> > Is the problem still reproducible with glibc 2.9?
> 
> Can't say, I haven't used that laptop for months. It doesn't seem to be
> broken on amd64, but that probably isn't helpful.
> 

Ok, given no one reported the problem, I consider this bug has fixed. In
case you are able to reproduce it later with glibc version 2.9, I suggest
to reopen the bug.

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

--- End Message ---
Reply to: