You did not look very close?
See https://bugs.kde.org/show_bug.cgi?id=220047
Yes, but no. Yes, it looks very close to dozens of KDE and downstrem/distro
bugs!
It's actually
https://bugs.kde.org/show_bug.cgi?id=268038
And it was fixed (thanks, mikala!) by releasing of
ntrack-014-3.mga2 !!!
2011/7/4 Radu-Cristian FOTESCU beranger...@yahoo.ca:
You did not look very close?
See https://bugs.kde.org/show_bug.cgi?id=220047
Yes, but no. Yes, it looks very close to dozens of KDE and downstrem/distro
bugs!
It's actually
https://bugs.kde.org/show_bug.cgi?id=268038
And it was fixed
Not so fast! :(
It's nice that you are happy. But since last updates my windows do not
have any decorations (no border, no title bar, no chance to
close/minimize/maximize), konsole window does not get focus at all,
after reboot I see all decorations for a split
Not so fast! :(
It's nice that you are happy. But since last updates my windows do not
have any decorations (no border, no title bar, no chance to
close/minimize/maximize), konsole window does not get focus at all,
after reboot I see all decorations for a split second, then they
vanish from the
2011/7/4 Radu-Cristian FOTESCU beranger...@yahoo.ca:
Not so fast! :(
It's nice that you are happy. But since last updates my windows do not
have any decorations (no border, no title bar, no chance to
close/minimize/maximize), konsole window does not get
2011/7/4 Radu-Cristian FOTESCU beranger...@yahoo.ca:
[...]
Oh, I see that kdebase4-runtime-4.6.90-4.mga2 was also updated, but I believe
this update doesn't change anything (adding ntrack as a Requires is IMHO
useless as it was installed anyway, and removing it was and it's still
2011/7/4 John Balcaen mik...@mageia.org:
2011/7/4 Radu-Cristian FOTESCU beranger...@yahoo.ca:
[...]
Oh, I see that kdebase4-runtime-4.6.90-4.mga2 was also updated, but I
believe this update doesn't change anything (adding ntrack as a Requires is
IMHO useless as it was installed anyway,
2011/7/4 Wolfgang Bornath molc...@googlemail.com:
2011/7/4 John Balcaen mik...@mageia.org:
[...]
Hmm, I saw the new ntrack update coming in 3 days ago but it did not
fix the cpu load issue here!
Because ntrack was not installed in fact, kdebase4-runtime requires
should fix it.
I just created
It's not useless at all in fact. kdebase4-runtime was ony pulling by
internal requires lib(64)ntrack0 lib(64)ntrack-qt4
using only the « built-in noop monitor (always online).», i did not
notice only yesterday night that his package was installed locally
(ntrack binary which provides
you can reproduce it by removing with --no-deps ntrack restart your
kde session
You mean one could have been running kded4 --no-deps ntrack and experience no
CPU issues even w/o these updates?!
Geez, how would a regular user know that --no-deps ntrack was a valid
parameter?
R-C
2011/7/4 John Balcaen mik...@mageia.org:
2011/7/4 Wolfgang Bornath molc...@googlemail.com:
2011/7/4 John Balcaen mik...@mageia.org:
[...]
Hmm, I saw the new ntrack update coming in 3 days ago but it did not
fix the cpu load issue here!
Because ntrack was not installed in fact,
2011/7/4 Radu-Cristian FOTESCU beranger...@yahoo.ca:
you can reproduce it by removing with --no-deps ntrack restart your
kde session
You mean one could have been running kded4 --no-deps ntrack and experience
no CPU issues even w/o these updates?!
Arrf! I misunderstood that part about
Then I moved the complete ~/.kde4 to a backup place and restarted with
my normal user - back to the problem! :(
I will create a new normal user and then compare ~/home entries.
I'm currently experiencing a similar situation with XFCE: it's broken all of a
sudden, no titlebars, no focus in any
2011/7/4 Radu-Cristian FOTESCU beranger...@yahoo.ca:
you can reproduce it by removing with --no-deps ntrack restart your
kde session
You mean one could have been running kded4 --no-deps ntrack and experience
no CPU issues even w/o these updates?!
Geez, how would a regular user know that
2011/7/4 Wolfgang Bornath molc...@googlemail.com:
2011/7/4 John Balcaen mik...@mageia.org:
2011/7/4 Wolfgang Bornath molc...@googlemail.com:
2011/7/4 John Balcaen mik...@mageia.org:
[...]
Hmm, I saw the new ntrack update coming in 3 days ago but it did not
fix the cpu load issue here!
2011/7/4 John Balcaen mik...@mageia.org:
2011/7/4 Wolfgang Bornath molc...@googlemail.com:
2011/7/4 John Balcaen mik...@mageia.org:
2011/7/4 Wolfgang Bornath molc...@googlemail.com:
2011/7/4 John Balcaen mik...@mageia.org:
[...]
Hmm, I saw the new ntrack update coming in 3 days ago but it
2011/7/4 Radu-Cristian FOTESCU beranger...@yahoo.ca:
But removing ntrack does not fix anything! (CPU 100%) Maybe removing
libtrack0?
I said that you'll be able to reproduce the 100% CPU usage by kded4 if
the ntrack package is removed.
--
Balcaen John
Jabber-id:
On Monday, July 04, 2011 05:10:24 am Radu-Cristian FOTESCU wrote:
It's not useless at all in fact. kdebase4-runtime was ony pulling by
internal requires lib(64)ntrack0 lib(64)ntrack-qt4
using only the « built-in noop monitor (always online).», i did not
notice only yesterday night that
2011/7/4 Thomas Spuhler tho...@btspuhler.com
On Monday, July 04, 2011 05:10:24 am Radu-Cristian FOTESCU wrote:Same here,
after installing ntrack, logging out and loggin in tagain the kde4
cpu sage went to 0 = zero
--
Thomas
dito here 64-bit system
well done :-)
Magnus
It looks like the kded4 high-CPU is _not_ related to any of the following
modules:
bluedevil
desktopnotifier
device_automounter
dnssdwatcher
favicons
freespacenotifier
keyboard
khotkeys
kmixd
ksvnd
ktimezoned
kwrited
networkstatus
obexftpdaemon
powerdevil
randrmonitor
remotedirnotify
Op zondag 03 juli 2011 21:40:53 schreef Radu-Cristian FOTESCU:
[..]
I started to lose my confidence in the IQ of the Linux users...
really? the users? i wonder what those users IQ have to do with KDE4
taking too much CPU?
perhaps most users don't even care? with their quad and hexa-cored
So you should disable all kded modules (from systemsettings), then log off
(or even restart to be sure no process is left running) then log back on. If
you still get high CPU from kded then ths problem is in kded itself, if not
you can start loading the modules one by one (waiting long enough
2011/7/3 Radu-Cristian FOTESCU beranger...@yahoo.ca:
Is kded4 broken? How come there is no upstream report about kded4's high CPU
usage?
You did not look very close?
See https://bugs.kde.org/show_bug.cgi?id=220047
Funny thing: it already started in December 2009 with 4.3 !
--
wobo
On Saturday 02 July 2011 09:45:15 Wolfgang Bornath wrote:
[...]
Did that (after installing all updates up to 07:00 UTC), no signs of
any I/O activity other than the usual. Still, one of the 4 cores is on
full load. What strikes me here is:
- on a CPU with 1 core, this is fully loaded
- on a
2011/7/2 Balcaen John mik...@mageia.org:
On Saturday 02 July 2011 09:45:15 Wolfgang Bornath wrote:
[...]
Did that (after installing all updates up to 07:00 UTC), no signs of
any I/O activity other than the usual. Still, one of the 4 cores is on
full load. What strikes me here is:
- on a CPU
Op vrijdag 01 juli 2011 07:40:24 schreef Radu-Cristian FOTESCU:
I was trying to investigate the kded4 high CPU load, and I started to
investigate some upstream reports, even if not necessarily reported for
4.6.90.
Some such reports were related to ntrack, e.g. http://bugs.kde.org/268038
afaik ntrack, if that is a problem, why don't you try and recompile KDE
locally without ntrack? see if it improves stuff?
But _why_ is ntrack a *required* dependency of KDE as long as:
1. other distros don't have it, neither as required by KDE, nor as an
independent library;
2. It is
macro_log_feature(QNTRACK_FOUND QNtrack Network status tracking library
http://launchpad.net/ntrack;; FALSE Provides data input for Solid network
status)
We're just trying to provide our KDE with as much as functionnality as it's
possible.
OK, OK, OK (Leo Getz / Joe Pesci voice).
Some
2011/7/1 Radu-Cristian FOTESCU beranger...@yahoo.ca:
macro_log_feature(QNTRACK_FOUND QNtrack Network status tracking library
http://launchpad.net/ntrack;; FALSE Provides data input for Solid network
status)
We're just trying to provide our KDE with as much as functionnality as it's
possible.
On Friday 01 July 2011 03:56:21 Radu-Cristian FOTESCU wrote:
macro_log_feature(QNTRACK_FOUND QNtrack Network status tracking
library http://launchpad.net/ntrack;; FALSE Provides data input for
Solid network status)
We're just trying to provide our KDE with as much as functionnality as
it's
2011/7/1 Radu-Cristian FOTESCU beranger...@yahoo.ca:
[...]
It's not the packager, it's the policy. Adding something just because
upstream has provided an optional dependency...
So then how are you going to test the functionality without testing it ?
Even if we're not going to keep it why
On Fri, 1 Jul 2011, John Balcaen wrote:
2011/7/1 Radu-Cristian FOTESCU beranger...@yahoo.ca:
[...]
It's not the packager, it's the policy. Adding something just because upstream
has provided an optional dependency...
So then how are you going to test the functionality without testing it ?
On Friday 01 July 2011 05:26:19 Radu-Cristian FOTESCU wrote:
So then how are you going to test the functionality without testing it ?
So what am I supposed to be testing? Apart that it doesn't kill my CPU, and
that packaging etc. is correct, what is the _functionality_ to be tested?
It's
ntrack is supposed to provide more information regarding connection/route
change for desktop applications such so we'll probably see
applications or developpers used it later. If we can provide by default
an environnement so developers can use it (aka no need to
recompile/add 'x' br)
2011/7/1 Radu-Cristian FOTESCU beranger...@yahoo.ca:
This is making me crazy. After upgrading to KDE 4.6.90 (cauldron, of
course), the bloody m*f*er kded4 (the worse idea in KDE4) constantly takes
55-75% CPU.
Of course, killing it is possible, but this affects the plasmoids. (E.g. it
made me
On Fri, 1 Jul 2011, Radu-Cristian FOTESCU wrote:
Now, it's tough to determine what exactly is making kded4 to eat the
CPU. As I'm having a single core, I'm burned. At the same time, minor
changes that are actually small improvements make me want to stay with
4.6.90, not to revert to 4.6.4
One way to figure that out is to attach gdb to it while it's running and
then print a backtrace. If you do that several times, you may break in the
code
that's running a lot. But even if that works it is likely still not easy to
figure out what's going on.
Other ways to get
This is making me crazy. After upgrading to KDE 4.6.90 (cauldron, of course),
the bloody m*f*er kded4 (the worse idea in KDE4) constantly takes 55-75% CPU.
Of course, killing it is possible, but this affects the plasmoids. (E.g. it
made me inadvertently filling an invalid bug report 1981, which
On Thu, Jun 30, 2011 at 19:34, Radu-Cristian FOTESCU
beranger...@yahoo.cawrote:
This is making me crazy. After upgrading to KDE 4.6.90 (cauldron, of
course), the bloody m*f*er kded4 (the worse idea in KDE4) constantly takes
55-75% CPU.
Of course, killing it is possible, but this affects the
The solution which worked most of the time for such issues in kde 4.6.xx was:
1. open a terminal
2. run killall plasma-desktop
3. plasma-desktop
the plasmoids and the desktop come back, and kded4 stops using that much CPU.
Last time I looked what it was looking CPU at, it was caused by
On Thursday 30 June 2011 15:34:50 Radu-Cristian FOTESCU wrote:
This is making me crazy. After upgrading to KDE 4.6.90 (cauldron, of
course), the bloody m*f*er kded4 (the worse idea in KDE4) constantly takes
55-75% CPU.
Of course, killing it is possible, but this affects the plasmoids. (E.g.
On Thursday 30 June 2011 16:10:46 Radu-Cristian FOTESCU wrote:
[...]
Now, I know my KDE is somewhat b0rken, because akonadiserver can't start --
but I could live just fine this way in KDE 4.6.3-4.6.4, if not even better
than with it.
Well only kdepim is broken so it's not a big deal if you're
Le 2011-06-30 18:34, Radu-Cristian FOTESCU a écrit :
This is making me crazy. After upgrading to KDE 4.6.90 (cauldron, of
course), the bloody m*f*er kded4 (the worse idea in KDE4) constantly
takes 55-75% CPU.
Of course, killing it is possible, but this affects the plasmoids. (E.g.
it made me
On Thursday, June 30, 2011 05:23:58 pm Marc Paré wrote:
Le 2011-06-30 18:34, Radu-Cristian FOTESCU a écrit :
This is making me crazy. After upgrading to KDE 4.6.90 (cauldron, of
course), the bloody m*f*er kded4 (the worse idea in KDE4) constantly
takes 55-75% CPU.
Of course, killing it
(This is making me crazy. Otherwise, I'll tell you some day about a
bug/crash that was *accidentally* fixed by KDE 4.6.90.)
Which one ? ;o)
See
https://mageia.org/pipermail/mageia-dev/2011-July/006180.html
R-C
Could it be that it is indexing all of your files?
NOPE. I never ever use indexing, no matter what the OS is.
R-C
Well only kdepim is broken so it's not a big deal if you're not using
it.
(You should be able to use akregator).
Yes, akregator works just fine.
R-C
However here killing this process does not seems to affect my plasmoids.
I'm surprised to see you writing it. After killing kded4:
1. Klipper was not reacting.
2. The keyboard layout systray icon was dead.
3. Any changes in the way the clock is displayed (hour/date format) were not
applied.
I was trying to investigate the kded4 high CPU load, and I started to
investigate some upstream reports, even if not necessarily reported for 4.6.90.
Some such reports were related to ntrack, e.g. http://bugs.kde.org/268038
What the heck is ntrack and why do we need it? (The official
2011/7/1 Marc Paré m...@marcpare.com
Mine was doing this and I tried to stop it (I don't really know how to do
this), so in the end I let it go. It has now stopped. Could it be that it is
indexing all of your files? I know that I have 600 gigs of data, and, if
KDE4 was trying to index all of
50 matches
Mail list logo
