On Mon, Feb 21, 2011 at 5:27 AM, Matthias Fuchs <ma...@gmx.net> wrote: > Am Montag 14 Februar 2011, 15:35:31 schrieb todd rme: >> On Mon, Feb 14, 2011 at 7:51 AM, Sebastian Kügler <se...@kde.org> wrote: >> > On Sunday, February 13, 2011 18:20:10 todd rme wrote: >> >> I know this is not the proper place to be discussing bugs, but I am >> >> seeing a worrying pattern of problems with GHNS since KDE 4.5. As far >> >> as I can tell, there are at least 4 GHNS implementations that are >> >> currently broken. The plasmoid GHNS system does not remember the >> >> plasmoids you installed after a reboot, so the list of installed >> >> widgets always remains empty. Both the plasma theme and window >> >> decoration theme do not remember updates, so if you apply an update, >> >> close the GHNS dialog, then open it again the updates are still >> >> listed. The Dolphin service menu GHNS interface always fails during >> >> installation. There maybe other problems as well, but these are the >> >> ones I have personally run into. >> >> >> >> As I said, these problems have been around since at least KDE 4.5, and >> >> are still around in KDE 4.6. I am not sure whether there is a single >> >> problem that is causing random difficulties in multiple places, or >> >> multiple different problems. However, since these bugs are in >> >> multiple different places, and the start seems to roughly coincide >> >> with the adoption of the new GHNS system, I thought it was at least >> >> possible that there is a pattern that isn't apparent looking at the >> >> individual issues. >> > >> > Bugnumbers? If these have not been reported, that would be a good first >> > step... >> >> https://bugs.kde.org/show_bug.cgi?id=214054 >> https://bugs.kde.org/show_bug.cgi?id=234265 >> https://bugs.kde.org/show_bug.cgi?id=256473 >> >> -Todd >> >> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to >> >> unsubscribe << > > I mentioned these problems months ago. The reason for them are not wrong > implementations in the programs but GHNS itself. > > GHNS does not share its cache between instances of GHNS in the same app and > between apps. > > The first issue would have been solved by [1] which I forgot about. > I tried to discuss the second issue in kde-core-devel [2] but it never really > took off -- no GHNS developer involvment -- so I forgot about that as well. > > Basically all this means that it was impossible for me to add a working auto- > update mechanism in the comic plasmoid. > > The reason for updates being displayed as updateable despite being updated > already is likely this line [3] which I also reported. > > I talked about all these problems but did not get much or any feedback, seems > familiar to your situation. :D > So I simply supposed that I am the only one which sees or has that problem and > moved to something else to work on and forgot about it relatively fast. > > If you want you can take what I did work on (1 + 3) and implement it if it > fixes the problems, as I am not really willing to work on it anymore. > There are other projects which I find more interesting and where I get more > feedback and further time is scarce, reading the ml now should have been a > small break. :D > Same goes for 2, though my first tries never took off and it was a pita, the > GHNS code base is imo not really suited for that. > > > [1] http://reviewboard.kde.org/r/5528/ > [2] http://lists.kde.org/?l=kde-core-devel&m=128785351717032&w=2 > [3] > --- a/knewstuff/knewstuff3/core/installation.cpp > +++ b/knewstuff/knewstuff3/core/installation.cpp > @@ -304,7 +304,7 @@ void Installation::install(KNS3::EntryInternal entry, > const QString& downloadedF > if (!entry.updateVersion().isEmpty()) { > entry.setVersion(entry.updateVersion()); > } > - if (!entry.updateReleaseDate().isValid()) { > + if (entry.updateReleaseDate().isValid()) { > entry.setReleaseDate(entry.updateReleaseDate()); > } > } >
It seems strange that something as fundamental and pervasive as GHNS could be this broken without anyone caring about it. Does nobody else have these problems? Or are, for example, plasma developers not bothered by the fact that installing plasmoids and updating plasma themes are both broken? For a technology that KDE pushes so hard to be broken at a pretty fundamental level seems to be a serious issue. Unfortunately, looking at the patch it looks like it is beyond my abilities to work on. -Todd >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
