tracker-miner-fs-3 crashed with SIGABRT

Bug #1962633 reported by Mark Dominik Bürkle
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tracker-miners (Ubuntu)
New
Undecided
Unassigned

Bug Description

like bug##1843262 but instead of tracker-miner-fs it is tracker-miner-fs-3 with ABRT.

auto collected data, did not check.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: tracker-miner-fs 3.3.0~beta-1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Feb 28 11:15:47 2022
ExecutablePath: /usr/libexec/tracker-miner-fs-3
ExecutableTimestamp: 1645729202
InstallationDate: Installed on 2018-12-10 (1177 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcCmdline: /usr/libexec/tracker-miner-fs-3
ProcCwd: /home/mdb
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
Signal: 6
SourcePackage: tracker-miners
StacktraceTop:
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_free1 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: tracker-miner-fs-3 crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
separator:

Revision history for this message
Mark Dominik Bürkle (dominik-buerkle) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1962495, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Mark Dominik Bürkle (dominik-buerkle) wrote :

might affect bugs:
1955758
1962495
1962623
1962624
1962626
1962630
1962633
I will add this text to all open bugs.

affected parts:
tracker-miner-fs-3
totem
gvfsd-mtp
udisksd

background information:
- installed 18.04 lts
- dist-upgraded to 20.04 lts
- back up before sending hardware for repair, got replacement hardware (with default rubbish)
- restore on replaced hardware with
-- modified filesystem (btrfs, dont remember previously used fs) and
-- full-disk encryption (multiple luks2 partitions instead of home-only)
- noticed that integrating grub-2.06 correctly (building package etc) would be too much effort
- downgraded luks-headers from luks2 to luks1 to make it compatible with grub used in 20.04
- added grub-setup script to include cryptmount grub module etc.
- got btrfs kernel warnings regularly
- dist-upgraded to 22.04 lts (beta, late January)
- still btrfs kernel warnings regularly
[- many updates since, as to be expected.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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