Crash during Clock application start on Desktop

Bug #1475223 reported by Bartosz Kosiorek on 2015-07-16
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Ubuntu Clock App
High
Unassigned
ubuntu-ui-toolkit (Ubuntu)
Undecided
Unassigned

Bug Description

Statistically once per 8 Clock runs, the application is crashing with following BackTrace:

#0 0x00007ffff54539fc in g_type_check_instance (type_instance=type_instance@entry=0xf1a0b0) at /build/buildd/glib2.0-2.44.1/./gobject/gtype.c:4136
#1 0x00007ffff54496fe in g_signal_emit_valist (instance=0xf1a0b0, signal_id=289, detail=0, var_args=var_args@entry=0x7fffffffd250)
    at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3090
#2 0x00007ffff544a8ff in g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3361
#3 0x00007fffbe19e271 in () at /usr/lib/x86_64-linux-gnu/libgeoclue.so.0
#4 0x00007fffdfb0ef3c in marshal_dbus_message_to_g_marshaller (closure=0x1520db0, return_value=0x0, n_param_values=<optimized out>, param_values=<optimized out>, invocation_hint=0x7fffffffd530, marshal_data=0x0) at dbus-gproxy.c:1736
#8 0x00007ffff544a8ff in <emit signal received:org-freedesktop-Geoclue-MasterClient-PositionProviderChanged on instance 0xf0f780 [DBusGProxy]> (instance=instance@entry=0xf0f780, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3361
    #5 0x00007ffff54302d5 in g_closure_invoke (closure=0x1520db0, return_value=0x0, n_param_values=3, param_values=0x7fffffffd590, invocation_hint=0x7fffffffd530)
    at /build/buildd/glib2.0-2.44.1/./gobject/gclosure.c:768
    #6 0x00007ffff544203c in signal_emit_unlocked_R (node=node@entry=0x151e740, detail=detail@entry=1533, instance=instance@entry=0xf0f780, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffffffd590) at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3549
    #7 0x00007ffff544a698 in g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fffffffd740)
    at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3305
#9 0x00007fffdfb0f882 in dbus_g_proxy_manager_filter (message=0x5307c0, proxy=0xf0f780 [DBusGProxy]) at dbus-gproxy.c:1789
#10 0x00007fffdfb0f882 in dbus_g_proxy_manager_filter (connection=<optimized out>, message=0x5307c0, user_data=0xf1f540) at dbus-gproxy.c:1356
#11 0x00007fffec3e21d1 in dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3
#12 0x00007fffdfb095d5 in message_queue_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at dbus-gmain.c:90
#13 0x00007ffff515ac3d in g_main_context_dispatch (context=0x7fffe40016f0) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3122
#14 0x00007ffff515ac3d in g_main_context_dispatch (context=context@entry=0x7fffe40016f0) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3737
#15 0x00007ffff515af20 in g_main_context_iterate (context=context@entry=0x7fffe40016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>)
    at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3808
---Type <return> to continue, or q <return> to quit---
#16 0x00007ffff515afcc in g_main_context_iteration (context=0x7fffe40016f0, may_block=1) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3869
#17 0x00007ffff67bcc57 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007ffff67613e2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007ffff676902c in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x0000000000404098 in ()
#21 0x00007ffff5ac1a40 in __libc_start_main (main=
    0x4037d0, argc=4, argv=0x7fffffffdf38, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffdf28) at libc-start.c:289
#22 0x00000000004058b9 in ()

summary: - Crash during start
+ Crash during Clock application start
description: updated
description: updated
summary: - Crash during Clock application start
+ Crash during Clock application start on Desktop
Victor Thompson (vthompson) wrote :

I think I observe this as well. Running the app from QtCreator causes it to crash frequently for me.

Launchpad Janitor (janitor) wrote :

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

Changed in ubuntu-ui-toolkit (Ubuntu):
status: New → Confirmed
Changed in ubuntu-clock-app:
milestone: none → 3.x.backlog
Changed in ubuntu-clock-app:
importance: Undecided → High
status: New → Confirmed
Marcus Endberg (ubuntu5one) wrote :

Today I've updated my BQ 4.5 phone to Ubuntu 15.04 (OTA-12), can not open clock APP any more. Just after the splash screen appears it closes immediately.

Bartosz Kosiorek (gang65) wrote :

@Marcus

Please create separate bug report for that crash, and attach logs.
Here you have instruction how to gather logs:
http://askubuntu.com/questions/548504/ubuntu-sdk-how-can-i-see-error-logs-for-my-ubuntu-touch-app

Marcus Endberg (ubuntu5one) wrote :

@Bartosz

Thank you for the hint, I'll do so.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers