The author forgot to set the mainwidget. The attached patch fixed the problem here. I've mailed the author but I'm still waiting for a reply. Reproducible: Always Steps to Reproduce: 1. USE=kde emerge kchmviewer Actual Results: Load a chm file. Close the window either clicking on close on the window decoration or selecting file/quit. Window disappears but a ps ax|grep kchm shows kchmviewer is still running. Expected Results: kchmviewer should close and kill the application
Created attachment 107808 [details, diff] Patch for kchmviewer-2.7
Created attachment 107810 [details, diff] ebuild diff (just one line)
UPSTREAM seems to answer on mails just before they issue new release... I have not looked into sources, but could that be intentional to leave chm process running? Also I found that that processes are dying later on my system. Something in 1-2 minutes ps does not show any chm process...
> but could that be intentional to leave chm process > running? Why? If I open two or three chm files, I get two or three processes. There's no reuse. > Also I found that that processes are dying later on my system. > Something in 1-2 minutes ps does not show any chm process... Perhaps just a KDE feature. I think not setting the mainwidget it's a bug in kchmviewer which should be fixed, but I'll wait the official reply from George (kchmviewer's developer) just in case :) Best regards, Norberto
kchmviewer-3.0 is out. So what is the status here?
Bug has been fixed in the 3.1-2 release (-2 because the original 3.1 did not upload to sf.net well). The gentoo fixes have also made it upstream, so we can cut the patches out of the to-be bumped 3.0 ebuild.
I've just commited kchmviewer-3.1_p2 to CVS. It does indeed fix the issue described here.
