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 493279
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Sigh...
by lemur2 on Mon 17th Oct 2011 22:41 UTC in reply to "RE[6]: Sigh..."
lemur2
Member since:
2007-02-17

You are reading a techie website yet you seem to have little understanding of what could make software unstable. The problem with trying to force your opinions on others is additional frustration as now not only do they have to work through issues with KDE they also have to put up with people repeatedly saying "Well it works fine here so you must be wrong". At best you could encourage people who are having issues to raise a bug report and if many people chime in with evidence of the problem it will probably be confirmed and then fixed.


Indeed. There is plenty of scope for the bug in Thom's system to be amongst one of these:

http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/_kernel_on...

... most of which, on the face of it, have nothing to do with KDE4.

At worst (what you are currently doing) is just denying the possibility that although something works for you it may not work for others.


We are discussing the most likely location for bugs on Thom's system.

How is this in any way denying that Thom's system is not working?

Edited 2011-10-17 22:42 UTC

Reply Parent Score: 2

RE[8]: Sigh...
by aaronb on Tue 18th Oct 2011 17:30 in reply to "RE[7]: Sigh..."
aaronb Member since:
2005-07-06

How is this in any way denying that Thom's system is not working?


The below quotes from your posts are irrelevant when attempting to understand the root cause of a issue with a system that you do not own, we know your systems work fine and do not require further pointless repetition:

I can't think what you are doing wrong, it is beyond me. GNOME does include a number of work-arounds for parts of the kernel/driver stack that are supposed to work (but don't always). I don't believe that KDE does include kludges and work-arounds of this nature.

I, for example, have had no such trouble when running .x versions of KDE4 where x=2,4,6 or 7 (minor trouble with x=2 and 5), all on various different hardware configurations, using various different drivers, using various different distributions.

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.


Edited 2011-10-18 17:36 UTC

Reply Parent Score: 2

RE[9]: Sigh...
by lemur2 on Tue 18th Oct 2011 22:10 in reply to "RE[8]: Sigh..."
lemur2 Member since:
2007-02-17

How is this in any way denying that Thom's system is not working?
The below quotes from your posts are irrelevant when attempting to understand the root cause of a issue with a system that you do not own, we know your systems work fine and do not require further pointless repetition: I can't think what you are doing wrong, it is beyond me. GNOME does include a number of work-arounds for parts of the kernel/driver stack that are supposed to work (but don't always). I don't believe that KDE does include kludges and work-arounds of this nature. ...


So ... Thom submits a bug report to the KDE team. The bug report says this: "the crash handler crashes".

KDE devs say ... "Ran crash handler, could not duplicate. No fault found. Can you please provide more info on your system so that this bug can be duplicated"?

... and straight away we are into debigging the underlying layers of Thom's system.

After receiving information on Thom's system the root cause is investigated, and KDE devs say ... "Problem reported to downstream developers".

Sigh!

Edited 2011-10-18 22:13 UTC

Reply Parent Score: 2