Bug 388333

Summary: How to create new konqueror processes?
Product: [Applications] konqueror Reporter: nfxjfg
Component: generalAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: bugs.kde.attila, bugs.kde.org, dag, kavol, kde, m4rkusxxl
Priority: NOR    
Version: 5.0.97   
Target Milestone: ---   
Platform: Debian unstable   
OS: Linux   
Latest Commit: Version Fixed In: 20.04.1

Description nfxjfg 2017-12-29 18:28:08 UTC
After Debian unstable apparently updated Konqueror to KF5 (my guess), just running "konqueror" doesn't start a new process anymore if one already exists. Instead it focuses the current window if there is one.

If there is no window, nothing happens. (For some reason konqueror keeps running in the background even if you close the last window.)

Also, if you run konqueror with some argument (like "konqueror about:blank"), it reuses an existing process. This is slightly more useful than just doing nothing, but still not what I want.

How can I make konqueror just create a new process every time I call it? Like it was in "old" konqueror?

I don't know what the previous version of konqueror was, but post-update it's version 5.0.97, KDE Frameworks 5.37.0.
Comment 1 Andreas Kilgus 2018-03-16 07:03:37 UTC
I can confirm this behaviour. Konqueror (stating version 5.0.97) of KDE Applications 17.04 opened a new window when started from command line, krunner or using the application menu.
With the installation of konqueror contained in KDE Applications 17.12 (still stating its version as 5.0.97) this has changed: No new window with all the methods mentioned above - instead the last window opened gets the focus.

But: If I click a link in an email in kmail 1.9.10 (KDE 3.5.10) - yes, still using this mail program in a Plasma 5 environment - the referenced content opens in a new window. Therefore the topic of this report might be related with something just touching or even being beyond konqueror's scope. Otherwise: I already had upgraded all other components of Plasma 5 to current versions (KDE Frameworks 5.43, Plasma 5.12, KDE Applications 17.12) when I realized that konqueror still was stuck on 17.04. So the only change in packages from "new window" to "last window gets focus" was the upgrade of konqueror 17.04->17.12.

openSUSE 42.3, konqueror-17.12.3-58.1.x86_64
Comment 2 Jonathan M Davis 2018-07-08 00:40:29 UTC
This is _incredibly_ annoying. Previously, I could have a button on the taskbar that opened a new konqueror instance, and now, that doesn't work. Konqueror _does_ open a new instance if you provide a URL, so if I make the button provide a URL, then a new window does open. However, it doesn't give the URL bar focus, so I can't just start typing the URL I want like I could before, and of course, I'm stuck with it always opening a default URL when it starts, and I don't usually want a default URL.

FreeBSD finally got KDE 5 recently, and this is one of the problems that has made switching from KDE 4 to KDE 5 to be a downgrade rather than an upgrade. I really hope that this gets fixed sooner rather than later.
Comment 3 Christoph Feck 2018-07-31 00:46:54 UTC
*** Bug 396336 has been marked as a duplicate of this bug. ***
Comment 4 Clay Weber 2018-08-15 05:02:32 UTC
*** Bug 383815 has been marked as a duplicate of this bug. ***
Comment 5 Friedrich W. H. Kossebau 2019-01-20 19:15:40 UTC
Resetting to default assignee, please do not assign bugs to random developers, only because they touched the code last.
Comment 6 Christoph Feck 2019-02-15 16:24:58 UTC
*** Bug 403493 has been marked as a duplicate of this bug. ***
Comment 7 David Faure 2020-04-27 20:29:35 UTC
Git commit bebc1972900db5fe93942034ea9897566d952def by David Faure.
Committed on 27/04/2020 at 20:29.
Pushed by dfaure into branch 'release/20.04'.

Make `konqueror` open a window even if already running.
FIXED-IN: 20.04.1

M  +10   -5    src/konqmain.cpp

https://commits.kde.org/konqueror/bebc1972900db5fe93942034ea9897566d952def
Comment 8 Wolfgang Bauer 2020-05-29 15:05:23 UTC
*** Bug 398996 has been marked as a duplicate of this bug. ***