This behavior does not occur at every single start of Falkon, it occurs once in a while: Having started Falkon either from within the console with the corresponding command or by clicking the Falkon icon in the KDE start menu or in the KDE task bar, Falkon's main GUI window does not get displayed, but instead of that Falkon gets displayed through its minimized button in the KDE task bar. Clicking on that minimized button in the KDE task bar does not maximize Falkon, i. e. Falkon's main GUI window does not get displayed. The console provides the following debug information about this behavior: <User>@<Hostname>:~$ falkon Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/libexec/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/libexec/qtwebengine_dictionaries' MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete Falkon: 2 extensions loaded qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0 I cannot assess if this behavior is purely related to Qt and Wayland. journalctl did not log anything about this behavior: <User>@<Hostname>:~$ sudo journalctl --user --catalog -f No journal files were found. <User>@<Hostname>:~$ sudo journalctl --user -S today | grep -i falkon No journal files were found. <User>@<Hostname>:~$ <User>@<Hostname>:~$ sudo journalctl --system --catalog -S today | grep -i falkon [sudo] password for <User>: <User>@<Hostname>~$ SOFTWARE/OS VERSIONS Linux: Tuxedo OS 3 KDE Plasma Version: 6.1.5 KDE Frameworks Version (kf6-frameworkintegration): 6.5.0 Qt Version: 6.7.2
An update with much more information about this behavior: Directly after logging into KDE Plasma 6, start Falkon either via the KDE start menu or by the corresponding command in a console window: In many cases, but not always, at least in my Tuxedo OS 3 installation, Falkon's main window does not get displayed. Only the minimized button of Falkon is displayed in the Task Bar. If Falkon has been started within a console window, and this behavior occurs, then the console contains the following information: <User>@<Hostname>:~$ falkon Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/libexec/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/libexec/qtwebengine_dictionaries' MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete Falkon: 3 extensions loaded qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0 Optimizing database... Note that here Falkon is still running, i. e. the program button of Falkon is still displayed in the Task Bar, but Falkon's main window is not displayed. The last line in the console saying "Optimizing database..." is currently displayed since I started to write the text for this bug report, so here is the question if this database optimization is already complete or not. I will now stop Falkon by right-clicking its program button in the Task Bar, then I will click the "Close" entry in its context menu. Please keep in mind the 2nd last line in the output of the console above ("Segmentation fault"), having applied the "Close" functionality in this context menu: <User>@<Hostname>:~$ falkon Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/libexec/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/libexec/qtwebengine_dictionaries' MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete Falkon: 3 extensions loaded qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0 Optimizing database... KCrash: Application 'falkon' crashing... crashRecursionCounter = 2 Segmentation fault <User>@<Hostname>:~$ When I now start Falkon for a 2nd time from within the same console, then Falkon's main window gets displayed, and the console returns the following information if I then quit Falkon again: <User>@<Hostname>:~$ falkon Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/libexec/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/libexec/qtwebengine_dictionaries' MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete Falkon: 3 extensions loaded qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0 KCrash: Application 'falkon' crashing... crashRecursionCounter = 2 Segmentation fault <User>@<Hostname>:~$ Note that the following lines already specified above: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0 KCrash: Application 'falkon' crashing... crashRecursionCounter = 2 Segmentation fault have been reported in another bug report, too, i. e. in bug report #493406: https://bugs.kde.org/show_bug.cgi?id=493406 There is a difference between the bug report here and bug report #493406: Bug report #493406 does not contain the console output line "Optimizing database...", and the behavior reported in bug report #493406 is caused by a different way Falkon has been used. I will now log out of KDE and log into KDE again, and then directly start Falkon from within a console: The main window of Falkon gets displayed. I will now quit Falkon again. The console provides the following information: <User>@<Hostname>:~$ falkon Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/libexec/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/libexec/qtwebengine_dictionaries' MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete Falkon: 3 extensions loaded qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0 KCrash: Application 'falkon' crashing... crashRecursionCounter = 2 Segmentation fault <User>@<Hostname>:~$ I then restarted my Tuxedo OS 3 installation, and directly after my login into KDE I started Falkon from the console, and the main window of Falkon gets displayed with the message "Oops, Falkon crashed. We apologize for this. Would you like to restore the last saved state? [...]" (I did not do anything about that message), and having quit Falkon again, the console provides the following information: <User>@<Hostname>:~$ falkon Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/libexec/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/lib/qt6/libexec/qtwebengine_dictionaries' MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete Falkon: 3 extensions loaded qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0 <User>@<Hostname>:~$ Thus here no segmentation fault has occurred. I will now try to create a backtrace of this segmentation fault. I could reproduce the behavior again, this time in connection with using gdb. The last lines of the console output are these here: [...] [New Thread 0x7fffa9600640 (LWP 1331)] MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete [New Thread 0x7fff91800640 (LWP 1332)] [New Thread 0x7fff90e00640 (LWP 1333)] [New Thread 0x7fff87e00640 (LWP 1334)] [Thread 0x7fff91800640 (LWP 1332) exited] [New Thread 0x7fff91800640 (LWP 1335)] [New Thread 0x7fffa8c00640 (LWP 1336)] [Thread 0x7fffa8c00640 (LWP 1336) exited] [Thread 0x7fff91800640 (LWP 1335) exited] [New Thread 0x7fff91800640 (LWP 1337)] [Thread 0x7fff91800640 (LWP 1337) exited] [New Thread 0x7fff91800640 (LWP 1338)] [Thread 0x7fff91800640 (LWP 1338) exited] [New Thread 0x7fff91800640 (LWP 1339)] [Thread 0x7fff91800640 (LWP 1339) exited] Falkon: 3 extensions loaded [New Thread 0x7fff91800640 (LWP 1341)] [New Thread 0x7fffa8c00640 (LWP 1342)] [New Thread 0x7fff9fe00640 (LWP 1343)] [New Thread 0x7fff9f400640 (LWP 1344)] [New Thread 0x7fff9ea00640 (LWP 1346)] [New Thread 0x7fff9e000640 (LWP 1347)] [Thread 0x7fff9e000640 (LWP 1347) exited] [Thread 0x7fff9ea00640 (LWP 1346) exited] [New Thread 0x7fff9ea00640 (LWP 1348)] [New Thread 0x7fff9e000640 (LWP 1349)] [New Thread 0x7fff87400640 (LWP 1350)] [New Thread 0x7fff86a00640 (LWP 1351)] [Thread 0x7fff86a00640 (LWP 1351) exited] [Thread 0x7fff87400640 (LWP 1350) exited] [New Thread 0x7fff87400640 (LWP 1357)] qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0 [New Thread 0x7fff86a00640 (LWP 1358)] [New Thread 0x7fff86000640 (LWP 1359)] [New Thread 0x7fff85600640 (LWP 1360)] [New Thread 0x7fff84c00640 (LWP 1362)] [New Thread 0x7fff7fe00640 (LWP 1365)] [Thread 0x7fff87e00640 (LWP 1334) exited] [Thread 0x7fff90e00640 (LWP 1333) exited] At this point, nothing happens anymore, i. e. the program button of Falkon stays minimized in the Task Bar. I am now waiting for something to happen since approximately 3 or 4 minutes. I will now quit Falkon by right-clicking the program button of Falkon in the Task Bar, then I will click "Close". This is the return information in the console having quit Falkon: [Thread 0x7fff87e00640 (LWP 1334) exited] [Thread 0x7fff90e00640 (LWP 1333) exited] Thread 1 "falkon" received signal SIGSEGV, Segmentation fault. 0x00007ffff6e6354e in ?? () from /lib/x86_64-linux-gnu/libQt6Core.so.6 (gdb) backtrace #0 0x00007ffff6e6354e in () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #1 0x00007ffff793257b in History::resetHistory() (this=0x0) at /opt/falkon/falkon/build/src/lib/FalkonPrivate_autogen/ZGCQNSLDUB/moc_history.cpp:206 #2 0x00007ffff7ab8400 in History::clearHistory() (this=0x0) at /opt/falkon/falkon/src/lib/history/history.cpp:256 #3 0x00007ffff7a141fe in MainApplication::saveSettings() (this=0x7fffffffd5e0) at /opt/falkon/falkon/src/lib/app/mainapplication.cpp:847 #4 0x00007ffff79d3cca in QtPrivate::FunctorCall<QtPrivate::IndexesList<>, QtPrivate::List<>, void, void (MainApplication::*)()>::call(void (MainApplication::*)(), MainApplication*, void**) (f=(void (MainApplication::*)(MainApplication * const)) 0x7ffff7a13c00 <MainApplication::saveSettings()>, o=0x7fffffffd5e0, arg=0x7fffffffcba0) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:145 #5 0x00007ffff79d2496 in QtPrivate::FunctionPointer<void (MainApplication::*)()>::call<QtPrivate::List<>, void>(void (MainApplication::*)(), MainApplication*, void**) (f=(void (MainApplication::*)(MainApplication * const)) 0x7ffff7a13c00 <MainApplication::saveSettings()>, o=0x7fffffffd5e0, arg=0x7fffffffcba0) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:182 #6 0x00007ffff79d068d in QtPrivate::QCallableObject<void (MainApplication::*)(), QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x5555583eb400, r=0x7fffffffd5e0, a=0x7fffffffcba0, ret=0x0) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:553 #7 0x00007ffff6e6381b in () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #8 0x00007ffff6ea448e in QCoreApplication::aboutToQuit(QCoreApplication::QPrivateSignal) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #9 0x00007ffff6ea4515 in QCoreApplication::exit(int) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #10 0x00007ffff6ea453b in QCoreApplication::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #11 0x00007ffff760a1ab in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #12 0x00007ffff6ea1dd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #13 0x00007fffe9aeb34f in QGuiApplicationPrivate::processApplicationTermination(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /lib/x86_64-linux-gnu/libQt6Gui.so.6 #14 0x00007fffe9aebe6f in QGuiApplicationPrivate::quit() () at /lib/x86_64-linux-gnu/libQt6Gui.so.6 #15 0x00007ffff7a136da in MainApplication::quitApplication() (this=0x7fffffffd5e0) at /opt/falkon/falkon/src/lib/app/mainapplication.cpp:775 #16 0x00007ffff79fd039 in BrowserWindow::closeEvent(QCloseEvent*) (this=0x5555559413d0, event=0x7fffffffd0a0) at /opt/falkon/falkon/src/lib/app/browserwindow.cpp:1519 #17 0x00007ffff76482e5 in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #18 0x00007ffff79fbf50 in BrowserWindow::event(QEvent*) (this=0x5555559413d0, event=0x7fffffffd0a0) at /opt/falkon/falkon/src/lib/app/browserwindow.cpp:1251 #19 0x00007ffff760a1ab in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #20 0x00007ffff6ea1dd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #21 0x00007ffff764511d in QWidgetPrivate::handleClose(QWidgetPrivate::CloseMode) () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #22 0x00007ffff7657d9f in () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #23 0x00007fffe9b413f0 in QWindow::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt6Gui.so.6 #24 0x00007ffff760a1ab in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #25 0x00007ffff6ea1dd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #26 0x00007fffe9aecfa1 in QGuiApplicationPrivate::processCloseEvent(QWindowSystemInterfacePrivate::CloseEvent*) () at /lib/x86_64-linux-gnu/libQt6Gui.so.6 #27 0x00007fffe9b5017c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt6Gui.so.6 #28 0x00007fffe9f11e34 in () at /lib/x86_64-linux-gnu/libQt6Gui.so.6 #29 0x00007fffea11bd3b in g_main_dispatch (context=0x7fffe0005040) at ../../../glib/gmain.c:3419 #30 g_main_context_dispatch (context=0x7fffe0005040) at ../../../glib/gmain.c:4137 #31 0x00007fffea1712b8 in g_main_context_iterate.constprop.0 (context=context@entry=0x7fffe0005040, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:4213 #32 0x00007fffea1193e3 in g_main_context_iteration (context=0x7fffe0005040, may_block=1) at ../../../glib/gmain.c:4278 #33 0x00007ffff6c62700 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 --Type <RET> for more, q to quit, c to continue without paging--c #34 0x00007ffff6ea3feb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #35 0x00007ffff6ea5c2c in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #36 0x0000555555557bfd in main(int, char**) (argc=1, argv=0x7fffffffd838) at /opt/falkon/falkon/src/main/main.cpp:74 (gdb)
The behavior "Falkon starts with a minimized browser window, i.e. Falkon gets displayed merely by its program button in the KDE Taskbar, and you cannot open Falkon´ s GUI window by left- or right-clicking its program icon in the Taskbar" also occurs in my Manjaro installation, but it does not generate segmentation faults: This behavior always occurs after a complete (re-) start of my Manjaro installation and a successive login into KDE, with Wayland set as the display server, but not (always?) after a logout out of KDE and a re-login into KDE with Wayland set as the display server. A) Manjaro restart + first login into KDE + Wayland set as the display server: This is the output in the virtual console tab from where Falkon has been started: ---------- [<User>@<Hostname>: ~]$ falkon Falkon: Python plugin support initialized MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete Falkon: 6 extensions loaded qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0 ---------- When I then apply CTRL+C, no segmentation fault is displayed in the console window. This is the output of the command "journalctl --user --catalog -f" during the start of Falkon: ---------- Okt 20 16:21:13 <Hostname> plasmashell[790]: error creating screencast "Could not find window id {43b04add-f84e-40d0-9f16-1016069ba95a}" Okt 20 16:21:36 <Hostname> plasmashell[790]: error creating screencast "Could not find window id {43b04add-f84e-40d0-9f16-1016069ba95a}" Okt 20 16:21:44 <Hostname> plasmashell[790]: error creating screencast "Could not find window id {43b04add-f84e-40d0-9f16-1016069ba95a}" Okt 20 16:21:51 <Hostname> plasmashell[790]: error creating screencast "Could not find window id {43b04add-f84e-40d0-9f16-1016069ba95a}" ---------- B) Manjaro restart + first login into KDE + X11 set as the display server: ---------- [<User>@<Hostname>: ~]$ falkon Falkon: Python plugin support initialized MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete Falkon: 6 extensions loaded ---------- Result: Falkon gets started showing its complete GUI window. Falkon thus is not shown minimized, i.e. not only with its program button in the KDE taskbar. This is the output of the command "journalctl --user --catalog -f" during the start of Falkon: ---------- Okt 20 16:11:33 <Hostname> systemd[597]: Started Konsole - Terminal. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://forum.manjaro.org/c/support ░░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 372. Okt 20 16:14:20 <Hostname> plasmashell[724]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken. Okt 20 16:14:20 <Hostname> plasmashell[724]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken. ---------- When I then apply CTRL+C, no segmentation fault is displayed in the console window. Conclusion: The behavior "Falkon starts with a minimized browser window, i.e. Falkon gets displayed merely by its program button in the KDE Taskbar, and you cannot open Falkon´ s GUI window by left- or right-clicking its program icon in the Taskbar" seems to be related to Wayland in connection with Plasma. --- SOFTWARE/OS VERSIONS Linux: Manjaro KDE Plasma 6 version: 6.1.5 KDE Frameworks version: 6.6.0 Display server: Wayland QT version: 6.7.2 (built against 6.7.2)