Bug#493202: Bug is still there

2008-09-12 Thread Kel Modderman
reopen 493202 found 493202 1.12.0-2 tags 493202 pending thanks On Friday 12 September 2008 17:16:11 Kel Modderman wrote: > On Friday 12 September 2008 16:11:10 Wouter Koolen-Wijkstra wrote: > > > > > I do have a script with no LSB header. > > It is called >

Bug#493202: Bug is still there

2008-09-12 Thread Kel Modderman
On Friday 12 September 2008 16:11:10 Wouter Koolen-Wijkstra wrote: > > I do have a script with no LSB header. > It is called > /etc/rcS.d/S06wouter-keys and contains > setkeycodes \ > e03b 59 \ > e008 60 \ > e007 61 \ > e03e 62 \ > e03f 63 \ > e040 64 \ > e04

Bug#493202: Bug is still there

2008-09-11 Thread Wouter Koolen-Wijkstra
Here is the output of valgrind: [EMAIL PROTECTED]:/tmp$ sudo valgrind --leak-check=full /sbin/insserv ==11673== Memcheck, a memory error detector. ==11673== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al. ==11673== Using LibVEX rev 1854, a library for dynamic binary translation. =

Bug#493202: Bug is still there

2008-09-08 Thread Petter Reinholdtsen
[Wouter Michiel Koolen-Wijkstra] > Hope that helps, It definitely help. I suspect the script=0x0 is the problem. Can you provide the output from running it under valgrind as well? I suspect your system have an init.d script with a broken LSB header. Can you try to run this script and attach the

Bug#493202: Bug is still there

2008-09-08 Thread Wouter Michiel Koolen-Wijkstra
Dear maintainer, I think I suffer from this bug as well. Insserv segfaults somewhere during the installation process of other packages. I built insserv from source as you described above. When I run insserv -v -n under gdb it gives the following backtrace: Program received signal SIGSEGV, S