upgrading from 4.1 to 4.2 broke amarok

[Eduard Sukharev]

On Понедельник 23 февраля 2009 00:00:02 Gaetano Giunta wrote:
> Eduard Sukharev a écrit :
> > On Воскресенье 22 февраля 2009 17:33:57 Diego wrote:
> >> CCing the amarok mailing list, maybe someone there can help.
> >>
> >> Gaetano Giunta ha scritto:
> >>> Hello
> >>>
> >>> I just tried upgrading from the latest 4.1 to 4.2.0, on win xp french.
> >
> > It is strongly recommended not to upgrade between major releases. 4.1 and
> > 4.2 packages are binary incompatible, so upgrading from any 4.1.x
> > installation into 4.2.x causes unexpected errors. You should completely
> > delete the previous KDE installation and fresh install KDE 4.2 from
> > scratch. This should work, then. Even though Amarok is quite a separate
> > project it still uses kdelibs which is important.
> > If you have any issues deleting KDE consider reading this thread on KDE
> > forum: http://forum.kde.org/how-to-remove-kde-from-windows-t-20596.html
> >
> > Please, report the outcome of your reinstall.
>
> Mmmh, strange that this upgrade path is unsupported, as the installer
> will let you happily do that withoiut a warning - and the release
> announcements on kde sites did not mention it...
> Anyway:
> - removed by hand kde dir, kde download dir and the two .kde folders in
> the win32 user profile dir
> - launched installer again, picking 'latest-stable'
> - selecting just amarok detected 33 dependencies, total 34 packages
> downloaded
> - still no icons in my menu :(
>
> here's the tail of the installer log:
>
>     [2009-02-22 16:47:13] Debug: shared\unpacker.cpp 417
>     Unpacker::unpackFile filename:
>     "D:/downloads/kde/openssl-0.9.8g-1-bin.zip" root:  "D:\kde"
>     [2009-02-22 16:47:13] Debug: shared\unpacker.cpp 451
>     Unpacker::unpackFile ret:  true
>     [2009-02-22 16:47:13] Debug: gui\postprocesspage.cpp 34 checking for
>     app  "update-mime-database"  -  found
>     [2009-02-22 16:47:13] Debug: gui\postprocesspage.cpp 40 running
>     "update-mime-database" ("D:\kde/share/mime")
>     [2009-02-22 16:47:17] Debug: gui\postprocesspage.cpp 34 checking for
>     app  "kbuildsycoca4"  -  found
>     [2009-02-22 16:47:17] Debug: gui\postprocesspage.cpp 40 running
>     "kbuildsycoca4" ()
>     [2009-02-22 16:47:23] Debug: gui\postprocesspage.cpp 34 checking for
>     app  "kwinstartmenu"  -  found
>     [2009-02-22 16:47:23] Debug: gui\postprocesspage.cpp 40 running
>     "kwinstartmenu" ("--remove")
>     [2009-02-22 16:47:23] Debug: gui\postprocesspage.cpp 34 checking for
>     app  "kwinstartmenu"  -  found
>     [2009-02-22 16:47:23] Debug: gui\postprocesspage.cpp 40 running
>     "kwinstartmenu" ()
>     [2009-02-22 16:47:28] Debug: called
>
>
> and here's what happens when I run kwinstartmenu by hand in a cmd shell:
>
>     D:\kde\bin>kwinstartmenu
>     Family none
>     Family none
>     kbuildsycoca4 running...
>     Critical: winstartmenu(1884): No ksycoca4 database available!
>
>     Critical: winstartmenu(1884): No ksycoca4 database available!
>
>
>     D:\kde\bin>
>
>
> I have no idea about where the ksyscoca db should be and why it is not
> available.
> The only 'strange' thing on this laptop is the fact that there are a
> bazillion of tools already installed, including unxutils and lots of
> unixy stuff, and they might be in the shells'PATH env var...
>
>
> _______________________________________________
> Kde-windows mailing list
> Kde-windows at kde.org
> https://mail.kde.org/mailman/listinfo/kde-windows
Hmm... If it complains about ksycoca - try to navigate to your kde install dir 
in the cmd.exe shell. Note, though, that you should navigate to KDE install (i 
belive it's D:\kde for you), not the /bin dir inside of it (not D:\kde\bin).
Then run this:

bin\kbuildsycoca4 --noincremental

This is supposed to rebuild your kbuildsycoca database.
Or, maybe that'd be better, run any of "post-install-*.bat" files that you'll 
find in 'manifest' subdir. Nte that these should be run also from the kderoot:

manifest\post-install-kdebase-runtime-20080202-bin.bat

Of course, you should adopt the file name to some existing one. You don't need 
to run all of them, only one and nly once. Though, running it multiple times 
won't hurt. If there're no such files - just run that kbuildsycoca command as 
adviced at first.
-- 
Regards,
Eduard Sukharev
	proud KDE developer