OSNews

uhmmm...



Yes it does. Even 3.5.x does. I still see way too much of even the 3.5 crash dialog. Konqueror is a particularly egregious offender.



Yes it does.



I cannot comment on this since I have none. I didn't even have any before I tested KDE4. Are you claiming that you had children before your KDE4 adventure, and that they remain uneaten at this moment? ;-)

uhmmm...

It doesn't crash.

Yes it does. Even 3.5.x does. I still see way too much of even the 3.5 crash dialog. Konqueror is a particularly egregious offender.

It doesn't flake out.

Yes it does.

"

Then you're using the wrong distro. I haven't had a crash in KDE 4.x with openSUSE, with KDE4 apps or KDE3.

Seriously, when Gnome 1.0 and 2.0 were released, they needed some love to become loveable. But they were usable, mostly, and bugs were quickly addressed. Look where they led to.

If you've got serious problems with KDE4, then please report the bugs, otherwise you're not helping the situation.



I cannot comment on this since I have none. I didn't even have any before I tested KDE4. Are you claiming that you had children before your KDE4 adventure, and that they remain uneaten at this moment? ;-) "

I didn't before KDE4, but they were brought in as package dependencies... Damned RPM

Ummmmmmmmmm. Yer, there's lots of useful information people can take out of that comment.



Sadly, saying this doesn't make any of it true, nor does it give you any credibility. Without specifics, descriptions and backtraces this is about as useful as your comments normally are.

In my experience, I very rarely if ever see the crash dialogue in 3.5, Konqueror as a file manager has never crashed for me and the only time it has choked is as a web browser with some JavaScript - as Firefox has on occasions. So what? Oh, and I also use Amarok with my music on a NFS fileshare, and that sometimes hangs for a while. That's about it.


Yes it does. "

Based on............what? You know what the current state and functionality of KDE 4 is, and so does everyone else. We should all know why that's the case by now, and where things are heading. I've used KDE 4, but I don't use it as my main Linux desktop at the moment.

Functionally, it's by no means complete, but trying to create this impression of extreme instability and making the usual and predictable comebacks about children eating is pretty sad really, isn't it? If you're worried about something, just say come out and say it.

Unfortunately it still does crash, though 4.0.1 helped quite a bit. Given my workflow KDE 4.X is still unusable:

- Can not set keyboard macros for apps from the menus. This is very important to my workflow since I am extremely keyboard centric.
- Given a 1024x768 screen the current panel takes up way too much space.
- The use of xrandr to add/remove screens does not work correctly.
- The plasma desktop and panel crash (less often in 4.0.1) Usually this is due to me trying xrandr, though it does happen occasionally in other situations (I have not figured out a pattern yet) Once the desktop plasmoid crashes it is a bit of a challenge to use KDE.
- Konqueror crashes occasionally when used as a browser (though this is not really unique to KDE4)
- System Settings for display not functioning correctly.
- System Settings in general are incomplete
- please for the love of all that is holy give us an option to turn off the cashew in the top right corner (where I would normally put the hidden panel if I could move it... or hide it... or resize it... you get the idea)


Honestly I have far less problems with 4.0.1 and if that had been released as 4.0 I probably would not have complained. I can actually see how some might be able to use 4.0.1 as a daily desktop. Given its current limitations it is not usable as a main desktop for me though.

yes, this has not been ported yet. the shortcuts system changed fairly radically at all levels (shared daemon for globals, the shortcut API changed for apps, etc) so lots of breakage happened here.

note that adding shortcuts for apps in kde3 didn't happen immediately either; i'm sure it'll appear eventually in kde4.



4.0.2



this is a problem in Qt due to xrandr breaking compatibility in the xinerama api so absolutely horribly. some x.org devs (in this case keithp) are a bit ... unusually unconcerned about the effects of some of their decisions.

there is a patch in qt-copy that mostly fixes these issues (#0172) and we are working right now with Trolltech to get the fixes polished and upstreamed for Qt 4.4 (and therefore KDE 4.1)



i hope you've reported this on bugs.kde.org with backtraces?



alt-f2 (run dialog), plasma, enter.



khtml is what's crashing, and it's got some issues in kde4 atm.



in which way?



i do wish there were people who could spend more time with the control panels. they are generally underloved; that said, what parts are particularly incomplete for you? (he says, hoping this isn't a "critic's perfectionism" sort of observation on your part)



what does the toolbox have to do with panels? nothing: they live on different zorder'd windows.



so to get to 4.0.1 we needed to release 4.0.0. sitting on the code base longer would have resulted in us not being nearly as far forward as we are now.

we said this right at the start, many people refused to believe us. some probably still don't.

it would be awesome, though, if people would actually appreciate that to get *there* (4.0.x, 4.1) we had to start *here* (4.0.0). every journey of a thousand miles starts with a single step, and try as you might you can't avoid the first step. if you do, your second step becomes the first step and really, you can only skips so many steps before you run out of leaping power.



that's fine; different people will come along at different points in time. saying "it's not ready for me" can be useful if you can enunciate exactly what is missing for you (no, it's not always obvious, we aren't mind readers) and even more so if you can get involved and help push things forward directly.

when we get over these various humps, the number of things people will have left to complain about will start to approach zero (it's a limit, not a solution and all this will be behind us.