Bus error when trying to install

I'm unable to replicate this. Given that you are getting a Bus error, I suspect you have a problem unrelated to amavisd-new.

Please try:

less /etc/passwd|grep amavis

If that produces no output, please try:

sudo adduser amavis --system --group --home "/var/lib/amavis"
sudo chown amavis:amavis /var/lib/amavis

Please report back any output you get from those commands.

The command gives:
amavis:x:107:115:AMaViS system user,,,:/var/lib/amavis:/bin/sh

OK. Then the user creation succeeded.

How about sudo sh /etc/init.d/amavis start? What does that produce?

As regular user:
sh /etc/init.d/amavis start
Starting amavisd: chown: changing ownership of `/var/run/amavis': Operation not permitted

As sudo:
rpr@homeserver:~$ sudo sh /etc/init.d/amavis start
[sudo] password for rpr:
Starting amavisd: Bus error
(failed).

Btw my sources.list are:
rpr@homeserver:~$ sudo cat /etc/apt/sources.list
deb http://be.archive.ubuntu.com/ubuntu/ gutsy main restricted universe multiverse
deb http://be.archive.ubuntu.com/ubuntu/ gutsy-updates main restricted universe multiverse
deb http://be.archive.ubuntu.com/ubuntu/ gutsy-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu gutsy-security main restricted universe multiverse

I'm almost certain this isn't amavid-new directly. There should be more
information about the bus error in you logs somwhere.

Strange it is a standard server install except for 1 thing.
I use software raid and everything else works.

You could try to find the place in the amavisd-new script which causes the error.
It should be somewhere after the "starting." gets logged and the other two lines mentioned in the debug log output above.
Just add "print 1;", "print 2;" etc to amavisd-new (probably in /usr/bin - see "which amavisd-new") and you should see where it fails.

Going to install every version from dapper and see where it goes sour.

Grep your logs and see if you can find more about the bus error.

Which logs specific and how can I do this fast?

I'd grep -ir bus /var/log and see what looks interesting.

I'd guess most likely /var/log/messages, /var/log/kern.log, or /var/log/udev

Could find anything suspisious:

/var/log/dpkg.log:2008-01-12 16:29:15 install busybox-initramfs <none> 1:1.1.3-5ubuntu7
/var/log/dpkg.log:2008-01-12 16:29:15 status half-installed busybox-initramfs 1:1.1.3-5ubuntu7
/var/log/dpkg.log:2008-01-12 16:29:15 status unpacked busybox-initramfs 1:1.1.3-5ubuntu7
/var/log/dpkg.log:2008-01-12 16:29:15 status unpacked busybox-initramfs 1:1.1.3-5ubuntu7
/var/log/dpkg.log:2008-01-12 16:29:17 install libdbus-1-3 <none> 1.1.1-3ubuntu4
/var/log/dpkg.log:2008-01-12 16:29:17 status half-installed libdbus-1-3 1.1.1-3ubuntu4
/var/log/dpkg.log:2008-01-12 16:29:17 status unpacked libdbus-1-3 1.1.1-3ubuntu4
/var/log/dpkg.log:2008-01-12 16:29:17 status unpacked libdbus-1-3 1.1.1-3ubuntu4
/var/log/dpkg.log:2008-01-12 16:29:21 install libusb-0.1-4 <none> 2:0.1.12-7
/var/log/dpkg.log:2008-01-12 16:29:21 status half-installed libusb-0.1-4 2:0.1.12-7
/var/log/dpkg.log:2008-01-12 16:29:21 status unpacked libusb-0.1-4 2:0.1.12-7
/var/log/dpkg.log:2008-01-12 16:29:21 status unpacked libusb-0.1-4 2:0.1.12-7
/var/log/dpkg.log:2008-01-12 16:29:30 configure libdbus-1-3 1.1.1-3ubuntu4 1.1.1-3ubuntu4
/var/log/dpkg.log:2008-01-12 16:29:30 status unpacked libdbus-1-3 1.1.1-3ubuntu4
/var/log/dpkg.log:2008-01-12 16:29:30 status half-configured libdbus-1-3 1.1.1-3ubuntu4
/var/log/dpkg.log:2008-01-12 16:29:30 status installed libdbus-1-3 1.1.1-3ubuntu4
/var/log/dpkg.log:2008-01-12 16:29:30 configure libusb-0.1-4 2:0.1.12-7 2:0.1.12-7
/var/log/dpkg.log:2008-01-12 16:29:30 status unpacked libusb-0.1-4 2:0.1.12-7
/var/log/dpkg.log:2008-01-12 16:29:30 status half-configured libusb-0.1-4 2:0.1.12-7
/var/log/dpkg.log:2008-01-12 16:29:30 status installed libusb-0.1-4 2:0.1.12-7
/var/log/dpkg.log:2008-01-12 16:29:32 configure busybox-initramfs 1:1.1.3-5ubuntu7 1:1.1.3-5ubuntu7
/var/log/dpkg.log:2008-01-12 16:29:32 status unpacked busybox-initramfs 1:1.1.3-5ubuntu7
/var/log/dpkg.log:2008-01-12 16:29:32 status half-configured busybox-initramfs 1:1.1.3-5ubuntu7
/var/log/dpkg.log:2008-01-12 16:29:32 status installed busybox-initramfs 1:1.1.3-5ubuntu7
/var/log/apt/term.log:Starting amavisd: Bus error
/var/log/apt/term.log:Starting amavisd: Bus error
/var/log/apt/term.log:Starting amavisd: Bus error
/var/log/apt/term.log:Starting amavisd: Bus error
/var/log/apt/term.log:Starting amavisd: Bus error
/var/log/apt/term.log:Starting amavisd: Bus error
/var/log/apt/term.log:Starting amavisd: Bus error
/var/log/messages:Jan 12 16:49:48 homeserver kernel: [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
/var/log/messages:Jan 12 16:49:48 homeserver kernel: [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
/var/log/messages:Jan 12 16:49:48 homeserver kernel: [ 19.127673] EISA bus registered
/var/log/messages:Jan 12 16:49:48 homeserver kernel: [ 19.127695] ACPI: bus type pci registered
/var/log/messages:Jan 12 16:49:48 homeserver kernel: [ 19.129423] PCI: PCI BIOS revision 2.10 entry at 0xfa0f0, last bus=1
/var/log/messages:Jan 12 16:49:48 homeserver kernel: [ 19.352618] ACPI: bus type pnp registered
/var/log/messages:Jan 12 16:49:48 homeserver kernel: [ 19.363676] ACPI: ACPI bus type pnp unregistered
/va...

Done a fresh install without updating the installatie and using enlgish instead of my native language dutch and it works.
Now updating the installation to see if the error comes with updating.

Can confirm this:
Dutch version works out of the box.
But as soon as I do the update the bus error appears.

So problem is in one of the updates with the nl_be language setting.

After googling a bit.
There are a lot of bus errors with perl scripts.
So my guess right now that this is a perl language error.

Anyone know a way to test this?
Maybe I can switch to english do a test and switch back to my dutch language?

Ok latest update.

It isn't language related I guess.
The english version has the same problem after updating the standard installation. I forgot to reboot previous time. So going to test if it is a kernel error or some kind;

At this point I think it's extremely unlikely that you are having a problem that is specifically with the amavisd-new package, so I'm marking this invalid. If you find information that points in a specific direction for further troubleshooting/triaging, please re-open the bug and assign it to whatever package proves to be the problem.