Linked by Thom Holwerda on Thu 13th Oct 2011 21:33 UTC, submitted by mahmudinashar
Thread beginning with comment 493240
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2007-12-10
Of course it's not proof, and the whole point of the stack is that you start at the top. As I said: blame starts at the top. You start with the thing that crashed, let the maintainer of that software figure out the root cause.
More to the point, just check out the current bugs filed against Dr Konqi: https://bugs.kde.org/buglist.cgi?quicksearch=drkonqi
There are several yet-to-be-fixed crashers there. To assume that the KDE software is free of bugs is just supremely naive.