indicator-datetime-service crashed with Settings schema 'com.canonical.indicator.datetime' is not installed

Bug #1304572 reported by barbablu
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
indicator-datetime (Ubuntu)
Expired
Medium
Unassigned

Bug Description

...

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: indicator-datetime 13.10.0+14.04.20140408-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
Date: Tue Apr 8 19:41:17 2014
ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
InstallationDate: Installed on 2014-03-12 (27 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140310)
ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
Signal: 5
SourcePackage: indicator-datetime
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 unity::indicator::datetime::LiveSettings::LiveSettings() ()
Title: indicator-datetime-service crashed with signal 5 in g_object_new_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
barbablu (corettistefano) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_settings_set_property (object=0x1c83030, prop_id=<optimized out>, value=<optimized out>, pspec=<optimized out>) at /build/buildd/glib2.0-2.40.0/./gio/gsettings.c:481
 object_set_property (nqueue=0x1c77810, value=<optimized out>, pspec=0x1c828d0, object=0x1c83030) at /build/buildd/glib2.0-2.40.0/./gobject/gobject.c:1378
 g_object_new_internal (class=class@entry=0x1c75d70, params=params@entry=0x7fffa1243910, n_params=1) at /build/buildd/glib2.0-2.40.0/./gobject/gobject.c:1757
 g_object_new_valist (object_type=object_type@entry=29877728, first_property_name=first_property_name@entry=0x7fe32a19238f "schema-id", var_args=var_args@entry=0x7fffa1243a68) at /build/buildd/glib2.0-2.40.0/./gobject/gobject.c:1980
 g_object_new (object_type=29877728, first_property_name=0x7fe32a19238f "schema-id") at /build/buildd/glib2.0-2.40.0/./gobject/gobject.c:1571

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in indicator-datetime (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Charles Kerr (charlesk) wrote :

Hi barbablu,

Thanks for reporting this bug and helping to make Ubuntu better. It looks like this is being caused by some configuration issue on your system -- the com.canonical.indicator.datetime schema get installed when indicator-datetime is installed, so something's gone wrong with the install on the system that got this crash.

You may be able to resolve this by uninstalling, then reinstalling, indicator-datetime on that system.

If this doesn't solve the problem, please let me know by changing the status of this ticket back to 'New' and giving any new information that you think might be helpful. Thanks!

summary: - indicator-datetime-service crashed with signal 5 in
- g_object_new_valist()
+ indicator-datetime-service crashed with Settings schema
+ 'com.canonical.indicator.datetime' is not installed
information type: Private → Public
Changed in indicator-datetime (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for indicator-datetime (Ubuntu) because there has been no activity for 60 days.]

Changed in indicator-datetime (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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