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

konqueror infinite self-clones



when using konquer in file-browser mode (nosnig around my home
directory, for example) if i run across a *.tar.gz for example
and if i make the mistake of double-clicking on it (thinking
that if less can read it, everything ought to be able to)
knoqueror tries to display the file, figures out it should pass
it to a helper application -- which is konqueror -- and then
hands the task off to that application.

which is konqueror. which doesn't know how to handle *.gz files.
so it spawns a helper application to do the work...

which is konqueror. which doesn't know how to handle *.gz files.
so it spawns a helper application to do the work...

which is konqueror. which doesn't know how to handle *.gz files.
so it spawns a helper application to do the work...

which is konqueror. which doesn't know how to handle *.gz files.
so it spawns a helper application to do the work...

...

until i ctl-alt-f1 to get console, log in an kill one of the
main kdm processes; then all my current windows are okay (even
switching virtual desktops is no problem) but no new processes
can be spawned. when i log out (or wind up killing X via
atl-alt-backspace) kdm restarts and then all is rosy again.

i let it go one time to see if it'd quit after so many
iterations, and there appeared to be no end in sight.

how do i tell konqueror to NOT spawn itself as a helper app?

-- 
DEBIAN NEWBIE TIP #65 from der.hans <der.hans@LuftHans.com>
:
Wondering about which KEYBOARD SHORTCUTS ARE UNDERSTOOD BY BASH?
Enter this at your bash shell prompt:
	bind -p | less
and see how much of that you can interpret :). For more info
about all of this stuff, do "man bash" then search for "emacs"
and "readline" (to search a manpage, type / and then the pattern
to look for).

Also see http://newbieDoc.sourceForge.net/ ...



Reply to: