Konqueror won't exit gracefully in LEAP 15

English Applications
1

I depend heavily on Konqueror for reading man and info pages.
Unfortunately, in Leap 15, Konqueror will only run once in a user session unless extra steps are taken.

I had a bit of brain-fade, so it took longer than it should have to determine the cause but the process for /usr/bin/konqueror doesn’t die when the window is closed. I’ve tried clicking the X in the upper right corner, using the crtl-Q keyboard shortcut and selecting Quit from the File menu. In each case, the window closes but the process doesn’t stop. So the next time I try to launch it an entry briefly appears in the taskbar, but then disappears. So I have to

~> ps -ef | grep konq
ron       3920  2785  1 16:30 ?        00:00:02 /usr/bin/konqueror
ron       3927  2738  0 16:30 ?        00:00:00 file.so [kdeinit5] file local:/run/user/1000/klauncherTJ2739.1.slave-socket local:/run/user/1000/konqueroriK3920.3.slave-socket
ron       3928  2738  0 16:30 ?        00:00:00 file.so [kdeinit5] file local:/run/user/1000/klauncherTJ2739.1.slave-socket local:/run/user/1000/konquerorvE3920.4.slave-socket
ron       3929  2738  0 16:30 ?        00:00:00 file.so [kdeinit5] file local:/run/user/1000/klauncherTJ2739.1.slave-socket local:/run/user/1000/konqueroreY3920.5.slave-socket
ron       3930  2738  0 16:30 ?        00:00:00 file.so [kdeinit5] file local:/run/user/1000/klauncherTJ2739.1.slave-socket local:/run/user/1000/konquerorYa3920.6.slave-socket
ron       3931  2738  0 16:30 ?        00:00:00 man.so [kdeinit5] man local:/run/user/1000/klauncherTJ2739.1.slave-socket local:/run/user/1000/konquerorfM3920.7.slave-socket
ron       3936  2738  0 16:31 ?        00:00:00 help.so [kdeinit5] help local:/run/user/1000/klauncherTJ2739.1.slave-socket local:/run/user/1000/konquerorUz3920.8.slave-socket
ron       3954  3875  0 16:32 pts/0    00:00:00 grep --color=auto konq
~> kill 3920

before it will launch again.

I’m getting ready to report it as a bug, but I though I’d check here first to see if there’s some configuration error that could cause this.

This machine has been getting upgraded though all of the openSUSE releases since 13.1, so it’s certainly possible that there’s a configuration artifact remaining from one of the previous releases.

Thanks for your time and knowledge,
ron

2

I ran into that problem.

Settings → Configure Konqueror → Performance

There are two options:

  • Preload an instance after desktop startup
  • Always try to have one preloaded instance

I seem to recall that when I first checked, the second of those options had been set. I unset it, and I have not had that problem since. I suggest you clear both of those options.

3

Thank you for the info and the quick response.
The second box was, indeed checked. I cleared it.

I had to log out and back in for it to take effect because I couldn’t quickly figure out an easy way to get kdeinit5 to reload the configuration.

But after logging out and back in, I can open and close Konqueror as I choose.

Thanks again,
ron

4

I’m glad that helped. And thanks for reporting back.