I confirm too the bad behaviour with Google account. Worked around deactivating
calendar sync.
This is a problem, anyway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
I confirm the bad behavior on my side with google account enabled..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
To manage
The problem seems to be that one call to
e_cal_client_get_objects_for_uid does not result in a callback when
querying a uid with infinite entries. Probably ecal tries to fetch all
of them?
Is there a different ecal function that one could call? How is it done
in Evolution or Gnome calendar, so
Output generated with:
valgrind --tool=massif
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
Can be viewed with:
ms_print massif.out.8535 | less
Might be the following function be at fault?
unity::indicator::datetime::EdsEngine::Impl::fetch_detached_instances(_GObject*,
This is still an issue in Ubuntu 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
To manage notifications about this bug go to:
No. I see it in 17.10 as of today (2018-01-09). I cannot log intro Unity
because of this bug. Right after login, indicator-datetime-service" eats
all of my CPU, breaks, starts again, eats all of my CPU, breaks, starts
again, eats all of my CPU, breaks, starts again, eats all of my CPU,
breaks,
The problem went away in 17.10. Cheers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
To manage notifications about this bug go to:
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
(#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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
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
Seeing this after upgrade from 16.04 to 16.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
To manage notifications about this bug
Since I upgraded to 12.04 recently I've started to notice this problem.
Namely, indicator-datetime-service was still running at 100% CPU, and
was quickly restarted (with just highter PID) after killing its process.
However, I was puzzled why at the same time some geoclue- related
service also
Don't expect anybody to read a bug report that has a fix released
state since 2011. Either change the state of this bug report or file a
new one (I think the latter would be better actually, but i did not read
the whole thread in detail).
--
You received this bug notification because you are a
It's a great problem for me, because i've got multi-user machines. So
it's about 3 or 5 datetime-indicator-service processes on every machine
and each one consumes whole core.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am having this same problem also. I have to restart to make it go
away. This happens every once in awhile. I did not notice any other
processes using much cpu. It affects 1 of 2 cores. I am using LinuxMint
14.1 and will post it to that launchpad, but wanted to inform this group
as LM is an
I experienced the similar problem on 12.10 and 13.04
indicator-datetime-service together with gnome-settings-daemon - process kept
eating RAM and used 100% CPU. Problem turned out to be some corrupted cache
files in ~/.cache/ . Upon deleting them, problem stopped.
It first began then I used
After the upgrade to Ubuntu 12.10, I have to kill indicator-datetime-
service everytime at startup to stop cpu usage and constant access to
hdd and turn the system usable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the same issue like jherazob. Maybe this is a new issue compared
to the 100% cpu issue discussed above?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service
Quick demonstration of the effect i mentioned is attached, as a
recordmydesktop ogv video capture
Turning off alternate locations will not solve the issue, it'll still be
there open and taking up all of the CPU. Also, the involved processes
will only occasionally stay dead, they typically
I suspect it's linked to geoclue.
Just now i killed geclue-master, which remained open and taking CPU
after i killed indicator-datetime, and system load and CPU usage went
drastically down. And before that, the locations on the indicator
flashed in and out of existence (flashing between being and
I am now having this problem too, after just upgrading to 12.04 from
11.10. I have noticed 2 things that may be relevant:
(1) It only occurs when booting with lightdm as display manager. I'm a
KDE user, and when I switched back to kdm, the problem went away. I've
switched between lightdm and kdm
The problem for me is gone after installing 12.04.
On Thu, May 03, 2012 at 06:03:12PM -, RawwrBag wrote:
Hit the same issue today on 12.4. I was unable to unlock my desktop
until I killed indicator-datetime-service from a virtual terminal.
--
You received this bug notification because
Hit the same issue today on 12.4. I was unable to unlock my desktop
until I killed indicator-datetime-service from a virtual terminal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Does anyone still work on this? I have tried the ubuntu standard WM
again (unity), but still I have 100% CPU consumed by indicator-date-time
and it is eating memory (was 1.1% after restarting the computer, now
11.1% after ten minutes).
--
You received this bug notification because you are a
This bug is still not solved for me today. I'm on a macbook pro 6,2 with
an uptotdate 11.10 ubuntu.
indicator-datetime 0.3.1-0ubuntu1.1
I did the following:
$ gdb program 27962 (where 27962 is the PID of indicator-datetime)
This stops the application from eating all my CPU! Does that say
Hi guys, I still have this bug (I'm running natty). Any chance that the
fix will land here???
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU
P Cantwall, sounds great -- now we only need to do this 98 more times
and things will be perfect! ;)
In the OP's description, it was indicator-datetime-service that was
pegging to 100%. In your snapshot in comment #32 it's e-calendar-factory
going crazy, so it's possible that you're encountering
That's pretty good: it's down to 98% now. Ubuntu 11.10 Evo 3.2.1.
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
24579 pete 20 0 769m 475m 6760 S 98 23.7 0:33.85 e-calendar-fact
23083 pete 20 0 545m 89m 36m R4 4.4 0:51.38
BTW, 11.10 and Evolution 3.2.1, but I had it in 10.10 11.04 and
Evolution 2.whatever.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
E-calendar-factory will peruse my calendar data periodically, possibly
to determine if I have to be reminded of something. However, I keep a
very large amount of historical data in my calendar. Because of this, e
-calendar-factory takes a very long time to search, all the while taking
100% of one
This bug still haunts natty, which still has indicator-datetime 0.2.3.
Is there any hope for the fixed package finding its way into natty-
updates?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
** Branch linked: lp:~indicator-applet-developers/indicator-
datetime/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
To manage
** Changed in: indicator-datetime
Milestone: None = 0.3.0
** Changed in: indicator-datetime
Status: In Progress = Fix Released
** Changed in: unity-foundations
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Branch linked: lp:~ubuntu-desktop/indicator-datetime/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
To manage notifications
Now, the fix should prevent dbus-daemon to get to 100% CPU, but there's
still excess traffic caused by e-calendar-factory. I will continue on
investigating that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package indicator-datetime - 0.3.0-0ubuntu1
---
indicator-datetime (0.3.0-0ubuntu1) oneiric; urgency=low
[ Ken VanDine ]
* debian/control
- Added recommends for e-d-s
[ Ted Gould ]
* New upstream release.
* Fix corrupt environment when
I get this bug constantly. Clicking the indicator and selecting
Refresh seems to often trigger the problem.
Doing a quick ltrace when it's in hog mode shows:
e_cal_get_source(0x92a14a0, 0xb7843b31, 5, 0xb78575ac, 0x92a14a0)
= 0xb2e013b0
the recent comment is interesting, thanks James, random idea about the
issue:
could it happen if you have a calendar that requires authentification
but is not unlocked? in natty the indicator was segfaulting on those
but made to ignore them because there was an issue with the ui, maybe
it's
aq1018, James: Thanks for the info!
Sebastian: I will check that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
To manage
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
To manage notifications about this bug go to:
I got the core dump for indicator-datetime.
http://dl.dropbox.com/u/7022019/core.1815
Size is about 110MB.
I'm using Ubuntu 11.10 beta and got this core dump when both indicator-
datetime and dbus-daemon are taking out most of my cup cycles.
--
You received this bug notification because you
** Changed in: unity-foundations
Milestone: oneiric-beta-2 = oneiric-final
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
To
@Antti: I've had this bug as well. It was essentially EDS configured
with an extra gmail account trying to sync/import my online calendar;
except that the authenication was not working because i had removed the
password from the keyring, or the keyring was not unlocked because I had
cancelled the
Unfortunately the core dump TImo provided was from dbus-daemon. Not much
happening there :(
I've tried to reproduce, but no luck yet.
If someone sees the bug happening, please, provide a core dump of the
indicator-datetime-service process. Thanks!
--
You received this bug notification because
This happens to me often in 11.10. I've never experienced it in 11.04. I
have no idea how to reproduce it. It just happens when I leave my
computer running for some time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If someone happens to stumble upon this bug on a live system, please try to
provide core dump with gdb:
(gdb) generate-core-file
That way I can debug the problem on my end even though there would be no
debug symbols available on your end (like in the backtrace Ted
provided).
Thanks!
** Changed
the corefile is 87MB, I've put it here:
http://koti.kapsi.fi/~tjaalton/tmp
it'll take ~15min to upload though..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Thank you Timo!
** Changed in: indicator-datetime (Ubuntu)
Assignee: (unassigned) = Antti Kaijanmäki (kaijanmaki)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
This problem is happening quite often so should be reproduce able.
I think Evolution calendar has something to do with the load. However evolution
needs not to be running. EDS would be enough.
Also I believe it to be related to dbus because I see my 2 cpu cores burned by
1 indicator-datetime
** Changed in: indicator-datetime
Assignee: Javier Jardón (jjardon) = Antti Kaijanmäki (kaijanmaki)
** Changed in: unity-foundations
Assignee: Javier Jardón (jjardon) = Antti Kaijanmäki (kaijanmaki)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I had it happen just now and I grabbed the process with GDB and stole a
backtrace. Not sure if this is telling, but I thought I'd safe it here
:-)
(gdb) bt
#0 0x7fe4539118bd in nanosleep () at ../sysdeps/unix/syscall-template.S:82
#1 0x7fe453b8cd32 in g_usleep (microseconds=optimized
I don't have i-weather installed and get this, too, so it seems
unrelated to weather. When this happens, dbus-daemon is also spinning at
100% CPU. It seems indicator-datetime is stuck in a tight loop and sends
a million d-bus calls to evolution-data-server. Apparenlty it fails to
check the d-bus
** Changed in: indicator-datetime (Ubuntu)
Importance: Low = High
** Changed in: indicator-datetime
Status: Incomplete = Confirmed
** Changed in: unity-foundations
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: unity-foundations
Milestone: None = oneiric-beta-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
To manage
** Also affects: unity-foundations
Importance: Undecided
Status: New
** Changed in: unity-foundations
Status: New = Incomplete
** Changed in: unity-foundations
Importance: Undecided = Medium
** Changed in: indicator-datetime
Importance: Low = Medium
** Changed in:
** Changed in: indicator-datetime (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
To
@Jelmer: what indicators have you installed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
To manage notifications about this bug go
I can reproduce this as well - and I also see fairly high CPU usage from
dbus-daemon when this happens, similar to Romano.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
This is with the current version of indicator-datetime on Oneiric.
I'll try to grab a traceback next time this happens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
[Expired for indicator-datetime (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: indicator-datetime (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Happened to me. My guess is the wild e-calendar-fact(ory, I suppose)
which make dbus and the indicator applet spin like crazy. As you can see
in the attached screenshot, the indicator-datetime applet do not show
anything when clicking...
** Attachment added: screenshot with top during the problem
I see this bug on Ubuntu 11.04 in Classic mode immediately after boot up
as well. I'm not using the Gnome panels, but deleted those in favor of
the AWN dock. I do have weather-indicator installed on the system and I
cannot get it to not load with AWN, but I exit it immediately upon boot
up
OK, after uninstalling the Gnome weather indicator and restarting, none
of my CPUs pegs at 100%. It indeed looks like indicator-weather is
related to the issue, though that's counter-intuitive with indicator-
datetime. Since I'm using AWN and have deleted the standard Gnome panels
in 11.04,
I see this bug too on Ubuntu 11.04 in Classic mode. The first time
realizing this bug was after installing the weather indicator from
http://ppa.launchpad.net/weather-indicator-team/ppa/ubuntu repo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry, Sebastien Bacher, but the bug have not occured to me since I
reported it, so I have not had a chance to make a backtrace.
However, I, like Christian Holschuh, also have indicator-weather
installed. It might be related.
--
You received this bug notification because you are a member of
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down
See this too. Ubuntu 11.04 32 bits, updated from 10.10.
The process with 100% CPU was the oldest (smaller PID), after killing it
everything seems back to normal, with the remaining indicator working
ok.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
69 matches
Mail list logo
