** Changed in: canonical-devices-system-image
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1425297
Title:
Sometimes
This bug was fixed in the package indicator-datetime -
13.10.0+15.04.20150318~rtm-0ubuntu1
---
indicator-datetime (13.10.0+15.04.20150318~rtm-0ubuntu1) 14.09; urgency=medium
[ Charles Kerr ]
* Work around glib's type initialization deadlock. (LP: #1425297)
-- CI Train BotWed,
This has been in RTM silo 4 since the 18th and is waiting on QA signoff.
I'll ping QA and see if we can get this landed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net
charles can we land this in rtm please
** Changed in: indicator-datetime (Ubuntu RTM)
Status: Won't Fix => In Progress
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Charles Kerr (charlesk)
--
You received this bug notification because you are a member of Ub
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Status: New => In Progress
** Changed in: canonical-devices-system-image
This bug isn't cleared for rtm-14.09, so closing that Affects here.
** Changed in: indicator-datetime (Ubuntu RTM)
Status: In Progress => Won't Fix
** Changed in: indicator-datetime (Ubuntu RTM)
Assignee: Charles Kerr (charlesk) => (unassigned)
--
You received this bug notification
This bug was fixed in the package indicator-datetime -
13.10.0+15.04.20150301-0ubuntu1
---
indicator-datetime (13.10.0+15.04.20150301-0ubuntu1) vivid; urgency=medium
[ CI Train Bot ]
* New rebuild forced.
[ Charles Kerr ]
* Work around glib's type initialization deadlock. (LP
** Branch linked: lp:~charlesk/indicator-datetime/lp-1425297-prevent-
gdbusproxy-type-init-deadlock-rtm-14.09
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/142529
** Changed in: indicator-datetime (Ubuntu RTM)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1425297
Title:
Sometimes indicato
** Branch linked: lp:~charlesk/indicator-datetime/lp-1425297-prevent-
gdbusproxy-type-init-deadlock-trunk-15.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1425
I was able to reproduce this bug after many, many reboots.
The relevant gdb trace is:
> Thread 2 (Thread 0xb1eff3c0 (LWP 2818)):
> #0 0xb69a84b0 in syscall () from /lib/arm-linux-gnueabihf/libc.so.6
> #1 0xb6b51112 in g_cond_wait () from
> /lib/arm-linux-gnueabihf/libglib-2.0.so.0
> #2 0xb6b3
Also, if you could include the output of
$ gdbus call --session --dest org.freedesktop.DBus --object-path /
--method org.freedesktop.DBus.GetNameOwner
com.canonical.indicator.datetime
that should at least tell us whether or not indicator-datetime-service
reached the point of owning its name on t
>From what aacid's said in IRC and in duplicate bug #1421919, indicator-
datetime-service is still running but is not responding to dbus-send
messages.
If anyone experiences this in the future, a gdb backtrace could be
helpful here -- I'm wondering if the code is deadlocked somewhere s.t.
it's una
Also happens with RTM.
** Also affects: indicator-datetime (Ubuntu RTM)
Importance: Undecided
Status: New
** Summary changed:
- Sometimes indicator-datetime is not available in the UI after a reboot
(vivid/mako)
+ Sometimes indicator-datetime is not available in the UI after a reboot
** Changed in: indicator-datetime (Ubuntu)
Assignee: (unassigned) => Charles Kerr (charlesk)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1425297
Title:
For a data point, I've seen this a couple times before the timerfd stuff
landed. So I'm pretty sure that isn't the culprit.
I've not been able to recreate it reliably. But with U8 in Vivid, I've
been rebooting a lot :-)
** Changed in: indicator-datetime (Ubuntu)
Importance: Undecided => High
The process was active and running, just not showing in the UI. After
killing the service it worked fine on the following respawn.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.laun
17 matches
Mail list logo
