LibreOffice Crash if started other than opening a document

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

LibreOffice Crash if started other than opening a document

Ed Ahlsen-Girard-2
First message December 21, no replies. Text below is the Document
Foundation bugzilla bug and exchange with developers there.

I'm baffled that nobody else seems to has seen this.

Description:
If LibreOffice is opened from the command line or from the cwm start
menu, it displays a dialog box to the effect that due to an unexpected
error, LibreOffice crashed, that documents that had been open will be
recovered. In the case when there had not be a real crash, the are no
files in the list to choose recovery for. Closing the dialog box ends
the program. If the command line is used, this error appears in the
terminal window: Warning: failed to launch javaldx - java may not
function correctly

A dmesg (sanitized) is included.

Steps to Reproduce:
1. Run soffice without a filename as an argument.
2. Wait.
3. It will come

Actual Results:  
Crashes: can only be run by opening a document

Expected Results:
crashed, had to open a document


Reproducible: Always

User Profile Reset: Yes

Additional Info:
OpenBSD 6.0-current (GENERIC.MP) #87: Thu Dec 29 22:12:14 MST 2016
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4242014208 (4045MB)
avail mem = 4108795904 (3918MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf06d0 (43 entries)
bios0: vendor American Megatrends Inc. version "0504" date 10/05/2009
bios0: ASUSTeK Computer INC. P-P5G41
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP APIC MCFG OEMB HPET GSCI SSDT
acpi0: wakeup devices P0P2(S4) P0P3(S4) P0P1(S4) UAR1(S4) PS2K(S4)
USB0(S4) USB1(S4) USB2(S4) USB3(S4) EUSB(S4) MC97(S4) P0P4(S4) P0P5(S4)
P0P6(S4) P0P7(S4) P0P8(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24
bits acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat cpu0 at mainbus0:
apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU E7500 @
2.93GHz, 2933.69 MHz cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR
cpu0: 3MB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 266MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz, 2933.30 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR
cpu1: 3MB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf0000000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (P0P2)
acpiprt2 at acpi0: bus -1 (P0P3)
acpiprt3 at acpi0: bus 3 (P0P4)
acpiprt4 at acpi0: bus -1 (P0P5)
acpiprt5 at acpi0: bus 2 (P0P6)
acpiprt6 at acpi0: bus 1 (P0P7)
acpicpu0 at acpi0: !C2(500@1 mwait.1@0x10), C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: !C2(500@1 mwait.1@0x10), C1(1000@1 mwait.1), PSS
aibs0 at acpi0 RTMP RVLT RFAN GGRP GITM SITM
aibs0: FSIF: invalid package
"PNP0501" at acpi0 not configured
"PNP0303" at acpi0 not configured
acpibtn0 at acpi0: PWRB
cpu0: Enhanced SpeedStep 2933 MHz: speeds: 2936, 2670, 2403, 2136,
1870, 1603 MHz pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel G41 Host" rev 0x03
inteldrm0 at pci0 dev 2 function 0 "Intel G41 Video" rev 0x03
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp0: aperture at 0xe0000000, size 0x10000000
inteldrm0: msi
inteldrm0: 1920x1080
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel G41 Video" rev 0x03 at pci0 dev 2 function 1 not configured
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x01: msi
azalia0: codecs: Realtek ALC888
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01: msi
pci1 at ppb0 bus 3
xhci0 at pci1 dev 0 function 0 vendor "Fresco Logic", unknown product
0x1100 rev 0x01: msi usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Fresco Logic xHCI root hub"
rev 3.00/1.00 addr 1 ppb1 at pci0 dev 28 function 2 "Intel 82801GB
PCIE" rev 0x01: msi pci2 at ppb1 bus 2
re0 at pci2 dev 0 function 0 "Realtek 8168" rev 0x02: RTL8168C/8111C
(0x3c00), msi, address 48:5b:39:c5:63:95 rgephy0 at re0 phy 7:
RTL8169S/8110S/8211 PHY, rev. 2 ppb2 at pci0 dev 28 function 3 "Intel
82801GB PCIE" rev 0x01: msi pci3 at ppb2 bus 1
vendor "VIA", unknown product 0x3401 (class serial bus subclass
Firewire, rev 0x00) at pci3 dev 0 function 0 not configured vendor
"VIA", unknown product 0x401a (class mass storage subclass
miscellaneous, rev 0x00) at pci3 dev 0 function 1 not configured sdhc0
at pci3 dev 0 function 2 vendor "VIA", unknown product 0x401b rev 0x00:
apic 2 int 19 sdhc0: SDHC 1.0, 50 MHz base clock sdmmc0 at sdhc0:
4-bit, sd high-speed, mmc high-speed uhci0 at pci0 dev 29 function 0
"Intel 82801GB USB" rev 0x01: apic 2 int 23 uhci1 at pci0 dev 29
function 1 "Intel 82801GB USB" rev 0x01: apic 2 int 19 uhci2 at pci0
dev 29 function 2 "Intel 82801GB USB" rev 0x01: apic 2 int 18 uhci3 at
pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x01: apic 2 int 16
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x01: apic 2
int 23 usb1 at ehci0: USB revision 2.0 uhub1 at usb1 configuration 1
interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 ppb3 at pci0 dev
30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xe1 pci4 at ppb3 bus 4
pcib0 at pci0 dev 31 function 0 "Intel 82801GB LPC" rev 0x01 pciide0 at
pci0 dev 31 function 1 "Intel 82801GB IDE" rev 0x01: DMA, channel 0
configured to compatibility, channel 1 configured to compatibility
pciide0: channel 0 disabled (no drives) pciide0: channel 1 disabled (no
drives) pciide1 at pci0 dev 31 function 2 "Intel 82801GB SATA" rev
0x01: DMA, channel 0 configured to native-PCI, channel 1 configured to
native-PCI pciide1: using apic 2 int 19 for native-PCI interrupt wd0 at
pciide1 channel 0 drive 0: <Hitachi HDS721010CLA332> wd0: 16-sector
PIO, LBA48, 953869MB, 1953525168 sectors atapiscsi0 at pciide1 channel
0 drive 1 scsibus1 at atapiscsi0: 2 targets cd0 at scsibus1 targ 0 lun
0: <TEAC, DV-W524GS, BT11> ATAPI 5/cdrom removable wd0(pciide1:0:0):
using PIO mode 4, Ultra-DMA mode 6 cd0(pciide1:0:1): using PIO mode 4,
Ultra-DMA mode 5 ichiic0 at pci0 dev 31 function 3 "Intel 82801GB
SMBus" rev 0x01: apic 2 int 19 iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM non-parity PC2-6400CL6
spdmem1 at iic0 addr 0x52: 2GB DDR2 SDRAM non-parity PC2-6400CL6
usb2 at uhci0: USB revision 1.0
uhub2 at usb2 configuration 1 interface 0 "Intel UHCI root hub" rev
1.00/1.00 addr 1 usb3 at uhci1: USB revision 1.0
uhub3 at usb3 configuration 1 interface 0 "Intel UHCI root hub" rev
1.00/1.00 addr 1 usb4 at uhci2: USB revision 1.0
uhub4 at usb4 configuration 1 interface 0 "Intel UHCI root hub" rev
1.00/1.00 addr 1 usb5 at uhci3: USB revision 1.0
uhub5 at usb5 configuration 1 interface 0 "Intel UHCI root hub" rev
1.00/1.00 addr 1 isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
it0 at isa0 port 0x2e/2: IT8720F rev 2, EC port 0x290
vmm0 at mainbus0: VMX
uhub6 at uhub0 port 3 configuration 1 interface 0 "VIA Labs, Inc.
USB2.0 Hub" rev 2.10/90.90 addr 2 uhub7 at uhub0 port 7 configuration 1
interface 0 "VIA Labs, Inc. USB3.0 Hub" rev 3.00/90.91 addr 3 uhidev0
at uhub2 port 2 configuration 1 interface 0 "KYE Optica? Mouse" rev
1.10/1.01 addr 2 uhidev0: iclass 3/1 ums0 at uhidev0: 3 buttons, Z dir
wsmouse0 at ums0 mux 0
uhidev1 at uhub3 port 1 configuration 1 interface 0 "CPS UPS
CP1000AVRLCD" rev 1.10/0.01 addr 2 uhidev1: iclass 3/0, 24 report ids
upd0 at uhidev1
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on wd0a (51cdc1f6f7433a99.a) swap on wd0b dump on wd0b


User-Agent: Mozilla/5.0 (X11; OpenBSD amd64; rv:50.0) Gecko/20100101
Firefox/50.0

[tag] [reply] [−] Comment 1 Edward Ahlsen-Girard 2016-12-31 00:39:04 UTC

Created attachment 130044 [details]
screen capture of dialog box

[tag] [reply] [−] Comment 2 Buovjaga 2017-01-03 19:58:52 UTC

I got some feedback from #openbsd IRC channel @ Freenode:
is that related to wxallowed? https://www.openbsd.org/faq/upgrade60.html

Edward: can you check if that change to wxallowed mount option is the
cause?

Set to NEEDINFO.
Change back to UNCONFIRMED, if not. Change to RESOLVED NOTABUG, if you
solved it.

[tag] [reply] [−] Comment 3 Buovjaga 2017-01-03 20:06:15 UTC

Apparently it can't be because of wxallowed because dmesg after crash
should show if it's a w^x violation. Additionally, output of mount
should show if wxallowed is present.

A further advice was given: update to the latest snapshot, and package,
pkg_add -u

[tag] [reply] [−] Comment 4 Edward Ahlsen-Girard 2017-01-04 02:57:26 UTC

I'll try the new snapshot and get back.

The notion that wxallowed mount is required is surprising, since there
is no error if a file is passed as a startup argument: why would that
just that one code path in the whole application be the problem?

[tag] [reply] [−] Comment 5 Edward Ahlsen-Girard 2017-01-04 02:58:52 UTC

In any event, /usr/local is mounted wxallowed.

[tag] [reply] [−] Comment 6 Edward Ahlsen-Girard 2017-01-04 11:10:18 UTC

New snao and pkg_add -u, no change.

[tag] [reply] [−] Comment 7 Buovjaga 2017-01-05 11:44:02 UTC

Ok, maybe you could try seeking for testers on #openbsd @ Freenode or
some other gathering-place of OpenBSD folks. I don't have time to
install OpenBSD in a VM right now to test this..



--

Edward Ahlsen-Girard
Ft Walton Beach, FL

Reply | Threaded
Open this post in threaded view
|

Re: LibreOffice Crash if started other than opening a document

Mikolaj Kucharski-3
I had similar issue, was not even aware of it. For me following command
makes it work again:

        rm -rf ~/.config/libreoffice

It was on:

OpenBSD 6.0-current (GENERIC.MP) #97: Tue Jan  3 00:47:09 MST 2017
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP

with libreoffice-5.2.4.2p0v0 packaged at 2017-01-05T14:48:47Z


On Thu, Jan 05, 2017 at 09:30:08PM -0600, Ed Ahlsen-Girard wrote:

> First message December 21, no replies. Text below is the Document
> Foundation bugzilla bug and exchange with developers there.
>
> I'm baffled that nobody else seems to has seen this.
>
> Description:
> If LibreOffice is opened from the command line or from the cwm start
> menu, it displays a dialog box to the effect that due to an unexpected
> error, LibreOffice crashed, that documents that had been open will be
> recovered. In the case when there had not be a real crash, the are no
> files in the list to choose recovery for. Closing the dialog box ends
> the program. If the command line is used, this error appears in the
> terminal window: Warning: failed to launch javaldx - java may not
> function correctly
...

--
best regards
q#

Reply | Threaded
Open this post in threaded view
|

Re: LibreOffice Crash if started other than opening a document

Ed Ahlsen-Girard-2
In reply to this post by Ed Ahlsen-Girard-2
> I had similar issue, was not even aware of it. For me following
> command makes it work again:
>
> rm -rf ~/.config/libreoffice
>
> It was on:
>
> OpenBSD 6.0-current (GENERIC.MP) #97: Tue Jan  3 00:47:09 MST 2017
>     [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>
> with libreoffice-5.2.4.2p0v0 packaged at 2017-01-05T14:48:47Z
>
>
> On Thu, Jan 05, 2017 at 09:30:08PM -0600, Ed Ahlsen-Girard wrote:
> > First message December 21, no replies. Text below is the Document
> > Foundation bugzilla bug and exchange with developers there.
> >
> > I'm baffled that nobody else seems to has seen this.
> >
> > Description:
> > If LibreOffice is opened from the command line or from the cwm start
> > menu, it displays a dialog box to the effect that due to an
> > unexpected error, LibreOffice crashed, that documents that had been
> > open will be recovered. In the case when there had not be a real
> > crash, the are no files in the list to choose recovery for. Closing
> > the dialog box ends the program. If the command line is used, this
> > error appears in the terminal window: Warning: failed to launch
> > javaldx - java may not function correctly
> ...
>
> --
> best regards
> q#

Thanks, I've tried that, and it works the first time. The issue always
comes back.

--

Edward Ahlsen-Girard
Ft Walton Beach, FL

Reply | Threaded
Open this post in threaded view
|

Re: LibreOffice Crash if started other than opening a document

Robert Nagy
Try a different window manager.

On (2017-01-09 18:28), Ed Ahlsen-Girard wrote:

> > I had similar issue, was not even aware of it. For me following
> > command makes it work again:
> >
> > rm -rf ~/.config/libreoffice
> >
> > It was on:
> >
> > OpenBSD 6.0-current (GENERIC.MP) #97: Tue Jan  3 00:47:09 MST 2017
> >     [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> >
> > with libreoffice-5.2.4.2p0v0 packaged at 2017-01-05T14:48:47Z
> >
> >
> > On Thu, Jan 05, 2017 at 09:30:08PM -0600, Ed Ahlsen-Girard wrote:
> > > First message December 21, no replies. Text below is the Document
> > > Foundation bugzilla bug and exchange with developers there.
> > >
> > > I'm baffled that nobody else seems to has seen this.
> > >
> > > Description:
> > > If LibreOffice is opened from the command line or from the cwm start
> > > menu, it displays a dialog box to the effect that due to an
> > > unexpected error, LibreOffice crashed, that documents that had been
> > > open will be recovered. In the case when there had not be a real
> > > crash, the are no files in the list to choose recovery for. Closing
> > > the dialog box ends the program. If the command line is used, this
> > > error appears in the terminal window: Warning: failed to launch
> > > javaldx - java may not function correctly
> > ...
> >
> > --
> > best regards
> > q#
>
> Thanks, I've tried that, and it works the first time. The issue always
> comes back.
>
> --
>
> Edward Ahlsen-Girard
> Ft Walton Beach, FL
>

Reply | Threaded
Open this post in threaded view
|

Re: LibreOffice Crash if started other than opening a document

David Coppa
On Wed, Jan 11, 2017 at 11:55 AM, Robert Nagy <[hidden email]> wrote:
> Try a different window manager.

Or you can try with wmname.

Install wmname with 'pkg_add wmname'

And then put:

/usr/local/bin/wmname LG3D

into your ~/.xinitrc right before the line that exec your window manager...

Ciao!
David

> On (2017-01-09 18:28), Ed Ahlsen-Girard wrote:
>> > I had similar issue, was not even aware of it. For me following
>> > command makes it work again:
>> >
>> >     rm -rf ~/.config/libreoffice
>> >
>> > It was on:
>> >
>> > OpenBSD 6.0-current (GENERIC.MP) #97: Tue Jan  3 00:47:09 MST 2017
>> >     [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>> >
>> > with libreoffice-5.2.4.2p0v0 packaged at 2017-01-05T14:48:47Z
>> >
>> >
>> > On Thu, Jan 05, 2017 at 09:30:08PM -0600, Ed Ahlsen-Girard wrote:
>> > > First message December 21, no replies. Text below is the Document
>> > > Foundation bugzilla bug and exchange with developers there.
>> > >
>> > > I'm baffled that nobody else seems to has seen this.
>> > >
>> > > Description:
>> > > If LibreOffice is opened from the command line or from the cwm start
>> > > menu, it displays a dialog box to the effect that due to an
>> > > unexpected error, LibreOffice crashed, that documents that had been
>> > > open will be recovered. In the case when there had not be a real
>> > > crash, the are no files in the list to choose recovery for. Closing
>> > > the dialog box ends the program. If the command line is used, this
>> > > error appears in the terminal window: Warning: failed to launch
>> > > javaldx - java may not function correctly
>> > ...
>> >
>> > --
>> > best regards
>> > q#
>>
>> Thanks, I've tried that, and it works the first time. The issue always
>> comes back.
>>
>> --
>>
>> Edward Ahlsen-Girard
>> Ft Walton Beach, FL
>>
>



--
"If you try a few times and give up, you'll never get there. But if
you keep at it... There's a lot of problems in the world which can
really be solved by applying two or three times the persistence that
other people will."
                -- Stewart Nelson

Reply | Threaded
Open this post in threaded view
|

Re: LibreOffice Crash if started other than opening a document

Erling Westenvik-2
In reply to this post by Ed Ahlsen-Girard-2
On Thu, Jan 05, 2017 at 09:30:08PM -0600, Ed Ahlsen-Girard wrote:
> Steps to Reproduce:
> 1. Run soffice without a filename as an argument.
> 2. Wait.
> 3. It will come

Well, thank YOU, pal. Now I have to edit my upcoming book "1001 ways to
easily crash LibreOffice".. ;)
 
--
Erling Westenvik

Reply | Threaded
Open this post in threaded view
|

Re: LibreOffice Crash if started other than opening a document

Ed Ahlsen-Girard-2
In reply to this post by Ed Ahlsen-Girard-2
On Wed, 11 Jan 2017 11:55:02 +0100
Robert Nagy <[hidden email]> wrote:

> Try a different window manager.
>
> On (2017-01-09 18:28), Ed Ahlsen-Girard wrote:
>  [...]  
>  [...]  
>  [...]  
>  [...]  

Switching to fvwm and leaving the profile directory in place, same
results. After deleting the profile directory, LibreOffice starts
normally and started normally again after shutting it down (so that a
new profile was in place).

--

Edward Ahlsen-Girard
Ft Walton Beach, FL

Reply | Threaded
Open this post in threaded view
|

Re: LibreOffice Crash if started other than opening a document

Ed Ahlsen-Girard-2
In reply to this post by Robert Nagy
On Wed, 11 Jan 2017 12:51:12 +0100
David Coppa <[hidden email]> wrote:

> On Wed, Jan 11, 2017 at 11:55 AM, Robert Nagy <[hidden email]>
> wrote: [...]  
>
> Or you can try with wmname.
>
> Install wmname with 'pkg_add wmname'
>
> And then put:
>
> /usr/local/bin/wmname LG3D
>
> into your ~/.xinitrc right before the line that exec your window
> manager...
>
> Ciao!
> David
>
>  [...]  
>  [...]  
>  [...]  
>  [...]  
>  [...]  
>  [...]  
>
>
>

That did the trick. Thank you.

--

Edward Ahlsen-Girard
Ft Walton Beach, FL