Newly-built Amarok would not start

[Mikhail T.]

Dear Amarok developers!

We can't get the newly-built amarok-2.3.1 (built against KDE-4.4.5) 
off-the ground... It complains about the database and crashes. This is a 
new laptop with a new user's home directory -- not inherited from an 
earlier Amarok version. This is, what we get:

    s at s:~ (276) amarok
    kdeinit4: Shutting down running client.
    kdeinit4: preparing to launch /opt/kde4/lib/libkdeinit4_klauncher.so
    Connecting to deprecated signal
    QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
    kdeinit4: preparing to launch /opt/kde4/lib/libkdeinit4_kded4.so
    KDE Daemon (kded) already running.
    kdeinit4: preparing to launch /opt/kde4/lib/libkdeinit4_kbuildsycoca4.so
    kbuildsycoca4 running...
    InnoDB: The first specified data file
    /home/s/.kde4/share/apps/amarok/mysqle/ibdata1 did not exist:
    InnoDB: a new database to be created!
    100712 19:56:48  InnoDB: Setting file
    /home/s/.kde4/share/apps/amarok/mysqle/ibdata1 size to 10 MB
    InnoDB: Database physically writes the file full: wait...
    100712 19:56:49  InnoDB: Log file
    /home/s/.kde4/share/apps/amarok/mysqle/ib_logfile0 did not exist:
    new to be created
    InnoDB: Setting log file
    /home/s/.kde4/share/apps/amarok/mysqle/ib_logfile0 size to 5 MB
    InnoDB: Database physically writes the file full: wait...
    100712 19:56:49  InnoDB: Log file
    /home/s/.kde4/share/apps/amarok/mysqle/ib_logfile1 did not exist:
    new to be created
    InnoDB: Setting log file
    /home/s/.kde4/share/apps/amarok/mysqle/ib_logfile1 size to 5 MB
    InnoDB: Database physically writes the file full: wait...
    InnoDB: Doublewrite buffer not found: creating new
    InnoDB: Doublewrite buffer created
    InnoDB: Creating foreign key constraint system tables
    InnoDB: Foreign key constraint system tables created
    <unknown program name>(45632)/: Communication problem with  "amarok"
    , it probably crashed.
    Error message was:  "org.freedesktop.DBus.Error.ServiceUnknown" : "
    "The name org.kde.amarok was not provided by any .service files" "

    KCrash: Application 'amarok' crashing...
    sock_file=/home/s/.kde4/socket-s.local/kdeinit4__0
    kdeinit4: preparing to launch /opt/kde4/lib/kde4/libexec/drkonqi
    s at s:~ (277) 100712 19:56:51  InnoDB: Error: Write to file
    /home/s/.kde4/share/apps/amarok/mysqle/ibdata1 failed at offseoffset
    0 1048576.
    InnoDB: 262144 bytes should have been written, only -1 were written.
    InnoDB: Operating system error number 9.
    InnoDB: Check that your OS and file system support files of this size.
    InnoDB: Check also that the disk is not full or a disk quota exceeded.
    InnoDB: Error number 9 means '.....'.
    InnoDB: Some operating system error numbers are described at
    InnoDB:
    http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
    100712 19:56:51InnoDB: Assertion failure in thread 821375872 in file
    fil0fil.c line 4023
    InnoDB: Failing assertion: ret
    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.0/en/forcing-recovery.html
    InnoDB: about forcing recovery.
    Unable to start Dr. Konqi
    klauncher: Exiting on signal 15

The disk has plenty of room... The Operating System is FreeBSD-8.1/i386 
(32-bit). Amarok was built via FreeBSD-port 
<http://www.freshports.org/audio/amarok-kde4>. The maintainers (CC-ed) 
advised us to contact you -- the developers... Please, help. Thank you!

    -mi

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/amarok/attachments/20100712/f1a0b23a/attachment.html>