libreoffice-writer becomes non-responsive

[Lorin Soura]

Writer crashed suddenly and will not reopen. I transferred the file I was working on to another computer and the file was locked for editing. I have managed to recover the document but still cannot restart Writer, even after a removal/re-installation of the libreoffice package. The other libreoffice programs are working fine.

root@nemesis:/home/chaos# lsb_release -rd
Description: Ubuntu 14.04.3 LTS
Release: 14.04

root@nemesis:/home/chaos# lshw -short
H/W path Device Class Description
======================================================
                            system TravelMate B113 (TravelMate B113_0748
/0 bus BA10_HX
/0/0 memory 128KiB BIOS
/0/4 processor Intel(R) Pentium(R) CPU 987 @ 1.50GHz
/0/4/9 memory 32KiB L1 cache
/0/4/a memory 256KiB L2 cache
/0/4/b memory 2MiB L3 cache
/0/8 memory 32KiB L1 cache
/0/18 memory 4GiB System Memory
/0/18/0 memory 2GiB SODIMM DDR3 Synchronous 1333 MHz
/0/18/1 memory 2GiB SODIMM DDR3 Synchronous 1333 MHz
/0/100 bridge 2nd Generation Core Processor Family
/0/100/2 display 2nd Generation Core Processor Family
/0/100/16 communication 7 Series/C210 Series Chipset Family M
/0/100/1a bus 7 Series/C210 Series Chipset Family U
/0/100/1b multimedia 7 Series/C210 Series Chipset Family H
/0/100/1c bridge 7 Series/C210 Series Chipset Family P
/0/100/1c.1 bridge 7 Series/C210 Series Chipset Family P
/0/100/1c.1/0 wlan0 network Centrino Advanced-N 6235
/0/100/1c.2 bridge 7 Series/C210 Series Chipset Family P
/0/100/1c.2/0 p2p1 network NetLink BCM57785 Gigabit Ethernet PCI
/0/100/1c.2/0.1 generic BCM57765/57785 SDXC/MMC Card Reader
/0/100/1d bus 7 Series/C210 Series Chipset Family U
/0/100/1f bridge 7 Series Chipset Family LPC Controlle
/0/100/1f.2 storage 7 Series Chipset Family 6-port SATA C
/0/100/1f.3 bus 7 Series/C210 Series Chipset Family S
/0/1 scsi0 storage
/0/1/0.0.0 /dev/sda disk 320GB ST320LT020-9YG14
/0/1/0.0.0/1 /dev/sda1 volume 1047MiB Windows FAT volume
/0/1/0.0.0/2 /dev/sda2 volume 9510MiB Linux swap volume
/0/1/0.0.0/3 /dev/sda3 volume 287GiB EXT4 volume

Package: libreoffice
Status: install ok installed
Priority: optional
Section: metapackages
Installed-Size: 161
Maintainer: Ubuntu Developers <email address hidden>
Architecture: amd64
Version: 1:4.2.8-0ubuntu2

root@nemesis:/home/chaos# ps aux | grep "libre"
chaos 2222 0.0 0.0 133404 3220 ? Sl 01:36 0:00 /usr/lib/libreoffice/program/oosplash --writer
chaos 2250 0.1 2.7 1264024 105616 ? Sl 01:36 0:03 /usr/lib/libreoffice/program/soffice.bin --writer --splash-pipe=5
root 4451 0.0 0.0 11744 936 pts/1 S+ 02:16 0:00 grep --color=auto libre

Killed processes, restarted Writer, got a recovery window (see attached screenshot), Writer crashed again after trying to recover "untitled: in recovery screen. That was not the document I was working on when the program crashed. I have not used Writer on this particular computer until just recently...

root@nemesis:/home/chaos# ps aux | grep "libre"
chaos 4515 0.0 0.1 141600 5264 ? Sl 02:23 0:00 /usr/lib/libreoffice/program/oosplash --writer
chaos 4534 0.7 2.5 1232148 97156 ? Sl 02:23 0:01 /usr/lib/libreoffice/program/soffice.bin --writer --splash-pipe=5
root 4643 0.0 0.0 11740 936 pts/1 S+ 02:26 0:00 grep --color=auto libre

root@nemesis:/home/chaos# kill -9 4515 4534

root@nemesis:/home/chaos# ps aux | grep "libre"
root 4645 0.0 0.0 11740 936 pts/1 S+ 02:27 0:00 grep --color=auto libre

Restarted again and skipped through the recovery screens for "untitled" and managed to get Writer restarted. This still may cause a problem in the future as I do not know what caused the initial crash. Writer was locked up even after a logout and a reboot. I reinstalled the libreoffice package and still could not get Writer running until I went through the process kill in terminal. Program seems to be functioning normally for now...

Hope you have enough info on this one...
):}>

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libreoffice-writer 1:4.2.8-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
Uname: Linux 3.13.0-63-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.13
Architecture: amd64
Date: Fri Sep 18 01:46:25 2015
InstallationDate: Installed on 2014-05-13 (492 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

[Lorin Soura (gr8can8dian)]

There is no crash report. I followed your instructions to the letter.
libreoffice just crashed and will not open. Clicking on the icon produces a
greyed-out desktop screen with a small window that says "view contents of
filesystem" when you hover over it. I suspect that it is a graphics-related
issue with my hardware.

On Fri, Sep 18, 2015 at 3:01 AM, Christopher M. Penalver <
<email address hidden>> wrote:

> Lorin Soura, thank you for reporting this and helping make Ubuntu better.
> However, your crash report is missing. Please follow these instructions to
> have apport report a new bug about your crash that can be dealt with by the
> automatic retracer. First, execute at a terminal:
> cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y
> upgrade && sudo apt-get -y install libreoffice-dbg uno-libs3-dbg ure-dbg &&
> sudo service apport start force_start=1
>
> If you are running the Ubuntu Stable Release you might need to enable
> apport in /etc/default/apport and restart.
>
> Now reproduce the crash, then open your file manager, navigate to your
> /var/crash directory and open the crash report you wish to submit.
> If this fails you will have to open a terminal and file your report with
> 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash
> is the crash you would like to report. If you get an error that you aren't
> allowed to access this report you will have to file it with 'sudo
> ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command
> against the crash report and a window pops up asking you to report this,
> but then never opens a new report, you would be affected by
> https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order
> to WORKAROUND this, one would need to open the following file via a command
> line:
> sudo nano /etc/apport/crashdb.conf
>
> and comment out the line:
> 'problem_types': ['Bug', 'Package'],
>
> by changing it to:
> # 'problem_types': ['Bug', 'Package'],
>
> Save, close, and try to file the crash report again via:
> ubuntu-bug /var/crash/_my_crash_report.crash
>
> Please follow https://wiki.ubuntu.com/LibreOfficeBugWrangling when you
> file this crash report so the necessary information is provided.
>
> I'm closing this bug report since the process outlined above will
> automatically open a new bug report which can then dealt with more
> efficiently.
>
> Please do not attach your crash report manually to this report and
> reopen it.
>
> As well, please do not announce in this report you created a new bug
> report.
>
> Thank you for your understanding.
>
> Helpful bug reporting tips:
> https://wiki.ubuntu.com/ReportingBugs
>
> ** Changed in: libreoffice (Ubuntu)
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1497196
>
> Title:
> libreoffice-writer crashed and will not restart
>
> Status in libreoffice package in Ubuntu:
> Invalid
>
> Bug description:
> Writer crashed suddenly and will not reopen. I transferred the file I
> was working on to another computer and the file was locked for
> editing. I have managed to recov...

[Lorin Soura (gr8can8dian)]

On Thu, Oct 1, 2015 at 11:51 AM, Lorin Soura <email address hidden> wrote:

> There is no crash report. I followed your instructions to the letter.
> libreoffice just crashed and will not open. Clicking on the icon produces a
> greyed-out desktop screen with a small window that says "view contents of
> filesystem" when you hover over it. I suspect that it is a graphics-related
> issue with my hardware.
>
> On Fri, Sep 18, 2015 at 3:01 AM, Christopher M. Penalver <
> <email address hidden>> wrote:
>
>> Lorin Soura, thank you for reporting this and helping make Ubuntu better.
>> However, your crash report is missing. Please follow these instructions to
>> have apport report a new bug about your crash that can be dealt with by the
>> automatic retracer. First, execute at a terminal:
>> cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y
>> upgrade && sudo apt-get -y install libreoffice-dbg uno-libs3-dbg ure-dbg &&
>> sudo service apport start force_start=1
>>
>> If you are running the Ubuntu Stable Release you might need to enable
>> apport in /etc/default/apport and restart.
>>
>> Now reproduce the crash, then open your file manager, navigate to your
>> /var/crash directory and open the crash report you wish to submit.
>> If this fails you will have to open a terminal and file your report with
>> 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash
>> is the crash you would like to report. If you get an error that you aren't
>> allowed to access this report you will have to file it with 'sudo
>> ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command
>> against the crash report and a window pops up asking you to report this,
>> but then never opens a new report, you would be affected by
>> https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order
>> to WORKAROUND this, one would need to open the following file via a command
>> line:
>> sudo nano /etc/apport/crashdb.conf
>>
>> and comment out the line:
>> 'problem_types': ['Bug', 'Package'],
>>
>> by changing it to:
>> # 'problem_types': ['Bug', 'Package'],
>>
>> Save, close, and try to file the crash report again via:
>> ubuntu-bug /var/crash/_my_crash_report.crash
>>
>> Please follow https://wiki.ubuntu.com/LibreOfficeBugWrangling when you
>> file this crash report so the necessary information is provided.
>>
>> I'm closing this bug report since the process outlined above will
>> automatically open a new bug report which can then dealt with more
>> efficiently.
>>
>> Please do not attach your crash report manually to this report and
>> reopen it.
>>
>> As well, please do not announce in this report you created a new bug
>> report.
>>
>> Thank you for your understanding.
>>
>> Helpful bug reporting tips:
>> https://wiki.ubuntu.com/ReportingBugs
>>
>> ** Changed in: libreoffice (Ubuntu)
>> Status: New => Invalid
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1497196
>>
>> Title:
>> libreoffice-writer crashed and will not restart
>>
>> Status in libreoffice package in Ubuntu:
>> Invalid
>>
>> Bug description:
>> Writer crash...

[penalvch (penalvch)]

Lorin Soura, as per the screenshot it looks that while LibreOffice is still actually running, it has become non-responsive.

[penalvch (penalvch)]

Lorin Soura, ok so part of your problem may very well be that you used a Server ISO (non-GUI) and installed a GUI on top of it. Hence, if you install Ubuntu via the Desktop (GUI) ISO, is this still reproducible?

[Launchpad Janitor (janitor)]

[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]