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-activation-server segfaults, running "sudo hwclock -r" returns this: 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-activati[1519]: segfault at 4 ip 08052922 sp b7579e30 error 4 in bonobo-activation-server[8048000+15000] [ 100.794036] bonobo-activati[1526]: segfault at 4 ip 08052922 sp b6d97e30 error 4 in bonobo-activation-server[8048000+15000] [ 195.958973] bonobo-activati[1587]: segfault at 4 ip 08052922 sp b6d45e30 error 4 in bonobo-activation-server[8048000+15000] [ 197.164949] bonobo-activati[1593]: segfault at 4 ip 08052922 sp b6d38e30 error 4 in bonobo-activation-server[8048000+15000] [ 198.349928] bonobo-activati[1598]: segfault at 4 ip 08052922 sp b6ee1e30 error 4 in bonobo-activation-server[8048000+15000] -- bonobo-activation-server segfaults and many gnome applets do not start when the date is set too early https://bugs.launchpad.net/bugs/422215 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
