<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div><br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">s@s:~ (206) amarok --debug --nofork<br>amarok: ************************************************************************************************************ <br>amarok: ** DEBUGGING OUTPUT IS NOW ENABLED. PLEASE NOTE THAT YOU WILL ONLY SEE THE FULL OUTPUT ON THE NEXT START. ** <br>amarok: ************************************************************************************************************ <br>amarok: END__: static void App::handleCliArgs() - Took 0.0003s <br>amarok: END__: virtual int App::newInstance() - Took 0.00049s <br>amarok: BEGIN: MainWindow::MainWindow() <br>amarok: BEGIN: static ServicePluginManager* ServicePluginManager::instance()
<br>amarok: BrowserCategoryList named "internet" starting... <br>amarok: BEGIN: BrowserCategoryListDelegate::BrowserCategoryListDelegate(QTreeView*) <br>amarok: END__: BrowserCategoryListDelegate::BrowserCategoryListDelegate(QTreeView*) - Took 0.00011s <br>amarok: We are sorting!! <br>amarok: ServiceBrowser starting... <br>amarok: BEGIN: void ServicePluginManager::collect() <br>amarok: [PluginManager] Plugin trader constraint: "[X-KDE-Amarok-framework-version] == 56 and [X-KDE-Amarok-plugintype] == 'service' and [X-KDE-Amarok-rank] > 0" <br>amarok: Received [ "6" ] collection plugin offers <br>amarok: BEGIN: static Plugins::Plugin*
Plugins::PluginManager::createFromService(KSharedPtr<KService>) <br>amarok: [PluginManager] Trying to load: "amarok_service_ampache" <br>amarok: BEGIN: void CollectionManager::init() <br>amarok: [PluginManager] Plugin trader constraint: "[X-KDE-Amarok-framework-version] == 56 and [X-KDE-Amarok-plugintype] == 'collection' and [X-KDE-Amarok-rank] > 0" <br>amarok: [CollectionManager] Received [ "7" ] collection plugin offers <br>amarok: [CollectionManager] Initialising sqlcollection <br>InnoDB: Log scan progressed past the checkpoint lsn 0 36808<br>100702 19:24:05 InnoDB: Database was not shut down normally!<br>InnoDB: Starting crash recovery.<br>InnoDB:
Reading tablespace information from the .ibd files...<br>InnoDB: Restoring possible half-written data pages from the doublewrite<br>InnoDB: buffer...<br>InnoDB: Doing recovery: scanned up to log sequence number 0 43655<br>100702 19:24:05 InnoDB: Starting an apply batch of log records to the database...<br>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 <br>InnoDB: Apply batch completed<br>KCrash: Application 'amarok' crashing...<br>sock_file=/home/s/.kde4/socket-s.local/kdeinit4__0<br>100702 19:24:06 InnoDB: Error: Write to file /home/s/.kde4/share/apps/amarok/mysqle/ibdata1 failed at offset 0 1048576.<br>InnoDB: 262144 bytes should have been written, only -1 were
written.<br>InnoDB: Operating system error number 9.<br>InnoDB: Check that your OS and file system support files of this size.<br>InnoDB: Check also that the disk is not full or a disk quota exceeded.<br>InnoDB: Error number 9 means 'Bad file descriptor'.<br>InnoDB: Some operating system error numbers are described at<br><span>InnoDB: <a target="_blank" href="http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html">http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html</a></span><br>100702 19:24:06InnoDB: Assertion failure in thread 822771456 in file fil0fil.c line 4023<br>InnoDB: Failing assertion: ret<br>InnoDB: We intentionally generate a memory trap.<br><span>InnoDB: Submit a detailed bug report to <a target="_blank" href="http://bugs.mysql.com">http://bugs.mysql.com</a>.</span><br>InnoDB: If you get repeated assertion failures or crashes, even<br>InnoDB: immediately after the mysqld startup, there may
be<br>InnoDB: corruption in the InnoDB tablespace. Please refer to<br><span>InnoDB: <a target="_blank" href="http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html">http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html</a></span><br>InnoDB: about forcing recovery.<br>Unable to start Dr. Konqi<br>s@s:~ (207) <br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Mikhail T. <mi+thun@aldan.algebra.com><br><b><span style="font-weight: bold;">To:</span></b> Matt <datahead4@gmail.com><br><b><span style="font-weight: bold;">Cc:</span></b> kde@freebsd.org; kasablankastopkova@yahoo.com<br><b><span style="font-weight: bold;">Sent:</span></b> Thu, July 1, 2010 9:46:50 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: amarok-kde4 dies at start-up<br></font><br>
01.07.2010 15:45, Matt написав(ла):
<blockquote type="cite">
<pre>Please try starting Amarok with the "--debug --nofork" options set.<br>You will need to do this twice in a row for the debug flag to truly<br>become active. Please forward the resulting console output.<br><br>At one time I remember Amarok had a problem with using InnoDB tables<br>for the embedded MySQL connection. Not sure if that is still the case<br>though.<br> </pre>
</blockquote>
Thanks, Matt! I'm upgrading this machine to KDE-4.4.5 now. When that's
over, I'll try your request. Yours,<br>
<blockquote>-mi<br>
</blockquote>
</div></div>
</div><br>
</body></html>