Re: Message: System program problem detected
Thomi Richards <[email protected]> Wed, 11 Mar 2015 16:19:30 +1300
| Newsgroups | gmane.org.user-groups.linux.dunedin.general |
|---|---|
| Message-ID | <CAN2KdQ88Rbfe_YaSQZ3AKkubKhbPoMBoNP4eoE9_6OMaVics0A@mail.gmail.com> |
Hi, On 11 March 2015 at 12:43, Kathinka <[email protected]> wrote: > Any ideas, please? look at the '*.crash' files in /var/crash - these are text files that contain the raw information apport dumped when something crashed. For example, I have: /var/crash/_usr_bin_mojo.1000.crash which contains: """ ProblemType: Crash CrashCounter: 1 CurrentDesktop: Unity Date: Fri Mar 6 11:39:51 2015 ExecutablePath: /usr/bin/mojo ExecutableTimestamp: 1424695094 InterpreterPath: /usr/bin/python2.7 ProcCmdline: /usr/bin/python /usr/bin/mojo workspace-new -p adt-rabbit --series trusty /home/thomi/code/canonical/canonical-mojo-specs/ci-trunk/ue/mojo-ue-adt-rabbit/ mojo-adt-rabbit """ and then a whole lot more. Those first few lines are usually enough to determine what crashed. Cheers, -- Thomi Richards _______________________________________________ DunLUG mailing list [email protected] http://lists.ethernal.org/listinfo/dunlug DunLUG Wiki - http://dunlug.kallisti.net.nz/