[Bug 1475223] Re: Crash during Clock application start on Desktop

2016-07-29 Thread Marcus Endberg
@Bartosz

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475223

Title:
  Crash during Clock application start on Desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1475223/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1475223] Re: Crash during Clock application start on Desktop

2016-07-29 Thread Bartosz Kosiorek
@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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475223

Title:
  Crash during Clock application start on Desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1475223/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1475223] Re: Crash during Clock application start on Desktop

2016-07-28 Thread Marcus Endberg
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.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475223

Title:
  Crash during Clock application start on Desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1475223/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1475223] Re: Crash during Clock application start on Desktop

2015-08-26 Thread Nekhelesh Ramananthan
** Changed in: ubuntu-clock-app
   Importance: Undecided => High

** Changed in: ubuntu-clock-app
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475223

Title:
  Crash during Clock application start on Desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1475223/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1475223] Re: Crash during Clock application start on Desktop

2015-08-16 Thread Nekhelesh Ramananthan
** Changed in: ubuntu-clock-app
Milestone: None => 3.x.backlog

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475223

Title:
  Crash during Clock application start on Desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1475223/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1475223] Re: Crash during Clock application start on Desktop

2015-07-17 Thread Victor Thompson
I think I observe this as well. Running the app from QtCreator causes it
to crash frequently for me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475223

Title:
  Crash during Clock application start on Desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1475223/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1475223] Re: Crash during Clock application start on Desktop

2015-07-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475223

Title:
  Crash during Clock application start on Desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1475223/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1475223] Re: Crash during Clock application start

2015-07-16 Thread Bartosz Kosiorek
** Summary changed:

- Crash during start
+ Crash during Clock application start

** Description changed:

- Statistically one per 5 clock runs, the application is crashing with
+ Statistically one per 8 clock runs, the application is crashing with
  following BackTrace:
  
  #0  0x754539fc in g_type_check_instance 
(type_instance=type_instance@entry=0xf1a0b0) at 
/build/buildd/glib2.0-2.44.1/./gobject/gtype.c:4136
  #1  0x754496fe in g_signal_emit_valist (instance=0xf1a0b0, 
signal_id=289, detail=0, var_args=var_args@entry=0x7fffd250)
- at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3090
+ at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3090
  #2  0x7544a8ff in g_signal_emit (instance=, 
signal_id=, detail=) at 
/build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3361
  #3  0x7fffbe19e271 in  () at /usr/lib/x86_64-linux-gnu/libgeoclue.so.0
  #4  0x7fffdfb0ef3c in marshal_dbus_message_to_g_marshaller 
(closure=0x1520db0, return_value=0x0, n_param_values=, 
param_values=, invocation_hint=0x7fffd530, marshal_data=0x0) 
at dbus-gproxy.c:1736
  #8  0x7544a8ff in  (instance=instance@entry=0xf0f780, 
signal_id=, detail=) at 
/build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3361
- #5  0x754302d5 in g_closure_invoke (closure=0x1520db0, 
return_value=0x0, n_param_values=3, param_values=0x7fffd590, 
invocation_hint=0x7fffd530)
- at /build/buildd/glib2.0-2.44.1/./gobject/gclosure.c:768
- #6  0x7544203c 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=0x7fffd590) at 
/build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3549
- #7  0x7544a698 in g_signal_emit_valist (instance=, 
signal_id=, detail=, 
var_args=var_args@entry=0x7fffd740)
- at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3305
+ #5  0x754302d5 in g_closure_invoke (closure=0x1520db0, 
return_value=0x0, n_param_values=3, param_values=0x7fffd590, 
invocation_hint=0x7fffd530)
+ at /build/buildd/glib2.0-2.44.1/./gobject/gclosure.c:768
+ #6  0x7544203c 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=0x7fffd590) at 
/build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3549
+ #7  0x7544a698 in g_signal_emit_valist (instance=, 
signal_id=, detail=, 
var_args=var_args@entry=0x7fffd740)
+ at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3305
  #9  0x7fffdfb0f882 in dbus_g_proxy_manager_filter (message=0x5307c0, 
proxy=0xf0f780 [DBusGProxy]) at dbus-gproxy.c:1789
  #10 0x7fffdfb0f882 in dbus_g_proxy_manager_filter (connection=, message=0x5307c0, user_data=0xf1f540) at dbus-gproxy.c:1356
  #11 0x7fffec3e21d1 in dbus_connection_dispatch () at 
/lib/x86_64-linux-gnu/libdbus-1.so.3
  #12 0x7fffdfb095d5 in message_queue_dispatch (source=, 
callback=, user_data=) at dbus-gmain.c:90
  #13 0x7515ac3d in g_main_context_dispatch (context=0x7fffe40016f0) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:3122
  #14 0x7515ac3d in g_main_context_dispatch 
(context=context@entry=0x7fffe40016f0) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:3737
  #15 0x7515af20 in g_main_context_iterate 
(context=context@entry=0x7fffe40016f0, block=block@entry=1, 
dispatch=dispatch@entry=1, self=)
- at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3808
+ at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3808
  ---Type  to continue, or q  to quit---
  #16 0x7515afcc in g_main_context_iteration (context=0x7fffe40016f0, 
may_block=1) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3869
  #17 0x767bcc57 in 
QEventDispatcherGlib::processEvents(QFlags) () 
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #18 0x767613e2 in 
QEventLoop::exec(QFlags) () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #19 0x7676902c in QCoreApplication::exec() () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #20 0x00404098 in  ()
  #21 0x75ac1a40 in __libc_start_main (main=
- 0x4037d0, argc=4, argv=0x7fffdf38, init=, 
fini=, rtld_fini=, stack_end=0x7fffdf28) at 
libc-start.c:289
+ 0x4037d0, argc=4, argv=0x7fffdf38, init=, 
fini=, rtld_fini=, stack_end=0x7fffdf28) at 
libc-start.c:289
  #22 0x004058b9 in  ()

** Description changed:

- Statistically one per 8 clock runs, the application is crashing with
+ Statistically once per 8 Clock runs, the application is crashing with
  following BackTrace:
  
  #0  0x754539fc in g_type_check_instance 
(type_instance=type_instance@entry=0xf1a0b0) at 
/build/buildd/glib2.0-2.44.1/./gobject/gtype.c:4136
  #1  0x754496fe in g_signal_emit_valist (instance=0xf1a0b0, 
sign