SUMMARY On my system I have a Win7 and I recently downloaded Okular from https://binary-factory.kde.org/view/Windows%2064-bit (presumably build 12). Okular version 1.7.70 STEPS TO REPRODUCE 1. Go in okular menu to "Tools->Configure Okular..." 2. Under "General" activate "Open new files in tabs" 3. Close okular or keep it open, it does not matter. Ich checked the ~/AppData/Local/okular/okularpartrc and I find a line with "ShellOpenFileInTabs=true" 4. Open any two PDFs in Windows Explorer OBSERVED RESULT There will be two instances of Okular showing the PDFs in their own window. EXPECTED RESULT One instance of Okular is showing the two PDFs in two tabs. SOFTWARE/OS VERSIONS Windows: Win7 macOS: - Linux/KDE Plasma: - (available in About System) KDE Plasma Version: - KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION https://binary-factory.kde.org/view/Windows%2064-bit/job/Okular_Nightly_win64/12/
same problem in windows 10 and flatpak installed okular in debian 10
Still same problem. Opening another/or same pdf in file explorer opens new instance. Opening through File -> Open... opens in new tab or switches to open file. Okular 20.12.2 Windows 10 Related to this issue on github, though I don't use flatpak: https://github.com/flathub/org.kde.okular/issues/36
*** Bug 435994 has been marked as a duplicate of this bug. ***
*** Bug 436387 has been marked as a duplicate of this bug. ***
SUMMARY `Open new files in tabs` works only from inside of Okular STEPS TO REPRODUCE 1. Double-click on .pdf file in File Manager OBSERVED RESULT it opens it in a new Okular Window EXPECTED RESULT it opens it in a new tab SOFTWARE/OS VERSIONS Windows: 11
(In reply to aj520418 from comment #5) > SUMMARY > `Open new files in tabs` works only from inside of Okular > > STEPS TO REPRODUCE > 1. Double-click on .pdf file in File Manager > > OBSERVED RESULT > it opens it in a new Okular Window > > EXPECTED RESULT > it opens it in a new tab > > SOFTWARE/OS VERSIONS > Windows: 11 Okular version 22.04.0
*** Bug 442763 has been marked as a duplicate of this bug. ***
*** Bug 451826 has been marked as a duplicate of this bug. ***
*** Bug 456480 has been marked as a duplicate of this bug. ***
*** Bug 462704 has been marked as a duplicate of this bug. ***
This still doesn't work. Why isn't it being fixed? Thanks
(In reply to bugzilla123 from comment #11) > This still doesn't work. Why isn't it being fixed? > Thanks This is open source. It's fixed if someone volunteers to do it.
*** Bug 466225 has been marked as a duplicate of this bug. ***
Faced the exact same problem with all versions provided by the website namely: Windows store (23.08.1), nightly stable (23.08.04) and nightly experimental (24.01.80) build. I managed to build the newest version from source myself (24.07.70) and with that version the problem was not there. I followed a wiki entry for building KDE connect on Windows using Visual Studio and craft without modifying any settings or source code. (https://community.kde.org/KDEConnect/Build_Windows) I also build it with QT6, whereas the other versions used QT5. However, I don't know what resolved the matter (build settings, newer Okular version, newer QT version,...).
(In reply to yhd1km from comment #14) > Faced the exact same problem with all versions provided by the website > namely: > Windows store (23.08.1), nightly stable (23.08.04) and nightly experimental > (24.01.80) build. > > I managed to build the newest version from source myself (24.07.70) and with > that version the problem was not there. I followed a wiki entry for > building KDE connect on Windows using Visual Studio and craft without > modifying any settings or source code. > (https://community.kde.org/KDEConnect/Build_Windows) I also build it with > QT6, whereas the other versions used QT5. > > However, I don't know what resolved the matter (build settings, newer Okular > version, newer QT version,...). Potentially you built and run dbus which would make it work, but we don't ship dbus with Okular because it's a bit messy. One potential solution is to use https://github.com/KDAB/KDSingleApplication instead of dbus stuff to make the "should i start myself or attach to another app" logic.
*** Bug 489183 has been marked as a duplicate of this bug. ***
Confirm this behavior for 23.08.1 with Windows 10P22H2/19045.4780
*** Bug 498128 has been marked as a duplicate of this bug. ***
Confirmed this behaviour for 23.801.1522.0 using Windows 11 Pro 23H2 v22631.4751.
*** Bug 504053 has been marked as a duplicate of this bug. ***
*** Bug 434777 has been marked as a duplicate of this bug. ***
*** Bug 484623 has been marked as a duplicate of this bug. ***
*** Bug 470942 has been marked as a duplicate of this bug. ***
*** Bug 461873 has been marked as a duplicate of this bug. ***
*** Bug 436774 has been marked as a duplicate of this bug. ***
Riccardo, it was a very bad idea to merge non Windows bugs to a bug that is speciffically about Windows, please do not do it again.
(In reply to Albert Astals Cid from comment #26) > Riccardo, it was a very bad idea to merge non Windows bugs to a bug that is > speciffically about Windows, please do not do it again. Sorry, you are right; two of those bugs are actually not Windows related. Apologies for the confusion.