libedataserver crashed with signal 5 in clock-app

Bug #1376256 reported by Omer Akram
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
qtorganizer5-eds (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Not really sure what happened. Found the crash file here http://ci.ubuntu.com/smokeng/utopic/touch/mako/264:20141001:20140929.1/10758/ubuntu_clock_app/1761864/

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: qmlscene 5.3.0-3ubuntu12
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.7-0ubuntu2
Architecture: armhf
CurrentDesktop: Unity
Date: Wed Oct 1 05:04:18 2014
ExecutablePath: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene
ExecutableTimestamp: 1410860063
InstallationDate: Installed on 2014-10-01 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141001-020204)
ProcCmdline: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ share/qml/ubuntu-clock-app.qml
ProcCwd: /usr/share/click/preinstalled/com.ubuntu.clock/3.1.125
Signal: 5
SourcePackage: qtdeclarative-opensource-src
StacktraceTop: ?? () from /usr/lib/arm-linux-gnueabihf/libgio-2.0.so.0
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dialout dip plugdev sudo tty video

Revision history for this message
Omer Akram (om26er) wrote :
information type: Private → Public
Revision history for this message
Omer Akram (om26er) wrote :

So it seems qmlscene crashed while launching the clock app

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

StacktraceTop:
 g_settings_set_property (object=0x3c4618, prop_id=<optimized out>, value=<optimized out>, pspec=<optimized out>) at /build/buildd/glib2.0-2.41.5/./gio/gsettings.c:476
 object_set_property (nqueue=<optimized out>, value=<optimized out>, pspec=0x36af98, object=<optimized out>) at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:1415
 g_object_new_internal (class=0x3c38a8, class@entry=0x0, params=params@entry=0xbea0a55c, n_params=n_params@entry=1) at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:1808
 g_object_new_valist (object_type=object_type@entry=3579824, first_property_name=first_property_name@entry=0xb34be8c4 "schema-id", var_args=..., var_args@entry=...) at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:2034
 g_object_new (object_type=3579824, first_property_name=0xb34be8c4 "schema-id") at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:1617

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 qtdeclarative-opensource-src (Ubuntu):
importance: Undecided → Medium
tags: removed: need-armhf-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: qmlscene crashed with signal 5

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

Changed in qtdeclarative-opensource-src (Ubuntu):
status: New → Confirmed
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

This happens somewhere in eds, so I'm guessing qtorganizer5-eds could possibly do something about not crashing unless it's a severe Evolution bug that needs fixing directly there.

affects: qtdeclarative-opensource-src (Ubuntu) → qtorganizer5-eds (Ubuntu)
summary: - qmlscene crashed with signal 5
+ libedataserver crashed with signal 5 in clock-app
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

(note: all QML apps always state it's "qmlscene" that crashes, and the actual crash place can usually be found from the stacktrace)

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.