3 ms·

KDE 4.0 was released almost 6 years ago, and I wish people would get over it. 4.11 is not the same software. It's very fast and stable, and if you develop for i

by ewzimm 13y ago

KDE 4.0 was released almost 6 years ago, and I wish people would get over it. 4.11 is not the same software. It's very fast and stable, and if you develop for it, you can count on long-term compatibility. It's GNOME and Unity that break backward compatibility with new releases now. They certainly have the right to do that, and I respect their desire to move their desktop forward, but it means software like qtcurve no longer works for GTK because some developers don't want to have to rewrite for every GNOME release.

makomk 13y ago
Well, it was very fast and stable. For the last few KDE major releases plasma-desktop has been segfaulting on a regular basis for me. I looked up the backtrace a few versions back and found a bugreport where a lot of people were experiencing the same issue; the developers confirmed it and reckoned that it was probably a bug in some new Qt functionality they'd moved to that they couldn't do much about.
- ewzimm 13y ago
  Could you post a link to the bug report? I'd like to look at it.
  - makomk 13y ago
    I'm fairly this was the bug report: https://bugs.kde.org/show_bug.cgi?id=311871 https://bugs.kde.org/show_bug.cgi?id=311871 Apparently someone finally checked in a workaround a couple of days ago.
    - ewzimm 13y ago
      Looks like it was fixed on 10/28, which is definitely a long turnaround since it was first posted 10 months ago. I suppose it took so long because it was a pretty specific situation (removing a notification while inserting one while hitting a 10 minute timer) but still, that just goes to show two things: the latest KDE has fixed a ton of bugs, even unusual ones like that, and KDE still needs more people looking at bugs so things like this can get a faster turnaround in the future. If anyone does find something like this that isn't getting enough attention on the official bug reports, I'd suggest just mentioning it to a developer friend who uses KDE.

by ewzimm 13y ago

makomk 13y ago

Well, it was very fast and stable. For the last few KDE major releases plasma-desktop has been segfaulting on a regular basis for me. I looked up the backtrace a few versions back and found a bugreport where a lot of people were experiencing the same issue; the developers confirmed it and reckoned that it was probably a bug in some new Qt functionality they'd moved to that they couldn't do much about.

ewzimm 13y ago
Could you post a link to the bug report? I'd like to look at it.
- makomk 13y ago
  I'm fairly this was the bug report: https://bugs.kde.org/show_bug.cgi?id=311871 https://bugs.kde.org/show_bug.cgi?id=311871 Apparently someone finally checked in a workaround a couple of days ago.
  - ewzimm 13y ago
    Looks like it was fixed on 10/28, which is definitely a long turnaround since it was first posted 10 months ago. I suppose it took so long because it was a pretty specific situation (removing a notification while inserting one while hitting a 10 minute timer) but still, that just goes to show two things: the latest KDE has fixed a ton of bugs, even unusual ones like that, and KDE still needs more people looking at bugs so things like this can get a faster turnaround in the future. If anyone does find something like this that isn't getting enough attention on the official bug reports, I'd suggest just mentioning it to a developer friend who uses KDE.