Linked by Thom Holwerda on Thu 13th Oct 2011 21:33 UTC, submitted by mahmudinashar
Ubuntu, Kubuntu, Xubuntu Ah, it's that time of the year again. We already had this up on the sidebar, but I figured we'd turn it into a proper front page item - mostly because I want to discuss the move by the Ubuntu team to no longer install GNOME 2 as the 'classic' desktop option - which pretty much ends any and all involvement for me with Ubuntu (KDE 4 here I come). There's more to this than just that, of course, so those of you who do like Unity still have enough reason to upgrade.
Thread beginning with comment 493238
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: Sigh...
by saynte on Mon 17th Oct 2011 10:34 UTC in reply to "RE[5]: Sigh..."
saynte
Member since:
2007-12-10

That is possible, of course, that the crash triggered some fundamental bug somewhere lower in the stack. However, usually the blame should work top-down, not bottom-up.

If kMail happens to crash, do you immediately file a bug against the kernel, or let Intel/AMD they have a bug in their CPU? Of course not, you first blame kMail, then if the maintainer can show that it's somewhere in a library he/she passes down the stack so it can be fixed.

Thom (quite likely) found a few bugs in KDE, denying this won't help anything.

Reply Parent Score: 1

RE[7]: Sigh...
by lemur2 on Mon 17th Oct 2011 11:17 in reply to "RE[6]: Sigh..."
lemur2 Member since:
2007-02-17

That is possible, of course, that the crash triggered some fundamental bug somewhere lower in the stack. However, usually the blame should work top-down, not bottom-up.

If kMail happens to crash, do you immediately file a bug against the kernel, or let Intel/AMD they have a bug in their CPU? Of course not, you first blame kMail, then if the maintainer can show that it's somewhere in a library he/she passes down the stack so it can be fixed.

Thom (quite likely) found a few bugs in KDE, denying this won't help anything.


Au contraire, it is clear that no such bug exists on any of my systems, which are running the same version of KDE. None of my systems exhibit anything like the behaviour which Thom describes.

All of my well-behaved, bug-free systems and Thom's system have KDE (and KDE applications) in common.

The only thing that sets Thom's system apart is "somewhere lower in the stack".

This observation is not proof, but nevertheless it is a strong indication that the fault on Thom's system does indeed lie "somewhere lower in the stack". Certainly, given all the described symptoms (and lack thereof on other systems), that is the first place I would look.

Reply Parent Score: 2

RE[8]: Sigh...
by saynte on Mon 17th Oct 2011 11:27 in reply to "RE[7]: Sigh..."
saynte 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.

Reply Parent Score: 1