The problem went away in 17.10. Cheers.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100%
*** This bug is a duplicate of bug 774071 ***
https://bugs.launchpad.net/bugs/774071
The problem went away in 17.10. Cheers.
** This bug has been marked a duplicate of bug 774071
Indicator-datetime-service renders 100% CPU usage
--
You received this bug notification because you are a me
Last work-around didn't stick. Don't think this bug or #1731939 is about
indicator-datetime-service. It seems to be evolution calendar that is
the problem. See comment below:
https://bugs.launchpad.net/ubuntu/+source/indicator-
datetime/+bug/1731939/comments/4
Will test 17.10 now.
--
You receiv
Last work-around didn't stick. Did some test and can reproduce the error
now easily in 17.04. Ubuntu reports it is the Indicator-datetime-service
that crashes when its the evolution calendar that is the problem. During
the system overload the problem can be fixed by killing all evolution
processes
Sorry, wrote incorrect. Reported for 17.04 LTS above.
Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the t
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https:
(#51 was a mistake)
Sorry, wrote incorrect. Reported for 17.04 LTS above.
Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the "Show
a clock in the menu bar" in System Settings for Time & Date. Worked
after cold reboot.
--
You received this bug notification because you are a member
Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the "Show
a clock in the menu bar" in System Settings for Time & Date. Worked
after cold reboot.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matchi
Seeing this on 17.10 as well. Battery indicator says ("estimating,
100%) and indicator-datetime-service uses between 2.4 GiB and (mostly)
~14.5 GiB RAM. CPU usage stays at 25% all the time. The indicator-
datetime-service crashes after reaching all available RAM, then restarts
with new PID.
I
PID changes after crash when RAM is depleted. Sceenshoot of RAM usage
attached.
** Attachment added: "Exampel of memory usage"
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+attachment/5008303/+files/Screenshot%20from%202017-11-13%2015-29-41.png
--
You received th
Public bug reported:
Same as Bug #774071 but with 100% RAM instead. Collected info while the
Indicator-datetime-service was acting up. I.e., writing this with a few
hundred megabytes RAM available..
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: indicator-datetime 15.10+17.04.20170322-0ubu
Also getting lots of these (new installation).
Sep 14 21:20:14 boll org.gnome.zeitgeist.Engine[1592]: message repeated 3
times: [ ** (zeitgeist-datahub:2095): WARNING **: zeitgeist-datahub.vala:212:
Error during inserting events:
GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Inco
I can confirm this in 13.10. Often when using dash some race condition
occurs and the whole unity interface gets distorted with a logoff
through terminal only solution. My zeitgeist-fts starts at 140 mb and
goes up depending on what task i perform on my desktop.
--
You received this bug notificat
12 matches
Mail list logo
