Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-08-18 Thread Willian Gustavo Veiga
I can confirm what Emmanuel Fleury said. Using the lines above I can run Icedove. Thank you. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-05-09 Thread Jonathan Nieder
tags 617759 - moreinfo quit Jonathan Nieder wrote: $ icedove; echo $? /usr/lib/icedove/icedove-bin: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc 127 I tried reproducing this with upstream glibc. I'm way too lazy to rebuild icedove in a

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-05-09 Thread Jonathan Nieder
Jonathan Nieder wrote: * This class is not threadsafe and is intented for use only on the main * thread. */ Maybe the warning is relevant? But this does not feel like a race (especially with a narrow window like that between the following if and return) if

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-05-09 Thread Aurelien Jarno
Le 09/05/2011 13:56, Jonathan Nieder a écrit : tags 617759 - moreinfo quit Jonathan Nieder wrote: $ icedove; echo $? /usr/lib/icedove/icedove-bin: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc 127 I tried reproducing this with

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-05-05 Thread Jonathan Nieder
severity 617759 important tags 617759 + moreinfo quit Jonathan Nieder wrote: Typical experimental system. Not reproducible on sid. Tagging moreinfo until it is clear how to reproduce (hopefully upgrading the test vm to experimental will do the trick, so that the hunt for the specific

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-05-04 Thread Jonathan Nieder
Jonathan Nieder wrote: $ icedove; echo $? /usr/lib/icedove/icedove-bin: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc 127 Backtrace: #0 _dl_signal_cerror (errcode=0, objname=0x7fffe6e70640 /usr/lib/icedove/components/libdbusservice.so,

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-04-14 Thread Jonathan Nieder
Hi again, On Mon, Apr 04, 2011 at 05:53:29AM -0500, Jonathan Nieder wrote: Jonathan Nieder wrote: Yes! With libc6 2.11.2-13 from sid, icedove loads without trouble. Hmm, on second thought, it works again when I upgrade to experimental, just as you hinted. Hmm, so here's the latest

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-04-04 Thread Jonathan Nieder
reassign 617759 libc6 2.13-0exp5 quit Hi, Christoph Goehre wrote: On Fr, Apr 01, 2011 at 06:07:35 -0500, Jonathan Nieder wrote: $ dpkg-query -W libc6 libc62.13-0exp5 ^^ I've tried to reproduce your bug. And I succeeded with libc6 from experimental one time.

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-04-04 Thread Jonathan Nieder
Jonathan Nieder wrote: Christoph Goehre wrote: Could you try to run 'ldconfig' or downgrade to libc6 from unstable and test Icedove again? Yes! With libc6 2.11.2-13 from sid, icedove loads without trouble. Hmm, on second thought, it works again when I upgrade to experimental, just as you

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-04-04 Thread Aurelien Jarno
On Mon, Apr 04, 2011 at 05:53:29AM -0500, Jonathan Nieder wrote: Jonathan Nieder wrote: Christoph Goehre wrote: Could you try to run 'ldconfig' or downgrade to libc6 from unstable and test Icedove again? Yes! With libc6 2.11.2-13 from sid, icedove loads without trouble. Hmm, on

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-04-04 Thread Jonathan Nieder
Aurelien Jarno wrote: I have to say I don't have a lot of idea there. Maybe a prelink issue? Are you using prelink? No, not that I'm aware of. Yesterday I ran cupt full-upgrade so now icedove is at version 3.1.9-2. Today's experiments, omitting package manager output: $ dpkg-query -W

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-04-03 Thread Christoph Goehre
Hi, On Fr, Apr 01, 2011 at 06:07:35 -0500, Jonathan Nieder wrote: $ dpkg-query -W libc6 libc6 2.13-0exp5 ^^ I've tried to reproduce your bug. And I succeeded with libc6 from experimental one time. Could you try to run 'ldconfig' or downgrade to libc6 from unstable and test Icedove

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-04-01 Thread Christoph Goehre
Hi, some more things to try: $ LD_DEBUG=symbols icedove and $ ls -l /lib/ld-linux.so.2 /lib64/ld-linux-x86-64.so.2 LD_DEBUG will generate lot of output, but we need all of this. On Mi, Mär 23, 2011 at 03:53:27 -0500, Jonathan Nieder wrote: Did this happen after an update or is this a

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-03-29 Thread Jonathan Nieder
# Guido Günther wrote: # # Did this happen after an update or is this a fresh install? # # Being curious, I tried the squeeze and sid versions. found 617759 icedove/3.0.11-2 icedove/3.0.11-1+squeeze1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-03-23 Thread Guido Günther
Hi Jonathan, On Fri, Mar 11, 2011 at 01:28:33AM -0600, Jonathan Nieder wrote: Package: icedove Version: 3.1.9-1 Severity: grave Hi, Typical experimental system. Trying to run icedove, I get $ icedove; echo $? /usr/lib/icedove/icedove-bin: symbol lookup error:

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-03-23 Thread Jonathan Nieder
Hi Guido, Guido Günther wrote: $ readelf -a /usr/lib/icedove/libxpcom.so | grep NS_Alloc 002035b8 00030001 R_X86_64_64 NS_Alloc_P + 0 00203880 00030007 R_X86_64_JUMP_SLO NS_Alloc_P + 0 3: 0 FUNCGLOBAL

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-03-11 Thread Christoph Goehre
Hi, On Fri, Mar 11, 2011 at 01:28:33AM -0600, Jonathan Nieder wrote: Typical experimental system. Trying to run icedove, I get $ icedove; echo $? /usr/lib/icedove/icedove-bin: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc 127 I have

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-03-11 Thread Jonathan Nieder
Christoph Goehre wrote: On Fri, Mar 11, 2011 at 01:28:33AM -0600, Jonathan Nieder wrote: $ icedove; echo $? /usr/lib/icedove/icedove-bin: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc 127 I have no plugins installed. Any hints for

Bug#617759: icedove: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

2011-03-10 Thread Jonathan Nieder
Package: icedove Version: 3.1.9-1 Severity: grave Hi, Typical experimental system. Trying to run icedove, I get $ icedove; echo $? /usr/lib/icedove/icedove-bin: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc 127 I have no plugins installed.