baloo_file_extractor crashed with SIGABRT in qt_message_fatal()

Bug #1765002 reported by Prasanna Loganathar on 2018-04-18
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
baloo-kf5 (Ubuntu)
Medium
Unassigned

Bug Description

Random crashes in the background.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: baloo-kf5 5.44.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Apr 18 13:04:01 2018
ExecutablePath: /usr/bin/baloo_file_extractor
InstallationDate: Installed on 2018-02-11 (65 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
ProcCmdline: /usr/bin/baloo_file_extractor
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.utf8
 SHELL=/bin/bash
Signal: 6
SourcePackage: baloo-kf5
StacktraceTop:
 QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 ?? ()
 ?? ()
 QXcbConnection::initializeScreens() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
Title: baloo_file_extractor crashed with SIGABRT in QMessageLogger::fatal()
UpgradeStatus: Upgraded to bionic on 2018-04-17 (0 days ago)
UserGroups: adm bumblebee cdrom dip docker lpadmin plugdev sambashare sudo

Prasanna Loganathar (pvl) wrote :

StacktraceTop:
 qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1690
 QMessageLogger::fatal (this=<optimized out>, msg=<optimized out>) at global/qlogging.cpp:796
 queuedConnectionTypes (typeNames=...) at kernel/qobject.cpp:92
 ?? ()
 ?? ()

Changed in baloo-kf5 (Ubuntu):
importance: Undecided → Medium
summary: - baloo_file_extractor crashed with SIGABRT in QMessageLogger::fatal()
+ baloo_file_extractor crashed with SIGABRT in qt_message_fatal()
tags: removed: need-amd64-retrace
information type: Private → Public
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in baloo-kf5 (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers