Description of problem: When run falkon on i586 the pages never loads not even falkon:start In terminal i get falkon Falkon: Creating new profile directory Error creating database schema "Consulta vacía No es posible obtener la fila" Falkon: Python plugin support initialized Library plugin "KDEFrameworksIntegration.so" not found Falkon: 1 extensions loaded ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383 Version-Release number of selected component (if applicable): How reproducible: with current version of falkon or testing version in bug#32953 Steps to Reproduce: 1. On i586 system run falkon 2. start page never load 3. try to load other url 4 page never load
Current : falkon-23.04.1-1.mga9 In testing: falkon-23.04.3-1.mga9 Falkon is my preferred browser - x64. I am surprised that this is the first x32 alert about it. BTAIM Assigning to neoclust who deals with this among many other Plasma things. It looks like a build issue.
Assignee: bugsquad => mageiaSummary: falkon not load pages on i586 => falkon does not load pages on i586Source RPM: falkon => falkon-23.04.1-1.mga9.src.rpm
CC'ing TJ to ask 32-bit testers to probe this application; currently in testing (or the original).
CC: (none) => andrewsfarm
MGA9-32 Plasma, AMD Phenom II X4 910, AMD HD 8490 graphics, using the server kernel. I installed falkon and ran it from the command line. The GUI came up, but there were messages at the top that indicated it was trying to initialize. Eventually, it crashed with a LOT of verbiage in the terminal, most of it indicating a loop. I updated everything installed with the new KDE applications, but it made no difference. KDEFrameworksIntegration.so is provided by falkon-kde. Installing it removes the message that it is missing, but that's about all Ths is a sample of what I see in the terminal: $ falkon Falkon: Python plugin support initialized Please register the custom scheme 'cifs' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'filenamesearch' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'thumbnail' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'xz' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'zeroconf' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'timeline' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'recentlyused' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'smb' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'tar' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'obexftp' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'ar' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'metainfo' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'webdav' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'clementine-feed' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'clementine-itms' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'bzip2' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'bookmarks' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'audiocd' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'activities' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'baloosearch' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'fonts' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'ldaps' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'camera' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'zstd' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'clementine-itpc' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'nfs' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'sevenz' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'info' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'akonadi' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'webdavs' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'bzip' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'mtp' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'help' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'lzma' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'desktop' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'tags' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'ms-its' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'sftp' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'recentdocuments' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'ldap' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'videodvd' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'gzip' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'man' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'trash' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'kdeconnect' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'afc' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'fish' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'clementine-zune' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'remote' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'programs' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'applications' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'bluetooth' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'zip' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Please register the custom scheme 'ghelp' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Falkon: 2 extensions loaded ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 03830383 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383 and much more...
A 64-bit install on the same hardware produces the same messages in the terminal, up to the point where they say "**CRASHING**" and it works in spite of them.
(In reply to Thomas Andrews from comment #4) > A 64-bit install on the same hardware produces the same messages in the > terminal, up to the point where they say "**CRASHING**" and it works in > spite of them. In my actual 64b system works, this message is posted from falkon And joselp from atelier is also very happy with this browser
Hardware: i586 => AllSummary: falkon does not load pages on i586 => falkon does not load pages or crash in old hardware
(In reply to katnatek from comment #5) > (In reply to Thomas Andrews from comment #4) > > A 64-bit install on the same hardware produces the same messages in the > > terminal, up to the point where they say "**CRASHING**" and it works in > > spite of them. > > In my actual 64b system works, this message is posted from falkon > > And joselp from atelier is also very happy with this browser And In this hardware not produce any "**CRASHING**" message
lscpu Architecture: i686 CPU op-mode(s): 32-bit, 64-bit Model name: Intel(R) Core(TM) i5-3340M CPU @ 2.70GHz inxi -S System: Host: localhost Kernel: 6.6.18-desktop-1.mga9 arch: i686 bits: 32 Desktop: Xfce v: 4.18.1 Distro: Mageia 9 for me, invoking from cli $ falkon results in ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 03830383 repeating until I killed it. ^C real 7m23.156s user 5m24.080s sys 1m30.430s would not load a local page.
CC: (none) => westel
Thank you both for trying this. @katnatek Again, please say whether you are on real h/w or VB. Post O/P of: $ inxi -MSG falkon-23.04.1-1.mga9 On my x64 system, starting Falkon from terminal gives just: $ falkon Falkon: Python plugin support initialized Falkon: 1 extensions loaded and as usual, it works a treat. My only qualm about it is that some too-clever-by-half sites refuse it as not being recent enough; pooh ! Re-assigning to KDE/Plasma, just CC'ing neoclust.
CC: (none) => mageiaAssignee: mageia => kdeHardware: All => i586Summary: falkon does not load pages or crash in old hardware => falkon does not load pages ,or crashes, on 32-bit hardware
RH mageia 9 i586 LC_ALL=C lscpu Architecture: i686 CPU op-mode(s): 32-bit, 64-bit Address sizes: 36 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Vendor ID: GenuineIntel BIOS Vendor ID: Intel(R) Corporation Model name: Intel(R) Pentium(R) Dual CPU T2370 @ 1.73GHz BIOS Model name: Intel(R) Pentium(R) Dual CPU T2370 @ 1.73GHz FFFF CPU @ 1.7GHz BIOS CPU family: 185 CPU family: 6 Model: 15 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 Stepping: 13 CPU(s) scaling MHz: 61% CPU max MHz: 1733.0000 CPU min MHz: 800.0000 BogoMIPS: 3458.00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe nx lm constant_tsc arch_perfmon pebs bts cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx1 6 xtpr pdcm lahf_lm pti dtherm Requested information will come later
Changing the summary once again. The messages I saw with my 64-bit install disappear if I remove falkon-kde. They seem to concern themselves with configuring various KDE applications as "helpers" to the browser. Removing the one package only leaves the "Library plugin "KDEFrameworksIntegration.so" not found" message, and the browser works as it should. However, In a 32-bit install on the same hardware, removing falkon-kde removes the "Please register..." messages, as it does in the 64-bit install, but I still get the messages containing the word "CRASHING" as before. They continue until I stop it. While it is trying to start, there is an impossibly long url that it acts like it is trying to load, but can't. So, this issue appears to be on ALL 32-bit installs, regardless of hardware.
Summary: falkon does not load pages ,or crashes, on 32-bit hardware => falkon does not load pages ,or crashes, in 32-bit installs
valid for Mga10 cauldron
I see the same problem on mga9, lxde, Thinkpad T43. First time in years I have tried Falkon on i586 as I usually do not surf on that machine nowadays...
CC: (none) => fri