Version: (using KDE KDE 3.5.0) Installed from: Gentoo Packages OS: Linux After installing new themes via the "new stuff" interface, they do not show up in the list of available themes. I have installed 3, ViewPortageX (1.01), LiquidWeather++ (8.9) and Airo AIO Kmail notifier (2.1.1)
Some theme authors don't post direct urls to their download links, but instead post their website urls. I know that Liquid Weather does this, and SVN has a fix where author urls launch in a browser for the user. I'm not sure about the Aero Kmail plugin, but ViewPortageX installed and appeared for me in the theme dialog. To reset the status fo them being installed, you can edit the file(which this will be fixed soon as well) ~/.kde/share/config/superkarambarc and remove the lines below the [NewStuff] tag. Then try running SuperKaramba from konsole and repeat the downloads that failed for you. That way any errors will hopefully be reported in the output.
Hi, I have to quote: > To reset the status fo them being installed, you can edit the file > (which this will be fixed soon as well) Well, this bug is for 3.5.0, the comment has a date of December 16th, I have 3.5.1 which was released on January 31st, and the problem is still there, so what do you mean by "fixed soon"? (Do not take me bad, shouting "hurry, hurry!" - I am just curious if this was not forgotten and does not need a reminder like this ...) btw, in my opinion, I would not allow the website links, i.e. _manual_ installation, within a dialogue for _automatic_ installation (or at least do not run it without the warning that you have to install it yourself using that page because at the first try I confused it with some stupid advertisement or sort of "readme after install" info)
Proper uninstallation of themes has the "fix" already and should be in 3.5.1. There was no changes to reset any previous status that was saved, so you'll have to either rm that file and start fresh or just hand edit it. Any further themes installed via New Stuff should behave much better now though.
> Proper uninstallation of themes has the "fix" already and should be in 3.5.1 well, I have got 3.5.1 (Mandriva rpm, version 3.5.1-0.1.20060.SoS, to be exact), I had never installed Superkaramba before ... when I had started it for the first time, I tried to install (among others) LiquidWeather but it opened a web page (*) instead of the installation ... after that the manager showed status like installed (so it refused to open the page again) but did not provide uninstallation (or cleanup) option so I could return to the original state (*) which I immediatelly closed - unaware that _this_ is the installation procedure because the previous theme was installed without interaction I understand that cleaning the mess from the previous installation or handmade configuration would be a problem, but this was fresh 3.5.1, nothing before it and just clicking the mouse in the superkaramba GUI ... so, to be sure, tried on another computer (this time using Gentoo): $ emerge -s superkaramba ... * kde-base/superkaramba Latest version available: 3.5.1 Latest version installed: 3.5.1 $ superkaramba -v Qt: 3.3.4 KDE: 3.5.1 SuperKaramba: 0.38 $ superkaramba ~/.superkaramba doesn't exist created ~/.superkaramba clicking "Nové motivy" (New themes - or New stuff?) => Liquid Weather ++ => Instalovat (Install) it opens a Konqueror window with http://liquidweather.net/, makes green check mark in front of Liquid Weather ++ in the list and disables the install-button I close the Konqueror window and close the new stuff dialogue Liquid Weather ++ is not in the list of themes, so I reopen the New stuff dialogue ... and I stare at the screen surprised as the green mark for Liquid Weather ++ is gone I do not understand how it is possible (**) that it did not work (the green mark lasted) on another computer with _the same_ superkaramba version, but it looks like this is really fixed - thanks and sorry for the confusion (**) well, in fact, I have one suspection - Mandriva likes to put some own configuration stuff at the time of package installation (or even on each system boot) so this may be the cause ... sorry, I do not have time to play with it to find out p.s. sorry if the tenses are messed or for other mistakes, I hope the text is understandable ... I am not native English speaker
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.