bonobo-activation-server segfaults and many gnome applets do not start when the date is set too early
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| libbonobo (Ubuntu) |
Low
|
Unassigned |
Bug Description
Binary package hint: gnome-panel
If the system clock is set to too early a date, there are many gnome-panel applets that will not start. Some of them are the clock applet, the notification area, and the user switcher.
I'm not sure what the threshold date is, but my ibook g4 has a bad logic board and resets the date to Jan. 1st 1904 on every boot. If I start the computer without an internet connection, I get a lot of error messages when gnome loads. If internet is available, then the time gets updated before the panel loads and there are no problems.
If you want to reproduce this error, just set the system time to a ridiculously old date and start ubuntu without internet available.
Sebastien Bacher (seb128) wrote : | #1 |
affects: | gnome-panel (Ubuntu) → libbonobo (Ubuntu) |
Changed in libbonobo (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Invalid |
Changed in libbonobo (Ubuntu): | |
status: | Invalid → Confirmed |
robepisc (robepisc) wrote : | #2 |
Sorry Sebastien, after extensive search (well, I did my best...) I couldn't find any bug this one is a duplicate of and you forgot to indicate this information.
So I reopen and confirm this bug on my Lucid machine, whose CMOS battery has died some months ago.
On every boot, the clock is set to Jan 1st 1904 and this makes bonobo-
See https:/
What's worst is that this makes gnome-panel emit a number of "applet failed to load" popups. In general, anything requiring Bonobo fails to boot, making my Gnome sessions almost unusable.
summary: |
- Many gnome applets do not start when the date is set too early + bonobo-activation-server segfaults and many gnome applets do not start + when the date is set too early |
robepisc (robepisc) wrote : | #3 |
I suppose the same error may happen in many other programs which expect the current time is above 1970-01-01.
So probably it would be a good idea for hwclock's upstart job to force the HW clock to 1970-01-01 whenever it is below that.
Please, tell me if I should open another bug for that (on package "util-linux"?).
Whenever bonobo-
The Hardware Clock registers contain values that are either invalid (e.g. 50th day of month) or beyond the range we can handle (e.g. Year 2095).
And here's what goes into dmesg:
[ 98.919182] bonobo-
[ 100.794036] bonobo-
[ 195.958973] bonobo-
[ 197.164949] bonobo-
[ 198.349928] bonobo-
Glen Turner (gdt-gdt) wrote : | #4 |
robepisc pointed this discussion out to me. See bug 90923 comment 19 onwards.
Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.