Konqueror becomes a zombie process after being closed.

Bug #1760724 reported by Ryan
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
konqueror (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

In Kubuntu 18.04 LTS, Koqnueror becomes a zombie process when closed.

A new instance can't be started without killing the zombie process.

Konqueror package version is 4:17.12.3-0ubuntu1

Ryan (baronhk)
affects: falkon (Ubuntu) → konqueror (Ubuntu)
Revision history for this message
Ron Widell (r-widell) wrote :

I had the same issue, and posted to the ubuntu forum.
The solution for me was to go to Settings->Configure Konqueror->Performance and uncheck the box "Always try to have one preloaded instance".

After logging out and back in to get kdeinit5 reloaded, I can launch Konqueror multiple times per session, and there is no longer a zombie process.

ron

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in konqueror (Ubuntu):
status: New → Confirmed
Revision history for this message
Brian Foster (blfoster) wrote :

Yes, I can confirm that once Konqueror is started - with "Always try to have one preloaded instance" enabled - a process (possibly the same one? (didn't check)) does stay around, even after an clicking quit. This is very annoying, since when shutting down the system (or possibly even when logging out?), it does not seem to respond (quickly enough?) to the (presumed) SIGTERM, and as a result, you get a Crash Report at the next login.

Disabling "Always try to have one preloaded instance" appears to avoid the problem.

As an aside, it's not technically a "zombie process" - it has not actually exit()ed - but an idling process which seems to interfere with things....

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.