Sorry, the program "indicator-datetime-service" closed unexpectedly

Bug #1052468 reported by Cliff Carson
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
indicator-datetime (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers.

See this message popup shortly after boot. No other indications of problems. No further information can be found in the System Logs. No indication after the problem that there was any shortage of memory.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: indicator-datetime 12.10.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Tue Sep 18 08:34:53 2012
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120822)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: indicator-datetime
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Cliff Carson (ccarson1) wrote :
Revision history for this message
Alan Pope 🍺🐧🐱 🦄 (popey) wrote :

I just had this, and it's lying :) Loads of memory and disk space available.

Awful load average though...

top - 23:50:04 up 11:50, 5 users, load average: 138.19, 68.07, 26.14
Tasks: 434 total, 2 running, 431 sleeping, 0 stopped, 1 zombie
%Cpu0 : 2.3 us, 1.0 sy, 0.0 ni, 96.3 id, 0.0 wa, 0.0 hi, 0.3 si, 0.0 st
%Cpu1 : 1.7 us, 1.4 sy, 0.0 ni, 96.9 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu2 : 1.4 us, 0.7 sy, 0.0 ni, 98.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu3 : 1.0 us, 1.3 sy, 0.0 ni, 97.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu4 : 0.7 us, 0.3 sy, 0.0 ni, 99.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu5 : 0.7 us, 0.7 sy, 0.0 ni, 98.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu6 : 0.7 us, 0.3 sy, 0.0 ni, 99.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
%Cpu7 : 0.3 us, 0.3 sy, 0.0 ni, 99.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem: 8024512 total, 7451996 used, 572516 free, 495152 buffers
KiB Swap: 4805628 total, 222196 used, 4583432 free, 3010332 cached

Filesystem Size Used Avail Use% Mounted on
/dev/sdc1 76G 16G 57G 22% /
udev 3.9G 4.0K 3.9G 1% /dev
tmpfs 1.6G 1.1M 1.6G 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 3.9G 4.5M 3.9G 1% /run/shm
none 100M 76K 100M 1% /run/user
cgroup 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/sda1 917G 266G 605G 31% /home
none 3.9G 58M 3.8G 2% /tmp/guest-0NZmfB
gvfsd-fuse 917G 266G 605G 31% /home/alan/.gvfs
/home/alan/.Private 917G 266G 605G 31% /home/alan

Changed in indicator-datetime (Ubuntu):
status: New → Confirmed
Revision history for this message
Bilal Shahid (s9iper1) wrote :

i have also experienced this crash and the same case. dont know how to reproduce it.

Changed in indicator-datetime (Ubuntu):
importance: Undecided → Low
Omer Akram (om26er)
Changed in indicator-datetime (Ubuntu):
importance: Low → Undecided
Revision history for this message
Charles Kerr (charlesk) wrote :

Popey, did this just happen the once for you, or are you able to reproduce it?

Revision history for this message
crtm (carlosrtm) wrote :

datetime disappear and reinstall with "sudo apt-get install datetime"

Revision history for this message
Charles Kerr (charlesk) wrote :

 Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in indicator-datetime (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for indicator-datetime (Ubuntu) because there has been no activity for 60 days.]

Changed in indicator-datetime (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.