Ubuntu 13.04 crashes even after reinstallation

[Tom Colley]

I have had numerous crashes since installing Ubuntu 13.04 from disk. Reinstalling from the same disk did not solve the problem. Typically, mouse actions begins to become unresponsive, and when shortcuts to log off or shutdown are tried, nothing happens. Eventually, I resort to regular use of SysRq to reboot the machine. I've maintained a log - see below - that indicates that the problem does not appear related to the opening/use of specific applications by the user. I am not sure if I've placed this bug report against the right package.

---------------------------------------------------
-------------Start of Log----------------------

Crashes/crashing have been occurring since installation of Ubuntu 13.04 on 17 May 2013 (installed as dual boot beside existing Windows Vista system.
I removed Firefox webapps related to Gmail and Gcalendar.
30/5/13 - having thought it was related to either Firefox or Libreoffice, when a crash happened without firefox being open (Libreoffice and Chrome were), I reinstalled Libreoffice. During the removal and re-installation process, I noticed that Writer retained my auto-correct and custom dictionary settings. Clearly, some files from the previous installation were carried across into the new one.
30/5/13 - Sometime after reinstallation of Libreoffice, I got an Ubuntu internal error message saying the error related to executable path was "...soffice.bin" i.e. Libreoffice
Sometime after this, the computer crashed.
30/5/13 - I ran memtest86+ from the Grub screen and allowed it to to run 3 times. It detected no errors in this time.
I found out that the place to look for crash log data is : /var/log/kern.log
30/5/13 - No crashes tonight - worked with libreoffice only, with occasional use of Chrome, closing Chrome when not needed.
31/5/13 - Today around 1300, the computer crashed about 30 min after startup. Libreoffice (Writer and Calc) were the only user-initiated programs running. Four files were open (a) xls, 2.7MB (b) xls, 134KB (c) doc, 641KB (d) odt, 44KB. Files (Nautilus?), Chrome and Firefox had been used earlier but weren't running at time of crash. I rebooted using SysRq s-u-b.
31/5/13 - 15.28 - Crash again. After operating for a short time (<20 minutes). User-initiated running software: Calc, Writer and Chrome. I rebooted using SysRq s-u-b.

---------------------
1/6/13 - I reinstalled Ubuntu 13.04 from CD. Before doing so, I saved a list of the installed packages. After reinstalling Ubuntu, I then reloaded these packages automtatically. Not everything got reloaded. e.g. not Chromium, not Tweak (even though these are in the standard Ubuntu repositories). I then worked for 1 hour without a crash using libreoffice.
2/6/13 - I had a crash at 1500 about 2 hours after booting up without having opened any Libreoffice apps. Graphics went funny and mouse became gradually less responsive. I rebooted using Alt+SysRq combination with s-u-b. I then ran "sudo dpkg --configure -a" which finished installation of some packages I'd been installing when the system crashed. I then ran "sudo apt-get -f install" and got the output in the point below - seems all is good!
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
kde-l10n-engb
Use 'apt-get autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

2/6/13 - Around 1730, I had another crash. The only user-initiated software that was running was nautilus, chromium and Libreoffice (writer and calc). After rebooting, I got a couple of "Internal Error" messages for Ubuntu, one related to the executable path .../Xorg.
2/6/13 - Around 2300, I had another crash. The only user-initiated software I was running was libreoffice (writer and calc).
2/6/13 - At 2350, I got an Ubuntu Internal Error message reporting an issue with executable path /usr/lib/libreoffice/program/soffice.bin (Title: soffice.bin crashed with SIGABRT in raise() )
3/6/13- I booted computer at 0815, and then it crashed around 1000. The only user-initiated software running was nautilus and libreoffice (writer and calc). Crash occurred immediately after opening Calc. Chromium had been running previously.
3/6/13 - Around midnight or soon after - computer crashed again, after/during being left alone for a while.
--------Commence working without USB Stick---------------

Note: Prior to this, I was regularly reading/writing data to a USB stick as part of my normal operation.
4/6/13 - 1200 - I revised my working method that had included standard use of files from my USB Stick. My main library will now be on the Vista partition of my laptop, with backups on the family drive and my USB Stick.
4/6/13 - 1400 - Computer crashed again. No USB stick in use. User initiated software: libreoffice (writer, 3 docs), chromium, nautilus (Files), Zotero Standalone. After reboot, I got an Ubuntu Report Internal Error dialog box (from Apport?) relating to exectuable path: /usr/lib/lbreoffice/program/soffice.bin. (Title: soffice.bin crashed with SIGABRT in raise() )
18/6/13 - I have been working daily with this Ubuntu 13.04 system and having crashes nearly every day, often 2 or 3 times a day.
------------------End of Log----------------
-------------------------------------------------

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: ubuntu-release-upgrader-core 1:0.192.11
ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
Uname: Linux 3.8.0-25-generic i686
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: i386
CrashDB: ubuntu
Date: Tue Jun 18 16:02:06 2013
InstallationDate: Installed on 2013-05-31 (17 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Tom Colley (tcolley)]

From my point of view, this bug could be closed. I reported it and the problem later resolved itself - somehow - I don't know how. But it's gone and the bug is probably not worth wasting time on. Not sure whether I should try to close this bug or leave that decision in the hands of the Janitors. Thanks bug-managers!