[opensuse] amarok will not start 11.2
I upgraded using zypper dup from 11.1 to 11.2 Amarok says: The Amarok collection database was created by a newer version of Amarok, and this version of Amarok cannot use it. The debug info is: amarok --debug InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 091119 14:02:08 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... 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.00022s amarok: END__: virtual int App::newInstance() - Took 0.00031s steve@hh1:~> amarok: BEGIN: XesamCollectionBuilder::XesamCollectionBuilder(SqlCollection*) amarok: END__: XesamCollectionBuilder::XesamCollectionBuilder(SqlCollection*) - Took 0.00086s Can anyone help? Thanks L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 19 November 2009 08:05:20 am lynn wrote:
I upgraded using zypper dup from 11.1 to 11.2
Amarok says:
The Amarok collection database was created by a newer version of Amarok, and this version of Amarok cannot use it.
The debug info is:
amarok --debug InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 091119 14:02:08 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... 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.00022s amarok: END__: virtual int App::newInstance() - Took 0.00031s steve@hh1:~> amarok: BEGIN: XesamCollectionBuilder::XesamCollectionBuilder(SqlCollection*) amarok: END__: XesamCollectionBuilder::XesamCollectionBuilder(SqlCollection*) - Took 0.00086s
Can anyone help? Thanks L x
Chances are you went from Amarok 2.2.1 (In KDE 4.3 repo but doesn't work in 11.2) -> Amarok 2.1.1 (Shipped with 11.2) which can not be done do to changed in the database. Just remove the ~/.kde4/apps/amarok directory and let it rebuild your database and you will be good. -- "We must plan for freedom, and not only for security, if for no other reason than only freedom can make security more secure." Karl Popper
Can anyone help? Thanks L x
Chances are you went from Amarok 2.2.1 (In KDE 4.3 repo but doesn't work in 11.2) -> Amarok 2.1.1 (Shipped with 11.2) which can not be done do to changed in the database. Just remove the ~/.kde4/apps/amarok directory and let it rebuild your database and you will be good.
Thanks and yes I did. It must be one of the downgrades it did. Can cofirm that removal of the folder makes amarok work again. Thanks so much. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Adam Jimerson
-
lynn