baloo_file_extractor crashed with SIGSEGV in wl_proxy_marshal_array_flags()

Bug #2011638 reported by Michael Navigator
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
baloo-kf5 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Fresh install from Kubuntu 23.04 daily image.

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: baloo-kf5 5.103.0-0ubuntu1
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Tue Mar 14 22:11:36 2023
ExecutablePath: /usr/lib/x86_64-linux-gnu/libexec/baloo_file_extractor
InstallationDate: Installed on 2023-03-14 (0 days ago)
InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230314)
ProcCmdline: /usr/lib/x86_64-linux-gnu/libexec/baloo_file_extractor
ProcEnviron:
 LANG=pt_PT.UTF-8
 LANGUAGE=pt:pt_BR:en
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7ff60a773a9d <__strlen_avx2+29>: vpcmpeqb (%rdi),%ymm0,%ymm1
 PC (0x7ff60a773a9d) ok
 source "(%rdi)" (0x55e8059f06c4) not located in a known VMA region (needed readable region)!
 destination "%ymm0" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: baloo-kf5
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libwayland-client.so.0
 ?? () from /lib/x86_64-linux-gnu/libwayland-client.so.0
 wl_proxy_marshal_array_flags () from /lib/x86_64-linux-gnu/libwayland-client.so.0
 wl_proxy_marshal_flags () from /lib/x86_64-linux-gnu/libwayland-client.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeWaylandPlugin.so
Title: baloo_file_extractor crashed with SIGSEGV in wl_proxy_marshal_array_flags()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
separator:

Revision history for this message
Michael Navigator (cbnavigator) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 wl_map_insert_at (map=map@entry=0x55ed5b4b5c20, flags=flags@entry=1, i=23, data=<optimized out>) at ../src/wayland-util.c:276
 proxy_destroy (proxy=proxy@entry=0x55ed5b4e4a50) at ../src/wayland-client.c:510
 wl_proxy_destroy_caller_locks (proxy=0x55ed5b4e4a50) at ../src/wayland-client.c:530
 wl_proxy_marshal_array_flags (proxy=proxy@entry=0x55ed5b4e4a50, opcode=opcode@entry=0, interface=interface@entry=0x0, version=version@entry=1, flags=flags@entry=1, args=args@entry=0x7fff312fa020) at ../src/wayland-client.c:868
 wl_proxy_marshal_flags (proxy=0x55ed5b4e4a50, opcode=0, interface=0x0, version=1, flags=1) at ../src/wayland-client.c:791

tags: removed: need-amd64-retrace
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.