tracker-miner-fs crashed with SIGSEGV in up_exported_daemon_get_on_battery()

[Сергей Терещенко]

UBUNTU BAGS

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: tracker-miner-fs 1.6.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic i686
ApportVersion: 2.20-0ubuntu3
Architecture: i386
CurrentDesktop: Unity
Date: Mon Apr 4 08:41:34 2016
ExecutablePath: /usr/lib/tracker/tracker-miner-fs
InstallationDate: Installed on 2016-03-31 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160331)
ProcCmdline: /usr/lib/tracker/tracker-miner-fs
ProcEnviron:
 LANGUAGE=ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb737f77d <up_exported_daemon_get_on_battery+29>: pushl (%esi)
 PC (0xb737f77d) ok
 source "(%esi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "(%esp)" (0xbfe98664) ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
 up_exported_daemon_get_on_battery () from /usr/lib/i386-linux-gnu/libupower-glib.so.3
 up_client_get_on_battery () from /usr/lib/i386-linux-gnu/libupower-glib.so.3
 ?? ()
 ?? ()
 g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: tracker-miner-fs crashed with SIGSEGV in up_exported_daemon_get_on_battery()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 up_exported_daemon_get_on_battery (object=0x0) at up-daemon-generated.c:716
 up_client_get_on_battery (client=0xb380a180) at up-client.c:242
 on_on_battery_changed ()
 tracker_power_init ()
 ?? ()

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Launchpad Janitor (janitor)]

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