SUMMARY Since Plasma 5.18, Falkon will crash everytime trying to open facebook.com or other websites (not every website), but only when using it under Wayland. Updated today to Plasma 5.19, re-emerged Falkon but it's still crashing. This didn't happened before, it was stable both on X and Wayland. Tried to create a new test user and reproduce and opening it with no extensions (-e), portable mode (-o) and private mode (-i), but on all cases it crashed. It saves a crashlog file, but (I guess it's because my system doesn't have gcc debug symbols) it only says this: Time: wed. jun. 10 07:09:20 2020 Qt version: 5.14.2 (compiled with 5.14.2) Falkon version: 3.1.0 Rendering engine: QtWebEngine ============== BACKTRACE ============== #0: falkon(+0x412a) [0x55e4112a712a] #1: /lib64/libc.so.6(+0x3332c387a0) [0x7f7671a437a0] I don't know what else to do. This made me go back to X as Wayland was already my daily driver. Though it's weird I hadn't read about someone else with the same issue anywhere else. STEPS TO REPRODUCE 1. Be under a Wayland session with Plasma 5.18/5.19 2. Open Falkon 3. Open facebook.com OBSERVED RESULT Falkon immediately crashes before the progress bar even reaching its 100% state. EXPECTED RESULT Hmmm... Not crashing? SOFTWARE/OS VERSIONS Linux: Kernel 5.6.0-pf7 (pf-sources) KDE Plasma Version: Plasma 5.19 KDE Frameworks Version: 5.70 Qt Version: 5.14.2 ADDITIONAL INFORMATION
Just found out that setting QT_QPA_PLATFORM=xcb serves as a workaround.
I've just used Falkon 3.1.0 on Qt 5.14.2 to browse Facebook without any issues. Can you please try again and let us know if the issue persists.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!