Home
Download
Screenshots
FAQ
Feedback
Help needed
PGP Key
History
Archive

FAQ

Generic Informations

Is there a mailing list for KMago?

There is one, kmago-user@lists.sourceforge.net. To subscribe, go to kmago-user management page, web archive here. You can find more informations about lists on KMago mailing lists.

Using KMago

Can I use KMago to mirror web sites?

No, the mirroring capabilities of wget are not supported.

Settings are not saved

Be sure to use a persistent document, i.e. a document not saved in a temporary file. You can convert a temporary document using save as menu entry to save it to a file. Besides that, there is an configure entry named start up with last used document to automatically reload the last used document on start up.

I dont' care about document files

From 1.1.1 release there is an option (that you have to add to kmago.desktop file to make persistent), named --single-doc, to run it as a unique application, and using a single document file located in ~/.kde/share/apps/kmago/data.

What does it mean to run as unique application?

Without options, every kmago invocation fire up a new process, while in this mode you have only one process managing all windows.

How can I exit KMago letting the wget daemons running in background?

Simply kill it, i.e. don't use the quit, or close, or whatever graphical button, you have to send to it a SIGQUIT signal. However this is not recommended, as it doesn't save the last state, even if on restarting it will try to be fair reloading it.

The OK button doesn't work in configure's dialog

If KMago finds some incorrect entries (maybe not in the current tab), it prevent the dialog's close.

How could I use KMago to automate modem dialing?

As there is no standard way to handle the dialing, it's somehow difficult to handle this. From version 1.1 there is some support for this, as KMago can automatically quit when there are no transfers left to run. Another way to handle disconnection come from a configure entry in which you can insert a shell command, that will be executed when there are no transfers left to run. From version 1.1.2, there is support for DCOP, that you can use to gain full control over the application. From more informations, look at DCOP's documentation, and dig the kmago interface using the command-line tool dcop, or maybe with its graphical counterpart kdcop.

Problems

KMago executable size continue to grow until I have to kill it

You are experimenting a memory leakage. Currently there is a known problem about it.
Check file kdebug.areas, and if they are not present, append the following lines to the end, (a tab between number and kmago):

41000 kmago (ini)

41001 kmago (vie)

41002 kmago (run)

41003 kmago (prs)

If this don't resolve the problem, and you have downloaded the source tarball, add to configure the option --enable-debug=no and recompile.

KMago crashes on start up

If you have compiled it yourself, be sure that it is linked with the correct libraries, (in particular QT).
If you are upgrading from an older version, try to remove ~/.kde/share/apps/kmago/kmagoui.rc, or maybe ~/.kde/share/config/kmagorc too. Adapt the paths to follow you local kde directory. Chances are that you are trying to run an old document, although from version 1.1 there is a check for document version, in this case, you have to start KMago from console, typing

kmago <new document
file>

Last modified: Thu Apr 19 10:50:09 CEST 2001

FAQ