Debian Bug report logs - #246288
getgrouplist causes segfaults when running NIS

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Fabian Wenzel <f.wenzel@gmx.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: dbus-1: dbus-daemon-1 segfaults

Date: Wed, 28 Apr 2004 11:08:52 +0200

Package: dbus-1
Version: 0.21-1
Severity: important

When starting dbus-daemon-1 --system, it segfaults. gdb gives the
following stack:

#0  0x401a6ad1 in _nss_compat_initgroups_dyn () from
/lib/tls/libnss_compat.so.2
#1  0x401a6645 in _nss_compat_initgroups_dyn () from
/lib/tls/libnss_compat.so.2
#2  0x6200003a in ?? ()
#3  0x00000000 in ?? ()
#4  0x32313100 in ?? ()
#5  0x0000003a in ?? ()
#6  0x00000000 in ?? ()
#7  0x00000000 in ?? ()
#8  0xbfffeaac in ?? ()
#9  0x40173192 in _dl_open () from /lib/tls/libc.so.6
Previous frame inner to this frame (corrupt stack?)

though I don't know if this gives relevant information (due to last line). The
error remains if dbus-1 is built from source on my system.



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.5
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (ignored: LC_ALL set to de_DE@euro)

Versions of packages dbus-1 depends on:
ii  adduser                     3.52         Add and remove users and groups
ii  libc6                       2.3.2.ds1-12 GNU C Library: Shared libraries an
ii  libexpat1                   1.95.6-8     XML parsing C library - runtime li

-- no debconf information

Message #10 received at 246288@bugs.debian.org (full text, mbox, reply):

From: sjoerd@spring.luon.net (Sjoerd Simons)

To: Fabian Wenzel <f.wenzel@gmx.net>

Cc: 246288@bugs.debian.org

Subject: Re: dbus-1: dbus-daemon-1 segfaults

Date: Thu, 4 Nov 2004 10:59:11 +0100

On Wed, Apr 28, 2004 at 11:08:52AM +0200, Fabian Wenzel wrote:
> Package: dbus-1
> Version: 0.21-1
> Severity: important
> 
> When starting dbus-daemon-1 --system, it segfaults. gdb gives the
> following stack:

Does this bug still occur with the 0.22 packages ?

  Sjoerd
-- 
Reality is for people who lack imagination.

Message #15 received at 246288@bugs.debian.org (full text, mbox, reply):

From: "Tom Parker" <palfrey@tevp.net>

To: 246288@bugs.debian.org

Subject: Dbus segfault

Date: Mon, 20 Dec 2004 16:02:08 +0000 (GMT)

I'm still seeing a remarkably similar trace with the 0.22-3 package, see
below...

#0  0xb7e745e8 in _nss_compat_initgroups_dyn () from
/lib/tls/i686/cmov/libnss_compat.so.2
#1  0xb7e741d6 in _nss_compat_initgroups_dyn () from
/lib/tls/i686/cmov/libnss_compat.so.2
#2  0xb7e73bf7 in _nss_compat_initgroups_dyn () from
/lib/tls/i686/cmov/libnss_compat.so.2
#3  0xb7f1c134 in initgroups () from /lib/tls/i686/cmov/libc.so.6
#4  0xb7f1bf43 in getgrouplist () from /lib/tls/i686/cmov/libc.so.6
#5  0x080757bc in _dbus_watch_unref ()
#6  0x08075a15 in _dbus_watch_unref ()
#7  0x080779e1 in _dbus_watch_unref ()
#8  0x080784b5 in _dbus_watch_unref ()
#9  0x08077d06 in _dbus_watch_unref ()
#10 0x08077e99 in _dbus_watch_unref ()
#11 0x08078154 in _dbus_watch_unref ()
#12 0x08077f76 in _dbus_watch_unref ()
#13 0x0804df91 in ?? ()
#14 0xbfffd890 in ?? ()
#15 0x0809685c in ?? ()
#16 0x08096678 in ?? ()
#17 0x08095318 in ?? ()
#18 0xbfffdbd0 in ?? ()
#19 0x08081e39 in _IO_stdin_used ()
#20 0xbfffd860 in ?? ()
#21 0x0808200b in _IO_stdin_used ()
#22 0xbfffd864 in ?? ()
#23 0x08081e33 in _IO_stdin_used ()
#24 0xbfffd868 in ?? ()
#25 0x00000000 in ?? ()
#26 0x08095270 in ?? ()
#27 0x08094da8 in ?? ()
#28 0xbfffd878 in ?? ()
#29 0x08096850 in ?? ()
#30 0x08094840 in ?? ()
#31 0x08094898 in ?? ()
#32 0xbfffd878 in ?? ()
#33 0xb7fca309 in XML_GetFeatureList () from /usr/lib/libexpat.so.1
#34 0x080590ac in ?? ()
#35 0x08095298 in ?? ()
#36 0x08096700 in ?? ()
#37 0x08096678 in ?? ()
#38 0x08095318 in ?? ()
#39 0xbfffdbd0 in ?? ()
#40 0xb7fa7620 in __after_morecore_hook () from
/lib/tls/i686/cmov/libc.so.6
#41 0x00000002 in ?? ()
#42 0x08094898 in ?? ()
#43 0x08095318 in ?? ()
#44 0x08096678 in ?? ()
#45 0x08096700 in ?? ()
#46 0xb7fde6e4 in ?? () from /usr/lib/libexpat.so.1

Message #20 received at 246288@bugs.debian.org (full text, mbox, reply):

From: sjoerd@spring.luon.net (Sjoerd Simons)

To: Tom Parker <palfrey@tevp.net>, 246288@bugs.debian.org

Subject: Re: Bug#246288: Dbus segfault

Date: Tue, 21 Dec 2004 21:12:21 +0100

On Mon, Dec 20, 2004 at 04:02:08PM +0000, Tom Parker wrote:
> 
> I'm still seeing a remarkably similar trace with the 0.22-3 package, see
> below...

Can your run the deamon with verbose turned on ? To do this you have to comment
<fork/> in /etc/dbus-1/system.conf and run:  
DBUS_VERBOSE=1 /usr/bin/dbus-daemon-1 --config-file=/etc/dbus-1/system.conf

  Sjoerd
-- 
We are sorry.  We cannot complete your call as dialed.  Please check
the number and dial again or ask your operator for assistance.

This is a recording.

Message #25 received at 246288@bugs.debian.org (full text, mbox, reply):

From: Stef Epardaud <stef@inforealm.org>

To: 246288@bugs.debian.org

Subject: Getting a very similar segfault here

Date: Sun, 16 Jan 2005 14:33:18 +0100

Hi,

I'm getting a segfault too, rendering dbus useless. Any time a client
connects to it, it segfaults. I didn't manage to get a core dump even
when starting it myself with 'ulimit -c unlimited'.
However I've got some info. When I run the command 
 DBUS_VERBOSE=1 dbus-daemon-1 --system --nofork
I get this output:

9151: Allocated slot 0 on allocator 0x8090628 total 1 slots allocated 1 used
9151: No cache for UID 0
9151: No cache for UID 4294967295
9151: Using cache for UID 4294967295 information
9151: listening on unix socket /var/run/dbus/system_bus_socket abstract=0
9151: Initialized server on address unix:path=/var/run/dbus/system_bus_socket
9151: Adding a read watch on fd 3 using newly-set add watch function
9151: Allocated slot 0 on allocator 0x80905dc total 1 slots allocated 1 used
9151: No cache for UID 4294967295
9151: full-duplex pipe 4 <-> 5
9151: We are on D-Bus...
9151: Running main loop, depth 0 -> 1

Then it waits, and if I try a connection to it by calling hal-device-manager
it goes on like this:

9151: Handling client connection, flags 0x1
9151: Creating new client connection with fd 6
9151: check_read_watch: fd = 6
9151:   setting read watch enabled = 1
9151: check_write_watch(): needed = 0 on connection 0x809bab0 watch 0x809be00 fd = 6 outgoing messages exist 0
9151: Adding a write watch on fd 6 using newly-set add watch function
9151: Adding a read watch on fd 6 using newly-set add watch function
9151: dispatch status = complete is_connected = 1
9151: Connection 0x809bab0 authentication expires in 29999 milliseconds
9151: Enabled expire timeout with interval 29999
9151: Running expire_incomplete_timeout
9151: Connection 0x809bab0 authentication expires in 29999 milliseconds
9151: Enabled expire timeout with interval 29999
9151: handling read watch 0x80942e8 flags = 1
9151: read credentials byte
9151: Credentials:  pid 9195  uid 1000  gid 1000
9151:  server auth state: waiting for input
9151: check_read_watch: fd = 6
9151:   setting read watch enabled = 1
9151: check_write_watch(): needed = 0 on connection 0x809bab0 watch 0x809be00 fd = 6 outgoing messages exist 0
9151: do_reading: fd = 6
9151: dispatch status = complete is_connected = 1
9151: handling read watch 0x80942e8 flags = 1
9151:  server auth state: waiting for input
9151:  read 24 bytes in auth phase
9151: server: got command "AUTH EXTERNAL 31303030"
9151: server: Trying mechanism EXTERNAL
9151: server: data: '1000'
9151: server: going from state WaitingForAuth to state WaitingForBegin
9151: server: authenticated client with UID 1000 matching socket credentials UID 1000
9151:  server auth state: bytes to send
9151: check_read_watch: fd = 6
9151:   setting read watch enabled = 0
9151: check_write_watch(): needed = 1 on connection 0x809bab0 watch 0x809be00 fd = 6 outgoing messages exist 0
9151: do_reading: fd = 6
9151: dispatch status = complete is_connected = 1
9151: handling write watch, have_outgoing_messages = 0
9151:  server auth state: bytes to send
9151: server: Sent 4 bytes of: OK

9151:  server auth state: waiting for input
9151: check_read_watch: fd = 6
9151:   setting read watch enabled = 1
9151: check_write_watch(): needed = 0 on connection 0x809bab0 watch 0x809be00 fd = 6 outgoing messages exist 0
9151: Not authenticated, not writing anything
9151: check_write_watch(): needed = 0 on connection 0x809bab0 watch 0x809be00 fd = 6 outgoing messages exist 0
9151: dispatch status = complete is_connected = 1
9151: handling read watch 0x80942e8 flags = 1
9151:  server auth state: waiting for input
9151:  read 7 bytes in auth phase
9151: server: got command "BEGIN"
9151: server: going from state WaitingForBegin to state Authenticated
9151: No cache for UID 1000
Segmentation fault

And there it dies.
If I try an strace around it, I get some calls to NIS (my system is a yp 
client) that fail like:

socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 8
bind(8, {sa_family=AF_INET, sin_port=htons(918), sin_addr=inet_addr("0.0.0.0")}, 16) = -1 EACCES (Permission denied)
connect(8, {sa_family=AF_INET, sin_port=htons(893), sin_addr=inet_addr("192.168.14.1")}, 16) = 0
write(8, "\200\0\0LIw\366\200\0\0\0\0\0\0\0\2\0\1\206\244\0\0\0\2"..., 80) = 80
poll([{fd=8, events=POLLIN, revents=POLLIN}], 1, 25000) = 1
read(8, "\200\0\10\\Iw\366\200\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4000) = 2144
close(8)                                = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

Somehow I'm not sure why it would bind a socket locally before connecting 
it to the NIS server, but I'm not sure whether this is wrong or even related
to the segfault.

I'm running the latest debian unstable with dbus 0.23.

Please tell me if I should report this upstream or how to get more info 
from my breakage, it's very frustrating.

Thanks.
-- 
Stéphane Epardaud

Message #30 received at 246288@bugs.debian.org (full text, mbox, reply):

From: sjoerd@spring.luon.net (Sjoerd Simons)

To: Stef Epardaud <stef@inforealm.org>, 246288@bugs.debian.org

Subject: Re: Bug#246288: Getting a very similar segfault here

Date: Sun, 16 Jan 2005 19:03:30 +0100

On Sun, Jan 16, 2005 at 02:33:18PM +0100, Stef Epardaud wrote:
> socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 8
> bind(8, {sa_family=AF_INET, sin_port=htons(918), sin_addr=inet_addr("0.0.0.0")}, 16) = -1 EACCES (Permission denied)
> connect(8, {sa_family=AF_INET, sin_port=htons(893), sin_addr=inet_addr("192.168.14.1")}, 16) = 0
> write(8, "\200\0\0LIw\366\200\0\0\0\0\0\0\0\2\0\1\206\244\0\0\0\2"..., 80) = 80
> poll([{fd=8, events=POLLIN, revents=POLLIN}], 1, 25000) = 1
> read(8, "\200\0\10\\Iw\366\200\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4000) = 2144
> close(8)                                = 0
> --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> +++ killed by SIGSEGV +++
> 
> Somehow I'm not sure why it would bind a socket locally before connecting 
> it to the NIS server, but I'm not sure whether this is wrong or even related
> to the segfault.

The socket opening stuff is something your nisbindings do, not a dbus thing.
Could you trace the daemon with ltrace and provide the last part of the output.

It's probably something that's being triggered by the fact your using nis for
authentication.. Makes me wonder what the other reporters are using for
authentitcation.
  
> I'm running the latest debian unstable with dbus 0.23.
> 
> Please tell me if I should report this upstream or how to get more info 
> from my breakage, it's very frustrating.

Your the first to give someusefull feedback :) Getting no feedback is also very
frustrating..

  Sjoerd
-- 
Wonder is the feeling of a philosopher, and philosophy begins in wonder.
		-- Socrates, quoting Plato
	[Huh?  That's like Johnson quoting Boswell]

Message #35 received at 246288@bugs.debian.org (full text, mbox, reply):

From: Stef Epardaud <stef@epardaud.net>

To: Sjoerd Simons <sjoerd@spring.luon.net>

Cc: 246288@bugs.debian.org

Subject: Re: Bug#246288: Getting a very similar segfault here

Date: Sun, 16 Jan 2005 22:02:49 +0100

On Sun, Jan 16, 2005 at 07:03:30PM +0100, Sjoerd Simons wrote:
> The socket opening stuff is something your nisbindings do, not a dbus thing.
> Could you trace the daemon with ltrace and provide the last part of the output.

Ok, thanks for the quick reply, here goes:

memmove(0x809bc9d, 0x809bc98, 0, 0x80903d0, 0)   = 0x809bc9d
memcpy(0x809bc98, "BEGIN", 5)                    = 0x809bc98
memmove(0x8091360, 0x8091365, 2, 0x80903d0, 0x809ba00) = 0x8091360
memmove(0x8091360, 0x8091362, 0, 0x80903d0, 0x809ba00) = 0x8091360
free(0x8093cf8)                                  = <void>
free(0x809bc98)                                  = <void>
calloc(24, 1)                                    = 0x8093c38
getpwuid(1000, 0xb7f9f620, 1, 0xbfffed18, 0xb7ee0014) = 0xb7f9fe9c
strlen("stephane")                               = 8
malloc(9)                                        = 0x8093cf8
memcpy(0x8093cf8, "stephane", 9)                 = 0x8093cf8
strlen("/home/stephane")                         = 14
malloc(15)                                       = 0x809bc98
memcpy(0x809bc98, "/home/stephane", 15)          = 0x809bc98
malloc(68)                                       = 0x8094310
getgrouplist(0x8093cf8, 1000, 0x8094310, 0xbfffed08, 0xb7ee0014 <unfinished ...>
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++

that's the last part, if you want what's before (and there's quite a few), 
do tell :)

> Your the first to give someusefull feedback :) Getting no feedback is also very
> frustrating..

Oh don't worry I'll give you all the info I can, thanks a lot for the help!
-- 
Stéphane Epardaud

Message #40 received at 246288@bugs.debian.org (full text, mbox, reply):

From: Sjoerd Simons <sjoerd@spring.luon.net>

To: Stef Epardaud <stef@epardaud.net>, 246288@bugs.debian.org

Subject: Re: Bug#246288: Getting a very similar segfault here

Date: Sun, 16 Jan 2005 22:36:30 +0100

[Message part 1 (text/plain, inline)]

On Sun, Jan 16, 2005 at 10:02:49PM +0100, Stef Epardaud wrote:
> On Sun, Jan 16, 2005 at 07:03:30PM +0100, Sjoerd Simons wrote:
> > The socket opening stuff is something your nisbindings do, not a dbus thing.
> > Could you trace the daemon with ltrace and provide the last part of the output.
> 
> Ok, thanks for the quick reply, here goes:
> 
> memmove(0x809bc9d, 0x809bc98, 0, 0x80903d0, 0)   = 0x809bc9d
> memcpy(0x809bc98, "BEGIN", 5)                    = 0x809bc98
> memmove(0x8091360, 0x8091365, 2, 0x80903d0, 0x809ba00) = 0x8091360
> memmove(0x8091360, 0x8091362, 0, 0x80903d0, 0x809ba00) = 0x8091360
> free(0x8093cf8)                                  = <void>
> free(0x809bc98)                                  = <void>
> calloc(24, 1)                                    = 0x8093c38
> getpwuid(1000, 0xb7f9f620, 1, 0xbfffed18, 0xb7ee0014) = 0xb7f9fe9c
> strlen("stephane")                               = 8
> malloc(9)                                        = 0x8093cf8
> memcpy(0x8093cf8, "stephane", 9)                 = 0x8093cf8
> strlen("/home/stephane")                         = 14
> malloc(15)                                       = 0x809bc98
> memcpy(0x809bc98, "/home/stephane", 15)          = 0x809bc98
> malloc(68)                                       = 0x8094310
> getgrouplist(0x8093cf8, 1000, 0x8094310, 0xbfffed08, 0xb7ee0014 <unfinished ...>
> --- SIGSEGV (Segmentation fault) ---
> +++ killed by SIGSEGV +++
> 
> that's the last part, if you want what's before (and there's quite a few), 
> do tell :)

Hrm, it crashes inside the getgrouplist call, odd.. 
> 
> > Your the first to give someusefull feedback :) Getting no feedback is also
> > very frustrating..
> 
> Oh don't worry I'll give you all the info I can, thanks a lot for the help!

Cool.. Could you try to run the attached program as user messagebus (or as your
normal user, should have the same result)

  Sjoerd
-- 
An anthropologist at Tulane has just come back from a field trip to New
Guinea with reports of a tribe so primitive that they have Tide but not
new Tide with lemon-fresh Borax.
		-- David Letterman

[test.c (text/x-csrc, attachment)]

Message #45 received at 246288@bugs.debian.org (full text, mbox, reply):

From: "Tom Parker" <palfrey@tevp.net>

To: sjoerd@spring.luon.net, 246288@bugs.debian.org

Subject: Re: Bug#246288: Dbus segfault

Date: Wed, 19 Jan 2005 17:45:10 +0000 (GMT)

On 12/21/2004, "(Sjoerd Simons)" <sjoerd@spring.luon.net> wrote:
>Can your run the deamon with verbose turned on ? To do this you have to comment
><fork/> in /etc/dbus-1/system.conf and run:
>DBUS_VERBOSE=1 /usr/bin/dbus-daemon-1 --config-file=/etc/dbus-1/system.conf

Results was as follows:

As root(assuming this would be necessary), I got:
26526: Allocated slot 0 on allocator 0x808f90c total 1 slots allocated 1
used
26526: No cache for UID 0
zsh: segmentation fault  DBUS_VERBOSE=1 /usr/bin/dbus-daemon-1
--config-file=/etc/dbus-1/system.conf

As my standard user I got:
26497: Allocated slot 0 on allocator 0x808f90c total 1 slots allocated 1
used
26497: No cache for UID 3017
26497: No cache for UID 4294967295
zsh: segmentation fault (core dumped)  DBUS_VERBOSE=1
/usr/bin/dbus-daemon-1 --config-file=/etc/dbus-1/system.conf

Message #50 received at 246288@bugs.debian.org (full text, mbox, reply):

From: Sjoerd Simons <sjoerd@spring.luon.net>

To: Tom Parker <palfrey@tevp.net>

Cc: 246288@bugs.debian.org

Subject: Re: Bug#246288: Dbus segfault

Date: Wed, 19 Jan 2005 19:53:37 +0100

On Wed, Jan 19, 2005 at 05:45:10PM +0000, Tom Parker wrote:
> 
> On 12/21/2004, "(Sjoerd Simons)" <sjoerd@spring.luon.net> wrote:
> >Can your run the deamon with verbose turned on ? To do this you have to comment
> ><fork/> in /etc/dbus-1/system.conf and run:
> >DBUS_VERBOSE=1 /usr/bin/dbus-daemon-1 --config-file=/etc/dbus-1/system.conf
> 
> Results was as follows:
> 
> As root(assuming this would be necessary), I got:
> 26526: Allocated slot 0 on allocator 0x808f90c total 1 slots allocated 1
> used
> 26526: No cache for UID 0
> zsh: segmentation fault  DBUS_VERBOSE=1 /usr/bin/dbus-daemon-1
> --config-file=/etc/dbus-1/system.conf
> 
> As my standard user I got:
> 26497: Allocated slot 0 on allocator 0x808f90c total 1 slots allocated 1
> used
> 26497: No cache for UID 3017
> 26497: No cache for UID 4294967295
> zsh: segmentation fault (core dumped)  DBUS_VERBOSE=1
> /usr/bin/dbus-daemon-1 --config-file=/etc/dbus-1/system.conf

Are you also running NIS like Stef ? And could you try the testprogram i send
to him ? (Should be available in the bts)

  Sjoerd
-- 
Algebraic symbols are used when you do not know what you are talking about.
		-- Philippe Schnoebelen

Message #55 received at 246288@bugs.debian.org (full text, mbox, reply):

From: Stef Epardaud <stef@epardaud.net>

To: Sjoerd Simons <sjoerd@spring.luon.net>

Cc: 246288@bugs.debian.org

Subject: Re: Bug#246288: Getting a very similar segfault here

Date: Wed, 19 Jan 2005 21:57:00 +0100

Hi.

I could not run that program due to a segfault in the call to
getgrouplist. After googling a little, I changed the 'compat' settings
in /etc/nsswitch.conf to 'files nis' and all went well. Now dbus is up
and running (and I gotta figure out how to make it do what I want, but
that's anothing thing ;)

Thanks a lot for your help. I'll probably try to forward this bug to the
debian libc6 package.
-- 
Stéphane Epardaud

Message #60 received at 246288@bugs.debian.org (full text, mbox, reply):

From: Sjoerd Simons <sjoerd@spring.luon.net>

To: Stef Epardaud <stef@epardaud.net>, 246288@bugs.debian.org

Cc: control@bugs.debian.org

Subject: Re: Bug#246288: Getting a very similar segfault here

Date: Wed, 19 Jan 2005 22:59:30 +0100

reassign 246288 libc6
retitle 246288 getgrouplist causes segfaults when running NIS 
merge 226515 246288 
thanks, 

On Wed, Jan 19, 2005 at 09:57:00PM +0100, Stef Epardaud wrote:
> Hi.
> 
> I could not run that program due to a segfault in the call to
> getgrouplist. After googling a little, I changed the 'compat' settings
> in /etc/nsswitch.conf to 'files nis' and all went well. Now dbus is up
> and running (and I gotta figure out how to make it do what I want, but
> that's anothing thing ;)

The segv proves that the getgrouplist call is buggy here and not something else
in dbus..
> 
> Thanks a lot for your help. I'll probably try to forward this bug to the
> debian libc6 package.

Reassigning

  Sjoerd

-- 
"Protozoa are small, and bacteria are small, but viruses are smaller
than the both put together."

Message #77 received at 246288@bugs.debian.org (full text, mbox, reply):

From: GOTO Masanori <gotom@debian.or.jp>

To: 226515@bugs.debian.org, 246288@bugs.debian.org, 305316@bugs.debian.org, 314480@bugs.debian.org, 316914@bugs.debian.org, 226515-submitter@bugs.debian.org, 246288-submitter@bugs.debian.org, 305316-submitter@bugs.debian.org, 314480-submitter@bugs.debian.org, 316914-submitter@bugs.debian.org, stef@inforealm.org, palfrey@tevp.net, mace@darksilence.net, malte@cornils.net, todd.goyen@swri.org, sjoerd@spring.luon.net

Subject: Re: dbus-1 does not start because of segmentation fault

Date: Wed, 17 Aug 2005 12:43:36 +0900

Hi,

These bugs are marked as important when glibc 2.3.2.ds1 is used in
sarge.  Nowadays we have new glibc 2.3.5-3 in unstable.  Could you
test dbus-1 with new glibc?  I guess this problem is already fixed.

Regards,
-- gotom

Send a report that this bug log contains spam.