[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 246678] virtuoso: Usage of CPU is much too high
From:       Martin L ü c h e m <Heinrich20 () gmx ! de>
Date:       2012-01-17 13:19:24
Message-ID: E1Rn8we-0007Gu-Bw () bugs ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=246678





--- Comment #124 from Martin L ü c h e m <Heinrich20 gmx de>  2012-01-17 13:19:23 ---
Sven, 

I can see, what you pointed out. This is, what happened within the GMX client
and I did not take care about. Sorry for that! But anyway, when we start to
discuss about quoting like that or not, the way we communicate has reached a
quality that not at all helps to solve the problem.

Two things where I wonder, how to improve the situation out of the persepctive
(=role) of a user:

1. Debugging as described by your link is far too complicated to make that
happen by a user.

2. How an where would I start? When would I start debugging? Which application
to debug first. This is not cynism, I do think this to be a real problem for
users.

/Off-Topic
Even though we are "only" users of KDE/Linux we do a real hard job. We stay on
a platform (in case of KDE 4.x) that is shipped with Ubuntu but is really far
away from being stable. If e.g. I try to write bug reports I even run into
problems with that because I  c a n n o t  describe the bug itself appearing in
a very complex system environment that is far to complecated. See 1. So by the
time you wonder what you could do and find out: nothing!
/

Regards, Martin

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]