indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-datetime (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I started the computer, and some thing crashed.
Regards,
Pankaj Pal
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: indicator-datetime 12.10.3daily13.
ProcVersionSign
Uname: Linux 3.8.0-14-generic i686
ApportVersion: 2.9.2-0ubuntu2
Architecture: i386
Date: Mon Mar 25 21:26:59 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2012-11-22 (122 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MarkForUpload: True
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x804d97f: mov 0x8(%eax),%eax
PC (0x0804d97f) ok
source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
?? ()
g_cclosure_
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
Title: indicator-
UpgradeStatus: Upgraded to raring on 2013-01-22 (61 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
XsessionErrors:
gnome-
(process:2495): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
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 #1132174, 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.