d on the gdb
trace I sent?
Best,
Jan
--
+---------+
| Jan Oberländer|
| PGP key: 0xC4D910E3 |
+-+
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi,
On Thu, Nov 17, 2011 at 11:24:24AM +0100, Michel Dänzer wrote:
> Can you try if the patch below fixes this crash?
Sorry for the late reply, I've been out of town. I'll see if I can try
your patch this weekend.
Best,
Jan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.
Hello again,
I suppose it's a good thing this bug reproduces so well. :) Here's a
better backtrace.
-- gdb output:
Program received signal SIGABRT, Aborted.
0xb75d3424 in __kernel_vsyscall ()
(gdb) bt full
#0 0xb75d3424 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb72a4911 in *
Hi,
I've observed the same problem in my installation. Changing
/usr/share/sympa/db/install-pg-db so that the sympa user has createdb
rights doesn't help. The problem seems to be that the database gets
created by one of the installation scripts, and create_db.Pg tries to
create the database agai
4 matches
Mail list logo
