activity-log-manager crashed with SIGSEGV in g_str_hash()

Bug #932355 reported by jlb181 on 2012-02-14
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Activity Log Manager
activity-log-manager (Ubuntu)

Bug Description

I was adding a directory I wanted ignored. After, I minimized the program to the launcher. Not 1 minute later it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: activity-log-manager 0.9.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Feb 14 16:34:36 2012
ExecutablePath: /usr/bin/activity-log-manager
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.2)
ProcCmdline: activity-log-manager
 PATH=(custom, no user)
 Segfault happened at: 0x7f4953a746e0 <g_str_hash>: movzbl (%rdi),%edx
 PC (0x7f4953a746e0) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: activity-log-manager
 g_str_hash () from /lib/x86_64-linux-gnu/
 ?? () from /usr/lib/
 ?? () from /usr/lib/
 alm_files_widget_construct ()
 alm_activity_log_manager_construct ()
Title: activity-log-manager crashed with SIGSEGV in g_str_hash()
UpgradeStatus: No upgrade log present (probably fresh install)

jlb181 (jeffery-birkhofer) wrote :
visibility: private → public

 g_str_hash (v=0x0) at /build/buildd/glib2.0-2.31.16/./glib/ghash.c:1722
 gee_hash_map_lookup_node (self=0xfefe90, key=0x0) at hashmap.c:951
 gee_hash_map_real_set (base=0xfefe90, key=0x0, value=0x1) at hashmap.c:1109
 alm_files_widget_construct (object_type=<optimized out>, blacklist_interface=<optimized out>) at files-widget.c:1511
 alm_activity_log_manager_construct (object_type=<optimized out>) at activity-log-manager.c:214

Changed in activity-log-manager (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace

Sadly I am not able to reproduce this,

Launchpad Janitor (janitor) wrote :

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

Changed in activity-log-manager (Ubuntu):
status: New → Confirmed
Mohamed Alaa (m-alaa8) on 2012-03-13
Changed in activity-log-manager:
status: New → Confirmed
Paolo Stivanin (polslinux) wrote :

me also :(

Is anyone still able to get this? on 0.9.4 +

Changed in activity-log-manager:
status: Confirmed → Triaged
Changed in activity-log-manager:
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers