[kde-freebsd] amarok-kde4 dies at start-up

[Rusty Nejdl]

On Fri, 2 Jul 2010 10:29:33 -0700 (PDT), blanka x  wrote:  

s at s:~ (206) amarok --debug --nofork
amarok:
************************************************************************************************************

amarok: ** DEBUGGING OUTPUT IS NOW ENABLED. PLEASE NOTE THAT YOU WILL
ONLY
SEE THE FULL OUTPUT ON THE NEXT START. ** 
amarok:
************************************************************************************************************

amarok: END__: static void App::handleCliArgs() - Took 0.0003s 
amarok: END__: virtual int App::newInstance() - Took 0.00049s 
amarok: BEGIN: MainWindow::MainWindow() 
amarok: BEGIN: static ServicePluginManager*
ServicePluginManager::instance() 
amarok: BrowserCategoryList named "internet" starting... 
amarok: BEGIN:
BrowserCategoryListDelegate::BrowserCategoryListDelegate(QTreeView*) 
amarok: END__:
BrowserCategoryListDelegate::BrowserCategoryListDelegate(QTreeView*) -
Took
0.00011s 
amarok: We are sorting!! 
amarok: ServiceBrowser starting... 
amarok: BEGIN: void ServicePluginManager::collect() 
amarok: [PluginManager] Plugin trader constraint:
"[X-KDE-Amarok-framework-version] == 56 and [X-KDE-Amarok-plugintype]
==
'service' and [X-KDE-Amarok-rank] > 0" 
amarok: Received [ "6" ] collection plugin offers 
amarok: BEGIN: static Plugins::Plugin*
Plugins::PluginManager::createFromService(KSharedPtr) 
amarok: [PluginManager] Trying to load: "amarok_service_ampache" 
amarok: BEGIN: void CollectionManager::init() 
amarok: [PluginManager] Plugin trader constraint:
"[X-KDE-Amarok-framework-version] == 56 and [X-KDE-Amarok-plugintype]
==
'collection' and [X-KDE-Amarok-rank] > 0" 
amarok: [CollectionManager] Received [ "7" ] collection plugin offers 
amarok: [CollectionManager] Initialising sqlcollection 
InnoDB: Log scan progressed past the checkpoint lsn 0 36808
100702 19:24:05 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 0 43655
100702 19:24:05 InnoDB: Starting an apply batch of log records to the
database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
19
20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43
44
45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68
69
70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93
94
95 96 97 98 99 
InnoDB: Apply batch completed
KCrash: Application 'amarok' crashing...
sock_file=/home/s/.kde4/socket-s.local/kdeinit4__0
100702 19:24:06 InnoDB: Error: Write to file
/home/s/.kde4/share/apps/amarok/mysqle/ibdata1 failed at offset 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 'Bad file descriptor'.
InnoDB: Some operating system error numbers are described at
InnoDB:
http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
[1]
100702 19:24:06InnoDB: Assertion failure in thread 822771456 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 [2].
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
[3]
InnoDB: about forcing recovery.
Unable to start Dr. Konqi
s at s:~ (207)