No worries from me. fixed MBR and deleted and re-aquired Ubuntu partition. Just too much. Not a Linux front-liner. Not a Linux anything.
[email protected] On Tue, Feb 9, 2010 at 4:36 PM, AndyRobbo <[email protected]> wrote: > Confirming. This also happened to me on first boot after upgrading from > 9.10 to 10.04 alpha 2. > > -- > cron crashed with SIGSEGV in _init() > https://bugs.launchpad.net/bugs/447080 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “cron” package in Ubuntu: Triaged > > Bug description: > Binary package hint: cron > > no run > > ProblemType: Crash > Architecture: i386 > Date: Fri Oct 9 10:40:01 2009 > Disassembly: 0xb8014004: Cannot access memory at address 0xb8014004 > DistroRelease: Ubuntu 9.10 > ExecutablePath: /usr/sbin/cron > Package: cron 3.0pl1-106ubuntu3 > ProcAttrCurrent: unconfined > ProcCmdline: /USR/SBIN/CRON > ProcEnviron: > LC_CTYPE=pl_PL.ISO-8859-2 > PATH=(custom, no user) > LANG=pl_PL.ISO8859-2 > ProcVersionSignature: Ubuntu 2.6.31-12.41-generic > SegvAnalysis: > Segfault happened at: 0xb8014004: Cannot access memory at address > 0xb8014004 > PC (0xb8014004) ok > Reason could not be automatically determined. > Signal: 11 > SourcePackage: cron > StacktraceTop: > ?? () > _init () from /lib/libpthread.so.0 > ?? () > ?? () > ?? () > Title: cron crashed with SIGSEGV in _init() > Uname: Linux 2.6.31-12-generic i686 > UserGroups: > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/cron/+bug/447080/+subscribe > -- cron crashed with SIGSEGV in _init() https://bugs.launchpad.net/bugs/447080 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
