[debian-mysql] Bug#708049: Can't install

[spikethehobbitmage.excite]

I'm not the original submitter, but I'm having what appears to be the same problem.
I did not get a 'gdbm fatal' message.
I do not have libnss-mysql* installed.
I believe this is a clean install of mysql, but I can't guarantee that old files may be present from an ancient install.

# ls -l /var/log/mysql*
-rw-r----- 1 mysql adm    0 Jun 21 01:31 /var/log/mysql.err
-rw-r----- 1 mysql adm    0 Jun 21 01:31 /var/log/mysql.log

/var/log/mysql:
total 0

nothing in dmesg

/var/log/debug contained
/etc/init.d/mysql[31956]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
/etc/init.d/mysql[31956]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed
/etc/init.d/mysql[31956]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
/etc/init.d/mysql[31956]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!

# su mysql
# mysqld

130621  1:36:01 [Note] Plugin 'FEDERATED' is disabled.
130621  1:36:01 InnoDB: The InnoDB memory heap is disabled
130621  1:36:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130621  1:36:01 InnoDB: Compressed tables use zlib 1.2.7
130621  1:36:01 InnoDB: Using Linux native AIO
130621  1:36:01 InnoDB: Initializing buffer pool, size = 128.0M
130621  1:36:01 InnoDB: Completed initialization of buffer pool
130621  1:36:01 InnoDB: highest supported file format is Barracuda.
130621  1:36:02  InnoDB: Error: trying to access tablespace 1 page no. 2,
InnoDB: but the tablespace does not exist or is just being dropped.
......repeated many times......
130621  1:36:02  InnoDB: Error: trying to access tablespace 1 page no. 2,
InnoDB: but the tablespace does not exist or is just being dropped.
InnoDB: Error: Unable to read tablespace 1 page no 2 into the buffer pool after 100 attempts
InnoDB: The most probable cause of this error may be that the table has been corrupted.
InnoDB: You can try to fix this problem by using innodb_force_recovery.
InnoDB: Please see reference manual for more details.
InnoDB: Aborting...
130621  1:36:02  InnoDB: Assertion failure in thread 140655213950784 in file buf0buf.c line 2346
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
07:36:02 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346682 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x30000
mysqld(my_print_stacktrace+0x29)[0x7fecd8678569]
mysqld(handle_fatal_signal+0x3d8)[0x7fecd8560748]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf210)[0x7fecd7d10210]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7fecd6505295]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fecd6508438]
mysqld(+0x5b73b4)[0x7fecd86f83b4]
mysqld(+0x5f0d83)[0x7fecd8731d83]
mysqld(+0x58932e)[0x7fecd86ca32e]
mysqld(+0x589a6b)[0x7fecd86caa6b]
mysqld(+0x58c50e)[0x7fecd86cd50e]
mysqld(+0x578e40)[0x7fecd86b9e40]
mysqld(+0x54543f)[0x7fecd868643f]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7fecd8562ad1]
mysqld(+0x330e31)[0x7fecd8471e31]
mysqld(_Z11plugin_initPiPPci+0xa43)[0x7fecd8473dc3]
mysqld(+0x2b3f85)[0x7fecd83f4f85]
mysqld(_Z11mysqld_mainiPPc+0x45b)[0x7fecd83f9d4b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fecd64f1a55]
mysqld(+0x2b0199)[0x7fecd83f1199]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.