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

[jlb181]

Simply trying to start Activity Log Manager. It has not started since I installed it. This start was done at the command line using sudo.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: activity-log-manager 0.9.0.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
Uname: Linux 3.2.0-15-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Sun Feb 12 09:37:38 2012
ExecutablePath: /usr/bin/activity-log-manager
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.2)
ProcCmdline: activity-log-manager
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f51413b4640 <g_str_hash>: movzbl (%rdi),%edx
 PC (0x7f51413b4640) 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
StacktraceTop:
 g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/libgee.so.2
 ?? () from /usr/lib/libgee.so.2
 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)
UserGroups:

[jlb181 (jeffery-birkhofer)]

The output I received in the terminal

jeffery@Birkhofer-Aspire-X1430G:~$ sudo activity-log-manager
[sudo] password for jeffery:
====>
2012 2 12
2012 2 12
jeffery@Birkhofer-Aspire-X1430G:~$

[Sam_ (and-sam)]

Possibly dupe of bug 928946

[Apport retracing service (apport)]

StacktraceTop:
 g_hash_table_get_values (hash_table=0x0) at /build/buildd/glib2.0-2.31.16/./glib/ghash.c:1654
 gee_hash_map_lookup_node (self=0x1585e90, key=0x0) at hashmap.c:951
 gee_hash_map_real_set (base=0x1585e90, key=0x0, value=0x1) at hashmap.c:1109
 alm_files_widget_construct (object_type=<optimized out>, blacklist_interface=<optimized out>) at files-widget.c:1464
 alm_activity_log_manager_construct (object_type=<optimized out>) at activity-log-manager.c:215

[Manish Sinha (मनीष सिन्हा) (manishsinha)]

Can someone check out the latest 0.9.1 and confirm if this can be reproduced?