indicator-datetime-service crashed with SIGSEGV in g_main_context_dispatch()

Bug #731640 reported by Chris Halse Rogers
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-datetime (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: indicator-datetime

This will probably be a duplicate of bug 729444, but filing incase the backtrace suggests something different.

Like 729444, this happens dependably at logon.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-datetime 0.1.96-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic x86_64
Architecture: amd64
Date: Wed Mar 9 09:29:45 2011
ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110117)
ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service
ProcEnviron:
 SHELL=/bin/zsh
 LANGUAGE=en_AU:en_GB:en
 LANG=en_AU.utf8
SegvAnalysis:
 Segfault happened at: 0x4048fa: mov 0x0(%rbp,%rcx,1),%edx
 PC (0x004048fa) ok
 source "0x0(%rbp,%rcx,1)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
Title: indicator-datetime-service crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to natty on 2011-03-08 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare sbuild

Revision history for this message
Chris Halse Rogers (raof) 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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #729444, 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.

visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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