Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Trying to click through to the second page of an unordered proximity search. Version-Release number of selected component: recoll-1.43.6-1.fc43 Additional info: reporter: libreport-2.17.15 type: CCpp reason: recoll killed by SIGTRAP journald_cursor: s=f5312f51772b414d8799435cffc8070e;i=ad610;b=fe18727fe5a54fbfa1b534855daa3822;m=7248d13d;t=642af0a33dc3f;x=163289c044bd3520 executable: /usr/bin/recoll cmdline: /usr/bin/recoll cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-recoll\x2dsearchgui rootdir: / uid: 1000 kernel: 6.17.6-300.fc43.x86_64 package: recoll-1.43.6-1.fc43 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: base::ImmediateCrash comment: Trying to click through to the second page of an unordered proximity search. Truncated backtrace: Thread no. 1 (26 frames) #0 base::ImmediateCrash at ../../../../../src/3rdparty/chromium/base/immediate_crash.h:186 #1 logging::CheckFailure at ../../../../../src/3rdparty/chromium/base/check.h:254 #2 navigation_interception::InterceptNavigationThrottle::CheckIfShouldIgnoreNavigation at ../../../../../src/3rdparty/chromium/components/navigation_interception/intercept_navigation_throttle.cc:91 #3 navigation_interception::InterceptNavigationThrottle::WillStartRequest at ../../../../../src/3rdparty/chromium/components/navigation_interception/intercept_navigation_throttle.cc:41 #4 ExecuteNavigationEvent at ../../../../../src/3rdparty/chromium/content/browser/renderer_host/navigation_throttle_runner.cc:48 #5 content::NavigationThrottleRunner::ProcessInternal at ../../../../../src/3rdparty/chromium/content/browser/renderer_host/navigation_throttle_runner.cc:360 #6 content::NavigationRequest::WillStartRequest at ../../../../../src/3rdparty/chromium/content/browser/renderer_host/navigation_request.cc:7748 #7 content::NavigationRequest::BeginNavigationImpl at ../../../../../src/3rdparty/chromium/content/browser/renderer_host/navigation_request.cc:2872 #8 content::NavigationRequest::BeginNavigation at ../../../../../src/3rdparty/chromium/content/browser/renderer_host/navigation_request.cc:2452 #9 content::Navigator::OnBeginNavigation at ../../../../../src/3rdparty/chromium/content/browser/renderer_host/navigator.cc:1292 #10 content::RenderFrameHostImpl::BeginNavigation at ../../../../../src/3rdparty/chromium/content/browser/renderer_host/render_frame_host_impl.cc:10968 #11 content::mojom::FrameHostStubDispatch::Accept at gen/content/common/frame.mojom.cc:5528 #12 mojo::InterfaceEndpointClient::HandleValidatedMessage at ../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:1052 #13 mojo::MessageDispatcher::Accept at ../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/message_dispatcher.cc:48 #14 mojo::InterfaceEndpointClient::HandleIncomingMessage at ../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:724 #15 AcceptOnEndpointThread at ../../../../../src/3rdparty/chromium/ipc/ipc_mojo_bootstrap.cc:1202 #16 Invoke<void (IPC::ChannelAssociatedGroupController::*)(mojo::Message, IPC::(anonymous namespace)::ScopedUrgentMessageNotification), scoped_refptr<IPC::ChannelAssociatedGroupController>, mojo::Message, IPC::(anonymous namespace)::ScopedUrgentMessageNotification> at ../../../../../src/3rdparty/chromium/base/functional/bind_internal.h:729 #17 MakeItSo<void (IPC::ChannelAssociatedGroupController::*)(mojo::Message, IPC::(anonymous namespace)::ScopedUrgentMessageNotification), std::tuple<scoped_refptr<IPC::ChannelAssociatedGroupController>, mojo::Message, IPC::(anonymous namespace)::ScopedUrgentMessageNotification> > at ../../../../../src/3rdparty/chromium/base/functional/bind_internal.h:921 #18 RunImpl<void (IPC::ChannelAssociatedGroupController::*)(mojo::Message, IPC::(anonymous namespace)::ScopedUrgentMessageNotification), std::tuple<scoped_refptr<IPC::ChannelAssociatedGroupController>, mojo::Message, IPC::(anonymous namespace)::ScopedUrgentMessageNotification>, 0, 1, 2> at ../../../../../src/3rdparty/chromium/base/functional/bind_internal.h:1058 #19 RunOnce at ../../../../../src/3rdparty/chromium/base/functional/bind_internal.h:971 #20 base::OnceCallback<void ()>::Run() && at ../../../../../src/3rdparty/chromium/base/functional/callback.h:156 #21 base::TaskAnnotator::RunTaskImpl at ./../../../../../src/3rdparty/chromium/base/task/common/task_annotator.cc:209 #22 RunTask<base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::LazyNow*)::<lambda(perfetto::EventContext&)> > at ../../../../../src/3rdparty/chromium/base/task/common/task_annotator.h:106 #23 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl at ./../../../../../src/3rdparty/chromium/base/task/sequence_manager/thread_controller_with_message_pump_impl.cc:456 #24 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork at ./../../../../../src/3rdparty/chromium/base/task/sequence_manager/thread_controller_with_message_pump_impl.cc:330 #25 QtWebEngineCore::MessagePumpForUIQt::handleScheduledWork at /usr/src/debug/qt6-qtwebengine-6.10.0-2.fc43.x86_64/src/core/browser_main_parts_qt.cpp:153
Created attachment 2112323 [details] File: proc_pid_status
Created attachment 2112324 [details] File: maps
Created attachment 2112325 [details] File: limits
Created attachment 2112326 [details] File: environ
Created attachment 2112327 [details] File: open_fds
Created attachment 2112328 [details] File: mountinfo
Created attachment 2112329 [details] File: os_info
Created attachment 2112330 [details] File: cpuinfo
Created attachment 2112331 [details] File: core_backtrace
Created attachment 2112332 [details] File: dso_list
Created attachment 2112333 [details] File: var_log_messages
Created attachment 2112334 [details] File: backtrace
Crash seems to be in qt6-qtwebengine, changing component
A workaround is to view search results as a spreadsheet.
Upstream bug link: https://framagit.org/medoc92/recoll/-/issues/351 As of about three hours ago, this is fixed in the Recoll source. A new release should be coming shortly.
(Note to the maintainer: The next release will also include a patch I submitted to the Meson build system, that avoids installing man pages for tools that are excluded from the build. So, you'll need to remove a line from the %files section of the spec: %{_mandir}/man1/xadump.1* Since the (useless) xadump(1) man page will no longer be installed even though the tool itself _isn't_ installed.)
(In reply to "FeRD" (Frank Dana) from comment #15) > Upstream bug link: https://framagit.org/medoc92/recoll/-/issues/351 > > As of about three hours ago, this is fixed in the Recoll source. A new > release should be coming shortly. Thanks, Frank! And to Jean-Francois Dockes, if he's reading this. The bug has been a real nuisance.
Oh, I just noticed this was moved to python-pyqt6-webengine. That's doubly wrong. The issue was in the Recoll code, and Recoll doesn't use PyQt6. It's written in C++.
Thanks for helping upstream to fix the original issue! recoll 1.43.10 should contain the fixes, right?
FEDORA-2026-55e0885332 (recoll-1.43.10-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2026-55e0885332
FEDORA-2026-6f4df063bf (recoll-1.43.10-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-6f4df063bf
FEDORA-EPEL-2026-58e814b635 (recoll-1.43.10-1.el10_2) has been submitted as an update to Fedora EPEL 10.2. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-58e814b635
FEDORA-EPEL-2026-58e814b635 has been pushed to the Fedora EPEL 10.2 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-58e814b635 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
(In reply to Terje Rosten from comment #19) > Thanks for helping upstream to fix the original issue! > > recoll 1.43.10 should contain the fixes, right? Sorry for the delay — just to confirm, yes it does.
FEDORA-2026-55e0885332 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-55e0885332` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-55e0885332 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-6f4df063bf has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-6f4df063bf` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-6f4df063bf See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-3dd199bb1e has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-3dd199bb1e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-3dd199bb1e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-455fe69d57 has been pushed to the Fedora EPEL 10.2 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-455fe69d57 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-c244aa6bf7 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-c244aa6bf7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-c244aa6bf7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Do a search Click next page Crash reporter: libreport-2.17.15 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-dbus\x2d:1.2\x2dorg.mate.panel.applet.MateMenuAppletFactory.slice/dbus-:1.2-org.mate.panel.applet.MateMenuAppletFactory backtrace_rating: 4 xsession_errors: crash_function: base::ImmediateCrash package: recoll-1.43.9-1.fc43 uid: 1000 journald_cursor: s=495e60fdf29044a88ab7e2a2de2db319;i=e99d13;b=a46656a3490b499298c381753a25721f;m=2ecd40051;t=6497aaa548f3e;x=49eb377511a0936e runlevel: /bin/sh: line 1: runlevel: command not found type: CCpp kernel: 6.18.6-200.fc43.x86_64 executable: /usr/bin/recoll cmdline: /usr/bin/recoll reason: recoll killed by SIGTRAP rootdir: /
FEDORA-2026-3dd199bb1e (recoll-1.43.12-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-c244aa6bf7 (recoll-1.43.12-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2026-e66a2b1fef has been pushed to the Fedora EPEL 10.2 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-e66a2b1fef See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.