Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 !!! The latest ntrack update was meant to fix https://bugs.mageia.org/show_bug.cgi?id=1976 by applying an upstream patch for https://bugs.launchpad.net/ntrack/+bug/750554 However, this also fixed https://bugs.launchpad.net/ntrack/+bug/755608 in the process. Case closed. Happy happy happy! R-C aka beranger
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 (thanks, mikala!) by releasing of ntrack-014-3.mga2 !!! The latest ntrack update was meant to fix https://bugs.mageia.org/show_bug.cgi?id=1976 by applying an upstream patch for https://bugs.launchpad.net/ntrack/+bug/750554 However, this also fixed https://bugs.launchpad.net/ntrack/+bug/755608 in the process. Case closed. 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 screen, only the windows stay. Then after 10 seconds the complete task bar of KDE vanishes, such keybindings like Alt+F2 or Ctrl+TAB do not work at all, etc. Total failure at the moment. xsession_errors shows lots of errors, I can not distinguish which is related. -- wobo
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 screen, only the windows stay. Then after 10 seconds the complete task bar of KDE vanishes, such keybindings like Alt+F2 or Ctrl+TAB do not work at all, etc. Total failure at the moment. xsession_errors shows lots of errors, I can not distinguish which is related. OUCH! wobo, the gods don't love you! However, by no means can this be related to ntrack! I have never encountered such a syndrome in KDE4, only in XFCE, but this can't be related. Using a different user acct helps or it doesn't help? R-C aka beranger
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 screen, only the windows stay. Then after 10 seconds the complete task bar of KDE vanishes, such keybindings like Alt+F2 or Ctrl+TAB do not work at all, etc. Total failure at the moment. xsession_errors shows lots of errors, I can not distinguish which is related. 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 impossible, should you want to use KDE), and it also should not affect KDE. Are you using a reliable mirror? I updated from distrib-coffee.ipsl.jussieu.fr. R-C
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 focus at all, after reboot I see all decorations for a split second, then they vanish from the screen, only the windows stay. Then after 10 seconds the complete task bar of KDE vanishes, such keybindings like Alt+F2 or Ctrl+TAB do not work at all, etc. Total failure at the moment. xsession_errors shows lots of errors, I can not distinguish which is related. OUCH! wobo, the gods don't love you! However, by no means can this be related to ntrack! I have never encountered such a syndrome in KDE4, only in XFCE, but this can't be related. Using a different user acct helps or it doesn't help? R-C aka beranger Yes, trying with xguest (the first I did after experiencing the problem) showed normal behavior. 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. Oh! I just saw that the taskbar is not gone, it is hidden! When I move the mouse to the places where the menue and other standard items are located I can click and use these icons! Next: I suddenly get a message about Nepomuk and after that the taskbar is visible again! But no window borders nor decorations! This is weird - I'll come back after I created a new user. -- wobo
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 impossible, should you want to use KDE), and it also should not affect KDE. 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 /usr/lib(64)/ntrack/modules/ntrack-libnl1.so. Also it's strange that kded4 was fixed for you only today since i pushed the new ntrack 3 days ago when i noticed it the kde's bug you're referring in the last mail. -- Balcaen John Jabber-id: mik...@jabber.littleboboy.net
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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, and removing it was and it's still impossible, should you want to use KDE), and it also should not affect KDE. 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 /usr/lib(64)/ntrack/modules/ntrack-libnl1.so. Also it's strange that kded4 was fixed for you only today since i pushed the new ntrack 3 days ago Hmm, I saw the new ntrack update coming in 3 days ago but it did not fix the cpu load issue here! when i noticed it the kde's bug you're referring in the last mail. I just created a new normal user with same standard values as my main user - KDE desktop works ok. htop shows no unusual cpu load. So, I have to find out what makes the difference. -- wobo
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 a new normal user with same standard values as my main user - KDE desktop works ok. htop shows no unusual cpu load. So, I have to find out what makes the difference. for the kded usage, the fact that ntrack is now required. you can reproduce it by removing with --no-deps ntrack restart your kde session -- Balcaen John Jabber-id: mik...@jabber.littleboboy.net
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 /usr/lib(64)/ntrack/modules/ntrack-libnl1.so. Also it's strange that kded4 was fixed for you only today since i pushed the new ntrack 3 days ago when i noticed it the kde's bug you're referring in the last mail. mikala, I believe I've got it. I was only having libntrack0 installed, but not ntrack. Therefore, no matter a new ntrack was released on July 1, I wasn't getting it anyway. It was kdebase4-runtime-4.6.90-4.mga2, released today, July 4, that brought as a dependency the new ntrack! Fabulous. (Still, I'm wondering why Fedora Rawide doesn't use ntrack at all.) Thanks, R-C aka beranger
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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, kdebase4-runtime requires should fix it. I just created a new normal user with same standard values as my main user - KDE desktop works ok. htop shows no unusual cpu load. So, I have to find out what makes the difference. for the kded usage, the fact that ntrack is now required. you can reproduce it by removing with --no-deps ntrack restart your kde session # urpme --no-deps ntrack --no-deps: unknown option Then it wants to remove all of 128 packages (kdebase4-runtime and all dependencies, in short: almost complete KDE) Anyhow, I thought the problems I have with my main user would be related to the new kdebase4-runtime version. If they are not, I'm stuck. -- wobo
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 removing! -- wobo
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 window, it's totally unusable. Creating a different user shows that XFCE is not broken. However, deleting ~/.config/xfce4 and ~/.cache for my current user does not help, XFCE is still unusable. What else to delete? There is no ~/.xfce4 directory! This might be the last time I was using that piece of crap called XFCE... R-C
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 --no-deps ntrack was a valid parameter? it was a rpm command aka remove the ntrack package with --nodeps aka rpm -e --nodeps ntrack not running kded4 whith thoses argument. -- Balcaen John Jabber-id: mik...@jabber.littleboboy.net
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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! Because ntrack was not installed in fact, kdebase4-runtime requires should fix it. I just created a new normal user with same standard values as my main user - KDE desktop works ok. htop shows no unusual cpu load. So, I have to find out what makes the difference. for the kded usage, the fact that ntrack is now required. you can reproduce it by removing with --no-deps ntrack restart your kde session # urpme --no-deps ntrack --no-deps: unknown option Then it wants to remove all of 128 packages (kdebase4-runtime and all dependencies, in short: almost complete KDE) urpmi does not support --no-deps ,i was referring to « rpm » directly. -- Balcaen John Jabber-id: mik...@jabber.littleboboy.net
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 did not fix the cpu load issue here! Because ntrack was not installed in fact, kdebase4-runtime requires should fix it. I just created a new normal user with same standard values as my main user - KDE desktop works ok. htop shows no unusual cpu load. So, I have to find out what makes the difference. for the kded usage, the fact that ntrack is now required. you can reproduce it by removing with --no-deps ntrack restart your kde session # urpme --no-deps ntrack --no-deps: unknown option Then it wants to remove all of 128 packages (kdebase4-runtime and all dependencies, in short: almost complete KDE) urpmi does not support --no-deps ,i was referring to « rpm » directly. Warning! Extensive usage of urpmi may lead to dumb usage of rpm! man rpm says: rpm -e --nodeps package_name :) Anyhow, it is not related to the problem I have. -- wobo
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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: mik...@jabber.littleboboy.net
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 his package was installed locally (ntrack binary which provides /usr/lib(64)/ntrack/modules/ntrack-libnl1.so. Also it's strange that kded4 was fixed for you only today since i pushed the new ntrack 3 days ago when i noticed it the kde's bug you're referring in the last mail. mikala, I believe I've got it. I was only having libntrack0 installed, but not ntrack. Therefore, no matter a new ntrack was released on July 1, I wasn't getting it anyway. It was kdebase4-runtime-4.6.90-4.mga2, released today, July 4, that brought as a dependency the new ntrack! Fabulous. (Still, I'm wondering why Fedora Rawide doesn't use ntrack at all.) Thanks, R-C aka beranger Same here, after installing ntrack, logging out and loggin in tagain the kde4 cpu sage went to 0 = zero -- Thomas
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 solidautoeject statusnotifierwatcher I have used qdbus org.kde.kded /kded unloadModule to unload, one by one, each and every module, until qdbus org.kde.kded /kded loadedModules listed nothing. So even with no loaded module, kded4 is taking too much CPU. Is kded4 broken? How come there is no upstream report about kded4's high CPU usage? I started to lose my confidence in the IQ of the Linux users... R-C aka beranger
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 monsters... get your priorities straight, man; you sound like you're the single most important person in the universe, it pisses me off...
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 between each) to identify which one will start eating the CPU. I did that. Unfortunately, I cannot stop from the KDE Services Configuration dialog: favicons Also, no matter I have disabled _all_ the Startup Services in KDE, the following are automatically started: networkstatus desktopnotifier ktimezoned So these are the 4 services whose modules I can only unload using qdbus. But if I unload them and kill kded4, not only I can't find ant process whose name suggests that any of them would be running, but also the CPU usage drops to 2-3%. Restarting kded4 automatically loads networkstatus... and the CPU goes mad! Is networkstatus the culprit? R-C aka beranger
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 dual core CPU only 1 core is loaded - on a quadcore CPU only 1 core is loaded. So, whatever it is, it affects only one CPU core no matter how many cores the CPU offers. Kded is not taking 100% of one core here since the ntrack update. Did you try eventually to unload modules from kcmshell4 kcmkded ? (especially the Network Status module which should be related to the ntrack process) Regards, -- Balcaen John Jabber ID: mik...@jabber.littleboboy.net
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 with 1 core, this is fully loaded - on a dual core CPU only 1 core is loaded - on a quadcore CPU only 1 core is loaded. So, whatever it is, it affects only one CPU core no matter how many cores the CPU offers. Kded is not taking 100% of one core here since the ntrack update. Did you try eventually to unload modules from kcmshell4 kcmkded ? (especially the Network Status module which should be related to the ntrack process) No, I did not alter anything. ATM I do not work with Cauldron, I only do the updates and watch. Except for such special cases, where I do something to give output to you :) I'm using gkrellm as rough information, so I know that in my i3 CPU only one core is affected (which changes from one core to another occasionally) As kmail crashes right at the start (reproducible) and takes the whole kontact down with it, I couldn't use the system anyway. -- wobo
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 What the heck is ntrack and why do we need it? (The official description tells me exactly nothing). There is *no* ntrack in either of Mandriva or Fedora -- it's actually likely to be an Ubuntu project; either way, it's definitely *not* part of the KDE4 project, as it's hosted on https://launchpad.net/ntrack Then why the heck removing libntrack0 wants to remove *all* the KDE??? Is Mageia becoming Kubuntu? All these excessive dependencies are making me sick. Everything depends on everything. Is dynamic loading of libraries, with dynamically getting pointers to functions and using them or not, depending on availability, a mechanism that only works in Windows? Then, you'll excuse me, for the fist time in 9 days, I'll reboot into XP SP3. And I'm doing that because, after having rebooted in F15, their plasma (4.6.3) crashed on me for 3 times in 5 minutes. This is unbearable. Pissed off, R-C aka beranger dude, it kind of pisses me off what i read here... you're using cauldron; it's nice that you find these bugs so they can be fixed, but i mean... it's cauldron, imho you can't expect s stable state in our development version... so please, do what everyone else does in cauldron: - use another DE if the current one is unworkable. afaik ntrack, if that is a problem, why don't you try and recompile KDE locally without ntrack? see if it improves stuff?
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 obviously *not* part of the KDE project. No, I can't recompile KDE with my Celeron M-520, I am not suicidal. R-C
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 Debian KDE guy managed to add an optional QNTrack backend to the solid-networkstatus kded module, almost nobody knows exactly what this is good at, yet top-notch, bleeding-edge distros (but not Fedora rawhide) adds this Kubuntu-derived dependency, right? http://lists.kde.org/?l=kde-commitsm=128570600407656w=2 Cool. I can hardly wait until KDE5 gets GNOME4 dependencies. R-C
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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. OK, OK, OK (Leo Getz / Joe Pesci voice). Some Debian KDE guy managed to add an optional QNTrack backend to the solid-networkstatus kded module, almost nobody knows exactly what this is good at, yet top-notch, bleeding-edge distros (but not Fedora rawhide) adds this Kubuntu-derived dependency, right? Did you really read my mail about *testing* eventually removing thoses dependency non useful/problematic BR ? Or it is just the way you're used to talk without any consideration for the packager? -- Balcaen John Jabber-id: mik...@jabber.littleboboy.net
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 possible. OK, OK, OK (Leo Getz / Joe Pesci voice). Some Debian KDE guy managed to add an optional QNTrack backend to the solid-networkstatus kded module, almost nobody knows exactly what this is good at, yet top-notch, bleeding-edge distros (but not Fedora rawhide) adds this Kubuntu-derived dependency, right? Did you read my whole mail or are you just quoting something to start a flamewar ? -- Balcaen John Jabber ID: mik...@jabber.littleboboy.net
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 should not we test it on cauldron since cauldron is cauldron ? -- Balcaen John Jabber-id: mik...@jabber.littleboboy.net
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 ? AFAICT the question was: what is this added functionality? Did this kde4 component not get network status updates and now it does get them through the library? Christiaan
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 not documented, not even upstream. Just a commit from last September. Even if we're not going to keep it why should not we test it on cauldron since cauldron is cauldron ? Cauldron or not, what can be tested in an addition that nobody knows what functionality it's _supposed_ to bring? [...] 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) if it's not a burden for end users why not providing it ? As i said earlier it's cauldron, so we can add it remove build dependency even more use it to report bug upstream if something is broken /not working as expected. From my point of view it's allow us to have eventually more interaction from upstream as a distribution trying to follow upstream as much as possible then probably get more developers using our distribution. Anyway it just seems Not to minimize your work as a packager. But I _feel_ (I didn't say _believe_) that, with huge projects such as KDE4, adding a non-mandatory dependency should be pondered on more carefully that with small projects -- because of the impact. Well i guess it was a little bit tested before getting merged in kde master even as an optionnal buildrequires. if it was such problematic i guess it would not have been merged or dropped after... -- Balcaen John Jabber ID: mik...@jabber.littleboboy.net
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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) if it's not a burden for end users why not providing it ? Thank you. It makes sense. However, it's very frustrating that the upstream doesn't bother to document what's new in such a release, being it an RC. They didn't even bother to list the most important bugs that are fixed (although I also suspect some bugs vanished as a side effect of some changes). 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 R-C
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 inadvertently filling an invalid bug report 1981, which disappeared once I let kded4 live.) Really, isn't anybody experiencing high CPU from kded4? I experience the same problem. kded4 uses 50% of my dual core CPU (so, one core I suppose). Killing kded4 using kill -9 `pidof kded4` and launching it again fixed it (temporarily I guess). Rémi / Akien
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 information would be to strace (or ltrace) this daemon to get an idea what it's trying to do. But CPU usage by the application itself cannot be seen this way. An easier way to start is to run iotop and check if kded4 is doing any I/O related to this cpu usage. Christaan
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 information would be to strace (or ltrace) this daemon to get an idea what it's trying to do. But CPU usage by the application itself cannot be seen this way. An easier way to start is to run iotop and check if kded4 is doing any I/O related to this cpu usage. Well, thanks for the ideas. As long as it takes at least 55% of the CPU anyway, this is going to be quite cumbersome, and I have some other (productive) tasks to do, so I don't expect to investigate this before Sunday night. R-C
[Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 disappeared once I let kded4 live.) Really, isn't anybody experiencing high CPU from kded4? (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.) Thanks, R-C aka beranger
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 plasmoids. (E.g. it made me inadvertently filling an invalid bug report 1981, which disappeared once I let kded4 live.) 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 some run-away timer loop deep in kdelibs, but as those issues are quite random I haven't figured out what exactly causes this. -- Eugeni Dodonov http://eugeni.dodonov.net/
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 some run-away timer loop deep in kdelibs, but as those issues are quite random I haven't figured out what exactly causes this. Евгений, thank you, but this is not a solution. It is not a solution because, as soon as plasma-desktop is back, kded4 takes the same 55...75% CPU. It is not a solution because, even if it were a temporary fix, it needed to be run after each and every login. 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. So I should report this as a bug, however I won't do it as long as I'm the only Cauldron user to experience it. OTOH, let me tell you how to crash *any* KDE4 version (have to report it upstream, works on F15 too): 1. Folder View for the Desktop. 2. Click on a desktop icon, F2 (rename), select the text, right-click (as a reflex to find a menu with Copy); 3. plasma-desktop glorious crash. Here's the KDE bug that was fixed by accident in KDE 4.6.90: Upstream bug 235020, with duplicates 228036, 236800, 256257, 255393, 256993, 257591, 262912, 264287, 264664, 265064, 265823, 266245, 270591, 272198, 272662, 274792, 274135, 274659, 275301, 275906, 275906, 276020, 276261. In short: KCharSelect crashes in some circumstances. How to make KCharSelect crash on any version up to and including 4.6.4: 1. Open KCharSelect and make it have the minimum horizontal size (it should display 18 characters on a row; if it doesn't, keep it at this size nevertheless); 2. Select the DejaVu Sans or any other DejaVu typeface. 3. Keep European Alphabets in the first drop-down list. 4. In the second drop-down list, start to switch the code pages between the available ones, in order: -- Basic Latin -- Latin-1 Supplement -- Latin Extended A -- Latin Extended B -- Latin Extended Additional -- Latin Extended C -- Latin Extended D and so on. 5. It should have crashed by now. If not, keep switching back and forth between the code pages until it does! The bug is actually triggered by unknown errors in some fonts (the DejaVu family being one of them). It's funny to use KDE4 (I was a GNOME guy, that is, until GNOME Shell was announced). Except that kded4 is not funny. Best regards, R-C aka beranger
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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. it made me inadvertently filling an invalid bug report 1981, which disappeared once I let kded4 live.) Really, isn't anybody experiencing high CPU from kded4? Nop you're not the only one. However here killing this process does not seems to affect my plasmoids. It could be an upstream bug but it would be nice to narrow it. @ first i was looking @ the nm applet, but a fresh install (by dropping all package only install the minimum aka kmail, dolphin,kdebase4-workspace) does not fix the problem (there's an upstream bug related to kded with networkmanagement kde #220047) (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) -- Balcaen John Jabber ID: mik...@jabber.littleboboy.net
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 not using it. (You should be able to use akregator). -- Balcaen John Jabber ID: mik...@jabber.littleboboy.net
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 inadvertently filling an invalid bug report 1981, which disappeared once I let kded4 live.) Really, isn't anybody experiencing high CPU from kded4? (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.) Thanks, R-C aka beranger 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 these files (photos, music and larger LibreOffice files that it would take quite a while to index them. Maybe this is the problem? My CPU has returned to normal after a couple days of churning. I also never log-out of my system. Cheers Marc
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 is possible, but this affects the plasmoids. (E.g. it made me inadvertently filling an invalid bug report 1981, which disappeared once I let kded4 live.) Really, isn't anybody experiencing high CPU from kded4? (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.) Thanks, R-C aka beranger 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 these files (photos, music and larger LibreOffice files that it would take quite a while to index them. Maybe this is the problem? My CPU has returned to normal after a couple days of churning. I also never log-out of my system. Cheers Marc I get 50% on a VM -- Thomas
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
(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
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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. 4. Hibernation was completely broken (doing nothing), only logout, shutdown and restart worked. 5. Power Management profiles were not displayed and could not be editer, nor were they functional. Other effects might have taken place, that was at first sight. So kded4 is indeed a *vital* process of the KDE4 desktop. It could be an upstream bug but it would be nice to narrow it. @ first i was looking @ the nm applet, but a fresh install (by dropping all package only install the minimum aka kmail, dolphin,kdebase4-workspace) does not fix the problem (there's an upstream bug related to kded with networkmanagement kde #220047) Not easy to narrow it here either. If it's an upstream one (can't test 4.6.90 in other distro for now), then the upstream QA is non-existent. R-C aka beranger
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 description tells me exactly nothing). There is *no* ntrack in either of Mandriva or Fedora -- it's actually likely to be an Ubuntu project; either way, it's definitely *not* part of the KDE4 project, as it's hosted on https://launchpad.net/ntrack Then why the heck removing libntrack0 wants to remove *all* the KDE??? Is Mageia becoming Kubuntu? All these excessive dependencies are making me sick. Everything depends on everything. Is dynamic loading of libraries, with dynamically getting pointers to functions and using them or not, depending on availability, a mechanism that only works in Windows? Then, you'll excuse me, for the fist time in 9 days, I'll reboot into XP SP3. And I'm doing that because, after having rebooted in F15, their plasma (4.6.3) crashed on me for 3 times in 5 minutes. This is unbearable. Pissed off, R-C aka beranger
Re: [Mageia-dev] Anybody having high CPU by kded4 after upgrading to 4.6.90?
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 these files (photos, music and larger LibreOffice files that it would take quite a while to index them. Maybe this is the problem? My CPU has returned to normal after a couple days of churning. I also never log-out of my system. I don't believe. My installation has no data. One core is using continuously 100% (with sometimes switching the core) Magnus
