[Falkon] [Bug 493407] Starting Falkon occasionally results in Falkon being displayed only with its minimized program button in the KDE task bar. Segmentation fault when quitting Falkon

[Jens]

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

--- Comment #2 from Jens <senf at mailbox.org> ---
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)

-- 
You are receiving this mail because:
You are the assignee for the bug.