This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The problem is still present on Fedora 29,
konqueror-18.08.1-1.fc29.x86_64

The issue is that it leaves a process active which blocks subsequent launches.  If you kill the lingering konqueror process via the task manager, you can launch it again.

This is a workaround, however this issue seems a bug to me!

I can confirm this happens reproducibly using the webengine backend.  webkit/khtml backends do not suffer from this.

2 things:
* this ought to be reported upstream to bugs.kde.org
* if upstream doesn't act in a reasonable amount of time, we can consider switching the default backend (to webkit)

Tested latest 18.12.0 release.  

good news: konqueror does quit and start now

bad news: the "quit" part is a crash now instead of it just hanging

Upstream there is already a bug report on this issue (just found)

https://bugs.kde.org/show_bug.cgi?id=258124

but it is really outdated, last entry is in 2016.
I will try to create a cross-reference there with a link to this bug report

(In reply to Maurizio Paolini from comment #7)
> Upstream there is already a bug report on this issue (just found)
> 
> https://bugs.kde.org/show_bug.cgi?id=258124
> 
> but it is really outdated, last entry is in 2016.
> I will try to create a cross-reference there with a link to this bug report

I opened a new BUG report on bugs.kde.org:

https://bugs.kde.org/show_bug.cgi?id=401976

konqueror-18.12.0-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-c7e6196529

I have to take back comment #6 , it crashed on quit once (first time I tried it), now it still reproducibly hangs on quit and previously reported.  :(

Given how profoundly fundamental to KDE konqueror has been over the years I am astonished this bug has been around for as long as it has been with seemingly no interest at the KDE side.  I can only presume konqueror is considered depreciated in light of dolphin and firefox.

Your guess is fairly accurate, dolphin + falkon (or firefox or whatever) is generally preferable these days.

Given this has been languishing for awhile, I'll follow through on my threat from comment #5 and patch fedora's builds to use kwebkitpart by default instead.

%changelog
* Sat Dec 29 2018 Rex Dieter <rdieter> - 18.12.0-2
- default to kwebkitpart until kwebenginepart works properly (#1523082,kde#401976)

konqueror-18.12.0-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-c7e6196529

Darn, my findings this time are different.  konqueror hangs on quit regardless of what rendering engine used (I tested all 3 available, kwebenginepart, kwebkitpart, khtml)

konqueror-18.12.0-2.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-c7e6196529

As Rex said, this is still not fixed.  I have a partial workaround as follows:

(1) Edit the /usr/share/applications/konqbrowser.desktop file and edit the line "Exec=konqueror" to read "Exec=/usr/local/bin/konqueror.sh"

(2) Create an executable file /usr/local/bin/konqueror.sh and set the contents to be "kill `ps -C konqueror -o pid=`; wait; konqueror &"

This runs konqueror via a script that kills the previous instance before launching a new one.  Of course this only works if you are content to have only one running instance (which is the case for me).

Yes, I know this is nasty, but it works for now for me.

(In reply to Ian Laurie from comment #16)
> As Rex said, this is still not fixed.  I have a partial workaround as
> follows:
> 
> (1) Edit the /usr/share/applications/konqbrowser.desktop file and edit the
> line "Exec=konqueror" to read "Exec=/usr/local/bin/konqueror.sh"
> 
> (2) Create an executable file /usr/local/bin/konqueror.sh and set the
> contents to be "kill `ps -C konqueror -o pid=`; wait; konqueror &"
> 
> This runs konqueror via a script that kills the previous instance before
> launching a new one.  Of course this only works if you are content to have
> only one running instance (which is the case for me).
> 
> Yes, I know this is nasty, but it works for now for me.

I see the risk of losing open konqueror sessions by inardventently opening a new konqueror
instance.  We should need a way to know if the existing konqueror has e.g. open tabs...

baloo-widgets-18.12.2-1.fc29 dolphin-18.12.2-1.fc29 dolphin-plugins-18.12.2-1.fc29 kate-18.12.2-1.fc29 konsole5-18.12.2-1.fc29 khelpcenter-18.12.2-1.fc29 konqueror-18.12.2-1.fc29 kfind-18.12.2-1.fc29 keditbookmarks-18.12.2-1.fc29 kdialog-18.12.2-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-cf6c31ef35

reverting status, still no evidence this has been fixed in latest releases.

OK, I think I may have a workaround, from the intial comment here,

> Also, it seems to me that the mechanism of using an already active konqueror

indeed, going to settings->configure konqueror -> performance -> 
*uncheck* always try to have one preloaded instance

seems to make konqueror start/restart reliably for me (at least for the 4-5 times I just tried it).  I'll do more testing.  If this helps, we can toggle that option off by default.

(In reply to Rex Dieter from comment #20)

Indeed, it seems that unchecking that option works around the problem.

> OK, I think I may have a workaround, from the intial comment here,
> 
> > Also, it seems to me that the mechanism of using an already active konqueror
> 
> indeed, going to settings->configure konqueror -> performance -> 
> *uncheck* always try to have one preloaded instance
> 
> seems to make konqueror start/restart reliably for me (at least for the 4-5
> times I just tried it).  I'll do more testing.  If this helps, we can toggle
> that option off by default.

For people who want to try this workaround, it won't work for the instance in which you make the change... that one will still need killing via the task manager, but from then on it seems to work.  At least that was my experience.

baloo-widgets-18.12.2-1.fc29 dolphin-18.12.2-1.fc29 dolphin-plugins-18.12.2-1.fc29 kate-18.12.2-1.fc29 kdialog-18.12.2-1.fc29 keditbookmarks-18.12.2-1.fc29 kfind-18.12.2-1.fc29 khelpcenter-18.12.2-1.fc29 konqueror-18.12.2-2.fc29 konsole5-18.12.2-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-cf6c31ef35

baloo-widgets-18.12.2-1.fc29 dolphin-18.12.2-1.fc29 dolphin-plugins-18.12.2-1.fc29 kate-18.12.2-1.fc29 kdialog-18.12.2-1.fc29 keditbookmarks-18.12.2-1.fc29 kfind-18.12.2-1.fc29 khelpcenter-18.12.2-1.fc29 konqueror-18.12.2-2.fc29 konsole5-18.12.2-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-cf6c31ef35

baloo-widgets-18.12.2-1.fc29, dolphin-18.12.2-1.fc29, dolphin-plugins-18.12.2-1.fc29, kate-18.12.2-1.fc29, kdialog-18.12.2-1.fc29, keditbookmarks-18.12.2-1.fc29, kfind-18.12.2-1.fc29, khelpcenter-18.12.2-1.fc29, konqueror-18.12.2-2.fc29, konsole5-18.12.2-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-cf6c31ef35

baloo-widgets-18.12.2-1.fc29, dolphin-18.12.2-1.fc29, dolphin-plugins-18.12.2-1.fc29, kate-18.12.2-1.fc29, kdialog-18.12.2-1.fc29, keditbookmarks-18.12.2-1.fc29, kfind-18.12.2-1.fc29, khelpcenter-18.12.2-1.fc29, konqueror-18.12.2-2.fc29, konsole5-18.12.2-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.

This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.