| Summary: | "Enable automatic searching from the Adress Bar" option deactivated in Falkon's preferences: If a search is executed in the Address Bar, Falkon quits with a segmentation fault | ||
|---|---|---|---|
| Product: | [Applications] Falkon | Reporter: | Jens <senf> |
| Component: | general | Assignee: | Juraj <jurajoravec> |
| Status: | REPORTED --- | ||
| Severity: | crash | CC: | jurajoravec, senf |
| Priority: | NOR | ||
| Version: | 24.08.1 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Jens
2024-09-20 14:59:20 UTC
Hello Jens, Since you already compiled Falkon, can you provide backtrace? https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports I am not sure if KCrash showed up, you might need to use some other option (I use plain gdb). I am unable to reproduce this on my machine. (I will try some virtual machine later) It could be that Falkon tries to start an external program (another web browser?) to process the "site" protocol which is unknown to Falkon. And maybe since it cannot find any program associated with it, well it crashes. (The backtrace would help narrow down where it crashed) Thank you for reporting. PS: I remember here being another report that Falkon always tries to execute stuff from addressbar with unknown protocol without asking the user. It could be since there is no associated program to run it crashes, hard to say without proper backtrace or testing. Hi Juraj,
No, KCrash is never displayed whenever I cause this error to happen (I can always reproduce this error).
So here is my backtrace log:
[...]
qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0
[New Thread 0x7fff86a00640 (LWP 2623)]
[New Thread 0x7fff86000640 (LWP 2624)]
[New Thread 0x7fff85600640 (LWP 2625)]
[New Thread 0x7fff84c00640 (LWP 2626)]
[New Thread 0x7fff7fe00640 (LWP 2629)]
Thread 1 "falkon" received signal SIGSEGV, Segmentation fault.
0x00007fffe4fa3823 in QtWaylandClient::QWaylandWindow::requestXdgActivationToken(unsigned int) () from /lib/x86_64-linux-gnu/libQt6WaylandClient.so.6
(gdb) backtrace
#0 0x00007fffe4fa3823 in QtWaylandClient::QWaylandWindow::requestXdgActivationToken(unsigned int) () at /lib/x86_64-linux-gnu/libQt6WaylandClient.so.6
#1 0x00007fffe9f14b94 in QGenericUnixServices::openUrl(QUrl const&) () at /lib/x86_64-linux-gnu/libQt6Gui.so.6
#2 0x00007fffe9db13be in QDesktopServices::openUrl(QUrl const&) () at /lib/x86_64-linux-gnu/libQt6Gui.so.6
#3 0x00007fffebfdb1d8 in () at /lib/x86_64-linux-gnu/libQt6WebEngineCore.so.6
#4 0x000000000000001b in ()
#5 0x00007ffff528a8c0 in QWebEnginePagePrivate::navigationRequested(int, QUrl const&, bool&, bool) () at /lib/x86_64-linux-gnu/libQt6WebEngineCore.so.6
#6 0x00007fffffffcc98 in ()
#7 0x01007fffffffcc98 in ()
#8 0x00007fffffffcc50 in ()
#9 0x00007fffebf1b409 in () at /lib/x86_64-linux-gnu/libQt6WebEngineCore.so.6
#10 0x000055555902ddc0 in ()
#11 0x000055555902ddd0 in ()
#12 0x000000000000001b in ()
#13 0x00005555586f6290 in ()
#14 0x0000000000000001 in ()
#15 0x000055555902de40 in ()
#16 0x0000000000000000 in ()
(gdb) quit
A debugging session is active.
Inferior 1 [process 2556] will be killed.
Quit anyway? (y or n) n
Not confirmed.
(gdb) kill
Kill the program being debugged? (y or n) y
[Inferior 1 (process 2556) killed]
(gdb) quit
<User>@<Hostname>:~$
Please note that the vendor of Tuxedo OS 3 (tuxedocomputers.com) does not seem to provide a debuginfod web domain. I had put the line
export DEBUGINFOD_URLS="https://debuginfod.ubuntu.com"
into my normal user's ~/.bashrc file because my LibreWolf browser returns the following information when trying to access a possibly existing URL https://debuginfod.tuxedocomputers.com:
"Hmm. We’re having trouble finding that site.
We can’t connect to the server at debuginfod.tuxedocomputers.com."
These are the repositories which have been defined by the vendor of my Tuxedo OS 3 installation in several files in the directory /etc/apt/sources.list.d:
deb https://deb.tuxedocomputers.com/ubuntu jammy main
deb https://txos-extra.tuxedocomputers.com/ubuntu jammy main
deb https://txos.tuxedocomputers.com/ubuntu jammy main
deb https://txos.tuxedocomputers.com/ubuntu jammy-plasma main
deb https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
deb https://mirrors.tuxedocomputers.com/ubuntu/mirror/security.ubuntu.com/ubuntu jammy-security main restricted universe multiverse
deb https://mirrors.tuxedocomputers.com/ubuntu/mirror/archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
I do not know if Tuxedocomputers changed the contents of the original deb packages provided by Ubuntu for Ubuntu 22.04 which Tuxedo OS 3 is based on. So maybe the debug symbols which I retrieved here for creating the backtrace log specified above are not the correct ones for my Tuxedo OS 3 installation.
Bug report #493407 https://bugs.kde.org/show_bug.cgi?id=493407 reports the same error messages in the console when Falkon is started from there, plus it reports an additional error message "Optimize database ..." |