Splashy fail to install with apt-get

[Angel Guzman Maeso]

Binary package hint: splashy

When I install splashy wit apt-get:

$ sudo apt-get install splashy splashy-themes
Reading package lists... Done
Building dependency tree
Reading state information... Done
splashy-themes is already the newest version.
The following packages were automatically installed and are no longer required:
  libmono-posix1.0-cil libmono-security1.0-cil libmono-sharpzip0.84-cil libmono-system-web1.0-cil libmono-data1.0-cil
  libmono-getoptions1.0-cil libmono1.0-cil libmono-data-tds1.0-cil libmono-system-data1.0-cil
Use 'apt-get autoremove' to remove them.
Suggested packages:
  console-common
The following NEW packages will be installed:
  splashy
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0B/1180kB of archives.
After this operation, 1831kB of additional disk space will be used.
(Reading database ... 256538 files and directories currently installed.)
Unpacking splashy (from .../splashy_0.3.13-3ubuntu1_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/splashy_0.3.13-3ubuntu1_i386.deb (--unpack):
 trying to overwrite `/etc/lsb-base-logging.sh', which is also in package lsb-base
Processing triggers for man-db ...
Errors were encountered while processing:
 /var/cache/apt/archives/splashy_0.3.13-3ubuntu1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
Package: splashy None [modified: /var/lib/dpkg/info/splashy.list]
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: splashy
Uname: Linux 2.6.28-8-generic i686

[rww (rww-deactivatedaccount)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 328089, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.