Re: knotify4 going crazy & breeding like rabbits

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday, February 20, 2012 08:08:28 PM Chuck Burns did opine:

> On 2/20/2012 5:00 PM, gene heskett wrote:
> > Greetings;
> > 
> > I have so far today, killed around 75 copies of /usr/bin/knotify4
> > which is pegging out all 4 cores of my phenom, and running it up to
> > 70C+.
> > 
> > Killing all copies (which is puzzling because killall can't find them
> > but htop can) cleans the system up&  brings back normal operation.
> > 
> > But in half an hour I am back to 4 to 6 copies and a pegged cpu.
> > 
> > This seems to go along with an uptime of 10 days or more, currently at
> > 18 days.
> > 
> > Is there a permanent fix for this other than switching to (I'd rather
> > just have somebody shoot me) gnome or even (quite a bit better IMO)
> > xfce?
> > 
> > Thanks.
> > 
> > Cheers, Gene
> 
> I hate to sound like a smartass..

Not at all.

> but have you tried logging out of kde,
> and back in? Your uptime won't suffer, and KDE will be able to
> completely refresh.. There may some sort of leak somewhere..

I suspect there is, but running it down seems nearly impossible when it 
doesn't show up for 2 weeks.
 
> AFAIK, no one has reported a bug about this.. perhaps if you have time,
> you can try to narrow it down to exactly what.
> 
> You can also try disabling all notifications.. ymmv

I do use inotifywait, a seperate utility to facilitate mail travel within 
the machine for one, and to issue an automatic print this command when a 
print file comes out of drivewire, but AFAIK, the rest of it is pure kde.  
I note that I found another copy of it the 2nd time I went on a killing 
rampage today, about 75 processes down from the top, killed it too, and the 
problem has not come back, but something has called up 2 copies of it since 
I nuked them all.

If that had a visible link to whatever restarts it, that would help 
considerably in tracking this down, but apparently no one knows what 
(re)starts it.

But:
[root@coyote eagle]# lsof |grep knotify4|wc -l
1198

How the heck can you separate the wheat from the chaff in a list that 
long..  :(

Half of that is vlc linked:
[root@coyote eagle]# lsof |grep knotify4|grep vlc|wc -l
604

And I haven't specifically used vlc that I know of in months, so I assume a 
news site I have visited must have called it up.

ATM, I have an eagle session on a pcb going in another window, pending info 
that I screwed the moose, so I would rather get that fixed before I reboot 
kde.

So I'll likely muddle along, keeping my rifle barrel warm if it happens 
again.

Thanks Chuck.

Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://coyoteden.dyndns-free.com:85/gene>
Q:	What do you get when you cross a mobster with an international 
standard?
A:	You get someone who makes you an offer that you can't understand!
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.


[Index of Archives]     [Trinity (TDE) Desktop Users]     [Fedora KDE]     [Fedora Desktop]     [Linux Kernel]     [Gimp]     [GIMP for Windows]     [Gnome]     [Yosemite Hiking]
  Powered by Linux