[Bug 86680] Re: knetworkmanager stops kde applications from accessing the network

2008-05-29 Thread Andrew Kohlsmith
KPPP shouldn't do this, as there are other sources of PPP startup; perhaps putting it in the /etc/ppp/ip-up and /etc/ppp/ip-down scripts; umtsmon also starts up ppp, for example. -- knetworkmanager stops kde applications from accessing the network https://bugs.launchpad.net/bugs/86680 You receive

[Bug 193907] Re: kppp does not set KDE network status to "online"

2008-05-29 Thread Andrew Kohlsmith
KPPP isn't the only thing that needs to be changed; umtsmon also starts up pppd. Perhaps a better solution is to emit the appropriate dbus message through the /etc/ppp/ip-up and /etc/ppp/ip-down scripts? -- kppp does not set KDE network status to "online" https://bugs.launchpad.net/bugs/193907 Y

[Bug 128537] Re: kopete grabs all memory/CPU when triggered by unrelated file I/O

2007-07-30 Thread Andrew Kohlsmith
Just another datapoint... it isn't *just* a file dialogue that trips this, but that is the only easily-reproducible method I've come across. -- kopete grabs all memory/CPU when triggered by unrelated file I/O https://bugs.launchpad.net/bugs/128537 You received this bug notification because you ar

[Bug 128537] Re: kopete grabs all memory/CPU when triggered by unrelated file I/O

2007-07-26 Thread Andrew Kohlsmith
Homing in on this bug... 1) Kopete does not need to be online. The MSN conversation bit in my last note was a red herring. 2) Save As doesn't always cause it, but Konq's archive web page tool does. -- kopete grabs all memory/CPU when triggered by unrelated file I/O https://bugs.launchpad.net/b

[Bug 128537] Re: kopete grabs all memory/CPU when triggered by unrelated file I/O

2007-07-26 Thread Andrew Kohlsmith
It may need an ongoing MSN conversation to trigger... i.e. 1) open up kopete, start up an MSN conversation and get a decent conversation going 2) click on a link in konq or archive a web page. Kopete starts ratcheting up mem and CPU. -- kopete grabs all memory/CPU when triggered by unrelated f

[Bug 128537] Re: kopete grabs all memory/CPU when triggered by unrelated file I/O

2007-07-26 Thread Andrew Kohlsmith
I figured out the trigger. Kopete will grab all CPU/mem (and race Kontact to OOM kill if it's running) if any KDE application opens a file selection dialog (e.g. save as or open). It is 100% repeatable. -- kopete grabs all memory/CPU when triggered by unrelated file I/O https://bugs.launchpad.n

[Bug 128537] kopete grabs all memory/CPU when triggered by unrelated file I/O

2007-07-26 Thread Andrew Kohlsmith
Public bug reported: Binary package hint: kopete Kopete seems to have an issue where if there is some kind of file I/O (seemingly unrelated to Kopete), it starts grabbing all available memory and CPU. If Kontact is running, Kontact will join this race for hte top, and the OOM handler will genera